HTC One M8 Stuck on Bootloader - One (M8) Q&A, Help & Troubleshooting

I was going thru the process of updating the Windows Phone 8.1 to 10. I had just started the device in bootloader and plugged it in to the computer (running Windows 10). The Windows Device Recovery Tool doesn't recognize the device.. HTC Synch Manager doesn't recognize the device. I've updated the drivers, still nothing. Now the device is on the bootloader screen and I cannot get it to restart or anything. HELP????

This forum section is specific to the Android version M8. I'm not sure if too many (or any) folks here are that familiar with the Windows Phone version. You may get better (device specific) help on the "M8 for Windows" device section:
https://forum.xda-developers.com/one-m8-windows

Related

[Q] ADB no devices found please help

I recently got an insurance replacement for my HTC ONE M8, I converted my (original) HTC one m8 into a GPE w/ OTA.
Now with the replacement I want to again change it to a GPE but I am unable to unlock the device I have platform tools from the HTC Developer. It recognizes the devices when it is on and fully booted up but when I use ADB reboot bootloader to reboot the device it no longer shows on adb device list once booted to fastboot. I have tried booting the device manually (power+Volume down) and then connecting through usb and again adb can not see it.
Just to clarify I am trying to unlock the device I do not have s off or the unlock token, the device is completely stock as of right now
The usb ports on my laptop are 2.0 I used this same laptop to convert the my original htc one m8 to gpe
Please help
I had a similar problem with my nexus 7 (2012) at one point. I had to update the Android SDK to the latest version because something had changed in the way the device talked to the computer with adb. Under SDK>Tools you will find a file called "android" that opens the SDK through terminal so you can take updates.

Can't unlock bootloader

Hi folks, Trying to unlock my bootloader with no luck. Registered with HTCDev, downloaded Android SDK, JRE, and HTC Sync Manager. Boot into bootloader mode and connect to the computer via USB. Opening CMD, I can't seem to get the computer to find the device, and therefore can't execute the command to unlock the bootloader.
It is a Sprint HTC One M9 running Android 5.0.2, stock. Computer is Windows 7 x64-based Lenovo. Both are up to date. I've noticed that the device can sync with HTC Sync Manager and is recognized in file explorer when it is attached as a portable media device. It is not seen by the computer when mounted as a disk drive. HTCDev instructions didn't specify whether USB Debugging needed to be turned on or not, but flipping it on and off didn't seem to matter. Device Manager on my computer says that I have the driver for the phone is working properly.
Any thoughts would be greatly appreciated!!!
IncredibleHulk6 said:
Hi folks, Trying to unlock my bootloader with no luck. Registered with HTCDev, downloaded Android SDK, JRE, and HTC Sync Manager. Boot into bootloader mode and connect to the computer via USB. Opening CMD, I can't seem to get the computer to find the device, and therefore can't execute the command to unlock the bootloader.
It is a Sprint HTC One M9 running Android 5.0.2, stock. Computer is Windows 7 x64-based Lenovo. Both are up to date. I've noticed that the device can sync with HTC Sync Manager and is recognized in file explorer when it is attached as a portable media device. It is not seen by the computer when mounted as a disk drive. HTCDev instructions didn't specify whether USB Debugging needed to be turned on or not, but flipping it on and off didn't seem to matter. Device Manager on my computer says that I have the driver for the phone is working properly.
Any thoughts would be greatly appreciated!!!
Click to expand...
Click to collapse
Delete the sync manager. Don't ask me how or why but it interferes with the SDK so that your PC cannot recognize your phone properly.
also you have to download the BMP x64 and a complete platform tools folder ...you may want to check my personal backup here: https://drive.google.com/drive/fold...RSdGJTVnVhQTJQZUZiMG5uRWl0blNackNWMVU1NUNoVjg
Thanks guys... I'm at work and won't have the ability to check these out until later, but I'll keep you posted
It worked! Thanks guys
astboot command in bootloader screen gives error FAILED (remote: cannot flash this partition in s-on state)
please someone help to solve this problem.
Bootloader
Blue blank screen
This screen comes every time and reset htc logo and then same blue screen
any body can help me

adb/fastboot not working

I finally got around to trying to install a custom recovery and root my HTC M8 (Verizon, KitKat 4.4.4).
I had previously unlocked my phone with SunShine - and have S-Off.
I tried installing adb/fastboot/drivers downloading from this thread:
http://forum.xda-developers.com/showpost.php?p=48915118
On my phone I turned off fastboot, enabled developer mode, and enabled USB debugging.
I connect my phone, it says USB debugging connected - and my PC (Windows 7) recognized the device.
However, when I try fastboot devices it does not recognize my phone - it returns nothing.
I realized that I had previous versions of adb/fastboot installed on my PC (From HTC Syanc & the WugFresh Nexus toolkit). I uninstalled them and reinstalled the drivers from that link, but still no adb/fastboot.
One thing I noticed is that (unlike the tutorial video on the link) in Device Manager my phone is not recognized under Other devices/ADB interface, but rather appears under Android USB devices / My HTC. I tried following the tutorial and tried to update the driver software, but it was not possible to use the downloaded Google drivers.
I tried unistalling the My HTC driver. The phone then appears for time under Other Devices / Android phone and then it re-installs the My HTC driver.
The PC recognizes it as an MTP/Media Player device, but not as an ASB one.
Any suggestions?
edit: Never mind. Arg, stupid me - I forgot to put the phone into fastboot usb mode.
Yeah....
ADB commands only work in a booted O.S or recovery
FASTBOOT commands only work in the bootloader

Can't get sdk to detect my device when is fastboot/bootloader.

Hello,
Ever since the latest oxygen os update, my device got wiped from it's root and twrp. And for the past week when I have been trying to reroot it (w/ the bootloader unlocked) it won't even bother to detect the devices. I have tried reinstalling the drivers, using and different port, fasboot.exe, rebooting my pc, etc but nothing is working. Also, it detects it as an ADB device.
I really need this to be fixed asap as I will be sending my device for a screen repair and will loose all my data if I don't root my device and use titanium backup.
~ ronaldonater.
I have the same issue and am curious how this is fixed. I have Windows 10 and the oneplus three. ADB recognizes device and "adb reboot bootloader" reboots the phone into bootloader. Then "fastboot devices" just says searching for devices. I am tired of having to use my widows 7 laptop each time. Any help would be greatly appreciated.
My phone not recognised on pc. Not even on twrp. I reinstaled drivers, adb..., nothing. Then i tryied on pc at work. Booom! it works. When I arrived home i've reinstaled windows on my laptop. 100% works.
had the very same issue. the phone would detect properly on my work laptop running Win 7 but wouldn't recognise on my home PC running Win10. Tried every ADB tool and driver available out there. But nothing seemed to work.
Problem is with driver conflicts.
Then tried the age old method of factory reseting my PC, installed Minimal ADB tool and voila!!!
everything started like a charm.
First of all go into Windows drivrs and select hidden drivers and delete your entire driver history for that machine and reboot, then connect your phone whilst it's booted up so it can install.
Connect phone in fastboot and let it install. After this you need to manually update the driver for the phone unless it's already showing "android bootloader interface" in device manager. Finally check over android SDK so it's up to date and you'll be good to go.

Boot loop after attempted downgrade of twrp

I attempted a downgrade to an older version of twrp via twrp in recovery mode. Not sure what I did wrong. Now my LineageOS hangs at the LG logo at startup. When I try to access TWRP using recovery mode, the LG logo flashes on and off (loops). I cannot access the LineageOS to enable debugging, OEM unlock, MTP USB mode, etc...
From a Windows XP SP3 desktop:
I can manually put my D851 into Download mode and can get from Download mode to firmware update mode when connected to a Windows XP computer. The Windows XP computer sees the phone as new hardware ("LGE Android Net MTP") device when connected in Firmware Update mode. In Firmware Update mode, I cannot properly access the phone using the LG PC Suite, ADB/fastboot tools, etc...
I have tried installing various versions of the LG United USB drivers. Originally, the driver installs failed citing "Windows MTP driver" not found and advising me to install Windows Media Format Update. After learning Windows Media player contained the Windows MTP driver, I installed Win Media Player 11. Now the LG United driver install fails but without mentioning missing Windows MTP driver or Windows Media Format 11 runtime updates. I have tried installing the USB drivers using LG PC Suite but it too fails when reinstalling the driver. LG PC Suite cannot connect to my phone. . Ihave tried to install the LGMobile Support Tool (ie. LGMobile Phone Software Update Tool), but the install seems to hang.
I feel that if I could just get a computer to communicate properly with the phone while in Firmware Update mode, I should be able to restore my phone. Does anyone have any ideas on other things I might try?
Thank you
I got stuck in that same boot loop as you. There's a thread that claims that the D851 is unbrickable: https://forum.xda-developers.com/tmobile-lg-g3/help/lg-g3-d851-unbrick-qualcomm-9008-t3430221 But I was also unable to get it to work on my laptop. I think some computers may have a hard time using the drivers correctly and maybe trying another computer is your best bet.
But personally, I ended up sending mine to a J-Tag service on eBay and paying some $30 to get the thing completely reset.

Categories

Resources