So I followed the guide to root with s=off and it seemed to work fine and I installed clockworkmod v3.0.0.5 through ROM Manager and had made 2 nandroid backups and everything seemed to be working great.
Then I tried to install CM7 RC1 through ROM Manager, thinking if anything went wrong I'd be able to restore the nandroid backups.
Something went wrong and I ended up stuck with the CM7 skateboarder animation infinitely repeating. So after pulling the battery I was able to boot into recovery. It looked like the stock recovery, but after selecting factory reset it went into Clockworkmod. From there I restored my backup, and everything seemed to work fine.
But when I reboot it just gets stuck forever at the MyTouch4G logo (the first one that comes up immediately on power up, not the second, round logo.
I've tried to restore both backups but always get stuck at the same screen.
Right now I need to get the phone working as fast as possible, hopefully to one of my backups (but if I can get it working I've also got MyBackup Pro and Titanium backups of my data and apps).
Can someone tell me what's the best way to get this working again and hopefully if it's possible to successfully restore my nandroid backup?
Thanks!!
Current:
Rom Manger (v3.0.1.0)
Recovery (v3.0.0.5)
When you go in Recovery from bootloader what color is the text green (2.x) or orange (3.x)? Keep in mind if your using 3.0.0.5 which has Recovery 2.5.1.2 then you can't flash CM7 as you need to use 2.5.1.4(Recovery) or 3.0.0.5(Recovery).
If you meet the basic requirement as you still have the rom on your SDCard. I want you to go in Recovery via bootloader. Then go in format and wipe /system, /data. Then go back in advance wipe dalvik and from main screen wipe cache, then do full factory wipe it will remount all. Once this is done select Install zip files> Choose zip files> Find and run the rom> select yes.
When you load for the first time give it some time as it will take few min but if it takes more than 5min than ya its in bootloop. If you get to the part here then it should be working but if you get stuck in mytouch 4g logo then it won't load. Now if you have green(2.x) text then what you need to do is install the Recovery 3.0.0.6.zip though Recovery as you won't be able to access Rom Manager and then try to flash CM7RC1. Let me know if you have any problem or its hard to understand. I know people always get Rom Manager and Recovery version number confused and the whole problem get started.
It says "ClockworkMod Recovery v3.0.0.5" at the top and bottom and has orange text on a black background (highlight line is white text on orange background).
This morning I managed to get it to boot by flashing PD15IMG.zip from HBOOT (took me a while to figure out I have to keep holding both down and power to get to HBOOT, just holding down and releasing power took me to ClockworkMod which wouldn't install the file).
Then I set up my account and downloaded MyBackup Pro which I used to restore visionary+ and rom manager to re-root and re-install clockworkmod then I rebooted into recovery and tried to restore my nandroid backup.
Same problem, stuck in the boot logo. So seems like these nandroid backups are useless.
Is there any way I can recover the backups? At this point I don't have much time to play with CM7 so I'd rather just get my phone back to where it was and play with CM7 a bit later when I have more time. If necessary I'll just go back to PD15IMG and manually restore using MyBackup Pro, but that backup isn't quite as fresh and it's a pain to restore the widgets, etc.
I'll try doing the wipes you suggested and see if that will bring back my backup...
Thanks!
To be clear:
ClockworkMod Recovery 3.0.0.5 -- the orange text version -- CANNOT be used with Stock ROMs, or any other Froyo-based ROM. Not backup, not restore, and not install. It is only for Gingerbread-based ROMs, like CM7.
Froyo and Gingerbread versions of Android use different filesystem structures. CWMR 3.0.0.5 is for EXT4 filesystems, which the Froyo kernel cannot mount.
At boot up, the Froyo kernel tries to mount /system, and fails, because /system is in EXT4 format that it doesn't understand. So the Froyo kernel crashes, reboots .... and fails again. And again.
That explains it. Thanks.
So I installed ClockWorkMod 3.0.0.6 and used that to restore my last nandroid backup (even though it was made in 3.0.0.5) and that seems to have worked!
CM7 does look quite nice. I look forward to playing with it when I have more time.
Thanks for your help!
Related
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..
I had an earlier version of cyanogenmod installed, I went into rom manager and pressed update (or something like that). It did the whole installation thing but now it's just hanging at the cyanogenmod splash screen.
What do?
silverback88 said:
I had an earlier version of cyanogenmod installed, I went into rom manager and pressed update (or something like that). It did the whole installation thing but now it's just hanging at the cyanogenmod splash screen.
What do?
Click to expand...
Click to collapse
Have you tried to boot into recovery ? (turning it on by pressing the power button and the - volume button)
Did you backup? Always, always backup.
If not try downloading the ROM and flashing that, don't wipe just yet, if that fails you will probably need to wipe and flash again.
ok so i did a recovery of the backup i did just before trying to install cyanogen 7
FFUUUUU.... now everything is pretty much lost! even the old cyanogen is gone. What can I do?!
Was your old backup from a pre 2.3 ROM?
^^ how can i tell?
sorry for being a noob
What was the ROM you backed up before flashing CM7?
the backup i did just before trying to install cyanogen 7
Click to expand...
Click to collapse
it was cyanogenmod 6.1.3
Ok, your problem now is that the file system changed from 2.2 (Froyo) to 2.3 (Gingerbread) and you will need to flash a new version of ClockworkMod Recovery to restore that backup.
Do you have ENG S-OFF? You will be able to flash it via fastboot, if not you will have to start again from CM7 and downgrade ClockworkMod Recovery from there, then restore your backup.
I flashed the latest ClockworkMod Recovery (3.0.0.6) - I think before I tried to install CM7.
Restoring the backup means almost everything is gone, apps, settings, etc (but not everything). Did I **** it up? Will I have to redo everything?
If I have to do that anyway I might as well use CM7, but installing that means the splash screen hangs (I had the same problem with CM6, I dont remember how I fixed it)
Your right, to flash CM7 you needed CWM 3.x.x.x
Restoring that backup 6.1.3 will take you back to pre-CM7 so yes everything will be gone.
Have you tried just flashing CM7 again?
ok, trying to install cm7 again...
Don't wipe just yet, if it still hangs after flashing again you will then have to wipe.
****, it's hanging at the CM7 splash screen again
Ok, you will need to perform a wipe.
In CWM you have "mounts & storage"
Format boot & system, then flash CM7 again, (btw which CM7 ROM are you flashing?)
I did that (through the recovery or w/e) and then it was hanging at the HTC logo....
I had to restore the backup once again and am back where I was before
What can I do?
btw it's CM 7.0.0-RC2
Ok sounds like a full wipe is needed.
Again in CWM "mounts and storage" format everything except scdard, then back out and go into "advanced" and wipe dalvik cache.
Flash CM7 again, it should work now.
can i flash CM7 through the recovery console? because if i wipe everything then obviously i cant boot back into it?
Don't worry you can't wipe recovery from within recovery, so after a full wipe it will still be available.
before I do that, how exactly do i install CM 7 from recovery console? I think it was downloaded to my SD card but I dont see a straight forward option in the recovery console
I don't know if this could be really repetetive, since it's only happened twice, but it's 2 times in a week and a half, with a RUU and reroot, etc in between.
Reboot the phone and it white screens/freezes for no reason.
Clearing caches or doing a full wipe doesn't fix that issue.
Go to recovery and try to do a nandroid restore and get an "oops... something went wrong error"
Also notice my latest nandroid doesn't show up in the restore list.
I have to pull the sdcard, put it in my spare phone, connect to my pc and move Amon Ra back to the SD Card/Root, then put it back in the Evo, and reboot to Hboot so I can reflash recovery, and then everything seems to work again.
Including my latest nandroid showing the restore list again.
Anyhone encounter this, or know why it's happening?
BTW, using v2.3
Flash it through Rom manager, flash clockwork and after you flash clockwork, then you flash alternate recover aka amon ra
HipKat said:
I don't know if this could be really repetetive, since it's only happened twice, but it's 2 times in a week and a half, with a RUU and reroot, etc in between.
Reboot the phone and it white screens/freezes for no reason.
Clearing caches or doing a full wipe doesn't fix that issue.
Go to recovery and try to do a nandroid restore and get an "oops... something went wrong error"
Also notice my latest nandroid doesn't show up in the restore list.
I have to pull the sdcard, put it in my spare phone, connect to my pc and move Amon Ra back to the SD Card/Root, then put it back in the Evo, and reboot to Hboot so I can reflash recovery, and then everything seems to work again.
Including my latest nandroid showing the restore list again.
Anyhone encounter this, or know why it's happening?
BTW, using v2.3
Click to expand...
Click to collapse
im pretty sure the ruu deletes the recovery because stock does not have a recovery.
drtdiver83 said:
im pretty sure the ruu deletes the recovery because stock does not have a recovery.
Click to expand...
Click to collapse
Well, of course it does. That's not the issue.
Obviously, I had to reflash recovery after running the RUU.
The point is, it happened a few days before and a few days after I ran RUU.
I'm wondering if it's a recovery issue or an SD Card issue.
Treated, I root with UnrEVOked, which flashes clockwork, then I flash A.R. after that, but if it happens again, and I can boot up, I'll try flashing CW from Rom Manager and then A.R. afterwards.
Hi there. Thought I'd finally get around to rooting my Glacier, making progress but hit a roadblock.
ROM Manager app is stuck on "Error while downloading from server.", so I flashed clockwork recovery 3.0.2.4 with fastboot shell, ROM Manager still thinks recovery isn't installed and gives me the same download error when I try to manual override.
In recovery, attempting to start a backup gives me the error in the title, that is, "Error while backing up boot image!" and halts.
I could probably continue on to flashing cyanogenmod 7 and gapps, but I'm not comfortable doing that without a backup handy.
Android ver. 2.21, eng SPL (85.2007), 3.0.2.4 ClockworkMod recovery.
Can anyone help?
If it were me, I would download a fresh copy of CWM from here and flash it via fastboot. I bet then you'll be able to successfully make a Nandroid. If not, try formatting your SD card.
Downloaded that and re-flashed to no avail. Backed up SD card, formatted it, and for some reason it started working then.
Ah well, at least I have a backup. Thanks!
Had an odd error with the md5 checksums changing, too.. pushed them with adb, used md5sum, they were correct. Rebooted into recovery and they had changed again. Had to push and verify from recovery in order to install.
It ended up working though, so no complaints.
The easiest workaround I found to this problem was to boot into recovery mode using Quick Boot and follow these steps in the cwm boot screen: apply update from sdcard, install /sdcard/update.zip, reboot into recovery, backup and restore, and BACKUP. Worked for me and I didn't have to reformat my sd card, deleting everything on it.
Hi,
I would like to remind you that, CWM v3.x above are no longer support amend scripting which is used in Froyo ROM. Instead it used edify scripting which is used in Gingerbread ROM.
When you are on Froyo and try to use the latest CWM, it will not work, and you will encounter a problem just like you said.
My self, i use the CWM v.2.5.x, on my fascinate, and it can make backup successfully, although i never try the restore function yet.
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