Related
Sorry for creating a lot of help threads, but things just don't wanna work my way.
Yesterday I wanted to flash a RUU to see exactly how HTC does things and if it's easy or hard. Anyway. I come from a Galaxy S3 and if I wanted to go back to stock from any other rom, I simply flashed a stock rom tar with a program called Odin, but it doesn't seem to be as simple with HTC.
I downloaded a RUU for the Europe region as it seemed the most obvious thing to do, but my CID is Nordic (HTC__Y13). Here's how it went:
Being on a 4.2.2 custom rom:
I tried running the RUU when I was on a 4.2.2. custom rom (InsertCoin 2.0.2), and I fired up the RUU file and followed the instructions. Then it said my phone isn't supported and that I need another RUU file.
Being on a stock odexed 1.29 rom:
I then installed a stock 1.29 rom from Mike1986. and then fired up the RUU. I followed the instructions and it seems the flashing started. It sent me to the RUU mode (the HTC screen) and began the flashing process. It said it wiped the data and that it sent some signature keys, I think. Three minutes later, the RUU window disappeared. I could see the program was still running but the window disappeared. It quickly flashed for about half a second and I could see some text saying that my phone isn't supported, but why the hell did it commence the flashing?
I pulled the cable, long-pressed the power button and let it boot, it hadn't wiped a thing.
Let it be known that before I opened the RUU's, I made sure I was bootloader locked and S-ON (with the revone method).
Is it because I have the Nordic CID and I had a RUU for the European region? If so, I looked anywhere and everywhere for a Nordic RUU but there's none to be found.
Any help is appreciated.
You can only use an RUU which is the same or newer than the firmware on the phone, e.g. if your last official update was 1.29.401.13 you could only use an RUU that version or above UNLESS you're S-OFF, in which case you can use an older one if you have Super CID and a locked/relocked bootloader
EddyOS said:
You can only use an RUU which is the same or newer than the firmware on the phone, e.g. if your last official update was 1.29.401.13 you could only use an RUU that version or above UNLESS you're S-OFF, in which case you can use an older one if you have Super CID and a locked/relocked bootloader
Click to expand...
Click to collapse
So what you're saying, is:
If I acquire Super CID, then flash a Europe RUU and then set my CID back to what it originally was (or maybe even set it to HTC__001) and then reflash the RUU, and it'll work beautifully? I'm S-OFF, btw.
Theshawty said:
So what you're saying, is:
If I acquire Super CID, then flash a Europe RUU and then set my CID back to what it originally was (or maybe even set it to HTC__001) and then reflash the RUU, and it'll work beautifully? I'm S-OFF, btw.
Click to expand...
Click to collapse
Where you S-Off or S-On when you ran the RUU?
bobsie41 said:
Where you S-Off or S-On when you ran the RUU?
Click to expand...
Click to collapse
S-ON with the bootloader locked. I wanted to see if it was possible.
I'm not really looking to revert to unrooted stock, at least not now. I just want to know that it's possible without too much work for when it would be necessary or when I want to try out unrooted stock again. It's always nice to have a fallback.
Theshawty said:
S-ON with the bootloader locked. I wanted to see if it was possible.
I'm not really looking to revert to unrooted stock, at least not now. I just want to know that it's possible without too much work for when it would be necessary or when I want to try out unrooted stock again. It's always nice to have a fallback.
Click to expand...
Click to collapse
As far as I'm aware, you can only run a RUU that is relevant to you device whilst you are s-on and only one that is equal to or above the firmware that you are running.
The only way to return to official un-rooted stock is, again, to run a RUU for your device or install a completely stock nandroid backup of your device or one running the same version as yours.
OK, full example...
You originally get an unbranded One from the EU and you get the OTA to 1.29.401.13. From this point on, with an S-ON/Locked phone with CID HTC__001 you can ONLY flash an RUU which is 1.29.401.13 or higher. This will never change. If you get an RUU from a specific carrier you cannot flash it as it doesn't match your CID.
If you unlock the bootloader, but stay S-ON, you cannot flash an RUU at all - you HAVE to relock the bootloader first but you can still only flash an RUU matching your CID and is the same or newer than your current version.
If you S-OFF and change the CID to 11111111 you can flash ANY RUU you want, even those older than your current version, e.g. 1.28.401.7. You still have to have a locked/relocked bootloader but you can stay S-OFF and flash the RUU. As the only RUU available at the moment for the unbranded One is 1.28.401.7 it means you can flash that and then get the OTA updates in sequence to get to the latest version
Once back at the older version using the RUU you could change your CID back to HTC__001 if you wanted but I don't think it matters
EddyOS said:
OK, full example...
You originally get an unbranded One from the EU and you get the OTA to 1.29.401.13. From this point on, with an S-ON/Locked phone with CID HTC__001 you can ONLY flash an RUU which is 1.29.401.13 or higher. This will never change. If you get an RUU from a specific carrier you cannot flash it as it doesn't match your CID.
If you unlock the bootloader, but stay S-ON, you cannot flash an RUU at all - you HAVE to relock the bootloader first but you can still only flash an RUU matching your CID and is the same or newer than your current version.
If you S-OFF and change the CID to 11111111 you can flash ANY RUU you want, even those older than your current version, e.g. 1.28.401.7. You still have to have a locked/relocked bootloader but you can stay S-OFF and flash the RUU. As the only RUU available at the moment for the unbranded One is 1.28.401.7 it means you can flash that and then get the OTA updates in sequence to get to the latest version
Once back at the older version using the RUU you could change your CID back to HTC__001 if you wanted but I don't think it matters
Click to expand...
Click to collapse
Ah, thanks for the clarification! If I do this (Super CID plus flash the RUU), should I change back to the HTC__Y13 cid or change to something like HTC__001 to get the updates for the Europe region? I heard Europe gets OTA's faster than other regions.
One more thing, why does the bootloader have to be locked? Does the RUU check for this?
Theshawty said:
Ah, thanks for the clarification! If I do this (Super CID plus flash the RUU), should I change back to the HTC__Y13 cid or change to something like HTC__001 to get the updates for the Europe region? I heard Europe gets OTA's faster than other regions.
One more thing, why does the bootloader have to be locked? Does the RUU check for this?
Click to expand...
Click to collapse
If you wish to get ota's you will need to have a cid which is relevant to the RUU you have run. Either of those cid's should work for a x.xx.401.x RUU. Not sure about the bootloader locking for an RUU.
bobsie41 said:
If you wish to get ota's you will need to have a cid which is relevant to the RUU you have run. Either of those cid's should work for a x.xx.401.x RUU. Not sure about the bootloader locking for an RUU.
Click to expand...
Click to collapse
The bootloader doesn't need to be locked to flash a RUU. A guy over at Swedroid flashed a Europe RUU (401 device) (after setting Super CID) coming from a carrier-branded One and the RUU did flash perfectly.
I would of course want OTA's, but the thing is, I heard Europe gets them faster than the Nordic region.
Theshawty said:
The bootloader doesn't need to be locked to flash a RUU. A guy over at Swedroid flashed a Europe RUU (401 device) (after setting Super CID) coming from a carrier-branded One and the RUU did flash perfectly.
I would of course want OTA's, but the thing is, I heard Europe gets them faster than the Nordic region.
Click to expand...
Click to collapse
Not necessarily. As with the s3, releases seem pretty random from country to country in Europe. I had the one x with HTC__001 cid and was one of the last to be updated.
Sent from my Nexus 7 using xda premium
Locked the bootloader and went into fastboot and started the RUU. It is now flashing :victory:
After it's done, I will turn the CID back to HTC__Y13 and reflash the RUU.
Theshawty said:
The bootloader doesn't need to be locked to flash a RUU. A guy over at Swedroid flashed a Europe RUU (401 device) (after setting Super CID) coming from a carrier-branded One and the RUU did flash perfectly.
I would of course want OTA's, but the thing is, I heard Europe gets them faster than the Nordic region.
Click to expand...
Click to collapse
I, personally, would relock the bootloader purely to cover yourself. As for CID, it's up to you. Using HTC__001 might not get it the second an OTA comes out but I'm sure you're patient enough to wait a few days
EddyOS said:
I, personally, would relock the bootloader purely to cover yourself. As for CID, it's up to you. Using HTC__001 might not get it the second an OTA comes out but I'm sure you're patient enough to wait a few days
Click to expand...
Click to collapse
I just want back to stock for a few days. I'm a bit tired of custom roming yet I can't stay away from it!
Theshawty said:
I just want back to stock for a few days. I'm a bit tired of custom roming yet I can't stay away from it!
Click to expand...
Click to collapse
I've done the same with my Nexus 4, and shall do the same with my One when I get it next month. I want S-OFF purely because the only RUU we have is an older than what I'll likely get on my phone. This way I can always go back to stock (unless a newer RUU leaks that is!)
How awfully peculiar, though. After I flashed to stock (the 1.28 something RUU), I got an update to 1.29.401.12. My brother, whom also have a One in the same region as I, has the 1.29.401.16 update (I am four decimals behind him ).
I thought I would get an update to .16, or am I just being too impatient?
I know I had .16 before custom roms though.
I read all, very useful conversation,saved me lot of time
Only a thing i havent understand
Im now S-OFF,unlocked with superCID ( runnind a branded italian rom with (now old)TIM__041(if i rememeber right)cid)
What i need to do to have a stock unbranded european RUU
Do i need to relock bootloader Before flashing or not matters?
Theshawty said:
How awfully peculiar, though. After I flashed to stock (the 1.28 something RUU), I got an update to 1.29.401.12. My brother, whom also have a One in the same region as I, has the 1.29.401.16 update (I am four decimals behind him ).
I thought I would get an update to .16, or am I just being too impatient?
I know I had .16 before custom roms though.
Click to expand...
Click to collapse
.16 was for the M7_U handsets, M7_UL is on .12
EddyOS said:
.16 was for the M7_U handsets, M7_UL is on .12
Click to expand...
Click to collapse
But my little brother and I both have UL devices, and his clearly says UL in the about screens.
Theshawty said:
But my little brother and I both have UL devices, and his clearly says UL in the about screens.
Click to expand...
Click to collapse
Hmmm, perhaps it is down to CID then...I don't know anyone in the UK with anything over .12
Firstly, all I want to do is making my AT&T version One with SIM unlock become developer edition. Therefore I can get OTAs from HTC directly and fastest(I hate AT&T.)
So, I s-off my AT&T(thanks revone =b)
Then I changed cid from CWS__001 to 11111111, and installed RUU(1.29.1504.3), after first boot I reboot into bootloader and change CID from supercid to BS_US001, in order to pass the OTAs check. And I relock the bootloader also(fastboot oem lock.)(Thanks @nugzo) However, when I checked the updates, it pops up notification of update(1.29.1504.16), after I downloaded it, it shows "variant system version."
Then I want to run RUU again, but this time it shows error[131]: customer I'D Error.
Anything I can do?
By the way, the CID in fastboot is BS_US001 and ro.cid is BS_US001 too.
Grateful.
Sent from my HTC One using xda app-developers app
tommy0411 said:
Firstly, all I want to do is making my AT&T version One with SIM unlock become developer edition. Therefore I can get OTAs from HTC directly and fastest(I hate AT&T.)
So, I s-off my AT&T(thanks revone =b)
Then I changed cid from CWS__001 to 11111111, and installed RUU(1.29.1504.3), after first boot I reboot into bootloader and change CID from supercid to BS_US001, in order to pass the OTAs check. And I relock the bootloader also(fastboot oem lock.)(Thanks @nugzo) However, when I checked the updates, it pops up notification of update(1.29.1504.16), after I downloaded it, it shows "variant system version."
Then I want to run RUU again, but this time it shows error[131]: customer I'D Error.
Anything I can do?
By the way, the CID in fastboot is BS_US001 and ro.cid is BS_US001 too.
Grateful.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
This one has got me, i dont know what is holding you up. We've been talking in PM's trying to get to the bottom of this but havent had any luck. He has the same ATT device as me, followed the exact procedure i did but keeps getting the error. Has anyone else had issue doing OTA's when all pre requisites are met? The ATT and Dev are the same MID so that's not it. Which s-off method did u use? revolutionary most likley.. it's the easiest. I used moonshine method. Anyone using the revolutionary method that has been successful doing what we're trying to do here? I know it probably doesnt matter which s-off method was used but i'm grasping at the moment.. cant figure this one out, it should be working. Did you change your ro.cid to BS_us001 via hex edit or was it like that? I never hex edited mine and it worked with the ATT cid. If you did change it, Maybe push your original mmcblkop19 back that had the original cid and retry.. The one that hasnt been edited. Again grasping here, but trying to duplicate my setup exactly.
Edit: i just noticed you said you cant even run the ruu now, are you talking about the same ruu you already ran successfully? 1.29.1504.3? Did you check the md5? How about changing back to supercid to install the ruu? I always initiate the ruu install when my phone is on fastboot screen.
tommy0411 said:
Firstly, all I want to do is making my AT&T version One with SIM unlock become developer edition. Therefore I can get OTAs from HTC directly and fastest(I hate AT&T.)
So, I s-off my AT&T(thanks revone =b)
Then I changed cid from CWS__001 to 11111111, and installed RUU(1.29.1504.3), after first boot I reboot into bootloader and change CID from supercid to BS_US001, in order to pass the OTAs check. And I relock the bootloader also(fastboot oem lock.)(Thanks @nugzo) However, when I checked the updates, it pops up notification of update(1.29.1504.16), after I downloaded it, it shows "variant system version."
Then I want to run RUU again, but this time it shows error[131]: customer I'D Error.
Anything I can do?
By the way, the CID in fastboot is BS_US001 and ro.cid is BS_US001 too.
Grateful.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
What I would do is start completely over, Restore to a stock ATT RUU, then run moonshine, then change to CID with the fastboot command, then do the hexedit procedure for changing the CID within your ro.prop. Then flash a DEV RUU. it should return CID 11111111 if its all done correctly.
tommy0411 said:
Firstly, all I want to do is making my AT&T version One with SIM unlock become developer edition. Therefore I can get OTAs from HTC directly and fastest(I hate AT&T.)
So, I s-off my AT&T(thanks revone =b)
Then I changed cid from CWS__001 to 11111111, and installed RUU(1.29.1504.3), after first boot I reboot into bootloader and change CID from supercid to BS_US001, in order to pass the OTAs check. And I relock the bootloader also(fastboot oem lock.)(Thanks @nugzo) However, when I checked the updates, it pops up notification of update(1.29.1504.16), after I downloaded it, it shows "variant system version."
Then I want to run RUU again, but this time it shows error[131]: customer I'D Error.
Anything I can do?
By the way, the CID in fastboot is BS_US001 and ro.cid is BS_US001 too.
Grateful.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Which region RUU are you trying to install?
tommy0411 said:
Firstly, all I want to do is making my AT&T version One with SIM unlock become developer edition. Therefore I can get OTAs from HTC directly and fastest(I hate AT&T.)
So, I s-off my AT&T(thanks revone =b)
Then I changed cid from CWS__001 to 11111111, and installed RUU(1.29.1504.3), after first boot I reboot into bootloader and change CID from supercid to BS_US001, in order to pass the OTAs check. And I relock the bootloader also(fastboot oem lock.)(Thanks @nugzo) However, when I checked the updates, it pops up notification of update(1.29.1504.16), after I downloaded it, it shows "variant system version."
Then I want to run RUU again, but this time it shows error[131]: customer I'D Error.
Anything I can do?
By the way, the CID in fastboot is BS_US001 and ro.cid is BS_US001 too.
Grateful.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I did this to my AT&T One yesterday and was successful. There are 3 things that I did differently and it worked for me...
- I never bothered with the SuperCID, I changed my cid to BS_US001 and then flashed the ruu, no problems. That is the correct cid for the dev edition, so might as well keep it that way.
- I did not relock the bootloader, it's completely unnecessary as the dev edition ships unlocked out of the box. That's the way it's meant to be.
- I flashed the 1.28 ruu as I wanted to be sure that I'd be able to receive ota's. I was then successfully able to download and install the latest 1.29 ota.
So I essentially have a dev edition One now, maybe something that I did can help you (and others).
nugzo said:
This one has got me, i dont know what is holding you up. We've been talking in PM's trying to get to the bottom of this but havent had any luck. He has the same ATT device as me, followed the exact procedure i did but keeps getting the error. Has anyone else had issue doing OTA's when all pre requisites are met? The ATT and Dev are the same MID so that's not it. Which s-off method did u use? revolutionary most likley.. it's the easiest. I used moonshine method. Anyone using the revolutionary method that has been successful doing what we're trying to do here? I know it probably doesnt matter which s-off method was used but i'm grasping at the moment.. cant figure this one out, it should be working. Did you change your ro.cid to BS_us001 via hex edit or was it like that? I never hex edited mine and it worked with the ATT cid. If you did change it, Maybe push your original mmcblkop19 back that had the original cid and retry.. The one that hasnt been edited. Again grasping here, but trying to duplicate my setup exactly.
Edit: i just noticed you said you cant even run the ruu now, are you talking about the same ruu you already ran successfully? 1.29.1504.3? Did you check the md5? How about changing back to supercid to install the ruu? I always initiate the ruu install when my phone is on fastboot screen.
Click to expand...
Click to collapse
Thank you my friend, I really appreciate everything u taught me =))
I already checked the md5, it's correct. And it's the same RUU which is I flashed success before.
And I never try to hex edit.
Maybe I can run RUU with supercid, but basically I could run with BS_US001 too.
I will try what u said.
I hope we can figure it out.
Sent from my HTC One using xda app-developers app
x017in said:
Which region RUU are you trying to install?
Click to expand...
Click to collapse
I don't want run any RUU, I just want to become Dev edition.
Sent from my HTC One using xda app-developers app
tommy0411 said:
I don't want run any RUU, I just want to become Dev edition.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
You do know the Dev edition isn't any better than an unbranded handset from another region, right?
EddyOS said:
You do know the Dev edition isn't any better than an unbranded handset from another region, right?
Click to expand...
Click to collapse
AFAIK, the software, from HTC, is the same. I just don't want use at&t version cuz its update is really late, and I want to keep absolutely stock cuz it's the gift for my mom =b
By the way, the AT&T and Dev edition have same MID, that's why I choose Developer version =))
It I am wrong, correct me plz.
Sent from my HTC One using xda app-developers app
aimfire72 said:
I did this to my AT&T One yesterday and was successful. There are 3 things that I did differently and it worked for me...
- I never bothered with the SuperCID, I changed my cid to BS_US001 and then flashed the ruu, no problems. That is the correct cid for the dev edition, so might as well keep it that way.
- I did not relock the bootloader, it's completely unnecessary as the dev edition ships unlocked out of the box. That's the way it's meant to be.
- I flashed the 1.28 ruu as I wanted to be sure that I'd be able to receive ota's. I was then successfully able to download and install the latest 1.29 ota.
So I essentially have a dev edition One now, maybe something that I did can help you (and others).
Click to expand...
Click to collapse
Thanks for your idea, I will try it.
Sent from my HTC One using xda app-developers app
Good news and bad news.
Good news is I finally can update by OTAs.
Bad news is I still don't know why I can't do that before. All I did this morning is that I changed CID from BS_US001 to 11111111, reboot, then changed CID from 11111111 to BS_US001, reboot and everything works perfect.
By the way, I found one thing. If I changed to Supercid, the ro.cid will show CWS_001. However, if I changed to BS_US001, the ro.cid shows BS_US001. Even I have never touched hex edit.
Anyway, thanks @nugzo. U made my day =b
Sent from my HTC One using xda app-developers app
Yeah, all we need now is a 4.2.2 OTA! Hope it comes soon!
4.2.2
can i update 4.2.2 with OTA?
my cid is 401.
djkinetic said:
What I would do is start completely over, Restore to a stock ATT RUU, then run moonshine, then change to CID with the fastboot command, then do the hexedit procedure for changing the CID within your ro.prop. Then flash a DEV RUU. it should return CID 11111111 if its all done correctly.
Click to expand...
Click to collapse
Hex edit is strictly cosmetic, You can do everything you need to do with fastboot oem writecid. Like OP said, his ro.prop cid changes with different fastboot CIDs. The ro.prop cid also changes with certain roms, aosp for example. IMO it's a little dangerous to hex edit for strictly cosmetic results..
---------- Post added at 11:44 AM ---------- Previous post was at 11:43 AM ----------
mehrzadkh said:
can i update 4.2.2 with OTA?
my cid is 401.
Click to expand...
Click to collapse
wont know till it gets here. Also dont update as soon as its available. It could lock you out let the devs get a hold of it first.
nugzo said:
Hex edit is strictly cosmetic, You can do everything you need to do with fastboot oem writecid. Like OP said, his ro.prop cid changes with different fastboot CIDs. The ro.prop cid also changes with certain roms, aosp for example. IMO it's a little dangerous to hex edit for strictly cosmetic results..
---------- Post added at 11:44 AM ---------- Previous post was at 11:43 AM ----------
wont know till it gets here. Also dont update as soon as its available. It could lock you out let the devs get a hold of it first.
Click to expand...
Click to collapse
Not exactly, my phone's prop.ro cid didnt match fastboot changed cid till i hex edited. the hex edit changes the value within the mm block, the HTC one cid is stored in two places hence why u still see the original CID when u do the fastboot command to read from ro.prop, there are some instances where users have experienced being unable to flash a particular ruu even after changing their cid via fastboot only..Hex editing the prop value allowed them to flash whatever ruu they were trying to provided its the right region for the phone...if you want to change the phones region then you would need to also change the mid.
Sent from my One using Tapatalk 4 Beta
djkinetic said:
Not exactly, my phone's prop.ro cid didnt match fastboot changed cid till i hex edited. the hex edit changes the value within the mm block, the HTC one cid is stored in two places hence why u still see the original CID when u do the fastboot command to read from ro.prop, there are some instances where users have experienced being unable to flash a particular ruu even after changing their cid via fastboot only..Hex editing the prop value allowed them to flash whatever ruu they were trying to provided its the right region for the phone...if you want to change the phones region then you would need to also change the mid.
Sent from my One using Tapatalk 4 Beta
Click to expand...
Click to collapse
The MID absolutely, but the getprop cid is cosmetic, it does not matter. It is not the tru cid location. I've been through all of these supercid threads as well as s-off 7 or 8 Ones and i cant find any evidence of this being needed. Please link me to one if you know any. My phone and 7 others that i updated never touched get prop cid in mmcblk019. only changed fastboot cid and was able to switch from ATT to Dev edition, Install RUU and get the OTA installed all while still having the ATT CID in mmcblk019. CID has always been modified the same way, fastboot oem writecid, There has always been different partitions that stored CID information, just cos they are stored there doesnt mean its the location that counts. Its just super dangerous and i personally haven't needed it for a total of 8 phones that i touched, and 2 more here at XDA the i helped with. Not 1 needed to hex edit to achieve the goal.
nugzo said:
The MID absolutely, but the getprop cid is cosmetic, it does not matter. It is not the tru cid location. I've been through all of these supercid threads as well as s-off 7 or 8 Ones and i cant find any evidence of this being needed. Please link me to one if you know any. My phone and 7 others that i updated never touched get prop cid in mmcblk019. only changed fastboot cid and was able to switch from ATT and tmobile to Dev edition, Install RUU and get the OTA installed all while still having the ATT or tmobile CID in mmcblk019. CID has always been modified the same way, fastboot oem writecid, There has always been different partitions that stored CID information, just cos they are stored there doesnt mean its the location that counts. Its just super dangerous and i personally haven't needed it for a total of 8 phones that i touched, and 2 more here at XDA the i helped with. Not 1 needed to hex edit to achieve the goal.
Click to expand...
Click to collapse
I haven't had issues flashing personally but I have seen reports by some being able to flash a ruu cause of cid mismatch even tho a phone has been fast boot written... might be a rare occurrence or it could just be user error.. Also I don't recommend that anyone just go hex editing without good reason... It is though one other step someone can take to ensure everything is what it should be.
djkinetic said:
I haven't had issues flashing personally but I have seen reports by some being able to flash a ruu cause of cid mismatch even tho a phone has been fast boot written... might be a rare occurrence or it could just be user error.. Also I don't recommend that anyone just go hex editing without good reason... It is though one other step someone can take to ensure everything is what it should be.
Click to expand...
Click to collapse
The only issues i've seen are with people having the wrong MID. They can do the RUU but cant get OTA;s/
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 recently S-OFF-ed my One and converted into GPe with 4.4. However I choose the supercid 11111111 because I was recommended to do so and those instructions where provided after a question in which I stated all getvars. But I have been reading that 11111111 doesn't get the OTA which I would like to receive might I get 4.5 or whatever future versions HTC will still support.
According to this thread SuperCid 11111111 doesn't get OTA and the best bet for me would be HTC__001. Is that correct, or can I also choose from HTC_001 or GOOGL001? The latter I remember reading is supposed to be good too.
So which CID is best, should I change at all and are there downsides to any CID.
(Also, can I S-ON again by writing the security flag? I feel a bit more secure knowing that I cannot unintentionally completely brick my phone.)
ruud.walraven said:
I recently S-OFF-ed my One and converted into GPe with 4.4. However I choose the supercid 11111111 because I was recommended to do so and those instructions where provided after a question in which I stated all getvars. But I have been reading that 11111111 doesn't get the OTA which I would like to receive might I get 4.5 or whatever future versions HTC will still support.
According to this thread SuperCid 11111111 doesn't get OTA and the best bet for me would be HTC__001. Is that correct, or can I also choose from HTC_001 or GOOGL001? The latter I remember reading is supposed to be good too.
So which CID is best, should I change at all and are there downsides to any CID.
(Also, can I S-ON again by writing the security flag? I feel a bit more secure knowing that I cannot unintentionally completely brick my phone.)
Click to expand...
Click to collapse
Normally in order to receive OTAs your MID (PN0712000) and CID (GOOGL001) have to match. Super CID is okay for flashing firmware and RUUs.
As long as you're careful with flashing any firmware, I don't see a good reason to revert to S-on. There's a good chance that it'll be impossible to achieve S-off again after an OTA update.
How can I get a matching mid/cid and what are the implications? Are there advantages to the GOOGL001 or HTC__001 cids?
As title says, I'm taking my T-Mobile HTC One M7 to AT&T. From what I can tell, it should just work with the new SIM (it's SIM-unlocked from T-Mobile as I paid the device off fully). Should also note that my devices is bootloader-unlocked, S-Off, and rooted as well.
After doing some reading, it looks like I might want to change the CID, MID, or ROM. I'm no stranger to new ROMs, but the CID and MID thing are new to me.
It seems like the logical options are to (1) stay on T-Mobile CID, MID, and ROM; (2) change to AT&T CID, MID, and ROM; (3) change to un-branded/unlocked CID, MID, and ROM.
Of these three options, option #3 is the most interesting to me, as I would get the OTA updates way ahead of T-Mobile or AT&T. I'm actually pretty set on this idea, but one thought occurred to me: radio update problems. I know the T-Moble HTC One M7 supports different radio bands, I think because it has different radio hardware. If I switch to the unlocked CID, MID, and ROM and I get an OTA that includes a radio update, isn't there potential for a bad radio flash?
Also, in general, are there any other downsides to converting a T-Mobile M7 to an unlocked M7?
Any other advice when switching?
ERamseth said:
As title says, I'm taking my T-Mobile HTC One M7 to AT&T. From what I can tell, it should just work with the new SIM (it's SIM-unlocked from T-Mobile as I paid the device off fully). Should also note that my devices is bootloader-unlocked, S-Off, and rooted as well.
After doing some reading, it looks like I might want to change the CID, MID, or ROM. I'm no stranger to new ROMs, but the CID and MID thing are new to me.
It seems like the logical options are to (1) stay on T-Mobile CID, MID, and ROM; (2) change to AT&T CID, MID, and ROM; (3) change to un-branded/unlocked CID, MID, and ROM.
Of these three options, option #3 is the most interesting to me, as I would get the OTA updates way ahead of T-Mobile or AT&T. I'm actually pretty set on this idea, but one thought occurred to me: radio update problems. I know the T-Moble HTC One M7 supports different radio bands, I think because it has different radio hardware. If I switch to the unlocked CID, MID, and ROM and I get an OTA that includes a radio update, isn't there potential for a bad radio flash?
Also, in general, are there any other downsides to converting a T-Mobile M7 to an unlocked M7?
Any other advice when switching?
Click to expand...
Click to collapse
As far as the radio goes, you can pull the latest radio from the firmware in a carrier's OTA. If you want to get the OTA updates you will need the stock recovery, stock rom and depending on OTA some of the preload apps. It would be easier to use the RUU exe or zip or nandroid to accomplish it. Follow the OP instructions to a T, since you are S-OFF you can do major damage if you do not. Do not go back to S-ON!