Develop Bugs

[Problem] With Unroot, OTA update and Version-main not showing

First of all , Hi everyone ! And please excuse my english, it's not my native language... (wich is French)
I did not want to brick my HTC One (m8) so i went here before to do something wrong.
I received my phone the first august and I rooted it 5 days ago, when it was in kitkat 4.4.2. I did not know that i had to update it to 4.4.3 (even if every man in earth should use his brain and do the update) before to root it.... (because now i can't install custom rom to use link2sd efficiently because all of the best custom rom (that actually use .ext partition on Micro Sd card) are in android kitkat 4.4.3 or 4.4.4)
I know that this question has been asked several times but i did not find the answer for my problem, so i'm really sorry to ask this but i have to.
Okay I rooted my htc when it was in 4.4.2 with TheUnlockr methode on youtube and since then the only things that I did is :
install busybox (twrp) , es explorateur, titanium backup, diskdigger,airdroid,apptoide,root checker, lucky patcher and clean master, NOTHING else.
Now i have to unroot my HTC to finally update it to 4.4.3
Problem is : when i do "getvar all" with hasoon200's toolkit (i'm following TheUnlockr's method to unroot the phone correctly), the field where i should find my version-main is EMPTY, and I absolutly don't know how to find it since I'm a total beginner on android.
My info : HTC ONE (m8)
Rooted with kitkat 4.4.2 (TWRP recovery)
actual software in : 1.54.401.10
cidnum: HTC__203
By any chance , can anyone help me ? THX 3000 times in advance since i'm totally lost !

That NOTHING else appears to include installing TWRP 2.7.1.x, which is where the problem lies, I don't know how to get it back, other than to reflash the firmware... Catch 22 if you don't know what it is.
Perhaps narrow down with a search of MID, CID and radio version.

Sorry man i did not understand
Here is what i have got when I do a getvar :
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH443WM13877
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.005s

Howard X said:
Sorry man i did not understand
Here is what i have got when I do a getvar :
...
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
...
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
Click to expand...
Click to collapse
FIRST: you should delete your IMEI from your post above!
Second: it is a known issue with TWRP that, after installing it version-main is no longer shown in bootloader, as already statet in this thread.
If what you wrote is correct you are on 4.4.2 with FW 1.54.401.10.
To unroot you could search for the unsupersu.zip and install it with TWRP.
After this you can download stock recovery 1.54.401.10 (assuming you data is correct and you are on the given Android version. This should enable you to receive AND install OTAs again.
The problem is, that without S-Off it is not that easy to flash the actuall FW again.

HTCNerdYoda said:
FIRST: you should delete your IMEI from your post above!
Second: it is a known issue with TWRP that, after installing it version-main is no longer shown in bootloader, as already statet in this thread.
If what you wrote is correct you are on 4.4.2 with FW 1.54.401.10.
To unroot you could search for the unsupersu.zip and install it with TWRP.
After this you can download stock recovery 1.54.401.10 (assuming you data is correct and you are on the given Android version. This should enable you to receive AND install OTAs again.
The problem is, that without S-Off it is not that easy to flash the actuall FW again.
Click to expand...
Click to collapse
Okay i managed to S-OFF.
Do i follow the Unlocker way now or do I just use the unsuperuser from X site ?
Is it sure that i have to download the 1.54.401.10 stock firmware ? cause noone of these are with the htc_203
Thx verrry much in advance guys !

Howard X said:
Okay i managed to S-OFF.
Do i follow the Unlocker way now or do I just use the unsuperuser from X site ?
Is it sure that i have to download the 1.54.401.10 stock firmware ? cause noone of these are with the htc_203
Thx verrry much in advance guys !
Click to expand...
Click to collapse
Ok you are S-Off and got 4.4.2 with ROM version 1.54.401.10 installed right!?
If so install the unsupersu.zip in TWRP and download firmware for ROM version 1.54.401.10. After you installed the unsupersu.zip reboot to bootloader and run the following commands:
fastboot oem rebootRUU
fastboot flash zip nameoffirmware.zip
DO IT AGAIN TO FLASH IT CORRECTLY!!!
fastboot flash nameoffirnware.zip
fastboot reboot-bootloader
Make sure OS is showing in Hboot. HBoot should be 3.16 and radio 1.16 if I remember correctly.
Congrats you are back to full stock. Reboot phone and check for OTA.
Sent from my HTC One_M8 using XDA Free mobile app

The bug within TWRP has been identified, a fix has been submitted to the Gerrit of TWRP and it was also already verified and accepted.
The Next update of TWRP for the M7 and M8 should include it, if it's being build from the main tree.
mobile post

Howard X said:
First of all , Hi everyone ! And please excuse my english, it's not my native language... (wich is French)
I did not want to brick my HTC One (m8) so i went here before to do something wrong.
I received my phone the first august and I rooted it 5 days ago, when it was in kitkat 4.4.2. I did not know that i had to update it to 4.4.3 (even if every man in earth should use his brain and do the update) before to root it.... (because now i can't install custom rom to use link2sd efficiently
By any chance , can anyone help me ? THX 3000 times in advance since i'm totally lost !
Click to expand...
Click to collapse
Hello OP
Here is the Thread that talks about why the Version-main / OS is blank in HBOOT mode aka (Bootloader)
http://forum.xda-developers.com/showpost.php?p=53733669&postcount=1592
Thanks

jcbjoe said:
Hello OP
Here is the Thread that talks about why the Version-main / OS is blank in HBOOT mode aka (Bootloader)
http://forum.xda-developers.com/showpost.php?p=53733669&postcount=1592
Thanks
Click to expand...
Click to collapse
Hi guys I have almost the same problem
I had a custom recovery an Unlocked bootloader
But with CMD i flashed the stock recovery and relocked my phone to get the 4.4.4 update But I still has this message : There is no update available on your phone!
My software number is: 2.22.401.2
Any solution please :victory:
I called HTC support and they saied that my phone rooted ist and it still dont become any update more !!!

AnJo_Droid said:
Hi guys I have almost the same problem
I had a custom recovery an Unlocked bootloader
But with CMD i flashed the stock recovery and relocked my phone to get the 4.4.4 update But I still has this message : There is no update available on your phone!
My software number is: 2.22.401.2
Any solution please :victory:
I called HTC support and they saied that my phone rooted ist and it still dont become any update more !!!
Click to expand...
Click to collapse
This isn't even a similar issue as the OP, and this thread is 2 months old. Really shouldn't have dug up this old thread and posted to it. A different thread, or starting your own would have been more relevant.
Rooted phones still get the OTA notfication and download, they just won't install if it detects any system files have been modified.
Also, relocking the bootloader is not necessary to get the OTA or install.
Something else is going on. If you are stock ROM and stock reocvery, thre is no reason you shouldn't get and be able to install the OTA. Sometimes a factory reset will prompt the OTA to come through, for no explicable reason.

redpoint73 said:
This isn't even a similar issue as the OP, and this thread is 2 months old. Really shouldn't have dug up this old thread and posted to it. A different thread, or starting your own would have been more relevant.
Rooted phones still get the OTA notfication and download, they just won't install if it detects any system files have been modified.
Also, relocking the bootloader is not necessary to get the OTA or install.
Something else is going on. If you are stock ROM and stock reocvery, thre is no reason you shouldn't get and be able to install the OTA. Sometimes a factory reset will prompt the OTA to come through, for no explicable reason.
Click to expand...
Click to collapse
Ok thanks, I have already reset my phone to factory via stock recovery and I have no root and stock recovery & Rom .. so I should wait to become it
I live in germany and maybe its not available in my region ?
And sorry about posting here but I need an quick answer:fingers-crossed:

AnJo_Droid said:
Ok thanks, I have already reset my phone to factory via stock recovery and I have no root and stock recovery & Rom .. so I should wait to become it
I live in germany and maybe its not available in my region ?
Click to expand...
Click to collapse
You should check around the forums to see if your specific version has had 4.4.4 rolled out. But I know most (if not all) Euro versions have been updated by now.
AnJo_Droid said:
And sorry about posting here but I need an quick answer
Click to expand...
Click to collapse
Your issue is no more urgent than anyone else here, that takes the time to post to an appropriate thread.

Seeking quick answers and not researching anything will always lead to more issues and maybe serious ones.
Read, learn, read.... Then do. That's the XDA spirit.
If anyone has no time for that.... Then this hobby may not be for you. ?
This has been a public service announcement.

H3G__001 stock lollipop nandroid

Hi im trying to update to lollipop on my 3 UK branded m8 but im having serious issues upgrading to 4.4.4 eye experience version 3.32.771.3 was wondering if anyone has or could get a nandroid of the stock 4.20.771.2 ROM. I can see an OTA in http://forum.xda-developers.com/showthread.php?t=2701376 but I have no idea how to use those OTA files. Any help would be appreciated.

Post your fastboot getvar all result (minus serial no. & imei no.)
then we know which backup that you really need.
No point to give you 4.20.771.2 backup for now.

ckpv5 said:
Post your fastboot getvar all result (minus serial no. & imei no.)
then we know which backup that you really need.
No point to give you 4.20.771.2 backup for now.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.771.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
hmmm it says OS version 4.20.771.2 there but in about phone --> software info. it says 2.22.771.5 for software number. not sure what that means?!

Try restore my backup and see how it goes : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598

ckpv5 said:
Try restore my backup and see how it goes : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598
Click to expand...
Click to collapse
cool thanks. I tried your nandroid backup and it starts up fine but I cant connect to my wifi network. It sees the network but it wont connect. It does allow me to connect to another open network I can see but not my own. This happened on one of the stock updates I did too. Any ideas why this might be? or how it might be fixed?

f_padia said:
cool thanks. I tried your nandroid backup and it starts up fine but I cant connect to my wifi network. It sees the network but it wont connect. It does allow me to connect to another open network I can see but not my own. This happened on one of the stock updates I did too. Any ideas why this might be? or how it might be fixed?
Click to expand...
Click to collapse
There are two options :
1. Restore 3.32.771.10 backup and its stock recovery image then do OTA to 4.20.771.2
You can have all the needed files here : http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1897
Or
2. Reflashed the untouched 4.20.771.2 firmware that linked here : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598
but you need to relock bootloader in order to do that.
a. put your device in bootloader/fastboot mode
b. relock bootloader - fastboot oem lock
c. run these commands
fastboot oem rebootRUU
fastboot flash zip 4.20.771.2_firmware.zip
fastboot flash zip 4.20.771.2_firmware.zip .....( again for the 2nd time)
fastboot reboot
d. check your wifi
For me .. 1st option is a better choice

ckpv5 said:
There are two options :
1. Restore 3.32.771.10 backup and its stock recovery image then do OTA to 4.20.771.2
You can have all the needed files here : http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1897
Or
2. Reflashed the untouched 4.20.771.2 firmware that linked here : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598
but you need to relock bootloader in order to do that.
a. put your device in bootloader/fastboot mode
b. relock bootloader - fastboot oem lock
c. run these commands
fastboot oem rebootRUU
fastboot flash zip 4.20.771.2_firmware.zip
fastboot flash zip 4.20.771.2_firmware.zip .....( again for the 2nd time)
fastboot reboot
d. check your wifi
For me .. 1st option is a better choice
Click to expand...
Click to collapse
so I tried option 2 first and that didnt work Then I tried option 1. Flashing 3.32.... worked ok wifi working etc. I then did the OTA that popped up. That flashed and it boots up but system ui force closes and wifi doesnt turn on at all Is there anyway to flash your OTA update specifically and avoid downloading and flashing the one that pops up on screen?

f_padia said:
so I tried option 2 first and that didnt work Then I tried option 1. Flashing 3.32.... worked ok wifi working etc. I then did the OTA that popped up. That flashed and it boots up but system ui force closes and wifi doesnt turn on at all Is there anyway to flash your OTA update specifically and avoid downloading and flashing the one that pops up on screen?
Click to expand...
Click to collapse
You can't flash OTA manually because your device is S-On.
When you have system ui force close and wifi doesn't turn on at all ... that's a good sign.
What you need to do now is unlock bootloader again with unlock_code.bin that you received from HTC. Then install TWRP 2.8.5.0. Boot to TWRP recovery, select mount - advance - format data - yes
Reboot - check your wifi again - system ui should work and wifi should work too.
Then restore my 4.20.771.2 backup (reason is when re-unlock bootloader and format data .. all data files such as calculator & flashlight & etc are removed)
EDIT : before you do the above, please try boot to recovery where you see the red triangle .. press & hold volume up & press power once.
In stock recovery, select factory reset/wipe data ... reboot

ckpv5 said:
You can't flash OTA manually because your device is S-On.
When you have system ui force close and wifi doesn't turn on at all ... that's a good sign.
What you need to do now is unlock bootloader again with unlock_code.bin that you received from HTC. Then install TWRP 2.8.5.0. Boot to TWRP recovery, select mount - advance - format data - yes
Reboot - check your wifi again - system ui should work and wifi should work too.
Then restore my 4.20.771.2 backup (reason is when re-unlock bootloader and format data .. all data files such as calculator & flashlight & etc are removed)
EDIT : before you do the above, please try boot to recovery where you see the red triangle .. press & hold volume up & press power once.
In stock recovery, select factory reset/wipe data ... reboot
Click to expand...
Click to collapse
before I saw your message I did a factory rest from stock recovery as you suggested in your edit and system ui force close was fixed and wifi does turn on... but im back to the problem of not being able to connect to my wifi network. I've managed to connect to 2 separate open (public) networks fine but cant connect to mine for some reason. I cant understand why this might be happening.
Thanks for all the help by the way really appreciate it!

That's something I'm not familiar with as I never have that problem before. I read a few thread of this kind of wifi problem .. there are a few suggestions such as reset the router, try change wifi password and a few more like 2.4GHz & 5.0 GHz problem
Maybe someone else more familiar with this kind of problem will step in.

ckpv5 said:
That's something I'm not familiar with as I never have that problem before. I read a few thread of this kind of wifi problem .. there are a few suggestions such as reset the router, try change wifi password and a few more like 2.4GHz & 5.0 GHz problem
Maybe someone else more familiar with this kind of problem will step in.
Click to expand...
Click to collapse
I had a look around and came across this http://www.pcadvisor.co.uk/how-to/g...llipop-solve-wi-fi-problems-on-nexus-devices/ where it suggests changing wifi router channel. I did and it works
Cant thank you enough dude. i've tried to thank all your posts to reflect how many thanks you deserve! At one point when one of the software updates went bad and the screen wouldnt turn on I was told HTC would charge around £200 to fix it! so yeah, thanks

Great :good::good:
Will keep that in mind in case someone else has same problem

-deleted-

Lost RUU backup
Hi I to am trying to revert back to stock on my HTC one M8 (Three UK H3g__00)1 but I have lost my original backups do to an hdd fail the RUU files you posted on here I believe I could have used but the links no longer work
My phone is in a bad way at the moment it is softbricked with the latest version of CWRM on and no OS currently installed, is this why my version main appears blank?
My phone has ended up in this state after trying to install the latest android revolution rom (5.0.1). The rom seemed to install ok booted and setup fine but my Wifi wouldn't turn ON at all. After I rebooted the phone for the first time it got stuck in a boot loop.
I deally would like to get lollipop on the phone and doing some reading I believe with the situation I'm in I have to go back to stock and do the OTA updates to raise my hboot version to 3.18 or above, that way I could install cyanogen 12.1
Apologies for noob question still learning.
My bootloader (3.16) is tampered, unlocked and S-ON
D:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: H3G__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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s

lv426HuDz said:
Hi I to am trying to revert back to stock on my HTC one M8 (Three UK H3g__00)1 but I have lost my original backups do to an hdd fail the RUU files you posted on here I believe I could have used but the links no longer work
My phone is in a bad way at the moment it is softbricked with the latest version of CWRM on and no OS currently installed, is this why my version main appears blank?
My phone has ended up in this state after trying to install the latest android revolution rom (5.0.1). The rom seemed to install ok booted and setup fine but my Wifi wouldn't turn ON at all. After I rebooted the phone for the first time it got stuck in a boot loop.
I deally would like to get lollipop on the phone and doing some reading I believe with the situation I'm in I have to go back to stock and do the OTA updates to raise my hboot version to 3.18 or above, that way I could install cyanogen 12.1
Apologies for noob question still learning.
My bootloader (3.16) is tampered, unlocked and S-ON
Click to expand...
Click to collapse
First - remove the serial no. & imei no. on your above post.
Second - install TWRP 2.8.1.0, don't use CWM recovery.
Third - read this thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
for how-to and restore 1.54.771.9 backup & its matching recovery then do multiple OTAs up to the latest 4.xx.771.x

ckpv5 said:
First - remove the serial no. & imei no. on your above post.
Second - install TWRP 2.8.1.0, don't use CWM recovery.
Third - read this thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
for how-to and restore 1.54.771.9 backup & its matching recovery then do multiple OTAs up to the latest 4.xx.771.x
Click to expand...
Click to collapse
Hi ckpv5, thanks I will give this a try now, I did try to flash TWRP 2.8.7.0 recently but when I tried to enter the recovery it just hung and I never figured out why. I will give 2.8.1.0 a go now.
Last night, just to get my phone working I flashed on cm-11-20141112-SNAPSHOT-M12-m8 with open_gapps-arm-4.4-mini-20151203. It all seemed to be working fine and I liked the look and feel of the KitKat cyanogenmod but after I received my first phone call my phone speaker went crazy and gave some nasty distortion out, I rebooted the phone to stop it and now I have the noise on everything if I turn my volume up to mid/high, I'm worried my speakers are damaged. I followed a couple of threads to install the viperapp but with no success, any ideas on this one?
Cheers,

Thanks
CHeers ckpv5 Ifollowed the guide used the files and its all sorted now.
Looks like CM11 has damaged my bottom speaker though i have ordered a replacement.
I do have 1 last question, after all the updating i have now put cm12.1 on and it seems to be running ok however when im booted into the OS my SD card is not being detected. If i drop back into TWRP recovery it does recognise the SD card, any ideas? im searching for a solution now.

I can't comment anything on CM as I never use one .. no experience on CM .. sorry.

HELP PLEASE HTC ONE M8 stuck on bootloader when flashing stock rom

Hi all,
I have installed the rom GPE with this cid and mid, S-off but i lost my carrier, sim is no unlocked. Then i try to back to stock rom. The big mistake i have do is to do no backup of my original CID and MID. So during 3 mouths i had try all solutions that i see on the web ex :
Fashing splash firmware : 1.54.401.5 with stock rom but the phone always stuck on bootloader
Then i try 1.54.401.10 , 4.16.401.5 , 4.16.401.10 and last 2.22.401.4 with there rom stock and sotck recovery but nothing change, always stuck on bootloader.
NB : i'm in super CID
I have try :
1) wirecid : supercid or HTC__001 or HTC__J15 etc...
2) Flashing firmware 1.54.401.5, 1.54.401.10, 4.16.401.5, 4.16.401.10, 2.22.401.4
3) flashing custom recovery twrp
4) format data and changing partition cache because it's always corruped after flashing new firmware
5) install rom stock with there firmware :
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed.zip
m8_4.16.401.10_AROMA.zip
One_M8_4.16.401.10_stock_system_dump.zip
insertcoin-7.1.9-REPACK-M8_UL_L50_SENSE70_MR_HTC_Europe_4.16.401.10.zip
rom_one_m8_2.22.401.4_odexed.zip revolution HD
Android_Revolution_HD-One_M8_45.0_758ff1.zip
m8_1.54.401.5_AROMA
6) reboot phone, but stuck on bootloader
7) try to flash boot.img and stock recovery on the firmware but nothing change,
8) try to enter to stock recovery but redirected in bootloader
9) try to lock bootloader
I have do this with all firmware and rom
I have try to install with ruu.exe but the application have error 155, i have change the cid and mid to match with in the androidinfo.txt.
!!! But boot with custom like CM12, Carbon rom etc... the only problem is that the simcard is not detected.
If anyone have other solution ?
My last 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.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------
(bootloader) imei: --------
(bootloader) imei2: Not Support
(bootloader) meid: --------
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please help, i will become the master of reflashing rom and firmware on HTC ONE M8 but corrupted.

Someone can help me ?
Someone can help me ?
kimpak said:
Hi all,
I have installed the rom GPE with this cid and mid, S-off but i lost my carrier, sim is no unlocked. Then i try to back to stock rom. The big mistake i have do is to do no backup of my original CID and MID. So during 3 mouths i had try all solutions that i see on the web ex :
Fashing splash firmware : 1.54.401.5 with stock rom but the phone always stuck on bootloader
Then i try 1.54.401.10 , 4.16.401.5 , 4.16.401.10 and last 2.22.401.4 with there rom stock and sotck recovery but nothing change, always stuck on bootloader.
NB : i'm in super CID
I have try :
1) wirecid : supercid or HTC__001 or HTC__J15 etc...
2) Flashing firmware 1.54.401.5, 1.54.401.10, 4.16.401.5, 4.16.401.10, 2.22.401.4
3) flashing custom recovery twrp
4) format data and changing partition cache because it's always corruped after flashing new firmware
5) install rom stock with there firmware :
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed.zip
m8_4.16.401.10_AROMA.zip
One_M8_4.16.401.10_stock_system_dump.zip
insertcoin-7.1.9-REPACK-M8_UL_L50_SENSE70_MR_HTC_Europe_4.16.401.10.zip
rom_one_m8_2.22.401.4_odexed.zip revolution HD
Android_Revolution_HD-One_M8_45.0_758ff1.zip
m8_1.54.401.5_AROMA
6) reboot phone, but stuck on bootloader
7) try to flash boot.img and stock recovery on the firmware but nothing change,
8) try to enter to stock recovery but redirected in bootloader
9) try to lock bootloader
I have do this with all firmware and rom
I have try to install with ruu.exe but the application have error 155, i have change the cid and mid to match with in the androidinfo.txt.
!!! But boot with custom like CM12, Carbon rom etc... the only problem is that the simcard is not detected.
If anyone have other solution ?
My last 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.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------
(bootloader) imei: --------
(bootloader) imei2: Not Support
(bootloader) meid: --------
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please help, i will become the master of reflashing rom and firmware on HTC ONE M8 but corrupted.
Click to expand...
Click to collapse

Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A

Hold Power + Volume Up for at-least 20secs and when screen turns black, release the buttons and hold Volume Down until you enter bootloader... which is mainly couple of seconds.

Mr_Jack_Frost said:
Hold Power + Volume Up for at-least 20secs and when screen turns black, release the buttons and hold Volume Down until you enter bootloader... which is mainly couple of seconds.
Click to expand...
Click to collapse
The OP is already in bootloader, and stuck there.

CID Numbers (Sprint only):
SPCS_001: standard Sprint M8
SPCS_004: Harman/Kardon version M8
I would try to rewrite the correct cid--> Update Hboot to 3.19-->Relock Bootloader-->Flash latest Ruu
---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------
bombo_b said:
CID Numbers (Sprint only):
SPCS_001: standard Sprint M8
SPCS_004: Harman/Kardon version M8
I would try to rewrite the correct cid--> Update Hboot to 3.19-->Relock Bootloader-->Flash latest Ruu
Click to expand...
Click to collapse
Tho latest Ruu should already contain the 3.19 Hboot

bombo_b said:
I would try to rewrite the correct cid--> Update Hboot to 3.19-->Relock Bootloader-->Flash latest Ruu
Click to expand...
Click to collapse
In addition to your comment, that hboot does not need to be updated before RUU (RUU will do it):
1) Need to change MID back to Sprint MID to RUU
2) Shouldn't need to change CID, but it doesn't hurt to do so.
3) No need to relock bootloader to RUU, since OP is s-off.
But I agree, the OP should try to RUU back to Sprint stock image. (and obviously take the actions to meet the requirements to do so). After that, if is still doesn't work its probably a radio brick.

redpoint73 said:
In addition to your comment, that hboot does not need to be updated before RUU (RUU will do it):
1) Need to change MID back to Sprint MID to RUU
2) Shouldn't need to change CID, but it doesn't hurt to do so.
3) No need to relock bootloader to RUU, since OP is s-off.
But I agree, the OP should try to RUU back to Sprint stock image. (and obviously take the actions to meet the requirements to do so). After that, if is still doesn't work its probably a radio brick.
Click to expand...
Click to collapse
Error 155 is usually fixed by relocking Bootloader. Since the phone is in a funny state I would advise putting all chances on your side. Dont worry if the logic says S-off doesnt need BL relocked , you just need every chance to flash Stock ruu back to the phone

Thanks, i will try it...
So, if it's work i can unlock the phone to use another operator ?
ckpv5 said:
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Click to expand...
Click to collapse

Amazing, it's work :highfive:
Actualy, i'm working to unlock the SIM now....
ckpv5 said:
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Click to expand...
Click to collapse
kimpak said:
Thanks, i will try it...
So, if it's work i can unlock the phone to use another operator ?
Click to expand...
Click to collapse

All right tout marche bien
kimpak said:
Amazing, it's work :highfive:
Actualy, i'm working to unlock the SIM now....
Click to expand...
Click to collapse

kimpak said:
All right tout marche bien
Click to expand...
Click to collapse
Good to hear that it worked for you.

How do you saw that my phone is for sprint version ?
ckpv5 said:
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Click to expand...
Click to collapse

kimpak said:
How do you saw that my phone is for sprint version ?
Click to expand...
Click to collapse
(bootloader) product: m8_whl
m8_whl is Sprint device
m8_ul is GSM device

Boot Loader Loop, Unlocked, S-Off, Rooted HTC M8 Tmobile
A year ago I believe I used HBoot and or Firewater to root my M8. I recently removed some applications that seemed to make my phone act funny, and now the phone is stuck in a boot loop, or rather just a boot and stop at the second HTC "One" screen. Not exactly a loop.
I've download ADB tool and tried the fastboot method to install TWRP but have no success because the computer does not recognize the phone while running ADB or Fastboot, therefore I cant install TWRP and am stuck in the bootloader menu. I have tried various different cables and restarted the pc several times, and installed htc sync and other drivers necessary for that process. Also uninstalled and installed different drivers later as well. Now im not sure what i have installed but I have access to the phones internal drive via explorer.
Using Hboot.
Stats:
***UNLOCKED***
M8_UL PVT SHIP S-OFF
CID-HTC__32
RADIO- 1.15.2133156
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMc-boot 2048MB
Mar 22 2014, 00:53:32.0
Options:
HBOOT (when scanning says that all images are not found)
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMART SD
IMAGE CRC
SHOW BARCODE
Recovery leads to nothing and eventually returns to the HTC One menu stop.
Reset does nothing, acts like fast boot actually.
Ramdump under fastboot seems to works, and does produce log files.
While the phone was still active, I managed to create a full "manual" backup of the device by plugging it in and backing up/copying the entire internal memory. After screwing with the phone and every option for several hours I managed to access the files of the internal memory by switching to recovery mode via the boot menu and then plugging in the phone via usb to comp while deleting the drivers at the same time. I tried a full restoration of the internal backup i made, by copy and replace if the same method, but still nothing.
Ive attached an image of the Hboot menu with the details and options of that Hboot for those of you familiar with hboot.
The ideal situation, or what i'd like to do is restore the phone without flashing the rom and loosing the information, then id like to upgrade to lollipop or a new custom rom I found here actually, but the first step is getting back into the phone which i would be very grateful for in general.
also, not great with cmd and all that stuff, I do have sdk tools downloaded and installed but not great with that either. If there was a more simple way to replace existing files in the phone via the file manager (because im able to access the internal drive via the file manager, that would be the most ideal and easiest situation. But knowing the path and the boot files and which files are necessary for boot is what im looking for as well.
Also i know how to flash a sd and htc has a sdcard slot as well. Also i should mention that prior to the phone being screwed up I did want to delete some internal certificates because i believe someone installed a spy application on the phone, hence the reason for all of this checkup and removal anyway. In the process of trying to do that, i followed a tutorial on this forum which suggested I create a security lock pin, which I did. This could also be the cause of the problem not being recognized by the adb or fastboot script.
Who ever helps me do that gets a tip.
Please help.
---------- Post added at 05:02 PM ---------- Previous post was at 04:49 PM ----------
JamesM8 said:
A year ago I believe I used HBoot and or Firewater to root my M8. I recently removed some applications that seemed to make my phone act funny, and now the phone is stuck in a boot loop, or rather just a boot and stop at the second HTC "One" screen. Not exactly a loop.
I've download ADB tool and tried the fastboot method to install TWRP but have no success because the computer does not recognize the phone while running ADB or Fastboot, therefore I cant install TWRP and am stuck in the bootloader menu. I have tried various different cables and restarted the pc several times, and installed htc sync and other drivers necessary for that process. Also uninstalled and installed different drivers later as well. Now im not sure what i have installed but I have access to the phones internal drive via explorer.
Using Hboot.
Stats:
***UNLOCKED***
M8_UL PVT SHIP S-OFF
CID-HTC__32
RADIO- 1.15.2133156
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMc-boot 2048MB
Mar 22 2014, 00:53:32.0
Options:
HBOOT (when scanning says that all images are not found)
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMART SD
IMAGE CRC
SHOW BARCODE
Recovery leads to nothing and eventually returns to the HTC One menu stop.
Reset does nothing, acts like fast boot actually.
Ramdump under fastboot seems to works, and does produce log files.
While the phone was still active, I managed to create a full "manual" backup of the device by plugging it in and backing up/copying the entire internal memory. After screwing with the phone and every option for several hours I managed to access the files of the internal memory by switching to recovery mode via the boot menu and then plugging in the phone via usb to comp while deleting the drivers at the same time. I tried a full restoration of the internal backup i made, by copy and replace if the same method, but still nothing.
Ive attached an image of the Hboot menu with the details and options of that Hboot for those of you familiar with hboot.
The ideal situation, or what i'd like to do is restore the phone without flashing the rom and loosing the information, then id like to upgrade to lollipop or a new custom rom I found here actually, but the first step is getting back into the phone which i would be very grateful for in general.
also, not great with cmd and all that stuff, I do have sdk tools downloaded and installed but not great with that either. If there was a more simple way to replace existing files in the phone via the file manager (because im able to access the internal drive via the file manager, that would be the most ideal and easiest situation. But knowing the path and the boot files and which files are necessary for boot is what im looking for as well.
Also i know how to flash a sd and htc has a sdcard slot as well. Also i should mention that prior to the phone being screwed up I did want to delete some internal certificates because i believe someone installed a spy application on the phone, hence the reason for all of this checkup and removal anyway. In the process of trying to do that, i followed a tutorial on this forum which suggested I create a security lock pin, which I did. This could also be the cause of the problem not being recognized by the adb or fastboot script.
Who ever helps me do that gets a tip.
Please help.
Click to expand...
Click to collapse
**** I just realized it would be more appropriate to create a new thread for my problem rather than intruding on this mans problem, please see the One (M8) Q&A, Help & Troubleshooting. And respond there*****

Sprint M8 Stock Roms

Hi, I made this post in the Sprint section a few days ago, but figured I'd post here as well to see if maybe this section has more traffic. If that's not allowed, I apologize in advance.
https://forum.xda-developers.com/sprint-htc-one-m8/help/stock-roms-t3669676
Basically, I'm looking for a stock rom for Sprint that would work with 1.54.651.8 firmware. All the links I can find on the forums seem to be dead.
Alternatively, a nandroid backup or way to extract the rom from the 1.54.651.8 RUU I do have (but won't successfully flash for whatever reason)
Any help would be appreciated. Thanks!

A custom ROM would need to support the Sprint M8, and be based on 4.4.2. Most any newer (newer than KitKat) ROMs will suffer major incompatibility with your ancient firmware, including extreme long boot time or no boot, and broken WiFi.
Suggest stocking with updating the firmware. Is the device s-on or s-off?
Problems with the RUU while "sending" are usually on the PC side. Try to re-install HTC drivers, try another USB port (USB 2.0 works best), and try another cable. Or even try another PC if possible.

Yeah I was able to find one custom 4.4.4 ROM (It was labelled 4.4.2, but it works so I guess it's close enough). There are just a few issues with it and I've always been more of a stock person anyway so I'd rather use a stock rom if I have the option.
As far as updating firmware, I am S-ON - I only originally rooted for a wifi hotspot app, so I didn't have a need to go S-OFF.
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site? I was willing to try it back when I had no rom at all, but now that I have a custom rom that mostly works, I'd rather not totally crap the bed.

Fuhcue said:
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site?
Click to expand...
Click to collapse
You can "skip" RUUs, and go the latest. However, you may (probably) need to update to the Marshmallow firmware anyway, before you can RUU. There is a strange limitation on most US version M8, where the RUU will fail with Error 155, if you try to go to Marshmallow from any former version (be it Kitkat or Lollipop) without first updating the firmware.
So the steps would be:
1) Relock bootloader
2) Flash to Marshmallow signed firmware (Sprint), in fastbootRUU mode
3) RUU to Marshmallow
4) Unlock bootloader again
5) Flash TWRP, root, and do whatever mods you want
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.

redpoint73 said:
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
Click to expand...
Click to collapse
I don't so much mind the wipe, but I am a bit nervous about updating the firmware since that sounds like it could leave me in limbo if the RUU still didn't want to work for whatever reason. I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).

Fuhcue said:
I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
Click to expand...
Click to collapse
The firmware is posted in the same thread as the RUUs. And instructions on how to flash, as well.
https://forum.xda-developers.com/showthread.php?t=2729173
Fuhcue said:
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Click to expand...
Click to collapse
You can also opt for the Lollipop RUU (does not require flashing the firmware first). While not the latest, it's obviously more updated than what you presently have. And most of the current MM ROMs should work with LP firmware. There isn't much difference in the firmware it seems, for LP versus MM. Much different from KK to LP, which causes the problems I mentioned earlier (if you try to run KK firmware with LP or MM ROMs).
For maximum compatibility, matching the firmware is usually best. But I was running LP firmware with MM ROMs for a while (was simply to lazy to flash the MM firmware or RUU).

Ok so it sounds like the easiest option for me at this point is to grab a Lollipop RUU and try to flash it from a new computer with a fresh install of all the drivers. That way, at least if it fails to recognize my phone like the newest one did, I'll still be where I currently am with the stock (though outdated) firmware and custom rom.
Otherwise, I'll keep my fingers crossed that someone stumbles across this thread that has a meticulous archive of all old stock Sprint roms
Thanks so much for all your help and answering my questions so quickly. Much appreciated.

Hi
This is Sudheer from INDIA
i got Sprint HTC one M8 Harman Kardon from my friend.
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting. yesterday i am trying to install os from following reference.
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.

Krishna Sudheer said:
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
Click to expand...
Click to collapse
"Jail break" is a term specific to only iPhones. There is not such thing as "jail break" on an Android device. I assume you mean s-off, or some other mod? I can only guess, if you don't use the specific and proper terminology.
Krishna Sudheer said:
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting.
Click to expand...
Click to collapse
All in one Toolkit is obsolete, you shouldn't be using it. It contains a very old version of TWRP which will cause problems for many folks.
System partition is the OS/ROM. Should be obvious, that wiping the system partition results in no OS. Can't boot to an OS that isn't there any more. If you didn't know what the result would be from wiping a partition, you should be touching it in the first place!!!! Those options are listed under "Advanced" for a reason. If you aren't an advanced user, don't mess with them, unless you are following directions form an experienced user, or know what the result is going to be.
Krishna Sudheer said:
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Click to expand...
Click to collapse
Not enough info to know why the RUU failed. You linked a post with multiple RUUs, so we don't know which one you tried. We also don't know your current phone configuration.
Which version number RUU did you try? For HK version, you typically will need to flash the one that contains the digits "654". The RUU with digits "651" is for non-HK Sprint version. Assuming CID/MID has not been modified (which we don't know, if you don't provide more info).
Post specific info about your phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If the phone is s-on, you need to lock it in order to RUU. I don't know if you are s-on of s--off.
You can't run a lower number (downgrade) RUU unless you have s-off. Again, I don't know what version number RUU you tried, your current version number on the phone, or whether you are s-on or s-off.

Hi Sir,
Thank you for replying. Sim Unlocked from mobile store. actually I also don't know witch method they are using to unlock. After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
I tried to change CID and s-off but it's not working.
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot?
My mobile model is HTC one M8 HK (831C) Sprint Internal storage is 32GB.
I download and used to flash following files.
1. signed_6.20.654.3_firmware.zip
2.RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe
3.0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(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:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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.031s
Kindly check and do the needful. Let me know how to install OS and where witch rom I use to install.

My responses below in red font:
Krishna Sudheer said:
After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
LTE is difficult (maybe impossible) to get working in cases where the device is not intended for your region/carrier (which I assume is the case, that you are not located in US, on the Sprint carrier). GSM should work (as you indicated) as well as 3G (HSPA) provided that your carrier uses a band(s) supported by the Sprint version M8
I tried to change CID and s-off but it's not working. I don't know what that means "it's not working". Most folks who say they have trouble with getting s-off, are trying the hopeless waste of time, which is trying to usethe long obsolete "free" s-off method of firewater. It's never going to work.
Also, you should also be careful here, when changing CID. Only use a Sprint CID, or SuperCID with a Sprint firmware/RUU. Trying to use any other firmware or RUU will result in a radio brick (possibly permanent).
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot? That version is too old (over 4 years) and you should have used current TWRP. This was probably caused by using the toolkit (which I mentioned is not advised anymore). Old versions of TWRP was not compatible with Sprint M8 (it had it's own "CDMA" version TWRP) and it probably caused the wrong partition to be overwritten.
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3 Try flashing firmware again, the number should show up in getvar all (below) under "version-main". Flashing firmware twice is usually a good idea.
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Error 155 is common, if flashing a US Marshmallow RUU, without being on the matching firmware. Flashing firmware again, as indicated above, may solve it.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: firmware number should appear here
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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.031s
Click to expand...
Click to collapse

Which version is the M8 I bought ? Tampered/compromised phone ?

Hello, sorry for the probably completely noob question that might have already been answered but I searched for this answer and dinn't find anything really relevant.
I'd like to check the version of the unit I received so I can install a proper ROM without killing the phone as I'm aware certain versions of the M8 (GSM/CDMA) might get into troubles if wrong roms are used.
So I bought this phone from a chinese reseller. Phone is obviously refurbished (phone was rooted "out of the box" with all bloatware removed). There is a sticker on the back of the phone with 3 barcode (P/N, S/N amnd IMEI). What's strange is IMEI is similar on sticker and "about phone" but S/N doesn't match, as if it had been tampered/manually modified... So, definitely, the motherboard or the case had been replaced and I couldn't rely on the model number wirtten on the back of the phone.
First thing I tried was using the IMEI to check version but it matches an HTC Desire 820, I wasn't aware you could modify IMEI or dupe. Anyway, I moved on to the next step, which was going into bootloader. Bootloader says CID-1111111, which is, from my understanding, a way of making the phone open to any roms, from any country. Ok, one more info that doesn't help.
So I used the fastboot getvar all and it gave me this :
Code:
(bootloader) 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: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC******
(bootloader) imei: 35************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I googled "0P6B6****" (it comes with the ****, I didn't replaced any digits, only hidden IMEI and S/N) and it didn't gave me any solid information. Since phone was rooted and seemingly heavily tampered, I went back to stock and possibly get OTA to get Marshmallow (current os is 4.18.708.12) but there's no more updates so I'm "stuck" with 5.0.1. I thought the phone was initially a taiwanese version since it had the Snapdragon [email protected] but there's a lot of chinese bloatware.
So I can't update to M and therefore convert the phone to GPe or even use any custom roms (unless I missed something and I'm completely wrong). Can you help me trying to figure out what I received and if there's anything I can do with it or if I'm stuck with the stock rom.
Thank you.

Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.

Thank you for your quick answer. Yes, I use it in Europe so it works fine with my carrier (even if LTE B20 is missing but it's ok). I'll do as you suggested. I'm glad I got a GSM-only phone, I thought I received a hybrid unit. Thank you again.

ckpv5 said:
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Click to expand...
Click to collapse
Ok, so I modifed MID 0P6B10000 and then tried to install latest Marshmallow RUU 6.12.401.4 via fastboot but phone is not booting up (stuck on HTC One logo). So i restored with my previous clean Nandroid backup. I'm back to 4.18.708.12 (phone is 100% working)
First question : bootloader tells me os is 6.12.401.4 while I'm actually running 4.18.708.12. Is it a problem or not ?
Second question : in order to have a working (eu) MM rom on my phone, I guess I'm supposed to flash the firmware to the latest right (which is something I haven't done in my previous attempt to flash MM) ? But which one am I supposed to grab ? 6.12.401.4 or 6.16.708.1 ? I'll use your guide to do it (https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5). Can you confirm updating the firmware is mandatory before flashing stock MM rom when upgrading from Lollipop stock ? I can't install MM RUU, coming from LP, without flashing the fw first ?
Once firmware is updated, I can safely flash MM 6.12.401.4 ? I might as well flash to MM with TWRP and use one of your stock MM backup. Can it be done coming from my current LP rom version ?
Last question : let's say I flash the 6.12.401.4 firmware and keep the 4.18.708.12 LP rom, phone won't boot right ? Keep in mind I have a phone with a ModelID 0P6B10000 and a stock LP rom 4.18.708.12
I'm sorry for the noob questions and to bother you with these but I tried a lot of different things (and I don't want to go to fast and kill the phone) without any success, and since this is my first HTC phone, there are some novelties in the flashing process. And I recovered the phone several times so I might run out of luck next time.
Thank you again for your help.

Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot

ckpv5 said:
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
Click to expand...
Click to collapse
OS line is green and single so I'm good.
So if I'm understanding correctly, if OS in bootloader says 6.12.401.4, then it means firmware actually installed on phone is 6.12.401.4.
Now, when installing the RUU zip provided there (https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6), the file is corrupt, on both links. File size is correct in Windows but when I open the archive (for example to add 11111111 in android-info.txt), it says archive is corrupt and file size of the different files in this archive are way too small.
I'm gonna try Nandroid backup.

Don't do thing that is not in the instructions. No where I wrote you need to add anything to the RUU zip. It's simple process, why need to make it harder ?
RUU zip is a htc signed zip. No windows archiver such as winzip, winrar, 7-zip and etc can properly open it and you're not supposed to open it.
Read the instruction again. No need to add 11111111 to the zip as there is no such thing as SuperRUU or SuperFirmware. 11111111 is for the device which means your M8 is SuperCID and you can install the zip regardless what your device CID is.

You are absolutely right about me doing unnecessary steps. That probably explain why I didn't manage to get it working. Anyway, I used twrp to restore one the MM Nandroid backup you provided in one of your post (+ recovery) and it went smoothly. I'm now on MM and phone is working fine. I'll see if it's worth flashing a custom rom if I can find one that fits my needs.
Thank you for your answers, it did help me quite a lot. Your guides (+ all the different files you provide) are excellent, as long as you follow the instructions and don't do unnecessary steps
Have a nice day/evening.

hi,
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
I tried following the instructions at https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
It seemed to be installing but after about 20mins it failed with the error - "(bootloader) shift signature_size for header checking...FAILED (remote: 32 header error)"
I then found another RUU which I think is the correct one but received the same error (0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.1_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465001_signed.zip)
btw - i tried changing the mid to 0P6B10000 but this also failed (i downloaded an app which runs in twrp to do it, is this the correct way?)
----------------- my current phone info ------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.30.401.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4BRY-----
(bootloader) imei: -----
(bootloader) imei2: ----
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(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: 49d38c68
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

alanes said:
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
Click to expand...
Click to collapse
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
I don't think you can update your device directly to the latest Marshmallow as your current firmware is Lollipop. In order to do that you need to install Marshmallow firmware first then RUU but I don't see Marshmallow firmware is available anywhere except the RUU.
So my suggestion is install the Lollipop RUU then do OTA to Marshmallow. You may need to do 2 or 3 OTAs to reach that level.
1. No need to change anything to your MID yet. Let it be as it is now 0P6B6****
Only when the RUU fails to install due to MID error, then you need to change it to 0P6B64000 NOT 0P6B10000
https://forum.xda-developers.com/showthread.php?t=2708581
2. Download 0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip
from here - https://easy-firmware.com/home/browse/category/id/7825/
3. Install the RUU as instructed here - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use the above downloaded RUU
or you can rename it to 0P6BIMG.zip and place it on your microsd and boot to bootloader to install.
Make sure you don't rename it to 0P6BIMG.zip.zip

ckpv5 said:
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
Click to expand...
Click to collapse
Hi,
Thanks for your reply - sorry if I posted in the wrong place etc. - I struggle as I can't get the xda search to work so find it difficult to find anything.
As you know I keep giving up on this but then end up trying again and spending all night messing about with it.....
I tried installing *0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip* but get the same error.
I am not sure if this includes the firmware or if that is separate to the RUU (as I have tried to install new firmwares so the installed one may well not be the correct one).
update: I have now installed the firmware to match (i.e. a 40mb zip file version 4.30.40 1.15) but still getting the error when i try to install the RUU
btw - I tried copying to the sd card but that gives error "device halted due to large image update fail"
---------
This I think is the info from my phone when I first received it
info on my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.18.30306251.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4...............
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6b903f73
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks again
Alan.

I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.
I already gave you link on how to do it as in item #1

ckpv5 said:
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.1
Click to expand...
Click to collapse
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to install twrp.
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
"htc-fastboot devices" shows nothing
btw - I have tried it on another computer and is the same

alanes said:
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to unlock the device (i.e. fastboot oem get_identifier_token)
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
btw - I have tried it on another computer and is the same
Click to expand...
Click to collapse
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.

ckpv5 said:
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
Click to expand...
Click to collapse
Hi,
I had assumed it had re-locked the bootloader but later realised it was still S-off
and you are right it is "FASTBOOT USB", not "BOOTLOADER USB" - sorry for the confusion
My phone shows OS-4.30.401.15
I can use a friends Windows laptop and will see if I can give it a try
On another subject, the GPS on this phone seems to be dead (it has never seen a single satellite), is this a known problem with these phones do you happen to know?
thanks
Alan

alanes said:
My phone shows OS-4.30.401.15
Click to expand...
Click to collapse
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Once you successfully back on stock 4.30.401.15, you should check for OTA and install. I believe you will have 2 or 3 OTA to get to Marshmallow firmware.
Have you check for OTA & update ?
About GPS, maybe you have faulty gps cable in it. I don't have M8 dual SIM but no reason why it is not working unless it is hardware issue. I can't help when it comes to hardware.
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999

ckpv5 said:
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Have you check for OTA & update ?
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
Click to expand...
Click to collapse
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you

alanes said:
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
Click to expand...
Click to collapse
I don't make mistake as I understand what you are trying to do. If you unlock bootloader and install twrp now, you're back to earlier problem.
To install LOS 14, you must have Marshmallow firmware installed. Now you're on stock 4.30.401.15. You don't need to do unlocking & install twrp yet. You need to do OTA until you get final OTA either 6.16.401.1 or 6.16.401.101 then only you proceed to unlock bootloader and install twrp and install LOS 14.
Forget about link to GPS matter for now as that require device teardown.
Most important now OTA. Without OTA it serves no purpose on what you're doing now and intend to do later.

ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........

alanes said:
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
Click to expand...
Click to collapse
In case you're not sure what OTA I'm talking about, go to settings - about - software update - check here for OTA. When there is one, download and install. Again repeat the process until it says there is no update available.
Every time you install OTA, you OS no. on bootloader will change to current firmware. You need this until the OS no. is written as 6.16.401.1 or 6.16.401.101.
Then only you unlock bootloader and install latest twrp 3.x and install LOS 14