As reported by many users upgrading to kernel 2.6.32.28 will kill Skype on your GTAB ( It will be stuck on Sign-in)
Can anyone PLEASE post link where to download the older
2.6.32.9-dirty kernel?
THANKS
Reflash the custom rom you are using. It will give you the kernel you want. Dont wipe data and you wont lose anything. It will replace the custom kernel you installed with the one that came with Vegan rom.
Thanks, I may have to do that.
I wish there was a way just to extract the kernel from the zip file.
thebadfrog said:
Reflash the custom rom you are using. It will give you the kernel you want. Dont wipe data and you wont lose anything. It will replace the custom kernel you installed with the one that came with Vegan rom.
Click to expand...
Click to collapse
Thanks a lot
Skype works well now..
Related
Where do i get JUST a kernal (Air Kernal 3.9)?
i cannot find it alone and i already have a rom on and id like to not get rid of it.
Im pretty sure you can just flash a kernal over the older one.
anyone have links?
Thanks.
Nickozz said:
Where do i get JUST a kernal (Air Kernal 3.9)?
i cannot find it alone and i already have a rom on and id like to not get rid of it.
Im pretty sure you can just flash a kernal over the older one.
anyone have links?
Thanks.
Click to expand...
Click to collapse
Nick ... it's an easy operation to change kernels. Go to the proper development forum and d/l the Air kernel for your device to your SD card. Boot into recovery, wipe the cache and dalvik cache, and flash the new kernel. Reboot and you should be good to go.
Further: if you're using ICS and are on a gsm phone, this is the thread link ...
http://forum.xda-developers.com/showthread.php?t=1469842
If you're on ICS and a Sprint NS4g phone, this is the thread link ...
http://forum.xda-developers.com/showthread.php?t=1516535
Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!
devcager said:
Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!
Click to expand...
Click to collapse
I can't use Adam's Jelly Belly rom, as I have a NS4g, but I do follow his work. I believe that his rom comes with Thalamus kernel, and if you want to flash a different kernel, there is a file which needs to be deleted before doing so. There was quite a discussion about all this in his thread in the development forum. That's where you can figure it out ... good luck!
same for me
Hey i also tried to flash thalamus kernel but my phone didnt start it was hanged up on the boot screen. I am using Nexus S i9023 SCLD version stock rom 4.1.1 build JRO03E and it is rooted.
Can anyone please help me and also which other kernels are supported on stock rom.
There's a script you must delete in the init.d to use another kernel in Jelly Belly 0.1.5
Otherwise, your phone will poweroff
panks_4ever said:
Hey i also tried to flash thalamus kernel but my phone didnt start it was hanged up on the boot screen. I am using Nexus S i9023 SCLD version stock rom 4.1.1 build JRO03E and it is rooted.
Can anyone please help me and also which other kernels are supported on stock rom.
Click to expand...
Click to collapse
i have also a i9023 and i have allredy flashed bedalus kernel, thalamus and air kernel also matrix and vta2 worked for me..
i use JRO03E DX stock ROM..never had a problem
S.R.
(I use stock JB with Air #153, and got i9023. No OC, no NSTools, yet. I have no problem.)
On stock:
Try to do a factory reset/wipe data, or reflash the OS from scratch using factory images. And right after flashing the rom, flash the kernel. Even before installing any apps.
On JBelly:
For this, I think the Thalamus kernel is the best, the rom is come with it, so they made for each other If this kernel works with it, i think it is unnecessary to switch to another kernel right now.
Because JB kernels are not final yet, are "immature", there can be compatibility issues, collisions between (certain functions of) roms and kernels.
After a 2 or 3 releases, both on rom and kernel side, there will be more complete and stable versions.
Have you tried to fix permissions ?
Go to /etc/init.d/ folder and delete a file called 'kernel'. You can read it first if you want.
This is basically a hack that AdamG added to avoid everyone changing kernels and reporting problems about the ROM. He only allows thalamus kernel.
Can please provide me detailed steps of how to flash a thalamus kernel on stock jb because i think the procedure is wrong. I did the following steps:
1. Reboot into recovery( I am using Clockwork Mod recovery touch 6.0.1.0)
2. Wipe Cache partition
3. Wipe Dalvik cache
4. Install the kernel zip file
And after i tried restarting my phone but it hanged up on the boot screen.
Please someone advise me the correct steps if this is wrong
. Thanks in advance
Sent from my Nexus S using xda app-developers app
panks_4ever said:
1. Reboot into recovery( I am using Clockwork Mod recovery touch 6.0.1.0)
2. Wipe Cache partition
3. Wipe Dalvik cache
4. Install the kernel zip file
Click to expand...
Click to collapse
I think the cache partition wipe is your problem. You shouldn't have to wipe anything if you're flashing _thalamus' kernel on stock JB. Just flash and reboot. I've done it plenty of times without problems.
devcager said:
Hi,
I tried several kernels for JB. Air, Matrix. None of them worked for me. After flashing it, it won't boot the system and turn off the device. I currently use JellyBelly 1.5. Any idea? Is it ROM bug? Thanks!
Click to expand...
Click to collapse
To not have to deal with third party kernel support there is /system/etc/init.d/00kernel that simply powers off your phone if you flash another kernel.
Flash the rom to boot it, delete the file, then flash any kernel you want as you usually would.
charchuck said:
I think the cache partition wipe is your problem. You shouldn't have to wipe anything if you're flashing _thalamus' kernel on stock JB. Just flash and reboot. I've done it plenty of times without problems.
Click to expand...
Click to collapse
wipe is not needed...
but fix permissions should be done...but I´m not sure thats required for all kernel.
S.R.
so this are the final steps...
shivasrage said:
wipe is not needed...
but fix permissions should be done...but I´m not sure thats required for all kernel.
S.R.
Click to expand...
Click to collapse
Firstly, thanks for replying. I need to do the folloing steps (just to confirm because its better to do so and also i dont want to again restore a backup)
1. Reboot into recovery
2. Wipe Dalvik Cache
3. Install the kernel zip file
4. Fix Permissions
or 3. Fix Permissions, and then
4. Install kernel zip file
Please advise the correct steps and thanks in advance.
(I know i am getting a bit more concerned because i had it twice and i am not able to flash the same. So, I am trying to get a correct way and this the best place to ask. XDA rocksssssss<3<3<3)
panks_4ever said:
Firstly, thanks for replying. I need to do the folloing steps (just to confirm because its better to do so and also i dont want to again restore a backup)
1. Reboot into recovery
2. Wipe Dalvik Cache
3. Install the kernel zip file
4. Fix Permissions
or 3. Fix Permissions, and then
4. Install kernel zip file
Please advise the correct steps and thanks in advance.
(I know i am getting a bit more concerned because i had it twice and i am not able to flash the same. So, I am trying to get a correct way and this the best place to ask. XDA rocksssssss<3<3<3)
Click to expand...
Click to collapse
There's no need for all that... flash jellybelly latest version, boot with the original kernel and delete /system/etc/init.d/00kernel with Rom Toolbox or Root explorer. After that you can flash the kernel that you want. Mind that this will only work for version 0.1.5.1, versions after that one will probably have a framework check to prevent flashing 3rd party kernels because the dev of jellybelly doesn't want to be disturbed with bugs caused by other kernels then not the Thalamus one.
---------- Post added at 08:55 AM ---------- Previous post was at 08:34 AM ----------
Checked. Version 1.0.0 only allows Thalamus kernel to be flashed. A framework check doesn't allow 3rd party kernels to be fixed so either you stick to the stock kernel of jellybelly or get another ROM so you can use other Kernels.
Panks_4ever
What I always do.. (phone i9023 X-JB Stock).
1. flash kernel zip
2. wipe cache
3. wipe dalvik
4. fix permissions
i only know that thalamus kernel don´t need any wipe...also i don´t know if this procedure is right or not
and i don´t won´t discuss about i only can report what worked for me so try it or not its your decision....
S.R.
thank you
shivasrage said:
Panks_4ever
What I always do.. (phone i9023 X-JB Stock).
1. flash kernel zip
2. wipe cache
3. wipe dalvik
4. fix permissions
i only know that thalamus kernel don´t need any wipe...also i don´t know if this procedure is right or not
and i don´t won´t discuss about i only can report what worked for me so try it or not its your decision....
S.R.
Click to expand...
Click to collapse
DeuXGod said:
There's no need for all that... flash jellybelly latest version, boot with the original kernel and delete /system/etc/init.d/00kernel with Rom Toolbox or Root explorer. After that you can flash the kernel that you want. Mind that this will only work for version 0.1.5.1, versions after that one will probably have a framework check to prevent flashing 3rd party kernels because the dev of jellybelly doesn't want to be disturbed with bugs caused by other kernels then not the Thalamus one.
---------- Post added at 08:55 AM ---------- Previous post was at 08:34 AM ----------
Checked. Version 1.0.0 only allows Thalamus kernel to be flashed. A framework check doesn't allow 3rd party kernels to be fixed so either you stick to the stock kernel of jellybelly or get another ROM so you can use other Kernels.
Click to expand...
Click to collapse
Thank you shivasrage and DeuXGod. I am surely goona try out this, i am being eagerly waiting to flash a custom kernel because as compared to ICS i feel JB is eating up more battery. Thank you so much:good:
I recently rooted my galaxy sl using amit bagaria's universal cf root. After rebooting, the wifi wasn't switching on (it gave me an error message). So I googled it an found a solution. I flashed the bam kernel v14 (google it) and the wifi is working properly. Now, apparently the bam kernel v14 is not compatible with cm and i cannot flash any cm rom. Is that how it is supposed to be? How can i fix this? Thanks for all the help
rohit_6 said:
I recently rooted my galaxy sl using amit bagaria's universal cf root. After rebooting, the wifi wasn't switching on (it gave me an error message). So I googled it an found a solution. I flashed the bam kernel v14 (google it) and the wifi is working properly. Now, apparently the bam kernel v14 is not compatible with cm and i cannot flash any cm rom. Is that how it is supposed to be? How can i fix this? Thanks for all the help
Click to expand...
Click to collapse
The wifi problem is because you were on a value pack for 2.3.6, and if you root the device you can't use wifi unles you use bam kernel.
About CM, every ROM includes it's own kernel, so if you flash Dhiru's CM10 for example, this will come with it's own kernel and will install it automatically when you install the ROM. There are kernels for each Rom, so beware when you install a kernel on your Rom, first check if it's compatible. I think that's what you read about bam kernel, that is only compatible with Gingerbread.
PS: Please be more specific on the title next time
salaesp said:
The wifi problem is because you were on a value pack for 2.3.6, and if you root the device you can't use wifi unles you use bam kernel.
About CM, every ROM includes it's own kernel, so if you flash Dhiru's CM10 for example, this will come with it's own kernel and will install it automatically when you install the ROM. There are kernels for each Rom, so beware when you install a kernel on your Rom, first check if it's compatible. I think that's what you read about bam kernel, that is only compatible with Gingerbread.
PS: Please be more specific on the title next time
Click to expand...
Click to collapse
Alright.....now for example I want to flash Dhiru's CM10, how do I go about doing it? The normal way....with Odin? Just flash it PDA??
rohit_6 said:
Alright.....now for example I want to flash Dhiru's CM10, how do I go about doing it? The normal way....with Odin? Just flash it PDA??
Click to expand...
Click to collapse
No, you have to flash it using CWM. Please follow the installation instructions given in CM10 from dhiru:
http://forum.xda-developers.com/showthread.php?t=1868074
You are on stock rom, so follow the stock rom steps. You can skip the root step if you already rooted it.
As an advice, I suggest you make a /efs folder backup. This folder from your phone keeps a lot of information about it. I had some problems with 3g and stuff, and recovering it helped me. Before doing anything please read some threads about flashing this device.
Good luck!
I'd like to remove the trinity Kernel for JellyBean. I enjoy it's overclock but I hate it when my phone just randomly reboots. Is there a way to remove it. I have created a backup before I flashed it, but I'd like to remove it without having to restore to that backup.
Thanks
flash your rom without wiping, then flash gapps
ej8989 said:
flash your rom without wiping, then flash gapps
Click to expand...
Click to collapse
I should have mentioned, I'm running stock. No custom rom installed
Just flash a different custom kernel or the stock kernel. If you want a different custom kernel, and you want something stockish, you wan try SimpleKernel or thalamus kernel. As for the stock, I think you can find a flashable zip somewhere here in the NS forum.
Phone is rooted, CWM installed latest, recovery e3 does not check signatures.
Can I just create nandroid backup, wipe phone and install this one rom for example?
AjvarXX said:
Phone is rooted, CWM installed latest, recovery e3 does not check signatures.
Can I just create nandroid backup, wipe phone and install this one rom for example?
Click to expand...
Click to collapse
Yep.. You take a backup, wipe cache,data and dalvik cache. You are ready to flash your custom rom.. But while changing kernels you gotta flash your stock rom+stock kernel then root then flash new kernel then the custom rom.
haridevil99 said:
Yep.. You take a backup, wipe cache,data and dalvik cache. You are ready to flash your custom rom.. But while changing kernels you gotta flash your stock rom+stock kernel then root then flash new kernel then the custom rom.
Click to expand...
Click to collapse
Appreciate. So I now will backup and wipe everything and then update it with kies mini. And then will ask more about custom stuff, am I doing right?
The problem about SGS4G is that it is WAY TOO MUCH information about it as well as kernels, mods, articles and you are lost because some of them conflicts with other.
P.S. I spent a week for going into Android stuff and Galaxy S.
AjvarXX said:
Appreciate. So I now will backup and wipe everything and then update it with kies mini. And then will ask more about custom stuff, am I doing right?
The problem about SGS4G is that it is WAY TOO MUCH information about it as well as kernels, mods, articles and you are lost because some of them conflicts with other.
P.S. I spent a week for going into Android stuff and Galaxy S.
Click to expand...
Click to collapse
Well.. If you were talking bout updating your stock rom using kies... I dont see any use of that if you are going to flash a custom rom. Its just mere waste of time.
haridevil99 said:
Well.. If you were talking bout updating your stock rom using kies... I dont see any use of that if you are going to flash a custom rom. Its just mere waste of time.
Click to expand...
Click to collapse
it's because 2.2 version is so hard for modding that I didn't risk to update from it.
Now I have modded kernel on stock 2.3.6. And thinking about what ROM to use.
Here is a link I found recently and it is so very helpful! http://forum.xda-developers.com/showthread.php?t=1470716
AjvarXX said:
it's because 2.2 version is so hard for modding that I didn't risk to update from it.
Now I have modded kernel on stock 2.3.6. And thinking about what ROM to use.
Here is a link I found recently and it is so very helpful! http://forum.xda-developers.com/showthread.php?t=1470716
Click to expand...
Click to collapse
The guide seems good enough but a bit more complicated that it should be. Anyway here are two tips or info for you. First, whatever you do, have Odin and Stock Firmware ready to flash coz when everything else fails, Odin to the rescue and also flash stock firmware (Rom+kernel) whenever you change kernel as changing kernels without doing so removes root access and you cant apply root update on a custom kernel unless it has pre root access. Second, you dont need any kind of manager to flash firmwares and updates. CWM is a replacement to all. But its all your choice.