Develop Bugs

Nandroid Fail to restore Boot.img

Im Rooted thx to the great instructions posted by Regaw (Thx). One issue that I am having seems to be my Nandroid, before I install my first custom Rom I use Nandroid to back up my stock rooted 2.2, So today I wanted to see what was exactly the 2 saved back ups was (I had forgotten which was which). So i went to restore Via Nandroid and I get the "Error while Loading boot Image" as it begins to restore, funny thing is I can restore everything seperately except the BOOT.IMG. Plus I can restore my CM6 just fine with no issues. Only thing I can think of me doing since my stock rooted 2.2 was install/flash end bootloader to get my CM6 to install. Any suggestions would be sweet thx everyone.

Wats yur hboot ver?

My Hboot Version is 0.79

0.79.0000. That's wat seems to load with the directions. Download simpleroot and run nand unlock. For some reason that will bring u back to stock 2.1 but try to back up then it worked for me. When I tried to run Cm6 rc2 it always gave me an error cuz I was on .79 but then ran simpleroot and got .76 and haven't had a prob since...other than SERIOUS batt drain

I Think I needed to be on 0.79 to install CM6 before, 0.79 it would not install I think I was running 0.76. But I do have my CM6 Backed up...Thats what Im running right now.

If you ran the directions regaw posted u should have loaded .79. I would recommend load the nand unlock from toast on simpleroot to get .76 and even loading amon ra recovery

Im sorry I might of already had 0.79 after the root/2.2 install, I was able to install CM6 after someone told me to download end bootloader. then CM6 would flash just fine..Figuring out this Nanunlock still plus I do have the Amon recovery too.

I dont think simple root is working for me, I phone is sitting at the bootloader screen it says go into bootload and it should take a few minutes and press up for yes, But I dont have any files or zip files to update, while atleast I dont see them on the screen.

Boot Image Issues

In Brief:
Got New Phone due to light leak. Finally after 2 months
Came with 2.2 on it.
Used the new 2.2 Root Guide with Unrevoked. Worked great.
Installed VirusROMX - working great.
Wanted to try out the Final 6.0 ROM from Cyan.
NanDroided the ViruxROMX
Got an error 7? So I found this link that was to correct that issue.
http://forum.xda-developers.com/showthread.php?t=752832
Flashed the new Hboot and it allowed me to install the CYAN R6.0.
CYAN ROM - Keep on Rebooting and Reloading the CYAN Boot Screen after setup and scrolling some apps.
Removed it and went for a Nandroid Restore.
I get the MD5 Checksum message and then trying to reload boot image. And Boot Image cannot load.
I have tried to reflash the recovery(Clockwork) and still no good.
My working Daily with all my updates and apps are on the Nandroid. I would hate to lose it.
Any help would be appreciated.

Anyone?
Sent from my DROIDX using XDA App

instead of re-flashing the recovery, have you tried to do a restore via a nand recovery, or is that what your talking about that you did.

tomh1979 said:
instead of re-flashing the recovery, have you tried to do a restore via a nand recovery, or is that what your talking about that you did.
Click to expand...
Click to collapse
That's is what I tried to do. It would say boot image unloadable and spits me out to the HBOOT options. With no ROM loaded and messes up my current ROM in place.
At least for me when I restored in the past and I have done it often is that I would just restore and not wipe or anything since the restore does all of that for me. Well in this case it does not and when it cannot restore I have to reload a new ROM again in recovery and start the process all over again. I have tried the NANDROID again after going through the entire ROM reload again and still a no go.
I can't nandroid restore my old daily which has text messages and everything that I wanted to reference. I can live without it but the inability to restore any Nandroid is driving me crazy.
It happened when I flashed that HBOOT update on the link I provided in OP. I am just trying to figure out how to reflash the old image back so I don't have to worry about it. The only reason I did it in the first place is to test out the Cyanogen R6 and that wasn't a good experience.
I guess I could post in the thread that started all of this to ask. But I thought I would keep the SECTION POLICE from hounding me about posting in the wrong section

about the hboot, did you try the PC36IMG.zip, or did you do the flashable zip file through recovery?
I did the flashable file though recovery last night had no issue with that, maybe that's the problem, what is it showing for you current hboot.

tomh1979 said:
about the hboot, did you try the PC36IMG.zip, or did you do the flashable zip file through recovery?
I did the flashable file though recovery last night had no issue with that, maybe that's the problem, what is it showing for you current hboot.
Click to expand...
Click to collapse
The PC36IMG.zip - I will try the flash.
The Hboot through PC36IMG.zip worked fine. It's the nandroid thats fuxored. Will try later on and see. Thanks for the suggestion.

I had to redo the second part of the Froyo 2.2 update with the Rooted Froyo and the 2.2 unrevoked. It finally worked and I was able to restore. I really want to try out the CM 6.0 again in the future but not at the expense of time to restore to get it back.

ClockwordMod Recovery 3.0.0.5 problems (URGENT!)

Okay so i had CM6.1.1 flashed onto my evo and everything was working fine. i installed the new version of clockwork mod on my phone and i found something else i wanted to flash. i tried to reboot my phone and now everything force closes. and i mean EVERYTHING! i tried to restore all of my backups and none are working. can anyone help?

dude what i just did was go to rom manager and scroll all the way down flash alternate recovery and after its installed go and tap om clockworkmod recoveries and install the 2.5.0.1 and your good to go !!

JJS714 said:
Okay so i had CM6.1.1 flashed onto my evo and everything was working fine. i installed the new version of clockwork mod on my phone and i found something else i wanted to flash. i tried to reboot my phone and now everything force closes. and i mean EVERYTHING! i tried to restore all of my backups and none are working. can anyone help?
Click to expand...
Click to collapse
I doubt *flashing* clockwork would cause force closes. But you can always revert back to 2.5.0.1 or AmonRa and restore a backup. Check the "Legacy" area of ROM Manager.

I also had this problem as ROM manager kept informing me that a new version of clockwork mod was available. after "updgrading" I couldn't flash any new ROMs and got a truncated message that during the process that 3.0 series clockwork mod needed to have some files deleted due to changes with Gingerbread and something about google.... (sorry about the lack of good definition on this, but the text was truncated and I was freaking out at the time since I started getting stuck at the white HTC boot screen.) Eventually I was able to perform a recovery and finally flash back to clockwork 2.5 and everything is OK now.
Strangely, after doing this ROM Manager indicated that 2.5 CW was the current version... However, after a few hours I started getting the message to "upgrade" to 3.0 again. I'll just ignore that for now.
Does anyone know why 3.0 is not working for everyone?

I got this also, but i wasnt using CM...i was on a sense mod and was able to restore a different rom and went to the new amon-RA instead.
Maybe its something with CM specifically

It has to do with the scripts used in the update.zips. Most people are still using the olds version used in 1.5... Net said that he had to change it to the new scripts used in gingerbread which makes it not work with any updates or backups made prior. There is a topic on it in here where he explains it. He says to flash the 2.5 if it's not letting you update something.
snappydave said:
I also had this problem as ROM manager kept informing me that a new version of clockwork mod was available. after "updgrading" I couldn't flash any new ROMs and got a truncated message that during the process that 3.0 series clockwork mod needed to have some files deleted due to changes with Gingerbread and something about google.... (sorry about the lack of good definition on this, but the text was truncated and I was freaking out at the time since I started getting stuck at the white HTC boot screen.) Eventually I was able to perform a recovery and finally flash back to clockwork 2.5 and everything is OK now.
Strangely, after doing this ROM Manager indicated that 2.5 CW was the current version... However, after a few hours I started getting the message to "upgrade" to 3.0 again. I'll just ignore that for now.
Does anyone know why 3.0 is not working for everyone?
Click to expand...
Click to collapse
Sent from my PC36100 using Tapatalk

They put up a new version of Clockworkmod recovery 2.6.0.1. This will work for all that had problems with the 3.0.XXX versions of the recovery. All the goodies of the 3.0XXX but with amend support so it will work with all roms.

All I can say is that Amon has never let me down. May want to check it out if you haven't already. Even their recent update was smooth as silk. No problems for me.

I had this happen to me too with a flash resulting in the white evo screen loop. I was able to flash to the amon ra 1.8 but I couldn't flash anything. So I upgarded to the new version of RA but am still not able to flash anything. I go into the white evo screen loop and then I have to pull the battery and nand a restore. Not sure what I need to do now. Any help would be greatly appreciated.

[Q] having a bunch of problems. need help plz.

Ok where to start? I've been trying to get cm 6.1.2 running correctly on my evo and get it themed but can't seem to get it done and all the back ups I make through amon recovery just send me into boot loop or white screen. Everytime I flash cm and try to flash the 7.6 or 8.x kernel the rom becomes unstable and I get fcs everywhere then I try to restore and it freezes. Now if I just leave the kernel alone and try to flash themes I seem to be getting some unverified package error even after I turn off the security or some other error. I'm not sure if it is because I have ra2.2.1 and hboot. 76 if so I can't find the older ra1.8 anywhere but even with that out of about 15 backups only 1 or 2 where working and those where only sense that would restore.
Any ideas, all you brilliant people of xda?

You need to disable signature verification in Ra recovery to stop the unverified package errors.
As towards your boot loops after restoring a backup, I had the exact same problem with RA 2.2.1, I ended up switching back to clockword 2.6 and all my problems went away.

I have disabled the sig verification and I'm getting another error I can't get around it. I'm wondering if it is because I have the Eng .76 hboot running the newest clockwork and amon.

Major Major Issues With 2.1 - 2.3 (Rooted/Unrooted)

Hey guys,
So here's what happened and is happening:
1. I was running a custom ROM (Baked Snack 1.7) on Froyo (2.2). The phone was working fine but I wanted to try Gingerbread 2.3.3 out because I heard it had great battery life.
2. My phone would not update to 2.3.3 from Baked Snack. I thought it might have something to do with it being rooted. I used this method to unroot...and I think I only got through the first part:
http://www.thedroiddemos.com/2010/09/10/how-to-unroot-the-evo-in-2-steps/
I installed the S-On tool like he said to. Then I moved the "new updated version" of PC36IMG (I had the old version on my card already). He said something about the "S-Off" appearing on his phone but not the viewer's...well, mine says S-Off.
So fast forwarding, I got Sprint to push me the update for 2.3.3. It downloaded it, but then a voicemail error came up saying I had 2 voicemails. Then when I called voicemail, it said I had no messages. Sprint said a Sprint store would have to physically go into the phone to erase the error.
I also got a second update message that said there were minor enhancements to Gingerbread. I tried downloading them but the installation failed. Sprint told me to ignore the update, that there had been issues with Gingerbread (and the update) and that they were working on getting these resolved.
Somehow I managed to clear the phone and get back to 2.1. Here's what my system says when I look at the Phone Information:
Firmware Version: 2.1-update1
When I boot into the main bootloader/Recovery menu (Phone Off + Power Button + Volume Down), here's what it says:
Supersonic EVT2-2 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
If I click down to Recovery from this menu and press "Power" to enter it, NOW I get a picture of an EVO with a Red Triangle/Exclamation Point. This means I have to take my battery out and restart the phone.
Also, the OTA SimpleRoot procedure doesn't seem to work on the phone either. When I originally set it back, the procedure worked. Now it just goes through the motions on the computer but nothing happens with the phone (rebooting, skating Androids, etc.)
All I want to do is basically put it back 2.2 and re-run Baked Snack 1.7 which was giving me NO issues.
If someone could help me with this issue, I would be very grateful.

Well you have a simple fix. The error you got with the triangle and red ! is you booting into recovery, but no recovery is loaded [stock recovery]. Head over to the development section, and download the recovery of your choice. Personally I recommend in order: twrp [team win recovery project] , amon ra 2.3, cwm 3.0+. After you have your recovery installed, boot back into recovery and flash your baked snack rom. Also, don't manually take an OTA of 2.3.3 as it can't be rooted. if you want to try a gingerbread rom, simply download CM7, evervolv, deck's, ect rom and flash it like any other rom. Just backup your previous rom before flashing so you can go back.

teh roxxorz said:
Well you have a simple fix. The error you got with the triangle and red ! is you booting into recovery, but no recovery is loaded [stock recovery]. Head over to the development section, and download the recovery of your choice. Personally I recommend in order: twrp [team win recovery project] , amon ra 2.3, cwm 3.0+. After you have your recovery installed, boot back into recovery and flash your baked snack rom. Also, don't manually take an OTA of 2.3.3 as it can't be rooted. if you want to try a gingerbread rom, simply download CM7, evervolv, deck's, ect rom and flash it like any other rom. Just backup your previous rom before flashing so you can go back.
Click to expand...
Click to collapse
You like TWRP better??
I haven't tried it yet

HipKat said:
You like TWRP better??
I haven't tried it yet
Click to expand...
Click to collapse
Basically amon ra, but better. it has some additional options, such as the option to automatically reboot after a successful flash [good for doing a single flash, but if you're doing multiple, checked it at the last flash.] You have the option to compress backups to save space, though it takes a little bit longer, and they have some built in skins you can change at will. And MOAR.

I tried rooting using this method:
http://www.androidcentral.com/evo-4g-root-instructions
I put the PC36IMG on the root of my SD card and let the phone update in bootloader. It seemed to work fine, updated, rebooted the phone, etc.
Then I downloaded ROM Manager so I could let Clockwork install and then install Amon Ra....when ROM Manager tried installing Clockwork, it gave me the following message: "An error occurred while attempting to run privileged commands!"
It also will not let me flash an alternate recovery. I have the file "recovery-RA-supersonic-v2.3.img" on the root of my SD card right now.
What does this mean? Does this mean I'm not rooted? Or some other issue? I remember eons ago when I tried using this program I got the same message but I don't remember how I got around it. (obviously I did though)
Is there a different way I should install it?

nbakid2000 said:
I tried rooting using this method:
http://www.androidcentral.com/evo-4g-root-instructions
I put the PC36IMG on the root of my SD card and let the phone update in bootloader. It seemed to work fine, updated, rebooted the phone, etc.
Then I downloaded ROM Manager so I could let Clockwork install and then install Amon Ra....when ROM Manager tried installing Clockwork, it gave me the following message: "An error occurred while attempting to run privileged commands!"
It also will not let me flash an alternate recovery. I have the file "recovery-RA-supersonic-v2.3.img" on the root of my SD card right now.
What does this mean? Does this mean I'm not rooted? Or some other issue? I remember eons ago when I tried using this program I got the same message but I don't remember how I got around it. (obviously I did though)
Is there a different way I should install it?
Click to expand...
Click to collapse
That's a bit outdated; use unrevoked. I've already done the linking for you.
1. http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install <- Download and install the modified hboot drivers, follow the instructions.
2. On your phone, enable usb debugging from the applications > development, in settings
3. Connect your phone to your pc via usb cable, leave it on the home screen, no apps should be running; restart the phone just to be sure.
4. http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install <- download and run unrevoked
It'll take 3-5 minutes and reboot about 2 times, don't touch in the process, it'll say done at the end. Also, this will only work if on 2.2 still. if on 2.3.3, you're outta luck.

Okay, forget Rom Manager, forget "rooting" your phone - at least according to the normal use of the word.
Delete any PC36IMG files you may have on your SD card, then download this one of Amon Ra 2.3: http://db.tt/WP0beNa
Don't rename it, don't extract it... just put it on the root of your SD card. Then download whatever rom you want to use. Put it on the root of your SD card or in a folder that you'll remember. Amon Ra (and possibly other recoveries) can flash zips that are inside of folders. Just be sure that you know where it is because you'll need to navigate to it in recovery.
Then boot into the bootloader and let it flash the way you've done with other PC36IMG files. When it asks you to reboot just decline and then select recovery. I would make a backup just in case, then flash your rom.
Sent from my PC36100 using Tapatalk

Thank you guys, I will try these methods when I get back from work tonight. I really really appreciate it, I was about having a meltdown without my phone (the way I want it).
I'll report back either way. (and yes, I'm still on 2.1-update1)

nbakid2000 said:
Thank you guys, I will try these methods when I get back from work tonight. I really really appreciate it, I was about having a meltdown without my phone (the way I want it).
I'll report back either way. (and yes, I'm still on 2.1-update1)
Click to expand...
Click to collapse
Well between plainjane and myself, you'll be rooted before dinner time!

teh roxxorz said:
Well between plainjane and myself, you'll be rooted before dinner time!
Click to expand...
Click to collapse
OK, I forgot to mention this earlier...last time I was stuck in the Boot Sequence where it kept looping the Sprint and 4G logo....now that I'm rooted using plainjane's method (thank you) I'm stuck with the same thing.
I flashed the recovery, then flashed the Baked Snack ROM....now I'm in the Baked Snack bootload section....and it just keeps looping.
Is this an issue with my system that can be resolved?

EDIT: So weird. I went back into Recovery and wiped everything and set the phone back to original condition...and voila, Baked Snack comes up as the ROM! So now it appears it's for the most part back to normal and back to where I wanted it....thank you guys again.
Now can anyone point me in the direction of the latest radios, etc. that I can download and flash?
And why would it be giving me those looping problems, and then go back to normal when I cleared/wiped everything?
I mean, I'm happy this happened but I don't want the same things happening if I decide to flash another ROM at some point.