I just flashed the latest stable CM10 and it is working well. If I were to flash a new ROM, do I have to flash a new boot.IMG for it to work? And if I were to update my CM10, do I need to flash the new boot.IMG in the new update?
Sent from my One X using xda premium
If you are on ATT version 2.20, yes you need to flash the boot.img when you flash a new rom.
You shouldn't need to when upgrading CM10, however, but if there are kernel changes you may want to, to take full advantage.
area51avenger said:
If you are on ATT version 2.20, yes you need to flash the boot.img when you flash a new rom.
You shouldn't need to when upgrading CM10, however, but if there are kernel changes you may want to, to take full advantage.
Click to expand...
Click to collapse
Then while doing so, do I need to full wipe or just wipe cache and dalvik?
Sent from my One X using xda premium
For going from ics <-> aosp full wipe
For just upgrading CM10, cache and dalvik should be enough
Related
I just flashed the 8/15 version of PA and was wondering if i have to completely wipe everything just to update to 8/18?
It is always recommended to do so to avoid any problems. But you can flash without the wipes and if you run into many issues, wipe and reflash
Sent from my sweet & buttery Infuse
I just flashed the pa jb update without wiping anything and it caused a world of problems for me I had to wipe and and start fresh to have a smoothly running phone again !!! Hope that helps
Sent from my SGH-I997 using xda premium
Flashing Paranoid
stevenk007 said:
I just flashed the 8/15 version of PA and was wondering if i have to completely wipe everything just to update to 8/18?
Click to expand...
Click to collapse
You should not have to wipe data, just wipe cache and dalvik cache. However it is a better chance of no force closes or other problems if you do wipe everything between upgrades.
following the question above about upgrading, do I also need to reflash the kernel too?
Yes you would have to flash the OC kernel again.
Sent from my sweet & buttery Infuse
digitalsunshine said:
following the question above about upgrading, do I also need to reflash the kernel too?
Click to expand...
Click to collapse
Or, you can just replace the boot.img from the PA zip with the one from OC kenel zip file (i.e. extract all the files on your PC, replace the file, re-zip, and flash as per-norm).
When going from one ROM to another (ie. AOKP to CM10), is it only necessary to do a "clean" wipe, or are other steps recommended, such as reverting to stock first? I used to have a Droid 2 and people used to recommend that, but I don't know if it's necessary with this phone.
Also, what exactly does a "clean" wipe entail? I've seen multiple explanations. This guide suggests that you need only wipe data/factory reset and format system. Other people mention things like wiping cache and dalvik cache from recovery. Is there any sort of consensus on this?
Lastly, is it necessary to do these "clean" wipes when flashing a new nightly or new build, or does this simply vary depending on the ROM in question?
Thanks.
If you change ROMs most people recommend doing a data wipe.
Clean wipe is wiping data. If you wipe data, /cache is wiped too, so any subsequent cache wiping is unnecessary.
It is not necessary to wipe data when flashing a nightly or updated build.
When going from one Rom to another or one base to another (4.1 to 4.1.2) a full wipe is recommended that's system, data, cache. Nightly builds are usually safe to flash on top of each other unless otherwise noted. Biggest advice I can give is if you don't do a full wipe and encounter bugs you should go back and do a full wipe to ensure its the dirty wipe that caused it.
Neverendingxsin said:
When going from one Rom to another or one base to another (4.1 to 4.1.2) a full wipe is recommended that's system, data, cache. Nightly builds are usually safe to flash on top of each other unless otherwise noted. Biggest advice I can give is if you don't do a full wipe and encounter bugs you should go back and do a full wipe to ensure its the dirty wipe that caused it.
Click to expand...
Click to collapse
+1 its just not worth it.. Full wipe
Also when changing roms if the rom you are running has a custom kernel and the new rom uses a stock kernel but doesnt flash it then you will wanna make sure you flash a working kernel too
Sent from my SCH-I535 using xda app-developers app
x714x said:
Also when changing roms if the rom you are running has a custom kernel and the new rom uses a stock kernel but doesnt flash it then you will wanna make sure you flash a working kernel too
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Ha, I have made this mistake before.
x714x said:
Also when changing roms if the rom you are running has a custom kernel and the new rom uses a stock kernel but doesnt flash it then you will wanna make sure you flash a working kernel too
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
How can I verify this? It looks like AOKP has a custom kernel; what are the extra steps I need to take if I want to go to CM10 or back to stock?
Quacker said:
How can I verify this? It looks like AOKP has a custom kernel; what are the extra steps I need to take if I want to go to CM10 or back to stock?
Click to expand...
Click to collapse
If you're on AOSP (which includes CM10 and AOKP) then you'll need to reflash an ICS Touchwiz Kernel to go back to stock. You can go from CM10 to AOKP on the same kernel, depending on the merges. Sometimes new merges make it so an older kernel won't boot, etc.
I have the unofficial AOKP ROM on my one s and its running smoothly. I am not sure how i should update. "Flash boot.img and then install rom over existing ROM" or "Wipe all then flash boot.img and install fresh new updated ROM"?
I usually wipe unless dev specifies bit needed. But if you are using the same Rom then wiping shouldn't be an issue.
Please post questions in the q&a action
Sent from my HTC VLE_U using xda app-developers app
yes Q&A
if you are just going to new version of aokp, with no framework changes, i just flash rom then gapps, no wipe at all. some wipe caches. but i found i lose some settings that way
on the latest cm10 nightlies, no need to flash gapps. there is a script that keeps it on phone afaik
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.
Hi!
I have couple of questions regarding boot.img, kernels and how they relate to ROMs.
1. I believe every ROM comes with a kernel. Am I right?
2. Say I'm running CM10 and decide to flash beastmode bricked kernel and later flash Viper OneS. Do I still have beastmode kernel in Viper or has the kernel now been replaced by Viper's kernel? (Answer to q 1 might also answer this one...)
3. I believe boot.img is where the kernel is in a ROM. Am I correct?
4. What else does boot.img actually contain? The name atleast refers to some stuff needed for booting...
Thans !
Sent from my HTC One S using xda app-developers app
1. Yes, most likely. All ROMs Ive flashed has come with a kernel, either in the rom.zip file or as a separate download.
2. You will have to reflash the kernel if youre on hboot 1.14+ at least. If you are updating a ROM, as in not wiping anything, the kernel does not have to be reflashed.
In some cases you still have to fastboot flash it to get the updated rom to boot though.
3. Yes, Im quite sure it is. That has been the case with the ROMs Ive flashed at least.
4. It contains the ramdisc, which is pretty much everything related to the booting process, some settings and some other modules.
Goatshocker said:
1. Yes, most likely. All ROMs Ive flashed has come with a kernel, either in the rom.zip file or as a separate download.
2. You will have to reflash the kernel if youre on hboot 1.14+ at least. If you are updating a ROM, as in not wiping anything, the kernel does not have to be reflashed.
In some cases you still have to fastboot flash it to get the updated rom to boot though.
3. Yes, Im quite sure it is. That has been the case with the ROMs Ive flashed at least.
4. It contains the ramdisc, which is pretty much everything related to the booting process, some settings and some other modules.
Click to expand...
Click to collapse
Thanks for your answer! That cleared alot.
About the question 2... So if I have a kernel other than that which came with the ROM, I just have to fastboot flash boot.img of the ROM to revert back to the ROM's own kernel?
I am on hboot 2.15.
Sent from my HTC One S using xda app-developers app
zaak00 said:
Thanks for your answer! That cleared alot.
About the question 2... So if I have a kernel other than that which came with the ROM, I just have to fastboot flash boot.img of the ROM to revert back to the ROM's own kernel?
I am on hboot 2.15.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yep that right.