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.
Related
So i was in the middle of following the steps in the s-off and perma root thread and i ran into a problem. Hope someone here is nice enough to help me out.
So i ran revolutionary and everything went smooth. I already had the clockwork mod zip in the root of my sd card so i just rebooted the phone into hboot. When i went into hboot it detected the pg58img file and ran it, it prompted me if i wanted to update and so i did. It rebooted the phone and then i went back into hboot. The hboot said it was 1.23 and said Locked instead of Revolutionary as it displayed previously.
When i try to run the pg58 file in hboot an error occurs and said it is not compatible and only asks me to power off. So now at this moment it displays 1.23 version of hboot and s-off and says locked.
What can i do after this point? Any help i can get would be fantastic, thanks.
You're still good.
You're locked out of some of the most advanced fastboot commands. But that's it.
You still have S-Off. ADB will still work. You can flash ROM's. Etc etc etc....
It's a known problem. But it's not really a problem.
It's not like you divided by zero and destroyed the fabric of the universe or anything.
This is a noob question but how would i install clockwork recovery? I thought i would try dl from market but it said i didnt have root permission(obviously)
Is there a thread that has a solution to my issue or maybe you can quickly guide me out of this? lol Just kind of confused as to what i should do next lol.
Look in the development section for a thread called guide to s-off.
Skip the s-off part since you've done that.
Go right to the part about installing recovery. Following the directions. It's incredibly easy. It'll take about 3 minutes.
Once you have clcokwork recovery you can flash custom ROMs. You don't actually have to root the stock ROM. (Though you should make a backup of it just for kicks. You can do it all through clockwork recovery)
Yea I tried it multiple times already. I have the pg58 file in the root of the sd and when i go to the hboot it says
"Model ID incorrect!
Update Fail!
Press <POWER> to reboot."
Thats the only option it gives me so i am not able to install clockwork recovery.
Do you have SuperCID?
no i do not, would that fix the issue? i thought that is just for installing any rom on the device. My issue is that i cant get recovery to work.
I would think that is the next step after i run the perma root zip.
jonslaught said:
no i do not, would that fix the issue? i thought that is just for installing any rom on the device. My issue is that i cant get recovery to work.
I would think that is the next step after i run the perma root zip.
Click to expand...
Click to collapse
It should. Follow the SuperCID instructions here. Then update your firmware via the bootloader with this package that rmk made. It includes ClockworkMod Recovery.
Cool, thanks. I will definately try this as soon as I get off work later today and post up a status regarding the issue
Sent from my HTC Sensation 4G using xda premium
aNYthing24 said:
It should. Follow the SuperCID instructions here. Then update your firmware via the bootloader with this package that rmk made. It includes ClockworkMod Recovery.
Click to expand...
Click to collapse
He doesn't have use of Fastboot commands. I am pretty sure they are needed for super CID. Let me check.
He can't super CID as Fastboot commands are used.
Have you tried to run the correct RUU.exe? I think that would change back your h boot. There are zips in the development section you can use to downgrade but you may need super CID to use them.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Rhiannon224 said:
He doesn't have use of Fastboot commands. I am pretty sure they are needed for super CID. Let me check.
He can't super CID as Fastboot commands are used.
Click to expand...
Click to collapse
Yes, he does. CID commands will work with 1.23.xxxx. I've done it myself. Advanced fastboot commands won't work (he can't flash a radio through fastboot).
aNYthing24 said:
Yes, he does. CID commands will work with 1.23.xxxx. I've done it myself. Advanced fastboot commands won't work (he can't flash a radio through fastboot).
Click to expand...
Click to collapse
So basic Fastboot commands work with h boot 1.23? Good to know, my bad.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Rhiannon224 said:
So basic Fastboot commands work with h boot 1.23? Good to know, my bad.
Click to expand...
Click to collapse
Yeah, I had SuperCID to flash the new firmware to use an ICS ROM, then changed it back to the T-Mobile one after. No worries, it's confusing.
aNYthing24 said:
It should. Follow the SuperCID instructions here. Then update your firmware via the bootloader with this package that rmk made. It includes ClockworkMod Recovery.
Click to expand...
Click to collapse
I have the same problem. The Super CID does not work for me because when I type adb devices two blank lines show up, can't get the device number. I followed the instructions to the letter and usb debugging is on.
eagle_101 said:
I have the same problem. The Super CID does not work for me because when I type adb devices two blank lines show up, can't get the device number. I followed the instructions to the letter and usb debugging is on.
Click to expand...
Click to collapse
Do you have the correct drivers installed?
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
eagle_101 said:
I have the same problem. The Super CID does not work for me because when I type adb devices two blank lines show up, can't get the device number. I followed the instructions to the letter and usb debugging is on.
Click to expand...
Click to collapse
What mode are you in when you are in adb?
Rhiannon224 said:
Do you have the correct drivers installed?
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
Click to expand...
Click to collapse
I have adb tools only.
im having the same problem, but i can access recovery and i flashed a ROM but my screen freezes during boot. when i go into bootloader is says locked, 1.23.0000 s-off i can access fastboot and recovery i just dont know what to do from here, i installed a ROM and it was successful but i cant get passed the beats audio screen during boot up.
eagle_101 said:
I have adb tools only.
Click to expand...
Click to collapse
Okay, I am not near a pc atm so I cannot look where they are located, if you have the adb tools you also need another program called Net Framework installed on your pc.
Make sure your phone is powered onvand usb debugging checked when plugged into pc. I find it easiest to hold the mouse over the adb tools folder, press alt & ctrl keys and right click on the mouse and choose open command window here. Now type the command "adb devices".
Good luck.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
shehade08 said:
im having the same problem, but i can access recovery and i flashed a ROM but my screen freezes during boot. when i go into bootloader is says locked, 1.23.0000 s-off i can access fastboot and recovery i just dont know what to do from here, i installed a ROM and it was successful but i cant get passed the beats audio screen during boot up.
Click to expand...
Click to collapse
First boot can take 10 minutes to load as the Davilk cache is being recreated. Also, did you perform a full wipe first and check the Md5 checksums, make sure your downloaded ROM is not corrupt.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
I see the clean Rom requires you to be on 1.85 before you can flash it. Does anyone know if all new roms coming out will be 1.85 like this ???
Reason I ask is because I'm 1.73 & from my understanding I'd have to relock, reroot, ruu etc in order to flash this Rom & not really feeling all that lol assuming we had s-off this wouldn't be an issue. But for now is this the only method ? Thanks
Sent from my HTC One X using xda premium
doin-it said:
I see the clean Rom requires you to be on 1.85 before you can flash it. Does anyone know if all new roms coming out will be 1.85 like this ???
Reason I ask is because I'm 1.73 & from my understanding I'd have to relock, reroot, ruu etc in order to flash this Rom & not really feeling all that lol assuming we had s-off this wouldn't be an issue. But for now is this the only method ? Thanks
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I'm not an expert by any stretch of the imagination but I believe we will need a proper recovery and "S-Off" before things like this become more streamlined and user friendly. I'm just sitting back and waiting for the devs to do their magic and/or I might be picking up a second HOX to do testing on.
doin-it said:
I see the clean Rom requires you to be on 1.85 before you can flash it. Does anyone know if all new roms coming out will be 1.85 like this ???
Reason I ask is because I'm 1.73 & from my understanding I'd have to relock, reroot, ruu etc in order to flash this Rom & not really feeling all that lol assuming we had s-off this wouldn't be an issue. But for now is this the only method ? Thanks
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It looks like the ROM builders are using 1.85 just to be up to date.
I'm feeling your hesitation. I think most of us should just be patient until the dev work is done. The phone hasn't been out a month, and some amazing progress has been made. Remember when news of the locked bootloader first came out, a lot of people were suggesting it would take months to crack if it was possible at all.
Re-locking your device, upgrading RUU, and unlocking again is really a rather simple process if you want the steps to do it.
freshleysnipes said:
Re-locking your device, upgrading RUU, and unlocking again is really a rather simple process if you want the steps to do it.
Click to expand...
Click to collapse
Do you mind posting the steps?
Thanks!
How to relock bootloader to upgrade to 1.85
If you're reading this I'm going to assume you are already on 1.82 with your bootloader unlocked. I will tell you how to relock it, upgrade, and unlock it again.
Just to make things simple, open the folder where you downloaded the tools to unlock your bootloader, and copy the adb.exe AdbWinApi.dll fastboot.exe and your Unlock_code.bin to C:\Android
First to Relock your device, you will want to boot into your bootloader and select fastboot. After you've selected fastboot plug your device into your pc and open a command prompt. You'll want to type 'cd C:\Android' and then 'fastboot oem lock' and your phone will restart with a locked bootloader. Now you can upgrade to the 1.85 RUU without any issues.
Once you've finished upgrading to 1.85 you will want to boot into your bootloader again, with your device unplugged, and select fastboot. THEN plug your device in and run your command prompt again on your PC. Again, cd to C:\Android and type in the following command to unlock your bootloader again: 'fastboot flash unlocktoken Unlock_code.bin' (I've heard reports of some people having to type this command two or three times for it to work but it went the first time for me)
Now once you've finished unlocking your bootloader again you can install CWM Recovery the same way you did before.
I hope this helps!
CAN ANY BODY HELP??? I tried flashing the beta Jellybean Custom Rom. I installed the G Apps first by accident in trwp When i tried installing the actual rom. It failed
# I tried again.
Factory rested it first. So it erased my back ups
It failed again
#Now my phone was bricked
read some forums. tried unbricking it my self by using the ARU wizard and RRU.
All it did was secruity lock it.:crying::crying::crying:
# Now My One X is stuck on Hboot. But i can still get into twrp.
Ive been a fan android forever but new to rooting,.
Can anybody hellp me Please??
Andriod_Kuki_ said:
CAN ANY BODY HELP??? I tried flashing the beta Jellybean Custom Rom. I installed the G Apps first by accident in trwp When i tried installing the actual rom. It failed
# I tried again.
Factory rested it first. So it erased my back ups
It failed again
#Now my phone was bricked
read some forums. tried unbricking it my self by using the ARU wizard and RRU.
All it did was secruity lock it.:crying::crying::crying:
# Now My One X is stuck on Hboot. But i can still get into twrp.
Ive been a fan android forever but new to rooting,.
Can anybody hellp me Please??
Click to expand...
Click to collapse
if u can get into twrp...
mount sd copy a rom
wipe everyrhing except sdcard
and flash the rom... u should be good
Sent from my HTC One X using xda app-developers app
i tried doing that but my phone wont show up on my computer. ILL Try again. But what rom would u recommend.
Also is there another way i can fix it??
Thank you for helpping
Andriod_Kuki_ said:
i tried doing that but my phone wont show up on my computer. ILL Try again. But what rom would u recommend.
Also is there another way i can fix it??
Thank you for helpping
Click to expand...
Click to collapse
one promising fix would be relock your bootloader ...run a ruu....unlock ...twrp...
niceppl said:
one promising fix would be relock your bootloader ...run a ruu....unlock ...twrp...
Click to expand...
Click to collapse
Ok.. Run an RUU but it didnt get past the rom update. Am i doing it right.?
Andriod_Kuki_ said:
Ok.. Run an RUU but it didnt get past the rom update. Am i doing it right.?
Click to expand...
Click to collapse
?
what do u mean?
niceppl said:
?
what do u mean?
Click to expand...
Click to collapse
Im Using
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
When i run it. It tries to update the rom and it says rom up date fail. then closes.. Do i need to do anything before i run it??/
Andriod_Kuki_ said:
Im Using
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
When i run it. It tries to update the rom and it says rom up date fail. then closes.. Do i need to do anything before i run it??/
Click to expand...
Click to collapse
Yes, you most likely need to run the 1.85 ruu.
Sent from my One X using xda app-developers app
Andriod_Kuki_ said:
Im Using
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
When i run it. It tries to update the rom and it says rom up date fail. then closes.. Do i need to do anything before i run it??/
Click to expand...
Click to collapse
yes..relock your bootloader..
also are you att hox? or rogers hox
did you get supercid?
how you running the ruu?
if you running the .exe...did you install htc sync?(need to install this and have it running before running ruu)
Ok thanks ill try it thank u
Sent from my HTC VLE_U using xda app-developers app
Andriod_Kuki_ said:
Ok.. Run an RUU but it didnt get past the rom update. Am i doing it right.?
Click to expand...
Click to collapse
rpomponio said:
Yes, you most likely need to run the 1.85 ruu.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
suggestion to re lock his hox was mentioned but his reply didn't say if he locked it, just said he tried to run the ruu. Bet it still needs locking! Also OP do you have super cid? If so he doesnt need 1.85 right? He can use the 1.73. I would still probably use the 1.85 like rpopo recommended though. Also if you have done everything correct (re locked and 1.85 if not super cid) the USB drivers can make a difference. I was super cid and locked and ruu kept failing. uninstalled my HTC drivers and ran the HTC sync program and used those drivers...Worked first time after that! Just have to remember to not actually have HTC sync running!
Wats a super cid..? Srry I'm new to rooting
Sent from my HTC VLE_U using xda app-developers app
Try the 1.85 ruu. Relocking and running the 1.85ruu usually gets you back up and running.
Sent from my HTC One X using xda app-developers app
You have to be able to use adb on your computer to relock. There is a sticky with the info on how to install drivers, use adb and relock your phone.
Sent from my HTC One X using xda app-developers app
I have used adb to relock it
Sent from my HTC VLE_U using xda app-developers app
Then run 1.85 ruu, make sure you have the USB drivers for the phone installed and then once you do that, re-root and unlock the bootloader.
It works ran the 1.85 ruu. Ten minutes later running perfectly/ :laugh::good::good::good:
Thanks :laugh::laugh::good::good::good:
If you flashed a good ROM and your stuck in hboot, use fastboot and use the following command 'fastboot oem boot' that will force your phone to boot.
Stay unlocked push recovery in fastboot again
fastboot oem rebootRUU
Start the RUU. Finish the install, then back into hboot, select recovery
Invest in a copy of titanium backup and use between rom flashing hence there isn't a micro sd card slot in the HOX
Sent from my HTC One X using xda premium
lmnope1 said:
If you flashed a good ROM and your stuck in hboot, use fastboot and use the following command 'fastboot oem boot' that will force your phone to boot.
Click to expand...
Click to collapse
8125Omnimax said:
Stay unlocked push recovery in fastboot again
fastboot oem rebootRUU
Start the RUU. Finish the install, then back into hboot, select recovery
Invest in a copy of titanium backup and use between rom flashing hence there isn't a micro sd card slot in the HOX
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
fyi, This is an old thread. It looks like he got what he needed the 2nd day of august.
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
AT&T HOX from Android 4.2.1, with 3.18 firmware. Attempting to get to CM 10.1
Rooted and flashed TWRP via http://forum.xda-developers.com/showpost.php?p=41830252&postcount=201
Moved on to Facepalm S-off http://forum.xda-developers.com/showthread.php?t=2155071, was getting error 99.
Used the Viper solution from ChongoDroid on page 17 http://forum.xda-developers.com/showpost.php?p=38186473&postcount=163 using viper from http://forum.xda-developers.com/showthread.php?t=2087443
Install Viper from TWRP, Viper install stops at 0.00%, will not progress. Hard restart via power button battery remove sim, attempted s-off again. At some point I ended up getting the correct error 92. Success! Run 'fastboot oem boot', get list of errors, wait for boot into Android. Boot stops at white HTC splash screen, android will not boot.
Panic, hard restart back into bootloader, and this is where things go hazy (it was 5 in the morning by now). At this point I'm sure I put in some commands I should not have via adb (don't remember which ones), and did a factory reset via hboot. Recovery now brings me back into the bootloader. Bootloader shows *** TAMPERED ***, ***RELOCKED *** and *** Security Warning ***. I'm still S-ON with hboot 2.14.0000.
When in fastboot, my phone will not list via 'adb devices'. FAQ Q16 (http://forum.xda-developers.com/showthread.php?t=2136172) says if I did a factory reset in hboot, my SD mem is wiped and i need to format it from device manager. Device Manager shows my phone as Android USB Devices > My HTC and options are Update Driver Software..., Disable, and Uninstall. Updating drivers gives me a drivers up to date notice. No option to format the SD
Word is that if it turns on, it isn't bricked, but if I can't get my adb to recognize my phone, what is there that I can do to fix it? I'm on 64 bit Windows 7.
alright, first off, you flashed a ROM for the international quad core One X and you're lucky not to have bricked your phone. Secondly, what you're gonna need to do is run the 3.18 ruu and restore your phone to factory settings with that. That's the only way to recover from factory reset in bootloader. Before you do, you need to be S-Off. Which you are, correct?
Edit: re-reading this, it appears you're not s-off. I'm gonna need to call in some help here because 3.18 ruu with SuperCID will brick you, but I don't think you can use a lower RUU since you're s-on. Anyone know what to do? If you are s-off and I just misread your post, then go ahead and run the ruu.
If it turns on, there's always a way to fix it!
Adb requires an os to work, since you can't boot to your os, no Adb
That being said, in bootloader, you should be able to access your phone with fastboot. Boot to bootloader/fastboot with your phone plugged in to your pc.
Do: fastboot devices and confirm that fastboot commands reach your phone, then we will move on to the next step.
Sent from my HTC One X using xda app-developers app
Correct, I am still s-off, and 'adb devices' gives an empty list, and does not list my phone. I cannot send commands to my phone via adb commands.
You just said in your first post you're still s-on......
These details are extremely important so please be sure of what you've typed prior to posting.
Sent from my HTC One X using xda app-developers app
exad said:
Adb requires an os to work, since you can't boot to your os, no Adb
That being said, in bootloader, you should be able to access your phone with fastboot. Boot to bootloader/fastboot with your phone plugged in to your pc.
Do: fastboot devices and confirm that fastboot commands reach your phone, then we will move on to the next step.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
exad said:
You just said in your first post you're still s-on......
These details are extremely important so please be sure of what you've typed prior to posting.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes, sorry. I realized my mistake as soon as I posted, but since I'm a new member I can only edit or reply every 5 minutes.
Yes, I am S-ON. S-ON, not S-OFF.
And aha, yes. 'fastboot devices' does list my phone.
Good good. So first you'll want to unlock your bootloader again since it's relocked. Just flash the unlock_code.bin or whatever it's called again that you previously used.
Sometimes if you're relocked it does the unlock process like it's going to unlock but then leaves you relocked. If this happens press and hold power to simulate a battery pull and try again. It should work eventually. Might take several tries.
Sent from my HTC One X using xda app-developers app
Korad said:
Yes, sorry. I realized my mistake as soon as I posted, but since I'm a new member I can only edit or reply every 5 minutes.
Yes, I am S-ON. S-ON, not S-OFF.
And aha, yes. 'fastboot devices' does list my phone.
Click to expand...
Click to collapse
I'm assuming you have supercid already?
I would reflash twrp.. nothing higher that 2.3.3.1
Then load a sense Rom from this forum through twrp. Just to get a running os on the phone. Then you can s-off and run 3.18 ruu
Sent from my HTC One XL using xda premium
exad said:
Good good. So first you'll want to unlock your bootloader again since it's relocked. Just flash the unlock_code.bin or whatever it's called again that you previously used.
Sometimes if you're relocked it does the unlock process like it's going to unlock but then leaves you relocked. If this happens press and hold power to simulate a battery pull and try again. It should work eventually. Might take several tries.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Okay, flashed Unlock_code.bin on first try, now showing *** UNLOCKED ***
Korad said:
Okay, flashed Unlock_code.bin on first try, now showing *** UNLOCKED ***
Click to expand...
Click to collapse
Do as ken posted above though twrp 2.6 is supposedly stable and fine too.
Roms from here are safe to flash: http://forum.xda-developers.com/forumdisplay.php?f=1541
And... Here: http://forum.xda-developers.com/forumdisplay.php?f=1726
Sent from my HTC One X using xda app-developers app
exad said:
Do as ken posted above though twrp 2.6 is supposedly stable and fine too.
Roms from here are safe to flash: http://forum.xda-developers.com/forumdisplay.php?f=1541
And...:
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Have you flashed 2.6 yet? I've heard it works as well but was waiting for more input
Sent from my HTC One XL using xda premium
Not yet, going to when I get home. Jacobas92 said hes been using it though and I trust him.
Sent from my HTC One X using xda app-developers app
Well I'll take ur word for it. Gonna download and flash now and test the hell out of all options.
Sent from my HTC One XL using xda premium
31ken31 said:
I'm assuming you have supercid already?
I would reflash twrp.. nothing higher that 2.3.3.1
Then load a sense Rom from this forum through twrp. Just to get a running os on the phone. Then you can s-off and run 3.18 ruu
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Korad said:
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Click to expand...
Click to collapse
I believe you need to be on a rooted ROM to get s-off.
Korad said:
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Click to expand...
Click to collapse
Viper xl will work fine that's what I used to s-off. Not with the new cm10.1 kernel you have to ruu up to 3.18 before you install it.
Sent from my HTC One XL using xda premium
31ken31 said:
Viper xl will work fine that's what I used to s-off. Not with the new cm10.1 kernel you have to ruu up to 3.18 before you install it.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
hes already on 3.18
If I'm using ViperXL as my ROM during S-Off, will I want to use ChongoDroid's extra steps when installing ViperXL or should I only need to do those if the Facepalm S-Off steps don't work by themselves?
Korad said:
If I'm using ViperXL as my ROM during S-Off, will I want to use ChongoDroid's extra steps when installing ViperXL or should I only need to do those if the Facepalm S-Off steps don't work by themselves?
Click to expand...
Click to collapse
You should be able to S-OFF with viperxl without any problems just by flashing viperxl and following the S-OFF thread right after.
So ViperXL finally finished downloading, and I've sent the command to push the .zip to /sdcard in prep to install it with TWRP, but it's been stuck there for 15+ minutes. Should I be worried? Should I restart?