Hi,
I had a few questions about kernels...hope someone can help me in answering these...
I am thinking of trying out the Netarchy kernel on my Nexus S, but i was just wondering is there anywhere I can download the stock kernel (so that if anything does go wrong i dont have to do a full nandroid restore?)
Also, when installing a new kernel does that wipe data (of course I will make a backup etc before installing it, but should all my settings and apps etc remain intact normally?)
what impact does an OTA update have if i am running a non stock kernel? so say i am using Netarchy's kernel, and google releases a new OTA update...will i still be able to install the update? If i do, will it revert to stock kernel?
Thanks in advance,
brownmonkey said:
Hi,
I had a few questions about kernels...hope someone can help me in answering these...
I am thinking of trying out the Netarchy kernel on my Nexus S, but i was just wondering is there anywhere I can download the stock kernel (so that if anything does go wrong i dont have to do a full nandroid restore?)
Also, when installing a new kernel does that wipe data (of course I will make a backup etc before installing it, but should all my settings and apps etc remain intact normally?)
what impact does an OTA update have if i am running a non stock kernel? so say i am using Netarchy's kernel, and google releases a new OTA update...will i still be able to install the update? If i do, will it revert to stock kernel?
Thanks in advance,
Click to expand...
Click to collapse
I'm not aware of anywhere that the stock kernel is available for download so doing a NANDroid backup is really your best option. If you have anything that deviates from stock (kernel, rom, theme, even just deleted stock apps) it will prevent you from being able to successfully update from an OTA.
You can find a lot of information about all the available kernels here just scroll down to the third post and you'll find the info.
Finally, just as a note of personal opinion, getting OTA updates is a little overrated. If you run a custom ROM, the OTAs will be included in those ROMs eventually so you won't have to worry about restoring a stock ROM just to get the updates.
kenvan19 said:
I'm not aware of anywhere that the stock kernel is available for download so doing a NANDroid backup is really your best option. If you have anything that deviates from stock (kernel, rom, theme, even just deleted stock apps) it will prevent you from being able to successfully update from an OTA.
You can find a lot of information about all the available kernels here just scroll down to the third post and you'll find the info.
Finally, just as a note of personal opinion, getting OTA updates is a little overrated. If you run a custom ROM, the OTAs will be included in those ROMs eventually so you won't have to worry about restoring a stock ROM just to get the updates.
Click to expand...
Click to collapse
Thanks for the quick answer. I had read that post before (it was actually how i came to discover kernels ). The reason why I was asking about the OTA is because I actually use the stock ROM but was just thinking about trying out the Netarchy kernel just to see what its all about. Hence if there is an OTA update, and i am running a different kernel to the stock, is the only way for me to incorporate the update by flashing the new stock rom and then reinstall the netarchy kernel?
Also, if i install it, do you know if it wipes data/apps?
Thanks
brownmonkey said:
Thanks for the quick answer. I had read that post before (it was actually how i came to discover kernels ). The reason why I was asking about the OTA is because I actually use the stock ROM but was just thinking about trying out the Netarchy kernel just to see what its all about. Hence if there is an OTA update, and i am running a different kernel to the stock, is the only way for me to incorporate the update by flashing the new stock rom and then reinstall the netarchy kernel?
Also, if i install it, do you know if it wipes data/apps?
Thanks
Click to expand...
Click to collapse
I apologize as I forgot to mention that part of your question, I'm sick with the flu and a little out of it on some cold medications lol. You only lose data and apps when flashing if you wipe the /data partition in mounts and storage and this is not required nor is it recommended when flashing a kernel. Sorry for answering out of order, but I thought I should clear that up first. As to the other question, you have it correct; you would need to flash the new update ROM and then flashing a new kernel.
I should also note that whenever you install a new ROM, you will need to reflash a custom kernel. This is because the vast majority of ROMs released include a kernel and when you flash them it will overwrite whatever kernel you currently have.
Finally, if you have any other questions you can always feel free to post them on that thread. I'm the one who wrote it and I check it often to try and answer questions as best and as quickly as I can. Happy flashing!
Are you using a custom ROM? Flashing CM7 has the stock kernel. There are probably other ones out there that includes stock kernel with them such as OTA.
Related
Hello Everyone,
I have in the last 3 or 4 days joined in the rooted party of phones. With the Stock 2.2 rooted ROM on my Incredible i have tried a number of Circle Battery mods without success.
Thanks to the people that did a walk through on nandroid backups and restores i have not completely broke my phone.
With the above being known i apologize to anyone that reads this and says to them self "IDIOT!!" but i have a few questions I'm hoping i can get some answers on from other people with Incredibles.
1. If I install a different ROM like Cyanogen or Uncommon Sense to get the Circle Battery mod working will i be able to get back to my stock 2.2 rooted ROM using the restore like i did before?
1a. Is doing the ROM update done just like installing a mod "recovery-->install from .zip-->choose .zip"?
2. Is the Stock 2.2 rooted ROM worth staying with?
2a. If not and Verizon comes out with 3.0 or whatever the next number is can i go back to the stock ROM?
3. Does anyone have any known working Circle Battery mods for the Incredible running stock 2.2 rooted? ((I'm looking for something like "Ultimate Online Theme Kitchen") (SCB with %, Version Z, Custom type, colors--> A.))
Thanks for anyone replying.
I'm no expert, but I believe the reason the battery mod doesn't work with your stock ROM is because in order for those types of customizations to work, your ROM must be de-odexed. This is pretty standard in most custom ROMs but is not the case with stock.
As for your questions:
kevinlferguson said:
1. If I install a different ROM like Cyanogen or Uncommon Sense to get the Circle Battery mod working will i be able to get back to my stock 2.2 rooted ROM using the restore like i did before?
Click to expand...
Click to collapse
Yes, but when you do the restore everything will go back to the way it was before you flashed the new ROM. You won't be able to restore and keep the battery icon. When you create a nandroid backup, it's essentially a complete snapshot inside and out of everything on your phone.
kevinlferguson said:
1a. Is doing the ROM update done just like installing a mod "recovery-->install from .zip-->choose .zip"?
Click to expand...
Click to collapse
Yes. Be sure to wipe data/cache when flashing a new ROM though, otherwise you will run into problems. Always have a nandroid backup before flashing anything new just in case!
kevinlferguson said:
2. Is the Stock 2.2 rooted ROM worth staying with?
Click to expand...
Click to collapse
It depends on what you are looking for. Many ROMs include additional features, performance tweaks and customization options not available with stock. I'd suggest trying a few out to see what fits your tastes. If you're looking for something similar to stock with all the junk removed and ability to add things like custom battery modifications, I would give Virtuous a try.
kevinlferguson said:
2a. If not and Verizon comes out with 3.0 or whatever the next number is can i go back to the stock ROM?
Click to expand...
Click to collapse
For the most part, I would just stay rooted, as you'll most likely be able to get an official 3.0 ROM leak before Verizon gets an OTA out anyway. However, there are ways to revert to stock and unroot your device if you really want to. A little searching of these forums can provide you with a guide on how to do this.[/QUOTE]
Sent from my Droid Incredible
Wow... thanks for the information XideXL i think i will try a few other ROMs like your suggest and just keep my nandroid backup on hand should anything go bad.
Hi, I'm new to flashing ROM's and wanted to give this a try, but I had a few questions (I searched and read the wiki, but I didn't see these specific questions):
I have the Samsung Galaxy S2 Skyrocket on ATT. I'm rooted on Stock GB 2.3.6
1. I wanted to try flashing this ROM([ROM][CyanogenMod 9 (unofficial)][TeamChopsticks][Alpha 1 - 4/26]), Can I come from gingerbread if I follow the instructions in post 1? Or do I need to have an ICS leak installed first?
2. I assume I can revert back to my rooted-stock ROM by using CWM with my current restore point?
3. If I restore the backup from step-2, does it restore the original radio (the UCLA3 radio)? Or am I stuck with the new one? Any disadvantes to just leaving the new one installed?
4. When flashing the new radio, is it just like flashing a ROM in CWM?
5. How would I get all my apps back on the custom ROM? (I know the contacts are linked to the google cloud) I have titanium backup pro installed now, but I read something about not restoring the apps across different ROMs?
6. If I decide to go back to my stock ROM after looking at a few custom ROMs, would I be able to get the ATT OTA updates? (I know I'd need to un-root and un-freeze all the bloatware, but I assume installing the custom ROM's would trigger the flash counter?)
7. I keep hearing about the "yellow triangle" when the flash counter is triggered. Does it only happen at boot and go away after that? Or is it always there?
Thanks in advance!
skyrockets said:
Hi, I'm new to flashing ROM's and wanted to give this a try, but I had a few questions (I searched and read the wiki, but I didn't see these specific questions):
I have the Samsung Galaxy S2 Skyrocket on ATT. I'm rooted on Stock GB 2.3.6
1. I wanted to try flashing this ROM([ROM][CyanogenMod 9 (unofficial)][TeamChopsticks][Alpha 1 - 4/26]), Can I come from gingerbread if I follow the instructions in post 1? Or do I need to have an ICS leak installed first?
2. I assume I can revert back to my rooted-stock ROM by using CWM with my current restore point?
3. If I restore the backup from step-2, does it restore the original radio (the UCLA3 radio)? Or am I stuck with the new one? Any disadvantes to just leaving the new one installed?
4. When flashing the new radio, is it just like flashing a ROM in CWM?
5. How would I get all my apps back on the custom ROM? (I know the contacts are linked to the google cloud) I have titanium backup pro installed now, but I read something about not restoring the apps across different ROMs?
6. If I decide to go back to my stock ROM after looking at a few custom ROMs, would I be able to get the ATT OTA updates? (I know I'd need to un-root and un-freeze all the bloatware, but I assume installing the custom ROM's would trigger the flash counter?)
7. I keep hearing about the "yellow triangle" when the flash counter is triggered. Does it only happen at boot and go away after that? Or is it always there?
Thanks in advance!
Click to expand...
Click to collapse
1) if you're a newb I wouldn't recommend flashing alpha versions of anything
2)You can revert back
3)No, flash a ginger radio before restoring
4)Yes, wipe cache/dalvik cache
5)You can restore apps accross the same OS, but I never do
6)Yes, if you're on official software. It wont trigger unless you flash with odin or sometimes a custom kernel like cm will trigger it. No big deal, we have a counter reset.
7)only at boot, we have counter reset, so no worries
Wow, that was a quick reply! Thanks.
Sorry if I'm dense, I just wanted to clarify two things before proceeding.
Re 1: I also saw another ROM I wanted to try, I guess I'll do that one ([ROM]SKY ICS--- 4.2D-9). Thanks for the heads up.
Re 3: From your response, am I correct to understand I can't use an ICS radio with GB? (it just wont work? or there's no advantage to keeping it?)
Re 5: Same OS meaning inside GB based ROMs or ICS based ROMs? If I go from stock GB to custom ICS, I need to re-download each app individually?
skyrockets said:
Wow, that was a quick reply! Thanks.
Sorry if I'm dense, I just wanted to clarify two things before proceeding.
Re 1: I also saw another ROM I wanted to try, I guess I'll do that one ([ROM]SKY ICS--- 4.2D-9). Thanks for the heads up.
Re 3: From your response, am I correct to understand I can't use an ICS radio with GB? (it just wont work? or there's no advantage to keeping it?)
Re 5: Same OS meaning inside GB based ROMs or ICS based ROMs? If I go from stock GB to custom ICS, I need to re-download each app individually?
Click to expand...
Click to collapse
1) very good choice, I run it and it is outstanding.
3)they will have a RIL mismatch. You can use them by deleting the system folder out of it, but I would just use the la3 radio and flash that before the rom. After a full wipe, of course.
5)Right, it ensures everything will be clean and run right.
Thanks to everyone on this board - last night I rooted my device, unlocked the bootloader, installed CWM, backed up my stock ROM, and installed CleanROM 3 Lite (which is excellent btw!). My first time doing this, so it was very helpful having all the FAQs and instructions.
On to my question: now that I am running a custom ROM, what happens if there is a newer ROM released? Do I simply re-flash that specific ROM, the same way I installed CleanROM 3 Lite?
If so, it sounds like I lose all my apps/settings... is there some way to keep that across ROMs?
Thanks!
neocryte said:
Thanks to everyone on this board - last night I rooted my device, unlocked the bootloader, installed CWM, backed up my stock ROM, and installed CleanROM 3 Lite (which is excellent btw!). My first time doing this, so it was very helpful having all the FAQs and instructions.
On to my question: now that I am running a custom ROM, what happens if there is a newer ROM released? Do I simply re-flash that specific ROM, the same way I installed CleanROM 3 Lite?
If so, it sounds like I lose all my apps/settings... is there some way to keep that across ROMs?
Thanks!
Click to expand...
Click to collapse
yes. And unless the developer says not to, you can USUALLY skip wiping /data when upgrading to the newer version of that developer's ROM.
As for keeping apps, get Titanium Backup. worth paying for.
If you are going to upgrade to the next cleanrom release, you should be fine...just flash the next release and your apps and info should be fine.
Should you choose to switch to another rom, it is typically recommended that you wipe the phone first, in which case you will lose your apps and info, so make sure everything is backed up.
The problem with keeping apps and settings across different roms is that there can be "compatibility" problems.
That makes a lot of sense, thank you guys. I thought that flashing a ROM automatically wiped everything - but I realize now that's not the case.
I will check out Titanium Backup as well.
neocryte said:
That makes a lot of sense, thank you guys. I thought that flashing a ROM automatically wiped everything - but I realize now that's not the case.
I will check out Titanium Backup as well.
Click to expand...
Click to collapse
Actually, sometimes it does. Recently some Devs are adding Aroma Installer to their ROMS. It only works on touch recoveries (I believe). I am using TWRP and it works great. It backs up your info, lets you choose different options you want for your rom (modifications, different choice of apps, look and feel, sense or senseless, etc), flashes the rom, then restores your info automatically.
Hi,
After flashing a few ROM/Kernel combinations on my dad's I9023, eventually running into problems every time, we're now tired of having to attend to the phone and just need something stable and self-sustaining, but still better than the stock offering, if possible. Reliability is the main concern, followed by performance, followed by features and easy upgradability to the next Android version (or the custom ROM's equivalent), but battery life is low priority.
Thanks in advance for any suggestion.
knzo strawberry
rasbeanjelly
flo's stock 4.1.2
The closer to stock, the safer.
Strawberry is a good candidate.
Thanks for your replies. So far, Strawberry does look like the best option. Questions:
1. Does it keep up with Android updates?
2. Once it's flashed, will updating it to the latest version require wiping user data every time?
3. Which kernel should I use with it?
Glaux said:
Thanks for your replies. So far, Strawberry does look like the best option. Questions:
1. Does it keep up with Android updates?
2. Once it's flashed, will updating it to the latest version require wiping user data every time?
3. Which kernel should I use with it?
Click to expand...
Click to collapse
1. Your question is strange. Does it get updated? Yes. Keep up with Android updates? As in cross version (GB/ICS/JB)? Probably won't. But that doesn't mean crap, because CM7/9/10 are all different and flashing from one to the other without wiping is just bad omen. So in the end, it doesn't matter if your favorite ROM moves from one version of Android to the other. You want something new? Find a new ROM. There's only very few roms that went from ICS to JB without notable changes and none as far as I'm aware that went from GB to ICS to JB.
If you mean incremental updates (say, Jellybean gets updated) then yes, most ROM cookers update their roms.
2. No
3. Included kernel
I did mean incremental updates, thanks.
Glaux said:
I did mean incremental updates, thanks.
Click to expand...
Click to collapse
Alright. Then yes, most roms available here are update incrementally by their developpers. Usually popularity brings constant updates, too.
You want true "flash and forget" for your dad, Flash factory from Google. If your Dad doesn't care if it is custom or stock, just flash factory and move on. All custom Rom's and kernels come with issues. Google's bugs are solved by Google and send the update via OTA so Dad can do it himself.
https://developers.google.com/android/nexus/images
Use this guide
http://forum.xda-developers.com/showthread.php?t=1785672
I've never had any issues with RasBeanjelly. So saying that all roms have issues and bugs is a bit weird.
Flash RasBeanjelly and trinity or bedalus kernel (check for stable one) and forget all about it as it is incredibly stable!
Sent from my Nexus S
Well I recently gave slim a run and noticed it has the ota update option, so that may be an option.
Hey, sorry for such a noob question, I do lots of reading on here and tried to post within a certain rom, C-Rom Kit-Kat 4.4.2 5/13/14, and it won't allow me since I have never posted anything on XDA. I have the Verizon HTC ONE M8 and it is bootloader unlocked, s-off, and on the stock rom with build number 1.56, with lots of customization but I found a new rom I wanted to try. It is an AOSP rom like mentioned above but I never seemed to find what build number it is on? I know with a SENSE rom you have to be careful of what build number your phone is, whether it is 1.54 before the update or 1.56 after the update.
My question is, when flashing an AOSP/AOKP/CM rom through TWRP, does the build number matter? In all the AOSP roms I never haven't been able to find where the OP states which it is, making me wonder if I need to worry about it or not? I want to flash away from the stock rom but only to an AOSP type rom.. I want to be careful because since we don't have a removable battery, I am worried I will be stuck in bootloop and I am not sure how to get out of it without a battery pull.. (I know holding power and volume up will restart the phone but how would you get back into recovery to restore a backup?)
Also while I am at my first post, do you recommend TWRP, CWM, or Philz touch recovery? I would like to stick to one recovery throughout the tenure of the rooted ONE M8, makes keeping backups
Thanks for the help and I greatly appreciate it! And I apologize again for such a noob question..
pahlerc1 said:
Hey, sorry for such a noob question, I do lots of reading on here and tried to post within a certain rom, C-Rom Kit-Kat 4.4.2 5/13/14, and it won't allow me since I have never posted anything on XDA. I have the Verizon HTC ONE M8 and it is bootloader unlocked, s-off, and on the stock rom with build number 1.56, with lots of customization but I found a new rom I wanted to try. It is an AOSP rom like mentioned above but I never seemed to find what build number it is on? I know with a SENSE rom you have to be careful of what build number your phone is, whether it is 1.54 before the update or 1.56 after the update.
My question is, when flashing an AOSP/AOKP/CM rom through TWRP, does the build number matter? In all the AOSP roms I never haven't been able to find where the OP states which it is, making me wonder if I need to worry about it or not? I want to flash away from the stock rom but only to an AOSP type rom.. I want to be careful because since we don't have a removable battery, I am worried I will be stuck in bootloop and I am not sure how to get out of it without a battery pull.. (I know holding power and volume up will restart the phone but how would you get back into recovery to restore a backup?)
Also while I am at my first post, do you recommend TWRP, CWM, or Philz touch recovery? I would like to stick to one recovery throughout the tenure of the rooted ONE M8, makes keeping backups
Thanks for the help and I greatly appreciate it! And I apologize again for such a noob question..
Click to expand...
Click to collapse
Correct me if im wrong, but the sense build is just telling what that ROM is based on. Once your S-OFF, you can flash them as you please. I know the bootloader version was what would cause bricks in the past (flashing a 4.2.2 rom in a 4.3 bootloader) but i havent seen anything like that for the M8 yet.
Vol DOwn and power will get you to hboot which will let you get to recovery. I use CWM but theyre all comparable, just personal preference.
Abe21599 said:
Correct me if im wrong, but the sense build is just telling what that ROM is based on. Once your S-OFF, you can flash them as you please. I know the bootloader version was what would cause bricks in the past (flashing a 4.2.2 rom in a 4.3 bootloader) but i havent seen anything like that for the M8 yet.
Vol DOwn and power will get you to hboot which will let you get to recovery. I use CWM but theyre all comparable, just personal preference.
Click to expand...
Click to collapse
Thanks for the reply! I can't wait to flash this new AOSP rom so I can remove all the bloatware put on by Verizon and Sense.. Just want to vierfy, so if the build number no longer matters since I am s-off, you're saying I can flash the ARHD rom on my phone even though it states the build number 1.54 and I have 1.56? Because I would also love to have a stock sense rom with lots of optimizations and tweaks for performance with less bloatware.
Thanks again
pahlerc1 said:
Thanks for the reply! I can't wait to flash this new AOSP rom so I can remove all the bloatware put on by Verizon and Sense.. Just want to vierfy, so if the build number no longer matters since I am s-off, you're saying I can flash the ARHD rom on my phone even though it states the build number 1.54 and I have 1.56? Because I would also love to have a stock sense rom with lots of optimizations and tweaks for performance with less bloatware.
Thanks again
Click to expand...
Click to collapse
I just read that if you have the newest 1.55.6.. firmware and baseband and try to flash roms with the older baseband (1.54) then you might run into problems with losing root and and other issues..
Can someone please verify this? Currently on stock rom, rooted, s off, bootloader unlocked, with baseband 1.55.6.. Looking into flashing either AOSP rom or Sense rom but does it matter if its based on 1.54 or the newest 1.56?
Thanks, the help is greatly appreciated
pahlerc1 said:
I just read that if you have the newest 1.55.6.. firmware and baseband and try to flash roms with the older baseband (1.54) then you might run into problems with losing root and and other issues..
Can someone please verify this? Currently on stock rom, rooted, s off, bootloader unlocked, with baseband 1.55.6.. Looking into flashing either AOSP rom or Sense rom but does it matter if its based on 1.54 or the newest 1.56?
Thanks, the help is greatly appreciated
Click to expand...
Click to collapse
you're just gonna end up with whatever baseband you flash as the latest baseband. where are you seeing people lose root bc of flashing a different baseband?
Abe21599 said:
you're just gonna end up with whatever baseband you flash as the latest baseband. where are you seeing people lose root bc of flashing a different baseband?
Click to expand...
Click to collapse
It was in a different thread, can't recall which.. I have been doing way too much reading I think it was in one last few pages of the venom rom thread.. I'll just wait for Venom and Skyfall to update their baseband to the latest 1.56 build. No worries. Thanks.
Updated to the latest VZW firmware, and have had no issues using the multi-variant roms, which use the non-Verizon versions. My radio base still reflects the updated version (0321). On Viper right now with no issues, waiting for AOKP. Been using 2.7.0.2 TWRP with no problems. If you have a concern about flashing any ROM (and/or gapps if you are trying an AOSP ROM), just make sure you make a backup in recovery before anything else, and if the new stuff doesn't work well or borks your device, just learn how to get back into recovery and restore your backup. Read first, try second.
ebb said:
Updated to the latest VZW firmware, and have had no issues using the multi-variant roms, which use the non-Verizon versions. My radio base still reflects the updated version (0321). On Viper right now with no issues, waiting for AOKP. Been using 2.7.0.2 TWRP with no problems. If you have a concern about flashing any ROM (and/or gapps if you are trying an AOSP ROM), just make sure you make a backup in recovery before anything else, and if the new stuff doesn't work well or borks your device, just learn how to get back into recovery and restore your backup. Read first, try second.
Click to expand...
Click to collapse
Okay thanks for the help. I always make sure to read first and create a backup, I've made the mistake once and took a long process to get it solved and won't let that happen again that's for sure! Thanks for the response, I just flashed Skyfall 2.5 and it is amazing!