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
Related
First of all, I heard that Google had an API error in 4.1.2 that causes the mobile data or internet data to consume twice as fast. Which means you use 2x more data compared to normal. Is this true? and has it been fixed in CM10?
Secondly, if I am going to flash a new ROM, do I have to flash the ROM first then flash the boot.img separately? Or just flash everything together in the recovery? When should I flash the boot.img separately? I am kinda new to this new phones I so don't know about much these things.
Sent from my One X using xda premium
You only need to flash boot.img separately if you are on hboot 1.14 or higher. Otherwise, it will just flash in TWRP automatically when you flash the ROM.
Don't know about your other questions.
That's "tons" of questions??? That's just 2!
CalamitySir said:
First of all, I heard that Google had an API error in 4.1.2 that causes the mobile data or internet data to consume twice as fast. Which means you use 2x more data compared to normal. Is this true? and has it been fixed in CM10?
Secondly, if I am going to flash a new ROM, do I have to flash the ROM first then flash the boot.img separately? Or just flash everything together in the recovery? When should I flash the boot.img separately? I am kinda new to this new phones I so don't know about much these things.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Where did you hear that? Seems like bs because your carrier measures the amount of data on their servers
If you have hboot 1.14 then you have to flash the boot.IMG separately after you flash the ROM
Otherwise you flash everything in recovery all at once
Sent from my One X using Tapatalk 2
superchilpil said:
Where did you hear that? Seems like bs because your carrier measures the amount of data on their servers
If you have hboot 1.14 then you have to flash the boot.IMG separately after you flash the ROM
Otherwise you flash everything in recovery all at once
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Then how do I downgrade the hboot?
Another question is that when I tried to flash 4.1.1 ROMs when coming from 4.1.2 Roms, it stuck in the boot logo.
Sent from my One X using xda premium
You'll pretty much have to flash boot.IMG seperate every time... Or it will boot loop.
Sent from my One X using Tapatalk 2
InflatedTitan said:
You'll pretty much have to flash boot.IMG seperate every time... Or it will boot loop.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
ok now the question is, do i flash the boot.img first then flash the rom or flsah the rom first then the boot.img??!! The latter method was reccomendded by devs in the HOX section and the former one was used in ours?
I tried ROM then kernel on my cousins phone... Bootlooped.. Started fresh, flashed kernel then ROM and works perfectly every time
Sent from my One X using Tapatalk 2
Another question is the ss below, the total amount of data doesn't add up correctly....is this a bug or was it already predetermined like this?
Sent from my One X using xda premium
CalamitySir said:
Then how do I downgrade the hboot?
Click to expand...
Click to collapse
Tool here (but requires a Linux machine): http://forum.xda-developers.com/showthread.php?t=1982442
The total amount of data doesn't add up. Is this a bug in CM10?
Sent from my One X using xda premium
I'm still not seeing the "tons" of questions.
iElvis said:
I'm still not seeing the "tons" of questions.
Click to expand...
Click to collapse
maybe u cna help me answer the question regarding the data in page one, i have 2 screenshots for that.
Another question is how do i flash the b6 kernel for cm10? flash like normal in twrp or flash the boot.img? i am messed up!
CalamitySir said:
maybe u cna help me answer the question regarding the data in page one, i have 2 screenshots for that.
Another question is how do i flash the b6 kernel for cm10? flash like normal in twrp or flash the boot.img? i am messed up!
Click to expand...
Click to collapse
I have heard only that there may be a bug in CM that makes your data usage appear to be worse. That's all I know.
I have never used CM so I can't help with the kernel. If you're on 1.14 you have to flash it separately in fastboot.
iElvis said:
I have heard only that there may be a bug in CM that makes your data usage appear to be worse. That's all I know.
I have never used CM so I can't help with the kernel. If you're on 1.14 you have to flash it separately in fastboot.
Click to expand...
Click to collapse
ok. does fastboot makes me unable to downgrade the android version, i tried to flash 4.1.1 from 4.1.2, i did it separately and it didnt work, stuck at bootloop... any idea?
Well you have to flash the boot.img from the 4.1.1 rom. Maybe try flashing the older gapps http://goo.im/gapps/gapps-jb-20120726-signed.zip I would also wipe cache, dalvik and system. Use flashimagegui for kernel flashing so you dont need to use fastboot and a pc http://forum.xda-developers.com/showthread.php?t=1963896
Here's what I do and I have flashed every ROM in this section without a single boot loop.
Flash boot IMG in fast boot
Reboot to recovery
Wipe dalvik and cache
Wipe system
Factory reset
Flash rom and gapps or just ROM (sense)
Reboot system
Do I do steps I don't need? Perhaps. But the results are hard to argue
Sent from my One X using xda app-developers app
smolck said:
Here's what I do and I have flashed every ROM in this section without a single boot loop.
Flash boot IMG in fast boot
Reboot to recovery
Wipe dalvik and cache
Wipe system
Factory reset
Flash rom and gapps or just ROM (sense)
Reboot system
Do I do steps I don't need? Perhaps. But the results are hard to argue
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
do i have to follow this sequence to wipe everytime?
Usually if its same rom u dont need to factory reset[wipe data] but ive been wiping system alot each time though.
I somehow flashed Cyanogen Mod with ClockWork Recovery, and it boots up properly. However it I can't use the touchscreen.
I am using an HTC One XL
Cyanogen Mod 10
Help would be appreciated and please make instructions as simple as possible
Thanks
kingsukhoi said:
I somehow flashed Cyanogen Mod with ClockWork Recovery, and it boots up properly. However it I can't use the touchscreen.
I am using an HTC One XL
Cyanogen Mod 10
Help would be appreciated and please make instructions as simple as possible
Thanks
Click to expand...
Click to collapse
Go into fastboot and type 'fastboot flash boot boot.img' without the quotes of course. And switch to twrp cwm isn't supported on our device and has major bugs that could possibly turn your phone into a weight
By the way make sure you put the boot.img that was in the ROM zip into your fastboot folder
Sent from my HTC One XL using xda app-developers app
The touchscreen still dosen't work
Kole_Ackerson said:
Go into fastboot and type 'fastboot flash boot boot.img' without the quotes of course. And switch to twrp cwm isn't supported on our device and has major bugs that could possibly turn your phone into a weight
By the way make sure you put the boot.img that was in the ROM zip into your fastboot folder
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ok, so I flashed TWRP on it and installed CleanRom Version 5.1, flashed the boot image, but I still can't use the touch screen.
I know the touch screen isn't broken because I can use the interface on TWRP perfectly.
Dose any one else know any roms for the HTC One XL from Rogers that work.
Thanks
Seems as though you were on rogers or Telstra and took the ota...you can only run jb sense roms right now so maybe I suggest viper
A good one I like is king kang I works for me
Sent from my One X using xda app-developers app
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 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.
The dialer app is not working at all I can't receive calls nor can I make calls it says "Unfurtunately, the process com.android.htcdialer has stopped" and this just hapens on sense ROMS on every of them, the aosp ones work just great but I want sense right now (Magio ROM R3.6.1) Does anybody knows how to fix this?
remulacha said:
The dialer app is not working at all I can't receive calls nor can I make calls it says "Unfurtunately, the process com.android.htcdialer has stopped" and this just hapens on sense ROMS on every of them, the aosp ones work just great but I want sense right now (Magio ROM R3.6.1) Does anybody knows how to fix this?
Click to expand...
Click to collapse
are you wiping everything before flashing the sense rom?
Try fastboot command:
fastboot erase cache
Then wipe cache in TWRP.
Sent from my Evita
This is a bug from going from touch cwm to twrp
You can either reflash cwm and stay on it or reflash cwm then flash a non touch cwm then flash twrp. Using fastboot erase cache after every recovery flash.
Sent from my HTC One X using xda app-developers app
exad said:
This is a bug from going from touch cwm to twrp
You can either reflash cwm and stay on it or reflash cwm then flash a non touch cwm then flash twrp. Using fastboot erase cache after every recovery flash.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I will try to flash cwm thanks
exad said:
This is a bug from going from touch cwm to twrp
You can either reflash cwm and stay on it or reflash cwm then flash a non touch cwm then flash twrp. Using fastboot erase cache after every recovery flash.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I nkow this is an old post. I hit the thanks button; clearly not enough so I had to post to say it.
THANK YOU!!!!!!
I know it sounds dumb but I search for 2 days before I found this and it work 100%!!! My phone is 100% working again! I can't thank you enough; I was really worried I messed it up because I had tried a "german 4.2.2" on it. It seemed laggy slow* wonder if that would be the recovery. But I got the RUU from HTC for my phone (4.1.1) done that and poof nothing working(your fix worked). still debating on trying the 4.2.2 again. It is nice has some cool features. But I know 4.1.1 works great.
Sorry got of track. THANKS AGAIN!