Related
After an upgrade to android 2.3.5 and Sense 3.0, i decided to downgrade and s-off my phone to try custom roms.
Now i decided to go back to stock rom's. I managed to flash 2.12.405.7 Ruu and s-on my phone, but i can't manage to update my phone with OTA function.
My cid is 038 and the original firmware was 2.12.720.5. I can't find that version of ruu(if someone has it please share it).
If i create a gold card and use it to flash for example RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1 can i update by OTA to the latest version available?
Your region and your RUU must match for it to get OTA's.
If your CID hasn't changed since the start, you need to run the RUU of what you started with
markj338 said:
Your region and your RUU must match for it to get OTA's.
If your CID hasn't changed since the start, you need to run the RUU of what you started with
Click to expand...
Click to collapse
Can i change the CID number?
I can't find any 2.12.720.5 ruu version, Football seams to have it, but i can't reach him. And i will first try to find a free version
I managed to find this RUU, but i think the radio is to old, and i will like to avoid a brick. What do you think?
PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip
uqadwe said:
I managed to find this RUU, but i think the radio is to old, and i will like to avoid a brick. What do you think?
PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip
Click to expand...
Click to collapse
If you have a 2.x ROM then DO NOT attempt to flash that 1.X RUU. The radio is TOO OLD and you will BRICK YOUR DEVICE.
ok, thought so, but i really can't find any solution
i can see the next posibilities :
1. gold card + wwe ruu(don't know if ota update will work)
2. cid change (don't know how and if ota update will work)
3. pay for 2.12.720.5 ruu
4. find some 3.**720.* ruu (don't know where)
could you please tell me your point of view?
uqadwe said:
ok, thought so, but i really can't find any solution
i can see the next posibilities :
1. gold card + wwe ruu(don't know if ota update will work)
2. cid change (don't know how and if ota update will work)
3. pay for 2.12.720.5 ruu
4. find some 3.**720.* ruu (don't know where)
could you please tell me your point of view?
Click to expand...
Click to collapse
Make a goldcard and flash the 3.11.405.x WWE RUU.
i made the gold card, everything works, i am now on 3.11.405.2.
Is it normal, that the first row in the bootloader is ***LOCKED*** or
is this one of the downsides of downgrading and restocking.
I don't remember if it was originally here.
Another questions is, when the ICS OTA will be here, can i update
by OTA
uqadwe said:
i made the gold card, everything works, i am now on 3.11.405.2.
Is it normal, that the first row in the bootloader is ***LOCKED*** or
is this one of the downsides of downgrading and restocking.
I don't remember if it was originally here.
Another questions is, when the ICS OTA will be here, can i update
by OTA
Click to expand...
Click to collapse
Yeah this is normal. I'm not sure if the ICS update will come as an OTA, but as long as the bootloader is locked you should be fine installing any official updates.
Is there anyway to downgrade to older version of hboot?
Now, i am on hboot 1.25.My phone is thailand region.
I cant install stock ruu.i have 140 error all the time.
I think RUU is too old but i dont know where to find a newer version.
I download ruu from stickied topic in development forum.
http://forum.xda-developers.com/showthread.php?t=1317895
I think that is the only ruu for thailand region. Anyone can help?
Many thanks.
Btw, my phone is still s-on and i think i cant s-off because i still want a warranty(that is why i am trying to go back to stock rom). Please help.
Sorry for my English. I am not good at English(I am Thai).
KazumaSaruwatari said:
Is there anyway to downgrade to older version of hboot?
Now, i am on hboot 1.25.My phone is thailand region.
I cant install stock ruu.i have 140 error all the time.
I think RUU is too old but i dont know where to find a newer version.
I download ruu from stickied topic in development forum.
http://forum.xda-developers.com/showthread.php?t=1317895
I think that is the only ruu for thailand region. Anyone can help?
Many thanks.
Btw, my phone is still s-on and i think i cant s-off because i still want a warranty(that is why i am trying to go back to stock rom). Please help.
Sorry for my English. I am not good at English(I am Thai).
Click to expand...
Click to collapse
There are only 2 versions of Hboot -> 1.25 and 1.28, there are no official older versions, maybe beta or engineering ones that were not released publicly.
You can S-OFF with unprotected Hboot, but this is not needed for you, check your CID from your phone and flash the according RUU for it, if not, take this tool and flash the S-OFF for 1.25 and after that you can flash any RUU you want as it bypasses that (as far as i know), after the RUU flashing, the HBOOT will be overwrited as well, so you will end up with a stock, locked, S-ON device with the region-stock ROM of your choice, hope this helps
Lexmazter said:
There are only 2 versions of Hboot -> 1.25 and 1.28, there are no official older versions, maybe beta or engineering ones that were not released publicly.
You can S-OFF with unprotected Hboot, but this is not needed for you, check your CID from your phone and flash the according RUU for it, if not, take this tool and flash the S-OFF for 1.25 and after that you can flash any RUU you want as it bypasses that (as far as i know), after the RUU flashing, the HBOOT will be overwrited as well, so you will end up with a stock, locked, S-ON device with the region-stock ROM of your choice, hope this helps
Click to expand...
Click to collapse
I just did what you say.
I S-OFF my phone.
I relock bootloader.
Then, I install RUU. It seems to run smoothly but in the end error 140 came up and my phone is S-ON again with still old custom rom.
What should I do?
KazumaSaruwatari said:
I just did what you say.
I S-OFF my phone.
I relock bootloader.
Then, I install RUU. It seems to run smoothly but in the end error 140 came up and my phone is S-ON again with still old custom rom.
What should I do?
Click to expand...
Click to collapse
Well, as far as i know, you unlock the bootloader again, S-OFF, and after that you flash the RUU, i didn't install any RUU's until now, you should check the guide from stona15 that can be found here, There are more details about what to do and what you want.
Hope this helps
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
Hi, i am new here and after some help. Have just had my htc one repaired for the 2nd time (blown top speaker ee didn't repair properly so had to go to htc) so now want to go to stock htc_001.
I am on orange and been waiting for the 1.29 update (never going to come) so i carried out s-off on my phone this morning and changed the cid to htc_001. That all went okay and i relocked the phone and put it back to s-on. When i check the cid on the phone and with revone it says htc_001, so that all worked okay.
I downloaded the htc ruu 1.28 from xda and installed it, it when through the checking and installed it all (took about 15mins), i got no error messages it said update successful. The phone rebooted and was wiped clean and had to go through all the settings when you first get your phone. When i go to software version its still running 1.28.61.7 (the orange software) and when i check for updates it says none available. I have tried twice to install the ruu and both times it says successful but won't write over the orange software.
I am not sure what i have done wrong but some help to get my phone onto stock htc so i get timely updates and not having to wait for rubbish orange.
Any help would be greatly appriciated
Thanks Ashley
CID is HTC__001 (capital letters, double underscore). If you're not using that it might not work...can't see why not tho
EddyOS said:
CID is HTC__001 (capital letters, double underscore). If you're not using that it might not work...can't see why not tho
Click to expand...
Click to collapse
Thanks for the quick reply, I have just double checked it is HTC-001 the only thing i can think of is its because the orange version is a higher number to the htc. Would i have to install a ruu for a different area (asia maybe) and then put it back to HTC_001 and try to update to the 1.28 htc version? I wouldnt want it to be stuck on the wrong country version if it still wont update to the europe version.
HTC__001, not HTC_001 - you HAVE to use TWO underscores...
EddyOS said:
HTC__001, not HTC_001 - you HAVE to use TWO underscores...
Click to expand...
Click to collapse
Thanks for replying again, I looked and I did only have 1 underscore. So I s-off it again and changed it to HTC__001 and ran the ruu again, it still not overwriting the orange software even though it says its completed and phone is ready to use.
I am not sure what to do now to get it to overwrite it, you anyone has any answers or things for me to try that would be great.
Ashley
I'm also having the same problem. Changed my CID to HTC__001 (confirmed in bootloader), the RUU runs all the way through successfully (takes about 10 minutes) but the update is not applied.
Not sure what I am doing wrong?
saquib said:
I'm also having the same problem. Changed my CID to HTC__001 (confirmed in bootloader), the RUU runs all the way through successfully (takes about 10 minutes) but the update is not applied.
Not sure what I am doing wrong?
Click to expand...
Click to collapse
Looks like I'm having the same issue - did either of you find a solution?
I ended up applying a nandriod backup to get 1.28.
Change cid to super cid 11111111.
saquib said:
I ended up applying a nandriod backup to get 1.28.
Click to expand...
Click to collapse
Cheers - guess I'll go that way too - don't suppose you have a link to the backup - unfortunately the BugsyLawson site is down
Sorry don't have a copy to hand, I also downloaded it from that site.
Ashes20vt said:
Thanks for replying again, I looked and I did only have 1 underscore. So I s-off it again and changed it to HTC__001 and ran the ruu again, it still not overwriting the orange software even though it says its completed and phone is ready to use.
I am not sure what to do now to get it to overwrite it, you anyone has any answers or things for me to try that would be great.
Ashley
Click to expand...
Click to collapse
I had this very similar issue yesterday, What I was trying to do was restore my other HTC One back to stock before giving it to my nephew. It made me panic a little bit because after restoring my nandroid backup I proceeded to change the CID, lock the bootloader and have S-ON. But after doing that I just remembered that I forgot to change the MID back to the original and also I have the "Tampered" flag..
So I got S-OFF again and unlocked the bootlaoder and ran the 1.28.401.7 RUU just to start fresh before I change the MID back and get rid of the "Tampered" flag. Anyway even after I ran the RUU the the original ROM was still there and the "Tampered" flag was still present. I didn't get any errors at all when running the RUU.
So in the end after erasing the cache and dalvik cache I managed to successfully get the 1.28.401.7 on the HTC One and flashed the 1.29.401.12 OTA. I then locked the bootloader and put S-ON back. I didn't bother changing the MID back because I had enough of flashing for the day.
Up to now I still don't have any clue what I did or happened why the RUU won't overwrite the original ROM (nandroid restore). I'm just glad thatit is back to stock. It may have a different stock ROM but I'm sure my nephew won't even care what he has.
Rex2369 said:
I had this very similar issue yesterday, What I was trying to do was restore my other HTC One back to stock before giving it to my nephew. It made me panic a little bit because after restoring my nandroid backup I proceeded to change the CID, lock the bootloader and have S-ON. But after doing that I just remembered that I forgot to change the MID back to the original and also I have the "Tampered" flag..
So I got S-OFF again and unlocked the bootlaoder and ran the 1.28.401.7 RUU just to start fresh before I change the MID back and get rid of the "Tampered" flag. Anyway even after I ran the RUU the the original ROM was still there and the "Tampered" flag was still present. I didn't get any errors at all when running the RUU.
So in the end after erasing the cache and dalvik cache I managed to successfully get the 1.28.401.7 on the HTC One and flashed the 1.29.401.12 OTA. I then locked the bootloader and put S-ON back. I didn't bother changing the MID back because I had enough of flashing for the day.
Up to now I still don't have any clue what I did or happened why the RUU won't overwrite the original ROM (nandroid restore). I'm just glad thatit is back to stock. It may have a different stock ROM but I'm sure my nephew won't even care what he has.
Click to expand...
Click to collapse
I managed to sort it out, not sure how I did it really. I tried to flash it manually which it didn't do as it was playing games with me. I tried the ruu with supercid which it didn't work. I put it back to HTC__001 and relocked it then tried flashing manually again, it didn't work so tried afew times but no luck. So I tried the ruu one more time and it worked, I got the 1.29.401.12 ota straight away too. I think trying to manually flash it corrupted something so the ruu was able to overwrite orange. The phone nearly broke me and was about to give in but glad I kept at it though as orange updates are ridiculous.
Thanks to all that helped me with my error of not putting 2 underscores in the cid.
I am just hoping the 4.2.2 updates on my phone okay when it's released soon.
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!