[Q] HTC one m8 device not found after updating to 4.4.3 - One (M8) Q&A, Help & Troubleshooting

ok so i just updated my htc to 4.4.3. before i did that it had TWRP custom recovery flashed to it so i had to flash the stock recovery back to it to make my device able to update. i didnt really find the right stock recovery so i got a recommended one which is: 1.157.112.2(maybe this recovery is the problem why it is not recognised while in fastboot mode.) I rooted my phone before this update so it is still rooted now. So im trying to reflash the TWRP custom recovery to my phone but it doesnt work cus my phone is not listed in the device list. When my phone is in normal mode (normally booted) it gets recognised but when i go into fastboot it does not get recognised anymore. I need a custom recovery to be able to install xposed for rootcloak. cus now my phone is rooted and i cant use bank applications. i installed all kinds of drivers. i installed the drivers via HTC sync manager, i installed them manually, i even installed adb interface drivers. but it still wont work. i have windows 8 and my htc is a tmobile one. can anyone please help me?

oh
oh and also i cannot seem to install MTP DEVICE after the update

and
when my phone is turned OFF and i connect it to a random pc it automatically boots into fastboot mode which is not normall i gues this is a software issue?

Fixed it myself
Thread can be closed

Related

Soft brick help (HTC M9)

Hi guys – hoping you can help me following an issue with my M9 I bought a couple of days ago. Last night I unlocked the bootloader with HTC dev, rooted with TWRP/SuperSU, S-OFF’ed with SunShine, updated firmware to 1.40.401.5 per matanlevanon‘s thread, then flashed MaximusHD.
Up until the last step, everything went well – but I’m now stuck in boot loops. I can currently access both Download Mode and bootloader; but trying to launch recovery gets as far as the TWRP splash screen before my phone reboots again.
I've reflashed TWRP.img using fastboot; but when rebooting into recovery I still have the same result (TWRP splash screen before my phone reboots again)
I've also lost ABD - in Download Mode/bootloader, Windows Device Manager see’s my phone without issue and correct drivers – but ADB server doesn’t recognise my phone.
I’ve tried everything from HTC Sync bundled drivers, PdaNet drivers to generic ADB drivers – but ADB seems to refuse to see my phone regardless of what I try.
Seemingly if I can get a working recovery image / TWRP on and working I can wipe and try to flash again, but current images don't seem to be helping. Any suggestions / help please?
Got it, cache partition was corrupted! fastboot erase cache let me get back into TWRP and reflash my ROM.
Fingers crossed it's smooth sailing from here

Phone won't boot

Guys I think i did something a little stupid haha
I received my new HTC M9 today. I rooted the device, installed TWRP just fine, and then I installed a custom ROM (all as I did with my M8).
My problem is that after installing the custom ROM (which installed successfuly) now the phone gets stuck in the HTC logo.
Now adb don't recognize the phone even when I manually enter download mode. I don't know what to do
Can someone give any ideas?
I solved it. Please close the thread

M9 bootloop and no downlaod mode - unbrick possible?

Hi guys,
my father's M9 was on the newest ViperOne for some time now.
Now a few problems popped up:
1. If the device is turned off and you plug it in to charger, it boots into bootloader
2.booting to download mode results in "failed to boot to download mode"
3.Every ROM i install via TWRP is ending in a boot loop (The boot-animation is visible for about a second)
4. i tried other TWRP version, other ROMs and other Kernels and also wiped the complete device.
As I dont get into downlaod mode, I dont know how to recover the device to stock ROM via RUU at least.
Any help is appreciated! Thanks!
download RUU your correct current *os/sku number* installed version, you can find it at
https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
you should have thanks to mr flippy498
**download adb universal driver and adb debugger or htc driver.
1. plug your phone to pc/laptop and install on** desrciptions above
2.open RUU and follow the rules and wait until finish *cafully if your cable is disconnect/unlpug or your phone force reboot by your own hands it will cause abnormal problem or your phone will never boot
I can't because, like I said, I cannot boot into download mode (black screen saying "failed to boot to download mode").
LeErdnuss said:
Hi guys,
my father's M9 was on the newest ViperOne for some time now.
Now a few problems popped up:
1. If the device is turned off and you plug it in to charger, it boots into bootloader
2.booting to download mode results in "failed to boot to download mode"
3.Every ROM i install via TWRP is ending in a boot loop (The boot-animation is visible for about a second)
4. i tried other TWRP version, other ROMs and other Kernels and also wiped the complete device.
As I dont get into downlaod mode, I dont know how to recover the device to stock ROM via RUU at least.
Any help is appreciated! Thanks!
Click to expand...
Click to collapse
What os are you currently running? And what version of twrp are you on?
I know you've said you've installed other twrp versions/roms/kernels but to know which is most compatible, your firmware and a bit more info is needed.
I'm willing to bet it's an s-on device too.
If you can't get to download mode, what modes CAN you get it to?.
Beamed in by telepathy.
C.f. Q7

TWRP BOOT LOOP has anyone found a solution (OTA update)

i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
[SOLVED]
went back to stock recovery and side loaded the full 1.4 gb rom i will leave a link for tutorial that i used, i wanted to get back to complete stock and this was the one use
"https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/"
When you have TWRP you have to install full zip, not simply the eval OTA zip
bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
Flash the stock recovery.
Get stock recovery from downloads.oneplus.net
I cant seem to flash the stock recovery. The device is not visible in adb devices or fastboot devices. im facing the same issue.
If you are using TWRP 3.0.4-0 - try a hard boot...hold down the power button for 20s...wait 20s, power it back on.
bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
easy solution. Boot into fastboot
download this tool.
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
if newest version isnt working, download an older version with older twrp
than unzip the tool and run the .bat file and install twrp.
Thats it
There are many posts on Nougat not working with official TWRP (based on 6.0 build). Try booting into stock recovery. performing a system settings reset, then booting into fastboot and run the adb command, <fastboot boot TWRP-3.0.2-1.28.img>. From there you can do virtually anything you need to do. I recommend at least using a modified version of TWRP (such as 1.28). This has been posted many times before, please try and do a search for the answers first, it will help tremendously. Thanks
recovery
i had the same problem on my rooted OP3 when i used TWRP 3.0.2-1 , it worked to flash the full 4.0.1 rom but failed for everything else, flashing latest verion of twrp fixed it for me
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Aislandas said:
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Click to expand...
Click to collapse
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Noted that you solved your issue, but this post is about the new version of TWRP. Version 3.0.3 is available on twrp.me and it works with Nougat.
bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Gave up trying and booked a session with OP technicians Will see how it goes in a week.

Android fails into TWRP, TWRP Won't Load Anymore, and Phone Not Recognized in Win10

Hello, I tried to install the rom Google PixelROM v7.3 for LG Nexus 5X[7.1.2] by argraurand, and now my phone will no longer boot into TWRP or the OS. I am running TWR 3.0.2-0, I didn't see anything about having to have that updated to the most recent for using this rom. I was able to install the rom fine from this TWRP, but now my phone seems to be bricked like. Sitting with the phone in the bootloader, I can't get windows/fastboot/adb to recognize my device connected to my computer, the google drivers are definitely installed as earlier it was being recognized fine by windows/fastboot/adb. My bootloader changed with this ROM being installed, but now the TWRP won't load either, and neither will the Android OS (it looks like it's about to load then just defaults into the TWRP loading screen, which just sits forever). I can get also into the download mode "firmware update" tool of the phone by pressing the volume up when booting, but even in this mode the phone isn't being recognized in windows anymore. Do I have any chance of restoring my phone, or should I start shopping? I've fixed other phones many times, but without being able to load/restore via fastboot I feel totally lost.
myselfalex said:
Hello, I tried to install the rom Google PixelROM v7.3 for LG Nexus 5X[7.1.2] by argraurand, and now my phone will no longer boot into TWRP or the OS. I am running TWR 3.0.2-0, I didn't see anything about having to have that updated to the most recent for using this rom. I was able to install the rom fine from this TWRP, but now my phone seems to be bricked like. Sitting with the phone in the bootloader, I can't get windows/fastboot/adb to recognize my device connected to my computer, the google drivers are definitely installed as earlier it was being recognized fine by windows/fastboot/adb. My bootloader changed with this ROM being installed, but now the TWRP won't load either, and neither will the Android OS (it looks like it's about to load then just defaults into the TWRP loading screen, which just sits forever). I can get also into the download mode "firmware update" tool of the phone by pressing the volume up when booting, but even in this mode the phone isn't being recognized in windows anymore. Do I have any chance of restoring my phone, or should I start shopping? I've fixed other phones many times, but without being able to load/restore via fastboot I feel totally lost.
Click to expand...
Click to collapse
Try a different USB port. Maybe even a different pc. Fastboot tools was just updated. Make sure you have the latest one.
Maybe you can get a fastboot connection in Linux. Try this:
https://forum.xda-developers.com/showthread.php?t=3526755
Sent from my Nexus 5X using Tapatalk
Thank you both, I tried both another computer, and running this linux version with the fastboot built in, nada! Guess I'm shopping for a new phone. Pixel here I come. Thanks for the help agian.

Categories

Resources