Hello all,
I made this over at the GNex forums for a stock GNex 4.2/4.2.1 kernel... here it is for the Nexus 7 for those that accidentally flashed a 4.1.2 kernel or just want to get back to stock.
Flash at your own risk, should work just fine though!
UPDATED: Kernel should work now! Sorry about the bad zip before!
Will it work on 4.1.2? I have AOKP on my device, would like to flash this, just need to check if it's safe...
Cheers
Sent from my Nexus 7 using xda app-developers app
where were you couple of days ago when I was dealing with the issue - trying to flash stock kernel.....wish you posted this before.
I will save this just in case :silly:
thanks!!!
I flashed LeanKernel and then wanted to go back to stock kernel before flashing latest Faux Kernel.
So I have just flashed your kernel but "about tablet" is telling me I still have LeanKernel installed?
If you can overclock then you're still on lean kernel. Either way, I'd suggest a reflash.
Sent from my Nexus 7 using xda premium
Caliyork said:
If you can overclock then you're still on lean kernel. Either way, I'd suggest a reflash.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
It was definetely still on LeanKernel, I tried it twice.
Only issue could be that I was using an older version of TWRP that wasn't updated for 4.2, but it seemed to flash ok.
edit
Ok, tried it again now I have the updated TWRP and the same thing happens...i.e. nothing, it flashes in the normal way but changes nothing.
This is all wrong. The boot.img inside does not match the one from the N7 nakasi factory image and the updater-script is written for the Galaxy Nexus.
Code:
"of=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");
N7 certainly doesn't run OMAP. Flash at your own risk, indeed.
I urge you to take this down and make sure you know you've got it right before you put it up again. Only saving grace here is you were using the platform by-name method (which just plain won't work on the N7) instead of the actual mmc block names or you could have really messed up some peoples' devices.
osm0sis said:
This is all wrong. The boot.img inside does not match the one from the N7 nakasi factory image and the updater-script is written for the Galaxy Nexus.
Code:
"of=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");
N7 certainly doesn't run OMAP. Flash at your own risk, indeed.
Click to expand...
Click to collapse
My mistake. I thought it would just transfer over. I will fix the link... Didn't realize when I tested it I already had the stock kernel on there. Gimme a minute to fix it!
OK should be fixed and good to go! Again, my apologies!
Sent from my Galaxy Nexus using Tapatalk 2
stonebear said:
It was definetely still on LeanKernel, I tried it twice.
Only issue could be that I was using an older version of TWRP that wasn't updated for 4.2, but it seemed to flash ok.
edit
Ok, tried it again now I have the updated TWRP and the same thing happens...i.e. nothing, it flashes in the normal way but changes nothing.
Click to expand...
Click to collapse
Please try again... I have updated my zip and tested it by flashing a 4.1.2 kernel, having the device sit at the X for a few minutes without doing anything (to test a non-working kernel) then flashing my zip, and my N7 is back up and running again.
I am still learning about kernel stuff... sorry about any confusion!
SkaldfraNorden said:
Will it work on 4.1.2? I have AOKP on my device, would like to flash this, just need to check if it's safe...
Cheers
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Negative. This is the stock 4.2 kernel... I found the stock 4.1.2 kernel on XDA... Should be easy to find!
Sent from my Galaxy Nexus using Tapatalk 2
Where can I find the stock kernel for the Galaxy Nexus running on 4.2? If you can redirect me to the link, I'll greatly appreciate it. Thanks in advance.
evaradar said:
Where can I find the stock kernel for the Galaxy Nexus running on 4.2? If you can redirect me to the link, I'll greatly appreciate it. Thanks in advance.
Click to expand...
Click to collapse
wasn't that hard to find out, but here you go: stock kernel
This is JOP40C kernel for 4.2 but will it work on JOP40D 4.2.1 stock ROM please ?
I've added this kernel to the Nexus 7 Complete Index
Sent from my Nexus 7 using xda premium
..
BTW..Excellent system stability with this kernel and rasbeanjelly ROM. Tested on my daughter.
cydef said:
This is JOP40C kernel for 4.2 but will it work on JOP40D 4.2.1 stock ROM please ?
Click to expand...
Click to collapse
+1
Sent from my Nexus 7 using xda app-developers app
Can anyone confirm if the kernel listed (jop40c) is the actual kernel used in the stock 4.2.1 system? The build is jop40d, and the question seams to be getting overlooked. I cannot find the stock jop40d 4.2.1 kernel anywhere, and just do not have any interest at this time in flashing the factory image/re-rooting etc. Any help would be appreciated.
annoyingduck said:
Can anyone confirm if the kernel listed (jop40c) is the actual kernel used in the stock 4.2.1 system? The build is jop40d, and the question seams to be getting overlooked. I cannot find the stock jop40d 4.2.1 kernel anywhere, and just do not have any interest at this time in flashing the factory image/re-rooting etc. Any help would be appreciated.
Click to expand...
Click to collapse
This.. I was about to post, my N7 (16g, wifi) is JOP40D as well, not 40C.
Thinking about trying out a custom kernel, but want the stock to fall back on, as it's super stable.
khaytsus said:
This.. I was about to post, my N7 (16g, wifi) is JOP40D as well, not 40C.
Thinking about trying out a custom kernel, but want the stock to fall back on, as it's super stable.
Click to expand...
Click to collapse
As it turns out, I built a "slightly rooted" JOP40D stock flash kit yesterday (mods to build.prop in boot.img, and su/SuperSU in system.img). I'm posting this reply from that.
I started with the Google JOP40D (grouper) distro to do that. I thought I was going to need to unpack the boot.img from the OP's .zip to do comparisons of the kernels (to answer your question) ... but it turns out that his boot.img has the same MD5 sig as the boot.img from Google's JOP40D... and the OP's updater-script merely flashes boot.img to the /boot partition.
That means one of two things: either the two successive Google releases (for grouper) had identical boot images (which implies identical kernels), or there is some mistake by the OP. (I don't have the 40C distro to check ... only picked up my N7 a few days ago.)
It should work in your specific case though, as you are on JOP40D.
In any event, flashing boot.img is way way more than just a kernel replacement. I haven't looked at it for a while, but I would suppose that Koush's kernel flasher is a much more appropriate technique for switching ONLY the kernel out from underneath an arbitrary ROM.
cheers
That's great info there. I'm searching for the simplicity of just flashing a kernel instead of pushing the entire boot image. Thanks for a step in clarifying this question
Sent from my Nexus 7 using xda premium
Related
With a little of trial and error you can now flash any modem whether it be FC09 or FC19 or any other modem without odin! How you ask?!?!?! with a little renaming and rezipping youll be on a ns4g modem or a epic 4g modem without ODIN!!! And noone likes ODIN lol
All you have to do is flash the modified kernel then reboot recovery into the new recovery and then my zip either the FC19 or FC09 modem in cwm with the rom its meant for then either flash your kernel again say your on cm7 flash the modified kernel flash the modem then reflash your kernel like shadow or nyan same thing for cm9 or cm10 just make sure you have another kernel to flash so it will boot this is the only way i have figured out OR you could flash this Kernel then install the modem then after you install just reflash your rom and gapps for a fresh install. if your on cm9 you can keep the kernel installed but if your not after you get done installing the modem install the correct kernel for your rom
For Epic 4G modem!
BEFORE FLASHING MAKE SURE YOU HAVE ANOTHER KERNEL TO FLASH AFTERWARD OR YOU WONT HAVE THE EPIC MODEM! NEXUS MODEM IS ALL GOOD
These Kernels should allow changing modems if your on them.
Modified CM9 Kernel:https://dl.dropbox.com/u/60122779/Modem%20install%20kernel.zip
Modified CM7 Kernel:http://eigerzoom.com/darkjje/xbkernel-0812.zip
Modified CM10 Kernel:http://darkierawr.com/Android/Users/xboxfanj/nexusmodempatch-CM10-0808_mms.zip
FC09:https://dl.dropbox.com/u/60122779/FC09-Modem-CWM.zip
MD5:a20cd46e61909dd90919c153458e96f7
FC19:https://dl.dropbox.com/u/60122779/FC19-Modem-CWM.zip
MD5:8acd10876c767825d06d86f2a56a3b6c
DK28:https://dl.dropbox.com/u/60122779/DK28-Modem-CWM.zip
MD5:a20cd46e61909dd90919c153458e96f7
EB13:https://dl.dropbox.com/u/60122779/EB13-Modem-CWM.zip
MD5:f01e6785cd0acb381d5613d8150d4584
EC05:https://dl.dropbox.com/u/60122779/EC05-Modem-CWM.zip
MD5:429ba29d063372309affb4171285f9b6
EE03:https://dl.dropbox.com/u/60122779/EE03-Modem-CWM.zip
MD5:9552b354966b86099d02d643f02e3cf6
EH05:https://dl.dropbox.com/u/60122779/EH05-Modem-CWM.zip
MD5:63bf06b50fb3cc0b3e4e71dbb346bef8
EL30:https://dl.dropbox.com/u/60122779/EL30-Modem-CWM.zip
MD5:ec6afd25409bd1aba0242cd2c54031d0
For NS4G modem!
To be on a ns4g modem go to xboxfanj's thread http://forum.xda-developers.com/showthread.php?t=1842037
NOTE:Make sure your not on NS4G patched rom or your baseband will be unknown until you go to the appropriate rom for the modem.
HOW TO:
1.Install any of these kernels above.(doesnt matter which one because it will only be used to flash the modem)
2.Go to advanced in cwm
3.Go to reboot recovery.
4.Now that your in the new recovery flash any of the above modems.
5.Then after you flash the desired modem flash any rom and it will replace the kernel with the one from that rom.
6.flash your gapps then all should be fine.
http://www.youtube.com/watch?v=jWM8mA_4cgc
Thanks to: The CM team for Everything! and xboxfanj,marcusant,didhiy and anyone else im forgetting!!!
you mind posting the md5 or sha1s when you got a min?
Awesome job, joemossjr.
Sure will post some md5's for ya
so I'm just on normal CM7, but flashing either FC09 or FC19 doesn't seemt do anything. I'm still on EL30. md5s match. Am I missing something here?
imma try to find your problems
ok i odined the el30 modem gonna flash the Fc09 one real quick hold on
I will see if mine works.
Sent from my GT-P7510 using Tapatalk 2
The NS4G modem that was posted in this thread when I first found it works, at least if you're already on the NS4Gmod CM7
Now the question is, which NS4G modem will give an Epic the best signal and data speed... has anyone compared a few yet?
Sent from my SPH-D700 using xda app-developers app
Its is now fixed just read all the instructions and fallow all directions turns out there is a certian file that is modified in the kernel that allows the writing of modems without odin that i needed so just flash the kernel then install the modem then reflash your kernel
styles420 said:
The NS4G modem that was posted in this thread when I first found it works, at least if you're already on the NS4Gmod CM7
Now the question is, which NS4G modem will give an Epic the best signal and data speed... has anyone compared a few yet?
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
I have tried all of the nexus modems and kl2 is by far the best for me. Got 2.25 down and 1.3 up on 3g!
Sent from my SPH-D700 using xda premium
i agree that one seems to be the best
Is this worth bugging the CM team to get them to add this option to the stock kernel?
dzl said:
you mind posting the md5 or sha1s when you got a min?
Click to expand...
Click to collapse
dzl said:
Is this worth bugging the CM team to get them to add this option to the stock kernel?
Click to expand...
Click to collapse
it would really help things progress so we wouldn't have to change kernels every time we want to change a modem but its way better then fooling with Odin and having it fail half way then restart lol
WOW! Another case of "they said it couldn't be done!"
Nice work Joe!
Sent from my PantechP4100 using xda premium
Thanks man!
Okey doke, for one I tip my hat to you good sir.
Now, just so I've an idea of how you went about this.The kernel(zImage) is left untouched and this is more based upon the init's correct? The Recovery init to be more exact? Or am I off-base and there are patches to the kernel?
AproSamurai said:
Okey doke, for one I tip my hat to you good sir.
Now, just so I've an idea of how you went about this.The kernel(zImage) is left untouched and this is more based upon the init's correct? The Recovery init to be more exact? Or am I off-base and there are patches to the kernel?
Click to expand...
Click to collapse
I think no kernel related too.. first though just the updater script on ns4g modem that make it happen
will take a look further over the file
AproSamurai said:
Okey doke, for one I tip my hat to you good sir.
Now, just so I've an idea of how you went about this.The kernel(zImage) is left untouched and this is more based upon the init's correct? The Recovery init to be more exact? Or am I off-base and there are patches to the kernel?
Click to expand...
Click to collapse
I didnt do the kernel people like xboxfanj and marcusant and UBER and other i may be forgeting made the kernel so its not really mine its actually a modified shadow kernel that for some reason allowed the modem area to be written to and if you werent on the kernel it would say it successfully flashed the modem but it really didnt so i experimented and waaalaaaaah things were starting to peice together and i put the puzzle peices together and now we no longer need odin! i dont know what in the kernel allowed it but as soon as we figure out it will most like be in some other kernels and it would make the process easier and more user friendly:highfive:
has anyone contacted qbking77 to make a how-to-video on this ? ... :fingers-crossed: ( preferrably the REAL qbking77 NOT the blackqbking that has been mentioned in other sections / threads ... LOL )
EDIT - I sent him a PM :fingers-crossed:
Hi.
I'm going to root and unlock my device this weekend. I can't settle on a ROM because I want a steady ROM and a really stable ROM. I don't want to be flashing every 5 minutes.
Basically I just want Voodoo sound badly on my device. I am running 4.1.2 at the moment.
Is it possible to flash a custom kernel with stock android?? I have read you need to delete a file before flashing on 4.1.1. Is this still the case on 4.1.2.?
Can anyone recommend a Kernel?
Thanks.
Warren_Orange said:
Hi.
I'm going to root and unlock my device this weekend. I can't settle on a ROM because I want a steady ROM and a really stable ROM. I don't want to be flashing every 5 minutes.
Basically I just want Voodoo sound badly on my device. I am running 4.1.2 at the moment.
Is it possible to flash a custom kernel with stock android?? I have read you need to delete a file before flashing on 4.1.1. Is this still the case on 4.1.2.?
Can anyone recommend a Kernel?
Thanks.
Click to expand...
Click to collapse
Yes you can do it. I suggest you to try Marmite Kernel v5, it's really smooth and it has a good battery life.With this kernel you can stay with your stock Jelly Bean 4.1.2, like me, and use a custom kernel (Idon't have to delete any file, I root my phone flash the kernel and gooo)
Wow thanks for replying.
I have heard many good things about Marmite .
So I defo don't need to delete anything from stock 4.1.2. Before flashing the Marmite kernel?
Sent from my Nexus S using xda app-developers app
Warren_Orange said:
Wow thanks for replying.
I have heard many good things about Marmite .
So I defo don't need to delete anything from stock 4.1.2. Before flashing the Marmite kernel?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Nop, just flash via fastboot a custom recovery (recomend TWRP,link below) and root your phone with supersu or superuser zip.
then flash your kernel (dont forget to wipe cache and dalvik cacche before flashing the kernel)
TWRP RECOVERY: http://goo.im/devs/OpenRecovery/crespo
Hi.
I was going to use CWM as I have used that before back in the days of the G2/Hero.
Would CWM be OK?
Sent from my Nexus S using xda app-developers app
Warren_Orange said:
Hi.
I was going to use CWM as I have used that before back in the days of the G2/Hero.
Would CWM be OK?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Yes with CWM no problem with flashing this kernel
Hi all.
Well today I gave it a go. I managed to flash my NS using the guide by gullu101. Everything went fine.
I have downloaded Voodoo app and have Voodoo sound at last! :good:
I also flashed Marmite kernel V5, but I have a few questions.
I'm still on stock 4.1.2. and used Marmite V5 Stock OTA zip.
After flashing the kernel I noticed that I had no extra options in the settings menu. I take it because I'm still at stock these options aren't available?? If I was to flash a custom ROM and the 'All Other Roms' Marmite zip I would have these options?
Another thing, after the factory reset I had to install a few things from the market. I also got an notification exclamation error which I had never had before, it said 'need google play services' and took me to the Play store to install it. I have never had to install this app before and I'm wondering what it is.
Thanks.
install NS tools then you will have the "extra options"
Do I need to flash that or can I get that off the market?
Tbh I'm not bothered about tinkering. I just want to know that leaving the stock marmite kernel as is will be fine for my phone?
Sent from my Nexus S using xda app-developers app
it's just an app you can download at the google play store.
I am trying to install Franco kernel on my phone, and I have found the thread for this, but I am really confused on how to install it on my phone. I know that it's the same as installing a ROM, so I downloaded the appropriate version for my phone, but it said "Failed" while flashing it with TWRP. Am I doing something wrong?
SketchySean said:
I am trying to install Franco kernel on my phone, and I have found the thread for this, but I am really confused on how to install it on my phone. I know that it's the same as installing a ROM, so I downloaded the appropriate version for my phone, but it said "Failed" while flashing it with TWRP. Am I doing something wrong?
Click to expand...
Click to collapse
Yes, you are doing something wrong. FranciscoFranco does not have a kernel for the Verizon GSIII. Stop what you're doing and use a kernel from the VZW GSIII Original dev section.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Yes, you are doing something wrong. FranciscoFranco does not have a kernel for the Verizon GSIII. Stop what you're doing and use a kernel from the VZW GSIII Original dev section.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Ahh! Not gonna lie, I feel stupid right now. And thanks, I will. But what kernel would you recommend in terms of battery life-friendly? I've seen you around in the threads. You're awesome at helping people!
SketchySean said:
Ahh! Not gonna lie, I feel stupid right now. And thanks, I will. But what kernel would you recommend in terms of battery life-friendly? I've seen you around in the threads. You're awesome at helping people!
Click to expand...
Click to collapse
I personally love ktoonsez kernel, lots of tweaks and governors to it.
Sent from my SCH-I535 using Tapatalk 2
SketchySean said:
Ahh! Not gonna lie, I feel stupid right now. And thanks, I will. But what kernel would you recommend in terms of battery life-friendly? I've seen you around in the threads. You're awesome at helping people!
Click to expand...
Click to collapse
All the Touchwiz kernels do a good job with increasing battery life.
Wow, I tried to flash the Zeus kernel and it just messed up my phone.. I rebooted and my screen was black. Couldn't reboot again, so I went into recovery mode and restored from back up :/ What did I do wrong?
which rom have you?
I am currently on CM10.1
Sent from my SCH-I535 using xda app-developers app
SketchySean said:
I am currently on CM10.1
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You need an AOSP kernel. Not TW. KT747 is probably the way to go. Just make sure you download the AOSP version. Next time say what ROM you're running. That way you can avoid confusion early on.
Oh, alright. So that kernel is battery friendly? And is there a specific thread where I can find kernels for my ROM and or phone?
Sent from my SCH-I535 using xda app-developers app
SketchySean said:
Oh, alright. So that kernel is battery friendly? And is there a specific thread where I can find kernels for my ROM and or phone?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not sure if there is a single thread that lists all the kernels. Just go here to the original android development forum:
http://forum.xda-developers.com/forumdisplay.php?f=1692
and look for threads that have AOSP and Kernel in the thread title.
Edit - actually, perhaps this thread may help you:
http://forum.xda-developers.com/showthread.php?t=2064506
landshark68 said:
Not sure if there is a single thread that lists all the kernels. Just go here to the original android development forum:
http://forum.xda-developers.com/forumdisplay.php?f=1692
and look for threads that have AOSP and Kernel in the thread title.
Edit - actually, perhaps this thread may help you:
http://forum.xda-developers.com/showthread.php?t=2064506
Click to expand...
Click to collapse
Okay, so I flashed the Ktoonz kernel.. and now my screen is black again. I really don't know what I'm doing wrong.
SketchySean said:
Okay, so I flashed the Ktoonz kernel.. and now my screen is black again. I really don't know what I'm doing wrong.
Click to expand...
Click to collapse
When is your CM10.1 rom dated as? When was it released? You might need a kernel from before the rom's date.
SlimSnoopOS said:
When is your CM10.1 rom dated as? When was it released? You might need a kernel from before the rom's date.
Click to expand...
Click to collapse
I can't check cause my screen is black.. but I think I got the one dated at 3/4/2013
I checked the ROM that was in my ext hard drive, and I think it's CM 10.1- 201330304-EXPERIMENTAL-d2vzw-M2
SketchySean said:
I can't check cause my screen is black.. but I think I got the one dated at 3/4/2013
Click to expand...
Click to collapse
As in, from March? lol Ahh, you basically can't flash any current kernel out unless it's from around March 4th. Ahh, you're using the Linux 3.0 based version then. All AOSP roms have moved to the Linux 3.4 kernel as of early April Edit: Actually,mid-March was the Linux 3.0 to 3.4 switch which means all kernels are now incompatible with roms dated say before early March.
Here's KT747 from March 5th, should be fine flashing this.
Edit: flash the AOSP 4.2 version btw, that's what CM10.1 is based on
SlimSnoopOS said:
As in, from March? lol Ahh, you basically can't flash any current kernel out unless it's from before March 4th. Ahh, you're using the Linux 3.0 based version then. All AOSP roms have moved to the Linux 3.4 kernel as of early April which means all kernels are now incompatible with roms dated say before early April.
Here's KT747 from March 5th, should be fine flashing this.
Edit: flash the AOSP 4.2 version btw, that's what CM10.1 is based on
Click to expand...
Click to collapse
If I flash this kernel, will it wipe everything? And is this the only kernel that I can use? I'm really sorry if I'm asking a lot of questions, lol...
SketchySean said:
If I flash this kernel, will it wipe everything? And is this the only kernel that I can use? I'm really sorry if I'm asking a lot of questions, lol...
Click to expand...
Click to collapse
Nah, flashing kernels only necessitates you wiping Cache and Dalvik Cache in recovery. Neither of which is user data. Cache and Dalvik Cache get rebuilt once the rom boots so it's not something you'll notice besides the initial boot.
As for your second question, no this is not the only kernel you can use. If you want to stay on this exact rom, then you'll just have to do a lot of searching through kernel threads, for their Linux 3.0 based kernels from early March. However, this goes along with what I said in my prior post. Given that you are on a March 4th rom, you can only use Linux 3.0 based kernels which kernel devs usually mention in their changelog. Most (honestly all) kernel devs have stopped actively developing these and have moved onto Linux 3.4 kernels which will not boot on the rom you are on because it is outdated.
I encourage you to upgrade your rom to a current one and to keep up with active development that way you don't get left behind when flashing kernels (if that's your thing).
SlimSnoopOS said:
Nah, flashing kernels only necessitates you wiping Cache and Dalvik Cache in recovery. Neither of which is user data. Cache and Dalvik Cache get rebuilt once the rom boots so it's not something you'll notice besides the initial boot.
As for your second question, no this is not the only kernel you can use. If you want to stay on this exact rom, then you'll just have to do a lot of searching through kernel threads, for their Linux 3.0 based kernels from early March. However, this goes along with what I said in my prior post. Given that you are on a March 4th rom, you can only use Linux 3.0 based kernels which kernel devs usually mention in their changelog. Most (honestly all) kernel devs have stopped actively developing these and have moved onto Linux 3.4 kernels which will not boot on the rom you are on because it is outdated.
I encourage you to upgrade your rom to a current one and to keep up with active development that way you don't get left behind when flashing kernels (if that's your thing).
Click to expand...
Click to collapse
Alright, I will flash the 3.0 kernel right now. And as for updating my CM10.1, can i just update it through my phone? I've came across this option where I can just update it through settings. Will updating ROMS wipe my stuff? And I REALLY appreciate your help.
SketchySean said:
Alright, I will flash the 3.0 kernel right now. And as for updating my CM10.1, can i just update it through my phone? I've came across this option where I can just update it through settings. Will updating ROMS wipe my stuff? And I REALLY appreciate your help.
Click to expand...
Click to collapse
I wouldn't. Being that you're moving from a March CM build to a May CM build with a lot of changes, you need to do a full wipe in recovery to upgrade roms. Doing a dirty flash in this case introduces way too much room for issues to arise. As long as you do not wipe internal storage then you will not lose your data on the internal sdcard.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
I wouldn't. Being that you're moving from a March CM build to a May CM build with a lot of changes, you need to do a full wipe in recovery to upgrade roms. Doing a dirty flash in this case introduces way too much room for issues to arise. As long as you do not wipe internal storage then you will not lose your data on the internal sdcard.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So if I flash from recovery, everything will be exactly the way it was?
Hi all,
First let me start by telling you what device I am using a Samsung Galaxy S III I535 running Liquid Smooth 2.37 rom.
I have been flashing phones for years and have bricked, unbricked & in most cases had success with dirty flashing and doing clean flashes. I have gotten to the point in my adventures with flashing phones to experiment with kernels, since that's all anyone talks about that gets some legit performance and battery life stats. So my questions are as follows ( and i apologize now if this has been asked a bazillion times before. If that is in fact the case, some direction to the link would be much appreciated, thanks! )
1) what are the steps one would have to take to properly flash a Kernel
2) are there any pitfalls and caveats i should be concerned about ( bricking is the obvious one here )
Thank you again in advance for taking the time to help me out. Just trying to get fully educated before i decide to start messing around further with my phones!
e_poch145 said:
Hi all,
First let me start by telling you what device I am using a Samsung Galaxy S III I535 running Liquid Smooth 2.37 rom.
I have been flashing phones for years and have bricked, unbricked & in most cases had success with dirty flashing and doing clean flashes. I have gotten to the point in my adventures with flashing phones to experiment with kernels, since that's all anyone talks about that gets some legit performance and battery life stats. So my questions are as follows ( and i apologize now if this has been asked a bazillion times before. If that is in fact the case, some direction to the link would be much appreciated, thanks! )
1) what are the steps one would have to take to properly flash a Kernel
2) are there any pitfalls and caveats i should be concerned about ( bricking is the obvious one here )
Thank you again in advance for taking the time to help me out. Just trying to get fully educated before i decide to start messing around further with my phones!
Click to expand...
Click to collapse
1) Make sure the kernel is compatible with your rom, Do some reading about the kernel -pros & cons.
2) Flash away. In theory, you don't even need to wipe cache or dalvik cache, but just wipe them to make you feel like...it's clean!!
3) The worst thing is you get a bootloop which is an easy fix.
One other thing to note, is AOSP kernels are not compatible with TouchWiz roms, and TW kernels are not compatible with AOSP roms.
Make sure you get the right one, if the developer offers both options.
Sent from my SCH-I535 using XDA Premium 4 mobile app
buhohitr said:
1) Make sure the kernel is compatible with your rom, Do some reading about the kernel -pros & cons.
2) Flash away. In theory, you don't even need to wipe cache or dalvik cache, but just wipe them to make you feel like...it's clean!!
3) The worst thing is you get a bootloop which is an easy fix.
Click to expand...
Click to collapse
Just adding onto this, one good way of ensuring #1 is to flash a compatible AOSP 4.3 or 4.4 kernel that is dated at or about the same time as your rom. If the more recent kernel doesn't work, try the release prior to that.
Sent from my SCH-I535 using Tapatalk 4
Thanks Guys!
SlimSnoopOS said:
Just adding onto this, one good way of ensuring #1 is to flash a compatible AOSP 4.3 or 4.4 kernel that is dated at or about the same time as your rom. If the more recent kernel doesn't work, try the release prior to that.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Much appreciated guys! I decided to go with [4.3/4.4][AOSP] ¤ BMS ¤ d2vzw / d2usc 3.4.y (link below). So far so good, flashed easily and no problems at this point. Ill report back and see how the performance gains are.
http://forum.xda-developers.com/showthread.php?t=2133550
Thanks again for all of your advice!
I run that kernel on all roms. Hope u get good battery life. I suggest let it stabilize a day or two.. Jst my two cents
Sent from my unknown using Tapatalk
wont connect to wifi for me
twistedillutions said:
I run that kernel on all roms. Hope u get good battery life. I suggest let it stabilize a day or two.. Jst my two cents
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
I noticed as soon as I loaded the Kernel there was an issue. It wouldn't connect to any wifi networks. As a matter of fact, I couldn't even turn on wifi, the switch just stayed grayed out after i initially hit it. So currently I am running KT until I can find a solution to my issue. I would love to run BMS given the great response but I need to be able to use wifi lol
e_poch145 said:
I noticed as soon as I loaded the Kernel there was an issue. It wouldn't connect to any wifi networks. As a matter of fact, I couldn't even turn on wifi, the switch just stayed grayed out after i initially hit it. So currently I am running KT until I can find a solution to my issue. I would love to run BMS given the great response but I need to be able to use wifi lol
Click to expand...
Click to collapse
What is the name and date of the rom that you are on? Which version and date of KT747 are you using? Lastly, which version and date of BMS did you flash?
Sent from my SCH-I535 using Tapatalk 4
versions im running
SlimSnoopOS said:
What is the name and date of the rom that you are on? Which version and date of KT747 are you using? Lastly, which version and date of BMS did you flash?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Liquid Smooth 2.37 from 11/06/2013
KT747-AOSP-JB-MR2-3.4-VZW-11-04-2013
BMS_3.4_d2_2014-01-27
U need an older version of BMS thoss new version from dec till now are for 4.4 roms and liquid 2.37 is a 4.3 thats the reason why ur having issues
Sent from my unknown using Tapatalk
Stock Kernel
Background:
When Verizon released the ML1 Update you had two options, take the new boot-loader and be locked or NOT take the new boot-loader and remain unlocked. If you choose the latter of the two options the firmware and boot-loader never got updated. This seemed Ok but it would cause WiFi not to work because of the way Verizon coded the kernel to look at the new firmware (from my understanding). If the firmware was not the new version thee WiFi would just never turn on.
Intent:
As the name implies, this is just a recompiled stock kernel without the "WiFi bug" for Android 4.3 / ML1 based ROMS on the OLD UNLOCKED firmware! If you have taken the new firmware (aka: the 4.3 OTA) then you dont have to worry about this! It does not apply to you! This is Only for people on the OLD UNLOCKED firmware!
Why no features added?
Not everyone wants a super duper overclock kernel with 10 million features. Some prefer the simplicity of stock. I am one of those people! This is just a STOCK kernel with no mods other than working WiFi for the ML1 base on the old unlocked firmware.
Note: Version 2 is posted with the exFAT option checked for those using exFAT. Oversight on original build!
Download Stock Kernel v2 HERE: Stock-Kernel-v2.zip - 8.42 MB
Dont be lame, hit Thanks!
Stock Samsung Kernel Source Code: HERE
Change Log
v2 - 1/27/2014
Added missing exFat support causing some users SD Card to never mount if formatted with exFat (thanks prdog for the heads up)
V1 - 1/26/2014
Initial Build
Just fixed the download link!
scrosler said:
Just fixed the download link!
Click to expand...
Click to collapse
Wow let's all show some love this dude is a beast of a developer and does things few others are willing to take on. A big standing ovation from me my friend.
Sent from my SCH-I535 using xda app-developers app
So I just replaced lean kernel with this kernel on old & slows stock rom and it seems to be much snappier so far, well done good sir
MIKEYSAKZ said:
Wow let's all show some love this dude is a beast of a developer and does things few others are willing to take on. A big standing ovation from me my friend.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Your Welcome!
chocolate8175 said:
So I just replaced lean kernel with this kernel on old & slows stock rom and it seems to be much snappier so far, well done good sir
Click to expand...
Click to collapse
Funny thing is... This is a PURE stock build. BUT... here are some oddities I noticed over the stock kernel from VZW...
1. The compiled size is smaller (odd)
2. I used the defconfig that samsung said to use and I dont think its the typical Verizon defconfig. The name just seemed weird.
Its been a long time since I did a kernel so my observations may be pointless...
But I can agree with your statement that it is very smooth. I am running the stock roooted ROM I made with this kernel and I am tempted to get rid of my Note 3!
I think Samsung posted the wrong source or modified it after Verizon used it for the ML1 ROM (or I downloaded the wrong one!!!! lol).
Hmm, that is interesting...
scrosler said:
Just fixed the download link!
Click to expand...
Click to collapse
4l
Thanks. Will test to see if I get better battery life over lk. Also grabbed your ml1 ROM version. Been waiting for the release. All previous ROMS have been the best. Thanks.
I usually keep 1 custom kernel and 1 stock kernel around, thank you for bringing the stock option!
EAGLEEYE51 said:
4l
Thanks. Will test to see if I get better battery life over lk. Also grabbed your ml1 ROM version. Been waiting for the release. All previous ROMS have been the best. Thanks.
Click to expand...
Click to collapse
Just so you know the ML1 ROM has this kernel in it.
AS far as battery life, Im sure LK will be better, ITs a tweaked kernel.
This is a pure stock build no changes to the code, AT ALL.
I didint even add in a build name. I just did make defconfig followed by make -j16.
The odd thing is, WiFi just happens to work but the Verizon build doesn't. Go figure!
Thats it!
After installing this kernel on old&slows ROM, my SDcard discounts and won't remount. I have wiped both caches and rebooted.
Anyone else having this issue? I don't have time to clean wipe right now, but I will try that when I have some time.
jskolm said:
After installing this kernel on old&slows ROM, my SDcard discounts and won't remount. I have wiped both caches and rebooted.
Anyone else having this issue? I don't have time to clean wipe right now, but I will try that when I have some time.
Click to expand...
Click to collapse
Just noticed I'm having the same issue. Can't mount.
Hmmm... I will check in about 5 hours when I get home.
I talked with one of my Site Admins and he said he had no issues running this kernel with SD Card. Granted he is running it on "my" stock rooted ROM.
What size are ya'll running? and what format?
scrosler said:
I talked with one of my Site Admins and he said he had no issues running this kernel with SD Card. Granted he is running it on "my" stock rooted ROM.
What size are ya'll running? and what format?
Click to expand...
Click to collapse
32 gig, exfat.
Just flashed your Rom. Same issue. Wiped cache, dalvik, and system.
gnader said:
32 gig, exfat.
Just flashed your Rom. Same issue. Wiped cache, dalvik, and system.
Click to expand...
Click to collapse
Hmmm, strange
I have a 32 Gig I can test when I get home.
I just tested a micro SD a guy at work had in his S4.
Had no issues with it.
scrosler said:
Hmmm, strange
I have a 32 Gig I can test when I get home.
Click to expand...
Click to collapse
Fir testing, I went back to lk 4 kernel. SD card works again. Flashing back to yours once more to test.
---------- Post added at 04:10 PM ---------- Previous post was at 03:57 PM ----------
gnader said:
Fir testing, I went back to lk 4 kernel. SD card works again. Flashing back to yours once more to test.
Click to expand...
Click to collapse
Went back to your kernel... SD card not working again.
Going back to lk. I'm a fan of stock bits. Looking forward to a fix. Thanks for your efforts on this kernel!
Working fine on slow&old 12/31 release. No problems with the SD card. Came from lean kernel and this actually seems snappier.
Sent from my SCH-I535 using XDA Premium 4 mobile app
bill15872 said:
Working fine on slow&old 12/31 release. No problems with the SD card. Came from lean kernel and this actually seems snappier.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How big is your card? Trying to narrow down why gnader and the other guy are having issues. Thanks for the feedback!