Develop Bugs

[Q] [HELP] Stuck in bootloader menu

I Rooted an evo that kept having the restart issue with revolutionary. I was able to unroot it, but now the origional rom will not load. everytime i restart the phone it goes to the bootloader screen. I can choose fastboot, recovery , simlock, or restart i believe. I just want to get it to load the original rom. I never put any custom roms or anything on. cus it got stuck so i decided to unroot hoping it would fix but still stuck. Any suggestions?

so are you still s-on?

ak074 said:
so are you still s-on?
Click to expand...
Click to collapse
I am s on now.
Bline's Iced Out Supersonic... If anyone helps you out click THANKS!!!

I fixed it and now an still booting to 4g screen and then rebooting it has to be a software issue but now i can atleast get insurance thanks

Phone restarts and won't turn on

For the past several months my phone would restart randomly when I used 3G, GPS or sometime just from heavy usage. It would turn off, boot to the white HTC screen but then the screen went black and it would vibrate 3 times and a led would blink. At that point the only way to turn it back on was to pull the battery and power on (although that usually didn't work until after a few tries or letting it sit for a while).
It has done this with both CM7.1 and decks 1.3 and with the Tiamat 3.3.7 & 4.1 kernels. I flashed Mason .14 on Tuesday hoping it might fix the problem. It did at first but after 24 hours it was back to restarting randomly, only this time it was worse. I was also getting a lot of force closes and it would restart even it was sitting unused. It would take hours until I could get it to successfully boot again. I attempted to do a full wipe and install CM7.2 yesterday only to find out I can not boot into recovery, attempting to do so causes the phone to turn off (I tried both through holding the power button and selecting recovery and through the bootloader).
As of right now my phone will not turn back on at all (going on 4 hours), I've had it successfully boot twice only to immediately turn off, other times it gets stuck on the white HTC screen.
I am still able to access the bootloader so I'm thinking my best option may be to place a PC36IMG.zip on my sdcard and see if I can't flash back to stock and then load CM7.2. My concerns are a) not sure if that will even work b) if the phone were to turn off in the middle of that would it completely brick my phone?
Sorry for the long post but I just wanted to provide as much info as possible. Any thoughts/suggestions would be greatly appreciated.

Can't boot into recovery? Have you tried reflashing your recovery? Get a PC36IMG file of your desired recovery (preferably amonRA, or drellisdee) and flash it thru bootloader. It only takes a second to flash, so I wouldn't be too worried about it shutting off while flashing it.
That's all I got.
Sent from my PC36100 using xda premium

scottspa74 said:
Can't boot into recovery? Have you tried reflashing your recovery? Get a PC36IMG file of your desired recovery (preferably amonRA, or drellisdee) and flash it thru bootloader. It only takes a second to flash, so I wouldn't be too worried about it shutting off while flashing it.
That's all I got.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Unfortunately that doesn't work. Flashes the recovery just fine but I still can't access it. I did manage to get my phone to boot into android after trying, not sure if that's a coincidence or not.
So I'm left with my original option, flashing a stock PC36IMG.zip. Also this might be a dumb question but can I rename anything PC36IMG.zip and flash? If so I could just rename Calkulin's format all, flash that and then repeat the process with CM7.2. Anyone know if this will work?
Edit: Should probably also ask if anyone knows what is causing this, is it a kernel issue?

Just a thought, maybe a bad battery or a bad usb?
Did you try the battery in another phone? Or, another battery in your phone?
Sounds like it may also be going for the reboot of death... If your recovery is corrupted and getting random reboots, maybe your internal storage is going bad...
Sent from my PC36100 using xda premium

imheroldman said:
Just a thought, maybe a bad battery or a bad usb?
Did you try the battery in another phone? Or, another battery in your phone?
Sounds like it may also be going for the reboot of death... If your recovery is corrupted and getting random reboots, maybe your internal storage is going bad...
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I was able to flash back to stock and it is still having similar problems. Turns off during any sort of data usage both 3g and Wifi. The fact that it has happened on multiple ROMs, multiple kernels, and multiple radios makes me think it is something hardware related. I guess I will talk to sprint and see what they can do.
BTW does anyone know of a method to flash an S-On zip file as a PC36IMG in the bootloader? I am still S-Off because I can't go into recovery to flash.

mcotter said:
BTW does anyone know of a method to flash an S-On zip file as a PC36IMG in the bootloader? I am still S-Off because I can't go into recovery to flash.
Click to expand...
Click to collapse
Well after going back to stock but still being S-Off I decided to try reflashing Amon_RA and I eventually got it to boot into recovery. It was similar to booting into the OS, I just had to pull the battery and wait 30+ mins before trying and then boot into bootloader and select recovery. It was a PITA since I needed flash a couple things but it worked. Got it back to S-On and took it to Sprint. Of course they didn't bother checking for any of that haha but I was able to get a replacement EVO.

[Q] Is my EVO Dead/Gone for good?

Hi Friends,
I did a lot of searching and tried a bunch of things, but I am not very successful. Can you experts please tell me if my EVO is dead/gone for good?
Symtoms:
My Evo was charging (it was rooted and S-Off), I took the charger cable off, and the phone rebooted.
It went to the White HTC Evo screen that comes before any ROM boots, and basically looped their infinitely.
Since then, the symptoms have switched back and forth from Bootloops on the white screen OR STUCK on the white screen, infinitely.
Currently, I am getting white screen boot loops
Things I have tried:
1. Cleared Storage (via Bootloader/Fastboot)
2. Chose "Recovery" from Bootloader/Fastboot (nothing happens, reboots and stuck on the white screen or loops)
3. Reverted back to S-ON
4. Flashed other Recovery zips
5. Upgraded the Fastboot version
6. Flashed the RUU
Current Situation:
Nothing changed guys... and after the RUU flash (out of which the Radio flash was the only component that FAILED) my PC31IMG.zip files are no longer being promoted for updates in my Fastboot/Bootloader menu.
While the reboots continue on the white screen...
Can't access Recovery
Can't run PC36IMG.zips anymore
Am I done here guys, or is there still anything I can do to save my EVO?
Appreciate ALL your help!

Man I have the same problem execept I'm not rooted or s off if you change the battery and let it sit for awhile off it will turn on but it will reboot in about 5 mintues then get stuck on the sprint 4g screen of the htc screen

Hey theneguy,
Thanks for your response... My phone was rooted, but is now S-On and Unrooted, I believe (I can't tell because I am not able to get in the OS).
I can't get into Recovery and my PC31IMG is not being read now...
Any ideas, friends?
theneguy said:
Man I have the same problem execept I'm not rooted or s off if you change the battery and let it sit for awhile off it will turn on but it will reboot in about 5 mintues then get stuck on the sprint 4g screen of the htc screen
Click to expand...
Click to collapse

same thing happened to my son, pulled sd card and it would boot fine, found and deleted a corrupt .img file on sd...all is fine

Latest Update guys:
I tried flashing the RUU via HBoot/Flashboot, and the update failed, but the progress bar at the screen was full/successful. The on-screen wizard tried to take me to the "Recovery" steps, nothing was fixed.
The computer wizard was stuck at: Sending Signature....
And the phone had the full progress bar from the previous flash.
So I yanked the battery out, cause I had no options left.
Well, needless to say, now, NOTHING turns on. The phone doesn't charge, and blah, blah, blah.
So guys, can someone give me a verdict... is my EVO done for good?
Thanks for your help.

I can't get in the recovery eather I tryed pulling the sd card out it is still doing the same thang

ProFragger said:
Hey theneguy,
Thanks for your response... My phone was rooted, but is now S-On and Unrooted, I believe (I can't tell because I am not able to get in the OS).
I can't get into Recovery and my PC31IMG is not being read now...
Any ideas, friends?
Click to expand...
Click to collapse
It should be PC36IMG not 31.
Sent from my PC36100 using Tapatalk 2

Thanks Mark,
But I don't think it matters anymore... I think with the battery pulled out after a failed RUU.exe installation has truly bricked my phone for good.
It doesn't charge, the battery was good, NOTHING lights up, and I just think it's game over...
MarkEv0 said:
It should be PC36IMG not 31.
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse

I think you're right...

Boot Loop - Help

Just got my HTC One M9 (Canadian on Bell today).
I go home to start getting all my apps and data back on and the phone reboots itself, half way through the reboot, it reboots all over again. This just keeps going on creating a massive bootloop.
I can get into flashboot mode. But none of the options in there seem to help.
I've tried flashing the RUU but am S-ON so that was no good.
I've tried everything I can think of and got nowhere.
Any help is greatly appreacited

Have you tried going into recovery and doing a factory reset?
Sent from my HTC One M9 using Tapatalk

The phone won't even boot into recovery. Just keeps boot looping when selecting that too.

AaronDC19 said:
The phone won't even boot into recovery. Just keeps boot looping when selecting that too.
Click to expand...
Click to collapse
if you have a costume recovery hold Volume UP and DOWN and POWER button at the same time, it should take you to the boot loader there boot to recovery

No custom recovery.
Phone is completely stock.

*deleted*

AaronDC19 said:
No custom recovery.
Phone is completely stock.
Click to expand...
Click to collapse
maybe the power button is stuck or something any updates?

Thought about that idea.
Brought it back to bell and traded it for another. No issues yet...

Pixel XL stuck in Boot Loop after PPP5 installed

My Pixel XL downloaded and installed PP5 yesterday, seemed to go okay. Initially, it would boot but spontaneously reboot after 1-2 minutes of run time. But it degraded and now it is stuck on a white screen with Google, and reboots before the animation begins.
I can get into the Bootloader, but when I try to select Recovery mode it just goes back to the white boot screen and repeats. In Bootloader I can select Off, but it only shuts off for a short time then reboots on its own into the boot loop.
This was running stock Android, bought from Google Play store, unlocked, 32GB version, and I had run the previous 3 versions of Android P Beta without problems.
Is there anyway I can do a factory data reset without the Recovery mode?
Thanks,
...Patrick

pamack said:
My Pixel XL downloaded and installed PP5 yesterday, seemed to go okay. Initially, it would boot but spontaneously reboot after 1-2 minutes of run time. But it degraded and now it is stuck on a white screen with Google, and reboots before the animation begins.
I can get into the Bootloader, but when I try to select Recovery mode it just goes back to the white boot screen and repeats. In Bootloader I can select Off, but it only shuts off for a short time then reboots on its own into the boot loop.
This was running stock Android, bought from Google Play store, unlocked, 32GB version, and I had run the previous 3 versions of Android P Beta without problems.
Is there anyway I can do a factory data reset without the Recovery mode?
Thanks,
...Patrick
Click to expand...
Click to collapse
You didn't relock the bootloader did you? After unlocking it?

Phalanx7621 said:
You didn't relock the bootloader did you? After unlocking it?
Click to expand...
Click to collapse
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick

Phalanx7621 said:
You didn't relock the bootloader did you? After unlocking it?
Click to expand...
Click to collapse
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick

pamack said:
No, I did not lock the bootloader. The phone was originally unlocked, and I never rooted it. It was completely stock. But it was definitely acting crazy....at one point I did see the Recovery mode but I did not know at the time what to do with it. Once I had a minute to research that on my laptop then it would never go back into Recovery mode.
So maybe I inadvertently locked it, but not that I know that I did it.
...Patrick
Click to expand...
Click to collapse
I ended up asking uBreakiFix to diagnose the problem....and they indicate it is a bad motherboard.
It can be repaired for $380. I passed, and now own a brick that flashes from one Boot to the next, occassionally running for 30 seconds, but not quite long enough for me to run Reset Factory Settings.
Oh bother, < 2 years old.
...Patrick

pamack said:
I ended up asking uBreakiFix to diagnose the problem....and they indicate it is a bad motherboard.
It can be repaired for $380. I passed, and now own a brick that flashes from one Boot to the next, occassionally running for 30 seconds, but not quite long enough for me to run Reset Factory Settings.
Oh bother, < 2 years old.
...Patrick
Click to expand...
Click to collapse
Still probably worth flashing via adb to check?

mikefnz said:
Still probably worth flashing via adb to check?
Click to expand...
Click to collapse
He means fastboot.