Related
So my At&t One X (evita) has been rooted and the bootloader has been unlocked for some time now. I came from the old Htc Hero on Sprint, so I am use to rooting and flashing roms. The issue is I decided to try Cm10 and I flashed it correctly through the flash gui app. An update appeared at the top so I (like a noob) decided to install it.. I realized after the fact how I had messed up by not using flash gui (boot.img ,etc..) , So it would boot to the Htc logo and then just blackness would occur. I could and still could go to the bootloader successfully though. My mistake was doing a whole factory reset from the phone so no more TWRP recovery unit... I went back to the utility that I rooted and unlocked my bootloader on and relocked it just in case I needed to flash something such as a RUU (whatever that is) but I do have one ready to be installed. I tried to do it myself and kept getting the sentence in the picture posted... Can anyone help me??
that picture doesn't help much, my not relock bootloader run the .exe ruu. then reunlock and flash twrp then flash a rom? also flashimagegui doesnt flash a rom all it does it flash boot.img and modules or recovery. you still have to reboot into recovery and flash the rom zip. since youve used android before it is an easy fix. so fix it already =)
hrrsncrawford14 said:
So my At&t One X (evita) has been rooted and the bootloader has been unlocked for some time now. I came from the old Htc Hero on Sprint, so I am use to rooting and flashing roms. The issue is I decided to try Cm10 and I flashed it correctly through the flash gui app. An update appeared at the top so I (like a noob) decided to install it.. I realized after the fact how I had messed up by not using flash gui (boot.img ,etc..) , So it would boot to the Htc logo and then just blackness would occur. I could and still could go to the bootloader successfully though. My mistake was doing a whole factory reset from the phone so no more TWRP recovery unit... I went back to the utility that I rooted and unlocked my bootloader on and relocked it just in case I needed to flash something such as a RUU (whatever that is) but I do have one ready to be installed. I tried to do it myself and kept getting the sentence in the picture posted... Can anyone help me??
Click to expand...
Click to collapse
Had that happen to me. But just had to flash a kernel for it to boot properly. Everything fine after that.
Sent from my HTC One X using Tapatalk 2
THANKS!!! I have it working now thanks to the suggestions! :laugh::laugh:
DvineLord said:
that picture doesn't help much, my not relock bootloader run the .exe ruu. then reunlock and flash twrp then flash a rom? also flashimagegui doesnt flash a rom all it does it flash boot.img and modules or recovery. you still have to reboot into recovery and flash the rom zip. since youve used android before it is an easy fix. so fix it already =)
Click to expand...
Click to collapse
glad u got it working again. i would recommend doing s-off so you don't have to flash boot.img separately anymore.
Hey all, been a member here for years but dont post offten. Normally able to get the info i need from other posts but this time i am stuck Just wondering if anyone has had the same issue flashing a One S C2 with the S3 CPU that im having now. It was stuck with 4.0.3 with hboot 2.09.001, raido 16.05.2.24_M and CID OPTUS001...
Last night i dev unlocked it via the HTC site and flashed TWRP 2.4.4.0 recovery. Tried to put on luxandroidROM v4 but it failed part way through ROM install. The progess bar just got to a point and stopped?? I noticed i had a hboot that was too old for the JB ROM so tried BackToBasics v3 (ICS) ROM but that did the same thing...
Thinking it was maybe just a issue with the ROMs, i tried TrickDroid 6 and CM10 Unofficial build but that was doing the exact same thing... Tried redownloading all the ROMs and looking into SupoerCID but as other with the S3 CPU have reported, it all appears to have worked but does not change the CID Oddly enough when i was in ADB Shell while the phone was sitting on the TWRP recovery mode the SU command was not working. Relevent?
I'm now thinking the issue is the phone is not getting permissions to write the ROMs but have no idea how to correct this. I made sure TWRP has all sections mounted (not sure if this is needed as i normally use CWM) but didn't help.
TWRP keeps saying device isnt rooted when i go to reboot it but fails to root when i tell it to on exit. I have manually flashed SuperSU through TWRP and tried fixing permissions. Tried full factory wipe, Bulletproof-S3-1.3 Kernal and SuperSU again. Still nothing.
Not able to find a RUU for the OPTUS001 CID. Tried extracted version of RUU_VILLEC2_U_ICS_40_hTC_Asia_WWE_1.11.707.112_Radio_16.12.20.02U_16.05.20.16_M2 with CID changed in texts files but it still saied with carrier ID issue
This would be the first time i think i have bricked a phone Does anyone have any suggestions? At this point i would be happy for a nandroid backup to go back to sock and just like with 4.0.3
$40 reward to whoever provides me the info i need to fix this
On the s4 versions of TWRP newer than 2.4.0.0 have issues. I'm not sure if they affect the c2 version but I shouldn't hurt to try an older version.
Sent from my HTC One S using xda app-developers app
TWRP 2.4.4.0 has known bugs. Downgrade to 2.3.3.0 or 2.3.3.7.
And remember to open (BUT NOT EXTRACT) the .zip and to copy and paste the boot.img into your fastboot working environment and manually flash it with this command:
fastboot flash boot boot.img
Then try to flash the ROM that you got the boot.img from. This should work.
Sent from my One S using xda premium
Managed to get this working, figured i would post in case anyone else runs in this issue.
Tried multiple versions of TWRP and no matter what one i tried the roms were unable to write to the stoage. Had to format the phone storage using boot cd - I used GParted through a virtual to do so.
Once that was done TWRP 2.4.4.0 worked fine to flash rom. Still stuck with 4.0.3 with hboot 2.09.001 due to the optus CID but phone is atleast alive. Thanks all for the input
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.
I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!
qabi said:
I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!
Click to expand...
Click to collapse
Do you have Ville (S4) or Ville C2 (S3) model?
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery --> http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ville/philz_touch_6.19.3-ville.zip
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
PLS check if you have S3 or S4
LS.xD said:
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
Click to expand...
Click to collapse
Thanks for your suggestion.
Actually I don't know. I think only one HTC One S was ever in my market (Denmark).
In the meantime I succeeded installing the TwistedKat ROM and have it running now.
Does anybody know of a tutorial for resetting to stock ROM? (Just in case I want to revert).
-qabi
Unable to enter clockwork recovery?
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!
qabi said:
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!
Click to expand...
Click to collapse
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
Which recovery do you use? Are you S-OFF // SuperCID // HBOOT 2.15??
808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...
Rapier said:
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...
Click to expand...
Click to collapse
Rapier, can you explain this? A while back I loaded TWRP (S-ON) then loaded one of the CM series (either 11 or 10, can't remember). Then after I flashed boot.img, I was stuck in boot loop with HTC/red letters.
The reason I was asking what he did was I never did get to stop the boot loop myself. I paid to get it fixed, but I would like to know what I should have done to fix the boot loop after flashing the boot.img and having the problem. Seems like a lot of people get this so, so would be nice to know.
I was basically following everything listed on a web page and everything was working. Unlocked boot loader, SuperSU, TWRP etc... the last thing I did was flash the boot.img and then the problems occurred.
As far as the double try for CWM, I am S-OFF, 2.15 and I noticed it happens every now and then. I don't have this issue with TWRP at all.
It is hard to say why, apparently you did all right. What I can think off is a bad download or a bad flash or you could have used a wrong TWRP version. Also that ROM you have tried could have issues. It is very hard to know why without some logs that shows what went wrong
Sent from nowhere over the air...
LS.xD said:
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery -->
Click to expand...
Click to collapse
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!
qabi said:
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!
Click to expand...
Click to collapse
I think so. I am running the latest CWM and never had problems before this.
Hey guys,
I just recently wanted to Cyanogenmod my friends' phone (which I have done with many others already) and never could get it to actually boot anything but the stock rom.
I S-OFF'ed it via HTCDev and installed the 4X recovery. (not sure if the name is right, I don't have the phone here)
Then I Installed the custom Rom after Wiping Cache/Dalvic/Factory Reset and it went through, but every Rom gets either stuck at the "HTC" screen or in the case of Cyanogenmod (Official) it got the the Boot animation and then looped.
Anyone knows what could've gone wrong? I re-flashed the stock Rom after giving up and now the phone seems to have issues with the WiFi connection.
So how do I get a custom Rom to actually Boot?
bobdowl said:
I S-OFF'ed it via HTCDev and installed the 4X recovery. (not sure if the name is right, I don't have the phone here)
Click to expand...
Click to collapse
you can't S-OFF via htcdev
post your bootloader details
bobdowl said:
Hey guys,
I just recently wanted to Cyanogenmod my friends' phone (which I have done with many others already) and never could get it to actually boot anything but the stock rom.
I S-OFF'ed it via HTCDev and installed the 4X recovery. (not sure if the name is right, I don't have the phone here)
Then I Installed the custom Rom after Wiping Cache/Dalvic/Factory Reset and it went through, but every Rom gets either stuck at the "HTC" screen or in the case of Cyanogenmod (Official) it got the the Boot animation and then looped.
Anyone knows what could've gone wrong? I re-flashed the stock Rom after giving up and now the phone seems to have issues with the WiFi connection.
So how do I get a custom Rom to actually Boot?
Click to expand...
Click to collapse
As rzr said you can't s-off via htcdev. Activate smartflash in 4ext recovery and try again.
Sajito said:
As rzr said you can't s-off via htcdev. Activate smartflash in 4ext recovery and try again.
Click to expand...
Click to collapse
Okay, sorry I just asked my friend (who is in possession of the phone)
I unlocked the Bootloader via HTCDev, I will contact my friend to make sure what I did. (It's been a week)