Database Info

[Q] Stuck at HTC booting screen after flashing Cm9 alpha4 or aokp

Please help. When i first received my HTC One X, i had it rooted and the boot loader unlocked. TWRP recovery is also installed. The first thing i did was flash Clean Rom 3 LE and it booted up and was working perfectly. A few days later, i attempted to flash Cm9 alpha4 and after telling TWRP to reboot, it would just sit at the HTC screen for over twenty minutes. I tried restoring my backup and re downloading the file but it still failed. At this point i had just thought that it must be an issue with the rom on my phone, so i downloaded aokp rom from rootzwiki. I did a factory reset and cleared my caches, but it would then get stuck at the HTC screen, and then proceed to the recovery as if i had never flashed the rom. Any help is really appreciated. Thank you

If nothing else work, you can run one of the RUUs. But it will wipe data, and you will need to root, unlock bootloader (?) and install recovery again.

Thanks, but I am able to plug my phone into my mac and get to the recovery via terminal. I can then flash Clean rom and it will boot up and work fine. I'm wondering if this is an issue flashing any non-Sense based roms.

I've Flashed miui and cm9 and aokp with no problems. Did you flash the ones found in our development section? The ones in the International section won't work.

Try redownloading the zips. Make sure you wipe everything a couple times.

In the TWRP recovery wipe menu select cache, factory reset, and system then install CM9. This should fix your problem.

I flashed the ones found in our development section. Is there any extra step that I have to take. I did a factory reset, cleared my cache and dalvik cache, and then flashed the rom. I then cleared my cache and dalvik cache and then rebooted.

AMDERS17 said:
I flashed the ones found in our development section. Is there any extra step that I have to take. I did a factory reset, cleared my cache and dalvik cache, and then flashed the rom. I then cleared my cache and dalvik cache and then rebooted.
Click to expand...
Click to collapse
I don't think it's casuing the problem but the 2nd cache and dalvik clearning aren't necessary.

P_Dub_S said:
In the TWRP recovery wipe menu select cache, factory reset, and system then install CM9. This should fix your problem.
Click to expand...
Click to collapse
Still not working, but thank you for the advice. If it helps any, its stuck at the first HTC screen where it tells you in red that the software is for development purposes only.

AMDERS17 said:
Still not working, but thank you for the advice. If it helps any, its stuck at the first HTC screen where it tells you in red that the software is for development purposes only.
Click to expand...
Click to collapse
it just sits there?
that's odd.
if you connect it to your computer can you get a logcat?
type adb logcat from command prompt.

gunnyman said:
it just sits there?
that's odd.
if you connect it to your computer can you get a logcat?
type adb logcat from command prompt.
Click to expand...
Click to collapse
When i enter the command, this is what i get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
Ive never taken a logcat before, so Im sure i must have done something wrong

AMDERS17 said:
When i enter the command, this is what i get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
is adb in your path?

gunnyman said:
is adb in your path?
Click to expand...
Click to collapse
It is, but does my phone need to be on, because it is stuck at the HTC screen

Ok. Flash a rom you know works. Get the phone running then do a fresh download of cm9 alpha 4. Before you install it do a backup in recovery in case it's borked again.

gunnyman said:
Ok. Flash a rom you know works. Get the phone running then do a fresh download of cm9 alpha 4. Before you install it do a backup in recovery in case it's borked again.
Click to expand...
Click to collapse
Doing that now

Re downloaded the file and flashed it but it is still stuck at the HTC booting screen

AMDERS17 said:
Re downloaded the file and flashed it but it is still stuck at the HTC booting screen
Click to expand...
Click to collapse
stupid question is your bootloader locked?

gunnyman said:
stupid question is your bootloader locked?
Click to expand...
Click to collapse
It is. I was a able to flash Clean Rom. Im pretty stumped as to what the problem is.

AMDERS17 said:
It is. I was a able to flash Clean Rom. Im pretty stumped as to what the problem is.
Click to expand...
Click to collapse
if it's LOCKED that's probably your problem. Unlock it. There's no reason to re-lock it anyway.

gunnyman said:
if it's LOCKED that's probably your problem. Unlock it. There's no reason to re-lock it anyway.
Click to expand...
Click to collapse
Sorry. I read your other post wrong. It is unlocked. lol

[Q] Speaker Phone broke?

I've been having a problem with phone calls putting them on speaker. The volume of the external speaker is comparable to the volume of the ear piece. This is only in calls, music and notifications seem to be fine. It was fine before I rooted, but seems to be goofed up on JB roms. I rooted with the brand new 2.20 root method. I tried things like Volume+ and nothing seems to make a difference. I've tried all the basic things like wiping cache/dalvick. What are the chances it's a bad device?

you already posted this in the roms thread. someone probably saw it so why make a thread? wipe and reflash. you also can't blame root because you flashed another rom. on first root, unlock, recovery flashing i always "fastboot erase cache", then wipe literally everything in twrp, then flash my rom. you could first try "fastboot erase cache" in bootloader then wipe cache/dalvik then fix permissions before doing the above and see if that fixes it.

DvineLord said:
you already posted this in the roms thread. someone probably saw it so why make a thread? wipe and reflash. you also can't blame root because you flashed another rom. on first root, unlock, recovery flashing i always "fastboot erase cache", then wipe literally everything in twrp, then flash my rom. you could first try "fastboot erase cache" in bootloader then wipe cache/dalvik then fix permissions before doing the above and see if that fixes it.
Click to expand...
Click to collapse
yes, i posted it there because at the time i thought the problem was specific to that rom (i think it started with the codename rom). but after being on more than one rom (i'm now on the jb build 4) i don't think it is. or it may be specific to jb roms. i'm not sure. i thought i would ask before i just go flashing away... i'm also wondering if anybody else is having this problem.
i followed you all the way till "fix permissions", is this another tab in twrp?

with all the changes right now with CM10 which is base for alot of jb roms its hard to determine the cause. unless you are using a jb aosp build before the kernel changes which is basically anything after 10/01 then you might have some unique issues.
fix permissions is under advanced

Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app

ck4794 said:
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
use the stock kernel that comes with your rom for now. reboot in to bootloader and "fastboot flash boot boot.img" the kernel(ie boot.img) from ur current rom. then run "fastboot erase cache" then boot into recovery. wipe cache/dalvik then go into advanced and fix permissions.
if that doesnt work then wipe everything and reflash your rom and gapps if its aosp rom, then rewipe cache/dalvik and reboot.

Didn't work, but sandy just knocked out the power so I think this can wait a while haha
Sent from my One X using xda app-developers app

ck4794 said:
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I respectfully suggest you stay away from custom kernel for now until you are a little more familiar with your device, especially if you're playing with jb/cm10 based roms stay with the kernel that came with. The devs will not support any issues that arise from flashing a custom kernel on top of a their roms.

Crappyvate said:
I respectfully suggest you stay away from custom kernel for now until you are a little more familiar with your device, especially if you're playing with jb/cm10 based roms stay with the kernel that came with. The devs will not support any issues that arise from flashing a custom kernel on top of a their roms.
Click to expand...
Click to collapse
i will definitely take this under consideration

DvineLord said:
use the stock kernel that comes with your rom for now. reboot in to bootloader and "fastboot flash boot boot.img" the kernel(ie boot.img) from ur current rom. then run "fastboot erase cache" then boot into recovery. wipe cache/dalvik then go into advanced and fix permissions.
if that doesnt work then wipe everything and reflash your rom and gapps if its aosp rom, then rewipe cache/dalvik and reboot.
Click to expand...
Click to collapse
did this and still a no go... no volume on speaker phone during a call. wiped everything and reflashed rom with stock kernel, wiped again, fixed permissions. all other volumes seem to be appropriate.

ck4794 said:
did this and still a no go... no volume on speaker phone during a call. wiped everything and reflashed rom with stock kernel, wiped again, fixed permissions. all other volumes seem to be appropriate.
Click to expand...
Click to collapse
relock bootloader and ruu...if that does not do it you have a hardware issue.

i'm not questioning your logic, but for my own knowledge can you explain this a little better for me? not the process but the reasoning? to my understanding an ruu basically strips the phone back to some previous state, depending on the ruu you chose, and reverts it back to stock. what purpose does re locking the bootloader serve here? would i need a new unlock code or would the unlock code i got from the first time i unlocked it still work?
also let me make sure i have this process down, relock, ruu, unlock, flash? am i missing any steps in there? like will i need to reflash my recovery?

ck4794 said:
i'm not questioning your logic, but for my own knowledge can you explain this a little better for me? not the process but the reasoning? to my understanding an ruu basically strips the phone back to some previous state, depending on the ruu you chose, and reverts it back to stock. what purpose does re locking the bootloader serve here? would i need a new unlock code or would the unlock code i got from the first time i unlocked it still work?
also let me make sure i have this process down, relock, ruu, unlock, flash? am i missing any steps in there? like will i need to reflash my recovery?
Click to expand...
Click to collapse
here is the logic.
1. you need to relock bootloader to run ruu
2. ruu bring you back to vanilla stock everything, allowing you to evaluate your hardware/software issue. If your speaker works it was some kind of corruption if doesn't it you know you have a hardware problem.
Unlock code stays the same.
That's also why you should always do a clean install/full wipe/factory reset when you experiment with different roms (aosp/sense)

Crappyvate said:
here is the logic.
1. you need to relock bootloader to run ruu
2. ruu bring you back to vanilla stock everything, allowing you to evaluate your hardware/software issue. If your speaker works it was some kind of corruption if doesn't it you know you have a hardware problem.
Unlock code stays the same.
Click to expand...
Click to collapse
thanks for being patient with me man, i appreciate it. i'll give this a go a little later this evening and post back results.

ck4794 said:
thanks for being patient with me man, i appreciate it. i'll give this a go a little later this evening and post back results.
Click to expand...
Click to collapse
good luck. :highfive:

[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502
am i ok to run this ruu even though i came from 2.20 when i rooted?

ck4794 said:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502
am i ok to run this ruu even though i came from 2.20 when i rooted?
Click to expand...
Click to collapse
http://dl3.htc.com/application/htc_o...s_08022012.exe

Crappyvate said:
http://dl3.htc.com/application/htc_o...s_08022012.exe
Click to expand...
Click to collapse
bad link

ck4794 said:
bad link
Click to expand...
Click to collapse
what...i just tested it ?? hold on
http://forum.xda-developers.com/showpost.php?p=29766409&postcount=3

Crappyvate said:
what...i just tested it ?? hold on
http://forum.xda-developers.com/showpost.php?p=29766409&postcount=3
Click to expand...
Click to collapse
i saw some where i think that this ruu would get me back to square one, unrooted. is there anything like that i should know about before i run this ruu? also i've never run an ruu, is it one of those i put it on my c: drive run it and it will do the work?

[Q] Please help! Can't mount SD in Recovery can't flash ROM

Not sure what i've done...
I wiped my System partition, and data partitions and was going to flash the latest AOKP (i had some issues with rohan's kernel so i needed to start fresh) but i can't mount my SD in TWRP and I'm pretty concerned that my built in storage is screwed. Any help ??

Prfndhatrdofman said:
Not sure what i've done...
I wiped my System partition, and data partitions and was going to flash the latest AOKP (i had some issues with rohan's kernel so i needed to start fresh) but i can't mount my SD in TWRP and I'm pretty concerned that my built in storage is screwed. Any help ??
Click to expand...
Click to collapse
go here: http://forum.xda-developers.com/showthread.php?t=1671237 and read before you do anything else. Then.. find your device specific RUU and run it. You'll have to relock your bootloader and reflash TWRP.
Which AOKP were you looking to flash?
Which hboot do you have?
and do you have the international or US version?

Myrder said:
go here: http://forum.xda-developers.com/showthread.php?t=1671237 and read before you do anything else. Then.. find your device specific RUU and run it. You'll have to relock your bootloader and reflash TWRP.
Which AOKP were you looking to flash?
Which hboot do you have?
and do you have the international or US version?
Click to expand...
Click to collapse
I was hoping to avoid doing an RUU, don't RUUs wipe USB Storage?
I have Hboot 1.09
CID 11111111
I had flashed AOKP Milestone 1 JB earlier.
I flashed a few 4.2 JB apps and upon reboot my phone would stick at the boot animation.
So I wiped my data partition and system to reflash Milestone 1 but now i can't flash anything.

Can you get into TWRP? If so, you can adb push.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz

I've been trying to flash using fastboot: fastboot update blahblah.zip
fails saying there is android-info.txt

Yes, RUU wipes everything and gets rid of any corruption. Wait, are you wiping cache and delvik, and system...?
Sent from my HTC One XL cellular device over clocked to 1.9Ghz

Myrder said:
Yes, RUU wipes everything and gets rid of any corruption. Wait, are you wiping cache and delvik, and system...?
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
Click to expand...
Click to collapse
I did yes. Everything is wiped currently so im sort of in a soft brick. i can boot in and out of recovery but i cannot flash anything. my SD storage wont mount in TWRP

I figured out what i did. i accidentally hit factory reset from Bootloader. and then stopped the reset. had to flash stock recovery and flash twrp again. lost all of my stuff. pretty upset about it. my fault though i guess.

Close this thread please.

Does windows ask you if you want to format when you mount usb in twrp?
If so format fat32, transfer files over and go.
I don't know why everyone are telling people to RUU when they dont have to

because formatting in windows doesn't always fix it.

newbie mistake
So after stumbling to this thread I realized what happened with my attempt at flashing a rom. I selected Viper 2.6.0 for my newly rooted At&t one x on firmware 2.20. It was stuck on bootloop. I had backed up using TWRP 2.3.1, but the restore was stuck on a bootloop as well.
I realize now that this was because I was flashing an international rom. Is this recoverable or is this the last mistake I can make on this phone?
Any advice or links to the proper thread would be very much appreciated.

[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL

I'm having the "E: Can't mount /sdcard/ problem in CWM recovery v5.8.3.1. I followed the guide to install but I find it misleading. I came from Leedroid so I had to "factory reset" but this has caused the problem. Any advice to a noob?

Bradz213 said:
I'm having the "E: Can't mount /sdcard/ problem in CWM recovery v5.8.3.1. I followed the guide to install but I find it misleading. I came from Leedroid so I had to "factory reset" but this has caused the problem. Any advice to a noob?
Click to expand...
Click to collapse
your in the wrong forum

DvineLord said:
your in the wrong forum
Click to expand...
Click to collapse
Wrong thread perhaps, right forum!

No wrong forum. Sounds like you have a tegra 3 Onex. This forum is for the s4 version
Sent from my One X using xda app-developers app

Help! Trying to revert to stock rooted from CM10

I upgraded to CM10 from the original OS and I am using the latest version to root my phone, I am using TWRP. Anyway, Everything worked fine, I rooted the phone, I upgraded to CM10. I want to go back to the original OS. I downloaded [ROM][8/3] - Stock Rooted AT&T 2.20.502.7 - Android 4.0.4 - Odex or De-Odex, I got the ODEX version, I flashed it to my phone but its just hangs at the HTC One X Splash screen with the red lettering. What am I missing here? I can get back into recovery and I backed up my old ROM just in case.

How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.

mgutierrez87 said:
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
Click to expand...
Click to collapse
It just shuts off and turns back on again, it basically loops. Did I download the wrong file maybe? Is there a specific ROM I need other than the one I mentioned earlier?

Boot into recovery and wipe your cache and dalvik cache again

mgutierrez87 said:
Boot into recovery and wipe your cache and dalvik cache again
Click to expand...
Click to collapse
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app

This was the ROM that worked when i did it.
http://forum.xda-developers.com/showthread.php?t=1872842
---------- Post added at 04:53 AM ---------- Previous post was at 04:46 AM ----------
Myrder said:
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
He mentioned in another thread that he did those steps. The only other thing I would try is to flash the boot.IMG from the ROM you want to use

I still want to keep my phone rooted. This wont kill the root right?

No the ROM posted above is stock rooted
But if you made a backup as you said in the first post why are you not just restoring the backup?
Sent from my Nocturnalized One XL using Forum Runner

Basically where I am right now. I downloaded the original OS, by following instructions, I have managed to delete my backed up rom of CM10 that i backed up earlier. I was able to FLASH the OS I wanted, I flashed the boot.img file using fastboot. I restarted the phone and now its just stuck on the HTC Quietly Brilliant screen with the red lettering at the bottom. It doesn't restart or anything, it just hangs there. What am I missing here guys? ):

I'm going to install cm10 right now them go back to stock rooted and see what's up with this

There's no issues going back and forth. You probably flashed a bad ROM

yea, your most likely just doing it wrong. you need to do a full wipe and flash boot.img
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.

What hboot are you on? If you separately flashed boot.img from CM10 via fastboot, you might need to again separately flash the boot.img from the stock ROM. Also remember that the procedure employed to root 2.20 is substantially different from the root procedure to root the previous build of stock. Not sure what software you rooted, or whether this would pose a problem, but it's a consideration.
Another option is to just restore to stock via RUU and re-unlock, re-root, if nothing else works. Getting stuck on HTC splash screen sounds like a boot.img issue. Good luck.

DvineLord said:
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
Click to expand...
Click to collapse
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!

Did you fastboot flash boot boot.img?
Sent from my HOX running Cyanogenmod 10

redpoint73 said:
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Click to expand...
Click to collapse
im assuming the age of the stock rooted would have conflicts with the new twrp. i have had problems with roms not flashing with newest twrp. it is also a known problem since twrp 2.3.1.0 release.

[Q][Solved] HTC One X AT&T - Boot looping once, defaulting to recovery boot

I just installed the VenomXL 3.2.6 on my HTC One X using TWRP 2.5.0.0. I am not 100% sure that I have S-Off, I rooted my phone right when the exploit for the "impossible" firmware was figured out a number of months ago. HBoot is showing 1.14.
I did factory wipe 3x before starting the installer. Then chose "wipe" in the installer. Everything installed quickly/correctly. After installing, I rebooted into fastboot and flashed the boot.img over with no issues.
Now when I try to boot, it'll boot loop at the initial white HTC-with-red-warning screen and then automatically boot into TWRP.
What can I do to make this ROM work?
Thanks

You can download twrp 2.3.3.1, check md5
flash twrp 2.3.3.1
fastboot erase cache
reboot to recovery, wipe cache, dalvik, system, factory reset.
flash rom, flash boot.img
Working.
Good Luck. By the way, if you were S-OFF, you would know.

exad said:
You can download twrp 2.3.3.1, check md5
flash twrp 2.3.3.1
fastboot erase cache
reboot to recovery, wipe cache, dalvik, system, factory reset.
flash rom, flash boot.img
Working.
Good Luck. By the way, if you were S-OFF, you would know.
Click to expand...
Click to collapse
Thank you for your advice! I've followed it as you listed and, unfortunately, my problem persists. After flashing fastboot flashing the boot.img at the end and restarting, it will hang at the white HTC-with-red-warning-text screen and then reboot into recovery.
Do you have any other suggestions?
I'm still searching that particular ROM thread looking for people with similar issues.
My next step is to try the next most popular ROM, whichever that is.

sappro said:
Thank you for your advice! I've followed it as you listed and, unfortunately, my problem persists. After flashing fastboot flashing the boot.img at the end and restarting, it will hang at the white HTC-with-red-warning-text screen and then reboot into recovery.
Do you have any other suggestions?
I'm still searching that particular ROM thread looking for people with similar issues.
My next step is to try the next most popular ROM, whichever that is.
Click to expand...
Click to collapse
the boot.img you are flashing is extracted from viperxl rom? viper xl should have the option to flash the boot.img for you so you don't even have to.
Otherwise i'd check MD5 of the Rom, either the file is bad or you're doing something wrong.

exad said:
the boot.img you are flashing is extracted from viperxl rom? viper xl should have the option to flash the boot.img for you so you don't even have to.
Otherwise i'd check MD5 of the Rom, either the file is bad or you're doing something wrong.
Click to expand...
Click to collapse
The MD5 on my flash drive of the downloaded ROM is incorrect, even though it was correct before moving to my flash drive. I will redownload and see if that solves the issue.
Thank you!

exad said:
the boot.img you are flashing is extracted from viperxl rom? viper xl should have the option to flash the boot.img for you so you don't even have to.
Otherwise i'd check MD5 of the Rom, either the file is bad or you're doing something wrong.
Click to expand...
Click to collapse
Wow, I've never had an MD5 problem before, but that appeared to have fixed it. Thanks very much for the suggestion!
SOLVED: The ZIP files were somehow subtly corrupted during transfer from computer to flash drive to phone. After checking the MD5 using http://forum.xda-developers.com/showthread.php?t=1939007 I was verify this. Using a different computer/browser, I downloaded the ROMs again and now the MD5 hashes correctly!

Cool glad you are up and going. Personally I like to download roms to phone then install with twrp . Also you probably know this but a nandriod backup is a must .
Sent from my HTC One X using xda premium