I am creating this post as a tip and warning to everyone with an at&t htc one x (mostly noobs for help). If you have rom manager on your phone do not use it to flash the new recovery listed for the htc one x (gsm). I've been messing with android since 2009, but me seeing a new recovery for the one x with (gsm) next to it thought hey finally got an official clockwork recovery for our phones!!!!! Well i was wrong. Its for the international versions only not ours. The partition it writes the recovery to is on our bootloader partition, and flashing it will kill your phone. I flashed it, kept it on for hours but as soon as i rebooted the phone it turned off and would not turn on or charge. You'll pretty much be screwed and have to get a new phone unless you know how to run linux and ask for help fixing it which is harder than you think. Again do not flash the htc one x (gsm) recovery in rom manager!!!!!
Hope this helps some of you before hand and not after.
If this post isn't necessary i am sorry and please close it.
Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.
Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium
nooomoto said:
Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.
rob219 said:
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.
Click to expand...
Click to collapse
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only
sugeraddict said:
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only
Click to expand...
Click to collapse
The ruu has to access the boot loader to verify your version. If you end up flashing a device and it writes certain partitions of your boot loader (ICJ).... Well your left with a permabrick, until someone finds a way to JTAG the One X(AT&T). I've heard that its already been done, but the person who has performed it has kept the pinout secret.
I'm not entirely sure which partitions your ROM manager has wrote to, if you can find that out you might be able to fix it... Depending on which ones have been written too.
Sent from my One X using xda app-developers app
Zombie thread alert!
Like many of us have said before. We are not the one x. We are the one XL.
Sent from my One X using xda app-developers app
_MetalHead_ said:
Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.
Click to expand...
Click to collapse
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike
MaverickCoast said:
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike
Click to expand...
Click to collapse
You must be doing something wrong then. You don't even need to locate backups with TWRP, they're found automatically. Anyway, was it really necessary to revive an 18 month old thread just to say that?
Sent from my Evita
Related
I went to flash some things...and now it's stuck in the qualcomm download mode? How the hell do I get out of it??
You can't, you're screwed
I had this on my old Sensation, it stands for Qualcomm High Speed USB
Basically what's happened is your phone has lost the drivers for the chip set and needs them re-installed, as far as I'm aware, no-one has managed to find a way to do it.
Hope its still under warranty mate, I think its the only way you'll get it sorted
Sent from my GT-I9100 using xda premium
redrumsilence said:
You can't, you're screwed
I had this on my old Sensation, it stands for Qualcomm High Speed USB
Basically what's happened is your phone has lost the drivers for the chip set and needs them re-installed, as far as I'm aware, no-one has managed to find a way to do it.
Hope its still under warranty mate, I think its the only way you'll get it sorted
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
You're kidding, right? Well I installed the drivers for that, and it's now recognized by my computer, but there's nothing I can do? At all?
What exactly did you do to cause this?
Sent from my HTC One X using Tapatalk 2
random1204 said:
You're kidding, right? Well I installed the drivers for that, and it's now recognized by my computer, but there's nothing I can do? At all?
Click to expand...
Click to collapse
When it happened to me, I found the QHSUSB drivers and installed them, my computer recognised my Sensation, but nothing else.
I scoured XDA, Google, all sorts, I couldn't find anything, I just sent mine in under insurance and got a new one
Sent from my GT-I9100 using xda premium
Your not screwed. Pmed
Sent from my HTC One X using xda premium
Galaxy s3 Tmobile in same state
18th.abn said:
Your not screwed. Pmed
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Hey do you have any info on this mode? I would love to have some kind of info as to a course of action, even though this is for a different model...
18th.abn said:
Your not screwed. Pmed
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
i to am stuck in this mode. i flashed clockwork recovery (gsm) on my at&t one x thinking it was for our phone since it wasnt there the last time i checked. after i did a reboot the phone never came back on.
rob219 said:
i to am stuck in this mode. i flashed clockwork recovery (gsm) on my at&t one x thinking it was for our phone since it wasnt there the last time i checked. after i did a reboot the phone never came back on.
Click to expand...
Click to collapse
Is it completely dead and unresponsive? Just flashing the wrong recovery shouldn't kill your phone. I've done it myself a couple of times by accident, and fixing it was just a matter of flashing the right one.
Sounds like you actually flashed the wrong rom. Doing that can kill your bootloader, which will put you in QHSUSB mode. There is a way out that's been discussed, but I can't find it at the moment. It involves pushing a new hboot onto your phone and I believe requires Linux.
iElvis said:
Is it completely dead and unresponsive? Just flashing the wrong recovery shouldn't kill your phone. I've done it myself a couple of times by accident, and fixing it was just a matter of flashing the right one.
Sounds like you actually flashed the wrong rom. Doing that can kill your bootloader, which will put you in QHSUSB mode. There is a way out that's been discussed, but I can't find it at the moment. It involves pushing a new hboot onto your phone and I believe requires Linux.
Click to expand...
Click to collapse
it wasnt a rom. it was definetly the clockwork recovery in rom manager. it said gsm next to htc one x and its a new one so i was stupid enough to flash it. i did a reboot and it was dead. i already talk to at&t about it and there sending me a new one.
rob219 said:
it wasnt a rom. it was definetly the clockwork recovery in rom manager. it said gsm next to htc one x and its a new one so i was stupid enough to flash it. i did a reboot and it was dead. i already talk to at&t about it and there sending me a new one.
Click to expand...
Click to collapse
That's interesting, because I did (almost) the same thing. When I first unlocked my HOX, I installed ROM Manager and accidentally flashed the Samsung GSII recovery. I was able to fix it just by going back to bootloader and adb flashing the correct version.
iElvis said:
That's interesting, because I did (almost) the same thing. When I first unlocked my HOX, I installed ROM Manager and accidentally flashed the Samsung GSII recovery. I was able to fix it just by going back to bootloader and adb flashing the correct version.
Click to expand...
Click to collapse
just found out the one x international recovery flashes on the partition that on our phones is the boot loader partition. could be fixed inside of linux, but i didnt get into how.
I had the same problem with the QHSUSB Download it turns out my phone had a really drained battery so how I managed to fix it was had it plugged into my computer and let the lights flash until i got a solid amber light. after about 15 minutes, I turned it on and it worked fine!
on my tablet i pressed for a really long time the power button and then it started up
it enters almos allways in qualcomm download mode when the battery is depleated.
you revived a dead thread to say something about your tablet?
I'm going to go revive some too now
Sent from my HTC One XL using Tapatalk 2
DvineLord said:
you revived a dead thread to say something about your tablet?
Click to expand...
Click to collapse
Someone can find my reply useful, compared to you and the other troll that did not say anything useful.
Same situation for me .. i flashed TWRP, backedup my rom, flashed a new rom and reboot. black screen, no light, unresponsive .. this same message shows up on my windows machine "QHUSB_LOAD no driver found"
atombone said:
Same situation for me .. i flashed TWRP, backedup my rom, flashed a new rom and reboot. black screen, no light, unresponsive .. this same message shows up on my windows machine "QHUSB_LOAD no driver found"
Click to expand...
Click to collapse
I'm guessing you flashed an international ROM on your One XL. That will do it.
iElvis said:
I'm guessing you flashed an international ROM on your One XL. That will do it.
Click to expand...
Click to collapse
Its a One X (ATT) but your probably right. I downloaded it from ONEXROOT.com. just strange to me that because i flashed a rom it screws the bootloader. ugh... sucks
I can get it to get into recovery mode, but it wont go any further than the red lettered warning banner. I tried to flash the ROM from the clockwork mod app from the market. No luck. My phone is not in the list of phones in the "Flash clockwork mod recovery". I tried to flash the 5.8.4.0 endeavoru.img file to my phone, but in my command prompt on my computer, it doesn't recognize my command as a batch command or anything. Any help folks? I was trying to find a stick on rooting, unlocking bootloader, and then flasing roms, but to my surprise I didn't find them all in one. I don't know what I'm doing wrong at this point. Spent a few hours last night, and now it all seems like a blur. Help please!
CP24EVA said:
I can get it to get into recovery mode, but it wont go any further than the red lettered warning banner. I tried to flash the ROM from the clockwork mod app from the market. No luck. My phone is not in the list of phones in the "Flash clockwork mod recovery". I tried to flash the 5.8.4.0 endeavoru.img file to my phone, but in my command prompt on my computer, it doesn't recognize my command as a batch command or anything. Any help folks? I was trying to find a stick on rooting, unlocking bootloader, and then flasing roms, but to my surprise I didn't find them all in one. I don't know what I'm doing wrong at this point. Spent a few hours last night, and now it all seems like a blur. Help please!
Click to expand...
Click to collapse
Do some research first because seems like u don't have even a custom recovery or even roooted... Now also never install anything that says endeavour or you will **** up your phone enough said...now do u have att one x or rogers telstra
WOAH, STOP RIGHT THERE.
endeavoru.img IS THE WRONG IMAGE!!!! I can smell a brick!!! the endeavoru image is for the quad core tegra one x. I am assuming you have a OneXL or one of the other Qualcomm DUAL CORE One X's
Our phone is called EVITA.
If you have a non ATT one x like a Telstra One XL or rodgers go to htcdev website.
If you have a ATT version I have recently found out that some versions cannot be rooted, and root is needed to unlock the bootloader. If it has ATT logo on the top where HTC should be, then you need to know the version number of your current rom before putting in any more effort to unlock. Check settings>about phone>
Check the forum in the One X Android Development/[INDEX] AT&T/ROGERS One X Resources Compilation Roll-Up (Updated 10/2/12) for the versions that can be rooted/unlocked.
Hope this helps
-Liam
mine is the ATT version......
My phone isn't bricked yet...phew. SO....going to get the EVITA then. right? for ATT version?
First thing is first you need to know the version of the stock rom you have, go to settings/about phone, I believe that if your version is greater than 1.85 then you are pretty screwed. You can only wait until A) ATT allow unlocking B) someone finds an exploit. If your One X is brand new, I doubt it is 1.85 as this is an old version.
llambkin said:
First thing is first you need to know the version of the stock rom you have, go to settings/about phone, I believe that if your version is greater than 1.85 then you are pretty screwed. You can only wait until A) ATT allow unlocking B) someone finds an exploit. If your One X is brand new, I doubt it is 1.85 as this is an old version.
Click to expand...
Click to collapse
Many phones are still being sent out with 1.85/1.73:angel: and to op DONT use clock word mod oonce you root and unlock bootloader I will show u which recovery to flash
WOW, Thats good. Ours are shipped with the latest, well at least my sisters one was. I thought she would have been screwed, But I was able to unlock with HTCDEV
@omario8484, is there a reason for not using CWM? I have it on my OneXL. I got the touch version, TWRP is good I guess, but I am more familiar with the CWM interface.
-Liam
omario8484 said:
Many phones are still being sent out with 1.85/1.73:angel: and to op DONT use clock word mod oonce you root and unlock bootloader I will show u which recovery to flash
Click to expand...
Click to collapse
I'm simply looking for a link to the evita version. I keep seeing the other one .
Sent from my HTC One X using Tapatalk 2
Also mine was 1.82. Found it on craigslist.
Sent from my HTC One X using Tapatalk 2
AWESOME!!!
Try This http://forum.xda-developers.com/showthread.php?t=1777773
:good:
CP24EVA said:
Also mine was 1.82. Found it on craigslist.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
That's because clock work doesn't support out phone officially !!!!!!!!!!!!!
ChummyDays said:
If you flash some roms with cwm, they sometimes will have serious problems. Twrp works with very Rom perfectly fine.
Click to expand...
Click to collapse
OK, I might flash back to TWRP then, I have always used CWM....I did like the skinnable interface of TWRP tho :
llambkin said:
OK, I might flash back to TWRP then, I have always used CWM....I did like the skinnable interface of TWRP tho :
Click to expand...
Click to collapse
Yes use twrp because USB mount works also some Tom's like he said will have problems
Ok, I got it all sorted. Out. My main problem is I didn't know what the goo interface let me do. Once I found out then it was cake from there. I'm loving this AOKP one so far.
I there a way to get to the play store that doesn't include using an internet browser?
CP24EVA said:
I there a way to get to the play store that doesn't include using an internet browser?
Click to expand...
Click to collapse
Maybe the play store app?
I don't see a play store app in the app tray at all. and when I press the PLAY STORE option in the menu tray, it does nothing.
Hey guys my s3 killed its self yesterday so I grabbed one of these beauties today and I'm really impressed so far(maybe its the custom ROM).
Now I got the phone off a guy, had it he unlocked the bootloader,rooted,and gave me the phone already running 4.1(dirty 1.8).no back ups to even a rooted stock.
Although I love jelly bean this battery is killing me and I would really like to have at least a stock zip I can flash in emergencies.
I am so unfamiliar with HTC(nexus one was the last one I owned)thank I really don't want to brick it.
OK so my questions are these
I have the rogers version of the Onex is there certain builds I need to look for or are they all just HTC one x?
With HTC is there a fallback like with samsung if things go wrong at least there's always download mode and Odin.
Do I need to have my boot loader unlocked?
Thanks in advance
And sorry for the noobness I just can't kill 2 phones in a week
Sent from my One X using xda app-developers app
You have a lot of reading ahead of you, grasshopper, before you're ready to do anything to your phone:
http://forum.xda-developers.com/showthread.php?t=1671237
To answer your questions:
todorcim said:
I have the rogers version of the Onex is there certain builds I need to look for or are they all just HTC one x
Click to expand...
Click to collapse
No! It is wise of you to ask this, because there are two versions of the One X, the International (Tegra 3 quad-core) and the US/Rogers/Telstra (dual-core S4). Flashing stuff for the wrong version can permanently brick your phone (i.e., there is no current fix for some of these mistakes).
With HTC is there a fallback like with samsung if things go wrong at least there's always download mode and Odin.
Click to expand...
Click to collapse
Assuming you haven't flashed the wrong ROM, you can generally always get out of trouble by booting into bootloader, relocking, and running the RUU for your firmware. Most problems can be fixed by going back into recovery and re-flashing or flashing something else.
Note: Figure out what version of hboot you have before doing anything. With 1.09, modding is pretty straightforward. With 1.14, you have to take some extra steps and there are a few things you can't do at all.
Do I need to have my boot loader unlocked?
Click to expand...
Click to collapse
Yes. Leave it unlocked unless you need to RUU.
His hboot should be 1.11 which is the same as 1.09 as far as installing roms go.
If you're looking for a Sense ICS rom, I recommend ViperXL or CleanRom5. But there are other roms to try. As long as you stay in this forum and not the international forum you should be safe to flash anything you want.
Awesome thanks guys.
I check my boot loader and it is 1.11..
So that makes me happy cause all in all I'm addicted to flashing
One last question for you before I venture off on my own here..
With my nexus one I and the passimg I could flash through my bootloader in cause something went wrong or I just want to refresh my n1,is there something like that for this phone or are those days long gone?
Again thanks a bundle
Sent from my One X using xda app-developers app
Flash from TWRP recovery
todorcim said:
With my nexus one I and the passimg I could flash through my bootloader in cause something went wrong or I just want to refresh my n1,is there something like that for this phone or are those days long gone?
Click to expand...
Click to collapse
Correct, stick to TWRP. There is an app called GooManager that makes installing and updating TWRP close to effortless.
If you haven't already, reboot to recovery and see what you've got installed. Some people insist on using ClockworkMod recovery because they've used it on other phones, but it's not supported for this one and can cause issues with data getting corrupted. If you have CWM installed, all you need to do is download GooManager and select "Install openrecovery script" in settings and it will replace it with TWRP.
Ya I always use twrp have for a while but what I mean is if (can?) I soft brick my phone or something happens that I can't flash from recovery is there a passimg zip like we had for the n1 that could be flash through the boot loader?
You know just in case
I only ask cause its HTC thought maybe there was something like that...could have been a Google thing too not sure..
Sent from my One X using xda app-developers app
todorcim said:
Ya I always use twrp have for a while but what I mean is if (can?) I soft brick my phone or something happens that I can't flash from recovery is there a passimg zip like we had for the n1 that could be flash through the boot loader?
You know just in case
I only ask cause its HTC thought maybe there was something like that...could have been a Google thing too not sure.
Click to expand...
Click to collapse
Yes, you can still flash stuff through fastboot, if that's what you mean.
Ya that's what I mean
Thanks
Sent from my One X using xda app-developers app
I've got an AT&T HTC One, I rooted it and installed TWRP and haven't had the down time to do much else with it, including installing a rom yet.
I don't mind the oem ATT rom but I do need the Hotspot feature to work for my wifi tablet.
I've tried to turn on the hotspot feature with a couple scripts I've found on XDA but none of them seem to work so I've come to the conclusion that I'm going to have to change rom to be able to use the hotspot so this morning I Downloaded CM10 and placed it on the "SDcard" of my phone. I then tried to install it with TWRP. everything goes well half way through the install and then it hangs up about 60% through, it eventually seems to time out after like 15-20 minutes of not doing anything.
I then reboot it and all I get is an infinite animated CM boot logo.... I let it sit for an hour just to make sure it wasn't just a slow install.
I reinstalled it three times and the outcome was the same each time so I tried to ADB sideload it with the same outcome.
I even went on CM's site and downloaded another copy of CM10 but it made no difference.
I ended up having to reinstall the backup I made prior to starting this so I had my phone as I needed to go run some errands.
Does anyone know why I had the issues I was having with installing CM10?
Something I did wrong? How do I get CM to install?
Thanks
jessepatty said:
I've got an AT&T HTC One, I rooted it and installed TWRP and haven't had the down time to do much else with it, including installing a rom yet.
I don't mind the oem ATT rom but I do need the Hotspot feature to work for my wifi tablet.
I've tried to turn on the hotspot feature with a couple scripts I've found on XDA but none of them seem to work so I've come to the conclusion that I'm going to have to change rom to be able to use the hotspot so this morning I Downloaded CM10 and placed it on the "SDcard" of my phone. I then tried to install it with TWRP. everything goes well half way through the install and then it hangs up about 60% through, it eventually seems to time out after like 15-20 minutes of not doing anything.
I then reboot it and all I get is an infinite animated CM boot logo.... I let it sit for an hour just to make sure it wasn't just a slow install.
I reinstalled it three times and the outcome was the same each time so I tried to ADB sideload it with the same outcome.
I even went on CM's site and downloaded another copy of CM10 but it made no difference.
I ended up having to reinstall the backup I made prior to starting this so I had my phone as I needed to go run some errands.
Does anyone know why I had the issues I was having with installing CM10?
Something I did wrong? How do I get CM to install?
Thanks
Click to expand...
Click to collapse
What hboot? You may have to flash boot image separately in adb or s-off.
Venomtester said:
What hboot? You may have to flash boot image separately in adb or s-off.
Click to expand...
Click to collapse
1.14
I don't do much of this stuff so I am not entirely sure how to flash the boot image separately in adb.
I didn't think there was a way to s-off the HOX.
Thanks for the reply
jessepatty said:
1.14
I don't do much of this stuff so I am not entirely sure how to flash the boot image separately in adb.
I didn't think there was a way to s-off the HOX.
Thanks for the reply
Click to expand...
Click to collapse
On 1.14 the boot image needs to be flashed separately. Flash from fastboot..
Fastboot flash boot boot.img
The boot image is inside the Rom.zip your flashing. Keep a copy of the Rom on pc and extract files with winzip or whatever you like to use. But boot.img in adb folder and type the command, reboot and it should boot.
S-off can be done but only on a sense based Rom like viperXL.
Also read the stickies... They are there for a reason..
Sent from my HTC One X using xda app-developers app
This is not true. I s-off'd with cm10. Though you need to enable ADB root in settings for it to work.
Sent from my HTC One X using xda app-developers app
jessepatty said:
1.14
I don't do much of this stuff so I am not entirely sure how to flash the boot image separately in adb.
I didn't think there was a way to s-off the HOX.
Thanks for the reply
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2136172
exad said:
This is not true. I s-off'd with cm10. Though you need to enable ADB root in settings for it to work.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Well that explains why I was having issues on cm10.
Sent from my HTC One X using xda app-developers app
Make sure you're using the cm 10 for one xl (evita) and not the one x.
http://wiki.cyanogenmod.org/w/Evita_Info
I'll check out the links, thanks.
I can see allot has changed since December when I last messed with the phone. Back in December Clockwork recovery wasn't supported on the ATT version of the HOX. I see it now is in a touch version.
apparently I am doing something wrong as I keep getting the same indefinite CM boot logo and can't get past it. It appears I do not fully understand the process to side load the rom.
With that said, I restored it from a backup and I guess I'll just wait until I can confidently install a rom. This phone is so much different then my previous phones and tabs in regards to how it was unlocked and the install of different roms. I didn't have any problem figuring those out but this one has more steps involved which is aiding to my confusion. Maybe I'll find a step by step for my Hboot that I can follow, in the meantime I'll just keep having to look for free wifi for my tablet while I'm out and about.
You'd think there would be an easier way to enable the wifi hotspot on the phone.... LoL
Thanks for the info guys.....truly appreciated.
Try this...
http://code.google.com/p/android-wifi-tether/
Sent from my HTC One X using xda app-developers app
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.