[Q] How do I copy the Jellybean firmware to AT&T ONE X phone's root or root? - AT&T, Rogers HTC One X, Telstra One XL

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/

Related

[Q] how to root desire s 2.3.5

i am having trouble rooting my htc desire s hboot 2.00.002 S-ON android version 2.3.5. can anyone help??
iGeoo said:
i am having trouble rooting my htc desire s hboot 2.00.002 S-ON android version 2.3.5. can anyone help??
Click to expand...
Click to collapse
.............why???? Everytime again..
What kind of trouble do you have after doing what to your phone??
I would like to see a doctor curing people ota after they send an email "help me I'm sick"
Sent my thoughts to your head with XDA App
Hi there! this worked for me
http://forum.xda-developers.com/showthread.php?t=1390496
another method
first unlock bootloader through htcdev.com it isn't a big deal
make sure you have installed android sdk
download recovery-clockwork-5.0.2.0-saga.img and Superuser-3.0.7-efghi-signed.zip I've attached it
(rename recovery-clockwork-5.0.2.0-saga.img to recovery.img)so you can flash it easily
than download android fastboot tools I've attached it
extract the fastboot-tools.zip to lets say C:\android
check out the 11.jpg
now turn on your phone into bootloader to do that push volume button down and power button than go into fastboot and plug your phone into usb
than run command and go to folder that you created lest say cd c:\android
than type "fastboot flash recovery recovery.img"
done you've installed clockworkmod recovery
Now it's time to root your phone.
put Superuser-3.0.7-efghi-signed.zip to sdcard root folder means just move it sdcard no subfolder
start your phone into cwm recovery to do that turn of your phone and again press volume down and power button
than scroll to recovery via volume up and down button than push power button when recovery highlight
and cwm will start up than select install zip from sdcard go to the Superuser-3.0.7-efghi-signed.zip and select yes
phone is rooted
HOPE THIS HELP
niravnn said:
first unlock bootloader through htcdev.com it isn't a big deal
make sure you have installed android sdk
download recovery-clockwork-5.0.2.0-saga.img and Superuser-3.0.7-efghi-signed.zip I've attached it
(rename recovery-clockwork-5.0.2.0-saga.img to recovery.img)so you can flash it easily
than download android fastboot tools I've attached it
extract the fastboot-tools.zip to lets say C:\android
check out the 11.jpg
now turn on your phone into bootloader to do that push volume button down and power button than go into fastboot and plug your phone into usb
than run command and go to folder that you created lest say cd c:\android
than type "fastboot flash recovery recovery.img"
done you've installed clockworkmod recovery
Now it's time to root your phone.
put Superuser-3.0.7-efghi-signed.zip to sdcard root folder means just move it sdcard no subfolder
start your phone into cwm recovery to do that turn of your phone and again press volume down and power button
than scroll to recovery via volume up and down button than push power button when recovery highlight
and cwm will start up than select install zip from sdcard go to the Superuser-3.0.7-efghi-signed.zip and select yes
phone is rooted
HOPE THIS HELP
Click to expand...
Click to collapse
Wow, quite a big solution, maybe you covered his problem. but I would never recommend to someone to use htcdev.
Sent my thoughts to your head with XDA App
Thanks for the helpful comment, i will try and report back
Thanks this resolved my problem.!
Sent from my Nexus S using XDA App
Can I now install custom rom? It still says S-On but is now unlocked. Thanks
Sent from my Nexus S using XDA App
darius0519 said:
Can I now install custom rom? It still says S-On but is now unlocked. Thanks
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If you unlocked with htcdev you can flash custom roms and you need to flash the boot.img separately
Sent by my fingers to your head
@darius0519
Its bee said soooooo many times, I am shocked someone wouldn't find it.
Flash a custom recovery.... Using fastboot then follow what eyahl said.
eyahl said:
If you unlocked with htcdev you can flash custom roms and you need to flash the boot.img separately
Sent by my fingers to your head
Click to expand...
Click to collapse
Thanks men! You're a genius!
Sent from my Nexus S using XDA App
iGeoo said:
i am having trouble rooting my htc desire s hboot 2.00.002 S-ON android version 2.3.5. can anyone help??
Click to expand...
Click to collapse
You can't root the phone unless you've S-OFF'd it... trouble is with v2.00.002 Hboot, then Revoutionary won't work (requires 0.98.0000 or 0.98.0002).
You can try: http://forum.xda-developers.com/showthread.php?t=1390496
anchemis said:
You can't root the phone unless you've S-OFF'd it... trouble is with v2.00.002 Hboot, then Revoutionary won't work (requires 0.98.0000 or 0.98.0002).
You can try: http://forum.xda-developers.com/showthread.php?t=1390496
Click to expand...
Click to collapse
I have rooted my phone by unlocking the bootloader from htcdev. Then flashing cwm from fast boot. Once cwm image is flashed i booted to recovery and installed superuser to root my friends phone. It is still on s-on state but says unlocked. And now its rooted.
Sent from my Nexus S using XDA App
darius0519 said:
I have rooted my phone by unlocking the bootloader from htcdev. Then flashing cwm from fast boot. Once cwm image is flashed i booted to recovery and installed superuser to root my friends phone. It is still on s-on state but says unlocked. And now its rooted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Interesting! Try using 4EXT recovery? I find it better than CWM. Ext4 file systems, mount USB in recovery mode, etc.
darius0519 said:
I have rooted my phone by unlocking the bootloader from htcdev. Then flashing cwm from fast boot. Once cwm image is flashed i booted to recovery and installed superuser to root my friends phone. It is still on s-on state but says unlocked. And now its rooted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
In my opinion it is in any way better to s-off and not unlock with htcdev. anything you do will be much more easier when s-off (for example flashing ROM, no need to flash boot.img separately...) And also there's a bigger chance of voiding your warranty when using htcdev.
Sent by my fingers to your head
eyahl said:
In my opinion it is in any way better to s-off and not unlock with htcdev. anything you do will be much more easier when s-off (for example flashing ROM, no need to flash boot.img separately...) And also there's a bigger chance of voiding your warranty when using htcdev.
Sent by my fingers to your head
Click to expand...
Click to collapse
i thinks your right men. but i just don't have the guts to try to downgrade the hboot loader since i am only doing it for a friend. im afraid i may brick his phone.

[Q] Return to stock, relock bootloader, etc.

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

Help with HTC Desire S (bricked)

OK, need a bit of help with a Desire S that can only get to HBOOT screen (vol down + power) otherwise it's just a white HTC screen.
Phone is S-ON. HBOOT 0.98.002.
I've tried Revolutionary.io's guide to convert to S-OFF but I just get 'Waiting for Device'. Tried uninstalling HTC drivers then installing again without luck, disabling firewall and AV, still no luck. Kinda given up on that front.
Trying 'fastboot devices', device is recognised, but if I try to flash a recovery ROM from fastboot I get an 'out of memory' error.
I don't know if USB debugging is enabled or not (how can I tell & enable from HBOOT if not)?
I thought about going via HTCDEV and their method, but my HBOOT is at the wrong version (can I upgrade it to V 2.000.2?)
I'm really running out of options now....anything else I can try??? HELPPPP!
Run htc ruu exe file and don't close the windows, find rom.zip in windows temp folder, rename it to PG88IMG.zip ale copy to sdcard. Turn on your phone in hboot mode, rom will be flashed automaticaly.
Or just go to fastboot mode in hboot and then run RUU, should work if you have bootloader locker (relocked).
amdr said:
Run htc ruu exe file and don't close the windows, find rom.zip in windows temp folder, rename it to PG88IMG.zip ale copy to sdcard. Turn on your phone in hboot mode, rom will be flashed automaticaly.
Or just go to fastboot mode in hboot and then run RUU, should work if you have bootloader locker (relocked).
Click to expand...
Click to collapse
Thanks. Noobish of me, but where do I download the relevant RUU file from? I don't know what carrier the phone is locked to by the way.
Download original ics rom here : http://dl4.htc.com/RomCode/Source_a...401.2_20.76.30.0835_3831.19.00.110_275068.zip
it has hboot 2!!!:fingers-crossed:
uberduder101 said:
Thanks. Noobish of me, but where do I download the relevant RUU file from? I don't know what carrier the phone is locked to by the way.
Click to expand...
Click to collapse
dave3002 said:
Download original ics rom here : .htc.com/RomCode/Source_and_Binaries/RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068.zip
it has hboot 2!!!:fingers-crossed:
Click to expand...
Click to collapse
I couldn't open that, but thanks.
sorry, but I'm really not getting this. I'm looking for a RUU to flash a recovery ROM. When I went to HTC dev, there were all the ROMs for all the different carriers. I don't know what mine is. I tried downloading one for Vodafone, unzipped and searched for RUU.exe but there isn't one.
I need to get to this RUU.exe but dont know how.:crying:
what is a recovery ROM? anyway, people over here at the DS forum has already extracted the radio, Hboot and ROM of official ICS. search around...
Sent from my supercharged :tank:
I had a bit of progress. I downloaded the latest 4.0 RUU util from HTC Dev, ran it, extracted the ROM.zip and renamed it to PG88IMG.zip, copied it up to the SD card, rebooted the phone into FASTBOOT and the phone recognised it and started installing.
Wahey, I thought, that's it I've cracked it, but then it gets stuck on Updating the bootloader. Stuck for nearly an hour. Tried twice and different SD cards...same thing.
Is this because I'm still S-ON and bootloader is locked, or do you think my internal memory is fried?
uberduder101 said:
I had a bit of progress. I downloaded the latest 4.0 RUU util from HTC Dev, ran it, extracted the ROM.zip and renamed it to PG88IMG.zip, copied it up to the SD card, rebooted the phone into FASTBOOT and the phone recognised it and started installing.
Wahey, I thought, that's it I've cracked it, but then it gets stuck on Updating the bootloader. Stuck for nearly an hour. Tried twice and different SD cards...same thing.
Is this because I'm still S-ON and bootloader is locked, or do you think my internal memory is fried?
Click to expand...
Click to collapse
you can't flash that when you are s-on
Sent from my supercharged :tank:
uberduder101 said:
..., or do you think my internal memory is fried?
Click to expand...
Click to collapse
You're right, that's the case. Search and you'll see similar cases.
hisname said:
you can't flash that when you are s-on
Click to expand...
Click to collapse
Absolutely irrelevant. He's not flashing anything himself, he's executing RUU which can flash everything.
OK, so how do I enable USB debugging if I can only get into HBOOT? Is there a FASTboot or ADB command that can do it? I think that's what's stopping Revolutionary.
Jack_R1 said:
Absolutely irrelevant. He's not flashing anything himself, he's executing RUU which can flash everything.
Click to expand...
Click to collapse
if you read again, he said he was flashing the rom zip after extracting the rom from the RUU
Sent from my supercharged :tank:
hisname said:
if you read again, he said he was flashing the rom zip after extracting the rom from the RUU
Sent from my supercharged :tank:
Click to expand...
Click to collapse
And the difference is?
Sent from my HTC Desire S
FYI - I tried executing the RUU itself, and that just hangs too.
I'm going down the line of toasted internal memory and am now throwing in the towel. Besides I just can't spend any more time on it.
Thanks for all your help.
amidabuddha said:
And the difference is?
Sent from my HTC Desire S
Click to expand...
Click to collapse
difference is he isn't flashing the RUU, just the ROM
Sent from my supercharged :tank:
hisname said:
difference is he isn't flashing the RUU, just the ROM
Sent from my supercharged :tank:
Click to expand...
Click to collapse
And what means to flash a RUU? Do you see any RUU running on your phone?
Trying to help people is a good thing but not before trying the stuff yourself, knowing the differences, how it works and WHY it should be done
amdr said:
Run htc ruu exe file and don't close the windows, find rom.zip in windows temp folder, rename it to PG88IMG.zip ale copy to sdcard. Turn on your phone in hboot mode, rom will be flashed automaticaly.
Or just go to fastboot mode in hboot and then run RUU, should work if you have bootloader locker (relocked).
Click to expand...
Click to collapse
Same problem with this post!
When i followed your step, this has many time to wait. I'm waiting 45 minute but this just show:
Can you help me?
Do you have recovery?Can you get in? If you can fastboot then flash recovery and try to get in.Once in try to open info or just try to wipe all (no SD card) then you will see bricked or not.
SKENER said:
Do you have recovery?Can you get in? If you can fastboot then flash recovery and try to get in.Once in try to open info or just try to wipe all (no SD card) then you will see bricked or not.
Click to expand...
Click to collapse
i don't have recovery, when i press power, my device just show HTC with white screen
When I press power + volume down, then come to recovery, it's not show

[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] help rooting htc one xl cid -622

hi
i have a cid of htc-622 which is asia -hong kong
software number is 3.17.708.5
evita pvt ship s-on rl
hboot-2.14.0000
radio-0.23a.32.09.29
open dsp-v31.1.0.45.0815
can i follow this guide?
http://forums.team-nocturnal.com/showthread.php/1147
No. Just unlock your boot loader with htcdev.com and flash twrp 2.3.3.1
Sent from my One X using xda app-developers app
exad said:
No. Just unlock your boot loader with htcdev.com and flash twrp 2.3.3.1
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
thanks for the quick response
in this thread
http://forum.xda-developers.com/showthread.php?t=1677447
it says i have to be rooted to install the recovery?
is there an easy way to root?
emu123 said:
thanks for the quick response
in this thread
http://forum.xda-developers.com/showthread.php?t=1677447
it says i have to be rooted to install the recovery?
is there an easy way to root?
Click to expand...
Click to collapse
You need an unlocked bootloader to install recovery, not root.
As per AT&T, HTC blocks bootloader unlocks for AT&T customers. To do this, HTCDEV.com blocks any requests for bootloader unlocks which have an AT&T CID.
Because of this, for AT&T customers only, one must change their CID in order to trick HTCDEV.com into allowing a bootloader unlock.
To gain write access to the file that needs changing to spoof the CID, you need root access.
So what this means:
To flash recovery, you need bootloader unlocked, not root.
But because AT&T OneXLs needs to spoof the CID before unlocking the bootloader, they require root.
For AT&T > Root > SuperCID > Unlock bootloader > Flash twrp
For everyone else Skip right to > Unlock bootloader > Flash twrp
Because you do not have an AT&T phone, you will have no problems unlocking the bootloader to flash a custom recovery.
At first, things can be confusing because many posts don't really make a point of saying that those steps are only needed if you are with AT&T but when you read more than just one post, and make a point of trying to understand what you're doing, things become clearer.
right managed to get the bootloader unlocked and i am rooted
i have installed team win recovery v2.5.0.0
when i go to try and do a backup of my current rom i get e:not enough free space on storage
just found out i only have 1gb free of space on my memory so it was not enough to backup
last question
with mine being the international version can i choose any rom?
emu123 said:
last question
with mine being the international version can i choose any rom?[/QUO
Any evita rom
Sent from my HTC One XL running super smooth Sense 5
Click to expand...
Click to collapse
emu123 said:
last question
with mine being the international version can i choose any rom?
Click to expand...
Click to collapse
Considering your version (EVITA) the "international version" will get you into trouble. Most people consider the quad core Tegra3 variant ENDEAVOURU the "international" version. Yes, this is confusing, and dates back to the time when the ENDEAVORU was available in multiple countries across Europe and other regions, and the EVITA was only available in North America. Of course, the EVITA is available in many countries now, so the term "international" is basically meaningless. Stick to ROMs for the dual core Snapdragon S4 version of the One X/XL, and you will be okay.
Better yet, just use my Index thread. Any of the ROMs linked here are fine for the EVITA: http://forum.xda-developers.com/showthread.php?t=1671237
thought i would give cm10 a go
flashed the zip then extracted the boot img and flashed it and now touchscreen doesnt work
tried to get back into recovery and now it looks like my internal sd card is messed up
managed to reflash recovery and now the touchscreen works again
but having trouble getting the internal memory to show up and restore my backup
emu123 said:
thought i would give cm10 a go
flashed the zip then extracted the boot img and flashed it and now touchscreen doesnt work
Click to expand...
Click to collapse
If your phone was shipped with Jellybean, or your RUU or OTA'ed to it, the touchpad firmware was upgraded, and will not work with any AOSP ROMs.
You can downgrade the touchpad firmware, but you need to be S-off: http://forum.xda-developers.com/showthread.php?t=2159863
emu123 said:
tried to get back into recovery and now it looks like my internal sd card is messed up
managed to reflash recovery and now the touchscreen works again
but having trouble getting the internal memory to show up and restore my backup
Click to expand...
Click to collapse
If you tried to do a factory reset in bootloader, you corrupted the SD card (known bug, don't ever do it, always factory reset in recovery).
See Question 15 here: http://forum.xda-developers.com/showthread.php?t=2136172
There are also other fixes for this, if you search around this forum.
thanks
managed to get the card back , but think i will have to sideload a rom as i cant connect it to my computer and copy across my twrp backup
bit messy this flashing business lol
for some reason cleanrom wont install it was stuck on the boot logo for about 30 mins
i did try and flash the boot.img from the rom as well with the same results
viper one xl seemed to work fine
if i manage to get my twerp back up back onto my sd card and flash it back
when an update comes out does it wipe the custom recovery and root?
really struggling to find a proper ruu for my phone and the only one i could find as a .zip file

Categories

Resources