• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Nandroids - Always fail

Aggie12

Aggie12

Android Expert
So I've been having problems lately with nandroids. It started when still on 2.2.1. I was on Fission 2.6.1 and wanted to restore my stock Froyo for one reason or another. I originally created the backup using the DroidX bootstrapper app and renamed it using astro (no spaces). When I went to restore the backup it looked as if it was successful, but when I went to reboot it was stuck at the M logo. I had to SBF to remedy my situation and have been hesitant to do it again. Well that brings me to today. I was on ZombieStomp and wanted to go back to the nandroid that I made of GB stock I made a week or so ago using this time the Droid 2 Bootstrapper app as directed by everyone. I didn't choose to rename this one just to try and see if that was the problem. Well it 'restored' in less than 2 minutes so I knew something was up. And sure enough rebooted and stuck on M logo. I was able to boot into factory recovery and wipe data/cache and still a no-go.

Am I doing something wrong??? Please advise.
 
Aggie12 said:
So I've been having problems lately with nandroids. It started when still on 2.2.1. I was on Fission 2.6.1 and wanted to restore my stock Froyo for one reason or another. I originally created the backup using the DroidX bootstrapper app and renamed it using astro (no spaces). When I went to restore the backup it looked as if it was successful, but when I went to reboot it was stuck at the M logo. I had to SBF to remedy my situation and have been hesitant to do it again. Well that brings me to today. I was on ZombieStomp and wanted to go back to the nandroid that I made of GB stock I made a week or so ago using this time the Droid 2 Bootstrapper app as directed by everyone. I didn't choose to rename this one just to try and see if that was the problem. Well it 'restored' in less than 2 minutes so I knew something was up. And sure enough rebooted and stuck on M logo. I was able to boot into factory recovery and wipe data/cache and still a no-go.

Am I doing something wrong??? Please advise.
Click to expand...


did you wipe data first??
 
The only time I've ever had a problem was when I accidentally formatted my SD card and used a program to restore my lost data. None of my nandroid backups would restore correctly, but they were aborted and I didn't have to SBF.

When you're restoring your nandroid and CWM is running through its script, does it print any errors when it restores? I was getting MD5 sum mismatch errors, but it sounds like yours are restoring all the way...

Try updating Rom Manager (or going back to a version that worked).
 
Metfanant said:
did you wipe data first??
Click to expand...

No data wipe prior to it. Only after. But it seems as if my system isn't loading properly since it won't make it past the M logo. If it were data giving me trouble and not system then it should get past the logo and get me stuck in a Bootloop, right?

WalmartSecurity said:
The only time I've ever had a problem was when I accidentally formatted my SD card and used a program to restore my lost data. None of my nandroid backups would restore correctly, but they were aborted and I didn't have to SBF.

When you're restoring your nandroid and CWM is running through its script, does it print any errors when it restores? I was getting MD5 sum mismatch errors, but it sounds like yours are restoring all the way...

Try updating Rom Manager (or going back to a version that worked).
Click to expand...

Not using Rom Manager. And CWM is showing that everything is working properly.
 
I just posted something similar (a mod may wish to move my topic here.) I can restore system files just fine, but never data. Maybe there's some issue with D2 bootstrap?
 
If you know how to use adb and have access to a PC at the time you are doing the Nandroid restore (i.e., while you are still in custom recovery), I believe you should be able to examine (and/or pull over to you PC) the /cache/recovery/log file to see the full details about what the nandroid-mobile.sh script is/was doing at the time of the issue / errors.

Oftentimes, there's simply not enough room to display the full details on the phone about the error that has occured--hence the terse and cryptic message on your phone.

Hope that helps.
 
I don't get any error codes in CW, it seems to complete backups without any problems, and restores fine until it hits a particular file, then just freezes.
 
cybergreen said:
I don't get any error codes in CW, it seems to complete backups without any problems, and restores fine until it hits a particular file, then just freezes.
Click to expand...

Yeah, I was just suggesting that the details of what is actually going on (and possibly not being reported) could be gleaned from the log file that is created during the Nandroid restore (or backup, as the case may be).

Right after the restore (or backup) operation, while you are still in recovery, you should be able to "adb shell" to your phone and "cat /cache/recovery/log" (or "adb pull /cache/recovery/log my-recovery-log.txt" for later analysis).

I'm just speculating that its possible that there are relevant things not being reported that might shed some light on what might be going on.

Cheers!

edit: sorry, I didn't focus enough on the freeze issue...you could "monitor" the backup or restore while its going on via adb by watching the log file (it may be that adb will still be active even while things are frozen).
 
Can you go more in depth about getting this error log with ADB. I can do a lot of normal stuff with ADB but am unfamiliar with this. And I'm not going to do this atm. I've been dealing with this all day. It doesn't help that when I took my macbook pro in for repair at apple they corrupted my single-boot linux distro. to which I had to start all over. :( another one against apple. I was showing the Geniuses my DX and they thought it was pretty cool but then said it doesn't have as good of a display. . . I was like stfu.
 
Aggie12 said:
Can you go more in depth about getting this error log with ADB. I can do a lot of normal stuff with ADB but am unfamiliar with this. And I'm not going to do this atm. I've been dealing with this all day. It doesn't help that when I took my macbook pro in for repair at apple they corrupted my single-boot linux distro. to which I had to start all over. :( another one against apple. I was showing the Geniuses my DX and they thought it was pretty cool but then said it doesn't have as good of a display. . . I was like stfu.
Click to expand...

Sure, Aggie, no problem.

When a custom recovery is running, be it Amon_RA or ClockworkMod, there should be an adb daemon running too. So, when custom recovery is running and doing its thing, it will log its progress and messages to /cache/recovery/log, which obviously contains more details than what can be shown on the phone.

From your PC (or Mac, as the case may be), you can retrieve the log file with:

adb pull /cache/recovery/log

- or (to give it a more meaningful name) -

adb pull /cache/recovery/log cwm-recovery-log.txt

You should be able to do this while recovery is running, even while a Nandroid backup or restore is taking place.

Another way is to invoke a shell and poke around that way:

c:\ adb shell
# cd /cache/recovery
# cat log
# exit

I should let you know that I have not done this on my X (since I have not install ClockworkMod recovery), but have done this on my Eris under Amon_RA, which, I is based-on an early version of ClockworkMod or early work by Koush. I have recompiled Amon_RA's recovery for the Eris and built an alternate version for those whose trackballs no longer work. I've looked at the source code for ClockworkMod and they are very similar to each other in many respects.

Hope this helps. Good luck!
 
Ok yeah that does help. I was under the impression that I would have to start an ADB shell and watch it as it goes then pipe the output to a text file but all that is automated. niice.
 
Aggie12 said:
So I've been having problems lately with nandroids. It started when still on 2.2.1. I was on Fission 2.6.1 and wanted to restore my stock Froyo for one reason or another. I originally created the backup using the DroidX bootstrapper app and renamed it using astro (no spaces). When I went to restore the backup it looked as if it was successful, but when I went to reboot it was stuck at the M logo. I had to SBF to remedy my situation and have been hesitant to do it again. Well that brings me to today. I was on ZombieStomp and wanted to go back to the nandroid that I made of GB stock I made a week or so ago using this time the Droid 2 Bootstrapper app as directed by everyone. I didn't choose to rename this one just to try and see if that was the problem. Well it 'restored' in less than 2 minutes so I knew something was up. And sure enough rebooted and stuck on M logo. I was able to boot into factory recovery and wipe data/cache and still a no-go.

Am I doing something wrong??? Please advise.
Click to expand...


My Question is how old is that Stock Froyo? if you've upgraded the bootloader, for example, after that nandroids was made you wouldn't be able to restore with it. So it really depends on where you were and where this backup is taking you. And since you get no errors I feel that may be what is happening. ie restoring a nandroid that is not compatible with your phones current firmware.

Can you restore other more recent backups?
 
Piiman said:
My Question is how old is that Stock Froyo? if you've upgraded the bootloader, for example, after that nandroids was made you wouldn't be able to restore with it. So it really depends on where you were and where this backup is taking you. And since you get no errors I feel that may be what is happening. ie restoring a nandroid that is not compatible with your phones current firmware.

Can you restore other more recent backups?
Click to expand...

Well. The bootloader has been the same at 30.04 since the froyo update. So that wouldn't be the case. But I'm trying to think about what you're saying with the incompatible firmware nandroids. That would make sense but I can't remember what version of stock GB I had tried to flash back to. I want to say it was the same as what zombiestomped used but I honestly don't know. And no I can't restore recent backups. I made a GB backup and then less than a week later I attempted the restore but it was a no go.
 
Aggie12 said:
Well. The bootloader has been the same at 30.04 since the froyo update. So that wouldn't be the case. But I'm trying to think about what you're saying with the incompatible firmware nandroids. That would make sense but I can't remember what version of stock GB I had tried to flash back to. I want to say it was the same as what zombiestomped used but I honestly don't know. And no I can't restore recent backups. I made a GB backup and then less than a week later I attempted the restore but it was a no go.
Click to expand...

A week? You probably missed 2-3 leak releases during that time! LOL:D

I'm curious to know if you got this resolved. I've seen a few others post on the forums with a similar problem and I'm at a loss for a solution besides checking the obvious (i.e. trying to restore froyo on GB, etc).
 
alprazolam said:
A week? You probably missed 2-3 leak releases during that time! LOL:D

I'm curious to know if you got this resolved. I've seen a few others post on the forums with a similar problem and I'm at a loss for a solution besides checking the obvious (i.e. trying to restore froyo on GB, etc).
Click to expand...

No I haven't. I quiver at the thought of restoring a backup. But when I do I will check the log to see if anything went awry.
 
You must log in or register to reply here.
Back
Top Bottom