Develop Bugs

[Q] Need to convert AT&T M8 into Tmobile M8

I have never gotten my MMS to work on my Unlocked AT&T HTC One M8. I recently read that this is a problem because I'm not using a Tmobile branded M8, and that if I updated to a Tmobile ROM it would fix my MMS issues.
http://support.t-mobile.com/thread/66514
I have a solution that will work however I offer this with no-warranty and for a use at your own risk, however I can say I have done this for maybe about 60 T-Mobile customers who brought their HTC One m7 from AT&T. I have done this as well. HTC m7 phone are all built with the exact same parts, the only thing that makes the phone operate differently is the firmware for the baseband, and of course the rom. However HTC offer's a RUU (Rom Upgrade Utility) right on their support page. This reinstalls the android os, along with new baseband and firmware versions. All you have to do is run the T-Mobile HTC One m7 RUU that is on the HTC website. You can use the link here to download the RUU from the HTC website. It generally about 1GB in file size, as this is not just the Android OS, but this is the software for the phone's hardware to flash it from an AT&T HTC One to a T-Mobile HTC One.This will also enable your phone to receive Over-The-Air updates from T-Mobile as well. Again I and T-Mobile will not support this. However I can say from personal experience and also on behalf of the people I done this for that it works. *Also you will get to enjoy the T-Mobile Wi-Fi Calling as well. Your phone will act and perform just like the T-Mobile version will after this. After all they all have the exact same parts under the hood. Just different firmware, and operating systems. This converts it all over to T-Mobile
Click to expand...
Click to collapse
Relevant Info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I have since rooted my device, unlocked the bootloader, done S-OFF, and set CID to SuperCid.
I just wan't to confirm that I'm doing the right thing so I don't end up bricking my phone.
Do I need to change the MID or CID of my device?
Do I need to update through RUU to a Tmobile ROM in order to make make all the relevant firmware changes to convert my M8 into a Tmobile branded phone rather than AT&T or can I just flash through the the Recovery and flash a Tmobile ROM?
My understanding is that reinstalling the Tmobile ROM will keep S-OFF, SuperCid, and Unlocked Bootloader, but will NOT keep Root. Is this correct? Will it keep my custom recovery?
Sorry for all the questions. Thank you for your time!

NiklasK said:
I have never gotten my MMS to work on my Unlocked AT&T HTC One M8. I recently read that this is a problem because I'm not using a Tmobile branded M8, and that if I updated to a Tmobile ROM it would fix my MMS issues.
http://support.t-mobile.com/thread/66514
Relevant Info:
I have since rooted my device, unlocked the bootloader, done S-OFF, and set CID to SuperCid.
I just wan't to confirm that I'm doing the right thing so I don't end up bricking my phone.
Do I need to change the MID or CID of my device?
Do I need to update through RUU to a Tmobile ROM in order to make make all the relevant firmware changes to convert my M8 into a Tmobile branded phone rather than AT&T or can I just flash through the the Recovery and flash a Tmobile ROM?
My understanding is that reinstalling the Tmobile ROM will keep S-OFF, SuperCid, and Unlocked Bootloader, but will NOT keep Root. Is this correct? Will it keep my custom recovery?
Sorry for all the questions. Thank you for your time!
Click to expand...
Click to collapse
The information you quoted is incorrect. The AT&T and T-Mobile versions are two different hardware versions. AT&T M8 being m8_ul_ca and T-Mobile being m8_ul. They do not have the same network compatibility.
At&t - 0P6B1200 supported bands (in MHz):
3G=850, 1900, 2100
LTE=700, 850, 1700, 1800, 1900, 2100, 2600
T-Mobile - 0P6B1300 supported bands:
3G=850, 1700, 1900, 2100
LTE=700, 1700, 2100
As you can see, T-mobile has an extra HSPA band that AT&T doesn't support. This is also why the AT&T model does not support 42.2Mb per second HSPA+ downloads while the T Mobile version does. AT&T maxes out at 21.1Mb over HSPA. You'll also note that the AT&T version supports more LTE bands, however, those are bands that T-Mobile does not operate it's LTE network on so really it doesn't help. Long story short the devices are actually not the same.
Now, you can still operate an AT&T model on T-Mobile's network with a large degree of success depending on your coverage area and what network bands are currently being utilized. The 700MHz band has not been switched on everywhere for T-Mobile just yet so you would be limited to only two bands of LTE support.
All that being said, if you do flash a T-Mobile RUU, you will have wifi calling support you will have the correct device and network settings for T-Mobile, including MMS, and you may notice little to no loss of network performance on your device, however, you may notice significant loss of performance. It depends solely on the network in your area. After flashing a RUU, you will have the T-Mobile software & firmware as well as maintain your s-off status, but you will not effect supported network bands. Also, if you want to receive OTA updates you will need to change your model ID aka MID.

Behold_this said:
All that being said, if you do flash a T-Mobile RUU, you will have wifi calling support you will have the correct device and network settings for T-Mobile, including MMS, and you may notice little to no loss of network performance on your device, however, you may notice significant loss of performance. It depends solely on the network in your area. After flashing a RUU, you will have the T-Mobile software & firmware as well as maintain your s-off status, but you will not effect supported network bands. Also, if you want to receive OTA updates you will need to change your model ID aka MID.
Click to expand...
Click to collapse
Ok I understand. I wasn't aware that the AT&T model didn't go up to the same data rates as the Tmobile one. The only reason I bought the AT&T one was because I liked the color better
So as far as using the T-Mobile RUU, I'm set and don't need to make any further adjustments (ex: MID, CID, Bootloader Lock, or S-Off)?
If I want to receive OTA updates from tmobile after changing the MID do I need to get S-Off or relock the bootloader or change CID?

NiklasK said:
Ok I understand. I wasn't aware that the AT&T model didn't go up to the same data rates as the Tmobile one. The only reason I bought the AT&T one was because I liked the color better
So as far as using the T-Mobile RUU, I'm set and don't need to make any further adjustments (ex: MID, CID, Bootloader Lock, or S-Off)?
If I want to receive OTA updates from tmobile after changing the MID do I need to get S-Off or relock the bootloader or change CID?
Click to expand...
Click to collapse
You need to change your MID [how to] change your MID without an eng bootloader and then run the RUU. I don't think changing the CID is necessary but you can do that too if you want.
Once you're S-OFF you don't ever have to relock the bootloader for anything. Just leave it unlocked.
If you don't want to do RUU then just restore a stock T-Mobile nandroid, preferably an earlier version. That way you can see if your device does the OTA updates like it's supposed too. For me, I don't know if anyone else had the problem, I had to flash the first OTA manually and then the device did the rest automatically. This was with a conversion from International to Developer Edition.

So as far as Im reading I need to LOCK my bootloader in order to use the Tmobile RUU. Yet you say I just need to change my MID. Can you confirm that the RUU will still work on an unlocked bootloader?
Would I still need to change my MID if I just used Recovery to flash a Tmobile ROM?
EDIT:
Just changed my MID to 0P6B13000 (Tmobile USA)
Am I all good to go now to use the RUU without bricking?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse

NiklasK said:
So as far as Im reading I need to LOCK my bootloader in order to use the Tmobile RUU. Yet you say I just need to change my MID. Can you confirm that the RUU will still work on an unlocked bootloader?
Would I still need to change my MID if I just used Recovery to flash a Tmobile ROM?
EDIT:
Just changed my MID to 0P6B13000 (Tmobile USA)
Am I all good to go now to use the RUU without bricking?
Click to expand...
Click to collapse
Yeah go for it. Shouldn't brick unless unforeseen connection issue with your PC.
*edit
Also keep in mind only HSPA+ speeds will be affected. If you are in an area with T-Mobile LTE support, speeds will not be affected. So you may be lucky and have no issues whatsoever.

Behold_this said:
Yeah go for it. Shouldn't brick unless unforeseen connection issue with your PC.
*edit
Also keep in mind only HSPA+ speeds will be affected. If you are in an area with T-Mobile LTE support, speeds will not be affected. So you may be lucky and have no issues whatsoever.
Click to expand...
Click to collapse
My area is predominately LTE =]
So I just downloaded this TMOUS-M8-3.32.531.2-Stock-TWRP.zip
However, I found this in a thread on xda:
3.16 hboot = 1.12 / 1.54 software
3.18 hboot = 2.22 software
3.19 hboot = 3.xx software
Click to expand...
Click to collapse
Since my hboot currently is 3.16 does that mean I can only flash 1.12/1.54? And not the 3.32.531.2 I downloaded since it corresponds to 3.19 hboot?

NiklasK said:
My area is predominately LTE =]
So I just downloaded this TMOUS-M8-3.32.531.2-Stock-TWRP.zip
However, I found this in a thread on xda:
Since my hboot currently is 3.16 does that mean I can only flash 1.12/1.54? And not the 3.32.531.2 I downloaded since it corresponds to 3.19 hboot?
Click to expand...
Click to collapse
Personally I would just flash the T -Mobile 3.32 RUU and be done with it
http://dl3.htc.com/application/RUU_...G_20.56.4198.02_F_release_394971_signed_2.exe
*edit
Well maybe not done with it, I'd still flash supersu, rw mod or custom kernel, and remove the bloat, but I think you get what I mean.

Behold_this said:
Personally I would just flash the T -Mobile 3.32 RUU and be done with it
http://dl3.htc.com/application/RUU_...G_20.56.4198.02_F_release_394971_signed_2.exe
*edit
Well maybe not done with it, I'd still flash supersu, rw mod or custom kernel, and remove the bloat, but I think you get what I mean.
Click to expand...
Click to collapse
Having so much trouble getting the RUU Installer to work. Tried it on 2 different Windows computers (8.1 and 7) with the installer always exiting. Does the RUU do anything special that flashing through cmd prompt or recoveries wont do? At this point I'd much rather do that.

NiklasK said:
Having so much trouble getting the RUU Installer to work. Tried it on 2 different Windows computers (8.1 and 7) with the installer always exiting. Does the RUU do anything special that flashing through cmd prompt or recoveries wont do? At this point I'd much rather do that.
Click to expand...
Click to collapse
Like I said previously, I'd personally go for an older version first. That way you can test to make sure the conversion is 100% by letting the device do the OTA updates. What's the point of converting straight to the latest version and leaving yourself unsure whether OTA will work once Lollipop comes out?
I'd go for one of the 1.xx.xxx.x versions and update it to the latest, but that's me...Just a thought/suggestion.

BerndM14 said:
Like I said previously, I'd personally go for an older version first. That way you can test to make sure the conversion is 100% by letting the device do the OTA updates. What's the point of converting straight to the latest version and leaving yourself unsure whether OTA will work once Lollipop comes out?
I'd go for one of the 1.xx.xxx.x versions and update it to the latest, but that's me...Just a thought/suggestion.
Click to expand...
Click to collapse
My apologies, I wasn't totally clear with my intentions. I just wanted to flash the stock latest ROM from T-mobile that I knew would fix my MMS issue. Then I would make a backup of that so I could always recover my phone to that point. I was always going to flash custom ROMs based off Tmobile base firmware, just wanted to have a fallback backup.

NiklasK said:
My apologies, I wasn't totally clear with my intentions. I just wanted to flash the stock latest ROM from T-mobile that I knew would fix my MMS issue. Then I would make a backup of that so I could always recover my phone to that point. I was always going to flash custom ROMs based off Tmobile base firmware, just wanted to have a fallback backup.
Click to expand...
Click to collapse
I know what the intention is, I'm just stating what I personally would have done. Like I said before, when I converted to Dev Edition I had to manually install the OTA and flash the firmware twice before my device picked up the newest OTA updates and installed it automatically. Don't know why this is...Which is why I personally go back at least 2 or so versions prior to the latest version available to test and make sure that my device can do the OTA updates. You don't have to do this, just figured it would be good to know all is in working order for when 5.0 launches, else you'd probably have to install/flash manually OR go back a version in order for it to update automatically. It's fine either way I suppose, no "biggie".
RUU is the easiest way to do it but you can also just head over to the collection thread, download the latest nandroid backup from there and restore it in TWRP. Then head over to the update thread you'll find a collection of OTA.zip files. Download the one for T-Mobile and install it. You can also extract the firmware.zip from the OTA.zip and flash that in RUU mode(Twice flash) just to make sure the firmware is all in place.
You'll also then have a downloaded backup for nandroid(2.22.531.5) and you'll also have the stock recovery(Which is available in the firmware.zip file) for future references.
Collection for stock nandroid backups Latest nandroid for x.xx.531.x T-Mobile is 2.22.531.5 So you'll have to do OTA's anyways if you want that one.
OTA Zip collection Yours will be under "branded"
Afterwards you can just flash custom recovery and make a nandroid backup of 3.32.531.x for T-Mobile then you're set. You don't have to worry about making a backup of stock recovery as it is in the firmware.zip file like previously mentioned.
All that said, like mentioned before, RUU is probably the easiest way. Try an older version, should be available in the T-Mobile section.
http://forum.xda-developers.com/tmobile-htc-one-m8

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 figure out if M8 is US or EU model

Hello all,
I just got a refurbished M8 from China and after many hours reading tons of documents I am still struggling to figure out if it is a EU model as advertised or a US one.
On the back of the phone it says Model 0P6B100 but the MID (0P6B120), the model string M8_UL_CA and probably more important the IMEI point to an AT&T version. Now the OS/firmware seems to be the stock EU one (version 3.28.401.6), there is no AT&T logo or app anywhere.
Since you can pretty much change everything in software I'm not sure which of the above information I can really trust.
Is there any way to tell for sure if the device is EU or US?
If it is US is it by design limited to the US 4G bands or will using an EU firmware make it use all the EU bands?
I can post the full bootloader information if it helps.
Edit:
Forgot to mention: the CID came set to 11111111
Thanks

My responses below in red font:
Gnondpom said:
On the back of the phone it says Model 0P6B100
This means little. We've seen a lot of M8 devices that have had their back covers replaced; usually to remove the US carrier logos - which reinforces the notion that it was originally ATT. Its what is inside the phone that matters, so we need to go by the getvar data.
but the MID (0P6B120), the model string M8_UL_CA and probably more important the IMEI point to an AT&T version. Now the OS/firmware seems to be the stock EU one (version 3.28.401.6), there is no AT&T logo or app anywhere.
MID number is easy to change with s-off, but the product ID (M8_UL_CA) I've never seen changed, and is reliable to go by.
Likewise, OS number is easy to change with s-off. First can you confirm where you got the OS number, is it from the bootloader screen (which is the correct place to get it)? If so, former owner or the reseller probably flashed Euro 401 firmware/software in order to "convert" it to Euro, and remove all ATT branding, give it the proper Euro band support, etc.
Since you can pretty much change everything in software I'm not sure which of the above information I can really trust.
True that CID, MID and OS number can be changed. But as mentioned, I've never seen the product ID (M8_UL_CA in this case) changed. So that should be reliable to go by, making it the ATT version, or much less likely the US Developer's Edition.
Is there any way to tell for sure if the device is EU or US?
If it is US is it by design limited to the US 4G bands or will using an EU firmware make it use all the EU bands?
If the OS number you gave was taken from the bootloader screen, its already had Euro firmware flashed. Does it work on your carrier's LTE network currently?
I can post the full bootloader information if it helps. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial numer before posting). But I'm pretty sure this is an ATT version that has been modified, and back cover replaced.
Is the phone s-off?
Click to expand...
Click to collapse

Thanks, I suspected that phone to be a US model with EU firmware.
Here's the getvars output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.7
(bootloader) version-misc: PVT SHIP S-OFF
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Note about version-main: the phone came with 3.28.401.6 (same in bootloader and information from phone) but it refused to install OTA updates so I flashed a stock 3.28.401.7 after changing CID and MID to EU values. This allowed OTA to process all the way up to Lollipop and this is where problems started: the Apps store decided that the device is not compatibe with applications which I was able to install on KK without problems and the MM OTA does not show up when I check for updates.
I just got my nano SIM and initial tests shows the phone connecting to 4G but I have no clue which band it uses (any way to check???)... it also switches back and forth between 3G and 4G a bit too much for me but I am in a rural area so it might be normal. I will have to do some side by side comparison with my wife's Wiko which I know to be working fine.
Right now I'm in the middle of bringing the phone back into the state I received it, just have to flash to 3.28.401.6 firmware. Or would it make more sense to get a stock MM right away (I don't care about the data)?

Gnondpom said:
Note about version-main: the phone came with 3.28.401.6 (same in bootloader and information from phone) but it refused to install OTA updates so I flashed a stock 3.28.401.7 after changing CID and MID to EU values. This allowed OTA to process all the way up to Lollipop
Click to expand...
Click to collapse
Something is strange here. The MID isn't for Euro version now. It should be 0P6B10000.
And the fact its not, should prevent the Euro OTA from installing (possibly even from giving the update notification and downloading).
Further, if you did OTA update to Euro Lollipop, the main version would say 4.16.401.10 (or .13).
Something doesn't add up here. I think you did something wrong, or may have some of the steps confused.
Gnondpom said:
I just got my nano SIM and initial tests shows the phone connecting to 4G but I have no clue which band it uses (any way to check???)...
Click to expand...
Click to collapse
It would probably make the most sense to find out what LTE band(s) your carrier uses. From there, I can see if your firmware version supports that band(s).
Gnondpom said:
Right now I'm in the middle of bringing the phone back into the state I received it, just have to flash to 3.28.401.6 firmware. Or would it make more sense to get a stock MM right away (I don't care about the data)?
Click to expand...
Click to collapse
My recommendation would be to properly change to the Euro MID using this guide (is this how you changed the MID before?): http://forum.xda-developers.com/showthread.php?t=2708581
Then RUU to Marshmallow using this post: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
RUU will wipe the phone. But as you said, you don't care about that. And since you are having other issue (with Play store), the RUU may fix that.
RUU is a complete stock Euro image; re-writes every partition. Nice clean install, and the best way to update (as long as you don't mind the phone being wiped).

redpoint73 said:
Something is strange here. The MID isn't for Euro version now. It should be 0P6B10000.
Click to expand...
Click to collapse
This is because I started to bring the phone back to the weird "China config" having the AT&T MID with an Euro FW.
To get the OTA to work I did set it to 0P6B10000 with a CID of HTC__203 but seems there is an additional check somewhere which disabled the MM upgrade from showing up.
redpoint73 said:
Further, if you did OTA update to Euro Lollipop, the main version would say 4.16.401.10 (or .13).
Click to expand...
Click to collapse
Right, but as said I reverted back to KK for now due to the store issues in Lollipop.
redpoint73 said:
It would probably make the most sense to find out what LTE band(s) your carrier uses. From there, I can see if your firmware version supports that band(s).
Click to expand...
Click to collapse
700, 1800 and 2600 Mhz
Does your statement imply that the EU and US versions use the same hardware and that the used frequencies only dependent on the installed firmware?
Because at the end it all boils down to: can I use the phone reasonably well in Europe or should I ask for an exchange / refund.
redpoint73 said:
My recommendation would be to properly change to the Euro MID using this guide (is this how you changed the MID before?): http://forum.xda-developers.com/showthread.php?t=2708581
Click to expand...
Click to collapse
Didn't use that guide but the same method
Do I need to change the CID as well to flash the RUU or can I leave it as is?
redpoint73 said:
Then RUU to Marshmallow using this post: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Ok, I will give it a try as soon as possible (likely over the week-end) and report back.

Gnondpom said:
This is because I started to bring the phone back to the weird "China config" having the AT&T MID with an Euro FW.
Click to expand...
Click to collapse
You should always describe all the exact steps, and what you have done to the device (in detail, be specific), in order for folks to help you. Otherwise, its really confusing. You want to make it easier for folks to help you, not harder!
Gnondpom said:
To get the OTA to work I did set it to 0P6B10000 with a CID of HTC__203 but seems there is an additional check somewhere which disabled the MM upgrade from showing up.
Click to expand...
Click to collapse
I've never seen such a check, and don't believe this assumption is correct. There are lots of glitches that can happen in the system, that can prevent an OTA. That is likely what happened.
Gnondpom said:
Right, but as said I reverted back to KK for now due to the store issues in Lollipop.
Click to expand...
Click to collapse
You did not state such a thing. The only mention I see of such a thing is the following:
Gnondpom said:
This allowed OTA to process all the way up to Lollipop and this is where problems started: the Apps store decided that the device is not compatibe with applications which I was able to install on KK without problems and the MM OTA does not show up when I check for updates.
Click to expand...
Click to collapse
Which to me does not say you downgraded to KK. And even if you said so, you'd have to be specific that you downgraded both the firmware and OS (by RUU? Or by flashing firmware.zip and a Kitkat TWRP backup?). Again, I'm just saying you should always try to provide the proper and complete details about what you have done, in order for us to help you. Otherwise, its confusing and makes it harder for us to help you. Already wasted time trying to figure out what you did, and asking you about it.
Gnondpom said:
Does your statement imply that the EU and US versions use the same hardware and that the used frequencies only dependent on the installed firmware?
Click to expand...
Click to collapse
That is correct. The hardware is the same in this case (ATT and EU) and the band support is set in radio baseband firmware. Meaning, if you have a Euro radio firmware installed, it should support the bands specified for the Euro version.
Gnondpom said:
700, 1800 and 2600 Mhz
Click to expand...
Click to collapse
Based on the specs here, the Euro firmware does not support LTE 700 MHz.
You may have better results with the Asia radio firmware, which supports all the LTE bands you stated. But that would be assuming its the 700 MHz LTE band that is being used in your area, and the missing support is what is causing the problem (which may or may not be true).
Gnondpom said:
Because at the end it all boils down to: can I use the phone reasonably well in Europe or should I ask for an exchange / refund.
Click to expand...
Click to collapse
Hard to say for certain, but again, you may flash the Asia radio, and see if that helps.
Gnondpom said:
Do I need to change the CID as well to flash the RUU or can I leave it as is?
Click to expand...
Click to collapse
SuperCID 11111111 is fine. SuperCID basically "passes" any CID check by the RUUs and OTAs, that is what makes it super!

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.