I converted my SIM Free GSM HTC One M8 to a GPE at the end of December.
Everything works and I'm really enjoying the experience.
However, I have since found out that I needed to change the MID and the CID. All I did was change the CID to GOOGL001. Will I receive OTA's from Google and will they install properly or do I also need to change the MID? Thanks
Goldenears2015 said:
I converted my SIM Free GSM HTC One M8 to a GPE at the end of December.
Everything works and I'm really enjoying the experience.
However, I have since found out that I needed to change the MID and the CID. All I did was change the CID to GOOGL001. Will I receive OTA's from Google and will they install properly or do I also need to change the MID? Thanks
Click to expand...
Click to collapse
best to change the MID too, its just as easy to change the MID as the CID.
Goldenears2015 said:
I converted my SIM Free GSM HTC One M8 to a GPE at the end of December.
Everything works and I'm really enjoying the experience.
However, I have since found out that I needed to change the MID and the CID. All I did was change the CID to GOOGL001. Will I receive OTA's from Google and will they install properly or do I also need to change the MID? Thanks
Click to expand...
Click to collapse
Your going to want to change the MID to match GPE and when your ready to take the OTA your going to want the stock recovery that matches the current OS your on.
Also make sure your system is not modified at all for instance (platform.xml) witch most people have altered when they use "sdcardfix" app for read/write permissions
Will the OTA just fail without the correct MID or will it brick the phone?
I don't have access to a PC at the moment, just a Chromebook. To change the MID, do I need root access? I've downloaded the terminal Emulator for Android but it says device not found.
Yes you need to change the MID.
yes you will need root .I'm not familiar with the chromebook so I'm not sure
For OTA updates you definitely need the CID, I didn't need to change MID when I was converted
EddyOS said:
For OTA updates you definitely need the CID, I didn't need to change MID when I was converted
Click to expand...
Click to collapse
Thanks for the reply. Did you update to Lollipop from KitKat through an OTA after conversion? also, is your M8 a UK model? The reason I'm asking is because if I can avoid changing the MID I will. It was a bit of a headache converting it in the first place.
Yes to the above. The OTA files seem to work with all MIDs but the CID is crucial otherwise the FW won't flash
I've converted to GPE two times and each time I ruu the earliest ruu so I could OTA up to the latest firmware/version (I followed the guide 100% and it included changing the MID)
I also change the CID to the specific variant it's supposed to be .I recently converted back to Sense Dev edition and changed everything to match so I could update to Dev lollipop, now I run the Dev lollipop firmware with a stock GPE lollipop ROM and it's great
EddyOS said:
Yes to the above. The OTA files seem to work with all MIDs but the CID is crucial otherwise the FW won't flash
Click to expand...
Click to collapse
That's good news, I'll leave it as is then, the CID is GOOGL001 .
jball said:
I've converted to GPE two times and each time I ruu the earliest ruu so I could OTA up to the latest firmware/version (I followed the guide 100% and it included changing the MID)
I also change the CID to the specific variant it's supposed to be .I recently converted back to Sense Dev edition and changed everything to match so I could update to Dev lollipop, now I run the Dev lollipop firmware with a stock GPE lollipop ROM and it's great
Click to expand...
Click to collapse
I was looking at a GPE ROM yesterday and tbh, I was thinking that it should be the official ROM because of the additional features and extra settings available.
This is the ROM I used up until two days ago.
http://forum.xda-developers.com/showthread.php?t=2706441
Now I'm checking out Liquidsmooth 5.0.2
Related
Hello all. I converted my m8 to gpe using @graffixnyc's conversion rom. Purposely older rom (non-rooted 5.0.1) used to see if OTA will work. CID is changed to GOOGL001 but mid leaved untouched. Evertything works but phone does not receive OTA. Is there some certain mid that should be used to reveive updates ?
Thanks in advance.
The MID is 0P6B11000.
Yes you'll need it for OTAs
Thanks for quick reply ! When looking for instructions to change the MID I found also another mid (OP6B17000) for gpe m8. Just wondering if there are different hardware editions of gpe available ? Cdma/gsm ?
Hey guys,
I own an original unlocked M9 (1.32.617.30) and want to convert it to the international model for the quicker updates.
Just got it S-OFF and wanted to make sure I got the rest of the steps right:
1. Change MID to 0PJA10000
2. Change CID to 11111111 (or to HTC__001? which is better?)
3. Run 1.32.401.17 RUU (is it possible to run 1.40.401.8 RUU instead? or do I need to flash a 1.32 base first?)
Cheers! Trying to avoid a bricked phone :angel:
Jhonys said:
Hey guys,
I own an original unlocked M9 (1.32.617.30) and want to convert it to the international model for the quicker updates.
Just got it S-OFF and wanted to make sure I got the rest of the steps right:
1. Change MID to 0PJA10000
2. Change CID to 11111111 (or to HTC__001? which is better?)
3. Run 1.32.401.17 RUU (is it possible to run 1.40.401.8 RUU instead? or do I need to flash a 1.32 base first?)
Cheers! Trying to avoid a bricked phone :angel:
Click to expand...
Click to collapse
Who is your carrier?
You shouldn't need to change your mid. Just change to super cid and you can flash the latest firmware and any custom rom you want.
If you're AT&T, the 401 firmware should work seamlessly, you just probably will not get voLte. If you're tired mobile, 401 firmware should also work, but no Wi-Fi calling (you should confirm this because I'm really not sure). If you're Verizon or Sprint, I have no idea, but I think you're sol and have to wait until they release an update. .
Edit: nevermind about carrier stuff. Didn't see that you have dev edition. 401 firmware should all work.
jollywhitefoot said:
Who is your carrier?
You shouldn't need to change your mid. Just change to super cid and you can flash the latest firmware and any custom rom you want.
If you're AT&T, the 401 firmware should work seamlessly, you just probably will not get voLte. If you're tired mobile, 401 firmware should also work, but no Wi-Fi calling (you should confirm this because I'm really not sure). If you're Verizon or Sprint, I have no idea, but I think you're sol and have to wait until they release an update. .
Edit: nevermind about carrier stuff. Didn't see that you have dev edition. 401 firmware should all work.
Click to expand...
Click to collapse
I'm not in the US, but europe. I've bought the phone through HTC US and that's why i'm on 617.
Regarding the MID, it is only because it is listed as a step here: http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
And when you say "flash latest firmware" what do you mean exactly? should I install 1.40 RUU or 1.32.401.17 RUU first? I really want to know Im flashing the right file now that i'm S-OFF.
Jhonys said:
I'm not in the US, but europe. I've bought the phone through HTC US and that's why i'm on 617.
Regarding the MID, it is only because it is listed as a step here: http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
And when you say "flash latest firmware" what do you mean exactly? should I install 1.40 RUU or 1.32.401.17 RUU first? I really want to know Im flashing the right file now that i'm S-OFF.
Click to expand...
Click to collapse
Gotcha. I didn't understand your desires. I thought you were basically asking how to upgrade your firmware and flash a rom. Probably you should ask in that thread and maybe clsA or someone else in that thread can give you specific advise. I assume you're looking to convert to stock 401/0PJA10000 and receive official otas?
This might help you as well.. its an A,B, C ... guide
http://www.droidviews.com/how-to-restore-htc-one-m9-to-stock/
From what Im aware, I thought Sunshine 3.17 only supports 501... arent we on 502?
Thanks guys I followed the guide from clsA and it worked perfectly. :good:
Yup! If you have a GSM M-9 than it's easy as pie! S-OFF, Super CID, Flash Firmware, Flash Rom! BAM! DONE!
I am using AT & T HTC M8 S - OFF super CID. Can I install this recovery ?
[ROM][5.1] 9/17/2015-Lollipop Stock Rooted Google Play Edition LMY47O.H9
HTML:
http://forum.xda-developers.com/showthread.php?t=2706441
thanks alot!!!!! :good::good::good:
That's not a recovery, it's a ROM !
Mr Hofs said:
That's not a recovery, it's a ROM !
Click to expand...
Click to collapse
yes. i'm sorry but can i use it??
The short answer is yes. However, the longer answer is yes, but you need to think carefully about this before pulling the trigger.
Some people repartition their phones to fully convert to the GPE version, but I don't recommend this unless you are either certain you want a GPE ROM or are highly skilled in this area. In your case, since you aren't certain, I would install without altering your partitions. From what I read in the first post, it appears this ROM simply rewrites your existing Sense partitions with GPE code, so it should be perfectly safe.
Also, make sure you note the required firmware version. AT&T has released a Lollipop version of their ROM, so if you aren't sure, you might consider running their RUU as a way to ensure you have compatible firmware. (since you are S-off, you can also use the Developer Edition RUU, but since you are converting to GPE, it really doesn't matter) Attempting to run a Lollipop GPE build with KitKat firmware will not work well.
jshamlet said:
The short answer is yes. However, the longer answer is yes, but you need to think carefully about this before pulling the trigger.
Some people repartition their phones to fully convert to the GPE version, but I don't recommend this unless you are either certain you want a GPE ROM or are highly skilled in this area. In your case, since you aren't certain, I would install without altering your partitions. From what I read in the first post, it appears this ROM simply rewrites your existing Sense partitions with GPE code, so it should be perfectly safe.
Also, make sure you note the required firmware version. AT&T has released a Lollipop version of their ROM, so if you aren't sure, you might consider running their RUU as a way to ensure you have compatible firmware. (since you are S-off, you can also use the Developer Edition RUU, but since you are converting to GPE, it really doesn't matter) Attempting to run a Lollipop GPE build with KitKat firmware will not work well.
Click to expand...
Click to collapse
yes thank you very much. I just installed this ROM. first boot times appeared broken and I had to factory reset. so far has not detected any errors.
I used the AT & T version of the ROM, but I feel uncomfortable because of the bundled applications, which I never use because I was in Vietnam. So how to completely remove them?
minhtienls said:
yes thank you very much. I just installed this ROM. first boot times appeared broken and I had to factory reset. so far has not detected any errors.
I used the AT & T version of the ROM, but I feel uncomfortable because of the bundled applications, which I never use because I was in Vietnam. So how to completely remove them?
Click to expand...
Click to collapse
Since you have the AT&T variant, and you are S-off, this is easy. Install the Developer Edition RUU. They are the exact same phone (same MID) but the Developer Edition doesn't have any of the AT&T bloat.
You may have to change the CID back to match one or the other of the unlocked/developer phones for the RUU to install. (either BS_US001 for unlocked or BS_US002 for developer edition) but you don't have to alter the MID at all.
If you don't root, you will get OTA updates directly from HTC.
As an aside, you might also try the WWE (world-wide English) variant as well, though that WILL require altering the MID.
jshamlet said:
Since you have the AT&T variant, and you are S-off, this is easy. Install the Developer Edition RUU. They are the exact same phone (same MID) but the Developer Edition doesn't have any of the AT&T bloat.
You may have to change the CID back to match one or the other of the unlocked/developer phones for the RUU to install. (either BS_US001 for unlocked or BS_US002 for developer edition) but you don't have to alter the MID at all.
Click to expand...
Click to collapse
I agree, if the OP wants a relatively clean, unbranded Sense setup (including official OTAs, and band support same as AT&T version) that the Dev Edition RUU is the way to go.
OP stated the phone is SuperCID, so no need to change CID (and I'd recommend not to change the CID to flash the Dev Ed RUU
Although GPE and Sense are two completely different animals. Not sure if the OP prefers one or the other? Although OP's last post did make it sound like they wanted a Sense ROM, just without AT&T branding.
As an aside, I don't see the utility in super CID anymore. It no longer "unlocks" anything (you don't get a free SIM unlock), so really the only advantage is being able to install any another HTC ROM via RUU. On the flip side, super CID blocks OTA updates on official ROMs, which makes it more of a disadvantage now.
Since most people are going to need a specific HTC ROM (for band support), or they are going to go with a third-party ROM which doesn't care what your CID is, I'd actually suggest using the CID/MID for the appropriate Sense ROM instead of super CID to ensure there aren't problems down the road. If you do, your phone essentially becomes that model for all intents and purposes.
(The obvious exception being Sprint/Verizon devices, but that isn't applicable here)
jshamlet said:
super CID blocks OTA updates on official ROMs, which makes it more of a disadvantage now.
Click to expand...
Click to collapse
You sure of that? I've seen folks say that a lot, but others also contradict the statement. ckpv5 in particular, and that guy knows his stuff. He's stated it a number of times (SuperCID does not prevent OTA); just yesterday, in fact: http://forum.xda-developers.com/showpost.php?p=63075776&postcount=9
But I agree that SuperCID is very limited in its usefulness (since MID is also a requirement, and there are so many different MIDs) and probably only in specific circumstances. For instance, I made my M8 SuperCID to install the Dev Ed RUU, and be able to RUU back to ATT if I wanted. But also, like you mentioned, I also run custom ROMs often, in which case CID is fairly irrelevant.
In the OP's case, as long as SuperCID doesn't block OTA, it saves him from changing the CID (although its just a single fastboot command) and also go back to ATT if desired.
SuperCID is probably pretty useful for Euro M8 owners, as there are a ton of CIDs for the same MID.
redpoint73 said:
You sure of that? I've seen folks say that a lot, but others also contradict the statement. ckpv5 in particular, and that guy knows his stuff. He's stated it a number of times (SuperCID does not prevent OTA); just yesterday, in fact: http://forum.xda-developers.com/showpost.php?p=63075776&postcount=9
But I agree that SuperCID is very limited in its usefulness (since MID is also a requirement, and there are so many different MIDs) and probably only in specific circumstances. For instance, I made my M8 SuperCID to install the Dev Ed RUU, and be able to RUU back to ATT if I wanted. But also, like you mentioned, I also run custom ROMs often, in which case CID is fairly irrelevant.
In the OP's case, as long as SuperCID doesn't block OTA, it saves him from changing the CID (although its just a single fastboot command) and also go back to ATT if desired.
SuperCID is probably pretty useful for Euro M8 owners, as there are a ton of CIDs for the same MID.
Click to expand...
Click to collapse
I've read conflicting reports on SuperCID blocking OTA updates as well, so he may very well be right. I will say that when I first installed the KitKat DevEd ROM, it appeared to refuse to download the OTA update to 4.4.4 until I reverted to using the official CID (BS_US002), but it's also possible that I just didn't wait long enough. Maybe that has changed since Lollipop?
If it really doesn't block OTA updates, then it's probably a pure don't care. If you are S-off, it's a trivial change. Also, if you are rooted, it's a moot issue anyway, as that is more likely to foul up OTA updates than the CID.
jshamlet said:
I've read conflicting reports on SuperCID blocking OTA updates as well, so he may very well be right. I will say that when I first installed the KitKat DevEd ROM, it appeared to refuse to download the OTA update to 4.4.4 until I reverted to using the official CID (BS_US002), but it's also possible that I just didn't wait long enough. Maybe that has changed since Lollipop?
If it really doesn't block OTA updates, then it's probably a pure don't care. If you are S-off, it's a trivial change. Also, if you are rooted, it's a moot issue anyway, as that is more likely to foul up OTA updates than the CID.
Click to expand...
Click to collapse
SuperCID doesn't block OTAs. It allows you to flash firmware for any CID without the need to change it. The CID works with all.
Since the OP is S-Off, I would suggest using WWE/International firmware. It's updated sooner if a Sense ROM is what he is after. OP could run MaximusHD if he wishes to remain Stock.
Hi all,
I have recently surrendered and got s-off using sunshine.
I managed to RUU the AT&T ROM, but I want to get a clean unbranded ROM, that is unrooted - basically a factory-reset unbranded phone.
is that possible?
every RUU except the ATT one doesnt work for me...
thanks in advance.
mishumashu said:
every RUU except the ATT one doesnt work for me...
Click to expand...
Click to collapse
You'll need to change the CID and MID to run another carrier's RUU.
Alternately, instead of an RUU, you can flash a custom ROM, or stock ROM (such as stock DevEd MM ROM posted in Development), which will work fine on LP firmware. This would require an unlocked bootloader and custom recovery.
redpoint73 said:
You'll need to change the CID and MID to run another carrier's RUU.
Alternately, instead of an RUU, you can flash a custom ROM, or stock ROM (such as stock DevEd MM ROM posted in Development), which will work fine on LP firmware. This would require an unlocked bootloader and custom recovery.
Click to expand...
Click to collapse
is there any risk involved in changing my MID to a Europe one assuming the device is AT&T from the US?
any danger in running that RUU?
I already have TWRP and am unlocked.
Forgot to mention that because of my work I cant use a custom ROM (had Viper till now)..
mishumashu said:
is there any risk involved in changing my MID to a Europe one assuming the device is AT&T from the US?
any danger in running that RUU?
Click to expand...
Click to collapse
As long as you follow the instruction carefully and exactly, there is little risk in changing the CID and MID. For the MID in particular, be sure to get the location correct for the parameter you are changing (the instructions advise to cut and paste the command, to prevent a typo) otherwise you can do some permanent damage.
Once you've changed to the proper CID, MID, running the Euro RUU is not any more risk than running an AT&T one. The phones are the same in hardware.
redpoint73 said:
As long as you follow the instruction carefully and exactly, there is little risk in changing the CID and MID. For the MID in particular, be sure to get the location correct for the parameter you are changing (the instructions advise to cut and paste the command, to prevent a typo) otherwise you can do some permanent damage.
Once you've changed to the proper CID, MID, running the Euro RUU is not any more risk than running an AT&T one. The phones are the same in hardware.
Click to expand...
Click to collapse
cool, will give it a go, thanks!
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