Database Info

[Q] Question on Flashing a Rom

Hello, recently i've just rooted my htc one s, s4. I stalled for a bit and had the 4.0.4 update already, so currently I have root access with the stock firmware. I'm looking through the rom list and the viper One s room caught my eye. So my question is, are there any prerequisite requirements before i flash this rom. Sorry for such a ridiculous question, but i havn't flashed a rom since the G1 and I remember having to flash certain kernels for certain roms. I still haven't messed with the kernel yet so that's stock too.
_________________________________________________________
My One S is s4 t-mobile, TWRP recovery, obtained root access with the All in One Toolkit v3.0 by hasoon2000. firmware is stock update 4.0.4 and everything else is just stock. so all i did was root

Just follow the instructions in the Viper Thread.
Since you have it rooted (and I assume a working recovery) you should already have all tools needed (fastboot etc).

On the Working Recovery, I would recommend installing TWRP. Best recovery atm for rom flashing. Get it thru the Goo Manager App on PlayStore. Just open Goo Manager then open Menu and tap on Install OpenScript Recovery.
Read OP pages carefully and scan the threads of the rom you want to flash. Depending on your hboot version, you may have to fastboot boot.img right after flashing rom. If at or above .13. Or, get Flash Image GUI from PlayStore and it will do it for you.
On CM roms there are some other quirks with radio etc, so some pre-study would be advised as well as nandroiding and backing up sdcard first. Put both backups on PC for extra safety.
Good Luck--

rugmankc said:
On the Working Recovery, I would recommend installing TWRP. Best recovery atm for rom flashing. Get it thru the Goo Manager App on PlayStore. Just open Goo Manager then open Menu and tap on Install OpenScript Recovery.
Read OP pages carefully and scan the threads of the rom you want to flash. Depending on your hboot version, you may have to fastboot boot.img right after flashing rom. If at or above .13. Or, get Flash Image GUI from PlayStore and it will do it for you.
On CM roms there are some other quirks with radio etc, so some pre-study would be advised as well as nandroiding and backing up sdcard first. Put both backups on PC for extra safety.
Good Luck--
Click to expand...
Click to collapse
Thanks! i went ahead and flashed viper rom and after reading a bit i noticed that i had hboot .14 so it broke my wifi . I'm still currently searching info and came across that i need linux to downgrade, which i don't have . do you know any other method? or roms beside trickdroid 7 that support the hboot version and allow wifi?

On .14 the items I mentioned will apply on all roms
Not sure on wifi, i use mostly cm roms atm

Im on Hboot .14, and wifi works fine for me on viperS

there is a wifi partition zip floating around for wifi issues. didn't pay much attn to it as i have no issues--maybe a search, or someone will post it

[Q] 1.85 rooted to scottsrom JB rooted

Ok, I know this is probably already all documented somewhere, but the problem is, there is also lots of out of date info, and I'm not sure how to tell which info is current, and which isn't. This is my first Android phone, so I'm not completely up to speed on the meanings of everything.
I have an AT&T (evita) HOX. Its on 1.8.5 stock, and is rooted. I also set supercid some time ago, in preparation for unlocking it. I didn't proceed with the unlock at that time because I wasn't yet comfortable that everything I wanted backed up was backed up, and everything said unlock would wipe all user data.
I believe I have backup under control now, and I'd like to get to where I can put the "Scottsroms" rooted JB on, and do whatever I need to ensure that I can keep root. I want to stay as close to stock as possible, but with root, and that seems to be the best path for that.
I've been doing a bit of reading (including stuff linked from the rollup thread) and I have some questions I haven't been able to answer.
- Do I need to unlock the BL in order to get S-off? Or, if I S-off, do I not need to unlock the bootloader?
- I see the note about htc blocking supercid unlocking and using all 2's instead - is this still valid?
- I had read CWM didn't support this phone, but now I see something that contradicts that.
Basically, while I understand that there are no guarantees, I'd like to at least avoid doing things that are KNOWN not to work.
FWIW, I am a long time linux user. I have the Android sdk installed with adb and fastboot programs... I'm very comfortable at the command line.
If anyone can suggest what the recommended procedure is, which steps I need, which I should avoid, which info is current, which is out of date, I'd be very thankful.
If more info from me is needed, just let me know...

Megadave123 said:
Ok, I know this is probably already all documented somewhere, but the problem is, there is also lots of out of date info, and I'm not sure how to tell which info is current, and which isn't. This is my first Android phone, so I'm not completely up to speed on the meanings of everything.
I have an AT&T (evita) HOX. Its on 1.8.5 stock, and is rooted. I also set supercid some time ago, in preparation for unlocking it. I didn't proceed with the unlock at that time because I wasn't yet comfortable that everything I wanted backed up was backed up, and everything said unlock would wipe all user data.
I believe I have backup under control now, and I'd like to get to where I can put the "Scottsroms" rooted JB on, and do whatever I need to ensure that I can keep root. I want to stay as close to stock as possible, but with root, and that seems to be the best path for that.
I've been doing a bit of reading (including stuff linked from the rollup thread) and I have some questions I haven't been able to answer.
- Do I need to unlock the BL in order to get S-off? Or, if I S-off, do I not need to unlock the bootloader?
- I see the note about htc blocking supercid unlocking and using all 2's instead - is this still valid?
- I had read CWM didn't support this phone, but now I see something that contradicts that.
Basically, while I understand that there are no guarantees, I'd like to at least avoid doing things that are KNOWN not to work.
FWIW, I am a long time linux user. I have the Android sdk installed with adb and fastboot programs... I'm very comfortable at the command line.
If anyone can suggest what the recommended procedure is, which steps I need, which I should avoid, which info is current, which is out of date, I'd be very thankful.
If more info from me is needed, just let me know...
Click to expand...
Click to collapse
Finish unlocking bootloader
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Backup your current Rom via recovery.
Copy Rom of choice to sd card
Wipe everything except sd card. Wipe cache,dalvik, system, factory reset.
Flash Rom.
If you are on hboot 1.14 or higher you will need to extract boot.img from Rom.zip and flash via fastboot, flash boot boot.img
Good luck
Sent from my HTC One X using xda app-developers app

31ken31 said:
Finish unlocking bootloader
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Backup your current Rom via recovery.
Copy Rom of choice to sd card
Wipe everything but sd card, cache,dalvik, system, factory reset.
Flash Rom. If you are on hboot 1.14 or higher you will need to extract boot.img from Rom.zip and flash via fastboot, flash boot boot.img
Good luck
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Regarding unlocking - can I do it with supercid set, or do I need to change to all 2's ?
Should I do s-off?
I'm on whatever versions of everything are stock for a device shipped with 1.85 - ok, the bootloader screen says hboot is 1.09.0000
I'll search around but are there docs on the specific steps for flashing roms?
BTW, thanks for the quick reply...

Hit install from recovery pick Rom and flash.. don't worry about s-off being on hboot 1.09 u can flash whatever from recovery. Htcdev has 1111111 blocked I think if it is use all 2's
Sent from my HTC One X using xda app-developers app

FWIW supercid seemed to work for unlock just fine...

31ken31 said:
Flash recovery twrp 2.3.3.1 or lower being higher versions have mount and wipe bugs.
Click to expand...
Click to collapse
Ok, looking for a bit of an expansion on this, and possibly some second opinions?
Looks like TWRP is up to 2.5.0.0 now, and the changelog shows a number of bugfixes since 2.3.x
Goomanager puts 2.5.0.0 on by default, I installed ROM Manager and it puts CWM..
The rollup page on the HOX says CWM officially supports it now..
The ROM I want says CWM "not supported" - I'm wondering if that is a holdover from when CWM didnt support HOX..

Megadave123 said:
Ok, looking for a bit of an expansion on this, and possibly some second opinions?
Looks like TWRP is up to 2.5.0.0 now, and the changelog shows a number of bugfixes since 2.3.x
Goomanager puts 2.5.0.0 on by default, I installed ROM Manager and it puts CWM..
The rollup page on the HOX says CWM officially supports it now..
The ROM I want says CWM "not supported" - I'm wondering if that is a holdover from when CWM didnt support HOX..
Click to expand...
Click to collapse
It's says bugs fixed but it's not fixed.. I don't recommend cwm for this device. Go to twrp website and download 2.3.3.1 and flash it
Sent from my HTC One X using xda app-developers app

[Q] Htc One X Unique problem

So as a n00b, I posted in the wrong forum earlier, lol
Anyways , long story short, htc one x evita, unlocked bootloader, tampered, rooted, will not flash past htc splash screen, when I try to restore, it does nothing, when going into folders there is NOTHING there, so random, I did clear my caches as instructed, maybe I am n00bish and deleted the wrong things, I can read the phone in adb, will go into teamwin screen,
REgardless, If I can get this fixed, I will not be messing with it again, lol(as all noobs say)
IS there anything I can do at this point before I throw my hands in the air and throw my phone at a wall?

Far from unique. It's possible that you've accidentally wiped the sd at some point, or did you possibly do a factory reset from the bootloader? Why haven't you just copied a ROM to the device to flash?
Sent from my Evita

timmaaa said:
Far from unique. It's possible that you've accidentally wiped the sd at some point, or did you possibly do a factory reset from the bootloader? Why haven't you just copied a ROM to the device to flash?
Sent from my Evita
Click to expand...
Click to collapse
HI, I may have wiped the sd, let's say sure to this..lol..
I have tried to copy a rom, I had Viper somewhat load, then it flashes back to htc splash, then to twrp,
Any insite to one that may possibly work?(the others will not load at all, they all fail install)

I need a bit more background on the device, please post your bootloader details (the first five lines). What TWRP version are you using? What had you done to the device directly before encountering this problem?
When you say you had Viper somewhat load what do you mean? Did it boot into the ROM at all? Or did it only boot as far as the Viper boot animation? Or did it only make it as far as the HTC splash screen?
I can't really say what's going to work until we figure out exactly what's wrong. Make sure you answer all the above questions with as much relevant detail as possible and we'll see if we can sort it out.
Sent from my Evita

timmaaa said:
I need a bit more background on the device, please post your bootloader details (the first five lines). What TWRP version are you using? What had you done to the device directly before encountering this problem?
When you say you had Viper somewhat load what do you mean? Did it boot into the ROM at all? Or did it only boot as far as the Viper boot animation? Or did it only make it as far as the HTC splash screen?
I can't really say what's going to work until we figure out exactly what's wrong. Make sure you answer all the above questions with as much relevant detail as possible and we'll see if we can sort it out.
Sent from my Evita
Click to expand...
Click to collapse
First off, thank you for your prompt replies
Venom loaded splash screen, then reboot to htc splash with the red developer on the bottom
twrp is the newest one
first 5 lines are you meaning?
*** TAMPERED ****
*** UNLOCKED ****
Evita put ship s-on rl
hboot-2.14.0000
radio-0.23a.32.09.29
??
Well I tried to load the stock RUU from rogers, (ota one)
then after rooting,unlocking bootloader, I tried to load a custom rom(slimkat IIRC)
then IT shut down, I left it for the night, and then nothing, so I tried to install slimkat again, nothing, so I tried venom, and I had the splash screen for the rom, now I am basically back at square one, nothing lol

Yes those are the bootloader details I needed. When you say the latest TWRP I'm assuming you mean 2.6.3.0? There are two versions of 2.6.3.0, the official version and the modified version.
Official version
Can flash any ROM except 4.4 ROMs. If you're using this one it is why SlimKat (plus any other 4.4 ROM) is failing to install.
Modified version
This is required to flash 4.4 ROMs. It does work on some pre 4.4 ROMs but it doesn't on others.
The most common cause for your current situation to happen is that you've forgotten to flash the boot.img with fastboot. Your phone is s-on, this means that the boot.img is unable to be flashed during the recovery install due to security restrictions on hboots equal to or greater than 1.14. So, make sure you're using the correct recovery for the ROM you want to flash (official 2.6.3.0 for Viper, modified 2.6.3.0 for 4.4 ROMs), and make sure you flash the boot.img with fastboot. I have detailed instructions on how to flash a boot.img in my How-To Guide For Beginners thread, link in my signature.
Do that and report back with how you go.
Sent from my Evita

timmaaa said:
Yes those are the bootloader details I needed. When you say the latest TWRP I'm assuming you mean 2.6.3.0? There are two versions of 2.6.3.0, the official version and the modified version.
Official version
Can flash any ROM except 4.4 ROMs. If you're using this one it is why SlimKat (plus any other 4.4 ROM) is failing to install.
Modified version
This is required to flash 4.4 ROMs. It does work on some pre 4.4 ROMs but it doesn't on others.
The most common cause for your current situation to happen is that you've forgotten to flash the boot.img with fastboot. Your phone is s-on, this means that the boot.img is unable to be flashed during the recovery install due to security restrictions on hboots equal to or greater than 1.14. So, make sure you're using the correct recovery for the ROM you want to flash (official 2.6.3.0 for Viper, modified 2.6.3.0 for 4.4 ROMs), and make sure you flash the boot.img with fastboot. I have detailed instructions on how to flash a boot.img in my How-To Guide For Beginners thread, link in my signature.
Do that and report back with how you go.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so very much, once again with the quick replies and the "dumming" it down for me,
I will try in a little bit, to be honest, im not sure what twrp it is, I know its 2.3.6.0, it was the newest one,
in your instructions is there a way to boot just back to stock rom as well?(my pc is horrible, if I load more then one page it dies off lol) I will try this when I get home in a little bit herre.

I can almost positively say you're on the official version of TWRP, you'd need to go out of your way to find the modified one usually. With your phone in its current state you can't use an RUU to go back to stock. The latest Rogers RUU is older than your current firmware and you can't run an older RUU while s-on. If you made a TWRP backup of your stock ROM before wiping you could restore that backup though.
Your best and easiest option right now is to just flash a ROM. Once you've gotten a custom ROM booted up my guess is you won't want to go back to stock
Once you've gotten a ROM booted you can get s-off on your device which will make life a lot easier for you. It means no more flashing a boot.img, you'll be able to flash radios, you can run any Evita RUU (forwards or backwards, and from any carrier), and more benefits. But for now just concentrate on getting the ROM booting.
I'm assuming you have adb/fastboot installed on your PC already? If not you'll need to do that first, Google search "minimal adb and fastboot", the first result should take you to a thread that can get it done with very little effort.
Sent from my Evita

timmaaa said:
I can almost positively say you're on the official version of TWRP, you'd need to go out of your way to find the modified one usually. With your phone in its current state you can't use an RUU to go back to stock. The latest Rogers RUU is older than your current firmware and you can't run an older RUU while s-on. If you made a TWRP backup of your stock ROM before wiping you could restore that backup though.
Your best and easiest option right now is to just flash a ROM. Once you've gotten a custom ROM booted up my guess is you won't want to go back to stock
Once you've gotten a ROM booted you can get s-off on your device which will make life a lot easier for you. It means no more flashing a boot.img, you'll be able to flash radios, you can run any Evita RUU (forwards or backwards, and from any carrier), and more benefits. But for now just concentrate on getting the ROM booting.
I'm assuming you have adb/fastboot installed on your PC already? If not you'll need to do that first, Google search "minimal adb and fastboot", the first result should take you to a thread that can get it done with very little effort.
Sent from my Evita
Click to expand...
Click to collapse
Yes I have a basic Adb/fastboot setup already, is there a particular rom you recommend?(I will trust your best judgement here) I am home now, I will try and let you know
Thank you again

Asking for a ROM recommendation isn't allowed on XDA so I can't answer that question, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge.
Each user has different tastes anyway. Some people like Sense ROMs, some like aosp ROMs. Personally I'm an aosp guy, aosp ROMs are generally a bit snappier, plus you can run the latest version of Android (Sense ROMs are limited to 4.2.2 for our device). I'd suggest having a look at the ROMs on offer, check out their features and pick one to flash. If you don't end up liking it you can always just flash another, and that's half the fun.
As a side note, getting s-off via Rumrunner s-off seems to work better on Sense ROMs. I know someone very recently got s-off while on the Kickdroid ROM so if you do want to get s-off I'd suggest flashing that ROM purely for the s-off process. You might like it and want to stay on it, if not just flash away.
Sent from my Evita

timmaaa said:
Asking for a ROM recommendation isn't allowed on XDA so I can't answer that question, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge.
Each user has different tastes anyway. Some people like Sense ROMs, some like aosp ROMs. Personally I'm an aosp guy, aosp ROMs are generally a bit snappier, plus you can run the latest version of Android (Sense ROMs are limited to 4.2.2 for our device). I'd suggest having a look at the ROMs on offer, check out their features and pick one to flash. If you don't end up liking it you can always just flash another, and that's half the fun.
As a side note, getting s-off via Rumrunner s-off seems to work better on Sense ROMs. I know someone very recently got s-off while on the Kickdroid ROM so if you do want to get s-off I'd suggest flashing that ROM purely for the s-off process. You might like it and want to stay on it, if not just flash away.
Sent from my Evita
Click to expand...
Click to collapse
I understand and apologize, Never thought of it that way,
Anyways an update, I followed your tutorial, and I am not having much luck here, It still maintains to say NO OS installed (through twrp when rebooting after I do adb and such)
maybe I am missing something ?

Adb or fastboot?
Sent from my Evita

timmaaa said:
Adb or fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Fastboot,
Small update I did manage to get a rootbox rom to load, but its not stable by anymeans...Ugh super frustrated with it

Are you wiping in TWRP before flashing? It's very important to wipe system/factory reset/cache/dalvik cache before installing a ROM. Just never do a factory reset in the bootloader, that'll corrupt your sd card.
Sent from my Evita

timmaaa said:
Are you wiping in TWRP before flashing? It's very important to wipe system/factory reset/cache/dalvik cache before installing a ROM. Just never do a factory reset in the bootloader, that'll corrupt your sd card.
Sent from my Evita
Click to expand...
Click to collapse
Yes to wiping before flashing in TWRP just those ones mentioned, (if you do sd you loose your flash right?), anyways the rom I flashed yesterday was super unstable, just trying a few diff. ones out and trying to find one that will continue to stay working lol!! Your tutorial in your signature is very helpful
thank you so much for all your help,and patience

Yeah you don't want to wipe sd card/internal storage or you'll lose all of your personal data like images, music, ROM zips, backups.
Sent from my Evita

timmaaa said:
Yeah you don't want to wipe sd card/internal storage or you'll lose all of your personal data like images, music, ROM zips, backups.
Sent from my Evita
Click to expand...
Click to collapse
Oh this is a clean phone, I already backed up on pc Before lol
Question though, I installed Viper again(just to try it) and it loads a menu showing ram, one of the memory sections shows -1? is this correct?

On a side note, I got Venom up and running and WOW!!!
once again, a super thank you for your patience and help all along Timmaaa,

I'm not sure what you're talking about, is that after booting into the ROM? Can you show me a screenshot?
Sent from my Evita

timmaaa said:
I'm not sure what you're talking about, is that after booting into the ROM? Can you show me a screenshot?
Sent from my Evita
Click to expand...
Click to collapse
it was while I was installing, everything seems fine, still no wifi(original issue)
im thinking the logic board may be buggered...sad day...lol
But, it is fast as heck now, running venom rom, I will try to get S-off and then maybe try to get it so I can load up the 4.4X roms
Thanks for all the help

[Q] HTC One XL rooting problem

Please Help! I have a HTC One X At&t unlocked phone with lot of issues. I decided to install custom ROM on this phone. I am a newbie in the world of rooting, flashing etc. I follow some directions and I was able to unlock my boot loader then installed twrpv.2.6. I tried to flash one custom rom that I found in web, during flashing twrp give me a message "Your phone is not rooted. You want to flash SuperSu. When I confirm and reboot the system, phone stuck in htc logo screen with white back ground. I guess my phone lacking super user permission. Is there any way I can fix my phone?
I tried to manually put su and other files into this phone but its lacking following directories

menorah said:
Please Help! I have a HTC One X At&t unlocked phone with lot of issues. I decided to install custom ROM on this phone. I am a newbie in the world of rooting, flashing etc. I follow some directions and I was able to unlock my boot loader then installed twrpv.2.6. I tried to flash one custom rom that I found in web, during flashing twrp give me a message "Your phone is not rooted. You want to flash SuperSu. When I confirm and reboot the system, phone stuck in htc logo screen with white back ground. I guess my phone lacking super user permission. Is there any way I can fix my phone?
I tried to manually put su and other files into this phone but its lacking following directories
Click to expand...
Click to collapse
You haven't provided enough information. What are your bootloader details? What ROM did you flash?
Have you looked at the Evita FAQ thread? It's stickied at the top of the q&a section you're posting in, I can almost guarantee it contains the solution to your problem.

Your issue isn't with the phone not being rooted, the error message you got in TWRP would have resolved that.
Its highly likely that your issue is that if you are s-on, you neglected to flash boot.img separately using fastboot. By far, the #1 reason for bootloops after flashing a new ROM.

More Details
Here few more details about my phone-
BootLoader- Evita
Recovery - TWRP V 2.6
S- ON - Tried S-Off by flashing PJ8312000-OneX but phone was stuck at the htc logo with black screen
Tried to install SuperSu from chainfire - Installed successfully but when I reboot the system phone stuck at the HTC screen with white background
Phone had AT&T ROM for HTC One XL and I was using T-Mobile simcard. Phone started hang down and restart multiple times when its AT&T hot spot later its been happened randomly. So I decided get ride of AT&T rom and flash custom rom. Following custom roms I tried so far
1. cm-10.2.1-endeavoru- cyanogenmod 10.2(Evita) - I wiped sdcard,data before this installation. Installation failed (I guess its require S-OFF)
2. EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge - T-Mobile stock ROM for One XL- Germany -Installation was success but TWRP give me a message "Phone not rooted, flash supersu, when I flash it , phone stuck at HTC logo with white background
3. cm-11-20140218-NIGHTLY-evita - cyanogenmod 11(Evita) - Failed
4. Android_Revolution_HD-One_X_33.1 - This one come with a installer (aroma i guess), I thought finally.... but when the system reboot, its stuck again on the same screen.
Few screen shots are attached

menorah said:
Here few more details about my phone-
BootLoader- Evita
Recovery - TWRP V 2.6
S- ON - Tried S-Off by flashing PJ8312000-OneX but phone was stuck at the htc logo with black screen
Tried to install SuperSu from chainfire - Installed successfully but when I reboot the system phone stuck at the HTC screen with white background
Phone had AT&T ROM for HTC One XL and I was using T-Mobile simcard. Phone started hang down and restart multiple times when its AT&T hot spot later its been happened randomly. So I decided get ride of AT&T rom and flash custom rom. Following custom roms I tried so far
1.cm-10.2.1-endeavoru- cyanogenmod 10.2(Evita) - I wiped sdcard,data before this installation. Installation failed (I guess its require S-OFF)
2.EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge - T-Mobile stock ROM for One XL- Germany -Installation was success but TWRP give me a message "Phone not rooted, flash supersu, when I flash it , phone stuck at HTC logo with white background
3.cm-11-20140218-NIGHTLY-evita - cyanogenmod 11(Evita) - Failed
4.Android_Revolution_HD-One_X_33.1 - This one come with a installer (aroma i guess), I thought finally.... but when the system reboot, its stuck again on the same screen.
Few screen shots are attached
Click to expand...
Click to collapse
Well, where should I start. What do you mean when you say the phone was stuck at the HTC logo on black screen after flashing the PJ8312000-OneX.zip?
Now onto the ROMs you've flashed.
1. The problem is this: cm-10.2.1-endeavoru-. Can you see what's wrong with that? Maybe the fact that it says Endeavoru in the filename when you don't have the Endeavoru phone, you have the Evita. You're lucky that ROM didn't brick you.
2. You most likely just needed to flash the boot.img from that ROM through fastboot. At least that one is meant for our phone though.
3. This ROM is for our phone as well. Your problem with that one is that you're using the wrong recovery. You need the unofficial modified TWRP 2.6.3.0 from our Original Android Development section to flash KitKat ROMs.
4. And here's another ROM that isn't for our phone.
I'm not sure where you found those two ROMs that aren't for our phone.
My guess is that you've somehow stumbled into the the HTC One X Endeavoru forum, don't ever go into that forum, not a single thing there is compatible with our phone. You're extremely lucky you haven't bricked after flashing two incompatible ROMs, you should buy a lottery ticket.
Do yourself a huge favour and stay within our device forum (HTC One XL / at&t One X Evita), here's the main page, bookmark this:
One XL Main Page
http://forum.xda-developers.com/forumdisplay.php?f=1538
And here are our two development sections:
One XL Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1541
One XL Original Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1726
Only ever download ROMs from those two sections.
Please read the Evita FAQ thread I mentioned before, your answers are there. You should also read my How-To Guide For Beginners thread, it contains information you probably desperately need. Both of those are linked in my signature.
Sent from my Evita

menorah said:
2. EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge - T-Mobile stock ROM for One XL- Germany -Installation was success but TWRP give me a message "Phone not rooted, flash supersu, when I flash it , phone stuck at HTC logo with white background
Click to expand...
Click to collapse
The TWRP message is appearing as it should, as the ROM is not rooted (as mentioned right in the top post of the thread for this ROM) and TWRP will show this any time you flash an unrooted ROM. Whether you pick the option for TWRP to root (I use this ROM, and that is what I picked) or not, this is not the cause of your boot issue.
Its more likely your issue is that you didn't extract and flash boot.img manually via fastboot. This is required for s-on, and if you don't know what this means, its absolutely the cause for why your phone won't boot.
Refer to timmaaa's guide for details:
http://forum.xda-developers.com/showthread.php?t=2593382

Thanks
redpoint73 said:
Your issue isn't with the phone not being rooted, the error message you got in TWRP would have resolved that.
Its highly likely that your issue is that if you are s-on, you neglected to flash boot.img separately using fastboot. By far, the #1 reason for bootloops after flashing a new ROM.
Click to expand...
Click to collapse
Thanks Brother! You saved my phone. I was very close to get a new phone. After I flash boot.img, phone was able to getout of bootloop and flashed the rom EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.
Now if i want to do a different rom cm-11-20140218-NIGHTLY-evita just do the same steps? push the rom to sdcard, extract boot.img from from rom and flash boot.img?

Thanks
timmaaa said:
Well, where should I start. What do you mean when you say the phone was stuck at the HTC logo on black screen after flashing the PJ8312000-OneX.zip?
Now onto the ROMs you've flashed.
1. The problem is this: cm-10.2.1-endeavoru-. Can you see what's wrong with that? Maybe the fact that it says Endeavoru in the filename when you don't have the Endeavoru phone, you have the Evita. You're lucky that ROM didn't brick you.
2. You most likely just needed to flash the boot.img from that ROM through fastboot. At least that one is meant for our phone though.
3. This ROM is for our phone as well. Your problem with that one is that you're using the wrong recovery. You need the unofficial modified TWRP 2.6.3.0 from our Original Android Development section to flash KitKat ROMs.
4. And here's another ROM that isn't for our phone.
I'm not sure where you found those two ROMs that aren't for our phone.
My guess is that you've somehow stumbled into the the HTC One X Endeavoru forum, don't ever go into that forum, not a single thing there is compatible with our phone. You're extremely lucky you haven't bricked after flashing two incompatible ROMs, you should buy a lottery ticket.
Do yourself a huge favour and stay within our device forum (HTC One XL / at&t One X Evita), here's the main page, bookmark this:
One XL Main Page
http://forum.xda-developers.com/forumdisplay.php?f=1538
And here are our two development sections:
One XL Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1541
One XL Original Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1726
Only ever download ROMs from those two sections.
Please read the Evita FAQ thread I mentioned before, your answers are there. You should also read my How-To Guide For Beginners thread, it contains information you probably desperately need. Both of those are linked in my signature.
Sent from my Evita
Click to expand...
Click to collapse
Thanks a lot! I was able to flash the second rom EVITA_UL_JB_50_S_TMO_DE_5.08.111.2_By_Turge.I extracted the rom, flash boot.img. I didn't realize that, there are multiple model for this phone. I thought only one HTC One X. I wanna try cyanogenmod 11 and I already have TWRP 2.6.3.0. So just do the some steps?

Yes, the same steps exist for any ROM you want to flash. Make sure you also flash gapps when you're installing an aosp ROM.
Sent from my Evita

menorah said:
Thanks Brother! You saved my phone. I was very close to get a new phone.
Click to expand...
Click to collapse
You're welcome. And just so you know, this phone is virtually always recoverable, as long as the screen comes on. Its just a matter of trouble shooting what you did wrong, and performing the correct steps. Usually pretty simple to get the phone bootable, as long as the screen comes on at all. So in the future, don't panic. Just take some deep breaths, and come on here and do some research, or ask if you can't find the answer.

Updating Android 4.1

Hey there, guys. I've been around XDA a while & have messed around with different ROMS. I had found one that I liked (decent battery life is the most important for me) & stuck with ParanoidAndroid 3.60 (4.2 based ROM) for Android 4.1 (I believe the firmware version is 10.4.2.20). TWRP is 2.5.0.0. This was around 1-2 years ago, and I finally decided it was time to upgrade it.
Can anyone point me the direction on where to start? I would like to update to the latest (or most stable) android version, if possible. I have a basic knowledge of fastboot & how it works.:fingers-crossed:

First, you will have to upgrade your bootloader to the latest version to run the latest recovery. I don't know if there's an easier way of doing this, but I'd suggest installing a stock ROM and then unlocking/rooting/installing recovery again.
You can download the latest official firmware from here (assuming you have a TF300T model): http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/
Make sure to select the one with the correct SKU.
Then, follow this guide: http://forum.xda-developers.com/showthread.php?t=1757077
This will wipe all your data so make sure to backup all the files you need.
The bootloader will most likely remain unlocked, so what you need now is root and recovery. There are plenty of guides for those, so find the right one for you. You can download the latest TWRP from here: http://teamw.in/project/twrp2/97
An installation guide is on the same page, but make sure to download the one ending with 4.2 since you will be on the latest firmware version (here's the name of the file you'll probably need if you have a TF300T model: openrecovery-twrp-2.6.3.0-tf300t-4.2.blob).
Hope this will help

Duchman said:
First, you will have to upgrade your bootloader to the latest version to run the latest recovery. I don't know if there's an easier way of doing this, but I'd suggest installing a stock ROM and then unlocking/rooting/installing recovery again.
You can download the latest official firmware from here (assuming you have a TF300T model): http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/
Make sure to select the one with the correct SKU.
Then, follow this guide: http://forum.xda-developers.com/showthread.php?t=1757077
This will wipe all your data so make sure to backup all the files you need.
The bootloader will most likely remain unlocked, so what you need now is root and recovery. There are plenty of guides for those, so find the right one for you. You can download the latest TWRP from here: http://teamw.in/project/twrp2/97
An installation guide is on the same page, but make sure to download the one ending with 4.2 since you will be on the latest firmware version (here's the name of the file you'll probably need if you have a TF300T model: openrecovery-twrp-2.6.3.0-tf300t-4.2.blob).
Hope this will help
Click to expand...
Click to collapse
Thanks for replying! I got it to boot, but it stays stuck on the Asus logo with the loading circle. I installed the correct TWRP recovery. I tried rebooting, but it says no OS installed. Furthermore, it does not mount the External storage. I can browse the files through the file Manager in TWRP.
EDIT: It rebooted & I have everything back. It just took forever to reboot. Thanks for your help!!

boxer3310 said:
Thanks for replying! I got it to boot, but it stays stuck on the Asus logo with the loading circle. I installed the correct TWRP recovery. I tried rebooting, but it says no OS installed. Furthermore, it does not mount the External storage. I can browse the files through the file Manager in TWRP.
EDIT: It rebooted & I have everything back. It just took forever to reboot. Thanks for your help!!
Click to expand...
Click to collapse
I'm glad I was able to help. Could you tell me the order of your actions and what happened after what? I'm a bit confused as to why it'd get stuck like this.
Also, you might need a newer recovery for more recent ROMs. There are both 2.7.0.1 and 2.7.1.0 versions available in the development section.

Duchman said:
I'm glad I was able to help. Could you tell me the order of your actions and what happened after what? I'm a bit confused as to why it'd get stuck like this.
Also, you might need a newer recovery for more recent ROMs. There are both 2.7.0.1 and 2.7.1.0 versions available in the development section.
Click to expand...
Click to collapse
I did everything as you posted:
1. Downloaded the most current firmware for the TF300T from the Asus site.
2. Pushed it to my device using fastboot
3. Installed custom recovery for my version of Android
4. Rebooted.
The Installation bar completed after I pushed the firmware & recovery. It just took long to reboot. I read that you have to let the ROM "stabilize," so I suspect it might have been the cause of the hang. Everything went pretty smooth after the reboot, though. I installed TWRP 2.7.1.0 (as you posted above) and installed a new ROM. Thank you very much for taking the time to reply. I love this update! :victory: