Database Info

[WIP] Rooting the XL - Fastboot freezing? Help!

Situation changed.
Anyhow, I've unlocked my Bootloader but every time I try to flash anything whatsoever, the phone just crashes. Boot, recovery, etc. Looking for some insight from those with more experience.
fastboot devices DOES return my device.
Other commands (getvar) do work
fastboot boot does not work
fastboot flash does not work

these are the commands that work with fastboot...
http://android-dls.com/wiki/index.php?title=Fastboot#Fastboot_Commands

How does it crash? What file(s) are you trying to flash?
If you are willing to flash the AT&T leaked rom, you can just put the su binary in there before flashing.

I know how fastboot works. That being said, I've tried flashing a custom boot.img, stock boot.img, custom recovery, and stock recovery. None of them work. It says "sending file 'boot.img' (****kb)..." or similar, and hangs there until I disconnect the device. The device locks up as soon as a fastboot flash or fastboot boot command is run.
As far as flashing the ATT rom, I'm concerned with it a) working on my device and b) taking away my 3g/4g toggles. Seeing as we have no Rogers RUU yet, it's a legitimate concern.

i don't know mate. wish i could help you. without a device in hand it's harder for me to troubleshoot.

Only thing I can think of is that it's a Rogers ROM issue. I want to flash the ATT RUU, but I have no way to revert if it doesn't work, and that scares the piss out of me, to be blunt. Lol

RMatt1992 said:
Only thing I can think of is that it's a Rogers ROM issue. I want to flash the ATT RUU, but I have no way to revert if it doesn't work, and that scares the piss out of me, to be blunt. Lol
Click to expand...
Click to collapse
If you can live without the toggles for a while (until Rogers RUU), then it wouldn't be so bad. If this is your only device, don't gamble!

Pretty much how it's gonna be. When a Rogers RUU comes out, I'll be all over that like a dirty shirt and maybe I can get this thing rooted, just maybe. Until then, I'm not going to take the chance!

I am gonna wait until this forum gets cooking

You're going to have to wait at least till the 6th of may or a few days after. No one here in canada knows how to root i guess

Which operating system are you running? It's probably something silly that's being overlooked. I've had a ton of issues like that. But right now I'm running Ubuntu and I just have to do "sudo fastboot xxx" and it works just fine.
I was one of the few that accidentally try flashing HTC One X ROMs for the Tegra 3 chip, but I got everything working on my Rogers HTC One XL. I'm not in an LTE enabled area but I'm getting 10+mbps for my download and almost 5mbps for the upload so I don't know if that answers the LTE question or not. At least 3G is working solid as hell though.

Glad to hear you're up and running again ...
bongd said:
Which operating system are you running? It's probably something silly that's being overlooked. I've had a ton of issues like that. But right now I'm running Ubuntu and I just have to do "sudo fastboot xxx" and it works just fine.
I was one of the few that accidentally try flashing HTC One X ROMs for the Tegra 3 chip, but I got everything working on my Rogers HTC One XL. I'm not in an LTE enabled area but I'm getting 10+mbps for my download and almost 5mbps for the upload so I don't know if that answers the LTE question or not. At least 3G is working solid as hell though.
Click to expand...
Click to collapse
Hey, I hadn't come across any of your posts for a few days. I'm happy to hear that you've got your Rogers unit up and running again.
I'm patiently waiting for someone to find a way to root the Rogers unit. I'm sure it will happen soon enough, but waiting isn't my strong point.
Peter

bongd said:
Which operating system are you running? It's probably something silly that's being overlooked. I've had a ton of issues like that. But right now I'm running Ubuntu and I just have to do "sudo fastboot xxx" and it works just fine.
I was one of the few that accidentally try flashing HTC One X ROMs for the Tegra 3 chip, but I got everything working on my Rogers HTC One XL. I'm not in an LTE enabled area but I'm getting 10+mbps for my download and almost 5mbps for the upload so I don't know if that answers the LTE question or not. At least 3G is working solid as hell though.
Click to expand...
Click to collapse
Did you flash the ATT RUU? And, I'm running Ubuntu 12.04 64bit but I run sudo -s. I'll try sudo normally anyhow to see if the outcome changes.
Edit: ^ no difference. Is it possible that my bootloader didn't properly unlock the first time, and that I should relock and unlock it? Just an idea...

RMatt1992 said:
Did you flash the ATT RUU? And, I'm running Ubuntu 12.04 64bit but I run sudo -s. I'll try sudo normally anyhow to see if the outcome changes.
Edit: ^ no difference. Is it possible that my bootloader didn't properly unlock the first time, and that I should relock and unlock it? Just an idea...
Click to expand...
Click to collapse
Strange how it didn't work. I'd try a lock and re-lock just to be on the safe side. I don't understand why it's not working.

anyone simply try renaming the rom.zip from the at&t evita 1.6x ruu to PJ83IMG.zip, stuffing it on the internal storage, and booting to bootloader? I haven't tried it yet, but I bought my phone outright for $704, tax in, and dont want to risk it without a rogers evita ruu in my hands. It wouldnt get you rooted, but it would get you running a test keys build at least with exploitable holes (thats if it'll allow you to downgrade).

JSLEnterprises said:
anyone simply try renaming the rom.zip from the at&t evita 1.6x ruu to PJ83IMG.zip, stuffing it on the internal storage, and booting to bootloader? I haven't tried it yet, but I bought my phone outright for $704, tax in, and dont want to risk it without a rogers evita ruu in my hands. It wouldnt get you rooted, but it would get you running a test keys build at least with exploitable holes (thats if it'll allow you to downgrade).
Click to expand...
Click to collapse
I actually think I saw some devs complaining about HTC's unlocking process for the bootloader. I think with newer devices you can't flash p*img.zips from HBOOT and things of that sort.
Also, they're being real wankers and not releasing the source for their kernels either. I thought their bootloader unlocking was a real win for the community but it looks like they've taken steps backwards in other areas.

bongd said:
I actually think I saw some devs complaining about HTC's unlocking process for the bootloader. I think with newer devices you can't flash p*img.zips from HBOOT and things of that sort.
Also, they're being real wankers and not releasing the source for their kernels either. I thought their bootloader unlocking was a real win for the community but it looks like they've taken steps backwards in other areas.
Click to expand...
Click to collapse
I noticed that as well... also, the file sizes of the new bootloader, and recovery images.... jesus... comparing them to the size of th DHD's (the device I came from) they're almost triple the size. I love how they continue to complicate what doesn't need to be complicated.

At this point the only thing holding me back is knowing I don't have a way to get back to stock if I screw up, and I have no other handset. I'm tempted to try the rom.zip thing, but again, if something goes wrong I'll cry. If bongd (or anyone else) can tell me that they've successfully flashed the ATT RUU onto their Rogers device I will then go ahead and try to get us rooted, however until then, I can't stand to temp-brick my device and be unrecoverable.

I don't know if I read it here or over on Rootz, but someone was saying they went and bricked their Rogers HOX and the ATT RUU actually worked
Sent from my HTC One X using xda premium

SN4K3B1T3 said:
I don't know if I read it here or over on Rootz, but someone was saying they went and bricked their Rogers HOX and the ATT RUU actually worked
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
The only thing that I'm skeptical about (regarding that) would be the inability to 'downgrade' (lower bootloader version in the at&t 1.68 RUU), and different CID's (because of the carriers). That's why i'd love to see some confirmation from those people who semi-bricked their devices when flashing stuff ment for the Endeavour(PJ43).

Please help installing CleanROM 4.5....Stuck in Recovery....

I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!

reflash
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp

thesm4rt1 said:
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
Click to expand...
Click to collapse
I will definitely be trying that. Will be back in a couple of hours and let you know how it went. Thank you!

bbonline said:
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.

Butters619 said:
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Click to expand...
Click to collapse
I did do the factory wipe.
By the way, I tried what I was told to do and nothing happened. It successfully flashes the boot image and recovery, but when it tries to boot into the recovery, it just freezes in the recovery with the word TEAMWIN and a blue background....No menu or options.... I did try several different ways by downloading and installing several versions of the CWM and TWRP, but no success. Any other suggestions? Will I be stuck with this piece of brick now? Please help.

bbonline said:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.

Butters619 said:
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Click to expand...
Click to collapse
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!

bbonline said:
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
Click to expand...
Click to collapse
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!

Butters619 said:
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Click to expand...
Click to collapse
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?

bbonline said:
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
Click to expand...
Click to collapse
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
Darn.... I just hope I don't have to deal with sending it for any repair. Gave you thanks!

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
But only if they reboot and look, which from what I've seen here, they never seem to do.

iElvis said:
But only if they reboot and look, which from what I've seen here, they never seem to do.
Click to expand...
Click to collapse
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
Butters619 said:
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Click to expand...
Click to collapse
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on

trichrome1 said:
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
Click to expand...
Click to collapse
Nope once you unlocked it won't ever say locked again. Just re-locked

gunnyman said:
Nope once you unlocked it won't ever say locked again. Just re-locked
Click to expand...
Click to collapse
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.

trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
You should probably double check that. Anybody with an AT&T One X had to have SuperCID to unlock their bootloader so that wouldn't matter. I have unlocked two AT&T One Xs and run the 1.85 RUU on both (one of them a couple times) and I have run the 2.20 RUU on one. every time it says RELOCKED.

Mine did this to when going to 4.5.
I did the following to get back into Recovery.
Use fastboot to flash the boot.img from the cleanrom 4.5 zip.
"fastboot flash boot boot.img"
I then flashed the recovery (TWRP 2.2.1.4 at the moment) again to the phone.
next I erased Cache.
"fastboot erase cache"
I then used the phone itself to reboot the bootloader and went into recovery. It took about 10 minutes but recovery finally booted.
At this point I had no access to anything on the SD card. so I selected mount and mounted the sd card as disk drive to access it through my PC. I was forced to format the drive at this point and loaded a fresh copy of the ROM onto the drive for flashing.

You probably just got a wrong recovery. The recovery on twrp website didn't work for me. The one I downloaded from the development section works fine.
Sent from my One X using xda app-developers app

trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
Screenshots PLS

[Q] trouble flashing PG59IMG.zip

I've been running CM9 for a few weeks now, but have decided that I want to get S-Off and open the phone's capability up some more... Anyway, I'm on a MT4GS:
HBOOT 1.45.0013
Nov 21 2011 build
Tried flashing this https://www.cx.com/mycx/share/O2W61....00_11.16.3504.20_2_release_245247_signed.zip
from weekendsr2short's mirror page (http://forum.xda-developers.com/showthread.php?t=1878329) of Blue6ix's stuff...(i tried autoflashing from the bootload/fastboot screen)
anyway, it loads up like it is going to actaully flash, but nothing changes on the Bootloader screen. The phone is unlocked via HTC's tool and is rooted. Any help is greatly appreciated! Please lemme know if any more info is needed.
Josh

more to it than flashing an hboot
read up on THIS

SurfRodder said:
I've been running CM9 for a few weeks now, but have decided that I want to get S-Off and open the phone's capability up some more... Anyway, I'm on a MT4GS:
HBOOT 1.45.0013
Nov 21 2011 build
Tried flashing this https://www.cx.com/mycx/share/O2W61....00_11.16.3504.20_2_release_245247_signed.zip
from weekendsr2short's mirror page (http://forum.xda-developers.com/showthread.php?t=1878329) of Blue6ix's stuff...(i tried autoflashing from the bootload/fastboot screen)
anyway, it loads up like it is going to actaully flash, but nothing changes on the Bootloader screen. The phone is unlocked via HTC's tool and is rooted. Any help is greatly appreciated! Please lemme know if any more info is needed.
Josh
Click to expand...
Click to collapse
If you're rooted, install a stock-based ROM and then use juopunutbear.

blackknightavalon said:
If you're rooted, install a stock-based ROM and then use juopunutbear.
Click to expand...
Click to collapse
OK, that's what I was hoping to do. I noticed in the JB instructions that it said I must be a stock RUU not a custom ROM or something to that effect. I am on CWM 5.Something so a rom flash is NP. Any recommended ROMs? I.e One that worked for you? I tried the wire trick about 100 times over the course of an hour or so(on cm9.1), but then reread the bit shout the rom again.
Thanks for all the responses so far!

Any stock based ROM will do. I went with MikTouch myself and it worked like a charm! (on the 4th try so be patient....)

demkantor said:
more to it than flashing an hboot
read up on THIS
Click to expand...
Click to collapse
Thanks, after reading that thread <again> it linked me the this http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
Which I have Also already read,but noticed this time that I cannot be unlocked via HTC and still flash pg59imgs... so im off to relock, if the stock rom method doesn't work...

WeekendsR2Short said:
Any stock based ROM will do. I went with MikTouch myself and it worked like a charm! (on the 4th try so be patient....)
Click to expand...
Click to collapse
Awesome, thanks brotha

well, one down, one to go. I have my phone all dialed in...now its time to fix my wife's... Thanks again Gents! (& Ladies, as applicable!)
edit: well, hers is done now... I ended up using another SD card, the original one I tried was kinda old, but the newer one I normally use worked on the 2nd try... didnt lose any data either... her sd card on the other hand was toasted and needed to be reformated... anyway, both phones are now S-Off!!

SurfRodder said:
well, one down, one to go. I have my phone all dialed in...now its time to fix my wife's... Thanks again Gents! (& Ladies, as applicable!)
edit: well, hers is done now... I ended up using another SD card, the original one I tried was kinda old, but the newer one I normally use worked on the 2nd try... didnt lose any data either... her sd card on the other hand was toasted and needed to be reformated... anyway, both phones are now S-Off!!
Click to expand...
Click to collapse
Man, that's GREAT! Once you knew HOW, the process was nothing for you. That's a far cry from most. Way to go!

WeekendsR2Short said:
Man, that's GREAT! Once you knew HOW, the process was nothing for you. That's a far cry from most. Way to go!
Click to expand...
Click to collapse
yeah, Ive been running root since my MT3G way back when...couldnt stand how laggy that thing was with all the bloat... wasnt even that great with CM6 but still night and day better than stock (=hooked on rooting). then upgraded to the MT4g and now this thing... was fairly concerned about all the extra hoops but wouldve just chosen another platform had I borked it...glad I didnt, saved me some funds!
On a related note, what radios are you guys running? Are there any issues between the GB radios and ICS ones? Im assuming so, but with the custom ROMs/kernels anything should be able to be overcome I'm hoping... I know I def. had issues on CM7 -> CM9 on the reg. 4G when swapping radios...

I don't generally swap my radios around since there are only two that I'm aware of. But I DID find that the new one (when I replaced my phone) seemed to lock a signal a bit quicker but for me the original radio gets MUCH better phone reception. Depends on your phone I suppose.
(you'll be glad you went with this phone though. basically a Sensation with a keyboard)

WeekendsR2Short said:
I don't generally swap my radios around since there are only two that I'm aware of. But I DID find that the new one (when I replaced my phone) seemed to lock a signal a bit quicker but for me the original radio gets MUCH better phone reception. Depends on your phone I suppose.
(you'll be glad you went with this phone though. basically a Sensation with a keyboard)
Click to expand...
Click to collapse
cool, I just flashed the older one today... been having really crappy recption on campus lately (esp. since switching from the MT4G) better reception is what I'd rather have... ill give this one a week or so and see if I think its any better... I like the phone a lot already... i still use the soft keyboard from time to time as I forget the other one is there, but it comes in really handy on certain sites...

Hello guys, I've been lurking the forums for hours trying to find a thread with an issue close to mine, and this is the closest I got. I followed all the necessary steps on the first page, but the problem I'm having is when I try to flash the PG59IMG.zip file, it says "Loading... PG59IMG.zip", but then it says "Checking....PG59IMG.zip" and afterwards it says "Wrong zipped image!" Any ideas what it could mean? I just want to get it back to stock. Any help is greatly appreciated.

THIS MAY HELP YOU

Thanks for the link. It said I need to relock the phone in order to flash the image, but when i type "fastboot oem lock" into command prompt, I get a message saying 'fastboot' is not recognized as an internal or external command, inoperable program or batch file." I'm guessing this means my fastboot wasn't set up correctly, but I don't know where to go from here. As always, thanks again for any help or advice.

The third post in this thread
http://forum.xda-developers.com/showthread.php?p=27796375
It was made for the g2 so don't use the drivers in it, but it will at least give you an idea of what to do
Sent from my HTC Vision using xda premium

Hanenbow said:
Thanks for the link. It said I need to relock the phone in order to flash the image, but when i type "fastboot oem lock" into command prompt, I get a message saying 'fastboot' is not recognized as an internal or external command, inoperable program or batch file." I'm guessing this means my fastboot wasn't set up correctly, but I don't know where to go from here. As always, thanks again for any help or advice.
Click to expand...
Click to collapse
Does fastboot work like this
./fastboot oem lock
On my PC some of my fastboot commands need that.
Sent from my Freaked out JellyBean

Thanks so much for your help guys. I followed the instructions on the pathing link, and the phone is currently flashing the image. I'll post a final time once I can confirm everything is fine.

[Q] Is there a way to completely wipe HTC One XL?

Ok... so, I'll admit it, I messed up my One X. Was trying to put CM10 on it, got stuck on the blue, circular boot screen. Tried several fixes from the forums, but nothing worked. One attempted fix even ended up writing over TWRP. Now all I can get is HTC boot screen (complete with red wording beneath) and occasionally the CM10 screen. The fastboot screen says "tampered" and "unlocked".
Here's my situation. AT&T is sending another phone. I have to send this one back to them, and I just want to make sure that they can't figure out I was trying to install a third-party ROM. Is there a way to completely wipe the device altogether so that I just won't even try to boot?
If not, I'll just take my chances that they don't know what to look for besides water/physical damage and won't charge me full price for the replacement.
Any help is appreciated.

Your device is in a completely fixable state but ok...if u want to make it so your device doesn't turn on at all flash a Rom called ice cold jelly ...if youother wise the best you can do is have it say relocked and they would know you unlocked the bootloader...

don't flash ICJ, just relock bootloader and ruu.
if you have no physical damage why are you getting a replacement phone?

Did you flash boot.img?
And how about you not ask how to defraud att because you don't know how to flash and fix a botched flash.

schumachermp said:
Ok... so, I'll admit it, I messed up my One X. Was trying to put CM10 on it, got stuck on the blue, circular boot screen. Tried several fixes from the forums, but nothing worked. One attempted fix even ended up writing over TWRP. Now all I can get is HTC boot screen (complete with red wording beneath) and occasionally the CM10 screen. The fastboot screen says "tampered" and "unlocked".
Here's my situation. AT&T is sending another phone. I have to send this one back to them, and I just want to make sure that they can't figure out I was trying to install a third-party ROM. Is there a way to completely wipe the device altogether so that I just won't even try to boot?
If not, I'll just take my chances that they don't know what to look for besides water/physical damage and won't charge me full price for the replacement.
Any help is appreciated.
Click to expand...
Click to collapse
... and this is why we can't have nice things. Thanks, guy.

All I can think is, at least he did not throw it under his car.
It can be salvaged, where as other clown just destroyed it for nothing.
WR
Sent by WR's One XL

omario8484 said:
Your device is in a completely fixable state but ok...if u want to make it so your device doesn't turn on at all flash a Rom called ice cold jelly ...if youother wise the best you can do is have it say relocked and they would know you unlocked the bootloader...
Click to expand...
Click to collapse
Brother, if you can tell me how to fix this thing, I am all ears. I don't want to replace it, but after trying so many different ways to fix it from the forums I just kind of gave up.
If you have any advice, I'd love to hear it!
Thanks for the reply.

schumachermp said:
Brother, if you can tell me how to fix this thing, I am all ears. I don't want to replace it, but after trying so many different ways to fix it from the forums I just kind of gave up.
If you have any advice, I'd love to hear it!
Thanks for the reply.
Click to expand...
Click to collapse
All you had to do is fastboot the boot.img thats inside the zip bro.. Are you familiar with fastboot at all? If not we can walk you through it!
Sent from my One X using Tapatalk 2

InflatedTitan said:
All you had to do is fastboot the boot.img thats inside the zip bro.. Are you familiar with fastboot at all? If not we can walk you through it!
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I did flash boot.img. It just never moved past the CM10 starting animation. And honestly, not super familiar with fastboot three days ago... fairly familiar at this point. But nothing seems to get this thing to work. Please tell me what to do!
(BTW - I only called warranty at the advice of an AT&T employee in the store. I'd love to just fix my phone)

Twrp 2.3.1.0, wipe everything, flash boot.img in fastboot, and flash cm10 and gapps in twrp.

How do I get TWRP back on it?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

schumachermp said:
How do I get TWRP back on it?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Try Goo Manager, go into its settings an select install open recovery script.
WR
Sent by WR's One XL

WarRaven said:
Try Goo Manager, go into its settings an select install open recovery script.
WR
Sent by WR's One XL
Click to expand...
Click to collapse
Ok, great. I've downloaded the TWRP recovery image and the Goo Manager APK... now how do I use Goo Manager on a device that won't boot up?

You can't BC its an app.. Download tarp off the official site, a quick Google search brings it up first shot... Once downloaded, drop the recovery img into your adb and fastboot folder.. Enter fastboot USB on your phone. Now right click on your adb/fastboot folder and choose "open command prompt here"
Once cmd is running, type fastboot flash recovery <---- type in the name of the twrp img you dropped in
Sent from my One X using Tapatalk 2

InflatedTitan said:
You can't BC its an app.. Download tarp off the official site, a quick Google search brings it up first shot... Once downloaded, drop the recovery img into your adb and fastboot folder.. Enter fastboot USB on your phone. Now right click on your adb/fastboot folder and choose "open command prompt here"
Once cmd is running, type fastboot flash recovery <---- type in the name of the twrp img you dropped in
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Woohoo!!! You guys got it going! Running CM10 FTW!
I hope you all don't mind me saying that I FREAKING LOVE YOU ALL. It's true.
Thank you SO much!
Deuces. I'm going to go play with JB.

schumachermp said:
Woohoo!!! You guys got it going! Running CM10 FTW!
I hope you all don't mind me saying that I FREAKING LOVE YOU ALL. It's true.
Thank you SO much!
Deuces. I'm going to go play with JB.
Click to expand...
Click to collapse
I'm happy you got your phone running.

Don't get it all sticky with all that love.

Lol good job bro
Sent from my One X using Tapatalk 2

ECEXCURSION said:
... and this is why we can't have nice things. Thanks, guy.
Click to expand...
Click to collapse
Exactly right! If you screw up your phone, take responsibility for it! Don't make somebody else pay for your failure.
Do you even read before you flash rom's? clear red letters. This could brick your phone or even worst if you dont know what you're doing
Research very much before doing anything, that's how I started

rodpgfx said:
Exactly right! If you screw up your phone, take responsibility for it! Don't make somebody else pay for your failure.
Do you even read before you flash rom's? clear red letters. This could brick your phone or even worst if you dont know what you're doing
Research very much before doing anything, that's how I started
Click to expand...
Click to collapse
Completely agreed. The notion astounds me (and disappoints me also) that the OP was going to send the phone in for a warranty replacement simply because they didn't do the proper research and learning before modding the phone. And when the condition was completely and easily reversible. If the screen comes on with this phone, it can be recovered.

[Q] AT&T HTC One X Soft Brick. Tried everything I could find. Suggestions?

So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!

roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.

roycedavies said:
So my AT&T HTC One X is bootloader unlocked, super CID and was rooted. I installed a copy of Viper XL 4.2.0 that had issues with the radio turning off so I thought I'd try Maximus HD. I flashed the boot.img and went to install the rom only to find that the rom was for the international version of the HTC One X only (this was conveniently overlooked in the thread). I backed out of installation, went to restore with my TWRP backup and it had been deleted. I reinstalled the Viper XL rom and my phone booted up to the HTC developers screen (red text) and went black. This now happens every time I try to boot the phone up.
I have access to fastboot and clockwork recovery. I can't get ADB to work as I don't have access to enable USB debugging. I have flashed a few roms since with their respective boot.img to no avail. The phone still just boots to the HTC screen and blacks out.
I don't have S-off and, from my research, I can't get it without ADB so I can't RUU and return to stock without bricking (apparently). I've been at this for about a month and this soft brick is starting to look a whole lot like a hard brick.
Any suggestions, or am I out of business?
Thanks in advance!
Click to expand...
Click to collapse
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Sent from my Evita

timmaaa said:
You said you flashed the boot.img from Maximus before flashing the ROM (which is ok, the previous member is incorrect in saying that it must be afterwards, it can be either), but did you flash the boot.img from the Viper XL ROM when you flashed that? If not your phone is trying to boot Viper while the Maximus boot.img is still installed, obviously this won't work.
One thing. The fact that Maximus ROM is only for the Endeavoru wasn't "conveniently overlooked" as you sarcastically put it. You were in the wrong forum. The ROM itself is in the Endeavoru forum and you have the Evita so you shouldn't be in the Endeavoru forum in the first place. The ROM is in the correct forum, it doesn't need to be labelled "Endeavoru only" because the user should be aware of which device they have and be aware of which forum they are in. The fact that you're bouncing around both forums is a bit of a worry. You have no reason to be in that forum.
Our forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Our two development sections are here:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Stay within our device forum, you don't ever need to be anywhere else. You're pretty lucky you haven't actually bricked your phone by flashing that ROM. By the way, there's no such thing as a soft brick. A brick is when your phone will not power on at all. It's either bricked or it isn't.
Click to expand...
Click to collapse
Thanks for the reply. I believe the reason I'm not bricked is because I backed out of the installation of Maximus HD during the setup screen progression. The actual ROM was never flashed. However, I have flashed the boot.img and ROMs for Viper, Xylon, and Cyanogenmod with no success. The result is the same every time (HTC screen, then black). I extract the boot.img from each of the roms, flash it, and then flash the ROM. The ROM I flash is a copy of the the original with the boot.img still inside. Perhaps I should be removing the boot.img if I am going to flash it separately in fastboot? And I realize that the threads are specific for certain phones now. It's all kind of a mess to get into at first.

I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita

Madcat8686 said:
Not sure if I can help you much but I did notice an important clue by what you said. It looks like you flashed the boot.img before flashing the Rom. This is backwards. You are supposed to flash the Rom first and then the boot.img. If you are not S-Off this will indeed cause problems. If you are still able and have the files on the phone, try flashing in that order and see if that clears it up. Oh and P.S. I'm sure you already are kicking yourself but yes, stick to Roms made for our phone in this forum.
Just noticed something else:
you said you had access to fastboot? Connect the phone and open a CMD prompt, navigate to your ADB/Fastboot folder (Where ever you keep your adb/fastboot tools) and then type "fastboot devices" to see if your computer is talking to your phone. If it is, you said you can flash Viper. you will just need to unzip the Viper zip and get the boot.img. Put that file in your ADB/Fastboot folder. open a CMD prompt again and navigate once again to you ADB/Fastboot folder, then type "fastboot flash boot boot.img and that should get you back on the road.
This is assuming you have a folder with the required ADB/Fastboot resources (if you don't I recommend you learn how) and knowledge on how to navigate to that folder with DOS commands.
Click to expand...
Click to collapse
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.

Oh, that's great. Usually it shouldn't matter which order you flash in, but at least it got you out of trouble this time.
Sent from my Evita

roycedavies said:
Dude, you are a golden-freaking genius. Your suggestion to flash the boot.img second did the trick! I'm currently running Uxylon! Hopefully things continue to work. Thank you, thank you, thank you.
Click to expand...
Click to collapse
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!

Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
Hey, you should take the credit, I believe flashing it afterwards was what got his phone booted :thumbup:
Sent from my Evita

Madcat8686 said:
Actually I can't take credit for this. Timmaaa pointed out something I didn't know. You can flash them in either order (mind blown!) I've only see it one way. I learn a ton every day. @timmaaa pointed out you had the Maximus boot.img loaded. I think you just flashed over it and now you have the correct boot.img for the Rom you are running. Glad everything worked out for you and I learned something in the process too. Cheers!
Click to expand...
Click to collapse
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?

timmaaa said:
I understanding that it can be a bit confusing at first, especially with the phones betting similarly named. But you know now so you shouldn't have this problem again. I believe you will probably need to run an RUU to get out of this mess, but I'll need to see your bootloader details first, just the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply! I will get the bootloader info ASAP bit don't I need to be s-of in order to RUU? from what I've read, if you don't have unlocked bootloader, root access, and s-off, you'll end up bricking your phone with RUU. I'd really like to do it but I have tried to get s-off to no avail.

No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita

roycedavies said:
thanks again for your help and this might be a total shot in the dark but I am still having the boot to black issue after installing uxylon. the room is running well enough (4g won't turn on but one problem at a time) but every time I turn the phone off or rent I have to get into fastboot and flash the boot.img to get the phone on again. is that normal? the only other ROM I have ever had working is viper but I haven't seen any indication that having to use fastboot to turn the phone on every time is normal. is there a way to fix this possibly?
Click to expand...
Click to collapse
Definitely not normal. A few recommendations:
1. Back up all your stuff, wipe everything except the SD card, Flash a fresh copy of the Rom, Flash the boot.img (you really should consider S-Off), Wipe the cache and DALVIK cache one more time, boot up the system.
2. Same as above except choose another Rom. There are plenty to choose from. The 4.4 Roms are getting a lot better now that the new Kernel fix got rid of the boot loops/reboots.
Sorry about the delay, it's been a heavy week at work. Hope things work out for you.

I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app

timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
Sometimes is pays to see if there is a page 2 to the thread...Sorry about that! lol
---------- Post added at 08:48 PM ---------- Previous post was at 08:45 PM ----------
timmaaa said:
I don't think flashing another ROM is going to fix the problem at hand. There's very possibly something much deeper wrong here, which a ROM flash won't fix. I honestly think it's better to run an RUU which will bring everything back to the way it's meant to be and the user can start with a blank slate.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have no idea how much I have vicariously learned from your posts. Thanks Timmaa! I keep thinking if more of these folks would go ahead and get S-Off they would have waaaaaaaaaay less issues.

Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app

timmaaa said:
Flashing another ROM could be worth a try, but the fact that the boot.img seems to be disappearing whenever the screen is off suggest something has gone wrong at a lower level.
I'm glad to help, I'm still learning something new just about every day too from XDA.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I totally agree now because after rereading the post, there is a radio issue in addition to the boot issue. Is it possible that the Endeverou boot.img messed something up?

Yeah, that's exactly what I'm thinking. An RUU will hopefully fix that right up.
Sent from my Evita.

timmaaa said:
No, that isn't normal at all, there's definitely something screwy there. I think you're gonna need to run an RUU, so you'll need to get s-off. Try this:
Http://Rumrunner.us
Sent from my Evita
Click to expand...
Click to collapse
That sounds like a good plan. (I'm really appreciating all your input by the way! Thanks so much!) One question though, upon checking out the rumrunner website, there isn't specific mention of the HTC One X Evita. Call me paranoid, but after what I've been through I want to make 100% sure I'm compatible before moving forward. Have you or anyone used this specific method for S-Off on the One X Evita?

For the Evita you use the universal HTC method. I've created a thread for it if you want to make sure it's worked for other Evita owners.
http://forum.xda-developers.com/showthread.php?t=2540232
Sent from my Evita.