Develop Bugs

[Q] Canada Rogers M8 RUU

Hi,
I know Rogers doesn't have an RUU for the M8, but when I had my M7, I was using an RUU that was for Brightstar (decrypted) and it worked great. It turned my M7 into a WWE Dev Edition with Sense and the OTAs worked. All i had to do was change my CID to BS_US001 and RUU away. I needed to install a LOT of OTAs afterwards but who doesn't like updating, right?!
Would anyone know what RUU I could use on my Rogers M8 that would be the equivalent of that? Doesn't need to be rogers specific, it could be a world wide edition, I'd bu happy with that. I think that AT&T is the US carrier that uses the same type of network so I'm not sure if there is an AT&T RUU out there. Searched XDA and Google and I haven't found an RUU that I am confident would work.
Thank you.

This is the closest thing I could find and it looks like it could work, but it's an EXE RUU, I've never used that before.
http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777

Nic2112 said:
This is the closest thing I could find and it looks like it could work, but it's an EXE RUU, I've never used that before.
http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
Click to expand...
Click to collapse
All "official" RUUs are released as Windows .exe files. If you used something else before (RUU that was not an .exe), it was modified by a XDA user.
---------- Post added at 10:25 AM ---------- Previous post was at 10:18 AM ----------
Nic2112 said:
I think that AT&T is the US carrier that uses the same type of network so I'm not sure if there is an AT&T RUU out there. Searched XDA and Google and I haven't found an RUU that I am confident would work.
Click to expand...
Click to collapse
Latest AT&T RUU:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Modified bootable (no PC required) version:
http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
I think you are right, that Rogers uses a similar or same network to AT&T. Rogers was in fact partially owned by AT&T at one point. But you should confirm the network is the same. Be aware that the radio is included on the RUU, so if there are any network differences, using the wrong RUU can impact reception.
In particular, the international WWE firmware/radio is known to not work well in North America. Although you won't find an RUU for WWE anyway. For the most part, only US carriers have RUUs.
Other than that, the RUUs I linked are fine. You will need to change CID (or s-off may be necessary) otherwise it will install fine. Hardware on all GSM M8s (but not CDMA versions) are essentially the same aside from some cosmetic differences. The RUU you posted is also fine, as the US Dev Edition is designed to support AT&T's network (and likely also Rogers).
EDIT: Fixed the link to bootlable RUU above.

redpoint73 said:
Other than that, the RUUs I linked are fine. You will need to change CID (or s-off may be necessary) otherwise it will install fine. Hardware on all GSM M8s (but not CDMA versions) are essentially the same aside from some cosmetic differences. The RUU you posted is also fine, as the US Dev Edition is designed to support AT&T's network (and likely also Rogers).
Click to expand...
Click to collapse
That is great information, thank you very much. I'm S-OFF with GOOGL001 as CID, all I need to do is change it to one that matches the text file in the RUU, or I think BS_US001 will work.
Thanks again!

redpoint73 said:
Latest AT&T RUU:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Modified bootable (no PC required) version:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Click to expand...
Click to collapse
Did you mean to link to the same file twice?

Interesting, I have 3 EXE RUUs and they all have the same behavior, I click them ,the installer starts, I accept the agreement, and then it closes completely.

I would like to know the outcome as well. I did the GPE conversion and now want to go back to stock Rogers or the Developers Edition Sense but can't find a Rogers RUU and the Dev one is an exe.
Sent from my HTC One_M8 using Tapatalk

Elisha said:
I would like to know the outcome as well. I did the GPE conversion and now want to go back to stock Rogers or the Developers Edition Sense but can't find a Rogers RUU and the Dev one is an exe.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I managed to get the RUU to go further but it tells me it can't update my device. Maybe I put the wrong CID or have the wrong MID
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: BS_US001

Try changing CID back to Rogers maybe?
Where did you get the RUU?
Sent from my HTC One_M8 using Tapatalk

Elisha said:
Try changing CID back to Rogers maybe?
Where did you get the RUU?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I don't remember what the original CID was. The RUU is the one from this thread.

You mean the Develepor edition one?

Elisha said:
You mean the Develepor edition one?
Click to expand...
Click to collapse
I tried both, none work. On my M7, I had a RUU in ZIP format and the CID I needed was BS_US001, but I tried that and BS_US002 and neither work.
Maybe my MID doesn't match but I don't know. It's easy with a ZIP, there is a text fire that tells you what it looks for but I never used an EXE before.

Nic2112 said:
I tried both, none work. On my M7, I had a RUU in ZIP format and the CID I needed was BS_US001, but I tried that and BS_US002 and neither work.
Maybe my MID doesn't match but I don't know. It's easy with a ZIP, there is a text fire that tells you what it looks for but I never used an EXE before.
Click to expand...
Click to collapse
That sucks. I kinda want to for back from Sense from my GPE conversion and can't find the proper RUU to flash via fastboot to get back to it.
The one linked in this thread is dead: http://forum.xda-developers.com/showthread.php?t=2733523
When I run the Dev RUU exe, it says do you want to update from a 2.X.X.X version to a 1.x.x.x. version which didn't make sense so I quit it.

Between the instructions here here, and then the HBOOT from here, the Brightstar RUU is installing.
I'll probably RUU back to GPE when it gets released for the HTC M8
Update: The Brightstar RUU worked but no APNs were discovered, had to configure one manually. Since Redpoint said that WWE editions don't work as well here, I'm giving the AT&T RUU a try right now. It's installing, I'm curious to see if it will set the Rogers APN automatically this time. It's also 4.4.3 instead of 4.4.0 so I might not need to download as many updates.
Update 2: AT&T is a bit worse, it's very AT&T flavored and seems even more out of place on Rogers. I think the only way would be to flash the HBOOT, then a custom recovery, restore a Rogers backup, set the CID and Recovery back to stock, and then factory reset.
I've decided to RUU back to GPE and stick to it. If L is released November 1st, it should be available as an OTA shortly after and I know that when that comes out, I'll want it so for a month's worth of usage, I'll stick to GPE.

Nic2112 said:
Did you mean to link to the same file twice?
Click to expand...
Click to collapse
Nope. My bad, bootable RUU is here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
---------- Post added at 12:01 PM ---------- Previous post was at 11:54 AM ----------
Nic2112 said:
Update 2: AT&T is a bit worse, it's very AT&T flavored and seems even more out of place on Rogers. I think the only way would be to flash the HBOOT, then a custom recovery, restore a Rogers backup, set the CID and Recovery back to stock, and then factory reset.
Click to expand...
Click to collapse
Yes, AT&T stock ROMs suck, with all the bloat and gimped features.
Really, if you decide you want a Sense experience, I would just recommend flashing a custom ROM of your choice and the radio that is friendly with your network.

The first link goes nowhere and the second one is one I was having trouble with as the 1.54.401.5-W_Splash.zip leads to a dead link as well.

Nic2112 said:
I don't remember what the original CID was. The RUU is the one from this thread.
Click to expand...
Click to collapse
ROGER001

Nic2112 said:
I managed to get the RUU to go further but it tells me it can't update my device. Maybe I put the wrong CID or have the wrong MID
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: BS_US001
Click to expand...
Click to collapse
Ok might be a bit outdate info seeing as you already decided to stick to GPE but yes the MID was wrong. MID for AT&T, Unlocked Version and Developer Edition are 0P6B12000 not 16000

BerndM14 said:
Ok might be a bit outdate info seeing as you already decided to stick to GPE but yes the MID was wrong. MID for AT&T, Unlocked Version and Developer Edition are 0P6B12000 not 16000
Click to expand...
Click to collapse
Thank you for the information. Since we might be a few short weeks from L, I figured no point in risking a brick at this time but I might change the MID anyways because I think the developer edition gets OTAs first.

Nic2112 said:
Thank you for the information. Since we might be a few short weeks from L, I figured no point in risking a brick at this time but I might change the MID anyways because I think the developer edition gets OTAs first.
Click to expand...
Click to collapse
Yeah they do, I also already downloaded all the necessary things to convert my device to a Developer Edition. :good:

[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.

Problem with htc one m8 ota

I tried upgrading my HTC one m8 by RUU but keep getting this error 155 wrong RUU used....
my phone is:
S-off
bootloader locked
CID version supercid 1111111
I tried using fastboot method,.zip method but nothing works

BruceWayne16594 said:
keep getting this error 155 wrong RUU used....
Click to expand...
Click to collapse
In order to troubleshoot this, we need to know what RUU you are trying (exact file name).
SuperCID is not enough, you need to also match MID in order to run RUU.
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
Also, your title says "OTA" but your post says "RUU". Confirm its RUU you are talking about? RUU and OTA are 2 very different things, with very different requirements, so you need to clarify here.

redpoint73 said:
In order to troubleshoot this, we need to know what RUU you are trying (exact file name).
SuperCID is not enough, you need to also match MID in order to run RUU.
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
Also, your title says "OTA" but your post says "RUU". Confirm its RUU you are talking about? RUU and OTA are 2 very different things, with very different requirements, so you need to clarify here.
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.08.20.0916
version-cpld: None
version-microp: None
version-main: 2.16.654.4
version-misc: PVT SHIP S-OFF
meid: 99000499079516
product: m8_whl
platform: hTCBmsm8974
modelid: 0P6B70000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 8a0f02ff
hbootpreupdate: 11
gencheckpt: 0
Yeah i'm talking about RUU
Ruu version (tried both)
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4

BruceWayne16594 said:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
Click to expand...
Click to collapse
Since you have the Sprint version, you should not try to use this RUU. The Sprint version has different partitioning than other M8 versions. Trying to flash any firmware or RUU besides Sprint can result in a radio brick.
Error 155 is common when trying to flash MM RUU on any device that is currently on LP (or in your case KK) firmware. Fastboot flash the 6.20.651 .3 firmware from the following thread, then try the RUU again: http://forum.xda-developers.com/showthread.php?t=2729173
Also, it looks like you have the Harmon Kardon variant (654 version numbers, versus 651 for non-HK Sprint). But I think 6.20.651 should still work. Otherwise, use the 6.20.654.3 firmware, then the 6.20.654.3 RUU.

redpoint73 said:
Since you have the Sprint version, you should not try to use this RUU. The Sprint version has different partitioning than other M8 versions. Trying to flash any firmware or RUU besides Sprint can result in a radio brick.
Error 155 is common when trying to flash MM RUU on any device that is currently on LP (or in your case KK) firmware. Fastboot flash the 6.20.651 .3 firmware from the following thread, then try the RUU again: http://forum.xda-developers.com/showthread.php?t=2729173
Also, it looks like you have the Harmon Kardon variant (654 version numbers, versus 651 for non-HK Sprint). But I think 6.20.651 should still work. Otherwise, use the 6.20.654.3 firmware, then the 6.20.654.3 RUU.
Click to expand...
Click to collapse
I already have the .zip version of the Ruu used , should i use that??

Thanks,
i succesfully flashed the firmware and rebooted but then the phone got stuck at splash screen.... pls help

BruceWayne16594 said:
I already have the .zip version of the Ruu used , should i use that??
Click to expand...
Click to collapse
Firmware and RUU are not the same thing; which is the very reason I've advised to flash the firmware, then the RUU.
Firmware is a small but critical zip package that contains several modules, including hboot, radio, and a few others. Once you install the firmware, the RUU should run properly to update all the remaining partitions.
---------- Post added at 09:16 AM ---------- Previous post was at 09:14 AM ----------
BruceWayne16594 said:
Thanks,
i succesfully flashed the firmware and rebooted but then the phone got stuck at splash screen.... pls help
Click to expand...
Click to collapse
You didn't follow my instruction, to flash the firmware, then try the RUU again. As I just mentioned above, RUU and firmware are not the same, and are 2 very different things.

Solved
redpoint73 said:
Firmware and RUU are not the same thing; which is the very reason I've advised to flash the firmware, then the RUU.
Firmware is a small but critical zip package that contains several modules, including hboot, radio, and a few others. Once you install the firmware, the RUU should run properly to update all the remaining partitions.
---------- Post added at 09:16 AM ---------- Previous post was at 09:14 AM ----------
You didn't follow my instruction, to flash the firmware, then try the RUU again. As I just mentioned above, RUU and firmware are not the same, and are 2 very different things.
Click to expand...
Click to collapse
Thanks,
I flashed the firmware follwed by the RUU as mentioned by you, this time following each thing very carefully and ................IT WORKS!!!!!!!!!!!
Thanks a lot

You're very welcome. Happy you got it sorted out.

HTC M9 RUU PROBLEMS (Spint to European)

hello,
sorry for being a pain.. i have spent the last 2 days trolling thru here to find answers but have failed to sort my problem out (user error) my problem is i have the HTC M9 which, after inspection, i discovered was on Sprint but have managed to S-Off the device and unlock the bootloader and then change both the MID & CID to European settings (getvar below) my problem is choosing the correct firmware for my device and then RUU file ... any help please?
Ive downloaded this file:
RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Radio_01.01_U11440261_56.02.50306G_2_F_release_429340_signed_2_4.exe
I thought the above file would work with my firmware version but tells me to get correct RUU?
(D:\>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: removed
(bootloader) version-main: 1.32.401.17
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0P6B10000
(bootloader) cid: HTC__032
all:
finished. total time: -0.000s
Thanks again

It could be that you're trying to apply firmware for the M9 when you have a M8. Your MID (0P6B10000) tells the story here.

computerslayer said:
It could be that you're trying to apply firmware for the M9 when you have a M8. Your MID (0P6B10000) tells the story here.
Click to expand...
Click to collapse
Thanks for pointing that out..i have a HTC M9...i used to have an M8 and had a list of MID's for that which i used for my M9 .. iv'e now changed the MID back but still having problems ...would you know what MID & CID i would use to maybe instal a European ROM please?

Craig_CFC said:
Thanks for pointing that out..i have a HTC M9...i used to have an M8 and had a list of MID's for that which i used for my M9 .. iv'e now changed the MID back but still having problems ...would you know what MID & CID i would use to maybe instal a European ROM please?
Click to expand...
Click to collapse
So you're trying to convert a Sprint M9 to European (I assume you mean the WWE variant)?
In short, this is not possible. The Sprint variant is a CDMA model, and those are locked in to their own firmware versions. Attempting to flash other firmware - even other CDMA firmware - will almost assuredly brick your phone.
I'm sorry I didn't say so at first - I got caught up in the MID mismatch and missed the obvious here.

computerslayer said:
So you're trying to convert a Sprint M9 to European (I assume you mean the WWE variant)?
In short, this is not possible. The Sprint variant is a CDMA model, and those are locked in to their own firmware versions. Attempting to flash other firmware - even other CDMA firmware - will almost assuredly brick your phone.
I'm sorry I didn't say so at first - I got caught up in the MID mismatch and missed the obvious here.
Click to expand...
Click to collapse
thanks for your help... is there any way i could get this phone to work in the UK? iv'e tried 3 different ROMs but al say 'no SIM found' or would that be down to the firmware?

Craig_CFC said:
thanks for your help... is there any way i could get this phone to work in the UK? iv'e tried 3 different ROMs but al say 'no SIM found' or would that be down to the firmware?
Click to expand...
Click to collapse
As far as I know, Sprint's CDMA network is pretty much USA-only. What little coverage they offer outside of the United States is limited.
As for the "no SIM found" issue, I think restoring your phone to stock is the only way to go - assuming that is possible. Recall that attempting to apply GSM firmware to a CDMA phone will potentially unrecoverably damage your phone.

HTC M8 - Need specific RUU and can't seem to find it. Details in post.

Hey all,
Recently got a HTC M8 from a garage sale. All works fine but it's stuck on KitKat.
When going to search for updates, just says "No Updates Available etc"
Went into fastboot and got all the info:
"C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA12.5mv
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.109
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxx
(bootloader) imei: xxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!"
Checking on RUU files, I don't seem to get a match with anything in particular and with my CID being 11111, it's likely been modified at some point in it's life - thus not getting OTA (that's from what I have found anyways)
Would anyone be able to help me on this one, I have zero knowledge when it comes to flashing RUUs for HTC. Only been doing Samsung stuff for ages
Help would be appreciated and if you need more info - let me know!
Thanks all!

No, I don't think it's possible that cidnum is modified, because of s-on. Maybe the one you got is a developer model?
And iirc cidnum 11111111 can use any RUU, but won't receive any OTA.

Never_Sm1le said:
No, I don't think it's possible that cidnum is modified, because of s-on. Maybe the one you got is a developer model?
And iirc cidnum 11111111 can use any RUU, but won't receive any OTA.
Click to expand...
Click to collapse
No idea the history of the device and I was just going off what other forums said about the cidnum.
There's no developer text on startup either (seen this on other HTC devices)
Cause I obviously want to grab a marshmallow RUU, so would I go about grabbing any one of them and just seeing what happens?
Bootloader is still locked but from the looks of it, it may need to be unlocked to flash an RUU?
It's pretty confusing, if you have a noob guide to it that would be good.
Thanks!

skylirizm said:
No idea the history of the device and I was just going off what other forums said about the cidnum.
There's no developer text on startup either (seen this on other HTC devices)
Cause I obviously want to grab a marshmallow RUU, so would I go about grabbing any one of them and just seeing what happens?
Bootloader is still locked but from the looks of it, it may need to be unlocked to flash an RUU?
It's pretty confusing, if you have a noob guide to it that would be good.
Thanks!
Click to expand...
Click to collapse
I think you could try, because RUU won't need unlocked bootloader (I might be wrong here, you can do it for extra precaution) and if the RUU is not compatible it will end with an error and nothing will be flashed to your m8.
And turn out s-off can become s-on again, so I think this is the work of the seller. The hard thing right now is to find out the original cid of your device. Did the seller mention anything about the variant of the phone?

Never_Sm1le said:
I think you could try, because RUU won't need unlocked bootloader (I might be wrong here, you can do it for extra precaution) and if the RUU is not compatible it will end with an error and nothing will be flashed to your m8.
And turn out s-off can become s-on again, so I think this is the work of the seller. The hard thing right now is to find out the original cid of your device. Did the seller mention anything about the variant of the phone?
Click to expand...
Click to collapse
It was just at a garage sale and was just for parts only (screen is a little bit damaged) but otherwise it works fine.
There's no carrier specific apps on here and I am in Australia so I assume the device is from one of those.
It's also a M8n if that makes a difference, most M8 phones I have come across are M8x.
Well it's still S-ON and from what i also found, it seems I can't even do that anymore since firewater doesn't work?

skylirizm said:
It was just at a garage sale and was just for parts only (screen is a little bit damaged) but otherwise it works fine.
There's no carrier specific apps on here and I am in Australia so I assume the device is from one of those.
It's also a M8n if that makes a difference, most M8 phones I have come across are M8x.
Well it's still S-ON and from what i also found, it seems I can't even do that anymore since firewater doesn't work?
Click to expand...
Click to collapse
you can s-off by using an app called sunshine but it will cost $25 (US Dollar).

Never_Sm1le said:
you can s-off by using an app called sunshine but it will cost $25 (US Dollar).
Click to expand...
Click to collapse
Nah not worth it. If I can flash an RUU being S-ON then I will attempt a couple of them and see how I go I guess. As you said, if it won't work then it will come up with some sort of error. Thanks!

Never_Sm1le said:
you can s-off by using an app called sunshine but it will cost $25 (US Dollar).
Click to expand...
Click to collapse
Update:
Updated using this RUU "0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4 _Radio_1.29.214500021.12G_20.72.4196t.01_release_4 64360_signed.zip" - via SD Card method and all working perfect. Running on Marshmallow now and it's much better. Thanks for the help

skylirizm said:
Update:
Updated using this RUU "0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4 _Radio_1.29.214500021.12G_20.72.4196t.01_release_4 64360_signed.zip" - via SD Card method and all working perfect. Running on Marshmallow now and it's much better. Thanks for the help
Click to expand...
Click to collapse
No root?

jerryspring said:
No root?
Click to expand...
Click to collapse
Nope, just flashed via SDCard and all is working perfect.
Checked and it's not rooted. May have been in one point of it's life but not now.

skylirizm said:
Bootloader is still locked but from the looks of it, it may need to be unlocked to flash an RUU?
Click to expand...
Click to collapse
The reverse is true: bootloader needs to be LOCKED (or RELOCKED) in order to run RUU (will fail if UNLOCKED).
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
skylirizm said:
Update:
Updated using this RUU "0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4 _Radio_1.29.214500021.12G_20.72.4196t.01_release_4 64360_signed.zip" - via SD Card method and all working perfect. Running on Marshmallow now and it's much better.
Click to expand...
Click to collapse
If I had seen this thread earlier, that is the RUU I would have recommended for most folks. Nice work figuring it out (not an easy feat).
The product ID of the device (m8_ul_ca) means it is most likely the AT&T version or US Developer's Edition. But the Euro (401) RUU you flashed is probably a better fit for most regions/carriers, unless you actually use AT&T as your carrier (US).
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
Never_Sm1le said:
you can s-off by using an app called sunshine but it will cost $25 (US Dollar).
Click to expand...
Click to collapse
You don't need s-off to update (RUU) the phone, so I don't understand why you are telling him to do this.
---------- Post added at 02:12 PM ---------- Previous post was at 02:08 PM ----------
Never_Sm1le said:
No, I don't think it's possible that cidnum is modified, because of s-on. Maybe the one you got is a developer model?
And iirc cidnum 11111111 can use any RUU, but won't receive any OTA.
Click to expand...
Click to collapse
Phone can be made s-off and SuperCID, then s-on again. We've seen this a lot, usually done by previous owner or seller to unlock the SIM, etc.
"Any" RUU is a dangerous statement. Flash a CDMA RUU to a non-CDMA variant will radio brick the device.

redpoint73 said:
The reverse is true: bootloader needs to be LOCKED (or RELOCKED) in order to run RUU (will fail if UNLOCKED).
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
If I had seen this thread earlier, that is the RUU I would have recommended for most folks. Nice work figuring it out (not an easy feat).
The product ID of the device (m8_ul_ca) means it is most likely the AT&T version or US Developer's Edition. But the Euro (401) RUU you flashed is probably a better fit for most regions/carriers, unless you actually use AT&T as your carrier (US).
---------- Post added at 02:08 PM ---------- Previous post was at 02:07 PM ----------
You don't need s-off to update (RUU) the phone, so I don't understand why you are telling him to do this.
---------- Post added at 02:12 PM ---------- Previous post was at 02:08 PM ----------
Phone can be made s-off and SuperCID, then s-on again. We've seen this a lot, usually done by previous owner or seller to unlock the SIM, etc.
"Any" RUU is a dangerous statement. Flash a CDMA RUU to a non-CDMA variant will radio brick the device.
Click to expand...
Click to collapse
Thanks for correcting me. I think I mistake the firmware zip (don't know why people called this ruu.zip) and ruu.exe.

Never_Sm1le said:
I think I mistake the firmware zip (don't know why people called this ruu.zip) and ruu.exe.
Click to expand...
Click to collapse
Same rules apply for firmware.zip (do not need s-off as long as you are flashing the firmware for your phone's CID).
Folks will often call the RUU or the stock ROM generically as "firmware" (to their own detriment). But for this device (as you seem to be aware) firmware.zip is a very specific thing (and not the same as RUU or ROM).