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

No Support by Sunshine!

If Sunshine is the only way to achieve S-OFF, But my device isn't supported does this mean i just have to cry about my S-ON One M8?

If you are that disappointed then yes cry all you like ! If that's a disappointment you will cry about i wonder what you will do when you get a real disappointment in life ?!
They are working on a update maybe that will cheer you up

Araytha said:
If Sunshine is the only way to achieve S-OFF, But my device isn't supported does this mean i just have to cry about my S-ON One M8?
Click to expand...
Click to collapse
Just so you know, The HTC One M7 was out for nearly 6 months without S-Off and it never stopped the developers form creating dozens of Roms and the development of the phone went on without any problems. All S-Off is really needed for is converting a phone to a different branding or carrier. Or to downgrade firmware. In most cases the phone will function and update just fine without s-off. All you need is an unlocked bootloader and custom recovery to enjoy most of the custom roms available to this device.

clsA said:
Just so you know, The HTC One M7 was out for nearly 6 months without S-Off and it never stopped the developers form creating dozens of Roms and the development of the phone went on without any problems. All S-Off is really needed for is converting a phone to a different branding or carrier. Or to downgrade firmware. In most cases the phone will function and update just fine without s-off. All you need is an unlocked bootloader and custom recovery to enjoy most of the custom roms available to this device.
Click to expand...
Click to collapse
That was the main thing I needed, a new carrier. I'm sure it will happen eventually for my version just a matter of waiting for it!
already unlocked bootloader with custom recovery, running SlimKat atm, just the carrier issue.

Araytha said:
That was the main thing I needed, a new carrier. I'm sure it will happen eventually for my version just a matter of waiting for it!
already unlocked bootloader with custom recovery, running SlimKat atm, just the carrier issue.
Click to expand...
Click to collapse
What is the phone not doing on your current carrier that you think a firmware / CID MID change will fix ?

Maybe he means SIM unlock it ?

clsA said:
What is the phone not doing on your current carrier that you think a firmware / CID MID change will fix ?
Click to expand...
Click to collapse
Not updating fast enough and he rather wants an unlocked WWE International, WWE Asia, Developer Edition for faster updates? :cyclops:

Mr Hofs said:
Maybe he means SIM unlock it ?
Click to expand...
Click to collapse
Exactly what I want, but also just want a fully unblocked M8. Prefer to have no restrictions what so ever.

Araytha said:
Exactly what I want, but also just want a fully unblocked M8. Prefer to have no restrictions what so ever.
Click to expand...
Click to collapse
I have the Sim unlocked Developers Edition so I'm not sure whats needed for that. But yeah S-Off is nice even at $25. I hope they get it updated for you soon.

clsA said:
I have the Sim unlocked Developers Edition so I'm not sure whats needed for that. But yeah S-Off is nice even at $25. I hope they get it updated for you soon.
Click to expand...
Click to collapse
Definitely worth it. No Issues paying for s-off. Hope they are working hard lay

I don't know what you're talking about that it won't work? FYI I'm running Viper Rom 3.2.1 and my device is supported. Or did you mean that you already bought the license and your phone says that it's still s-on?
Sent from my HTC One_M8

talpes said:
I don't know what you're talking about that it won't work? FYI I'm running Viper Rom 3.2.1 and my device is supported. Or did you mean that you already bought the license and your phone says that it's still s-on?
Sent from my HTC One_M8
Click to expand...
Click to collapse
If you would have stopped at "I don't know what you're talking about", you would have been correct.

talpes said:
I don't know what you're talking about that it won't work? FYI I'm running Viper Rom 3.2.1 and my device is supported. Or did you mean that you already bought the license and your phone says that it's still s-on?
Sent from my HTC One_M8
Click to expand...
Click to collapse
I don't get to that, it does testing and says that it won't work on my device thus won't let me in app purchase or enter a code.

Araytha said:
I don't get to that, it does testing and says that it won't work on my device thus won't let me in app purchase or enter a code.
Click to expand...
Click to collapse
Flash ARHD or Maximus then try it.

xunholyx said:
If you would have stopped at "I don't know what you're talking about", you would have been correct.
Click to expand...
Click to collapse
Thanks for correcting me, English isn't even my native language and I translated it from German so maybe that was my mistake

jsho31 said:
Flash ARHD or Maximus then try it.
Click to expand...
Click to collapse
ARHD Still brings the same issue. It might be how new my phone is?
Fastboot GetVar All:
Code:
(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.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4XXXXXXXXX
(bootloader) imei: 35733XXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
help at all?

If all you desperately need sim unlock, and you're going to have to pay anyways, have you checked the usual sim unlock services? Most of those only cost like $10-15 and you'd get to switch carriers while you're waiting for sunshine to update.
With that and the right kernel/rom combo you'd get most of what s-off gets you anyways, with the exception of downgrading firmware, etc. but really how often are you going to do that? Just something to consider I suppose.

gokun said:
If all you desperately need sim unlock, and you're going to have to pay anyways, have you checked the usual sim unlock services? Most of those only cost like $10-15 and you'd get to switch carriers while you're waiting for sunshine to update.
With that and the right kernel/rom combo you'd get most of what s-off gets you anyways, with the exception of downgrading firmware, etc. but really how often are you going to do that? Just something to consider I suppose.
Click to expand...
Click to collapse
Incorrect. You can't flash new firmware unless your MID and CID match the new version. With S-Off, you can always be on top of the new firmware from any carrier. (unless you are on Sprint or Verizon). For instance, AT&T is still on the old stuff. With S-Off, AT&T users can be on the newest 4.4.4
Also, I was on 4.4.4 (telus in canada) two months before my carrier updated. S-Off gives you full freedom.
Also, S-Off and SIM unlock are two totally separate things. So there is also that.

gokun said:
If all you desperately need sim unlock, and you're going to have to pay anyways, have you checked the usual sim unlock services? Most of those only cost like $10-15 and you'd get to switch carriers while you're waiting for sunshine to update.
With that and the right kernel/rom combo you'd get most of what s-off gets you anyways, with the exception of downgrading firmware, etc. but really how often are you going to do that? Just something to consider I suppose.
Click to expand...
Click to collapse
Three services have said they can't get an unlock code for my M8... Can an M8 be HardLocked like a Sony M2? Does anyone know where I might find the unlock counter is present on HTC?

xunholyx said:
Incorrect. You can't flash new firmware unless your MID and CID match the new version. With S-Off, you can always be on top of the new firmware from any carrier. (unless you are on Sprint or Verizon). For instance, AT&T is still on the old stuff. With S-Off, AT&T users can be on the newest 4.4.4
Click to expand...
Click to collapse
That's what I said though..."with the exception of downgrading firmware, etc" meaning you can't do that. So, I'm just saying, I wasn't incorrect. (but your post was still informative and helpful to many people I'm sure).
---------- Post added at 01:45 AM ---------- Previous post was at 01:42 AM ----------
Araytha said:
Three services have said they can't get an unlock code for my M8... Can an M8 be HardLocked like a Sony M2? Does anyone know where I might find the unlock counter is present on HTC?
Click to expand...
Click to collapse
Most likely your phone just isn't in their databases yet. I ran into that exact same thing when I had my OneX+. It's basically just a waiting game until they get the new databases that have your code in them. Back when I had my X+ it took about 2-3 weeks before anyone got the newest databases. It sucks, but all you can really do at that point is just wait. Which, again, definitely sucks.

[Q] SkyDragon 5.0.1 firmware

Hi all,
Currently I'm running Viper 1.8.0 ( Android 4.4.2 ) as you can see I'm behind my update schedule.
I'd love to give LP a try but in the SkyDragon thread I can see that i should check my firmware before upgrading to ensure WiFi is working.
Now the problem is that when i want to check my firmware there are no numbers so I have no clue what to update to.
Could anyone push me into the right direction to ensure a smooth upgrade ?
Other specs when booting into bootloader
- Tampered
- Unlocked
- M8_UL
- S-ON
- OS- [ This line is empty ]

Its a bit confusing, but OS or software number will actually not tell you the firmware number. The OS numbers will just tell you what software build the ROM was based off of, and will change if you flash the ROM.
To check firmware, look at hboot and radio number and post those here.
But essentially:
hboot 3.16 = 1.x firmware
hboot 3.17 = 2.x firmware
hboot 3.19 = 3.x firmware; and also 4.x (not many of those have OTA'ed yet)

Hi, excuse me for my late response.
My HBoot is 3.16. Beneath is an output of
Code:
fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Actually i frankly do not mind what rom I should take next as long as its a 'stable' 5.0.x version.
Also right now I'm still running Venom 1.8.0 on 4.4.2.
I read about sunshine and S-OFF the device but I was thinking about reverting to stock and OTA updating.
Or should I proceed otherwise.
Thanks in advance !

Wickedd said:
Actually i frankly do not mind what rom I should take next as long as its a 'stable' 5.0.x version.
Also right now I'm still running Venom 1.8.0 on 4.4.2.
I read about sunshine and S-OFF the device but I was thinking about reverting to stock and OTA updating.
Or should I proceed otherwise.
Click to expand...
Click to collapse
If you want to run Lollipop Sense, you need Lollipop firmware. Has Lollipop OTA started rolling out for your version yet? Far as I know, only the Dev Edition have gotten it, in addition to some Euro versions (just started rolling out yesterday).
If your version hasn't gotten the LP OTA yet, you either need to wait or s-off and update the firmware "manually".

redpoint73 said:
If you want to run Lollipop Sense, you need Lollipop firmware. Has Lollipop OTA started rolling out for your version yet? Far as I know, only the Dev Edition have gotten it, in addition to some Euro versions (just started rolling out yesterday).
If your version hasn't gotten the LP OTA yet, you either need to wait or s-off and update the firmware "manually".
Click to expand...
Click to collapse
And what if I dont care about Sense, would i be update without changing my firmware ?
Also the only 'working' method I read about is Sunshine or does firewater still work ? I'm a bit careful because of the risks involved.
Any idea what would be my next step ? And what ROM should I keep as a backup, since I dont have a copy of Venom 1.8.0
Thanks in advance,
- Wickedd

Or would I be able to grab a 'factory' ROM for my device and let it update OTA, at least so I'm off my current ROM.

Wickedd said:
And what if I dont care about Sense, would i be update without changing my firmware ?
Click to expand...
Click to collapse
If the intent is to install Skydragon GPE, you need 4.4.4 firmware, as it states right in Post #2 of the Skydragon thread.
Your current firmware is very old. There aren't many (if any) current ROMs that it will support. You need to update firmware one way or another.
Wickedd said:
Also the only 'working' method I read about is Sunshine or does firewater still work ? I'm a bit careful because of the risks involved.
Click to expand...
Click to collapse
Sunshine is the only way to s-off. Firewater was discontinued in December.
---------- Post added at 11:30 AM ---------- Previous post was at 11:28 AM ----------
Wickedd said:
Or would I be able to grab a 'factory' ROM for my device and let it update OTA, at least so I'm off my current ROM.
Click to expand...
Click to collapse
Yes, this will get you on whatever current firmware your carrier version has had released.
You need the stock ROM and the stock recovery for your CID, in order for OTA to install. Root and unlocked bootloader are okay to OTA.

Thanks again for your help, When i check this thread I can't seem to find any numbers matching mine. So what image and recovery am I going to flash ?
http://forum.xda-developers.com/showpost.php?p=58606328&postcount=4278
Also : Firewater is discontinued in December, but my rom is in a state way before that. A reason to get my hopes up ? Also any risk in trying ?
Thanks in advance

Wickedd said:
When i check this thread I can't seem to find any numbers matching mine. So what image and recovery am I going to flash ?
Click to expand...
Click to collapse
hboot 3.16 means you are on 1.x firmware (and 1.x software before you flashed custom ROM). Which one from there is anyone's guess (1.12 or 1.54). I'd guess to try the more recent 1.x ROM, or 1.54.161.10.
Wickedd said:
Also : Firewater is discontinued in December, but my rom is in a state way before that. A reason to get my hopes up ? Also any risk in trying ?
Click to expand...
Click to collapse
Nope, absolutely no reason to get your hopes up. Firewater was an online service, so it will not work anymore.
When I said it was discontinued, I meant it. If there was a reason to think it would work, I would have said so.
Wickedd said:
Thanks again for your help,
Click to expand...
Click to collapse
There's a button for that.

How can I confirm this ? The only one I found was 1.54.401.5 as build number That'd be my firmware ?
Oh but the stock ROM doesn't have to match my current build number, so with 1.54.161.10 for VODAP102 i'd be good right ?

[Q] Wondering...

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

No does not work.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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!