Somewhat bricked htc one m8. Stock recovery boot loop no fastboot access - One (M8) Q&A, Help & Troubleshooting

I was trying to revert to stock rom when all this happened. I had the google play edition rom on my phone (and had installed the custom firmware needed at the time for said installation). I was trying to convert my phone back to sense first via android revolution to then go back to the stock rom when all this happened. I flashed the firmware for android revolution which overwrote the twrp recovery and initiated the bootloop. At first I thought it was completely bricked because I had no access to fastboot or adb but this morning I was able to get into the stock recovery. My only options at this point would be to somehow flash a custom recovery or get a working os running on the phone.
Any thoughts on what I can do? I can't flash anything custom at the moment since it always fails the verification of a package (since it's the stock recovery). I relocked my bootloader in order to flash the firmware fyi. The only way I can interact with my phone currently is via sd card with a zip file, adb shows the device as offline.
Any help is greatly appreciated. Thanks.
EDIT: Phone is a US variant tmobile m8. cid:T-MOB010 mid:0P6B13000 Phone was S-OFF as well

Filthy casual

UPDATE: I can also access HBOOT but fastboot and adb aren't accessible in it's current state. HTC drivers are able to see the device when in fastboot mode but I'm still unable to interact with the device via htc_fastboot or google's fastboot
Update2: I ended up finding a tmobile htc m8 RUU zip file, renamed it to 0P6BIMG.zip, loaded it onto an external sd card, put the card in my phone, booted into hboot and the file was flashed automatically. When it finished the phone booted back into the last rom I had on it which was google play edition. Phone is working again.

Related

[Q] Phone stuck on HTC Logo Help !!!

These are the steps I did & forgot to place rom.zip to sdcard & now I am stuck at the HTC Logo.
1. Unlocked bootloader.
2. Installed CWM Recovery.img
3. Installed Super Swipe from Android HD Rom 6.0 ICS
4. Went into fastboot & done Swipe directly. It erased all the data & now only stuck at HTC Logo.
I tried even
1. Reboot phone and erase cache (Not worked).
2. Install cwm & then custom rom (Not worked).
3. Relock bootloader & install stock rom (Not worked).
4. Installed latest RUU directly (Not worked as my phone has 1.28.720.10)
5. ADB shell mount /sdcard & adb push rom.zip /sdcard (Not worked).
6. Even factory Reset didn't work.
Developers plzz guide needed.....
me too
i'm having the same problem, tried everything... i just updated my rom OTA 1.29.707..... then try to install some roms, then now i'm stock at htc logo...
the last thing i remember is i did a superswipe, then the rest is history...
i can't downgrade either... i guess the solution is to wait for ruu of hTC_Asia_WWE_1.29.707.10 so i can install ruu that will not make error 140...
is there any solution?? please help...
Install the latest CWM recovery with USB storage auto-mounted. Put in any custom rom that you like and install it. Don't forget to flash the boot.img that comes with the custom rom.
To be back on stock, yes you need to wait for the RUU.
urgent help
when i lost the network signal,read from forums that i need to make unlock and as you know install the new custom rom's so i did many times, but still no phone signal,i am living in moscow but phone intended from Poland. Then when i was trying the other roms in the recovery mode wiped away sdcard and system etc.now phone just stuck HTC logo.
Is there a solution or i need to buy a new phone?
best regards.
Saldiray Yildiray Cakmak
i made a thread about this guys.. just follow the instructions
http://forum.xda-developers.com/showthread.php?t=1692681

[Q] Phone doesn't boot after flashing boot.img, can't get into recovery

Hello there,
I might have ****ed up.
I was on ViperOne 1.8.0 for a long time, but decided to wait for L which is now here.
As I know, I need a new firmware flashed, but as I wasn't on s-off, every method failed (FUU flasher and also flashing via adb, it rejected the file)
So I decided to give sunshine a shot to s-off my phone, but dang, it didn't want to as I am not on a stock boot img.
So, what was the logical step? Flash a stock boot img, the newest one. boot_3.28.401.9.img it was.
Now I am stuck on the white htc boot screen, combination for recovery (power+voldown) is not working. Can't switch the phone off or anything, it just is stuck there. Well actually it runs, I get message notifications and the LED blinks and I can also connect via USB but I just don't get into the user interface.
I can however reboot it by pressing power+volup, but it just gets stuck in the white screen again respectively is running but stuck in the whitescreen.
Installing RUU does not work. Phone is not recognized albeit being accessible in Windows Explorer.
adb is not working, doesn't recognize the phone so also no way to get into recovery or bootloader.
How am I supposed to flash stock img now to get it back to life?
Okay, got into bootloader now by pressing Power+VolUp and then VolDown.
I tried to flash 4.16.401.10-Firmware.zip from http://forum.xda-developers.com/showthread.php?t=2701376
but it says signature verify fail
So how can I get a valid firmware on my phone so I can flash TWRP and Viper and be happy?
What could be possible is to flash the ViperOne's boot.img (of the one I have installed) but that won't help me get newest firmware and lollipop.
Trying the old fashioned way now... got myself a TWRP backup of the stock image that corresponds to my firmware. Hopefully it will install and boot through. Then I just let it OTA all the way up until I got the newest version, then firmware and everything should be right and I can flash Viper. Hope that works.
After you flash the TWRP backup you will need to restore the stock recovery as OTA updates won't work with TWRP
Yup, did that. Thank god, it boots now.
I am on a super old System now of course, like last June or something.
But all I should do now is let it OTA all the way up to lollipop, right? Then I'll have firmware and everything up to date so I just unlock again, flash TWRP, flash my Rom and be done?
Probably easier to connect in fastboot and use fastboot getvar all to give more details on your details (remove your IMEI and serial number)

Help Please. Soft-Bricked Device

Hello all!
I recently flashed the 4.16.xx firmware to my device. I am now stuck on the Bliss Rom bootscreen for some reason. Booting into recovery takes me to stock recovery and the phone isn't being recognized through ADB on several different PC's.
Am I screwed here? Any options?
Thanks for any input.
Try going into the fastboot option from the hboot (or called bootloader to many people. To get to hboot, do power and volume down when the phone is booting up. ) and try flashing your TWRP recovery from there. Also make sure your drivers are working.
If you don't know how to flash recovery just Google it, you should be fine.
Dw, dont panic, it'll be fine xD
Zomb!e said:
I recently flashed the 4.16.xx firmware to my device. I am now stuck on the Bliss Rom bootscreen for some reason. Booting into recovery takes me to stock recovery and the phone isn't being recognized through ADB on several different PC's.
Click to expand...
Click to collapse
Stock recovery is the logical result for flashing firmware, unless the firmware was hacked to remove stock recovery.
adb not working, is also normal. You need to be in OS or recovery to use adb commands (and I don't know whether you can with stock recovery). adb does not work in bootloader.
If you flashed an official firmware with s-on, then not boot is also the expected result.
You need to unlock the bootloader again, flash TWRP back onto the phone, and flash a ROM.
redpoint73 said:
Stock recovery is the logical result for flashing firmware, unless the firmware was hacked to remove stock recovery.
adb not working, is also normal. You need to be in OS or recovery to use adb commands (and I don't know whether you can with stock recovery). adb does not work in bootloader.
If you flashed an official firmware with s-on, then not boot is also the expected result.
You need to unlock the bootloader again, flash TWRP back onto the phone, and flash a ROM.
Click to expand...
Click to collapse
Hey thanks for the reply!
I figured it out finally and forgot to update the post. I ended up finding and flashing a Lollipop RUU from the SDcard and that got me booted up. Then I just had to re-flash TWRP, re-root and flash a new rom.
All is well now. Thanks for trying to help out.

Sprint HTC one m9 fail

I previously rooted my htc one with s-off as well. Had TWRP 2.8.6.4 and Viper ROM. I recently decided to use the htc again and tried updating everything. First, I flashed new Viper ROM. ROM wouldnt boot up but gave successful install. I can only assume because the firmware was out of date on my phone. I then tried flashing TWRP 302 img and now phone wont boot into twrp. I was able to get into download mode, bootloader and thats it. I downloaded the Batch tool and did cmd/ adb reboot download. It took my phone to a black screen with a security warning about flashing any rom not fron htc can get you info stolen. I then tried fastboot flash zip rom.zip Unfortunately the rom.zip i had from Sneakyghost's firmware page isnt compatible with my sprint phone. I am looking for the correct zip to flash. It seems that i am committed at this point to this method because i cannot reboot into bootloader anymore. At least i think i cannot. Any help is greatly appreciated. Thank you
I was able to restart phone back into bootloader
i can access download mode as well but cannot boot into recovery mode
Software status : modified
Unlocked
s-off
Whenever i try flashing a slightly older version of TWRP i get a successful flash on both phone and computer but it still wont reboot into recovery

M8s stuck in bootloader

Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Hi McBad,
you could try the following. I also had some problems to access the recovery.
- Again bring the phone into fastboot, flash the 2.8 recovery and access it
- Do a wipe for factory reset, not just only cache
- after that try to flash the twrp-3.0.1-0-m8ql.img version, the other one worked for me neither
- the try to install the custom ROM LOS13
I hope this will help you.
clone
It would be great if that would work, but flashing a recovery does not work. I flash it, success message, try to access it, vibrates and bootloader pops back instantly. That is the problem.
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Have you tried sideloading twrp ?
McBad said:
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Click to expand...
Click to collapse
Did you use HTC fastboot ?
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Is there any way you could flash twrp 2.8 again? Once in that recovery you have sideloading option which you could use to transfer latest recovery onto your device. Are we talking about the same process?
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Sideload as follows ....
McBad said:
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Click to expand...
Click to collapse
You can't install lineage if you haven't upgraded your device with latest official update. I would try reinstaling twrp 2.8, do a wipe of cache, dalvik cache and system, Sideload CM 12; and see how it goes. As well, while in twrp I would try relocking bootloader but only after an unsuccessful attempt to flash said rom. I don't know what your experience with soft bricked devices is, but sometimes it takes a while, different usb cable or usb slot on your PC, correct files in adb folder, re-download of rom or recovery because it easily gets corrupted while downloading. And obviously a fully charged device. Let us know how it goes.

Categories

Resources