I tried following this guide:
thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2849-how-restore-stock-rooted-non-rooted-users.html
I successfully flashed MR1, now when I go to flash the bootloader using the same PG05IMG.zip method it says bypassed. I checked the md5 hash, it checked out okay. What would cause this?
This is for a warranty replacement, I just need the phone to be stock again!
Just find the latest unrooted gingerbread rom that leaked and flash it, it will go back to stock. check here or android police for the download....
Jrocker23 said:
Just find the latest unrooted gingerbread rom that leaked and flash it, it will go back to stock. check here or android police for the download....
Click to expand...
Click to collapse
Thanks, I will give that a shot.
If you originally used the Revolutionary root method, its not just flashing a new hboot, as its a hboot that doesn't allow it to be easily overwritten. This stops you from accidentally flashing a s-on hboot at a time you didn't mean to (most likely through ruu). If you did that, you have to adb some files to your phone to put a stock s-on hboot on. If you did the old downgrade root method, i would try downloaded the files from somewhere other than where you did this time, and try again.
nbdysreal said:
If you originally used the Revolutionary root method, its not just flashing a new hboot, as its a hboot that doesn't allow it to be easily overwritten. This stops you from accidentally flashing a s-on hboot at a time you didn't mean to (most likely through ruu). If you did that, you have to adb some files to your phone to put a stock s-on hboot on. If you did the old downgrade root method, i would try downloaded the files from somewhere other than where you did this time, and try again.
Click to expand...
Click to collapse
This is exactly what I needed to know.
For people in the same boat this is what I did (sorry for the links, apparently I don't have enough posts)
Follow this guide to flash a different hboot:
thunderboltforums.com/forum/htc-thundebolt-hacking-guides/5427-rs-guide-how-return-stock-revolutionary-root.html
Then flash the PG05IMG from here:
droid-life.com/2011/09/27/finally-the-htc-thunderbolt-gingerbread-update-appears-to-be-ready-as-build-2-11-605-3/
so to get back to stock, if you didnt use the rev root method, what exactly do you flash? could someone link me?
shawnn218 said:
so to get back to stock, if you didnt use the rev root method, what exactly do you flash? could someone link me?
Click to expand...
Click to collapse
What I outlined above should get you to stock.
even if i rooted the normal way and not rev?
http://forum.xda-developers.com/showthread.php?t=1310014&highlight=return+to+stock
2/3 of the way down under this section "Putting current stock firmware and s-on back onto the phone"
This will put you back to STOCK / S-0N from the old downgrade root method. If you just want a stock rooted rom, flash one. Unless you are taking it in for service or returning it, there really isn't a need to unroot it just to put a stock rom on.
hi
this zip file in this thread http://forum.xda-developers.com/showthread.php?t=2123337
was the latest version of the software i was running before i unlocked the bootloader and installed a custom rom
in the thread the zip is listed as an ruu how do i use this to get back to stock?
in the zip file is meta-info , system ,firmware.zip,fotaboot and skin_fota
That is not a RUU, its a OTA file. RUU is an executable (.exe) file.
An OTA will not return you back to stock, either. For instance, it will no return you to stock recovery (which RUU will do). Better off to find and run the appropriate RUU for your version (if one exists).
redpoint73 said:
That is not a RUU, its a OTA file. RUU is an executable (.exe) file.
An OTA will not return you back to stock, either. For instance, it will no return you to stock recovery (which RUU will do). Better off to find and run the appropriate RUU for your version (if one exists).
Click to expand...
Click to collapse
You can technically flash the recovery.img from the OTA and then flash the OTA through stock recovery though I can confirm that evenso, the phone is not returned to 100% stock. The htc splash screen and I'm sure other things do not get flashed. I have run an OTA a few times though and never had any problems.
RUU IS the best way to return to 100% stock though.
thanks for the ultra quick replies
i am really struggling to find an ruu for my phone
i am correct in that i cannot flash a lower ruu?
if i go supercid can i flash any ruu?
emu123 said:
i am really struggling to find an ruu for my phone
Click to expand...
Click to collapse
Based on this, it doesn't seem that there is an RUU for the HK Jellybean stock ROM.
emu123 said:
i am correct in that i cannot flash a lower ruu?
if i go supercid can i flash any ruu?
Click to expand...
Click to collapse
If S-on, correct, you cannot flash a previous version RUU (usually hboot version check is what prevents this).
SuperCID will allow you to flash an RUU for another region, but still will not allow an RUU with previous version hboot to be installed (SuperCID bypasses carrier/region check, not version check). You also need to be really careful with SuperCID; since with SuperCID and S-on, some Jellybean RUUs will brick the device.
S-off bypasses all security checks, and will allow you to flash a previous RUU.
Hello there guys,
Been trying to root my XL from Telstra (AUS) but some weird things are going on.
Can't figure out why i'm unable to to SuperCid my phone, my current Supercid is TELST001
http://forum.xda-developers.com/showthread.php?t=1952038
Also, tried to root my phone using this thread below:
http://forum.xda-developers.com/showthread.php?t=1859478
So far, I have achieved to Installed S-OFF and CWM.
What i'm trying to do here is to use any 4.22 Android Rom with sense 5, like CleanROM or CyanogenMod 10
Im uploading some of the current photos taken so you guys can have more information on S-OFF and CWM.
Thanks in advance.
Ps: One of the pictures was a Failed OTA from Telstra, is there a way to go back to and be able to install the OTA from Telstra instead of any custom ROM (In case we cant find what is causing the phone to block the supercid and the super SU)
Ota won't work with a custom recovery.
I am running MagioR4 sense 5 4.2.2 you can install that now without doing anything else to your phone. There are a few others as well, but this is only one I've been running so I can't say much about others, but assume they will work out just as well.
Sent from my HTC One XL using xda app-developers app
31ken31 said:
Ota won't work with a custom recovery.
I am running MagioR4 sense 5 4.2.2 you can install that now without doing anything else to your phone. There are a few others as well, but this is only one I've been running so I can't say much about others, but assume they will work out just as well.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hi there mate,
Tried to run Super Su and shows as the phone been not rooted, i'm a bit confused atm.
Is there a need to Super Cid and if i were to use the OTA, can i remove the custom recovery?
Desertum said:
Can't figure out why i'm unable to to SuperCid my phone, my current Supercid is TELST001
Click to expand...
Click to collapse
That's the carrier ID (CID) not SuperCID. SuperCID is 11111111 or 22222222. I think you know that, but let's get the terms right to avoid confusion.
You don't have S-off. It says right in your screenshot that the phone is still s-on.
But you it says UNLOCKED, so your bootloader is unlocked. All S-on means is that you can still install custom ROMs, you just have to flash boot.img seperately from fastboot.
As mentioned, you have to return to stock recovery in order to be able to install OTAs. Easiest way is to RUU back to stock. But be completely sure you are not SuperCID, otherwise S-on + SuperCID + Jellybean RUU = BRICK.
Personally, going stock just to install the stock 4.2.2 ROM is a step backward, not forward, as you already have an unlocked bootloader and cutom recovery. But you also seem confused about a number of things. I would suggest reading and more fully understanding the concepts and processes before proceeding with any further mods to the phone.
---------- Post added at 09:17 AM ---------- Previous post was at 09:12 AM ----------
Desertum said:
Hi there mate,
Tried to run Super Su and shows as the phone been not rooted, i'm a bit confused atm.
Is there a need to Super Cid and if i were to use the OTA, can i remove the custom recovery?
Click to expand...
Click to collapse
Unlocking the bootloader does't root the phone. You can flash an SU package in recovery to obtain root, or flash a rooted ROM.
You don't need SuperCID for anything but s-off.
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
Desertum said:
What i'm trying to do here is to use any 4.22 Android Rom with sense 5, like CleanROM or CyanogenMod 10
Click to expand...
Click to collapse
CleanROM is neither 4.2.2 nor Sense 5. CM10 is an AOSP ROM, so by definition not a Sense ROM at all.
redpoint73 said:
That's the carrier ID (CID) not SuperCID. SuperCID is 11111111 or 22222222. I think you know that, but let's get the terms right to avoid confusion.
You don't have S-off. It says right in your screenshot that the phone is still s-on.
But you it says UNLOCKED, so your bootloader is unlocked. All S-on means is that you can still install custom ROMs, you just have to flash boot.img seperately from fastboot.
As mentioned, you have to return to stock recovery in order to be able to install OTAs. Easiest way is to RUU back to stock. But be completely sure you are not SuperCID, otherwise S-on + SuperCID + Jellybean RUU = BRICK.
Personally, going stock just to install the stock 4.2.2 ROM is a step backward, not forward, as you already have an unlocked bootloader and cutom recovery. But you also seem confused about a number of things. I would suggest reading and more fully understanding the concepts and processes before proceeding with any further mods to the phone.
---------- Post added at 09:17 AM ---------- Previous post was at 09:12 AM ----------
Unlocking the bootloader does't root the phone. You can flash an SU package in recovery to obtain root, or flash a rooted ROM.
You don't need SuperCID for anything but s-off.
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
CleanROM is neither 4.2.2 nor Sense 5. CM10 is an AOSP ROM, so by definition not a Sense ROM at all.
Click to expand...
Click to collapse
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Thanks
Desertum said:
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Thanks
Click to expand...
Click to collapse
No you've got it backwards. The boot.img goes in your fastboot folder on your pc, not on your phone.
You need to fastboot flash the boot.img from each ROM you want to flash. So, if you want to install CM10.2, you must extract the boot.img from the ROM zip and put it in your fastboot folder on your pc (not your sd card in your phone). Then you put the ROM zip on your phone, and install it in recovery (after wiping cache/dalvik cache/factory reset/system), then reboot to bootloader and flash the boot.img using fastboot. You must follow this process for each new ROM you want to flash.
Do a backup of your current setup in recovery before flashing anything new though.
Sent from my Evita
---------- Post added at 11:42 PM ---------- Previous post was at 11:40 PM ----------
By the way, even though our phone doesn't have a physical sd slot, we refer to the stage as the sd card.
Sent from my Evita
Desertum said:
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
Click to expand...
Click to collapse
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
Desertum said:
Hello there,
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Click to expand...
Click to collapse
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
redpoint73 said:
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
Click to expand...
Click to collapse
Hi there,
Im trying to Update the RUU as per this thread:
http://forum.xda-developers.com/showthread.php?t=2382933
However, I'm getting an error called 155, which says that Im trying to install the wrong RUU
I was trying to update the RUU, then restart the phone, went into S-off, then into recovery and Wipe factory/data reset, then install the CM10.2 build
Is something missing here?
Thanks.
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Sent from my Evita
---------- Post added at 12:41 AM ---------- Previous post was at 12:41 AM ----------
timmaaa said:
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Also, what do you mean you "went into s-off"?
Sent from my Evita
Click to expand...
Click to collapse
Sent from my Evita
Desertum said:
Im trying to Update the RUU as per this thread:
http://forum.xda-developers.com/showthread.php?t=2382933
However, I'm getting an error called 155, which says that Im trying to install the wrong RUU
Click to expand...
Click to collapse
Its saying wrong RUU, because its the wrong RUU.
If you are S-on, you can only run an RUU meant for your Telstra version.
It appears you ignored my previous advice to read up on the basic concepts and procedures, before continuing to try to mod the phone.
redpoint73 said:
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
Click to expand...
Click to collapse
timmaaa said:
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Sent from my Evita
---------- Post added at 12:41 AM ---------- Previous post was at 12:41 AM ----------
Sent from my Evita
Click to expand...
Click to collapse
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
And yes, I'm trying to install the 3.18 RUU, currently using 3.17.
Thanks.
Desertum said:
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
Click to expand...
Click to collapse
I think this is a lost cause. You aren't even reading what people have replied to you. I clearly stated in post #4 above, you DO NOT have s-off.
Right in your second screen shot (white bootloader screen) it says S-ON (third line of text). This means you DO NOT HAVE S-OFF.
Desertum said:
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
And yes, I'm trying to install the 3.18 RUU, currently using 3.17.
Thanks.
Click to expand...
Click to collapse
Like Redpoint just said, you can't install an RUU from another carrier (the 3.18 RUU is at&t) while you're s-on. You don't have s-off, look at the screenshots you attached earlier, in your bootloader it says s-on. You have an unlocked bootloader which is an entirely different thing.
Unless you've flashed a superuser zip or flashed a rooted ROM you don't have root. Root just means that you have administrative access to system files in a ROM. The real thing you need to install custom ROMs is an unlocked bootloader and a custom recovery.
I'm gonna be honest, you're in over your head and you're ignoring good advice which was given to prevent you from damaging your phone.
You really have two choices: either do a hell of a lot of reading until you have a firm understanding of what you're doing, or leave your phone alone. The way you're going right now you're on track to destroy your phone.
Do yourself a favour and click on the link in my signature. It's a resource thread, it contains all the information you'll ever need. I'll put it this way, I read for a week or two before I even started modifying my phones.
Sent from my Evita
John uallowt
redpoint73 said:
Its saying wrong RUU, because its the wrong RUU.
If you are S-on, you can only run an RUU meant for your Telstra version.
It appears you ignored my previous advice to read up on the basic concepts and procedures, before continuing to try to mod the phone.
Click to expand...
Click to collapse
I have not ignored your advised, It rather hard to understand all this, since there is no Indication for the right RUU, since the thread i'm looking at, does not mention anything in regards of using a different RUU.
I apologise If you feel like i'm ignoring your advised, I would rather ask you now, What should I do?
Are you able to do some prompts in regards of what to do?
So far, IMAO I need to to this:
Flash the Correct RUU (Gotta find it first)
Use S-off to Install the Custom ROM (ROM is already copied to the phone's memory)
Install the new Custom ROM, however, not to sure about the GApps, which are google apps.
http://www.reddit.com/r/Android/comments/1kbeoh/gapps_20130813_for_android_43_and_20130812_for/
I guess that you need to copy them before you install the new ROM?
Thank you for your patience.
redpoint73 said:
I think this is a lost cause. You aren't even reading what people have replied to you. I clearly stated in post #4 above, you DO NOT have s-off.
Right in your second screen shot (white bootloader screen) it says S-ON (third line of text). This means you DO NOT HAVE S-OFF.
Click to expand...
Click to collapse
Fair enough, I need to read more about it.
As i Have atm S-ON and I need to have S-off to be able to install the RUU and the custom Rom, I either need to accomplish this :
SuperUser the Phone with the current Stock ROM
or
Install a Rooted ROM, correct?
Desertum said:
I have not ignored your advised, It rather hard to understand all this, since there is no Indication for the right RUU, since the thread i'm looking at, does not mention anything in regards of using a different RUU.
I apologise If you feel like i'm ignoring your advised, I would rather ask you now, What should I do?
Click to expand...
Click to collapse
As you've been told at least 3 times now, what you should do is READ READ READ.
None of this is hard to understand once you start diving into it and learning.
I'm personally not going to spoonfeed you any more steps (and suggest against doing it either), as shortcutting the learning process is only going to turn your phone into an expensive paperweight.
timmaaa said:
Like Redpoint just said, you can't install an RUU from another carrier (the 3.18 RUU is at&t) while you're s-on. You don't have s-off, look at the screenshots you attached earlier, in your bootloader it says s-on. You have an unlocked bootloader which is an entirely different thing.
Unless you've flashed a superuser zip or flashed a rooted ROM you don't have root. Root just means that you have administrative access to system files in a ROM. The real thing you need to install custom ROMs is an unlocked bootloader and a custom recovery.
I'm gonna be honest, you're in over your head and you're ignoring good advice which was given to prevent you from damaging your phone.
You really have two choices: either do a hell of a lot of reading until you have a firm understanding of what you're doing, or leave your phone alone. The way you're going right now you're on track to destroy your phone.
Do yourself a favour and click on the link in my signature. It's a resource thread, it contains all the information you'll ever need. I'll put it this way, I read for a week or two before I even started modifying my phones.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, If you put it that way then it makes more clear, stay away from your phone before you bricked it!
Will read about you've said before,however I have tried several ways to Super SU this phone and nothing works.
http://ausdroid.net/2012/05/21/how-to-root-the-htc-one-xl-generic-telstra/
Tried the one above, and no good.
Thanks for the help, will leave it as it is until I feel more confident about how to get this thing going.
Desertum said:
Fair enough, I need to read more about it.
As i Have atm S-ON and I need to have S-off to be able to install the RUU and the custom Rom, I either need to accomplish this :
SuperUser the Phone with the current Stock ROM
or
Install a Rooted ROM, correct?
Click to expand...
Click to collapse
We're getting there, here are the exact steps you need to take:
1) Read a lot.
2) Read some more.
3) Flash a superuser zip on your current stock ROM, or flash a rooted Sense ROM so you have root.
4) Get SuperCID.
5) Get s-off.
6) RUU to latest.
7) Flash whatever ROM you want.
Sent from my Evita
---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------
Desertum said:
Thank you, If you put it that way then it makes more clear, stay away from your phone before you bricked it!
Will read about you've said before,however I have tried several ways to Super SU this phone and nothing works.
http://ausdroid.net/2012/05/21/how-to-root-the-htc-one-xl-generic-telstra/
Tried the one above, and no good.
Thanks for the help, will leave it as it is until I feel more confident about how to get this thing going.
Click to expand...
Click to collapse
Just go to our Android Development section here and flash one of the new Sense 5 ROMs. They're already rooted.
Don't get information/software from anywhere except XDA by the way.
Sent from my Evita
He is already on 2.14 hboot I'm not even sure why he's trying to ruu.
Sent from my HTC One XL using xda app-developers app
31ken31 said:
He is already on 2.14 hboot I'm not even sure why he's trying to ruu.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Good catch. I missed that.
To the OP: you don't need to RUU to install cm10.2 on your device as you already have the required hboot/firmware. Without s-off you will need to manually flash the boot.img using fastboot though.
Sent from my Evita
Hi,
I want to know if in case I want to relock my bootloader, what's the RUU for? and how can I find one for my carrier? I'm with Fido (Canada), I'm s-on, hboot 2.15, rooted and running CarbonRom. I have the stock OS backup on my pc, and I was reading the steps to go back to stock with a locked bootloader.
Thanks
lucasmedaffy said:
I am on Fido and recently soft-bricked my phone.
I just went back to stock using the OTA ROGERS JB RUU (I found it online). It was a bit more complicated because the OTA zip doesn't have a RUU utility to flash it. There is a thread that will walk you through the steps; XDA's search is down or I would locate it. It took a bit of time but worked.
Click to expand...
Click to collapse
So you say the Rogers RUU will work? and I must use the ruu to lock the bootloader right?
Thanks!
elias.acab said:
So you say the Rogers RUU will work? and I must use the ruu to lock the bootloader right?
Thanks!
Click to expand...
Click to collapse
If you just want to relock the bootloader you can use fastboot
Code:
fastboot oem lock
But, this is probably not what you want to do, right?
RUU = ROM UPGRADE UTILITY. It's an .exe file that lets you install the stock rom on your phone. The RUU needs to match your hboot (and carrier). Get the RUU here:
http://www.androidruu.com/index.php?developer=Ville
Requirements:
- min 30% battery
- HTC drivers installed (devices is recognized by windows)
- USB debugging enabled
- Charging only mode
Hope this helps.
Thank you guys for that!! Theres something I still dont get, and its if I got the backup of the stock os (I dont really wanna relock the bootloader), I dont need the ruu right? But if I want to install the stock os and relock the bootloader (without using the backup) I do need the ruu, am I right?
Thanks
Sent from my One S
lucasmedaffy said:
I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2394165
and I used this RUU: http://www.androidfiles.org/ruu/get....27.50.08L_release_301897nn5lu23br8cg9q7l.zip
Unfortunately I couldn't use the older RUU because they were for ICS (IceCream Sandwich), not JB (JellyBean) and wouldn't install. As I mentioned, it is a few more hoops but the directions are very clear and it worked for me.
Good luck!
EDIT: If you just want to relock your bootloader, you can follow the above step (which is part of flashing the RUU and included in the instructions in the thread I linked to). If you want to reflash stock, follow the full instructions.
Click to expand...
Click to collapse
Thank you guys so much for that!! Theres something I still dont get, and its if I got the backup of the stock os (I dont really wanna relock the bootloader), I dont need the ruu right? But if I want to install the stock os and relock the bootloader (without using the backup) I do need the ruu, am I right? The Ruu installs the stock os for me?
Thanks, and sorry for asking too many questions
Sent from my One S
elias.acab said:
Hi,
I want to know if in case I want to relock my bootloader, what's the RUU for? and how can I find one for my carrier? I'm with Fido (Canada), I'm s-on, hboot 2.15, rooted and running CarbonRom. I have the stock OS backup on my pc, and I was reading the steps to go back to stock with a locked bootloader.
Thanks
Click to expand...
Click to collapse
Your Stock backup will work (you will also need to fastboot flash the boot.img if you are S-ON) to bring you back to your stock ROM.
RUU does that and a whole lot more that a simple backup can do.
Such as:
HBoot
Returns to stock recovery (which in turn will allow to correct partitions and fix unmountable sdcard)
Radio update
Boot.img
Splash screen
Or you could say it updates: Boot/System/Data/Recovery/Radio
---------- Post added at 05:05 PM ---------- Previous post was at 04:55 PM ----------
elias.acab said:
Thank you guys so much for that!! Theres something I still dont get, and its if I got the backup of the stock os (I dont really wanna relock the bootloader), I dont need the ruu right? But if I want to install the stock os and relock the bootloader (without using the backup) I do need the ruu, am I right? The Ruu installs the stock os for me?
Thanks, and sorry for asking too many questions
Sent from my One S
Click to expand...
Click to collapse
If you run your backup and then relock the bootloader, The bootloader will still say "tampered" I believe. This is because the modified recovery will still be there. You would need to unlock the bootloader and flash stock recovery to remove the "tampered" (i think)
So yeah, theoretically it will be just like running a RUU, if you restore your backup, fastboot flash boot.img, flash stock recovery. (assuming you haven't changed radio or hboot)
tivofool said:
Your Stock backup will work (you will also need to fastboot flash the boot.img if you are S-ON) to bring you back to your stock ROM.
RUU does that and a whole lot more that a simple backup can do.
Such as:
HBoot
Returns to stock recovery (which in turn will allow to correct partitions and fix unmountable sdcard)
Radio update
Boot.img
Splash screen
Or you could say it updates: Boot/System/Data/Recovery/Radio
---------- Post added at 05:05 PM ---------- Previous post was at 04:55 PM ----------
If you run your backup and then relock the bootloader, The bootloader will still say "tampered" I believe. This is because the modified recovery will still be there. You would need to unlock the bootloader and flash stock recovery to remove the "tampered" (i think)
So yeah, theoretically it will be just like running a RUU, if you restore your backup, fastboot flash boot.img, flash stock recovery. (assuming you haven't changed radio or hboot)
Click to expand...
Click to collapse
Thank you again, I really appreciate it!!, I totally get it now I'll make sure I re-read these steps when I feel like I wanna go back to stock.
I'm trying to update a phone I haven't used for a while with a newer ROM, but I'm not able to get in to recovery to do it. It's already rooted with an old ViperOne ROM on and I thought it already had CWM on., but Flashify is telling me it has the stock recovery. I've tried installing CWM and TWRP via Flashify and Fastboot and they've completed without any errors, but I'm never able to get in to it and it boots as normal. I can't even get in to the stock recovery that's supposedly there.
Does anyone have any idea what the problem might be?
Thanks.
Well try this.
Download Rom Manager
It wil flash the CWM by itself and then reboot into the Recovery. Notice what happens.
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
If Helped Click Thanks...
I've tried that too, still just reboots as normal.
Then it might be a Dead Recovery. Well which device are you using. And maybe Flashing your Device back to stock which would flash back the stock recovery.
Hope This Works ..!
---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------
Tell me wgich device are you using.
HTC One S S4 running Android 4.0.4 ICS
mrkwtrs said:
HTC One S S4 running Android 4.0.4 ICS
Click to expand...
Click to collapse
As first step you should flash the latest JellyBean RUU which will also upgrade your bootloader to 2.15. If your phone is "S-ON" you will have to relock the bootloader before running the RUU. Once done your phone should be fully working again so you can unlock the bootloader again and flash the latest TWRP recovery.
For getting the matching RUU you need to check your CID. Connect your phone in fastboot mode, open commandline and typ:
fastboot getvar all
LS.xD said:
As first step you should flash the latest JellyBean RUU which will also upgrade your bootloader to 2.15. If your phone is "S-ON" you will have to relock the bootloader before running the RUU. Once done your phone should be fully working again so you can unlock the bootloader again and flash the latest TWRP recovery.
For getting the matching RUU you need to check your CID. Connect your phone in fastboot mode, open commandline and typ:
fastboot getvar all
Click to expand...
Click to collapse
OK, Bootloader relocked, back to S-On, CID reset to O2___001.
Would you agree that the RUU is the 7th one down in this list?
mrkwtrs said:
OK, Bootloader relocked, back to S-On, CID reset to O2___001.
Would you agree that the RUU is the 7th one down in this list?
Click to expand...
Click to collapse
NO! You were S-OFF? That made life easier. Unbranded EU firmware is fine BUT I suppose you cant flash it now, as you reverted the CID...
I said, IF you're S-ON...
Best way is get S-OFF again via rumrunner.us, change CID to HTC__001 and then flash the RUU you mentioned before
LS.xD said:
NO! You were S-OFF? That made life easier. Unbranded EU firmware is fine BUT I suppose you cant flash it now, as you reverted the CID...
I said, IF you're S-ON...
Best way is get S-OFF again via rumrunner.us, change CID to HTC__001 and then flash the RUU you mentioned before
Click to expand...
Click to collapse
Just seen an O2 UK RUU further down the list so I'll try that.
mrkwtrs said:
Just seen an O2 UK RUU further down the list so I'll try that.
Click to expand...
Click to collapse
Ok, give it a try, you should go S-OFF anyway as you need HBOOT 2.15 if you want to use roms newer than ICS.
LS.xD said:
Ok, give it a try, you should go S-OFF anyway as you need HBOOT 2.15 if you want to use roms newer than ICS.
Click to expand...
Click to collapse
Think I'm all sorted. Thanks for your help! :good: