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

Unlocking Bootloader

Hey I have tried everything to unlock the boot loader but i keep getting a error " Waiting for device" I even downloaded everything for AVD and SDK manager and changed USB ports. I was wondering if anyone can help me through skype or aim.
Thanks

looks like you don't have the proper driver for the one S phone

Sorry to barge in like this.
But since you were saying something like this maybe you can help me.
I am using an a Acer TravelMate 3200 windows xp.
What is the driver that I need to preinstall in the computer for me to use for later exploits like flashing,rooting for my xperia arc.
Sent from my LT15i using xda app-developers app

Sandro8771 said:
Sorry to barge in like this.
But since you were saying something like this maybe you can help me.
I am using an a Acer TravelMate 3200 windows xp.
What is the driver that I need to preinstall in the computer for me to use for later exploits like flashing,rooting for my xperia arc.
Sent from my LT15i using xda app-developers app
Click to expand...
Click to collapse
Im on a Mac running Windows 7.

Doughh said:
Hey I have tried everything to unlock the boot loader but i keep getting a error " Waiting for device" I even downloaded everything for AVD and SDK manager and changed USB ports. I was wondering if anyone can help me through skype or aim.
Thanks
Click to expand...
Click to collapse
Tried putting your phone in fastboot?

you need to put the phone in fastboot and have these fastboot files downloaded on your computer
http://www.mediafire.com/?50baad8rykng2j0

Have you tried the AIO?
http://forum.xda-developers.com/showthread.php?t=1604677
[TOOL] HTC One S All-In-One Toolkit V1.1 [6-11-12] [PERM ROOT][Noob-Proof]
Sent from my HTC One S using Tapatalk 2

O0cynix0o said:
Have you tried the AIO?
http://forum.xda-developers.com/showthread.php?t=1604677
[TOOL] HTC One S All-In-One Toolkit V1.1 [6-11-12] [PERM ROOT][Noob-Proof]
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Just tried AIO. Finally unlocked the bootloader! Now im confused on what to do lol..

if you have root then all that's left is to boot up into recovery (volume down and power then select recovery from the bootloader) and flash a custom rom .zip file from your sd card. just be sure to follow all the installation steps for your selected rom (i recommened AOKP Jelly Bean, check my signature for the link if you like) and always ALWAYS wipe data/cache before installing a new rom. and happy flashing

Doughh said:
Just tried AIO. Finally unlocked the bootloader! Now im confused on what to do lol..
Click to expand...
Click to collapse
First things first you need to boot into recovery (I use Goo Manager for this; Im lazy like that. It will also install the TWRP recovery.) and make a backup of the stock ROM your running now and keep a copy on your PC. Some times the contents of the SD Card can be corrupted. If any thing goes wrong your going to need something to go back to.
Then depending on your needs (AOSP/Sence) location in the world (EU/US) and what kind of One S (S3/S4) you have; you want to pick a ROM that's suits your needs.
I would stay away from Viper for now at least till your more secure with flashing, there are some extra steps like flashing a different boot.img; which can soft brick your phone or worse.
Start with something like Axiom S, for all your Sence needs. Or CodefireX CM10 for AOSP. If you use TWRP for your recovery you won't have to fast boot flash the boot.IMG for the ROM you chose. But again this depends on the ROM you choose to use, some ROMs don't play well with TWRP.
But most of all read. And then read some more. And when you think you know what your doing read a little more. This device seems to be real finicky. What works on one might not work on a another.
Good luck, be safe and welcome to the One S Forums!
Sent from my HTC One S using Tapatalk 2

[Q] Help! Bricked HTC One X AT&T

I've been using Hassoon2000's All in one toolkit. I successfully unlocked the boot loader. I was going to install Cyanogenmod 10. I copied the boot.img into the kernals folder for the AIO toolkit. I flashed that and that's where it went south. My phone continuously rebooted at the HTC bootup screen.
After some reading I have "relocked" the bootloader. I attempted to flash what I thought was the stock RUU. I can get into fast boot, but not the recovery. ( I was using the TWRP recovery that came with the tool kit). If I try to choose factory reset, it acts like it's flashing my phone (gray screen with a progress bar, but then goes back into fastboot after about 30sec.)
Am I SOL? I'm willing to compensate via pay pal if we get this thing going. If not, I did find a site call JTag brick repair.

When you flashed the kernel, did you install the actual Rom? If your phone can turn on, its not bricked. Which ruu did you download? Why isn't it working?
Sent from my HTC One XL using xda app-developers app

area51avenger said:
When you flashed the kernel, did you install the actual Rom? If your phone can turn on, its not bricked. Which ruu did you download? Why isn't it working?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I found an ruu after some googling. I perhaps didn't get the right one. No I didn't install the rom after I flashed the kernel. I flashed the kernel first, then I was going to boot into the recovery to install the rom. The phone just hung at the HTC screen before going into recovery. In red letters it says: This build is for development purposes only... etc"

Did you hold volume down and power at the same time to boot into recovery? Also make sure you get the right ruu. Which carrier are you on and what firmware were you before you flashed? The ruu is an exe you run from your desktop while your phone is in fastboot
Sent from my HTC One XL using xda app-developers app

Here's where I'm currently at. I have the bootload unlocked again through the toolkit. I also have the TWRP installed. I CAN get into TWRP.

I have AT&T, I'll do some searching on trying to find an RUU.
Hboot-1.14.0002
Radio-0.19as.32.09.11_2
openDSP-v29.1.0.45.0622

Awesome. Now mount USB storage in twrp and plug it in to your computer. If windows asks you to format. Say yes and format fat32. Copy the cm10.zip file to your sd card. Install from twrp. You may have to flash the boot.img again in fastboot.
Sent from my HTC One XL using xda app-developers app

I get an E:Error in sdcard/cm10.zip (Status 7)
Error flashing zip
Updating partition details...
I did do a factory reset and wipe cache.

Is it the right cm10 for HTC evita

omario8484 said:
Is it the right cm10 for HTC evita
Click to expand...
Click to collapse
I'm doing endevarou. I have the HTC One X, not the XL.

You have the one xl if you have the dual core att evita. if you have the quad core international one x then it's the endeavor.
Sent from my HTC One XL

deathbyenduser said:
I'm doing endevarou. I have the HTC One X, not the XL.
Click to expand...
Click to collapse
If so, then you are in the wrong forum, and if you used the toolkit from this forum, it also explains why you are stuck in the state you are. This forum is for the Evita. Are you sure you have the quad core Tegra3 version? What carrier is your phone from?
Also, if you can get into hboot, you are nowhere near bricked. Any type of power on (even just hboot) is not that hard to recover from. The only real brick is if the screen doesn't come on at all, and no charge LED when plugged to charger. Even then, the phone can sometimes be unbricked in Linux.

redpoint73 said:
If so, then you are in the wrong forum, and if you used the toolkit from this forum, it also explains why you are stuck in the state you are. This forum is for the Evita. Are you sure you have the quad core Tegra3 version? What carrier is your phone from?
Also, if you can get into hboot, you are nowhere near bricked. Any type of power on (even just hboot) is not that hard to recover from. The only real brick is if the screen doesn't come on at all, and no charge LED when plugged to charger. Even then, the phone can sometimes be unbricked in Linux.
Click to expand...
Click to collapse
Okay. I have the One XL for LTE. I was thinking the XL meant the bigger HTC One X that was out.

deathbyenduser said:
I'm doing endevarou. I have the HTC One X, not the XL.
Click to expand...
Click to collapse
deathbyenduser said:
Okay. I have the One XL for LTE. I was thinking the XL meant the bigger HTC One X that was out.
Click to expand...
Click to collapse
Really?! You my friend should not be flashing, rooting, unlocking bootloaders until you know the process and you can do it without reading how to do so. Learn how to swim before you jump into the deep end.

This is my third my root. I had the OG Motorola Droid and HTC Sensation with Tmobile. Now this One X LTE.
I can see why you said that though. I made an honest mistake. Looking back at the HTC models what I meant to say for some stupid reason I thought the HTC One X + (new one for att) was actually the HTC One XL. So I confused myself, flashed the wrong kernel. Luckily with some confirmation from you guys I'm back on the road. My phone is working.
My phone is working with CM10. I just need to get a compatible version of Gapps on. I'll be sending someone beer money. :victory:

deathbyenduser said:
This is my third my root. I had the OG Motorola Droid and HTC Sensation with Tmobile. Now this One X LTE.
I can see why you said that though. I made an honest mistake. Looking back at the HTC models what I meant to say for some stupid reason I thought the HTC One X + (new one for att) was actually the HTC One XL. So I confused myself, flashed the wrong kernel. Luckily with some confirmation from you guys I'm back on the road. My phone is working.
My phone is working with CM10. I just need to get a compatible version of Gapps on. I'll be sending someone beer money. :victory:
Click to expand...
Click to collapse
Great to hear.
You are very lucky you didn't do it the other way around (flash an endeavor rom on an evita device), as you would be the proud owner of a very expensive paperweight.
HTC can get stuffed for naming 3 different phones almost exactly the same One X/ One XL (or AT&T One X) / One X+. It is a minefield for people new to the phone.

Regardless of how many phones you've rooted, its pretty clear that you didn't do the enough reading to know the difference between the X, XL, and X+, and to know what you own. As already mentioned, you're lucky you didn't brick.
Only flash things from our forum, and you'll be safe: http://forum.xda-developers.com/forumdisplay.php?f=1538

Need Google apps package..

Hi all. Today I installed CyanogenMod 10.1 using twrp on my newly rooting phone. I followed a youtube video by Graeme Biggs. I should have watched it fully before I started. I neglected to download a Google apps package. He said I could find it on XDA. I did a search and could not find it. Can somebody point me in the right direction to this file? Thankyou.
Sent from my HTC One using xda app-developers app

My phone presently boots up to the white HTC screen and then shuts off continually.
Sent from my Nexus 7 using xda app-developers app

here you can find g.apps
http://goo.im/gapps

Thank you very much.
Sent from my HTC One using xda app-developers app

Your signature says HTC One. Is your phone an HTC One or an HTC One XL? That's very important to know because you can brick your phone if you install the wrong software.

Hi. I was using my one to post in the forum. I was installing CyanogenMod on my Rogers one x.
Sent from my HTC One using xda app-developers app

quicksilver53 said:
I followed a youtube video by Graeme Biggs. I should have watched it fully before I started. I neglected to download a Google apps package.
Click to expand...
Click to collapse
You should fully research and understand any root/mod process, before you start it. You also shouldn't rely on YouTube guides, this being one of the many reasons.

Yes thanks. I realize I should have done a little more research. I will certainly in the future.
Sent from my HTC One using xda app-developers app

So I went and plugged my one x into my PC so U could try abd flash the Google apps package and my phone does not show up as a removable drive. Since my **** up with trying to install cyanogenmod, my phone has been in continuous bootloop and only going as far as the HTC screen before rebooting. I can get it into twrp. How would I be able to get the zip file from my computer to my phone? Is there something else I need to do to fix this problem? Thanks for any suggestions.
Sent from my HTC One using xda app-developers app

Go into TWRP, connect your phone to pc, select mount in TWRP menu, select mount usb storage, your phone should show up as a removable drive now, copy file from pc to phone.
Sent from my Evita

Thank you so much Timmaaa. I thought that there must be a solution.I will try in the morning.
Sent from my HTC One using xda app-developers app

Hi Timmaaa. I tries what you suggested and it still did not show up on my computer. My computer makes the same sound as it always does when an external device is attached. When in tarp and I press mount, a window opens up which shows the storage. It says SD card (0MB). Should something be checked off in partitions to moun t? I tried to mount the SD several times an nothing shows up. Thanks.
Sent from my Nexus 7 using xda app-developers app

I have now found out that it does not show up as an htc device. It shows up as an f drive and a g drive. I tried to copy the gapps to the g drive and it said I need to format the removable disk. I hope that this works.
Sent from my Nexus 7 using xda app-developers app

Ah ok, you did a factory reset in bootloader at some point didn't you, that corrupts your sd card. You will need to format it like Windows instructed, format it to fat32 format and you'll be able to access it again. Unfortunately any data you had on it has been wiped now, I hope there wasn't anything too important on there.
Sent from my Evita

Thanks. I did reformat the SD card as windows asked. Then I copied both files onto my phones SD cars and followed the instructions again using twrp. It said that they were both installed successfully but theCyanogenMod home screen did not come up after completion. When I reformatted the SD card, I just let windows do. I did not set it to format to anything specific. I will try it again when I get home tomorrow from work,. Thanks again for your help.
Sent from my Nexus 7 using xda app-developers app

If you're s-on you need to flash the boot.img from the ROM zip via fastboot after you've flashed the ROM and gapps.
Sent from my Evita

Thanks. I am s-on. I will look at it tomorrow and figure out how to do that.
Sent from my HTC One using xda app-developers app

Just extract the boot.img from the root of the ROM zip, put it in your fastboot folder on your pc, bit your phone into bootloader and connect it to your pc, wait for it to say fastboot usb on your phone display then give this command:
Code:
fastboot flash boot boot.img
Now reboot your phone and it'll boot into the ROM.
Sent from my Evita

Hi Timmaaa. I am still having problems flashing the boot.img from cyanogenmod to my Evita. I put it I'm my fastboot folder and typed in the command as you have told me. I get this message pop up from fastboot.exe. ( this application has failed to start because AbdWinApi.Dll was not found. Re-installing the application may fix the problem). I just do not understand what I could be doing wrong. Is it possible I am not using the right folder? I started this a week ago but got the Norovirus from work and could not reply sooner. Thanks for any assistance you can give.
Sent from my Nexus 7 using xda app-developers app

I believe I did have the wrong folder. I just tried the afastboot ADB folder and it worked. Thanks again for your help. I appreciate it greatly.
Sent from my Nexus 7 using xda app-developers app

Can't mount corrupted internal sd

Hi all. I was trying to install android revolution on my Rogers one x and something went wrong while flashing the ROM. It does not show up as a removable drive when in twrp and connected to my PC. I have done a search on this forum and can not find a solution. I have lost my backups that were in the SD. I know it is possible to reformat as I have done this I this before. Can anyone give me directions or provide a link to them. Thanks
Sent from my Nexus 7 using XDA Free mobile app

I feel like such an idiot for not being able to figure this out. This happened once before while trying to flash a Rom on my evita.
Sent from my HTC One using XDA Free mobile app

Well, I had that yesterday. I rebooted into Cwm recovery, connected the phone to my PC with the USB cable, and went to mount SD Card in Cwm. The drive appeared on windows and I could reformat it.

When I plug mine into the pc and press mount while in twrp it does not show up. I am stumped.
Sent from my HTC One using XDA Free mobile app

Your first problem is that you're flashing a ROM that isn't meant for this device, you've been wandering into the wrong forum, make sure you stay in the one you're posting in now.
Try using the advanced wipe feature of TWRP to wipe the sd card, which should format it.
Transmitted via Bacon

Thanks for your reply. I should have clarified. I was trying to flash ARHD 4.18.401.3 which is supposed to be a stock Rom for the evita. I downloaded it from the I did an advanced wipe but it still does not show up on my pc.
Sent from my HTC One using XDA Free mobile app

quicksilver53 said:
Thanks for your reply. I should have clarified. I was trying to flash ARHD 4.18.401.3 WHICH is supposed to be a stock Rom for the evita. I did and ad danced wipe but it still does not show up on my pc.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
No that's what I'm saying, there is no ARHD for Evita, only for Endeavoru. You're getting your phone HTC One XL/at&t One X (Evita) mixed up with the HTC One X (Endeavoru), they're completely different devices. You're lucky you didn't brick. Try flashing CWM recovery instead.
Transmitted via Bacon

Oh I see. What an idiot I am. I totally forgot that there were 2 different versions. I'll see if I can flash via otg cable.
Sent from my HTC One using XDA Free mobile app

quicksilver53 said:
Oh I see. What an idiot I am. I totally forgot that there were 2 different versions. I'll see if I can flash via otg cable.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Hi all. I am still having no luck getting my evita recognized by my pc so I can mount it. I get a beep from the pc when I plug it in, in bootloader mode. I have reinstalled abd and htc sync to get the drivers. it appears to recognize my device while it is checking the media on it, but when it is complete it says no phone attached. I even deleted htc sync and just left the drivers, but still no joy. I just don't get it. My m7 is recognized on my pc, so I would imagine that the drivers are there. When my evita is off and I push power and volume down to get into bootloader, the capacitive buttons do not flash like they used to. Can anyone offer any information? I wonder if someone would be able to help me over Team viewer? I feel so lost. Never had these problems with my m7. Thanks.

The button lights only flash while using the button combo while the phone is already turned on, if the device is switched off it just boots into the bootloader without any flashing lights. As for why your device isn't being recognised, it's really difficult to troubleshoot without actually having access to the device and the PC.
Transmitted via Bacon

Thanks Timmaaa.
Sent from my Nexus 7 using XDA Free mobile app

Well I have managed to fix my Evita two nights ago. I deleted my SDK tools and various programs and reinstalled them all. Then I was able to flash a boot.img via fastboot. My device was still not able to mount on my PC but I was able to flash a ROM via an otg cable. Today I managed to achieve s-off with firewater and then super-cid. I am overjoyed. Thanks to all who helped. Have to figure out how to change status to solved.
Sent from my One X using XDA Free mobile app