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.
Related
Whats this problem with the boot.img?
So to flash a rom, I need to flash the boot.img using the boot installer tool, then I put the rom on my SD card and flash it?
Do I also have to flash the boot.img to restore my phone from a previous recovery? I heard this somewhere and was a bit confused,
Just download a ROM from the phone itself. Use flash image GUI. Using flashgui app, Navigate to ROM you downloaded, click. It'll automatically flash kernel. Immediately after boot into recovery, flash entire ROM, then flash gapps if necessary... Profit
Sent from my One X using Tapatalk 2
CollegeProfesor said:
Whats this problem with the boot.img?
So to flash a rom, I need to flash the boot.img using the boot installer tool, then I put the rom on my SD card and flash it?
Do I also have to flash the boot.img to restore my phone from a previous recovery? I heard this somewhere and was a bit confused,
Click to expand...
Click to collapse
There are a couple of roms that are hboot 1.14 friendly right? Doesn't viper have the ability to flash the kernel upon install?
Sent from my HTC One XL using xda app-developers app
I'm not really into sense ROMs, but I know viperxl and cleanrom 5.1 you can flash ROM in recovery.. they're definitely good to have on your SD card as a safety net in case something goes crazy and there's no way to fast boot...
Sent from my One X using Tapatalk 2
I know you guys hate this, but I need help.
I have an HTC One S, unlocked. I am in Canada, it's unlocked for Mobilicity, but not sure where it came from originally.
How do I know what exact version phone I have, and how do I go about getting a newer android version on it. 4.2.2 or at least 4.2.
AW: [Q] Complete Help
What do you mean with "version"
Look under settings->phone information or sth like that. Latest official version for the one s is android 4.1.1.
If you mean which model, check how your CPU frequency is, 1,7ghz is the C2/S3, 1,5ghz is the C1/S4.
If you want android 4.2.2 flash a custom recovery and follow the instruction for flashing a custom rom (cm10.1), you will find it in the development section
Sent from my HTC One S using xda premium
Ok, so I want to install
http://forum.xda-developers.com/showthread.php?t=2051865
Not sure how. I have 1.06 band and 3.08-01575 kernel version.
hboot 1.14....what do I need to do to get this installed. It says something about aroma installer, but have no idea how to use that.
AW: [Q] Complete Help
Aroma installer is a GUI for the installing progress.
Wipe everything twice before flashing the Rom.
Extract the Boot.IMG Form the flash zip.
Flash the Boot.IMG via fastboot ("fastboot flash boot boot.img" there are flashing guides in the forum)
Clear dalvik cache
Flash the rom and everything should work fine
Good luck
Sent from my HTC One S using xda premium
NQNH said:
Aroma installer is a GUI for the installing progress.
Wipe everything twice before flashing the Rom.
Extract the Boot.IMG Form the flash zip.
Flash the Boot.IMG via fastboot ("fastboot flash boot boot.img" there are flashing guides in the forum)
Clear dalvik cache
Flash the rom and everything should work fine
Good luck
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I don't see any boot.img inside the zip file?
I am reading all you do is extract the zip, but I don't see the boot.img once that is done? Help please.
AW: [Q] Complete Help
Sry my fault, didnt read the thread carefully, you dont need the boot.img
You cam flash the Rom the usual way
Sent from my HTC One S using xda premium
NQNH said:
Sry my fault, didnt read the thread carefully, you dont need the boot.img
You cam flash the Rom the usual way
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
So wipe it twice, then install from zip? That's it?
AW: [Q] Complete Help
I think so
Sent from my HTC One S using xda premium
I have an AT&T One XL and have had problems recently. I unlocked my bootloader last year on the 2.20 firmware, which is how the phone came. I was able to flash ROMs no problem. About 3 weeks ago I decided to go S-Off with the whole thing. The S-Off was successful, I immediately flashed a new splashscreen and it is confirmed in bootloader that I am S-off. Last week I tried to flash the stable CM10 build, but it was unsuccessful. I found that the only ROMs I am able to flash are Sense ROMs 4.1.1 and above, or AOSP ROMs that are 4.2.x or above. I am on hboot 1.14 and I am very confused as to why I cannot flash properly. I am on TWRP 2.4.1.0, but have used various recoveries trying to solve the problem. I have also RUU'd trying to fix the problem, but to no avail. Any help would be much appreciated!
Twrp 2.4 has issues with wiping properly. Have you tried a different version or wiping with adb in fastboot?
Sent from my HTC One X using xda premium
From what I understand twrp 2.4.1 should be working but I would flash 2.3.x just in case, then do fastboot erase cache. Then wipe cache, dalvik, system, factory reset.
If you RUUd and are s-off why are you still on 1.14? You may as well go up to 2.14 then downgrade touchscreen to use AOSP. Super easy.
Since S-OFF is just a security flag, I am 100% sure it's not the cause of your issue.
Sent from my One X using xda app-developers app
exad said:
From what I understand twrp 2.4.1 should be working but I would flash 2.3.x just in case, then do fastboot erase cache. Then wipe cache, dalvik, system, factory reset.
If you RUUd and are s-off why are you still on 1.14? You may as well go up to 2.14 then downgrade touchscreen to use AOSP. Super easy.
Since S-OFF is just a security flag, I am 100% sure it's not the cause of your issue.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I haven't wiped in fastboot because I thought that's what wiping in recovery was for, I really appreciate all of the input and I will be trying both of these things as soon as I'm done with dinner. Man's gotta eat, ya know :laugh:
Lol. Yep.
Sent from my HTC One X using xda premium
Only fastboot erase cache! The rest of the wiping is done in recovery!
Sent from my One X using xda app-developers app
exad said:
Only fastboot erase cache! The rest of the wiping is done in recovery!
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
As a question, what is the difference between wiping cache in recovery and the fastboot command?
Downgrade twrp to 2.3.3.1
Sent from the HOXL dimension of S-OFF
The fastboot command wipes a cache related to the recovery. Wiping cache in recovery wipes a cache relating to the rom.
Sent from my One X using xda app-developers app
exad said:
The fastboot command wipes a cache related to the recovery. Wiping cache in recovery wipes a cache relating to the rom.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
So I wiped cache via fastboot, and flashed the ROM like i normally would (wipe everything in recovery), but nothing has changed. I still get hung up on the splashscreen when trying to boot the new ROM. ViperXL boots fine when I restore my NANDroid backup, though.
Did you try flashing the boot.img after? You're still on hboot 1.14 afterall. I haven't seen first hand if you can skip flashing the boot.img with s-off, in your case, it seems not.
Sent from my One X using xda app-developers app
exad said:
Did you try flashing the boot.img after? You're still on hboot 1.14 afterall. I haven't seen first hand if you can skip flashing the boot.img with s-off, in your case, it seems not.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Even without flashing the boot.img, it should go past the splashscreen to the boot animation, am I wrong?
You are wrong. It may depending on the kernel previously installed
Sent from my One X using xda app-developers app
exad said:
You are wrong. It may depending on the kernel previously installed
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Sorry to sound like a complete noob, I've been rooting ect for 2.5 years and never seen this problem. Could you please explain a bit more what you mean by the previous post. Are you saying it's the kernel or the boot.img not being installed correctly?
WeiblezWobble said:
Sorry to sound like a complete noob, I've been rooting ect for 2.5 years and never seen this problem. Could you please explain a bit more what you mean by the previous post. Are you saying it's the kernel or the boot.img not being installed correctly?
Click to expand...
Click to collapse
flashing the boot.img is flashing the kernel. you don't sound like a complete noob so don't worry.
I'm going to try again right now to flash the boot.img and then the ROM like normal, reporting back in 15 mins
WeiblezWobble said:
I'm going to try again right now to flash the boot.img and then the ROM like normal, reporting back in 15 mins
Click to expand...
Click to collapse
wipe everything first of course. cache dalvik system and factory reset. i dont mean to treat you like a noob but its better to be extra specific than not specific enough
exad said:
wipe everything first of course. cache dalvik system and factory reset. i dont mean to treat you like a noob but its better to be extra specific than not specific enough
Click to expand...
Click to collapse
Alright, tried it all exactly how you said and it had the same response, got stuck on splashscreen. I am completely puzzled
WeiblezWobble said:
Alright, tried it all exactly how you said and it had the same response, got stuck on splashscreen. I am completely puzzled
Click to expand...
Click to collapse
alright so just to be sure. first off youre on twrp 2.3.x right?
you wipe cache, dalvik, system and factory reset right?
then you flash the rom and the boot.img right? (doesnt matter what order these are flashed)
and still bootlooping?
exad said:
alright so just to be sure. first off youre on twrp 2.3.x right?
you wipe cache, dalvik, system and factory reset right?
then you flash the rom and the boot.img right? (doesnt matter what order these are flashed)
and still bootlooping?
Click to expand...
Click to collapse
Exactly, but just to be 100% clear, I am getting stuck at the splashscreen, and it just sits there infinitely.
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.
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