Looking for some urgent help... any would be appreciated. First of all I should start by saying this is the Mrs' phone, just so you get an idea of how much trouble I'd be in if I can't get it working.
I had set her up with a custom ROM many months ago, but it was very lagy and slow. About two days ago I took it upone myself to look for other options as far as Roms go. I found a few that I wanted to try but when I went into TWRP to start flashing them I kept getting a FAILED error regarding PARTITION DETAILS. I read a bit about it and most people recomended trying other recovery, i.e. Philz Touch.... so that's what I tried. I tried both flashing it and also installing it via Flashify but the Recovery was not there. I then tried to install CWM recovery. After supposedly installing CWM I tried to boot into recovery, but now the recovery is entirely gone. If I go HBOOT, I can see the text RECOVERY, but upon selecting it nothing happens, just goes back to the previous screen. I can still power on the phone on it's current laggy ROM, but that's not what I want. I downloaded ROM MANAGER and it tells me that I have both CWM and TWRP installed., but can't really boot into any of them. Also tried pushing the Philz Touch and the stock recovery via fastboot but keep getting an "cannot load recovery.img". It seems like something broke regarding the recovery. I saw that Rom Manager has an "install ROM from SD card option" but I've never used that... not sure if it's safe and if for some reason the ROM I downloaded doesn't work I wouldn't know how to restore from the back up without having a recovery installed.
Please find the bootloader info attached.
p.s I'm posting this because I can't find the answer anywhere else... Thanks!
You're posting in the wrong device section and sub-forum. You have the HTC One X+, this is the HTC One XL section. You'll need to go over to the One X+ section, but make sure you post in the q&a and troubleshooting section, not the general section.
Transmitted via Bacon
Related
Good Morning,
I have run into a problem with my HOX. After rooting and unlocking, I attempted to flash a custom ROM. Well, in my haste I flashed the new boot.img before transferring the new ROM to the phone. I have now formatted all info in all areas of the phone (wrong move I know). I can boot into fastboot, I can boot into CWM.
The problem lies in the mounting of the SDcard. I read through countless threads and everything I have tried up to this point has netted zero results. I have been flashing since the old Win Mobile days. I have a fairly strong understanding of ADB. I am not a developer, nor do claim to have the knowledge of one. I am reaching out and asking for help. I have CWM, version 5.8.3.1 touch. I also tried flashing back to the original boot.img and still no dice. Perhaps I have missed a step, I hope that is all. I did make a quick post in another thread, but it was made before I read allot of the other threads, so I am double posting. I am open to trying any advice that is offered.
Thank You all so much
Jason
zad2k2 said:
Good Morning,
I have run into a problem with my HOX. After rooting and unlocking, I attempted to flash a custom ROM. Well, in my haste I flashed the new boot.img before transferring the new ROM to the phone. I have now formatted all info in all areas of the phone (wrong move I know). I can boot into fastboot, I can boot into CWM.
The problem lies in the mounting of the SDcard. I read through countless threads and everything I have tried up to this point has netted zero results. I have been flashing since the old Win Mobile days. I have a fairly strong understanding of ADB. I am not a developer, nor do claim to have the knowledge of one. I am reaching out and asking for help. I have CWM, version 5.8.3.1 touch. I also tried flashing back to the original boot.img and still no dice. Perhaps I have missed a step, I hope that is all. I did make a quick post in another thread, but it was made before I read allot of the other threads, so I am double posting. I am open to trying any advice that is offered.
Thank You all so much
Jason
Click to expand...
Click to collapse
1. Wrong section, things like this should be in Q&A
2. Did you flash the CWM recovery with working ADB? If so you should be able to push the rom to your sdcard from recovery (someone correct me if I'm wrong about that).
RUU back to stock?
Sent from my HTC One X using XDA
Enter Fastboot re flash a recovery that has ADB working either teamwins or the CWM that has working ADB. Then push the rom to the sd card through ADB in recovery.
My apologies for posting in the wrong area...Thank you for the quick responses. I reflashed the current CWM, no luck. I flashed the recovery from Teamwin and things are looking up. I was able to look at the sdcard in recovery and I was able to push the ROM to the sdcard via ADB. However, when I try to install the zip, it gives the error again "can't mount sdcard" failed....hmmm Any other ideas or thoughts??
Thank You
Jason
I just wanted to say thank you to those who helped. All the time wasted, I never relocked before trying to flash RUU!!
made same mistake
...everything was too cool to be true,
rooted my HOX with
One Click HTC One X Root by kennethpenn (Win/Mac/Linux) (Recommended)
then
Auto Deodex/Debloat AT&T One X by kennethpenn
then let my HOX relax for a week, but past weekend after install CWM with
How To: Install CWM Recovery on HTC One X (AT&T)
Filed under Development, Guides by Kenneth Pennington
i was not sure about wether to install ROM
CleanROM DE 2.1 -★| Sense / AOSP Blend | Smooth! | Refreshing! |★-
or
CleanROM 2.4.5 SE -★| Landscape! | EQS! | APM! | Clean! |
i download both and then restart in recovery then i did
install zip from sdcard, but instead of do it over CleanROM 2.4.5, I did it with CleanROM DE 2.1
after reboot i realize that i screw it big time since CleanROM DE 2.1 comes without boot.img
so now when i start my HOX just reboot by itself after 5sec, the only thing i am able to do is start on recovery and when i tried to install all over again thru install zip from sdcard i just get
"E: Cant mount /sdcard/"
I ran AT&T RUU_Evita_UL_Cingular_US-1.83.502.exe and RUU 1.73 but it cant detect my HOX
help!!!
I found this for you. Give it a try. It was not my work just googled.
This is for people who have the following problem:
Cannot boot into ROM (e.g Stuck at the HTC Logo)
Boot Loop
Re-locked bootloader while having a non-working ROM
Cannot flash RUU because battery is below 30%
[edit] Try this first
The most common problem is being stuck at the HTC Logo after flashing a ROM, try clearing the fastboot cache with these steps:
Power off your phone and hold the power button + volume down
Choose fastboot from bootloader
Connect the phone to your computer
In command prompt window opened in your platform-tools folder type:
fastboot erase cache
Choose "Reboot" in fastboot menu
If this doesn't work, try the rest of the guide
http://forum.xda-developers.com/wik...very_-_what_to_do_in_the_event_of_a_bad_flash
was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.
What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.
first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off
No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?
I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.
i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.
i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.
well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.
So I Unlocked my bootloader with htcdev.com, used hasoons toolkit to get Team Win Recovery Project, Once again used hasoons tool to get superSU rooted, installed etc. I then made a backup with TWRP, wiped the phone and flashed the Xylon Rom which i downloaded from the OneXRoot website along with the google apps .zip file. I then booted into fastboot and used cmd to flash the boot.img file onto the phone. Now the phone boots into the grey xylon screen but does not get any further, just that flashing white streak that indicates "Loading". I have tried wiping and restoring to the backup i made in TWRP but then it just loades the HTC One screen over and over not booting any OS, I have also tried wiping and re installing the rom with the previous steps to no avail. How should i recover my phone to a usable state? I dont care what Rom/OS is on there i would just like to get it working again.
Any advice would be appreciated greatly.
Kind Regards, Raf.
Did you erase dalvik and cache?
Or you can do an RUU. And next time, use xda as a despot of knowledge. ROMs downloads inclusive
And next time, also post in the q&a section
Sent from my HTC One XL using XDA Premium 4 mobile app
Are you Soff?
I believe Xylon uses the 3.4 kernel which required S off and running the 3.18 RUU beforehand.
Sent from my One X using XDA Premium 4 mobile app
Raff1234 said:
So I Unlocked my bootloader with htcdev.com, used hasoons toolkit to get Team Win Recovery Project, Once again used hasoons tool to get superSU rooted, installed etc. I then made a backup with TWRP, wiped the phone and flashed the Xylon Rom which i downloaded from the OneXRoot website along with the google apps .zip file. I then booted into fastboot and used cmd to flash the boot.img file onto the phone. Now the phone boots into the grey xylon screen but does not get any further, just that flashing white streak that indicates "Loading". I have tried wiping and restoring to the backup i made in TWRP but then it just loades the HTC One screen over and over not booting any OS, I have also tried wiping and re installing the rom with the previous steps to no avail. How should i recover my phone to a usable state? I dont care what Rom/OS is on there i would just like to get it working again.
Any advice would be appreciated greatly.
Kind Regards, Raf.
Click to expand...
Click to collapse
Ok firstly I wouldn't suggest getting ROMs from anywhere except XDA. Other sites (especially OneXRoot) don't properly distinguish between phone models, put simply this leads to bricks. Secondly can you please post your bootloader details, it's pretty standard to do this when asking for help as it gives us the information we need to help you properly.
There could be a few reasons the ROM didn't boot but lets not get into that now. When you created the backup of your stock ROM which boxes did you check? You're s-on so most likely even if you checked the right boxes (system/data/boot) and then restored those partitions later your phone can't flash the boot partition in recovery which means it won't boot. I'd strongly suggest getting s-off, it has many advantages which we can get into once your phone is recovered, and at this stage there's really no reason not to have it.
The best way to recover and get your phone booting right now is just to flash a different ROM. You can download a ROM to your PC and use the mount menu in TWRP recovery to mount your sd card so you can copy it to your phone. If it's aosp just make sure you have the correct version of gapps to correspond with the Android version of the ROM (4.0/4.1/4.2/4.3/4.4). And obviously make sure you flash the boot.img via fastboot after flashing the ROM. Also make sure you perform a full wipe (cache/dalvik/system/factory reset) before flashing any ROM. Before you attempt to flash anything though I need to see your bootloader details as mentioned above, certain ROMs require certain firmware to be installed in order to work.
I mentioned before not to get ROMs from other sites, you actually don't need anything from anywhere except XDA, it literally has everything you'll ever need. The other sites generally just copy/paste from here anyway. Here is our device forum main page:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Here are our two development sections:
http://forum.xda-developers.com/forumdisplay.php?f=1541 (mainly Sense ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1726 (aosp ROMs)
Here's the q&a section:
http://forum.xda-developers.com/forumdisplay.php?f=1572 (this is where your post should have been created)
Also if you click the Everything Evita link in my signature you'll find that thread extremely valuable. It contains links to basically anything and everything that's of any use.
PS. I'm reporting this thread so the mods can move it to the right section (q&a), please make sure you post in the correct section next time. Thanks!
PPS. Welcome to our forum
Sent from my Evita
timmaaa said:
Ok firstly I wouldn't suggest getting ROMs from anywhere except XDA. Other sites (especially OneXRoot) don't properly distinguish between phone models, put simply this leads to bricks. Secondly can you please post your bootloader details, it's pretty standard to do this when asking for help as it gives us the information we need to help you properly.
There could be a few reasons the ROM didn't boot but lets not get into that now. When you created the backup of your stock ROM which boxes did you check? You're s-on so most likely even if you checked the right boxes (system/data/boot) and then restored those partitions later your phone can't flash the boot partition in recovery which means it won't boot. I'd strongly suggest getting s-off, it has many advantages which we can get into once your phone is recovered, and at this stage there's really no reason not to have it.
The best way to recover and get your phone booting right now is just to flash a different ROM. You can download a ROM to your PC and use the mount menu in TWRP recovery to mount your sd card so you can copy it to your phone. If it's aosp just make sure you have the correct version of gapps to correspond with the Android version of the ROM (4.0/4.1/4.2/4.3/4.4). And obviously make sure you flash the boot.img via fastboot after flashing the ROM. Also make sure you perform a full wipe (cache/dalvik/system/factory reset) before flashing any ROM. Before you attempt to flash anything though I need to see your bootloader details as mentioned above, certain ROMs require certain firmware to be installed in order to work.
I mentioned before not to get ROMs from other sites, you actually don't need anything from anywhere except XDA, it literally has everything you'll ever need. The other sites generally just copy/paste from here anyway. Here is our device forum main page:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Here are our two development sections:
http://forum.xda-developers.com/forumdisplay.php?f=1541 (mainly Sense ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1726 (aosp ROMs)
Here's the q&a section:
http://forum.xda-developers.com/forumdisplay.php?f=1572 (this is where your post should have been created)
Also if you click the Everything Evita link in my signature you'll find that thread extremely valuable. It contains links to basically anything and everything that's of any use.
PS. I'm reporting this thread so the mods can move it to the right section (q&a), please make sure you post in the correct section next time. Thanks!
PPS. Welcome to our forum
Sent from my Evita
Click to expand...
Click to collapse
Hi, thanks for the tips about Son/Off I plan on doing that later,I figured out i could put a new rom on using the mount function in TWRP, I successfully loaded cyanogen nightly onto my phone and it is working great, however i flashed the gapps aswell but when I booted my phone i had to manually install the play store, maps, and other google services. When i made a backup I believe i ticked all the correct boxes, and i always cleared the cache, etc.
Thanks for all the help so far.
Raff.
You had to install Play Store? Or you had to install apps from the Play Store? Which ROM and which gapps package did you flash?
Sent from my Evita
timmaaa said:
You had to install Play Store? Or you had to install apps from the Play Store? Which ROM and which gapps package did you flash?
Sent from my Evita
Click to expand...
Click to collapse
I installed CM10.2 Nightly (The .zip is called cm-10.2-20130821-NIGHTLY-evita) and gapps 4.3, I got these from the OneXRoot site unfortunately. I did this before I checked on the thread again and saw that these other sites were not the best/reliable things to use. I had to install the play store from my browser, I just googled play store download and installed it, then proceeded to install all my other apps.
Ahh ok, I see. As far as I know the best place to get gapps from is the goo.im gapps page. I'm not sure if they have 4.4 gapps up yet but they're fairly easy to find with Google.
Sent from my Evita
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.
Hi everyone.
I used to be rooted until this morning when I decided to unroot back to stock firmware. I have a HTC One M8 that used to be on TWRP. This morning when installing a nandroid backup from XDA I cam across a bug where my camera app wasn't working, and because the STOCK roms for my CID (H3G__001) are really limited, I decided to root back to CWM. When everything was loaded up again, I downloaded a different stock nandroid to my phone (Usable by CWM or Philz Touch Recovery) however I accidentally hit "Clean to Install a New ROM" thinking it'd give me a fresh system. Now I have no OS!
I've tried to download the stock again and put it onto my SD card, however the only Stock Backup available for my CID on CWM is corrupted, and I'm stuck. I've tried to us TWRM mode and install a TWRM Stock Backup by transferring that to my SD Card. I've even tried ADB pushing both CWM and TWRM backups but they still don't work.
My only other option is to download a custom rom and adb push that to my phone now I think, but I don't know which one will work with my CID number. Please give me some information/advice on what to do!
I've been struggling with this since the early hours of the morning and I'm getting really frustrated. Please please help.
Thanks.
Hi there,
I see you already posted in the right thread your question. Please wait ar ask there an answer from the owners/experts.
[HELP THREAD] HTC One M8 - Ask any questions here!
Good luck