Develop Bugs

Super CID ? ?

M8 ul, HTC__001, 2.22.401.05
S-off, rooted, unlocked bootloader
If I super cid my handset does that mean I can use ANY RUU suitable for "international m8" even if the RUU has an older hboot and firmware ?
Currently on ARHD 11.1 and trying to work out best, and easiest, way to get back for stock for OTA "L" update when it comes.
Thanks
Sent from my unknown using XDA Free mobile app

I believe the super CID means you can install any RUU period - sort of like a skeleton key. It's then up to you to make sure that you are installing an appropriate version.
If you just need to go back to stock, however, you only need a CID for your carrier/region (or developer edition) and the appropriate RUU.

jshamlet said:
I believe the super CID means you can install any RUU period - sort of like a skeleton key.
Click to expand...
Click to collapse
It won't allow you to "downgrade" or run an RUU with a lower hboot number. Although s-off will allow this.
To the OP, does a RUU for any international M8 even exist? AFAIK only US variants have RUUs. You will probably have to find your carrier's nandroid, and stock recovery to return to stock for OTA.
But if you are willing to flash custom ROMs, there will probably be custom ROMs based on Android "L" soon after it starts rolling out OTA. Possibly even faster than waiting for your carrier version.

redpoint73 said:
It won't allow you to "downgrade" or run an RUU with a lower hboot number. Although s-off will allow this.
To the OP, does a RUU for any international M8 even exist? AFAIK only US variants have RUUs. You will probably have to find your carrier's nandroid, and stock recovery to return to stock for OTA.
But if you are willing to flash custom ROMs, there will probably be custom ROMs based on Android "L" soon after it starts rolling out OTA. Possibly even faster than waiting for your carrier version.
Click to expand...
Click to collapse
Will, more than likely, use mikes "version" of L when released. Main reason I want to get OTA update is so my firmware is updated for L.
My handset is not locked to any carrier, sim free UK handset.
Thanks
Edit, was just curious as to the benefits of super cid. I've got my own "complete" nandroid, no missing data, so as I was told by mr hofs yesterday all I need to do is flash one of his stock recoveries.
Sent from my unknown using XDA Free mobile app

[Q] Steps to convert to Dev Edition from AT&T?

I'm currently bone-stock AT&T, 4.4.2. I'm frustrated by the lack of OTAs from AT&T, especially given that the 4.4.4 was reportedly pulled. So I'm considering converting to Dev Edition to get timely updates and I'd like to make sure I have all of my ducks in a row before I begin.
Am I correct with these steps and order?
1. Unlock bootloader (htcdev key)
2. s-off
3. Change MID and CID as appropriate
4. Run the 5.0.1 RUU that HTC posted
5. ???
6. Profit
Thanks!

Close
Skip HTCDev, because Sunshine will take care of that for you. Once you are S-off, you can trivially lock/unlock your bootloader, and by skipping HTCDev, you can potentially avoid losing your warranty.

jshamlet said:
Close
Skip HTCDev, because Sunshine will take care of that for you. Once you are S-off, you can trivially lock/unlock your bootloader, and by skipping HTCDev, you can potentially avoid losing your warranty.
Click to expand...
Click to collapse
I literally just saw (and did) this with Sunshine. Thanks for the tip. Everything else looks good on the list though, right?

OGhoul said:
I literally just saw (and did) this with Sunshine. Thanks for the tip. Everything else looks good on the list though, right?
Click to expand...
Click to collapse
Yup, except I forgot to mention that you only have to change the CID. The MID is already correct. (The Developer Edition is essentially the same as the AT&T edition, but has a different CID)
You would have figured that out on your own, and it wouldn't have hurt to attempt to change it, but it's not necessary on your device.

jshamlet said:
Yup, except I forgot to mention that you only have to change the CID. The MID is already correct. (The Developer Edition is essentially the same as the AT&T edition, but has a different CID)
You would have figured that out on your own, and it wouldn't have hurt to attempt to change it, but it's not necessary on your device.
Click to expand...
Click to collapse
I've already got the tabs open for the adb steps for that on my home PC. Thanks a bunch; you've confirmed that I actually have learned something from lurking around here all this time.

I have the Tmobile version. Will this same thing work as well, just changing the CID and flashing the 5.0.1 RUU?
I already have S-Off and unlocked bootloader. Everything else is the same from when I got it. Stock 4.4.4 Sense, Stock recovery (No CWM or TWRP), with T-Mobile CID.

vjaamm said:
I have the Tmobile version. Will this same thing work as well, just changing the CID and flashing the 5.0.1 RUU?
I already have S-Off and unlocked bootloader. Everything else is the same from when I got it. Stock 4.4.4 Sense, Stock recovery (No CWM or TWRP), with T-Mobile CID.
Click to expand...
Click to collapse
Yes, except you *DO* have to change your MID.
http://forum.xda-developers.com/showthread.php?t=2708581

And slightly off topic, the 5.0.1 RUU will update my firmware to what would be required for any of the (Sense-based) Lollipop ROMS (like ARHD) right? I won't have to incrementally flash firmwares, will I?

OGhoul said:
And slightly off topic, the 5.0.1 RUU will update my firmware to what would be required for any of the (Sense-based) Lollipop ROMS (like ARHD) right? I won't have to incrementally flash firmwares, will I?
Click to expand...
Click to collapse
No you won't. The Developer edition has the latest firmware needed by the latest ROMs 4.x
So you'll be good to go.

I actually had to do some monkey business to get this to work.
I changed my CID to Super CID, then adb fastboot bootloader. Then ran the RUU .exe. This started to work, however it failed at I think step 5 telling me my CID was wrong, and the .exe told me to hold power for 10 seconds to reboot.
This then booted back into 4.4.2, and settings > about still said 4.4.2.
fastboot getvar all however, revealed all of the lollipop firmware settings.
So I rebooted to fastboot again, then changed my CID to the BS_US002.
Ran the RUU again. It took, and it's currently optimizing apps.

[Q] Converting to GPE (CID/MID)

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

[Q] Changing from unlocked (617) to international (401) with s-off

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!

[Q] I need help HTC One M8 AT&T

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.