when i try to restore my nandroid it says error flashing boot image please help
That happened to me once. I think the actual file was corrupt because I was able to restore from a different nandroid. Do you have any others saved that you can try?
I don't remember that exact error message (I actually think it might have been different), but a very similar (or identical) error can occur of on backup/restore you have a low battery, low disk space or have renamed the directories.
What recovery are you using?
Do you have other backupsyou can try?
Are you trying to restore a clockwork backup with ra, or an ra backup with clockwork?
Sent from my blah blah blah blah
Once you get through this (best option, use one of the other Nandroid backups if you have them), download and install Titanium Backup, I trust it more than Nandroid's backup. Heck use both before you install ROMS and make any major changes. Just a thought...
rcbarr said:
Once you get through this (best option, use one of the other Nandroid backups if you have them), download and install Titanium Backup, I trust it more than Nandroid's backup. Heck use both before you install ROMS and make any major changes. Just a thought...
Click to expand...
Click to collapse
Wait, what?
It's not like you have a choice to do one or the other, nand and titanium do totally different things. You should always do a nand backup before flashing anything, regardless if you use tb...unless I misunderstood what you're saying...
Sent from my blah blah blah blah
I am having this same problem. i switched from the regular sense rom to CM 6 rs2. i can load cm6 backups all day long but my sense rom gives me an error when i try to load it saying "clockwork mod error while flashing boot image!". Both nandroid backups were made with clockworkmod. I had to downgrade my version of hboot to install cm6. I am wondering if i need to upgrade it again to load my original sense rom or am i wrong in thinking this?
DaKlown said:
I am having this same problem. i switched from the regular sense rom to CM 6 rs2. i can load cm6 backups all day long but my sense rom gives me an error when i try to load it saying "clockwork mod error while flashing boot image!". Both nandroid backups were made with clockworkmod. I had to downgrade my version of hboot to install cm6. I am wondering if i need to upgrade it again to load my original sense rom or am i wrong in thinking this?
Click to expand...
Click to collapse
OP didn't give as much detail as you - good example of how details help.
You can only restore backups you made with the same version of hrboot. You can't restore a .79 backup while running .76 (which I'm pretty sure is what you downgraded to in order to load cm6).
Now I need to find flashable zips of both hboots so I can switch between cm6 and sense. I so miss my 4g lol. Thanks for your help!
I upgraded hboot to .79 and still got the same error. Funny thing is that my cm6 loaded fine and my hboot is still reading .79 anyone have any clue as to why sense wont load and why cm6 loaded on a different hboot?
did you ever get this figured out? i am in the exact same boat.
i rooted with unrevoked 3.21, this went well
i backed up oem sense in recovery via nandroid, this worked, i wiped and restored from this backup just to test, again the restore worked just fine.
later i tried to flash cm6 but all arrows pointing towards not having the right hboot. i dont remmeber what i had but i needed to got to eng boot .76.2000, which i finaly got figured out and was able to flash to cm6.
at this point cm6 loads and runs juts fine, i decided to boot to recovery and do a backup via nandroid, infact i did two of these back ups. i wiped my phone and did a restore just to test these back ups.
heres my problem: just for the fun of it i thought i would try to use the first nadroid back up to restore (that had stock sense installed at the time) and it wont flash. it says something about:
"Checking MD5 sums…
Erasing boot before restore…
Restoring boot image…
Error while flashing boot image!"
i thought i found a fix: i need to "Switch .76 with .79", this still did not allow me to restore from my oem sense backup, i get the exact same error.
i found another potential fix pertaining to going back to .93.
i feel like i dont know enough about what i am doing and im abit scared to try this as i dont see much info on this method.
basicaly i'd lile to be able to go back and forth between stock and custom for a while and also i'd like to be able to use nandroid backups to quickly do this.
am i approaching my problem correctly pertaining to the hboot thing? and can i just drop the .76,.79, 93. images in and out of the pc36image.zip file that i will place on root on my sd card with out anything else in this zip and expect it to just work?
i was able to achieve my objective and then some. now i can restore to a cm6 or a oem rom in a matter of maybe 5 or ten minutes.
maybe it wasn't directly the way i wanted to do it but i think it was similar enough that it worked without me understanding what i was doing therefore keeping me out of the mix which is why it probably worked.
what ui did was i found a ruu.exe for 3.29, i downloaded it and ran it
once it was done i ran unrevoked to get root again and the boot loader installed, i think the .97 boot loader was key here, but i dont know.
then i booted to recovery and did a nandbackup
then i did a nand recovery to my older backups of cm6-success
then i did a nand recovery of a older oem 3.29 sense rom- success
im sure that i rambled on here and i never really knew what i was doing but i was able to do what i set out to do and then some. if only we could dual boot roms.....
potna said:
i was able to achieve my objective and then some. now i can restore to a cm6 or a oem rom in a matter of maybe 5 or ten minutes.
maybe it wasn't directly the way i wanted to do it but i think it was similar enough that it worked without me understanding what i was doing therefore keeping me out of the mix which is why it probably worked.
what ui did was i found a ruu.exe for 3.29, i downloaded it and ran it
once it was done i ran unrevoked to get root again and the boot loader installed, i think the .97 boot loader was key here, but i dont know.
then i booted to recovery and did a nandbackup
then i did a nand recovery to my older backups of cm6-success
then i did a nand recovery of a older oem 3.29 sense rom- success
im sure that i rambled on here and i never really knew what i was doing but i was able to do what i set out to do and then some. if only we could dual boot roms.....
Click to expand...
Click to collapse
You are doing exactly what I am trying to do, and ran into the same trouble.
Seems like having to run unrevoked again is unnecessary. There must be a way to switch the boot loader without it ? Did you ever find a quicker way?
I feel pretty comfortable messing with this stuff, even though I am new to the EVO. That said, I really do not want to brick it doing something stupid. Messing with these boot loaders does scare me a bit.
potna said:
did you ever get this figured out? i am in the exact same boat.
i rooted with unrevoked 3.21, this went well
i backed up oem sense in recovery via nandroid, this worked, i wiped and restored from this backup just to test, again the restore worked just fine.
later i tried to flash cm6 but all arrows pointing towards not having the right hboot. i dont remmeber what i had but i needed to got to eng boot .76.2000, which i finaly got figured out and was able to flash to cm6.
at this point cm6 loads and runs juts fine, i decided to boot to recovery and do a backup via nandroid, infact i did two of these back ups. i wiped my phone and did a restore just to test these back ups.
heres my problem: just for the fun of it i thought i would try to use the first nadroid back up to restore (that had stock sense installed at the time) and it wont flash. it says something about:
"Checking MD5 sums…
Erasing boot before restore…
Restoring boot image…
Error while flashing boot image!"
i thought i found a fix: i need to "Switch .76 with .79", this still did not allow me to restore from my oem sense backup, i get the exact same error.
i found another potential fix pertaining to going back to .93.
i feel like i dont know enough about what i am doing and im abit scared to try this as i dont see much info on this method.
basicaly i'd lile to be able to go back and forth between stock and custom for a while and also i'd like to be able to use nandroid backups to quickly do this.
am i approaching my problem correctly pertaining to the hboot thing? and can i just drop the .76,.79, 93. images in and out of the pc36image.zip file that i will place on root on my sd card with out anything else in this zip and expect it to just work?
Click to expand...
Click to collapse
I'm having the same problem, but I don't have the luxury of either Sense or Cyanogen working--I'm just permanently stuck inside the ClockworkMod Recovery and can't get back to a nandroid restore point I've verified in the past as working.
Is there something I can do to remove the pc36img.zip file? How?!
I have amon_ra and I ran into this issue a while back too. You most likely got this error due to your battery level being too low. Turn your phone off, charge the battery for a while and try again.
http://forum.xda-developers.com/showthread.php?t=705026&highlight=%5Brecovery%5D
Near the top of his post it states your battery must be atleast 30%, in red text.
Sent from my HTC Evo 4g
Was using my dad's Desire (I have my own), and thought I would do him a favour by rooting it, so he could backup. I rooted using unrevoked 3.21, and did a backup using ROM Manager. I've heard this is a bad idea, but I never had a problem with my Desire using ROM Manager, and an older version of unrevoked.
Anyway, after the backup, I tried to restart, and it got caught in a boot loop, never getting past the pink circle. (My dad has a t-mobile, HBOOT 0.75, have since upgraded to 0.93 with android 2.2)
My old backup Roms that I did for my desire work fine on his phone, so I have been able to do the above, but I really wanna get his old system back.
I've wiped the cache, done a full wipe, re-rooted, loaded the backup from Rom Manager, and from recovery, and nothing seems to work. The best I can get is looping from the splash screen, but another variation is getting stuck on the pink arrow circle.
So, what is the deal with unrevoked and ROM Manager not working together, when they used to be fine with old versions? Do I have to now backup by recovery alone? But more importantly, is there any way to get my dad's backup back, or is it gone forever?
Please help,
I'm sorry I can't help but here is an advice, never ever use Rom manager. Gives me lots of problems and scared me badly so many times in recovery. Maybe the plain all recovery methods in the clockworkmod would do fine although it has never worked for me. When I use it I still go into boot loops. Try not to use it but maybe that's just for me. Maybe you could try to get the Rom your dad previously used, flash it and on your SD card, there is a folder called clockworkmod, in it there is a folder named backup. From there maybe you could recover your data. I am not sure how but there is always a possibility. Hope that helps!
Thanks for the reply. I've given the phone back to my dad now. He wasn't best pleased about the wipe, but I was able to pull out his contacts from the data.img, which was the most important thing.
Sent from my HTC Desire using XDA App
I installed a few of my favorite sense 2.1 skin .apk's from the Desire forum on my GingerSense ReMix Rom this morning. I knew it might cause an issue because they aren't officially set up for our phones/framework, but I thought that I could easily restore my Rom using the Nandroid backup I made beforehand.
I have attempted several times to restore the backup, but I am stuck in bootloop land. I wouldn't want anyone else to stumble across this problem by accident, so here is my warning: I don't recommend messing with it, might brick your phone. Here's hoping a complete wipe and reinstall will resolve my issues.
Here is my request: Can one of our pro themers/devs get us set up with some additional 2.1 skins? Even though the HTC hub is working, I would love some additional options.
Secondly: If someone can think of why a nandroid restore would send my phone into bootloop land, could you let me know what the problem is? Just curious. If I can get one of my older backups to work, I'll probably chill out with them for the time being as I garner the motivation to reattempt a GingerSense Rom.
Did you wipe before you restored? I've had issues with not doing that before.
heres more skins http://forum.xda-developers.com/showthread.php?t=1091564&page=3
hey all,
Im sure this is a random spot for this but, since we dont have a home yet.
Im looking for a stock back up image (Titanium backup pro)with all apps and system settings. I think I may have cleared out a system file or two when cleaning out all the Tmo bloat.
Any help or other suggestions would be great.
You didnt make a backup before you started deleting things?
Titanium back up said that a back up had been created but none was there after reboot of phone. now all kinds of issues.. just need an image to try and get it back
I am talking about a nandroid backup. You shouldnt mess with anything until you make a backup in recovery.
ok so do you have a Nandroid backup image to offer as a way to get back up and running?
Really need some help on this, I'm sure some one out there has made a back up on titanium back up pro or a nandroid back up please contact me.
Still looking for someone with a titanium back up or Nandroid image
still need some help
the mytouch q currently has no way to boot into recovery that i know of. even if you do get the system backups you may have problems, i keep trying to restore mine with titanium but it does nothing. just shows a progress bar for hours and hours.
can you adb? On the lg c800 (mytouch q), adb reboot recovery will do a factory reset.
HELP!
NEED SYSTEM PROP FOR lg c800g mytouch q please reply need to fix force close on camera
Hello,
My dad wanted soft keys on nikez ics. I copied the zip to the SD card and flashed it to his phone. I'm 100% sure it was for the right version of the rom. It was stuck in a bootloop. I thought no problem I still have a nandroid backup. So I restored the nandroid backup and restarted the phone. But when it was on I noticed that a few things had changed. For example all the homescreens he had set up are gone. Second and more important is that his apps still are in the appdrawer but they all force close when I open them. What went wrong and why doesn't the nandroid restore everything as it was before I made the nandroid backup. Can somebody please help me out!?
Thanks in advance,
Rsdf430.
Maybe the sd-ext broke somehow. Try repartitioning your sd-card.