Database Users

[RECOVERY] ClockworkMod Recovery for Captivate (FINAL! SAFE!)

First things first, if you flashed a previous version of Clockwork Recovery using Odin, FLASH BACK TO A STOCK KERNEL using this Odin package:
http://koush.tandtgaming.com//test/kernel-captivate-stock.tar.md5
This recovery is *very* safe to use. It does NOT flash your kernel; it is a completely uninvasive recovery method.
How it works: The recovery is packaged as an update.zip that you run from STOCK recovery. The update.zip unpacks Clockwork Recovery onto the ramdisk and restarts recovery. When you reboot, it reverts back to the original, unmodified, stock recovery. So, you will need to keep the recovery on the root of your SD card as an update.zip, and apply the zip every time you want to start Clockwork.
HOWEVER, if you use ROM Manager, all of the recovery installation and management instructions are done for you!
Installation instructions:
Download ROM Manager from the Market.
Flash Recovery.
Choose Captivate as your phone.
Accept the Superuser prompt.
Use ROM Manager to create a Backup.
On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
Watch the backup go!
That's it! This is completely painless and safe! There is no need for Odin anymore to replace the recovery or flash updates!
If you appreciate my work, please buy the Premium version of ROM Manager!

Sweet!
Nandroid'd!

Ah yeah....smooth like butter baby!!! Great work once again. Remember to donate people!!!

big99gt said:
Ah yeah....smooth like butter baby!!! Great work once again. Remember to donate people!!!
Click to expand...
Click to collapse
For us Noobs, can we get more information on where and when to use this?
In reading everything I get some of it, but not all. This is my first hackable android phone, so I am still learning the lingo.
With other phones, I would just Flash a custom ROM or Flash Factory ROM back.
So how do ROM Manager and Clockwork recovery come into play?
Are there any tutorials - not that just give step by step (like above) but explain what is happening in each step or why?

alphadog00 said:
For us Noobs, can we get more information on where and when to use this?
In reading everything I get some of it, but not all. This is my first hackable android phone, so I am still learning the lingo.
With other phones, I would just Flash a custom ROM or Flash Factory ROM back.
So how do ROM Manager and Clockwork recovery come into play?
Are there any tutorials - not that just give step by step (like above) but explain what is happening in each step or why?
Click to expand...
Click to collapse
The long and short of it is that you can now flash ROMs and make backups, and restore, without your computer.
The recovery is the tool that lets you do the backups and installations. ROM Manager is a convenient Android front end to the recovery.

After these steps you won't really have to "hack" your phone lol. Root your phone and download Rom Manager from the Android market...then have it flash a recovery (the first selection at the top) choose your device when prompted. Now after that finishes select "reboot into recovery" and as the above post states you may need to select "reinstall packages" (I did). Once that goes through, you'll see your new custom recovery menu. DO A NANDROID BACKUP of your current Rom as soon as you can....then (as long as your current rom isn't messed up, if its stock your fine) from there on out you can play as much as you want with very little risk of bricking your phone. There are others who can explain it better but your stuck with me till they chime in lol. Its a very easy process and nearly foolproof.

Koush said:
That's it! This is completely painless and safe! There is no need for Odin anymore to replace the recovery or flash updates!
If you appreciate my work, please buy the Premium version of ROM Manager!
Click to expand...
Click to collapse
Awesome work! Premium version has been purchased by me. Thank you for the efforts.

Didn't work at first for me.
I installed Rom Manager (premium)
Installed CW recovery
Accepted SU
Tried to backup from within Rom Manager
I got a "Can't find update.zip" message.
When I rebooted and opened Rom Manager again, I got the "Error Occured" message, but it locked up on me and became unresponsive.
I uninstalled Rom Manager, rebooted, then reinstalled. I flashed CW recovery again, rebooted normally, opened rom manager again, and flashed CW recovery again.
After that I was able to use rom manager to reboot into recovery and backup.
Not sure if mine was just a fluke or what, but I figured I would share.

MSigler said:
Didn't work at first for me.
I installed Rom Manager (premium)
Installed CW recovery
Accepted SU
Tried to backup from within Rom Manager
I got a "Can't find update.zip" message.
When I rebooted and opened Rom Manager again, I got the "Error Occured" message, but it locked up on me and became unresponsive.
I uninstalled Rom Manager, rebooted, then reinstalled. I flashed CW recovery again, rebooted normally, opened rom manager again, and flashed CW recovery again.
After that I was able to use rom manager to reboot into recovery and backup.
Not sure if mine was just a fluke or what, but I figured I would share.
Click to expand...
Click to collapse
Titanium Backup did that to me also the first time I ran it....I've had quite a few freezes and slowdowns when opening a program for the first time and waiting for SU to kick in.

It should also be noted that when you chose to partition the sdcard via the recovery menu, it partitions the internal sdcard and not the external.
Maybe that can be made an option? I would like to do my nandroid backup to my external card so I have it for safe keeping.
Everything else working as expected, I enabled advanced options and downloaded the superuser package (from Extras) just to test things. Havent experienced any problems other than the sdcard wipe (which wasnt totally unexpected).
If something should happen to your phone (brick, unrecoverable error, etc), how can we reboot into this custom recovery to reflash the nandroid backup? Can we get into it via adb (adb reboot recovery)?

Yeah, having an external SD Nandroid would be a great option. Not just for safekeeping, but for easy transfer in case of hardware loss or replacement.

dweebs0r said:
It should also be noted that when you chose to partition the sdcard via the recovery menu, it partitions the internal sdcard and not the external.
Maybe that can be made an option? I would like to do my nandroid backup to my external card so I have it for safe keeping.
Everything else working as expected, I enabled advanced options and downloaded the superuser package (from Extras) just to test things. Havent experienced any problems other than the sdcard wipe (which wasnt totally unexpected).
If something should happen to your phone (brick, unrecoverable error, etc), how can we reboot into this custom recovery to reflash the nandroid backup? Can we get into it via adb (adb reboot recovery)?
Click to expand...
Click to collapse
I just did a reboot into recovery mode (the normal way, not with rom manager) and I had to click "reinstall packages" to get into the ClockworkMod recovery menu. So I'm not sure but I'm guessing (hoping) that its still available if we run into problems later.

Yep. It's pretty much how the Droid and N1 people are used to doing it anyway.
Clockwork is hella handy to manage and switch between working ROMs on the fly, as well as triggering recovery mode without keypress acrobatics, but having update.zip on the SD card to fall back on using the normal restore and the stock kernel is great in case of semi-bricking, and as this last week has shown us, the Galaxy phones are a bit prone to this.

THANK YOU!!! Been waiting for this since I got the phone, you are the man, I'll be adding to your Paypal account shortly!

Works like a charm. Thanks Koush!

Thank you. I am new to the scene, but looks like I chose the right hardware for hacking. The swift and easy way in which I have been able to advance my freedom on this gorgeous hardware makes me forget for a while that I am on AT&T, home of the fruit carrying zombie army.

Sweet! Can't wait to try this on my phone later tonight. Will deff be buying ROM Manager Pro

Thanks for this...I just bought the premium version...Since this is my first Android phone I have a question. I previously rooted my phone and uninstalled alll the AT&T bloatware, My question is about the backup I just made using this. If I restore the backup will it restore a rooted backup with out all the AT&T bloatware? Also when I ran the backup I go 2 messages at the end
No /sdcard/.andriod_secure found. Skipping backup of applications on external storage.. Is this normal?
No sd-ext found. Skipping backup of sd-ext. Is this normal?
Also I now have 2 ROM Manager icon in my application screens. 1 will open the program and the other tells me that the aplication is not installed on my phone. I tried to delete that icon but it won't go away, Any ideas? FIXED..I rebooted my phone and the extra icon went away...
Thanks for all help and these great apps...

jhernand1102 said:
Thanks for this...I just bought the premium version...Since this is my first Android phone I have a question. I previously rooted my phone and uninstalled alll the AT&T bloatware, My question is about the backup I just made using this. If I restore the backup will it restore a rooted backup with out all the AT&T bloatware? Also when I ran the backup I go 2 messages at the end
No /sdcard/.andriod_secure found. Skipping backup of applications on external storage.. Is this normal?
No sd-ext found. Skipping backup of sd-ext. Is this normal?
Thanks for all help and these great apps...
Click to expand...
Click to collapse
i got the same message, im assuming that you dont have an external sd card thats why it generated the message...

rabbivj said:
i got the same message, im assuming that you dont have an external sd card thats why it generated the message...
Click to expand...
Click to collapse
I do have one in my phone but there is nothing installed on it yet..maybe that's why..

[HELP] Lots of problems! Come in and help!

I killed my phone while trying to install a ROM, so I re-flashed a bunch of stuff and it's back. Some problems though - it has Superuser installed still. Even though I did a factory reset, Superuser is still there. When I try to re-root it, it goes through the whole things and gives me "error: device not found". I don't understand why it finds my device in the beginning of the process, but doesn't find it at the end.
1. How do I delete Superuser for good so I can start fresh, and re-root again?
2. What do I do now?

Could you list everything you've done in chronological order starting with the first thing you flashed and ending with the last thing you flashed?
Sent from my oc'd Voodoo Fascinate using XDA App

AlgorithmX said:
Could you list everything you've done in chronological order starting with the first thing you flashed and ending with the last thing you flashed?
Sent from my oc'd Voodoo Fascinate using XDA App
Click to expand...
Click to collapse
1. I was playing nice with the clean, magic roms, etc, everything was cool.
2. Then I tried to install Blue Breeze the same way and it froze the phone (later found out it was the wrong way to do it).
3. Then I followed the restore to stock thread (flashed system, kernel, etc), and brought it back to life, and Superuser was still installed. I tried to uninstall the root, and that doesn't work either.
So right now I can't uninstall Superuser, OR re-root it again because it just keeps giving me the error: device not found.

If you go into settings and check your internal phone memory...what is it saying you have?
Can you download apps from the market?
I got this same error when the voodoo bit me and gave me the 0.00 internal memory issue.
Try either flashing your stock+root CWM backup (you made one, right?) or the nandroid "stock" image in the forum through CWM.
(Wipe data/cache on reboot in stock recovery and then from the "privacy" menu of your stock settings do a "factory reset".)

PhoenixPath said:
If you go into settings and check your internal phone memory...what is it saying you have?
Can you download apps from the market?
I got this same error when the voodoo bit me and gave me the 0.00 internal memory issue.
Try either flashing your stock+root CWM backup (you made one, right?) or the nandroid "stock" image in the forum through CWM.
(Wipe data/cache on reboot in stock recovery and then from the "privacy" menu of your stock settings do a "factory reset".)
Click to expand...
Click to collapse
1. I have 1.50 GB free.
2. Yes, I can download apps from the market.
3. Where is the stock image located?
4. I did that factory reset like 3 times.

Have you attempted this?
http://forum.xda-developers.com/showthread.php?t=782204

Visit the first thread in this forum for info on stock recovery (including where to find the "stock" nandroid recovery image).
I take it you did not create a CWM recovery backup immediately after rooting your phone?

[Q] Help unrooting?

How would I go about unrooting this device? I bought it today, and shortly after that I got the 3.2.1 OTA update. Then I rooted by downgrading to 3.0.1. then I installed the apkinstaller and tried to download/install the Acer Recovery apk via the market. I keep getting FC's and android.process.acore errors. everytime I try to use the keyboard to search for the recovery installer, it happens. This is becoming really bothersome. I can't side load it via USB stick or anything. I'm not sure what else to do at this point. I successfully unrooted, but now when i try to download the system update, it gets nearly done and then stalls out. any ideas?

chattguy said:
How would I go about unrooting this device? I bought it today, and shortly after that I got the 3.2.1 OTA update. Then I rooted by downgrading to 3.0.1. then I installed the apkinstaller and tried to download/install the Acer Recovery apk via the market. I keep getting FC's and android.process.acore errors. everytime I try to use the keyboard to search for the recovery installer, it happens. This is becoming really bothersome. I can't side load it via USB stick or anything. I'm not sure what else to do at this point. I successfully unrooted, but now when i try to download the system update, it gets nearly done and then stalls out. any ideas?
Click to expand...
Click to collapse
You could just downgrade again back to 3.0.1 and NOT root it and then allow the OTA to roll you back to the future to 3.2.1.
TD

-also Make sure you Completly Wipe (4) + Format (3) (Data, cache, dalvik-cache, battery stats, flexrom)
-then install {Rom}.zip file.
* When you do get to a stable ROM you like, Wipe (3) (Cache, dalvik-cache, battery stats). Then Backup your Rom in CWM (save Folder to PC for backup)
Putting any Rom on top of another is too difficult to troubleshoot and is sloppy.
I'm not saying you did this, just advice!

ktmdave7 said:
-also Make sure you Completly Wipe (4) + Format (3) (Data, cache, dalvik-cache, battery stats, flexrom)
-then install {Rom}.zip file.
* When you do get to a stable ROM you like, Wipe (3) (Cache, dalvik-cache, battery stats). Then Backup your Rom in CWM (save Folder to PC for backup)
Putting any Rom on top of another is too difficult to troubleshoot and is sloppy.
I'm not saying you did this, just advice!
Click to expand...
Click to collapse
Right, I appreciate the advice. I'm trying to figure out how to get CWM on the tablet after it's rooted. It was entirely too unstable with all the "acore" errors and FC's to even use the keyboard at the android market. Moderately annoying. In other news, after I did a factory reset, that seemed to fix the stability issues, and then I was able to roll it back to the future, and onto 3.2.1. So after work this evening, I may take another crack at it.
EDIT: But for the money, this thing is entirely worth it.

check link below (more options)
http://forum.xda-developers.com/showthread.php?t=1420382
if you follow instructions to link, you will have HC v3.2.1
-it will not have "Superuser" in apps. so it's not considered Rooted. (it has TD's backdoor)
-it also will still have CWM Recovery. (so it's not entirely stock -stock recovery would have locked bootload)
it's like being half way rooted. it'll be easy to root or change roms (via CWM recovery)
when u turn it in, if they look in Apps menu for "superuser" they won't find and think it's stock.
but if they boot into recovery, they'l know it doesn't have stock recovery.
Rooting Facts:
Gingerbreak -can only Root up to v3.01
IconiaRoot -can only Root up to v3.1
for v3.2, 3.2.1 - TimmyDeans 3.2.1 v3 (backdoor method) or "Flash Custom Rooted ROM"

The update zips are on these forums, you shpuld be able to download and flash to a stable stock version that way, the same wqy you downgraded. From there, if you want root, i recommend downloading acer recovery and iconiaroot and installimg before flashing the downgrade. Thats what i did and i was on the unstable 3.0.1 rom for about 2 minutes before flashing a stable rom with root.

Do a search on here for acer recovery installer, the apk is on XDA... Loasd from pc, install and now you have a rooted A500 with CWM... Load a firmwar to our taste using CWM to get rid of bug ridden unstable 3.01...

SBKv2 and custom ROMs

So I just got a SBKv2,(C30). TF101 and wanted to try out Megatron. What's the safest way to do this without ending up with a brick?
Not new to flashing. Got several Android devices, Nook Color and Droidx on roms
Sent from my Transformer TF101 using Tapatalk 2

i think you may have 8.x.x.21 fw, if you havent updated asus fw yet. I have same device as well, and I used vipermod for rooting which is the first step in moving forward.
Only thing i really recommend is OTA rootkeeper once you root your device.

Already rooted (vipermod opt1) and got OTA rootkeeper installed.
Also installed recoveryinstaller lastnight, but then I chicken-out didn't go any further.
I guess I just need to be careful when flashing. Check MD5 matched on everything I downloaded to make sure I don't get stuck with a bad file.
Anymore tips guys before I start the flashing frenzy?

jdpdata said:
Already rooted (vipermod opt1) and got OTA rootkeeper installed.
Also installed recoveryinstaller lastnight, but then I chicken-out didn't go any further.
I guess I just need to be careful when flashing. Check MD5 matched on everything I downloaded to make sure I don't get stuck with a bad file.
Anymore tips guys before I start the flashing frenzy?
Click to expand...
Click to collapse
First is to go into CWM recovery and do a nandroid backup.
I suggest you stay with a recovery that read from external sd card.
If you used RecoveryInstaller it should have installed Roach's 3.2.0.1 which is good
or you can use Team Rouge recovery which read from both internal and external sd.
The newer recovery read from the internal storage only, which is ok just make sure you don't use a Superwipe script.
I highly recommend you set up ADB which come in handy also.
http://forum.xda-developers.com/showthread.php?t=1071584

baseballfanz said:
If you used RecoveryInstaller it should have installed Roach's 3.2.0.1 which is good
Click to expand...
Click to collapse
+1 to this, never had a problem with 3.2.0.1 and it reads ext-sd. I've just stuck with this version.

My TF101 is a C20 serial. This is what I did, I'll skip rooting the TF since you already did it (I did it the same way). Everything was with the TF attached to the dock:
-Installed gnufabio's Recovery Installer from this thread: http://forum.xda-developers.com/showthread.php?t=1346180
-Booted into recovery and installed rburrow's Rogue XM Recovery from this thread: http://forum.xda-developers.com/showthread.php?t=1446019
-Rebooted into recovery
-Followed "First time install instructions" on first post of ricardopvz's Megatron ROM (http://forum.xda-developers.com/showthread.php?t=1525148) which basically are:
-Go to mounts and storage, format data, cache and system
-Do a factory reset (wipe)
-Install Megatron ROM
-Install gapps
-Install custom kernel (I used guevor's test17c from it's own thread http://forum.xda-developers.com/showthread.php?t=1565519 but now I'm on test18e)
-Reboot into ROM
-Download and install Megatron Parts
-Have fun!
And I'm really having fun with it!

jdpdata said:
Already rooted (vipermod opt1) and got OTA rootkeeper installed.
Also installed recoveryinstaller lastnight, but then I chicken-out didn't go any further.
I guess I just need to be careful when flashing. Check MD5 matched on everything I downloaded to make sure I don't get stuck with a bad file.
Anymore tips guys before I start the flashing frenzy?
Click to expand...
Click to collapse
Lol, chicken. I never check MD5 but I don't advise following my lead
But yes, be careful and set up ADB before anything. It's best to set it up before you mess something up than after, like I did (hence why I said to not follow my lead ) but I was lucky and able to use nvflash to unbrick it (thank God b/c I wasn't sure which model I had)

[Q] Error while restoring /data!

I got this error when I restore a full backup in CWM.
I explain better:
I made a full nandroid backup & a full titanium backup on my old PB G100W, then I received a brand new tablet from Acer.. Now I would restore back all my apps & data, so I made downgrade from HC 3.2.1 to HC 3.0.1 unstable, root, recovery 1.3.4, updated recovery to 1.7.3 touch and flashed Tegraowners v169.
I restored apps by Titanium and everything was ok, but 2 apps (Opera and a game weren't work properly). Tried something to solve it, but nothing.
I decided to restore my last nandroid backup from cwm 1.7.3, but nothing, restoring boot ok, restoring system ok, restoring data works for a while, almost at the end stops and give me back "Error while restoring /data!".
Maybe my backup could be corrupted or maybe it's a internal storage issue.
So I made a real format (data/media enabled) -> /format system.
Retried, nothing, get back the same error.
Flashed back recovery 1.3.4 by thor and retried restoring, works for a while, then stops again.
I tried another nandroid backup, different from the first one (of 1 week before), same procedure, and stops and the same point.
So, I got two corrupted backup or I'm missing something?
EDIT:
Solved!
I tried so much methods that I bricked the tab, but solved with TimmyDean's method, unbricked, reflashed and then (I don't know how) all Titanium backup were working and no issues.
Maybe the solution on titanium back is reboot a few times.
SOLVED!

3 things possible.
1. You had corrupted data when you did the recovery.
2. Your recovery image is messed up.
3. Thor 1.7.3 is flakey. See number 2.
I'm betting on 3.
Just a hunch. Seems CWM 1.7.2+ has issues on some tablets. This is known in the XDA bootloader forums. Sorry you didn't hear about this, but I would advise ver 1.7 or one of the other options. A pity your recovery image is no good.
Rule of thumb. After making a recovery image, you should always restore it to make sure it is good. Not take it for granted that it works.

Moscow Desire said:
3 things possible.
1. You had corrupted data when you did the recovery.
2. Your recovery image is messed up.
3. Thor 1.7.3 is flakey. See number 2.
I'm betting on 3.
Just a hunch. Seems CWM 1.7.2+ has issues on some tablets. This is known in the XDA bootloader forums. Sorry you didn't hear about this, but I would advise ver 1.7 or one of the other options. A pity your recovery image is no good.
Rule of thumb. After making a recovery image, you should always restore it to make sure it is good. Not take it for granted that it works.
Click to expand...
Click to collapse
I got some freezes on 1.7.3, a few in flashing/wiping time.. Then, I restored 1.3.4 recovery, and it worked fine.
I had to update the old version to 1.7.3 for tegraowners v169 flashing, so I made it. On reboot, it wasn't work anymore.. In recovery mode the screen was blinking, no way to get out. In normal boot the tab got stuck on Acer logo, in recovery mode blinked.
Used the unbricking method with new recovery image (the same 1.7.3 touch) and all went fine.
Rebooted, flashed, restored by titanium and no issues.
Faith mistery!
Thanks for answering master Moscow
Sent from my Packard Bell [email protected]_rv3 using Tapatalk