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
I have a Mint Condition HTC One phone I am trying to sell - Mostly just because I also own a Nexus 4 and love it - and decided I'd rather keep it and use the money on the HTC One on something else.
I'm having a hard time selling it because the "everything is unlocked" is making people scared to buy it.
It's S-OFF, SuperCID, TWRP 2.6.0.1, Bootloader Unlocked, Running 2.24 Firmware and Android Revolution 12.1, Sim Unlocked too.
It's originally a Rogers Canada HTC One
Is there any way (or guide) to completely make it stock again to help sell it? Any help would be appreciated.
Yep, just flash the Rogers RUU (if available) and then you're good to go! If there isn't one then use one of the Nandroids provided and then get the stock recovery and relock the bootloader
don't forget to go back to S-ON after flashing the RUU
herwegan said:
don't forget to go back to S-ON after flashing the RUU
Click to expand...
Click to collapse
Hmm... never flashed a RUU before. Will need to do some reading.
Anyone know where to find a Rogers RUU?
I don't care if its Rogers specifically - it can be Telus or Bell too as long as it works.
I just want to go back to Stock so it's capable of updating OTA somehow if possible.
bigystyle84 said:
Hmm... never flashed a RUU before. Will need to do some reading.
Anyone know where to find a Rogers RUU?
I don't care if its Rogers specifically - it can be Telus or Bell too as long as it works.
I just want to go back to Stock so it's capable of updating OTA somehow if possible.
Click to expand...
Click to collapse
just download the RUU (sorry, don't know if there is one for your carrier), be sure to be s-off, and then run the RUU.exe or flash the RUU.zip.
the RUU will flash stock recovery, stock rom and i think it will even relock your bootloader. and then you'll be able to download OTA-updates again.
last step is to put it back to s-on and you should be done..
Ruu for bell. Rogers, telus is not available yet, your best bet is to flash the stock wwe Ruu. Remember to flash the stock hboot if you are using a modified hboot for the red lines or you would brick your device
Sent from my HTC One using XDA Premium HD app
EnIXmA said:
Ruu for bell. Rogers, telus is not available yet, your best bet is to flash the stock wwe Ruu. Remember to flash the stock hboot if you are using a modified hboot for the red lines or you would brick your device
Sent from my HTC One using XDA Premium HD app
Click to expand...
Click to collapse
Thanks
I'm S-OFF using the Revone Method
I'm on firmware 2.24 and HBoot 1.54 (Still S-Off though)
If anyone has time, can somebody give me a real quick overview on what I need to do? I'll buy ya a beer!
I'm not real familiar with HTC Devices - This was my first experience and to be honest, Right now I'm wishing I didn't do this if I knew before hand I was going to flip it so fast.
Ok no problem
First download the RUU from here: http://forum.xda-developers.com/showthread.php?p=39588860
and run the .exe.
then you'll have stock hboot and stock recovery + stock rom.
After this you can use hasoon2000's toolkit to get back to s-on: http://forum.xda-developers.com/showthread.php?t=2183942
Be sure you never installed a custom hboot before and you are using a official hboot. Better check twice if the red warning text is there before you go s-on
And that's it
No beer needed, "thanks-button" is enough
Cheers
herwegan said:
Ok no problem
First download the RUU from here: http://forum.xda-developers.com/showthread.php?p=39588860
and run the .exe.
then you'll have stock hboot and stock recovery + stock rom.
After this you can use hasoon2000's toolkit to get back to s-on: http://forum.xda-developers.com/showthread.php?t=2183942
Be sure you never installed a custom hboot before and you are using a official hboot. Better check twice if the red warning text is there before you go s-on
And that's it
No beer needed, "thanks-button" is enough
Cheers
Click to expand...
Click to collapse
You cant run the RUU with Super CID. You will have to change it to one that matches the RUU you choose before running it, but keep s-off. Then you should be able to use the tool as mentioned above or do all the things manually. You can use my guide if you like:
http://forum.xda-developers.com/showthread.php?p=43458497
Thanks for the help.
Which specific RUU should I flash? I don't see a Generic WWE One in that thread - just a couple of WWE ones for Developer Editions. Should I use an AT&T one? I can change the CID back to whatever is needed.
Am I able to do this somehow with the Nandroid backup for Rogers in that thread?
Also - What do you mean by "check for the red lines" exactly? I am on HBoot 1.54, Is there a easy way of going back to 1.44?
Sorry for all the questions - I'm kinda annoyed there isn't a Rogers RUU available. Last thing I need is a bricked phone - I'm only selling it as I honestly I shouldn't have bought it to begin with (Financially)
Where are you going to try and sell it? If to another user in Canada with one of those carriers, then they wouldn't to buy the unit with a AT&T image on it, I would think.
However running the ATT one would be a very easy way to reset everything including the hboot (no worry about red lines if run the RUU). Then you could sell to a US buyer who is going to use ATT (Tmobile also has a RUU). My guide for reseting to ATT:
http://forum.xda-developers.com/showthread.php?p=43458497
There are some threads around here where users are resetting Rodgers back to stock but it is much harder without a RUU and I am not sure of your comfort level.
To use one of the Rodgers Nandroids to do a complete reset to stock I would:
Change the CID to CWS__001 and run the ATT RUU to reset all your firmware, hboot etc, back to stock. You will still have unlocked bootloader and s-off, so you can then change back to your stock CID and then use the fastboot command to boot (but not install) a custom recovery in order to restore the Rodgers Nandroid and then just relock and s-on. Should be 100% Rodgers stock.
Code:
fastboot boot yourcustomrecovery.img
You can only use this method to boot a recovery without installing it, if on hboot 1.44, so that is why I recommend using the RUU to downgrade all that stuff for you.
Let me know if you need more help. I'd be happy to guide you.
Crush
PS - Love your Avatar. You should change your location to "Parts Unknown" to complete the joke. I may have to bust out a Conky avatar now!
bigystyle84 said:
Thanks for the help.
Which specific RUU should I flash? I don't see a Generic WWE One in that thread - just a couple of WWE ones for Developer Editions. Should I use an AT&T one? I can change the CID back to whatever is needed.
Click to expand...
Click to collapse
you could take the latest open europe RUU (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7), or take an AT&T one.. don't really know which one would be better for your situation you'll know it better
Am I able to do this somehow with the Nandroid backup for Rogers in that thread?
Click to expand...
Click to collapse
this is also an option. you can flash this nandroid backup through cwm recovery. but then you'd have to manually install stock recovery and lock the bootloader/go back to s-on. why not :good:
Also - What do you mean by "check for the red lines" exactly? I am on HBoot 1.54, Is there a easy way of going back to 1.44?
Click to expand...
Click to collapse
you can stay on 1.54 if everything works fine after flashing the older firmware. the "warning text" is related to this thread: http://forum.xda-developers.com/showthread.php?t=2316726
but if you've never installed a custom HBoot you don't have to worry about this when going back to s-on. just check once if the red warning text in the bootscreen is there.
Sorry for all the questions - I'm kinda annoyed there isn't a Rogers RUU available. Last thing I need is a bricked phone - I'm only selling it as I honestly I shouldn't have bought it to begin with (Financially)
Click to expand...
Click to collapse
hope it works :fingers-crossed:
crushalot said:
Where are you going to try and sell it? If to another user in Canada with one of those carriers, then they wouldn't to buy the unit with a AT&T image on it, I would think.
However running the ATT one would be a very easy way to reset everything including the hboot (no worry about red lines if run the RUU). Then you could sell to a US buyer who is going to use ATT (Tmobile also has a RUU). My guide for reseting to ATT:
http://forum.xda-developers.com/showthread.php?p=43458497
There are some threads around here where users are resetting Rodgers back to stock but it is much harder without a RUU and I am not sure of your comfort level.
To use one of the Rodgers Nandroids to do a complete reset to stock I would:
Change the CID to CWS__001 and run the ATT RUU to reset all your firmware, hboot etc, back to stock. You will still have unlocked bootloader and s-off, so you can then change back to your stock CID and then use the fastboot command to boot (but not install) a custom recovery in order to restore the Rodgers Nandroid and then just relock and s-on. Should be 100% Rodgers stock.
Code:
fastboot boot yourcustomrecovery.img
You can only use this method to boot a recovery without installing it, if on hboot 1.44, so that is why I recommend using the RUU to downgrade all that stuff for you.
Let me know if you need more help. I'd be happy to guide you.
Crush
PS - Love your Avatar. You should change your location to "Parts Unknown" to complete the joke. I may have to bust out a Conky avatar now!
Click to expand...
Click to collapse
Hey, I'm trying to do the same thing as OP, and this thread has been the closest thing to my issue. I'm trying to return everything on my phone to stock, however my Canadian carrier is Bell. Currently my HTC One has the bootloader unlocked, is rooted, TWRP recovery, and TrickDroid installed.
If I understand your instructions correctly, what I should do (given I want to restore using a nandroid backup) is:
1) S-Off my phone
2) Change the CID to CWS___001 and run the ATT RUU
3) Change the CID back to my original (BM_001 is what I think it is, do you know how I can make sure? What command to run for ADB?)
4) The Nandroid backup from http://forum.xda-developers.com/showthread.php?t=2207874&highlight=bell+update for my phone is for CWM (it's this one: M7 CWM Nandroid Backup / CID BM___001 / 1.29.666.5), does that mean I have to change my recovery from TWRP to CWM at this point?
5) Use fastboot to boot the recovery --> two questions regarding this, 1) why would I not install the .zip I downloaded from step 4? 2) where do I get the recovery.img? Just the one that is in the zip? In which case, shouldn't I also has to boot the boot.img or anything else?
6) I also want to upgrade the radio, should that be done last?
Thanks for all your help!
Lastly, I'm looking for a ROM to flash afterwards, I was wondering if you had any suggestions/know of a ROM that can allow me to use the swipe2sleep features, as well as hold the back touch button to force kill an app.
Just sell it on swappa. They love rooted unlocked modded phones.
I got myself in a bit of a dead zone here.
I have my HTC one. Its HTC__001 WWE Europe. It OTA upgraded to 2.24.401.1.
When I saw that you can convert to a GPE I really wanted to check it out specially after users reported success in getting OTA updates. But I quickly realized I needed S-Off and thats not available yet.
I decided to at least take it to a test drive with ARHD GPE 3.0. I downloaded the latest RUU for my device (1.28.401.7) thinking I would need that to get back to stock. I went and unlocked the bootloader at HTC dev. Flashed CWM recovery and flashed ARHD GPE 3.0. Played around with it for a bit and now when I needed to go back to stock.
RUU.exe file got stuck at updating signature then returned 155 unknown. I realized maybe its attempting to downgrade the bootloader so i looked around for a 2.24.401.1 RUU but its not available yet.
I looked at Nandroid backups and found 1.28.401.7 HTC__001 but its UK unbranded. When I restored this version it loaded up but my touch screen didnt work at all. I flashed back ARHD to get touch capability back.
So my question is... Any chance anyone can nandroid backup the stock 2.24.401.1 i need? How can I go to stock now? Am I stuck with custom roms untill atleast s-off or HTC decides 2.24.401.1 RUU should be made available?
Thanks!
+1
Are you s off?? Downgrade your hboot to 1.44 and then flash the ruu for your device....
Sent from my HTC One using xda premium
No unfortunately im s-on... Funny how being a good boy and being s-on HTC rewards me with no option to go back to stock...
Sent from my HTC One using xda app-developers app
LOL............ I am in same postion . want to go back to stock for updates but cant !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
AllAboutTheCore said:
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
Click to expand...
Click to collapse
You cant s-off on hboot 154 yet. Unless I am mistaken.
Like op says we need a nandroid of firmware think that's only way until ruu is releasee ; (
Sent from my GT-I9100 using xda app-developers app
ipmanwck said:
You cant s-off on hboot 154 yet. Unless I am mistaken.
Like op says we need a nandroid of firmware think that's only way until ruu is releasee ; (
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
2 things:
1) I'll quote what I said, I never said S-Off was available .. "Obviously you'll need S-Off for Hboot 1.54 if/when it happens"
2) What I said above for going to stock is a way of doing it, a Nandroid is not the only way.
AllAboutTheCore said:
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
Click to expand...
Click to collapse
I actually did this and Im running it right now without problems...
But Im not sure id be getting OTAs as the bootloader main ver still says 2.24.401.1 and not 2.24.401.8. I dont think Mike made a 2.24.401.1 available.
Its a bit disappointing. Im fine with having my bootloader tampered and relocked and s-on as long as I got stock running like it should be. i dont understand why HTC gives you the option to unlock ur bootloader to play around with custom firmware but not allow you to go back to stock. im guessing the RUU is on the way but I have my doubts... Just like s-off.
Sent from my HTC One using xda app-developers app
ossman said:
I actually did this and Im running it right now without problems...
But Im not sure id be getting OTAs as the bootloader main ver still says 2.24.401.1 and not 2.24.401.8. I dont think Mike made a 2.24.401.1 available.
Its a bit disappointing. Im fine with having my bootloader tampered and relocked and s-on as long as I got stock running like it should be. i dont understand why HTC gives you the option to unlock ur bootloader to play around with custom firmware but not allow you to go back to stock. im guessing the RUU is on the way but I have my doubts... Just like s-off.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Nah, the stock firmware for 2.24.401.8 is not available yet, only a customised one which would require S-Off anyway. The method I mentioned is the only way at the moment to get as close to stock as possible without being able to go S-Off and flash an older RUU. When Mike gets hold of the stock firmware to post, I'm sure he will ... I can't see any 2.24 RUU's being available seeing that HTC are pushing for a 4.3 release by the end of September, so I'd wait anyways, unless you need to return your device for warranty purposes of course.
As for you getting OTA updates ... I haven't installed the .8 ROM but it shouldn't affect it as the base you are on is still an older base than what you'd be trying to update to but I'm not 100% on that as I haven't flashed it as my device is away for repair lol. I would imagine that the 2.24.401.8 firmware would be about soon enough and then you would be able to revert to stock with the newest base but obviously as you said yourself, without S-Off you wouldn't be able to wipe any trace of you flashing and modding.
I think HTC only allow you to unlock your bootloader because they can void so many warranties that way and bill for repairs lol ... Maybe I'm being cynical but I do agree that they could provide a stock RUU for people to return to stock, without all the hassle of S-Off or waiting months before any suitable RUU is available but sometimes you have to just suck it up and live with what we have lol
ossman said:
I got myself in a bit of a dead zone here.
I have my HTC one. Its HTC__001 WWE Europe. It OTA upgraded to 2.24.401.1.
When I saw that you can convert to a GPE I really wanted to check it out specially after users reported success in getting OTA updates. But I quickly realized I needed S-Off and thats not available yet.
I decided to at least take it to a test drive with ARHD GPE 3.0. I downloaded the latest RUU for my device (1.28.401.7) thinking I would need that to get back to stock. I went and unlocked the bootloader at HTC dev. Flashed CWM recovery and flashed ARHD GPE 3.0. Played around with it for a bit and now when I needed to go back to stock.
RUU.exe file got stuck at updating signature then returned 155 unknown. I realized maybe its attempting to downgrade the bootloader so i looked around for a 2.24.401.1 RUU but its not available yet.
I looked at Nandroid backups and found 1.28.401.7 HTC__001 but its UK unbranded. When I restored this version it loaded up but my touch screen didnt work at all. I flashed back ARHD to get touch capability back.
So my question is... Any chance anyone can nandroid backup the stock 2.24.401.1 i need? How can I go to stock now? Am I stuck with custom roms untill atleast s-off or HTC decides 2.24.401.1 RUU should be made available?
Thanks!
Click to expand...
Click to collapse
i got an nandroid backup for you fully stock unrooted : https://mega.co.nz/#!AUZGkKwC!EAfhUXYAgjpAR42jGzG_mhzWJjwcs1j7R_tm_HPMDAo
I know, this question is asked a lot but I haven't been able to find any threads that reflect my exact situation so please hear me out!
I have a Developer Edition from launch and recently wanted to try out making it a Google Play Edition, so I did that.
Got S-Off, unlocked, rooted, flashed with the GPE RUU
However I find myself missing the camera features and now that 4.3 is out and with rumors of Sense 5.5 I'd like to go back to Sense
Here's where I'm confused: My custom recovery is gone since flashing the RUU and my bootloader now says that it's locked, even though it's a Developer Edition. I understand that the Google Play Edition doesn't come with an unlocked bootloader so my assumption is that the RUU simply resets it.
Here's my tl;dr version of the question: Do I need to go through the whole unlocking process to go back to sense? Can I just flash the RUU for the Developer Edition and automatically get my unlocked bootloader back? I didn't change the CID or any of that, all I did was flash the RUU.
Thanks for any help!!
Edit: The only thing truly confusing me is the fact that the bootloader got locked (or so that's what is says)
docdoc518 said:
I know, this question is asked a lot but I haven't been able to find any threads that reflect my exact situation so please hear me out!
I have a Developer Edition from launch and recently wanted to try out making it a Google Play Edition, so I did that.
Got S-Off, unlocked, rooted, flashed with the GPE RUU
However I find myself missing the camera features and now that 4.3 is out and with rumors of Sense 5.5 I'd like to go back to Sense
Here's where I'm confused: My custom recovery is gone since flashing the RUU and my bootloader now says that it's locked, even though it's a Developer Edition. I understand that the Google Play Edition doesn't come with an unlocked bootloader so my assumption is that the RUU simply resets it.
Here's my tl;dr version of the question: Do I need to go through the whole unlocking process to go back to sense? Can I just flash the RUU for the Developer Edition and automatically get my unlocked bootloader back? I didn't change the CID or any of that, all I did was flash the RUU.
Thanks for any help!!
Edit: The only thing truly confusing me is the fact that the bootloader got locked (or so that's what is says)
Click to expand...
Click to collapse
Do you still have s-off? Then you can flash a dev edition RUU to get back sense.. If you want to keep s-off, flash a 4.1.2 RUU, get s-off and then ota update to the latest version.
When you flash the dev RUU, you'll get back your unlocked bootloader.
Sent from my iPod touch using Tapatalk
n1234d said:
Do you still have s-off? Then you can flash a dev edition RUU to get back sense.. If you want to keep s-off, flash a 4.1.2 RUU, get s-off and then ota update to the latest version.
When you flash the dev RUU, you'll get back your unlocked bootloader.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I do still have s-off, if I flash the latest RUU for dev edition will I lose s-off? Will I lose it if I flash any RUU?
Just curious at this point.
and THANK YOU!
docdoc518 said:
I do still have s-off, if I flash the latest RUU for dev edition will I lose s-off? Will I lose it if I flash any RUU?
Just curious at this point.
and THANK YOU!
Click to expand...
Click to collapse
Some say you lose s-off, some say you don't..Afaik, an RUU is the safest way to go back to s-on. So to be on the safer side get the dev edition RUU for a 4.1.2 base and flash it.. If you lose s-off use Revone, then ota update to the latest 3.xx base. This will also update your hboot to 1.55, so make sure you're s-off before upgrading, as 1.55 cannot be s-offed yet.
Ps: Always use the thanks button
Sent from my iPod touch using Tapatalk
so as long as the you are s-off, you can ruu to any version even if you are at 1.54 hboot?
n1234d said:
Some say you lose s-off, some say you don't..Afaik, an RUU is the safest way to go back to s-on. So to be on the safer side get the dev edition RUU for a 4.1.2 base and flash it.. If you lose s-off use Revone, then ota update to the latest 3.xx base. This will also update your hboot to 1.55, so make sure you're s-off before upgrading, as 1.55 cannot be s-offed yet.
Ps: Always use the thanks button
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
You need to downgrade the HBOOT first following post #2 in the GPe conversion thread, and then flash the RUU. You will NOT lose S-OFF but you will lose all data on the phone so back it up first
EddyOS said:
You need to downgrade the HBOOT first following post #2 in the GPe conversion thread, and then flash the RUU. You will NOT lose S-OFF but you will lose all data on the phone so back it up first
Click to expand...
Click to collapse
So considering I'm S-Off with the GPE RUU flashed, hboot 1.54
Will the S-Off allow me to directly flash the 4.3 RUU exe from htcdev? Will I maintain S-Off?
I'm just a bit confused now as you guys somewhat told me the opposite things, I appreciate the help though, getting great information
docdoc518 said:
So considering I'm S-Off with the GPE RUU flashed, hboot 1.54
Will the S-Off allow me to directly flash the 4.3 RUU exe from htcdev? Will I maintain S-Off?
I'm just a bit confused now as you guys somewhat told me the opposite things, I appreciate the help though, getting great information
Click to expand...
Click to collapse
Follow what eddy says, he's the man @eddy, how does the hboot version make a difference??
Sent from my iPod touch using Tapatalk
I'm not sure, here's what I found today...
I was running the leaked Sense 5.5 system dump and FW and wanted to go back to the 1.28.401.7 RUU so I could get the official update. Not an issue I thought as I'd just flash it and away I go as I'd done in the past when on hboot 1.54. It gave the 155 error about not being the right RUU even though I'm S-OFF. So I flashed the hboot in the GPe conversion thread #2 which put it back to 1.44 and the RUU worked fine so it must be something with the new 1.55 hboot that stops it working. I can't be certain but it worked for me
EddyOS said:
I'm not sure, here's what I found today...
I was running the leaked Sense 5.5 system dump and FW and wanted to go back to the 1.28.401.7 RUU so I could get the official update. Not an issue I thought as I'd just flash it and away I go as I'd done in the past when on hboot 1.54. It gave the 155 error about not being the right RUU even though I'm S-OFF. So I flashed the hboot in the GPe conversion thread #2 which put it back to 1.44 and the RUU worked fine so it must be something with the new 1.55 hboot that stops it working. I can't be certain but it worked for me
Click to expand...
Click to collapse
Hmm, I have hboot 1.54 not 1.55, so it sounds like I may be able to flash right to 4.3 with the .exe (at least from what I understand)
If it is incompatible it should just give me an error, correct?
I'm willing to take the extra steps but if they're not totally necessary then I'd much prefer to just go down the simpler path
Also, I've got CID BS_US001, what are the benefits of changing it to supercid? Would I get OTAs such as the Sense 5.5 faster?
Hopefully I'm not being a pain, I'm trying my best to learn.
You should be fine on that HBOOT, just try it and if it works it works! If not, you'll get an error and then you just following the second post in the GPe conversion thread
docdoc518 said:
Hmm, I have hboot 1.54 not 1.55, so it sounds like I may be able to flash right to 4.3 with the .exe (at least from what I understand)
If it is incompatible it should just give me an error, correct?
I'm willing to take the extra steps but if they're not totally necessary then I'd much prefer to just go down the simpler path
Also, I've got CID BS_US001, what are the benefits of changing it to supercid? Would I get OTAs such as the Sense 5.5 faster?
Hopefully I'm not being a pain, I'm trying my best to learn.
Click to expand...
Click to collapse
Yep, go ahead and try, if it gives you an error, post back.
AFAIK, the dev edition BS_US001 gets OTAs the quickest, so you could keep it at that. SuperCID will allow you to flash any RUU/OTA, even of a different region/MID/CID
Nope, you're not being a pain We're all trying to learn and help here
Good news, I tried flashing the 4.3 RUU exe from HTCDev and it wouldn't work so I just took the longer route and flashed 1.44 hboot, flashed stock 4.1 RUU and then exe flashed up to 4.3
So I'm back on Sense and I'm happy, the only thing that was a slight setback was my bootloader, for some reason it did not unlock after flashing the Brightstar RUU so I went through the process on HTC dev and reflashed the 4.3 RUU to get back the flashlight and other apps lost through the unlocking process. Maybe I should have unlocked it through fastboot while on the GPE ROM? Not sure, but either way I'm back on Sense, bootloader unlocked and S-Off maintained so a huge huge THANK YOU from me.
Now I'm just waiting for Sense 5.5!
You guys are awesome :good:
docdoc518 said:
Good news, I tried flashing the 4.3 RUU exe from HTCDev and it wouldn't work so I just took the longer route and flashed 1.44 hboot, flashed stock 4.1 RUU and then exe flashed up to 4.3
So I'm back on Sense and I'm happy, the only thing that was a slight setback was my bootloader, for some reason it did not unlock after flashing the Brightstar RUU so I went through the process on HTC dev and reflashed the 4.3 RUU to get back the flashlight and other apps lost through the unlocking process. Maybe I should have unlocked it through fastboot while on the GPE ROM? Not sure, but either way I'm back on Sense, bootloader unlocked and S-Off maintained so a huge huge THANK YOU from me.
Now I'm just waiting for Sense 5.5!
You guys are awesome :good:
Click to expand...
Click to collapse
All you had to do was flash the HBOOT in post #2 of the GPe conversion thread and then the 4.3 RUU and you would have had the same result
EddyOS said:
All you had to do was flash the HBOOT in post #2 of the GPe conversion thread and then the 4.3 RUU and you would have had the same result
Click to expand...
Click to collapse
Newbie move I suppose :angel: haha
I've been rooting and flashing ROMs on my Androids since the G1/Dream believe it or not, but with every new phone/manufacturer there's always new terminology and steps to be taken so I feel like I start over every single time, which honestly isn't much of a bad thing, keeps things exciting (even though HTC made the G1 but that was what feels like ages ago now)
Thanks again guys, it's hard not to feel intimidated but it's been an extremely pleasant experience learning from you. This is why xda is by far the best site you can find for these things.
Cheers
I was originally on Sense 6 with Hboot 1.57, however I made a switch to GPE and flashed the ruu. Prior to this I changed my cid to supercid 1111111 so that I could do so. My Hboot has dropped to 1.54.
If I wish to return to Sense do I need to find my regional ruu, or as I have changed my cid I can pretty much wwe release? Also, do I need to change my Hboot to a lower version or leave as is?
While I'm on GPE, can I flash aosp roms such as cm, aokp etc?
Thank you.
maritimesbob said:
I was originally on Sense 6 with Hboot 1.57, however I made a switch to GPE and flashed the ruu. Prior to this I changed my cid to supercid 1111111 so that I could do so. My Hboot has dropped to 1.54.
If I wish to return to Sense do I need to find my regional ruu, or as I have changed my cid I can pretty much wwe release? Also, do I need to change my Hboot to a lower version or leave as is?
While I'm on GPE, can I flash aosp roms such as cm, aokp etc?
Thank you.
Click to expand...
Click to collapse
1. The best way to get back your warranty (I think you want it) is to change CID to your stock CID and flash RUU for your CID.
2. Yoou don;t have to change Hboot coz RUU will do it for you so leave it as is.
3. Yes you can flash all Custom ROMS not only AOSP but it's good to have SuperCID.
No I'm not after keeping my warranty, just asking in case I wanted to switch back to Sense. I can flash a Sense rom over GPE? I wasn't aware that was possible. Figured I would need to go back to a Sense base via ruu.
maritimesbob said:
No I'm not after keeping my warranty, just asking in case I wanted to switch back to Sense. I can flash a Sense rom over GPE? I wasn't aware that was possible. Figured I would need to go back to a Sense base via ruu.
Click to expand...
Click to collapse
Yes to go back to Sense you should flash a Sense RUU. And to be on the safe side you should use the earliest ruu you can downgrading to hboot 1.4.4. Then update the phone to the latest sense.
If you don't use an ruu to revert you risk running into problems later. And as your obviously s-off do not under any circumstance 're-lock your bootloader or go back to s-on. you will be stuck with a brick.
Ok, any tips to avoid accidently relocking the bootloader?
I was checking the GPE conversion thread, it simply states flashing the hboot 1.44 ruu, flash a stock ruu, pretty much it? Is there anything that could cause the bootloader to lock or for me to lose s-off? I paid sunshine for that, don't fancy losing it again!!
Assume, I'll have to root and flash custom recovery again? Yeah don't fancy going through the unlocking bootloader procedure again.
I simply want to go back to Sense, retain s-off and my unlocked bootloader so I can continue flashing custom roms and all that fun.
I have supercid 1111111 which means I can use a Euro ruu or any other? I was on Vodafone UK.
Thanks,
maritimesbob said:
Ok, any tips to avoid accidently relocking the bootloader?
I was checking the GPE conversion thread, it simply states flashing the hboot 1.44 ruu, flash a stock ruu, pretty much it? Is there anything that could cause the bootloader to lock or for me to lose s-off? I paid sunshine for that, don't fancy losing it again!!
Assume, I'll have to root and flash custom recovery again? Yeah don't fancy going through the unlocking bootloader procedure again.
I simply want to go back to Sense, retain s-off and my unlocked bootloader so I can continue flashing custom roms and all that fun.
I have supercid 1111111 which means I can use a Euro ruu or any other? I was on Vodafone UK.
Thanks,
Click to expand...
Click to collapse
Well you'll be pleased to know that if you used Sunshine to s-off. Should you need it again you won't have to pay. You only pay once per device.
Locking the bootloader and switching s-on can only be done manually using specific fastboot commands. Or Very specific dd commands in recovery. It's not likely to happen accidentally.
I only warned you of it because some users made the mistake of thinking it was necessary. But if the phone ends up locked or s-on without a proper conversion they can become impossible to recover.
All done, quite painless really. Thanks for the help.