I would like to put my phone back to stock, I currently have Cyanogenmod on there, rooted, unlocked bootloader and a custom recovery. I am wanting to sell my phone so I need to know how to put it back to stock. Any help is appreciated
I am s-on
unlocked bootloader
HBOOT 2.00.0002
4ext recovery
deadphone99 said:
I would like to put my phone back to stock, I currently have Cyanogenmod on there, rooted, unlocked bootloader and a custom recovery. I am wanting to sell my phone so I need to know how to put it back to stock. Any help is appreciated
I am s-on
unlocked bootloader
HBOOT 2.00.0002
4ext recovery
Click to expand...
Click to collapse
Basically, just follow a 2.00.002 to 0.98.00000 downgrade guide involving using htcdev, such as this one, starting from the step where you push misc_version onto the device (you're already rooted and unlocked).
Obviously, if you don't want to S-OFF, you don't have to run Revolutionary.
You will need to use a RUU, you will need to re-lock your bootloader immediately before the RUU step. If you're not sure about how to choose a RUU, please see the relevant section of my guide in my signature.
If you want to sell the device as a 2.00.002 (you meanie! xD) then you can apply a newer RUU than for 0.98.0000, just don't put on ICS D:
paulie-uk said:
Basically, just follow a 2.00.002 to 0.98.00000 downgrade guide involving using htcdev, such as this one, starting from the step where you push misc_version onto the device (you're already rooted and unlocked).
Obviously, if you don't want to S-OFF, you don't have to run Revolutionary.
You will need to use a RUU, you will need to re-lock your bootloader immediately before the RUU step. If you're not sure about how to choose a RUU, please see the relevant section of my guide in my signature.
If you want to sell the device as a 2.00.002 (you meanie! xD) then you can apply a newer RUU than for 0.98.0000, just don't put on ICS D:
Click to expand...
Click to collapse
I get permission denied when trying to change the misc_version number, any ideas?
EDIT: I just sorted it
deadphone99 said:
I get permission denied when trying to change the misc_version number, any ideas?
Click to expand...
Click to collapse
You need to run misc_version as root, use su to gain root in your terminal for when you issue the command. You may need to interact with a permission request on the phone screen.
If you have an old adb on your computer and your rom is android 4.x, you might need to get a newer adb for it to work properly (some security stuff was changed).
Related
Hi I have just got a Desire S and its on H Boot 2.00.0002
Now I have looked at this guide- {GUIDE} Root Desire S hboot 2.00.0002 android 2.3.5 the easy way
and i am still un clear as to whether this will S-off the Desire S or is there a better way?
Any pointers for me would be good thanks
Nexus04
Nexus04 said:
Hi I have just got a Desire S and its on H Boot 2.00.0002
Now I have looked at this guide- {GUIDE} Root Desire S hboot 2.00.0002 android 2.3.5 the easy way
and i am still un clear as to whether this will S-off the Desire S or is there a better way?
Any pointers for me would be good thanks
Nexus04
Click to expand...
Click to collapse
You need S-OFF if you want to change the hboot/bootloader or the radio. SInce you have the latest versions of both it is not necessary at this moment. In you need to S-OFF by any reason it is possible via downgrading to older version that is supported by Revolutionary.
If you unlock the bootloader with HTCDev.com you will remain S-ON but will have the ability to flash custom Recovery, Kernel or ROMs and rooting as well. So basically you have the freedom to change your system according to your preferences
Hi thanks for the reply,
so it`s not neccessary to S-off to be able to root the phone? I will do some more reading before I take the plunge as I do not want to brick my new phone
Cheers Nexus04
Nexus04 said:
...
so it`s not neccessary to S-off to be able to root the phone? ...
Click to expand...
Click to collapse
Exactly.
Basically you will need to unlock your hboot at htcdev.com, then flash a custom recovery then
1) flash Superuser to have root or
2) flash a custom ROM, they are all prerooted
amidabuddha said:
Exactly.
Basically you will need to unlock your hboot at htcdev.com, then flash a custom recovery then
1) flash Superuser to have root or
2) flash a custom ROM, they are all prerooted
Click to expand...
Click to collapse
What about relocking hboot?
Thanks for your input into this thread by the way, I was led to believe according to the guide section that you must be s-off (therefore downgrade from 2.00.0002) in order to flash custom roms.
dontjudgemekk said:
What about relocking hboot?
Thanks for your input into this thread by the way, I was led to believe according to the guide section that you must be s-off (therefore downgrade from 2.00.0002) in order to flash custom roms.
Click to expand...
Click to collapse
AFAK re-locking the bootloader is necessary only when you want to run a RUU (to restore the Stock configuration if needed)
amidabuddha said:
AFAK re-locking the bootloader is necessary only when you want to run a RUU (to restore the Stock configuration if needed)
Click to expand...
Click to collapse
Just in case I was to send my device for a warranty fix or such!
Unlocking the bootloader at htcdev will void your warranty.
I am patiently waiting for May 2012 for my warranty to be over and then I will unlock my boot loader..
As said the htcdev unlock void your warranty, it will send the info of your phone to HTC.
You can do the HBOOT downgrade http://forum.xda-developers.com/showthread.php?t=1399331 and use Revolutionary to get S-OFF and if you need the warranty you can use eng hboot and flash a new RUU to get back to stock and S-ON.
amidabuddha said:
You need S-OFF if you want to change the hboot/bootloader or the radio. SInce you have the latest versions of both it is not necessary at this moment. In you need to S-OFF by any reason it is possible via downgrading to older version that is supported by Revolutionary.
If you unlock the bootloader with HTCDev.com you will remain S-ON but will have the ability to flash custom Recovery, Kernel or ROMs and rooting as well. So basically you have the freedom to change your system according to your preferences
Click to expand...
Click to collapse
please will someone guide me how to flash custom recovery.
i have s-on, bootloader unlock htcdev and boot h2.00.0002.
i'm new to to desire s , previous hd2 owner,
thank you.
riaan0010 said:
please will someone guide me how to flash custom recovery.
i have s-on, bootloader unlock htcdev and boot h2.00.0002.
i'm new to to desire s , previous hd2 owner,
thank you.
Click to expand...
Click to collapse
Check the sticky posts on DesireS forums, you will find all you need
Swyped from my Desire S
Let the ads those who succeeded in HBoot Revolucionary 6.98.1002 S-OFF to get back to Hboot 2.00.0002 S-ON.
Some write to read this post and this post, last but nothing concrete.
Thank you.
As the title says, I am having a lot of trouble rooting this phone.
I got this phone as a warranty replacement for my old phone that was rooted following the CM guide.
I tried following the CM guide to root and get s-off but that did not work since it would not let me change the version number. I had to unlock the bootloader through HTC before it would let me run the misc_version file. After I got that working, it wouldn't let me flash old rom. No errors, it would just scan the rom and then not give me the option to flash.
I tried a few of the other guides to try to get s-off but those did not work either. Visionary does not work to get temp root. I did get temp root using fre3vo then tried running gfree to get s-off but that did not work either.
So as of now I am unable to downgrade my rom, so I can't follow the rest of the instructions from CM.
Any ideas?
Data from bootloader:
*** UNLOCKED ***
GLACIER PVT **** S-ON
HBOOT-0.90.0000
MICRIO-0429
RADIO-26.13.04.07_M
eMMC-boot
OS related:
Android 2.3.4
Software number
2.35.531.1 710RD
I did try to flash the 0.89 hboot with the htc tool but that did not work either. It timed out waiting for the phone to reconnect after reboot.
Let me know if other information is needed. I would like to get back to ICS, hard to stay with gingerbread now.
Thanks in advance!
After some more searching, looks like I need to relock my bootloader before I can downgrade. Is this right?
Roman217 said:
After some more searching, looks like I need to relock my bootloader before I can downgrade. Is this right?
Click to expand...
Click to collapse
I also just got a replacement phone and had some issues with the Cyanogenmod guide that I've used several times in the past. I downgraded to froyo, installed visionary. Gained temp root then turned s-off by :
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree --secu_flag off
I was then able to gain perm root by using this guide:
http://forum.xda-developers.com/showthread.php?t=834225
Hope this helps!
Looks like relocking the bootloader did it. Now it's letting me downgrade, so I guess I am one step closer to returning to ICS.
::EDIT::
As a recap:
Original locked bootloader did not let misc_version run.
Unlocked bootloader let fre3vo and misc_version run but did not let me flash the froyo rom.
Relocked bootloader lets fre3vo, misc_version and the the downgrade to froyo run.
And I can just flash my old nandroid backup, correct?
Or do I need to flash the rom first?
Roman217 said:
Looks like relocking the bootloader did it. Now it's letting me downgrade, so I guess I am one step closer to returning to ICS.
::EDIT::
As a recap:
Original locked bootloader did not let misc_version run.
Unlocked bootloader let fre3vo and misc_version run but did not let me flash the froyo rom.
Relocked bootloader lets fre3vo, misc_version and the the downgrade to froyo run.
And I can just flash my old nandroid backup, correct?
Or do I need to flash the rom first?
Click to expand...
Click to collapse
You should be able to reflash your nandroid backup. If not, you have a rom to flash correct?
EDIT: Are you fully rooted or are you just downgraded?
Finally got it fully rooted, flashing the nandroid backup now.
Looks like the 0.90 hboot needs to be unlocked then relocked to be able to downgrade.
It has nothing to do with bootloader, and everything to do with temp root that you didn't achieve. If you would succeed - you'd be able to flash misc_version.
Even with temp root and changing the version, the PD15IMG wouldn't flash until I relocked the boot loader.
That, of course, is correct. But I mean - you didn't have to unlock it in first place.
can you post full instruction how to gain root please and what to do, i have the bootloader unlocked i really really need that root
Deleted
estallings15 said:
Deleted
Click to expand...
Click to collapse
can you send me PM? ..??
First off here's what I'm working with:
Rogers HTC One X
Cyanogenmod from http://forum.xda-developers.com/showthread.php?t=2205183
Recovery - TWRP 2.5
Hboot - 2.14
radio - 0.23a.32.09.29
Rooted - I don't think so
SuperCID - 22222222
S-OFF - No
Lock status - Unlocked with HTCDev after SuperCID
Story time:
After deciding to install cyanogenmod on the weekend I've run in to a myriad of issues. I was able to unlock, flash CWM recovery, and install Cyanogen fairly easily, but I ran into the issue where the touch screen doesn't work.
What I've done:
I've found the fix detailed here: http://forum.xda-developers.com/showthread.php?t=2159863, but have been unable to get all the prerequisites going. From the screen fix thread linked above I need to be rooted, s-offed, and superCIDed.
I believe I got the superCID working by following the steps in this post: http://forum.xda-developers.com/showpost.php?p=41482419&postcount=2 and fastboot oem readcid returns 22222222
After that I was unlocked before but locked and relocked with a new unlockcode from htcdev
For rooting, I've looked at the methods listed under Root on http://forum.xda-developers.com/showthread.php?t=1671237, but I'm not too sure where to find which firmware I'm on. That would be the version of cyanogen would it not. I've tried the x-factor method using All-In-One Toolkit from http://forum.xda-developers.com/showthread.php?t=1952426 to no avail, as well as SuperSU from http://forum.xda-developers.com/showthread.php?t=1673935 and this one: http://forum.xda-developers.com/showthread.php?t=1644167, but I don't think any method has worked so far.
In order to use S-Off I'm pretty sure you need to be rooted, so it of course it didn't work, what made me think I wasn't rooted was when I was going through the Facepalm S-Off guide here: http://forum.xda-developers.com/showthread.php?t=2155071 when I ran "adb shell su -c "/data/local/tmp/soffbin3" it would just me the error su: not found, which means your not in as root according to: http://forum.xda-developers.com/showthread.php?p=38278577#post38278577
I've also tried going back to stock using the RUU RUU_Evita_UL_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe from http://ruu.androidfiles.org/getdown...9.28L_10.103.32.24L_release_268972_signed.exe, but when I run it I get error 99: Unknown Error, and I if I look in the log it creates it says error 44 HBOOT mismatch. I'm running after relocking, and I've tried just grabbing the rom.zip from %temp%, extracting it and flashing the boot and system imgs, but it says the system.img is too big.
At this point I'd just like to get my phone to work. If I can get it with CM that'd be cool, but stock would be good too. Any help would be appreciated.
Thanks!
In cyanogenmod you have to allow adb root access in developer options.
To ruu without s-off you need to change your cid back to the default but you will brick if you update to 3.18 after. Best to s-off since you changed your cid.
Sent from my Sony Tablet S using xda app-developers app
exad said:
In cyanogenmod you have to allow adb root access in developer options.
Click to expand...
Click to collapse
The touchpad doesn't work in cyanogenmod though, that's the root of the issue
exad said:
To ruu without s-off you need to change your cid back to the default but you will brick if you update to 3.18 after. Best to s-off since you changed your cid.
Click to expand...
Click to collapse
I was trying to RUU before changing CID, but was running in to "FAILED (remote: 44 hboot version check fail)", when running the RUU mentioned in the OP
Ah I see the ruu must have had an older hboot version than the one on your phone. You cant downgrade firmware without s-off.
To fix your issue you will need to flash a sense rom and then s-off and then downgrade your touchscreen firmware. Then you can flash whatever evita rom you like.
Sent from my Sony Tablet S using xda app-developers app
exad said:
Ah I see the ruu must have had an older hboot version than the one on your phone. You cant downgrade firmware without s-off.
To fix your issue you will need to flash a sense rom and then s-off and then downgrade your touchscreen firmware. Then you can flash whatever evita rom you like.
Click to expand...
Click to collapse
Thank you very much!
I flashed the Sense build from http://forum.xda-developers.com/showthread.php?t=2293032 and was then able to S-Off. After that I was able to down grade the touchpad firmware and install cyanogenmod.
Thanks again for pointing me in the right direction
:victory:
Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.
Have you changed your CID?
mag13 said:
Have you changed your CID?
Click to expand...
Click to collapse
Please read again.
I was Super CID (11111111) but easily changed it to match TMobile (T-MOB010) with this tool for the update.
Click to expand...
Click to collapse
yooouuri said:
Please read again.
Click to expand...
Click to collapse
I am on Super CID and it does not work
mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
You have to change your CID back to the one for your RUU.
Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4 after I flashed MaximusHD and firmware?
Now my phone is like this:
Hboot 2.16
Radio 1.20.50 (worst radio ever)
S-OFF
CID 11111111
The rom's with sense 5 (I tried just maximus because the others are not compatible with the new firmware, the sdcard mount point for multi user) are killing my battery more than twice faster compared with ViperS. 2h Display vs 5h on Viper.
Thank you!
Can we use this as rollback from h-boot 2.16 ?
mag13 said:
I am on Super CID and it does not work
Click to expand...
Click to collapse
I didn't think it would. Glad you didn't brick your phone and I'll update the OP based on your experiment.
flow27 said:
Can we use this as rollback from h-boot 2.16 ?
Click to expand...
Click to collapse
arazvan2002 said:
Can I use this tutorial to rollback to 2.15 or whatever works for ViperS rom with sense 4
Click to expand...
Click to collapse
Upgrading your hboot is a one way street, as far as I know. Can't you change the radio to something else?
I flashed Viper ROM. All the things are ok, gsm, wifi, etc just I can't see the internal memory like I should. I can browse to it file es file explorer but I need a method to default mount the new (4.2.2) location of it. Where is mounted by the internal memory in 4.1 JB? I discovered a file vold.fstab. Maybe I can change something like that somewhere to be able to use 4.1 ROM's again.
Sorry for OFF topic.
Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?
yooouuri said:
Somebody asked it but i want a clear awnser.
Can i use it to roll back to 2.15 from 2.16?
Click to expand...
Click to collapse
Yes you can if youre s-off.
Sent from HTC One S using android 4.2.2 sense 5
Im s-off and changen my RUU back to the origonal.
Using RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?
yooouuri said:
Im s-off and changen my RUU back to the origonal.
Using RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
But i get the same error. Cant update because wrong "Update tool".
-------------------------------
Flashed orig_hboot_2.15.0000.zip
But im stuck on 1.20 Radio?
Click to expand...
Click to collapse
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?
tivofool said:
Did you run the RUU.exe when your phone was in bootloader (fastboot USB mode)?
Click to expand...
Click to collapse
That's the right thing to do, yes?
kilo94 said:
That's the right thing to do, yes?
Click to expand...
Click to collapse
Yes
I have the same problem. I can't go back to stock. I haven't changed my CID yet but I see that has not worked for you.
Did you try with HTC__001 ?
dhigby said:
Running an RUU is only simple for those who haven't been messing with their devices, and that usually isn't us. Since I just did this, I want to write down the steps because I was not able to find easy answers.
This assumes your device is rooted with a different ROM installed. If that is not the case, then you can just download and run the RUU for your device, end of instructions.
Downloading the correct RUU
The most complete list of RUUs for Ville is found on androidruu.com
T-Mobile: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
HTC Europe: http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
There are RUU updates listed for other service providers, but I can't tell if they are JellyBean hboot 2.15 or not. If someone knows, I'll update this post.
Preparing your device
Make your device s-off if it isn't already. Why?
You will not have to relock the bootloader to perform the RUU update.
You will not have to flash the boot image separately.
If for some reason you can't or won't go s-off, you can still do this, but will have many more steps to follow.
Instructions to make your device s-off are here for firmwares below 3.14: Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
Or you can use the HTC All-In-One Toolkit which helps you through the process.
Use the HTC All-In-One Toolkit (link above) to change the CID to match the RUU.
You needed Super CID to gain s-off, but it won't help you install RUUs. Even if you are Super CID (11111111), you must change your CID to match the RUU you are installing (mine is TMobile: T-MOB010). I know, kinda defeats the purpose of being Super CID, but the RUU won't succeed otherwise. If you are s-off, it is a one click operation using the All-In-One Toolkit.
Backup your device
Use Titanium backup to backup all your user apps so you can restore them afterwards. (No, don't restore system apps please!)
Also back up your ROM by booting into recovery mode and selecting Backup.
If you are only updating the hboot but keeping the same ROM, you can just restore the backup afterwards. Not sure why anyone would need to update the hboot without installing a new ROM, but then you also have a backup in case things go wrong.
Run the RUU
If you are s-on you will have to relock the bootloader by rebooting into the fastboot mode, connecting your device to the computer and running the command "fastboot oem lock". You will also have to follow the process again to unlock your bootloader after doing the update. Tutorials for that are found elsewhere.
1. Leave bootloader unlocked, and leave s-off as is. No need to go back to s-on or relock bootloader.
2. Run the RUU and wait while it updates the phone (Incidentally, it didn't even wipe my sd partition data!)
3. While you are still in bootloader mode (before booting up), use the All-In-One tool to install the TWRP S4 recovery. Or, if you don't want to use the tool, you'll have to download a recovery and use "fastboot flash recovery" followed by the name of the recovery img file.
4. Reboot bootloader and enter recovery mode
5. Restore from backup or Mount USB from TWRP and copy over the ROM and gapps package, flash, wipe cache, and you are up and running.
If you are s-on you will need to extract the boot.img from the zip you are flashing and flash that image separately with "fastboot flash boot boot.img"
Note that device still has the unlocked bootloader and is still s-off! :victory:
My device before: hboot 1.09, unlocked bootloader, Super CID, s-off (In layman's terms, this is a device with an unlocked bootloader so it can accept other ROMs, set to accept any service provider's RUU update via SuperCID, and has had write permission to the boot sector removed via s-off).
My device after: hboot 2.15, unlocked bootloader, T-MOB010 CID, s-off
If possible, I will answer your comments or questions by updating this post and I'll refer you back to here.
Click to expand...
Click to collapse
Hey I used your instructions and everything was perfect thank you. I used to upgarde and downgrade hboot even to restore the HTC one S
I got the RUU "Error: 159" again with both RUU from first post and testet with each common cid, but at the end I only got success with super cid and the TMO_US Ruu.
Now I am back on Hboot 2.15 and can flash again the newest custom-recovery, thank you very much.
I've heard about a flashabe standalone zip for the hboot 2.15 and found this:
Only for S4!
Boot into bootloader and enable fastboot.
Code:
fastboot oem rebootRUU
Wait for the black screen with white HTC symbol. (Like when you flash a RUU)
then enter:
Code:
fastboot flash zip modded_hboot_YOUR_NEEDED_HBOOT.zip
then if you want
Code:
fastboot oem boot
(Boot into your current ROM)
modded_ = The red text is removed and "tampered" is gone in bootloader.
Download:
modded_hboot_1.06.0000.zip - (397.1 KB)
modded_hboot_1.09.0000.zip - (400.6 KB)
modded_hboot_1.13.0000.zip - (399.0 KB)
modded_hboot_1.14.0002.zip - (405.3 KB)
modded_hboot_1.14.0004.zip - (373.2 KB)
modded_hboot_1.14.0005.zip - (373.6 KB)
modded_hboot_2.15.0000.zip - (400.9 KB)
modded_hboot_2.16.0000.zip - (398.6 KB)
Thx goes to: touch of jobo XDA Post Source
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
Greetings by Idijt
Hi guys I think I know how to do it but any help or advise is always appreciated. This is what I know:
1.- I downloaded RUU from: http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
2.- Phone Information: Android 4.1.1, HTC Sense 4+, Software Version 3.18.502.6 710RD, BaseBand 0.24p.32.09.06_10.130.32.34L Hboot version 2.14.
3.- Phone is not rooted, not boot loader unlocked, supercid'ed or nothing.
So as far as I know I just need to install HTC Sync for dab and fast boot drivers and after that connect phone with debug enabled, run RUU utility and wait for finish update?
Thanks in advance
If you ever want to unlock your bootloader do not take that update, it has patched the latest root exploit. I'd suggest unlocking your bootloader, installing TWRP recovery, installing Superuser or SuperSU to get root, getting s-off, all before considering running the RUU. If you don't do this before taking the update you may never be able to unlock the phone.
Once you've done all that you can leave the bootloader unlocked and still run the RUU. This way you can experience the update but already have the freedom of an unlocked bootloader.
Sent from my Evita
luis4ever said:
So as far as I know I just need to install HTC Sync for dab and fast boot drivers and after that connect phone with debug enabled, run RUU utility and wait for finish update?
Click to expand...
Click to collapse
Just follow the instruction on the following webpage under "Manual system update instructions":
http://www.htc.com/us/support/htc-one-x-att/news/
HTC Sync is required, but fast boot drivers are not required, and I don't believe USB debugging is required either.
Once you run the RUU executable, it will walk you through step-by-step. Also be aware this will wipe the data partition (but not the "virtual SD" partition). So backup your data accordingly. I'd also backup what is on the virtual SD, just to be safe.
As timmaaa mentioned, the new RUU and OTA updates close the existing exploits, so if you have any desire to mod the phone in the future, its highly recommended to SuperCID, unlock bootloader, S-off before running the RUU.
redpoint73 said:
Just follow the instruction on the following webpage under "Manual system update instructions":
http://www.htc.com/us/support/htc-one-x-att/news/
HTC Sync is required, but fast boot drivers are not required, and I don't believe USB debugging is required either.
Once you run the RUU executable, it will walk you through step-by-step. Also be aware this will wipe the data partition (but not the "virtual SD" partition). So backup your data accordingly. I'd also backup what is on the virtual SD, just to be safe.
As timmaaa mentioned, the new RUU and OTA updates close the existing exploits, so if you have any desire to mod the phone in the future, its highly recommended to SuperCID, unlock bootloader, S-off before running the RUU.
Click to expand...
Click to collapse
So, what you both recommend is:
Follow timmaaa thread to get supercid and then unlock boot loader via HTC Dev and after that run rumrunner to get S-OFF?
If that's correct I have a question, can I run a RUU with S-OFF and Supercid? Do I have to relock bootloader in fastboot to run?
luis4ever said:
So, what you both recommend is:
Follow timmaaa thread to get supercid and then unlock boot loader via HTC Dev and after that run rumrunner to get S-OFF?
If that's correct I have a question, can I run a RUU with S-OFF and Supercid? Do I have to relock bootloader in fastboot to run?
Click to expand...
Click to collapse
Yes that's right. You need to use the 3.18 root method to get SuperCID, then you can unlock your bootloader. Once you unlocked your bootloader you can install TWRP recovery which will allow you to install root. Once you have root you can get s-off.
The only way you can safely run an RUU with SuperCID is if you have s-off, if you run an RUU with SuperCID and s-on you'll brick your phone. You don't need to relock the bootloader.
luis4ever said:
So, what you both recommend is:
Follow timmaaa thread to get supercid and then unlock boot loader via HTC Dev and after that run rumrunner to get S-OFF?
Click to expand...
Click to collapse
I clearly stated: "if you have any desire to mod the phone in the future, its highly recommended to SuperCID, unlock bootloader, S-off before running the RUU"
So I'm not sure why you are asking what I recommend.
If you want further clarification: If you ever want to root, or install custom ROMs on the phone, then you should SuperCID, unlock the bootloader, S-off before running the RUU.
If you intend to keep the phone stock, and never root or install custom ROMs, then its okay to run the 5.18 RUU.
luis4ever said:
If that's correct I have a question, can I run a RUU with S-OFF and Supercid? Do I have to relock bootloader in fastboot to run?
Click to expand...
Click to collapse
Yes, you can. And you should be able to do so with the bootloader unlocked.
Also, be aware that running past Jellybean RUUs with SuperCID and S-on will brick the phone. Its not known whether this still holds true for 5.18 RUU, but I'd assume it does, and never run the RUU with SuperCID and S-on. Simply get S-off first.
There isn't a reason not to get s off either. Super easy with rumrunner and from there use fastboot oem writecid
Sent from my One X using Tapatalk