Database Info

Tip/warning rom manager recovery for htc one x (gsm)

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

RUU Question

So My phone is constantly freezing and rebooting in apps every 5-15 minutes and I am going to try going back to stock and seeing if this occurs. My question is do i have to wipe my current rom? Or do i only have to fastboot oem lock and run ruu? Help would be appreciated. Think it is getting worse..

WhatTheAndroid? said:
So My phone is constantly freezing and rebooting in apps every 5-15 minutes and I am going to try going back to stock and seeing if this occurs. My question is do i have to wipe my current rom? Or do i only have to fastboot oem lock and run ruu? Help would be appreciated.
Click to expand...
Click to collapse
Yes, just run fastbook oem lock and then run the ruu. Make sure that you have the latest drivers from HTC (use htc sync if you can). Good luck!

For ruu grab the appropriate one .... Relock your bl like you Saud and run the ruu from you bl mode ...no need to wipe anything the ruu will do that for you

Skeeterdrums said:
Yes, just run fastbook oem lock and then run the ruu. Make sure that you have the latest drivers from HTC (use htc sync if you can). Good luck!
Click to expand...
Click to collapse
and i run the command in fastboot on my htc one x? ive did it once before.

WhatTheAndroid? said:
and i run the command in fastboot on my htc one x? ive did it once before.
Click to expand...
Click to collapse
Yessir head over to gunnymans thread in general forum to clear any confusion that remains

phone is going haywire.....Not being detected..rebooting every second..cant even get into an app...got into twrp and going to charge it ill 70 and restore to a better backup then hopefully ruu...thanks for the help

WhatTheAndroid? said:
phone is going haywire.....Not being detected..rebooting every second..cant even get into an app...got into twrp and going to charge it ill 70 and restore to a better backup then hopefully ruu...thanks for the help
Click to expand...
Click to collapse
Usually, the phone doesn't get detected if the drivers aren't up to date. Is it rebooting even from bootloader? You should be able to install everything from there, hopefully meaning restarts aren't an issue.
HTC One X using CleanRom 5.1 with BeastKernel 4.4

Skeeterdrums said:
Usually, the phone doesn't get detected if the drivers aren't up to date. Is it rebooting even from bootloader? You should be able to install everything from there, hopefully meaning restarts aren't an issue.
HTC One X using CleanRom 5.1 with BeastKernel 4.4
Click to expand...
Click to collapse
finally got it recognized and successfully ruu'd.It was very odd, like the phone was progressively getting worse for some reason.i am not not getting rebooted on stock rooted so it had to do something with my settings on the rom..like i said i under clocked and overclocked it, hot rebooted it, wiped cashe and dalvik...nothing was working and it finally just kept rebooting and freezing at home screen..Maybe a bad successful flash lol.. im not really sure.. or flashing over a bad flash had something to do with it..I might wait till jellybean comes out.

Have you tried to simply factory reset?

i personally like ruu'ing. i should do the same soon just to clean house. in the end it's pretty easy to get fluent on this phone.
i would say immediately after unlocking bootloader to ruu. i noticed some differences in the 1.85 to 2.20 ota vs the 2.20 ruu. it will also clean up any mess that might of been left on the phone. im also pretty ocpd =)
also htc sync imo is useless, i just use the standalone htc drivers haven't had any issues with them.

OP... What rom/kernel combo were you running?
Only time I've seen another phone go that nuts is when my cousin flashed rohans kernel in viper lol
Sent from my One X using Tapatalk 2

InflatedTitan said:
OP... What rom/kernel combo were you running?
Only time I've seen another phone go that nuts is when my cousin flashed rohans kernel in viper lol
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Viper and beastmode. My phone was going nuts....froze at the start screen 3 times and reset it self into a bootloop, then went back to freezing when start screen appeared..one of the times all I could see is the notification bar but I couldn't drag it Down. Lots of other crazy stuff happened on it as well...to much to tell. But I heard cleanrom is pretty stable, do I have to wipe stock rooted(no custom Rom yet) trying to find a good one and do I have to flash boot IMG if I'm on 1.14 or is it Included in the cleanrom installer? Might try elemental with cleanrom..see how that works out.

[Q] Bricked HOX? Please help.

I have an ATT One X, which I recently rooted. Yesterday I tried to flash a JB ROM and it said it was successful. However, now when I turn it on it just stays on the Quietly Brilliant screen indefinitely.
I can get into fastboot, and TWRP is there too.
I can't mount from within TWRP, as my computer just says the drive must be formatted before it can be used. I tried to run an RUU but it doesn't recognize that the phone is connected. Anytime I go to reboot, etc from within TWRP it tells me I have no OS.
Help? Please?

Reference the other 20,000 threads opened and answered about this topic

emylibef said:
I have an ATT One X, which I recently rooted. Yesterday I tried to flash a JB ROM and it said it was successful. However, now when I turn it on it just stays on the Quietly Brilliant screen indefinitely.
I can get into fastboot, and TWRP is there too.
I can't mount from within TWRP, as my computer just says the drive must be formatted before it can be used. I tried to run an RUU but it doesn't recognize that the phone is connected. Anytime I go to reboot, etc from within TWRP it tells me I have no OS.
Help? Please?
Click to expand...
Click to collapse
If it tells you in needs to be formatted... FORMAT IT!! Mount in twrp and right click removable storage. Choose format. Look down about 2 threads.. I literally just explained the process to another guy. Gotta read bro.
Sent from my HTC One XL using Tapatalk 2

I think these people need some tough love so they do some research and learning
Sent from my HTC One XL

Ya, I just stopped replying to these threads

My new years resolution didn't last long I passed on a few but OMFG how can so many people be so lazy and not see all the answers
Sent from my HTC One XL
---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------
Maybe next year I'll be a more patient person
2013 is not the year for me sorry noobs at least titan will be ready to hold your hand.
Titan you are my idol
Sent from my HTC One XL

emylibef said:
I have an ATT One X, which I recently rooted. Yesterday I tried to flash a JB ROM and it said it was successful. However, now when I turn it on it just stays on the Quietly Brilliant screen indefinitely.
I can get into fastboot, and TWRP is there too.
I can't mount from within TWRP, as my computer just says the drive must be formatted before it can be used. I tried to run an RUU but it doesn't recognize that the phone is connected. Anytime I go to reboot, etc from within TWRP it tells me I have no OS.
Help? Please?
Click to expand...
Click to collapse
If you have no OS, download cleanrom 5.1, and trasnfer it to your phone. Flash that in twrp and you'll have your phone back... If you want to venture further, pm me and ill help you through it
Sent from my HTC One XL using Tapatalk 2

Do not worry, ur phone not brick, just you did not flash kernel before flash rom. Always remember this, if you are on Hboot 1.14 or higher, flash kernel (boot.img) before flash rom. Now just extract the boot.img from the JB rom, hook phone to PC (make sure fastboot USB), using kernel flasher, and flash the kernel. Then bingo, your phone back to life!
*** Remember this, always nandroid backup, and as long as you can get into recovery mode, it means ur phone never been bricked!

[Q] Please help unbrick???!!!!

Here is what I did....
HTC One X (ATT). Unlocked and rooted yesterday. (TWRP)
Today tried to install CM10 and GApps, got stuck on CM bootscreen, then I flashed the boot.img and it still did not work....then my immediate next step (probably stupidly) was to flash modded boot...still did not work....I just got to HTC screen with the red writing on the bottom and nothing else....
So I got into TWRP and restored to my backup (which I was able to do before the above) and just got to the same HTC screen with red type on the bottom......now I started to panic.
I tried to relock the phone...and I did but now I cant go anywhere but the fastboot screen!!!!
Please Help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

If you relocked already just run the ruu in fastboot and restore to stock.

davezaff said:
If you relocked already just run the ruu in fastboot and restore to stock.
Click to expand...
Click to collapse
I am downloading the RUU....we'll see

Many Thanks
davezaff said:
If you relocked already just run the ruu in fastboot and restore to stock.
Click to expand...
Click to collapse
Many thanks....it worked!!!!!
Now the question is...do I try again? (Not today anyway)

trevorb21 said:
Many thanks....it worked!!!!!
Now the question is...do I try again? (Not today anyway)
Click to expand...
Click to collapse
Just read read and read more..be comfortable first than you'll be fine and know how to get out of any situation

Just read up and give it another go.....like anything else, sometimes you need certain thing to happen to learn....good luck.

Just saying, you flashed the boot.img after flashing the rom and gapps? The boot.img is flashed before flashing the rom

It can be done either way.

ive been seeing alot of new members soft bricking this way should read though this post http://forum.xda-developers.com/showthread.php?t=1957193 it explains every thing for ppl on hboot 1.14 and higher.

trevorb21 said:
I tried to relock the phone...and I did but now I cant go anywhere but the fastboot screen!!!!
Click to expand...
Click to collapse
That is what is supposed to happen. Once you relock, you need to run the RUU. It won't boot otherwise.

I am unlocked and rooted again.....ready to try again...
I want to leave the phone alone but I cant help myself.......Anyone else have this issue???

I know what you mean, when i first got my one x and learned of rooting, i felt i was claustrophobic with normal stock. I Read and read and read some more, before I even thought about flashing roms. But I Recommenced flashing Viper JB 3.1.0 As it basically installs the boot img in the boot-loader for you. I also recommend Cm 10.1, except it does not have camera working as of yet. If you dont mind not having a camera, cm 10.1 is a very smooth rom. Also remember if flashing certain roms like cm 10. dalvik, cache and factory reset, as well as flashing the boot img are required for the rom to work. Good luck

trevorb21 said:
I am unlocked and rooted again.....ready to try again...
I want to leave the phone alone but I cant help myself.......Anyone else have this issue???
Click to expand...
Click to collapse
I've had this problem since may 6th, 2012 lol.. good god you should here my wife when I tell her I didn't get her messages or calls because I was in recovery lol!
Sent from my HTC One XL using Tapatalk 2

InflatedTitan said:
I've had this problem since may 6th, 2012 lol.. good god you should here my wife when I tell her I didn't get her messages or calls because I was in recovery lol!
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I'm livin in the same life man been though 4 android phone and a tablet in a year o and rooted all my friends phones

Thanks a ton this thread helped me save my phone

[Q] Not getting past HTC screen

I looked around and didn't see a solution to my problem. I might have missed it because I'm kind of panicked right now.
My HOXL was dying really fast. Within a few hours, it falls from 80% to 0%. I wanted to factory reset because I heard that it helps the battery life.
So I followed the process I always have (I'm unlocked, rooted, and had pacman's evita ROM installed) and did a factory reset, wiped cache and dalvik cache. Then I re-flashed pacman's ROM and the gapps. When I rebooted though, it went to the HTC screen and in a few seconds it just went black. I think it might have still been on or something, but nothing was happening for like 30 minutes. I tried it over and over again, flashing new ROMs and kernels, but now all that's happening is that it's stuck on that very first HTC screen.
I downloaded the latest JB RUU for evita to try it out. But if I can't get past that first screen, is there a way to connect it? I can still get into TWRP's recovery. My HBoot is 1.09. I'm really starting to feel nervous about having to buy a new phone, yet I feel like there should be a way to fix this. Could flashing the stock kernel be all I need? I tried to download from Viper's hub, but the download just stops at 99% and doesn't finish.
Please, I would really, really appreciate any help!

I would run the 3.18 RUU (which you can do in fastboot).

Try a complete wipe: Factory reset, system, cache and dalvik cache in twrp or if it is not wiping correctly due to twrp version " 2.3......" is best fro our phones, try downloading and installing twrp again or use adb commands to wipe and flash rom again.

I've tried a complete wipe, but I just noticed that my TWRP version is 2.2.0. I tried the wipe like five or more times and it didn't work. My PC isn't reading the HOXL in the adb command window. I rooted a Sero Pro 7 this way, so I think I should have the drivers installed for it... I'm going to try installing the HTC Sync drivers and seeing if I can send adb commands to my HOXL. If this doesn't work, I'm going to try the 3.18 RUU. I heard that some people have bricked their HOXL completely doing this, but I didn't change my SuperCID and s-on (?), so would I be fine? Or would it be safer to just use the latest ICS one (RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio _0.19as.32.09.11_2_10.105.32.25L_release_271865_si gned.exe)?

So you have no way to flash boot image separately? I would definitely try to get device recognition so adb can be used before running ruu.
Sent from my HTC One X using xda premium

Yeah, I went through the noob way of unlocking and rooting this phone, so there was no need to use adb commands. I would have liked to try that first before running RUU, but I just want to have a working phone again, even if I have to go through the whole process of unlocking and rooting.
Sent from my Nexus 7 using XDA Premium HD app

I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium

Venomtester said:
I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is what I'm worried about:
SERooted wrote: Note to OP: You really should add to the 1st post that it is not wise to flash the 3.18 firmware over super cid and s-on.. its not a good thing for most people to have a qhsb_dload turn their phone into a paper weight before finding out that they shouldn't have used that file to begin with. i had to find out the hard way. i would have flashed the ics firmware on my phone but decided to go with the big JB only to find out that it turns it into a paperweight. I understand this is no fault but my own, however this would greatly help people when choosing which ruu to run.
http://forum.xda-developers.com/showthread.php?t=2191477

I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium

Venomtester said:
I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Huh...I just tried flashing the UrDroid ROM because of its aroma installer, but it didn't happen in recovery, like I thought it would. It said it was successful, so I rebooted the system. It got past the initial screen with an AT&T boot img and htc one img. Now I'll have to see if it actually loads past this.
EDIT: It worked! I'm going to have to try to see if I can load boot img some other way than just an aroma installer.

You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium

Venomtester said:
You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Second Flash GUI....works like a charm