Develop Bugs

[Q] Converting my M8

Hello guys,
I have my M8 bought from US, Verizon and I am living in Netherlands. The problems is that I cannot get the updates from Verizon because as you know is CDMA so I have been trying to find a way to convert my M8 Verzion into an international M8.
First step: I flashed @Mike1986's One_M8_2.22.401.4_odexed and everything workes on my phone, even wifi and I also receive notification about software updates, the only problem is that when I try to install that updates ( see the error in the attached image).
My question is : what do i need to modifiy to make the phone 100% international version ?
I have to mention that I have S-off already

Is your network carrier a cdma or gsm network? If it's gsm network, it will not work.

It's gsm.
Yes I read that it won't work if you are on a gsm network it will not work but technically Verizon M8 has the same hardware as the international version so logically it should be possible to convert it, I just don't know what do i need to do.

"logical" or not, the internal electronics are different in the radio section, so you will not be able to get it to work as you would like..

S0wL said:
It's gsm.
Yes I read that it won't work if you are on a gsm network it will not work but technically Verizon M8 has the same hardware as the international version so logically it should be possible to convert it, I just don't know what do i need to do.
Click to expand...
Click to collapse
I don't know much about Verizon and I maybe wrong but if it is a GSM and S-Off (as you mentioned that you flash mike's ROM and it works flawlessly and you received OTA) then what you need is the right combination of CID and MID.
For e.g an Intl GSM EU_WWE, the MID is 0P6B10000 and for CID you can make it SuperCID.
Check your current MID - command fastboot getvar mid

ckpv5 said:
I don't know much about Verizon and I maybe wrong but if it is a GSM and S-Off (as you mentioned that you flash mike's ROM and it works flawlessly and you received OTA) then what you need is the right combination of CID and MID.
For e.g an Intl GSM EU_WWE, the MID is 0P6B10000 and for CID you can make it SuperCID.
Check your current MID - command fastboot getvar mid
Click to expand...
Click to collapse
My MID is 0P6B20000

S0wL said:
My MID is 0P6B20000
Click to expand...
Click to collapse
Yeah, International version is 0P6B10000

S0wL said:
My MID is 0P6B20000
Click to expand...
Click to collapse
That's explained the error that you posted in your screenshot because the OTA expect that you have MID 0P6B10000
You can change MID as in this guide : http://forum.xda-developers.com/showthread.php?t=2708581
The only question is whether the conversion will really work or not. I have no idea about verizon so not so sure. I only assume it will work based on your own comment that said Mike's ROM works flawlessly on your device. If this is true, then it should work.
Damn...it's really late over here ... gotta go now... maybe someone else have better idea for you ... good luck

S0wL said:
My MID is 0P6B20000
Click to expand...
Click to collapse
You'll need to change your MID if you're trying for International WWE.
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify 0P6B10000 for modelid
fastboot reboot
Credit for code goes to @scotty1223 [how to] change your MID without an eng bootloader
---------- Post added at 08:29 PM ---------- Previous post was at 08:29 PM ----------
ckpv5 said:
That's explained the error that you posted in your screenshot because the OTA expect that you have MID 0P6B10000
You can change MID as in this guide : http://forum.xda-developers.com/showthread.php?t=2708581
The only question is whether the conversion will really work or not. I have no idea about verizon so not so sure. I only assume it will work based on your own comment that said Mike's ROM works flawlessly on your device. If this is true, then it should work.
Damn...it's really late over here ... gotta go now... maybe someone else have better idea for you ... good luck
Click to expand...
Click to collapse
You keep jumping ahead of me by mere minutes
:good:

ckpv5 said:
That's explained the error that you posted in your screenshot because the OTA expect that you have MID 0P6B10000
You can change MID as in this guide : http://forum.xda-developers.com/showthread.php?t=2708581
The only question is whether the conversion will really work or not. I have no idea about verizon so not so sure. I only assume it will work based on your own comment that said Mike's ROM works flawlessly on your device. If this is true, then it should work.
Damn...it's really late over here ... gotta go now... maybe someone else have better idea for you ... good luck
Click to expand...
Click to collapse
Thanks, I changed MID, I will try now the software update to see what happens, I will be back with a reply

Can executable RUUs be used to downgrade?

There's something that I'm a bit unclear on when it comes to RUUs
Let's say that I'd like to try out the latest Marshmallow release without waiting for the OTA and use the HTC-provided RUU .exe (3.35.617.12)
I'm on a T-Mobile branded M9 and would like to keep WiFi Calling and Visual Voicemail. If I find that I am unable to use these features in the non-branded HTC MM release, will I simply be able to use the T-Mobile branded RUU .exe (2.11.531.19) to revert back or will I be unable to as it's an older version (Android 5.1)
I'm currently still locked and S-ON
I seem to remember downgrades not being possible on my M7 once the hboot was updated to a newer version, but am a bit confused about the specifics of the M9
Thank you, and my apologies if this is a dumb question -- I've done my best to find an answer through searching

You cannot flash RUU that does not match your device variant. In this case, you would need 3.35.531.xx RUU, to try marshmallow. 3.35.617.xx won't install on your phone, unless you S-off and change the variant CID.

But once your phone is S-OFF then you are able to downgrade, too. (Although it doesn't matter whether you use a RUU.zip or a RUU.exe.)

asestar said:
You cannot flash RUU that does not match your device variant. In this case, you would need 3.35.531.xx RUU, to try marshmallow. 3.35.617.xx won't install on your phone, unless you S-off and change the variant CID.
Click to expand...
Click to collapse
Well, now I'm a bit confused as far as variants are concerned. This HTC release page states
This software upgrade comes in the form of two sequential updates. The first update will install software version 2.11.617.180 , which does not include the Android OS upgrades. The following update will install software version 3.35.617.12 , which includes the changes to the Android OS.
Click to expand...
Click to collapse
Am I correct in understanding now that the '617' portion of those two versions is what indicates the device variant? And that my device's variant is '531'?
So then it appears that the only ways for me to try out Marshmallow at this point would be:
1) Wait until HTC/T-Mobile unleash their official release and update via OTA or RUU
2) Unlock my bootloader, flash TWRP, and install whatever ROM I please
3) Unlock bootloader, S-OFF, and RUU as I please
Flippy498 said:
But once your phone is S-OFF then you are able to downgrade, too. (Although it doesn't matter whether you use a RUU.zip or a RUU.exe.)
Click to expand...
Click to collapse
And so long as I'm S-OFF I could use this particular T-Mobile RUU executable to revert back to stock at any point and then re-lock my bootloader, correct? But as long as I'm S-ON, then downgrading is not an option, even using an RUU of the '531' variant?
(bootloader) kernel: lk
(bootloader) product: htc_himaul
(bootloader) version: 1.0
(bootloader) imei: REDACTED
(bootloader) version-main: 2.11.531.19
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_86.09.50731G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA12000
(bootloader) cid: T-MOB010
Click to expand...
Click to collapse

Miguel_Lancaster said:
Am I correct in understanding now that the '617' portion of those two versions is what indicates the device variant? And that my device's variant is '531'?
Click to expand...
Click to collapse
Correct. 617 is the SKU for the unlocked/developer edition and 531 belongs to T-Mobile US.
Miguel_Lancaster said:
So then it appears that the only ways for me to try out Marshmallow at this point would be:
1) Wait until HTC/T-Mobile unleash their official release and update via OTA or RUU
2) Unlock my bootloader, flash TWRP, and install whatever ROM I please
3) Unlock bootloader, S-OFF, and RUU as I please
Click to expand...
Click to collapse
1) Correct.
2) You can't flash Android M Sense roms when your phone is using the Android L firmware. So you need to look for the Android L versions of the roms (e.g. ARHD 14.0 or Viper 3.5). Sense-less Android M roms like CM should be fine, though.
3) Correct.
Miguel_Lancaster said:
And so long as I'm S-OFF I could use this particular T-Mobile RUU executable to revert back to stock at any point and then re-lock my bootloader, correct? But as long as I'm S-ON, then downgrading is not an option, even using an RUU of the '531' variant?
Click to expand...
Click to collapse
Correct (both times). Although you should keep in mind that your phone will bootloop if it's not 100% stock and you lock or relock the bootloader. (I personally think there is no benefit in locking/re-locking or even setting S-OFF back to S-ON unless you want to send your phone to HTC for warranty claims.)

asestar said:
2) You can't flash Android M Sense roms when your phone is using the Android L firmware. So you need to look for the Android L versions of the roms (e.g. ARHD 14.0 or Viper 3.5). Sense-less Android M roms like CM should be fine, though.
3) Correct.
Click to expand...
Click to collapse
Hmm, and here I was thinking that ROMS included the firmware and both could be flashed through TWRP. Guess I was mistaken. Or...
asestar said:
Correct (both times). Although you should keep in mind that your phone will bootloop if it's not 100% stock and you lock or relock the bootloader. (I personally think there is no benefit in locking/re-locking or even setting S-OFF back to S-ON unless you want to send your phone to HTC for warranty claims.)
Click to expand...
Click to collapse
Phone was just purchased used, so if there's any warranty period left it probably isn't for very much longer. In the past I've gone S-OFF for all my HTC devices (Incredible, then One S, then One M7) but they've always seemed to have their own unique quirks and this M9 appears to be no different.
My main reasoning for staying S-ON/Stock at the moment is just in case I find a reason to return the device to the seller. After a few days when I'm sure everything is alright with it, I'm sure I'll be less reluctant to tweak.
Is a bootloop easily fixable?
So, to clarify (again!) --
In my phone's current state, I would be limited to Lollipop ROMs when flashing via TWRP?
So then, the shortest route to flashing custom Marshmallow ROMs would be to S-OFF and then RUU to an International Marshmallow firmware? Would I need to change CID manually or is that handled during RUU so long as I'm S-OFF?
And the safest route (in which S-OFF would be completely optional) would be to wait for the T-Mobile OTA release for Marshmallow before unlocking the bootloader and flashing TWRP?
Thanks a bunch for your responses. I'm sure this stuff gets answered all the time, but it can sometimes be difficult to find a specific answer in the depths of these boards. Plus, I find it hard to keep 100% on all development when I only buy a new device every couple of years.
I used the ARHD rom on my last device and quite liked it, but there was a T-Mobile specific variant that kept WiFi calling and all the other carrier-specific stuff. I'm pretty sure the developer has since long given up on maintaining those features., but it's my understanding that ViperOne may still have them.

Miguel_Lancaster said:
Hmm, and here I was thinking that ROMS included the firmware and both could be flashed through TWRP. Guess I was mistaken. Or...
Click to expand...
Click to collapse
The difference between rom and firmware.
Miguel_Lancaster said:
Is a bootloop easily fixable?
Click to expand...
Click to collapse
Just reflash a RUU. The problem for most non-US firmwares is that HTC doesn't provide RUUs so sometimes there is no freely accessible RUU for a specific firmware version. (The only other method besides flashing a RUU is restoring a TWRP backup or re-/flashing a custom rom which needs an unlocked bootloader and TWRP.) If someone decides to re-S-ON and to lock/relock and the rom doesn't boot then that person might not be able to fix that bootloop without this RUU service. (The same applies to S-ON users who decide to relock if the rom doesn't boot.) HTC introduced a new security feature with Android 5.1 (firmware 2.x and higher). It prevents the bootloader unlock if the option OEM Unlock isn't activated in developer options. That's why I recommend everyone staying S-OFF and unlocked unless you need to send your phone back to HTC for a warranty claim since even OTAs can be installed with an unlocked bootloader. Well, RUU.exe deny to flash with S-ON and an unlocked bootloader but there are not many RUU.exe for non-US firmware versions and you can always extract the RUU.zip from a RUU.exe. (RUU.zip files can be flashed via an external SD card even if the bootloader is unlocked.)
Miguel_Lancaster said:
In my phone's current state, I would be limited to Lollipop ROMs when flashing via TWRP?
Click to expand...
Click to collapse
Correct if you're talking about Sense roms.
Miguel_Lancaster said:
So then, the shortest route to flashing custom Marshmallow ROMs would be to S-OFF and then RUU to an International Marshmallow firmware? Would I need to change CID manually or is that handled during RUU so long as I'm S-OFF?
Click to expand...
Click to collapse
Or you use an unlocked/dev edition RUU. There is no big difference between the firmware of those two M9 versions. Nevertheless you need to change both the CID and the MID. The commands are fastboot oem writecid <enterwhicheverCIDisneeded> and fastboot oem writemid <enterwhicheverMIDisneeded>. (SKU 617 - unlocked/dev edition - CID: BS_US002 - MID: 0PJA11000; SKU 401 - international version - CID: HTC__001 - MID: 0PJA10000; SKU 531 - T-Mobile US - CID: T-MOB010 - MID: 0PJA12000)
Miguel_Lancaster said:
And the safest route (in which S-OFF would be completely optional) would be to wait for the T-Mobile OTA release for Marshmallow before unlocking the bootloader and flashing TWRP?
Click to expand...
Click to collapse
Correct.
Miguel_Lancaster said:
I used the ARHD rom on my last device and quite liked it, but there was a T-Mobile specific variant that kept WiFi calling and all the other carrier-specific stuff. I'm pretty sure the developer has since long given up on maintaining those features., but it's my understanding that ViperOne may still have them.
Click to expand...
Click to collapse
Don't know about ARHD but Viper has that feature.
Btw: Getting S-OFF is quite easy but it costs 25 USD. You simply need to use the Sunshine App. (Or you look for someone who has a java card.)

Thank you for taking the time to answer all of my questions.

No problem. Maybe those detailed answers might help other users as well. (That's at least what I hope. )

Flippy498 said:
Or you use an unlocked/dev edition RUU. There is no big difference between the firmware of those two M9 versions. Nevertheless you need to change both the CID and the MID. The commands are fastboot oem writecid <enterwhicheverCIDisneeded> and fastboot oem changemid <enterwhicheverMIDisneeded>. (SKU 617 - unlocked/dev edition - CID: BSUS_002 - MID: 0PJA11000; SKU 401 - international version - CID: HTC__001 - MID: 0PJA10000; SKU 531 - T-Mobile US - CID: T-MOB010 - MID: 0PJA12000)
Click to expand...
Click to collapse
**** --
I changed my MID to the Developer edition, but I accidentally used the letter O and not the number 0 -- so OPJA11000
Then I attempted an RUU and now my phone is stuck in the RUU screen and I can't even turn it off. Is there any way to recover this? I don't even think I can use ADB anymore.
edit: I got it to reboot by holding BOTH volume buttons and POWER. What a stupid mistake. I'll leave this here though so hopefully no one else does anything so stupid.
Yikes :silly:
edit 2: Hmm, changed MID to the correct value but I'm still getting ERROR 131 CUSTOMER ID ERROR during RUU. Will have to investigate this further. Maybe I need to relock the bootloader.
P.S. The command to change the MID actually seem to be writemid, not changemid -- figured that out through trial and error
edit 3: Relocking the bootloader still gives the same error RUU. Now I'm stumped.
edit 4: Turns out the CID should actually be BS_US002, not BSUS_002, as you told me in the earlier reply.
edit 5: Yup, fixing the CID solved the problem

Miguel_Lancaster said:
P.S. The command to change the MID actually seem to be writemid, not changemid -- figured that out through trial and error
Click to expand...
Click to collapse
Ah, sorry. I don't know why I wrote changemid. It wasn't intended. Of course it has to be writemid. I will correct the post.
Miguel_Lancaster said:
Turns out the CID should actually be BS_US002, not BSUS_002, as you told me in the earlier reply.
Click to expand...
Click to collapse
Sinc I don't know every CID by heart I copied it from a CID list I found with google. I'm going to correct that mistake, too. Thanks for clarifying.
Sorry for the hassle.

Flippy498 said:
Ah, sorry. I don't know why I wrote changemid. It wasn't intended. Of course it has to be writemid. I will correct the post.
Sinc I don't know every CID by heart I copied it from a CID list I found with google. I'm going to correct that mistake, too. Thanks for clarifying.
Sorry for the hassle.
Click to expand...
Click to collapse
I didn't brick anything and got it all figured out in the long run, so no worries. I may not have attempted this in the first place without everything explained so concisely by you earlier, so thank you. Hopefully this thread (mistakes and all) can be beneficial to others.
Seriously though, who decided it was a good idea to put a zero before 'PJA' for the CID? That's just asking for trouble.

Miguel_Lancaster said:
I didn't brick anything and got it all figured out in the long run, so no worries. I may not have attempted this in the first place without everything explained so concisely by you earlier, so thank you. Hopefully this thread (mistakes and all) can be beneficial to others.
Seriously though, who decided it was a good idea to put a zero before 'PJA' for the CID? That's just asking for trouble.
Click to expand...
Click to collapse
That whole "0" or "O" bull**** ...
Cost me 3 days of heartache getting errors...
Yeah....that structure is a horrible idea....g

Shall I update to marshmallow?

Guys, I got my m8 about 5 days back. I think it's international Taiwan version. I have attached the images of current software version I am on.
Currently the phone is asking me about 3 very small updates available. I have attached that image also. I don't know what these updates are for.
Shall I update?
Will my phone remain unlocked after these updates?
If after these updates I get prompted for real marshmallow update, shall I update to marshmallow.
Does marshmallow offer much better and some desirable features which we currently don't have?
Btw, I am currently highly satisfied with my current lollipop version.
This thing has really surpassed my expectations. I previously had LG g pro and Xperia z ultra.

Yes, I would definitely update. The phone seems smoother and less laggy on android M. A few new features. Lollipop felt like a beta version of M.
There is really no point to not update.

lekhwani said:
I think it's international Taiwan version.
Click to expand...
Click to collapse
That's not Taiwan version but Asia WWE

ckpv5 said:
That's not Taiwan version but Asia WWE
Click to expand...
Click to collapse
I installed the 3 small updates. Phone prompted me to restart.
So I restarted.
Then I again check software updates and get this prompt:
After hitting the download button, I let it download as it starts downloading some 1.14 gb update. I also put it to charge.
But when after an hour so when I picked up the phone got the message given in second attached picture.
Can someone guide what is the issue?

That means your device is not the original Asia WWE ... I guess you don't bought a new device from authorized HTC dealer.
To know which device that originally is, you need to get the fastboot getvar all result.
Also what's written on the bootloader

ckpv5 said:
That means your device is not the original Asia WWE ... I guess you don't bought a new device from authorized HTC dealer.
To know which device that originally is, you need to get the fastboot getvar all result.
Also what's written on the bootloader
Click to expand...
Click to collapse
It was a new sealed pack I got from eBay. But why it throws up the second message about variant. (I mean when it says mm software update available) ?

It says an update available because the software version no. installed on device is 4.19.707.4 and there is an update to 6.14.707.1
But the second message says it can't install the update because the model-ID in incorrect. It expect model-ID for 4.19.707.4 which is 0P6B11000 but your device may have a different model-ID
That's why we need the fastboot getvar all to determine your original device variant

ckpv5 said:
It says an update available because the software version no. installed on device is 4.19.707.4 and there is an update to 6.14.707.1
But the second message says it can't install the update because the model-ID in incorrect. It expect model-ID for 4.19.707.4 which is 0P6B11000 but your device may have a different model-ID
That's why we need the fastboot getvar all to determine your original device variant
Click to expand...
Click to collapse
But why doesn't it check for the compatible version automatically.
I mean it should say software update is not available for mobile.
It shouldn't prompt in the first place.
The update should automatically check which version or software or hardware I am on.
Btw I have hit the download button again and it's downloading. It's been about 10 minutes and 13% progress.
If this doesn't work this time again, I suppose will have to do getvar thing.
Btw, can the information given on following link solve my problem?
It says don't restart after installing 3 small updates.
But think that guys problem was a bit different
https://www.reddit.com/r/htcone/comments/41809r/marshmallow_update_question/

Those questions only HTC can answer. If I am HTC .. I don't expect the device is modified and I won't check whether the device is modified or not. Most important what is the software version no. because things like model-ID is something in the hardware not the software and users are not supposed to modify hardware.
Sorry ... I don't read outside link ... only XDA for problem reported on XDA.
If you don't feel like to fix it ... just hit don't install, don't check auto checking and block the notification ...
Good luck .. I have to go now .. bed time.
Maybe someone else will help you.

ckpv5 said:
Those questions only HTC can answer. If I am HTC .. I don't expect the device is modified and I won't check whether the device is modified or not. Most important what is the software version no. because things like model-ID is something in the hardware not the software and users are not supposed to modify hardware.
Sorry ... I don't read outside link ... only XDA for problem reported on XDA.
If you don't feel like to fix it ... just hit don't install, don't check auto checking and block the notification ...
Good luck .. I have to go now .. bed time.
Maybe someone else will help you.
Click to expand...
Click to collapse
Thanks for your help so far. Actually its bed here for me as well.
Am already in bed actually.
I have only very occasionly done those fastboot thing.
Suppose will have to do it through laptop tomorrow (when I find time)
Will report here again.

ckpv5 said:
Those questions only HTC can answer. If I am HTC .. I don't expect the device is modified and I won't check whether the device is modified or not. Most important what is the software version no. because things like model-ID is something in the hardware not the software and users are not supposed to modify hardware.
Sorry ... I don't read outside link ... only XDA for problem reported on XDA.
If you don't feel like to fix it ... just hit don't install, don't check auto checking and block the notification ...
Good luck .. I have to go now .. bed time.
Maybe someone else will help you.
Click to expand...
Click to collapse
Buddy, today I found some time and installed adb and fastboot.
After going to fasboot I got to see that my device is s off.
Also ran the getvar all command.
Attached both pics.
Kindly let me know guys , what does my current configuration / status means?
And , what options I have to upgrade to marshmallow?

Here are the pics

lekhwani said:
Here are the pics
Click to expand...
Click to collapse
Your device is m8_ul_ca means it is originally an AT&T or a Developer Edition device.
Now it's running Asia WWE ROM, the CID is SuperCID (which is good) but the MID is EU MID
So .. you have to decide ..what you want your device to be ?
Most important where your location is then make it suitable for your current location.
The easiest is change it to EU WWE ... you don't need to change anything ... only run the EU WWE RUU

ckpv5 said:
Your device is m8_ul_ca means it is originally an AT&T or a Developer Edition device.
Now it's running Asia WWE ROM, the CID is SuperCID (which is good) but the MID is EU MID
So .. you have to decide ..what you want your device to be ?
Most important where your location is then make it suitable for your current location.
The easiest is change it to EU WWE ... you don't need to change anything ... only run the EU WWE RUU
Click to expand...
Click to collapse
Thanks for the quick reply.
I am from India. Is there any method by way of which I can install ota which currently throws the system variant issue after downloading the full 1.14 gb download.
Can this be due to s off?
can I just s on from s off and this will resolve my current issue.
Or its not possible now ?( Because it's modified too far?)

read just a few minutes back in one m8 thread on xda only that with a fastboot command (fastboot own writesecurflag 3) we can convert to s on but everything should be stock for this.

As I mentioned earlier, the system variant error is due to wrong MID on the device, nothing to do with S-Off/S-On status.
You would not have the system variant error if the MID is 0P6B11000 ( read back my post #7 )
To ensure a successful OTA installation ... both software version no. and MID must correct .. same goes for CID but since yours is SuperCID then it is universal for any variant.
Give you a few examples of correct version no. & MID
Asia WWE - x.xx.707.x - MID - 0P6B11000
EU WWE - x.xx.401.x - MID - 0P6B10000
India WWE - x.xx.720.x - MID - 0P6B65000
Your current configuration is wrong, that's why the system variant error.
I suggest to install EU WWE RUU so you save the headache to change this and that.
Read this for the driver part that you need on your PC - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Read this for the EU RUU and How-to : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

Or if the above is not possible, I am ready to flash ruu. Then kindly guide me how and what ruu to flash? Will I have to unlock also?

lekhwani said:
read just a few minutes back in one m8 thread on xda only that with a fastboot command (fastboot own writesecurflag 3) we can convert to s on but everything should be stock for this.
Click to expand...
Click to collapse
Don't do this when you have this kind of wrong configuration on your device.
You'll regret your action as you won't be able to do anything not even OTA until you spend another USD25 to S-Off it again and correct the configuration.
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
lekhwani said:
Or if the above is not possible, I am ready to flash ruu. Then kindly guide me how and what ruu to flash? Will I have to unlock also?
Click to expand...
Click to collapse
Read what I posted earlier ... that's all you need to do .. no need to unlock but you can unlock if you want to.

My mied reads 000000.. does this mean eu mied?

Or its just because it's not a cdma device?

[Q] How can I update my M9

Hey guys,
I came here as I got a replacement M9 (refurbished - for an old and well used M8) which I tried to update but it won't let me do the OTA's or even the RUU's to get from 5.1 to 6 (which even my M8 had). I even
got the Zip files for the 2-part update and copied them on the phone, using the manual update option in the boot-menu (manual update from sd-card).... but all of that doesn't work because of an "Error 7" .
After trying factory reset and what the "basic user" does in cases like this I found out that my phone had already been "tampered" with as it is "S-Off" and the all 1's CID (Super-CID ? as far as I read something
like that). I don't need OTA possibilities but at least the option to update it somehow :/ ... any suggestion?

Arcdar said:
Hey guys,
I came here as I got a replacement M9 (refurbished - for an old and well used M8) which I tried to update but it won't let me do the OTA's or even the RUU's to get from 5.1 to 6 (which even my M8 had). I even
got the Zip files for the 2-part update and copied them on the phone, using the manual update option in the boot-menu (manual update from sd-card).... but all of that doesn't work because of an "Error 7" .
After trying factory reset and what the "basic user" does in cases like this I found out that my phone had already been "tampered" with as it is "S-Off" and the all 1's CID (Super-CID ? as far as I read something
like that). I don't need OTA possibilities but at least the option to update it somehow :/ ... any suggestion?
Click to expand...
Click to collapse
1) Change your MID to the developer MID (i.e., fastboot oem writemid 0PJA11000)
2) Change your CID to the developer CID (i.e., fastboot oem writecid BS_US001)
3) Flash this RUU: http://www.htc.com/us/support/htc-one-m9/news/
EDIT: See here: http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948

efrant said:
1) Change your MID to the developer MID (i.e., fastboot oem writemid 0PJA11000)
2) Change your CID to the developer CID (i.e., fastboot oem writecid BS_US001)
3) Flash this RUU: http://www.htc.com/us/support/htc-one-m9/news/
EDIT: See here: http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
Click to expand...
Click to collapse
Thank's so much!
I'll try it tomorrow

Arcdar said:
Thank's so much!
I'll try it tomorrow
Click to expand...
Click to collapse
Hey,
I'm sorry I reply that late but I needed enough time to try everything out and do a full backup before that. I tried that today and somehow it tells me that it doesn't work - again
Bootloader:
-Software status is official
-Locked
-s-off
CID: BS__US001
MID: 0PJA10000
I also tried it with CID: HTC__001
I downloaded the 2.08GB file you linked and they talk about but it always tells me it can't update it. Same if I get the EU/Unlocked RUU's from HTC and try to go from 5.1 to 6 (the 2 step install process or with the one-RUU for 6).
I'm really sad/fed up/angry by now.... I even had 6.0 on my One M8 ... and just can't get 6 work on my One M9

Arcdar said:
Hey,
I'm sorry I reply that late but I needed enough time to try everything out and do a full backup before that. I tried that today and somehow it tells me that it doesn't work - again
Bootloader:
-Software status is official
-Locked
-s-off
CID: BS__US001
MID: 0PJA10000
I also tried it with CID: HTC__001
I downloaded the 2.08GB file you linked and they talk about but it always tells me it can't update it. Same if I get the EU/Unlocked RUU's from HTC and try to go from 5.1 to 6 (the 2 step install process or with the one-RUU for 6).
I'm really sad/fed up/angry by now.... I even had 6.0 on my One M8 ... and just can't get 6 work on my One M9
Click to expand...
Click to collapse
Not sure if it's a typo on your part, but the MID is wrong. You have it for Wwe. that could be the issue, unless it's a typo, then it's not.

squ89r97 said:
Not sure if it's a typo on your part, but the MID is wrong. You have it for Wwe. that could be the issue, unless it's a typo, then it's not.
Click to expand...
Click to collapse
my bad, a typo - here in the forum, not on my phone. the RUU-Installer that was linked for that still doesn't work

Demo unit => Supercid, restored TRWP stock backup - Demo software still present

Hi guys
I'm having an issue with my M) unit. It's a Demo unit and I have S-OFF using sunshine and SuperCid.
Installed TRWP and restored bonesy stock backup, but the demo software is still present.
I though changing the CID was enough as CID 02 was triggering it.
But it's not the case.
Any help is appreciated.
Thanks.

elmalote said:
Hi guys
I'm having an issue with my M) unit. It's a Demo unit and I have S-OFF using sunshine and SuperCid.
Installed TRWP and restored bonesy stock backup, but the demo software is still present.
I though changing the CID was enough as CID 02 was triggering it.
But it's not the case.
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
I'm presuming it will still have the demo firmware installed, but as you're super cid and soff, you can now flash a "normal" stock firmware to rid it.

squ89r97 said:
I'm presuming it will still have the demo firmware installed, but as you're super cid and soff, you can now flash a "normal" stock firmware to rid it.
Click to expand...
Click to collapse
But I restored his backup, not mine? What is it checking on if not CID?

elmalote said:
But I restored his backup, not mine? What is it checking on if not CID?
Click to expand...
Click to collapse
Well, I'm thinking the actual firmware.
I searched google, found this.
https://forum.xda-developers.com/one-m9/help/removing-demo-content-t3063179

squ89r97 said:
Well, I'm thinking the actual firmware.
I searched google, found this.
https://forum.xda-developers.com/one-m9/help/removing-demo-content-t3063179
Click to expand...
Click to collapse
Unfortunately the links on that post no longer exist.
But if I find the firmware and flash, it'll remove the demo, is that correct understood?

elmalote said:
Unfortunately the links on that post no longer exist.
But if I find the firmware and flash, it'll remove the demo, is that correct understood?
Click to expand...
Click to collapse
From what I read in that thread provided, yes.

elmalote said:
Hi guys
I'm having an issue with my M) unit. It's a Demo unit and I have S-OFF using sunshine and SuperCid.
Installed TRWP and restored bonesy stock backup, but the demo software is still present.
I though changing the CID was enough as CID 02 was triggering it.
But it's not the case.
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
If you're looking to change your device SKU, your CID and MID have to match. SuperCID is no accepted by HTC's software packages (RUUs and OTAs). Check out the Readme thread for everything you need.

computerslayer said:
If you're looking to change your device SKU, your CID and MID have to match. SuperCID is no accepted by HTC's software packages (RUUs and OTAs). Check out the Readme thread for everything you need.
Click to expand...
Click to collapse
So if I want to change my SKU, I need to change the CID to HTC__F08 (which is the Danish one) and what about the MID?
I have read the ReadMe, but I'm not sure how they are related and what needs to be done with the MID.
I want to restore this one https://forum.xda-developers.com/on...m9-4-14-617-6-stock-root-twrp-backup-t3518149 and use it without the Demo software.

elmalote said:
So if I want to change my SKU, I need to change the CID to HTC__F08 (which is the Danish one) and what about the MID?
I have read the ReadMe, but I'm not sure how they are related and what needs to be done with the MID.
I want to restore this one https://forum.xda-developers.com/on...m9-4-14-617-6-stock-root-twrp-backup-t3518149 and use it without the Demo software.
Click to expand...
Click to collapse
Maybe I'm missing something but you're S-OFF so what you're planning to do at the moment doesn't make any sense. Why do you want to use a 617 system/backup on a 401 firmware? Change your MID and your CID to the ones that belong to SKU 617 and flash the latest 617 RUU. (Be aware that you can't use 4.x RUUs if your still using firmware 3.x or below. In that case you need to use a 3.x RUU for SKU 617 and install the OTAs via the software update function, afterwards.) This way you minimize lags and bugs that may arise if firmware version and system version mismatch. And not to forget that you'll be able to install future OTAs which you wouldn't be able to do if you just restore the backup you linked in your last post.
Alternatively (if you want to keep the European SKU), you simply need to flash the 3.35.401.12 RUU and to install the OTAs for the European android N update. However, you need to be aware that CID HTC__F08 doesn't exist on the M9 (as far as I know). The by SKU 401 supported CIDs are HTC__001, HTC__J15, HTC__102, HTC__Y13, HTC__A07, HTC__032, HTC__016, HTC__M27, HTC__002 and HTC__031. So you need to change your current CID to one of those that got mentioned in the last sentence or you won't be able to flash the RUU.

Flippy498 said:
Maybe I'm missing something but you're S-OFF so what you're planning to do at the moment doesn't make any sense. Why do you want to use a 617 system/backup on a 401 firmware? Change your MID and your CID to the ones that belong to SKU 617 and flash the latest 617 RUU. (Be aware that you can't use 4.x RUUs if your still using firmware 3.x or below. In that case you need to use a 3.x RUU for SKU 617 and install the OTAs via the software update function, afterwards.) This way you minimize lags and bugs that may arise if firmware version and system version mismatch. And not to forget that you'll be able to install future OTAs which you wouldn't be able to do if you just restore the backup you linked in your last post.
Alternatively (if you want to keep the European SKU), you simply need to flash the 3.35.401.12 RUU and to install the OTAs for the European android N update. However, you need to be aware that CID HTC__F08 doesn't exist on the M9 (as far as I know). The by SKU 401 supported CIDs are HTC__001, HTC__J15, HTC__102, HTC__Y13, HTC__A07, HTC__032, HTC__016, HTC__M27, HTC__002 and HTC__031. So you need to change your current CID to one of those that got mentioned in the last sentence or you won't be able to flash the RUU.
Click to expand...
Click to collapse
Yes I am S-OFF.
Basically I just want stock software, everything stock. Also the recovery. I just dont want the demo software.
I have 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 can I just flash this or is it not possible? I have flashed ICE M9 custom ROM right now.
I can't fint the 3.35.401.12 RUU anywhere :/ only the ZIP, is it usable?
Thanks a lot for your help.

The *.exe files are nothing more than the *.zip files with a fancy installer that flashes the *. zip via htc_fastboot.
Read the ReadMe thread. It contains flashing instructions for the *.zip files.
Sent from my HTC One S using XDA Labs