Develop Bugs

[Q] About different One M8 boards, LTE support and more

I'm a happy One M8 user since June '14, never had an issue (except for the camera lens scratch, which I was able to reapir thankfully to the XDA community) but there's one thing that always bother me,
I have no 4G support.
I live in Brazil and here we use the 2600MHz (IMT-E) band for LTE, but my model only have LTE 700MHz (Lower SMH Blocks B/C) and LTE 1700MHz (AWS A-F) bands avaliable.
I know that is a way to change the avalible bands using a NV writer and changing some values there, and I did try to change, but my M8 always return to the old values after I disconnect from QPST. *Of course I looked for the proper way to calculate the numbers to put there before try anything*
My device is Unlocked/S-OFF/and w/Super CID.
Now the questions:
1. If I flash a EU RUU, is there a chance to this RUU change the NV partition and modify the values from LTE support? (Since the EU M8 have support for the 2600MHz band)
2. If the answer for the first question is afirmative, do I have to relock my phone to be able to flash the RUU or do something else?
3. If the answer for the first question is not afirmative, I need to know if all boards have LTE support. Mine is 0P6B13000. Maybe not all of them include hardware support for all LTE bands (?)
Could someone with the same board tell me if you have this band avaliable on your phone, please
PS: I do know that I have a US variant, but I don't know what carrier is the owner of the HTC__017 cid (the original from my phone). I know that this board is used by US T-Mobile too, and they also don't include support to 2600MHz LTE on their phones.

Bump

dxzdxz1 said:
I'm a happy One M8 user since June '14, never had an issue (except for the camera lens scratch, which I was able to reapir thankfully to the XDA community) but there's one thing that always bother me,
I have no 4G support.
I live in Brazil and here we use the 2600MHz (IMT-E) band for LTE, but my model only have LTE 700MHz (Lower SMH Blocks B/C) and LTE 1700MHz (AWS A-F) bands avaliable.
I know that is a way to change the avalible bands using a NV writer and changing some values there, and I did try to change, but my M8 always return to the old values after I disconnect from QPST. *Of course I looked for the proper way to calculate the numbers to put there before try anything*
My device is Unlocked/S-OFF/and w/Super CID.
Now the questions:
1. If I flash a EU RUU, is there a chance to this RUU change the NV partition and modify the values from LTE support? (Since the EU M8 have support for the 2600MHz band)
2. If the answer for the first question is afirmative, do I have to relock my phone to be able to flash the RUU or do something else?
3. If the answer for the first question is not afirmative, I need to know if all boards have LTE support. Mine is 0P6B13000. Maybe not all of them include hardware support for all LTE bands (?)
Could someone with the same board tell me if you have this band avaliable on your phone, please
PS: I do know that I have a US variant, but I don't know what carrier is the owner of the HTC__017 cid (the original from my phone). I know that this board is used by US T-Mobile too, and they also don't include support to 2600MHz LTE on their phones.
Click to expand...
Click to collapse
I'm about 99.99% sure it will work just fine. You won't need the whole RUU though. Just flash a 4.16.401.10 firmware package.

My advice below in red font:
dxzdxz1 said:
1. If I flash a EU RUU, is there a chance to this RUU change the NV partition and modify the values from LTE support? (Since the EU M8 have support for the 2600MHz band) Advise to flash the Euro firmware (in agreement with previous response) or RUU.
2. If the answer for the first question is afirmative, do I have to relock my phone to be able to flash the RUU or do something else? Since you are s-off, NO. You can run the RUU with unlocked bootloader. However, you will need to change the MID.
3. If the answer for the first question is not afirmative, I need to know if all boards have LTE support. Mine is 0P6B13000. Maybe not all of them include hardware support for all LTE bands (?) All boards have LTE support; and specific band support is set in radio firmware. All "GSM" versions are the same in hardware to my knowledge, the exceptions being "CDMA" variants (Sprint & Verizon) and dual SIM version.
Could someone with the same board tell me if you have this band avaliable on your phone, please
PS: I do know that I have a US variant, but I don't know what carrier is the owner of the HTC__017 cid (the original from my phone). I know that this board is used by US T-Mobile too, and they also don't include support to 2600MHz LTE on their phones. Not familiar with that CID. But my guess is that its a regional US carrier that uses T-Mobile's network. Google search for "HTC_0017" yields some results for Cincinnati Bell. Although that would make it associated with AT&T, rather than T-Mobile. So probably just confusing the issue more here.
But its somewhat irrelevant. You've already changed the CID, and can change the MID to whatever you like.
Click to expand...
Click to collapse

redpoint73 said:
My advice below in red font:
Click to expand...
Click to collapse
xunholyx said:
I'm about 99.99% sure it will work just fine. You won't need the whole RUU though. Just flash a 4.16.401.10 firmware package.
Click to expand...
Click to collapse
I tried to flash only a EU radio.img = No success.
Then I tried to flash a EU firmware = Still no success.
And then I tried to install a ruu, but again, no success.
Is there anything else that I could try?

dxzdxz1 said:
I tried to flash only a EU radio.img = No success.
Then I tried to flash a EU firmware = Still no success.
And then I tried to install a ruu, but again, no success.
Is there anything else that I could try?
Click to expand...
Click to collapse
Get into ADB/fastboot, and do fastboot getvar all. Post the readout here (delete your IMEI and serial# ~ that is private info you should never post on a public forum) and someone will be able to direct you on how to update properly.
I'm not positive (but I mostly am), but I don't think WWE/EU firmware is compatible with you model.

dxzdxz1 said:
I tried to flash only a EU radio.img = No success.
Then I tried to flash a EU firmware = Still no success.
And then I tried to install a ruu, but again, no success.
Is there anything else that I could try?
Click to expand...
Click to collapse
You need to tell us where the processes failed, and any error messages. And exactly what files you tried to flash. There are quite a few RUUs, firmwares, and radios possible, even if isolated to Euro WWE.
Did you change the MID on the phone, as I mentioned previously?
RUU will absolutely fail with your present MID. Firmware probably, and radio maybe will also fail due to MID. It depends on what exactly you tried to flash, and if the MID check was removed.

redpoint73 said:
You need to tell us where the processes failed, and any error messages. And exactly what files you tried to flash. There are quite a few RUUs, firmwares, and radios possible, even if isolated to Euro WWE.
Did you change the MID on the phone, as I mentioned previously?
RUU will absolutely fail with your present MID. Firmware probably, and radio maybe will also fail due to MID. It depends on what exactly you tried to flash, and if the MID check was removed.
Click to expand...
Click to collapse
xunholyx said:
Get into ADB/fastboot, and do fastboot getvar all. Post the readout here (delete your IMEI and serial# ~ that is private info you should never post on a public forum) and someone will be able to direct you on how to update properly.
I'm not positive (but I mostly am), but I don't think WWE/EU firmware is compatible with you model.
Click to expand...
Click to collapse
Here is the thing, guys
Nothing has failed.
The RUU has been installed, but LTE still doesn't work
This is my old getvar info that I saved for those "just in case" situations:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.12.422.19
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: HTC__017
(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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
And here is my actual getvar info
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(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
Click to expand...
Click to collapse

This may be a stupid question, but are you sure your SIM supports LTE? That is a carrier option that can be enabled or disabled. It may not be an issue, but it is certainly worth checking if you aren't sure.

jshamlet said:
This may be a stupid question, but are you sure your SIM supports LTE? That is a carrier option that can be enabled or disabled. It may not be an issue, but it is certainly worth checking if you aren't sure.
Click to expand...
Click to collapse
Not a stupid question at all. Assuming the proper LTE band support has been enabled, and proper APN settings, there isn't any reason for LTE to not work; unless there is something wrong carrier/network side, such as account provisioning as you mention.

M7 didn't retain nv changes either.

jshamlet said:
This may be a stupid question, but are you sure your SIM supports LTE? That is a carrier option that can be enabled or disabled. It may not be an issue, but it is certainly worth checking if you aren't sure.
Click to expand...
Click to collapse
redpoint73 said:
Not a stupid question at all. Assuming the proper LTE band support has been enabled, and proper APN settings, there isn't any reason for LTE to not work; unless there is something wrong carrier/network side, such as account provisioning as you mention.
Click to expand...
Click to collapse
This is the same SIM a used to have on my old Xperia Z, I just cut off to fit on my M8.
My SIM is not the problem, because on my old phone I was able to connect on LTE.
SaHiLzZ said:
M7 didn't retain nv changes either.
Click to expand...
Click to collapse
Maybe is locked by the kernel (?)
I really don't know why I can't modify the NV values
On my sister Nexus 5 I changed the NV settings and it work just fine.

dxzdxz1 said:
This is the same SIM a used to have on my old Xperia Z, I just cut off to fit on my M8.
My SIM is not the problem, because on my old phone I was able to connect on LTE.
Maybe is locked by the kernel (?)
I really don't know why I can't modify the NV values
On my sister Nexus 5 I changed the NV settings and it work just fine.
Click to expand...
Click to collapse
The SIM is definitely the problem.
You can't just cut them to make them fit. The contact points are all different.

xunholyx said:
The SIM is definitely the problem.
You can't just cut them to make them fit. The contact points are all different.
Click to expand...
Click to collapse
I use one of these tools made for cut SIM chips, and I can still make calls and use 3G connection. If the cut is (was) the problem, why everything else is working?
Well, just in case, I will buy another SIM and transfer my phone number tomorrow
Thank you for everything so far.

dxzdxz1 said:
I use one of these tools made for cut SIM chips, and I can still make calls and use 3G connection. If the cut is (was) the problem, why everything else is working?
Well, just in case, I will buy another SIM and transfer my phone number tomorrow
Thank you for everything so far.
Click to expand...
Click to collapse
I've googled this now, and apparently you can cut them down.
But you'll still need to buy a SIM that supports LTE. Older ones don't.
Thanks for the knowledge about cutting them. I never knew. I always thought that the resize changed contacts.

Not a kernel issue, afaik. I have tried with S-OFF, Tmobile RUU, custom roms. Best of luck though..

xunholyx said:
I've googled this now, and apparently you can cut them down.
But you'll still need to buy a SIM that supports LTE. Older ones don't.
Thanks for the knowledge about cutting them. I never knew. I always thought that the resize changed contacts.
Click to expand...
Click to collapse
Today a bought a new SIM, and LTE still doesn't work.
SaHiLzZ said:
Not a kernel issue, afaik. I have tried with S-OFF, Tmobile RUU, custom roms. Best of luck though..
Click to expand...
Click to collapse
I searched for threads about NV editing here on XDA and it seems that some manufacturers DO lock changes on NV partition.
Quoted from this thread
One surprising finding was that people with older phones were having better results. Why? It seems that Qualcomm quietly added some anti-tamper code into recent Android versions to keep us from doing this. It's almost like they read our forum and know what we're trying to mod. But they wouldn't spy on us like that, would they?
Click to expand...
Click to collapse
So it seems to be that now only people with custom ROMs/kernels can do modifications to NV.
I also read on a Nexus 5 thread that a combination of AOSP ROM and Faux Hybrid Kernel is working for newer devices and/or new updates.
I have only tested CM12 nightlies and I couldn't enter on DiagMode. The default shell command isn't working there.
Tonight I will try another combinations and see if works.

I tested all aosp roms from Orig Development subforum and I wasn't able to mount my M8 in Diag Mode
There's anything else left to try?

dxzdxz1 said:
I tested all aosp roms from Orig Development subforum and I wasn't able to mount my M8 in Diag Mode
There's anything else left to try?
Click to expand...
Click to collapse
I'm in the same boat too.. trying to add band 3 to my M8 with stock rom android 5.0.1 , this one is from Canada with bands 4, 7 and 17, same issue, NV values won't stick in M8, tried with ElementalX-m8-4.05-Sense kernel too. already used QPST, QXDM tool combination and DFS CDMA tool to try editing the 6828 and 6829 values. no luck still, values won't stick. read a lot and found lots of people with M8 having the same issue, no clue though.
You can try use the method in this guide, it's for M9 but works for M8 as well except NV values won't stick for me. also you can use this DFS CDMA tool to confirm the LTE bands you are already having. read button in LTE tab displays the bands you are having. by this you can confirm that there is no issue with the sim but you do or do not have the required LTE bands.
http://forum.xda-developers.com/one-m9/general/how-to-change-network-bands-gsm-devices-t3135401
i found two commands to get diag mood on,
1. echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
2. setprop sys.usb.diag.config diagon
you can try one of them to get diag mood on so you can use a tool. im about to give up on this now. let us know if you make any progress . :fingers-crossed:

M8 Stagefright update OTA not working + SUPERCID and Wrong ROM

Hello
Here are the "stats" of my brand new HTC M8, I say brand new in that I broke the cellophane seal, and took off the protectors but I'm starting to think it has been tampered with....
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.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I opened up a log file on phone whilst browsing the Android Recovery and spotted these attributes within a very large log file
Code:
CID = CWS__001
MID = 0P6B1200
aa.cid = BS_US001
sku = Brightstar US WWE
project = M8_UL_L50_SENSE60_MR 411207
buildline = M8UL_BrightstarUS_WWE_L50_CRC_Sense60_stable_mr
First thing you'll notice is the SUPERCID of 11111111, the log seems to imply it was once at CWS__001, but who knows.
You'll also notice it's an M8_UL_CA variant, which Google tells me is the AT&T variant, but that it has the M8_UL Brightstart WWE ROM installed. [I don't want AT&T updates]
So with all these changes, it's understandable that when I ran the OTA stagefright update, HTC would not allow the install saying I have a "Variant System Update" error, saying that I need to restore to stock or call HTC for support.
My question: How do I go about updating this phone with stock images as and when they get released without tampering too much with unlocked this and that?
What I've tried: I downloaded the latest RUU from the US site, tried to run it, but it closes before it even starts [even after I installed all the VCRedists, and tried on 3 computers]. So I unpacked the .exe and took out the rom.zip and tried to flash it in fastboot... I got an
Code:
FAILED (remote: 12 signature verify fail)
error. Google tells me this is because one or more of the checks on CID MID etc does not match the ROM. Android.txt in the .exe has the right MID but not the right CID.
I think my last hope is to Unlock the bootloader, S-OFF and Install TWRP and install Stock ROMS that way, but theres two problems with this approach, One - I don't why if I need S-OFF and Bootloader unlocked to install a ROM, do you need both, or just one or something else? and Two - I can't find the latest ROM. I can only find the one I'm on now, which will still probably bug me for an OTA update for stagefright. Plus it's a mine field to work out which ROM is what, with CIDs and MIDs and Models and Carriers etc.
Any help would be great, as I want to migrate to this phone from my S5, but I wont until I know its stable and working.
Thanks in advance.

Vyker said:
You'll also notice it's an M8_UL_CA variant, which Google tells me is the AT&T variant, but that it has the M8_UL Brightstart WWE ROM installed. [I don't want AT&T updates]
Click to expand...
Click to collapse
I think you are mostly correct, in that it was an AT&T variant, but "fully converted" (no just ROM, but all firmware - likely by RUU) to Developer's Edition (Brightstar) which happens to share the same MID (12000).
Does it have the AT&T "globe/deathstar" logo on the back cover? It only means much if the answer is "yes". If "no", its possible the back cover was replaced (with an "unbranded" cover).
Also, I agree SuperCID is an indication that phone was modded. I've never seen a phone come from the factory with SuperCID.
Vyker said:
What I've tried: I downloaded the latest RUU from the US site, tried to run it, but it closes before it even starts [even after I installed all the VCRedists, and tried on 3 computers]. So I unpacked the .exe and took out the rom.zip and tried to flash it in fastboot... I got an
Code:
FAILED (remote: 12 signature verify fail)
error. Google tells me this is because one or more of the checks on CID MID etc does not match the ROM. Android.txt in the .exe has the right MID but not the right CID.
Click to expand...
Click to collapse
What is the exact file name of the RUU.exe?
Vyker said:
I think my last hope is to Unlock the bootloader, S-OFF and Install TWRP and install Stock ROMS that way, but theres two problems with this approach, One - I don't why if I need S-OFF and Bootloader unlocked to install a ROM, do you need both, or just one or something else? and Two - I can't find the latest ROM. I can only find the one I'm on now, which will still probably bug me for an OTA update for stagefright. Plus it's a mine field to work out which ROM is what, with CIDs and MIDs and Models and Carriers etc.
Click to expand...
Click to collapse
You don't need s-off to flash a ROM or stock nandroid.
If you want to take this path, what you want is the Developer's Edition ROM which matches 4.16.1540.8 listed as your "main version".
But I'm confident we can get the proper RUU working.

Thanks for a thorough reply redpoint - was really worried I'd get a "just flash CM on it" one liner that won't really help me....
redpoint73 said:
Does it have the AT&T "globe/deathstar" logo on the back cover? It only means much if the answer is "yes". If "no", its possible the back cover was replaced (with an "unbranded" cover).
Click to expand...
Click to collapse
No, nothing on it hints to AT&T, not the box, not the phone and not the OS. If you look at it, you'd think its a brand new HTC branded device.
redpoint73 said:
What is the exact file name of the RUU.exe?
Click to expand...
Click to collapse
RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2.exe
I got it from here..
http://www.htc.com/us/support/htc-one-m8/news/
And here is what was in the android-info.txt file
Code:
modelid: 0P6B12000
modelid: 0P6B13000
cidnum: BS_US001
cidnum: BS_US002
cidnum: HTC__017
mainver: 4.17.1540.9
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
redpoint73 said:
You don't need s-off to flash a ROM or stock nandroid.
Click to expand...
Click to collapse
So just need to unlock the bootloader with htcdev.com and then flash a custom recovery - then straight onto nandroid backups of the correct version, right?
redpoint73 said:
If you want to take this path, what you want is the Developer's Edition ROM which matches 4.16.1540.8 listed as your "main version".
But I'm confident we can get the proper RUU working.
Click to expand...
Click to collapse
I would love to get it going with just an RUU. As I feel once the first RUU works, then it'll be plain sailing from there for all future ones including Marshmallow.
Looking forward to your reply and thanks again.

Vyker said:
No, nothing on it hints to AT&T, not the box, not the phone and not the OS. If you look at it, you'd think its a brand new HTC branded device.
Click to expand...
Click to collapse
Does it have a model number in tiny print, at the bottom of the back cover? If so, what model number is it?
Vyker said:
RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.17.1540.9_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_446501_signed_2.exe
Click to expand...
Click to collapse
This should work for your MID and main version. Is your bootloader UNLOCKED, RELOCKED, or LOCKED?

redpoint73 said:
Does it have a model number in tiny print, at the bottom of the back cover? If so, what model number is it?
Click to expand...
Click to collapse
I'll get another reply after this, need to get back home and check.
redpoint73 said:
This should work for your MID and main version. Is your bootloader UNLOCKED, RELOCKED, or LOCKED?
Click to expand...
Click to collapse
Bootloader is LOCKED.
Does it just check for MID, or will it also look for the CID? as you know the CID is 1111111, when I tried to change my CID I got the error below
Code:
fastboot oem writecid BS_US002
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.141s

Vyker said:
Bootloader is LOCKED.
Does it just check for MID, or will it also look for the CID? as you know the CID is 1111111
Click to expand...
Click to collapse
It checks both MID and CID. But SuperCID (11111111) should work, as SuperCID by definition will "pass" any CID checks.
But CID is the only remaining thing I can think of that would prevent the RUU from being run. The RUU is okay for your main version (1540, and the RUU is a equal or higher version), MID, and bootloader is LOCKED (as it should be to RUU).
Vyker said:
when I tried to change my CID I got the error below
Click to expand...
Click to collapse
You need s-off to change CID. It would be a last resort, as s-off costs $25 and might not even solve the issue.
One thing you can try, is load sunshine app to see if the phone was already s-off previously by sunshine. If so, you may be able to s-off for free; as the $25 license fee is per phone, and it should let you s-off again, if sunshine was used previously on this phone.
http://theroot.ninja/
I suspect the phone was s-off at some point, then SuperCID, then made s-on again.
The only other way it would be SuperCID, is from the factory. And as I've mentioned, I've never heard of an HTC device with SuperCID from the factory. Although there is a first time for everything!

redpoint73 said:
Does it have a model number in tiny print, at the bottom of the back cover? If so, what model number is it?
Click to expand...
Click to collapse
In very small print, the following is written on the bottom back.
Model: 0P6B100 and after the FCC ID it says "M8n"
redpoint73 said:
One thing you can try, is load sunshine app to see if the phone was already s-off previously by sunshine. If so, you may be able to s-off for free; as the $25 license fee is per phone, and it should let you s-off again, if sunshine was used previously on this phone.
http://theroot.ninja/
I suspect the phone was s-off at some point, then SuperCID, then made s-on again.
The only other way it would be SuperCID, is from the factory. And as I've mentioned, I've never heard of an HTC device with SuperCID from the factory. Although there is a first time for everything!
Click to expand...
Click to collapse
Interesting thought.
I installed SunShine, and had it run through its pre-tests - it says the phone passed and then goes ahead to attempt to temp-root it and then fails. The phone is not rooted.
Does this pre-test pass mean anything? is that what you were looking for?

Vyker said:
In very small print, the following is written on the bottom back.
Model: 0P6B100 and after the FCC ID it says "M8n"
Click to expand...
Click to collapse
Odder and odder. Of course, this doesn't match the MID given in getvar. So either the MID was hacked in software, or there was a "hardware hack" of replacing the back cover.
Vyker said:
Interesting thought.
I installed SunShine, and had it run through its pre-tests - it says the phone passed and then goes ahead to attempt to temp-root it and then fails. The phone is not rooted.
Does this pre-test pass mean anything? is that what you were looking for?
Click to expand...
Click to collapse
I think pre-test just means you have a stock system (not a custom ROM), which is pretty much required for sunshine to work.
Unfortunately, I can't help too much with sunshine, beyond what I've already stated. I actually did s-off long before sunshine using another (obsolete) method, and can only pass on sunshine knowledge that I've read on these forums!
I'm hesitant to go any further with sunshine, as it may just end up with you paying $25 and not even solve the RUU issue anyway.
I have a feeling I'm missing something here, but I can't imagine what.

redpoint73 said:
Odder and odder. Of course, this doesn't match the MID given in getvar. So either the MID was hacked in software, or there was a "hardware hack" of replacing the back cover.
Click to expand...
Click to collapse
Unmatched indeed - here's another dynamic, the part number on the back of the box, which has a sticker with the correct IMEI and Serial number tells me the part number is 99HJY001-00 - which a quick Google shows it as the Amber Gold variant - I'm holding a Red phone. :/
redpoint73 said:
I think pre-test just means you have a stock system (not a custom ROM), which is pretty much required for sunshine to work.
Unfortunately, I can't help too much with sunshine, beyond what I've already stated. I actually did s-off long before sunshine using another (obsolete) method, and can only pass on sunshine knowledge that I've read on these forums!
I'm hesitant to go any further with sunshine, as it may just end up with you paying $25 and not even solve the RUU issue anyway.
I have a feeling I'm missing something here, but I can't imagine what.
Click to expand...
Click to collapse
When I spoke to HTC support a week or so ago, they told me it's a GroupO Inc device, they are a large supply chain company in the US. M8_UL_CA tells us it's an AT&T model, HTC M8n is the international variant model number, and the part number says it should be Gold. The CID used to be CWS we think, but has SUPERCID now, yet its LOCKED and not RELOCKED or TAMPERED in the bootloader, which means how was it unlocked, changed and then relocked but still showing as LOCKED.
Does that sum up where we're so far? #confused.
I'm starting to think the only real option here is to go rouge, and unlock the lot, bootloader and S-OFF, then start with a fresh stock ROM that can be rooted. But I can only bring myself to go down this route knowing that I can get stock 6.0 update.

Vyker said:
I'm holding a Red phone. :/
Click to expand...
Click to collapse
Hubba-whaaat??? Its RED???
Holy plot twist! I did not see that coming. There was never any AT&T red version, and I'm pretty sure there was never a red Dev Edition (Brightstar) either.
The only red variants know of are Verizon (which would have the VZN logo, I believe) and UK O2, which might match the "100" model number.
So the front bezels are red also?
Where did you buy this from, anyway?
Vyker said:
I'm holding a Red phone. :/
The CID used to be CWS we think, but has SUPERCID now, yet its LOCKED and not RELOCKED or TAMPERED in the bootloader, which means how was it unlocked, changed and then relocked but still showing as LOCKED.
Click to expand...
Click to collapse
Once s-off (which would be required to make it SuperCID), it easy to mod the bootloader flag to say LOCKED. There is a guide for that in the Development section.
Vyker said:
I'm starting to think the only real option here is to go rouge, and unlock the lot, bootloader and S-OFF, then start with a fresh stock ROM that can be rooted. But I can only bring myself to go down this route knowing that I can get stock 6.0 update.
Click to expand...
Click to collapse
If we can't get an RUU to work, that may be your best bet.
If the RUU is failing, an OTA would probably fail also. But I'm confidant there will be Marshmallow custom Sense ROMs to flash. There is already a MM GPE ROM.

redpoint73 said:
Hubba-whaaat??? Its RED???
Holy plot twist! I did not see that coming. There was never any AT&T red version, and I'm pretty sure there was never a red Dev Edition (Brightstar) either.
The only red variants know of are Verizon (which would have the VZN logo, I believe) and UK O2, which might match the "100" model number.
So the front bezels are red also?
Where did you buy this from, anyway?
Click to expand...
Click to collapse
Hahaha, yes, it's red, its a lovely Red too, even the box has a red photo on the front.
Yes, all the parts are Red, front speaker grills and even the bits that come out, the sim tray and sd card holder etc.
I got it off eBay as a Brand new device from Hong Kong
redpoint73 said:
Once s-off (which would be required to make it SuperCID), it easy to mod the bootloader flag to say LOCKED. There is a guide for that in the Development section.
Click to expand...
Click to collapse
yes, I did spot this Googling around... so it may be what he has done
redpoint73 said:
If we can't get an RUU to work, that may be your best bet.
If the RUU is failing, an OTA would probably fail also. But I'm confidant there will be Marshmallow custom Sense ROMs to flash. There is already a MM GPE ROM.
Click to expand...
Click to collapse
What can we try next to get the RUU to run? I want to try and exhaust all avenues with this approach before giving in to unlocking and ROM'ing.
Thanks for your time and help so far mate, appreciate it.

Trouble locating origin of One m8

Hello to you all,
I thought about asking in the help thread but my post will be somewhat long XD
I'm having trouble locating the origin of my HTC One M8 that I bought 2 days ago in bulk from a local shop. It's new, SIM Unlocked, but apparently rooted and S-OFF, figured it was needed in order to unlock it from it's former carrier, which brings me to my question : I want to know it's original carrier and region in order to safely select RUU and ROMs and preferably I would like to do OTAs too. I want to know whether I'll have problems updating to Marshmallow in the future.
Now, in the back of the phone is written : model OP6B700, that would make it a Sprint device right ? which from what I read is pretty delicate to work with, being CDMA and all.
CID Getter gave me : OPTUS_001
And here is my fastboot getvar all :
(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: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT548WMxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I noticed I have superCID ... why doesn't CID Getter report it ? If I want to revert it back which one do I input ? I don't know the stock value.
I noticed my MID is OP6B65000 what model is this ?
Really confused right now should I go ahead and install OTA ? I have one notification version 4.16.401.13 that wants to be installed.
Also I have "unknown" under HTC SDK API level, don't know why.
It seems I have the 2.5Ghz version of S801, but some utilities report AC variant some others AB. I got 63k on AnTuTu 6.2.6
Other than that the phone seems to be running really good, snappy, no lag, gets a bit warm with light usage, I don't think I got a fake one but correct me if I'm wrong.
It's in airplane mode, haven't put a SIM card in yet.
So what do you guys think ? I surely appreciate any insight you might have

ELS28 said:
I want to know whether I'll have problems updating to Marshmallow in the future.
Click to expand...
Click to collapse
You don't have to wait to update to Marshmallow if you want to, you can do it now.
ELS28 said:
...in the back of the phone is written : model OP6B700, that would make it a Sprint device right ? which from what I read is pretty delicate to work with, being CDMA and all.
Click to expand...
Click to collapse
That's only back cover get replaced. You getvar result doesn't show it is a Sprint device.
Sprint product is M8_WHL and yours is GSM M8_UL
ELS28 said:
CID Getter gave me : OPTUS_001
And here is my fastboot getvar all :
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-main: 4.18.708.12
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
bootloader) security: off
I noticed I have superCID ... why doesn't CID Getter report it ? If I want to revert it back which one do I input ? I don't know the stock value.
I noticed my MID is OP6B65000 what model is this ?
It seems I have the 2.5Ghz version of S801
Click to expand...
Click to collapse
Based of the info above especially the MID 0P6B65000 & 2.5Ghz .. that's an Optus device ... originally from Australia. The original CID is OPTUS_001
ELS28 said:
Really confused right now should I go ahead and install OTA ? I have one notification version 4.16.401.13 that wants to be installed.
Click to expand...
Click to collapse
You can't do OTA to 4.16.401.13, won't work .. you'll get system variant error with OTA.
ELS28 said:
It's in airplane mode, haven't put a SIM card in yet.
Click to expand...
Click to collapse
You should put a SIM to test whether it's really SIM unlocked from Optus.
Also to check whether LTE is working fine.
Where are you located ? You have a S-Off device, you can install any region GSM RUU (if available) but not OTA to 4.16.401.13 when your OS on bootloader is shown as Hong Kong and MID is Optus Australia.

ckpv5 said:
You don't have to wait to update to Marshmallow if you want to, you can do it now.
That's only back cover get replaced. You getvar result doesn't show it is a Sprint device.
Sprint product is M8_WHL and yours is GSM M8_UL
Based of the info above especially the MID 0P6B65000 & 2.5Ghz .. that's an Optus device ... originally from Australia. The original CID is OPTUS_001
You can't do OTA to 4.16.401.13, won't work .. you'll get system variant error with OTA.
You should put a SIM to test whether it's really SIM unlocked from Optus.
Also to check whether LTE is working fine.
Where are you located ? You have a S-Off device, you can install any region GSM RUU (if available) but not OTA to 4.16.401.13 when your OS on bootloader is shown as Hong Kong and MID is Optus Australia.
Click to expand...
Click to collapse
Thank you for replying
To answer your question, my location is north africa. Tomorrow I'll get a nano SIM to try.
The information you provided raised some more questions :
1- I can't do OTAs, so the only way to update for me is through RUU or custom ROMS ?
2- I have a Hong Kong OS, can I change it ? will I have to change the MID and CID accordingly ? I can choose whatever values I want it won't cause any problems ?
3- How come while in OS I have different build numbers than in Bootloader ? in OS I have build version : 4.16.401.10. That's europe version right ?
4- Let's say I want to revert everything back to stock international version with Sense etc, to be able to do OTAs, what do I have to do ?

ELS28 said:
Thank you for replying
To answer your question, my location is north africa. Tomorrow I'll get a nano SIM to try.
Click to expand...
Click to collapse
Do that first .. see any problem with network.
ELS28 said:
1- I can't do OTAs, so the only way to update for me is through RUU or custom ROMS ?
Click to expand...
Click to collapse
You can do OTA only if you put the Optus ROM in your device. The problem is back to Optus and do OTA may break the SIM unlock.
But why do you want to OTA ? You can manually direct update it to Marshmallow if that is your intention.
ELS28 said:
2- I have a Hong Kong OS, can I change it ? will I have to change the MID and CID accordingly ? I can choose whatever values I want it won't cause any problems ?
Click to expand...
Click to collapse
You don't need to change the CID, let it be SuperCID but you may need to change MID (some people said no need to change MID when SuperCID but personally I don't experience a success firmware flashing without proper MID)
You can only choose any value meant for GSM but not CDMA. While on SuperCID, you need only change MID or change it to SuperMID.
ELS28 said:
3- How come while in OS I have different build numbers than in Bootloader ? in OS I have build version : 4.16.401.10. That's europe version right ?
Click to expand...
Click to collapse
Bootloader info is your firmware info.
OS no. in settings is Software info.
So this is like you're running a custom ROM, running a Europe ROM on Hong Kong firmware.
ELS28 said:
4- Let's say I want to revert everything back to stock international version with Sense etc, to be able to do OTAs, what do I have to do ?
Click to expand...
Click to collapse
Depends on which International version .. let say it is Europe version
1. I suggest to change the MID to 0P6B10000 - http://forum.xda-developers.com/showthread.php?t=2708581
2. Install latest Europe RUU - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
(skip the relocking part)

ckpv5 said:
Do that first .. see any problem with network.
You can do OTA only if you put the Optus ROM in your device. The problem is back to Optus and do OTA may break the SIM unlock.
But why do you want to OTA ? You can manually direct update it to Marshmallow if that is your intention.
You don't need to change the CID, let it be SuperCID but you may need to change MID (some people said no need to change MID when SuperCID but personally I don't experience a success firmware flashing without proper MID)
You can only choose any value meant for GSM but not CDMA. While on SuperCID, you need only change MID or change it to SuperMID.
Bootloader info is your firmware info.
OS no. in settings is Software info.
So this is like you're running a custom ROM, running a Europe ROM on Hong Kong firmware.
Depends on which International version .. let say it is Europe version
1. I suggest to change the MID to 0P6B10000 - http://forum.xda-developers.com/showthread.php?t=2708581
2. Install latest Europe RUU - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
(skip the relocking part)
Click to expand...
Click to collapse
Hi, sorry for delayed answer.
Bought a new nanoSIM today, seems to be working fine, made a few calls etc... LTE isn't available in my municipality yet, it will be in the upcoming months but I have the option to select it. I did test HSPA though and it works fine. I guess it's fully sim unlocked then
Regarding OTA, I just saw it as an easier way to update than the commands I had to enter to flash via RUU and all... I guess now I have to learn them alright
So it's my firmware that's from Hong Kong, I didn't know that thanks for the clarification.
Sorry I have more questions
1-Now that I'm running HK firmware and corresponding MID but EU ROM, you suggested I change to EU MID, but won't that cause issues with firmware being HK ?
2- If I flash the EU RUU you sent me, I assume the firmware will no longer be HK, correct ? and after that I can just keep to install EU roms and be trouble free ?
3-I assume that my simUnlock is definitive now, correct ?
4-You seem to be certain I have superCID, so bootloader info trumps CIDgetter info, but I'm curious, why the value differs between the two ? does the app not report it correctly after changing the value ?
5-I will be downloading the files from the links you sent me, and doing my homework too but for information's sake, when I boot in bootloader, I have the "locked" banner, but you know that already I also have "software status : official" does it indicate that the Lollipop EU ROM I currently have is a stock signed one ?
6-My device came rooted but I don't see Superuser installed, I assume I'll have to root it again after the update, correct ?
A Big Thank you for the big help :good:

1-Now that I'm running HK firmware and corresponding MID but EU ROM, you suggested I change to EU MID, but won't that cause issues with firmware being HK ?​You have OS Hong Kong no. which I assume it's HKG firmware but your MID is not HKG but it can be Australia and it can be India. I assume it is Australia as it has 2.5 Ghz and CID OPTUS001 (as you mentioned it)
Change it to EU MID won't cause any issue but a better option as the current ROM on your device is EU 4.16.401.10 and that's why you get notification for OTA to 4.16.401.13
2- If I flash the EU RUU you sent me, I assume the firmware will no longer be HK, correct ? and after that I can just keep to install EU roms and be trouble free​You need to change MID first to EU then install EU RUU. The firmware will be EU, no more HKG. You can install any GSM ROM after that, trouble free.
3-I assume that my simUnlock is definitive now, correct ?​Yes it is SIM unlocked, the reason why I don't recommend Australia Optus firmware & ROM so it won't get SIM locked again. The best option is EU as you're in North Africa.
4-You seem to be certain I have superCID, so bootloader info trumps CIDgetter info, but I'm curious, why the value differs between the two ? does the app not report it correctly after changing the value ?​That's what shown on getvar result. No idea about the app. I tried, it can't read my CID as I'm running Nougat ROM. You can try Simple CID Getter to recheck.
But getvar is always correct and the best option.
5-I will be downloading the files from the links you sent me, and doing my homework too but for information's sake, when I boot in bootloader, I have the "locked" banner, but you know that already I also have "software status : official" does it indicate that the Lollipop EU ROM I currently have is a stock signed one ?​Most probably.
If you want to see whether it is stock non-rooted, you change MID to EU then you can accept the OTA and see whether it will be successful to install.
As you have a LOCKED bootloader, you need different method to change the MID .. you need to install a flashable TWRP and do the MID change while in recovery.
But why want to waste time checking, downloading and installing OTA when RUU is available and you can directly update to the latest.
6-My device came rooted but I don't see Superuser installed, I assume I'll have to root it again after the update, correct ?​How do you know that it is currently rooted ? OTA won't work on a rooted ROM.
Yes, you have to root again after each update (when you need a rooted stock ROM). If you want to install custom ROM, no need to root .. only install TWRP and install custom ROM. Custom ROM mostly come pre-rooted.

ckpv5 said:
1-Now that I'm running HK firmware and corresponding MID but EU ROM, you suggested I change to EU MID, but won't that cause issues with firmware being HK ?​You have OS Hong Kong no. which I assume it's HKG firmware but your MID is not HKG but it can be Australia and it can be India. I assume it is Australia as it has 2.5 Ghz and CID OPTUS001 (as you mentioned it)
Change it to EU MID won't cause any issue but a better option as the current ROM on your device is EU 4.16.401.10 and that's why you get notification for OTA to 4.16.401.13
2- If I flash the EU RUU you sent me, I assume the firmware will no longer be HK, correct ? and after that I can just keep to install EU roms and be trouble free​You need to change MID first to EU then install EU RUU. The firmware will be EU, no more HKG. You can install any GSM ROM after that, trouble free.
3-I assume that my simUnlock is definitive now, correct ?​Yes it is SIM unlocked, the reason why I don't recommend Australia Optus firmware & ROM so it won't get SIM locked again. The best option is EU as you're in North Africa.
4-You seem to be certain I have superCID, so bootloader info trumps CIDgetter info, but I'm curious, why the value differs between the two ? does the app not report it correctly after changing the value ?​That's what shown on getvar result. No idea about the app. I tried, it can't read my CID as I'm running Nougat ROM. You can try Simple CID Getter to recheck.
But getvar is always correct and the best option.
5-I will be downloading the files from the links you sent me, and doing my homework too but for information's sake, when I boot in bootloader, I have the "locked" banner, but you know that already I also have "software status : official" does it indicate that the Lollipop EU ROM I currently have is a stock signed one ?​Most probably.
If you want to see whether it is stock non-rooted, you change MID to EU then you can accept the OTA and see whether it will be successful to install.
As you have a LOCKED bootloader, you need different method to change the MID .. you need to install a flashable TWRP and do the MID change while in recovery.
But why want to waste time checking, downloading and installing OTA when RUU is available and you can directly update to the latest.
6-My device came rooted but I don't see Superuser installed, I assume I'll have to root it again after the update, correct ?​How do you know that it is currently rooted ? OTA won't work on a rooted ROM.
Yes, you have to root again after each update (when you need a rooted stock ROM). If you want to install custom ROM, no need to root .. only install TWRP and install custom ROM. Custom ROM mostly come pre-rooted.
Click to expand...
Click to collapse
Alright thanks for reassuring me.
For the CID, with Simple CID Getter I get the same OPTUS_001... no idea why XD
Upon installing CPU-Z to have more information about the device I noticed "root access : yes" so I installed Root checker and indeed it told me I have root access, that's how I knew about it. Well then I don't plan to OTA anymore XD
The first method to change MID that you sent me doesn't work even if I'm S-off ? so I'll need to use this tool ? http://forum.xda-developers.com/showthread.php?t=2779524 if so then the sequence order should be : Unlock bootloader from htcdev, then flashing TWRP like you said here http://forum.xda-developers.com/htc-one-m8/help/unlock-bootloader-install-custom-t3371328 then using the MID changer tool ?
I don't need to revert to stock recovery and locked bootloader before flashiing with RUU ?

ELS28 said:
1. For the CID, with Simple CID Getter I get the same OPTUS_001... no idea why XD
2. The first method to change MID that you sent me doesn't work even if I'm S-off ? so I'll need to use this tool ? http://forum.xda-developers.com/showthread.php?t=2779524 if so then the sequence order should be : Unlock bootloader from htcdev, then flashing TWRP like you said here http://forum.xda-developers.com/htc-one-m8/help/unlock-bootloader-install-custom-t3371328 then using the MID changer tool ?
3. I don't need to revert to stock recovery and locked bootloader before flashiing with RUU ?
Click to expand...
Click to collapse
1. No idea why these app read differently. Just ignore it for now .. that can be fixed later
2. Don't follow those guide .. I'll give you the guide below
3. No need
First - you need to install TWRP.
a- Download the hboot flashable zip here : http://forum.xda-developers.com/showpost.php?p=70210155&postcount=19
b- put it on root of your microsd
c- boot to bootloader then select hboot - it will ask you to update, volume up to update .. let it finish, reboot once completed. Delete/remove the 0P6BIMG.zip from your microsd.
Second - you need to unlock bootloader as it is easier to thing with unlocked bootloader
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796[/B]
exit
reboot to bootloader .. you should see the bootloader is now unlocked.
Third - change MID to EU MID 0P6B10000
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
exit
reboot to bootloader
open a command prompt from your adb/fastboot folder then type
fastboot getvar mid
you should see the MID now read as 0P6B10000
Fourth - your device is ready, you can install RUU as per my earlier guide.
Note : if there is error related to CID ... we'll fix it after you tried the RUU. If the SuperCID is correct, the installation should be fine.
Credit to @scotty1223 for his threads as reference
http://forum.xda-developers.com/showthread.php?t=2708571
http://forum.xda-developers.com/showthread.php?t=2708581

ckpv5 said:
1. No idea why these app read differently. Just ignore it for now .. that can be fixed later
2. Don't follow those guide .. I'll give you the guide below
3. No need
First - you need to install TWRP.
a- Download the hboot flashable zip here : http://forum.xda-developers.com/showpost.php?p=70210155&postcount=19
b- put it on root of your microsd
c- boot to bootloader then select hboot - it will ask you to update, volume up to update .. let it finish, reboot once completed. Delete/remove the 0P6BIMG.zip from your microsd.
Second - you need to unlock bootloader as it is easier to thing with unlocked bootloader
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796[/B]
exit
reboot to bootloader .. you should see the bootloader is now unlocked.
Third - change MID to EU MID 0P6B10000
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
exit
reboot to bootloader
open a command prompt from your adb/fastboot folder then type
fastboot getvar mid
you should see the MID now read as 0P6B10000
Fourth - your device is ready, you can install RUU as per my earlier guide.
Note : if there is error related to CID ... we'll fix it after you tried the RUU. If the SuperCID is correct, the installation should be fine.
Credit to @scotty1223 for his threads as reference
http://forum.xda-developers.com/showthread.php?t=2708571
http://forum.xda-developers.com/showthread.php?t=2708581
Click to expand...
Click to collapse
Thank you for taking up the time to write this guide,
I'm in second step, when I select mount, I have multiple cases to tick, do I untick them all but system or do I leave Cache, Data and microSD ticked with system as well ? sorry super noob question xD

ELS28 said:
Thank you for taking up the time to write this guide,
I'm in second step, when I select mount, I have multiple cases to tick, do I untick them all but system or do I leave Cache, Data and microSD ticked with system as well ? sorry super noob question xD
Click to expand...
Click to collapse
Doesn't matter what already ticked, the important part is mount system (tick) as it is not mounted at default. The rest let them be as what they are when you select mount menu.
I'll check tomorrow your progress .. time to sleep now as it's over 1.30 am here.
Good luck.

ckpv5 said:
Doesn't matter what already ticked, the important part is mount system (tick) as it is not mounted at default. The rest let them be as what they are when you select mount menu.
I'll check tomorrow your progress .. time to sleep now as it's over 1.30 am here.
Good luck.
Click to expand...
Click to collapse
alright thank you and good night
EDIT : I successfully unlocked and changed MID to 0P6B10000 there seems to be no problem at all and the phone is running fine I don't get the red developpement message on boot to OS, only when I boot to recovery, it doesn't really bother me for now. I don't plan to update to MM immediately though, this has been a lot of new manoeuvers to learn in one take plus I want to read more about eventual issues with apps after I update, so I'll be using the current ROM some time before using your guide again and updating. Thank you so much for taking me through this process, I learned a lot

ELS28 said:
I successfully unlocked and changed MID to 0P6B10000 there seems to be no problem at all and the phone is running fine
Click to expand...
Click to collapse
:good::good:

Which RUU can i flash?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Thanks for your contribution, will definitely try tomorrow

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

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

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

Not sure about this M9

Hi there, I bought a htc m9 from ebay uk for use in Ireland.
It seems to work fine no problem. But it is on marshmallow and would like to update it.
OTA system update doesn't work.
I read through the m9 readme here and fastboot getvar gives
D:\Delete\m9\android>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himawl
(bootloader) version: 1.0
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) version-main: 3.37.605.7
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA30000
(bootloader) cid: 11111111
Which to my disappintment, seems to indicate it's a Verizon cdma version (how does it do gsm,4g,lte then ??)
However I am not sure if any of that fastboot info might have been modified (or even if it's possible) in the past sometime. Eg. the cid seems to be incorrect.
The sticker on the back of the phone and on the white box says p/n 99HVJ002-00. Does that match or is consistent with the fastboot info ?
The phone is unlocked and its S-OFF which I can see when boot into download mode.
Also, the phone settings, Boomsound is missing from the options. Has something called 'JBL LiveStage'. Which doesn't seem to do anything and is hardly mentioned anywhere in relation to this device.
So in an effort to restore Boomsound would like to go to a stock firmware.
So how can I confirm 100% this is a Verizon cdma phone ? I don't want to stupidly flash gsm firmware on it or something.
If could restore Boomsound in some other way I 'd probably leave it alone. Factory reset didn't have any effect on it.
thanks,

It's a verizon phone with an audio mod flashed to it.
Now, the problem you have is verizon is cdma and your Irish networks are gsm. Even though the phone can take sim cards there's a chance it won't work on the networks, but it will be a working phone, just only on cdma networks.
You need to change the cid from Supercid 11111111 (no longer valid) to the cid for verizon. Use fastboot on a pc and download mode on the phone.
Then download and flash the stock verizon firmware 3.37.605.x (x can be any number but the rest MUST MATCH EXACTLY). Use the zip version of the ruu and flash from the external sd and rename it to 0PJAIMG.ZIP.
Boot to download mode and you should be prompted to press vol up to flash.. If no prompt then check filename as it could be different. It will tell you in download mode what file it is looking for!.
DO NOT S-ON. DO NOT LOCK/RELOCK THE BOOTLOADER. It is not necessary.
Once flashed the phone is stock. You can then accept the ota updates over WiFi.

Thanks, that worked good. Boomsound is back and sounds really good.
I flashed with the 3.37.605.7 Ruu in download mode which I found here:
https://forum.xda-developers.com/ve...t-unlock-s-verizon-m9-mm-3-37-605-13-t3457717
I didn't change the Supercid 11111111 though. Do I really need to change that back to the default ? If so do you know what's the correct CID for this particular Verizon m9 ?
Also, not too bothered but OTA System Update still doesn't work. Just keeps saying try again when connected to the Verizon 4G Lte Network.
This thread seems to have all the nougat information:
https://forum.xda-developers.com/ve...t/6-0-verizon-htc-one-m9-marshmallow-t3316279
But it's not clear what firmware you need to be up to in order to flash, say, 4.49.605.16_NoBoot-NoRecovery_firmware.zip
thanks a lot

Even if you were connected to the Verizon network you wouldn't be able to receive OTAs. Since the M9 the SuperCID (11111111) prevents HTC's servers from sending the files to your phone.
The correct CID is listed in the RUU section of the ReadMe thread.
Sent from my HTC One M9 using XDA Labs