UPDATE
=========
I just wanna say that tomy1986.nt is the man!!!! If you have a bricked device send it to this guy, worth the money! He fixed my device within an hr! It wouldn't power on at all!
http://forum.xda-developers.com/member.php?u=4116958
Dropped it off at his house and he worked his magic!
=========
Ok got an HTC One X..... ran the RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe to update the device after running "fastboot oem lock" and the program said it had completed successfully, the phone turned off and never came back on. I unplugged the device and attempted to turn it on, no lights, no nothing.
The only thing that happens is if I plug it into my computer I hear the sound you hear when a driver is attempting to install. The HTC drivers are indeed on my computer.
Any hope for unbricking this thing or am I screwed?
Thanks!
Do you have the One X (Endeavor) or the One XL (Evita)?
Sent from my Evita
I have the one x but my understanding was the roms were interchangeable. It's the AT&T One X.
You're just a bit mixed up with your terminology. Your phone is the the at&t One X / HTC One XL (Evita), the HTC One X is the Endeavor.
Being that the at&t One X and HTC One XL are the same phone (Evita), the ROMs are the same. But HTC One X (Endeavor) ROMs are not for our phone and can brick it if flashed.
Was your phone second hand? Do you know if it had SuperCID? And whether it is s-on or s-off? If it has SuperCID and is s-on, running an RUU causes a brick.
Does the phone show up as QHSUSB_DLOAD in device manager on pc when you connect it? If so you have a brick, and still need to get a jtag repair done.
Sent from my Evita
If the phone was S-on and SuperCID, you have a true hard brick. As timmaaa mentioned, if you get QHSUSB_DLOAD when you connect to PC, this pretty much confirms it.
Sounds like either you, or the original owner unlocked the bootloader, since you went through the step of relocking it (or at least you suspected it may be unlocked). So my guess is that you are another victim of the S-on + SuperCID + Jellybean RUU/OTA combo.
http://forum.xda-developers.com/showthread.php?t=2181929
Actually I only used evita roms/ruu's.
Here is exactly what I did:
1) Rooted / S-OFF / Flashed Recovery / Unlocked Bootloader / Super CID 111111111 (how many ever 1's)
2) Locked Bootloader and refreshed with 2.20 RUU which was successful
3) Rebooted phone, enabled debugging
4) Ran 3.18 RUU (AT&T One X) and it said successful.
5) Device powered off and i waited, never came back on so i unplugged it
6) Makes driver noise when plugging to pc but does not power on visually, no lights etc
I found a guy locally who can try the jtag.
You could try charging it for a few hours and try holding power + volume down to see if it boots. Every now and again these phones have a power management issue where it loses power (or thinks it does) completely.
If that doesn't work it looks like you might be one of the very unlucky people who has had an RUU brick their phone for no apparent reason.
Sent from my Evita
ssconceptz said:
Here is exactly what I did:
1) Rooted / S-OFF / Flashed Recovery / Unlocked Bootloader / Super CID 111111111 (how many ever 1's)
Click to expand...
Click to collapse
Ok, so it wasn't the combo of S-on, SuperCID and Jellybean RUU that caused the brick then.
But any flashing of hboot has some small possibility of bricking the phone, if everything does not go exactly right (such as corrupt RUU file). You can look into the unbricking thread in General:
http://forum.xda-developers.com/showthread.php?t=1966850
You can see if you can enumerate the partitions with Linux. If the parititions can't be found, JTAG is your next option.
Nobody has been able to unbrick this way from the S-on, SuperCID, RUU combo, that I know of. But your case is slightly different, so maybe you still have a chance.
---------- Post added at 11:18 AM ---------- Previous post was at 11:13 AM ----------
timmaaa said:
You could try charging it for a few hours and try holding power + volume down to see if it boots. Every now and again these phones have a power management issue where it loses power (or thinks it does) completely.
Click to expand...
Click to collapse
Yes, its a good idea to try that.
Although the fact it went dark right after running the RUU, doesn't have me very hopeful.
Yeah I'm not hopeful at all either, but it's worth a try.
Sent from my Evita
timmaaa said:
Yeah I'm not hopeful at all either, but it's worth a try.
Click to expand...
Click to collapse
Absolutely! Always good to try the easy stuff first, before resorting to more drastic measures.
Thanks for the tips. Will try the unbrick hardware method, if doesn't work maybe i'll find a busted up device and use this one for parts.
I just wanna say that tomy1986.nt is the man!!!! If you have a bricked device send it to this guy, worth the money! He fixed my device within an hr! It wouldn't power on at all!
http://forum.xda-developers.com/member.php?u=4116958
Dropped it off at his house and he worked his magic!
Related
So I just got my phone back working properly by flashing a Ruu for a previous problem. I was notified of the Jellybean update and proceeded to download it.. Everything was going fine when it came down to installation, but all of a sudden the phone went black and will not turn back on. It had a full charge on it,so Idk whats the problem.. Any suggestions ???
Let me guess: You were rooted and had superCID?
Sent from my Nexus 7 using Tapatalk HD
Should have read this first:
http://forum.xda-developers.com/showthread.php?t=2181929
Sent from my One X using Tapatalk 2
No, I don't have neither..
iElvis said:
Let me guess: You were rooted and had superCID?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
the whole process took awhile for me, felt like it rebooted a few times also. about 20 minutes i think, you could of got in a hurry during the process and messed it up. does the phone detect? maybe u can reruu?
Have you tried holding the power button down for a while (like 30 secs)? You can't get into bootloader via power+vol down? What happens when you plug into your computer? What do you see in Device Manager?
Bricks on stock phones from borked otas are not common, but they do happen. If so, AT&T is good about replacements.
If the charge LED does not come on when charging (use the wall charger, not USB), and the screen doesn't come on at all after charging overnight, the phone is probably not recoverable.
As iElvis mentioned, bricks caused be the OTA aren't common, but they do happen. For one thing, the OTA flashes a new hboot. So if something goes wrong during that process, it may brick the phone. If you are bone stock, its the fault of the update, so AT&T will replace it.
The LED does not come on, believe me I have tried keeping it on the charger all night, with no success.
redpoint73 said:
If the charge LED does not come on when charging (use the wall charger, not USB), and the screen doesn't come on at all after charging overnight, the phone is probably not recoverable.
As iElvis mentioned, bricks caused be the OTA aren't common, but they do happen. For one thing, the OTA flashes a new hboot. So if something goes wrong during that process, it may brick the phone. If you are bone stock, its the fault of the update, so AT&T will replace it.
Click to expand...
Click to collapse
I tried this, and nothing happened.. I will head to my nearest AT&T store soon to get a replacement hopefully.. I guess its not all bad though, I have been enjoying my Lumia 920 with Windows phone 8, but I am missing my Android!
iElvis said:
Have you tried holding the power button down for a while (like 30 secs)? You can't get into bootloader via power+vol down? What happens when you plug into your computer? What do you see in Device Manager?
Bricks on stock phones from borked otas are not common, but they do happen. If so, AT&T is good about replacements.
Click to expand...
Click to collapse
hrrsncrawford14 said:
So I just got my phone back working properly by flashing a Ruu for a previous problem. I was notified of the Jellybean update and proceeded to download it.. Everything was going fine when it came down to installation, but all of a sudden the phone went black and will not turn back on. It had a full charge on it,so Idk whats the problem.. Any suggestions ???
Click to expand...
Click to collapse
I am having the same problem, just updated using 3.18 ruu and the phone went blank it detects as Qhsusb_dload and the ruu doesn't detect anymore
nmupparaju said:
I am having the same problem, just updated using 3.18 ruu and the phone went blank it detects as Qhsusb_dload and the ruu doesn't detect anymore
Click to expand...
Click to collapse
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
redpoint73 said:
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
Click to expand...
Click to collapse
I'm sure it's the same thing.
redpoint73 said:
Did you have SuperCID? S-on?
The OP is talking about updating via OTA, which is known to brick your phone if you have SuperCID and S-on. But I was wondering what would happen with the RUU, which was just posted by HTC a couple days ago.
Click to expand...
Click to collapse
I did get supercid, unlocked bootloader installed cm10 relocked bootloader, ruu to 2.20 used for few days, used update tool from htc website to update to jellybean, after using the tool phone never booted back , dead (I guess brick)
When connected to windows pc qhusb_dload shows up
nmupparaju said:
When connected to windows pc qhusb_dload shows up
Click to expand...
Click to collapse
You've got a brick. Sorry. It's not clear why this is happening, but once you're in that mode, you're done.
Starting with where I am now: my ATT One X is totally unresponsive. Power button held, Power plus either of the volume buttons held, nothing produces any response. When I plug it into a wall adapter, the charging LED doesn't light up. It is both looking and talking like a brick.
Here's how I got here, and I'm hoping someone may have some kind of suggestion .
I had been running Tachi91's original Sense JB ROM. TWRP recovery. I used the AT&T JB update RUU from HTC's site.
Before doing this, I rebooted to bootloader and re-locked the bootloader. After this, I seemed to be unable to reboot back into system, so I just ran the RUU while the phone was sitting in the bootloader (figuring that the first thing the RUU seems to have done in the past is reboot to the bootloader).
The RUU went through its usual lengthy, multi-reboot thing. No errors whatsoever, everything seemed totally fine. Clicked "Finish" at the end...and my phone's screen went black. I figured it was rebooting, but unless it's taken the past 40 minutes to reboot (which seems unlikely! ), something is obviously amiss. See beginning of post for what I've tried since and results.
Any suggestions?
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
I fear the worst.
Sent from my HOX w/CM10.1 4.2.2 s-off
subarudroid said:
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
I fear the worst.
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
...yeeeeah, total violation of item #1 on that list. And here I figured I was relatively safe with an RUU. Oops.
Thanks for pointing that post out to me. At least I know where I stand now! Better than sitting here making my thumbs go numb trying different power/volume combinations.
Why oh why do many people persist in thinking they don't need s-off??
Sent from my Nexus 7 using Tapatalk HD
Please help!
Hey, does any one know if there is any solution i can do myself? or do i have to send it to a jtag repair, because i just received it a month ago from a earlier brick. I just can not believe i bricked it again doing a RUU update. Thank you
buy a jtag
Nicobesso said:
Hey, does any one know if there is any solution i can do myself? or do i have to send it to a jtag repair, because i just received it a month ago from a earlier brick. I just can not believe i bricked it again doing a RUU update. Thank you
Click to expand...
Click to collapse
Could try the JET. Check the Development forum.
So, just to set the stage, I'm not a developer, but I'm fairly practiced at using ADB, unlocking bootloaders, rooting and unrooting, and installing custom recoveries and ROMs - that is to say, I know what I'm doing. I recently bought an HTC One, and in preparation for wanting to sell my One X on ebay, I wanted to return it to completely stock and make sure OTA updates were working properly.
I started by relocking the bootloading and installing the 2.20.502.7 RUU (I have an AT&T One X). That went fine and booted up properly, but I wasn't seeing the OTA updates, so I thought maybe the stock recovery hadn't been installed properly, and when I tried to boot into the recovery I couldn't get the menu to show (the initial image appeared, but holding Vol Up+Down didn't do anything, just made the error image appear after several seconds). So I downloaded the stock recovery image, reunlocked the bootloader, flashed the stock recovery...and then when I went to reboot the phone turned off and hasn't turned back on since.
Getting stuck in a bootloop or something I know how to deal with, but the phone is completely unresponsive, holding the power button for any length of time seems to have no effect, hoping you guys might have some ideas.
FYI My phone was on bootloader 1.09 before flashing the RUU, 1.14 after.
Requested moving to the AT&T One X forums
TToivanen said:
Requested moving to the AT&T One X forums
Click to expand...
Click to collapse
Ugh....thought that's where I was, evidently didn't look at the forum close enough...
bikeracer4487 said:
So I downloaded the stock recovery image, reunlocked the bootloader, flashed the stock recovery...and then when I went to reboot the phone turned off and hasn't turned back on since.
Click to expand...
Click to collapse
Where did you download from, and can you give link? Any charge light, when you connect the wall charger?
redpoint73 said:
Where did you download from, and can you give link? Any charge light, when you connect the wall charger?
Click to expand...
Click to collapse
Link to site of download link: http://onexroot.com/one-x-unroot/how-to-unroot-rooted-htc-one-x/
Download link: http://downloadandroidrom.com/file/HTCOneX/unroot/OneXUnroot.zip
Connecting charger shows blinking red notification light. As a side note, the phone was at 96% battery when I was working on it and I left it plugged in overnight, just in case.
That website doesn't make mention of the AT&T version. Not certain, but I'm inclined to believe its the recovery for the quad core version. Different hardware, with different partitions, so you might be hosed.
Take great care when you install mods from these kinds of websites (places other than XDA). They often do not clearly delineate between the dual core and quad core versions of the One X.
redpoint73 said:
That website doesn't make mention of the AT&T version. Not certain, but I'm inclined to believe its the recovery for the quad core version. Different hardware, with different partitions, so you might be hosed.
Take great care when you install mods from these kinds of websites (places other than XDA). They often do not clearly delineate between the dual core and quad core versions of the One X.
Click to expand...
Click to collapse
Yeah...that was dumb...I realized what you were getting at as I was getting the link for you... That said, I WAS able to get it turn on just now by holding down the Vol Down button and power for 10 seconds...although, didn't actually do anything, letting go of those buttons and simultaneously unplugging it from the charger made it turn on...not sure which or both of those things were actually the cause though. But once I was booted in I tried booting into recovery with "adb reboot recovery" but that got me to the HTC logo screen with the developer warning but it hung there. Luckily, I was able to boot into the bootloader, but again, trying to get into the recovery made it hand at the "quietly brilliant" screen. Do you know if the stock RUU's are supposed to flash the stock recovery, or do have a link to AT&T's stock recovery? I'm having a hard time finding one labeled properly.
Yes, RUU flashes stock recovery.
If the screen is coming on, that is usually a good sign. Try the RUU again.
BTW, do not not not install the 3.18 RUU if you are SuperCID and S-on. Or you will brick.
redpoint73 said:
Yes, RUU flashes stock recovery.
If the screen is coming on, that is usually a good sign. Try the RUU again.
BTW, do not not not install the 3.18 RUU if you are SuperCID and S-on. Or you will brick.
Click to expand...
Click to collapse
Okay, I'll try that, I still have the 2.20 RUU. Good to know on the 3.18 since I am def SuperCID. Will being SuperCID affect my ability to install OTA updates?
bikeracer4487 said:
Will being SuperCID affect my ability to install OTA updates?
Click to expand...
Click to collapse
Yes, SuperCID and S-on will also brick your phone, if you try to install 3.18 OTA.
You might consider doing s-off, or changing back to the AT&T CID. Even if you don't update using the 3.18 OTA, its very possible the buyer will.
redpoint73 said:
Yes, SuperCID and S-on will also brick your phone, if you try to install 3.18 OTA.
You might consider doing s-off, or changing back to the AT&T CID. Even if you don't update using the 3.18 OTA, its very possible the buyer will.
Click to expand...
Click to collapse
Good idea. Found a thread for S-OFF (http://forum.xda-developers.com/showthread.php?t=2155071) but not sure how to restore AT&T CID.
EDIT: Frick, wish I had though to do this BEFORE installing RUU and unrooting the phone.
Hi, I need some serious help. So I had a custom rom on my at&t htc one x and i made like 3 backup of my rooted stock rom to be safe. My phone is unlocked cause I live in the Caribbean (No AT&T). Then I realised that my 4g wasn't working on the custom rom so I booted to Recovery using Team Win, wiped my data, cache and the system then tried to restore my backup. It said successful but it just booted the HTC Quietly Brilliant screen over and over. So of course, I tried the other 2 backups and it did the same. So I decided to flash the custom rom back on then try to restore the 2.20 stock rom .exe (which I've done before) from my computer. But I didn't want to go back to ICS so I downloaded the 3.18 jellybean rom for AT&T HTC One X directly from HTC's website and proceeded to relocking my bootloader and unrooting the phone, etc. Again, it said successful. THIS IS WHERE IT GETS BAD. The phone never came back on :'(... It doesn't charge, no red light, no boot screen. I can't get into the bootloader, recovery nothing! When I hold down the volume down and power key nothing happens, not even the blinking lights. When I connect it to the pc it makes a sound I've never heard. While connected, when I hold down the buttons, I hear the sound I usually hear when you know it's connected but then it makes the other sound and in my device manager i see "QHSUB_DLOAD". I can't run nothing because the computer can't find it.
Sigh, forgive me I'm a noob who got overly exited about rooting and roms but was I wrong to jump to 3.18 considering it is an official update from HTC? But now what do I doooo? Is it gone? Dead? Can it be revived? Please help me
Did you have s-on or s-off? If you had s-on you've bricked your phone. S-on + SuperCID + jb RUU = brick. You can either get a jtag repair done or send it to HTC for motherboard replacement.
Sent from my Evita
timmaaa said:
Did you have s-on or s-off? If you had s-on you've bricked your phone. S-on + SuperCID + jb RUU = brick. You can either get a jtag repair done or send it to HTC for motherboard replacement.
Sent from my Evita
Click to expand...
Click to collapse
Damn I knew I should've changed it. Yea I have s-on, sigh ...I was hoping I didn't have to send it away but jtag it is.
Thanks.
You could try the hex edit method to change your CID, I'm not sure if it'll work but it's worth a try. You'll find it here.
Sent from my Evita
timmaaa said:
You could try the hex edit method to change your CID, I'm not sure if it'll work but it's worth a try. You'll find it here.
Sent from my Evita
Click to expand...
Click to collapse
I'm pretty sure it won't work because the phone won't turn on at all and command prompt can't find it. I can't access the bootloader, I can't turn on the phone to set debugging on
Sorry I think I posted that in the wrong thread maybe.
Sent from my Evita
ATT HTC One X
timmaaa said:
Did you have s-on or s-off? If you had s-on you've bricked your phone. S-on + SuperCID + jb RUU = brick. You can either get a jtag repair done or send it to HTC for motherboard replacement.
Sent from my Evita
Click to expand...
Click to collapse
Hi, I'm back again. Okay so I got my htc one x jtagged and I'm smiling from ear to ear but yea I'm really over ics so I'm about ready to root and all that. Now I checked my cid and it's 22222222:
1. Is that bad?
2. What does that mean?
3. Do I have to root, unlock bootloader, and turn s-off to update the ruu or can I do it just here how it is? Or will it hard brick again?
I can't take another hard brick so kindly help me out please. Thank you
Sounds like you are asking for some hand holding rather than researching and learning on your own. You had plenty of time to search and read and learn. I know you will get help but I don't think you deserve it.
Sent from my HTC One XL
Know your place
954wrecker said:
Sounds like you are asking for some hand holding rather than researching and learning on your own. You had plenty of time to search and read and learn. I know you will get help but I don't think you deserve it.
Sent from my HTC One XL
Click to expand...
Click to collapse
Excuse me, fyi I have been searching. I have like 20 tabs open. I've been searching for what all 2s mean If I found something you think I would've asked? Excuse me if I don't want my phone hard brick again! Don't be an ass! I'm trying and I'm learning slowly. If I don't ask how the hell am I gonna learn eh? All I'm asking is if I have to go through the rooting process or I can just update the ruu, I'm not asking how to from A to Z -_- I can do everything else myself thank you very much!
YannaKi said:
Hi, I'm back again. Okay so I got my htc one x jtagged and I'm smiling from ear to ear but yea I'm really over ics so I'm about ready to root and all that. Now I checked my cid and it's 22222222:
1. Is that bad?
2. What does that mean?
3. Do I have to root, unlock bootloader, and turn s-off to update the ruu or can I do it just here how it is? Or will it hard brick again?
I can't take another hard brick so kindly help me out please. Thank you
Click to expand...
Click to collapse
1. no
2. It's Super CID. It bypasses CID checks allowing you to flash things not intended for your device region. it also allows you to S-OFF
3. If you JTAGGED you might already be S-OFF, check in bootloader. IF you try to RUU and you are not S-OFF you risk bricking.
exad said:
1. no
2. It's Super CID. It bypasses CID checks allowing you to flash things not intended for your device region.
3. If you JTAGGED you might already be S-OFF, check in bootloader. IF you try to RUU and you are not S-OFF you risk bricking.
Click to expand...
Click to collapse
Thank You! Last time when I rooted it the supercid was all 1s and I didn't expect all 2s so I just wanted to make sure. And yes, it's S-ON. I only wanted it repaired, I wanna do the rest myself.
So thanks again I'll root it and turn S-OFF and hope I don't brick it a second time.
YannaKi said:
Thank You! Last time when I rooted it the supercid was all 1s and I didn't expect all 2s so I just wanted to make sure. And yes, it's S-ON. I only wanted it repaired, I wanna do the rest myself.
So thanks again I'll root it and turn S-OFF and hope I don't brick it a second time.
Click to expand...
Click to collapse
Good plan and good luck. If you have any other questions, do not hesitate to ask.
exad said:
Good plan and good luck. If you have any other questions, do not hesitate to ask.
Click to expand...
Click to collapse
So I'm trying to root it but cmd is saying CID not found. If 22222222 is a SuperCID then why does it say it failed? I'll paste it below:
[*] Waiting for device...
[*] Device found.
[+] Restoring first backup...
[+] Please authorize the backup on your phone, and
[+] press enter when the backup restore has completed.
Press any key to continue . . .
[+] Restoring second backup...
[+] Please authorize the backup on your phone, and
[+] press enter when the backup restore has completed.
Press any key to continue . . .
96 KB/s (64526 bytes in 0.650s)
[-] CID not found.
[+] Rebooting into bootloader mode...
[+] Press enter once the device has finished booting into bootloader mode.
Press any key to continue . . .
[+] Getting CID:
...
(bootloader) cid: 22222222
OKAY [ 0.053s]
finished. total time: 0.054s
[+] If your CID is not "11111111", the exploit has failed, and you should close
this window.
What exploit are you using?
Sent from my Evita
timmaaa said:
What exploit are you using?
Sent from my Evita
Click to expand...
Click to collapse
X-Factor: HTC One X Root Exploit (Windows version)
by Dan Rosenberg (@djrbliss)
Greets/thanks to Michael Coppola
YannaKi said:
X-Factor: HTC One X Root Exploit (Windows version)
by Dan Rosenberg (@djrbliss)
Greets/thanks to Michael Coppola
Click to expand...
Click to collapse
you do not need to do that. that exploit gives you supercid so you can unlock the bootloader through htcdev. Since you already have supercid, if you're bootloader is not unlocked, unlock it through htcdev.com and then flash recovery, then flash a rom or flash su to get root.
Yeah, what exad said.
Sent from my Evita
timmaaa said:
Yeah, what exad said.
Sent from my Evita
Click to expand...
Click to collapse
Sorry fo slight off topic BUT....
Looks like Timmaaa has got some competition in exad! :silly:
Lol. Exad is a good guy, he's helped a whole bunch of people around here.
Sent from my Evita
And there's no competition ^_^ We're both here for the same reasons! It's more like a teamup!
i everyone, i did a terrible mistake, tried to root without proper knowledge.
i have a htc one XL (international version). details below;
evita pvt ship S-OFF RL
cid- 11111111
hboot-2.15.0000
radio-1.30a.32.45.18
opendsp-v33.1.0.45.1128
emmc-boot
july 16 2013, 19.27.23.12895
Hboot
-----------------
fastboot
recovery
factory reset
clear storage
simlock
image crc
power down
show barcode
i used htcdev to unlock the bootloader and it went smoothly. next i htc one x aio kit by hasoon and tried to flash cwm but it did not work. out of desperration i downloaded r3 endeavor insecurebootandroot and clicked on the install-insecure-windows.bat file. it did something and while restarting under htc logo phone says 'this build is for development purposes only do not distribute outside of htc without written permission. Failure to comply may lead to legal action.'
i tried factory resetting from the boot screen(power button+volume down) but it did not work.
i dont know what to do, im exhausted and desperate. i know its not the XL forum but many say one x and xl can be rooted in the same way.
please someone help, what do i need to do? im a student and i cannot leave this one and buy another.
edit: phone was running on JB 4.2.2
The One XL and One X cannot be rooted in the same way, none of their exploits/firmware/software is compatible with each other. My suggestion is to run an Evita RUU to take it back to stock and start again. Stay within this forum, do not wander anywhere else, you're extremely lucky you haven't bricked your phone.
Sent from my Evita
timmaaa said:
The One XL and One X cannot be rooted in the same way, none of their exploits/firmware/software is compatible with each other. My suggestion is to run an Evita RUU to take it back to stock and start again. Stay within this forum, do not wander anywhere else, you're extremely lucky you haven't bricked your phone.
Sent from my Evita
Click to expand...
Click to collapse
thannk you, thank you. as you already know im a noob, can you please tell me what is evita RUU and where to get it? also how to RUN it?
Ok, Evita is the codename for the One XL, that's why it's displayed at the top of your bootloader. RUU is an acronym and it stands for Rom Update Utility, basically what it does is install a fully stock system on your phone, including ROM, recovery, hboot etc. The RUU will remove any dodgy firmware/software from your phone and replace it with the right ones. Here is the link for Evita RUU's:
http://androidruu.com/?developer=Evita
It's an exe program so all you need to do is connect your phone to your pc in fastboot mode and run the exe file, follow a few prompts on the PC and it's done. Make sure you don't have HTC Sync Manager installed, make sure no other programs are running, and make sure screen saver / hibernation is turned off. Once it's finished you can either stay stock or you can install a custom recovery (I'd suggest TWRP 2.6) and then custom ROMs. Just make sure your stay within this forum from now on and you'll be fine.
PS. Stay away from anything with Endeavoru in the filename, that's for the One X. If you need instructions on how to install TWRP recovery let me know.
Sent from my Evita
timmaaa said:
Ok, Evita is the codename for the One XL, that's why it's displayed at the top of your bootloader. RUU is an acronym and it stands for Rom Update Utility, basically what it does is install a fully stock system on your phone, including ROM, recovery, hboot etc. The RUU will remove any dodgy firmware/software from your phone and replace it with the right ones. Here is the link for Evita RUU's:
http://androidruu.com/?developer=Evita
It's an exe program so all you need to do is connect your phone to your pc in fastboot mode and run the exe file, follow a few prompts on the PC and it's done. Make sure you don't have HTC Sync Manager installed, make sure no other programs are running, and make sure screen saver / hibernation is turned off. Once it's finished you can either stay stock or you can install a custom recovery (I'd suggest TWRP 2.6) and then custom ROMs. Just make sure your stay within this forum from now on and you'll be fine.
PS. Stay away from anything with Endeavoru in the filename, that's for the One X. If you need instructions on how to install TWRP recovery let me know.
Sent from my Evita
Click to expand...
Click to collapse
thank you so much, I feel much better now.
from that list which one you think I should download ?
also in current state, will my phone charge from a wall charger ?
christo_tj said:
thank you so much, I feel much better now.
from that list which one you think I should download ?
Click to expand...
Click to collapse
With S-off, you can run any RUU. You might pick a more recent version (3.1x)
christo_tj said:
also in current state, will my phone charge from a wall charger ?
Click to expand...
Click to collapse
If the screen comes on, it should charge. Plug it in, and if the red or green charge LED comes on, its charging.
redpoint73 said:
If the screen comes on, it should charge. Plug it in, and if the red or green charge LED comes on, its charging.
Click to expand...
Click to collapse
when I plug the wall charger, the red led lights up for a couple of seconds and goes off.
Try a different USB cable?
Sent from my One Xl using xda app-developers app
to use RUU do I need to relock the bootloader?
exad said:
Try a different USB cable?
Sent from my One Xl using xda app-developers app
Click to expand...
Click to collapse
but I used the same charger to charge the phone before I screwed it up.
christo_tj said:
to use RUU do I need to relock the bootloader?
Click to expand...
Click to collapse
You're s-off so you don't need to relock the bootloader.
Sent from my Evita
---------- Post added at 10:04 AM ---------- Previous post was at 10:03 AM ----------
christo_tj said:
but I used the same charger to charge the phone before I screwed it up.
Click to expand...
Click to collapse
Leave it plugged in for a few hours, overnight if possible.
Sent from my Evita
timmaaa said:
You're s-off so you don't need to relock the bootloader.
Sent from my Evita
---------- Post added at 10:04 AM ---------- Previous post was at 10:03 AM ----------
Leave it plugged in for a few hours, overnight if possible.
Sent from my Evita
Click to expand...
Click to collapse
thanks for the tips.
I'll be trying to run RUU today.
things I'm gonna do;
uninstall htc sync.
install necessary drivers for fastboot
put phone in fastboot mode and connect the USB, where it will hopefully say 'fastboot USB'
then run the RUU.
fingers crossed, hop I won't get any errors. I'll update here whatever happens
and I'll be using OTA_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1 (3rd one on that list) is it ok ?.
No problems, and yes that all sounds right to me. Good luck.
Sent from my Evita
timmaaa said:
:
Make sure you don't have HTC Sync Manager installed, make sure no other programs are running, and make sure screen saver / hibernation is turned off.
Click to expand...
Click to collapse
sorry to go a bit off topic but why to NOT have HTC sync manager.
cause i had it installed when i RUUd my device nothing went wrong!?
It can get in the way and disrupt communications between the PC and the phone. While running an RUU it's suggested that no other programs are running at the same time, and while you can exit Sync Manager it has a habit of opening by itself randomly. The last thing you want to happen while running an RUU is any kind of disruption as this can cause a brick.
Sent from my Evita
timmaaa said:
It can get in the way and disrupt communications between the PC and the phone. While running an RUU it's suggested that no other programs are running at the same time, and while you can exit Sync Manager it has a habit of opening by itself randomly. The last thing you want to happen while running an RUU is any kind of disruption as this can cause a brick.
Sent from my Evita
Click to expand...
Click to collapse
what if the power supply fails?
ill go to some cyber cafe with power backup just to be on the safer side.
btw how much time does the RUU take to finish the job ?
I'm gonna do it tomorrow.
A power supply failure would be pretty rare, but yeah if it stops halfway through you'd be in trouble. The process usually takes about 15-20 minutes.
Sent from my Evita
timmaaa said:
A power supply failure would be pretty rare, but yeah if it stops halfway through you'd be in trouble. The process usually takes about 15-20 minutes.
Sent from my Evita
Click to expand...
Click to collapse
and the worst thing happened.
phone isn't switching on anymore. I kept it in my drawer all day and in the night tried to charge. the led blinked twice and turned off as usual. I kept it charging for an hour, then tried turning on by pressing and holding down the power button *nothing*
tried pressing the button for ten mins, nothing happened. tried holding down power key + volume down = same story. tried holding down power key + volume for 2 min = nothing.
I screwed it :'( can't bear the loss :'(
It's probably salvageable via a jtag repair, all is not lost yet. It usually costs about $60 USD.
Sent from my Evita
timmaaa said:
It's probably salvageable via a jtag repair, all is not lost yet. It usually costs about $60 USD.
Sent from my Evita
Click to expand...
Click to collapse
I'll be sending the phone back to the ebay seller. I've opened a claim some days ago as the phone was having some issues(yellow spots on screen, overheating, long charging time).
if all goes well, I'll get a new phone in two weeks.
btw thanks a lot for helping me out, I'll probably need more to root my (hopefully) comin evita