Hello, I need some serious help with my friends HTC m8.
We unlocked the phone of my friend and wanted to install a custom recovery. After installing TWRP latest version everything still worked fine, the device still booted normally. After that we tried to install the GPE ROM of the M8 through TWRP without realizing the phone isn't s-off. By itself the installation failed and we just rebooted the device and saw that it wouldn't boot anymore, it was stuck on the boot screen, even though it aborted the installation because the MD5 numbers weren't matching.
Now we don't know what to do, the M8 won't boot and is s-on. We tried downloading: http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563 the stock file and pushing the update by renaming the zip file to 0P6BIMG.zip but gave us the error "halted due to large image update fail". So this didn't help us either
CiD of the device = HTC_E11
After all we're just idiots by not researching enough before doing anything. Hopefully some experienced people can help us out!
Thanks in advance,
Pepie.
Pepie said:
Hello, I need some serious help with my friends HTC m8.
We unlocked the phone of my friend and wanted to install a custom recovery. After installing TWRP latest version everything still worked fine, the device still booted normally. After that we tried to install the GPE ROM of the M8 through TWRP without realizing the phone isn't s-off. By itself the installation failed and we just rebooted the device and saw that it wouldn't boot anymore, it was stuck on the boot screen, even though it aborted the installation because the MD5 numbers weren't matching.
Now we don't know what to do, the M8 won't boot and is s-on. We tried downloading: http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563 the stock file and pushing the update by renaming the zip file to 0P6BIMG.zip but gave us the error "halted due to large image update fail". So this didn't help us either
CiD of the device = HTC_E11
After all we're just idiots by not researching enough before doing anything. Hopefully some experienced people can help us out!
Thanks in advance,
Pepie.
Click to expand...
Click to collapse
Firstly, I don't think it has anything to do with "not researching" enough but more to do with NOT reading what you "researched" already. You post a link to the RUU .zip that you wanted to use and obviously haven't picked up on the fact that the OP in that thread specifically stated: S-Off is Required with Eurpean CID right after admitting that you are NOT S-OFF.
Secondly: You don't need S-OFF to flash a custom ROM. You just need an unlocked bootloader and a custom recovery, that's it. You'll need S-OFF to fully convert the device to GPE though, as it makes changes to partition sizes.
Try to get back into bootloader again. Hold Volume UP + Power for 10 seconds the moment the feel a vibration and/or screen goes dark immediately hold Power + Volume Down to enter bootloader. You should still have TWRP on the device you didn't mention anything about taking it off. Head over to the RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection grab a nandroid backup for your device. Unpack it and place it inside the TWRP backup folder on your device. If you don't have one, make a backup of just "Boot" it'll then create the path for you.
Once done, restore the nandroid. That'll take you back to "stock" then.
Else, just place a custom ROM on the SDcard enter TWRP again and try to flash a custom ROM again.
What ROM did you try to flash? Perhaps give the link...
Oh and remove the 0P6BIMG.zip from the SDCard else it'll just keep on trying to flash it through HBoot.
Hi folks,
I bought a stock German Vodafone HTC M9 on Android 5.1 with software 2.10.410.1 HTC sense 7.0 and everything had been going fine until Friday, my battery died and when I plugged it back in it looks like it tried to update to Marshmallow, it looks like that failed but my main problem is that now I have no navigation softkeys, it looks like HTC sense isn't loading up as I have no themes either. I tried an OTA update (fails on the "System partition has unexpected contents" issue). Since that happened I've tried a soft reset, hard reset, install an RUU.exe ( get correct rom update utility, Error 131), so far no joy. I was considering installing TWRP and trying to go back to a stock recovery (I was talking to HTC support and they want me to send my phone to a repair centre, I'd prefer to try fix it myself). My question is, would reverting to a stock recovery even bring back my softkeys or am I barking up the wrong tree? I have unlocked the bootloader now and I will probably end up S-off and playing around with custom ROMs in future but for now I just want my phone to work, it's been a weekend and I'm getting phone withdrawals. I'm in work now so just browsing the forums and seeing what other people are doing but nobody seems to have the same softkey issue as me?
Jamie
Fixed!!!!
Great success! Just in case anyone comes looking for solutions to problems similar to mine and wants to revert to stock firmware without S-OFF and finds an empty thread here's what I did ....
The way I went about it you'll need a micro SD (larger than 4GB I think, no maximum size according to Flippys instructions)
I followed this guide from KingInTheNorth up until the point where I had TWRP installed, this guide will get you through downloading files, tools and drivers unlocking bootloader and flashing TWRP. I DID NOT install SU as I didn't want to root my phone just restore it to stock so I could upgrade to Marshmallow through HTCs OTA update that originally broke my phone.
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
I followed Flippy498s guide to getting back to stock recovery (under the TWRP backups tab), this sheet also lets you download stock recoverys to match your firmware because Flippy seems to be a legend.
https://docs.google.com/spreadsheets/d/15K6xhb6wtosp9j8yu4xHBZ6n9v5OaFSW6ZVWxC4u_qc/pubhtml#
Team Win the folks who make TWRP make a fantastic tool, I started out trying to fix my broken phone and finished out wanting to try new ROMS and playing around to see what else I can do, at least now I have some idea where to start!
Have fun!
Jamie
I am quite the idiot when it comes to custom roms and such, so i apologize in advance for my lack of knowledge. Anyways, I had CM13 for quite some time before this and was using twrp. In my adventures of installing my first custom rom I had thought I needed to re-lock my boot loader, so because of this i no longer has s-off. I used sunshine to achieve s-off in the first place and needed to go back to a stock rom to repeat the process. along with this I had gps problems on my custom rom and had read that i need to go back to stock. I looked on the internet to find a twrp flash able rom, that would do such. (http://forum.xda-developers.com/showthread.php?t=2694994) I was unaware that this would get rid of my custom recovery (again, sorry for my stupidity) and now my screen is stuck on black when I try to boot up the phone, I am incapable of reverting back to my custom rom, and as I noted before, I have a locked boot loader. Everything I have looked for on the internet requires s-off. Is there any possible way re achieve s-off with out a functioning os (I can still access the stock bootloader) or am I just screwed?
Thank You for the help!
P.S. I have the Verizon variant.
Your biggest mistake here is installed wrong ROM on wrong device.
You shouldn't install a GSM stock ROM on a CDMA device, for your case is Verizon.
Search Verizon thread for RUU ..
http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972
read the last post in this thread
ckpv5 said:
Your biggest mistake here is installed wrong ROM on wrong device.
You shouldn't install a GSM stock ROM on a CDMA device, for your case is Verizon.
Search Verizon thread for RUU ..
http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972
read the last post in this thread
Click to expand...
Click to collapse
Thanks for the help! I found an 0PGBIMG for the lollipop Verizon Rom and from there I could reinstall TWRP and then finally a GPE Verizon rom. I really appreciate the response, I didn't really expect one to and I'm glad I could receive your input! :good:
Hi guys,
Got a phone a need to revive. I received unusable. Mother gave it to my sisters friend and she said it doesnt work. I now see why cause he was trying to mod it.
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
So currently "fastboot getvars" reports back all the info. It's showing version-main 6.13.206.5 and I just want official O2 stock so can use the phone. Ideally sim unlocked but could hassle O2 for that later since it was my mother's contract.
Basically just want to get a working recovery image on and then flash stock. CID is 02__001
Any suggestion to revive this welcomed, please.
So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup
ckpv5 said:
So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup
Click to expand...
Click to collapse
No, I cannot get into it. When I select HBOOT, then select recovery it just shows white screen, ANDROID and then back to the menu. TWRP no longer works. That's what I'm trying to fix or put on a stock recovery image and then stock OS/firmware.
Just wondering if I need to UNLOCK it again and also do I need USB debug on. I cannot boot into OS so unable to set USB debug.
To UNLOCK bootloader can that be done if you can only get into bootloader menu? S-ON is enabled but not 100% that will stop recovering it? That's just for signed rom/firmware and I just need something stock.
You don't need usb debugging on to unlock the bootloader as it is done on fastboot mode (bootloader).
First I suggest you install the O2 firmware only then see whether you can boot to OS (assuming the OS is still stock base)
Second, re unlock bootloader with unlock_code.bin that you can get from htcdev.com, install twrp 3.x and restore the stock backup and relock bootloader and reflash firmware. This will get your device to fully stock.
So far, I don't see any RUU for your device version that you can get for free, only paid site has it.
Tainted said:
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
Click to expand...
Click to collapse
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).
redpoint73 said:
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).
Click to expand...
Click to collapse
ok, well made some progress.
unlocked the bootloader the official way. Very quick which I was surprised.
This then repoened up the recovery menu working.
then used fastboot to install latest twrp
then installed S.Team-JW-7.5.0.zip !!!
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Wondering if end of the line. Any suggestions? I assume need to get into TWRP and flash stock update from ckpv5.
Must say thanks for replies guys. ckpv5 you done some good work on here.
Tainted said:
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Click to expand...
Click to collapse
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).
redpoint73 said:
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).
Click to expand...
Click to collapse
Hi there,
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
The ROM install finished, battery was at about 80% and everything looked good and I let it reboot the phone. And then it went dead. Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes. My S7 edge shows up. It flash an orage dot twice, so appears to be a in loop.
I charged the phoned and no luck with any of the power+ vol +/- keys. No response from any of those? I let the phone sit till flat and no orange light and then charged it today and still nothing. Not sure if it's a bad battery but it was up at 83% showing in the TWRP menu and working plugged or unplugged.
It's become a challenge now to make it work, I havent had to mod phones since my HTC One which got heavily modded and then back to stock. I stopped doing that after modding every phone I had since HTC Desire Android 2.3. So been about 4 years since doing all this again. Never had one that was totally bricked.
Tainted said:
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
Click to expand...
Click to collapse
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
Tainted said:
Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes.
Click to expand...
Click to collapse
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.
redpoint73 said:
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.
Click to expand...
Click to collapse
Cheers for that. Not getting much except for the 2 brief flashes of orange light.
Any chance the battery is totally messed and this is the problem?
Tainted said:
Any chance the battery is totally messed and this is the problem?
Click to expand...
Click to collapse
It's possible. Or it might be something else like motherboard or emmc. It's impossible to say for sure.
Okay so I just have a quick question and would like a very direct answer. Thanks in advance for that!
I'm new to the HTC stuff, RUU, s-on/off etc. I however did some of the reading, but I'm actually in a hurry to properly understand and try all the methods (also the device isn't physically with me so it's a bit hard to give instructions to someone else without handling such a device ever, and I'm not in a mood for brick and as such)
The device, in the current state only has TWRP recovery installed (TWRP 3.1.1-0), is in s-off state, bootloader locked. No ROM. I'm attaching a picture of the screen that I have. Fastboot is working.
My objective is to get the device in all-stock state (stock ROM, recovery everything, s-on etc), as I am getting a new device and exchanging this. So how can this be done from what I have?
Reserved.
--
Edit_1:
Yes, I read that ReadMe (I discovered it before your reply, and after I made this thread) and it was quite helpful @Flippy498. All I had to do was find a RUU and just run it when the m9 was in Download mode.
Got the RUU from http://www.androidruu.com/?developer=M9. Thanks to whoever posted it!
(however, not really sure about the latest TWRP running on an older firmware as you mentioned)
Please check out the ReadMe thread. It contains all information/files that you'll need.
Edit: Are you sure that you posted an up to date picture? If the phone really runs the firmware that is shown on the pic then it's impossible that it runs the TWRP version you mentioned. The mentioned TWRP version wouldn't be able to boot on such an old firmware.