Related
I've read and googled everything i can and I'm honestly still very confused and need the communities help!
Just got myself the one x with ROGERS, and yes I'm on stock rom 1.73
I'd like to flash a custom ROM...simple enough but the process seems confusing.
Here's what i understand i should do so far..
1. since I'm already locked (bootloader locked) i can just flash to 1.85 RUU..
2. Once i somehow find a way to do that...i need to unlock the bootloader from htcdev.com
Install CWM..by one click or maybe the adb method..
3. Or was it root first and then CWM...??
4. Install ROM..if you can figure out the instructions on that..
I need some serious help..the most detailed instructions possible...
Cheers and i appreciate all the help i can get.
http://forum.xda-developers.com/showthread.php?t=1676869
this link should give you all of the instructions.
rsnt said:
I've read and googled everything i can and I'm honestly still very confused and need the communities help!
Just got myself the one x with ROGERS, and yes I'm on stock rom 1.73
I'd like to flash a custom ROM...simple enough but the process seems confusing.
Here's what i understand i should do so far..
1. since I'm already locked (bootloader locked) i can just flash to 1.85 RUU..
2. Once i somehow find a way to do that...i need to unlock the bootloader from htcdev.com
Install CWM..by one click or maybe the adb method..
3. Or was it root first and then CWM...??
4. Install ROM..if you can figure out the instructions on that..
I need some serious help..the most detailed instructions possible...
Cheers and i appreciate all the help i can get.
Click to expand...
Click to collapse
Skip the first step. 1.85 is unrootable at the moment so if you try and flash using the 1.85 RUU you're screwing yourself over for the latter steps. Use the One-Click Root (search for tut) and root your device on the 1.73. Then you want to do the rest.
I belive you are mistaken. I from 1.73 root and bootloader unlock can be achieved. Then fastboot oem lock through command line, flash 1.85, unlock the bootloader again, and flash cwm. then you can flash superuser and you have root on 1.85. Right now if you want to flash custom roms 1.85 base is the only option. There are threads in the development section with tools and instructions on how to do this process.
Sent from my HTC One X using XDA
You cannot unlock your bootloader though without your phone being rooted, and if you update to 1.85 you're stripping away your root privileges. Maybe I'm mistaken, but that's how I've understood it.
This is exactly what I'm trying to avoid... all this confusion...
rsnt said:
This is exactly what I'm trying to avoid... all this confusion...
Click to expand...
Click to collapse
You can't directly unlock or root 1.85 yet, the only way you can is if you already have a super-CID from before you upgraded. Follow the tutorial on how to do that, then unlock your bootloader using HTC Dev, then flash your recovery with ClockWorkMod, then install SuperUser using ClockWordMod. That's the only thing that will work to get you what you want on 1.85
TrueLandon said:
You can't directly unlock or root 1.85 yet, the only way you can is if you already have a super-CID from before you upgraded. Follow the tutorial on how to do that, then unlock your bootloader using HTC Dev, then flash your recovery with ClockWorkMod, then install SuperUser using ClockWordMod. That's the only thing that will work to get you what you want on 1.85
Click to expand...
Click to collapse
That's exactly what I said. It is a roundabout way to root, but it is the only way. And it works.
He has a Rodgers phone so he can unlock the bootloader without needing to mod anything but i think he still needs to change the cid so that he can flash 1.85
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.
Hi everyone,
I feel kind of bad for asking such a generic question like this, and I assure you that I have read around and done my research, but before I do potentially dangerous, irreversible, things to my device, I just want to make sure that I will perform the necessary steps correctly.
Basically, I have owned my HOX since launch date, and it came with either 1.73 or 1.85 base. As such, I rooted and unlocked the bootloader as soon as the exploits were available, and have been comfortably flashing ROMs and kernels every since. However, I have been experiencing some issues with data connectivity and stuff, issues that remain with any ROM, kernel, or radio that I flash. The details aren't important...
Now, I want to basically "start over" with my HOX. As if it was a brand new, unmodified, fresh device. So basically, unroot, relock bootloader, RUU, etc... And then start all over, root, unlock bootloader, install recovery, etc.....
Basically, what exact steps do I need to take to accomplish the "starting over"? As in the methods to use, the RUU to use, etc... ?
An outline of the steps, basically. My biggest fear is restoring to the wrong thing and losing my old HBOOT.
Again, I know this question probably gets asked often, but please bear with me through this.
I ruu'd my wife a and it was about 3 weeks before att sent her the next update lol. As long as you don't accept it you'll be fine. I'm sure you'd prolly root as soon as its finished anyway..
But you got it right. No need to unroot, just fire up fastboot and enter "fastboot oem lock". (Without quotes)
Figure out which ruu you need, most likely 1.85. Make sure you have the right HTC drivers updated, and make sure HTC sync is working right. Download ruu, which is an executable application, and run it. It should factory restore your phone like the day you bought it.
As far as restoring to the "bad" hboot, it shouldn't let you complete an ruu that's for another firmware other than what you had on it when you got root... So you'll be safe. Good luck bro, come back and let us know how it went :thumbup:
Sent from my One X using Tapatalk 2
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone?
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me?
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally?
And also, once I relock my boot loader, should I immediately RUU?
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
?
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU?
And after I relock the bootloader, will the phone reboot out of fastboot or anything? Or should I go immediately from the relock phase to the RUU phase?
Thanks
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Yep.. Run it from anywhere, as long as your computer recognizes your device let us know how it goes
Sent from my One X using Tapatalk 2
Ok, thanks a lot.
I don't have a PC with me right now (mac user) but once I get the opportunity I will go through with this. Thanks again!
Im hoping this thread may help me to solve my problem (I'm a total noob too lol)
I rooted and flashed a Rom on my HTC One S, and I had the same issues as OP
Im with Fido, but I was told that both Fido and Rogers use the same RUU
Trying to go back to stock, I relocked the bootloader.
1. then I ran the RUU (found a tutorial online), but I got an error message (155: wrong RUU or file cant be larger or something like that)
2. then I tried an alternative method : extract 2 files from the RUU, move them to another folder and from there run a cmd; didnt work either
(By the way, in method number 1, I also had to flash a recovery file (stock recovery) during the bootloader unlock process)
Did I do it the right way?
Can some Senior member give me a detailed step by step method?
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
Yeah.
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
I did ???
Hey what do you know :laugh:
I have tried to do this multiple times, but no matter how many times a run the 2.2 exploit, and flash the unlock code bootloader continues to say relocked? any ideas
Yes, you need to check your pm. You need to hard reset the device. Hold power until device reboots, capacitive keys will flash during the process. Then run the unlock and you're device will unlock. I spent a full day to figure this out... Lol
Sent from my HTC One XL using Tapatalk 2
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Behemyth said:
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Click to expand...
Click to collapse
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
ECEXCURSION said:
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
Click to expand...
Click to collapse
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Behemyth said:
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671237
scroll down to the stock ruu section and look up the firmware 2.2 not the hboot 1.14
Well, I'm the OP, and I ended up figuring out what RUU to use, which was 1.73. Basically, I ran 'fastboot oem lock' , then ran the RUU right afterwards, then booted up and ran the root exploit, rooted, and then ran 'fastboot oem unlock' using my old Unlock.bin file that I had from the very first time I unlocked the bootloader. From there, I installed a custom recovery and was good to go.
Yah, if your using 2.20 firmware, run the below link, works like a charm. Must make sure you re-lock the bootloader before, or it will error out. Just hold down the power button until it turns off if this happens.
possible brick
Skeeterdrums said:
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Click to expand...
Click to collapse
I did this, but my phone never boots. It just stays at the bootloader after i run the RUU. Any ideas? :/
Also, i get the "this build is for development purposes only" message under the HTC logo before the phone enters the bootloader.
EDIT: managed to get the bootloadr unlocked again via HTCDev.com and flashed recovery and ROM. Guess Im not starting fresh after all lol
This is for International hTC One XL/Evita - Hboot 2.14 & firmware 3.17 (Orange UK)
If you own AT&T One X please look elsewhere, this guide is not for your phone
There is an abundance of information scattered in these forums and not all root methods/exploits work universally due to variation in firmware builds and Hboots.
I had to read a lot of threads to figure out how to S-off my Orange UK One XL with Hboot 2.14 and firmware build 3.17.
I was only interested in attaining S-off but had to start with HTCDev bootloader unlocking which I didn't really want to do but none of the known root exploits worked on my firmware.
I am sharing this hoping it would help others avoid taking pills for headaches when pursuing this noble quest
AIM:
Provide a short guide to others with similar device and configuration on where to start and simple clear steps to follow with needed links.
PREREQUISITES:
1. latest htc drivers for your Windows PC/laptop if you have one of those. Check here.
2. a working adb environment preferably from latest Android SDK, if you don't have this already set up please check here.
3. "USB debugging" must be checked under Phone settings>Developer options
4. an original htc USB cable is strongly recommended.
5. phone charged at above 50%
6. basic knowledge of using command prompt (cmd) in Windows and adb commands.
STEPS:
So in my case the steps were:
[1] Unlock bootloader through htcdev.com
[2] Flash/install TWRP recovery
This is done manually. All-In-One Toolkit didn't work for me BTW.
1. download latest TWRP recovery for One XL/Evita from here
2. you can rename file for easier command prompt typing later, like TWRP5.img
3. place file recovery file in your adb/fastboot folder
4. connect phone in fastboot mode to PC, make sure it displays fastboot USB on phone before you proceed.
5. start command prompt from within fastboot folder by right clicking inside folder and choosing "open prompt here", type following command:
Code:
C:\yourFastbootFolder> fastboot flash recovery TWRP5.img
Not a bad idea to test your recovery by making a nandroid backup before proceeding to next step.
[3] Flash a custom rom (root)
All custom roms are rooted by definition. If you chose e.g. ViperXL like I did remember to flash boot.img extracted form same rom zip afterwards, otherwise bootloop!
You can of course flash a SuperSU zip instead to gain root but I don't see the point.
[4] SuperCID
This is the simplest way that I found accidentally during my endless searches, all credit goes to @beaups for this one and @Austempest for sharing :good:
1. connect phone to PC in Android mode (mode where you can use phone)
2. Run the following command from command prompt (CMD):
Code:
C:\>adb shell
To enter adb shell, then enter following commands after each other:
Code:
# su
# echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
3. Reboot to bootloader and hopefully you'll see 11111111 as your CID ...... yes
[5] S-Off
Now that your are rooted with SuperCID you can just follow @beaups simple steps for S-Off found here Facepalm S-Off
That is it.... you broke your shackles :laugh:
I am not a dev and for sure not taking credit for other people's work, merely giving back and hoping this assists clarify stuff and save some time.
Cheers!
the one clicks would not work for you because you dont have an att one x so the supercid exploit doesnt work on our phones
all phones go through htcdev.com to unlock, att phones just need supercid first.
you should make a not in your guide that this guide wont work for at&t phones.
exad said:
the one clicks would not work for you because you dont have an att one x so the supercid exploit doesnt work on our phones
all phones go through htcdev.com to unlock, att phones just need supercid first.
you should make a note in your guide that this guide wont work for at&t phones.
Click to expand...
Click to collapse
Thanks for this important reminder, note added in red on top!
You mentioned one click is only for AT&T phones, I guess you mean All-In-One Toolkit by hason2000, you see even in the tool's thread it's not stated explicitly that tool works only for AT&T, while the respective threads for these exploit state that it's for AT&T One X not negating other international versions!
Most guides/tools are for North America and some Australia but very few for Europe which BTW only recently came on board with 4G/LTE.
So figuring out, especially for noobs, what is what with all these international variations for one device and huge amount of information, while searching doesn't always provide an answer is a tedious task and can end up miserably :crying:
I hope it's in order to add some info for European Evitas
guys kindly don't quote whole post(s), thanks
Only AT&T Phones are different in the case of unlocking/rooting because they can't use HTCDEV. Every other onexl is the same for unlocking/rooting.
Great guide, thanks you! it worked !
Now i'm stuck at the next step. ha :crying:
i cant get root, because my touchscreen not functional after flashed a custom rom. i had success until step 3, i cant proceed to step 4 as i cant use my touches when the rom loaded. i didnt have any back up. i already searched around to dgrade my touchscreen firmware, but it needs root. im stuck here, i can flash custom cwm recovery, install custom rom but cant touch screen. the default cm10.1 dont have android debugging enabled by default, i cant enable it cos i cant touch the screen. if i restore to stock ruu, i can touch screen n all works, but i had a problem sync google contacts.
The reason im getting my hands on custom rom is bcos my stock XL(Asian version) will neve sync google contacts properly, i tried to flash JB stock RUU, but its same. then, i started to tamper my fon with unlocking bootloader via htcdev, flash cwm(twrp mess on my sdcard storage). i had experience on older htc devices but its my 1st time on the htc one series. right now, im on evita s-on, unlocked bootloader, hboot 2.14, cwm recovery(twrp mess on my sdcard storage), not-super CID. I 'm left with a non-touchable cm10.1, i can flash any rom that supports s-on. tried to relock bootloader but i cant flash stock ICS ruu.flashing stock JB RUU is ok. my target now is to s-off n superCID.
i can :
flash RUU 3.17, running a stock RUU 3.17.
unlock bootloader
flash custom recovery(twrp mess with my internal storage)
i cant :
root my device on stock rom
touchscreen wont work on custom rom
any help will b greatly appreciated.
Do not make multiple posts about the same thing. It is strictly against XDA rules.
sorry, may i know how to delete it? i click on edit/delete but cant see any options to delete my post.
You cannot
Sent from my One X using xda app-developers app
sir how to back or normal cid help me
sir how to back or normal cid help me i have a one x its allredy super cid how get back normal cid
Fastboot oem writecid whateveryourcidwas
This will only work once with s-on after supercid but will work as many times as you want if s-off.
Sent from my One X using xda app-developers app
ignore this post. found a relevant thread
How to upgrade bootloader to 2.14
So what if you are not on HBoot 2.14?
EDIT:
Warning: It is not a good idea to upgrade only the bootloader if you intend to flash the latest CM10 builds! Avoiding RUU and unlocking again out of laziness will probably get you in trouble afterwards. RUU is definitely the safer way. You'll find a good collection of ROMs here
http://forum.xda-developers.com/showthread.php?t=2119610
and the tutorial for upgrading RUU on a previously modded phone here
http://forum.xda-developers.com/showthread.php?p=26260005
I found these threads which helped me SuperCID, S-Off and finally upgrade the HBoot of my already rooted evita.
First you need the superCID from this post:
http://forum.xda-developers.com/showthread.php?p=42351491
Next Step S-Off:
http://forum.xda-developers.com/showthread.php?t=2155069
Then RegawMOD the appropriate bootloader from this thread and flash:
http://forum.xda-developers.com/showthread.php?t=1786498
The procedure was easy once I had found the appropriate threads on XDA
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
Sent from my HTC One XL using xda app-developers app
New CM10 and derivates require HBoot 2.14
exad said:
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
Click to expand...
Click to collapse
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
ernstlustig said:
exad said:
You should not update hboot that way. It only updates one file and not all the firmware files. Ruu or flashing firmware.zip are the best ways.
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
Click to expand...
Click to collapse
That's exactly why you should not do it that way. You may get issues along the way as a result of the software not properly utilizing your hardware. This is why you're supposed to update hboot. What you did is more like tricking it into thinking you updated the firmware.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
ernstlustig said:
I simply needed an updated bootloader in order to enable flashing the latest CM10 nightlies. This did the job.
Click to expand...
Click to collapse
As exad said, CM 10 didnt want you to update just the hboot it wanted you to flash 3.18 RUU or equal to get updated firmware.
The requirement to install 3.18 RUU is listed as a requirement for CM. The hboot is what is checked but things like radio, adsp and wcnss are what actually needed to be updated, which you have not updated.
All you have successfully done is beaten the basic check for if you flashed the 3.18 RUU without actually doing what you were told to do.
How did you get s-off? i have a rogers version
salt204 said:
How did you get s-off? i have a rogers version
Click to expand...
Click to collapse
Links to XDA threads updated. (Sorry.) Please look again.
Has anyone tried successfully to write SuperCID into hboot 2.15 S-On devices?
as the instructions is for hboot 2.14, and I would like to S-Off the device with hboot 2.15 and it is S-On.
I have tried the hex with adb method, but it doesn't work.
Hi there guys,
Not sure if any of y'all remember way-back-when, but at one point my AT&T One X went into (what seemed like) a bricked state. For 8 months, I didn't touch it, charge it, yada-yada-yada. About 2 weeks ago I decided to give it a go so I charged it for a half hour and the mo'fo' decided to work. I updated my ViperXL ROM to 4.2.0 because I enjoyed it for its features. Now I'm left to ask the question, do I have to update HBOOT to flash a JB 4.3 ROM? I'm still unsure because I feel like I remembered seeing somewhere that your HBOOT has to be a newer version to run 4.3.
Thanks and regards, worldindo1.
NOTE: My current HBOOT version is reading "1.14.002".
Yes you do need to upgrade, it's written in the install instructions for the ROMs. It isn't just the hboot you need to update though, you need to run an RUU to make sure everything gets updated.
Sent from my Evita
timmaaa said:
Yes you do need to upgrade, it's written in the install instructions for the ROMs. It isn't just the hboot you need to update though, you need to run an RUU to make sure everything gets updated.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaaa,
So just relock bootloader, RUU file, and then unlock it again? Do you know of anyone who has just the firmware upgrade files from the RUU so I can do it from my Linux laptop? Thanks a ton, now I know I wouldn't have any problems or possibly brick my device haha.
Regards, worldindo1.
You need Windows to run an RUU properly, so you'll need to hit up friend to use their PC. You don't need to relock the bootloader as long as you get s-off first so I suggest getting s-off, it's pretty important because s-on + SuperCID + jb RUU = brick.
Sent from my Evita
timmaaa said:
You need Windows to run an RUU properly, so you'll need to hit up friend to use their PC. You don't need to relock the bootloader as long as you get s-off first so I suggest getting s-off, it's pretty important because s-on + SuperCID + jb RUU = brick.
Sent from my Evita
Click to expand...
Click to collapse
Howdy,
I am S-Off thankfully haha. I used XFactor back when it was still current. But I thought the main purpose of an RUU was to execute:
Code:
fastboot oem rebootRUU
fastboot flash zip (firmware).zip
Back when I had done some work with the HTC One V, we used unruu (for Linux) or on the Windows side, explored the RUU's %temp% folder to get the firmware files. Could I still issue those commands safely or have they changed how the RUU works? As well, since I'm S-Off, do I just issue all of the usual commands (minus the "fastboot oem lock") or ? Just making sure to do all of my homework before I jump in haha.
Regards, worldindo1.
Hang on, as far as I know Xfactor was a bootloader unlock exploit, that doesn't give you s-off. There's only one s-off method for our phone and that's the Facepalm method. Having an unlocked bootloader and having s-off are completely different. Can you please post your bootloader details?
Using unruu and pulling the RUU apart and flashing the firmware files is never how an RUU was supposed to be run, nor will it ever be. That's only doing a tiny portion of the job that actually running an RUU properly does. An RUU is an exe file which is meant to be run as an exe file, there is no other way to run it properly other than that. You connect your phone in fastboot mode and run the RUU in Windows and follow the prompts. Like I said though I really need to see your bootloader details (the first four lines) because I'm concerned you have s-off and bootloader unlock confused.
Sent from my Evita
timmaaa said:
Hang on, as far as I know Xfactor was a bootloader unlock exploit, that doesn't give you s-off. There's only one s-off method for our phone and that's the Facepalm method. Having an unlocked bootloader and having s-off are completely different. Can you please post your bootloader details?
Using unruu and pulling the RUU apart and flashing the firmware files is never how an RUU was supposed to be run, nor will it ever be. That's only doing a tiny portion of the job that actually running an RUU properly does. An RUU is an exe file which is meant to be run as an exe file, there is no other way to run it properly other than that. You connect your phone in fastboot mode and run the RUU in Windows and follow the prompts. Like I said though I really need to see your bootloader details (the first four lines) because I'm concerned you have s-off and bootloader unlock confused.
Sent from my Evita
Click to expand...
Click to collapse
Sorry about that my mind just drew a blank. I mixed up xfactor with facepalm haha. Yeah I'm s-off and bootunlocked.
Sent from Marianas Trench.