Nandroid Error - EVO 4G Q&A, Help & Troubleshooting

Last night after i did my nightly backup, i noticed that i couldn't exit the menu. After i did a backup, no buttons will work. I had to do a battery pull. I did three different backups, having to do a battery pull each time. Menu works fine, until i do the backup. It even says backup complete. The 3rd time i deleted the nandroid folder before running the backup, yet the problem is still there. I'm using the org HBOOT 0.76 eng, AMON_RA 1.8.0, CM 6.1.1, Zendroid kernel. Only thing i can think of is re-flashing the recovery and formatting the card. Anyone had this happen before???

Formatting the card did nothing. Re-flashed recovery did nothing. Any ideas???

You do a backup every night? Dang! I only one every couple weeks...
-Z

zzelinka said:
You do a backup every night? Dang! I only one every couple weeks...
-Z
Click to expand...
Click to collapse
Yea i do, i keep only the last 4 though. Just thought i would update this in-case it happens to someone else. To fix this, i had to repartition my sdcard in recovery, then reinstall my ROM. I guess what happen was when i installed the ROM on the new sdcard, without partitioning the new sdcard, it installed it wrong. This was causing the error.

This is one of the cases where your program failed working and is frozen like out of battery kinda fishy thingy there, I wish I could explain but It's bad mojo jojo.
I don't even use backups on my SDCARD, i put them on my computer, then switch roms/kernels with my pc on to my phone EVO. :/
THat sucks, sorry bro.

i dont have that problem with my nandroid backups but i keep gettin restore via adb on them...i keep about 3roms backed up on my card and this keeps happening...anyone have any ideas how to fix?

I'd try asking over the in Amon_RA recovery thread or you can @Amon_RA on Twitter. I've honestly never heard of or seen this issue.

Sounds like something is over-writing your recovery. "The moving over writer having writ moves on."
So start with all new "stuff" (os, recovery,downloads)

The recoveries are not very good about telling you what the Nandroid error was. You should run it via adb just as described:
adb shell
nandroid-mobile.sh -b (or I think -r for restore?)
Then you get a much better idea of what's going on. Happened to me once because my battery was too low to do a backup; recovery didn't tell me why, but running it from the shell did.

bwcorvus said:
To fix this, i had to repartition my sdcard in recovery, then reinstall my ROM. I guess what happen was when i installed the ROM on the new sdcard, without partitioning the new sdcard, it installed it wrong. This was causing the error.
Click to expand...
Click to collapse
Already fixed but thank you all

what was the issue? so others can find out as well.

Related

Can't NAND Restore

I NAND backed up my fresh Rom so I could get the PRI 1.40 update, and after the update I tried to restore back and when I click on my restore file I get the error something like " run nandroid-mobile.sh restore via adb"
I've backed up and restore plenty of roms, but for some reason this is the first error like this I've gotten.
I've been using and currently am using Amon RA 1.7 recovery.
I wiped/factory reset twice, data twice, and dalvic twice. Tried several times and even tried retoring another ROM from a few days ago and getting the same error.
I tried the command in adb, but that just doesn't seem right, I don't get a list of all my backup points, it just says "using a G1 keyboard, enter a directory name or substring and then <cr> to find matches or to accept defaults."
any help would be appreciated. Thanks!
first thing i would do is try a different recovery, RA 1.8 or clockwork. also, make sure that the md5 isnt corrupted. otherwise i would have no idea, i probably would just titanium my apps back and manually reset all my settings.
davebu said:
first thing i would do is try a different recovery, RA 1.8 or clockwork. also, make sure that the md5 isnt corrupted. otherwise i would have no idea, i probably would just titanium my apps back and manually reset all my settings.
Click to expand...
Click to collapse
I could do that, and I would, but I'd like to figure out the root cause of the problem so as not to have to do it in the future. I'd like to know I can Nand backup and Nand restore if and when I need to.
If I flash RA 1.8, i assume all my restore points show up the same?
Thanks
I've run into that problem for two different reason:
1. First, I had renamed my NAND backup files. I think if you place decimals within the file name (I.e "8.31.2010") it will give you that error
2. If you do not have a sufficient battery level it will not allow you to do a restore
astro004 said:
I've run into that problem for two different reason:
1. First, I had renamed my NAND backup files. I think if you place decimals within the file name (I.e "8.31.2010") it will give you that error
2. If you do not have a sufficient battery level it will not allow you to do a restore
Click to expand...
Click to collapse
I didn't rename the files, so that can't be it, but I just barely thought of the battery thing about 2 minutes ago. I actually got this error a couple days ago at night and gave up trying, the next morning (after charging the phone all night) I tried again, and it worked right off the bat.
I never thought it was because of the battery, but I do recall reading to make sure you have plenty battery left when flashing roms. I never knew that it was because it wouldn't physically let you flash. I thought it was more so your phone doesn't run out of juice while flashing.
I guess I'll try in the morning with a full battery and post back. I think I'm currently at 20% or so.
Thanks for the feedback.

[Q] HELP!!!!! Bricked Evo maybe??

Hi guys I am a noob and am pretty good with computers. I tried to flash cyanogen to my evo using there wiki page. I used clockwork for recovery then i downloaded the engineering spl. this is where things went to hell. i did the update from zip then it would reboot but get stuck and keep going to the fastboot page (with the android guy on the skateboard). i tried to nandroid but that didn't work. it says checking md5 sums for a long time then it say erasing boot before restore... restoring boot image.. error while flashing boot image!
I just want to go back to stock evo at this point. please help i can do anything with my phone!
You have to take you SD card out unless abd can be used here I don't know. Then copy amon ra recovery to the root of the SD then flash amon then wipe everything and flash cm6 again. If you can't get back into recovery I don't know what to say someone knows ya should probably check others points about it. Or you could just move another Rom onto the card and flash that clockwork and cm6 are bad news together.
exactly the same thing happened to me. HELP!
OK so if you power down the phone (turn it off), then, power up + volume down, can you get to recovery at all Y/N.
Step 2. Do you have a nand backup Y/N. If you do, perform a restore and carry on with life, if not, 3 demerits.
Step 3 will be dependent on 1 and 2 above.
yeah I can get into restore, but the issue is that when I try to restore a backup, it says checking MD5 sums for a bunch of time and then says erasing boot before restore, restoring boot image, then error while flashing boot image
How much battery do you have right now?
You need > 30% for nandroid restore to work.
The good news is, you will be able to recover from this....talk to me..
Ummmmmm..... I dunno maybe 50%. But sweeeeeet! I tried something, I just reflashed the ota update from last week and im getting a boot screen..... im gonna cross my fingers! I performed a backup before, so I am hoping that everything isn't lost since i did a factory data restore.
Sweet, let us know.
Always, Always, backup before flashing, I do a nandroid and titianum backup before flashing.
And before flashing wipe everything (me = twice) "ALL CACHES".
Im Lost: Did you do a nandroid backup first from Clockwork recovery?
ok so that at least go me back to where I was, but i tried factory reset before that so all my stuff is gone. I tried doing a restore from rom manager, and still says error locating boot image. Will this prove to be a problem later on? Like if I want to flash other new roms?
Download everything first, move it to your sdcard !!!!, then...continue...
Masonm159 , what I would do if I was you is (1) do a FULL wipe, everything !!!! (Exception, don't wipe battery stats and/or ext. partition, which you probably don't have anyway, cause you have not set it up...assuming)
Then try this ROM,
http://forum.xda-developers.com/showthread.php?t=793471&page=18
Post Number 1
Rom first, then Kings #9 BFS Kernel (kernel) this is the actual link, but it is also in the thread.
Then the theme: Swype v2.4.44.10912 MetaMorph theme
Then lastly:Stock Fonts
Flash them 1, 2, 3, 4, then reboot
Come up, everythings good, power down, come back up, everything is good, go into recovery, nandroid backup.
Reboot, done, Happy Camper.
If you like the ROM stay with it (best I have seen), if not, flash away from there.
Yeah I did, and a titanium backup too. The issue was that engineering SRL or whatever it was called. So I am back in business. Doesn't lookout backup all your stuff too, cuz I think I have one of those somewhere.
My main question is, will this problem persist if I try another rom? Will there be no boot image?
i did a nand but it "recognize it" i can see my sdcard and I can move items to it through adb, but when i try to install them it says " E: can't open /sdcard.update.zip (bad) intallation aborted."
ok so now i am trying to restore everything with titanium and it says error "there is a problem parsing the package" WTF
Great question, here is my hopothesis: If the ROM includes a kernel and I think most of them do, then yes, here is a script from Kings #9 (2.6.32.15), from the link I gave you already, if we look at a scipt included with this kernel , I found this script, which "creates" a new boot.img.
#!/sbin/sh
echo \#!/sbin/sh > /tmp/createnewboot.sh
echo /tmp/mkbootimg --kernel /tmp/zImage --ramdisk /tmp/boot.img-ramdisk.gz --cmdline \"$(cat /tmp/boot.img-cmdline)\" --base $(cat /tmp/boot.img-base) --output /tmp/newboot.img >> /tmp/createnewboot.sh
chmod 777 /tmp/createnewboot.sh
/tmp/createnewboot.sh
return $?
Now, with all that said, I am just now getting back into both Linux, scripting and diving into cooking. So my recommendation is, research to be sure.
Lastly, pass this message to your phone, welcome back to the living
Cya.
Screw Titanium and the apps, pull em from the market and be done with it. Sh!t I am now a pro at reinstalling, have documented my favorite apps. Have not yet used Titanium to restore, have not needed to so, it could be any number of things. So just pull em back down.
im lost, OK so when you say, "when I try to install them", what "exactly" does this mean, install them how?
Masonm159 said:
ok so now i am trying to restore everything with titanium and it says error "there is a problem parsing the package" WTF
Click to expand...
Click to collapse
Consider this your validation on whether these tools properly restore the apps, thanks for being a trendsetter here, laughing, sorry. Good news is, you are back in business.
sorry, try to restore them from titanium. Its ok I have app brain too, so i am just going down the check list of markit apps. I will just have to re do my homescreens. I am just worried about this boot image thing.
So lets talk about that if you have a few minutes, and my phone an I thank you by the way for the support and time. Now is there a unique boot image on every rom i flash? Or does my phone just have one that is used for every rom? ..... fun

Problems flashing, need help please!!!

Ok, so here is what I have done: I have already rooted my phone, etc, and have flashed some different roms on my phone, and have not had any problems until now. I recently tried the miui rom, but didn't like it.I just flashed the newest miui rom, and it was acting really weird, so I decided to go back to the virtuous rom which I had used before. For whatever reason, I am getting this error: E: can't mount /dev/block/mmcblk0p1 (file exists), and the installation aborts. I did the wipe data deal, and I also tried to reinstall the miui rom. It says that installs fine, but it won't get past the htc incredible screen. Any suggestions? Also, I didn't want to try this and mess things up further, but can I restore a backup I had done when I had the virtuous rom installed, or do I have to have the rom already working properly? Kind of a noob question, I know.
calamari85 said:
Ok, so here is what I have done: I have already rooted my phone, etc, and have flashed some different roms on my phone, and have not had any problems until now. I recently tried the miui rom, but didn't like it.I just flashed the newest miui rom, and it was acting really weird, so I decided to go back to the virtuous rom which I had used before. For whatever reason, I am getting this error: E: can't mount /dev/block/mmcblk0p1 (file exists), and the installation aborts. I did the wipe data deal, and I also tried to reinstall the miui rom. It says that installs fine, but it won't get past the htc incredible screen. Any suggestions?
Click to expand...
Click to collapse
Hmmm... Do you have any Nandroids from earlier roms? That'd be the easiest route.
If not, since you can't even get to a homescreen, you might try an RUU reset, but let's hope it won't come to that for now.
I get that too, but only when going into the menu for Dalvik Cache wiping, and it never actually gets in my way, it just pops up and then I can keep going on about my business.
1. yes you can restore the backup whether a rom is currently working or not
2. post questions in the correct forum
If you can't get a nandroid backup to work, you may have to RUU back to stock.
Here's the older one that will still let you use unrevoked after. Just rename this PB31IMG.zip, load up H-boot, follow the prompts, and be patient. Then run unrevoked when it finishes and install rom manager to restore your backup. If the backup still won't work, try a fresh install of virtuous.
Sorry
g00s3y said:
1. yes you can restore the backup whether a rom is currently working or not
2. post questions in the correct forum
Click to expand...
Click to collapse
My apologies, where should I have posted? And can I move the thread so it is in the correct place?
calamari85 said:
My apologies, where should I have posted? And can I move the thread so it is in the correct place?
Click to expand...
Click to collapse
Probably in the Q & A General Forum, but don't worry about it this time, just as long as it doesn't end up being a frequent thing.
But I don't know about being able to move the thread, I think that's a Moderator power.
Regarding your issue though, either use the RUU link posted above, or try Nandroid-ing back.
No go
I tried restoring a backup, and got cannot mount /data, along with the previous error... It changed my boot animation, but has not restored my phone. should I do this RUU back to stock? Sorry for not being very good at this, and I definitely appreciate the help.
calamari85 said:
I tried restoring a backup, and got cannot mount /data, along with the previous error... It changed my boot animation, but has not restored my phone. should I do this RUU back to stock? Sorry for not being very good at this, and I definitely appreciate the help.
Click to expand...
Click to collapse
It's cool.
Yes, you'll need it on the root of your SD-card (not in any folders), run it through hboot, and then you'll have to re-run the unrEVOked tool from your PC. I would also suggest running the S-Off tool afterwards, just to be safe. That has saved me once before.
Make sure you have at least 50% battery before you do the hboot flash. VERY IMPORTANT. If your phone dies or loses power while updating the radio files from the RUU, your phone is as good as bricked.
If you get stuck with the unrEVOked tool at waiting for root for more than fifteen minutes, post back here again and we'll continue from there.
EDIT: Actually, run the unrEVOked Forever S-Off tool through CWM recovery before doing this, as a pure precautionary measure.
I'm an idiot apparently
Well, I am really sorry guys, I won't ask any more questions on here. Apparently I am super stupid. I figured it out, I left out some info because it didn't even register as relevant, but it was the key apparently. So I just go a new sd card, and I formated it on my computer, and just dropped the zip files on there, and was trying to flash like that, and apparently the phone didn't like the new sd card, or it needed info off the old one, because once I put it back in and tried flashing from it, it works fine now. Sorry for bothering everyone, I am going to go sit in the corner in shame now.
calamari85 said:
Well, I am really sorry guys, I won't ask any more questions on here. Apparently I am super stupid. I figured it out, I left out some info because it didn't even register as relevant, but it was the key apparently. So I just go a new sd card, and I formated it on my computer, and just dropped the zip files on there, and was trying to flash like that, and apparently the phone didn't like the new sd card, or it needed info off the old one, because once I put it back in and tried flashing from it, it works fine now. Sorry for bothering everyone, I am going to go sit in the corner in shame now.
Click to expand...
Click to collapse
Hahaha! No worries, we all have our moments!
Glad you figured it out. Be sure to make a backup of your current rom on your new SD card right away haha.

amon-ra style recovery 3.11 problems/question

I'm having an issue with a nandroid restore with this recovery. It has been on the performing restore screen for quite some time now... enough to completely fill the screen with dots (greater then 20 minutes). All I did was perform a backup of my previous rom, upgraded ext3 to ext4 partition, wiped everything, flashed nitrous rom, didn't like it and wiped things again and performed restore and now I seem to be stuck here. Is it safe to pull the battery and just reflash my rom? Or should I let the device go longer on the restore? Never had this on prevous recovery (3.07). Did I do something wrong? Thanks.
wow i cant say i've EVER seen that happen lol i would have just done a battery pull and try it again? and or maybe just downgrade to 2.3 or something and then try and re upgrade? just a suggestion since i cant say i've ran across this personally but maybe someone else has
ben.nesheim said:
wow i cant say i've EVER seen that happen lol i would have just done a battery pull and try it again? and or maybe just downgrade to 2.3 or something and then try and re upgrade? just a suggestion since i cant say i've ran across this personally but maybe someone else has
Click to expand...
Click to collapse
Battery pull didn't harm anything thankfully. Ended up reflashing and just resetting the sd partition to ext3. Can mod mark solved? tia.

[Q] rom manager issue

i havent been able to restore any backups for a while now, not an issue since im not as bad with the crackflashing addiction lol
well went to try a restore, didnt work-error while flashing boot img
tried advanced restore and got the same messge.
how do i check to see why it isnt working properly?
ive never been able to get an answer for this issue before so a little help would be awesome
reason i tried a backup, i did a flashover on cm7, and lost some(quite a few) of my pictures...so i tried the backup and got that crap again
so ya...not sure whats up
OMG_VTEC said:
i havent been able to restore any backups for a while now, not an issue since im not as bad with the crackflashing addiction lol
well went to try a restore, didnt work-error while flashing boot img
tried advanced restore and got the same messge.
how do i check to see why it isnt working properly?
ive never been able to get an answer for this issue before so a little help would be awesome
reason i tried a backup, i did a flashover on cm7, and lost some(quite a few) of my pictures...so i tried the backup and got that crap again
so ya...not sure whats up
Click to expand...
Click to collapse
shouldn't your pictures have been on your sd card?
anyways, you didnt really give any helpful information as to what your problem is, but maybe you could try this http://forum.xda-developers.com/showthread.php?t=714114
yes they were on my sd card, thats what doesnt make a lot of sense about it
and its not say md5 mismatch, i told you everything my phone said...all it says is "error flashing boot img"
if i had helpful info pertaining to this issue id be a lot closer to solving it...
Yeah, There shouldn't be an MD5 mismatch when your phone generated the MD5 to begin with.
I would suggest reflashing clockwork a few times from within ROM manager. It is the first option on the app which says "Flash ClockworkMod Recovery"
If that doesn't help your problem:
It shouldn't make a difference because ROM Manager is made by the CWM team but I would suggest trying to create a backup from within Clockwork and see if you can then restore the backup or even to just try restoring the backup you already made from within CWM rather than trying to use ROM manager. I've heard a lot about ROM manager having problems, so even though it takes a little more work you might want to take that route from now on.
In case you don't know how, all you need to do to get to clockwork is hold down the power button on your phone and then select reboot into recovery.
Once you're in recovery mode you need to select backup/restore using the optical joystick at the bottom of the phone to make your selections. When you make a backup from within clockwork you are unable to change the name before the backup is created but when you boot your phone up you can use any file manager to navigate to the clockwork/backup folder on your SD card and the bottom one should be the most recent because they are listed by date and then time that they were created.
I know it is a little redundant but it is always worth trying the easiest thing first before trying to overhaul your phone.
i dont use rom manager for anything...
i think im gonna try to complete reflash and re root and see what happens...kinda pissed i lost a lot of my pictures though
really confuses me...
try checking the internal flash memory, for some reason some of my pictures wind up there on accident sometimes. When you connect to your PC it is the third mass storage that shows up usually. I don't know how to access it from within the phone. and I apologize for the confusion but the title of the thread is "ROM manager issue" so that's what i thought you meant.
i tend to mistakenly call cwm rom manager since thats where i got it from

Categories

Resources