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!
Related
So after installing this amazing rom and loving it for a week or two; I see a kernel update and install it. Everything went smooth but I lost my wifi after the fact. I was hoping someone could help me keep the kernel and get the wifi going. nothing about wifi problems were stated and it work fine previously. I wiped everything and even tried the wifi fix manager thingy i got with the ics rom i was running previously to see if that would do it but to no avail. I wanted to ask the developer but need some 10 post so help a bro out!
p.s....gotta give props to the man who had me running jb before anyone of my friends with newer phones!!! RANDOMBLAME!!!!
bboygmoney said:
So after installing this amazing rom and loving it for a week or two; I see a kernel update and install it. Everything went smooth but I lost my wifi after the fact. I was hoping someone could help me keep the kernel and get the wifi going. nothing about wifi problems were stated and it work fine previously. I wiped everything and even tried the wifi fix manager thingy i got with the ics rom i was running previously to see if that would do it but to no avail. I wanted to ask the developer but need some 10 post so help a bro out!
p.s....gotta give props to the man who had me running jb before anyone of my friends with newer phones!!! RANDOMBLAME!!!!
Click to expand...
Click to collapse
ditto, this happend with my Paranoidandroid install as well. kernel allowed me to stay running without crash, but wifi is a pretty big letdown...
unfortunatly, without the kernel itself being fixed, or the wifi module fixed, we are stuck looking for another alternate kernel... oh yeah, we are pretty limited.
thanks
appreciate the quick reply man. And I'll be keeping my eye out then
bboygmoney said:
appreciate the quick reply man. And I'll be keeping my eye out then
Click to expand...
Click to collapse
found out a very possible reason . are you using his kernel with another system or is this all jt only? he mentioned something about kangbang changing drivers.
dakunesu said:
found out a very possible reason . are you using his kernel with another system or is this all jt only? he mentioned something about kangbang changing drivers.
Click to expand...
Click to collapse
So I'm only using it with jelly time or jb. I'm flashing the os then the kernel cuz the os installs its own. This is an updated kernel for the os.I'm thinking i should maybe wipe the cache partition after the the os then do the kernel but at the same time I would think that other problems would be happening if that was the issue. What do you think?
bboygmoney said:
So I'm only using it with jelly time or jb. I'm flashing the os then the kernel cuz the os installs its own. This is an updated kernel for the os.I'm thinking i should maybe wipe the cache partition after the the os then do the kernel but at the same time I would think that other problems would be happening if that was the issue. What do you think?
Click to expand...
Click to collapse
does the system function without the kernel update?
if it does, you might want to hold off on updating til the ROM updates for it.
dakunesu said:
found out a very possible reason . are you using his kernel with another system or is this all jt only? he mentioned something about kangbang changing drivers.
Click to expand...
Click to collapse
dakunesu said:
does the system function without the kernel update?
if it does, you might want to hold off on updating til the ROM updates for it.
Click to expand...
Click to collapse
It does. N You know I am not even sure what advantages I get from this updated kernel anyways lol but I want it!!
problem solved!
bboygmoney said:
It does. N You know I am not even sure what advantages I get from this updated kernel anyways lol but I want it!!
Click to expand...
Click to collapse
The ROM was updated and the kernel included in the update! Amazing rom , highly recommended especially with the updated kernel!
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
This is for questions and answers (that's what Q&A means) regarding the ICS and JB proton kernels. If you have a logcat, do not post it here.
Re: [TFQ] Proton Kernel Q&A
Kyndig66 said:
This is for questions and answers (that's what Q&A means) regarding the ICS and JB proton kernels. If you have a logcat, do not post it here.
Click to expand...
Click to collapse
Well you can do that too...
Sent from [CONTENT DELETED]
I changed it to sarcasm. This thread will probably be deleted since I reported it as a duplicate before seeing yours was ICS.
Well hopefully, they will check before deleting it.
Sent from [CONTENT DELETED]
Locked to OP's request.
He changed his mind.
Is there a Twrp "recovery" for CM10...?If so I can't find it anyplace,.....help?
sent from my t959w running RemICS, Voodoo sound, Rom Toolbox pro, love TWRP
abonides said:
Is there a Twrp installer for CM10...?If so I can't find it anyplace,.....help?
Click to expand...
Click to collapse
There's no such thing as a TWRP installer. You either have a recovery from TWRP or CWM. If your asking about amarullz AROMA installer then no. It's not been used on any of the newer builds that have come out that I'm aware of.
hechoen said:
There's no such thing as a TWRP installer. You either have a recovery from TWRP or CWM. If your asking about amarullz AROMA installer then no. It's not been used on any of the newer builds that have come out that I'm aware of.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1721489
[MTD/CWM] SGS4G TWRP Installer (Oct 13, 2012)
It depends on the CWM version last I saw.
Sent from a hole in the time/space continuum.
Kyndig66 said:
http://forum.xda-developers.com/showthread.php?t=1721489
[MTD/CWM] SGS4G TWRP Installer (Oct 13, 2012)
It depends on the CWM version last I saw.
Click to expand...
Click to collapse
Kyngigg for the win. lol
Thanks for bringing that to my attention. Have you flashed it over the newer builds? I'm a CWM guy myself but I can say for sure that the GUI of TWRP is much nicer. Actually give me a minute and I'll report back with the results.
Not yet. I did learn how to incorporate it into a build today though. There were some issues with the installer and I know FB has been very busy.
Sent from a hole in the time/space continuum.
hechoen said:
Kyngigg for the win. lol
Thanks for bringing that to my attention. Have you flashed it over the newer builds? I'm a CWM guy myself but I can say for sure that the GUI of TWRP is much nicer. Actually give me a minute and I'll report back with the results.
Click to expand...
Click to collapse
It's a weird thing quoting yourself. lol
Kyndig66 said:
Not yet. I did learn how to incorporate it into a build today though. There were some issues with the installer and I know FB has been very busy.
Click to expand...
Click to collapse
Don't. Status 7 error. I'm sure with some edits to the updater script it would flash over fine. However it's an OLD version of TWRP. Maybe get FB's permission to get it to 2.4 then go from there. Either way, thanks for reminding me it existed. CWM FTW(for the win). LOL
Doing serious multi tasking. Besides, I never read what I'm posting answers to anyway
Sent from a hole in the time/space continuum.
Doesn't my slimbean come with twrp 2.4?
Sent from my Galaxy Nexus using xda premium
Beastmode said:
Doesn't my slimbean come with twrp 2.4?
Click to expand...
Click to collapse
It does. Problem is once you flash almost anything else it's gone. Unless you know some trickery to keep it around. Like
Code:
heimdall flash --kernel --boot.img
Don't do this unless you really know what you are doing. Google helps. lol
Beastmode said:
Doesn't my slimbean come with twrp 2.4?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Will try out slimbean, tho I like the cm 10 build...I hate clockwork, for some reason with this device it likes to lock up my SD card, I end up reformatting and reinserting,never had the issue with twrp....:what:
sent from my t959w running fah q's cm10 Voodoo sound, Rom Toolbox pro,sys tuner pro
what brand of sdcard do you have?
Patriot now but did it with Samsung stock card as well
sent from t959w running remics UV,voodoo sound
FUSE
Any chance we could get this kernel built with either exFAT or FUSE (so I can use Paragon Partition)?
I'm having a devil of a time keeping FAT32 64GB SD cards stable without.
IDisposable said:
Any chance we could get this kernel built with either exFAT or FUSE (so I can use Paragon Partition)?
I'm having a devil of a time keeping FAT32 64GB SD cards stable without.
Click to expand...
Click to collapse
Go grab the kernel source and do it.
Sent from a hole in the time/space continuum.
IDisposable said:
Any chance we could get this kernel built with either exFAT or FUSE (so I can use Paragon Partition)?
I'm having a devil of a time keeping FAT32 64GB SD cards stable without.
Click to expand...
Click to collapse
Mines 64gb fat32 class 6 and it works fine. It's not the kernel. exfat has only been used on a few devices at this point. CM doesn't support it and doesn't look like there going to with JB so why ask for it to be supported on a two year old device? What's not stable on your card? I/O would be a could place to start looking.
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?
*** Latest Build 10-11-2013 ***
For d2vzw! Note the forum you're in!
If you're as big of a fan as I am of KToonsez's KT747 kernel then you'll be happy to know there is now an updated version.
This is a forked version of KToonsez's KT747 kernel with commits pulled from the CM10.2 branch of the d2 kernel.
Disclaimer: Standard disclaimer goes here. I nor KToonsez are responsible for the actions you take when working with your phone. I've done a significant amount of testing and so have others but situations arise where a hiccup could cause data loss, IMEI loss, or phone failure. You, the flasher, assume these risks. Please make sure you backup/nandroid, use nvbackup, etc.
Note:
It has been reported that this kernel will not work with 4.3.1 ROMs, notably the latest nightlies of PAC-MAN. If you're on a 4.3.1 ROM flash with extra caution. If you find otherwise please alert me.
Branch "currentCherry" (my cherry picking branch) CI status:
Branch "mr2" (KT's 4.3 branch) CI status:
Instructions:
There seems to be an odd permissions issue that we've uncovered. Follow these exact steps so when you boot you'll have working cell data:
Reboot Recovery
Clear Caches
Flash your current ROM
Flash kernel
Reboot
Profit!!!
I'm working on clearing this up. I've verified the above process against mastamoon's unofficial CM10.2 10/07 build.
Download Link:
10-11-2013
A big thanks to shane269 for helping me test this from a bootlooper to working kernel!
Thanks!
KT747's sources can be found here:
https://github.com/ktoonsez/KT747-JB
Visit the official KT747 thread here:
http://forum.xda-developers.com/showthread.php?t=1853816
Visit kt's original, ORIGINAL kernel thread here:
http://forum.xda-developers.com/show....php?t=1756776
Also if you like this kernel then please consider donating to the dev that made it all happen, ktoonsez: http://forum.xda-developers.com/donatetome.php?u=4325945
Previous Builds
10-10-2013
10-09-2013
XDA:DevDB Information
KT747 For D2VZW Cherry Picked, a Kernel for the Verizon Samsung Galaxy S III
Contributors
mikejr83, KToonsez
Kernel Special Features: KT747 kernel with latest CM10.2 commits
Version Information
Status: Beta
Created 2013-10-09
Last Updated 2013-10-16
Change log:
-10/11/2013
* Merged the commit for touchscreen optimizations
* Cherry-picked commit for reverting portions of the touchscreen optimizations which may cause us camera issues.
* Changed updater-script to hopefully resolve issue with no data after flashing (still researching issue)
First?
Looking forward to this
tapped from a carbonized d2vzw
ktoonsez gave the OK. Download link is now up. Please follow the instructions or you'll get no data. If you accidently goof and do this just reflash your ROM and then in the same session flash the kernel.
Thanks!
Mike
Thanks for this I've been using this without issues pacman ROM.
Sent from my SCH-I535 using Tapatalk 2
Just flashed on Slim 1.6 weekly and set my kernel settings. No initial issues, thanks for the update. I was going through kernel flashing withdrawals.
Sent from my SCH-I535 using Tapatalk 4
Well @mikejr83 so far so good, thanks for the update!
sent from a custom s3 powered by pacman, ROM ,KT747 kernel w/mods by team kernelizers ,themed by blackout1911,Pimped by the candyshop, and modded by all!
Is anyone not seeing OC working? I have mine set to 1728 but I'm still seeing 1510 in BBS.
Sent from my SCH-I535 using xda app-developers app
mikejr83 said:
Is anyone not seeing OC working? I have mine set to 1728 but I'm still seeing 1510 in BBS.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I normally don't overclock my phone doesn't do well with it. I tried 1728 and it wasn't ever using it. Then I bumped it up to 1809 and it instantly rebooted. As expected, my processor just won't do it. After the reboot the phone was still set at 1728 and it was using that frequency. So maybe requires a reboot work?
Sent from my SCH-I535 using Tapatalk 2
Rebooting seems to make it stick or show up in the apps where I see freq values.
Sent from my SCH-I535 using xda app-developers app
OP Updated
Went through my cherry pick branch and realized I missed some commits. I missed about 2 days worth of merges at the end of August. These are now all added.
There is a gerrit reviewed commit for touchscreen optimizations (and a subsequent fix for camera issues). I'm having trouble merging this commit into my branch. I'll try to get that into the build for tomorrow.
Thanks!
Mike
Can I ask why there is a unofficial version of KT kernel? Did he drop support for s3?
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Rinkle McBally said:
Can I ask why there is a unofficial version of KT kernel? Did he drop support for s3?
Click to expand...
Click to collapse
He's just been really busy and this guy wanted to put a more recent build out since there have been many commits to cm 10.2
Sent from my SCH-I535 using Tapatalk 4
---------- Post added at 06:20 AM ---------- Previous post was at 06:19 AM ----------
Are we able to flash the kernel separately yet?
Sent from my SCH-I535 using Tapatalk 4
no cigar said:
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Click to expand...
Click to collapse
Shoot! Ok. Just want to ask a couple of questions to make sure I'm on the same page and I can collect some info to try and figure this out.
10/10 build? Probably a silly question since you posted after I posted the new build, but just checking.
Are you using CWM? If you are what version?
Just to be clear, are you flashing ROM and then the kernel in the same recovery session?
I'm not familiar with liquidsmooth. Is the 2.10 release version 4.3 of Android? I'm assuming it is otherwise you probably would have gotten a bootloop instead of no data.
Thanks for the feedback. It's important that I see these. I've been worried sick that there are people downloading this, having this problem, and immediately thinking that I through out something that is bunk. I want this effort to live up to the expectations that everyone has for KT's kernel. Last thing I want to do is turn people off to his great work!
jamminjon82 said:
He's just been really busy and this guy wanted to put a more recent build out since there have been many commits to cm 10.2
Sent from my SCH-I535 using Tapatalk 4
---------- Post added at 06:20 AM ---------- Previous post was at 06:19 AM ----------
Are we able to flash the kernel separately yet?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I was able to flash 10/10 over 10/09 without having to flash the ROM and still have data. I have not gone from sans KT to ROM with KT on the 10/10 build.
I'm going to try to get some input from some devs. I originally thought it was the updater-script applying the wrong permissions during the flash. I did, however, change the script to mimic more how LeanKernel does its flash but that fix was put in 10/09. This along with the touchscreen fixes are my top priorities to get fixed.
See responses below. Thanks!
mikejr83 said:
Shoot! Ok. Just want to ask a couple of questions to make sure I'm on the same page and I can collect some info to try and figure this out.
10/10 build? Probably a silly question since you posted after I posted the new build, but just checking.
Yep 10/10 for sure.
Are you using CWM? If you are what version?
Yes. 6.0.4.3
Just to be clear, are you flashing ROM and then the kernel in the same recovery session?
Yes, all in the same session
I'm not familiar with liquidsmooth. Is the 2.10 release version 4.3 of Android? I'm assuming it is otherwise you probably would have gotten a bootloop instead of no data.
Correct. I'm running android 4.3
Thanks for the feedback. It's important that I see these. I've been worried sick that there are people downloading this, having this problem, and immediately thinking that I through out something that is bunk. I want this effort to live up to the expectations that everyone has for KT's kernel. Last thing I want to do is turn people off to his great work!
I was able to flash 10/10 over 10/09 without having to flash the ROM and still have data. I have not gone from sans KT to ROM with KT on the 10/10 build.
I'm going to try to get some input from some devs. I originally thought it was the updater-script applying the wrong permissions during the flash. I did, however, change the script to mimic more how LeanKernel does its flash but that fix was put in 10/09. This along with the touchscreen fixes are my top priorities to get fixed.
Click to expand...
Click to collapse
Eclipse build 6
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Quie2TP said:
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Click to expand...
Click to collapse
^
SAME
New build in the OP.
Also, changelog is in the second post.
no cigar said:
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Click to expand...
Click to collapse
Quie2TP said:
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Click to expand...
Click to collapse
grislieber said:
^
SAME
Click to expand...
Click to collapse
Thanks for the reports guys. Researching this issue is proving difficult as no one seems to have documented it in the "usual" places. The only suggestion I have so far is checking to make sure the permissions are correct on everything that is flashed. I took a look at a couple of other kernel dev's updater-scripts and tried to modify this one accordingly. Flashing from 10/10 to 10/11's still gave me working data. I'm trying to follow up with a few other devs so please don't think that I'm not working on this. If you flash 10/11 please report your findings!
Thanks!