So I'm basically trying to unroot, reroot my phone to try and fix 4G issues, (my WIMAX partition and key are alive and kicking), and have ran into a few issues.
After I was back to stock and up to date with everything, I ran Unrevoked 3.21, installed Amon RA recovery, and did a nandroid backup of my stock ROM. Everything was great until I decided to wipe, and flash a ROM. No matter what I do, I cannot get out of the bootloader! It keeps starting up everytime the phone is reset, and immediately going into fastboot.
I've flashed numerous PC36IMG.zip's to try and fix this, and I'm at a lost. Where do I go from here?
I have managed to flash a PC36IMG to get me back up and running, but after rerooting, I cannot seem to flash any ROM without instantly being thrown back into this bootloop!
HBOOT 0.79.0000
RADIO 2.05.00.06.10
Apr 14 2010, 15:41:34
I have Amon RA 1.80...
I managed to fix this somehow... Sitting on my butt all day on my only day off!!!
I believe I ended up flashing some PC36IMG file that was of the newest RUU. It put HBOOT 2.02 on my phone!!!
I managed to get it working properly, and found out how to get Amon RA recovery installed which is a complete PITA.
Oh well. 4G is now working in every ROM it's supposed to! SUCCESS!
Mine did that when I downgraded my hBoot back to .76, I was able to bring it back with everything how I left it by just flashing a kernel.
I'm guessing the hboot and boot images are tied together somehow so that the latter needs redone if the hboot changes.
can you tell me which PC36IMG you used?
Thanks
xHausx said:
Mine did that when I downgraded my hBoot back to .76, I was able to bring it back with everything how I left it by just flashing a kernel.
I'm guessing the hboot and boot images are tied together somehow so that the latter needs redone if the hboot changes.
Click to expand...
Click to collapse
I don't know enough about the HBOOT, or bootloader. I'm still used to having just Amon RA on my old Hero's. Definately more stuff to learn, and now that I'm on HBOOT 2.02, it just means more things I'll have to understand if I decide to unroot/root in the future.
whoisjlk said:
can you tell me which PC36IMG you used?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=791019&highlight=PC36IMG.zip
I FOUND IT! I was looking for that all morning. That is the zip that fixed my problems. Only thing, is that I flashed it with s-off, and no recovery. So after that, I was on HBOOT 2.02, with no recovery. So I spent about three hours figuring out how to properly install Amon RA.
Related
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.
I flashed a file that was suppose to update my ra recovery and give me the eng hboot. Afterwards it would only boot to hboot. Nand restores would say they were successful but I would still have the same problem. Someone suggested flashing a rom, so I flashed fresh. It started loading, but bootloops on the splash screen. I rebooted into recovery and try to reboot the phone but it just goes to hboot. Please help!
Same thing happened to me after flashing that for unrevoked forever. Would just go into that screen. I had to do a clean cache/factory resent, dalvik and all from RA recovery and flashed a new ROM and that fixed it. In my case, I flashed AvaFroyo6 and CM6 Final as well, both worked, didn't try it with Fresh.
Thanks for replying! I will try that!
This has happened to several of us trying to do the ENG HBoot update. Not sure why some are fine with it, and others of us get stuck in hboot.
Did you go through the Amon_Ra path on the second part of the 2.2 root, or clockwork?
I did amon_ra. Wondering if there is a coincidence.
Amon Ra. I just flashed cm6 and that worked. I am not sure what to do now. Update recovery? Nand Restore? Step 2 of the root process?
ENG HBoot for the Desire???
I've not heard of such a beast, so I'm guessing this is an EVO thread that's been moved here by some overzealous mod?
Regards,
Dave
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 made a nandroid backup, went into recovery mode, and flashed the new Combo (radio, wimax, pri, nv). It said "reboot from menu to complete installation" so I did. It said "writing image" and seemed to be going fine, but then instead of rebooting into android, it went back to recovery and said "formatting cache..."
But it never finished, it just sat at formatting cache for ages. Eventually I just rebooted on my own, but now it just freezes at the splash screen and I have to do a battery pull. I tried: restoring my nandroid, wiping cache, everything I could think of, but I can't boot into Android no matter what :'(
Can someone please point me in the right direction???
Can you still get into recovery? If so try flashing a new PC36img.zip
yeah i can get into recovery. what does that zip file do?
milesnerenberg said:
yeah i can get into recovery. what does that zip file do?
Click to expand...
Click to collapse
Itll reflash everything. You will lose everything but at least it should get you back up. What hboot do you have? Remember which version software u were running?
After flashing it, even though i lose everything, i will be able to restore a nandroid backup right?
And can you point me towards the proper zip file?
milesnerenberg said:
After flashing it, even though i lose everything, i will be able to restore a nandroid backup right?
And can you point me towards the proper zip file?
Click to expand...
Click to collapse
Ya it should get your radios and recovery in order and then you can recover your nandroid. Theres so many version softwares out right now that it depends on alot of things. Which hboot are you running? Evo hardware ?
when i boot into recovery it says:
SUPERSONIC EVT2-3 SHIP S-OFF
HBOOT-0.97.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
does that tell you what you need?
ur issue is the same i had last week.
you cannot update the radio, pri, nv or wimax of a rom that doesn't support it. resulting in the situation ur in now. what u must do is boot into the recovery, and flash all the old components u had before.
i had this issue when i flashed a new 3.70 rom that also updated everything else. the new rom ran fine, but when i attempted to "roll back" and nandroid my older rom, it resulted in boot loops or stalling at splash screen.
once i reflashed all the old components my older rom booted fine.
and when it says formatting cache, its actually done, but doesn't say it. hit restart device in the recovery and let it boot.
so go to the radio archive thread,
http://forum.xda-developers.com/showthread.php?t=715485
and d/l and flash older each component, (wimax, pri, nv, radio) then nandroid ur latest back up.
dont update ur hbOOT, ITS UNNECCESSARY.
ull be fine.
malibu_23 said:
ur issue is the same i had last week.
you cannot update the radio, pri, pvi or wimax of a rom that doesnt support it. resulting in the situation ur in now. what u must do is boot into the recovery, and flash all the old compnents u had before.
i had this issue when i flashed a new 3.70 rom that also updated everything else. the new rom ran fine, but when i attempted to "roll back" and nandroid my older rom, it resulted in boot loops.
once i reflashed all the old components my older rom booted fine.
and when it says formatting cache, its actually done, but doesnt say it. hit restart device in the recovery and let it boot.
so go to the radio archive thread, and d/l and flash each component, then nandroid ur latest back up.
ull be fine.
Click to expand...
Click to collapse
Ya give that a shot, everything I find are stock PC36img.zip that will put you back to stock but probably unroot you.
so if i flash the newest radios and everything, and then flash a rom that i know requires those radios, it should start up fine as well, correct?
Any luck?
Sent from my Evo CM6
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