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.
Related
ok i am running simpleroot evo 2.1 and i was trying to flash the stock froyo rom but everytime i go into recovery to flash it, it gives me a error when attempting to write the boot. error on line 5 to be exact. then on restart the phone goes into an endless white screen reboot. before the flash i did a phone wipe and cache wipe. neither work. has anyone else had this problem and is it fixable? i flashed the radio and wimax fine. and i had this problem attempting to flash the Ava froyo mod also. they all end in a nand restore....
thanks in advance
Damn bro, I'm sorry you are having such difficulties flashing Roms. What recovery are you using to flash? RA or clockwork? Whichever one you are using, try using the other one and see if you get the same error.
Sent from my EVO 4G(Extraterrestial Velocity Object from a 4th Galaxy) - **** is fasttt
tried clockwork and ra neither work, and its with all roms, its line 5 with the froyo roms, line 383 i think with other roms, and another line 400 something error, but there all with the boot. everything else seems go fine
Any ideas? I also used the htc stock 1.47 ruu to restore the phone and re root. Still getting the boot error
ok, well i didnt get any answers to WHY the error was being caused but i did manage to get the stock OTA rooted via unrevoked forever. restored the stock recovery on the evo then did the OTA update, flashed clockwork recovery afterwords then installed superuser from recovery. so basically stock froyo rooted, which was all i wanted. so for anyone else having problems you can still maintain root after the OTA if you install unrevoked-forever.
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.
OK, so I'm a bit of a n00b here, and I need just a quick hand.
I'd flashed Myn's Warm TwoPointTwo a few days ago and was attempting to use metamorph to tweak the battery icon. Ran a Nand backup beforehand. Something went wrong with the metamorph and I was stuck in a bootloop afterwards.
So I hit power and held down on the volume rocker, hoping to get into my Nand.
Instead, it wouldn't let me select anything, went through its own update/recovery process, and now that it's done, I'm back to stock (complete with sprint bloatware) and totally unrooted. I DLed Rom Manager off the market and tried to get into Amon_Ra recovery, but it keeps telling me I don't have permission (thus I deduce I've lost root access.)
Is there anyway I can flash my Nand at this point, or do I need to go back through the rooting process?
Thanks for your help.
MadDogMaddux said:
OK, so I'm a bit of a n00b here, and I need just a quick hand.
I'd flashed Myn's Warm TwoPointTwo a few days ago and was attempting to use metamorph to tweak the battery icon. Ran a Nand backup beforehand. Something went wrong with the metamorph and I was stuck in a bootloop afterwards.
So I hit power and held down on the volume rocker, hoping to get into my Nand.
Instead, it wouldn't let me select anything, went through its own update/recovery process, and now that it's done, I'm back to stock (complete with sprint bloatware) and totally unrooted. I DLed Rom Manager off the market and tried to get into Amon_Ra recovery, but it keeps telling me I don't have permission (thus I deduce I've lost root access.)
Is there anyway I can flash my Nand at this point, or do I need to go back through the rooting process?
Thanks for your help.
Click to expand...
Click to collapse
To get a recovery on your phone, you need to have root.
To get root need superuser permissions and/or nand unlock
To get nand unlock and superuser permissions you need to go through the rooting process.
If you've used unrevoked 3.21 and have S-OFF. You can flash recoveries and superuser permissions without having to go through any rooting process.
So I guess then what I need to understand is how would I go about flashing the superuser?
edit: at this point I've already gone through the whole rooting process, including unrevokedforever.zip and the additional ENG bootloader. I get into ROM manager, and go to recovery, but the clockworkmod recovery doesn't see my most recent backup. Reflashing to RA recovery, it finds it, but tells me I have to run the recovery via ADB. ???
Pretty sure what happened is that you left a stock pc36img.zip on your sd card, leftover from your rooting process. When you booted into hboot, it loaded it automatically and you must have hit update. Not sure what caused your bootloop though.
Check your sd card, and if theres a pc36img.zip on it, delete it. Look for the superuser app in your app drawer, and also check your hboot to see if you're s-off. If you are in fact back to unrooted stock, you can always run unrevoked to quickly root and then you can restore your nandroid, just make sure you have the same recovery that you used to make the nandroid.
MadDogMaddux said:
So I guess then what I need to understand is how would I go about flashing the superuser?
Click to expand...
Click to collapse
When you go into the loader (Vol Down + Power) does it say S-Off in the first line?
If it does then you still have root and you can flash the custom recovery's .zip and you will be able to load back into recovery.
If you have S-Off read this: http://forum.xda-developers.com/showpost.php?p=8285266&postcount=1
Flashable SuperUser is located here: http://forum.xda-developers.com/showthread.php?t=682828
_MetalHead_ said:
Pretty sure what happened is that you left a stock pc36img.zip on your sd card, leftover from your rooting process.
Click to expand...
Click to collapse
Definitely. So now I need to get my microSD card reader and remove it. Can do.
Any idea why both Clockworkmod and Amon_RA are unable to load my backup? Versions for RA should be the same, and I think the same for Clockwork as well.
OK, I deleted PC36IMG.zip, now it just stays stuck in bootloader.
looks like I'm hosed, but here's what I'm learning on Freeza's thread, where I DLed the PC36IMG.zip in the first place:
freeza said:
UPDATE: It appears as though everyone is getting stuck in bootloader after this procedure. You can get out of this by reflashing your current ROM (without wiping) and/or restore a nandroid backup. Some have reported errors when trying to restore a nandroid backup. YMMV
Karadorde has put together a package that works. Read his instructions below:
First and foremost it seems that if you get stuck in the Bootloader (no matter what method you are using) then your Nandroid backups are broken. I don't know that anyone has been able to successfully restore from one of those yet.
The file in the OP allows you to apply just the engineering HBOOT.img (hboot_0.76.2000.img) This works flawlessly for some but not so well for others.
The file in Post 71 and Post 91 allows you to apply a full PC36IMG.zip that contains the engineering HBOOT.img (hboot_0.76.2000.img) This is a fix for some who have gotten stuck in the Bootloader after using the file from the OP. At the same time this has also caused the some of the same issues people were having with getting stuck in the Bootloader from the OP. This file will not downgrade any part of your phone, however, it will wipe the phone. Also it is reported that it broke root on one phone. I believe this only happened to one person, need confirmation on if it happened to multiple.
If you get stuck in the Bootloader you can re-flash your Kernel to fix the issue. Not sure if this works with the stock Kernel or if you have to have a custom Kernel. Looking for feedback on this.
If you get stuck in the Bootloader reflash your current rom. Need feedback on this as well.
Link to Karadorde's updated package: http://www.freeza-inc.com/PC36IMG.zip
Click to expand...
Click to collapse
With the text I've put in bold, looks like I'm hosed in that regard. So I'll just work on rebuilding it piecemeal.
Heh, first time I've tried to recover from a Nand, too. *sigh*
MadDogMaddux said:
looks like I'm hosed, but here's what I'm learning on Freeza's thread, where I DLed the PC36IMG.zip in the first place:
With the text I've put in bold, looks like I'm hosed in that regard. So I'll just work on rebuilding it piecemeal.
Heh, first time I've tried to recover from a Nand, too. *sigh*
Click to expand...
Click to collapse
If you reflash using the RUU from stock roms .com will that reset your hboot back to the non-dev hboot?
Sent from my Evo using XDA App.
xNotta said:
If you reflash using the RUU from stock roms .com will that reset your hboot back to the non-dev hboot?
Sent from my Evo using XDA App.
Click to expand...
Click to collapse
i do believe so, but someone correct me if im wrong, i do know when i unrooted a few weeks ago with the RUU i went to the newest hboot, but now that i'm rooted again im back to the ENG .76 version.
Running a RUU will put you at full stock, including radios and hboot.
If you are still stuck, try running the most current RUU and then rerooting.
http://forum.xda-developers.com/showthread.php?t=800582
_MetalHead_ said:
Running a RUU will put you at full stock, including radios and hboot.
If you are still stuck, try running the most current RUU and then rerooting.
http://forum.xda-developers.com/showthread.php?t=800582
Click to expand...
Click to collapse
RUU's solve everything. No? haha
Igotsanevo4g said:
RUU's solve everything. No? haha
Click to expand...
Click to collapse
They've sure helped me out of more than a couple binds
I am a bit confused about what to do now. First off.. I have the Evo rooted with OS 2.1 but recently I just found out that 2.2 has been rooted. So now I just need to know what to do to get rooted 2.2. I read on some searches I did that I can just flash a 2.2 rom and that would be fine but I am a little concern about doing it that way. I was wondering if I need to UNROOT then download the over the air update that sprint has to get 2.2 then start my root process from there or is there a guide that someone can link me to in order for me to proceed? Thanks for your input.
Just find a rooted stock rom in the Development forums (or experiment with a custom rom. There are several that don't lose any functionality these days). Do a nandroid backup, and a Titanium backup of your apps and data before since I think you will need to do a data and dalvik cache wipe.
The alternative you proposed would probably take you all day and it would still wipe!
Think of it this way. All of the 2.2 ROMS you flash is just like an upgrade from Sprint. If you flash the 2.2 OTA ROM its the same thing as getting from Sprint, but you don't lose root user access. Hope this clears it up a little. No need to jump through all the hoops you referenced.
So its has been a while since I did anything with my phone so I had to youtube how to flash a rom. When I get to the part where I select recovery it goes to a screen with a phone image with a red ! mark on it. What does that mean? Maybe I might just take path of unrooting this 2.1 and upgarding to 2.2 then root from there? Can someone direct me which steps to take? thanks
Whatever you do.....DON'T FLASH YOUR RADIO AND WIFI. You'll be screwed. Has taken me 24 hours + to get my ability to tether wirelessly back on my rooted 2.2 (I'm not complaining. the rooted 2.2 ROM is freagin awesomeness!)Just in case you do by accident there's lots of info out there on how to try to dig yourself back out.
Don't unroot your 2.1 dude.
ROM's are ROM's. It doesn't matter if it's 2.1 or 2.2, you can flash either one and flash back and forth between the two at your own leisure. Back before 2.2 was officially out for the evo, I used to flash back and forth between working 2.1 and experimental 2.2 on almost a daily basis. They always booted fine, my phone did not explode.
Reboot with volume key down, select recovery, wipe everything, flash the new rom, reboot.
You don't have a custom recovery installed, do you remember if your NAND is unlocked?
If you need to check turn off your phone and then turn it back on while holding the volume down button. At the top of the screen it should say either S-ON or S-OFF and below it an hBoot version. If it is S-OFF and ver .76 it should be simple for you to update it.
Thanks for the input guys. So I guess the final word is to not unroot my phone and just flash. Now to my problem with recovery mode.
Haus, it says S-ON and hboot is veryson 0.79.0000. Is this a problem? Can you guide me on what steps to take or what should i search for? thanks again.
still wasn't able to find information on this. anyone can link me? thanks
can anyone link me to where i should start?
well your going to want to make sure you have a custom recovery, when your in the bootloader scroll to recovery and click on it, if anywhere it says clockwork or amon ra, your set and then you only need to flash unrevoked forever to turn your s-off and then you can start flashing 2.2 roms from the htc evo android development section
if you do not have a custom recovery just head on over to unrevoked.com and download their latest for the evo, it will give a custom recovery and flash your s-off for you and youll be ready to roll
I tried and the problem I am having is when I select the recovery option it reboots and then shows a phone with the ! sign. Doesn't let me flash anything. This is where I am stuck now.
As mentioned before, you need to install a custom recovery on your phone. If you are rooted, then perhaps you can download ROM Manager and installed ClockworkMOD?? You can also change to Amon_RA as well through ROM Manager. Otherwise, in the unrevoked forever wiki, they do provide PC36IMG files that should install a custom recovery on your phone (take your pick of either ClockworkMOD or Amon_RA).
http://unrevoked.com/rootwiki/doku.php/public/forever#reinstalling_an_official_recovery
Scroll down to "Reinstalling an official recovery" section and you will see the links for the PC36IMGs.
Alright so I just remembered what that phone icon with the red ! meant. I plugged it back into my win7 machine and ran windowrecovery.bat and I somehow managed to flash it to s=off. So now all I have to do is select the rom I want to flash?
Rom manager
if you have a custom recovery, then yes download a rom from the development section and move it to the root of the sd card. Boot into recovery and wipe your dalvik and data. Go bac and choose install .zip from sd card. Find the file you downloaded and flash it. Wait for it to boot up and your good. Orrrrr download rom manager from the market and you can do all this from there.
I'm rooted, unrevoked; I'm currently stuck in a boot loop. I can not reach recovery. I can not get to my rom. I can only access bootloader.
So far I have taken these steps to cure my problem:
Ran RUU software in Windows (with and without sd card in evo)
Flashed RUU as PC36IMG in bootloader
Cleared Storage using fastboot in command prompt
Cleared Recovery and then Flashed Amon Ra's Recovery and Clockwork using fastboot in command prompt
Flashed Amon Ra's Recovery and Clockwork as PC36IMG in hboot
Flashed Sprint Lover's as PC36IMG in hboot
Flashed eng-PC36IMG from Toastctfh's Old Root Tutorial as PC36IMG in hboot
Each of these methods flashed successfully as far as I can tell... yet I still go into an infinite boot loop.
Before the bootloop this is what I was doing:
I had the initial CM7 nightly installed for about 2 weeks. It was buggy, and a few days ago restarted and deleted all my texts, and desynced from google. On rebooting, google apps acted as if I had never ran the phone before - it asked me to enter google account info, etc, upon reboot.
I decided CM7 was too unstable and so I wiped data and davlik, and flashed CM6. When CM6 booted google apps was already on, before I had even flashed it! Anyways I figured I wanted to give MIUI a run, so I wiped data and davlik, and flashed MIUI. It ran fine for about two hours, and then rebooted out of nowhere... and never came out of the boot loop.
I'm really starting to sweat this as I have gone three days now without a phone. Does anyone have any ideas that may help me? Thanks.
hmm, you could flash recovery through bootloader i think
davidc23 said:
hmm, you could flash recovery through bootloader i think
Click to expand...
Click to collapse
thanks for the suggestion!, but thats what i meant by
Flashed Amon Ra's Recovery and Clockwork as PC36IMG in hboot
all i need to know can u get into recovery? cause if u can flash calkulins format all and flash the rom and ur good
Nope, I can't reach recovery
idk what to say hopefully a expert drops by im sorry that i cant help
Maybe bootloops from having an older radio. Gb roms need the latest radios. You can get a flashable zip in caulkins thread
Swyped from a galaxy far far away......
Jimdog420 said:
Maybe bootloops from having an older radio. Gb roms need the latest radios. You can get a flashable zip in caulkins thread
Swyped from a galaxy far far away......
Click to expand...
Click to collapse
I had same problem, the radios messed my phone and was stuck in a boot loop and mess with my usb drivers as well so I couldnt charge my phone...i had to buy spare battery charger and flash different radio and rom through hboot
I'm pretty sure Sprint Lover's and RUU have the latest radios in them
You shouldnt be bricked and if you flashed an RUU, you wont have root anymore, nor will you have a recovery img. I would suggest running the RUU again. As long as it finishes without errors, you should be fine. Now, just a quick question, what are you seeing that makes you think you are in a bootloop??
Are you sure RUU removes root? I've RUU'd through my computer, as well as flashing an RUU zip as PC36IMG, and I still have S-OFF. If it would turn it to S-ON, that would be amazing.
your ruu file could be bad as well .. it happened to me once and had to redownload...for some reason it wasnt as big as it should of been