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/
Hello there
These are the current stats of my device:
ROM: TrickDroid 7.5.0
CID: superCID 11111111
S-OFF
Recovery: TWRP 2.5.0
Bootloader: Unlocked
If I want to flash a RUU, I understand that just about ANY RUU will work because I have Super CID, but I want to know if there certain prerequists to flashing a RUU? Like for instance would I have to relock bootloader, set it to S-ON, flash stock recovery first, etc?
I'll probably be flashing either one of those:
RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A .14.3250.13_10.33.1150.01_release_311678_signed.exe
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Thanks
TarekElsakka said:
Hello there
These are the current stats of my device:
ROM: TrickDroid 7.5.0
CID: superCID 11111111
S-OFF
Recovery: TWRP 2.5.0
Bootloader: Unlocked
If I want to flash a RUU, I understand that just about ANY RUU will work because I have Super CID, but I want to know if there certain prerequists to flashing a RUU? Like for instance would I have to relock bootloader, set it to S-ON, flash stock recovery first, etc?
I'll probably be flashing either one of those:
RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A .14.3250.13_10.33.1150.01_release_311678_signed.exe
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
Thanks
Click to expand...
Click to collapse
You should be able to flash the ruu the way you are. The only differences between your phone and mine when I flashed the brightstar ruu is the Rom I was on and I had relocked my bootloader. S-off will be retained after the flash but twrp will be replaced with the stock recovery. If it fails to flash you can try it again after relocking the bootloader but I don't think it's necessary.
Thank you very much. I won't need the bootloader to be unlocked anyhow in order to receive OTA updates so I might as well relock it and not flash a custom recovery. I do not need to be S-ON in order to receive OTA updates, right? Just locked bootloader, RUU, stock recovery and the proper CID (like HTC__001, for instance)? And while S-OFF, is changing CID from 111111 to HTC__001 as easy as using one command like
Code:
fastboot oem writecid 11111111
?
TarekElsakka said:
Thank you very much. I won't need the bootloader to be unlocked anyhow in order to receive OTA updates so I might as well relock it and not flash a custom recovery. I do not need to be S-ON in order to receive OTA updates, right? Just locked bootloader, RUU, stock recovery and the proper CID (like HTC__001, for instance)? And while S-OFF, is changing CID from 111111 to HTC__001 as easy as using one command like
Code:
fastboot oem writecid 11111111
?
Click to expand...
Click to collapse
Your pretty much spot on... Keep in mind that for otas your model id needs to be right for the ruu you flash as well as the cid. For example my phone is a US AT&T model has the same model id for the US dev version. So I just needed to be sure to flash the US dev ruu (brightstar) and then set the correct cid (bs_us001) and life is good. Problem is I don't personally know the model id or cid for the ruus you intend to flash. The good news is you can find your model id as well as change it if you need to. The threads to do this are pretty easy to find I'll get a link if you need me too. And to confirm "fastboot oem writecid ********" is what ya need... The asterisks are of course whatever cid you intend to write.
---------- Post added at 03:35 PM ---------- Previous post was at 03:14 PM ----------
http://forum.xda-developers.com/showthread.php?t=2269317&highlight=+model+id+
You can find your model id by doing this in this thread if you need to
Thank you so much for your reply. So from what I understood, in order to go back to stock, I'd have to flash a RUU that will be compatible with my Model ID, correct? I do know what my model is, and it is PN0711000 if I am not mistaken (I have it saved on a text file somewhere), but the problem is that I will not know which model ID I need and for which RUU. And by the way, if something ever goes wrong with my device after returning it to full stock but with a different Model ID, wouldn't HTC be able to figure that out and void my warranty? Sorry for the 20 questions I am very new to this. I appreciate your help.
TarekElsakka said:
Thank you so much for your reply. So from what I understood, in order to go back to stock, I'd have to flash a RUU that will be compatible with my Model ID, correct? I do know what my model is, and it is PN0711000 if I am not mistaken (I have it saved on a text file somewhere), but the problem is that I will not know which model ID I need and for which RUU. And by the way, if something ever goes wrong with my device after returning it to full stock but with a different Model ID, wouldn't HTC be able to figure that out and void my warranty? Sorry for the 20 questions I am very new to this. I appreciate your help.
Click to expand...
Click to collapse
Just replied to you in another thread lol... Um if that's your model id I believe... Emphasis on believe... That matches the Europe ruu and possibly the Asia one too. Maybe someone who knows for sure will pop in here and confirm. As far as the warranty stuff if there is no ruu for you specific carrier then make a fresh nandroid backup of the stock Rom and with s-off can be made like it was when you bought it.
Yeah I just saw your post there, thank you lol. Unfortunately I was stupid enough not to make a Nandroid Backup of my stock ROM before I went ahead and flashed a custom one.
viperlox said:
Just replied to you in another thread lol... Um if that's your model id I believe... Emphasis on believe... That matches the Europe ruu and possibly the Asia one too. Maybe someone who knows for sure will pop in here and confirm. As far as the warranty stuff if there is no ruu for you specific carrier then make a fresh nandroid backup of the stock Rom and with s-off can be made like it was when you bought it.
Click to expand...
Click to collapse
The MID for UK RUU is PN0710000
Rex2369 said:
The MID for UK RUU is PN0710000
Click to expand...
Click to collapse
Thank you so much. So MID PN0710000 and CID HTC__001. Correct?
TarekElsakka said:
Thank you so much. So MID PN0710000 and CID HTC__001. Correct?
Click to expand...
Click to collapse
Yeah that is correct.
I'm S-OFF. My device is recently unrooted, and my version is 1.28.771.10 on the THREE 3 UK network. It seems there isn't an RUU for my phone released by three. Is there any way that I can return to stock so that my phone is as new? Step by step instructions would be appreciated as i'm very new to this. My bootloader is also locked.
I am on 3 UK also.
Have done this many times .
As you have S off you can change your cid (customer or carrier id) from H3G__001 (which is 3 UK)
to so called super cid which is
11111111 (eight 1's)
When in bootloader fastboot usb mode
C:\adb> fastboot oem writecid 11111111
This will allow you to use any version RUU for your model.
Best one is WWE version which has 401 in the place where yours had 771.
I have always been unlocked when doing this. As you have got S off I will assume you can unlock bootloader.
Then download to your pc the appropriate ruu, I would suggest file (very long filename, I will just list first part of filename - will edit post to add download link)
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7
Download this to your pc
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
It's a large file 990 MB .
The following will delete all your data, photos, video, music, txt , etc (phone number should remain in SIM ) so BE SURE TO COPY FROM PHONE TO PC ANYTHING YOU WANT TO KEEP.
Then connect your HTC One to your pc with usb cable (usb 2, preferably) and simply run the program you've just downloaded .
Your phone can be either in fastboot mode or with android running, doesn't matter which .
Follow on screen instructions, ticking boxes as appropriate.
Total process takes approximately ten minutes from starting the program to finish.
When finished you will be on stock 1.28.401.6 which is original Android 4.1.1
However if you wish you can easily update Ota (over the air) through successive versions up to 4.2 by entering settings then about then software updates then check now
Hope this helps
Sent from my HTC One using xda app-developers app
paul_59 said:
I am on 3 UK also.
Have done this many times .
As you have S off you can change your cid (customer or carrier id) from H3G__001 (which is 3 UK)
to so called super cid which is
11111111 (eight 1's)
When in bootloader fastboot usb mode
C:\adb> fastboot oem writecid 11111111
This will allow you to use any version RUU for your model.
Best one is WWE version which has 401 in the place where yours had 771.
I have always been unlocked when doing this. As you have got S off I will assume you can unlock bootloader.
Then download to your pc the appropriate ruu, I would suggest file (very long filename, I will just list first part of filename - will edit post to add download link)
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7
Download this to your pc
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
It's a large file 990 MB .
The following will delete all your data, photos, video, music, txt , etc (phone number should remain in SIM ) so BE SURE TO COPY FROM PHONE TO PC ANYTHING YOU WANT TO KEEP.
Then connect your HTC One to your pc with usb cable (usb 2, preferably) and simply run the program you've just downloaded .
Your phone can be either in fastboot mode or with android running, doesn't matter which .
Follow on screen instructions, ticking boxes as appropriate.
Total process takes approximately ten minutes from starting the program to finish.
When finished you will be on stock 1.28.401.6 which is original Android 4.1.1
However if you wish you can easily update Ota (over the air) through successive versions up to 4.2 by entering settings then about then software updates then check now
Hope this helps
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hey buddy, I know this is an old threat but you're on the exact same network as me and such.
I managed to get back to stock, and i'm on android version 4.1.2... but i can't seem to find any OTA android updates? Which is the main reason why I unrooted my phone. Tried the google framework fix too. Got any ideas?
tomquartey said:
Hey buddy, I know this is an old threat but you're on the exact same network as me and such.
I managed to get back to stock, and i'm on android version 4.1.2... but i can't seem to find any OTA android updates? Which is the main reason why I unrooted my phone. Tried the google framework fix too. Got any ideas?
Click to expand...
Click to collapse
If you are supercid (11111111) you will not get ota. You must change cid to one that match you OS base.
alray said:
If you are supercid (11111111) you will not get ota. You must change cid to one that match you OS base.
Click to expand...
Click to collapse
I had to SUPER CID to flash this particular RUU.
If I change my CID back now, will this mean my RUU is redundant and then brick my phone?
And the original CID was H3G_001. Do I need to go back to this one?
tomquartey said:
I had to SUPER CID to flash this particular RUU.
If I change my CID back now, will this mean my RUU is redundant and then brick my phone?
And the original CID was H3G_001. Do I need to go back to this one?
Click to expand...
Click to collapse
no its safe to change CID, you will never get OTA with supercid from this carrier
change back your cid to H3G__001 (2 lower case H3G _ _001)
Code:
fastboot oem writecid H3G__001 [COLOR="SeaGreen"]---> cid change[/COLOR]
fastboot reboot-bootloader [COLOR="SeaGreen"]--> reboot and go back to fastboot usb[/COLOR]
fastboot oem readcid [COLOR="SeaGreen"]--->confirm cid is now H3G__001[/COLOR]
fastboot reboot [COLOR="SeaGreen"]--->reboot to system[/COLOR]
then install ota
alray said:
no its safe to change CID, you will never get OTA with supercid from this carrier
change back your cid to H3G__001 (2 lower case H3G _ _001)
Code:
fastboot oem writecid H3G__001 [COLOR="SeaGreen"]---> cid change[/COLOR]
fastboot reboot-bootloader [COLOR="SeaGreen"]--> reboot and go back to fastboot usb[/COLOR]
fastboot oem readcid [COLOR="SeaGreen"]--->confirm cid is now H3G__001[/COLOR]
fastboot reboot [COLOR="SeaGreen"]--->reboot to system[/COLOR]
then install ota
Click to expand...
Click to collapse
Thank you buddy, will try this soon.
tomquartey said:
I had to SUPER CID to flash this particular RUU.
If I change my CID back now, will this mean my RUU is redundant and then brick my phone?
And the original CID was H3G_001. Do I need to go back to this one?
Click to expand...
Click to collapse
alray said:
no its safe to change CID, you will never get OTA with supercid from this carrier
change back your cid to H3G__001 (2 lower case H3G _ _001)
Code:
fastboot oem writecid H3G__001 [COLOR="SeaGreen"]---> cid change[/COLOR]
fastboot reboot-bootloader [COLOR="SeaGreen"]--> reboot and go back to fastboot usb[/COLOR]
fastboot oem readcid [COLOR="SeaGreen"]--->confirm cid is now H3G__001[/COLOR]
fastboot reboot [COLOR="SeaGreen"]--->reboot to system[/COLOR]
then install ota
Click to expand...
Click to collapse
1- easy on the double posting , then make up your mind, where you wanna post, so people can actually help
2- what ruu are you referring to?
3- no just changing CID back to original (H3G__001) does not mean you're going to get any OTA if the ^^ ruu is not H3G
nkk71 said:
1- easy on the double posting , then make up your mind, where you wanna post, so people can actually help
2- what ruu are you referring to?
3- no just changing CID back to original (H3G__001) does not mean you're going to get any OTA if the ^^ ruu is not H3G
Click to expand...
Click to collapse
I was told to change my RUU to a particular RUU from another user who is on the same network as me.
tomquartey said:
I was told to change my RUU to a particular RUU from another user who is on the same network as me.
Click to expand...
Click to collapse
well if you are on CID H3G_001 then this "change my RUU to a particular RUU" (there is no particular RUU) makes no sense at all, if you are S-Off:
1- you can change CID to unbranded and use an unbranded RUU
2- you can use one of the guides around here to go back to H3G stock
My CID is htc_001 and it sucks i allways get ota updates very slow compared to the other cids, so my question is to which cid should i change in order to get the fastest ota updates?
And another question, i flashed TWRP and rooted my phone, i still can get ota updates?
Again sorry for my noobish questions and my bad english.
You will need to be fully stock to get OTA's, recovery, no missing apps, stock rom etc.
and as for CID, well at a guess I would say super cid would get the updates first, however, recently ive heard its very dependant on your operator, country and whether you brought your phone or its on contract.
Im in the UK and on CID HTC__001 too, I read today that HTC are releasing the sense 6 update to UK customers somewhere around the 11th June, so Wednesday. im all ready for it, just got to flash stock recovery.
Seanie280672 said:
You will need to be fully stock to get OTA's, recovery, no missing apps, stock rom etc.
and as for CID, well at a guess I would say super cid would get the updates first, however, recently ive heard its very dependant on your operator, country and whether you brought your phone or its on contract.
Im in the UK and on CID HTC__001 too, I read today that HTC are releasing the sense 6 update to UK customers somewhere around the 11th June, so Wednesday. im all ready for it, just got to flash stock recovery.
Click to expand...
Click to collapse
So all i need to do to get updateds is to flash stock recovery? (i can keep the root, right?)
How can i flash the stock recovery?
Num_Lock said:
So all i need to do to get updateds is to flash stock recovery? (i can keep the root, right?)
How can i flash the stock recovery?
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery.img
alray said:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok... do I need a file or something? can you explain more detailed?
I'm sorry for being noob it's just I'm used to samsung phones development and the htc development is different with new stuff (s off unlocking ruu and whatever) so i need you to explain me more detailed.
Thank you.
Num_Lock said:
Ok... I need a file or something? can you explain in more details?
I'm sorry for being noob it's just I'm reguler to samsung phones development and the htc development is different with new stuff (s off unlocking ruu and whatever) so i need you to explain me more detailed.
Thank you.
Click to expand...
Click to collapse
you need the stock recovery file (recovery.img) from the same version firmware of your phone. i.e if you phone is on 4.19.401.1 and you want to update to 5.20.401.1, you need the recovery.img file from the 4.19.401.1 firmware.
also read this: http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
alray said:
you need the stock recovery file (recovery.img) from the same version firmware of your phone. i.e if you phone is on 4.19.401.1 and you want to update to 5.20.401.1, you need the recovery.img file from the 4.19.401.1 firmware.
also read this: http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
Click to expand...
Click to collapse
OK and one more thing, i need to s off to change my cid?
Num_Lock said:
OK and one more thing, i need to s off to change my cid?
Click to expand...
Click to collapse
yes you need s-off, and if you change your cid, it must match your sw version! some software version only have a unique compatible cid and other have many compatible cid. i.e .401 sw version can use many different cid: HTC__001, HTC__Y13, HTC__032, HTC__203 etc etc..... but .502 version can only use one cid: CWS__001
to change cid:
Code:
fastboot oem writecid YOUR_CID [COLOR="Green"]<---- in most cases, start with HTC in capital letter, 2 underscores and 3 digits, always 8 characters total.[/COLOR]
i.e:
Code:
fastboot oem writecid HTC__001
you can read your actual cid with this command:
Code:
fastboot oem readcid
alray said:
yes you need s-off, and if you change your cid, it must match your sw version! some software version only have a unique compatible cid and other have many compatible cid. i.e .401 sw version can use many different cid: HTC__001, HTC__Y13, HTC__032, HTC__203 etc etc..... but .502 version can only use one cid: CWS__001
to change cid:
Code:
fastboot oem writecid YOUR_CID [COLOR="Green"]<---- in most cases, start with HTC in capital letter, 2 underscores and 3 digits, always 8 characters total.[/COLOR]
i.e:
Code:
fastboot oem writecid HTC__001
you can read your actual cid with this command:
Code:
fastboot oem readcid
Click to expand...
Click to collapse
I want to change to supercid, it supports my version? and with s off i can still get ota right?
Num_Lock said:
I want to change to supercid, it supports my version? and with s off i can still get ota right?
Click to expand...
Click to collapse
on some sw version, you will not receive ota update with supercid. supercid is used to bypass cid check when installing some rom/ruu.
for s-off question, read the link i have posted at post #6
alray said:
on some sw version, you will not receive ota update with supercid. supercid is used to bypass cid check when installing some rom/ruu.
for s-off question, read the link i have posted at post #6
Click to expand...
Click to collapse
In my version i will get ota updates with supercid?
Thanks for your help i really appreciate it.
Num_Lock said:
In my version i will get ota updates with supercid?
Thanks for your help i really appreciate it.
Click to expand...
Click to collapse
idk, refer to the android-info.txt of the ota.zip and you'll see all supported cid.
USA developers edition get ota first every time
from HTC One