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

no rom

I have unlocked my htc one m8 and root it but I fail in memory problem , so I install a new TWRP recovery and I wipe all data including the ROM . Now I'm stock with a unlocked bootloader and a S-On and no ROM .What should I do

thebluehammer20 said:
I have unlocked my htc one m8 and root it but I fail in memory problem , so I install a new TWRP recovery and I wipe all data including the ROM . Now I'm stock with a unlocked bootloader and a S-On and no ROM .What should I do
Click to expand...
Click to collapse
Conect to pc by cable or use microsd card. Copy new cook rom and flash by twrp recovery

thebluehammer20 said:
I wipe all data including the ROM . Now I'm stock with a unlocked bootloader and a S-On and no ROM .
Click to expand...
Click to collapse
What did you think was going to happen when wiping the system (ROM) partition?
Simple rule of thumb, do not wipe a partition if you aren't 100% sure of what it is, or what the result will be.
Another simple and fundamental rule of modding these phones, once you install TWRP, make a TWRP backup (backup the current ROM). Before doing any kinds of mods (root, custom ROM, etc) if you have a TWRP backup, you can easily revert in case you have any problems.

can I now install the official ROM . I'm now working with CM13 and I want to returm to stock htc ROM

thebluehammer20 said:
can I now install the official ROM . I'm now working with CM13 and I want to returm to stock htc ROM
Click to expand...
Click to collapse
What exactly (file name) are you trying to install?

redpoint73 said:
What exactly (file name) are you trying to install?
Click to expand...
Click to collapse
I want just to return to stock

thebluehammer20 said:
I want just to return to stock
Click to expand...
Click to collapse
hook up to your pc
fastboot getvar all and post the results here minus your serial# and IMEI (and MEID if you are on CDMA and have one), and someone will be able to direct you on the best way to return to stock, probably via RUU if there is one available.

thebluehammer20 said:
I want just to return to stock
Click to expand...
Click to collapse
This doesn't provide anymore info than you posted before. You didn't answer the question asked. I asked for the exact file name of what you intend to flash, and I asked that for a specific reason.
In particular, its completely unclear whether you are trying to flash a TWRP backup, an RUU, or something else. Further I wanted to see what version number you are trying to install.
Also, we need the getvar data as xunholyx requested to properly provide any further guidance. You simply have not provided nearly enough info for us to help you.

redpoint73 said:
This doesn't provide anymore info than you posted before. You didn't answer the question asked. I asked for the exact file name of what you intend to flash, and I asked that for a specific reason.
In particular, its completely unclear whether you are trying to flash a TWRP backup, an RUU, or something else. Further I wanted to see what version number you are trying to install.
Also, we need the getvar data as xunholyx requested to properly provide any further guidance. You simply have not provided nearly enough info for us to help you.
Click to expand...
Click to collapse
What informations do you need to help me ? does the IMEI number enough or there are others informations ?

thebluehammer20 said:
What informations do you need to help me ? does the IMEI number enough or there are others informations ?
Click to expand...
Click to collapse
They don't want your IMEI no.
Read again ...
fastboot getvar all and post the results here minus your serial# and IMEI (and MEID if you are on CDMA and have one)​

thebluehammer20 said:
What informations do you need to help me ? does the IMEI number enough or there are others informations ?
Click to expand...
Click to collapse
Did you even bother to read the responses to your post???
It perfectly clear what information we have requested.
xunholyx said:
hook up to your pc
fastboot getvar all and post the results here minus your serial# and IMEI (and MEID if you are on CDMA and have one)
Click to expand...
Click to collapse
redpoint73 said:
I asked for the exact file name of what you intend to flash, and I asked that for a specific reason.
In particular, its completely unclear whether you are trying to flash a TWRP backup, an RUU, or something else. Further I wanted to see what version number you are trying to install.
Click to expand...
Click to collapse
You've wasted 3 weeks spinning your wheels and not fixing the problem; by ignoring the requests for basic information you could/should have given when asked.

redpoint73 said:
You've wasted 3 weeks spinning your wheels and not fixing the problem; by ignoring the requests for basic information you could/should have given when asked.
Click to expand...
Click to collapse
it's over a month now
Sent from my HTC M8 using XDA Labs

redpoint73 said:
Did you even bother to read the responses to your post???
It perfectly clear what information we have requested.
You've wasted 3 weeks spinning your wheels and not fixing the problem; by ignoring the requests for basic information you could/should have given when asked.
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.24_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: ORANG309
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
​build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 205bdca3
hbootpreupdate: 11
gencheckpt: 0

thebluehammer20 said:
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.24_2G
modelid: 0P6B10000
cidnum: ORANG309
Click to expand...
Click to collapse
** remove serial & imei no in your post
Your stock ROM is 6.14.75.4
You can get it from : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

thank's a lot for your help
I did al the steps now my m8 is running on official htc sence and I've install twrp recovery and I rooted it all went good but sometimes it turn of or restart by itself and when it turned on I found some settings return to the stock like the quick settings and the navigation buttons
what could I do and what's the problem plzz

Help needed with HTC m8 (root succeeds, stuck at htc login)

Hello dear xda users,
Sometime ago, I have posted questions about my htc m8 being unable to read sim card. Unfortunately, I have still not been able to solve the issue and it stands as a wifi device at present Anyway, this post im posting is about a friend's m8 which she passed to me to inquire if i knew of a solution to fix it. Her phone, if I am not mistaken (though she says that she bought it off a phone dealer locally), is theoretically not a local device. I did a check on it and it says m8_ul. I'm currently residing in Taiwan and after looking around, m8_ul either belongs to europe or australia. She was experiencing com.process.gapps error issues and made it impossible to use the device in any and every way. Googling around, I found threads regarding this issue (or similar) asking the user to clear the cache of all google services. I proceeded to do it and the result was no different. So I thought about rooting the device and maybe even flashing to stock (or modified stock) to get the phone working again.
The problem that I have at hand is that flashing TWRP works fine. It boots into the system and I could use adb to reboot into fastboot (despite the errors popping up). After that, I rooted the phone and now it just stays on the HTC logo until the battery dies out (by leaving it for as long as need be). It is also impossible to do a normal force shutdown(holding power for x number of secs *tried using power + vol up/down/both) or the "under a bright light" method.
So is there anyone who is kind enough and willing to extend a helping hand here? With a guide or something? :crying: Thanks in advance.
Here's what I got from her my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT4BLWM04185
(bootloader) imei: 358716054985352
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.030s

you need to back to stock
download the stock TWRP backup and stock recovery for this device
restore the backup and flash the recovery may be you will get one OTA to the latest
here is the TWRP backup
https://mega.nz/#!u5ImFT5R!WZTC0Pi5Dw67xkTEoOxmezJ526WeL3EwEjrKuQgDdHU
and the stock recovery
https://mega.nz/#!rkxSAJCS!8ZFGp7AXMK_gP0Cmoj-vkqjw8VLARx82Be8cwErZwbs
and all the info you need and the instruction is here
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Sent from my HTC M8 using XDA Labs

Thank you ahmed.Ismael. I'll be downloading those in a couple. I hope it goes well. Will post here if it works fine. Thank you.

pacer3 said:
Thank you ahmed.Ismael. I'll be downloading those in a couple. I hope it goes well. Well post here if it works fine. Thank you.
Click to expand...
Click to collapse
there is no reason it will not work
GOOD LUCK
Sent from my HTC M8 using XDA Labs

pacer3 said:
She was experiencing com.process.gapps error issues and made it impossible to use the device in any and every way.
So I thought about rooting the device and maybe even flashing to stock (or modified stock) to get the phone working again.
Click to expand...
Click to collapse
To be clear, and for your information, there is no reason that root alone would fix the issue. There is something wrong with the OS (system processes) so the previous suggestion to restore the stock ROM, is a good one.
Root is just a permission change, it won't "fix" anything in itself besides that (root permissions).
Also, the symptom of rooting and being stuck on HTC logo screen is most usually because you used the wrong version TWRP and/or wrong version SuperSU to root (its common folks are trying to use really old versions of either/both). Since the device is on Marshmallow, you need to use TWRP 3.0.2 and current stable version SuperSU is 2.78.
But again, rooting even properly won't fix the core issue. Restoring the stock ROM is your best bet.

@redpoint73:
Thank you for replying as well. I guess I have to put this away till the next day as I was kinda piled with work today. Really pooped out now, so I'ma go get me some shut eyes. As for what you mentioned, yea.. (1) TWRP was working fine after flashing.. it booted normally and is still functioning properly as of now. (2) It's only after I flashed UPDATE-SuperSU-v2.37 that the m8 wouldnt get past boot screen and stays there frozen till battery drains out. (3) Well, I was thinking of removing the app that was causing the errors and fixing them by installing those applications again from scratch without touching the os and since it said something like com.process.gapps or something of the kind, I'm guessing that it's already related to the os and hence, rooting to remove the corrupted file(s) or replacing new ones (in this case, I'm guessing adb and fastboot to push the files might probably work; which would make rooting unnecessary). So yep, that's my train of thought; to make as little changes to the system, no matter how unstable it might be during the time, and working out the kinks one by one. You know, just so if my friend would need to suddenly use the phone, I might/would have fixed a portion of it for her to be able to use it at that moment. Thanks so much to the both of you. I'm hoping it'll turn out well. I mean, like ahmed.ismael said, what's there for it not to work. Having hopeful thoughts here ^.^

pacer3 said:
[MENTION=660462] It's only after I flashed UPDATE-SuperSU-v2.37 that the m8 wouldnt get past boot screen and stays there frozen till battery drains out.
Click to expand...
Click to collapse
As I guess, that version SuperSU is really old. No boot is the expected result.
pacer3 said:
[MENTION=660462] I was thinking of removing the app that was causing the errors and fixing them by installing those applications again from scratch without touching the os and since it said something like com.process.gapps or something of the kind, I'm guessing that it's already related to the os and hence, rooting to remove the corrupted file(s) or replacing new ones (in this case, I'm guessing adb and fastboot to push the files might probably work; which would make rooting unnecessary).
Click to expand...
Click to collapse
Definitely would not work. Its a system app, part of the OS, and therefore can't be modified without root. Even with root, system is write protected and requires kernel mod.
---------- Post added at 12:22 PM ---------- Previous post was at 12:20 PM ----------
pacer3 said:
I'm hoping it'll turn out well. I mean, like ahmed.ismael said, what's there for it not to work. Having hopeful thoughts here ^.^
Click to expand...
Click to collapse
I too see no reason for it not to work. Its just a software bug, and RUU will return the OS software to its original, intended condition.

sorry for not replying. im reattempting this again now and just a quick question. would rerooting with latest supersu at least fix booting? cause i dont really want to wait till battery dies out everytime i forget to boot directly into bootloader

pacer3 said:
sorry for not replying. im reattempting this again now and just a quick question. would rerooting with latest supersu at least fix booting? cause i dont really want to wait till battery dies out everytime i forget to boot directly into bootloader
Click to expand...
Click to collapse
you don't have to wait for the battery to die!!! when you boot and it boootloops just press the power button and volume up until in restarts and when it restarts quickly press the volume down and power for entering in bootloader...

pacer3 said:
sorry for not replying. im reattempting this again now and just a quick question. would rerooting with latest supersu at least fix booting?
Click to expand...
Click to collapse
It should fix the no-boot issue, yes. But you need to use the correct, up-to-date version TWRP (3.0.2) and SuperSU 2.78.

Hi all and thank you for the replies so far and sorry for the late reply. Been outstation for work again so I haven't been able to get on to reply to you guys.. Anyway, I have just completed all the steps until step 11 and now waiting on step 12 (after reboot in this tutorial http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860). Thank you for all your replies and will keep you guys posted on the progress. Hope it turns out well (crosses fingers). ^.^

Hey all. Thank you guys for assisting me with this problem. It has been fixed. ^.^ I dont know how i can repay you guys for assisting me, especially ahmed.ismael for providing the links and guide. It has been a big help for me. I deeply thank you guys for giving a helping hand here. Wish it could fix my problem with my own m8 HK edition.

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:

htc one m8 no sim/ network mode after Ruu install

hi all
the mother in law gave me her broken htc one m8 phone too look at as it was stuck on the htc boot screen.
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
the problem i am now having is that the phone wont let me choose a network mode as its blanked off and not able to choose, which also means when i enter a sim it just doesnt work.
i have done a fastboot getvar all and details follow
(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.401.4
(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: 0P6B10000
(bootloader) cidnum: HTC__001
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
any help would be greatfully appreciated

First of all, you posted in the General M8s section. The M8s is a variant with different hardware. You have the M8 (no "s") which has it's own General forum section, but you should post questions like this in the M8 Q&A section, anyway. Don't make another post, I'll ask the mods to move this one to the right place.
s84taylo41984 said:
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
Click to expand...
Click to collapse
Those are not RUU (as your thread title states). An RUU is an official HTC tool, which is run from bootloader. What you linked are stock TWRP backups, which are flashed using TWRP.
Which TWRP backup version number did you flash? What version TWRP did you use?
---------- Post added at 01:02 PM ---------- Previous post was at 12:59 PM ----------
s84taylo41984 said:
(bootloader) imei:
Click to expand...
Click to collapse
Is there an IMEI number listed? I know it's the right thing to leave this out, when posting online. But just want to make sure that is the case (and it is not actually missing from the getvar output as you see it). I don't want or need to know the IMEI number, just whether you can actually see it or not.

I realised i posted in the wrong section about 1 hour ago when i was looking through some other posts on here and noticed there was a differnce in the m8 and m8s.
yes IMEI is there. i just blanked it off when posting

Quote:
Originally Posted by s84taylo41984
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
https://forum.xda-developers.com/htc...-twrp-t3086860.
Those are not RUU (as your thread title states). An RUU is an official HTC tool, which is run from bootloader. What you linked are stock TWRP backups, which are flashed using TWRP.
Click to expand...
Click to collapse
Oh i thought that they all worked the same, didnt realise they was so different!
Which TWRP backup version number did you flash? What version TWRP did you use?
Click to expand...
Click to collapse
I used TWRP 3.3.1-0 amd followed the whole of that guide, i thought it was RUU not stock.

s84taylo41984 said:
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
Click to expand...
Click to collapse
What does that mean "mostly" working?
Seems you are going about this a bit haphazardly. You didn't answer all my questions, but instead decided to search around for you own solutions (we may have gotten you there faster).

redpoint73 said:
What does that mean "mostly" working?
Seems you are going about this a bit haphazardly. You didn't answer all my questions, but instead decided to search around for you own solutions (we may have gotten you there faster).
Click to expand...
Click to collapse
Mostly working as in i wasnt able to get the wifi to enable on the phone until i flashed the TWRP Backup collection in 3, and then flashed the stock recovery image's from post 4 and the signed firmware in post 5 all with the 6.12.401.4 and CID HTC__001
MID 0P6B10000

s84taylo41984 said:
Mostly working as in i wasnt able to get the wifi to enable on the phone until i flashed the TWRP Backup collection in 3, and then flashed the stock recovery image's from post 4 and the signed firmware in post 5 all with the 6.12.401.4 and CID HTC__001
MID 0P6B10000
Click to expand...
Click to collapse
WiFi not turning on is due to restoring the wrong stock TWRP backup which does not correspond to the installed firmware. As I mentioned, this is something we could have identified much earlier, if you supplied the requested info (questions I asked days ago).

what questions did you want me to answer to answer days ago??
is there anything that can be done for me to get the phone working again???

s84taylo41984 said:
what questions did you want me to answer to answer days ago??
Click to expand...
Click to collapse
redpoint73 said:
Which TWRP backup version number did you flash?
Click to expand...
Click to collapse
s84taylo41984 said:
is there anything that can be done for me to get the phone working again???
Click to expand...
Click to collapse
Not clear to me what doesn't work now. You already said the WiFi was fixed once you flashed the signed firmware.

redpoint73 said:
Not clear to me what doesn't work now. You already said the WiFi was fixed once you flashed the signed firmware.
Click to expand...
Click to collapse
Yes the WIFI started working after flashing the signed firmware but as posted in my original post, i am unable to select network mode to choose a network even with a sim card inserted it just says no sim card, emergency calls only!
The TWRP backup version i flashed was 6.12.401.4

s84taylo41984 said:
Yes the WIFI started working after flashing the signed firmware but as posted in my original post, i am unable to select network mode to choose a network even with a sim card inserted it just says no sim card, emergency calls only!
Click to expand...
Click to collapse
Not sure I necessarily have an answer for you. But at least so if I understand the sequence of events correctly:
1) You received the phone in "no boot" condition.
2) (Unlocked bootloader?). Restored stock TWRP backup 6.12.401.4 using TWRP 3.3.1-0.
3) Able to boot the phone, but no SIM and no WiFi.
4) (Relocked bootloader presumably). Flashed firmware 6.12.401.4. Also flashed stock recovery.
5) WiFi is not working, still no SIM.

redpoint73 said:
Not sure I necessarily have an answer for you. But at least so if I understand the sequence of events correctly:
1) You received the phone in "no boot" condition.
2) (Unlocked bootloader?). Restored stock TWRP backup 6.12.401.4 using TWRP 3.3.1-0.
3) Able to boot the phone, but no SIM and no WiFi.
4) (Relocked bootloader presumably). Flashed firmware 6.12.401.4. Also flashed stock recovery.
5) WiFi is not working, still no SIM.
Click to expand...
Click to collapse
i never unlocked the bootloader just booted the phone into bootloader
the WiFi is working, just no SIM

s84taylo41984 said:
i never unlocked the bootloader just booted the phone into bootloader
Click to expand...
Click to collapse
Was the phone already bootloader unlocked when you received it? Does it say LOCKED, UNLOCKED, or RELOCKED near the top of the bootloader screen?
You can't install TWRP with a locked bootloader (while s-on).

It says RELOCKED now when i put the phone in to bootloader. I have no idea if the bootloader was unlocked when i recieved the phone i cant remember

s84taylo41984 said:
It says RELOCKED now when i put the phone in to bootloader. I have no idea if the bootloader was unlocked when i recieved the phone i cant remember
Click to expand...
Click to collapse
The only way it could have been bootloader unlocked when you got the device, and relocked after, is if you relocked it yourself, with fastboot command: fastboot oem lock
Did your mother-in-law or someone she know, mod the phone? Or did she obtain it used or from a 3rd party vendor? If it was RELOCKED when you received it, it was definitely modded by someone at some point.
The only way the bootloader can be locked (or relocked) and you can still flash TWRP, is if the device is s-off, but has the security flag spoofed to say it is s-on.

redpoint73 said:
The only way it could have been bootloader unlocked when you got the device, and relocked after, is if you relocked it yourself, with fastboot command: fastboot oem lock
Did your mother-in-law or someone she know, mod the phone? Or did she obtain it used or from a 3rd party vendor? If it was RELOCKED when you received it, it was definitely modded by someone at some point.
The only way the bootloader can be locked (or relocked) and you can still flash TWRP, is if the device is s-off, but has the security flag spoofed to say it is s-on.
Click to expand...
Click to collapse
I did relock it using the fastboot oem lock command.
She did have somebody look at it before me and it was the same thing.