Develop Bugs

Unable to get into bootloader or recovery mode, stuck at white HTC logo screen

Hey everyone,
I have read the various topics with a similar title but none helped.
Here is my problem, I bought a used HTC Desire on eBay. It booted just fine on the first start, then I did a factory reset (from within the Android system menu).
Since then, I'm stuck at the white screen with the green HTC logo. I have tried to get into bootloader mode by removing the battery, holding vol down and power, but it just goes straight to the white screen again.
Also connected the phone to the pc, but adb isn't picking up anything...
Any ideas?

Try Power+Back button.

just got one step further:
I can get into fastboot mode with BACK + POWER. But volume keys doesn't work, is that a known issue that I can solve somehow?

Goddchen said:
just got one step further:
I can get into fastboot mode with BACK + POWER. But volume keys doesn't work, is that a known issue that I can solve somehow?
Click to expand...
Click to collapse
So you bought a Desire with broken volume keys.
Are you s-off?

abaaaabbbb63 said:
So you bought a Desire with broken volume keys.
Are you s-off?
Click to expand...
Click to collapse
looks like...
in fastboot mode it shows that it is s-on.

Goddchen said:
looks like...
in fastboot mode it shows that it is s-on.
Click to expand...
Click to collapse
Then you'll have to flash a RUU to make it work.
http://forum.xda-developers.com/showthread.php?t=1772499
It's official HTC Firmware. Your phone will boot after this.
So:
1. Install HTC Sync.
2. Download and extract the RUU.exe from the zip (It's somewhere in there)
3. Run the exe while you connect your phone in fastboot (Power+Back)
4. Wait for it to install
5. Boot

abaaaabbbb63 said:
Then you'll have to flash a RUU to make it work.
http://forum.xda-developers.com/showthread.php?t=1772499
It's official HTC Firmware. Your phone will boot after this.
So:
1. Install HTC Sync.
2. Download and extract the RUU.exe from the zip (It's somewhere in there)
3. Run the exe while you connect your phone in fastboot (Power+Back)
4. Wait for it to install
5. Boot
Click to expand...
Click to collapse
Thanks for the advice, I downloaded the 2.3 RUU and it starts the process, sais
rebooting to bootloader
erasing data
sending...
and after ~30 seconds it just shows me a screen that sais "ERROR_UNKNOWN"
On the phone I see a black screen with a silver HTC logo during the process and when I unplug the USB cable after the error it shows the hboot screen that now sais "update failed".

right before the error is shown it display "updating signature"

Goddchen said:
right before the error is shown it display "updating signature"
Click to expand...
Click to collapse
It only says "Error_Unknown"? No error number, anything?
Weird.
This may be the reason:
Now, that may not sound too bad to some of you, but there's more: the 2.3 RUU update is limited regionally, as well. It's not available to users in Germany, North America, South America, South Korea, or Japan.
Click to expand...
Click to collapse
You live in Germany, right?
Use this guide then:
Section 2, S-on
http://forum.xda-developers.com/showthread.php?t=1275632

yes I am in Germany,
made some progress (or not?)
I noticed that the device was "unlocked", so I did "fastboot oem lock" and it was "relocked".
Then the RUU update went through - nearly. At the very end if failed again and now I am stuck at a black screen with the silver HTC logo and triangles in every corner.

AW: Unable to get into bootloader or recovery mode, stuck at white HTC logo screen
Sent from my Nexus 4 using xda app-developers app

wtf... tried again flashing the 2.3 RUU, this time it worked, YEAY
But now I have a bootloop, device starts, vibrates 1 time, waits for 3 seconds, and then vibrates 7 times. And restarts...

Ok. Tests are done.
According to the screenshot above and the 7 vibrations, you have a radio brick. It's a brick that can hardly be overcome.
The only solution is flashing the RUU and hoping that the phone will eventually boot.
That's why I don't buy second hand phones.
This thread might help:
http://forum.xda-developers.com/showthread.php?t=1793369

abaaaabbbb63 said:
Ok. Tests are done.
According to the screenshot above and the 7 vibrations, you have a radio brick. It's a brick that can hardly be overcome.
The only solution is flashing the RUU and hoping that the phone will eventually boot.
That's why I don't buy second hand phones.
This thread might help:
http://forum.xda-developers.com/showthread.php?t=1793369
Click to expand...
Click to collapse
freecer did it, was able to flash the 2.3 RUU again successfully. But now I'm back at the bootloop, but now, it simply does vibrate once (no more 7 vibrations) and reboots after some seconds.
So what can I do now? RUU flashed successfully, I'm running out of ideas...

and again the freezer did it, put it in, normally started via POWER button, it booted right through into Android.
Well, let's see if it keeps running now or if this overheating issue also exists in normal operation mode...
Thanks so much for you help so far, the freezer hint saved this device and hopefully will make my gf very happy tomorrow

Hold on I thought it was some pvt1 devices that had overheating issues.
Thought it was fixed on your newer ones. Then again I've never had a problem with my pvt1 desire flashed both hboot and find countless times.
Sent from my GT-I9100 using xda app-developers app

dethrat said:
Hold on I thought it was some pvt1 devices that had overheating issues.
Thought it was fixed on your newer ones. Then again I've never had a problem with my pvt1 desire flashed both hboot and find countless times.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
it is a PCT3 device.
but the overheating-reboot issue is rendering it useless. I can use it just fine outside (-2° currently) but as soon as I'm inside, boot-loop...
Anything I can do from a hardware perspective to fix that? Sending it in for repair/replacement is not an option, it's simply not worth the cost.

do you think installing a custom rom of any kind might help?

Goddchen said:
it is a PCT3 device.
but the overheating-reboot issue is rendering it useless. I can use it just fine outside (-2° currently) but as soon as I'm inside, boot-loop...
Anything I can do from a hardware perspective to fix that? Sending it in for repair/replacement is not an option, it's simply not worth the cost.
Click to expand...
Click to collapse
It's a motherboard fault. If you don't send it to repair, you just got yourself an "Ice-Phone", or a very complex paper holder.

i think a custom rom would help a small bit, like the rom in abaaaabbbb63 sig (mildwild redux) because its small and lite unlike a sense rom. therefor it mite not overheat as quick or as often. but thats only a guess. the only dodgy thing is trying to get ur phone s-off or rooted because if ur phone overheats in the middle of the s-off/rooting progress u could brick ur phone. plus charge ur phone using ur computer coz it uses less power and the phone does'nt heat up as much as plugging into the wall.

HTC One X 10 minutes Black screen after TURN ON or RESTART

Good day everybody!
My device is:
HTC One X
CID: T-MOB101
HBOOT: 1.36.0000
BL: UNLOCKED
it started after sending ADB command (adb reboot recovery) to phone while it was ON. Phone turned off, just after several minutes it turned on. But not recovery. Since that it takes about 10-20 minutes to reboot or turn on phone (just black screen after POWER button pressed or RESTART command given). And it's heating. I can enter bootloader by pressing POWER and VOLUME- key, and holdin VOLUME- key until it turns on screen. After that I flashed HBOOT by entering RUU mode, but no result. If someone had this problem before, please I need help!

titanium2323 said:
Good day everybody!
My device is:
HTC One X
CID: T-MOB101
HBOOT: 1.36.0000
BL: UNLOCKED
it started after sending ADB command (adb reboot recovery) to phone while it was ON. Phone turned off, just after several minutes it turned on. But not recovery. Since that it takes about 10-20 minutes to reboot or turn on phone (just black screen after POWER button pressed or RESTART command given). And it's heating. I can enter bootloader by pressing POWER and VOLUME- key, and holdin VOLUME- key until it turns on screen. After that I flashed HBOOT by entering RUU mode, but no result. If someone had this problem before, please I need help!
Click to expand...
Click to collapse
Did you try the One X all in one kit?

Try this, put the phone in the bootloader and perform this fastboot command
Fastboot erase cache
Then unhook the usb cable and enter the recovery.

Mr Hofs said:
Try this, put the phone in the bootloader and perform this fastboot command
Fastboot erase cache
Then unhook the usb cable and enter the recovery.
Click to expand...
Click to collapse
Probably, you didn't understand me...
I can enter bootloader, I can enter recovery, I can flash ROM, I can even enter RUU mode to flash HBOOT and I can erase CACHE. I've tried them ALL!
The problem is - whenever phone goes to restart it won't turn on for about 10-20 minutes, just black screen and heating. After 10-20 minutes screen turns on and HTC logo appears for 3-5 minutes, then starts loading of OS.
If you haven't see it before, you won't understand...

I sense a hardware fault here...
-Sent from my IceCold One X!

You said and i qoute
not recovery.....so i assumed you could not enter the recovery !
Then you should have stated it a bit more clear in the first post !
And you have no idea what i know about the hox and what i have seen ! You think my thanks meter is over 3000 for doing nothing. What's up with people on xda these days. Can't handle help that's given with the provided info. I think im going to quit xda.
No offense to you.....its more of a general rant.
titanium2323 said:
Good day everybody!
My device is:
HTC One X
CID: T-MOB101
HBOOT: 1.36.0000
BL: UNLOCKED
it started after sending ADB command (adb reboot recovery) to phone while it was ON. Phone turned off, just after several minutes it turned on. But not recovery.
Click to expand...
Click to collapse

RE:2
Mr Hofs said:
You said and i qoute
not recovery.....so i assumed you could not enter the recovery !
Then you should have stated it a bit more clear in the first post !
And you have no idea what i know about the hox and what i have seen ! What's up with people on xda these days. Can't handle help that's given with the provided info. I think im going to quit xda.
No offense to you.....its more of a general rant.
Click to expand...
Click to collapse
Sorry about it... I'm so nervous because of phone...This is first time when I can't solve problem by myself.
So, what you advice to do with phone?

Well as V said, its likely a hardware failure at some point. You say you tried it all, no avail !
The only thing you can try once more is a factory reset from the bootloader. After that its off for repair. Try to get the phone to stock if you still can with the stock nandroid backup, stofk recovery and relock the bootloader. Best chance of claiming warranty.

yes,now it happen to me..grrrr.. after i use camera,suddenlly its stuck..so i off the phone,after thats,i try on again but screen is going black..i can t do anythings...cant..1st time happen to me..

I had something similar..since jb I can not boot with the normal 1500 mhz...if I boot the phone gets hot and restart ..I reflashed a ics..I can boot with 1500 again...so I made a kernel that boot with 1300. Mhz now all is Okey again...maybe its worth to try..look in my signature the s e kernel
Sent from my HTC One X using xda app-developers app

Alex-V said:
I had something similar..since jb I can not boot with the normal 1500 mhz...if I boot the phone gets hot and restart ..I reflashed a ics..I can boot with 1500 again...so I made a kernel that boot with 1300. Mhz now all is Okey again...maybe its worth to try..look in my signature the s e kernel
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=43780561#post43780561

ejoyeila said:
http://forum.xda-developers.com/showthread.php?p=43780561#post43780561
Click to expand...
Click to collapse
Yes..should be a problem of the board..not the display..did you have warranty send it in..if you get it running make it stock before...mine was a replaced because of a similar prob
Sent from my HTC One X using xda app-developers app

Mr Hofs said:
And you have no idea what i know about the hox and what i have seen ! You think my thanks meter is over 3000 for doing nothing. What's up with people on xda these days. Can't handle help that's given with the provided info. I think im going to quit xda.
No offense to you.....its more of a general rant.
Click to expand...
Click to collapse
You are extremely valuable to XDA Hofs! I cannot count how often i have seen you give valuable input (specific answers, long guides, great clues, etc). Just wanted to let you know And people can be dicks sometimes.. Sadly enough.
Kind Regards
TwinAdk

TwinAdk said:
You are extremely valuable to XDA Hofs! I cannot count how often i have seen you give valuable input (specific answers, long guides, great clues, etc). Just wanted to let you know And people can be dicks sometimes.. Sadly enough.
Kind Regards
TwinAdk
Click to expand...
Click to collapse
Thank you for the kind words, it was the heat of the moment where i got more of these posts under my nose as i tried to provide proper help. Its all good.....everybody has a small breaking-point
Lets help some more
I see even Alex is bored, never seen him so active in the Q&A threads before
What's the matter Alex ? Are your kernels too perfect ???

Mr Hofs said:
Thank you for the kind words, it was the heat of the moment where i got more of these posts under my nose as i tried to provide proper help. Its all good.....everybody has a small breaking-point
Lets help some more
I see even Alex is bored, never seen him so active in the Q&A threads before
What's the matter Alex ? Are your kernels too perfect ???
Click to expand...
Click to collapse
Lol..yeah from time to time...I also need a break...and have a look to qa...and still have the 2 sites of mine..1. I will help...2.why don't search a bit....most the help site win...
Anyway..about kernel...I must learn now c programing...i want to have long press 2 sleep....I know a bit but its not enough..
Nice rest of the weekend
Sent from my HTC One X using xda app-developers app

[Q] Endless loop of restarts into recovery

hi everyone,
I am in a quite a pickle here. I tried updating my phone with ARHD43 and after doing it couldn't get the WIFI to turn on. I read a bit and found that this is becuase I do not have the latest firmware. So I tried going back to stock through RUU (flashed stock recovery and boot.img) and in the process flashed new recovery and boot images. Now the my phone keeps booting into stock recovery with the red triangle continuously and I can't boot into the OS. From recovery when I select apply from SD card I throws CID error and reboots into recovery again!
I cannot connect to fastboot so I am stuck bad. :crying:
did I brick my device? can I save it? I am S-ON with unlocked boot loader. region is .707
Appreciate your help.
<I have posted a similar question in the ARHD43 thread but haven't recevied a response so posting in here in the general forum again>

simplyaha said:
I cannot connect to fastboot so I am stuck bad. :crying:
Click to expand...
Click to collapse
This part is your biggest issue. As you know, you can't do much without fastboot.
Make sure you are in bootloader-fastboot mode when issuing fastboot commands. Try to uninstall and re-install fastboot drivers, a different USB post on your computer, even another computer.
Once you get fastboot working, it should be as simple as flashing TWRP again (bootloader must be unlocked) than installing the proper stock nandroid and stock recovery from the following thread (instructions on how to restore the nandroid in Post #3 of the thread, under Questions & Answer). Then OTA to Lollipop.
http://forum.xda-developers.com/showthread.php?t=2701376
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
simplyaha said:
So I tried going back to stock through RUU (flashed stock recovery and boot.img) >
Click to expand...
Click to collapse
Why would you do this? You realize that boot.img is just the kernel (not a full ROM)?

redpoint73 said:
This part is your biggest issue. As you know, you can't do much without fastboot.
Make sure you are in bootloader-fastboot mode when issuing fastboot commands. Try to uninstall and re-install fastboot drivers, a different USB post on your computer, even another computer.
Once you get fastboot working, it should be as simple as flashing TWRP again (bootloader must be unlocked) than installing the proper stock nandroid and stock recovery from the following thread (instructions on how to restore the nandroid in Post #3 of the thread, under Questions & Answer). Then OTA to Lollipop.
http://forum.xda-developers.com/showthread.php?t=2701376
---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------
Why would you do this? You realize that boot.img is just the kernel (not a full ROM)?
Click to expand...
Click to collapse
thank you for replying.
I have have fast boot on my pic and it is working fine. I have used it to install custom rom on my wife's phone and my phone earlier. the problem is I am not able to get into the boot loader and push commands to my phone through fastboot or adb.
my plan was to actually run RUU and update to stock. I couldn't find the RUU for my 707 M8. I read somewhere that to make this work I should run RUU and extract and flash the boot.img it stores in the temporary folder on the PC. I also saved the stock rom file and was planning to flash that through recovery. but I cannot do that now because I am stuck in recovery.
any idea how I can get into boot loader.. this should give me a lot of options to fix my phone.

simplyaha said:
thank you for replying.
I have have fast boot on my pic and it is working fine. I have used it to install custom rom on my wife's phone and my phone earlier. the problem is I am not able to get into the boot loader and push commands to my phone through fastboot or adb.
any idea how I can get into boot loader.. this should give me a lot of options to fix my phone.
Click to expand...
Click to collapse
To get into bootloader, hold down power and vol up for several seconds (maybe up to 10 seconds or more). Once the screen goes black to reboot, immediately let go of both those buttons, and just hold vol down. Keep holding vol down until bootloader appears. If you fail to get into bootloader, you simply started holding vol down too late, or let go of it too early. Just repeat until you get it right.
Fastboot command only work in fastboot mode. adb commands will only work in OS or in recovery. So if you try to issue adb commands in bootloader or bootloader-fastboot modes, it won't work.
simplyaha said:
my plan was to actually run RUU and update to stock. I couldn't find the RUU for my 707 M8. I read somewhere that to make this work I should run RUU and extract and flash the boot.img it stores in the temporary folder on the PC. I also saved the stock rom file and was planning to flash that through recovery. but I cannot do that now because I am stuck in recovery.
Click to expand...
Click to collapse
Pulling files from another CID's RUU is not the proper way to restore to stock. I linked the proper thread with your stock ROM (which also includes boot.img) and stock recovery for your CID.
Plus, the stock ROM and recovery you restore has to match your firmware number, as indicated as OS number on bootloader screen, or main version on getvar all.

redpoint73 said:
To get into bootloader, hold down power and vol up for several seconds (maybe up to 10 seconds or more). Once the screen goes black to reboot, immediately let go of both those buttons, and just hold vol down. Keep holding vol down until bootloader appears. If you fail to get into bootloader, you simply started holding vol down too late, or let go of it too early. Just repeat until you get it right.
Fastboot command only work in fastboot mode. adb commands will only work in OS or in recovery. So if you try to issue adb commands in bootloader or bootloader-fastboot modes, it won't work.
Pulling files from another CID's RUU is not the proper way to restore to stock. I linked the proper thread with your stock ROM (which also includes boot.img) and stock recovery for your CID.
Plus, the stock ROM and recovery you restore has to match your firmware number, as indicated as OS number on bootloader screen, or main version on getvar all.
Click to expand...
Click to collapse
I did try this combination to get into boot loader but I couldn't successfully do that. I had also tried Hold power then immediately volume up and down at same time. When phone powers off release the volume up button.
I will try again and reply.
I couldn't find the 707 RUU anywhere on the web.. please share the link with me if you got it. I hope I get it into boot loader..

simplyaha said:
I did try this combination to get into boot loader but I couldn't successfully do that. I had also tried Hold power then immediately volume up and down at same time. When phone powers off release the volume up button.
Click to expand...
Click to collapse
You're making it more complicated than it needs to be. Stop trying other button combos, and just do it they way I said previously, this works every time as long as you don't start pressing vol down too late (it has to be while the screen is still black before the HTC logo screen appears - you have about 3 seconds which is plenty of time) or don't let go of vol down too early (don't let go until the bootloader screen appears - should only take a second).
If it doesn't work, its pilot error.
simplyaha said:
I couldn't find the 707 RUU anywhere on the web.. please share the link with me if you got it. I hope I get it into boot loader..
Click to expand...
Click to collapse
Only if you promise to stop messing around with incorrect processes, like trying to pull the recovery and boot.img out of the RUU.

redpoint73 said:
You're making it more complicated than it needs to be. Stop trying other button combos, and just do it they way I said previously, this works every time as long as you don't start pressing vol down too late (it has to be while the screen is still black before the HTC logo screen appears - you have about 3 seconds which is plenty of time) or don't let go of vol down too early (don't let go until the bootloader screen appears - should only take a second).
If it doesn't work, its pilot error.
Only if you promise to stop messing around with incorrect processes, like trying to pull the recovery and boot.img out of the RUU.
Click to expand...
Click to collapse
yeah.. i guess I tried all those random things because I am not very clear on all the processes.. but I am learning :victory:
yes, no more messing around, promise.. :angel:

simplyaha said:
yeah.. i guess I tried all those random things because I am not very clear on all the processes.. but I am learning
Click to expand...
Click to collapse
Yeah, stop doing that (trying random things). You can get yourself in a lot of trouble by "experimenting". Stick to proven solutions provided by knowledgeable XDA members.
Here is a link to the 4.19.707 RUU: http://forum.xda-developers.com/showpost.php?p=61886163&postcount=15
I only know of this, since xunholyx linked to it last week while we were helping another 707 owner. I take no responsibility for it. Just linking you to it by request.

redpoint73 said:
Yeah, stop doing that (trying random things). You can get yourself in a lot of trouble by "experimenting". Stick to proven solutions provided by knowledgeable XDA members.
Here is a link to the 4.19.707 RUU: http://forum.xda-developers.com/showpost.php?p=61886163&postcount=15
I only know of this, since xunholyx linked to it last week while we were helping another 707 owner. I take no responsibility for it. Just linking you to it by request.
Click to expand...
Click to collapse
ccol thank! I will try this tonight and share the outcome.. :good:

eureka! got my phone up and running now. the ruu was perfect. but got my memory card messed up (showing as raw format on the pc). gotta look for a solution for this now :banghead:
but my phone is back! thank you for all the help. much appreciated. :thumbup:
Sent from my HTC One_M8 using XDA Free mobile app

HTC M8 bootloop after android M OTA

i just updated my m8(4.16.401.13) to marshmallow. but installation stucked at 83% i guess. then it gives me bootloop. what should i do? are there any way to get my data back? i'm on stock bootloader and unrooted. i just want my data. please help.

I got the same problem . Get stuck at bootloader after it's finished update to android M when it restarts. I couldn't do recovery or factory reset ...anything. Try wipe cache shut down power up so many times but still stuck at bootloader.
My phone is unlocked brand new no-root and the status of fastboot is "LOCKED"
Please Help.

nascar895 said:
i just updated my m8(4.16.401.13) to marshmallow. but installation stucked at 83% i guess. then it gives me bootloop. what should i do? are there any way to get my data back? i'm on stock bootloader and unrooted. i just want my data. please help.
Click to expand...
Click to collapse
I had the same problem.. I ended up going to the boot loader (hold power and vol down simultaneously when phone is OFF) and then run Marshmallow RUU ZIP to recover it.
I don't know if there's another way to recover - probably it's possible. Good luck..
All data was gone for me including photos... But I think that happened because I used RUU to recover.

OOPS
Pepaaa said:
I had the same problem.. I ended up going to the boot loader (hold power and vol down simultaneously when phone is OFF) and then run Marshmallow RUU ZIP to recover it.
I don't know if there's another way to recover - probably it's possible. Good luck..
All data was gone for me including photos... But I think that happened because I used RUU to recover.
Click to expand...
Click to collapse
i also thought that. but are there anyway to backup data before doing it?

is it stuck on bootloader
MinhNg said:
I got the same problem . Get stuck at bootloader after it's finished update to android M when it restarts. I couldn't do recovery or factory reset ...anything. Try wipe cache shut down power up so many times but still stuck at bootloader.
My phone is unlocked brand new no-root and the status of fastboot is "LOCKED"
Please Help.
Click to expand...
Click to collapse
is it stuck on bootloader ?

Pepaaa said:
I had the same problem.. I ended up going to the boot loader (hold power and vol down simultaneously when phone is OFF) and then run Marshmallow RUU ZIP to recover it.
I don't know if there's another way to recover - probably it's possible. Good luck..
All data was gone for me including photos... But I think that happened because I used RUU to recover.
Click to expand...
Click to collapse
can you send me the link of marshmallow ruu

You can google it:
nstall-htc-one-m8-official-android-6-0-marshmallow-ota-update
Not sure it will work with HTC M8 Unlock Phone (Maybe International version )
Regards,
MN

can't find the ruu
MinhNg said:
You can google it:
nstall-htc-one-m8-official-android-6-0-marshmallow-ota-update
Not sure it will work with HTC M8 Unlock Phone (Maybe International version )
Regards,
MN
Click to expand...
Click to collapse
i just google it and i can't find the exact ruu. can you provide a link please

nascar895 said:
i just google it and i can't find the exact ruu. can you provide a link please
Click to expand...
Click to collapse
He can't post link as he is new on XDA ...
Check here : http://forum.xda-developers.com/htc-one-m8/general/marshmallow-6-0-update-htc-m8-european-t3296141
Link on post #3 ... read all posts to understand better how to do it ...

yet another brick thread, please help

Verizon
s-off/unlocked
I've been searching the interwebs for about a month trying various fixes before I posted here, but the time has come - last ditch effort before I give up
I can only access bootloader mode. No download, no recovery and no system. All that shows is the custom "no red text" hboot and bootloops.
Both MID and CID were blank when I checked at the beginning of my tinkering (but after bootloop), and now I get "FAILED (remote: unknown command)" when running htc_fastboot oem readcid
I've tried manually flashing partitions as explained in other threads with no success, tho I haven't tried sneakyghost's firmware because I'm on Verizon (would that really matter?? should I try it anyway? Thinking I'd be able to convert back to Verizon afterwards.)
Running ruu.exe tells me my battery is less than 30%, but can't charge because it just wants to bootloop.
So frustrating. Is there any hope?
Thanks in advance.

What caused this? And you should be able to charge in bootloader mode to run ruu

Other information if it helps:
TWRP 3.1.1-0
Firmware 2.41.605.12
Clean Slate Kernel 2.1.0
Viper 10 5.10
PnP Thermal tweaks
JohnFawkes said:
What caused this? And you should be able to charge in bootloader mode to run ruu
Click to expand...
Click to collapse
Does it charge while in bootloader mode? I only assumed not because the led doesn't come on.
As to what caused this..
I updated TWRP to 3.1.1-0 from 3.1.0-1 about 8 hours prior - before work. During work did get used. i was able to make a few phone calls and txts. After work, I'm doing something, whatever, and I notice my back button wasn't responding. Natural response is to reboot.. and bootloop began.
I was trying to improve battery life the best I could.. as with most everyone else, I have been unimpressed with it, especially since Nougat. I was using Elemental-X kernel for awhile and had only recently switched to Clean Slate, probably within a week of bootloop.

GillaxGurilla said:
Other information if it helps:
TWRP 3.1.1-0
Firmware 2.41.605.12
Clean Slate Kernel 2.1.0
Viper 10 5.10
PnP Thermal tweaks
Does it charge while in bootloader mode? I only assumed not because the led doesn't come on.
As to what caused this..
I updated TWRP to 3.1.1-0 from 3.1.0-1 about 8 hours prior - before work. During work did get used. i was able to make a few phone calls and txts. After work, I'm doing something, whatever, and I notice my back button wasn't responding. Natural response is to reboot.. and bootloop began.
I was trying to improve battery life the best I could.. as with most everyone else, I have been unimpressed with it, especially since Nougat. I was using Elemental-X kernel for awhile and had only recently switched to Clean Slate, probably within a week of bootloop.
Click to expand...
Click to collapse
None of that should cause a brick unless it's hardware related. Have you tried maybe flashing twrp from PC while in bootloader mode? Not sure if it's possible but worth a shot

JohnFawkes said:
None of that should cause a brick unless it's hardware related. Have you tried maybe flashing twrp from PC while in bootloader mode? Not sure if it's possible but worth a shot
Click to expand...
Click to collapse
Yeah, I tried that.
Do you know what would happen if I tried the full steps using sneakyghost's GSM firmware on my CDMA device?

GillaxGurilla said:
Yeah, I tried that.
Do you know what would happen if I tried the full steps using sneakyghost's GSM firmware on my CDMA device?
Click to expand...
Click to collapse
Would probably cause more damage since it's gsm only....

JohnFawkes said:
Would probably cause more damage since it's gsm only....
Click to expand...
Click to collapse
What I figured. Thanks..
So.. Any other suggestions?
Anyone?

GillaxGurilla said:
What I figured. Thanks..
So.. Any other suggestions?
Anyone?
Click to expand...
Click to collapse
Try to hold volume - and Power button for 50 to 60sec, it can force Download mode to appear.
Had an M9 that went into infinite bootloop but this trick worked and I could access download mode and from there all the rest

vegetaleb said:
Try to hold volume - and Power button for 50 to 60sec, it can force Download mode to appear.
Had an M9 that went into infinite bootloop but this trick worked and I could access download mode and from there all the rest
Click to expand...
Click to collapse
Just tried.. No luck. Thank you.

This may help to reset battery to show correctly, to flash RUU.
Switch off the device.
Then push and hold all three buttons (power / volume up / volume down) for approximately 1-2 minutes.
This will reset the battery calculation

andybones said:
This may help to reset battery to show correctly, to flash RUU.
Switch off the device.
Then push and hold all three buttons (power / volume up / volume down) for approximately 1-2 minutes.
This will reset the battery calculation
Click to expand...
Click to collapse
I'll give it a try. Thank you

andybones said:
This may help to reset battery to show correctly, to flash RUU.
Switch off the device.
Then push and hold all three buttons (power / volume up / volume down) for approximately 1-2 minutes.
This will reset the battery calculation
Click to expand...
Click to collapse
Nope.. Didn't change anything..
I think I should mention I've been trying both the ruu.zip and the ruu.exe. And both sdcard and fastboot methods.. All the while not being able to get into download mode. The splash screen (black background / white htc logo) appears for both download and recovery modes, but go back to system splash screen bootloop.. So I don't even know if I can ruu since I can't even get into download mode..
And also, I get the 30% battery error from the exe started while in bootloader mode since I can't get into any other mode - which might be the reason for the error..
Edit: words are hard