[Q] Return to stock, relock bootloader, etc. - AT&T, Rogers HTC One X, Telstra One XL

This phone might be sold, or given to someone who needs it completely stock, so my question is, how do i flash the stock recover/rom/kernel/etc, and relock the bootloader? Nothing has popped up under similar threads, and searches of the development section turned up nothing.
Gimme a hand

Relock bootloader with fastboot oem lock
Then run the ruu. Run 1.85 if you're on at&t

Keep in mind, it cannot be made completely stock. It will say RELOCKED on the bootloader screen, instead of LOCKED.

gunnyman said:
Relock bootloader with fastboot oem lock
Then run the ruu. Run 1.85 if you're on at&t
Click to expand...
Click to collapse
Does that replace Recovery mode app too (back to stock) ??

mrbillishere said:
Does that replace Recovery mode app too (back to stock) ??
Click to expand...
Click to collapse
yes.

gunnyman said:
Relock bootloader with fastboot oem lock
Then run the ruu. Run 1.85 if you're on at&t
Click to expand...
Click to collapse
Since my specialty has been Winmo, Samsung, and ASUS devices, I'm not too familiar with those. Is there a tutorial or thread available for this? Or for more info? I assume the RUU is installed from the stock recovery, right? Returning to stock on the devices I used, usually involved flashing the stock recovery, then wiping/doing a factory reset from the stock recovery.
Mad props for the concise instructions.

1) connect your phone to PC
2) Ensure your pc has android sdk and usb debugging is enabled on your device
3) open command prompt -- Navigate to folder having android-sdk/platform-tools
4) run command "fastboot oem lock" - This should lock your bootloader
5) Place 1.85 RUU on root directory of your storage ( rename it as PH98IMG.ZIP )
6) Reboot to bootloader and it should read the RUU file.

kancherlapraneeth said:
1) connect your phone to PC
2) Ensure your pc has android sdk and usb debugging is enabled on your device
3) open command prompt -- Navigate to folder having android-sdk/platform-tools
4) run command "fastboot oem lock" - This should lock your bootloader
5) Place 1.85 RUU on root directory of your storage ( rename it as PH98IMG.ZIP )
6) Reboot to bootloader and it should read the RUU file.
Click to expand...
Click to collapse
Awesome, it's just an ADB command. Can I use the 1.85 update? I think I've been updated since I first wrote this via the cleaning aroma installer. Do I need to use that RUu, the one I used when I unlocked it? Or can I use whatever is the latest.

kancherlapraneeth said:
1) connect your phone to PC
2) Ensure your pc has android sdk and usb debugging is enabled on your device
3) open command prompt -- Navigate to folder having android-sdk/platform-tools
4) run command "fastboot oem lock" - This should lock your bootloader
5) Place 1.85 RUU on root directory of your storage ( rename it as PH98IMG.ZIP )
6) Reboot to bootloader and it should read the RUU file.
Click to expand...
Click to collapse
So do i place the 1.85 ruu (exe file?) on the device (named ph98img.zip), reboot into the bootloader, and it will do the rest automatically? Or do i have to choose an option in the bootloader?

Jamesyboy said:
Awesome, it's just an ADB command. Can I use the 1.85 update? I think I've been updated since I first wrote this via the cleaning aroma installer. Do I need to use that RUu, the one I used when I unlocked it? Or can I use whatever is the latest.
Click to expand...
Click to collapse
i think the aroma installer from Cleanrom updated my ruu, so i assume i have to use the latest version. WIll try that.
If you have any info, please share.
=D

Jamesyboy said:
So do i place the 1.85 ruu (exe file?) on the device (named ph98img.zip), reboot into the bootloader, and it will do the rest automatically? Or do i have to choose an option in the bootloader?
Click to expand...
Click to collapse
i seem to be having issues with ADB-- it says "waiting for device".

Jamesyboy said:
So do i place the 1.85 ruu (exe file?) on the device (named ph98img.zip), reboot into the bootloader, and it will do the rest automatically? Or do i have to choose an option in the bootloader?
Click to expand...
Click to collapse
Jamesyboy said:
i think the aroma installer from Cleanrom updated my ruu, so i assume i have to use the latest version. WIll try that.
If you have any info, please share.
=D
Click to expand...
Click to collapse
I rebooted into the bootloader, and it's displaying "tampered, relocked"
So it seems, i've relocked the bootloader, i copied the 2.20 ruu over, and renamed it what i was supposed to, but the phone doesn't boot now. I've tried going to "recovery" from the bootloader menu, and i've tried "factory reset". Nothing's happening though.

How to hide or delete the red text on the second boot screen after unlock bootloader ?

One x has no ext. SD so that method isn't going to work without a powered y cable with card reader.....our Evita one x I'd not a ph9800 so its double not gonna work.......no Tom is going to give u official firmware update so Check hboot.....if ver. Is 1.14 use ruu 2.20....if ver 1.09 use ruu 1.85
Sent from my SCH-R720 using xda premium

pckeung said:
How to hide or delete the red text on the second boot screen after unlock bootloader ?
Click to expand...
Click to collapse
You can't

Jamesyboy said:
I rebooted into the bootloader, and it's displaying "tampered, relocked"
So it seems, i've relocked the bootloader, i copied the 2.20 ruu over, and renamed it what i was supposed to, but the phone doesn't boot now. I've tried going to "recovery" from the bootloader menu, and i've tried "factory reset". Nothing's happening though.
Click to expand...
Click to collapse
mine is doing the same thing

the renaming of the ruu is incorrect, you can rename the rom.zip inside maybe and have it work that way.
best to just boot into bootloader and run "fastboot oem lock" then run the ruu and follow the steps.

yungskeeme said:
mine is doing the same thing
Click to expand...
Click to collapse
This is an old thread from 3 months ago, the the original OP was confusing a lot of the terms and steps, so I would caution against doing anything he did, or chiming in on the thread and saying "my phone is doing the same". I'd suggest sticking to the other thread you started, and not confusing things more by posting here, too.

redpoint73 said:
This is an old thread from 3 months ago, the the original OP was confusing a lot of the terms and steps, so I would caution against doing anything he did, or chiming in on the thread and saying "my phone is doing the same". I'd suggest sticking to the other thread you started, and not confusing things more by posting here, too.
Click to expand...
Click to collapse
Cool. My bad. Just really despite to fix this so looking everywhere
Sent from my HTC One X using xda app-developers app

Related

Need help. One X on 1.88

I bought an att htc one x from someone else. The phone is rooted,and the bootloader in unlocked. it is running:
Nocturnal xi40 115
4.0.3 Android v
3.0.8-01158-g3d3f08d [email protected] #1
smp preempt (Kernel)
0.17a.32.09.24_2_10.91.32.19L (baseband)
1.88.707.2 cl64928 (build)
How do i get this phone back to stock? I want the phone to be on stock sense. I have searched but, i cant figure out how to revert back. Thank you for your help.
lakas187 said:
I bought an att htc one x from someone else. The phone is rooted,and the bootloader in unlocked. it is running:
Nocturnal xi40 115
4.0.3 Android v
3.0.8-01158-g3d3f08d [email protected] #1
smp preempt (Kernel)
0.17a.32.09.24_2_10.91.32.19L (baseband)
1.88.707.2 cl64928 (build)
How do i get this phone back to stock? I want the phone to be on stock sense. I have searched but, i cant figure out how to revert back. Thank you for your help.
Click to expand...
Click to collapse
1. Go to Settings -> Power and disable Fastboot.
2. Reboot the phone into the bootloader
3. Relock the bootloader by using the command "fastboot oem lock" from cmd (this is assuming you have the Android sdk on your computer, if you don't, go get it). I believe this causes your phone to reboot as well. If it does, just get back to the bootloader once it's done booting up again.
4. Enter Fastboot
5. Install HTC Sync on your PC (for drivers and such)
6. Connect your phone to your PC and let it install the drivers and what whatever Windows needs to do. You should see the text on your phone read FASTBOOT USB when it's done
7. Download the latest RUU from here: http://forum.xda-developers.com/showthread.php?t=1670238
8. Run the RUU (it's an exe, just run it like normal)
9. Follow the instructions and you'll be back to stock. The process takes like 10-15 minutes
Can I downgrade to 1.85?
lakas187 said:
Can I downgrade to 1.85?
Click to expand...
Click to collapse
You can if you have superCID, you can check by typing "fastboot getvar cid" and making sure it's 11111111 (uhhh...I think it's 8 digits, don't remember, it just has to be all 1's).
stnguyen09 said:
1. Go to Settings -> Power and disable Fastboot.
2. Reboot the phone into the bootloader
3. Relock the bootloader by using the command "fastboot oem lock" from cmd (this is assuming you have the Android sdk on your computer, if you don't, go get it). I believe this causes your phone to reboot as well. If it does, just get back to the bootloader once it's done booting up again.
4. Enter Fastboot
5. Install HTC Sync on your PC (for drivers and such)
6. Connect your phone to your PC and let it install the drivers and what whatever Windows needs to do. You should see the text on your phone read FASTBOOT USB when it's done
7. Download the latest RUU from here: http://forum.xda-developers.com/showthread.php?t=1670238
8. Run the RUU (it's an exe, just run it like normal)
9. Follow the instructions and you'll be back to stock. The process takes like 10-15 minutes
Click to expand...
Click to collapse
Is the process the same if you're on CleanROM 4.1 SE (1.85) or any other Custom ROM for that matter?
phishie said:
Is the process the same if you're on CleanROM 4.1 SE (1.85) or any other Custom ROM for that matter?
Click to expand...
Click to collapse
Yes, this are the instructions for returning to stock from any custom rom. Though, if you're on an AOSP based rom, you don't have to disable Fastboot in Settings -> Power (it's not there)
I don't have cid. Can I just flash it to the phone as is?
lakas187 said:
I don't have cid. Can I just flash it to the phone as is?
Click to expand...
Click to collapse
You mean you don't have superCID or you can't find your cid? Everyone phone has one (it's sort of an id number of sorts).
Go ahead and just run the RUU, it'll yell at you if you don't have superCID and try to downgrade. If it goes fine, then you're good.
I meant that i don't have supercid.
lakas187 said:
I meant that i don't have supercid.
Click to expand...
Click to collapse
Just curious, what is your CID then?
Here's the one-click for superCID http://forum.xda-developers.com/showthread.php?t=1672284
I'll try to run the 1.85 ruu. I just don't want to brick it.
lakas187 said:
I'll try to run the 1.85 ruu. I just don't want to brick it.
Click to expand...
Click to collapse
You won't brick it by running the RUU.
..d
I'll just follow the steps you posted above and see if i can fix it.
Thanks for your help! I was able to flash back to stock :good:

[GUIDE] Upgrade to ATT 2.20 OTA Safely

Ok this is a simple guide more for newer users as older members here already will know this information probably.
As people may have heard there is a new OTA for ATT. I and gunnyman bit the bullet to see if the old way of doing things ( upgrading, etc as long as you already had unlock token ) still worked with this new base and OTA.
Im proud to say yes. thanks to gunnyman and zounduser for help and hopes that I made it though un harmed lol
Disclaimer As usual this works as I am proof. However I cant be held liable if you mess up your phone! This only works for those who are already unlocked rooted etc.
Here are the steps to getting the update safely.
Prerequisites:
1. You must already be unlocked with supercid and have your Unlock_code.bin file still on your pc. ( there is a thread for this )
2. you must be rooted
3. You must have an understanding of adb and how it works (threads all over xda)
4. Have an RUU available I used 1.85
5. copy of custom recovery twrp 2.1.8.1 is what i used
6. copy of superuser in a zip available in attachments at bottom.
7. Disable HTC SYNC from running!
Here we go:
1. Reboot your phone into fastboot
2. Open a command promp and point to your adb directory. Type the following command: fastboot oem lock
This will lock your bootloader allowing you to RUU
3. Open the 1.85 RUU file.
4. Go through the RUU process.
5. Once you have finished RUUing boot the phone up if it isint booted already
6. Do a minimal setup just skip through the initial set up screens.
7. Check for att software update.
8. A box will appear saying a security update is available. enable your wifi and download it.
9. Allow the update to install
10. After the update finishes ( takes roughly 8-10 mins) some faster some longer. Boot the phone if it isin't booted ( should be ) disable fastboot under system settings power. Enable USB debugging under system developer options.
11. Attach your phone to your pc if it isint already.
12. Open a command promp and point to your adb directory.
type: adb reboot bootloader. If you get an error from adb type adb reboot-bootloader
13. Locate your unlocktoken Unlock_code.bin and place it in the same folder as your adb, fastboot, etc if its not already there from the last time you unlocked.
14. Flash your unlock token. Open a command prompt and type:
fastboot flash unlocktoken Unlock_code.bin
15. Once the token flashes before selecting yes to unlock, unplug your phone from pc. After you unplug it go ahead and select yes.
16. Once phone boots up do a minimal set up as before. Plug your phone back in to pc. Open command prompt and type: to verify unlock
adb reboot bootloader if you get an error from adb type adb reboot-bootloader
you should now see UNLOCKED at the top. If not repeat number 14 until it sticks can take a few tries.
17. If your screen says unlocked, flash your custom recovery. Locate your recovery flash it by typing in command promp: fastboot flash recovery recoveryname.img ( twrp2.1.8.1.img is mine replace with whatever yours is)
18. Once you have the recovery flashed reboot the phone.
19. Plug the phone in and select disk drive. Copy the superuser zip over to your sd card.
20. After that select charge only, open a command prompt and type:
adb reboot recovery
21. Once in recovery locate the superuser zip and flash it.
22. Reboot enjoy you should now be on OTA 2.20 Unlocked, Rooted, etc
O one thing I forgot Please hit thanks if this helped you!
Issues:
1. If you update you will get a newer hboot, you may not be able to use other older ruu's such as 1.85, etc. Recommend immediately making a backup once rooted, unlocked, etc.
2. Updating results in boot.IMG from custom roms not being flashed again. Have to flash the boot.IMG of custom Rom in fastboot as before.
3. Radio.img will not flash on new hboot either must be done in fastboot same as boot.img.
Wanna dd a radio img for me?
Sent from my HTC One X using xda app-developers app
First.. lol thanks man, nice guide!!! Site this will help our nooblets
Sent from my HTC One XL using xda app-developers app
Yeah, we want radio. Good guide too.
Sent from my HTC One X using xda premium
Thought gunnyman switched to the dark side and got a galaxy lol
Sent from my HTC One X using xda app-developers app
InflatedTitan said:
Thought gunnyman switched to the dark side and got a galaxy lol
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
He came Back!
if you have a higher hboot. u cant RUU with a lower hboot correct?
daddioj said:
if you have a higher hboot. u cant RUU with a lower hboot correct?
Click to expand...
Click to collapse
Hmm dunno that one. I was on 1.85 CleanROM 4.5 asia2.23 base when I went to new OTA. I thought as long as one had super cid RUU would work either way up or down software.
thanks for the tutorial.
john9 said:
thanks for the tutorial.
Click to expand...
Click to collapse
Welcome
eraste said:
Hmm dunno that one. I was on 1.85 CleanROM 4.5 asia2.23 base when I went to new OTA. I thought as long as one had super cid RUU would work either way up or down software.
Click to expand...
Click to collapse
well yea if you a custom rom. base dont matter b/c hboot does not get updated. i went to offical asia RUU and hboot got updated i am pretty sure u cant go backwards without s-off i could be wrong though
Any idea if root exploit works after update? People are saying it won't work on 1.85 now bc of update on server.
Sent from my HTC One X using xda app-developers app
drummaniac83 said:
Any idea if root exploit works after update? People are saying it won't work on 1.85 now bc of update on server.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
its right in the OP. as long as YOU HAVE the unlock code file from htc dev already you can update then unlock and root with the file posted. but if you didnt unlock already DO NOT UPDATE i dont think anyone knows yet
or are u talking about the original 1.85 exploit?
daddioj said:
or are u talking about the original 1.85 exploit?
Click to expand...
Click to collapse
Orignal exploit. I'm on 1.85 non root. Was going to root this weekend since CR 4.5 was final. DOH!
Sent from my HTC One X using xda app-developers app
drummaniac83 said:
Any idea if root exploit works after update? People are saying it won't work on 1.85 now bc of update on server.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I do not know that one as it was designed for 1.85 I would say no. People are working on root for the ota as we speak
eraste said:
I do not know that one as it was designed for 1.85 I would say no. People are working on root for the ota as we speak
Click to expand...
Click to collapse
Good to know. I got my One x last month from att with 1.85 loaded. I think I'm fine without the update. I'll stick to custom ROMs lol. And your awesome boot animations :thumbup:
Sent from my HTC One X
Updating now.
I prefer to run sense roms based on ATT, just seem to work a bit better imo.
Besides, with what i know of the 4.0.4 (clean rom) it is much smoother and all around much better than the 4.0.3 we got originally, may not need to run a custom rom to get the results i require (though i probably still will haha).
so if im unlocked, i can update and worry about rooting and unlocking tomorrow since i already have the unlock.bin file ?
Sent from my HTC One X using xda app-developers app
Psst; the command to rebooting to bootloader is 'adb reboot-bootloader'
...that hyphen is pretty important.
JSLEnterprises said:
Psst; the command to rebooting to bootloader is 'adb reboot-bootloader'
...that hyphen is pretty important.
Click to expand...
Click to collapse
hmm adb setup on my pc doesnt require that particular hyphen. I never have to use " either thought that was a little wierd. It works tho. I do need that hypen when doing kill-server start-server tho. Those are the only two commands that seem to not work without it for me.
thanks ill update lines.

Help Please I can't get any T-mobile U.S, RUUs to work ?

followed steps correctly usb debugging on..check, tried in fastboot....check, tried both t-mobile U.S. RUUs and even tried downloading each from different sources...check, restored stock recovery and relocked bootloader I also made sure htc drivers are properly installed. WTF I dont know whats going on im on stock rom just rooted, my hboot is 1.009, can anyone give me a hand? I have to return my phone for a warranty exchange the older ruu gives me the error 155(tried fasboot usb method) and the 1.84 ruu acts as if it's working hell it even reboots my phone and says rom update successfully installed in ruu prompt but when I boot into bootloader it still has tampered? also I can tell its not working properly because under the white HTC logo/w black screen the little green installation bar is not displayed.....sorry for the run on sentencing....just trying to remember everything. (video) http://youtu.be/Y8qIt-tYiwQ
can anyone provide a link for stock recovery.img; got one from modaco, but not sure if it's the correct one ? PLZNTHNX
kirkcody said:
followed steps correctly usb debugging on..check, tried in fastboot....check, tried both t-mobile U.S. RUUs and even tried downloading each from different sources...check, restored stock recovery and relocked bootloader I also made sure htc drivers are properly installed. WTF I dont know whats going on im on stock rom just rooted, my hboot is 1.009, can anyone give me a hand? I have to return my phone for a warranty exchange the older ruu gives me the error 155(tried fasboot usb method) and the 1.84 ruu acts as if it's working hell it even reboots my phone and says rom update successfully installed in ruu prompt but when I boot into bootloader it still has tampered? also I can tell its not working properly because under the white HTC logo/w black screen the little green installation bar is not displayed.....sorry for the run on sentencing....just trying to remember everything. (video) http://youtu.be/Y8qIt-tYiwQ
Click to expand...
Click to collapse
That's a tough one to nail down. Below is the stock recovery from the 1.84 t-mobile OTA. Maybe flash that and try the clear storage option.
Also, you might try doing the the Mainver Fix in the all in one tool kit. It's an option in the box in the lower right hand corner.
https://dl.dropbox.com/s/g4r0ryvjy6oce9k/recovery.img?dl=1
Thankyou my friend ill give it a go
unfortunately that didn't work either...i don't know why this wont work for me
kirkcody said:
unfortunately that didn't work either...i don't know why this wont work for me
Click to expand...
Click to collapse
This same thing happened to me at some point. I would suggest just starting over and redoing all the steps.
0. Flash original radio
1. Flash stock recovery
2. Use stock recovery "clear storage" option
3. Factory reset.
4. Enable usb debugging
5. Uninstall usb drivers from your computer
6. Reinstall HTC USB driver
7. Lock bootloader
8. Switch usb cable
9. Run RUU.
If that doesn't work use a hammer and smash the thing =)
Actually instead of using a hammer I would change to super cid and use a different RUU that had the same hboot as the one your on.
Extract the Rom.zip from the RUU, rename to PJ40IMG.zip, place on root of SD card.
Sent from my locked, tampered ville
@usaf22 really? Did that method work for you?(thought it may not work because we don't have s-off) Did it also remove the tampered and relocked banners? Thanks for both of you guys help will give it a go.
(Edit Hboot wont detect the PJ40IMG.zip )
usaff22 said:
Extract the Rom.zip from the RUU, rename to PJ40IMG.zip, place on root of SD card.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
No that won't work. Has it ever worked on the One S?
Didn't work Hboot didn't detect PJIMG.zip :crying:
kirkcody said:
Didn't work Hboot didn't detect PJIMG.zip :crying:
Click to expand...
Click to collapse
Did you try all this?
0. Flash original radio
1. Flash stock recovery
2. Use stock recovery "clear storage" option
3. Factory reset.
4. Enable usb debugging
5. Uninstall usb drivers from your computer
6. Reinstall HTC USB driver
7. Lock bootloader
8. Switch usb cable
9. Run RUU.
kirkcody said:
can anyone provide a link for stock recovery.img; got one from modaco, but not sure if it's the correct one ? PLZNTHNX
Click to expand...
Click to collapse
link no good-deleted
I have this exact same problem. The recovery cannot be flashed. I get a signature failed. I managed to download the the recovery just fine though. I need to flash the stock recovery so that I can do that latest update, but now I can't even enter the recovery. I get a security warning message next to Relocked everytime I try to get in... Awesome.
PS: The phone I already tried the RUU and I got a 155. Because you can only downgrade if you are S-OFF. So... What are we supposed to do now..?
Fixter said:
I have this exact same problem. The recovery cannot be flashed. I get a signature failed. I managed to download the the recovery just fine though. I need to flash the stock recovery so that I can do that latest update, but now I can't even enter the recovery. I get a security warning message next to Relocked everytime I try to get in... Awesome.
PS: The phone I already tried the RUU and I got a 155. Because you can only downgrade if you are S-OFF. So... What are we supposed to do now..?
Click to expand...
Click to collapse
I'm going to assume that by now you have taken off the phone everything you wanted to back up. You flashed the stock recovery onto the phone right? And now your bootloader is relocked?
If so do this:
enter fastboot
then select the bootloader option.
clear storage
factory reset
select fastboot again.
Run the RUU
dc211 said:
I'm going to assume that by now you have taken off the phone everything you wanted to back up. You flashed the stock recovery onto the phone right? And now your bootloader is relocked?
If so do this:
enter fastboot
then select the bootloader option.
clear storage
factory reset
select fastboot again.
Run the RUU
Click to expand...
Click to collapse
I got it working guys, but I know why. I was using the incorrect RUU. The link said it was the one for 1.83 but it was for the 1.5 version. I download it again and sure enough it's the 1.83 one. I guess I'm back to work now.
One question and this may save a big headache lol... did you LOCK your bootloader back? I had a couple RUU's that didn't work for me either, but I didn't follow the step of locking the bootloader I was just trying to flash over. Once I relocked I was good to go.
Thanks everyone yes I relocked the bootloader, hey @ dc211 can you provide a link for a successful RUU that you have used...plznthnx
kirkcody said:
Thanks everyone yes I relocked the bootloader, hey @ dc211 can you provide a link for a successful RUU that you have used...plznthnx
Click to expand...
Click to collapse
Your problem is that there is only 1 RUU you can use. Only 2 exist for T-mobile US and one you can't use because the hboot is lower then yours. But you're kinda lucky that a new OTA came out today. So a newer T-mobile US RUU should be out in a few days, that's normally how long it takes football to get them.
Here's a link to eh 1.83 RUU that should be fast. https://dl.dropbox.com/u/76257867/RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
Our you can try to get the OTA. You should be able to see it now if you check for software updates but it should fail to install. I saw you're using the 1.06es radio. You'd have to go back to the original radio, recovery, lock the booloader and factory reset. For it to work.
I know you should be able to get it working I was stuck where you're at but my Hboot also said "Security Warning" and RUU's & OTA's wouldn't run which I really haven't seen anyone else get.

[Q] How to root Desire S, S-OFF, hboot 2.00.0002, android 4.0.4

Hello people. Just one question. I searched on google and here on xda how to do it but still Im not sure how to do it. I have HTC Desire S, S-OFF with 2.00.002 hboot version and 4.0.4. android version. How do I permanetly root? The official 4.0.4 is kinda laggy, at least for me. I tried few methods but still nothing.. And, I found few methods like for 0.98 hboot or 2.3.5. android but my phone isnt that so Im not sure will it work. Thanks im advance
chorba69 said:
Hello people. Just one question. I searched on google and here on xda how to do it but still Im not sure how to do it. I have HTC Desire S, S-OFF with 2.00.002 hboot version and 4.0.4. android version. How do I permanetly root? The official 4.0.4 is kinda laggy, at least for me. I tried few methods but still nothing.. And, I found few methods like for 0.98 hboot or 2.3.5. android but my phone isnt that so Im not sure will it work. Thanks im advance
Click to expand...
Click to collapse
Is your bootloader unlocked? If so then flash a custom recovery and flash a custom ROM, they all tend to be pre-rooted.
Sent from my Desire S using xda app-developers app
You're already S-OFF so you don't need to worry about most steps in guides.
I assume you have a custom recovery? You can just flash one of the superuser/superSU zip packages. (Desire S uses ARM).
You may also need to flash busybox.
My good gentlemen,
he says the phone is s off already
If you want to ROOT your phone (my case: Desire S , Mfc date: 2011-July ). This is the procedures i learned from China Android forums, at least it works on Me.!!
Make Sure your Hboot is 2.00.0002
Prepare 2 files first: Superuser-3.0.7-efghi-signed.zip and su-bin-3.0.3.2-efghi-signed.zip
(you should find those on the internet)
First:
Recovery --> install Superuser-3.0.7-efghi-signed.zip from SDcard, and Reboot;
Second:
Recovery --> Install su-bin-3.0.3.2-efghi-signed.zip from SDcard Again and Reboot.
Usually, your phone should be Rooted.!!
Have Fun
Thanks for answers Well, the only thing I wanna do is flash a custom rom, and I dont know do I need rooted device for that? If I dont, what do I need? And, how can I check is my bootloader unlocked? And, where can I find a custom recovery? Can anyone link me please? Thanks ^^
I learned few things on my old Desire but this seems little complicated If isnt a probem, can anyone give me a step by step guide what I have to do to start flashing custom roms or something? I'd appreciate it. Thanks in advance
chorba69 said:
Thanks for answers Well, the only thing I wanna do is flash a custom rom, and I dont know do I need rooted device for that? If I dont, what do I need? And, how can I check is my bootloader unlocked? And, where can I find a custom recovery? Can anyone link me please? Thanks ^^
I learned few things on my old Desire but this seems little complicated If isnt a probem, can anyone give me a step by step guide what I have to do to start flashing custom roms or something? I'd appreciate it. Thanks in advance
Click to expand...
Click to collapse
Reboot to bootloader and check the first and second lines of text there...
first states < unlocked > if it was unlocked
second at the end: s-off.... or s- on
If your device realy was: s- off,
then your bootloader does not perform check of a signature,
so, in human language means: you may flash anything you want
custom recovery: clockworkmod or 4ext,
you may find in index thread for desire s...
here is the link
http://forum.xda-developers.com/showthread.php?t=1146601
there you can find tutorials about flashing, rooting etc, etc...all you`ll need
here is another link to the help thread, where you may ask questions if you
stumbled somewhere, along the way
http://forum.xda-developers.com/showthread.php?t=2143855
one more thing: when choosing roms, you should only flash roms for your device
htc desire s ( that`ll save you headaches )
Erm.. Just checked and it says bootloader is locked :/ It is S-OFF but locked. How can I unlock it? On HTCdev or? Thanks
chorba69 said:
Erm.. Just checked and it says bootloader is locked :/ It is S-OFF but locked. How can I unlock it? On HTCdev or? Thanks
Click to expand...
Click to collapse
I`ve never had stock s-off device ( always had to do it myself )
but if you phone was never rooted before and its security flag is set to s- off,
then i think its bootloader will never check manufacturer`s signature
Try this:
download from the market or from 4ext thread (index thread )
< 4ext recovery updater > and from within that application,
try to install recovery ( you`ll need it anyway )
if that`ll turn out to be succesful, then your phone is ready for the ride...
Go to the thread from the second link ( help thread )
and ask there whether device that is s- off, needs its bootloader to be unlocked
in order to be ready to flash custom roms...
To unlock bootloader you may try comand ( not sure if that would work for you )
fastboot oem unlock
issued to you phone through comand prompt ...
Prior to this action you should set up ADB on your pc,
and of course install the drivers for your device...
Says this what I attached. What now?
chorba69 said:
Says this what I attached. What now?
Click to expand...
Click to collapse
Ok then...
you have to flash recovery via fastboot
1. download and set up adb and drivers for you phone ( and install them )
2. download recovery ( clockworkmod or 4ext )
3.extract < recovery_xxxyyy.img > from the zip file- if you downloaded it zipped...
4.rename file to < recovery.img > and place it in the folder
where you`ve placed ADB
5.open command prompt and issue command:
cd c:\name of the folder with ADB [ enter ]
6. reboot your phone to bootloader and wire it to you pc
7. issue command:
fastboot devices
if your device has been recognised( list of devices attached xxxyyy05321...)
you`ll see your phone`s ID
8. issue command:
fastboot flash recovery recovery.img
9. reboot bootloader, and from its option choose recovery
10. from recovery you may flash < superuser.zip >
if you just want your current rom rooted
or via recovery you may flash custom rom...
Alright mate thanks a lot. Im gonna try that as soon as I come home. Just one thing more, any chance of bricking my device? While doing that.
chorba69 said:
Alright mate thanks a lot. Im gonna try that as soon as I come home. Just one thing more, any chance of bricking my device? While doing that.
Click to expand...
Click to collapse
To be honest, when fiddling with phone`s system, bootloader etc..
however small- there is always a chance that you may manage to brick it,
but i`ve been followiing the above mentioned procedures- and many others before me,
many times, and it was always working without a problem,
it was tested and shared, first by the great ones among us,
so one may call them safe to perform,
but you should always remember to be careful,
and better read or ask twice, before doing something you do not fully understand
Ok just to make sure Im doing everything alright.
First, nothing to do with bootloader? Unlock or something?
Next, I create new folder on my pc on C partiton (because of cmd prompt you've said?), download adb and phone drivers and place them in the folder. Then install the drivers. Afterwards, download recovery and place it in the folder with adb and phone drivers and rename to recovery.img. Next, I reboot phone in bootloader and flash recovery. Then I have to reboot in bootloader again, how to? Phone will turn off so I can reboot in bootloader or what? Then I go in recovery, flash superuser.zip for rooted phone and afterwards flash custom rom. Thats it?
chorba69 said:
Ok just to make sure Im doing everything alright.
First, nothing to do with bootloader? Unlock or something?
Next, I create new folder on my pc on C partiton (because of cmd prompt you've said?), download adb and phone drivers and place them in the folder. Then install the drivers. Afterwards, download recovery and place it in the folder with adb and phone drivers and rename to recovery.img. Next, I reboot phone in bootloader and flash recovery. Then I have to reboot in bootloader again, how to? Phone will turn off so I can reboot in bootloader or what? Then I go in recovery, flash superuser.zip for rooted phone and afterwards flash custom rom. Thats it?
Click to expand...
Click to collapse
In bootloader, there is an option to reboot it,
While in fastboot usb mode, bootloader is the first option,
go into it (power button )....
There you can also find < recovery > option....
@chorba69
Go here and find the zip download link (here), extract to same folder as fastboot/adb (and optionally md5 check).
Reboot your phone into Fastboot (reboot to bootloader and if there is an option "fastboot", choose it, else you're already there)
Connect by USB (see the "+files" in my signature if you need windows drivers so your computer understands it's an android phone)
Open a command prompt window (hold shift, right click in the folder, open command prompt..)
Code:
fastboot flash recovery recovery.img
Wait for flash, if you see a message like "waiting for device", your phone isn't connected, you're on the wrong screen on your phone or your computer doesn't have the drivers installed.
Reboot back into bootloader
vol up/down, power button to choose Recovery
You now have a custom recovery (and you're viewing it), now you just have to select your zip from sdcard to flash it (this time the zip is the superuser/whatever).
Backups save phone's lives!
I'm curious about the first line of your hboot (after locked/unlocked/relocked)? e.g. mine is "SAGA PVT ENG S-OFF", if yours says "SAGA PVT SHIP S-OFF" then you're "radio s-off" and can do things like change your phones CID (let it use any network). If it's ENG S-OFF and not pre owned, then you're very lucky indeed (and some people might want more info about/a copy of your hboot)!
Paulie, I attached the image as you can see. Says it's PVT SHIP S-OFF. Do I need to do something before flashing recovery and superuser/rom etc? Or it's not important? Whats the difference anyways between PVT and ENG? And thanks ^^
Mhm. Just tried to flash recovery but recieved this message (attached). Im on FASTBOOT USB screen on phone and in the right directory on pc. Do I need to set up adb or something? Or what do I have to do now?
PVT is expected there, SHIP seems to mean "this version is for general release" whereas "ENG" signifies that it is an ENGineering version.
chorba69 said:
Mhm. Just tried to flash recovery but recieved this message (attached). Im on FASTBOOT USB screen on phone and in the right directory on pc. Do I need to set up adb or something? Or what do I have to do now?
Click to expand...
Click to collapse
I'm surprised you got this error. S-OFF should've meant you had no problem. Instead, you can try using the PG88IMG.zip method. Place the file in the root directory of your phone's SD card, reboot to bootloader and it should detect it and ask you if you want to apply the update.
Remember to delete/rename/move this zip file after it's done, as you'll not be able to use your bootloader normally whilst it is detected.
If you still get another error message, let us know!
Please be careful with the file below.
P88IMG.zip MD5: 729f7b435eadf6321ffc36d1da6a0f83
recovery.img MD5: b81b154d1381c9a7f23be39b645be38b
paulie-uk said:
PVT is expected there, SHIP seems to mean "this version is for general release" whereas "ENG" signifies that it is an ENGineering version.
I'm surprised you got this error. S-OFF should've meant you had no problem. Instead, you can try using the PG88IMG.zip method. Place the file in the root directory of your phone's SD card, reboot to bootloader and it should detect it and ask you if you want to apply the update.
Remember to delete/rename/move this zip file after it's done, as you'll not be able to use your bootloader normally whilst it is detected.
If you still get another error message, let us know!
Please be careful with the file below.
P88IMG.zip MD5: 729f7b435eadf6321ffc36d1da6a0f83
recovery.img MD5: b81b154d1381c9a7f23be39b645be38b
Click to expand...
Click to collapse
Hmm. So after I put that file on SD card, I have to flash it or flash the recovery.img? Or just when I put it and enter bootloader it will automatically start flashing the recovery?

[Q] How do I copy the Jellybean firmware to AT&T ONE X phone's root or root?

I have viewed "Jelly Bean (Android 4.1) released for AT&T HTC One X … but how to install it on unlocked AT&T phone?"
How do I copy the Jellybean firmware to AT&T HTC One X phone's root or root?
I have downloaded the file and connected the phone to my computer and copied file to my sd card. I am using Astro file manager. Once I go to the recovery mode and select apply update from internal storage, it doesn't allow me to proceed further and my phone gets rebooted.
I think there is some problem in copying files to the internal storage and it is not reading from the sd card.
My phone is unlocked and unrooted.
Suggestions will be greatly appreciated.
fahad247 said:
I have viewed "Jelly Bean (Android 4.1) released for AT&T HTC One X … but how to install it on unlocked AT&T phone?"
How do I copy the Jellybean firmware to AT&T HTC One X phone's root or root?
I have downloaded the file and connected the phone to my computer and copied file to my sd card. I am using Astro file manager. Once I go to the recovery mode and select apply update from internal storage, it doesn't allow me to proceed further and my phone gets rebooted.
I think there is some problem in copying files to the internal storage and it is not reading from the sd card.
My phone is unlocked and unrooted.
Suggestions will be greatly appreciated.
Click to expand...
Click to collapse
I'm not sure what you're trying to do...
This is an OTA you downloaded? a Zip file?
You're bootloader is unlocked but not rooted?
This is an AT&T Phone? Did you Super CID?
Is it S-ON or S-OFF?
Are you using stock recovery to flash the zip file or CWM/TWRP?
fahad247 said:
I have viewed "Jelly Bean (Android 4.1) released for AT&T HTC One X … but how to install it on unlocked AT&T phone?"
How do I copy the Jellybean firmware to AT&T HTC One X phone's root or root?
I have downloaded the file and connected the phone to my computer and copied file to my sd card. I am using Astro file manager. Once I go to the recovery mode and select apply update from internal storage, it doesn't allow me to proceed further and my phone gets rebooted.
I think there is some problem in copying files to the internal storage and it is not reading from the sd card.
My phone is unlocked and unrooted.
Suggestions will be greatly appreciated.
Click to expand...
Click to collapse
If you are S-Off you can download the 2.20 Ruu from the relevant thread, then take the OTA. After that push TWRP and install rooted ROM of your choice.
exad said:
I'm not sure what you're trying to do...
This is an OTA you downloaded? a Zip file?
You're bootloader is unlocked but not rooted?
This is an AT&T Phone? Did you Super CID?
Is it S-ON or S-OFF?
Are you using stock recovery to flash the zip file or CWM/TWRP?
Click to expand...
Click to collapse
Yes, this is an OTA zip file : OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k
My phone is unrooted however i am unsure about boot loader.
Yes, it's an AT&T phone and I am not sure about super CID
S-ON or S-OFF, no idea
Yes, I am using the stock recovery.
All I am trying to do is to follow this tutorial: http : // android. stackexchange. com/ questions/ 41176/ jelly-bean-android-4-1-released-for-att-htc-one-x-but-how-to-install-it
But once I select apply update from internal storage, my phone gets restarted.
Could be a bad Download. Assuming that phones never been rooted, it should work.
I think the option to install is called install from phone storage though and not internal storage.
In your bootloader it will show if it's locked unlocked or relocked and it will show if it's s-on or s-off. Assuming you never rooted it and you bought it brand new, it should be fine but if you bought it used or it was rooted at some point you could be setting yourself up for a brick.
Sent from my HTC One X using xda app-developers app
exad said:
Could be a bad Download. Assuming that phones never been rooted, it should work.
I think the option to install is called install from phone storage though and not internal storage.
In your bootloader it will show if it's locked unlocked or relocked and it will show if it's s-on or s-off. Assuming you never rooted it and you bought it brand new, it should be fine but if you bought it used or it was rooted at some point you could be setting yourself up for a brick.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
how to check whether the boot loader is locked or unlocked? I bought it used and can I check it was rooted before? Can I unroot it?
fahad247 said:
how to check whether the boot loader is locked or unlocked? I bought it used and can I check it was rooted before? Can I unroot it?
Click to expand...
Click to collapse
in the bootloader!
you know where you boot to before selecting recovery to go into recovery? thats your bootloader. it will give you all that info at the top of the screen.
to check the cid though youll need fastboot. check to see if its locked relocked or unlocked and if its s-on or s-off first, that should give us a clue.
exad said:
in the bootloader!
you know where you boot to before selecting recovery to go into recovery? thats your bootloader. it will give you all that info at the top of the screen.
to check the cid though youll need fastboot. check to see if its locked relocked or unlocked and if its s-on or s-off first, that should give us a clue.
Click to expand...
Click to collapse
It's locked. Now do I have to unlock it first?
fahad247 said:
It's locked. Now do I have to unlock it first?
Click to expand...
Click to collapse
no. locked is better.
youll want to check if its supercid though just in case.
download fastboot if you dont have it already,
boot to bootloader, select fastboot. plug in your phone. fastboot should change to fastboot usb
open a cmd prompt in the folder fastboot is in by shift right clicking within the folder window and selecting "open command promt here".
then type fastboot oem readcid. then paste in here what it says.
exad said:
no. locked is better.
youll want to check if its supercid though just in case.
download fastboot if you dont have it already,
boot to bootloader, select fastboot. plug in your phone. fastboot should change to fastboot usb
open a cmd prompt in the folder fastboot is in by shift right clicking within the folder window and selecting "open command promt here".
then type fastboot oem readcid. then paste in here what it says.
Click to expand...
Click to collapse
How do I download fastboot?
fahad247 said:
How do I download fastboot?
Click to expand...
Click to collapse
Can you help me in updating my phone to official jelly beans as I am not getting OTA updates.
fahad247 said:
Can you help me in updating my phone to official jelly beans as I am not getting OTA updates.
Click to expand...
Click to collapse
Here's a link for adb and Fastboot https://dl.dropboxusercontent.com/u/19685555/fb-adb.zip
If you don't have htc sync installed. Install it as it will have the necessary drivers: http://www.htc.com/www/software/htc-sync-manager/

Categories

Resources