[Q] Custom Kernel and OTA Update - Vibrant Q&A, Help & Troubleshooting

I've tried to keep my Vibrant as close to stock as possible because I don't want to lose the OTA update capability. I don't want to have to flash to stock via Odin before I update my phone because it is hardware locked. So far, I've only done minor mods (metamorph, removed bloat).
So if I install a custom kernel such as JAC's or KK's overclocked kernels, will I lose the ability to OTA update? Will the update simply overwrite the existing kernel on my phone?

richan90 said:
I've tried to keep my Vibrant as close to stock as possible because I don't want to lose the OTA update capability. I don't want to have to flash to stock via Odin before I update my phone because it is hardware locked. So far, I've only done minor mods (metamorph, removed bloat).
So if I install a custom kernel such as JAC's or KK's overclocked kernels, will I lose the ability to OTA update? Will the update simply overwrite the existing kernel on my phone?
Click to expand...
Click to collapse
Most likely the devs in this forum will have a working and better version of any OTA you will get. Also when you get the OTA you will loose root and most likely get the bloat back. In my opinion you are better off waiting for one of eugene or bionix roms anyway.

To be more specific, my question is whether updating to any future ROM/OTA update will overwrite the existing kernel, or do I have to flash the stock kernel back before any of this?

richan90 said:
To be more specific, my question is whether updating to any future ROM/OTA update will overwrite the existing kernel, or do I have to flash the stock kernel back before any of this?
Click to expand...
Click to collapse
You have to flash the stock kernal in order to be able to receive an OTA
Frankin-Twiz Final, awesome

can a stock kernal be flashed right over a custom kernal? (jac oc/uv)

kboater said:
can a stock kernal be flashed right over a custom kernal? (jac oc/uv)
Click to expand...
Click to collapse
I think so, unless you have any kind of lagfix installed. I say so because I have flashed ROMS like Bionix (which has its own kernel) over stock and vice versa. MAKE SURE NO LAGFIX IS INSTALLED!

is there a link for a stock kernel that can be flashed through clockwork recovery as a zip without ODIN?
Im assuming there is as I flashed the OC/UV Jac kernel though clockwork, so assuming that stock should be able to be flashed through clockwork.
Thanks
EDIT:
Can someone confirm that this is the stock kernel that can be flashed through clockwork? If I flash this (just stay rooted and with mobile AP) I should go back to be able to receive OTA updates, correct (I have not flashed any custom roms, just kernel)??
http://www.tabbal.net/files/Stock-Vibrant-Kernel.zip

Related

minimum that needs to be done to receive OTA update?

I was just wondering, since I'm pretty much stock with JAC's OC/UV kernel, what the minimum I have to do to get the OTA update?
So far i've only flashed back to the stock kernal via clockwerk, but I'm still rooted (which is stated in the tips thread that it doesn't affect one's ability to receive OTA updates) with the GPS files pulled from the "sneak release" a while back. Other than that, I have launcherpro and mobileAP, while everything else is bone stock.
Is there anything else I have to do? I don't want to odin a completely stock rom because I don't want to deal with the bloatware all over again, but I'm just paranoid that i'm just not getting OTA updates since the announcement was broadcasted 10/7
Thanks in advanced, and I'm sorry if i'm just beating a dead cow
I think you need to have the stock kernel in order to receive the OTA updates
Sent from my SGH-T959 using XDA App
where do I get teh stock kernel and do I use clockwork to flash it??

Optimus one stable gingerbread ROM

Hello there!
I'm a n00b at this, and I just managed to flash a custom kernel on my Optimus one. (I needed it for overclocking)
I was wondering, what the most stable Gingerbread ROM is, for the Optimus one right now? I heard the unofficial CM7 ROM is a bit unstable
Also, can anyone give me instructions on how to use the ROM? Can I use ROM Manager?
Or should I boot into the clockwork mod recovery and flash zips from there?
Thanks in advance!
Go to this link:
http://www.megaupload.com/?f=XGKNWZQJ
look for CWM 3.1.0.0, flash it ( I didnt use Rom Manager)
than look for CM7, wipe dalvik/wipe everything, than flash that rom....it's not to bad of a rom
1.All roms based on official 2.3.3 are stable,while cm7 roms have some minor bugs.
2.Rom manager is a tool to install clockworkmod recovery directly.
3.now u can flash zip from cwm.
Thanks a lot for the replies folks!
I'll try out the official 2.3.3 ROM now.
What about Megatron? I know it's froyo, but the performance is supposed to be top notch Is it stable enough?
And another n00b question, don't mind,
If I flash any of these ROMs, official 2.3.3 or CM7 or Megatron, do I retain root access?
sp1408 said:
Thanks a lot for the replies folks!
I'll try out the official 2.3.3 ROM now.
What about Megatron? I know it's froyo, but the performance is supposed to be top notch Is it stable enough?
And another n00b question, don't mind,
If I flash any of these ROMs, official 2.3.3 or CM7 or Megatron, do I retain root access?
Click to expand...
Click to collapse
Go to the link that Jrhodes85 gave you and download both ClockworkMod 3.1.0.0 and AmonRA 2.2.1a, since you'll need to switch from one to the other depending on the ROM that you want to flash. As a very general rule older ROMs (like Megatron or LOL) need AmonRA, whereas newer ROMs (most 2.2.2 and 2.3.x based ROMs) will need ClockWorkMod (still you have to check the specific ROM post as they usually specify which recovery you need). Remember that these recoveries are ZIP-flashable, meaning that you can switch from one to the other simply by flashing from recovery (that is, you can be using Clockworkmod and flash AmonRA using the flash zip option and once you reboot into recovery you'll have your new recovery and viceversa).
I've tried most of the ROMs around here (except the 2.3's) and for me the most stable/better battery life is definitely LOL 1.4.2, still the best way to know is test them yourself (as every user is different).
Regarding the "root access" question if you flash any of the unofficial 2.3.x you'll keep root access, the only way that I think you'll lose root access is if you flash an official LG ROM. Keep in mind that that process is different since you won't be using a custom recovery but a tool called KDZ. I would advice to go that way only when you feel pretty comfortable flashing unofficial ROMs back and forth.
The other thing to keep in mind is that for ROMs "based" on the official 2.3.3 code there's an additional step that involves flashing a new "baseband" (this doesnt applies if you just want to flash any of the unofficial 2.3.4 ROMs like Andy's or Mik's CM7). The baseband flashing involves additional tools to the custom recovery so proceed with caution.
So if I flash any kind of stock Gingerbread ROM, I'll have to do the baseband?
(Is there and "unofficial stock Gingerbread ROM", without bugs? I wouldn't know )
So if I use kdz and flash an official Gingerbread ROM, I'll lose recovery and root right?
Can I use ROM Manager to get the CM7 mod or Megatron or the stock GB? Or should I flash from cwm?
sp1408 said:
So if I flash any kind of stock Gingerbread ROM, I'll have to do the baseband?
(Is there and "unofficial stock Gingerbread ROM", without bugs? I wouldn't know )
So if I use kdz and flash an official Gingerbread ROM, I'll lose recovery and root right?
Can I use ROM Manager to get the CM7 mod or Megatron or the stock GB? Or should I flash from cwm?
Click to expand...
Click to collapse
See below. Other than that, all of this has been answered about zillion times.
http://goo.gl/HJ2Gw
But what about ROM Manager? Can I use it to flash CM7 or Megatron?
And I have cwm installed. I've done a backup with it. Is this enough? how is it different from a Nandroid backup?
Also, is it necessary to partition my sd card for the same? Or can I move apps to it later on, by some other means?
(Pardon me, this is the first ROM I'm flashing )
Please read the dictionary and faq. Your questions have been answered previously. But, you don't need rom manager if you already have cwm. You also don't need to partition your sd card if you don't want to use a2sd/data2sd.
You will also need titanium for apps backup. There are other apps for contacts and messages backup.
Sent from my LG-P500 using XDA App
All of them are somewhat unstable, or buggy, but so is the official stock firmware I say CM7 6.5.5.

[Q] Understanding Android firmware updates

I have a SGS2 with the default ROM the phone came with, and CF-Root installed with CWM v3.0.0.5. Specifically, this is what’s installed:
Baseband version: I9100XXKDJ
Kernel: version 2.6.35.7-I9100XWKE8-CL214845, [email protected]#2
I just launched Kies to check for a firmware update, and was told this:
Current firmware: PDA:KE2 / PHONE:KDJ / CSC:KE2 (NEE)
Latest firmware: PDA:KF3 / PHONE:KE7 / CSC:KF1 (NEE)
I don’t quite understand what constitutes the Android firmware as I’ve recently migrated from iOS where baseband (modem) and OS are the two versions one needs to keep in mind (or just OS, if you had an unlocked iPhone like I did) for a jailbreak/unlock. Thus a few questions:
1. What are the PDA, PHONE and CSC parts of the firmware?
2. Why are there so many types of firmware; if you look at Chainfire’s CF-Root post there’s a host of patched kernels. Are SGS2s sold in regions with varying hardware? With the iPhone there was one hardware version, one OS (Verizon excluded). Simple.
3. I want to flash a custom ROM (Batista70 based on 2.3.4) - what is the best way to make sure everything is up to date before I do this? I was thinking of letting Kies update (which I guess will remove my root access), then installing the latest version of CF-Root with CWM 4, and finally flashing the ROM from CWM. I have the relevant app data backed up with Titanium Backup.
Many thanks!
Nitsson said:
I have a SGS2 with the default ROM the phone came with, and CF-Root installed with CWM v3.0.0.5. Specifically, this is what’s installed:
Baseband version: I9100XXKDJ
Kernel: version 2.6.35.7-I9100XWKE8-CL214845, [email protected]#2
I just launched Kies to check for a firmware update, and was told this:
Current firmware: PDA:KE2 / PHONE:KDJ / CSC:KE2 (NEE)
Latest firmware: PDA:KF3 / PHONE:KE7 / CSC:KF1 (NEE)
I don’t quite understand what constitutes the Android firmware as I’ve recently migrated from iOS where baseband (modem) and OS are the two versions one needs to keep in mind (or just OS, if you had an unlocked iPhone like I did) for a jailbreak/unlock. Thus a few questions:
1. What are the PDA, PHONE and CSC parts of the firmware?
2. Why are there so many types of firmware; if you look at Chainfire’s CF-Root post there’s a host of patched kernels. Are SGS2s sold in regions with varying hardware? With the iPhone there was one hardware version, one OS (Verizon excluded). Simple.
3. I want to flash a custom ROM (Batista70 based on 2.3.4) - what is the best way to make sure everything is up to date before I do this? I was thinking of letting Kies update (which I guess will remove my root access), then installing the latest version of CF-Root with CWM 4, and finally flashing the ROM from CWM. I have the relevant app data backed up with Titanium Backup.
Many thanks!
Click to expand...
Click to collapse
1. Pda is the basic firmware, Phone is the modem responsible for wifi/2g/3g, csc is the country specific code - language files/apps etc. You shouldn't consider these as separate, they all combine to make a single firmware (which will have the pda code)
2. There are multiple firmwares because they keep getting updated, the cf-root has multiple versions to accomodate those who haven't update to the latest. Usually the highest alphabetical and number code is the latest, currently kg3 i believe
3. Whatever kies updates, flashing a rom over it will overwrite anyway so there's no point using kies
Make a nandroid backup from cwm before you start flashing ROM in case something goes wrong
Ok, so neither pda, phone or scs constitute the kernel? I appreciate that custom ROMs incorporate the official (and sometimes the unofficial) Samsung releases meaning I don't need to faff around with Kies, but CF-Root handles only the kernel if understand it correctly.
In Chainfire's guide on rooting, specifically the but on getting rid of the warning triangle, he says "Find an original Samsung signed stock kernel (preferably from the same stock firmware you have, but it's not terribly important)" which I don't understand. How can I find a kernel, all I have are ROMs which as I understand it do not include the kernel.
Nitsson said:
Ok, so neither pda, phone or scs constitute the kernel? I appreciate that custom ROMs incorporate the official (and sometimes the unofficial) Samsung releases meaning I don't need to faff around with Kies, but CF-Root handles only the kernel if understand it correctly.
In Chainfire's guide on rooting, specifically the but on getting rid of the warning triangle, he says "Find an original Samsung signed stock kernel (preferably from the same stock firmware you have, but it's not terribly important)" which I don't understand. How can I find a kernel, all I have are ROMs which as I understand it do not include the kernel.
Click to expand...
Click to collapse
here is all the roms and kernels
if you read closely under each rom their is also a link for kernels.
http://forum.xda-developers.com/showthread.php?t=1075278
Nitsson said:
Ok, so neither pda, phone or scs constitute the kernel? I appreciate that custom ROMs incorporate the official (and sometimes the unofficial) Samsung releases meaning I don't need to faff around with Kies, but CF-Root handles only the kernel if understand it correctly.
In Chainfire's guide on rooting, specifically the but on getting rid of the warning triangle, he says "Find an original Samsung signed stock kernel (preferably from the same stock firmware you have, but it's not terribly important)" which I don't understand. How can I find a kernel, all I have are ROMs which as I understand it do not include the kernel.
Click to expand...
Click to collapse
Kernel is a (small) part of PDA. So flash PDA replaces the kernel. But you can flash kernel separately without changing the other parts of PDA.
Sent from my GT-I9100 using Tapatalk
zabihjan said:
here is all the roms and kernels
if you read closely under each rom their is also a link for kernels.
http://forum.xda-developers.com/showthread.php?t=1075278
Click to expand...
Click to collapse
tjtj4444 said:
Kernel is a (small) part of PDA. So flash PDA replaces the kernel. But you can flash kernel separately without changing the other parts of PDA.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Great, thanks. So if I flash a custom ROM based on KG2, do I need to flash the ROM first followed by CF-Root? I imagine that if I flash CF-Root first and then the customer ROM via CWM, this will overwrite portions of CF-Root which is needed for CWM etc.
Nitsson said:
Great, thanks. So if I flash a custom ROM based on KG2, do I need to flash the ROM first followed by CF-Root? I imagine that if I flash CF-Root first and then the customer ROM via CWM, this will overwrite portions of CF-Root which is needed for CWM etc.
Click to expand...
Click to collapse
CF-Root (flashed through Odin) is the 1st step in running a custom rom. The kernel will replace the stock samsung recovery with the clockworkmod recovery which is then used to flash custom ROMs
Custom ROMs may replace the CF-Root kernel but no responsible dev would include a kernel that removes the CWM recovery so you do not need to worry about overwriting it.
On a side note, in an original full stock rom (in tar format) the zImage file within the tar is the kernel, if you wanted to flash the original kernel back then you would remove all the other files from the tar (and leave zImage) and flash the tar in Odin as PDA.. although this wouldn't be a great idea as it would remove the custom CWM recovery
About point 3 - flashing a rom is the 'update'. Forget about KIES when you start flashing your roms, because all of the software is in there, the rom itself.
viva.fidel said:
CF-Root (flashed through Odin) is the 1st step in running a custom rom. The kernel will replace the stock samsung recovery with the clockworkmod recovery which is then used to flash custom ROMs
Custom ROMs may replace the CF-Root kernel but no responsible dev would include a kernel that removes the CWM recovery so you do not need to worry about overwriting it.
Click to expand...
Click to collapse
viva.fidel said:
On a side note, in an original full stock rom (in tar format) the zImage file within the tar is the kernel, if you wanted to flash the original kernel back then you would remove all the other files from the tar (and leave zImage) and flash the tar in Odin as PDA.. although this wouldn't be a great idea as it would remove the custom CWM recovery
Click to expand...
Click to collapse
Excellent, I get that part. Good explanation.
How about the order of flashing; the custom ROM I want to try is based on KG3, and I also want to flash the updated CF-Root v.4.1 KG3 kernel followed by the stock Samsung kernel to rid myself of that warning triangle (any future flashing I will do through CWM and not Odin). Should I install the custom ROM via my current version of recovery, then, upgrade CF-Root via the patched KG3 kernel, and finally flash the stock Samsung KG3 kernel?
Since I'm using KE2 at the moment, I'm thinking that flashing just a KG3 kernel to get CF-Root 4.1 isn't a best idea, as the KE2 firmware overall might not be compatible with a KG3 kernel.
Custom rom has to be installed as per each developers instructions for each individual rom .Not all are CWM flashable .
Personnel i would upgrade the CF root to the later verion before rthe custom rom but i would also read the details of the rom has it may have the latest CWM installed .
jje
Nitsson said:
Excellent, I get that part. Good explanation.
How about the order of flashing; the custom ROM I want to try is based on KG3, and I also want to flash the updated CF-Root v.4.1 KG3 kernel followed by the stock Samsung kernel to rid myself of that warning triangle (any future flashing I will do through CWM and not Odin). Should I install the custom ROM via my current version of recovery, then, upgrade CF-Root via the patched KG3 kernel, and finally flash the stock Samsung KG3 kernel?
Since I'm using KE2 at the moment, I'm thinking that flashing just a KG3 kernel to get CF-Root 4.1 isn't a best idea, as the KE2 firmware overall might not be compatible with a KG3 kernel.
Click to expand...
Click to collapse
which rom are you trying to flash? If it needs to be flashed through cwm then you'll have to flash a custom kernel through odin first to give you cwm recovery (custom rom can't be flashed with the stock samsung recovery), then flash the rom in cwm. Does the rom include cf-root? If it doesn't then flash the cf-root kernel and then the stock kernel to get rid of the triangle
If the rom can be flashed through odin then you can skip flashing the initial cwm-enabling ke2 kernel
Sent from my GT-I9100 using XDA App
JJEgan said:
Custom rom has to be installed as per each developers instructions for each individual rom .Not all are CWM flashable .
Personnel i would upgrade the CF root to the later verion before rthe custom rom but i would also read the details of the rom has it may have the latest CWM installed .
Click to expand...
Click to collapse
Ok thanks. I also think that I should install the latest version of CF-Root first.
viva.fidel said:
which rom are you trying to flash? If it needs to be flashed through cwm then you'll have to flash a custom kernel through odin first to give you cwm recovery (custom rom can't be flashed with the stock samsung recovery), then flash the rom in cwm. Does the rom include cf-root? If it doesn't then flash the cf-root kernel and then the stock kernel to get rid of the triangle
If the rom can be flashed through odin then you can skip flashing the initial cwm-enabling ke2 kernel
Click to expand...
Click to collapse
It's the Batista 3.2 ROM that I intend to flash. I already have CF-Root / recovery installed, and this ROM also installs recovery v4.0.1.4, but what I don't know if this is the same as the recovery included in CF-Root - most likely not.
I'll probably go ahead and will flash the custom CF-Root KG3 kernel and the stock KG3 kernel via Odin to get rid of the triangle, and finally the ROM via recovery. That should do it.
Should be pinned. This was exactly was I wanted to know and maybe many others too.
Nitsson said:
It's the Batista 3.2 ROM that I intend to flash. I already have CF-Root / recovery installed, and this ROM also installs recovery v4.0.1.4, but what I don't know if this is the same as the recovery included in CF-Root - most likely not.
I'll probably go ahead and will flash the custom CF-Root KG3 kernel and the stock KG3 kernel via Odin to get rid of the triangle, and finally the ROM via recovery. That should do it.
Click to expand...
Click to collapse
Think CF-Root comes with CWM 4.0.0.2
Looks like Batista's ROM includes a kernel.. you should therefore flash the ROM first, then CF-Root (so it overwrites the ROM kernel) and then the stock samsung-signed KG3 kernel
viva.fidel said:
Think CF-Root comes with CWM 4.0.0.2
Looks like Batista's ROM includes a kernel.. you should therefore flash the ROM first, then CF-Root (so it overwrites the ROM kernel) and then the stock samsung-signed KG3 kernel
Click to expand...
Click to collapse
I did exactly that Just flashed the CF-Root kernel via the CWM app at the end to have all the goodies. Works a treat so far but I'll see over the coming weeks.

Flashable stock kernel

Ok, I can't find the stock kernel to flash back, as I'm tired of the OTA updates nagging me.
I'm currently on stock ROM with Ninphetemine's kernel.
Anyone can help?
Why do you want to go back to stock to apply an update?
Updates will replace the kernel anway
I read somewhere that it's the kernel that's screwing up the OTA. I'm rooted via Chainfire's method and his stuff supports OTA so I'm sure it's the kernel that's causing the problem.
squeeish said:
Ok, I can't find the stock kernel to flash back, as I'm tired of the OTA updates nagging me.
I'm currently on stock ROM with Ninphetemine's kernel.
Anyone can help?
Click to expand...
Click to collapse
Posted in the usual place .
http://forum.xda-developers.com/showthread.php?t=1671969
jje

OTA update/brick bug?

I just picked up a second SGS2 for my wife. She does not care about a bunch of custom stuff on her phone. She wants it to "just work right" as she puts it. I do however want to root it for the purposes of CWM rom backup and app backup. My question is, will the genuine update of ICS automatically bring the brick bug with it if I update OTA or through kies? I know I need a different kernel for cwm etc. Looks like maybe I want the stock rom from the Semi16 thread?
Sent from my SGH-I777 using xda premium
highaltitude said:
Looks like maybe I want the stock rom from the Semi16 thread?
Click to expand...
Click to collapse
That's the way I would go.
Stock ICS UCLE5 with a custom kernel is an option. Stock Gingerbread with a custom kernel is another option. If you root and install a custom kernel, the phone will not update automatically, since it will not have the stock kernel.
My son's phone is still stock Gingerbread 2.3.4 with Entropy512's daily driver kernel which I installed for him way back in December.

Categories

Resources