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
EDIT: To make a long story short: Does my device have to be S-ON to be able to perform OTA updates? Does my Model ID have to match the CID? Like if my Model ID is PN0711000 and CID HTC__J15 and I decide to change CID to HTC_A07 in Russia, do I have to change Model ID as well to whatever it is they use in Russia?
Hello there
Just before someone chimes in with "Read tutorials or Google", I read just about every popular tutorial there is, including several here on XDA.
I understand that there are a couple of days to go back to stock, but only one of them is available to me: Installing a RUU.
My device is international, unlocked and came with CID HTC__J15 and MID PN0711000. The region is Middle East (Egypt).
We are always the latest to receive any OTA updates, I know because I came from a HTC One X before the Galaxy SIII. I decided I'd go S-OFF and SuperCID (after installing several custom ROMs) in order to go back to stock. I installed this RUU:
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
I was told that just about any .401 (WWE) RUU should work. I installed it when I had SuperCID (111111) but then I changed my CID to HTC__001. I then found an OTA update to 1.29.401 (229MB) and I downloaded it, but after it was done downloading it gave me this message:
Your device has been modified. Software updates are not available.
I do not understand how that came to be? I installed a RUU therefore I have stock recovery and I changed CID to HTC__001 so I should be eligible for OTA updates for that specific region, could it be that my device is S-OFF or is there maybe a CID/MID mismatch?
Thank you
You have to have stock recovery as well.
When s-off you can flash any ruu you like.
Sent from my HTC One
I am super CID and I flashed RUU. I then changed CID to HTC__001 and tried to perform OTA update to 1.29 and it said your software is modified. I do have stock recovery, by the way. So if it isn't because of S-OFF, could it be a Model ID thing?
Try changing cid back to original.
Sent from my HTC One
---------- Post added at 11:32 PM ---------- Previous post was at 11:24 PM ----------
Did you: fastboot oem lock
Sent from my HTC One
Yes, I did lock the bootloader using ADB and now it says "Locked".
I changed CID to HTC__A07 and am trying the update.
Is there a way to find out if your device status says stock or modified? I remember there was something like that before.
Ok here is what I had previously done to my phone
Unlocked bootloader
S-OFF
removed 'tampered'
Rooted
CID 11111111
ROM was stock and was on 129.xxxx (401)
Phone was originally had CID of ORANG001
Now I installed stock recovery and put CID to HTC__001 but only got the 217.xx update then kept getting the message that my phone is up to date. Knowing this was not true, tried lots of things from here but still not update
Last night, I downloaded the 128.xxx WWE shipped RUU from here and 'downgraded' the phone. All was ok and I went to software updates, which had 129 xx available. I updated, rebooted then got the 'small' update (217.xx i think), rebooted and finally got the 224.xx update available. I installed, rebooted and all was fine
Thing is, how did I get OTA with SuperCID? I thought it couldn't happen?
Phone was obviously back to stock to re-rooted and all is back to normal with 224.xx software
Most likely if you changed that cid when they pushed an ota the network recognised it and pushed it to that cid
sent from my one x+ if i helped you out hit that thanks button
First of all, hello to you all!
I have a US Unlocked with CID BS__0001 (same as Developer Edition) with everything stock, not even rooted. I already know that 4.3 is coming next month if HTC fulfills its promise but I want 4.2.2 to get rid of the black bar and get the AE/AF camera improvements.
After reading tons, and I means of threads and posts, I have a general understanding on how to proceed and what to do to get 4.2.2 OTA but I want confirmation from you guys on a few topics. I will enumerate the steps and ask a question(s) on each one.
1.- I need to unlock the bootloader via HTCDev or Revone. Then S-OFF with Revone (read about Moonshine but it seems that most folks are using the former). Going S-OFF will impact battery life? I remember reading about an error reporting service or something like it that will always run after going S-OFF. Is this true? Does it impact battery/performance in any way?
2.- After S-OFF, I will need to change my CID to SuperCID, install a stock WWE RUU and change the CID to one that already got 4.2.2 update, like HTC__001. Then the OTA updates will show up. Flashing the stock RUU posted on this guide won't affect any of the radios of my phone in any way, right? I don't want to risk getting poor reception/speeds or Wi-Fi range.
3.- After having all the OTA updates installed and running 4.2.2, I want to be able to receive the 4.3 OTA when it becomes available. Should I just change back my CID to BS__0001 and the update will show up? I also need to relock the bootloader, right? Are these the only two things to do?
I've also read that S-OFF is not possible at the moment after updating to 4.2.2. I don't want/need it as long as the 4.3 OTA can be installed normally as I'm more than happy with the One stock stuff. What do you guys recommend? Do I keep S-OFF or S-OFF?
I appreciate you taking the time to read this and answer my questions. If you have any other input, comments, suggestions or advice before I start messing with my phone, I'll be more than grateful.
Thanks!
ajua said:
First of all, hello to you all!
I have a US Unlocked with CID BS__0001 (same as Developer Edition) with everything stock, not even rooted. I already know that 4.3 is coming next month if HTC fulfills its promise but I want 4.2.2 to get rid of the black bar and get the AE/AF camera improvements.
After reading tons, and I means of threads and posts, I have a general understanding on how to proceed and what to do to get 4.2.2 OTA but I want confirmation from you guys on a few topics. I will enumerate the steps and ask a question(s) on each one.
1.- I need to unlock the bootloader via HTCDev or Revone. Then S-OFF with Revone (read about Moonshine but it seems that most folks are using the former). Going S-OFF will impact battery life? I remember reading about an error reporting service or something like it that will always run after going S-OFF. Is this true? Does it impact battery/performance in any way?
2.- After S-OFF, I will need to change my CID to SuperCID, install a stock WWE RUU and change the CID to one that already got 4.2.2 update, like HTC__001. Then the OTA updates will show up. Flashing the stock RUU posted on this guide won't affect any of the radios of my phone in any way, right? I don't want to risk getting poor reception/speeds or Wi-Fi range.
3.- After having all the OTA updates installed and running 4.2.2, I want to be able to receive the 4.3 OTA when it becomes available. Should I just change back my CID to BS__0001 and the update will show up? I also need to relock the bootloader, right? Are these the only two things to do?
I've also read that S-OFF is not possible at the moment after updating to 4.2.2. I don't want/need it as long as the 4.3 OTA can be installed normally as I'm more than happy with the One stock stuff. What do you guys recommend? Do I keep S-OFF or S-OFF?
I appreciate you taking the time to read this and answer my questions. If you have any other input, comments, suggestions or advice before I start messing with my phone, I'll be more than grateful.
Thanks!
Click to expand...
Click to collapse
1. S-off will not produce a noticeable drop in battery and no issue with performance.
2. You also need to make sure that the rom you flash supports your MID as well. You can "trick" the android info.txt file to cover this issue before you flash. There are threads around that show you how. The firmware you flash needs to sync up with the rom you flash, or you will run into radio issues, etc. Possibly even brick.
3. If you are running the HTC_001 rom, you won't be able to receive the BS_US001 OTA. For that, you would need to flash back to BS_US001 stock, which of course, would render all the work you put into flashing 4.2.2 moot. Basically, if you convert your phone to HTC_001, you'll be using those updates, not BS_US001 updates. For a buggy incremental update before 4.3, not worth it in my opinion. For any OTA, unless your device came shipped unlocked, you need to re-lock before you can OTA.
In your situation, I would re-lock (unless it shipped unlocked), s-off and wait for the 4.3 update. Hope this helps.
I unlocked my bootloader the day I bought my One , six months ago. Got S off via revone as soon as I saw it .
I haven't needed to relock bootloader to get OTA updates.
Sent from my HTC One using xda app-developers app
kibmikey1 said:
1. S-off will not produce a noticeable drop in battery and no issue with performance.
2. You also need to make sure that the rom you flash supports your MID as well. You can "trick" the android info.txt file to cover this issue before you flash. There are threads around that show you how. The firmware you flash needs to sync up with the rom you flash, or you will run into radio issues, etc. Possibly even brick.
3. If you are running the HTC_001 rom, you won't be able to receive the BS_US001 OTA. For that, you would need to flash back to BS_US001 stock, which of course, would render all the work you put into flashing 4.2.2 moot. Basically, if you convert your phone to HTC_001, you'll be using those updates, not BS_US001 updates. For a buggy incremental update before 4.3, not worth it in my opinion. For any OTA, unless your device came shipped unlocked, you need to re-lock before you can OTA.
In your situation, I would re-lock (unless it shipped unlocked), s-off and wait for the 4.3 update. Hope this helps.
Click to expand...
Click to collapse
Thanks for replying. I'm willing to do this for two things. One is to learn how to do it and gain experience as the only other experience I had flashing and rooting was with the original Kindle Fire. The second one is to get rid of the black bar and get the camera improvements, no matter how lesser they are.
About your #2 point, I think that my US unlocked MID is supported by the RUU that are available in the collection thread. If the RUU supports my MID, there won't be any issue with radios I guess.
About your #3 point. I don't mind spending a few hours doing this. After getting 4.2.2 OTA using HTC__001 (or any other CID), will I be able to revert back to BS_US001? I ask this because I would like to do it to get the intended 4.3 OTA for my exact phone model when it's available, not get stuck with HTC__001 and its updates. If I keep S-OFF then I think I will be able to revert right? Is this correct? If I can't revert to stock BS_US001 I guess I will skip my plan and wait another month to get 4.3.
Thanks again!
paul_59 said:
I unlocked my bootloader the day I bought my One , six months ago. Got S off via revone as soon as I saw it .
I haven't needed to relock bootloader to get OTA updates.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It's good to know that. Did you do the CID changing to get 4.2.2 OTA? If so, leaving S-OFF can allow me to revert back to BS_US001 when 4.3 arrives? Thanks!
Hi people
I used to have a htc one and the mrs has one with the new update, I broke my htc one and replaced it with a htc mini. can anyone help me with some info, what I would like to know is if I can make my HTC one mini update on the HG3 OTA. tried getting answers in the one mini section but no luck, is there a way of using the kernels from the dev site to change the EE phone thinking its a HG3 giving me the up[date?? I have unlocked the bootloader but I don't really want to mess around with custom roms.
thanks all
justyjust said:
Hi people
I used to have a htc one and the mrs has one with the new update, I broke my htc one and replaced it with a htc mini. can anyone help me with some info, what I would like to know is if I can make my HTC one mini update on the HG3 OTA. tried getting answers in the one mini section but no luck, is there a way of using the kernels from the dev site to change the EE phone thinking its a HG3 giving me the up[date?? I have unlocked the bootloader but I don't really want to mess around with custom roms.
thanks all
Click to expand...
Click to collapse
to receive ota updates for your phone on a given network:
CID must match the OTA update (s-off required to change CID)
MID must match the OTA update (s-off required to change MID)
OS version must match the OTA update (s-off required to do a full conversion, flashing a different OS version need to change MID and CID)
alray said:
to receive ota updates for your phone on a given network:
CID must match the OTA update (s-off required to change CID)
MID must match the OTA update (s-off required to change MID)
OS version must match the OTA update (s-off required to do a full conversion, flashing a different OS version need to change MID and CID)
Click to expand...
Click to collapse
thanks for the reply, is this a difficult process is there any tutorials??? cheers j
justyjust said:
thanks for the reply, is this a difficult process is there any tutorials??? cheers j
Click to expand...
Click to collapse
you'll have to refer to the htc one mini forum for this. s-off method is device specific. changing cid is done with the fastboot oem writecid command and changing MID is also specific to your phone model.