Develop Bugs

Issues restoring backup

So got my G2 today, rooted, installed Hboot, started up the phone, logged into all my accounts, got stuff how I wanted. Made a backup via Clockwork.
Then I tried out CM7 Nightlies, decided its pretty good but I wanted to go back to my backup. Loaded into Clockwork hit recover, picked my backup. The phone then just sits on the HTC screen. Never going to the G2 screen or getting back into the OS. I can't get a logcat from it either to see if it is crashing. I can get back into recovery, and flash another rom, but why isn't my backup of my original image working? There are no errors when restoring, I've tried a few times.

crater said:
So got my G2 today, rooted, installed Hboot, started up the phone, logged into all my accounts, got stuff how I wanted. Made a backup via Clockwork.
Then I tried out CM7 Nightlies, decided its pretty good but I wanted to go back to my backup. Loaded into Clockwork hit recover, picked my backup. The phone then just sits on the HTC screen. Never going to the G2 screen or getting back into the OS. I can't get a logcat from it either to see if it is crashing. I can get back into recovery, and flash another rom, but why isn't my backup of my original image working? There are no errors when restoring, I've tried a few times.
Click to expand...
Click to collapse
If you are using CM7, does this mean you upgraded to one of the CWM3 recoveries? Not sure if this has changed, but backups made with the older CWM2 recoveries are not compatible with CWM3. You will need to reflash back to the older recovery before restoring your backup (pretty sure there are lots of warnings about this in the CWM3/CM7 threads, so you should probably check those out to see if this is no longer the case).

I used CWM3 to make the backup, i assumed that would work to restore it.
EDIT: Okay. so CWM3 can't handle ANY Froyo, regardless of if the backup was made with it. Misunderstood that part. Flashed to CWM32 and it worked. Thanks.

Unable to restore nandroids

Ok, simply put, I am not able to restore a nandroid properly. I tried 2 different ones and when I reboot the phone just after the completion from recovery, it hangs on the white HTC screen forever (waited 40-50 mins before I took the battery out, with no luck). The "older" nandroid was restored succesfully a couple of weeks ago, so that's not the problem.
Any ideas? Thanks.

S-off and custom hboot image?
If yes make sure the hboot is not to small.
Sent from my HTC Desire using XDA App

Nope, S-ON. Recovery is AmonRA if it even matters, and the nandroids are MIUI_Au roms.

Sorry for double-posting, but just wanted to say I finally managed to restore the nandroid.
If it happens to anyone else, what i did was flashing the same exact rom the nandroid had in it. After that, back to recovery, wipe all user data and dalvik cache, and restore the nandroid.
Maybe it's something related to the kernel and not the rom itself. Anyway it's fixed.

[Q] Backup Issues

So tonight I was trying to show off my phone to a friend that didn't understand the concept of rooting. I made a nandroid of my current rom, so I could flash a past nandroid. As I started flashing, it was able to flash the boot and the system, but it could not flash the data for some odd reason. I am using clockwork mod 2.5.0.7, and have been using it before, but have never ran into this problem. I even tried flashing the nandroid that I had made tonight, but the same problem occurred. Any ideas?
Ps. My roms were MIUI 1.8.5(nandroid tonight) and Synergy RC 1(past nandroid).

Cmorris8848 said:
So tonight I was trying to show off my phone to a friend that didn't understand the concept of rooting. I made a nandroid of my current rom, so I could flash a past nandroid. As I started flashing, it was able to flash the boot and the system, but it could not flash the data for some odd reason. I am using clockwork mod 2.5.0.7, and have been using it before, but have never ran into this problem. I even tried flashing the nandroid that I had made tonight, but the same problem occurred. Any ideas?
Ps. My roms were MIUI 1.8.5(nandroid tonight) and Synergy RC 1(past nandroid).
Click to expand...
Click to collapse
Was your battery level low?
from my EVO 4G

dougjamal said:
Was your battery level low?
from my EVO 4G
Click to expand...
Click to collapse
It was at 60%. All I've read is that 30% is the minimum you can flash stuff at so the phone won't die.

Did you have ample space on your sd card when the backup was made? Cuz if not that portion could have been corrupted and not flashing.

+1 for a corrupted nand. Was there any transfers of the nand between pc and phone? Sometimes they can get corrupted like that. Also I suggest using amon ra 2.3 for recovery.
Sent from my PC36100 using XDA App

I have plenty of space on my sdcard (1.74 GB), and I had not messed with it on my computer. After trying the synergy backup and it not working, I tried to restore the backup I had just made that night, and it came up with the same problem. And I switched to Amon a few months back, but it is not as convenient as Clockwork to make nand backups. I have been contemplating switching to Amon, but the convenience of Clockwork is overwhelming with rom manager.

Need Help. Important...very important

Alright, so I have clockwork 3.0.0.5 and I backed up my system before flashing a new Rom. Well I need a text message out of that back up. The system was working fine which is why I backed it up. I backed up using clockwork. Now I try to flash back to get a picture of this Text and the freaking back up wont load. it just hangs on the boot animation. Has been there for over an hour now. I don't care how I get it, but I need to get this text message. Anyone have any ideas?

Have you tried pulling the battery and wiping caches then trying to boot up?
You could wipe everything and try to restore again.
Sent from my PC36100 using Tapatalk

Yeah. I have done everything that I can think of.
Wipe date, wipe cache, wip dalvik, reset security. Then reload the back-up
nothing
wipe data, wipe cache, wipe dalvik. then reload nothing
Wipe cache, reload. Reboot nothing.
I was using the Shooter Rom with the red fang remxed theme. It was slow as hell but worked. Always booted. I backed it up, loaded another rom, and now I cannot get the shooter to reload.
I hear that you can pull these thigns with the SDK. I will try anything. I need to get it.

I know it's after the fact, but this is why most of us shun CWM and use Amon Ra

He's got a point.
Can you browse the SD card, get into the backup and find the appropriate files? IDK offhand *where* the text history would be in there, but I'm sure one of these gurus knows. I'd guess it would be a matter of finding that file, flashing to a working rom, then dumping the file over top.
Mind you...this is just an educated guess.

Well the only people I know locally who flash use CWM. thats why I chose it over Amon. Does it make a huge difference? My stock rom back-up which does work and has been moved to three safe locations, was done in CWM.
How would I move the files over? I tried using a thread I found earlier and "Droid Explorer" but it didn't seem to work to well and just cleared my texts. So I tried to copy some .IMG files around and totally hosed my working back-up. Not the one with the Texts, the one I was booting from.

Yo no se....good luck with that man =/

scothern99 said:
Well the only people I know locally who flash use CWM. thats why I chose it over Amon. Does it make a huge difference? My stock rom back-up which does work and has been moved to three safe locations, was done in CWM.
How would I move the files over? I tried using a thread I found earlier and "Droid Explorer" but it didn't seem to work to well and just cleared my texts. So I tried to copy some .IMG files around and totally hosed my working back-up. Not the one with the Texts, the one I was booting from.
Click to expand...
Click to collapse
Yea people use CWM because thats what comes with rooting but if you actually read a little through these threads and talk to anyone who has had there phone rooted over a year they will let you know Amon is the way to go.... Very few issues do you see in the forums for AmonRa - IMO
I would back up to a good workable rom then flash AmonRa and start into your new world...Unfortunately you can not recover a CWM backup in AmonRa

Since your backups are with clockwork, you would need to make a whole new set of backups using Amon Ra. However we can get you where you need to be with clockwork. First the issue with Clockwork is, you cannot wipe boot without a script. Wiping boot is manditory for restoring any backup, otherwise as you have seen the phone won't boot. So download the attached file, place it on the root of your SDCARD, then boot to recovery, flash the file like you would flash a new ROM. Then without rebooting the phone restore your backup. This should get you back up and going.

Thank you!
I'm trying it right now. After I finish rebuilding and backing up this system.

Alright so as I tried to run that Superwipe.zip, I get an error tell me that Amend scripting was deprecated by google in android 1.5 I have to switch to edify scripting. Whats that mean?

scothern99 said:
Alright so as I tried to run that Superwipe.zip, I get an error tell me that Amend scripting was deprecated by google in android 1.5 I have to switch to edify scripting. Whats that mean?
Click to expand...
Click to collapse
It means get rid of clockwork mod because its strait up awful and install amon-ra
Sent from my PC36100 using XDA App

Like I said earlier.....

But I need clockwork to restore this back up as it was made in clockwork.

scothern99 said:
But I need clockwork to restore this back up as it was made in clockwork.
Click to expand...
Click to collapse
Look for calkulins format all. It's not as indepth as superwipe but it should work with the latest version of cwm.
Sent from my PC36100 using Tapatalk

Khilbron said:
Look for calkulins format all. It's not as indepth as superwipe but it should work with the latest version of cwm.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Calkulin's is also amend-scripted, I thought VR was edify though. I know that there's an edify wipe script, but not sure what it is.
Sent from my PC36100 using Tapatalk

What rom is the backup of. Try to wipe everything, restore the backup, wipe cache and dalvic cache, then flash a compatible kernel. See if it boots then.
Sent from my Nexus S 4G using xda premium

Its Kinged Shooter ROM. Its stock Kernal so....

twrp consistently crashes while restoring backups

I was playing around with some ROMs yesterday, since i was not happy with CM11 anymore. after installing a couple of different ROMs i decided to stick with slimkat. so i made a nandriod of slimkat and tried to go back to CM11 to get my apps all figured out for the switch. This is where the trouble started. when trying to restore CM11 I would get to "writing data" and at some point (always a different percentage) the phone would crash and reboot and get stuck in a boot loop. it would then do the same thing when trying to restore the slim ROM, always crashing before the restore finished. I always wiped data/sys/cache, i tried to fix permissions, install different version of twrp (2.6.x.x vs 2.8.6.0). I've since restored the phone back to factory and installed twrp again. I'm at my wits end as to what the problem could be. one thing that's odd is I get a splash screen before the twrp splash which still shows the little cyanogenmod guy at the bottom, even though there should be no remnants of CM on my s3 at this point.
I have slimkat installed at the moment and it's running fine. i'd still like to boot back into my old CM11. if i can't it's no tragic loss.
I will be travelling and i wont have access to odin for a little while, so i'm less inclined to go breaking things till i get back home. I thought maybe someone here has run into this or knows how to fix this.
Thanks for the help
Dom

wascalwabbit said:
I was playing around with some ROMs yesterday, since i was not happy with CM11 anymore. after installing a couple of different ROMs i decided to stick with slimkat. so i made a nandriod of slimkat and tried to go back to CM11 to get my apps all figured out for the switch. This is where the trouble started. when trying to restore CM11 I would get to "writing data" and at some point (always a different percentage) the phone would crash and reboot and get stuck in a boot loop. it would then do the same thing when trying to restore the slim ROM, always crashing before the restore finished. I always wiped data/sys/cache, i tried to fix permissions, install different version of twrp (2.6.x.x vs 2.8.6.0). I've since restored the phone back to factory and installed twrp again. I'm at my wits end as to what the problem could be. one thing that's odd is I get a splash screen before the twrp splash which still shows the little cyanogenmod guy at the bottom, even though there should be no remnants of CM on my s3 at this point.
I have slimkat installed at the moment and it's running fine. i'd still like to boot back into my old CM11. if i can't it's no tragic loss.
Click to expand...
Click to collapse
Was the original CM11 nandroid made with the same recovery make and version which would not install it? I am pretty sure TWRP will not install a CWM or Philz nandroid. I don't know if there are issues installing a 2.6.x.x TWRP nandroid with the 2.8.x.x version of TWRP.

Thanks for you're reply. The backup was made with twrp, I'm not sure which version it was, so I downgraded to see if it would help, then I installed the latest version again. There was no difference in the results no matter the twpr version. Twrp nandroids are in fact incompatible with CWM, not sure about philz

wascalwabbit said:
Thanks for you're reply. The backup was made with twrp, I'm not sure which version it was, so I downgraded to see if it would help, then I installed the latest version again. There was no difference in the results no matter the twpr version. Twrp nandroids are in fact incompatible with CWM, not sure about philz
Click to expand...
Click to collapse
Since Philz was originally based on CWM I wouldn't expect it to work with TWRP nandroids either.
Have you tried installing only specific partitions of the nandroid, such as the /data/data partition where the user installed apps are stored. As opposed to restoring the entire nandroid. I have heard mention of this, but in your case it may be problematic since your nandroid is of CM11 and the ROM you are running is SlimKat.

Oh that's a great idea, thanks, that may work. I i'll just flash CM and then restore data. I'm literally heading into the jungle right now, so in not sure if I'll be able to try this out for few days, but I will as soon as I get a chance.
Thanks for tour help