I read on flip board that cm 10.1 is official for our phone and I I want to flash it and I did but the after I flash it and flash the boot.IMG it get stuck on the HTC logo and I see that the soft key button turn on and have vibration when I touch them can anyone help .
Sent from my HTC One S using xda premium
Do you have an S4 or S3 phone
Did you check md5 for good/bad download
Did you wipe all including System 2x in recovery
Which recovery are you using
I have s4 and I didn't check the md5 cause all 4.2 ROMs have the same problem for me,i have twrp
Sent from my HTC One S using xda premium
which version twrp. some of the later 2.3's had issues
otherwise if you are wiping all and fastbooting boot, not sure
fastboot boot after rom and fastboot erase cache before booting onto rom
rugmankc said:
which version twrp. some of the later 2.3's had issues
otherwise if you are wiping all and fastbooting boot, not sure
fastboot boot after rom and fastboot erase cache before booting onto rom
Click to expand...
Click to collapse
I have v 2.3.3.0 for twrp I'll update it and try what you said and report back here if it works
Sent from my HTC One S using xda premium
i had 2.3.3.0 and it was not one of the bad ones
Still doesn't work and I tried force md5 sum check on twrp and it failed could that be the problem
Sent from my HTC One S using xda premium
brandontamas said:
Still doesn't work and I tried force md5 sum check on twrp and it failed could that be the problem
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'd reccomend clockworkmod over twrp, had more bootloops with twrp in the past.
Also, good alternative rom is dark jelly cm10.1 with android 4.2.1 stable and reliable, using it a pretty long time.
Easy install via an automatic installer program called aroma installer, no need to flash boot.img here
http://forum.xda-developers.com/showthread.php?t=2051865
Sent from my One S using xda app-developers app
yes, ck your md5's. i use es explorer and it is easy
as john said you can try another rom, but still ck md5 and wipe system as part of your wipes
if you flash a rom with aroma, don't wipe in recovery and aroma. only one. i prefer recovery
as for cwm or twrp. everyone has their favorite. it is my understanding though cwm hasn't kept pace on updates with later version roms afaik
hope you get it--
Hi everyone, I've just flashed the latest twrp recovery by mistake and I just realize that this version have some issue on flashing things. Can anyone tell me how go back to the old version?
Sent from my HTC One S using xda premium
fastboot flash recovery recovery.img the same way you updated to the new version
Or just dd your old recovery back from android terminal
If still looking, here are twrp images--
http://techerrata.com/browse/twrp2/ville
like mentioned:
fastboot flash recovery "exact recovery name here".img
I've fixed it, thanks everyone
Sent from my HTC One S using xda premium
Hi all, I just wanted to start by saying that xda is the shizz and has helped me through thick n thin. Anywho, I have a custom Rom and am trying to go to a different Rom. ViperX to be specific. I've tried before, but with little success. Extracted boot.img, fastboot flash boot boot.img in the command, put the Rom on my sd and installed via TWRP. Problem is, is that it never boots, only the HTC boot screen with the red writing. Anyone have any suggestions on what I need to do? I'm still S-on, but from what I understand, that doesn't matter if you fastboot the boot.img via command prompt. I also have Hboot 1.14.
Thanks.
Chuckles850 said:
Hi all, I just wanted to start by saying that xda is the shizz and has helped me through thick n thin. Anywho, I have a custom Rom and am trying to go to a different Rom. ViperX to be specific. I've tried before, but with little success. Extracted boot.img, fastboot flash boot boot.img in the command, put the Rom on my sd and installed via TWRP. Problem is, is that it never boots, only the HTC boot screen with the red writing. Anyone have any suggestions on what I need to do? I'm still S-on, but from what I understand, that doesn't matter if you fastboot the boot.img via command prompt. I also have Hboot 1.14.
Thanks.
Click to expand...
Click to collapse
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Will do thank you
Sent from my HTC One XL using xda app-developers app
exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Apparently there's a TWRP 2.4.4 out, would it hurt me to flash the latest version?
Sent from my HTC One XL using xda app-developers app
Yes. It would hurt anyone with a one xl as 2.4 does not wipe our device properly. I tested 2.4.4 myself.
Sent from my HTC One X using xda app-developers app
ok, well I found another problem you might be able to help me with, but I'll shoot it to you anyway. I just found out my phone was originally a One X when I got it from the ATT store. Now apparently after I flashed the Rom I got (odex-JB-Sense4+.zip), It's saying my phone is an XL. Seems to me I have a whole new set of issues. Did I flash the wrong Rom? I though I did enough research to find a compatible Rom. How do I find out for sure what's going on with my phone and how to fix it properly?
Chuckles850 said:
ok, well I found another problem you might be able to help me with, but I'll shoot it to you anyway. I just found out my phone was originally a One X when I got it from the ATT store. Now apparently after I flashed the Rom I got (odex-JB-Sense4+.zip), It's saying my phone is an XL. Seems to me I have a whole new set of issues. Did I flash the wrong Rom? I though I did enough research to find a compatible Rom. How do I find out for sure what's going on with my phone and how to fix it properly?
Click to expand...
Click to collapse
No problem you have the correct ROM, if you had flashed wrong one it would have not worked correctly. Depending on the ROM sometimes it will show XL instead of X.
One xl is the proper model name, code named Evita, not to be confused with the real HTC One X international quad core version.
So in other words, nothing is wrong. This is normal. If you flashed the wrong rom you would know as you would now have a paperweight
Sent from my HTC One X using xda app-developers app
ok cool, I was kinda confused there for a sec lol. Ok, now for the TWRP. I'm assuming you were referring to 2.3.0.0? just because there is a 2.3.0.0, 2.3.1.0, 2.3.3.0, and a 2.3.3.1. I just want to make sure I have the correct one for Hboot 1.14
Doesn't matter which one. I use 2.3.3.1 myself.
Sent from my HTC One X using xda app-developers app
You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium
ok, downloading it now. I'll keep you updated.
bkmo said:
You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Ah I didn't catch that in the first post! Good eye.
bkmo said:
You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
ok, I'll keep that in mind. Thank you!!
exad said:
Ah I didn't catch that in the first post! Good eye.
Click to expand...
Click to collapse
it's ok bud, just downloaded and installed TWRP 2.3.3.1 successfully, now i'm downloading ViperXL and hope everything comes out ok
exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Should I need to be thinking about Kernels of any sort?
Chuckles850 said:
Should I need to be thinking about Kernels of any sort?
Click to expand...
Click to collapse
Yeah.......give bulletproof 1.1 a shot. Gonna give you better performance and battery, plus a no brainer install and its stable.
Sent from my Transformer TF101 using xda premium
bkmo said:
Yeah.......give bulletproof 1.1 a shot. Gonna give you better performance and battery, plus a no brainer install and its stable.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Ok cool. Any links?
Sent from my HTC One X using xda app-developers app
It's in Android development page. if not the first page then the second.
exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
Click to expand...
Click to collapse
Except for ViperXL (and old builds of CleanROM, which may also happen with future builds if/when scrosler gets AROMA back in there) which is intended to flash the boot.img in AROMA.
Although, it doesn't always work for some folks, so they have had to flash boot.img manually. So yes, if at all in doubt (and you have a boot loop) flash boot.img manually.
ONE S C2
Help i cant get any rom to work ( Stuck at Boot Animation )
All i did was wiped cache, delvik cache and system after that
flashed the rom
extract the boot.img file from the rom and flashed it
fastboot flash boot boot.img
fastboot erase cache
Click to expand...
Click to collapse
i was using 4.1.1 stock rom and stock kernal
am i missing something ?
do i need to install a kernal or is there any other way to fix this
tried couple of roms CM 10/10.1
tried using TWRP 2.3.1.0 , TWRP 2.4.1.0 , TWRP 2.5.0.0 same result
btw i can go back to stock using my nandroid backup without any problems (4.1.1) ,
Thanks.
Is the ROM actually made for the C2 variant? Because you have done everything right, it must just be that the ROM is basically for the wrong phone
By the way, use TWRP 2.3.3.0. Best one.
Sent from my HTC One S using xda premium
kylepont said:
Is the ROM actually made for the C2 variant? Because you have done everything right, it must just be that the ROM is basically for the wrong phone
By the way, use TWRP 2.3.3.0. Best one.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Thanks for the reply , i have manage to fixed it strange though all i had to did was
instead of using
fastboot flash boot boot.img
fastboot erase cache
Click to expand...
Click to collapse
use it without the "erase cache" and it works perfectly
no idea why though it works now
Hope this help
Sent from my HTC One X using xda app-developers app
Did you have a cwm based recovery then flash twrp? That happens when you switch. If so you have to flash a non touch cwm then flash twrp and wipe cache after every flash
Sent from my HTC One using Tapatalk 4
I think the process is:
Non touch CWM
Touch CWM
TWRP
With fastboot erase cache between each flash.
Sent from my Evita
I just fastboot erase cache
fastboot flash recovery cwm whatever current version is
then installed the rom..
i think that dialer issue affects first gen htc one x owners some sort of dialer issue internally affected it they released a newer model with the fix.
i only say this bc my manager had the first gen and i had to flash cwm for him to get his dialer to work
timmaaa said:
I think the process is:
Non touch CWM
Touch CWM
TWRP
With fastboot erase cache between each flash.
Sent from my Evita
Click to expand...
Click to collapse
scrizo said:
I just fastboot erase cache
fastboot flash recovery cwm whatever current version is
then installed the rom..
i think that dialer issue affects first gen htc one x owners some sort of dialer issue internally affected it they released a newer model with the fix.
i only say this bc my manager had the first gen and i had to flash cwm for him to get his dialer to work
Click to expand...
Click to collapse
no.
This is a CWM - TWRP issue. If he flashes back to CWM it will work again.
Ah ok thanks for clearing that up, was curious because my hox ran fine with twrp 2.6 and venom Rom
Sent from my HTC One X using xda app-developers app
timmaaa said:
I think the process is:
Non touch CWM
Touch CWM
TWRP
With fastboot erase cache between each flash.
Sent from my Evita
Click to expand...
Click to collapse
Like always.. thanks.. u should make a rom.. i feel it would be amazing
classified_noob said:
Like always.. thanks.. u should make a rom.. i feel it would be amazing
Click to expand...
Click to collapse
Lol thanks but I don't have the necessary knowledge to do that yet, I'm still learning, maybe in a year or two.
Sent from my Evita
I bet you can learn fast.. it's like makin a cake. Same way to make just different flavors
Sent from my HTC One X using xda app-developers app