Related
when i wanna install the asia rom, the power down, and i reboot my phone , now is all black screen, i cant open my phone now, i m with rogers htc one x, how can i do ?anyone can help? Now my phone has no any ROM inside
help
Power on and hold volume down. Select fastboot. Install new Rom.
Also I would suggest not using SuperPatchef as it is not completely stable yet.
Sent from my HTC One X using xda premium
ForcedZucchini said:
Power on and hold volume down. Select fastboot. Install new Rom.
Also I would suggest not using SuperPatchef as it is not completely stable yet.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
how to install new ROM in fast boot ? any ROM i can flash?
Look in Development forum for a Rogers RUU. Just follow the instructions in the . exe.
Sent from my HTC One X using xda premium
ForcedZucchini said:
Look in Development forum for a Rogers RUU. Just follow the instructions in the . exe.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
But i cant get into the system to open the usb debugging, so i cant use superpatch , i can only use fastboot. Can it be using in fast boot?
In fastboot, execute the RUU.
lilhyper said:
In fastboot, execute the RUU.
Click to expand...
Click to collapse
i dont know how to do it, could u show me how to ?thx very much
when the phone is off...
hold VOLUME DOWN, then press the power botton
then run RUU, it should work
ytwytw said:
when the phone is off...
hold VOLUME DOWN, then press the power botton
then run RUU, it should work
Click to expand...
Click to collapse
any RUU file i can download this forum?
I love how people leap before they look. Christ, always have a way back to stock plan before jacking with your $600 toy
Sent from my HTC One XL using Tapatalk 2
help needed.
cao0215 said:
help needed.
Click to expand...
Click to collapse
There's an entire dev section you could have read by now. Stop looking for handouts and fix your [email protected]#
Sent from my HTC One XL using Tapatalk 2
cao0215 said:
Click to expand...
Click to collapse
You have given literally NO info on what you have done to try and fix it. Have you even TRIED to read and understand what you have been told and instructed to do? Have you taken it upon yourself to read the dev section about restoring stock? We are not your helpdesk and xda doesn't exist to serve you. Get off your ass and do some basic troubleshooting and problem solving. If you get stuck somewhere along the way, people will lend a hand. But until you prove that you have at least some initiative and can take it upon yourself to at least go through the steps of fixing it don't come here expecting to be spoonfed. The info is already in the dev section and the dev section isn't that big yet. It's not hard to find.
Sent from my HTC One XL using Tapatalk 2
OT, but it is good to see you with a One XL PG. From someone who remembers the Craptivate days...
Sent from my HTC One X using XDA Premium HD app
Pirateghost said:
You have given literally NO info on what you have done to try and fix it. Have you even TRIED to read and understand what you have been told and instructed to do? Have you taken it upon yourself to read the dev section about restoring stock? We are not your helpdesk and xda doesn't exist to serve you. Get off your ass and do some basic troubleshooting and problem solving. If you get stuck somewhere along the way, people will lend a hand. But until you prove that you have at least some initiative and can take it upon yourself to at least go through the steps of fixing it don't come here expecting to be spoonfed. The info is already in the dev section and the dev section isn't that big yet. It's not hard to find.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
/excited standing ovation!
Pirateghost said:
You have given literally NO info on what you have done to try and fix it. Have you even TRIED to read and understand what you have been told and instructed to do? Have you taken it upon yourself to read the dev section about restoring stock? We are not your helpdesk and xda doesn't exist to serve you. Get off your ass and do some basic troubleshooting and problem solving. If you get stuck somewhere along the way, people will lend a hand. But until you prove that you have at least some initiative and can take it upon yourself to at least go through the steps of fixing it don't come here expecting to be spoonfed. The info is already in the dev section and the dev section isn't that big yet. It's not hard to find.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
i just flash recovery into my phone , and use superpatch to flash asia ROM, but the power is dead, so the rom is not install completly, and then i get into the recovery and format the /system. Now my phone is only allowed to fast boot, and i m wondering to get the STOCK ROGERS RUU,but it's .zip , is there any way i can flash stock rom ? i m searching and go to dev section for the whole day, i m still not get the anwser.
cao0215 said:
i just flash recovery into my phone , and use superpatch to flash asia ROM, but the power is dead, so the rom is not install completly, and then i get into the recovery and format the /system. Now my phone is only allowed to fast boot, and i m wondering to get the STOCK ROGERS RUU,but it's .zip , is there any way i can flash stock rom ? i m searching and go to dev section for the whole day, i m still not get the anwser.
Click to expand...
Click to collapse
a whole day? really?
know what i found in about 2 minutes?
http://forum.xda-developers.com/showpost.php?p=25926794&postcount=39
Total recovery - flashing a RUU to completely restore your phone
If all else fails, this is your last resort.
This process will also erase all your data. But hey, beats having a dead phone, right?
First, ensure you have enough battery (more than 30%) to run an RUU.
Next, boot your phone into fastboot bootloader and open a command prompt window on your computer in the platform-tools folder.
Use the command:
fastboot getvar version-main
You now need to find the RUU that corresponds to this version. Start here. If you have problems visit #htc-one-x on freenode.
Now you must re-lock the bootloader using:
fastboot oem lock
It won't hurt to use the clear cache command as well
fastboot erase cache
Finally, run the RUU.exe that you have downloaded (must be used in Windows, and requires HTC drivers, which will have been installed whilst using HTCDev to unlock your phone).
This will write the /recovery, /boot, and /system to stock. You will need to start from scratch to unlock.
[edit]Extracting RUU if you have errors with the above method - Originally by torxx
Please note that this method isn't 100% reliable and should be considered a last resort; there have been various reports of this not working.
Many people have issues with flashing RUU's etc. having a bootlop.
Download a RUU (make sure you get the correct RUU, please see above)
Now open the .exe and make sure that it fully started.
Don't click anything, just go to windows icon and search for %temp%.
You will now find some folders, just search through these folders for the ROM.zip.
If you found it, you can copy it to your desktop or somewhere else.
Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
Plug in your One X, go into the bootloader and go into fastboot mode.
Navigate with the cmd in the folder with the fasboot.exe and the two .img's.
Now type in that:
fastboot flash boot boot_signed.img
fastboot flash system system.img
If everything worked, just reboot:
adb reboot
Click to expand...
Click to collapse
http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone
seriously man....if you arent ready to LEARN what you are doing to your phone then you need to back the hell off.
3 options:
stay stock
learn what you are doing
buy an iphone
Pirateghost said:
a whole day? really?
3 options:
stay stock
learn what you are doing
buy an iphone
Click to expand...
Click to collapse
Could not agree more. Please READ the dev forums in detail before trying to do ANYTHING to your phone. Understand what you are doing before diving in.
Staying stock seems to be the best option for you. I know English is not your first language, which is fine; it's not my first language either. Reading all the development stuff can be challenging, but it's more dangerous to venture in this world unprepared.
The HTC One X is really very usable out of the box. Just use it and don't try anything funny.
Hey Guys!
Bought a HTX One X from At&T and I'm trying to make it work here.
The problem is that the unlocking code I bought from ebay doesn't work. Neither worked the unlocking box used in a local smartphone store.
Will this actually work? What are my options?
http://forum.xda-developers.com/showpost.php?p=25251622&postcount=26
Forgot to mention the bootloader is unlocked and the phone is rooted!
Running King kang's rom, if that's matters for the case...
I saw someone saying earlier that you need to be on a Sense based ROM in order for a sim unlock to work.
Sent from my One XL using XDA Premium
Ok. That applies as well to the method I posted?
Then if I go back to a Sense based rom I'll be able to unlock it, right? Do I have to change back to the same kernel as well?
I'll search for a method to do so...
I'm not sure to be honest man, I vaguely remember seeing a thread somewhere here.
Sent from my One XL using XDA Premium
brunomcf said:
Hey Guys!
Bought a HTX One X from At&T and I'm trying to make it work here.
The problem is that the unlocking code I bought from ebay doesn't work. Neither worked the unlocking box used in a local smartphone store.
Will this actually work? What are my options?
http://forum.xda-developers.com/showpost.php?p=25251622&postcount=26
Click to expand...
Click to collapse
the thread you mentioned is for tegra 3 version. It may or may not work ( may result in other issues ) when you use on ATT version
---------- Post added at 07:37 PM ---------- Previous post was at 07:36 PM ----------
have you ever entered your unlock code?
brunomcf said:
Ok. That applies as well to the method I posted?
Then if I go back to a Sense based rom I'll be able to unlock it, right? Do I have to change back to the same kernel as well?
I'll search for a method to do so...
Click to expand...
Click to collapse
what you posted is for international one x and partitioning is different. so no it will not work. if you want to sim unlock your htc one xl you'll need to cough up a couple of bucks
Crappyvate said:
what you posted is for international one x and partitioning is different. so no it will not work. if you want to sim unlock your htc one xl you'll need to cough up a couple of bucks
Click to expand...
Click to collapse
I did pay for the unlock code on ebay, and it did not work.
probably because as the other user said, it has to be on Sense based rom.
I'm trying to find the topic to get back to it, but haven't suceeded yet.
Where can I find it?
Hey Guys!
I was trying to get my AT&T one X back to stock rom, using the RUU.
I've relocked first, but it won't get out of fastboot, and the RUU tool does not recognize my phone when usb connected.
I need to have it back at it's original rom, so I can sim unlock it...
ps: when trying to run the RUU I get error 170
brunomcf said:
Hey Guys!
I was trying to get my AT&T one X back to stock rom, using the RUU.
I've relocked first, but it won't get out of fastboot, and the RUU tool does not recognize my phone when usb connected.
I need to have it back at it's original rom, so I can sim unlock it...
ps: when trying to run the RUU I get error 170
Click to expand...
Click to collapse
Um ok ...... Did you grab the right ruu.....you need to be in bootloader for ruu not fastboot
I've tried in bootloader and still doesn't work.
I've also relocked it...
Checked several times the RUU and I have the right one. Unless it's damaged and I need another one...
brunomcf said:
I've tried in bootloader and still doesn't work.
I've also relocked it...
Checked several times the RUU and I have the right one. Unless it's damaged and I need another one...
Click to expand...
Click to collapse
make sure you have the right drivers installed...
Crappyvate said:
make sure you have the right drivers installed...
Click to expand...
Click to collapse
How do I know I have them? if not, where do I get them?
ps: just checked and instaled again. Seems not to be the problem
This is the RUU I'm using, and it matches with the phone's. Have no idea why it's not working and I'm freaking out...
RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7
MD5: A40CD830E8C57109D140E1E68E2D1328
https://www.dropbox.com/s/pq569ez3dteksp9/2012-11-12 12.42.34.jpg
As you can see from that image, it says "tampered" abd "security warning".
Is that preventing the RUU to update? How do I fix it?
everything it says is correct. the 2.20 ruu is the correct ruu also. your md5 for the ruu is also correct.
be in fastboot instead of hboot.
Check your drivers. What is it listed as in device manager?
What does "adb devices" return when the phone is connected?
Sent from my HTC One X using xda app-developers app
Hello guys, mainly developers and their friends who might mention my case between each other.
This is a quite big problem, so maybe these few lines below deserve a second read.
From the very beginning: I bought an XE in Europe from second hand. I was about to open the bootloader by using htcdev. As a good layman I found a useless thread which's misled me: I factory reset the phone and after that I did not enable USB Debugging. On the official htc site of unlocking bootloader I chose the option from the list, titled 'Sensation EU'. Since then I've already found out this is an Asian device (cid: ASIA-HK-CHT HTC__622), so I should have chosen 'All other supported device'. In the last step by unlocking bootloader I got a question about unlocking it, or not, whereupon I asked it to do so, causing immediate freeze on the screen.
So, this smartie is bricked now - even though I can reach the bootloader(h-boot 1.29) and the recovery(stock) too - considering the following: I can't unlock it anymore by using the right 'Unlock_code.bin' file either, since it shows me the same frozen screen after choosing 'yes' (by step 12 at htcdev). Nor I can S-OFF or accomplish the RUU procedure. At the latter I can go until it's checked the P58IMG.zip file, and asking me for applying the update. When I press vol_up the brick begins updating the bootloader and never finishes. I mean I like watching that screen for hours, colorful and I'm really obsessed with the phrase 'Updating...', but I'd still like to use this sensation for calls and things. If run the execute file(RUU) on PC, while the phone is connected via 'FASTBOOT USB' it gets stuck at 'rebooting bootloader...' In fastboot I can't even erase my cache, neither in recovery.
Do you think, it'll ever be able to use for its destiny again, if I'd follow the instructions you may give me?
Thank you very much in advance.
Post your bootloader details
Sent from my HTC Sensation 4G using xda premium
adamagic said:
Hello guys, mainly developers and their friends who might mention my case between each other.
This is a quite big problem, so maybe these few lines below deserve a second read.
From the very beginning: I bought an XE in Europe from second hand. I was about to open the bootloader by using htcdev. As a good layman I found a useless thread which's misled me: I factory reset the phone and after that I did not enable USB Debugging. On the official htc site of unlocking bootloader I chose the option from the list, titled 'Sensation EU'. Since then I've already found out this is an Asian device (cid: ASIA-HK-CHT HTC__622), so I should have chosen 'All other supported device'. In the last step by unlocking bootloader I got a question about unlocking it, or not, whereupon I asked it to do so, causing immediate freeze on the screen.
So, this smartie is bricked now - even though I can reach the bootloader(h-boot 1.29) and the recovery(stock) too - considering the following: I can't unlock it anymore by using the right 'Unlock_code.bin' file either, since it shows me the same frozen screen after choosing 'yes' (by step 12 at htcdev). Nor I can S-OFF or accomplish the RUU procedure. At the latter I can go until it's checked the P58IMG.zip file, and asking me for applying the update. When I press vol_up the brick begins updating the bootloader and never finishes. I mean I like watching that screen for hours, colorful and I'm really obsessed with the phrase 'Updating...', but I'd still like to use this sensation for calls and things. If run the execute file(RUU) on PC, while the phone is connected via 'FASTBOOT USB' it gets stuck at 'rebooting bootloader...' In fastboot I can't even erase my cache, neither in recovery.
Do you think, it'll ever be able to use for its destiny again, if I'd follow the instructions you may give me?
Thank you very much in advance.
Click to expand...
Click to collapse
bootloader details please
also does the phone fully boot up anymore? i assume not have you tried to factory reset from the stock recovery, or even hboot?
anything else you should know?
ganeshp said:
Post your bootloader details
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
heavy_metal_man said:
bootloader details please
also does the phone fully boot up anymore? i assume not have you tried to factory reset from the stock recovery, or even hboot?
Click to expand...
Click to collapse
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
adamagic said:
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
Click to expand...
Click to collapse
Hi,
If you can get to bootloader,you are not bricked.
adamagic said:
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
Click to expand...
Click to collapse
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
ganeshp said:
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
do you mean this link?
http://forum.xda-developers.com/showthread.php?t=1672425
ganeshp said:
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi,
THIS ONE?
rzr86 said:
do you mean this link?
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
Not the guide
malybru said:
Hi,
THIS ONE?
Click to expand...
Click to collapse
Yes this one
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Not the guide
Yes this one
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Thank you guys, I really appropriate your help. The only thing is when I try to run the execute file, it stops doing anything by "rebooting bootloader"... After 20 minutes the same screen, and the guide only tells me that it takes approximately 10 minutes. When I try to flash it from bootloader, I doesn't go any further then updating bootloader.
Question: the RUU on the link you post is 3.33.707. My phone is HK and not WWE, so it's 708 and not 707. In the txt the cid version is HTC__621, mine is HTC_622. Do you think is enough if I'd just write my cid number into that? I'll givi it a go anyways, but if you have any advice...
Thank guys, you're the best.
adamagic said:
Thank you guys, I really appropriate your help. The only thing is when I try to run the execute file, it stops doing anything by "rebooting bootloader"... After 20 minutes the same screen, and the guide only tells me that it takes approximately 10 minutes. When I try to flash it from bootloader, I doesn't go any further then updating bootloader.
Question: the RUU on the link you post is 3.33.707. My phone is HK and not WWE, so it's 708 and not 707. In the txt the cid version is HTC__621, mine is HTC_622. Do you think is enough if I'd just write my cid number into that? I'll givi it a go anyways, but if you have any advice...
Thank guys, you're the best.
Click to expand...
Click to collapse
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Sent from my Nexus 7 using xda premium
still nothing
malybru said:
Hi,
Click to expand...
Click to collapse
Yeah, thanks for the link, but it doesn't work either. I've written the 'cidnum: HTC__622' (without any spaces before and after that) into the txt, but after it's checked the P58IMG.zip doesn't ask me anything, just let me be in bootloader like I'd have started the device in bootloader mode without SD.
all right
ganeshp said:
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
All right, I will try to S-OFF using your guide, but the 3rd and 4th points are not available for me. So I can only connect my phone to PC with Fastboot USB. :\ What do you think?
p.s. This is the file I could go the furthest with: RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_HK_3.32.708.112_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253449_signed.exe
As you see, it is still 3.32, but finally 708, but the last number from that part really makes me anxious, because it's 112, and on my phone that number is 151. I really don't want to give up, so any advice will be appropriated. (Yes, I've seen the donate me button on your profile )
adamagic said:
All right, I will try to S-OFF using your guide, but the 3rd and 4th points are not available for me. So I can only connect my phone to PC with Fastboot USB. :\ What do you think?
p.s. This is the file I could go the furthest with: RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_HK_3.32.708.112_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253449_signed.exe
As you see, it is still 3.32, but finally 708, but the last number from that part really makes me anxious, because it's 112, and on my phone that number is 151. I really don't want to give up, so any advice will be appropriated. (Yes, I've seen the donate me button on your profile )
Click to expand...
Click to collapse
you can try it
you don't have to lose anything at all
if it doesn't work it will just throw you an error
see how it goes
ganeshp said:
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Click to expand...
Click to collapse
rzr86 said:
you can try it
see how it goes
Click to expand...
Click to collapse
Well, I'm in command: "* daemon not running. starting it now on port 5037 *|* daemon started successfully *" and it's been nothing happening since I've started the method 10 min ago.
"Hmm we need that ruu" => which numbers must match you think in the name of the file? And where the hell to find? yahoo twice better than ggl, so I found the previous one I've showed you.
adamagic said:
Well, I'm in command: "* daemon not running. starting it now on port 5037 *|* daemon started successfully *" and it's been nothing happening since I've started the method 10 min ago.
"Hmm we need that ruu" => which numbers must match you think in the name of the file? And where the hell to find? yahoo twice better than ggl, so I found the previous one I've showed you.
Click to expand...
Click to collapse
Flash the ruu with phone connected from fastboot
Thats should work
Also if the ruu flashing stuck at some point.. There will be a log generated at C:/ruu post the log here (latest modified file)
Edit: btw Donate won't work for me. You can donate to devs on my behalf if you want
Sent from my Nexus 7 using xda premium
ohh yes
ganeshp said:
Flash the ruu with phone connected from fastboot
Thats should work
Also if the ruu flashing stuck at some point.. There will be a log generated at C:/ruu post the log here (latest modified file)
Edit: btw Donate won't work for me. You can donate to devs on my behalf if you want
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Some persian guy has uploaded the file I need, but unfortunately I can't register, because I can't answer the randon question during the registration process... Somebody?
http://www.fars-gsm.com/showthread.php?t=57177
Ok, I have never been more tempted to throw a phone in all my life. This has me VERY irritated.
I got this htc one x on a hunch, was a good deal, seen great roms on here, thought it was a good idea. I've had nothing but trouble. Heres my deal:
I went to the htcdev site to get the boot loader unlocked. Im no dummy, I've gotten into LOTS of phones. This thing is crazy. I've watched 20 videos, used 3 different computers, NOTHING works. ALWAYS says Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
Now this isn't my first rodeo, I read, searched, paused videos made sure I was getting the same info selected, spaces, EVERYTHING that were showing between my screen and the youtube screens. This phone has taken the latest att update. Is this the problem? Has getting into the phone been cut out? Is there another way to get in and load roms? Should I ditch it for a galaxy?
You have supercid, right? The One XL can't have bootloader unlock without it. AT&T Doesn't like for people to use phones the way they're intended to be used
There is a new method for unlocking on the latest update over in general.
Sent from my HTC One XL using xda premium
I've never owned a phone so hard to deal with... Everything I read says I need to be rooted, I need to have bootloader unlocked to root, different direction loops I cant seem to break... The noobproof all require bootloader unlocked... there is SO much info, it all points in different directions, and I cant make heads or tails out of it to be honest. I've been reading for 2 days and am about to pitch this thing as far as I can.
I cant find the directions for supercid, just what it does. I normally don't require hand holding... I have an upgrade coming in September.....
Part of my issues is I don't have a charge only mode...
what carrier did the phone come from and what software version are you on?
klloyd said:
Part of my issues is I don't have a charge only mode...
Click to expand...
Click to collapse
Newest update doesn't have this option. There's a root method in dev section, however you need linux to run the script. But that's easy to make a bootable CD just to run the script. After you root then dev unlock. Then you can proceed to either fastboot a recovery or use goo manager to install the latest. Then flash away...
I recommend you follow the S-off thread too... That way you don't need fastboot to flash boot.img. then if it came with 3.18 firmware, you'll also need to follow the touchscreen downgrade thread if you plan on using Aosp roms.
It's really not hard to do the last 2 steps, but I have to agree you need to go through an a$$load of steps to get the desired effect. But this phone is great with custom roms. Some call me crazy, but if I run carbon Rom tweaked it'll rival my buddies S4 no problem
Sent from my HTC One XL using Tapatalk 2
Its a true blue att phone. Running 4.1.1, software 3.18.
I actually run Linux on about everything... I am using my wifes computer to do all this, cause it seemed windows was easier. (insert shame here)
Im just use to the one clicks, the easy additions of clockwork in a single flash on the galaxy phones. Im not giving up, but believe you me, there is an note2 or and s4 in my future.
klloyd said:
Its a true blue att phone. Running 4.1.1, software 3.18.
I actually run Linux on about everything... I am using my wifes computer to do all this, cause it seemed windows was easier. (insert shame here)
Im just use to the one clicks, the easy additions of clockwork in a single flash on the galaxy phones. Im not giving up, but believe you me, there is an note2 or and s4 in my future.
Click to expand...
Click to collapse
*Gags a little* lol. Good luck man
Sent from my HTC One XL using Tapatalk 2
The reason info conflicts is AT&T phones cant use htcdev unlock by AT&T request.
All other evita's can use htcdev fine.
So AT&T phones need root to change cid to pretend to not be an AT&T phone before they can unlock.
Sent from my HTC One XL using xda app-developers app
As normal, wonderful help! Im on the right track this time! Thanks!
klloyd said:
Its a true blue att phone. Running 4.1.1, software 3.18.
Click to expand...
Click to collapse
If that's the case, you need to go here:
http://forum.xda-developers.com/showthread.php?t=2283760
That will change you Cid so it no longer identifies your phone as an AT&T model. Then, and only then will you be able to use htcdev to unlock your phone.
Sent from my HTC One X using xda app-developers app
I am currently stuck in the bootloader. To make matters worse, I relocked to RUU and am stuck at Sending with that. I am Super CID which I think is the problem. To make matters even worse, I no longer have my unlock_code.bin file.
Is there any hope for my phone? Also, the RUU process has completely wiped my phone. Thanks for any input in advance. I have searched and searched for an answer but haven't found anything useful.
Sent from my HTC One XL using XDA Premium 4 mobile app
You haven't given enough information, what are you trying to do? You could just unlock your bootloader again.
Sent from my Evita
timmaaa said:
You haven't given enough information, what are you trying to do? You could just unlock your bootloader again.
Sent from my Evita
Click to expand...
Click to collapse
How can I unlock my bootloader without the unlock_code.bin file? Update. I reverted back to original CID CWS__001 and am going to try and run the RUU again.
I tried to s-off my wife's phone and it screwed it up somehow (rather I screwed it up). I simply wanted to take it back to stock to start fresh and now I am stuck in the bootloader with no Rom and a locked phone.
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
How can I unlock my bootloader without the unlock_code.bin file? Update. I reverted back to original CID CWS__001 and am going to try and run the RUU again.
I tried to s-off my wife's phone and it screwed it up somehow (rather I screwed it up). I simply wanted to take it back to stock to start fresh and now I am stuck in the bootloader with no Rom and a locked phone.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Sent from my Evita
timmaaa said:
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Thanks for your input. I appreciate it. Can I at least ruu the 3.18 now and get back to stock... That's better than bootloader I suppose. By the way, how could I have unlocked in the state I was in?
Ruu is stuck at sending for some time now.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
//JavaJ said:
timmaaa said:
You would just go to htcdev like you did in the first place and go through the unlock process again. But, you can't do that now because you just changed the CID back to CWS__001 which is blocked by htcdev. And I'm guessing you didn't succeed in getting s-off? If so, you've just used the one and only time you can change the CID without s-off to change it to a CID which is blocked, which means you have no way to unlock the bootloader again, ever. I hope your original plan was to stay stock because that's your only option now. Maybe that's for the best though, you seem to be doing things without fully comprehending what you're doing or the potential catastrophic results.
Thanks for your input. I appreciate it. Can I at least ruu the 3.18 now and get back to stock... That's better than bootloader I suppose. By the way, how could I have unlocked in the state I was in?
Ruu is stuck at sending for some time now.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you have a locked bootloader and the correct CID there should be no harm in running the RUU. The unlock process (from memory, I could be wrong) doesn't require the phone to be booted into an os, it's all taken care of while the phone is in bootloader. That's kinda irrelevant now anyway as it isn't possible anymore.
Are you using the usb cable that came with the phone? You can try using a different usb port, usually the ones on the back of the pc tower are the best.
May I ask, how exactly do you think the s-off process screwed up the phone? It either succeeds or fails, and there should be no serious repercussions from either.
Sent from my Evita
Click to expand...
Click to collapse
Ever since I ran the s off process I couldn't copy anything to the sd card, I.e. to flash a new Rom. I feel like an idiot for changing the cid back now. I ran the zip for s off and I waited an hour or so and it never went throufh
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
Ever since I ran the s off process I couldn't copy anything to the sd card, I.e. to flash a new Rom. I feel like an idiot for changing the cid back now. I ran the zip for s off and I waited an hour or so and it never went throufh
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It sounds to me like you might have actually done a factory reset from bootloader which corrupts the sd card. The s-off process has no ability to change the sd card. Did you have HTC drivers and adb/fastboot all installed when you tried the s-off process? That's probably why it didn't work.
The corrupted sd card might be why the RUU won't work, can you still get into TWRP recovery? If so, you can use the mount menu to mount it to your pc and format it. If not, you might seriously be in trouble. The combination of these things you've done have possibly rendered the device completely useless. If this if the case, I hope this has been a learning experience. It's really important to have a firm understanding of what you're doing (and the results and potential risks) when modifying your device. It looks like you've rushed into all this without understanding it all properly.
In any case, let me know about what I asked about above and I'll do my best to see if there's a way out of this.
Sent from my Evita
timmaaa said:
It sounds to me like you might have actually done a factory reset from bootloader which corrupts the sd card. The s-off process has no ability to change the sd card. Did you have HTC drivers and adb/fastboot all installed when you tried the s-off process? That's probably why it didn't work.
The corrupted sd card might be why the RUU won't work, can you still get into TWRP recovery? If so, you can use the mount menu to mount it to your pc and format it. If not, you might seriously be in trouble. The combination of these things you've done have possibly rendered the device completely useless. If this if the case, I hope this has been a learning experience. It's really important to have a firm understanding of what you're doing (and the results and potential risks) when modifying your device. It looks like you've rushed into all this without understanding it all properly.
In any case, let me know about what I asked about above and I'll do my best to see if there's a way out of this.
Sent from my Evita
Click to expand...
Click to collapse
Took your advice about the usb port. Switched it to the back and the ruu worked. Will I be able to run the root exploit again? Yes, this definitely has been a learning experience. Coupled with my lack of sleep and overall frustration I made some bad moves. Thanks for your patience and help though. Much appreciated.
And no, I could not get back into recovery after I relocked it. It would send me right back to the bootloader. Also, I did do a factory reset from the bootloader. Believe me, taking mental notes all the way here.
Sent from my HTC One XL using XDA Premium 4 mobile app
Now that you have a working os, you could be able to use the exploit again to unlock the bootloader etc. Just take it slowly though, do some reading so you gain a bit of knowledge. And if you have any questions, don't be afraid to ask.
Sent from my Evita
Unlocked and rooted. Again. Thanks for your help. Leary of trying to s off again though
Sent from my HTC One XL using XDA Premium 4 mobile app
Very glad to see you got it all working again. S-off might seem daunting now, but it's a pretty straight forward process as long as you follow the instructions exactly.
Sent from my Evita
timmaaa said:
Very glad to see you got it all working again. S-off might seem daunting now, but it's a pretty straight forward process as long as you follow the instructions exactly.
Sent from my Evita
Click to expand...
Click to collapse
Yes, I have done it before, on my One X. Not quite sure what went wrong. Maybe the issue with my wife's phone was preexisting and reared it's ugly head in the process. I have been rooting and nodding phones for years. I am not a complete noob. I am experienced in java programming and have created many interesting applications for my phone. Perhaps I should take my java knowledge and automate my s off experience.
Sent from my HTC One XL using XDA Premium 4 mobile app
If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita
timmaaa said:
If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita
Click to expand...
Click to collapse
Very nice found Tim.....:thumbup:
Swyped From BlueICESense_JBE
timmaaa said:
If you're looking for an automated method, I saw this just before. It's brand new but it looks to have some great tools incorporated. I prefer the manual method myself but many people will love this.
Sent from my Evita
Click to expand...
Click to collapse
Appreciate it. I don't mind working from the command line either. Could my trouble have had anything to do with being plugged into the front of the cpu, for s off that is? Was getting stuck at sending with the flash zip command.
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
Appreciate it. I don't mind working from the command line either. Could my trouble have had anything to do with being plugged into the front of the cpu, for s off that is? Was getting stuck at sending with the flash zip command.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah that was probably it, try again using the rear port and it'll probably be fine.
Sent from my Evita
timmaaa said:
Yeah that was probably it, try again using the rear port and it'll probably be fine.
Sent from my Evita
Click to expand...
Click to collapse
Just wanted to let you know that I went through s off and all went well. Only thing I can think was the problem was that either there was a pre existing corruption on the phone, or the usb port I was using.
Sent from my HTC One XL using XDA Premium 4 mobile app
It could have been anything. It's becoming more and more apparent that different things halt the process for different users. It makes it really difficult to troubleshoot when helping someone through the process. In the end you got it though which is great.
Sent from my Evita