Root Help please...

[WormDoes]

Hi Everyone,

I have done quite a few mods to my Eris the past couple days and made backups in between each. Long story short I just flashed a zip and got force closes, no big deal, so I pulled the battery and booted into recovery to flash my nand. So I chose the back up I wanted to restore, clicked the trackball to confirm and got this message Error : Run 'nandroid-mobile.sh restore' via adb!

I made 3 backups just last night in between my mods...

The one I tried to restore xtrSENSE4.2-20100928-CircleBatt-VanillaLock&Clock was the last one I made before the zip I just flashed today.

My question is, does the Nand HAVE to be renamed exactly the same as it was written? What I mean is am I putting too many words in my renaming of the backup? I rarely make custom mods or flash ROMs repeatidly (have flashed 2 ROM's ever) because I'm deathy afraid of "bricking" my phone or not having a nand work. Needless to say the message I got when I tried to restore my nand made my heart drop to my balls.

Also, I'm trying to restore my nand I made about 2 weeks ago and it's been "restoring" for close to 10 minutes now. Is this normal? Looking for some help from some of the vets on this issue...paging ScaryAlien, Frisco, Dooglad

Thanks in advance for the help, fellas

 

[Podivin]

I'd suggest you take the ampersand '&' out of the file name. I'm wondering if that is a 'special' enough of a character that it's giving you grief.

 

[WormDoes]

I was thinking the same thing. I had originally put a / in place of the & and it wouldn't even let me save the name. I finally got my nand restored I made about 2 weeks ago. The screen was filled with . . . . . . . literally FILLED! I've never had a nand take so long to restore.

Do you think if once my phone gets booted if I change the name of the nands that wouldn't restore and remove the & that I'll still have an issue restoring them?

 

[Podivin]

If the & is really the problem, then changing the name will fix that. The file itself is not corrupt, just the backup program can't deal with the file name.

 

[scary alien]

I'd suggest you take the ampersand '&' out of the file name. I'm wondering if that is a 'special' enough of a character that it's giving you grief.

I was thinking the same thing. I had originally put a / in place of the & and it wouldn't even let me save the name. I finally got my nand restored I made about 2 weeks ago. The screen was filled with . . . . . . . literally FILLED! I've never had a nand take so long to restore.

Do you think if once my phone gets booted if I change the name of the nands that wouldn't restore and remove the & that I'll still have an issue restoring them?

I think Hoto's on to something... Don't quote me on this , but the nandroid-mobile.sh script is invoked by Amon_RA's custom recovery and if its anything like other Unix systems, the ampersand character tells the shell to launch the process in the background. So....in my mind, this seems to match what you are seeing...a Nandroid restore that won't finish because Amon_RA's recovery is not seeing the nandroid-mobile.sh script finish--because its still running in the background and not the foreground.

I could certainly be wrong, but I could test this tonight if you want by adb'ing to my Eris while its in recovery and watching it. But, I'll bet if you, like Hoto said, remove the ampersand, your restore will complete just fine.

Amon_RA and the nandroid-mobile.sh script don't care what the recovery directory is named, insofar as it does not contain spaces, and apparently, ampersands.

Let us know if this fixes you up so we can spread the word to others about the ampersand char.

Thanks!

 

[WormDoes]

My phone finally reboot and I stopped sweating, lol. I'm going to try and change the name in the file to something simple and see what happens. Thanks for the quick response, sir, much appreciated

 

[WormDoes]

Scary!! Whats good my man! Thank you as well for the quick response. I'll repost back after removing the & and share what happened

 

[WormDoes]

It seems the & was the culprit.

I renamed my file which was xtrSENSE4.2-20100929-CircleBatt-VanillaLock&Clock
to xtrSENSE4.2-20100929-CircleBatt-VanillaMM and It restored and just booted up without any issues

That was a lot of stress for something so simple. I'm glad it wasn't something serious. Although if it was, I still have a NE2 upgrade stashed in my back pocket. Is there anyway to update and add the & issue to any thread giving instructions to nandroid backups so no one has to go through what I did?

Also, SA, real quick while I have you here, are you familiar with MetaMorph by any chance? I use MM to install a new battery but want to change it to something different, hense the flash that started this thread. Can I just delete the file itself or becuase it deals with framework.res.apk will that create a slew of issues? The battery is cool but the percent goes down by the 20's instead of by single digits so it's kind of frustrating.

 

[scary alien]

It seems the & was the culprit.

I renamed my file which was xtrSENSE4.2-20100929-CircleBatt-VanillaLock&Clock
to xtrSENSE4.2-20100929-CircleBatt-VanillaMM and It restored and just booted up without any issues

That was a lot of stress for something so simple. I'm glad it wasn't something serious. Although if it was, I still have a NE2 upgrade stashed in my back pocket. Is there anyway to update and add the & issue to any thread giving instructions to nandroid backups so no one has to go through what I did?

Also, SA, real quick while I have you here, are you familiar with MetaMorph by any chance? I use MM to install a new battery but want to change it to something different, hense the flash that started this thread. Can I just delete the file itself or becuase it deals with framework.res.apk will that create a slew of issues? The battery is cool but the percent goes down by the 20's instead of by single digits so it's kind of frustrating.

Glad that fixed you up! Props to mhotovec for zeroing-in on this...if I get the urge this weekend, I might test this on my phone and watch for similar results.

Sorry man, don't know anything about MetaMorph....seems like I remember Andrizoid being the oracle re. that...and I'm sure there are others...

Good luck!

 

[WormDoes]

OK, thanks! And, yes, BIG thanks to mhotovec for coming to the rescue and figuring out what the issue was. Thank you, sir

 

[Podivin]

Yeah, score one for the second string guys!
Happy to help WormDoes, glad it worked out for you.

 

[tproctor]

Ok, I'm trying to do a Nand restore and get the same error message as the OP. I've renamed the backup and taken every symbol out, but it still gives me that error. Anyone have any ideas?

 

[es0tericcha0s]

Ok, I'm trying to do a Nand restore and get the same error message as the OP. I've renamed the backup and taken every symbol out, but it still gives me that error. Anyone have any ideas?

Make sure your phone has enough juice. It's a failsafe built in case you are trying to flash something and your phone dies possibly resulting in a brick. Just plug it in somewhere and try it again. Will probably be fine if the name situation is straight.

 

[scary alien]

Ok, I'm trying to do a Nand restore and get the same error message as the OP. I've renamed the backup and taken every symbol out, but it still gives me that error. Anyone have any ideas?

Make sure your phone has enough juice. It's a failsafe built in case you are trying to flash something and your phone dies possibly resulting in a brick. Just plug it in somewhere and try it again. Will probably be fine if the name situation is straight.

The nandroid-mobile.sh script / Amon_RA's custom recovery should report if the battery is too low (30% or less), but make sure its well-charged nonetheless.

Also, double-check the directory name (don't post the HTxxxxxxx folder name here, but what was the final directory name?)--the OP's problem was an ampersand in his filename [no spaces allowed either!]

Are there all four requisite files in the Nandroid backup's directory (i.e., boot.img, system.img, data.img, and nandroid.md5)?

Also, if your ROM supports the md5sum utility, you can try to verify that you have a good Nandroid backup by doing this from either a terminal (Android Terminal Emulator) or adb shell session:

$ su
# cd /sdcard/nandroid/HTxxxxx/BDS-ccyymmdd-hhmm (or your directory name)
# md5sum -c nandroid.md5

it should report this:

boot.img: OK
data.img: OK
system.img: OK

Reference these threads for more information:

http://androidforums.com/eris-all-things-root/171764-i-messed-up.html
http://androidforums.com/eris-all-t...please-cant-nandroid-restore.html#post1604509

 

[tproctor]

Thanks for the help. I'm a dumba$$ and renamed the HT folder instead of the BDS folder. Good thing I wrote the HT name down before I changed it as it is working now.

 

[scary alien]

Thanks for the help. I'm a dumba$$ and renamed the HT folder instead of the BDS folder. Good thing I wrote the HT name down before I changed it as it is working now.

No worries .

By the way, you could always figure-out the HT folder name again by either 1) doing another Nandroid backup to see what folder it creates, 2) looking under your battery cover for the serial number, or 3) issuing the command "adb shell getprop ro.serialno" (courtesy of eu1).

Cheers!