[Q&A]Bricks, boot loops, and random shutdowns | Ask here | No new threads

Search This thread

voilatile

New member
Apr 9, 2022
2
0
Phone stuck on boot screen after attempting to flash a custom ROM

Hi!
It wa my first try at installing a custom ROM and steps I did are basically the following:
1) unlocked the bootloader
2) flashed twrp (twrp-3.6.1_9-0-pme)
3) did a backup
4) in recovery mode, did a format
5) rebooted to recovery, wiped Dalvik+cache+system
6) rebooted to recovery, chose ROM+GApps's zip to install (lineage-19.1-20220407-UNOFFICIAL-pme, MindTheGapps-12.1.0-arm64)
7) attempted to reboot to the system

And then, the HTC logo appeared with "this build is for development purpose only " etc. etc., in red font. It's been in this state for about an hour.
Could not get it to reboot into recovery mode by holding different combos. When holding power and volume down buttons' LEDs blinked but nothing happened.

I was on stock Oreo, with unlocked bootloader but S-ON.

EDIT:
after about a day, I connected it to pc with USB cable and it turned back on, starting the newly flashed OS. Afterwards, I was able to reboot to bootloader/download/recovery/system.
 
Last edited:

ondrasouk

Member
Apr 15, 2016
33
12
HTC One (m7)
Google Nexus 5
Phone stuck on boot screen after attempting to flash a custom ROM

Hi!
It wa my first try at installing a custom ROM and steps I did are basically the following:
1) unlocked the bootloader
2) flashed twrp (twrp-3.6.1_9-0-pme)
3) did a backup
4) in recovery mode, did a format
5) rebooted to recovery, wiped Dalvik+cache+system
6) rebooted to recovery, chose ROM+GApps's zip to install (lineage-19.1-20220407-UNOFFICIAL-pme, MindTheGapps-12.1.0-arm64)
7) attempted to reboot to the system

And then, the HTC logo appeared with "this build is for development purpose only " etc. etc., in red font. It's been in this state for about an hour.
Could not get it to reboot into recovery mode by holding different combos. When holding power and volume down buttons' LEDs blinked but nothing happened.

I was on stock Oreo, with unlocked bootloader but S-ON.

EDIT:
after about a day, I connected it to pc with USB cable and it turned back on, starting the newly flashed OS. Afterwards, I was able to reboot to bootloader/download/recovery/system.
When holding power and volume down, wait for buttons to start blinking and then holds for 20-30 seconds to force the reboot. The reboot is triggered when you release the buttons.
The custom ROM's kernel is not the most stable thing in universe and sometimes it gets stuck. Hope this will help.
 

TurboLolo

New member
Sep 19, 2022
1
0
Hi, I have problem with HTC 10. After power on it always loop (app optimization) and stays on green HTC sign. When enter download mode it shows:

*** UNLOCKED ***
htc_pmeuhl PVT S-OFF
CID-HTC__001
MID-2PS620000
ColorID-WHT00
LK-1.0.0.0000
[email protected]
OPenDSP-v20.0.08996.00007_0809
OS-2.41.401.41
Aug 2 2017,12:18:15(857212)

Bootloader shows:
*** Software status: Official ***
*** UNLOCKED ***
*** S-OFF ***

Android Recovery shows:
htc/pmeuhl_00401/htc_pmeuhl
7.0/NRD90M/857212.41
user/release-keys

all I know phone was on Oreo and no clue what was done earlier. I received it this way. I don't care about data lost just bring it back to life, please help.

UPDATE:
Flashing phone with OTA 3.16.401.2 unbrick the device.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    This thread has been created for users who are experiencing a hard brick, soft brick, boot loop, or random shutdown on their HTC 10. Feel free to ask your question(s) here.

    Going forward, new threads created regarding the topics listed above will be CLOSED by the moderating staff. Please remember to follow the XDA forum rules when posting.

    Cheers,

    Magnum_Enforcer
    FSM
    2
    Possible Explanation for the Random Shutdown and Boot Looping

    My phone was initially fine but then suffered this dreaded random shutdown and boot loop. And then after doing a certain technique, it didn't repeat when the phone got down to below 20%. I have a theory as to why this problem is happening.

    After I charged my phone back up to 100%, I then pressed and held the volume buttons and power button simultaneously for about 2 minutes. Upon release, battery level was 89%. I charged it back up to 100% and repeated. Next battery level was 92%. Repeated, and then battery level was 97%. From there I just charged normally back to 100% and let it gradually drain down from there. When I hit 25%, I put the screen on maximum and streamed YouTube videos. The battery level began to drop about 2% after each video. I got to 17%, stopped, and rebooted. 16% and still no shutdown and boot looping. After it got below 15% I got a low battery warning, and still no shut down. At 12% it was still running.

    I have a new (to me) theory that what may be happening is some kind of firmware issue, where the "adaptive" monitoring of the battery becomes flawed and thus the percentage battery level becomes misinterpreted. That's why there's that auto-shut down. Because the battery REALLY IS LOW, but the Android OS doesn't know it. And then the battery's safety circuitry kicks in and aborts power to the phone. Where it all goes wrong is when the battery becomes a bit worn after a year or so of use. The firmware starts to collect faulty battery status data and then erroneously report the battery level. THIS IS WHY, the phone tries to "boot loop" after the shutdown because it still has faulty battery data. It keeps trying, but the battery says "NO"... and denies sufficient power to complete. And then when you plug in the phone, the battery won't stop the phone from booting up because now the phone has sufficient power, so it completes. Only somehow at that moment, the firmware finally shows the right battery level. 1%.

    What cemented my theory was when I plugged my phone back in to my A/C powered USB charger, but this time I did not use the Quick Charge 3.0 port. I used a normal port. And within about 30 minutes, I check the phone and it's showing a 40% power level. That's too fast. From 12%, it should take about 2~3 full hours to charge back up to 100%, and in about 1 hour with Quick Charge. What it suggests to me is that the firmware is still screwing up the battery power level interpretation.

    So ultimately this problem isn't the battery. Batteries do wear down, and that's a fact. But from my observations I think it's the firmware in the HTC 10 that's screwing up in it's sensing of the actual battery power level. It gets "out of sync" and thus, this dreaded shutdown starts happening, anywhere from 20~50% power level, maybe more. It may be the micro code in the kernel... which is why some people who switched to a different kernel aren't suffering this problem.

    The HTC 10 firmware (or kernel) is PREVENTING the battery from fully charging, because it decides it's 100%, when it really isn't. And to get it to do so, you have to "force" it to see the actual lower battery level.

    Replacing the battery TEMPORARILY solves the problem, because the battery is fresh and new. But once the battery starts to accumulate some wear on it, this problem will repeat again... until the firmware (or kernel) is replaced. And if you stick with this flawed battery management code, what you'll have to do is make sure the battery REALLY IS at 100%, by doing that 3 button press for 2 minutes, then charge again. It's the only way to get the battery fully topped off, because the phone is actually not letting it get high enough. What you see is 100%, but it's probably more like 60~80%. And that's why, when the battery starts getting below 50%, you end up in that precarious situation where the battery is actually now in the "danger zone" of really low, but the phone is not reporting it... and thus, shutdown occurs.

    Alternative: Of course, this is all speculation from someone who is not an engineer. It's also possible that perhaps it's not so much the kernel as it could be actual hardware in the phone, somewhere in the interface between the battery and the CPU. And thus a replacement kernel like ElementalX is able to overcome it. HTC should take it upon themselves to figure this out... because if it can happen on a phone like the HTC 10, who knows -- maybe it's going to pop up on newer models too. They should understand what's going wrong so they can prevent it from happening again.
    2
    I'm no expert in this my self just FYI, but installing a RUU is usually a straight forward process.
    You need to download a ruu for your particular CID (Depens on where the phone was sold and what -if any- carrier the phone is locked to.)
    I have an european unlocked one so the RUU I used was this: https://androidfilehost.com/?fid=817550096634797504
    You can find more in this thread: https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297

    Download the ruu (just short of 2GB in size) , rename it to 2PS6IMG.zip and put it in the root of an SD-card and insert it into the phone.
    Reboot it into download mode by holding power+volume down until the grey HTC logo appears.
    It should now detect the zip file in the sd-card and ask you to install it. Press volume up to confirm.

    This will re-install everything (System image, recovery, firmware etc) all existing data gets destroyed.
    Worked like a charm for me, and was able to do a Oreo OTA right away after the first boot.
    2
    It's 1.96.708.5
    CID is from Hong Kong.
    Well a quick search in the stock thread came up with this Oreo RUU
    https://forum.xda-developers.com/ht...ection-recovery-ruu-ota-t3359297/post75300717
    If that matches your CID your good to go
    2
    Well, I suppose you are not booting into system, are you? If you are not and OEM lock is enabled + you dont have TWRP flashed - the only way (I know of) is to get RUU file for your CID and MID (since you are s-on). Also It needs to be an Oreo RUU. Unfortunately I wasnt able to find any for your android version (3.16.401.2)
    Best chance is to contact HTC support (they have online chat) and ask them if they can provide RUU for this version.