Related
Hello.
Surfed the forum for an entire week regarding rooting and unlocking the bootloader.
Its HTC One X, 4.0.3 ICS, on AT&T
Managed to root it using OneXRootOneClick method (onexroot.com)
Tried to backup through the fastboot method before flashing the ROM... and when I went to the fastboot screen, and clicked on Recovery, instead of giving options of recovering Vs backing up etc., the phone immediately just wiped everything and started clean slate.
Read in detail more, and realized there is no unlockable bootloader from htcdev.com (thanks effing AT&T!!). The only current method is the one posted recently on xda (by using the Hex editor and changing your ROMs code to think it's Rogers').
So now when i restart into fastboot, I see at the top the phone is 1-tampered 2-locked 3- S-ON .. (i restored all software and data and settings, and backed up everything on titanium afterward).
So... Questions
1. Beside achieving root access and SuperSU, what else can i do with a rooted android if I cant unlock it in order to flash it?
2. How do i get ClockWorkMod on so i can backup my ROM onto my SD? And is it doable if I cant unlock my bootloader?
3. What options are there from here? (a rooted but unlocked device without CWM) And do i need superCID , busybox etc?
There are one clicks for root, supervis/unlock, and cwm recovery, I just did it today easy. Linked the tools, was very easy.
Bootloader/supercid tool.
http://forum.xda-developers.com/showthread.php?t=1672284
One click cwm recovery.
http://forum.xda-developers.com/showthread.php?t=1671873
Sent from my HTC One X using xda premium
but..
thx for the reply
will it matter with this unlock method what software i got? i noticed people on the replies of the first link that they're 1.85 , im 1.73
secondly... any mac version of the one click unlock ?
I was 1.73 it makes it easy since you need to be rooted.
I don't think there is a Mac version, you could also follow the non one clicks, or just use the commands from the one clicks, just rename the .bat file to .txt open it and copy and paste each command in adb.
Sent from my HTC One X using xda premium
baddoor said:
will it matter with this unlock method what software i got? i noticed people on the replies of the first link that they're 1.85 , im 1.73
Click to expand...
Click to collapse
The unlock method (either one click, or the hex edit) can only be performed on 1.73 and 1.82, since it requires root. If you RUU to 1.85, you will lose root, and no root method exists on 1.85 unless your bootloader is unlocked, so you are stuck without root. After you get SuperCID, you can update to 1.85, if you like, then install root using CWM.
baddoor said:
How do i get ClockWorkMod on so i can backup my ROM onto my SD? And is it doable if I cant unlock my bootloader?
Click to expand...
Click to collapse
CWM can only be installed with an unlocked bootloader. If your intent is just to backup the ROM itself, there is no need to. You can always flash the RUU to return to that version (but data wiped). And SuperCID should allow you to revert to older RUU versions, if you want to go back to 1.73. If you want to keep your data and settings, you can use this method: http://forum.xda-developers.com/showthread.php?t=1671746
Hi Guys.
I wanted to confrim if I can install any RUU on my HTC One XL with out unlocking the Bootloader or rooting or supercid.
Because in most forums i have had a look at they dont mention if its needed.
In this case i wanted to install the RUU EVITA hTC Asia WWE 2.23.707.2 and wanted to know if its required to perform the above to install the RUU.
Regards
Ruus have 3 simple rules.
1. Bootloader must be locked.
2. Cid must match. Eg WWE is not the same cid as Telstra. You need to supercid or atleast change to Telstra cid.
3. You can not downgrade hboot. The ruu must be equal or newer than your current version.
Point 2 is where you will need root.
gondwn said:
Hi Guys.
I wanted to confrim if I can install any RUU on my HTC One XL with out unlocking the Bootloader or rooting or supercid.
Because in most forums i have had a look at they dont mention if its needed.
In this case i wanted to install the RUU EVITA hTC Asia WWE 2.23.707.2 and wanted to know if its required to perform the above to install the RUU.
Regards
Click to expand...
Click to collapse
The Telstra One XL is currently Bootloader unlockable through htcdev unlike the AT&T One X. This means that we don't have to mess around to get a ROM onto our device. Why you would go to all the trouble of rooting and changing your cid (Which sometimes I've read can wipe out your IMEI and Serial Number?) when you just just unlock your bootloader, flash a recovery and then install any ROM you want.
Thanks guys for your help
I am stuck in a cm10 boot loop. Never got çm sucessufulky flashed. Was on stock deodexed rom prior to attempting cm.
I can get to twrp 2.2.0 recovery and to recovery as well but don't have a backup to flash from twrp.
I was thinking of going back to ruu 1.8.5 but my bootloader is unlocked using HTC Dev.
Any suggestions?
[QUOTE=twistedddx;30840704]Ruus have 3 simple rules.
1. Bootloader must be locked.
2. Cid must match. Eg WWE is not the same cid as Telstra. You need to supercid or atleast change to Telstra cid.
3. You can not downgrade hboot. The ruu must be equal or newer than your current version.
Point 2 is where you will need root.[/QUOTE]
Grab another rom and flash it. Try nocturnals telstra rom and see what you think.
It will be a lot easier than heading back to stock via ruu
Sent from my HTC One XL using xda app-developers app
w0tha said:
Grab another rom and flash it. Try nocturnals telstra rom and see what you think.
It will be a lot easier than heading back to stock via ruu
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
how do you flash another rom though without being able to put it on your sd card first? is there a command you can put in command prompt so that the zip shows up in recovery?
from twrp recovery, you can connect the USB and mount SDCard
then connect to computer and copy over the rom
otherwise, you could use adb commands
adb devices (make sure device exists)
adb shell
mount sdcard
Then either
adb push ROM.zip \sdcard\
or copy
AT&T ONE X
Hi,
I have an AT&T one X and i see that i cant use tethered WiFi, I dont use the phone in the USA but here in NZL, is there some way to get around this ? I cant stand the ATT rubbish they put on the phone so im looking for a unbraded rom, but Id prefer a rom which is factory rather than a custom built.
Could someone please point me in the right direction
Thanks in advance
G
gymmy said:
Hi,
I have an AT&T one X and i see that i cant use tethered WiFi, I dont use the phone in the USA but here in NZL, is there some way to get around this ? I cant stand the ATT rubbish they put on the phone so im looking for a unbraded rom, but Id prefer a rom which is factory rather than a custom built.
Could someone please point me in the right direction
Thanks in advance
G
Click to expand...
Click to collapse
Any of the stock rooted ROMs in Development except AT&T ones have WiFi tethering enabled. You of course need to be bootloader unlocked and custom recovery.
redpoint73 said:
Any of the stock rooted ROMs in Development except AT&T ones have WiFi tethering enabled. You of course need to be bootloader unlocked and custom recovery.
Click to expand...
Click to collapse
I was trying to avoid loading a custom recovery, its not that i dont trust the kind folk on here, but lets face it , it wouldnt take much to have my phone upload its contents to a dev, just call me paranoid hahahaa, so do i have to use an ATT rom ? i really would like to unbrand it also
G
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
i have supercid and i locked the bootloader to flash an ruu and restored the recovery to stock and i tried to flash a ruu and it failed and i got stuck in bootloader mode.
i need RUU:
1.84.461.11
and baseband 0.17.31501S.10_2
its israel carrier cellcom.
really need help thanks
more details--
never ran one, but assume you ran correct one
how did you "flash" it--what guide did you use--you don't actually flash it, you actually install/run it--just asking--
rugmankc said:
more details--
never ran one, but assume you ran correct one
how did you "flash" it--what guide did you use--you don't actually flash it, you actually install/run it--just asking--
Click to expand...
Click to collapse
i flashed the stock recovery through modacos website than relocked the bootloader with fastboot oem lock and than ran the exe file and i waited for like an half hour and than i saw some kind of error (don't remember the number) and than phone rebooted into bootloader and got stuck there.
i also wanted to ask if i have supercid does it mean i can install any ruu or it depends on my baseband version and other stuff?
casue i wanted to install the latest tmobile 2.35 ruu and my baseband doesn't match but i have supercid so i dont know what to do.
im new to all this stuff cause i had galaxy s2 and it was a lot easier to play with its system.
sounds like you did it all correctly
are you sure you got the stock recovery--last time i was on the site he listed two recoveries and i had to check them both out to see which one was stock
not sure on supercid as i have not ran one--maybe search, there are some threads and many posts on it--sorry
LSGio said:
i flashed the stock recovery through modacos website than relocked the bootloader with fastboot oem lock and than ran the exe file and i waited for like an half hour and than i saw some kind of error (don't remember the number) and than phone rebooted into bootloader and got stuck there.
i also wanted to ask if i have supercid does it mean i can install any ruu or it depends on my baseband version and other stuff?
casue i wanted to install the latest tmobile 2.35 ruu and my baseband doesn't match but i have supercid so i dont know what to do.
im new to all this stuff cause i had galaxy s2 and it was a lot easier to play with its system.
Click to expand...
Click to collapse
If you have SuperCID you can flash an RUU from any carrier as long as it has an HBOOT version equal or greater than your current one.
Sent from my HTC One S using Tapatalk 2
hi
i have a cid of htc-622 which is asia -hong kong
software number is 3.17.708.5
evita pvt ship s-on rl
hboot-2.14.0000
radio-0.23a.32.09.29
open dsp-v31.1.0.45.0815
can i follow this guide?
http://forums.team-nocturnal.com/showthread.php/1147
No. Just unlock your boot loader with htcdev.com and flash twrp 2.3.3.1
Sent from my One X using xda app-developers app
exad said:
No. Just unlock your boot loader with htcdev.com and flash twrp 2.3.3.1
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
thanks for the quick response
in this thread
http://forum.xda-developers.com/showthread.php?t=1677447
it says i have to be rooted to install the recovery?
is there an easy way to root?
emu123 said:
thanks for the quick response
in this thread
http://forum.xda-developers.com/showthread.php?t=1677447
it says i have to be rooted to install the recovery?
is there an easy way to root?
Click to expand...
Click to collapse
You need an unlocked bootloader to install recovery, not root.
As per AT&T, HTC blocks bootloader unlocks for AT&T customers. To do this, HTCDEV.com blocks any requests for bootloader unlocks which have an AT&T CID.
Because of this, for AT&T customers only, one must change their CID in order to trick HTCDEV.com into allowing a bootloader unlock.
To gain write access to the file that needs changing to spoof the CID, you need root access.
So what this means:
To flash recovery, you need bootloader unlocked, not root.
But because AT&T OneXLs needs to spoof the CID before unlocking the bootloader, they require root.
For AT&T > Root > SuperCID > Unlock bootloader > Flash twrp
For everyone else Skip right to > Unlock bootloader > Flash twrp
Because you do not have an AT&T phone, you will have no problems unlocking the bootloader to flash a custom recovery.
At first, things can be confusing because many posts don't really make a point of saying that those steps are only needed if you are with AT&T but when you read more than just one post, and make a point of trying to understand what you're doing, things become clearer.
right managed to get the bootloader unlocked and i am rooted
i have installed team win recovery v2.5.0.0
when i go to try and do a backup of my current rom i get e:not enough free space on storage
just found out i only have 1gb free of space on my memory so it was not enough to backup
last question
with mine being the international version can i choose any rom?
emu123 said:
last question
with mine being the international version can i choose any rom?[/QUO
Any evita rom
Sent from my HTC One XL running super smooth Sense 5
Click to expand...
Click to collapse
emu123 said:
last question
with mine being the international version can i choose any rom?
Click to expand...
Click to collapse
Considering your version (EVITA) the "international version" will get you into trouble. Most people consider the quad core Tegra3 variant ENDEAVOURU the "international" version. Yes, this is confusing, and dates back to the time when the ENDEAVORU was available in multiple countries across Europe and other regions, and the EVITA was only available in North America. Of course, the EVITA is available in many countries now, so the term "international" is basically meaningless. Stick to ROMs for the dual core Snapdragon S4 version of the One X/XL, and you will be okay.
Better yet, just use my Index thread. Any of the ROMs linked here are fine for the EVITA: http://forum.xda-developers.com/showthread.php?t=1671237
thought i would give cm10 a go
flashed the zip then extracted the boot img and flashed it and now touchscreen doesnt work
tried to get back into recovery and now it looks like my internal sd card is messed up
managed to reflash recovery and now the touchscreen works again
but having trouble getting the internal memory to show up and restore my backup
emu123 said:
thought i would give cm10 a go
flashed the zip then extracted the boot img and flashed it and now touchscreen doesnt work
Click to expand...
Click to collapse
If your phone was shipped with Jellybean, or your RUU or OTA'ed to it, the touchpad firmware was upgraded, and will not work with any AOSP ROMs.
You can downgrade the touchpad firmware, but you need to be S-off: http://forum.xda-developers.com/showthread.php?t=2159863
emu123 said:
tried to get back into recovery and now it looks like my internal sd card is messed up
managed to reflash recovery and now the touchscreen works again
but having trouble getting the internal memory to show up and restore my backup
Click to expand...
Click to collapse
If you tried to do a factory reset in bootloader, you corrupted the SD card (known bug, don't ever do it, always factory reset in recovery).
See Question 15 here: http://forum.xda-developers.com/showthread.php?t=2136172
There are also other fixes for this, if you search around this forum.
thanks
managed to get the card back , but think i will have to sideload a rom as i cant connect it to my computer and copy across my twrp backup
bit messy this flashing business lol
for some reason cleanrom wont install it was stuck on the boot logo for about 30 mins
i did try and flash the boot.img from the rom as well with the same results
viper one xl seemed to work fine
if i manage to get my twerp back up back onto my sd card and flash it back
when an update comes out does it wipe the custom recovery and root?
really struggling to find a proper ruu for my phone and the only one i could find as a .zip file