Develop Bugs

HDC Desire HD does not start up. Cant access recovery after volume buttons are broken

Hello XDA experts,
I own a HTC Desire HD with ?CM 10? flashed on. Now suddenly the phone cant get over the boot screen (it worked in the past). It shows the loading screen and nothing happens. The CM loading screen spin all the time. I have a recovery thing installed, over that I flashed all kind of roms in the past. My problem is, I cant access this menu after the volume up and down buttons are broken now. Is it possible to get into this recovery menu in another way. May attache the device to my Mac and load something by the terminal?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The logo spin all the time and do nothing

maglat said:
Hello XDA experts,
I own a HTC Desire HD with ?CM 10? flashed on. Now suddenly the phone cant get over the boot screen (it worked in the past). It shows the loading screen and nothing happens. The CM loading screen spin all the time. I have a recovery thing installed, over that I flashed all kind of roms in the past. My problem is, I cant access this menu after the volume up and down buttons are broken now. Is it possible to get into this recovery menu in another way. May attache the device to my Mac and load something by the terminal?
Click to expand...
Click to collapse
I tried to enter recovery by adb "./adb reboot recovery" but this does not work either after the desire isn't recognized by my mac.

maglat said:
Hello XDA experts,
I own a HTC Desire HD with ?CM 10? flashed on. Now suddenly the phone cant get over the boot screen (it worked in the past). It shows the loading screen and nothing happens. The CM loading screen spin all the time. I have a recovery thing installed, over that I flashed all kind of roms in the past. My problem is, I cant access this menu after the volume up and down buttons are broken now. Is it possible to get into this recovery menu in another way. May attache the device to my Mac and load something by the terminal?
Click to expand...
Click to collapse
been through same **** man ...In my case i take out that volume button by any tools my phone in without volume button but volume slot can be operated by pencil or pen ...:victory:
i can use it that way dont know it will work for you or not u can go to bootloader by adb but dont know anyfurther how to choose options ....can feel yr pain

maglat said:
Hello XDA experts,
I own a HTC Desire HD with ?CM 10? flashed on. Now suddenly the phone cant get over the boot screen (it worked in the past). It shows the loading screen and nothing happens. The CM loading screen spin all the time. I have a recovery thing installed, over that I flashed all kind of roms in the past. My problem is, I cant access this menu after the volume up and down buttons are broken now. Is it possible to get into this recovery menu in another way. May attache the device to my Mac and load something by the terminal?
The logo spin all the time and do nothing
Click to expand...
Click to collapse
Remove the battery and re-insert it. Now Connect it to ur mac. Dont press the power button. As soon as the charging lights come on, type
Code:
./adb devices
Your phone should show as 924ffy8289292 recovery
then type
Code:
./adb reboot recovery
And you are there.
Pls use the thanks button if i have helped you.

mickeyasamoah said:
Remove the battery and re-insert it. Now Connect it to ur mac. Dont press the power button. As soon as the charging lights come on, type
Code:
./adb devices
Your phone should show as 924ffy8289292 recovery
then type
Code:
./adb reboot recovery
And you are there.
Pls use the thanks button if i have helped you.
Click to expand...
Click to collapse
YOU ARE MY HERO! :highfive: Many thanks! It worked! I now flashed the latest CM11 and my Desire is back on track! :good::laugh:

maglat said:
YOU ARE MY HERO! :highfive: Many thanks! It worked! I now flashed the latest CM11 and my Desire is back on track! :good::laugh:
Click to expand...
Click to collapse
You welcome. Thats what XDA is all about sharing. But use the thanks button instead of only saying thanks.

Stuck on 'Android is upgrading... Starting Apps'. HELP

Okay let me run through a couple of scenarios so that we can understand the main issue here. I flashed my i9250 GNEX phone with the linaro OMNI Metal's new update.... with a broken volume up button manually through CWM. Upon rebooting, the phone shows the starting logo and then gets to the updates eventually ending up with the: 'Android is upgrading... Starting Apps' screen. It's stuck there and I do not know what to do next.
I went to the shop to try and fix the volume button but for some reason I could not get into the recovery by holding the vol up, vol down + pwr button. THEY MIGHT HAVE NOT FIXED IT, but then again... how we're they going to test it anyways when the phone can't even boot up right?
They told me to sideload adb and flash the original stock image using a micro usb (they have this microusb that gets the phone to the download screen) so get to the update/download screen -> but I do not have that USB that allows me to do that now...
Any ideas on how I can revive this phone?? It's really a good phone and though I have the Nexus 5 now.. I still think about the Galaxy Nexus a lot... =/
Please help me T_T
:crying:

I understand your frustration, this happened to me a couple months ago after doing a custom update. I don't remember the exact solution, but I have some solid ideas. First we have to get into recovery.
Hold volume up + volume down + power to do this. (Using one volume and power just goes to Odin download mode / last resort of last resorts)
When you're in recovery, do a nandroid backup since well be trying a bunch of stuff, permission fixing, formatting.
After a nandroid try:
-fix permissions through recovery
-wipe cache and dalvik cache through recovery
If those don't boot you, try wiping data (NOT sdcard). If this doesn't work the problem is what's installed to /system..and we'll go from here.
We need to get into recovery first and sequentially try the things I listed. Let me know if this is now possible.

7175 said:
I understand your frustration, this happened to me a couple months ago after doing a custom update. I don't remember the exact solution, but I have some solid ideas. First we have to get into recovery.
Hold volume up + volume down + power to do this. (Using one volume and power just goes to Odin download mode / last resort of last resorts)
When you're in recovery, do a nandroid backup since well be trying a bunch of stuff, permission fixing, formatting.
After a nandroid try:
-fix permissions through recovery
-wipe cache and dalvik cache through recovery
If those don't boot you, try wiping data (NOT sdcard). If this doesn't work the problem is what's installed to /system..and we'll go from here.
We need to get into recovery first and sequentially try the things I listed. Let me know if this is now possible.
Click to expand...
Click to collapse
Sorry I forgot to mention that I can't boot into recovery using [vol up, down + pwr button] (sorry i didn't include vol down before) as my power up volume rocker is broken and not functioning. I just need to be able to get into recovery but not possible with the up rocker not functioning.
Is there any other way to get through to recovery by side loading? The phone can't get past the android is upgrading screen... so, I'm lost.

shencez said:
Sorry I forgot to mention that I can't boot into recovery using [vol up, down + pwr button] (sorry i didn't include vol down before) as my power up volume rocker is broken and not functioning. I just need to be able to get into recovery but not possible with the up rocker not functioning.
Is there any other way to get through to recovery by side loading? The phone can't get past the android is upgrading screen... so, I'm lost.
Click to expand...
Click to collapse
OK that makes sense, sorry I must have missed that. Have you tried booting the phone in safe mode? To do this, turn the phone off, then hold power to turn it on. Once you see the Google logo press and hold "volume down" until the phone has fully booted. Once the phone is booted, you will see the "safe mode" logo and can stop holding "volume down." If one of your apps in /data is causing the boot issue, this will get you into Android.
I see in the first post that you don't have a USB cable to attach to a computer? If this is true, we won't be able to adb, fastboot, or Odin download to push a ROM to the phone. Most people have this cable since it also attaches to a usb wall charger. Without it, there's maybe one last sketchy thing we can try, which would be to take the phone apart and electrically short the volume buttons to get into recovery. Even though the volume button is broken, the connection is still definitely there. The button just doesn't work or is disconnected.
Let us know if the safe mode gets you booted and whether or not you have a USB cable to connect your phone to a computer. I just want to double check about the cable cause if you don't have it. Our last resort attempt would be to short the broken volume button.

7175 said:
OK that makes sense, sorry I must have missed that. Have you tried booting the phone in safe mode? To do this, turn the phone off, then hold power to turn it on. Once you see the Google logo press and hold "volume down" until the phone has fully booted. Once the phone is booted, you will see the "safe mode" logo and can stop holding "volume down." If one of your apps in /data is causing the boot issue, this will get you into Android.
I see in the first post that you don't have a USB cable to attach to a computer? If this is true, we won't be able to adb, fastboot, or Odin download to push a ROM to the phone. Most people have this cable since it also attaches to a usb wall charger. Without it, there's maybe one last sketchy thing we can try, which would be to take the phone apart and electrically short the volume buttons to get into recovery. Even though the volume button is broken, the connection is still definitely there. The button just doesn't work or is disconnected.
Let us know if the safe mode gets you booted and whether or not you have a USB cable to connect your phone to a computer. I just want to double check about the cable cause if you don't have it. Our last resort attempt would be to short the broken volume button.
Click to expand...
Click to collapse
Thanks for your reply once again, I tried what you said about holding the vol down button once I see the google logo. However, the animation screen just comes up and goes back to Android is upgrading... optimizing apps 1 of 1.. starting apps... then it stops there as usual.
The USB i was referring to was the USB dongle which is similar to the ones like the hdmi cable. I have the usb cable for connecting to pc and may have to try the adb way to resolve the issue. Any steps on what I could do at this point? I've never flashed via adb in this situation so I may need some guidance.
Once again, thanks for you help very much appreciated.
UPDATE: I tried ADB REBOOT RECOVERY and I ended up with this error message. Attached is the photo to see it. 'error: device unauthorized. Please check the confirmation dialog n your device.'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update II: http://forum.xda-developers.com/showthread.php?t=2522401
This thread... I finally found what I need. a USB JIG. Where can I find these???

Sorry for the late reply, but glad you found a good thread link to this problem. I'm not sure what that guy means by USB jig, but I'm guessing he rigged up something to short out "volume down" when powering it on thereby getting to Odin mode. If you can get into Odin mode, by pressing "volume down" and "power", you won't need to do this. Let us know if you can get there. You'll see "Odin mode" in tiny red letters in the upper left corner.
Here's a good walkthrough (w/ mysid and yakju ICS images): http://www.inspiredgeek.com/2011/12...d-cf-root-insecure-kernels-step-by-step-guide
Maguro Odin Firmware Images:
takju: https://dl.google.com/dl/android/aosp/takju-jwr66v-factory-c2ef855e.tgz
yakju: https://dl.google.com/dl/android/aosp/yakju-jwr66v-factory-ad817ccc.tgz
(Here's another one in case: http://androidadvices.com/update-galaxy-nexus-official-ics-404-firmware-odin/2
..and also... http://www.theandroidsoul.com/update-galaxy-nexus-to-android-4-0-4-using-odindownload-mode)
Make sure you download and flash the right firmware image. International devices aka (maguro) use "yakju" and the USA ones like (toro,toroplus) use "mysid", I think "takju" is for engineer samples. By flashing this you'll temporarily downgrade back to 4.3, but then you can boot, download a new ROM. Forewarning, this will reformat the entire device but is probably the last reasonable option at this point.

Update to original problem: 'System hangs at the end of boot sequence when it says "starting apps" or "finishing boot".'
I ran into this problem finally, again, and I'm pretty sure that what's causing it are incorrect/misconfigured permissions on the /data/data/* directories for each data app. This is likely caused by dirty flash upgrading or incorrectly fixing the permissions. TWRP "fix permissions" might cause this too or fix the problem, seems like a gamble each time, so use with caution as a last resort attempt to fix a non booting android with this problem.
The best thing to do is restore the /data partition from a previous back up point. There's no easy fix for this, but there is a script you can run to try and reset the permissions and fix the "end of boot hang" issue. It's similar to the one TWRP uses.

7175 said:
Update to original problem: 'System hangs at the end of boot sequence when it says "starting apps" or "finishing boot".'
I ran into this problem finally, again, and I'm pretty sure that what's causing it are incorrect/misconfigured permissions on the /data/data/* directories for each data app. This is likely caused by dirty flash upgrading or incorrectly fixing the permissions. TWRP "fix permissions" might cause this too or fix the problem, seems like a gamble each time, so use with caution as a last resort attempt to fix a non booting android with this problem.
The best thing to do is restore the /data partition from a previous back up point. There's no easy fix for this, but there is a script you can run to try and reset the permissions and fix the "end of boot hang" issue. It's similar to the one TWRP uses.
Click to expand...
Click to collapse
How do I use this? Sorry. I probably need some steps for this :|

Hi shencez, does your problem still persist with the boot hanging? If only you could get to adb, we could totally fix this.
Anyway, for anybody wanting to run this, here's generally what to do:
The script needs to be downloaded or pushed via adb to android:
> adb push "windows or Linux path to file" "path_to_android_directory"
(e.g.: adb push C:\fix_permissions /fix_permissions)
Then make sure it's executable with:
> busybox chmod +rx
/path_to_android_directory/fix_permissions
(e.g.: busybox chmod +rx /fix_permissions)
The script uses /sbin/sh, so make sure that exists or do:
> cp -a /system/bin/mksh /sbin/sh
Execution:
> /path_to_android_directory/fix_permissions
(e.g.: /fix_permissions)
You should get an output like this:
./fix_permissions.sh 2.04 started at 08-10-2014 13:01:04
./fix_permissions.sh 2.04 ended at 08-10-2014 13:01:04 (Runtime:0m0s)

Hi i have same problem with samsung galaxy s6 it stuck with rotating gears i already posted this in a few places so hope so someone can help
Thanks in advance

I think busybox problem, trying to restore and stuck somewhere, best is flash official rom

hey i have the same problem. My galaxy s4 goes into an infinite boot cycle at the "android is upgrading optimizing apps" screen. Every so often it will finish the boot and go to the lockscreen but I can't remember my pin code After it gets to the lockscreen for 10 seconds it turns off and goes back into its infinite boot cycle. Please help me solve this problem! P.S I can't boot into safe mode for some reason. Whenever I try to the phone turns off before it boots.

Without working volume+ button you can flash stock using Odin. To boot in odin mode press power and volume - button.

Hey i know its late but
7175 said:
Hi shencez, does your problem still persist with the boot hanging? If only you could get to adb, we could totally fix this.
Anyway, for anybody wanting to run this, here's generally what to do:
The script needs to be downloaded or pushed via adb to android:
> adb push "windows or Linux path to file" "path_to_android_directory"
(e.g.: adb push C:\fix_permissions /fix_permissions)
Then make sure it's executable with:
> busybox chmod +rx
/path_to_android_directory/fix_permissions
(e.g.: busybox chmod +rx /fix_permissions)
The script uses /sbin/sh, so make sure that exists or do:
> cp -a /system/bin/mksh /sbin/sh
Execution:
> /path_to_android_directory/fix_permissions
(e.g.: /fix_permissions)
You should get an output like this:
./fix_permissions.sh 2.04 started at 08-10-2014 13:01:04
./fix_permissions.sh 2.04 ended at 08-10-2014 13:01:04 (Runtime:0m0s)
Click to expand...
Click to collapse
hey I know this is late but my note 4 keeps starting and saying android is upgrading optimizing apps 1 of 17 and gets stuck at 5 or any other number and restarts and some times it just completely turns of and I was wondering if their is a fix for this and I tried everything I could think of and also tried everything I found on the internet but it just wont work. Thank you in advance

Thanks a lot 7175! ))))))))
i ran into the same issue with a HTC Desire 10 pro and tried the recovery mode and it brought the device back to the normal home screen. Thnkxxxx
7175 said:
I understand your frustration, this happened to me a couple months ago after doing a custom update. I don't remember the exact solution, but I have some solid ideas. First we have to get into recovery.
Hold volume up + volume down + power to do this. (Using one volume and power just goes to Odin download mode / last resort of last resorts)
When you're in recovery, do a nandroid backup since well be trying a bunch of stuff, permission fixing, formatting.
After a nandroid try:
-fix permissions through recovery
-wipe cache and dalvik cache through recovery
If those don't boot you, try wiping data (NOT sdcard). If this doesn't work the problem is what's installed to /system..and we'll go from here.
We need to get into recovery first and sequentially try the things I listed. Let me know if this is now possible.
Click to expand...
Click to collapse

Blue light of death?

Tonight I was playing around with my new Nexus 5X, then it suddenly rebooted. First it was kinda in a bootloop, it booted till the animated google logo, then the animation stopped and after a second it rebooted again. This happened a few times by itself (I was unable to switch the phone off, it just started over again and again) until during a new reboot the LED illuminated blue permanently and this screen appeared:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that I could switch the phone off, but couldn't turn it on again, even not by holding the power button for more than 10 seconds. The screen just leaves blank, no boot image, no LED, no sign of life anymore. :crying: I also tried removing sim-card, charging, nothing works...
I received my Nexus two days ago. First of all I unlocked the bootloader, decrypted the data partition and rooted it. All worked fine until tonight...
Well, I already wrote the Google support. I hope the warranty is still valid? Does anybody else probably have another idea?

What was the root method?
Sent from my Nexus 5X using Tapatalk

I used Chainfire's systemless root (bullhead-mdb08i-boot-systemless.zip) on MDB08M.

If you can still get into the bootloader, you have to reflash the boot.img, the ramdisk of the boot image permissions got changed somehow. I got the same message when I flashed a boot.img with a bad ramdisk permissions.

You say you can turn it off but not on. Can you access the bootloader? Turn phone off, hold volume down + power button until you see the android lying on his back with his hatch open?
If you can, I'd try flashing factory images and start fresh.
Sent from my Nexus 5X using Tapatalk

No way to access the bootloader.
I guess I need a fix like this: http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
When I connect the phone to my PC and hold the power button for 10 secs a new device is listed in the device manager "QHSUSB_BULK". However the screen is still completly off.

Koboldchen said:
No way to access the bootloader.
I guess I need a fix like this: http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
When I connect the phone to my PC and hold the power button for 10 secs a new device is listed in the device manager "QHSUSB_BULK". However the screen is still completly off.
Click to expand...
Click to collapse
1) Tell me what you can do exactly with the phone (bootloader,recovery,reboot,etc) and the reactions i.e vibrates while starting or something else
2) Your pc recognizes the phone, even if its the qualcom (I guess) and thats good
3) I'm pretty sure, that there is a way to fix it somehoe
Gesendet von meinem SM-N920C mit Tapatalk

I got that same exact screen when I was trying to flash the vendor. img and the way I got out of it was by holding the volume up and the power button and got me into this download mode which was asking me to flash firmware so I keep holding the volume down button and the power button for a long time and finally if we booted into the ROM again I hope that helped

tlopez1973 said:
I got that same exact screen when I was trying to flash the vendor. img and the way I got out of it was by holding the volume up and the power button and got me into this download mode which was asking me to flash firmware so I keep holding the volume down button and the power button for a long time and finally if we booted into the ROM again I hope that helped
Click to expand...
Click to collapse
I can't get into the bootloader at all, neither with holding volume down + power nor with volume up + power (and also with volume down + up + power). The screen just leaves black with no backlight.
Mucky2 said:
1) Tell me what you can do exactly with the phone (bootloader,recovery,reboot,etc) and the reactions i.e vibrates while starting or something else
2) Your pc recognizes the phone, even if its the qualcom (I guess) and thats good
3) I'm pretty sure, that there is a way to fix it somehoe
Click to expand...
Click to collapse
Right now I can't do anything. There are no reactions, no vibrations, no LED, no screen... Yesterday I could at least get into the qualcomm-mode while holding down the power-button for 10 seconds and have the phone connected to my PC. Yesterday evening as I was trying again to get into the bootloader the LED just flashed red shortly and nothing else happened (even not the qualcomm-boatloader was accessible). I charged the phone overnight, but it still does nothing. It looks like the Nexus is really dead now.
I still wonder what happened. As I wrote I could use the phone two days long with no problems. Then it crashed/rebooted itself, I saw that screen I attached into my first post and blue light, yesterday I could at least get into the qualcomm-mode and now (after that red LED flash) really nothing works anymore.
Till Monday I'll keep watching and testing since I can't send it back on weekends. But I'm afraid that I have to get it fixed by Google/LG. Thanks for your help anyways, fortunately I still have my Nexus 4...

Some news: I can access the google bootloader again.
Whyever, during this day the phone became discharged completely again (red LED flashed by pressing the power button), but this time I charged it only for a few minutes... After this I held volume down + power and the LED was blue again and the screen was the same like the screenshot I posted. I held power to switch off the phone and next volume down + power for 10 sec immediately again. This time the bootloader was shown.
So I restored the stock image completely:
Code:
fastboot flash bootloader bootloader-bullhead-bhz10i.img
fastboot reboot-bootloader
fastboot flash radio radio-bullhead-m8994f-2.6.28.0.65.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot format userdata
fastboot reboot
The only thing I didn't do was relocking the bootloader.
All went fine, however, the phone still crashes upon reboot and switches off itself. I did another factory reset via recovery which didn't help. After a restart I usually get back to the blue-LED-thing, but like described above I can access the bootloader again.
So I guess something else is corrupted. Even when I use TWRP instead of stock recovery it crashes after a few seconds after use. What else differs: By holding volume down + power the bootloader doesn't appear immediately, I need to hold for about 10 seconds.
Any ideas?

m8 stuck in hboot and safe mode - fastboot not working but managed to get adb to reco

hi guys im having a problem here and would greatly appreciate some help. I have already installed android platform tools and the htc usb drivers. The phone will start in hboot only but will not go to fastboot (power button will not activate fastboot). The pc does not recognize the device either so cant use fastboot commands. Power button + vol up will boot to safe mode but then the os starts acting crazy with the touchscreen being activated all over the place (very annoying). while in safe mode, adb devices command shows that it recognizes the phone but also says unauthorized. What the heck can i do here to get this phone operational again?

What is the history of the device? Was it broken when you got it? Was there any problem with the power button before it started having these problems (only boots to bootloader or safe mode)?

Hey thanks for replying. I got the device new from att around 4 or 5 years ago and have had no problems out of it aside from a badly cracked screen which i replaced myself about 8 months ago. All of the buttons have always worked just fine.
I forgot to mention I unlocked the phone through htc website about 3 years ago and planned on rooting and modding the phone but never got around to it. I can't quite remember if I flashed a custom recovery though. I should also mention the phone got wet before all this started happening (not submerged kind of wet just rained on some )
So I'm assuming ADB sees the device as unauthorized because I'm unable to select OK when the debugging window pops up on the phone. This is due to the OK button being in a dead zone on the touch screen. This zone is the middle half of the screen top to bottom. I'm hoping it's just corrupted firmware and not a physical hardware issue as I mentioned earlier I have already replaced the screen once already.
As for fastboot not recognizing the device, I'm starting to think it's because of this older mini laptop I'm having to use as a backup because my good laptop is being loaned out to someone for a while longer. This mini laptop has 3 usb ports on it but all I believe are usb 1.1 (LOL!). Does fastboot require usb 2.0 or higher to work properly? The phone is visible in Device Manager (both internal and external storage), and I'm able to move files around no problem.
Also, does the sim card have to be in the phone in order to fix the firmware and os? I have the sim in a very basic flip phone right now just so I can make and recieve calls! I need my M8 back badly!
I'm assuming since the phone will actually get to hboot and will also boot into safe mode that this phone is recoverable ie. not bricked. I just need help with doing everything in the right order , so I dont end up doing something very wrong and rendering the device useless. Again thanks for replying and any help you might be able to give would be greatly appreciated!

My responses below in red font:
brokenm8 said:
I should also mention the phone got wet before all this started happening (not submerged kind of wet just rained on some )
Not clear on what you are telling us here. Are you saying that the current condition (stuck in hboot/safe mode) happen directly after it getting wet? Is so, then it would be pretty clear to me, that it is a hardware issue caused by water damage.
So I'm assuming ADB sees the device as unauthorized because I'm unable to select OK when the debugging window pops up on the phone.
You need debugging selected in phone Settings>Developer Options, as well as being able to "OK" the debugging connection request when you are connected to PC. Failing to do either of those, will prevent adb from being used. But I'm not clear on what adb command you want to use. Fastboot and adb should be thought of as 2 related, but different things. For recovering a phone in your condition, fastboot is the one you want.
As for fastboot not recognizing the device, I'm starting to think it's because of this older mini laptop I'm having to use as a backup because my good laptop is being loaned out to someone for a while longer. This mini laptop has 3 usb ports on it but all I believe are usb 1.1 (LOL!). Does fastboot require usb 2.0 or higher to work properly? The phone is visible in Device Manager (both internal and external storage), and I'm able to move files around no problem.
I don't remember USB 1.1 being an issue with adb/fastboot. In fact, it's probably more compatible then USB 3.0, which is known to cause issue with some of the HTC tools. I think I was using an old PC with Windows XP on it, when I first got my M8 (although not sure what type USB ports).
More important, is that fastboot will only work when fastboot mode selected while in bootloader (highlighted in red near the top of the screen). From what I remember, it goes to fastboot mode by default, if you boot into bootloader while the phone is connected to a PC. If not, and you can't select fastboot with the power button, than that is a problem
Also, does the sim card have to be in the phone in order to fix the firmware and os?
SIM card is not needed to fix the OS.
I'm assuming since the phone will actually get to hboot and will also boot into safe mode that this phone is recoverable ie. not bricked. I just need help with doing everything in the right order , so I dont end up doing something very wrong and rendering the device useless.
If the phone is s-on, there isn't much you can do, that is not reversible, or will make the condition worse. But as you said, it's best to follow specific instructions as we give them to you.
Click to expand...
Click to collapse

Not clear on what you are telling us here. Are you saying that the current condition (stuck in hboot/safe mode) happen directly after it getting wet? Is so, then it would be pretty clear to me, that it is a hardware issue caused by water damage.
Click to expand...
Click to collapse
Yes the current condition happened directly after getting wet.
More important, is that fastboot will only work when fastboot mode selected while in bootloader (highlighted in red near the top of the screen). From what I remember, it goes to fastboot mode by default, if you boot into bootloader while the phone is connected to a PC. If not, and you can't select fastboot with the power button, than that is a problem
Click to expand...
Click to collapse
Mine doesn't go into fastboot by default when booted into bootloader while connected to PC. While at the HBOOT main screen, Fastboot is at the top of the list of options available to select followed by Recovery, Factory Reset, etc... The power button does not activate any of the options in HBOOT but it works just fine to power the phone on or off and in combination with the Vol Up button to boot the OS which always goes into safemode. However, the Vol Down button doesn't work anywhere. This seems to indicate to me that HBOOT and/or the firmware might be corrupted? As I mentioned earlier, I am able to move files around with no problem. Pretty sure I can't put a RUU into the root directory and fix this because I'm unable to relock the bootloader due to fastboot not working right? If so, is there a way to load/flash a good copy of HBOOT and/or firmware to the phone via my sd card?

brokenm8 said:
However, the Vol Down button doesn't work anywhere. This seems to indicate to me that HBOOT and/or the firmware might be corrupted?
Click to expand...
Click to collapse
I'd say that is a big leap of logic, and probably not a correct one. Hboot is required for the very basic functioning of the phone. Hboot corruption usually equals hard brick (screen won't even come on).
I'd say it's more likely the water damage caused hardware failure of the vol down button.
brokenm8 said:
Pretty sure I can't put a RUU into the root directory and fix this because I'm unable to relock the bootloader due to fastboot not working right? If so, is there a way to load/flash a good copy of HBOOT and/or firmware to the phone via my sd card?
Click to expand...
Click to collapse
You can only flash RUU or firmware with an unlocked bootloader, if the device is s-off.
You also can't flash hboot separately unless you have s-off. You can flash firmware, which contains hboot. But again, unless you have s-off or can relock the bootloader, you can't flash firmware.

Hi there
I got the same exact problem with my m8. At the screen telling : s-on, locked..., the power button and the vol down button are not working, the vol up button is scrolling down instead of scrolling up. It appears that I am stuck in Hboot only I can't use fastboot or any other option. This is the second time I am facing that problem. The first time, I have replaced the motherboard, but since then I didn't flash any rom or done any mod on my htc and here I am now with the same mess.

Glasskeramika said:
I got the same exact problem with my m8.
Click to expand...
Click to collapse
Did you drop it in water, like the OP?
I would suggest anyone refrain from saying you have the "exact same problem" on this forum. I've seen that phrase (or similar) posted dozens (probably hundreds) of times. And not once, have I found (after digging for details) that statement to actually be true. Way too many variables in phone versions, software, what was done to it, etc.
Your time is much better spent giving specific details on the phone, and letter us go from there.

I did not drop in the water.
It went off after battery fully drained. When I tried to turn it on after I plugged it in my computer to charge it, the screen in the attachment showed off. It does show options like fastboot, recovery..etc, but I can't select any of them : the power button (on that screen) doesn't work but it does turn on my phone, the volume down button doesn't work at all (neither on safe mode nor on the attached screen). The vol up button works good when it's running on safe mode, but it plays the role of the vol down button once on that screen (it scrolls down instead of scrolling up).
I need to mention that I had that problem (the same exact haha) two years ago when I rooted my htc m8. Everything was just fine till one day, my phone suddenly started lagging a lot. When I tried to reboot it, that famous screen showed off. I took it to a guy who has replaced the motherboard :crying:. The phone was doing good, I didn't mod anything or rooted it, but it wasn't recognizing the second camera (once on the htc's camera app, it says that my finger is hiding the second camera). But everything was all good for about 1 year, till I got that problem again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 08:09 AM ---------- Previous post was at 07:54 AM ----------
Glasskeramika said:
I did not drop in the water.
It went off after battery fully drained. When I tried to turn it on after I plugged it in my computer to charge it, the screen in the attachment showed off. It does show options like fastboot, recovery..etc, but I can't select any of them : the power button (on that screen) doesn't work but it does turn on my phone, the volume down button doesn't work at all (neither on safe mode nor on the attached screen). The vol up button works good when it's running on safe mode, but it plays the role of the vol down button once on that screen (it scrolls down instead of scrolling up).
I need to mention that I had that problem (the same exact haha) two years ago when I rooted my htc m8. Everything was just fine till one day, my phone suddenly started lagging a lot. When I tried to reboot it, that famous screen showed off. I took it to a guy who has replaced the motherboard :crying:. The phone was doing good, I didn't mod anything or rooted it, but it wasn't recognizing the second camera (once on the htc's camera app, it says that my finger is hiding the second camera). But everything was all good for about 1 year, till I got that problem again.
Click to expand...
Click to collapse
Link (remove all space, please) to the mentioned screen : https: // imgur. com/a/yPY Z4rX
(The image doesn't appear in the previous post that I couldn't edit, oh yeah spam )

Stuck in a bootloop but can't go into recovery and phone isn't recognized by pc.

Ok, so this is my first phone without a removable battery so very new in terms of fixing bootloops. I just have to deplete the battery because I can't turn off the phone in said bootloop, and also when I plug the charger it goes into loop again...
So anyways, it's very sketchy but 1 out of 20 power-ons I can get it into bootloader/fastboot? but I can't get adb or MiFlash tool to recognize the phone. So for now it's a brick. Is there any way to fix this? My phone has unlocked bootloader and had pixel experience 9, and it was years ago since I did all the romming so I don't have the old files nor the old drivers because of fresh Windows install.
Looking forward for your answers.

How did you get in bootloop in the first place? Did you try to boot to the recovery using volume up and power button?

Phone used to freeze and reboot lately because of high ram and storage usage (like 2gb free) I think. Or could be an entirely different thing but I didn't mess with system level apps in a long time. Just that in one of these freezes it never finished booting up.
I tried the recovery but it freezes before I can get to the menu. I have TWRP by the way.

Fedegblack said:
Phone used to freeze and reboot lately because of high ram and storage usage (like 2gb free) I think. Or could be an entirely different thing but I didn't mess with system level apps in a long time. Just that in one of these freezes it never finished booting up.
I tried the recovery but it freezes before I can get to the menu. I have TWRP by the way.
Click to expand...
Click to collapse
When the phone is turned off press first the volume up and while holding it press the power button. After phone vibrates release the power button but still keep the volume up button pressed and wait until twrp starts. If it gets stuck again tell where exactly.

I think I managed to understand how f'd up it was. The phone freezes even in Fastboot mode, I just didn't realize it and it was the reason it didn't get detected by the pc. Seems like I have few windows of time where it detects the phone and button inputs, but mostly freezes where it likes and can't do anything until battery drains. And then charging makes it go into loop again.
I'm tempted to take advantage of the phone being recognized and flash something into it. Maybe boot.img or twrp.img, what are your thoughts on this?

Fedegblack said:
I think I managed to understand how f'd up it was. The phone freezes even in Fastboot mode, I just didn't realize it and it was the reason it didn't get detected by the pc. Seems like I have few windows of time where it detects the phone and button inputs, but mostly freezes where it likes and can't do anything until battery drains. And then charging makes it go into loop again.
I'm tempted to take advantage of the phone being recognized and flash something into it. Maybe boot.img or twrp.img, what are your thoughts on this?
Click to expand...
Click to collapse
If USB debugging is working you can try to flash twrp or even fastboot rom with MiFlash.

Ok, tried to flash twrp but it says write protected, so I did "fastboot boot twrp.img" but freezes in the same place as my old twrp. Seems likely I have to flash stock now.
Edit: On second thought I might be able to do something else now, even if it freezes before the twrp menu it's showing with "adb devices" instead of "fastboot devices" so I will try dirty flashing what I think is the same rom as before.
Also, if it's likely this issue with twrp I will be sad. I have no idea when my internal memory got encrypted since it was one of the first things I didn't want when I first romed this.

Welp, after days of trying to enter fastboot again I find myself with this problem.
Spoiler: Image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried fastboot -w or flashing twrp and orangefox recoveries but same ol' same ol'. Write protection error, it's likely to be hardware issues, but I'm open to suggestions.

Your Odyssey might have an end!
Try to flash the factory rom instead, the one that came with the device, not the most recent one!
I'll guarantee it will work!
I also would try OrangeFox recovery if I was you... way better then twrp. Both my devices have OF as recovery.
Note 5 Pro and Note 8T. My willow have Carbon OS on it but I'm not using it since it only serves as a backup device, in worst case scenario...