My issue was caused by trying to flash Mike's AHD ROM. I was able to Unlock the Bootloader via HTCDEV and Flash latest clockwork recovery. I understand the phone will not charge with that recovery, so I've flashed stock back and I was able to borrow an iPhone plug to get the phone to charge.
Issue is now: The phone will boot up and it boots in the setup process. It's when i try to skip through that process the phone flashes "Low Battery" and shuts down. The phone's battery is close to 100%. I have a backup but it yields the exact same result.
My question is: How do I flash back to bone stock? I'm not sure how exactly to determine which RUU I need? I'm in the US and the phone was purchased through Negri Electronics.
HBOOT - 0.32.0000
RADIO - 1.1204.103.14L
If I can ever get back to normal, I feel comfortable flashing Mike's ROM. I just wish his instructions would have mentioned the need to copy over his ROM to the phone before flashing the recovery. Sort of threw a monkey wrench into everything.
Thanks,
Forgot to add this bit:
MIDJ4610000
CID: None
**Update**
I was able to find my RUU just by trying a couple of different ones. The phone is working beautifully now.
I oem locked my bootloader and flashed stock recovery. Then I rebooted the phone back into fastboot and just ran the RUU in windows. Took care of everything!
I do not have a method for those of us who cant pull CIDs... I guess just try different RUU's until you get the right one.
freebirds87 said:
I do not have a method for those of us who cant pull CIDs... I guess just try different RUU's until you get the right one.
Click to expand...
Click to collapse
Which RUU worked for you?
This app will tell you your devices CID, after you have unlocked the bootloader using HTC Dev.
https://play.google.com/store/apps/details?id=org.tritonsoft.cidgetter
I've got the fuzzy lens problem and I want to get the phone replaced (preferably via T-Mobile but I'll go directly to HTC if I have to). I know you can scratch off the coating on the lens and get some camera improvement but I'm not interested in that solution.
My goal: Return the phone to completely stock condition. No root, locked bootloader and preferably S-ON. I've read a few stories where HTC insisted on replacing the motherboard (with an additional full price fee) because the device was S-OFF and I don't want to go there.
Background: I used firewater to S-off the phone as soon as I got it (it was running 1.12 at the time). I have flashed the Harmon Kardon audio stuff (http://forum.xda-developers.com/showthread.php?t=2737498). I have turned off the tamper flag (http://forum.xda-developers.com/showthread.php?t=2708565). I am running the Stock+ rom which is based on 1.57 (http://forum.xda-developers.com/showthread.php?t=2716843).
My plan:
1) Reset my bootloader to locked (http://forum.xda-developers.com/showthread.php?t=2708571)
2) Wipe the phone and restore my very first nandroid backup I made with TWRP. That will get me back to unrooted 1.12 firmware but without the stock bootloader and still S-OFF. Staying with 1.12 will allow me to S-OFF again with firewater if it comes to that. If some kind of emergency came up, I'd hate to spend $25 on sunshine for a one time use on a phone that is going back to HTC forever.
3) Install the stock bootloader that matches 1.12 firmware. Not sure how to do this yet. I'm afraid I won't be able to achieve this with a locked bootloader and no root.
4) Verify everything is back to stock.
5) Set the phone back to S-ON (http://forum.xda-developers.com/showthread.php?t=2758818)
6) Run the 1.57 RUU (http://forum.xda-developers.com/showthread.php?t=2714456)
7) Proceed with the warranty exchange.
I'm not sure running the RUU is 100% necessary, but I figure it's the best bet I have to make the phone completely stock.
Questions: Is this a sane plan? Am I doing anything in the wrong order? Are there any steps that won't work because I've lost root or unlocked bootloader? Am I setting myself up for a brick anywhere?
There is a thread about doing this on a EU M8 (http://forum.xda-developers.com/showthread.php?t=2735235) but I can't tell what, if any, modifications need to be done for the USA T-Mobile version of the M8. There is talk about having to flash a firmware file twice or risk a hard brick when setting S-ON. Do I need to be worried about any of that?
UPDATE: T-Mobile gave me a warranty replacement to fix the camera lens problem. I did get the old phone back to completely stock with locked bootloader and S-on before sending it back.
I found it was easiest to use the sunshine installer to gain temp root. You don't need to pay anything since you stop before it goes through the whole S-Off process. Just run the APK and select temp root. When sunshine shows you the next screen, you can exit out and still have root. (http://theroot.ninja/)
In the end I didn't bother with the old nandroid and keeping the exploitable version. I also had the order messed up in my initial post. Here is what worked for me:
1) factory reset the phone (in TWRP I did advanced wipe and also wiped internal storage). This step kills root. Rebooted the phone and verified it was back to factory defaults. Go through the setup wizard and skip all the steps. I couldn't find a way to bail out without going through every step in the wizard.
2) flashed stock recovery (the bootloader was unlocked and the phone was S-Off). Root is not necessary for this since it is done in fastboot. (http://forum.xda-developers.com/tmo...l/ota-recovery-ruus-firmware-dumps-t-t2852107). Rebooted the phone.
3) achieved temp root using sunshine APK
4) locked the bootloader (required before running the RUU). You must have root since you need a SU # prompt in the shell. (http://forum.xda-developers.com/showthread.php?t=2708571). I rebooted again for good measure but it's probably not necessary.
5) reset the phone back to completely stock using the latest 2.22.531.5 RUU. This step does not require root. I found it was easiest to put the phone into fastboot mode before running the RUU. (http://www.htcdev.com/devcenter/downloads)
6) Once the phone booted back up, I looked over everything and made sure it is all completely stock. Checked HBOOT said locked (not relocked) and dis not say tampered.
7) OPTIONAL - set S-On. Again root is not required since this is a fastboot command. (http://forum.xda-developers.com/showpost.php?p=52823014&postcount=2)
My actual process wasn't this streamlined. I ended up doing the RUU a couple of times because I didn't flash the stock recovery first and I didn't think the RUU installed the stock recovery right. Turned out I just didn't know what the stock recovery looked like (it was very confusing since I had never actually used a HTC stock recovery).
Thanks to the authors of the various threads I pulled info from. They are the real MVP's.
I flashed the stock HTC RUU via the .EXE and wasn't able to get the "RELOCKED" off the phone. Tried some steps here:
http://www.droidviews.com/restore-att-htc-one-m8-stock-firmware/
however I wasn't able to get "SU" to properly run in terminal.
No w the phone says *** RELOCKED ***
and im S-On
anything I can do?
It been a long time.. Well maybe 3years since i been on xda. I still remember how to root and flash this n that n etc... But yesterday i wanted to get started on flashing my verizon m8 onto a rom. Yeah little complicated. I tried everything to unlock my bootloader i keep getting the 172 error. Still considered S-on, So i just left that alone and tried to go #oldschool. I tried to update using htc sync manager. But I had to leave and go to the store. Left this on the computer to finish updating. came back 20-30mins later its on a black htc screen with the green line across. So i thought it was just finished But my computer had been frozed for 10mins. (ive checked the time) but Now it gotten bricked. i can only boot into hboot... Fastboot... And ruu.. But not recovery... I Already downloaded the rom, and the latest twrp recovery on my pc. But im still s-on.. I really don't got time to start from scratch and just factory reset this.. And im no longer worried about my data and shxt because i know im eventually going to losed them anyway. So right now its on fastboot. My win7 detects it in fastboot usb. So where do i go from here? Anybody? No worries though :fingers-crossed: :angel:
You can't unlock the bootloader on the VZN version by HTCDev.com, you need to s-off by sunshine, then use sunshine to unlock the bootloader.
Unfortunately, sunshine requires a working OS. So first you'll need to RUU back to working stock. http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
After that, you will need to root (think kingroot is the mot common method) then you can load the sunshine app ($25 license) to s-off and unlock the bootloader: http://theroot.ninja/
Once the bootloader is unlocked, you can load custom recovery TWRP and flash a custom ROM.
But keep in mind, there are kernel differences between the VZN version and most other M8 versions. Meaning, you will need to either flash a ROM that explicitly states it supports the VZN M8; or you can flash other ROMs, but you will need the proper kernel.
You'll want to read up in the Verizon M8 forum section, as this version has some peculiarities, as I've mentioned: http://forum.xda-developers.com/verizon-htc-one-m8
hello
i attempted to unlock bootloader on my wife's old HTC M8 (Australian/Vodafone), i was able to unlock the bootloader, but had to do some serious trial and error to get a custom recovery installed, eventually got an older twrp loaded, but the phone just refused to boot into recovery.
i then relocked the bootloader (no S-OFF), and when i try and unlock he bootloader now, the phone attempts to boot into the recovery, and is failing...
i've been trying to find an RUU from somewhere, just to blat the phone back to an old state, and try again.
are there RUUs available anywhere? i dont' care if its not for the local carrier, i just want to get a basic android rom on the thing.
However, im curious if i need to s-off to do this (wasnt the case with my previous HTC)
help!
what an idiot, i assumed this was an htc One m8, it wasnt, its an m7... reposting in there ...
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.