Develop Bugs

[Q] HTC One M8 Unlocked won't unlock bootloader not update OTA

Hello everyone,
I've tried everything in order to solve this myself (even contacting HTC support by mail), but can't get this to work. I'm actually facing 2 problems with my HTC One M8 Unlocked:
Can't unlock bootloader
Updating software via OTA won't work successfully
Let me briefly explain each problem:
I've tried to unlock my bootloader via htcdev.com but it's not working. I can enter fastboot, get my token, send it to HTC, receive my Unlock_code.bin file and send it to the phone. After selecting "Yes" when the phone asks me if I want to unlock the bootloader, it factory resets (as expected) as if everything went fine, but when I enter fastboot again, I see it's still saying "LOCKED". Tried this several times (manually, via AIO toolkits) but no luck.
My current software version is 2.22.1540.3. I get a notification stating there is an update for my phone in order to take it to version 2.22.1540.4. I download it, install it, but when it boots it says that my phone has been successfully update to 2.22.1540.3 (that is...my current version). So no update is really taking place. After that, I get again the notification that an update is available.
Those are the 2 problems I'm facing. Any ideas on what else can I try?
This is what I get from fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.1540.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
What's even more weird (and I've just noticed this) is that in one of those variables it says "version-main: 2.22.1540.4".

Your main version (OS or software) hboot and radio baseband all match the latest OTA, so you are already updated. There is just something wrong that is causing notifications, but not sure what that might be.
The bootloader unlock issue is odd. I haven't seen it before on this device yet, but on the One X EVITA there were instances where folks had to try the bin code multiple (even dozens) of times before it worked. So maybe just keep trying, and make sure the syntax is exactly correct. Not sure what else can be done?

redpoint73 said:
Your main version (OS or software) hboot and radio baseband all match the latest OTA, so you are already updated. There is just something wrong that is causing notifications, but not sure what that might be.
The bootloader unlock issue is odd. I haven't seen it before on this device yet, but on the One X EVITA there were instances where folks had to try the bin code multiple (even dozens) of times before it worked. So maybe just keep trying, and make sure the syntax is exactly correct. Not sure what else can be done?
Click to expand...
Click to collapse
That helps! Will keep trying to unlock the bootloader until it works then. Thanks!

I have the same problem. Have you solved your problem?
---------- Post added at 12:21 PM ---------- Previous post was at 11:46 AM ----------
I just find these problems might be caused by automatic factory reset, but I don't know how to solve it.

mkiderek said:
I have the same problem. Have you solved your problem?
---------- Post added at 12:21 PM ---------- Previous post was at 11:46 AM ----------
I just find these problems might be caused by automatic factory reset, but I don't know how to solve it.
Click to expand...
Click to collapse
Didn't solve it yet (haven't had time to try again). What do you mean by automatic factory reset?

nachochiappe said:
Didn't solve it yet (haven't had time to try again). What do you mean by automatic factory reset?
Click to expand...
Click to collapse
Ignore that please. I tried to flash 2.22.1540.4 ruu and failed. The one who help me says it might be caused by physical or logical damage on memory, service center is required to solve this issue. I have decided to return it to amazon and bought a new one. Hope the new one has no problem.

mkiderek said:
Ignore that please. I tried to flash 2.22.1540.4 ruu and failed. The one who help me says it might be caused by physical or logical damage on memory, service center is required to solve this issue. I have decided to return it to amazon and bought a new one. Hope the new one has no problem.
Click to expand...
Click to collapse
Will try flashing the RUU on mine too. Where did you get it from?

nachochiappe said:
Will try flashing the RUU on mine too. Where did you get it from?
Click to expand...
Click to collapse
http://bbs.gfan.com/android-7629706-1-1.html
You will need to register first.

mkiderek said:
http://bbs.gfan.com/android-7629706-1-1.html
You will need to register first.
Click to expand...
Click to collapse
Great! Thanks!

The can upload to another server?, Or you can link to download private message to another server?, Thank you very much.

I am also having the same issue with my m8. Have attempted to unlock the bootloader about 15 times with a different token id each time, and nothing, its remaining locked. I also get a persistent notification to update to 2.22.1540.3 regardless of how many times I install it. Any ideas?

Same issue with me, but it actually messed up my phone for good -
Ill post the whole issue was it happened -
1. Tried to unlock bootloader using HTC Dev, 3 times. Each time it would successfully take the token and stuff, reset the phone, but the bootloader would still be locked.
I tried this using 3 separate HTC Dev accounts. Same result.
2. Now the 4th time when i did this, the phone went back the RUU firmware mode (but with 4 triangles on the corners).
3. I can boot into the stock ROM, the one the phone came with by using - fastboot oem boot. But i have to do this every time the phone shuts down or has to be restarted.
From my understanding the bootloader, recovery and hboot partitions are corrupt. Best case scenario, only the bootloader. And i cannot flash either of the partitions since im not unlocked nor S-off.
Another issue would be, why was i not able to unlock my bootloader? The first time i thought maybe i made a mistake in copying the the unlock string. But that wasn't it.
If it helps, the phone came with Android 4.4.3 with Hboot 3.18 (2.22.1540.3).
The phone is a 32 GB US Unlocked version. CID - BS_US001 MID - 0P6B12000
And i cannot for the life of me find a RUU for this phone. The phone is just 1 day old.
Any help would be appreciated. I couldn't find anyone with the same 4 triangle issue on the forums.
UPDATE :
Just fixed the bootloader issue by flashing the firmware zip from here :
http://forum.xda-developers.com/showpost.php?p=55067300&postcount=1605
Though i still have not been able to unlock the bootloader.

mkiderek said:
http://bbs.gfan.com/android-7629706-1-1.html
You will need to register first.
Click to expand...
Click to collapse
I registered and still can't download this file. Would you consider uploading for us?

soundwavedj said:
I registered and still can't download this file. Would you consider uploading for us?
Click to expand...
Click to collapse
I tried to downloaded the file from other sources, by googl'ing the file name, the file downloads a rom.zip but i cant open it no matter what.
Winrar and 7zip both say the file is corrupt.
Try this - http://pan.baidu.com/wap/share/home?uk=1275354262&third=0
Do let us know if it works for you.
I am also now facing the constant OTA update notifications. I emailed HTC Dev about the whole thing yesterday.

bloodhawk said:
I tried to downloaded the file from other sources, by googl'ing the file name, the file downloads a rom.zip but i cant open it no matter what.
Winrar and 7zip both say the file is corrupt.
Try this - http://pan.baidu.com/wap/share/home?uk=1275354262&third=0
Do let us know if it works for you.
I am also now facing the constant OTA update notifications. I emailed HTC Dev about the whole thing yesterday.
Click to expand...
Click to collapse
That link worked for the download but the download says 15 hours until complete [emoji16]

soundwavedj said:
That link worked for the download but the download says 15 hours until complete [emoji16]
Click to expand...
Click to collapse
Pretty weird.. I get around 1.5-2 MBps down from this site. My actual is 8MBps.

Try downloading from this link :
http://pan.baidu.com/share/init?shareid=1861479922&uk=288682052
Password : q7ad
I haven't still tried the file, since im waiting to hear back from HTC. Keep us posted if someone else is willing to try.

Unlock Bootloader not working
I am also having trouble unlocking bootloader through htcdev.com
I tried it about 5-6 times, it resets phone but remains locked.
Have you guys found a solution?

Do post your Firmware and Hboot version. Ill try passing on the info about other people not being able to do it to the HTC Dev.

Firmware and hboot versions
bloodhawk said:
Do post your Firmware and Hboot version. Ill try passing on the info about other people not being able to do it to the HTC Dev.
Click to expand...
Click to collapse
Firmware 2.22.1540.4
Hboot 3.18.0.0000
Thanks for your dedication

HTC One m8 stuck in fastboot mode

Okay so.. In december i rooted my phone to Cyanogenmod. I lost the phone and got it back after 6 months.
I have reinstalled everything on my computer so i dont have the cyanogenmod left, unlock code or anything just so you know.
However.
Yesterday i tried to go back to stock android, HTC Sense.
So i searched on youtube how to do it, i followed the steps and i apparently had the wrong RUU.
What happend is weird..
Somehow i could startup my phone and it looked like i still had cyanogenmod. However this time i could not load up any applications without it crashing. I could not start my wifi or anything.
So i tried everything over again.
Installing twrp and.. after that i couldnt get into recovery.
Everytime i load up fastboot and try press recovert or factory reset it says "Entering recovery..." and then it reboots into android.
So i tried to install a new RUU.
Apparently still the wrong one, and this time im stuck in fastboot. No matter what i do i cant get out from fastboot.
So i'm asking you guys, do you have any idea of what i can do?
Oh and i managed to relock my phone, even though it said "failed" on CMD, it rebooted and then it said relocked.
So i cant unlock it either now. It just says "!!ERROR!!"
So im sitting here with what i think is a bricked phone, and im hoping for the best that it isnt..
So can you help me with this? Is it possible?
I can give you all information you need if you ask for it. For now i dont know what to say about this.
EDIT: Yes i have looked through 1000 different threads about beeing stuck in fastboot. But nothing helps.
If you need pictures of how it looks or anything i can fix that.

rambofreac said:
Okay so.. In december i rooted my phone to Cyanogenmod. I lost the phone and got it back after 6 months.
I have reinstalled everything on my computer so i dont have the cyanogenmod left, unlock code or anything just so you know.
However.
Yesterday i tried to go back to stock android, HTC Sense.
So i searched on youtube how to do it, i followed the steps and i apparently had the wrong RUU.
What happend is weird..
Somehow i could startup my phone and it looked like i still had cyanogenmod. However this time i could not load up any applications without it crashing. I could not start my wifi or anything.
So i tried everything over again.
Installing twrp and.. after that i couldnt get into recovery.
Everytime i load up fastboot and try press recovert or factory reset it says "Entering recovery..." and then it reboots into android.
So i tried to install a new RUU.
Apparently still the wrong one, and this time im stuck in fastboot. No matter what i do i cant get out from fastboot.
So i'm asking you guys, do you have any idea of what i can do?
Oh and i managed to relock my phone, even though it said "failed" on CMD, it rebooted and then it said relocked.
So i cant unlock it either now. It just says "!!ERROR!!"
So im sitting here with what i think is a bricked phone, and im hoping for the best that it isnt..
So can you help me with this? Is it possible?
I can give you all information you need if you ask for it. For now i dont know what to say about this.
EDIT: Yes i have looked through 1000 different threads about beeing stuck in fastboot. But nothing helps.
If you need pictures of how it looks or anything i can fix that.
Click to expand...
Click to collapse
In fastboot, issue the command fastboot getvar all, and post the readout here. Be sure to edit out the serial # and IMEI from it though. Never post those on a public forum.
I, or someone else here, will be able to direct you to the proper RUU with that information..

xunholyx said:
In fastboot, issue the command fastboot getvar all, and post the readout here. Be sure to edit out the serial # and IMEI from it though. Never post those on a public forum.
I, or someone else here, will be able to direct you to the proper RUU with that information..
Click to expand...
Click to collapse
I have now solved it, and i will post how i did it. Thx anyway, even if it was a bit late.

rambofreac said:
I have now solved it, and i will post how i did it. Thx anyway, even if it was a bit late.
Click to expand...
Click to collapse
Yeah. I scrolled the Q&A forum this morning looking for unanswered posts. Yours was one of them. I'm glad to hear that you have fixed it.

xunholyx said:
Yeah. I scrolled the Q&A forum this morning looking for unanswered posts. Yours was one of them. I'm glad to hear that you have fixed it.
Click to expand...
Click to collapse
same problem and i cant solve it . help plz

7anata said:
same problem and i cant solve it . help plz
Click to expand...
Click to collapse
Same info needed that I asked the last user for. fastboot getvar all results, minus your ser# and IMEI

xunholyx said:
Same info needed that I asked the last user for. fastboot getvar all results, minus your ser# and IMEI
Click to expand...
Click to collapse
version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
and why there is no version main number

7anata said:
same problem and i cant solve it . help plz
Click to expand...
Click to collapse
Same problem, meaning you rooted the phone a year ago, put CM on it, then lost it and got it back 6 months later???
That's an incredible coincidence!!!!
Seriously, some constructive advice for a new forum user: DO NOT EVER say "same problem" then don't post any details on your phone and issue. It makes it virtually impossible to provide you any help. There are far too many variables such as carrier versions, software versions, and personal setups; that guarantee that issues may be similar, but never the "same". That's why its important to provide details, otherwise you just waste time us having to ask you for them.
Additionally, what were you doing with the phone that brought it to this point (stuck in fastboot)? Provide as much detail as possible (you can never really provide too much detail). Exact steps, what you were trying to flash, install or update, etc. Any error messages or other behaviors from the phone before it got stuck, etc. Also, what TWRP version? Do you have a nandroid (TWRP backup) available? Do you have a custom ROM installed?
---------- Post added at 10:40 AM ---------- Previous post was at 10:35 AM ----------
xunholyx said:
minus your ser# and IMEI
Click to expand...
Click to collapse
Also, xunholyx was very clear that you should delete your serial number and IMEI before posting getvar data. These are personal data, that should never be posted on open forums; so please delete them from the above post.
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
7anata said:
and why there is no version main number
Click to expand...
Click to collapse
Known version caused by old TWRP builds.

---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
[/COLOR]
Known version caused by old TWRP builds.[/QUOTE]
thanx alot , but i have latest version of TWRP 2.8.7.0 , how can i know version-main , thanx in advance

7anata said:
thanx alot , but i have latest version of TWRP 2.8.7.0 , how can i know version-main , thanx in advance
Click to expand...
Click to collapse
If an older version of TWRP was used at any point in the past, it would have wiped out the main version, and the only way to make it reappear is to flash a firmware or RUU.
Based on your CID and radio number, I believe your main version is 4.18.708
If you want further help, you need to provide the information I asked for (and that you have ignored):
redpoint73 said:
Additionally, what were you doing with the phone that brought it to this point (stuck in fastboot)? Provide as much detail as possible (you can never really provide too much detail). Exact steps, what you were trying to flash, install or update, etc. Any error messages or other behaviors from the phone before it got stuck, etc. Do you have a nandroid (TWRP backup) available? Do you have a custom ROM installed?
Click to expand...
Click to collapse

redpoint73 said:
If an older version of TWRP was used at any point in the past, it would have wiped out the main version, and the only way to make it reappear is to flash a firmware or RUU.
Based on your CID and radio number, I believe your main version is 4.18.708
If you want further help, you need to provide the information I asked for (and that you have ignored):
Click to expand...
Click to collapse
sorry man i didn't ignore the info , i didn't see that , iam tring to update cm 13 17/12/2015 recovery , iam on cm13 15/12/2015 rom , i solved the stuck problem but can't get excat version main so i can uroot my phone .....
and according to this link there isn't main version is 4.18.708 with cid Htc__622

M8 stop booting

My HTC M8 stop booting when appears the white screen with HTC One. I can boot with power + down volume. I unlocked and locked it again. Before all this issue, I had to dry the phone. What can I do? Best regards, Guillermo

guillote4552 said:
My HTC M8 stop booting when appears the white screen with HTC One. I can boot with power + down volume. I unlocked and locked it again. Before all this issue, I had to dry the phone. What can I do? Best regards, Guillermo
Click to expand...
Click to collapse
If you relocked the bootloader, then stuck on HTC logo screen and no OS is normal and expected. Relocking the bootloader expects RUU to be run.
You need to provide more info on what has occurred (sequence of events), and what you did exactly so far:
- "dry the phone" means it got wet, did you drop it in water? Did it fail to boot after that?
- What was the intent of unlocking the bootloader? What else did you do with it unlocked? Did you install custom recovery TWRP, root, or anything else, was it successful (give in detail, the exact results of each step).
- What was the intent of relocking the bootloader?

-Yes, it fail after drop in water
-First I tried to root and I unlock
-Then I tried to install a RUU, and relock
-I tried to install a TWRP but I get an error messaje
-I run fastboot getvar all and this is the result:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: [email protected]
version-cpld: None
version-microp: None
version-main: 6.20.502.5
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 205bdca3
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.017s

My comments/questions below in red font:
In general, you need to give a lot more details and a lot more info.
guillote4552 said:
-Yes, it fail after drop in water What do you mean "fail"? No OS, but you can get into bootloader (I would assume so, if you were then able to unlock bootloader).
-First I tried to root and I unlock So you successfully unlocked the bootloader? Installed TWRP? Then what?
-Then I tried to install a RUU, and relock What RUU (exact version number of file name)? What happened when you tried to install? Success or fail? Did you get error message? If so, what was the error message.
-I tried to install a TWRP but I get an error message What was the error message? You can't install TWRP with a locked bootloader. What are you going to try once you install TWRP?
Click to expand...
Click to collapse

Failed: once wet, nothing worked. I let it dry for a month. Loaded battery, gave me access to fastboot. Its boot stopped.
-Bootloader: effectively once dry I can access. I figured a good way was to install the OS. And I tried to root it. First I unlock it. Then I tried to load TWRP without success. I do not remember the message, sorry it happened a weeks ago.
-I send the RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined, no success
-I know how to follow instructions; I forgot about error messages, I got tired
THANKS

guillote4552 said:
-I send the RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined, no success
I forgot about error messages, I got tired
Click to expand...
Click to collapse
It's the correct RUU. So run it again, and tell us what the error message says. Can't troubleshoot, if you don't give us the required info.

ok. Could you please remember me the steps / commands I have to follow? tks!

guillote4552 said:
ok. Could you please remember me the steps / commands I have to follow? tks!
Click to expand...
Click to collapse
Did you try to run the exe format RUU on a PC, or otherwise (zip file via fastboot, or SD card method)?

- I run the RUU, until in the PC appeared severals messages. like updating ... and at the end message like congratulations, your phone is ready ...
-the phone displayed severals black screens with a green bar indicating status ...
-then its boots, i saw att logo, then htc one white screen ... I left the phone three hours ... nothing changed
- no one error message

-nothing had changed = remain the white screen with htc one

RUU messages consist of each partitions attempting to be flashed. Did any partitions indicate failure, or did they all succeed?
Either way, since you ran the RUU, and the phone still won't boot, you likely have some hardware failure due to the water damage. Software isn't going to fix this.

none error messajes during install and finished with a congratulations, "now you can use your phone"

can i do a test to know if there are hardware damage?

guillote4552 said:
can i do a test to know if there are hardware damage?
Click to expand...
Click to collapse
Not a test that I know of for that. Really, based on the fact there was water damage, and you did RUU (which writes all software/firmware partitions to stock) installed, but hasn't fixed the issue, to me means a hardware problem is very likely.

so that it RIP, what a pity

Which RUU can i flash?

So, I had a marshmallow update on my phone, and later i converted into GPE, but didn't like it. Went back to Sense, but it just doesn't feel as good as before. One day, the battery died, and when i tried turning it on, it would give me all sorts of errors. This never happened while i was on marshmallow before conversion to GPE. Had to reset it from the recovery. I think it hasn't returned to Sense properly.
As i am S-Off, i was thinking of flashing it with a RUU which is compatible with my device. Please suggest me which is compatible.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.21450002
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.708.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------------------
(bootloader) imei: --------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.090s

Based on your MID, looks like you're on a GSM M8? I'd go to HTC Dev and download their stock ROM, or go the appropriate carrier sub section for the M8 and use an RUU there.

I have read here that flashing carrier RUU can brick the device radio for good. So, this is why I wanted to confirm.

cytherian said:
I'd go to HTC Dev and download their stock ROM, or go the appropriate carrier sub section for the M8 and use an RUU there.
Click to expand...
Click to collapse
HTC does not post the RUU for his version on HTC Dev.com (many versions are not posted there)
OP's version doesn't have a carrier forum sub-section.
---------- Post added at 09:38 AM ---------- Previous post was at 09:36 AM ----------
xexux said:
(bootloader) version-main: 6.16.708.1
Click to expand...
Click to collapse
I don't know if there is an RUU for this version number.
One alternative, is to restore the TWRP backup 6.16.708.1 from here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
---------- Post added at 09:42 AM ---------- Previous post was at 09:38 AM ----------
xexux said:
Went back to Sense, but it just doesn't feel as good as before.
I think it hasn't returned to Sense properly.
Click to expand...
Click to collapse
How exactly did you go back to Sense?

I tried the guide here, but I just couldn't complete it, as i received some modelid error. Tried multiple times to no avail. So, i tried the TWRP nandroid method, and restored to Sense that way.

xexux said:
I tried the guide here, but I just couldn't complete it, as i received some modelid error. Tried multiple times to no avail. So, i tried the TWRP nandroid method, and restored to Sense that way.
Click to expand...
Click to collapse
Good to hear that it worked out and thanks for posting. :good:

cytherian said:
Good to hear that it worked out and thanks for posting. :good:
Click to expand...
Click to collapse
This is how I got Sense back, and after that, I started experiencing bugs with M8 as explained in my first post.

xexux said:
So, i tried the TWRP nandroid method, and restored to Sense that way.
Click to expand...
Click to collapse
Which TWRP backup did you restore? Did you flash firmware, or only restore the TWRP backup?

redpoint73 said:
Which TWRP backup did you restore? Did you flash firmware, or only restore the TWRP backup?
Click to expand...
Click to collapse
I restored it with the latest TWRP backup for my model. About firmware, I am not sure, but i do see that firmware version in 'fastboot var all' data.
Since I am S-off, is there any Marshmallow RUU which i can try without bricking anything? May be a developer version or RUU for european/asian variant? Or the ones linked at gsmhosting M8 page? I have read people experiencing LTE radio problem with that. I hope that's not the case anymore, and there is a work around.

xexux said:
I restored it with the latest TWRP backup for my model.
Click to expand...
Click to collapse
What version number exactly? Perhaps you still have the files on your computer, and can look?
I've seen a number of times, folks say and think they restored the right version for their model, and once we ask for version numbers, we see they actually got it wrong.
xexux said:
About firmware, I am not sure, but i do see that firmware version in 'fastboot var all' data.
Click to expand...
Click to collapse
I can see it too. But doyou actually remember manually download and flash the firmware in RUU mode?
Did you convert to GPE using the RUU?
xexux said:
Since I am S-off, is there any Marshmallow RUU which i can try without bricking anything? May be a developer version or RUU for european/asian variant? Or the ones linked at gsmhosting M8 page? I have read people experiencing LTE radio problem with that. I hope that's not the case anymore, and there is a work around.
Click to expand...
Click to collapse
It's possible. But flashing another region's RUU will also change the radio baseband, and therefore changes the specific bands supported. It may have undesirable results (not support the 3G or LTE band or bands used by your local carrier).

My htc one m8 has no os due to an unsuccessful update, I have s-on, boot loader unlocked and not fully rooted. I have twrp as recovery. What are my options to get the official ruu to flash

Bukss said:
My htc one m8 has no os due to an unsuccessful update, I have s-on, boot loader unlocked and not fully rooted. I have twrp as recovery. What are my options to get the official ruu to flash
Click to expand...
Click to collapse
First of all, the phone won't update with TWRP installed (need stock recovery) so that is one reason for the update to fail.
Also, if the ROM is not stock (such as custom ROM, root) in any way, it needs to be returned to stock in order to update. I don't know what "not fully rooted" means. But if it was rooted, you need to re-install the stock ROM (such as stock TWRP backup) as most other "unroot" methods do not work (update will still fail).
RUU will update the phone, and bypasses the above requirements. But we would need to know more about the phone to know if your version M8 has an RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

redpoint73 said:
First of all, the phone won't update with TWRP installed (need stock recovery) so that is one reason for the update to fail.
Also, if the ROM is not stock (such as custom ROM, root) in any way, it needs to be returned to stock in order to update. I don't know what "not fully rooted" means. But if it was rooted, you need to re-install the stock ROM (such as stock TWRP backup) as most other "unroot" methods do not work (update will still fail).
RUU will update the phone, and bypasses the above requirements. But we would need to know more about the phone to know if your version M8 has an RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Hello guys. I took my M8 to someone to repair and they completely messed up the phone. Now no matter how you try to boot up the phone, a black screen with a silver HTC logo in the middle and 4 silver triangles in the corner shows up. I cannot reboot into bootloader, it brings me back to the same screen. Here is a getvar of my htc one m8, i was wondering if you could point me to the right RUU to use.
c:\miniadb_m7>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 99000499834418
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 11459804
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s

Abnova said:
Hello guys. I took my M8 to someone to repair and they completely messed up the phone. Now no matter how you try to boot up the phone, a black screen with a silver HTC logo in the middle and 4 silver triangles in the corner shows up. I cannot reboot into bootloader, it brings me back to the same screen. Here is a getvar of my htc one m8, i was wondering if you could point me to the right RUU to use.
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_wlv
(bootloader) modelid: 0P6B12000
Click to expand...
Click to collapse
Wow, this is quite a mess!
Was this a repair shop, or just some person you knew that tried to "fix" the phone. Either way, it is probably apparent that they shouldn't be trusted, and don't seem too knowledgeable (at least with this specific device).
Although there are a few details I'm not clear on, and you should clarify:
1) If you can't get to bootloader, how did you do fastboot getvar all?
2) What exactly was wrong with the phone that the shop/person tried to "fix" for you (and the specific condition before you gave it to them)? Was it able to boot to OS? Something else wrong (no SIM, etc.)?
What is clear, is that your device is the US Verizon version M8 (as shown by the product ID m8_wlv). But at some point (not completely clear if it was the repair person, or before that) it had its MID changed to that of the US Developer's Edition (0P6B12000). And had the Google Play Edition (GPE) firmware and/or RUU installed.
Those last two things (changing to Dev Ed MID, and running GPE RUU/firmware) are a very bad idea on the Verizon version M8. Reason being, the Verizon M8 is peculiar, and can only run firmware/RUU intended for the Verizon variant M8 (so Verizon RUU or firmware). Installing any other RUU/firmware will result in a radio brick, possibly permanent. And is probably also the reason the phone won't boot to OS now. It may be fixable. But first, I'd like more information (items above) on the history of the phone, and exactly what was done to it before the repair person worked their "magic" (as much as you know).

redpoint73 said:
Wow, this is quite a mess!
Was this a repair shop, or just some person you knew that tried to "fix" the phone. Either way, it is probably apparent that they shouldn't be trusted, and don't seem too knowledgeable (at least with this specific device).
Although there are a few details I'm not clear on, and you should clarify:
1) If you can't get to bootloader, how did you do fastboot getvar all?
2) What exactly was wrong with the phone that the shop/person tried to "fix" for you (and the specific condition before you gave it to them)? Was it able to boot to OS? Something else wrong (no SIM, etc.)?
What is clear, is that your device is the US Verizon version M8 (as shown by the product ID m8_wlv). But at some point (not completely clear if it was the repair person, or before that) it had its MID changed to that of the US Developer's Edition (0P6B12000). And had the Google Play Edition (GPE) firmware and/or RUU installed.
Those last two things (changing to Dev Ed MID, and running GPE RUU/firmware) are a very bad idea on the Verizon version M8. Reason being, the Verizon M8 is peculiar, and can only run firmware/RUU intended for the Verizon variant M8 (so Verizon RUU or firmware). Installing any other RUU/firmware will result in a radio brick, possibly permanent. And is probably also the reason the phone won't boot to OS now. It may be fixable. But first, I'd like more information (items above) on the history of the phone, and exactly what was done to it before the repair person worked their "magic" (as much as you know).
Click to expand...
Click to collapse
Yeah I realised how big of a mess I was in when I got it back. Anyway
1.)On further investigation it seems like the the phone is in a wierd RUU mode. So it still can interface with the laptop through fastboot. Like I said earlier, trying to reboot to bootloader brings you to the same black screen with the silver Logo (see attached). When the phone is plugged in to the laptop or switches to the HTC silver Logo screen however when it's unplugged, it goes to a wierd bootloader like screen but black and only has the option for RUU. ( See attached)
2.) I took it to them to replace the battery because . The phone would switch off even at 100% battery. It only worked when it stayed plugged in , like a PC. I'm guessing the repair guys saw I had modified the software (I was running Dirty Unicorns, Android 7.1.2, Latest TWRP with a relocked Bootloader, S-Off) and had thought the problem actually had to do with the software. I live in Kenya and the HTC model available here is the international Gsm model so im guessing it seemed reasonable for them to RUU the Google play edition to try to bring it to a stable, stock, state. It most likely previously worked on the other M8's brought to them. I doubt they realized that I had imported the phone from the US, so they were probably shocked when it failed.
Anyway I hope this information helps. Thanks for your help.

Abnova said:
I live in Kenya and the HTC model available here is the international Gsm model so im guessing it seemed reasonable for them to RUU the Google play edition to try to bring it to a stable, stock, state. It most likely previously worked on the other M8's brought to them. I doubt they realized that I had imported the phone from the US, so they were probably shocked when it failed.
Click to expand...
Click to collapse
"Because it worked before" is not a good philosophy when working with these devices. Different models have their own nuances, for any smartphone. Any repair shop should be smart enough to know that different models/versions of the same phone can have major differences. And assuming otherwise can have catastrophic results!
Abnova said:
1.)On further investigation it seems like the the phone is in a wierd RUU mode.
Click to expand...
Click to collapse
Not a bad thing, if it is in fact RUU mode. You can try the Verizon RUUs. As mentioned, these are the only RUUs you should try on your device!
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
You will likely need to change back to the Verizon MID to run those RUUs. Otherwise the RUU will fail with wrong MID.
https://forum.xda-developers.com/showthread.php?t=2708581
If the phone boots to OS, but with no SIM or no signal, the repair shop flashing the wrong RUU may have bricked the radio. You can try to flash an older (Kitkat) Verizon RUU, which sometimes will fix the problem. If it does fix the radio, then you can update up to something more recent (Marshmallow).
Of course, I don't know if any of this will help your original problem of the phone shutting off when not on charger. If it is a software problem, then the original factory image (Verizon RUU) has the best chance of fixing it!

Thanks for your contribution, will definitely try tomorrow

redpoint73 said:
"Because it worked before" is not a good philosophy when working with these devices. Different models have their own nuances, for any smartphone. Any repair shop should be smart enough to know that different models/versions of the same phone can have major differences. And assuming otherwise can have catastrophic results!
Not a bad thing, if it is in fact RUU mode. You can try the Verizon RUUs. As mentioned, these are the only RUUs you should try on your device!
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
You will likely need to change back to the Verizon MID to run those RUUs. Otherwise the RUU will fail with wrong MID.
https://forum.xda-developers.com/showthread.php?t=2708581
If the phone boots to OS, but with no SIM or no signal, the repair shop flashing the wrong RUU may have bricked the radio. You can try to flash an older (Kitkat) Verizon RUU, which sometimes will fix the problem. If it does fix the radio, then you can update up to something more recent (Marshmallow).
Of course, I don't know if any of this will help your original problem of the phone shutting off when not on charger. If it is a software problem, then the original factory image (Verizon RUU) has the best chance of fixing it!
Click to expand...
Click to collapse
I'm having trouble changing the MID Because adb is not working. However, fastboot is. So I've been stuck and I don't know what to do

Abnova said:
I'm having trouble changing the MID Because adb is not working. However, fastboot is. So I've been stuck and I don't know what to do
Click to expand...
Click to collapse
Ah, yes. Good point. You need adb to change the MID.
Try booting TWRP custom recovery, which should give you adb access.
Download TWRP (I suggest the latest, version 3.2.1-0). Put it in the same folder as fastboot.exe
Then do command: fastboot boot twrp.img
Where "twrp.img" has to match the exact file name of what you downloaded (you can change the name of the file to twrp.img or else type the whole/exact file name as downloaded).
Hopefully, you will see TWRP boot on the phone. Once it does, you should have adb access.
I also believe you should be able to run root (su) commands in TWRP (which is necessary to change MID). But I don't remember if there is an extra step of not to that.
Basically, the repair shop really screwed you by changing the MID and flashing the wrong RUU. Extra steps/tricks to do now, but hopefully we can get some progress anyway.

redpoint73 said:
Ah, yes. Good point. You need adb to change the MID.
Try booting TWRP custom recovery, which should give you adb access.
Download TWRP (I suggest the latest, version 3.2.1-0). Put it in the same folder as fastboot.exe
Then do command: fastboot boot twrp.img
Where "twrp.img" has to match the exact file name of what you downloaded (you can change the name of the file to twrp.img or else type the whole/exact file name as downloaded).
Hopefully, you will see TWRP boot on the phone. Once it does, you should have adb access.
I also believe you should be able to run root (su) commands in TWRP (which is necessary to change MID). But I don't remember if there is an extra step of not to that.
Basically, the repair shop really screwed you by changing the MID and flashing the wrong RUU. Extra steps/tricks to do now, but hopefully we can get some progress anyway.
Click to expand...
Click to collapse
I tried that, it would flash then refuse to reboot to the recovery. I've tried so many things but none of them worked. My only hope is if someone edited the Android.txt file inside the Rom Zip so that the model ID is the same as that of my corrupt phone. That way it'll flash and hopefully fix it. I've tried myself but everytime I tried to edit it says the zip/archive is corrupt on WinRAR. I don't know whether it's a problem with my laptop or if it's a complication related to the rom.zip. I've downloaded it again but it still does the same thing. So basically I'm stuck because there is no way I can change the MID. This probably means the phone is bricked.

HTC One M8 stuck on HTC screen

Hi all.
Got a HTC one m8 in and it appears to be stuck on the HTC screen, I can get into bootloader fine, have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Thanks in advance.

Jabbah said:
Hi all.
Got a HTC one m8 in and it appears to be stuck on the HTC screen, I can get into bootloader fine, have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Thanks in advance.
Click to expand...
Click to collapse
What does it say next to "OS" in your bootloader menu?

Jabbah said:
have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Click to expand...
Click to collapse
Tried to flash what? Can't troubleshoot what you did wrong, unless you tell is what you tried to flash. RUU, firmware.zip, or something else? What is the version number and file name?
That is in addition to the info requested in the previous reply.
Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.

redpoint73 said:
Tried to flash what? Can't troubleshoot what you did wrong, unless you tell is what you tried to flash. RUU, firmware.zip, or something else? What is the version number and file name?
That is in addition to the info requested in the previous reply.
Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
Click to expand...
Click to collapse
Tried to flash a stock UK rom.
I have no idea how to use that command sorry.
os is 6.12.61.4

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.61.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

Jabbah said:
Tried to flash a stock UK rom.
Click to expand...
Click to collapse
Still too vague for us to have any idea what you tried to flash.
I asked some specific questions for a reason; some of which you seem to have missed or ignored. I'm not just typing to exercise my fingers!
redpoint73 said:
RUU, firmware.zip, or something else?
What is the version number and file name?
Click to expand...
Click to collapse
"Stock UK ROM" can mean a number of things. If you are talking about RUU, then calling it a "stock ROM" is not the right term (and confusing) since RUU is a complete image containing something like 41 partitions, with the ROM being only one of those partitions.
In fact, if you are referring to RUU, I don't think your version M8 (or most UK versions, for that matter) has a valid RUU. So you are likely in fact not even trying to flash a stock UK ROM. Which also explains the CID error.
On a positive note, good work figuring out how to do fastboot getvar all. If you can provide more info on what you tried to flash, we can make some progress!

redpoint73 said:
Still too vague for us to have any idea what you tried to flash.
I asked some specific questions for a reason; some of which you seem to have missed or ignored. I'm not just typing to exercise my fingers!
"Stock UK ROM" can mean a number of things. If you are talking about RUU, then calling it a "stock ROM" is not the right term (and confusing) since RUU is a complete image containing something like 41 partitions, with the ROM being only one of those partitions.
In fact, if you are referring to RUU, I don't think your version M8 (or most UK versions, for that matter) has a valid RUU. So you are likely in fact not even trying to flash a stock UK ROM. Which also explains the CID error.
On a positive note, good work figuring out how to do fastboot getvar all. If you can provide more info on what you tried to flash, we can make some progress!
Click to expand...
Click to collapse
Thanks for the replies, ive actually gotten somewhere today, Ive installed twrp, and installed the latest Lineage ROM which booted fine .
But.... Not detecting sim card
Always something haha

Another option (especially now that you have unlocked the bootloader, and installed TWRP), is restore stock TWRP backup 6.12.61.4 from here:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
No need to do Step 3, nor Steps 10 or after (only relevant to get OTA updates - which no longer applies to this device). Just reboot.
Jabbah said:
Thanks for the replies
Click to expand...
Click to collapse
There is a button for that.

Quick update, Restored stock TWRP as you suggested, performed simunlock and am now a happy chappy with a working M8
Now, Whats the best ROM to use for it ? Is it worth installing Lineage ROM?
David.

Jabbah said:
Quick update, Restored stock TWRP as you suggested, performed simunlock and am now a happy chappy with a working M8
Now, Whats the best ROM to use for it ? Is it worth installing Lineage ROM?
Click to expand...
Click to collapse
Glad the TWRP restore worked out for you.
No such thing as a "best ROM". Each individual user has different preferences and tastes. That's the reason there are different ROM choices. If there was a "best ROM", nobody would ever need anything else, right?
I am not personally a Lineage user (so good example right there how one person's opinion may not apply to you). But if you flash it again, I assume you can (or will) have the same problem with SIM not detected. I think I've seen other folks with the problem on Lineage (again, I don't really keep up with that ROM), so you should check the thread to see if there is a fix for that issue.

redpoint73 said:
Glad the TWRP restore worked out for you.
No such thing as a "best ROM". Each individual user has different preferences and tastes. That's the reason there are different ROM choices. If there was a "best ROM", nobody would ever need anything else, right?
I am not personally a Lineage user (so good example right there how one person's opinion may not apply to you). But if you flash it again, I assume you can (or will) have the same problem with SIM not detected. I think I've seen other folks with the problem on Lineage (again, I don't really keep up with that ROM), so you should check the thread to see if there is a fix for that issue.
Click to expand...
Click to collapse
Got around the sim not detected issue, the phone was simlocked to orange, it just didnt pop up with the enter unlock code dialogue.
Ill try a few see what they are like
Thanks again for your help.

Jabbah said:
Got around the sim not detected issue, the phone was simlocked to orange.
Click to expand...
Click to collapse
Understood. I would not have expected the "SIM not detected" error in that case. So thanks for clarifying.
Jabbah said:
it just didnt pop up with the enter unlock code dialogue.
Click to expand...
Click to collapse
Stock (Sense) ROM is needed to unlock SIM. Which you either figured out, or stumbled upon the solution by luck! :good: