Develop Bugs

[Q] Phone stuck on HTC screen and won't boot

Hi,
I rooted my phone about a year ago and recently wanted to update it and try a new ROM. Since I have no idea what the compatibility of of my old ROM I made a NAND backup then I reset it to the factory RUU version 3.29.651.5 and my phone was back to normal in the boot loader S was set as S-on.
I then proceeded to use the autoroot v2.5 in this thread: http://forum.xda-developers.com/showthread.php?t=838448. In the cmd prompt it said it was flashing the firmware, then said it was waiting for the device to boot up; however, the device did not boot up, I waited for approx 60 min and it was stuck on a black screen with the HTC logo in the middle and a small warning (triangle with exclamation point) in each corner. Now, it is permanently stuck on that screen. Even if I try to hold the volume down to get to the boot loader when it starts, it still goes to this screen.
What can I do to try to get out of this? I cant go back to my recovery to get my backup.
Thanks
Sorry if I incorrectly used some of the terms in this post.

alibabazhang said:
Hi,
I rooted my phone about a year ago and recently wanted to update it and try a new ROM. Since I have no idea what the compatibility of of my old ROM I made a NAND backup then I reset it to the factory RUU version 3.29.651.5 and my phone was back to normal in the boot loader S was set as S-on.
I then proceeded to use the autoroot v2.5 in this thread: http://forum.xda-developers.com/showthread.php?t=838448. In the cmd prompt it said it was flashing the firmware, then said it was waiting for the device to boot up; however, the device did not boot up, I waited for approx 60 min and it was stuck on a black screen with the HTC logo in the middle and a small warning (triangle with exclamation point) in each corner. Now, it is permanently stuck on that screen. Even if I try to hold the volume down to get to the boot loader when it starts, it still goes to this screen.
What can I do to try to get out of this? I cant go back to my recovery to get my backup.
Thanks
Sorry if I incorrectly used some of the terms in this post.
Click to expand...
Click to collapse
The first time I tried to Root my phone, I had the same problem with Toasts Root method. That's stock Recovery you're seeing.
I ended up having to use Unrevoked Linux version and swore I would never unroot again, and I haven't.

I've tried using unrevoked and several other methods. The problem is I think most of them rely on the phone being on with USB debugging enabled. I unfortunately can't get there. The one ray of hope I have is that the device is recognized in my device manager as "Android USB device - HTC bootloader". Is there any other way I could fix this?

alibabazhang said:
Hi,
I rooted my phone about a year ago and recently wanted to update it and try a new ROM. Since I have no idea what the compatibility of of my old ROM I made a NAND backup then I reset it to the factory RUU version 3.29.651.5 and my phone was back to normal in the boot loader S was set as S-on.
I then proceeded to use the autoroot v2.5 in this thread: http://forum.xda-developers.com/showthread.php?t=838448. In the cmd prompt it said it was flashing the firmware, then said it was waiting for the device to boot up; however, the device did not boot up, I waited for approx 60 min and it was stuck on a black screen with the HTC logo in the middle and a small warning (triangle with exclamation point) in each corner. Now, it is permanently stuck on that screen. Even if I try to hold the volume down to get to the boot loader when it starts, it still goes to this screen.
What can I do to try to get out of this? I cant go back to my recovery to get my backup.
Thanks
Sorry if I incorrectly used some of the terms in this post.
Click to expand...
Click to collapse
Are you holding power and volume down at the same time. Sounds like you are just holding volume. When you get to the bootloader I'd you see s-off all you will need to do is flash a PC36IMG of the recovery of your choice(I recommend twrp). Good luck!
Sent from my PC36100 using XDA Premium App

Also, no need to unroot for any rom. Once you are rooted you can flash anything you want. Compatibility wise, you may need to update a radio but that is just flashed in recovery.
Sent from my PC36100 using XDA Premium App

Thanks for the reply. Unfortunately I am holding power and volume down. Powering it on normally and powering it on while holding volume down both go to the same screen.

No way out of this brick....tried for 7 hours..

Ok so basically, I rooted my phone yesterday. Installed cyanogen mod and cwm successfully. Didnt like cm....so I just flashed MIUI ontop of it (which was a stupid mistake and didnt think about it since it was early in the morning). So then I tried loading the stock rom ontop of that....no luck...then i tried loading another stock rom on top of it...no luck....and then another....no luck. Now I can only enter download mode with no way of entering recovery mode (which I was able to get into before but not after I installed like 3 stock roms)...Now when im in download mode, The custom binary download count is at 5....which im assuming is bad lol. Not only that, but i tried the "nand erase all" option on odin and still no luck....still stuck on the samsung glowing boot logo. Im ****ting my pants cause I just got this phone a week ago and cracked the screen the day before (first time every cracking a screen )...Goddamn android rooting is so much more complicated than jailbreaking the simplistic iphone (even though i fell in love with the s3 in just a week)
Soooo please Im shouting out to this community that has made so many guides (which i thank you for), but none were able to fix my problem .... Any suggestions? I can't do a factory reset either cause i cant even enter recovery mode...Im 100% sure that I used the correct ROMs and files for my att samsung i747
EDIT: I tried odining the stock ROM again (for like the 5th time) and now when I boot my phone, it gets past the 2nd screen (the samsung galaxy s3 screen) but blacks up right before the 3rd screen (the white att logo screen) and only shows a glowing green to blue LED at the top left. I am still able to enter download mode, but still not recovery mode even after odining cwm. Im up to a custom binary count of 8.

Odin back to stock.

shoupness said:
Odin back to stock.
Click to expand...
Click to collapse
Did you even read what I wrote...?

If you are able to enter download mode...you are able to odin back to stock. Yeah I'm sure we both read what you wrote.
Sent from my SAMSUNG-SGH-I747 using xda premium

penpen72 said:
If you are able to enter download mode...you are able to odin back to stock. Yeah I'm sure we both read what you wrote.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Ok let me rephrase it then. Ok yes I can odin back to stock. No i can't get past the samsung pulsating logo....and NOW i cant even get past the second screen and I freeze with a black screen and a blue LED right before when the att white logo screen is supposed to pop up. FML
HOWEVER i am now able to get into recovery mode so i atleast made some progress.

Warpclaw said:
Ok let me rephrase it then. Ok yes I can odin back to stock. No i can't get past the samsung pulsating logo....and NOW i cant even get past the second screen and I freeze with a black screen and a blue LED right before when the att white logo screen is supposed to pop up. FML
HOWEVER i am now able to get into recovery mode so i atleast made some progress.
Click to expand...
Click to collapse
Wipe data/cache now that you can get into recovery. All will be fine.
Sent from my SAMSUNG-SGH-I747 using xda premium

Warpclaw said:
Ok let me rephrase it then. Ok yes I can odin back to stock. No i can't get past the samsung pulsating logo....and NOW i cant even get past the second screen and I freeze with a black screen and a blue LED right before when the att white logo screen is supposed to pop up. FML
HOWEVER i am now able to get into recovery mode so i atleast made some progress.
Click to expand...
Click to collapse
Probably have to factory reset in recover after the Odin to stock to get it to boot up. It will erase the internal SD though.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

rizzo269 said:
Probably have to factory reset in recover after the Odin to stock to get it to boot up. It will erase the internal SD though.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
No, it won't. Factory Reset does not touch the internal sd. It merely deletes app data. But what they said, Factory Rest, Wipe Cache/Dalvik. You'll be good to go. This is causing your hang up.

Use TWRP to wipe system and data-wipe (bottom left corner, forget exact name). Those two items usually help me when nothing else is working.

You can wipe your internal sd card by using twrp and going to wipe.
Sent from my SGH-I747 using xda app-developers app

Warpclaw said:
Ok let me rephrase it then. Ok yes I can odin back to stock. No i can't get past the samsung pulsating logo....and NOW i cant even get past the second screen and I freeze with a black screen and a blue LED right before when the att white logo screen is supposed to pop up. FML
HOWEVER i am now able to get into recovery mode so i atleast made some progress.
Click to expand...
Click to collapse
Try THIS metod. It my work.

Only and I mean only if all else fails, you should look at this article, but I cannot guarantee it will work.
http://forum.xda-developers.com/showthread.php?p=30386309
Sent from my SAMSUNG-SGH-I747 using xda premium

boot up problem

So I go boot up my phone it will sit on the HTC logo with the red lettering I have a custom Romalso but It will sit on that screen for 5 minutes before it go black and onto my Rom there is no boot animation that pops up and I can take screenshot and it's like the phone is fully booted up but that white HTC screen will sit on there and 5 minutes later I can use my phone I really need son help with this also I need a stock rom

Same boat....

Make sure your firmware is up to date for the Rom you are on. Search how to flash firmware.. vomers guide. Wrong firmware can create very long boot times.
Sent from my HTC One_M8 using XDA Free mobile app

Bootlooped 30min, then came back. Memory corrupted? How do I check?

Okay, today evening, my Nexus 5X rebootet already 5 times while I was using it just as every evening (browsing web, watching youtube, nothing special).
After the second reboot, it actually vibrated two times during the boot animation (after entering the decryption pin) like it usually only does when powering it up.
After the third reboot, it bootlooped for more than 30min (!!) ... Just the bootloader (white google logo), then ~3s black screen, then vibrating and Google Logo again!
Entering boot menu was possible... I used it to power off and reboot, but didn't help. I was just letting it bootloop while I searched my old Nexus 4 to reactivate it
After the 30min or more bootlooping (by the time I already found my Nexus 4 and reinstalled its battery ) the Nexus 5X asked for decryption pin.... I entered it, it rebootet. It asked again. If finally bootet.
After ~3min of use (just enough for a whatsapp backup) it rebootet again and bootlooped again for ~15min. And same again.
Now it is back once again - for the moment.
I need help, what can I do now, except backing up all relevant data?
It is stock android, not rooted, bootloader locked
Can I somehow test the memory? See why it rebooted?
It NEVER rebooted before since I own it...
Thx

The device rebooted after few minutes yesterday... It still overcomes the first bootloop from time to time after dozens of bootloops but then crashes most of the time after I was able to enter the pin. Since yesterday, it only managed to finish booting two times but always rebooted after few minutes.
Is this the famous BLOD? Haven't heard of it until today (sorry) ...
I actually had OEM unlock enabled in the developer menu, so I could actually unlock the bootloader...
Can I verify that it actually is the BLOD by unlocking the bootloader and temporary booting the modified boot image using fastboot? I don't want to flash something at the moment, because I might get it replaced... I can lock the bootloader again afterwards, right?

I think it might be possible to use "fastboot boot boot.img" (using the 4-core kernel image) from the bootloader screen. That won't install anything.

Thx. However, it requires me to unlock the bootloader and delete all data, since there is no 4-core kernel provided/signed by google, right? I will be able to lock the bootloader again afterwards, as long as I won't flash a different kernel (or reflash the stock kernel), right?

dude while your phone is on, first backup your files, then enable OEM unlock, if your phone is damaged with bootloop of dead, you will be able to make it work using the 4 kernels fix.

caifaz said:
dude while your phone is on, first backup your files, then enable OEM unlock, if your phone is damaged with bootloop of dead, you will be able to make it work using the 4 kernels fix.
Click to expand...
Click to collapse
I do have all important data backed up, I guess. Doing Backups for Android is just PITA... I wasn't able to get the phone running for more than a few minutes today. OEM unlock is enabled, but the bootloader is locked still, so all data will be deleted. I'll try the 4 core kernel as soon as I completely restored all data to my replacement phone, so I'm really confident I can wipe all data from the old one.
Thx so far!

RFZ said:
I do have all important data backed up, I guess. Doing Backups for Android is just PITA... I wasn't able to get the phone running for more than a few minutes today. OEM unlock is enabled, but the bootloader is locked still, so all data will be deleted. I'll try the 4 core kernel as soon as I completely restored all data to my replacement phone, so I'm really confident I can wipe all data from the old one.
Thx so far!
Click to expand...
Click to collapse
you're welcome, there is no need to flash a bootloader, just flash the TWRP recovery (modded for 4 cores), restart to recovery and then flash EX kernel (modded for 4 cores) according to you SO version.
I have fixed a phone 2 years ago using this instructions

Okay, I just verified it... The device boots fine with the 4 core kernel. I then reflashed the stock image, locked the bootloader, and it bootloops again. Will send it back to the store now and hope I'll get a refund/replacement :fingers-crossed:

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.