Develop Bugs

[Q] Bootloader will not reload after flashing.

Followed all the steps to unlock the phone. All the command are correct and the unlock code bin was sent to phone and nothing happened. Still has *****Tampered**** and has ****Unlocked**** in the bootloader. Can anyone assist so i can get my phone working again properly??? Urgent!

It's not easy to help you when you keep on jumping/opening a new thread for every question that you have.
http://forum.xda-developers.com/htc-one-m8/help/htc-m8-phone-stuck-power-cycle-install-t3100384
http://forum.xda-developers.com/htc-one-m8/help/phone-unlocked-tampered-t3100432
How do you expect people to help you ? Stick only on one thread .. help will come.
You have "UNLOCKED" & "TAMPERED" on bootloader but yet you are trying to re-unlock it ? This is totally wrong.
Your problem was originally flashed a ROM not meant for your hboot version. Just get the right ROM to install in recovery or restore a backup or even install a RUU to fix it (if there is one for your device)
First step - to get to know your device version better so people can help you is :
when on bootloader and connect to PC, run this command
fastboot getvar all
then post here the result (delete out the imei no. & serial no.)
then people can guide you to the right direction.

ckpv5 said:
It's not easy to help you when you keep on jumping/opening a new thread for every question that you have.
http://forum.xda-developers.com/htc-one-m8/help/htc-m8-phone-stuck-power-cycle-install-t3100384
http://forum.xda-developers.com/htc-one-m8/help/phone-unlocked-tampered-t3100432
How do you expect people to help you ? Stick only on one thread .. help will come.
You have "UNLOCKED" & "TAMPERED" on bootloader but yet you are trying to re-unlock it ? This is totally wrong.
Your problem was originally flashed a ROM not meant for your hboot version. Just get the right ROM to install in recovery or restore a backup or even install a RUU to fix it (if there is one for your device)
First step - to get to know your device version better so people can help you is :
when on bootloader and connect to PC, run this command
fastboot getvar all
then post here the result (delete out the imei no. & serial no.)
then people can guide you to the right direction.
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 3.18.0.0000
INFOversion-baseband: 1.17.21331147A1.28G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-OFF
INFOserialno:
INFOimei:
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul_ca
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B12000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 0a026e9d
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.020s
Update: Phone now stuck on HTC One screen and can no longer get to bootloader. If you did, factory rest does not work.
Update: Phone is up and running but still has tampered.

suzyq42 said:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 3.18.0.0000
INFOversion-baseband: 1.17.21331147A1.28G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-OFF
INFOserialno:
INFOimei:
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul_ca
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B12000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 0a026e9d
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.020s
Update: Phone now stuck on HTC One screen and can no longer get to bootloader. If you did, factory rest does not work.
Update: Phone is up and running but still has tampered.
Click to expand...
Click to collapse
I don't see a ARHD ROM with LP for HTC One M8 ATT carrier. All the ones out there either have Sprint or International. Also, Where is the latest firmware? Looked on the website and the last one I see was dated last year. Do you know when the new ROM for this phone will be out???? The other ones, 34 and 41, had all kinds of issues. Current on 9.1.

suzyq42 said:
I don't see a ARHD ROM with LP for HTC One M8 ATT carrier. All the ones out there either have Sprint or International. Also,
Click to expand...
Click to collapse
Any ROM meant for the "GSM" M8 (don't flash any ROM specifically intended for Sprint/Verizon) is okay to flash on your phone. So the ARHD in the "international" Development forum is what you want (but you need to update your firmware, as you seem to be aware).
suzyq42 said:
Where is the latest firmware? .
Click to expand...
Click to collapse
Are you actually using AT&T as your carrier? If so, I'd suggest (at least for a start) using the Dev Edition firmware (4.16.1540) here (its packed with the ROM, but you just need the firmware): http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365

redpoint73 said:
Any ROM meant for the "GSM" M8 (don't flash any ROM specifically intended for Sprint/Verizon) is okay to flash on your phone. So the ARHD in the "international" Development forum is what you want (but you need to update your firmware, as you seem to be aware).
Are you actually using AT&T as your carrier? If so, I'd suggest (at least for a start) using the Dev Edition firmware (4.16.1540) here (its packed with the ROM, but you just need the firmware): http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Click to expand...
Click to collapse
Will this work with KK 9.1??? After I put this firmware in, will the Revolution 34 work in this ATT phone??

suzyq42 said:
Will this work with KK 9.1??? After I put this firmware in, will the Revolution 34 work in this ATT phone??
Click to expand...
Click to collapse
The 4.16.1540 firmware is for Lollipop, as the goal in my opinion would be to flash a current ROM. It may work with older Kitkat ROMs, but no guarantee. If your intent is to stay on Kitkat, then you don't need to flash firmware. You just need to have a software version that supports your firmware.
I think you should define in your own mind what you want to end up with, and stick to it.
If you put a current ARHD version (41, don't know why you are targeting 34 specifically) and the firmware I linked, then yes it should work on your phone.

redpoint73 said:
The 4.16.1540 firmware is for Lollipop, as the goal in my opinion would be to flash a current ROM. It may work with older Kitkat ROMs, but no guarantee. If your intent is to stay on Kitkat, then you don't need to flash firmware. You just need to have a software version that supports your firmware.
I think you should define in your own mind what you want to end up with, and stick to it.
If you put a current ARHD version (41, don't know why you are targeting 34 specifically) and the firmware I linked, then yes it should work on your phone.
Click to expand...
Click to collapse
I followed the instruction and it looks like it loaded it but in the bootloader screen, there is no recovery button.

redpoint73 said:
The 4.16.1540 firmware is for Lollipop, as the goal in my opinion would be to flash a current ROM. It may work with older Kitkat ROMs, but no guarantee. If your intent is to stay on Kitkat, then you don't need to flash firmware. You just need to have a software version that supports your firmware.
I think you should define in your own mind what you want to end up with, and stick to it.
If you put a current ARHD version (41, don't know why you are targeting 34 specifically) and the firmware I linked, then yes it should work on your phone.
Click to expand...
Click to collapse
After I re did the process, the firmware took. now flashing ROM.
Thanks....I hope this works!

suzyq42 said:
After I re did the process, the firmware took. now flashing ROM.
Thanks....I hope this works!
Click to expand...
Click to collapse
This failed! phone locked up on opening screen. Help

suzyq42 said:
This failed! phone locked up on opening screen. Help
Click to expand...
Click to collapse
OK, I am now on ARHD 41 but no wifi. I loaded the new firmware but still not wifi. Help!!

suzyq42 said:
This failed! phone locked up on opening screen. Help
Click to expand...
Click to collapse
OK, I am up on Revolution 41 but have issues. 1. no wifi after flashing the new firmware. 2. Need framework for xposed installer. 3. Sense 7 not functiional, resorted back to Sense 6. 4. bootloader does not show the new firmware. Is there any thing you can do to help?

suzyq42 said:
4. bootloader does not show the new firmware.
Click to expand...
Click to collapse
The only evidence of the firmware would be the hboot number and radio number. The main or OS version numbers is going to be the number for whatever custom ROM you flashed (does not tell you firmware number).
Post your adb getvar all data again (and again delete serial number and IMEI).

redpoint73 said:
The only evidence of the firmware would be the hboot number and radio number. The main or OS version numbers is going to be the number for whatever custom ROM you flashed (does not tell you firmware number).
Post your adb getvar all data again (and again delete serial number and IMEI).
Click to expand...
Click to collapse
Thanks guys but at this point, I have to stay with KK until LP and the ROM bugs are fixed. I can't have my main phone tied up like this. when the OS and ROM is solidly stable like KK, I will then migrate over. I have been fighting this upgrade for weeks and had enough. It looks like a lot of other people are in the same issue. Will be monitoring this to see when all the bugs are fixed.
Regards.

suzyq42 said:
Thanks guys but at this point, I have to stay with KK until LP and the ROM bugs are fixed. I can't have my main phone tied up like this. when the OS and ROM is solidly stable like KK, I will then migrate over. I have been fighting this upgrade for weeks and had enough. It looks like a lot of other people are in the same issue. Will be monitoring this to see when all the bugs are fixed.
Click to expand...
Click to collapse
What bugs specifically? Some folks have had some battery issues. But I've found LP to be plenty stable.
The WiFi issue is most likely pilot error, not a LP bug. But if you don't provide the info I asked for; I can't help any further.

redpoint73 said:
What bugs specifically? Some folks have had some battery issues. But I've found LP to be plenty stable.
The WiFi issue is most likely pilot error, not a LP bug. But if you don't provide the info I asked for; I can't help any further.
Click to expand...
Click to collapse
Right now I need to fix my phone. In bootloader, it shows tampered. This came about because I tried to load 41 and it got corrupted. I have to go to my back-ups to get it back but in a few days, it's gone again. I have wiped my system and data and reloaded it once and that didn't work. Can someone help?? as of now, I am on 9.1.

redpoint73 said:
The only evidence of the firmware would be the hboot number and radio number. The main or OS version numbers is going to be the number for whatever custom ROM you flashed (does not tell you firmware number).
Post your adb getvar all data again (and again delete serial number and IMEI).
Click to expand...
Click to collapse
This is incorrect. Version-main in getvar, and OS in bootloader show current firmware version. The ROM base is found in settings > about > software information > more > build number
But I see the old getvar had a blank version-main, so if the new firmware was flashed with a newer TWRP installed, version-main shouldn't be blank anymore. It was blank caused by bug in a couple of the older TWRP versions .

xunholyx said:
This is incorrect. Version-main in getvar, and OS in bootloader show current firmware version. The ROM base is found in settings > about > software information > more > build number
But I see the old getvar had a blank version-main, so if the new firmware was flashed with a newer TWRP installed, version-main shouldn't be blank anymore. It was blank caused by bug in a couple of the older TWRP versions .
Click to expand...
Click to collapse
Build # is 2.12.401.3 CL352296 release-keys

suzyq42 said:
Build # is 2.12.401.3 CL352296 release-keys
Click to expand...
Click to collapse
TWRP version 2.7.1.0 is what I have.

suzyq42 said:
TWRP version 2.7.1.0 is what I have.
Click to expand...
Click to collapse
Bootloader now shows **** Software status: Modified *** **** Unlocked**** . The OS is blank.

[Q] Wondering...

I know i need to pay for sunshine to get S-Off,i'm considering doing it sometime soon,but just asking,would firewater work if i flashed rom to earlier version of android,like 4.4.0 or so? Also would it need to be official or could costume rom work too? Sorry for another annoying S-Off question. :angel:

No does not work.

SynoX4 said:
Sorry for another annoying S-Off question. :angel:
Click to expand...
Click to collapse
It is annoying, since the exact same question was already asked (and answered) twice yesterday (and also easy to search and look for besides that) if you just scroll down on the first page of threads. It looks like you are new to XDA. But it would be your benefit to know that most every question you can think of about this device has already been posted, and the knowledge easily obtainable by just looking/searching. Only after doing your due diligence to search (and not finding anything) should you start a new thread.
Also, flashing different ROMs won't enable old s-off exploits that have since been patched by HTC. It doesn't work that way, HTC is not that stupid. The key is in hboot (not the ROM which can be easily changed) which cannot be "downgraded" unless you have s-off already.
In any case, firewater was an online service, so it doesn't work no matter what version hboot you have, since the dev stopped supporting firewater.

redpoint73 said:
It is annoying, since the exact same question was already asked (and answered) twice yesterday (and also easy to search and look for besides that) if you just scroll down on the first page of threads. It looks like you are new to XDA. But it would be your benefit to know that most every question you can think of about this device has already been posted, and the knowledge easily obtainable by just looking/searching. Only after doing your due diligence to search (and not finding anything) should you start a new thread.
Also, flashing different ROMs won't enable old s-off exploits that have since been patched by HTC. It doesn't work that way, HTC is not that stupid. The key is in hboot (not the ROM which can be easily changed) which cannot be "downgraded" unless you have s-off already.
In any case, firewater was an online service, so it doesn't work no matter what version hboot you have, since the dev stopped supporting firewater.
Click to expand...
Click to collapse
Alright,thanks,sorry for late reply. I've been going around xda forum and i saw that for some roms it says it requiers either htc dev unlocked or s-off. I can unlock phone with htc dev,does that mean i dont need s-off to flash rom,kernel and firmware?

SynoX4 said:
Alright,thanks,sorry for late reply. I've been going around xda forum and i saw that for some roms it says it requiers either htc dev unlocked or s-off. I can unlock phone with htc dev,does that mean i dont need s-off to flash rom,kernel and firmware?
Click to expand...
Click to collapse
You'll need S-Off to flash firmware. But there are other ways to update without flashing a firmware.zip, usually by going back to stock ROM and recovery, and taking the OTAs provided by your carrier or by running an RUU.

xunholyx said:
You'll need S-Off to flash firmware. But there are other ways to update without flashing a firmware.zip, usually by going back to stock ROM and recovery, and taking the OTAs provided by your carrier or by running an RUU.
Click to expand...
Click to collapse
I see. Well for RUU,can i get one with higher version than my phone version-main? Also i just got model id error 130 on ruu installation with only last number differing.

SynoX4 said:
I see. Well for RUU,can i get one with higher version than my phone version-main? Also i just got model id error 130 on ruu installation with only last number differing.
Click to expand...
Click to collapse
RUU stands for ROM Update Utility. So yes, since it's purpose is to update, it should be higher than your current firmware.
Error 130 is because you aren't running the right RUU.
Get into fastboot and do fastboot getvar all, then post the readout here minus your serial# and IMEI. I'll link you to the proper RUU.

xunholyx said:
RUU stands for ROM Update Utility. So yes, since it's purpose is to update, it should be higher than your current firmware.
Error 130 is because you aren't running the right RUU.
Get into fastboot and do fastboot getvar all, then post the readout here minus your serial# and IMEI. I'll link you to the proper RUU.
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.22.30306251.27G
version-cpld: None
version-microp: None
version-main: 3.33.401.6
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m8_dugl
platform: hTCBmsm8974
modelid: 0P6B64000
cidnum: HTC__032
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 4c3fbd70
hbootpreupdate: 11
gencheckpt: 0
It's dual sim. I know it says up there but just because you might skip it.

SynoX4 said:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.22.30306251.27G
version-cpld: None
version-microp: None
version-main: 3.33.401.6
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m8_dugl
platform: hTCBmsm8974
modelid: 0P6B64000
cidnum: HTC__032
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 4c3fbd70
hbootpreupdate: 11
gencheckpt: 0
It's dual sim. I know it says up there but just because you might skip it.
Click to expand...
Click to collapse
Here's the RUU you need. It'll bump you to Lollipop.

xunholyx said:
Here's the RUU you need. It'll bump you to Lollipop.
Click to expand...
Click to collapse
Awesome,thanks. I'll update when it downloads,shouldn't be too long.

xunholyx said:
Here's the RUU you need. It'll bump you to Lollipop.
Click to expand...
Click to collapse
Error 132 signature something... I did lock bootloader before doing it.
Will do nandroid recovery to android 4.4.3,lock again and try.

SynoX4 said:
Awesome,thanks. I'll update when it downloads,shouldn't be too long.
Click to expand...
Click to collapse
Wait. Dual sim? And I missed it anyways. lol. Hung over and just smoked a joint.
You'll have to change your MID as well.
You can find out how here.
I'm guessing this will work only, because I am unfamiliar with the dual sim. But since you are already running WWE firmware on your device, I think it will.

xunholyx said:
Wait. Dual sim? And I missed it anyways. lol. Hung over and just smoked a joint.
You'll have to change your MID as well.
You can find out how here.
I'm guessing this will work only, because I am unfamiliar with the dual sim. But since you are already running WWE firmware on your device, I think it will.
Click to expand...
Click to collapse
Thing is,that requires s-off which i don't have...

SynoX4 said:
Thing is,that requires s-off which i don't have...
Click to expand...
Click to collapse
Then you'll probably have to go back to stock to update via OTAs.
Go to this thread, and do a search for what it says in your version-main for a stock ROM backup (if you don't have one that you made yourself) and also for the stock recovery.

xunholyx said:
Then you'll probably have to go back to stock to update via OTAs.
Go to this thread, and do a search for what it says in your version-main for a stock ROM backup (if you don't have one that you made yourself) and also for the stock recovery.
Click to expand...
Click to collapse
I have stock ROM backup for version 4.4.3, but when i tried to update it just sent me into twrp,and i tried to install OTA from there but it just sent me some error. Do you suggest i move to 4.4.3,get stock recovery and then do OTAs? Also closest numbers to my main version in that thread are 3.32 and 3.34 for both ROM and recovery,if this doesn't work which one should i get?

SynoX4 said:
I have stock ROM backup for version 4.4.3, but when i tried to update it just sent me into twrp,and i tried to install OTA from there but it just sent me some error. Do you suggest i move to 4.4.3,get stock recovery and then do OTAs? Also closest numbers to my main version in that thread are 3.32 and 3.34 for both ROM and recovery,if this doesn't work which one should i get?
Click to expand...
Click to collapse
I am really unfamiliar with the dual sim, so your best bet would to be to ask in that thread.

xunholyx said:
I am really unfamiliar with the dual sim, so your best bet would to be to ask in that thread.
Click to expand...
Click to collapse
Alright,thanks for all your help.

Need stock details of my m8.

Hi there, recently i bought used m8 and its android version is 4.4.3, it is made in ireland as htc said. It is s-off and has supercid 11111, It means previous owner customized this device. I need to know its orignal Cid and Mid so i will update it to marshmallow( since i am not receving ota updates), so please help me out what should i do...I also dont know it has stock rom/ recovery. Bootloader is locked. I guess it has stock recovery. I want any stock upgrade because this rom has many bugs like delaying messeges e.t.c. Thanks in advance

worgamerx said:
Hi there, recently i bought used m8 and its android version is 4.4.3, it is made in ireland as htc said. It is s-off and has supercid 11111, It means previous owner customized this device. I need to know its orignal Cid and Mid so i will update it to marshmallow( since i am not receving ota updates), so please help me out what should i do...I also dont know it has stock rom/ recovery. Bootloader is locked. I guess it has stock recovery. I want any stock upgrade because this rom has many bugs like delaying messeges e.t.c. Thanks in advance
Click to expand...
Click to collapse
Power off your phone, then boot it up by holding both the power button + vol down. This will take you to the bootloader. Post here what it says there. To navigate in the bootloader, use the vol keys to change selections, and the power button to select. You'll need to know that to select reboot.

xunholyx said:
Power off your phone, then boot it up by holding both the power button + vol down. This will take you to the bootloader. Post here what it says there. To navigate in the bootloader, use the vol keys to change selections, and the power button to select. You'll need to know that to select reboot.
Click to expand...
Click to collapse
Already mentioned:
CID:111111
S-Off
Bootloader is locked and i guess it have stock recovery.
Software number is: 2.11.708.2
I think rom is stock because it matchs with stock software number. But i want to upgrade so suggest me what should i do.

worgamerx said:
Already mentioned:
CID:111111
S-Off
Bootloader is locked and i guess it have stock recovery.
Software number is: 2.11.708.2
I think rom is stock because it matchs with stock software number. But i want to upgrade so suggest me what should i do.
Click to expand...
Click to collapse
Already mentioned where? Certainly not here. That CID means absolutely nothing.
And the ROM is stock because it matches with what? You have matched the OS version in bootloader, or the version-main number in you getvar with the software version in settings > about you mean?
If that is your software number, then you probably are stock, since I don't know of any ROMs that use 708 as a base.
Do you have TWRP recovery still installed? You can tell if you boot to bootloader and then boot to recovery (you need to select hboot to get the recovery option in bootloader). If the TWRP logo comes up, then you do, and this will be an easy fix by going to this thread to find a stock ROM backup and stock recovery for you to flash back to stock so that you can get OTA updates on your device.

Twrp is not installed.....its still on stock recovery....i matched the software number from the settings in about section with other device running this OS.
The main prob is its supercid is changed so i dont know which rom is compatible with it.

worgamerx said:
Twrp is not installed.....its still on stock recovery....i matched the software number from the settings in about section with other device running this OS.
The main prob is its supercid is changed so i dont know which rom is compatible with it.
Click to expand...
Click to collapse
Well, almost any new ROM isn't compatible because your firmware is too old. You need to update that first. That's what I'm trying to help you with here.
Also, that phone isn't Irish. None of them are. UK yes, Ireland no. It's an Asian model. Specifically, from Hong Kong.
The only way I could offer help is if you were to unlock the bootloader again. Instead I will mention @ckpv5 here (he'll get a notification because of the mention) because I'm pretty sure he has a link to the RUU you need to update.
He's a really helpful guy, and will respond here when he sees the notification. He's not logged in now, so just be patient.
Good luck!

xunholyx said:
Well, almost any new ROM isn't compatible because your firmware is too old. You need to update that first. That's what I'm trying to help you with here.
Also, that phone isn't Irish. None of them are. UK yes, Ireland no. It's an Asian model. Specifically, from Hong Kong.
The only way I could offer help is if you were to unlock the bootloader again. Instead I will mention @ckpv5 here (he'll get a notification because of the mention) because I'm pretty sure he has a link to the RUU you need to update.
He's a really helpful guy, and will respond here when he sees the notification. He's not logged in now, so just be patient.
Good luck!
Click to expand...
Click to collapse
Thank you so much. You are really kind person. I am waiting

Post fastboot getvar all result (without serial & imei no) to see what is best for you

ckpv5 said:
Post fastboot getvar all result (without serial & imei no) to see what is best for you
Click to expand...
Click to collapse
thank you for replying
here is the result:
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.19.21331147A1.16G
version-cpld: None
version-microp: None
version-main: 2.11.708.2
version-misc: PVT SHIP S-OFF
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
battery-status: good
batter-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c802cb02
hbootpreupdate: 11
gencheckpt: 0

worgamerx said:
thank you for replying
here is the result:
version-bootloader: 3.18.0.0000
version-main: 2.11.708.2
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
security: off
Click to expand...
Click to collapse
Your device has Hong Kong firmware but the MID is EU.
You won't get OTA with this combination.
I suggest to install EU RUU as this is easier, no need to change MID to Hong Kong.
You can follow this, direct update to the latest Marshmallow
Link : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

ckpv5 said:
Your device has Hong Kong firmware but the MID is EU.
You won't get OTA with this combination.
I suggest to install EU RUU as this is easier, no need to change MID to Hong Kong.
You can follow this, direct update to the latest Marshmallow
Link : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
I am going to install RUU.....its my first time that i am doing such a thing..Thank you so much God Bless You

thank you so much "ckpv5", i just followed your instruction and i successfully installed marshmallow, thanks again you helped me out . i am also thanks full to "xunholyx".

How to unroot htc one m8??(thanks Redpoint3)

I got an update from the factory but it wan't work tell i unroot my phone , how can i do that??
guys the problem is more then unroot the device if you have the time read the comments and post any help
thanks

"Themes and apps" is a really weird section to post your question in. I'll ask the mods to move it to "Q&A, Help" where it belongs.
To unroot, you need to restore a stock TWRP backup. Either one you made before rooting, or get one from here (and restore with the instructions):http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Alternately, you can relock the bootloader and RUU (RUU will wipe the phone).

redpoint73 said:
"Themes and apps" is a really weird section to post your question in. I'll ask the mods to move it to "Q&A, Help" where it belongs.
To unroot, you need to restore a stock TWRP backup. Either one you made before rooting, or get one from here (and restore with the instructions):http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Alternately, you can relock the bootloader and RUU (RUU will wipe the phone).
Click to expand...
Click to collapse
Sorry man it was a miss click , how can I move it to other section?

jonasess said:
how can I move it to other section?
Click to expand...
Click to collapse
You don't have the ability to move threads, after they are created. The mods can, and have already moved it to the right section (Q&A). It usually takes someone else to report the thread (which I did), and I don't think you can report your own thread.
But back to the topic at hand, I hope the info I posted was useful to you. Let us know if you have further questions.

redpoint73 said:
You don't have the ability to move threads, after they are created. The mods can, and have already moved it to the right section (Q&A). It usually takes someone else to report the thread (which I did), and I don't think you can report your own thread.
But back to the topic at hand, I hope the info I posted was useful to you. Let us know if you have further questions.
Click to expand...
Click to collapse
Thanks men but there is one thing , the bootloader is already locked I didn't unlock it before , so I was wondering whether I have to unlock the bootloader and install CM13 room or not doing that and unroot the phone because may be there is a chance that the company send an update for 6.0
I only have two questions
Is there is an official update to 6.0 from HTC company?
Or should I go with CM13
Also is there are any risks in bootloader unlock?
I successfully unlocked the bootloader in lg g2 mini before and it was very easy without any big risks
And now with HTC one m8 I don't know if it is the same or not.

My responses below in red font:
jonasess said:
the bootloader is already locked I didn't unlock it before
How did you root? Was it kingroot, or similar root app?
so I was wondering whether I have to unlock the bootloader and install CM13 room or not doing that and unroot the phone because may be there is a chance that the company send an update for 6.0
Is there is an official update to 6.0 from HTC company?
Android 6 came to this phone a really long time ago, about a year ago (Dec 2015) for most M8 versions. If you didn't get the update, it may due to being rooted, which typically prevents OTA update.
Alternately, depending on what version M8 you have, you can just RUU to Marshmallow (Android 6) without unrooting (although it will wipe all data on the phone). Do you know your phone's CID, or at least provide the OS number on the bootloader screen? From that, I can possibly tell you if there is an RUU.
Or should I go with CM13
You're talking about 2 completely different things, unrooting to OTA, or installing a custom ROM. I can't make that decision for you, you need to do it yourself.
Also is there are any risks in bootloader unlock? Not really. The bootloader can still be relocked, and you can restore to stock. I don't recall seeing any brick reports from unlocking the bootloader. The critical "brick" partitions (hboot and radio) aren't accessed by unlocking the bootloader, and any partitions that are accessed (system, recovery, etc.), can be easily rewritten/repaired if anything goes wrong.
Click to expand...
Click to collapse

redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
It wasn't me because i got the phone from a friend , anyway the phone is rooted but the bootloader is locked because when i reboot to the bootloader mode i find it locked
about cid it's 11111111
OS-1.29.708.4
anyway how to unroot the phone , i'm going to try if it is possible to get the official 6.0 from the factory or not
if not i will unlock the bootloader and try to install ROM
so if it is possible i need the way how to unroot the phone and also how to unlock the bootloader
thanks

jonasess said:
anyway the phone is rooted but the bootloader is locked because when i reboot to the bootloader mode i find it locked
Click to expand...
Click to collapse
This doesn't tell me anything, you didn't already post before.
jonasess said:
about cid it's 11111111
OS-1.29.708.4
Click to expand...
Click to collapse
I don't recognize that OS version number. I Googled it, and I think you have the M7, not the M8.

redpoint73 said:
This doesn't tell me anything, you didn't already post before.
I don't recognize that OS version number. I Googled it, and I think you have the M7, not the M8.
Click to expand...
Click to collapse
i didn't get it , because there is a different between m8 and m7
m7 contain only one camera in the back
m8 contain 2 camera in the back
also the m7 doesn't support Card slot , m8 does
and a lot of other different
how could m8 phone contain an os of m7?

This all the information from bootloader mode
*** software status : official ***
*** locked ***
M8_UL_CA PVT SHIP S-OFF
CID - 11111111
HBOOT-3.19.0.0000
[email protected]
openDSP-V47.2.2-00564-118974_F0.1024
OS-1.29.708.4
2MMC-boot 2048MB
mar 20 2015,03:01:11.90025771
Also when i use an app to get the information it gives the CID CWS_001
and the OS version is LRX22C
Also the app shows that the bootloader version is 3.19.0.0000

jonasess said:
This all the information from bootloader mode
*** software status : official ***
*** locked ***
M8_UL_CA PVT SHIP S-OFF
CID - 11111111
HBOOT-3.19.0.0000
[email protected]
openDSP-V47.2.2-00564-118974_F0.1024
OS-1.29.708.4
2MMC-boot 2048MB
mar 20 2015,03:01:11.90025771
Also when i use an app to get the information it gives the CID CWS_001
and the OS version is LRX22C
Also the app shows that the bootloader version is 3.19.0.0000
Click to expand...
Click to collapse
post the result of ( fastboot getvar all ) after removing seialno and imei
this output info will be useful to identify the right path you should take
and the info you already posted is a little mixed up NOT CORRECT
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
post the result of fastboot getvar all after removing seialno and imei
this output info will be useful to identify the right path you should take
and the info you already posted is a little mixed up NOT CORRECT
Click to expand...
Click to collapse
What should I do , where can I get these information? From an app or..?

jonasess said:
What should I do , where can I get these information? From an app or..?
Click to expand...
Click to collapse
*get a working adb&fastboot by going to this thread
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
after installing it with success
*reboot to fastboot and connect your device to pc
*open cmd window
* type ( fastboot getvar all ) and press enter
*post the result here after removing serialno and imei
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
*get a working adb&fastboot by going to this thread
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
after installing it with success
*reboot to fastboot and connect your device to pc
*open cmd window
* type ( fastboot getvar all ) and press enter
*post the result here after removing serialno and imei
Click to expand...
Click to collapse
Thank I will

This is all the informations
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.708.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.021s

This phone is a mess. Its the AT&T version (m8_ul_ca), but its been rooted, s-off, SuperCID, and some other firmware installed, or partially installed.
Reason I say "partially installed" is that the firmware number (version-main) 1.29.708.4 isn't one I recognize. But 1.xx main versions typically correspond to KitKat on this device. Which doesn't correspond to hboot 3.19 (which is for Lollipop or Marshmallow), nor the radio number [email protected] which is for AT&T Lollipop firmware.
You should re-baseline this device by RUU. But which RUU is the question. Since you have s-off and SuperCID, you run most RUUs.
The main version "708" corresponds to the Hong Kong version. Is that where you are located? What bands does your carrier use for 3G, and for LTE? These things will determine with RUU to use.

redpoint73 said:
This phone is a mess. Its the AT&T version (m8_ul_ca), but its been rooted, s-off, SuperCID, and some other firmware installed, or partially installed.
Reason I say "partially installed" is that the firmware number (version-main) 1.29.708.4 isn't one I recognize. But 1.xx main versions typically correspond to KitKat on this device. Which doesn't correspond to hboot 3.19 (which is for Lollipop or Marshmallow), nor the radio number [email protected] which is for AT&T Lollipop firmware.
You should re-baseline this device by RUU. But which RUU is the question. Since you have s-off and SuperCID, you run most RUUs.
The main version "708" corresponds to the Hong Kong version. Is that where you are located? What bands does your carrier use for 3G, and for LTE? These things will determine with RUU to use.
Click to expand...
Click to collapse
َAm not sure but i guess it's not AT&T version because i can use any SIM card i want , AT&T version use specific SIM card i guess !!
Any way i'm not from Hong Kong , i use MOBILS SIM card (From the company MOBILIS) for 3g and LTE .
Also i forgot to motion that when i go to software update i find that there is a system update (Software update :4.16.401.13 (57.45 MB)) when i download it , it wan't install because it says (We determine that your phone maybe running a modified version pf its system software . for your protection , we cannot update your phone . please revert your phone to the official htc system software to update your phone.

My responses below in red font:
jonasess said:
ÙŽAm not sure but i guess it's not AT&T version because i can use any SIM card i want , AT&T version use specific SIM card i guess !!
You shouldn't be "guessing' anything, and your guesses would be wrong, anyway. As I've already stated, the product ID m8_ul_ca means its US variant AT&T (that product ID also US Developer's Edition, but ATT is much more common). That much is an absolute fact, and not a guess on my part. Being SIM locked or not, has little bearing on what version you have. Any of these versions can be SIM unlocked with the proper code. So stop guessing at answers, as its not particularly useful.
I'll also guess that the back cover has been replaced. As the AT&T version has the AT&T "globe" logo on the back. We've seen a good number of devices "debranded" by having the back covers replaced to remove carrier logos. I'll guess it has a model/carrier number on the back cover, that also doesn't match any of the getvar info.
Any way i'm not from Hong Kong , i use MOBILS SIM card (From the company MOBILIS) for 3g and LTE .
None of this tells me anything useful. What country are you actually from? More importantly, what specific band (or bands) number does your carrier use for 3G, and what band(s) do they use for LTE?
Also i forgot to motion that when i go to software update i find that there is a system update (Software update :4.16.401.13 (57.45 MB)) when i download it , it wan't install because it says (We determine that your phone maybe running a modified version pf its system software . for your protection , we cannot update your phone . please revert your phone to the official htc system software to update your phone.
The carrier version of the OTA is Euro (401) so it won't install on a phone what has firmware for the Hong Kong version (708). Additionally, you have to install the OTAs sequentially, without skipping. So if you currently have 1.xx version, you can't skip 2.xx and 3.xx and go straight to 4.xx. In other words, there is no way you will get that OTA to install in your current configuration.
Which is why I am suggesting RUU. The RUUs do not need to be installed sequentially. Its a complete re-image, and it would also fix the mismatch you have between the main version (HK) and the hboot, radio (AT&T Lollipop).
Click to expand...
Click to collapse

redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
I'm from Algeria , i guess my country is not supported from the HTC company .
Also as i said i use MOBILIS sim (http://www.mobilis.dz/) i didn't try the 3g or 4g because i use wifi to connect to the internet
Another qeustion : is that mean i can't unlock the bootloader and install the recovery to install CM rooms
In other word there is a risk for that?
++
thanks for the help

jonasess said:
Also as i said i use MOBILIS sim (http://www.mobilis.dz/) i didn't try the 3g or 4g because i use wifi to connect to the internet
Click to expand...
Click to collapse
Again, you are providing info that doesn't answer the questions I asked; and is not particularly useful. You didn't try 3G or 4G. So what? Does that mean you never want to use them, and will never use cell data? Or otherwise?
The following states that Mobilis uses 2100 MHz for 3g, but doesn't state info on 4G: http://www.worldtimezone.com/gsm.html
You can typically call your carrier, and get the answer to the question.
jonasess said:
Another qeustion : is that mean i can't unlock the bootloader and install the recovery to install CM rooms
In other word there is a risk for that?
Click to expand...
Click to collapse
You should be able to unlock the bootloader. But whether you can run any current ROMs is questionable.
Your firmware is a mess. The old firmware number 1.xx won't work with any current ROMs. You should fix your firmware first. But again, by RUU and I need more info before I can direct you to an RUU.
Also the version TWRP custom recovery you will need to flash custom ROMs, depend on what firmware version you have. And your firmware is all screwed up (seems to be partially modified) so again, its best you fix the firmware by RUU before proceeding with anything else.

help me fast please! cannot install RUU.EXE OR ZIP (stucked on white screen logo)

hello,
i really need help because my htc m8 stuck in ( htc white screen logo ) after trying installing a custom rom.
now i want to restore stock rom and i tried more methods but it failed.
i downloaded both of ruu exe and zip file
when i set up ruu.exe after two steps of the setup by click (next)..nothing happen!(although my htc m8 in the black and grey screen logo)
can you help me friends ?what can i do?by the easiest way.
thank you

audi19844 said:
hello,
i really need help because my htc m8 stuck in ( htc white screen logo ) after trying installing a custom rom.
now i want to restore stock rom and i tried more methods but it failed.
i downloaded both of ruu exe and zip file
Click to expand...
Click to collapse
Your post creates far more questions in my head, than answers.
It would make far more sense to try to figure out what went wrong with the custom ROM install, since that is what you were trying to accomplish from the start.
Most issues flashing custom ROM are due to outdated firmware on phone, old version TWRP, or wrong variant of M8. To determine which of those applies to you, we would need more info:
What custom ROM did you try to install? What version TWRP?
Also need to do fastboot getvar all, and post the results (delete IMEI and serial number).
If you still want to use the RUU:
How do you know it was the proper RUU version for your M8 variant (there are dozens)?
What is the file name or version number of the RUU(s) you tried?
Also need the getvar info indicated above, to know more info about the M8 variant, and therefore what determine what RUU to use.
You also need a relocked bootloader to RUU (unless the phone is s-off). But if it is still unlocked, I would recommend you leave it that way, and instead try to troubleshoot why the custom ROM is not working, rather than going backwards and relocking the bootloader, RUU, etc.
Also, when flashing a custom ROM, you should always make a backup in TWRP of the existing (such as stock) ROM before trying to flash a custom ROM. If you had done that, you could just restore the TWRP backup you made, instead of messing with RUUs.

redpoint73 said:
Your post creates far more questions in my head, than answers.
It would make far more sense to try to figure out what went wrong with the custom ROM install, since that is what you were trying to accomplish from the start.
Most issues flashing custom ROM are due to outdated firmware on phone, old version TWRP, or wrong variant of M8. To determine which of those applies to you, we would need more info:
What custom ROM did you try to install? What version TWRP?
Also need to do fastboot getvar all, and post the results (delete IMEI and serial number).
If you still want to use the RUU:
How do you know it was the proper RUU version for your M8 variant (there are dozens)?
What is the file name or version number of the RUU(s) you tried?
Also need the getvar info indicated above, to know more info about the M8 variant, and therefore what determine what RUU to use.
You also need a relocked bootloader to RUU (unless the phone is s-off). But if it is still unlocked, I would recommend you leave it that way, and instead try to troubleshoot why the custom ROM is not working, rather than going backwards and relocking the bootloader, RUU, etc.
Also, when flashing a custom ROM, you should always make a backup in TWRP of the existing (such as stock) ROM before trying to flash a custom ROM. If you had done that, you could just restore the TWRP backup you made, instead of messing with RUUs.
Click to expand...
Click to collapse
Thank you for your importance,
For now a successful ruu.zip flash done by HTC fastboot command prompt.
But the system looks like HTC one m7 Rom!!
Not the HTC m8
What is the wrong

audi19844 said:
For now a successful ruu.zip flash done by HTC fastboot command prompt.
But the system looks like HTC one m7 Rom!!
Not the HTC m8
What is the wrong
Click to expand...
Click to collapse
I asked a number of questions, zero of which you answered. I can't help you, if you don't provide any useful information. You haven't given a single piece of information about your device or the files you tried to flash. How do you think anyone can help you?

redpoint73 said:
I asked a number of questions, zero of which you answered. I can't help you, if you don't provide any useful information. You haven't given a single piece of information about your device or the files you tried to flash. How do you think anyone can help you?
Click to expand...
Click to collapse
sorry for missing information .
- i tried to install ( [ROM][UNOFFICIAL] LineageOS 15.1 for HTC One M8 )
-by twrb recovery 2.7.0.2 may be the recovery was old and i get fail when flashing the rom,so i sucked in the recovery between cant flash the custom rom or returning to the stock one.
-my big fault also was not making backup for my stock rom.
so i thought after that to use the ruu.zip files or ruu.exe
i tried to flash the ruu.exe but after 2 steps i see that (
erorr 130 model id error
the rom utility cannot update your android phone please get the correct rom utility and try again)
i tried to flash the ruu.zip by htc fastboot,and after many times it was succeeded to be flashed by htc fastboot
so this is my htc info
< waiting for device >
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT4*********
(bootloader) imei: 3591970********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__M27
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
the ruu zip file i used was this one ( RUU-4.16.401.10-0P6BIMG.zip )
i dont know if this is true or not one.
the ruu file was successfully flashed but the result was the (m7) like software not m8
thank you for your patience.

audi19844 said:
sorry for missing information .
Click to expand...
Click to collapse
No worries. Thanks for providing the info. You're doing much better now. Now we can get somewhere!
audi19844 said:
-by twrb recovery 2.7.0.2 may be the recovery was old and i get fail when flashing the rom,so i sucked in the recovery between cant flash the custom rom or returning to the stock one.
Click to expand...
Click to collapse
That version is really old, over 3 years old. It's not compatible with current ROMs, and not compatible with your current firmware (which is Marshmallow as shown in the getvar output).
Fail to flash the ROM is an expected result.
If you still want to flash Lineage, you need to flash a more current version (latest is TWRP 3.2.1-0) which you can get from here: https://dl.twrp.me/m8/
But you've also flashed an old RUU, and downgraded the firmware to Lollipop. It's probably not a big deal, but you're going backwards here. You might also find that you need to play around with TWRP versions to get one that works with Lollipop firmware. Not sure, but I think TWRP 3.2 (maybe earlier even) or later does not play well with Lollipop. And the 2.7 is way too old. So a version in between may be needed (2.8.7 is tried and trusted in many cases).
Probably better to RUU back to Marshmallow (I'll describe that below). Then from there, you can flash latest TWRP and then Lineage, if you like.
audi19844 said:
so i thought after that to use the ruu.zip files or ruu.exe
i tried to flash the ruu.exe but after 2 steps i see that (
erorr 130 model id error
Click to expand...
Click to collapse
Sounds like you are flashing multiple RUU versions. But we can't troubleshoot the error message, if you don't tell us what RUU's resulted in the error. RUU 4.16.401.10 clearly didn't give you that error, since it works. So it must have been other RUUs that you trie.
First of all, as the error message makes clear, the RUU for the wrong model (or wrong Carrier ID also) will result in RUU failure.
Also, flashing RUU's randomly, without knowing if it is the right one for your device is really dangerous, and can result in permanent damage if you flash the RUU for the wrong M8 version!
Be aware that flashing RUU (and some other things) is very risky with s-off, if you don't know exactly what you are doing!
audi19844 said:
the ruu zip file i used was this one ( RUU-4.16.401.10-0P6BIMG.zip )
i dont know if this is true or not one.
the ruu file was successfully flashed but the result was the (m7) like software not m8
Click to expand...
Click to collapse
You flashed the Lollipop RUU. You basically downgraded the OS, as you started with Marshmallow. That is probably why you think the software looks like that of the M7.
The Marshmallow RUU is here:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
After that, if you still want to flash Lineage, put TWRP back on the phone (such as version 3.2.1-0) and you should be able to flash Lineage successfully. I assume your bootloader is still shown as UNLOCKED on the bootloader screen?

redpoint73 said:
No worries. Thanks for providing the info. You're doing much better now. Now we can get somewhere!
That version is really old, over 3 years old. It's not compatible with current ROMs, and not compatible with your current firmware (which is Marshmallow as shown in the getvar output).
Fail to flash the ROM is an expected result.
If you still want to flash Lineage, you need to flash a more current version (latest is TWRP 3.2.1-0) which you can get from here: https://dl.twrp.me/m8/
But you've also flashed an old RUU, and downgraded the firmware to Lollipop. It's probably not a big deal, but you're going backwards here. You might also find that you need to play around with TWRP versions to get one that works with Lollipop firmware. Not sure, but I think TWRP 3.2 (maybe earlier even) or later does not play well with Lollipop. And the 2.7 is way too old. So a version in between may be needed (2.8.7 is tried and trusted in many cases).
Probably better to RUU back to Marshmallow (I'll describe that below). Then from there, you can flash latest TWRP and then Lineage, if you like.
Sounds like you are flashing multiple RUU versions. But we can't troubleshoot the error message, if you don't tell us what RUU's resulted in the error. RUU 4.16.401.10 clearly didn't give you that error, since it works. So it must have been other RUUs that you trie.
First of all, as the error message makes clear, the RUU for the wrong model (or wrong Carrier ID also) will result in RUU failure.
Also, flashing RUU's randomly, without knowing if it is the right one for your device is really dangerous, and can result in permanent damage if you flash the RUU for the wrong M8 version!
Be aware that flashing RUU (and some other things) is very risky with s-off, if you don't know exactly what you are doing!
You flashed the Lollipop RUU. You basically downgraded the OS, as you started with Marshmallow. That is probably why you think the software looks like that of the M7.
The Marshmallow RUU is here:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
After that, if you still want to flash Lineage, put TWRP back on the phone (such as version 3.2.1-0) and you should be able to flash Lineage successfully. I assume your bootloader is still shown as UNLOCKED on the bootloader screen?
Click to expand...
Click to collapse
I would like to thank you for your big help, thank you very much
I successfully used Marshmallow RUU
and my phone is now ok.
I learned now what i shoud do next time before installing a custom rom.
Thank you again.