I am having some issues. Don't know what is the problem. I nandroid to a sense rom and changed prl. Switched back to CM7 nightly 64 nandroid. Flashed tiamat's latest aosp kernel and did the viperboy's battery mod. Afterwards, my phone was stuck in boot loop. I went into recovery and there's nothing there. In the bottom of the screen, it says Build: RA-supersonic-v2.3, but the options aren't visible at all. And now, there's no way for me to boot the phone.
Any help would be greatly appreciated.
Can you not reflash amon RA via the bootloader?
posting & replying via the XDA Premium app.
jblazea50 said:
I am having some issues. Don't know what is the problem. I nandroid to a sense rom and changed prl. Switched back to CM7 nightly 64 nandroid. Flashed tiamat's latest aosp kernel and did the viperboy's battery mod. Afterwards, my phone was stuck in boot loop. I went into recovery and there's nothing there. In the bottom of the screen, it says Build: RA-supersonic-v2.3, but the options aren't visible at all. And now, there's no way for me to boot the phone.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try pulling the battery, and reflashing your recovery, using a PC36IMG.
Sent from my PC36100 using XDA App
I was able to flash to Amon RA 2.3 (I was originally on 2.1). However, that didn't fix the issue. Now, I just did a PC36IMG.zip for a stock unrooted. Hopefully this works and I can get back to root.
jblazea50 said:
I was able to flash to Amon RA 2.3 (I was originally on 2.1). However, that didn't fix the issue. Now, I just did a PC36IMG.zip for a stock unrooted. Hopefully this works and I can get back to root.
Click to expand...
Click to collapse
It sounds like the recovery isn't being flashed correctly... are you sure that it is being flashed properly?
Related
I flashed the following: EVO_Radio_2.15.00.11.19_WiMAX_27167_R01_PRI_NV_1.90_003.zip
http://www.mediafire.com/?6jb1pee933ubsex
Pulled battery, wiped everything. Still stuck. Pulled battery, nandroid into backup, still stuck.
Any ideas?
your the third person tonight reporting that problem
to the sprint store for you!
NewZJ said:
your the third person tonight reporting that problem
to the sprint store for you!
Click to expand...
Click to collapse
Recovery work perfectly fine, let me try flashing some other rom.
Also, because this might be a bad radio flash, can reflashing radio hurt?
jerryparid said:
Recovery work perfectly fine, let me try flashing some other rom.
Also, because this might be a bad radio flash, can reflashing radio hurt?
Click to expand...
Click to collapse
ahh, missed that part, you could try downgrading or reinstalling
jerryparid said:
I flashed the following: EVO_Radio_2.15.00.11.19_WiMAX_27167_R01_PRI_NV_1.90_003.zip
http://www.mediafire.com/?6jb1pee933ubsex
Pulled battery, wiped everything. Still stuck. Pulled battery, nandroid into backup, still stuck.
Any ideas?
Click to expand...
Click to collapse
Could you give more information so I could be of help. Like what Rom, kernel, recovery anything specific...
Sent from my PC36100 using XDA App
I recommend you flash the previous version and then do a full wipe....next, flash a rom...then when that boots you can go back into recovery again and restore a nandroid if you would like....
Sent from my PC36100 using XDA App
Using Clockwork 2.5.1 (?, flashing right now) so I can't check.
Was on MYN RLS4. Flashed the bundled radio zip linked above, now in this situation. Currently, I'm flashing to RLS5 after a ADB push of the zip file. Edit: Was on BS#6 Kernel
If this doesn't work, I'll flash a deodexed stock 3.70.
Any more recommendations?
edit: Looks like I got past the HTC Evo 4G screen, just waiting for the MYN boot animation now.
edit2: I booted up, thanks for the help. At least I can rest knowing that my radio flash wasn't borked.
jerryparid said:
Using Clockwork 2.5.1 (?, flashing right now) so I can't check.
Was on MYN RLS4. Flashed the bundled radio zip linked above, now in this situation. Currently, I'm flashing to RLS5 after a ADB push of the zip file. Edit: Was on BS#6 Kernel
If this doesn't work, I'll flash a deodexed stock 3.70.
Any more recommendations?
edit: Looks like I got past the HTC Evo 4G screen, just waiting for the MYN boot animation now.
Click to expand...
Click to collapse
What happened after you flash the radio? Be specific..
Sent from my PC36100 using XDA App
Ive had the same problem today on two different evos, with two different recoveries! Both times I just booted into recovery and ran a full nandroid backup, then restarted and it stuck in white screen.
First was with amon_ra recovery. I pulled the battery after it stuck on white screen and it rebooted fine.
Second time was with clockwork. I just now pulled the battery and rebooted..... and it looks to be sticking again.
Both are running Fresh Rom. v3.5.01 I think.
Do you have the SDK installed and a usb cable? Hook up the evo, then do: "adb logcat", power on, and post the output. Note: it sounds like it is looping so watch carefully and when you see it looping hit "crtl+c" to stop logcat.
Do this! download this to you sd card http://www.megaupload.com/?d=PXIYUNSY than boot into bottloader, let the phone search for the file update and this should get you up and running. The problem doing what you did is that that works when a different kernel not htc kernel.
good lookin out
evolishesh said:
Do this! download this to you sd card http://www.megaupload.com/?d=PXIYUNSY than boot into bottloader, let the phone search for the file update and this should get you up and running. The problem doing what you did is that that works when a different kernel not htc kernel.
Click to expand...
Click to collapse
What's the purpose of doing this? Just like a RUU, right?
yes! But this should give you all that you are looking for, is much easier.trust me!
You will not Loose Root.
You lucky son of a gun, my old evo wouldn't even not into recovery. Just bootloader. After stressing out for hours trying to fix it I finally got a replacement
The same thing happened to me and your link worked like a charm. I was just wondering if after I did this would I still be able to try and flash a different rom? or am I stuck with this one? I am just wondering....as you can see Im pretty new to the rooting game.
Basically, if you update your radios, you have to also update your rom to 3.70 build otherwise the phone won't get pass the bootanimation screen. Normally, you would update the rom then update the radios. Also, to nandroid or flash back to 3.30 build, you have to downgrade the radios back to the version used for 3.30. I was stuck on bootloop with new radios if I flashed any rom below 3.70, but downgrading the radios to previous version allowed for 3.30 nandroid restores.
Ok thank you a bunch for the info!! you were a life saver lol
Same Questions
Ok so I did what you said above and loaded that file onto sd card and went into bootloader if worked and i managed to get into recovery and flashed fresh and got the phone booted all way but I want Warm two point two so i flashed that version 4 and it wont go past the white HTC screen what can I do
I had a nightly running perfectly so decided to back it up in Rom Manager. After backing up it got stuck in booting loop. Couldn't get anything to work in recovery so ended up flashing a stock ROM in hboot (still with root). Now trying to install RC3 but get an error in recovery.
CM report log's last entry says:
line1: unexpected character at 'u'
Syntax error in update script
Any ideas? I'd like to be able to restore one of my older backups (a sense rom) if possible.
mtown_cyclone said:
I had a nightly running perfectly so decided to back it up in Rom Manager. After backing up it got stuck in booting loop. Couldn't get anything to work in recovery so ended up flashing a stock ROM in hboot (still with root). Now trying to install RC3 but get an error in recovery.
CM report log's last entry says:
line1: unexpected character at 'u'
Syntax error in update script
Any ideas? I'd like to be able to restore one of my older backups (a sense rom) if possible.
Click to expand...
Click to collapse
Try flashing CW manually and restoring your previous nandroid manually as well
Hope this helps
I always flash using Clockwork. I use Rom Manager to get the ROM but I perform the actual flash in Clockwork. You'll have fewer issues if you do.
Thanks for the replies. I rolled-back to an earlier version of ClockworkMod, then reflashed CyanogenMod. That worked. Not sure what happened to start this because I was just trying to do a backup. I did have SetCPU installed and overclocked so maybe that had something to do with it.
mtown_cyclone said:
Thanks for the replies. I rolled-back to an earlier version of ClockworkMod, then reflashed CyanogenMod. That worked. Not sure what happened to start this because I was just trying to do a backup. I did have SetCPU installed and overclocked so maybe that had something to do with it.
Click to expand...
Click to collapse
Which version of CWM are you using now, I'm thinking about going to 3.0.0.7 from 3.0.0.8
KB3MMX said:
Which version of CWM are you using now, I'm thinking about going to 3.0.0.7 from 3.0.0.8
Click to expand...
Click to collapse
I went to 3.0.0.7 but I'm back to 3.0.0.8 now. And just flashed RC4. Working great so far. Very fast.
As long as you fixed your problem, we're good, right? Also, try RA if you're having too many problems with CWM
Sent from my Magnolia Incredible
drk.hd said:
As long as you fixed your problem, we're good, right? Also, try RA if you're having too many problems with CWM
Sent from my Magnolia Incredible
Click to expand...
Click to collapse
Yep, all good.
I nandroid to a sense rom and updated prl. Nandroid back to CM7 and then flashed Tiamat's latest kernel and Viperboy's aosp battery mod. Rom went into boot loop. I took out battery and went to recovery (using Amon-RA). However, in recovery, nothing shows up. I get a blank screen with just the build number of the recovery at the bottom of the screen.
Now my phone is useless and I need it as I am in clinical rotations in Akron and away from home. This is my only source for communication.
EDIT: I know this is the general section, but no one visits the Q/A section and I need immediate help.
jblazea50 said:
I nandroid to a sense rom and updated prl. Nandroid back to CM7 and then flashed Tiamat's latest kernel and Viperboy's aosp battery mod. Rom went into boot loop. I took out battery and went to recovery (using Amon-RA). However, in recovery, nothing shows up. I get a blank screen with just the build number of the recovery at the bottom of the screen.
Now my phone is useless and I need it as I am in clinical rotations in Akron and away from home. This is my only source for communication.
EDIT: I know this is the general section, but no one visits the Q/A section and I need immediate help.
Click to expand...
Click to collapse
Well if it were bricked it wouldnt even turn on so your ok. When u boot into recovery, let it sit for a minute. I've had this issue while on sense based roms. When I boot into recovey it takes a minute for the menu to actually show up. It's just black screen with the version of amon at the bottom. Don't know why it happens but give it a few minutes and see if it eventually shows up.
jblazea50 said:
I nandroid to a sense rom and updated prl. Nandroid back to CM7 and then flashed Tiamat's latest kernel and Viperboy's aosp battery mod. Rom went into boot loop. I took out battery and went to recovery (using Amon-RA). However, in recovery, nothing shows up. I get a blank screen with just the build number of the recovery at the bottom of the screen.
Now my phone is useless and I need it as I am in clinical rotations in Akron and away from home. This is my only source for communication.
EDIT: I know this is the general section, but no one visits the Q/A section and I need immediate help.
Click to expand...
Click to collapse
Is S-On in the bootloader? If not, reflash the recovery from the bootloader.
I flashed Amon 2.3 from 2.1 and that didn't help. Now I did PC36IMG.zip to stock, unrooted and it seems to work. I will root now.
jblazea50 said:
I flashed Amon 2.3 from 2.1 and that didn't help. Now I did PC36IMG.zip to stock, unrooted and it seems to work. I will root now.
Click to expand...
Click to collapse
I think you flashed the recovery image wrong lol. How are you rooting?
It wasn't flashed wrong because the version number changed from 2.1 to 2.3. When I originally rooted, it was during launch time. I'm using unrevoked now and everything is going smooth. I'm nandroiding back to CM7.
jblazea50 said:
I nandroid to a sense rom and updated prl. Nandroid back to CM7 and then flashed Tiamat's latest kernel and Viperboy's aosp battery mod. Rom went into boot loop. I took out battery and went to recovery (using Amon-RA). However, in recovery, nothing shows up. I get a blank screen with just the build number of the recovery at the bottom of the screen.
Now my phone is useless and I need it as I am in clinical rotations in Akron and away from home. This is my only source for communication.
EDIT: I know this is the general section, but no one visits the Q/A section and I need immediate help.
Click to expand...
Click to collapse
Go to www.shipped-roms.com and go to the SUPERSONIC section....choose an RUU to download....I recommend the newest one, unless you have a special reason for something different.....
run the RUU on your PC, (meaning not in your boot loader recovery, or from your SD card.)
If you have a mac...it will take extra steps....but is doable.
You should be able to flash with an RUU and get back to normal...afterwards, head over to www.unrevoked.com and re-root your phone...
jblazea50 said:
It wasn't flashed wrong because the version number changed from 2.1 to 2.3. When I originally rooted, it was during launch time. I'm using unrevoked now and everything is going smooth. I'm nandroiding back to CM7.
Click to expand...
Click to collapse
okay unrevoked is the best way to do it.
i've seen issues with CM7 losing root... I think it has more to do with ROM Manager and flashing the recovery image wrong. I've actually had it happen. I am working on an app to flash recoveries/roms, and it was working fine, but then i flashed clockwork recovery from rom manager and it turned security back on, disabled usb, and disabled sd... lol.
Thanks for all your help. I appreciate it. I am still not sure what caused the problem, but I went to stock, unrooted and now I'm back rooted and nandroid back to CM7. All is working fine at the moment.
derekwilkinson said:
okay unrevoked is the best way to do it.
i've seen issues with CM7 losing root... I think it has more to do with ROM Manager and flashing the recovery image wrong. I've actually had it happen. I am working on an app to flash recoveries/roms, and it was working fine, but then i flashed clockwork recovery from rom manager and it turned security back on, disabled usb, and disabled sd... lol.
Click to expand...
Click to collapse
Yup, unrevoked is super easy to do. My second time using it (1st time I did my dad's Evo after I unrooted to take it to Sprint store).
jblazea50 said:
Thanks for all your help. I appreciate it. I am still not sure what caused the problem, but I went to stock, unrooted and now I'm back rooted and nandroid back to CM7. All is working fine at the moment.
Click to expand...
Click to collapse
Great to hear
have fun!
I've lost recovery twice on this phone. Not a big deal to just reflash it. Glad you got it working
I successfully rooted my phone a few days ago using the Revolutionary method and flashed ClockworkMod Recovery without a problem. Then I flashed CyanogenMod 7.1.0 again without a problem. I noticed my gps has been having an issue detecting my location so I figured I should flash the nandroid for my stock rooted android 2.3.3 rom and see if the issue still exists. My main problem is that I can't boot into recovery. Apparently I have the latest version of Clockwork. I try to boot into recovery using different methods and I keep ending up at the white screen that says 'Revolutionary' in pink at the top with the 3 skateboarding androids at the bottom. I try to get to recovery from that screen also still with no success. It just reboots into that screen. I was thinking I may have to use the ruu to unroot my Evo (I rather find an alternative solution). How can I regain my ability to boot into recovery? Any help would be much appreciated...
__________________
HTC Evo 4G
CyanogenMod 7.1.0
ClockworkMod 5.0.2.2
If grab the pc36img for amon_ra, throw it in the root of your SD, using a card reader in a computer, get into hboot and let it install. Then try to get into recovery. F clockwork anyway.....90% of the peeps around here having problems are running that recovery
DoubleA319 said:
I successfully rooted my phone a few days ago using the Revolutionary method and flashed ClockworkMod Recovery without a problem. Then I flashed CyanogenMod 7.1.0 again without a problem. I noticed my gps has been having an issue detecting my location so I figured I should flash the nandroid for my stock rooted android 2.3.3 rom and see if the issue still exists. My main problem is that I can't boot into recovery. Apparently I have the latest version of Clockwork. I try to boot into recovery using different methods and I keep ending up at the white screen that says 'Revolutionary' in pink at the top with the 3 skateboarding androids at the bottom. I try to get to recovery from that screen also still with no success. It just reboots into that screen. I was thinking I may have to use the ruu to unroot my Evo (I rather find an alternative solution). How can I regain my ability to boot into recovery? Any help would be much appreciated...
__________________
HTC Evo 4G
CyanogenMod 7.1.0
ClockworkMod 5.0.2.2
Click to expand...
Click to collapse
Turn off your phone,then when turning it on hold the volume rocker in the down position,you will then boot into hboot settings,hboot will automatically check for the update file(PC36IMG)after its done,scroll to recovery and enter that way,if you still cant get into recovery,you will need to download and reinstall the latest revolutionary root tool,i recommend using "TeamWin Recovery Project" i've never had a problem with it.
Just to let you know, guys, TWRP v2 is out! I'll post the link to Amon Ra. You can find the link to TWRP 2 in my sig.
http://forum.xda-developers.com/showthread.php?t=1339654
Thanks for the answers. I'll reply again when I get a chance to put the advice to use
Sent from my PC36100 using XDA App
Lacedaemon said:
Just to let you know, guys, TWRP v2 is out! I'll post the link to Amon Ra. You can find the link to TWRP 2 in my sig.
http://forum.xda-developers.com/showthread.php?t=1339654
Click to expand...
Click to collapse
I was actually going to go the amon ra route because i was familiar with it while I had a HTC Hero. But TWRP v2 caught my attention and I decided to go that route. So far so good as far as I can tell. I made a nandroid backup. Thanks. Any tips or info I should know about using TWRP?
And 1 more thing. I have a nandroid backup from when I had clockwork recovery. I should still be able to flash that back up right?
DoubleA319 said:
I was actually going to go the amon ra route because i was familiar with it while I had a HTC Hero. But TWRP v2 caught my attention and I decided to go that route. So far so good as far as I can tell. I made a nandroid backup. Thanks. Any tips or info I should know about using TWRP?
And 1 more thing. I have a nandroid backup from when I had clockwork recovery. I should still be able to flash that back up right?
Click to expand...
Click to collapse
Nope you can't flash your CWM backup since your on TWRP. You would have to flash back to the version of CWM that you made the backup with
Sent from my PC36100 using XDA App
Man that sucks. I need to be able to access that particular nandroid. Thats my stock backup right after I rooted my phone. Ok so I can flash back to clockwork, restore my nandroid, then go back to TWRP and make a backup compatible with TWRP?
DoubleA319 said:
Man that sucks. I need to be able to access that particular nandroid. Thats my stock backup right after I rooted my phone. Ok so I can flash back to clockwork, restore my nandroid, then go back to TWRP and make a backup compatible with TWRP?
Click to expand...
Click to collapse
Yup
Sent from my PC36100 using XDA App
How can I figure out the version though? clockwork installed on my phone right after I rooted my phone via the revolutionary method. I did this about 2 weeks ago. Im guessing i have to go through rom manager, but this was part of the issue to begin with
DoubleA319 said:
How can I figure out the version though? clockwork installed on my phone right after I rooted my phone via the revolutionary method. I did this about 2 weeks ago. And where can I get clockwork from?
Click to expand...
Click to collapse
Clockworkmod.com . Also I believe revolutionary gives you the latest version so just flash the latest CWM for the evo4g
Sent from my PC36100 using XDA App
some how after flashing twrp then going back to cwm via rom manager, cwm seems to be working now
DoubleA319 said:
How can I figure out the version though? clockwork installed on my phone right after I rooted my phone via the revolutionary method. I did this about 2 weeks ago. Im guessing i have to go through rom manager, but this was part of the issue to begin with
Click to expand...
Click to collapse
I installed a new recovery after i installed revolution,because i also had recovery issues.The version should be at the top of the recovery screen.I didnt like rom manager too much,for some reason it gives me problems.
They say that this version of Amon can be used to restore clockwork backups. I haven't tried it with clockwork myself because I avoids clockworkmod.
Thanks for the help everyone. Everything is gravy now. I'm happy with TWRP. I do have a question for making a backup. By default in TWRP, the 1st 3 boxes are checked up for when attempting to make a backup. Do any of you guys ever check the other boxes (Recovery, cache, .android_secure) and if so, why? Also, when you attempt to wipe before restoring, which items do you guys wipe? Any other tips or suggestions about this recovery would appreciated too.
I backup everything except cache.
By no means am I new to this so I'm at a loss. Any help would be greatly appreciated. I've flashed pretty much everything on my hero and now on the evo but I always go back to CM. About a week ago I wanted to flash the latest CM nightly so I booted into recovery to make a nandroid. It was taking way too long (almost 20 minutes) so I pulled the battery, rebooted to recovery, plugged in the usb cable, and mounted the phone to find out I had a 3.8gb backup. I deleted it, unmounted, screamed, wiped everything, and tried to flash the nightly. Nothing but splash screen. Booted into recovery, wiped all, flashed MikG. Good to go. Recovery, wipe, nightly. Nothing. Recovery, wipe, Evo Classic. Good to go. Anything CM. Nothing. I tried every combination of wiping, powering down, rebooting to recovery, flashing different recoveries (started with RA style, went to CWM, RA 2.3), tried flashing with the Mason kernel. I had to nandroid back to an older unofficial CM7 nightly backup. This has never happened to me before. I can flash Sense but I can't flash CM to save my life. I'm a little worried with Deck Reloaded coming out that it'll be a no go for me. Haven't tried Deck 1.3d yet so not sure if it's CM specific or AOSP ROMs. Anyone have any suggestions? Thanks.
Sent from my PC36100 using xda premium
I reached out to ropodope and he hit it on the head. He told me that I had corrupted one of my main partitions. His solution was to RUU back to unrooted stock to repartition and format every one of the partitions like when I first got the phone. It did the trick. It wasn't bad because I was S-OFF. I flashed an old RUU PC36IMG from HBOOT, booted and updated everything while stock, flashed Smelkus 4.2 PC36IMG from HBOOT, nandroided, wiped, flashed CM, and I was good to go again. No need to re-root thanks to S-OFF. I wanted to share this in case anyone else runs into this problem.
Sent from my PC36100 using xda premium