I have a T-Mobile HTC One (MID PN0713000) and I have been trying to test if my HSDPA on AWS band would work if I flashed a Dev Edition RUU. (I know there wouldn't be a way back without a T-Mobile RUU if I did lose the band, but that's fine.)
My problem is that the RUU is failing even though I have changed my CID to BS_US001 (Dev Edition CID) because my model ID doesn't match. Developer Edition (and AT&T) MID is PN0712000 versus my PN0713000, so it is not allowing the RUU to run. And even if it did, you can't get OTAs without a matching MID, so it would defeat the purpose of flashing a different RUU anyways.
So my question is, besides some modified HBOOT methods that I've seen, that I'm not in the mood to try due to a high risk of bricking the device, is there any way to change the Model ID of the device?
With Super CID you can flash any RUU but you will have the issue you said regarding the MID come OTA time...
EddyOS said:
With Super CID you can flash any RUU but you will have the issue you said regarding the MID come OTA time...
Click to expand...
Click to collapse
That's why I wanna see if there is a way to change the MID. Only point of flashing a Dev or Euro RUU for me would be to have a stock device but still get OTAs faster. And same would apply to the Google RUU if/when it comes out, which will also probably be a different MID.
I understand that the only differences between HTC One and developer edition is the storage and the unlocked bootloader. I have got HTC Unlocked International Edition (32 GB) from Amazon. Now the KitKat update is going to be released 60 days earlier to the dev edition. Is there a way to convert to a dev edition to receive future updates faster? Would unlocking the bootloader turn the phone into a dev edition? Or those handsets receive the updates according to IME, serial or something? Thanks in advance!
Here's the short version on how to properly convert to Dev Edition and retain future OTA updates. Make sure to back up any data or files on the phone you don't want to lose, as this will wipe your phone and make it like new. Find your current APN settings and write them down just in case your carrier isn't shown as an option when first booting your phone after converting.
Unlock bootloader via HTCDev.com
S-Off (method varies depending on bootloader version, but most would use Rumrunner)
Change CID to BS_US001
If your MID is anything other than PN712000, change it to that.
Run RUU exe file for Dev Edition (available for download on HTCDev.com)
You can leave the bootloader unlocked and S-Off.
EsJayEs said:
Here's the short version on how to properly convert to Dev Edition and retain future OTA updates. Make sure to back up any data or files on the phone you don't want to lose, as this will wipe your phone and make it like new. Find your current APN settings and write them down just in case your carrier isn't shown as an option when first booting your phone after converting.
Unlock bootloader via HTCDev.com
S-Off (method varies depending on bootloader version, but most would use Rumrunner)
Change CID to BS_US001
If your MID is anything other than PN712000, change it to that.
Run RUU exe file for Dev Edition (available for download on HTCDev.com)
You can leave the bootloader unlocked and S-Off.
Click to expand...
Click to collapse
Will this method change to developer edition and will ensure future OTA released for the Developer Edition? Thanks!
Yes it will get OTA , if the last step is to run RUU for Dev edition.
If you install custom recovery/root on top of it, then you will have isssues with OTA.
EsJayEs said:
Here's the short version on how to properly convert to Dev Edition and retain future OTA updates. Make sure to back up any data or files on the phone you don't want to lose, as this will wipe your phone and make it like new. Find your current APN settings and write them down just in case your carrier isn't shown as an option when first booting your phone after converting.
Unlock bootloader via HTCDev.com
S-Off (method varies depending on bootloader version, but most would use Rumrunner)
Change CID to BS_US001
If your MID is anything other than PN712000, change it to that.
Run RUU exe file for Dev Edition (available for download on HTCDev.com)
You can leave the bootloader unlocked and S-Off.
Click to expand...
Click to collapse
Do I have to change to SuperCID at any stage?
No you do not. As per the post from EsJayEs , you only need to change CID to BS_US001
To add to that, there's no reason to ever use superCID. It's takes less than a minute to change your CID. And this is part of what ensures you receive OTA updates.
EsJayEs said:
To add to that, there's no reason to ever use superCID. It's takes less than a minute to change your CID. And this is part of what ensures you receive OTA updates.
Click to expand...
Click to collapse
Thanks... It seems like it's not so common for people to convert to Developer Edition, all the search results I'm getting is about converting to-from GPE. Is that so uncommon right?
It's fairly common. For people on carrier branded phones that like the Sense user interface, the options are Dev Edition or International. Dev Edition has the advantage of significantly faster updates. International version has no real advantage that I know of. At the moment, the international version has a newer version of Sense, but they'll be waiting until January for Android 4.4. But those using the Dev Edition should receive that update any day now (including the updated version of Sense).
EsJayEs said:
It's fairly common. For people on carrier branded phones that like the Sense user interface, the options are Dev Edition or International. Dev Edition has the advantage of significantly faster updates. International version has no real advantage that I know of. At the moment, the international version has a newer version of Sense, but they'll be waiting until January for Android 4.4. But those using the Dev Edition should receive that update any day now (including the updated version of Sense).
Click to expand...
Click to collapse
Thanks!
I have the international version, but I will convert to Dev Ed once the 4.4 update (RUU) is released. Usually when the OTA update is released, the RUU is released at the same time? This is my first HTC phone, so I'm clueless
Hard to say. If they release the RUU, it could be a few days or weeks after the OTA is being pushed. But the OTA will almost definitely come first. If you were to convert now, you'd have verification that your work was done properly when the OTA is pushed and successfully installs.
EsJayEs said:
Hard to say. If they release the RUU, it could be a few days or weeks after the OTA is being pushed. But the OTA will almost definitely come first. If you were to convert now, you'd have verification that your work was done properly when the OTA is pushed and successfully installs.
Click to expand...
Click to collapse
Good to know, I'd start converting then once I hear the OTA is being pushed to find out the result of the conversion quickly. Thanks a lot for all your help!
EsJayEs said:
Here's the short version on how to properly convert to Dev Edition and retain future OTA updates. Make sure to back up any data or files on the phone you don't want to lose, as this will wipe your phone and make it like new. Find your current APN settings and write them down just in case your carrier isn't shown as an option when first booting your phone after converting.
Unlock bootloader via HTCDev.com
S-Off (method varies depending on bootloader version, but most would use Rumrunner)
Change CID to BS_US001
If your MID is anything other than PN712000, change it to that.
Run RUU exe file for Dev Edition (available for download on HTCDev.com)
You can leave the bootloader unlocked and S-Off.
Click to expand...
Click to collapse
Sorry to bother you again with my questions!
At any point do I need to install a custom recovery? I'm not going to root at the moment. What's the best and easy method to install/flash the RUU?
Sent from my HTC One using XDA Premium 4 mobile app
You will need to custom recovery & root to gain S-Off, but once you have ran the dev RUU and the phone is converted, you will not need to root/recovery again.
M_Shaaban said:
Sorry to bother you again with my questions!
At any point do I need to install a custom recovery? I'm not going to root at the moment. What's the best and easy method to install/flash the RUU?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You do not need to install custom recovery.or root. Once you have S-Off (download and use the latest version of Rumrunner http://rumrunner.us/downloads-2/ for this), change your CID to BS_US001 and change your MID to PN712000.
Change your MID using the information here http://forum.xda-developers.com/showthread.php?t=2322820
Changing your CID using the Fastboot command
Code:
fastboot oem writecid BS_US001
After that, run the RUU program downloaded from here http://dl4.htc.com/RomCode/Source_a...3_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe
Again, custom recovery and root are not required (or even useful) for this process. I strongly prefer not to use any custom recovery because it makes future OTA updates impossible.
EsJayEs said:
You do not need to install custom recovery.or root. Once you have S-Off (download and use the latest version of Rumrunner http://rumrunner.us/downloads-2/ for this), change your CID to BS_US001 and change your MID to PN712000.
Change your MID using the information here http://forum.xda-developers.com/showthread.php?t=2322820
Changing your CID using the Fastboot command
Code:
fastboot oem writecid BS_US001
After that, run the RUU program downloaded from here http://dl4.htc.com/RomCode/Source_a...3_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe
Again, custom recovery and root are not required (or even useful) for this process. I strongly prefer not to use any custom recovery because it makes future OTA updates impossible.
Click to expand...
Click to collapse
Thanks again for your response, the MID is mentioned in other posted slightly different than the one you mentioned here - PN0712000. Which one is correct? Or is there no difference between PN712000 and PN0712000? My current MID is PN0714000
Sent from my HTC One using XDA Premium 4 mobile app
Also do I need to relock the bootloader at any stage of the process?
Rumrunner S-OFF must have the phone rooted and requires custom recovery. Can I unroot and install stock recovery before flashing the RUU? Or Installing the RUU will overwrite the custom recovery and installing stock recovery and removing root? If I have to flash the stock recovery to overwrite the custom one, how to do so? Where can I find the compatible latest version of stock recovery?
Do I need to downgrade the hboot at any point? I'm running Windows 8.1 -if that's relevant.
Thanks a lot again for all your help!
Sent from my HTC One using XDA Premium 4 mobile app
M_Shaaban said:
Also do I need to relock the bootloader at any stage of the process?
Click to expand...
Click to collapse
As long as you're S-Off, no you don't. I highly recommend, you do not go back to S-On!!
M_Shaaban said:
Rumrunner S-OFF must have the phone rooted and requires custom recovery. Can I unroot and install stock recovery before flashing the RUU? Or Installing the RUU will overwrite the custom recovery and installing stock recovery and removing root? If I have to flash the stock recovery to overwrite the custom one, how to do so? Where can I find the compatible latest version of stock recovery?
Click to expand...
Click to collapse
Installing RUU, will wipe everything, and install everything back to stock (hboot, recovery, firmware, rom).
M_Shaaban said:
Do I need to downgrade the hboot at any point?
Click to expand...
Click to collapse
If running the RUU gives error 155, then downgrade to hboot 1.44 first; you'll get error 155 on hboot 1.55+
M_Shaaban said:
I'm running Windows 8.1 -if that's relevant.
Click to expand...
Click to collapse
If you have problems with fastboot and/or adb might be best to use Win7. Win8 and 8.1 are known to sometimes have "issues"
nkk71 said:
As long as you're S-Off, no you don't. I highly recommend, you do not go back to S-On!!
Installing RUU, will wipe everything, and install everything back to stock (hboot, recovery, firmware, rom).
If running the RUU gives error 155, then downgrade to hboot 1.44 first; you'll get error 155 on hboot 1.55+
If you have problems with fastboot and/or adb might be best to use Win7. Win8 and 8.1 are known to sometimes have "issues"
Click to expand...
Click to collapse
Thanks a lot for your response! Just to confirm MID for HTC One Developer Edition is it PN712000 or PN0712000? Or there is no difference.
M_Shaaban said:
Thanks a lot for your response! Just to confirm MID for HTC One Developer Edition is it PN712000 or PN0712000? Or there is no difference.
Click to expand...
Click to collapse
yes it makes a difference
It's PN0712000
http://xda7.androidrevolution.nl/db_mirror/ROMs/HTC_One/variants.png
and iirc correctly, you may need to use an engineering hboot to change mid, if the normal hboot doesnt work.
EDIT: an be careful with engineering hboot, they have some very powerful commands, that could brick your phone. i think there's a guide somewhere around here, but i don't have the link right now
I am wondering if rumrummer's at&t hboot (3.17.502.3) is compatible with dev edition (US_BS001).
As far as I know, hardware/partition layout, etc is the same- so if I Supercid or change CID or edit android-info.txt, will it work? Do I need to flash at&t 3.17.502.3 firmware first? (I am already s-off revone, hboot 1.44...)
If it doesn't boot after, can I get into RUU mode and just flash stock/backed-up hboot (in firmware.zip, android-info.txt, etc)?
Thanks @beaups @Fuses for hard work! I will donate if I get working hboot...
(I don't have access yet to post in dev forums...)
Hboot is universal as long as it's from the same network version.
You'll need supercid to flash unsigned firmware zips, but you can use hboots interchangeably.
I'm on an AT&T One flashed to International firmware with GPE dark hboot.
Sent from my HTC One using xda app-developers app
ilal2ielli said:
Hboot is universal as long as it's from the same network version.
You'll need supercid to flash unsigned firmware zips, but you can use hboots interchangeably.
I'm on an AT&T One flashed to International firmware with GPE dark hboot.
Click to expand...
Click to collapse
Thanks! just don't want to screw up my daily driver, but i think i will try after some backups.
Also, is there a known way yet to flash hboot from pbl or sbl3 download mode if s-off ? Is emmc mode accessible on the One?
I would guess HTC/qc built something in (even for *s-on* hboot sig verification failures), since it would be absurd to open and JTAG the One. Although perhaps qpst is usable if s-off and the xml/mbn files are available?... I'll poke around the recent GPE brick threads to see if there's anything there.
I was originally on Sense 6 with Hboot 1.57, however I made a switch to GPE and flashed the ruu. Prior to this I changed my cid to supercid 1111111 so that I could do so. My Hboot has dropped to 1.54.
If I wish to return to Sense do I need to find my regional ruu, or as I have changed my cid I can pretty much wwe release? Also, do I need to change my Hboot to a lower version or leave as is?
While I'm on GPE, can I flash aosp roms such as cm, aokp etc?
Thank you.
maritimesbob said:
I was originally on Sense 6 with Hboot 1.57, however I made a switch to GPE and flashed the ruu. Prior to this I changed my cid to supercid 1111111 so that I could do so. My Hboot has dropped to 1.54.
If I wish to return to Sense do I need to find my regional ruu, or as I have changed my cid I can pretty much wwe release? Also, do I need to change my Hboot to a lower version or leave as is?
While I'm on GPE, can I flash aosp roms such as cm, aokp etc?
Thank you.
Click to expand...
Click to collapse
1. The best way to get back your warranty (I think you want it) is to change CID to your stock CID and flash RUU for your CID.
2. Yoou don;t have to change Hboot coz RUU will do it for you so leave it as is.
3. Yes you can flash all Custom ROMS not only AOSP but it's good to have SuperCID.
No I'm not after keeping my warranty, just asking in case I wanted to switch back to Sense. I can flash a Sense rom over GPE? I wasn't aware that was possible. Figured I would need to go back to a Sense base via ruu.
maritimesbob said:
No I'm not after keeping my warranty, just asking in case I wanted to switch back to Sense. I can flash a Sense rom over GPE? I wasn't aware that was possible. Figured I would need to go back to a Sense base via ruu.
Click to expand...
Click to collapse
Yes to go back to Sense you should flash a Sense RUU. And to be on the safe side you should use the earliest ruu you can downgrading to hboot 1.4.4. Then update the phone to the latest sense.
If you don't use an ruu to revert you risk running into problems later. And as your obviously s-off do not under any circumstance 're-lock your bootloader or go back to s-on. you will be stuck with a brick.
Ok, any tips to avoid accidently relocking the bootloader?
I was checking the GPE conversion thread, it simply states flashing the hboot 1.44 ruu, flash a stock ruu, pretty much it? Is there anything that could cause the bootloader to lock or for me to lose s-off? I paid sunshine for that, don't fancy losing it again!!
Assume, I'll have to root and flash custom recovery again? Yeah don't fancy going through the unlocking bootloader procedure again.
I simply want to go back to Sense, retain s-off and my unlocked bootloader so I can continue flashing custom roms and all that fun.
I have supercid 1111111 which means I can use a Euro ruu or any other? I was on Vodafone UK.
Thanks,
maritimesbob said:
Ok, any tips to avoid accidently relocking the bootloader?
I was checking the GPE conversion thread, it simply states flashing the hboot 1.44 ruu, flash a stock ruu, pretty much it? Is there anything that could cause the bootloader to lock or for me to lose s-off? I paid sunshine for that, don't fancy losing it again!!
Assume, I'll have to root and flash custom recovery again? Yeah don't fancy going through the unlocking bootloader procedure again.
I simply want to go back to Sense, retain s-off and my unlocked bootloader so I can continue flashing custom roms and all that fun.
I have supercid 1111111 which means I can use a Euro ruu or any other? I was on Vodafone UK.
Thanks,
Click to expand...
Click to collapse
Well you'll be pleased to know that if you used Sunshine to s-off. Should you need it again you won't have to pay. You only pay once per device.
Locking the bootloader and switching s-on can only be done manually using specific fastboot commands. Or Very specific dd commands in recovery. It's not likely to happen accidentally.
I only warned you of it because some users made the mistake of thinking it was necessary. But if the phone ends up locked or s-on without a proper conversion they can become impossible to recover.
All done, quite painless really. Thanks for the help.