Related
Hi - I've got a rooted AMOLED Incredible.
Yesterday, it went into a bootloop. I could get to HBoot but could not get into recovery. I tried flashing multiple other recoveries but still could not get into it from HBoot (it would go into a bootloop every time I chose "Recovery" from HBoot).
Today, I installed an RUU from this post: http://forum.xda-developers.com/showpost.php?p=11717873&postcount=2
It updated, and then when I rebooted, it went into the same bootloop, this time with the stock splash screen.
I have HBoot 0.92, Radio 7.28. I'm S-off. I've formatted my SD card, and it's FAT32.
Anyone have any idea what's going on?
Thanks in advance!
-jaba
Is setcpu installed, and overclocking way high on boot? If setcpu is installed, you s/b able to mount device in adb and remove it.
Sent from my ADR6300 using XDA Premium App
smtom said:
Is setcpu installed, and overclocking way high on boot? If setcpu is installed, you s/b able to mount device in adb and remove it.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
no setCPU installed.
Can you dl another ROM like Virtuous and put it on sd, then flash it?
Have you tried another sd?
Sent from my ADR6300 using XDA Premium App
smtom said:
Can you dl another ROM like Virtuous and put it on sd, then flash it?
Have you tried another sd?
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
I can't get into recovery with bootlooping.
I'll try another SD card.
Basically at this point I'd be happy to get the phone to S-On so that I can take it back to Verizon. Unfortunately, I don't know how to do that as I can't access Recovery without going into a bootloop. I've tried to flash other recoveries and they all put me into a bootloop.
Anyone with any thoughts on how to get s-on without recovery?
Thanks!
I would say flash a bp31img through hboot. That should put you s-on i believe. If you cannot find a pb31img ill come back latter with a link for dl. The pb31img should put you completely stock. The image i have though is from the first shippments of 2.1 but its still stock.
Sent from my Incredible using Tapatalk
linuxmotion said:
I would say flash a bp31img through hboot. That should put you s-on i believe. If you cannot find a pb31img ill come back latter with a link for dl. The pb31img should put you completely stock. The image i have though is from the first shippments of 2.1 but its still stock.
Sent from my Incredible using Tapatalk
Click to expand...
Click to collapse
I tried that and it didn't work. Thanks, though.
I took the phone to verizon and they are sending me a new one.
Any solution to this?
To get s-on you need to be able to access recovery. Also what rom were you on when the phone messed up, was it cm7?
cmlusco said:
To get s-on you need to be able to access recovery. Also what rom were you on when the phone messed up, was it cm7?
Click to expand...
Click to collapse
I was on SR 4.2 but I figured it out. The first time I RUU'd the phone was shaking all over the place so I think that just ****ed it up. I reflashed the RUU and it's good to go. I decided I am just going to sell it to my buddy as a stock unrooted with S-OFF, screw it.
Thanks though.
REYES702 said:
I was on SR 4.2 but I figured it out. The first time I RUU'd the phone was shaking all over the place so I think that just ****ed it up. I reflashed the RUU and it's good to go. I decided I am just going to sell it to my buddy as a stock unrooted with S-OFF, screw it.
Thanks though.
Click to expand...
Click to collapse
Don't give up hope just now to S-ON. Have you read the below page for getting S-ON?
http://unrevoked.com/rootwiki/doku.php/public/forever
It should work with stock recovery as long as you're on one of the listed radios.
Get the unrevoked-forever-son.zip and follow instructions for unrevoked-forever.zip, renaming to update.zip
Quick question, I RUU'd back to Froyo so can he still receive the OTA with S-OFF? Or does it need to be S-ON?
REYES702 said:
Quick question, I RUU'd back to Froyo so can he still receive the OTA with S-OFF? Or does it need to be S-ON?
Click to expand...
Click to collapse
It can be s-off but everything else must be stock, including recovery and having all original apps. Since its s-off rooting after the ota is no problem if desired.
I had an issue with my phone a couple of weeks ago where I'm only able to the bootloader screen and the fastboot screen. Fortunately, I got a replacement EVO 3 days later but I'm still trying to get my old phone up and running. But after trying everything I can find, still nothing.
So my question is, when do I say that the phone is officially bricked?
Sent from my PC36100 using Tapatalk
If you can get to the bootloader screen, then you be able to flash an image to get you phone working again.
Sent from my Decked Out HTC EVO with Tapatalk!
dwelder said:
If you can get to the bootloader screen, then you be able to flash an image to get you phone working again.
Sent from my Decked Out HTC EVO with Tapatalk!
Click to expand...
Click to collapse
Believe me, I've tried everything, from using amon ra PC36IMG.zip in the bootloader. It updates successfully then still no recovery.
I've tried the ruu via bootloader, it updates successfully. It still bootloops continually.
I ran Football's recent 4.54 ruu in fastboot successfully and still nothing.
Everything I try, it continues to bootloop.
Sent from my PC36100 using Tapatalk
Were you using CM7 before your phone started bootlooping?
Concordium said:
Were you using CM7 before your phone started bootlooping?
Click to expand...
Click to collapse
10/14 miui with tiamat 4.1 sbc.
Sent from my PC36100 using Tapatalk
andygu3 said:
10/14 miui with tiamat 4.1 sbc.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well CM7 is the ROM typically being run when phones enter the bootloop of death. However, I've heard that there have been a couple of MIUI ROMs that have entered the bootloop of death as well. If you've flash a recovery and still cant enter it and tried to fully unroot then you might have to take it to Sprint. I'd make sure that you're fully unrooted before doing so. I would also recommend removing your SD card so that they cant try to deny you based on rooting the phone. Just a precaution.
andygu3 said:
Believe me, I've tried everything, from using amon ra PC36IMG.zip in the bootloader. It updates successfully then still no recovery.
I've tried the ruu via bootloader, it updates successfully. It still bootloops continually.
I ran Football's recent 4.54 ruu in fastboot successfully and still nothing.
Everything I try, it continues to bootloop.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Have you tried flashing the images via fastboot?
Concordium said:
Well CM7 is the ROM typically being run when phones enter the bootloop of death. However, I've heard that there have been a couple of MIUI ROMs that have entered the bootloop of death as well. If you've flash a recovery and still cant enter it and tried to fully unroot then you might have to take it to Sprint. I'd make sure that you're fully unrooted before doing so. I would also recommend removing your SD card so that they cant try to deny you based on rooting the phone. Just a precaution.
Click to expand...
Click to collapse
Fortunately, I already got a new phone but the reason I didn't take it into Sprint was because it still was S-off. Since I can't get to recovery, how would I get s-on?
And now that I ran stock ruu's, is it a possibility that the PC36IMG.zip's won't be recognized anymore?
I'd love to get this phone running again and let my 7 year play some games on it but I'm afraid I may be sol!!
Sent from my PC36100 using Tapatalk
teh roxxorz said:
Have you tried flashing the images via fastboot?
Click to expand...
Click to collapse
Please elaborate! Not sure what to flash in fastboot?
Sent from my PC36100 using Tapatalk
andygu3 said:
Please elaborate! Not sure what to flash in fastboot?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
andygu3 said:
Fortunately, I already got a new phone but the reason I didn't take it into Sprint was because it still was S-off. Since I can't get to recovery, how would I get s-on?
And now that I ran stock ruu's, is it a possibility that the PC36IMG.zip's won't be recognized anymore?
I'd love to get this phone running again and let my 7 year play some games on it but I'm afraid I may be sol!!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
teh roxxorz said:
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
Click to expand...
Click to collapse
Thanks for the info! I will give this a go.
I keep reading that the NV got corrupted some how, is there any way to correct this or flash something in fastboot?
Again thanks for your input, much appreciated!
Sent from my PC36100 using Tapatalk
andygu3 said:
Thanks for the info! I will give this a go.
I keep reading that the NV got corrupted some how, is there any way to correct this or flash something in fastboot?
Again thanks for your input, much appreciated!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
No problem.
And if the NV is corrupted, its toast. It was a flaw with the evo when you bought it, and now its decide to tap out. At that point you'd have to take it to sprint, as the NV is part of flash memory and its locked.
Concordium said:
Here you go
http://forum.xda-developers.com/showpost.php?p=18399552&postcount=2
Click to expand...
Click to collapse
Thanks for this, hopefully if I can't get the boot.img working from ruu, I will do this!
Sent from my PC36100 using Tapatalk
andygu3 said:
Thanks for this, hopefully if I can't get the boot.img working from ruu, I will do this!
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Oh crap I forgot you were the one having the issue with the boot.img. If you can't get that to work then the post I gave you will most likely not work either. It's worth a try....but I doubt it.
teh roxxorz said:
No problem.
And if the NV is corrupted, its toast. It was a flaw with the evo when you bought it, and now its decide to tap out. At that point you'd have to take it to sprint, as the NV is part of flash memory and its locked.
Click to expand...
Click to collapse
Well sh**, that's a downer! If this is the case, I'm definitely sol! But hopefully I can get something out of the phone but I seriously doubt it!
Thanks guys for your input, again much appreciated. I will report back if I have any breakthrough!!
Sent from my PC36100 using Tapatalk
Im having the same issue
bootloop and the phone was using CM7. I was able to get to boot loader menu but can not get to recovery.
Tried to add recovery image no dice...now the phone will only charge and not boot
teh roxxorz said:
Well you said you tried flashing via PC36IMG, and it 'worked' but it didn't stick, i.e it didn't 'work'. What you can do is extract the boot.img from the rom / ruu, place it in your adb tools folder. Then boot the phone to the bootloader, select fastboot, connect to your pc via usb cable, open up command prompt, navigate to you adb tools folder and type:
fastboot flash boot boot.img
fastboot reboot
That will flash the boot image to the correct partition, then reboot the phone, and see if it boots up.
Click to expand...
Click to collapse
No luck!
I know someone posted the EVO Brick_fix, I believe cutthroat but since no PC36IMG.ZIP is being recognized on my sdcard. I may officially say my phone is toast.
Any other suggestions are welcome!
Sent from my PC36100 using Tapatalk
Is this normal? I can run any stock ruu and my hboot changes! I was on 2.16 but I ran the froyo ruu and now I'm back to 2.10
Any thoughts?
Sent from my PC36100 using Tapatalk
andygu3 said:
Is this normal? I can run any stock ruu and my hboot changes! I was on 2.16 but I ran the froyo ruu and now I'm back to 2.10
Any thoughts?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Did you unbrick your EVO
I tried to use unbrick method and now phone will not boot at all
It just stays at black screen and vibrates once after pressing the power button
Tittle says everything.
I've researched about it for an hour or so now..and the answer I came up with is to get this thing for the SD card, hook up on my laptop, and get sock stock image or something like that.
May anyone help me? I really need help.
xCr4zYxKiiDx said:
Tittle says everything.
I've researched about it for an hour or so now..and the answer I came up with is to get this thing for the SD card, hook up on my laptop, and get sock stock image or something like that.
May anyone help me? I really need help.
Click to expand...
Click to collapse
What were you doing before this happened ?
Sent from my PC36100 using XDA App
What Rom were you running? Were you trying to flash something, and then it wouldn't boot, or just started to hang on a restart? Are you rooted? Is your phone s-off?
evo4gnoob said:
What were you doing before this happened ?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Attempting to root it w/ Revolutionary.
What Rom were you running? Were you trying to flash something, and then it wouldn't boot, or just started to hang on a restart? Are you rooted? Is your phone s-off?
Click to expand...
Click to collapse
ROM? I just used Revolutionary and forgot PC30 something like that I was using. My phone is S-OFF and at first it gave me an error the triangle thing and then I restarted it I ended up having the HTC EVO 4G boot screen.
xCr4zYxKiiDx said:
Attempting to root it w/ Revolutionary.
ROM? I just used Revolutionary and forgot PC30 something like that I was using. My phone is S-OFF and at first it gave me an error the triangle thing and then I restarted it I ended up having the HTC EVO 4G boot screen.
Click to expand...
Click to collapse
You don't have a recovery can someone post the amon RA recovery for me I'm on my phones
Sent from my PC36100 using XDA App
evo4gnoob said:
You don't have a recovery can someone post the amon RA recovery for me I'm on my phones
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Can you tell me so I should search for it?
xCr4zYxKiiDx said:
Can you tell me so I should search for it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=705026 download the PC36IMG.zip and put it on the root of your sd card(not in any folders).Power off the phone hold down the power button and volume down it will scan for it and will say there is a update accept it and you should have a recovery after it reboots
evo4gnoob said:
http://forum.xda-developers.com/showthread.php?t=705026 download the PC36IMG.zip and put it on the root of your sd card(not in any folders).Power off the phone hold down the power button and volume down it will scan for it and will say there is a update accept it and you should have a recovery after it reboots
Click to expand...
Click to collapse
Sorry to be a bothersome but I can't go on put the file in the root of my SD card since it doesn't allows me to. The only thing I can do is hold the power button and press down and still I can't go in the USB drive in my laptop.
xCr4zYxKiiDx said:
Sorry to be a bothersome but I can't go on put the file in the root of my SD card since it doesn't allows me to. The only thing I can do is hold the power button and press down and still I can't go in the USB drive in my laptop.
Click to expand...
Click to collapse
how long did you wait till till you decide it was stuck on the evo 4g screen?
What part of the process were you at trying to root with revolutionary when you go stuck on the HTC evolution screen ?
Sent from my PC36100 using XDA App
evo4gnoob said:
how long did you wait till till you decide it was stuck on the evo 4g screen?
Click to expand...
Click to collapse
Right after of the 'update'
evo4gnoob said:
What part of the process were you at trying to root with revolutionary when you go stuck on the HTC evolution screen ?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Right after when the update finished it gave me that error code with the triangle and I took the battery off, reboot it, and it gave me the HTC Evo 4G screen.
Quick Suggestion: Use Amon Ra 3.08 instead of Amon Ra 2.3.
Lacedaemon said:
Quick Suggestion: Use Amon Ra 3.08 instead of Amon Ra 2.3.
Click to expand...
Click to collapse
His download link doesn't work. :c
xCr4zYxKiiDx said:
Right after of the 'update'
Right after when the update finished it gave me that error code with the triangle and I took the battery off, reboot it, and it gave me the HTC Evo 4G screen.
Click to expand...
Click to collapse
What update ?did revolutionary give you a option to install clockworkmod recovery?did you use a guide off of here to root it?
Sent from my PC36100 using XDA App
evo4gnoob said:
What update ?did revolutionary give you a option to install clockworkmod recovery?did you use a guide off of here to root it?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yeah, and after the thing I had to click yes on my phone to update till I ran across this one which said ''PU-FAIL'' or something like that.
xCr4zYxKiiDx said:
His download link doesn't work. :c
Click to expand...
Click to collapse
*sigh* Here you go: http://www.mediafire.com/?ivfpk948a5bkrc2
Hey guys, my phone runs MIUI and Tiamat. Every time I would hold down the power button to select recovery, it would go into hboot. And if I tried going into recovery from hboot it would just go back into hboot.
I downloaded clockworkmod rom manager and tried getting into recovery from there and still no go.
What am I doing wrong?
Sent from my PC36100 using Tapatalk
You have fastboot enabled it sounds like
We are legion, for we are many.
YouThere said:
Hey guys, my phone runs MIUI and Tiamat. Every time I would hold down the power button to select recovery, it would go into hboot. And if I tried going into recovery from hboot it would just go back into hboot.
I downloaded clockworkmod rom manager and tried getting into recovery from there and still no go.
What am I doing wrong?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Yup,what evil said above me,go to settings/applications/developement at the bottom you will see fastboot,uncheck it.
Add in, uninstall ROM Manager, and flash Amon Ra for your recovery
Agree with Hip Kat
Sent from my PC36100 using Tapatalk
Diablo67 said:
Yup,what evil said above me,go to settings/applications/developement at the bottom you will see fastboot,uncheck it.
Click to expand...
Click to collapse
I don't see it. Perhaps you could give me a screenshot or something?
Sent from my PC36100 using Tapatalk
YouThere said:
I don't see it. Perhaps you could give me a screenshot or something?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Have you tried reflashing your recovery?
Sent from my PC36100 using xda app
The way they suggested to disable fastboot is for a stock system. I don't know if you can disable it that way with MIUI. I know you can't do it that way with CM7, which is similar to MIUI.
Do a battery pull, boot into bootloader, then try to go into your recovery from there.
Oh, and get rid of CWM. Flash AmonRa to your phone instead.
I encountered this today. Reflash recovery and then use rom manager to reboot into recovery.
Sent from my Sensation using xda premium
I went into clockworkmod and reflashed recovery. It's still not doing anything right.
Sent from my PC36100 using Tapatalk
OMG. STOP USING CLOCKWORK MOD! You have to flash Amon Ra, in Hboot. Click the link in my signature, follow my guide. Links are there, too
HipKat said:
OMG. STOP USING CLOCKWORK MOD! You have to flash Amon Ra, in Hboot. Click the link in my signature, follow my guide. Links are there, too
Click to expand...
Click to collapse
Oh man I miss Ra recovery! Is link to engineering hboot there too?
Sent from my Sensation using xda premium
It's not, but that's a good one to add!
If you are still using clockworkMOD recovery, flash an older version (5.0.2.0). I had issues with the latest version not going to recovery.
Hey OP use this http://forum.xda-developers.com/showthread.php?t=1339654 it'll solve your problem...
bbishop02 said:
If you are still using clockworkMOD recovery, flash an older version (5.0.2.0). I had issues with the latest version not going to recovery.
Click to expand...
Click to collapse
This worked for me. Thanks
Clockworkmod is bad pretty sure it contributed to bricking my og droid I miss that thing sometimes great device
HipKat said:
OMG. STOP USING CLOCKWORK MOD! You have to flash Amon Ra, in Hboot. Click the link in my signature, follow my guide. Links are there, too
Click to expand...
Click to collapse
HipKat I love you so much for your guide.
Thank you to everyone who took their time posting.
Sorry for bump, very sorry. I had two threads open - one for the ROM what I was going to post a question for, and this thread because it's similar to my problem. I posted a Loooooong post in here by accident, and am trying to move it to the other thread. sorry for bump
Found another solution
Hey guys,
thank your for all your suggestions and sorry I forgot about this thread as I solved my prob weeks ago.
I just flashed TWRP and had to continue to hold the volume up button after the logo and boot a second time into recovery.
I flashed Cyanogenmod and now everything works just fine.
Thanks again.
okay, first off im gonna start out saying i am a samsung user and know nothing about htc. my buddy got an evo 4g for free and he wants me to root and install a rom, so i figured out i need s-on but have no idea how to do it. i tried the revolutionary thing but i entered the beta code and it always says invalid. please help! how do i do this?
Check your Hboot version first, if you haven't already done so. You can check the version by going into the bootloader (volume down+power). If it's 2.18 you'll have to use the Htcdev method to unlock the bootloader, install a custom recovery and root the phone. Revolutionary won't work with the newest Hboot. Incidentally, you don't have to have S-OFF to install a ROM or flash kernels, for that matter. So long as the bootloader is unlocked and the phone is rooted with a custom recovery, you're good to go.
Sent from my PC36100
Its like 2.16.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
spitfire2425 said:
Its like 2.16.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
For that h boot u can use revolutionary. First u need to install drivers ,make sure u check on usb debugging and unknown sources When u enter beta key make sure its entered correctly it is case sensitive from my PC36100 using xda premium
I found it worked much better just to copy the beta key and then paste it once prompted to enter it. It seems like a lot of people were getting errors trying to manually type the key in, but hey, if it works, it works
Sent from my PC36100
FinZ28 said:
I found it worked much better just to copy the beta key and then paste it once prompted to enter it. It seems like a lot of people were getting errors trying to manually type the key in, but hey, if it works, it works
Sent from my PC36100
Click to expand...
Click to collapse
ive tried that many times, it just wouldnt work.
spitfire2425 said:
ive tried that many times, it just wouldnt work.
Click to expand...
Click to collapse
Weird. Worked for me when I rooted my last EVO, no problem whatsoever.
Sent from my PC36100
FinZ28 said:
Weird. Worked for me when I rooted my last EVO, no problem whatsoever.
Sent from my PC36100
Click to expand...
Click to collapse
everytime i try it it says invalid beta key even when i copy and paste
spitfire2425 said:
everytime i try it it says invalid beta key even when i copy and paste
Click to expand...
Click to collapse
Okay, dumb question. When you entered the serial number of the phone to get the key, did you make sure you didn't use O for 0 (zero)? Not sure that could be part of the issue but worth looking at. I honestly can't think of anything else at this point. I remember when Revolutionary first came out last year, people were having a lot of issues with getting the beta key accepted. I for one didn't have this issue so I'm at a loss at this point.
Sent from my PC36100
I got it all worked out.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
spitfire2425 said:
I got it all worked out.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
What ended up being the problem?
Sent from my PC36100
ok so i check for the boot loader version then what? i then install a custom made one from my computer? then i make a backup onto my sd card or comp? i have titanium but it says i need to be rooted...also...when do i instal the kernal? and where the heck do i find this stuff?:banghead:
HTC EVO 4G PC36100 ~ XDA Premium
If I recall correctly, there is a su binary file that you have to flash from recovery once you've run Revolutionary. It's a zip file that's in the Revolutionary guide. Running the su binary is what actually gives you root. You'll need to make sure that you have the app Superuser or SuperSU installed, as it will actually give permission for root apps (such as Titanium Backup) to operate. As far as kernels and such, look under the development section there, as there is a ton of great info there
Also, once you get rooted, I'd suggest going into Recovery and making a full Nandroid backup, especially if you plan on flashing a ROM or kernel. It'll come in handy if you get in a tight spot down the road.
Sent from my PC36100
FinZ28 said:
What ended up being the problem?
Sent from my PC36100
Click to expand...
Click to collapse
I'm not sure what the problem was but I ended up updating to gb with 2.18 hboot then downgraded to android 2.2 then ran the unrevoked program then flashed a rom. Worked perfectly.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app