Database Info

please help i need update my htc one x at&t

i have phone htc one x from at&t
iam do rooting in it and unlockbootloader and have recovery
i need update it in jelly bean which rom i use
my h-boot 1.14.0002
radio-0.19as. 32.09.11.2
evita pvt ship s-on rl
please iam new in htc one x

you have already unlocked the bootloader? you just want to know what ROM to choose? It is a highly personal choice.
do you value (speed/stability/bleeding-edge-features/audio-quality).
would you prefer an AOSP ROM or Sense (Android Open Source Project or HTC's skin).
can you live without some features? Do you need the latest google camera (with the photosphere).
there are plenty of great ROM's for this device, but you'll need to be a bit more specific about what you want.
Read a few of the threads about specific ROMs and see what features they have/lack, what bugs they have, and whether you think it will suit you.
If you want Jelly Bean, you are stuck with AOSP ROM's for now (until HTC releases the JellyBean update for this phone). So quite a few of the threads in the One X Original Dev forum will be relevant.
Just remember when you go to flash the ROM, you'll need to flash the boot.img through fastboot (as you have hboot 1.14).

codeprimate said:
you have already unlocked the bootloader? you just want to know what ROM to choose? It is a highly personal choice.
do you value (speed/stability/bleeding-edge-features/audio-quality).
would you prefer an AOSP ROM or Sense (Android Open Source Project or HTC's skin).
can you live without some features? Do you need the latest google camera (with the photosphere).
there are plenty of great ROM's for this device, but you'll need to be a bit more specific about what you want.
Read a few of the threads about specific ROMs and see what features they have/lack, what bugs they have, and whether you think it will suit you.
If you want Jelly Bean, you are stuck with AOSP ROM's for now (until HTC releases the JellyBean update for this phone). So quite a few of the threads in the One X Original Dev forum will be relevant.
Just remember when you go to flash the ROM, you'll need to flash the boot.img through fastboot (as you have hboot 1.14).
Click to expand...
Click to collapse
thx ur mean i can put rom now
how about hboot update i need that or no
and tell me which rom its good ur use it before
and remember my phone from at&t
thx

foronour said:
thx ur mean i can put rom now
how about hboot update i need that or no
and tell me which rom its good ur use it before
and remember my phone from at&t
thx
Click to expand...
Click to collapse
if you have a recovery on there (like TWRP, do not use CWM!!!), then yes, you can put a ROM onto it. transfer your ROM onto the sdcard and you'll probably want the Gapps there as well. Then power off your phone. Hold the volume down button and press the power button for a couple of seconds (do not release the volume down until your recovery is loading. With hboot 1.14 you will need to flash the kernel seperately (in fastboot mode with the usb connected to your computer, you should run "fastboot flash boot boot.img" from a folder that contains fastboot and boot.img (which can be extracted from the zip file of your ROM).
you can downgrade your hboot, but do not attempt to do this until you fully understand what it involves. Please read up on how it is done, as an error doing this can permabrick your device.
I am quite enjoying CyanogenMod 10. I have had better luck with the later nightlies than the stable version of this ROM, but YMMV. There are plenty of good ROMs to try.

Keep it simple go with viper
Sent from my HTC One XL

954wrecker said:
Keep it simple go with viper
Sent from my HTC One XL
Click to expand...
Click to collapse
I would have suggested it, but he did say he wanted Jellybean

I missed that I really had no idea what he said
Sent from my HTC One XL

codeprimate said:
if you have a recovery on there (like TWRP, do not use CWM!!!), then yes, you can put a ROM onto it. transfer your ROM onto the sdcard and you'll probably want the Gapps there as well. Then power off your phone. Hold the volume down button and press the power button for a couple of seconds (do not release the volume down until your recovery is loading. With hboot 1.14 you will need to flash the kernel seperately (in fastboot mode with the usb connected to your computer, you should run "fastboot flash boot boot.img" from a folder that contains fastboot and boot.img (which can be extracted from the zip file of your ROM).
you can downgrade your hboot, but do not attempt to do this until you fully understand what it involves. Please read up on how it is done, as an error doing this can permabrick your device.
I am quite enjoying CyanogenMod 10. I have had better luck with the later nightlies than the stable version of this ROM, but YMMV. There are plenty of good ROMs to try.[/QUOTt
this rom for my phone or no
http://forum.xda-developers.com/showthread.php?t=2022785
plz give me dirct link for the rom
and i have recovery TWRP
Click to expand...
Click to collapse

foronour said:
this rom for my phone or no
http://forum.xda-developers.com/showthread.php?t=2022785
plz give me dirct link for the rom
and i have recovery TWRP
Click to expand...
Click to collapse
if you have an evita device, then this ROM is compatible with your phone. I haven't tried it myself, so make sure you read through the forum for all instructions relating to that ROM.
there is a downloads link in the initial post of that thread, if you follow that, you will find the ROM. I won't to link directly to the download, as if the ROM is updated you'll end up with an older version, but if you go to the developers thread, you'll get the latest.

Newtoroots JB rom with Sense 4+ is available and stable now. I've been waiting for JB with Sense for a long time and it's perfect, i'd give it a go.
http://forum.xda-developers.com/showthread.php?t=2022785

hboot 1.14 issues switching ICS <--> JB

Hi,
After wasting precious hours on this, I was wondering why this thing doesn’t get more attention.
Long story short, some (all?) ROM installers through recovery have problems flashing the boot.img file (the kernel) when hboot version is 1.14.
The kernel can however be flashed from fastboot : fastboot flash boot.img
To make matters worse, JB roms don’t work with ICS kernels and vice-versa. So it’s very easy to reach a non-bootable state by moving from one to the other.
I learned that here:
http://forum.xda-developers.com/showpost.php?p=35891164&postcount=1
While on ICS Rom , copy ROM and Kernel installer to sdcard
Run Kernel Installer First reboot and after kernel installs (you will know because ICS will on boot to ROM)
you might have to hold down on power button until soft lights flash like 12 times, then hold down volume down button and press power button
when phone boots into bootloader volume down button to recovery option then press power button to get to recovery to flash JB ROM
Click to expand...
Click to collapse
The following procedure seems reliable (probably for every ROM):
http://forum.xda-developers.com/showpost.php?p=35755205&postcount=761
wipe system. wipe cache. wipe dalvik.
factory reset.
flash rom.
have twrp boot into bootloader.
fastboot flash boot.img
reboot
Click to expand...
Click to collapse
You can get the boot.img from the zip of the ROM you’re installing if you need it.
The major problem however is ROM installers that don’t offer the option to skip the kernel flashing. When the installers try to flash the kernel, it takes a LONG time for it to give-up.
During this time you're left wondering if it's ever going to finish or it needs to be interrupted.
Also, this time is completely wasted, because by the time it finishes, the kernel hasn't changed and it still needs to be done from fastboot.
A good example for one installer that does have the option to skip kernel flashing is here:
http://forum.xda-developers.com/showthread.php?t=1655011
All the ROMs that I found have incomplete information about this or neglect to mention this completely on their front page. I wish they didn’t.
I hope this will be useful to someone... it sure would have been for me.
ystavi

Wrong section ??
Sent from my HTC One XL using xda app-developers app

This will be moved/closed soon
Sent from my HTC One XL using xda premium
---------- Post added at 04:11 PM ---------- Previous post was at 04:08 PM ----------
Or you could download flash img gui and preflash the boot.img b4 flashing Rom. Simple as that.
Sent from my HTC One XL using xda premium

Where is cheesy nutz

I hate to say everything you just stated is common sense...
If you're having issues with your hnoot then downgrade and avoid all these so called problems
Sent from my One X using Tapatalk 2

superchilpil said:
I hate to say everything you just stated is common sense...
If you're having issues with your hnoot then downgrade and avoid all these so called problems
Click to expand...
Click to collapse
So you think that if a ROM installer assumes that I'm not using a specific hboot then there's no need to bother to say so on the front page of the ROM or during the installation?

I agree all installers for HTC One XL should offer the choice to not try to install boot.img inside their script.
The problem is super common and simple to resolve.
Many do not want to install boot.img from recovery, make it an option. Downgrade of hboot is not supported by HTC and is not at all required to install custom ROM's so why try beating a dead horse when the answer from HTC is simple, "flash boot.img from fastboot."

[Q] Help About Root & Revolutionary

help me, i have followed the instruction from htcdev.com to unlock my desire s bootloader with HBOOT 2.00.002.. after that i found my bootloader with text UNLOCKED but still it shows S-ON.
And then i continued to try root my desire s, i followed instructions that i found in this forum (thanks ) after finished, i tried to install some apps that need root access but i found that my desire s is not rooted (the apps said that).
The last things that i want to asked is, when i go to fastboot menu, i point to recovery mode and i found my desire with Revolutionary 4.0.1.4. I searched info about that things (revolutionary), i found many people said that if i have success install Revolutionary that means i have successfully rooted my device.
is there anybody could help and explained to me about those problems? i would very appreciate that

Revolutionary 4.0.1.4 is a custom recovery. Installing a custom recovery alone does NOT give you root access.
READ index thread in the forum and you'll have your answers

Thanks Bro ContactFront i will search in index thread
With the condition that i have now, is it possible if i want to return it back to default? I want to try update my desire to ICS using RUU Official uptade that i downloaded from htc website..
Sent from my Anvyn Desire S. Powered by XDA Developers

short answer is yes, you can go back to stock

Don't use the official ics Ruu, it's buggy and unfinished.
My pessimism extends to the point of even suspecting the sincerity of the pessimists.
—Jean Rostand

Alrighty then! Thanks All
But, do i need to root my device if i want to flash a custom rom? or all that i have done is enough to flash a custom rom? as i explained before, this is what i have done to my HTC Desire S :
HTC Desire S ( Gingerbread)
UNLOCKED using HTCDev
S-ON
HBOOT 2.00.0002
Installed Revolutionary 4.0.1.4
Sent from my Anvyn Desire S. Powered by XDA Developers

zidane_argun said:
Alrighty then! Thanks All
But, do i need to root my device if i want to flash a custom rom? or all that i have done is enough to flash a custom rom? as i explained before, this is what i have done to my HTC Desire S :
HTC Desire S ( Gingerbread)
UNLOCKED using HTCDev
S-ON
HBOOT 2.00.0002
Installed Revolutionary 4.0.1.4
Sent from my Anvyn Desire S. Powered by XDA Developers
Click to expand...
Click to collapse
seems like you still have not read the index.... You need root to flash a custom ROM(duh) since I am in a pretty good mood today so....
1.root your device
2 . Download your preferred ROM
3.flash your ROM
4.IMPORTANT!!!find your boot. img extracting it from the rom you downloaded
5.go to fastboot
6. connect your phone to computer
7.open CMD
8.cd to our directory(ensure you have adb and fastboot first)
9.
Code:
fastboot erase boot
10
Code:
fastboot boot boot. img
11.reboot and enjoy
Sent from my supercharged :tank:

1.root your device - not needed if he is going to flash a Custom. They are all rooted anyway. I think step 1 should be: flash a custom recovery
...
10
Code:
fastboot boot boot. img
- this will boot the kernel only, but after a restart of the device it will be gone. The command to use is :
Code:
fastboot flash boot boot.img
11.reboot and enjoy - that is all right

hisname said:
seems like you still have not read the index.... You need root to flash a custom ROM(duh) since I am in a pretty good mood today so....
1.root your device
2 . Download your preferred ROM
3.flash your ROM
4.IMPORTANT!!!find your boot. img extracting it from the rom you downloaded
5.go to fastboot
6. connect your phone to computer
7.open CMD
8.cd to our directory(ensure you have adb and fastboot first)
9.
Code:
fastboot erase boot
10
Code:
fastboot boot boot. img
11.reboot and enjoy
Sent from my supercharged :tank:
Click to expand...
Click to collapse
Thanks before
Now i have read the index, i found many tutorials to root my device there. i followed some.
but i have a problems when i want to root my device, i tried using SuperOneClick apps. I have done every single requirements of that tutorial.
The problem is i think my device is still not rooted. The first time i used SuperOneClick it shows finished & OK, then i reboot my device.
and then i tried to install some apps that needs rooted device, but those apps tell me that my device isn't rooted!
I tried to root my device using SuperOneClick again, but it always stuck in step #7 (Wait for Device).
any solutions for this problems?
Did i missed something to do?

amidabuddha said:
1.root your device - not needed if he is going to flash a Custom. They are all rooted anyway. I think step 1 should be: flash a custom recovery
...
10
Code:
fastboot boot boot. img
- this will boot the kernel only, but after a restart of the device it will be gone. The command to use is :
Code:
fastboot flash boot boot.img
11.reboot and enjoy - that is all right
Click to expand...
Click to collapse
he already has a custom recovery by revolutionary
Sent from my supercharged :tank:
edit: look here
http://forum.xda-developers.com/showthread.php?t=1525100

hisname said:
he already has a custom recovery by revolutionary
Click to expand...
Click to collapse
Well this is pretty outdated.
The attached is the latest 4EXT Recovery, touch edition.
Extract the recovery.img from the zip and flash:
Code:
fastboot flash recovery recovery.img
Then from the bootloader menu reboot to recovery and select backup/restore -> Backup. After the backup is done go back to the main menu, select wipe/format -> Wipe all partitions (except SDcard). When done select Install zip from the main menu and flash the ROM from your sdcard. After that reboot to bootloader from the Power menu and flash the boot.img as described in my previous post

amidabuddha said:
Well this is pretty outdated
Click to expand...
Click to collapse
true, but at least it is still usable till he gets 4ext or something later....
Sent from my supercharged :tank:

@zidane_argun
see my previous post

hisname said:
true, but at least it is still usable till he gets 4ext or something later....
Sent from my supercharged :tank:
Click to expand...
Click to collapse
amidabuddha said:
@zidane_argun
see my previous post
Click to expand...
Click to collapse
okay okay, roger that!
i will try that, thank you bro amidabuddha & hisname :good::good:
brb..

just realised that even my 4ext recovery is also outdated, thanks for the post :thumbup:
Sent from my supercharged :tank:

lol was trying to reply to your pm. don't know if they went through as they don't show up in my "sent item".
anyway you've got plenty of tips from the folks. so happy flashing

ContactFront said:
lol was trying to reply to your pm. don't know if they went through as they don't show up in my "sent item".
anyway you've got plenty of tips from the folks. so happy flashing
Click to expand...
Click to collapse
haha.. thanks to you too bro! now i'm trying to flash EXT4 first since they (the folks ) said that mine is pretty outdated.. LOL
after that, i want to search which rom is the best one for my Desire S.. do you have any idea which one is best ROM that i have to try?
Sent from my Anvyn Desire S. Powered by XDA Developers

zidane_argun said:
haha.. thanks to you too bro! now i'm trying to flash EXT4 first since they (the folks ) said that mine is pretty outdated.. LOL
after that, i want to search which rom is the best one for my Desire S.. do you have any idea which one is best ROM that i have to try?
Sent from my Anvyn Desire S. Powered by XDA Developers
Click to expand...
Click to collapse
there is really no "best" rom. it's all down to your personal preference.
say, I'm a big cm/aosp fan but if you are a sense fanboy then you may not like aosp based rom at all.
so if you see something interesting then just go ahead give it a try and decide for yourself.
---------- Post added at 09:37 AM ---------- Previous post was at 09:30 AM ----------
oh and speaking of 4ext recovery, i'd recommend installing either the free version updater or purchasing the full version from google play.
http://4ext.net/
it's absolutely worth it. one of the best recoverys you can have

[Q] I need the straight poop on flashing a custom ROM

Before I get flamed, let me say that I have done ALOT of research on the questions I am about to ask, and the fact of the matter that there is a lot of conflicting information out there. So please bear with me.
I am on a rooted phone, Android 4.1.1, Sense 4+, 3.18.502.6 radio, kernal version 3.4.10
Rooted with S-on
So here's my questions:
1. Can I install a custom rom with S-on?
2. If the answer is yes, can someone give me the quick run-down, or at the very least point me in the direction of another thread that I can refer to?
3. I have read conflicting threads that claim that with S-on, I need to flash the boot.img first, other threads say just go ahead and flash the ROM
Some of these threads are 30+ pages long and go back to 2012. If you miss one post in the thread then you're screwed. Any help is appreciated. For the record these forums have been extremely helpful. Successfully rooted two phones in the past year. I understand the rooting very, flashing custom roms gives me the willies.

First thing, why not just s-off and solve your problems? It's super simple. http://forum.xda-developers.com/showthread.php?t=2155071
But the answer is... Sometimes. Sometimes you need to flash the boot.img. If you're unsure, just do it anyways. This can be done by
1. Extracting the boot.img from the ROM zip archive you wish to flash.
2. Placing it in your adb working directory.
3. Enter fastboot on your phone.
4. fastboot flash boot boot.img
Sent from my HTC One X using Tapatalk 4

RollTribe said:
First thing, why not just s-off and solve your problems? It's super simple. http://forum.xda-developers.com/showthread.php?t=2155071
But the answer is... Sometimes. Sometimes you need to flash the boot.img. If you're unsure, just do it anyways. This can be done by
1. Extracting the boot.img from the ROM zip archive you wish to flash.
2. Placing it in your adb working directory.
3. Enter fastboot on your phone.
4. fastboot flash boot boot.img
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
Thanks Man! I'll give the S-off a shot. I'll take your advice and just flasht he boot.img, just to be on the safe side
I am thinking about flashing the CleanRom, unless anyone has any other suggestions

Fivetenfrank said:
Thanks Man! I'll give the S-off a shot. I'll take your advice and just flasht he boot.img, just to be on the safe side
I am thinking about flashing the CleanRom, unless anyone has any other suggestions
Click to expand...
Click to collapse
If you're s-off there's no need to flash boot.img.
Sent from my HTC One X using Tapatalk 4

RollTribe said:
If you're s-off there's no need to flash boot.img.
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
Thanks. One last question. Ok maybe not the last one but one more question regardless.
With custom roms, does the rom need to be based on the same firmware that's on my stock phone? I other words, right now my phone has build 3.18.502.6. I found a rom that I really like that's based on 3.8.402.1. Is that custom rom compatible with my phone?

Fivetenfrank said:
3. I have read conflicting threads that claim that with S-on, I need to flash the boot.img first, other threads say just go ahead and flash the ROM
Click to expand...
Click to collapse
The short (and incomplete) answer is that "it depends".
If you are s-on and hboot 1.14 or higher, you need to flash boot.img separately using fastboot. A few ROMs (ViperXL, some versions of CleanROM) will flash boot.img in the AROMA installer. But most will not.
Failure to do so will mean the kernel for the custom ROM is not flashed, and you will likely bootloop or be stuck on the boot screen.
Another option, as already mentioned, is to get S-off. But be aware that S-off means that all security checks are bypassed. Meaning you can flash lots of things, with security checks bypassed. Sometimes this is good, sometimes it can be really bad.
---------- Post added at 09:35 AM ---------- Previous post was at 09:29 AM ----------
Fivetenfrank said:
With custom roms, does the rom need to be based on the same firmware that's on my stock phone?
Click to expand...
Click to collapse
Typically no.
There are some exceptions. For instance, if you did OTA or RUU to get on the 3.18 stock ROM, the touch panel firmware was upgraded, and AOSP ROMs will not work right (no touch functions). The solution is to have S-off and downgrade the touch panel firmware.
Fivetenfrank said:
right now my phone has build 3.18.502.6. I found a rom that I really like that's based on 3.8.402.1. Is that custom rom compatible with my phone?
Click to expand...
Click to collapse
Link the ROM, and I can probably answer that for you pretty easily.

Notills his
redpoint73 said:
The short (and incomplete) answer is that "it depends".
If you are s-on and hboot 1.14 or higher, you need to flash boot.img separately using fastboot. A few ROMs (ViperXL, some versions of CleanROM) will flash boot.img in the AROMA installer. But most will not.
Failure to do so will mean the kernel for the custom ROM is not flashed, and you will likely bootloop or be stuck on the boot screen.
Another option, as already mentioned, is to get S-off. But be aware that S-off means that all security checks are bypassed. Meaning you can flash lots of things, with security checks bypassed. Sometimes this is good, sometimes it can be really bad.
---------- Post added at 09:35 AM ---------- Previous post was at 09:29 AM ----------
Typically no.
There are some exceptions. For instance, if you did OTA or RUU to get on the 3.18 stock ROM, the touch panel firmware was upgraded, and AOSP ROMs will not work right (no touch functions). The solution is to have S-off and downgrade the touch panel firmware.
Link the ROM, and I can probably answer that for you pretty easily.
Click to expand...
Click to collapse
It won't link to the rom because XDA won't let me because I am a new user. It's Scott's CleanRom version 6.5. It says its built on the 3.17 OTA build
My phone is a week old. It stock with 4.1.1 and 3.18.502.6. No OTA updates happening here. So can I assume the touchpanel firmware will NOT be an issue since 3.18 is stock?
And I'm not going to mess with S-off. Ill stick with S-on for now.

You should be fine to flash it. Like redpoint said, you may have to flash the boot.img. I can't remember whether CR6.5 flashes the boot.img for you or not. To be on the safe side, go ahead and flash it.

Fivetenfrank said:
It won't link to the rom because XDA won't let me because I am a new user. It's Scott's CleanRom version 6.5. It says its built on the 3.17 OTA build
Click to expand...
Click to collapse
Fair enough. CR6.5 will work great. One thing to note however, recent versions of TWRP (2.4 and 2.5) are known to be problematic and will not work with CR6.5. Either use an older TWRP (2.3) or use the official CWM.
Fivetenfrank said:
My phone is a week old. It stock with 4.1.1 and 3.18.502.6. No OTA updates happening here. So can I assume the touchpanel firmware will NOT be an issue since 3.18 is stock?
.
Click to expand...
Click to collapse
That would be the incorrect assumption. Since the phone came out of the box with 3.18, it will have the upgraded touch panel firmware. Meaning AOSP ROMs will not have a functional touch screen, unless you S-off and downgrade the touch panel firmware.
For Sense ROMs, its doesn't matter, you are fine with the upgraded touch panel firmware.
BTW, please hit the "Thanks" button for any posts that you found helpful!

redpoint73 said:
Fair enough. CR6.5 will work great. One thing to note however, recent versions of TWRP (2.4 and 2.5) are known to be problematic and will not work with CR6.5. Either use an older TWRP (2.3) or use the official CWM.
That would be the incorrect assumption. Since the phone came out of the box with 3.18, it will have the upgraded touch panel firmware. Meaning AOSP ROMs will not have a functional touch screen, unless you S-off and downgrade the touch panel firmware.
For Sense ROMs, its doesn't matter, you are fine with the upgraded touch panel firmware.
BTW, please hit the "Thanks" button for any posts that you found helpful!
Click to expand...
Click to collapse
I think I am in good shape. CleanRom is built on Sense. Ill flash the boot.img first to be on the safe side. Btw according to Scott's website for this Rom, with respect to TWRP vs CWM, this is what he says:
"Must have TWRP Recovery installed with unlocked bootloader! CWM Recovery not supported!" Can I get a clarification?
Once this is all done ill post and let everyone know how I made out. Going back now and "thanking" all who have replied

Fivetenfrank said:
I think I am in good shape. CleanRom is built on Sense. Ill flash the boot.img first to be on the safe side.
Click to expand...
Click to collapse
Since your phone is on 3.18, and CleanROM is 3.17 base, I don't know if you can be completely sure there haven't been kernel changes. You're right, it might be the same (or same enough) kernel, but to be on the safe side, it won't hurt to flash the boot.img.
Fivetenfrank said:
Btw according to Scott's website for this Rom, with respect to TWRP vs CWM, this is what he says:
"Must have TWRP Recovery installed with unlocked bootloader! CWM Recovery not supported!" Can I get a clarification?
Click to expand...
Click to collapse
Its an outdated statement. There was a time where CWM was only a unofficial (somewhat hacked) port, and caused some serious issues for some people, that then wrongly blamed scrosler and his ROM.
None of this is very relevant any longer. CWM is officially supported for our device. It works great with CleanROM 6.5 (its what I'm currently using); when I will guarantee you that the latest TWRP 2.5.0.0 will not work with CleanROM 6.5. And anything after TWRP 2.3.1.1 is known to be problematic for our device. So its really up to you, which recovery is the best to use.
If you pick CWM, this is the thread you want:
http://forum.xda-developers.com/showthread.php?t=2148909

redpoint73 said:
Since your phone is on 3.18, and CleanROM is 3.17 base, I don't know if you can be completely sure there haven't been kernel changes. You're right, it might be the same (or same enough) kernel, but to be on the safe side, it won't hurt to flash the boot.img.
Its an outdated statement. There was a time where CWM was only a unofficial (somewhat hacked) port, and caused some serious issues for some people, that then wrongly blamed scrosler and his ROM.
None of this is very relevant any longer. CWM is officially supported for our device. It works great with CleanROM 6.5 (its what I'm currently using); when I will guarantee you that the latest TWRP 2.5.0.0 will not work with CleanROM 6.5. And anything after TWRP 2.3.1.1 is known to be problematic for our device. So its really up to you, which recovery is the best to use.
If you pick CWM, this is the thread you want:
http://forum.xda-developers.com/showthread.php?t=2148909
Click to expand...
Click to collapse
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?

Fivetenfrank said:
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?
Click to expand...
Click to collapse
You don't have to remove TWRP. Just flash over the top of it with CWM.

Egrier said:
You don't have to remove TWRP. Just flash over the top of it with CWM.
Click to expand...
Click to collapse
Got it. Wish me me luck fellas. I am going to give this a whirl tonight
Hey while I have everyone's attention, are there any other roms out there worth checking out for someone like me? That's probably a loaded question given the fact that theres a boat load of Roms out there... but all opinions welcomed!

Fivetenfrank said:
Ok so noted. CWM is the way to go. So next question. How complicated is the process to remove TWRP before I flash CWM?
Click to expand...
Click to collapse
Just for the record, I'm not saying that CWM is necessarily better. Either CWM, or TWRP 2.3.1.1. Your choice. But TWRP 2.5 definitely does not work with CleanROM 6.5, and TWRP 2.4 has issues, also.
As already mentioned, no need to remove TWRP. Just flash CWM, and TWRP will be removed.
---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------
Fivetenfrank said:
Hey while I have everyone's attention, are there any other roms out there worth checking out for someone like me? That's probably a loaded question given the fact that theres a boat load of Roms out there... but all opinions welcomed!
Click to expand...
Click to collapse
Yes, that is a loaded question. They are all worth checking out! To suggest one (or a few), would suggest the others are somehow "not worth" checking out. Which is really not fair to the devs that have worked so hard to give us these ROMs.
Look through the ROMs, and if any look interesting, try them. This is what most of us do. You already mentioned you aren't going to s-off yet, so the AOSP ROMs are out (due to the touch panel firmware issue).

redpoint73 said:
Just for the record, I'm not saying that CWM is necessarily better. Either CWM, or TWRP 2.3.1.1. Your choice. But TWRP 2.5 definitely does not work with CleanROM 6.5, and TWRP 2.4 has issues, also.
As already mentioned, no need to remove TWRP. Just flash CWM, and TWRP will be removed.
---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------
Yes, that is a loaded question. They are all worth checking out! To suggest one (or a few), would suggest the others are somehow "not worth" checking out. Which is really not fair to the devs that have worked so hard to give us these ROMs.
Look through the ROMs, and if any look interesting, try them. This is what most of us do. You already mentioned you aren't going to s-off yet, so the AOSP ROMs are out (due to the touch panel firmware issue).
Click to expand...
Click to collapse
Yep, AOSPs are out. Thanks for all of your help everyone. Going to try this tonight. Hopefully I wont have a paperweight by this time tomorrow

Fivetenfrank said:
Yep, AOSPs are out. Thanks for all of your help everyone. Going to try this tonight. Hopefully I wont have a paperweight by this time tomorrow
Click to expand...
Click to collapse
Go slow follow directions and your phone will be fine. Don't skip steps or shortcut anything. That's where problems arise.
Sent from my HTC One XL using xda premium

also inpensi
31ken31 said:
Go slow follow directions and your phone will be fine. Don't skip steps or shortcut anything. That's where problems arise.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thanks for the heads up. I am good on the instructions. I have found a multitude of posts outlining the steps. My biggest fear is/was the compatibility issue - flashing a rom that's not compatible with my phone. I tried flashing a Rom a couple of months ago on an HTC One X on 2.20, and I bricked it. I flashed the wrong Rom. Luckily AT&T didnt catch it and they gave me a new phone. I had to get another new phone this week past because my old HTC One X died for some unknown reason. AT&T gave me another one on warranty. This new one has the 3.18

Sounds like you flashed a ROM for the quad core "international" version (ENDEAVORU). Stick to this forum (says "AT&T" at the top) and any ROM you flash will be fine.
Or use my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237

redpoint73 said:
Sounds like you flashed a ROM for the quad core "international" version (ENDEAVORU). Stick to this forum (says "AT&T" at the top) and any ROM you flash will be fine.
Or use my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
If my memory serves me correctly, that's exactly what I did.

[Q] Phone Noob Needs a Hand! :)

Hello everyone,
I have used you guys in the past for other devices but never needed serious help, so here I am stuck in a looping hell
I have an HTC One X that I am trying to root and install the TWRP (I want to have an android that is factory set without the carrier info and bloatware ect)
The utility I am using is the HTC One X (Tegra 3/International) AIO Kit By Hasoon2000 v2.5. Here is my main issue:
I have successfully navigated all the steps to root the phone (Steps 1-5) and now when I boot into the bootloader I see the following,
***TAMPERED***
*** UNLOCKED ***
evita pvt ship s-on rl
hboot-2.14.0000
radio-0.23a.32.09.29
opendsp-v31.1.0.45.0815
emmc-boot
nov 26 2012,18:37:14:-1
Now from here it was my understanding that under "next, flash a recovery" I would simply pick "TWRP" and then click "flash recovery". This seems to work as the green bar in the top right loads briefly. After that I am at a loss. If I go to "bootloader" then go to "recovery" like the instructions say the phone just restarts and I see the Rogers splash screen again...
If it helps, when I try to flash the recovery using the "clockwordmod" it gives me an error "cannot load recoveries/cwm.img"
So to make this easier all I want is my phone to have nothing to do with the carrier on it, all traces of that wiped off at the single file level if possible.
Any help would be greatly appreciated as I have been at this for almost 6 hours straight

The phone is boot looping because you don't have a tegra3 international one x. You have the evita (one xl). Stop what your doing i will post you a link with correct software in a minute.
Read this and then try again.
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One XL using xda premium

You're using the wrong toolkit, the Tegra 3/International is the Endeavor. You have the Evita, which is why it says Evita in your bootloader. You can flash TWRP 2.6 by following the below steps:
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and flash a custom ROM. You've been looking in the wrong forum, that's how your ended up with the toolkit for the wrong device. So always stay in this forum (the one you've posted in), and only ever download ROMs from here for Sense based ROMs or here for aosp ROMs. Don't ever download from a different forum or a different site. That leads to bricked phones.
Oh, and next time, do some more reading before you attempt to alter your phone, you're lucky you didn't brick it. It pays to spend 12 hours reading before trying anything, rather than spending 6 hours trying to fix a mistake because you didn't have the necessary understanding of what you were doing in the first place.
Sent from my Evita
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
31ken31 said:
The phone is boot looping because you don't have a tegra3 international one x. You have the evita (one xl). Stop what your doing i will post you a link with correct software in a minute.
Read this and then try again.
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ninja!
Sent from my Evita

timmaaa said:
You're using the wrong toolkit, the Tegra 3/International is the Endeavor. You have the Evita, which is why it says Evita in your bootloader. You can flash TWRP 2.6 by following the below steps:
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and flash a custom ROM. You've been looking in the wrong forum, that's how your ended up with the toolkit for the wrong device. So always stay in this forum (the one you've posted in), and only ever download ROMs from here for Sense based ROMs or here for aosp ROMs. Don't ever download from a different forum or a different site. That leads to bricked phones.
Oh, and next time, do some more reading before you attempt to alter your phone, you're lucky you didn't brick it. It pays to spend 12 hours reading before trying anything, rather than spending 6 hours trying to fix a mistake because you didn't have the necessary understanding of what you were doing in the first place.
Sent from my Evita
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
Ninja!
Sent from my Evita
Click to expand...
Click to collapse
you guys are amazing.... im going to try this now... I hope its not too late because I just noticed that I have no network connection to the provider and no signal I will update as soon as im done

WOW its working.... I cant believe its that easy lol....
On a side note I am in the screen that has install/wipe/backup ect.... so I am kinda lost on what to do from here. When I go to install it has a folder view of the internal phone. Is there something else I need to do to have it boot normally?

If you want to keep the stock ROM but have root, you'll need to download a superuser zip and flash that using the install menu in recovery. Wipe cache and dalvik cache afterwards.
Sent from my Evita

timmaaa said:
If you want to keep the stock ROM but have root, you'll need to download a superuser zip and flash that using the install menu in recovery. Wipe cache and dalvik cache afterwards.
Sent from my Evita
Click to expand...
Click to collapse
Do I need to download superuser.zip from somewhere special or does it matter?
As an update when I try to open up SuperSU it says "The SU binary needs to be updated. Continue?" I select continue and it gives me two choices, either "normal" or twrp/cwm"
I clicked twrp/cwm and it just restarts my phone to the recovery mode and I don't know where to go from there.
(I hate asking so many questions, is there a how-to for the recovery that I just installed? I am hunting around and cant find much)
UPDATE: I have successfully installed super user and everything is good to go, the only thing im still struggling with is the superuser.zip to set the phone to factory settings and get rid of all the providers bloatware/splashscreen ect

Ok, so you've already got a ROM on there with superuser? You can just try the normal method of updating instead of recovery method.
Sent from my Evita

inisings very
timmaaa said:
Ok, so you've already got a ROM on there with superuser? You can just try the normal method of updating instead of recovery method.
Sent from my Evita
Click to expand...
Click to collapse
I have the TWRP Recovery installed and also now have on my phone SuperSU installed, the only thing now is to figure out where I download a ROM to wipe out the cell providers bloatware and splash screens ect, I just want an "android" phone with nothing else on it lol

If you want to keep the stock ROM, you can use an app called Titanium Backup to remove bloatware. Or you can go to either of the development sections I listed before to find a ROM you think might suit you.
Sent from my Evita

timmaaa said:
If you want to keep the stock ROM, you can use an app called Titanium Backup to remove bloatware. Or you can go to either of the development sections I listed before to find a ROM you think might suit you.
Sent from my Evita
Click to expand...
Click to collapse
Yea I bought awhile ago titanium backup pro so I will use that for the bloatware, and as for the ROMS that you listed you mentioned Sense based ROMs or aosp ROMs... what is the difference? Is there one I should use over the other?

It really comes down to personal choice. Sense ROMs are what is installed on the phone when you buy it, they contain the HTC Sense UI.
Aosp ROMs are pure android, if you've ever seen a Nexus phone, that's essentially what it looks like. Aosp ROMs are generally a bit snappier.
There are some really good ROMs in both categories. The devs for our device do an outstanding job. I'm fond of both types of ROM. But, right now I'm using MagioRom, I've always disliked Sense ROMs but this one is Sense 5 and it looks a lot better than previous Sense versions, and is nice and smooth with great battery life.
Sent from my Evita

timmaaa said:
It really comes down to personal choice. Sense ROMs are what is installed on the phone when you buy it, they contain the HTC Sense UI.
Aosp ROMs are pure android, if you've ever seen a Nexus phone, that's essentially what it looks like. Aosp ROMs are generally a bit snappier.
There are some really good ROMs in both categories. The devs for our device do an outstanding job. I'm fond of both types of ROM. But, right now I'm using MagioRom, I've always disliked Sense ROMs but this one is Sense 5 and it looks a lot better than previous Sense versions, and is nice and smooth with great battery life.
Sent from my Evita
Click to expand...
Click to collapse
very interesting... I am a huge minimalistic fan... greys and whites are nice too... I appreciate all the help you have given me and I told my buddies who are jumping on the android bandwagon to come to this site...
is there anything special I need to do to install the ROMs? I assume there will be a guide in those links (at work cant view them yet)

jlambe7 said:
very interesting... I am a huge minimalistic fan... greys and whites are nice too... I appreciate all the help you have given me and I told my buddies who are jumping on the android bandwagon to come to this site...
is there anything special I need to do to install the ROMs? I assume there will be a guide in those links (at work cant view them yet)
Click to expand...
Click to collapse
If you like minimalistic, then aosp is probably the way to go for you. If your buddies are gonna get into modding their phones, I have some golden advice: read, read, read, and read some more before attempting anything. Modding is not hard if you know what you're doing, but it it's very easy to turn your phone into a paperweight if you rush in. Also, only ever get information and software from XDA, other sites don't properly distinguish between our model (HTC One XL/Evita) and the HTC One X (Endeavor).
In terms of installing, it's pretty simple:
1: Make a backup of your current setup using the backup function in recovery. That way if something goes wrong, you can restore it and have a working OS.
2: Perform a full wipe (cache/dalvik/factory reset/system).
3: Install the ROM using the install function. Aosp ROMs also require you to install a gapps package specific to the Android version of the ROM (4.1/4.2). Sense ROMs don't require this step.
4. You are s-on (security on) so you need to flash the boot.img for each ROM manually. Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita