Hiya everyone,
I've ported Dumfuq's overclocking patches from 2.6.29 to 2.6.32.21! This applies to those of us using the stock HTC OTA and allows the use of programs like SetCPU. This kernel was built from the source code from http://developer.htc.com and the kernel config is an identical copy of the one included in the latest Froyo OTA (my leak).
My current method of providing this is as an update.zip... just put this on your SDcard, boot into Clockwork, and flash it. If it kills your kittens, do not blame me.
Also, reminder: flashing this zip alone is not enough to overclock your device. Afterward, use a program (from the Market) such as SetCPU to overclock your device.
Download: http://www.multiupload.com/2XEWYRL62U
Change Log:
- Revision 2
Fix Wifi issues (as well as any other kernel module loading issues).
Add support for CPUfreq governers 'interactive' and 'smartass'.
Change the default governer from 'ondemand' to 'interactive' - this dramatically improves redraw performance and other user-interface responsiveness.
To change to the Smartass governer use something like SetCPU.
Include the MSM KGSL TLB performance tweak changes that are present in CM's kernel repository. You may or may not notice any video performance improvement, but it provides a possibility of improvement.
Fixed the kernel version string to properly read '2.6.32.21' not '2.6.32.17' - the first version wasn't .17, it was .21.
Please remember to disable the HTC Perflock in SetCPU by pressing the Menu key (while in SetCPU) and selecting 'Perflock Disabler'.
Happy? Donate.
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
What is the max frequency of this kernel? And does it include smartass governer?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
pettigrew95 said:
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
Click to expand...
Click to collapse
Ahh, one thing I didn't test, although I suspected it might break. I'll fix it tonight and post a new update.zip for ya'll.
agentg1001 said:
What is the max frequency of this kernel? And does it include smartass governer?
Click to expand...
Click to collapse
It's identical to Dumfuq's patches, so 864000Hz. And no, it doesn't include the smartass governer - I will investigate that possibility tonight, however I suspect I will be able to implement it. Additionally I will be disabling HTC Perflock in the kernel so it doesn't have to be done by SetCPU.
Toodles.
EDIT: I'll also be adding the new 'interactive' CPUfreq governer.
nbetcher said:
Ahh, one thing I didn't test, although I suspected it might break. I'll fix it tonight and post a new update.zip for ya'll.
It's identical to Dumfuq's patches, so 864000Hz. And no, it doesn't include the smartass governer - I will investigate that possibility tonight, however I suspect I will be able to implement it. Additionally I will be disabling HTC Perflock in the kernel so it doesn't have to be done by SetCPU.
Toodles.
EDIT: I'll also be adding the new 'interactive' CPUfreq governer.
Click to expand...
Click to collapse
I have made the changes, however I decided to NOT disable HTC Perflock through the kernel config, so please make sure to disable it (via SetCPU) first before trying to overclock or change your governer. New version uploaded, see OP.
Could you also include some higher frequencies? (Preferibly up to 960)? That would be great because my phone is stable up to 921. Also compcache enabled (like drowning child's kernel) would be awesome.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
I'm not sure why but my slide didn't like this kernel
http://pastebin.com/hVgG467j
Thank the devs for nandroid!
My slide not working with this kernel too (
Are you both running NB_Mod-2.15.531.1 Revision 2? Otherwise this won't work properly. Besides, according to that logcat your problems aren't related to the kernel... Android is unable to mount any of the MTD partitions (/system, /cache, /data, etc).
Please let me know more about what you're running.
Also, I'll be working on making a separate version of this that has OC enabled up to 960MHz, but 960MHz is very dangerous... 800MHz+ is even asking for trouble despite our processor's normal clockrate being 800MHz (T-Mobile downclocked it to 600MHz out-of-the-box).
I'll look into Compcache as well.
im IN.
good job, will try after work. gj
how long does it take to boot the first time?
been stuck at the white MT3GS boot screen for a few minutes now.
running CM7 RC4
EDIT: oops, did not know this is only for the leaked froyo update
pettigrew95 said:
Hey I'm running your NB 2.15 Mod ROM and just flashed this kernel. It broke the WiFi. I am now getting an Error when attempting to enable WiFi.
Click to expand...
Click to collapse
I just flash the this new Kernel and i'm also getting Error on the WiFi when trying to Enable it, also the SetCPU won't go higher then 600. The Rom i'm using is the 3rdSense 1.00
Thankfully i did a Rom Backup so i'm restoring my system
Sefy said:
I just flash the this new Kernel and i'm also getting Error on the WiFi when trying to Enable it, also the SetCPU won't go higher then 600. The Rom i'm using is the 3rdSense 1.00
Thankfully i did a Rom Backup so i'm restoring my system
Click to expand...
Click to collapse
This kernel is only to be flashed if youre running NB Mod 2.15 ROM. It wont work on 3rd sense
pettigrew95 said:
This kernel is only to be flashed if youre running NB Mod 2.15 ROM. It wont work on 3rd sense
Click to expand...
Click to collapse
Well, it showed it as the kernel in the "About" so it appeared to have flashed it (and it did kill the WiFi) so it did get flashed
Either way, i got back to the previous one (.17[aka .21]) and it's working fine again.
Sefy said:
Well, it showed it as the kernel in the "About" so it appeared to have flashed it (and it did kill the WiFi) so it did get flashed
Either way, i got back to the previous one (.17[aka .21]) and it's working fine again.
Click to expand...
Click to collapse
Hmm, .17 isn't AKA .21. They're two different kernels and contain different code. The kernel you're using in 3rdSense was from the HTC Legend release of 2.6.32.17 and had different Wifi drivers. When a kernel and its driver modules are built, the build process puts the kernel's version string into the modules, so if you try to load them on a different kernel it will fail. This is what happened to you... you have 3rdSense which uses 2.6.32.17 Wifi drivers and my 2.6.32.21 kernel cannot (well, I fib a little on that) load the .17 drivers. Get it? Got it? Good.
nbetcher said:
Hmm, .17 isn't AKA .21. They're two different kernels and contain different code. The kernel you're using in 3rdSense was from the HTC Legend release of 2.6.32.17 and had different Wifi drivers. When a kernel and its driver modules are built, the build process puts the kernel's version string into the modules, so if you try to load them on a different kernel it will fail. This is what happened to you... you have 3rdSense which uses 2.6.32.17 Wifi drivers and my 2.6.32.21 kernel cannot (well, I fib a little on that) load the .17 drivers. Get it? Got it? Good.
Click to expand...
Click to collapse
So... what you are saying is, a kernel from a different device all together, is working on a hardware which it doesn't really belong to. While a Kernel made specifically for this, will kill the WiFi of the device it's designed for?
From what i recall from Linux, and i could be wrong and this doesn't apply to Android, the Kernel and the UI are two separate components. The Kernel has all the drivers and the UI is the interface! but again, i could be wrong.
Sefy said:
So... what you are saying is, a kernel from a different device all together, is working on a hardware which it doesn't really belong to. While a Kernel made specifically for this, will kill the WiFi of the device it's designed for?
From what i recall from Linux, and i could be wrong and this doesn't apply to Android, the Kernel and the UI are two separate components. The Kernel has all the drivers and the UI is the interface! but again, i could be wrong.
Click to expand...
Click to collapse
What I'm saying is that the boot.img that I have in the update.zip from this post does NOT contain the modules for Wifi since the modules are stored on your /system MTD and the scope of this update.zip is for the kernel. Could I replace the modules from there with the ones shipped with the Froyo OTA? Sure, but where does it stop?
Anyways, the Legend is not a completely different device. The Legend is basically the UK version of the Slide, minus the keyboard. Same exact hardware all the way down to the Wifi and BT.
Let me explain things a little bit more:
There's sdio.ko and tiwlan_drv.ko in /system/lib/modules. NB_Mod has ones compiled from 2.6.32.21, 3rdSense has ones compiled from 2.6.32.17. This thread's kernel (boot.img, to dumb it down a bit ) is 2.6.32.21. So, when the system goes to load the modules from /system/lib/modules, it sees that you're running kernel 2.6.32.21, but the modules in that directory are for 2.6.32.17. It fails.
As far as Android being separate from the kernel... yes, of course. But touching "Wifi" (to enable Wifi) in Settings doesn't scurry out little Android gremlins to magically carry the firmware from your MTD to the Wifi chipset... all it does it say "Hey, kernel, would you mind loading the wifi module you have listed in init.rc? Thanks Linus! *kisses*" Then Android does some other stuff, but I won't bore you with the entire process or else I'll have to write a book (oops, too late).
EDIT: in hind-sight this all seems to not really answer your question and only further supports the need for a better answer to you, but hopefully you'll find some clarity.
nbetcher said:
What I'm saying is that the boot.img that I have in the update.zip from this post does NOT contain the modules for Wifi since the modules are stored on your /system MTD and the scope of this update.zip is for the kernel. Could I replace the modules from there with the ones shipped with the Froyo OTA? Sure, but where does it stop?
Anyways, the Legend is not a completely different device. The Legend is basically the UK version of the Slide, minus the keyboard. Same exact hardware all the way down to the Wifi and BT.
Let me explain things a little bit more:
There's sdio.ko and tiwlan_drv.ko in /system/lib/modules. NB_Mod has ones compiled from 2.6.32.21, 3rdSense has ones compiled from 2.6.32.17. This thread's kernel (boot.img, to dumb it down a bit ) is 2.6.32.21. So, when the system goes to load the modules from /system/lib/modules, it sees that you're running kernel 2.6.32.21, but the modules in that directory are for 2.6.32.17. It fails.
As far as Android being separate from the kernel... yes, of course. But touching "Wifi" (to enable Wifi) in Settings doesn't scurry out little Android gremlins to magically carry the firmware from your MTD to the Wifi chipset... all it does it say "Hey, kernel, would you mind loading the wifi module you have listed in init.rc? Thanks Linus! *kisses*" Then Android does some other stuff, but I won't bore you with the entire process or else I'll have to write a book (oops, too late).
Click to expand...
Click to collapse
Everyday you learn something new! thanks for being the teacher!
nbetcher said:
Are you both running NB_Mod-2.15.531.1 Revision 2? Otherwise this won't work properly.
Click to expand...
Click to collapse
Well now I feel a bit sheepish, I guess that's what I get for not reading closely enough, I'm running CM7 RC4, sorry about that.
Does anyone happen to have a copy of this kernel laying around somewhere? Megaupload is long gone unfortunately
Related
I'm presently working on the answers to another question I asked recently regarding cifs. I got some great technical advice but it seems that I must do some work with the kernel in my vegan ginger tab to understand all the info I received. I was sent a link to Pershoot's kernel page http://droidbasement.com/db-blog/ and I went there but I do not understand what I am seeing. I see that there is a numbering system 2.6.32.39 and I can guess that UV means undervolted and that OC means overclocked. The rest ??? Which one works with gingerbread ??? Also, reading the posts in the kernel page on XDA, there seems to be a lot of experimentation going on with voltages and governors, etc to try and squeeze the max out of the g-tab. That's great but I'm not ready to play in that league yet. I want a basic, stable kernel that I can learn to load modules with. I don't want to be worrying about adjusting other things at the moment. How, can I determine which is the correct kernel for my vegan ginger? Actually the one that came with the ROM is working fine (2.6.32.36) but I need to have the zip file to look at the information inside to understand the answers to my original questions about loading cifs module. Any kernel wizards out there that can give me some basics on the labeling system?
My guess would be the one with....(Gingerbread)........after it....
Its not that hard to read.......
ViewSonic Gtab/Malata Zpad (Gingerbread):
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-043011.zip
roguey said:
My guess would be the one with....(Gingerbread)........after it....
Its not that hard to read.......
ViewSonic Gtab/Malata Zpad (Gingerbread):
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-043011.zip
Click to expand...
Click to collapse
Of course its not that hard to read if you know what you are reading!
"ViewSonic Gtab/Malata Zpad (Gingerbread):
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-043011.zip
cm_2632.39 - kernel version (derived from cyanogen mod I presume)
gb - yup gingerbread
oc - overclocked - probably
uv - undervolted - another good guess
xtra - well he explains what is in that
vfp - no clue
fp - also no clue
043011 - yeah the date !!!
now there is all this reference to replacing the boot loader - which, based upon all the furor about the last viewsonic release might be a problem - or not. Do I need a new bootloader or is this just standard with kernels. I've flashed a few and never seen that before - but I was using clemsyn's. Will it mess up my clockworkmod?
Then it also looks like I have to install an app to manage the overclocking. Do I want to overclock? Should I overclock? Hmmm not working on that issue at the moment so I don't want to start a recursive thread in my mind investigating overclocking. Perhaps I shouldn't be using pershoot kernels at all if I want something less experimental. All I wanted really was to have cifs work. Clemsyn? Well cifs is built in but it didn't seem to work well with gingerbread rom. How to tell what works with what rom? Trying not to make a brick here. Anyway - I'm rambling but hopefully someone see the point. How do you find the information you need to make a decision? So far the only way I can see is to post questions like this, receive snarky answers and an occasional helping hand. Well if that's what it takes - bring it on because sooner or later I'm going to find out what I need to know to keep pushing forward with my g-tab.
There is a learning curve to anything, and Linux kernels are no different. First, don't over think it! It is sufficient to get the right kernel for whatever you are running. For us gtab folks that would be gtab, then either froyo or gingerbread as the major version, then either the original 1.1 or the new 1.2 bootloader. Combine all that and you will know which pershoot ron will work for you.
As to the overclocking, by default if you do nothing, the pershoot kernel will slightly underclock, so it will always work on any hardware. You can follow the directions to start pushing the overclock speed and see hot it works for you. Try 1200 for a few days, and if all goes well push it up to 1400
Ha-ha-ha Sorry I'm an INTJ - I ALWAYS overthink. Learning curves are my curse! That said - identifying the kernel makes more sense. I'm not sure I know how to determine what bootloader it is for - I prefer to stick with the old one for now. Is it something obvious that I just haven't seen? For example:
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-043011.zip which bootloader???
Then there is the question of "In order for UMS (USB mount) to work on Gingerbread, this must be reverted:
https://github.com/CyanogenMod/android_device_harmony/commit/f51f9e2a1037b4e3fb1a" What does REVERTED mean?
Good news on the overclocking - I can just leave it alone and it will work and then when I'm ready I can try the overclocking. Is this usually true with kernels that have been undevolted or overclocked that the default settings are more or less normal and you have to actually tweak them to use the OC or UV? I know nothing is carved in stone but would that be "the norm" for most developers?
enigma0456 said:
Ha-ha-ha Sorry I'm an INTJ - I ALWAYS overthink. Learning curves are my curse! That said - identifying the kernel makes more sense. I'm not sure I know how to determine what bootloader it is for - I prefer to stick with the old one for now. Is it something obvious that I just haven't seen? For example:
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-043011.zip which bootloader???
Then there is the question of "In order for UMS (USB mount) to work on Gingerbread, this must be reverted:
https://github.com/CyanogenMod/android_device_harmony/commit/f51f9e2a1037b4e3fb1a" What does REVERTED mean?
Good news on the overclocking - I can just leave it alone and it will work and then when I'm ready I can try the overclocking. Is this usually true with kernels that have been undevolted or overclocked that the default settings are more or less normal and you have to actually tweak them to use the OC or UV? I know nothing is carved in stone but would that be "the norm" for most developers?
Click to expand...
Click to collapse
You have to check out his blog page - it should clearly identify if a kernel is for the old or new boot loader. The vast majority are for the old boot loader, so if it's not mentioned at all, it's for the old one.
You can ignore the USB revert thing - that's not an instruction for you, it's what he did for gingerbread.
The way overclocking is implemented (at least in pershoot's case), you need to change something on your gtab to set the min/max clock. By default, on pershoot's kernel, the max will be just under 1Ghz, so doing nothing you get that. The undervolting is fixed in the kernel, you can't change it. Likewise the "steps" the cpu clock can take from min to max is fixed in the kernel and isn't changeable.
The other kernel (1.5ghz OC) I know nothing about, since I've never used it nor looked into it.
It's even easier than you are still trying to make it
There is only one bootloader for the Gtablet that supports "other" kernels and that is the one that is currently shipping and currently "officially the latest". There is a "newer" bootloader for the 1.2 system based stuff (3991 and above stock images...which were up for a day and then pulled for unknown reason) and there are zero replacement kernels for that bootloader.
If you read it says..
"Malata Zpad [New Bootloader] "
Click to expand...
Click to collapse
and no where does it mention new or old bootloader and Gtablet together.
So for Gingerbread based Viewsonic Gtablets you would want this one.
ViewSonic Gtab/Malata Zpad (Gingerbread):
boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-043011.zip
Download: boot-cm_2632.39_gb-oc-uv-xtra-vfp_fp-043011.zip
Click to expand...
Click to collapse
If you need extra filesystem or other support (CIFS, NTFS, etc..) you need the proper module from the lib file..
lib-2632.39_gb.tar.gz (kernel modules)
Download: lib-2632.39_gb.tar.gz
Click to expand...
Click to collapse
which you would open and extract the module you need and push it to your device however you want....ADB or Root Explorer, etc...
Pull the one you want from lib-2632.39.tar.gz (winrar can open this),
adb remount
adb push MODULE.ko /system/lib/modules/2.6.32.39-cyanogenmod/
adb shell chmod 644 /system/lib/modules/2.6.32.39-cyanogenmod/MODULE.ko
adb shell insmod /system/lib/modules/2.6.32.39-cyanogenmod/MODULE.ko
Note:
You can download gscript lite from the Market, and put the insmod line in there, and tap when you want to insert it and use its functionality.
Click to expand...
Click to collapse
if you want to use overclocking, download SetCPU or use the CPU settings in VEGAN-Ginger.
Overclocking-
How-To:
-Install the latest SetCPU (2.11a is current) from the market and/or XDA (http://forum.xda-developers.com/showthread.php?t=505419)
-Select auto
-If using CM7, then you can use the included CPU Settings within CyanogenMod Settings.
Note:
If you were using SetCPU prior, with ‘custom’ and this kernel set, please go to device selection and select auto. Please delete the custom setcpu file on your filesystem:
adb shell rm /data/local/setcpu
Note2:
Be aware, that if you leave it pinned to max, hammering it, it will get warm/warmer then your used to at 1GHZ, pinned.
It is advised not to select any of the 2 governor’s listed (but, at the very least, not performance).
It is advised to keep your min value at 216.
Click to expand...
Click to collapse
You don't need to worry about this statement
In order for UMS (USB mount) to work on Gingerbread, this must be reverted:
https://github.com/CyanogenMod/android_device_harmony/commit/f51f9e2a1037b4e3fb1a
Click to expand...
Click to collapse
If you are on a ROM based off the CyanogenMod source tree which VEGAn-Ginger is.
enigma0456 said:
vfp - no clue
fp - also no clue
Click to expand...
Click to collapse
FYI, vfp_fp = Vector Floating Point
Many Thanks
OK - all these postings have given me answers and ideas and things to try - now I'll go back into my cave for awhile, try them and digest the results. Thank you all for being so supportive - I really appreciate the time you have spent detailing your answers. I'm sure that others that find these posts will as well.
So after a couple of days of reading guides on the internets, I've been able to compile a mostly stock kernel that incorporates some of the changes made by joe85 in his NOLIGHTS Kernel. This kernel is stock other than the changes outlined below. The anykernel scripts keep your existing RAMDISK intact. If you had init.d support/other RAMDISK mod(s), it will still be present after flashing this kernel.
mKernel_v1.3
-Added TUN module for VPNC support
-Changed Display Maximum PWM from 232 -> 255
-Changed Display Minimum PWM from 8 -> 6
-Dimmed LEDs (from 20 mA -> 2 mA) or turned off completely
-Remove LED notification timer (does not shut off until dismissed)
------NotifyTimerOn versions use default timer to shut off notification LED
Click to expand...
Click to collapse
Adding overclocking has proven to be too much for me to do (more info on challenges of asynchronous dual core OC here. There isn't really much of an update going from 1.2 -> 1.3. I just re-did the changes from stock and tracked them using github. I did leave out the setting that joe85 made that allowed users to set a LED brightness via cmd line. There are 2 versions - mKernel_dim_1.3 for dim capacitive LEDs and mKernel_LEDoff_1.3 for capacitive LEDs which are always off.
You need a 2.3.4 based ROM for it to work and it can be flashed from recovery.
You can also flash it via joeykrim's Flash Image GUI with runs on your phone and is compatible with HBOOT 1.50. LINK!
Thanks to koush for the anykernel scripts and joe85 for all of his work (I just copied it into the new 2.3.4 kernel).
Everything works fine on my phone, but please post if you have any problems (not responsible, blah, blah, blah ).
github source with commits showing changes from stock kernel. There's not many and none should affect battery, performance, etc. compared to stock.
Nice will be checking this out for ya in a bit. Will report back
Currently on Myn's rom and about to give this a go Thank you.
Sent from my PG86100 using xda premium
Cool, gonna run it. Thanks.
Nandroids are for sissies.
Bang.
jayharper08 said:
Currently on Myn's rom and about to give this a go Thank you.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Dude, where can I find Myn's rom?! Been sporting him on Evo4g but miss him on my 3D.
Ok I wanna try too, but how come nobody reported back lol....
>.>
<.<
EDIT: running this now, lovin it dim lights + other mods, stock kernel, but with my ROMs ramdisk
lloydcabraham said:
Dude, where can I find Myn's rom?! Been sporting him on Evo4g but miss him on my 3D.
Click to expand...
Click to collapse
Rootzwiki.com
lloydcabraham said:
Dude, where can I find Myn's rom?! Been sporting him on Evo4g but miss him on my 3D.
Click to expand...
Click to collapse
Yup. Like il said, it's on rootzwiki, but there is a link in this thread for it. Last Page.
http://forum.xda-developers.com/showthread.php?t=1254341
Sent from my PG86100 using xda premium
mwalt2 said:
So after a couple of days of reading guides on the internets, I've been able to compile a mostly stock kernel that incorporates some of the changes made by joe85 in his NOLIGHTS Kernel. This kernel is stock other than the changes outlined below.
You need a 2.3.4 based ROM for it to work and it can be flashed from recovery.
Thanks to whomever made all of the scripts in the .zip and joe85 for all of his work (I just copied it into the new 2.3.4 kernel).
Everything works fine on my phone, but please post if you have any problems (not responsible, blah, blah, blah ).
Click to expand...
Click to collapse
You are now my hero! I have been dreaming of low lights since 2.3.4 came out! What about CIQ removal and the such?
I would thank the post but I ran out I'll hit you up tomorrow!
Also, I wont be able to provide feedback for a couple days. I am doing some load testing on my latest ROM.
scrosler said:
You are now my hero! I have been dreaming of low lights since 2.3.4 came out! What about CIQ removal and the such?
I would thank the post but I ran out I'll hit you up tomorrow!
Also, I wont be able to provide feedback for a couple days. I am doing some load testing on my latest ROM.
Click to expand...
Click to collapse
From my limited understanding android kernels and upgrading them, if the ROM you're using has it already removed, it will still be removed after flashing this kernel. CIQ removal is just done in the ramdisk. The compiled kernel makes a zImage and that, along with the modules for wimax & wifi, is all that is in the zip. The scripts in the zip extract your current boot.img, replaces the old zImage with the one in the zip, and re-makes boot.img (at least that's how I envision it working...could be wrong).
mwalt2 said:
From my limited understanding android kernels and upgrading them, if the ROM you're using has it already removed, it will still be removed after flashing this kernel. CIQ removal is just done in the ramdisk. The compiled kernel makes a zImage and that, along with the modules for wimax & wifi, is all that is in the zip. The scripts in the zip extract your current boot.img, replaces the old zImage with the one in the zip, and re-makes boot.img (at least that's how I envision it working...could be wrong).
Click to expand...
Click to collapse
Correct. CIQ crap is in the ramdisk. I'm trying this asap!! Muchas Gracias!!!
About to give this a try, Thanks
nice to see your handy work mwalt! you'll be a android pro in no time
mwalt2 said:
From my limited understanding android kernels and upgrading them, if the ROM you're using has it already removed, it will still be removed after flashing this kernel. CIQ removal is just done in the ramdisk. The compiled kernel makes a zImage and that, along with the modules for wimax & wifi, is all that is in the zip. The scripts in the zip extract your current boot.img, replaces the old zImage with the one in the zip, and re-makes boot.img (at least that's how I envision it working...could be wrong).
Click to expand...
Click to collapse
sweet I think you just answered my question, your updater script uses the ROMs ramdisk then and ONLY replaces the kernel/zimage ???
O.M.J said:
nice to see your handy work mwalt! you'll be a android pro in no time
Click to expand...
Click to collapse
you in mpls ?!?!
mwalt2 said:
From my limited understanding android kernels and upgrading them, if the ROM you're using has it already removed, it will still be removed after flashing this kernel. CIQ removal is just done in the ramdisk. The compiled kernel makes a zImage and that, along with the modules for wimax & wifi, is all that is in the zip. The scripts in the zip extract your current boot.img, replaces the old zImage with the one in the zip, and re-makes boot.img (at least that's how I envision it working...could be wrong).
Click to expand...
Click to collapse
removing carrier IQ is big task and goes beyond the kernel, as you stated.
there was a guy over on SDX dev's that did it by removing the scripts from the framework.res apk. so basically the programs were still on the phone, but when you fired the phone up they didn't start.
that is the only way that i am aware of that it can be done. it's a lot deeper than the kernel and deleting apk files from the system.
EDIT** and when i say that is the only way i know of, that doesn't mean it is the only way.
Will this kernel work on Synergy 475 with EXT4 Opt.?
mwalt2 said:
From my limited understanding android kernels and upgrading them, if the ROM you're using has it already removed, it will still be removed after flashing this kernel. CIQ removal is just done in the ramdisk. The compiled kernel makes a zImage and that, along with the modules for wimax & wifi, is all that is in the zip. The scripts in the zip extract your current boot.img, replaces the old zImage with the one in the zip, and re-makes boot.img (at least that's how I envision it working...could be wrong).
Click to expand...
Click to collapse
Ok, I didint look at the zip until now and didint realize it wasnt the entire boot.img. Thanks for letting me know.
cobraboy85 said:
removing carrier IQ is big task and goes beyond the kernel, as you stated.
there was a guy over on SDX dev's that did it by removing the scripts from the framework.res apk. so basically the programs were still on the phone, but when you fired the phone up they didn't start.
Click to expand...
Click to collapse
They are also very deep in the framework.jar and service.jar not to mentions some APK. TrevE did a great write up here: http://forum.xda-developers.com/showthread.php?t=1247108
It shows alot of dirty stuff HTC did.
Running clean. It's so perfect I'm not sure but I have to try. LOL. Will report back.
Sent from my PG86100 using xda premium
Ramdisk Hijack - what is it?
- We are trying to load a custom ramdisk in order to be able to load a non-Sony based ROM on a locked bootloader using 2nd-init. This is a work in progress.
How can I help?
- My source code is here: https://github.com/keiranFTW/huashan_ramdisk-hijack also, you will find how to install this on there too.
You'll probably wonder why I'm trying to hack the stock ramdisk in - because my phone is my only device, I also need to use it as a phone. Once I can fix things this way I can move to using CyanogenMod Ramdisk.
Progress? CyanogenMod is currently booting on the phone but there are lots of non-working features.
This is not a ROM, do not install this unless you know what you are doing.
On completion I will give you this in form of an update.zip
#keiran
Any developers willing to help me out here?
I am busy with personal work, will check this out later... FYI you can't boot everything on same kernel... Specific kernel patches are required for some ROMs... Without those patches crucial rom features may not work...
Sent from my C6902 using xda app-developers app
DooMLoRD said:
I am busy with personal work, will check this out later... FYI you can't boot everything on same kernel... Specific kernel patches are required for some ROMs... Without those patches crucial rom features may not work...
Sent from my C6902 using xda app-developers app
Click to expand...
Click to collapse
I know this, and some of these kernel patches can be loaded as a module or even the ROM source code edited to suit the needs of the stock kernel.
Edit: I have had many people asking me if kexec could work, and the answer is no, probably not. Why? Because it requires a in-kernel patch as well as a module and so it is not possible to get it to work as we cannot flash a new kernel.
I have an idea and I'll start to merge changes soon
Sent from my C5303 using Tapatalk
I am not experienced in kernel dev but maybe i can contribute in limited extent.
Unluckily, i also got "NO" in bootloader unlockable and very dissappointed to see that.
I hope someone will be able to find an alternative.
Have you looked at this?
http://www.xda-developers.com/android/locked-bootloader-xperia-s-and-want-cm10-no-problem/
Work in peace...
OP
can you link me to some good references about chroot? I got the basic understanding, want to try it on linux on my laptop.
Closest analogy i can draw is the linux live cd, which runs the OS live without installation. If thats the case, and if we succeed in this process, we could use some partition to dump cm and run it from there.
But lets not get too far, im still in infancy stage.
Regards
Yasir
finally Got the basics of what you are doing... You are essentially doing the same thing letama atis112 and company did to run cm10 usng stock kernel, but hijacked stock ramdisk to run cm ramdisk.... Seems a good idea but will only work for CM10 (4.1 based) and later when locked bootloader gets 4.3, we could get cm10.2 as well. If you are doing the same thing they did, then hopefully it will work soon. If its something different, then wish u luck, ill keep tracking ur progress.
Yes, he is trying to have it done the same way as letama, atis and others with one minor difference - we don't have pre_hwconfig.sh, so he's trying with chargemon. Older ramdisk Keiran's github worked fine, but after some commits he made it doesn't boot. When I try with older ramdisk and newest step2.sh, everything except sdcard works fine. I have an idea - what if we kill every process with every possible way(killall5, pkill,etc) and then start it manually, by calling them from /system/bin? Maybe it's the way.
Some offtop here:
Maybe the kernel from leak works on locked BL's? If DooM haven't changed anything in it - it's very possible. Maybe someone with 4.3 leak on their phone would try locking the bootloader?(Of course only if that person knows how to unbrick, if something goes wrong).
MrSteve555 said:
Yes, he is trying to have it done the same way as letama, atis and others with one minor difference - we don't have pre_hwconfig.sh, so he's trying with chargemon. Older ramdisk Keiran's github worked fine, but after some commits he made it doesn't boot. When I try with older ramdisk and newest step2.sh, everything except sdcard works fine. I have an idea - what if we kill every process with every possible way(killall5, pkill,etc) and then start it manually, by calling them from /system/bin? Maybe it's the way.
Some offtop here:
Maybe the kernel from leak works on locked BL's? If DooM haven't changed anything in it - it's very possible. Maybe someone with 4.3 leak on their phone would try locking the bootloader?(Of course only if that person knows how to unbrick, if something goes wrong).
Click to expand...
Click to collapse
I assume you have the same issue of unlockable BL? anyways, i am waiting for 4.3 so that after playing with, we can try and run cm10.2 at least... + miui
I've redone your work, and i can succesfully hijack ramdisk...
I've CM booted up, but:
1. graphical glithes (i know the solution)
2. no baseband
3. no sdcard (inner, external)
But it's improvement
Source: https://github.com/dh-harald/hijack-ramdisk-huashan
dh.harald said:
I've redone your work, and i can succesfully hijack ramdisk...
I've CM booted up, but:
1. graphical glithes (i know the solution)
2. no baseband
3. no sdcard (inner, external)
But it's improvement
Source: https://github.com/dh-harald/hijack-ramdisk-huashan
Click to expand...
Click to collapse
If my girlfriend would let me and I was near you I would kiss you right now :*
Jokes aside, I think I might be able to fix SD card and the rest
Sent from my C5303 using Tapatalk
I dont think any processes with late_start class are working... This would explain SD and also network.
Try:
/system/bin/sdcard /data/media /mnt/shell/emulated 1023 1023
/system/bin/qseecomd
/system/bin/secchand
Anything really..
When I was hijacking ramdisk before but loading the stock ramdisk just for testing I also lost network as well as sdcard, and I'm sure that I lost WiFi too. A possible solution would be *not* to stop these services maybe?
Sent from my C5303 using Tapatalk
New source code is at: https://github.com/keiranFTW/huashan_ramdisk-hijack
- Updated to work with Android 4.3
- Using 2nd-init instead of chroot
- Recovery included (not sure if working)
#keiran
hijack
Hy
I modified the hijack source and recompiled the cm10.2 was.
hijack
dev tree
vendor blobs
I made a new thread on xda.
bagyusz said:
Hy
I modified the hijack source and recompiled the cm10.2 was.
hijack
dev tree
vendor blobs
I made a new thread on xda.
Click to expand...
Click to collapse
Hey,
Thanks, your changes have helped a lot, so I have expanded on them to make it possible to integrate into AOSP more easily. I also use /system/bin/chargemon instead of system/bin/wipedata, it is earlier in boot process.
I also might want to note that you are not killing all processes, you need awk {'print $2'} instead of awk {'print $2'}
But yeah, great work.. you did what many others couldnt.
My repositories:
dev tree
vendor blobs
hijack
Feel free to add pull requests, and i can add you to the repository if you like.
Keiran
If only this could be done in other devices, as I also have a locked Xperia, but it's a Live Walkman. Unfortunately it also has the Unlock Bootloader: "NO", so if could also be ported to other devices it would be great. Not forcing or pushing you, but trying something more updated than 4.0.4 would be great
is this...?
@KeiranFTW & @bagyusz
sick work guys way to not never give up and accomplish what was thought to not be possible goes without saying one of the best development breakthroughs this year!
hey, in either of your opinions would this in some way be portable to our locked as **** bls on S4 Verizon and AT&T? We havent had ASOP capabilities or 4.4 for that matter yet and everyone is stuck on safestrap 4.3 stock kernels. Any help on this would be much appreciated. Its either trying to port this method or trying that new AnyKernel2.0 today not trying to hard brick heh
msm7x27
KeiranFTW said:
.
Click to expand...
Click to collapse
would this method work on any msm7x27 after pointing partitions ?? @KeiranFTW
deleted.
I still don't know what you're talking about. eace
Sent from my C5303 using Tapatalk
concerning hijack
KeiranFTW,
i am sorry to bother you with what may or may not be a 4 square dev question(s).
can i attempt something similar without building custom kernel? ( i read evrything i can but, lack funds for proper hardware so am limited.)
can i alter the insmod-ing of kernel modules to come as close to the beginning of the boot process as possible and have hardware functional in spite of slaying zygote/android userspace ?
this thread http://forum.xda-developers.com/showthread.php?t=1937328 outlines a means to
mount?load? a loop device from init.rc
my thought is as i have a gt-p5210 x86 device it might be possible to fire up (no matter how ugly)
a livecd or straight forward ext4 linux.img.
I would be interested in any insight/ideas you may have toward that end.
thank you for your time.
m
This is only to be used if you know what you are doing. This enables Unsigned Kernel Modules on the SCH-i545 (NC5/NK1), and the i337 (NC1).
Flash downloaded zip in Recovery.
https://www.androidfilehost.com/?fid=95916177934548235
Package of Modules built by @Surge1223:
https://www.dropbox.com/s/mpyeju0082c6f9m/modules.zip?dl=0
NOTE: Many of these are useful, but don't just load them for fun, they can be dangerous. Also, some do not function as expected, i.e. fastchg.ko has no effect, this is known, but I use that module in specific to test if modload is functioning.
Usage:
-- ALL of these commands must be run as root ("SU' in terminal/ADB Shell)
-- Run "Modload" to enable unsigned modules
-- Run "insmod /path/to/module.ko" to load a specific module
-- Run "rmmod modulename.ko"
-- Run "lsmod" to view a list of currently loaded kernel modules
-- Run "Modload -r" to re-enable kernel module signature checks
Credits:
This is completely based off of @jeboo's original BypassLKM exploit on MK2.
The whole script is kanged from @Surge1223 's update of the BypassKLM exploit to NC5.
@tulth found the memory address to overwrite to re-enable this exploit on NK1.
I just packaged it into Surge's ModLoad script.
Screenshot of usage:
http://imgur.com/Yk9uq6e
This allows kernel to be setup on non unlocked bootloader correct? If so that's pretty neat. I have mdk just was wondering.
And so it begins!
bryantjopplin said:
This allows kernel to be setup on non unlocked bootloader correct? If so that's pretty neat. I have mdk just was wondering.
Click to expand...
Click to collapse
Only kernel modules.
Sent from my SCH-I545 using XDA Free mobile app
Great to see the fight still rages on!!
jeboo said:
Great to see the fight still rages on!!
Click to expand...
Click to collapse
Haha. Good to see you around [emoji14] If you want to join the telegram group chat we have going about Kexec/the boot loader, just let me know, you are more than welcome.
I've been doing some research on this as of late (basically by tweaking the stock kernel and testing different gov's, turning off MP-Decison, etc) Now I want to learn more of what these unsigned modules are about. I have 2 questions. First is can we use other modules outside of the ones Surge compiled? (Like load in the smartassv2 gov or insert and overclock and voltage crtl) Second is for basic understanding can we get a description for each of the modules included in the package?
Thank you @npjohnson and @Surge1223 for your continued work on the VZW s4. I like so many are eagerly checking the thread for updates on the bootloader unlock!
wavedashdoc said:
I've been doing some research on this as of late (basically by tweaking the stock kernel and testing different gov's, turning off MP-Decison, etc) Now I want to learn more of what these unsigned modules are about. I have 2 questions. First is can we use other modules outside of the ones Surge compiled? (Like load in the smartassv2 gov or insert and overclock and voltage crtl) Second is for basic understanding can we get a description for each of the modules included in the package?
Thank you @npjohnson and @Surge1223 for your continued work on the VZW s4. I like so many are eagerly checking the thread for updates on the bootloader unlock!
Click to expand...
Click to collapse
A kernel module can execute code at the kernel level. I.e. make SMC Calls, and device hardware calls, and a lot more.
Any valid (signed or not) kernel module will attempt to load, but obviously fail if it isn't written correctly.
As for the modules in the zip, several are test modules, and some do not work correct, I haven't tested them all. The QuickCHG.KO one does not work for example. Feel free to test and report which ones work.
About 5 pages back in the boot loader thread, surge released over/under clocking modules (don't use if you aren't sure of what you are doing!). I would not recommend including these in a ROM (the over clocking ones), as the basic user will likely wayyy over clock and bad things will ensue.
Building a basic Linux kernel module is a complex process, as in most cases, you have to compile the module along with a kernel meant for your device. (Use NC5 source). If you need any help, I can put you i n touch with some helpful sources on building Kernel Modules.
I doubt a governor would come in the form of a module... But you could probably find a way to set the governor using a governor module and a ROM to enable governors. Also, don't load modules made for other devices/other kernels, as we mist remember, this is still the TW kernel.
npjohnson said:
A kernel module can execute code at the kernel level. I.e. make SMC Calls, and device hardware calls, and a lot more.
Any valid (signed or not) kernel module will attempt to load, but obviously fail if it isn't written correctly.
As for the modules in the zip, several are test modules, and some do not work correct, I haven't tested them all. The QuickCHG.KO one does not work for example. Feel free to test and report which ones work.
About 5 pages back in the boot loader thread, surge released over/under clocking modules (don't use if you aren't sure of what you are doing!). I would not recommend including these in a ROM (the over clocking ones), as the basic user will likely wayyy over clock and bad things will ensue.
Building a basic Linux kernel module is a complex process, as in most cases, you have to compile the module along with a kernel meant for your device. (Use NC5 source). If you need any help, I can put you i n touch with some helpful sources on building Kernel Modules.
I doubt a governor would come in the form of a module... But you could probably find a way to set the governor using a governor module and a ROM to enable governors. Also, don't load modules made for other devices/other kernels, as we mist remember, this is still the TW kernel.
Click to expand...
Click to collapse
I've had the conservative governor working for quite some time.
Has increased my battery life slightly but noticeable.
Do the modules that surge released also support u/v and o/v as well? or do you know?
I have tried building the kernel modules with nc5 source but haven't been able to get past a few errors but I do plan to get back to it sometime.
Do you mind pm'ing the sources you are speaking of? or post them here whichever you prefer
Thanks.
klabit87 said:
I've had the conservative governor working for quite some time.
Has increased my battery life slightly but noticeable.
Do the modules that surge released also support u/v and o/v as well? or do you know?
I have tried building the kernel modules with nc5 source but haven't been able to get past a few errors but I do plan to get back to it sometime.
Do you mind pm'ing the sources you are speaking of? or post them here whichever you prefer
Thanks.
Click to expand...
Click to collapse
Which source? The NC5 kernel is what I was talking about. Then you can kang Linux modules for just about everything else. Other than the governors, this have to be specific to our device.
npjohnson said:
Which source? The NC5 kernel is what I was talking about. Then you can kang Linux modules for just about everything else. Other than the governors, this have to be specific to our device.
Click to expand...
Click to collapse
I mean the sources for building kernels.
I know where to get nc5 from.
I want to try to import other governors eventually once I get past my errors.
klabit87 said:
I mean the sources for building kernels.
I know where to get nc5 from.
I want to try to import other governors eventually once I get past my errors.
Click to expand...
Click to collapse
Well, I could describe it to you, but I'd butcher how to setup a kernel build env. @tulth could describe it much better.
To build a kernel module, you have to build them with the kernel. Honestly though the readme for the NC5 kernel describes the process fairly well.
I can walk you through general kernel building, but each one requires different tools/toolchains.
npjohnson said:
Well, I could describe it to you, but I'd butcher how to setup a kernel build env. @tulth could describe it much better.
To build a kernel module, you have to build them with the kernel. Honestly though the readme for the NC5 kernel describes the process fairly well.
I can walk you through general kernel building, but each one requires different tools/toolchains.
Click to expand...
Click to collapse
Oh ok. I thought you might have a few reliable threads/guides that I may not have seen yet.
I have the environment and toolchains setup I just have some errors that keep getting in the way so it never compiles.
I may take some time this weekend to setup my system as a dualboot again.
Been quite a while since I've done it.
Any particular problems with building anything android on the latest ubuntu?
I would like to use the latest LTS 64 bit
klabit87 said:
Oh ok. I thought you might have a few reliable threads/guides that I may not have seen yet.
I have the environment and toolchains setup I just have some errors that keep getting in the way so it never compiles.
I may take some time this weekend to setup my system as a dualboot again.
Been quite a while since I've done it.
Any particular problems with building anything android on the latest ubuntu?
I would like to use the latest LTS 64 bit
Click to expand...
Click to collapse
Stick with 14.04, and a quick note, dont go installing the newest java, because you have to have jdk 7, and at least on my end, it kept resetting default to jdk 8.
Tl:dr: don't deal with 14.10. God its a pain.
If you want to PM me the errors, I might be able to help.
npjohnson said:
Stick with 14.04, and a quick note, dont go installing the newest java, because you have to have jdk 7, and at least on my end, it kept resetting default to jdk 8.
Tl:dr: don't deal with 14.10. God its a pain.
If you want to PM me the errors, I might be able to help.
Click to expand...
Click to collapse
Thanks for the tip.
I have everything setup in a vmachine but I recall you saying a while back that you never had any luck building with a vmachine
so I'm gonna dual boot for now.
I saved a screenshot of the errors so I will find it and pm you when I can.
thanks.
Sorry if this is off topic, but with loading custom modules couldn't you in a way make NC5/NK1 compatible with AOSP Roms? Just build what they need?
uplusion23 said:
Sorry if this is off topic, but with loading custom modules couldn't you in a way make NC5/NK1 compatible with AOSP Roms? Just build what they need?
Click to expand...
Click to collapse
Its called KitPop (its in the Dev section) [emoji14] MTP and WiFi softboot are the only bugs. Got WiFi AP to work.
Based on the first 5.1.1 sources, version OI5
Modifications:
SELinux unlocked
Disabled protection does not allow to boot the OS(disabled at the level of Linux kernel)
Permissive mode is set automatically at boot (without the possibility to switch back to enforce)
Before(you can do it after flash,but recommended before) installing the kernel required go to build.prop,find ro.securestorage.support and set the value to false. System may forget your WiFi passwords after flash custom kernel.
SecurityLogAgent has to be removed or frozen.
Flash kernel in odin.
v2 - SELinux fix.
Download: Google Drive
Sources: Google Drive
Blue cat said:
Based on the first 5.1.1 sources, version OI5
Modifications:
SELinux unlocked
Disabled protection does not allow to boot the OS(disabled at the level of Linux kernel)
Permissive mode is set automatically at boot (without the possibility to switch back to enforce)
Before installing the kernel required go to build.prop,find ro.securestorage.support and set the value to false. System may forget your WiFi passwords after flash custom kernel.
Flash kernel in odin.
This is my first kernel which I create on Linux. I hope everything will be working stable.
Download: Google Drive
Click to expand...
Click to collapse
Thank you - I flashed it as per your instructions. Seems to have worked fine and it's showing it as running as permissive!
Hi,
I made mine for my rom, but yours is good too.
Thank you for the comunity
Re...
Oops problems !! security notification
Alan-B said:
Hi,
I made mine for my rom, but yours is good too.
Thank you for the comunity
Re...
Oops problems !! security notification
Click to expand...
Click to collapse
I think you should remove ALL knox apk,because i never not seen security notifications on my device.
This kernel have only 2 changes.
security/selinux/Makefile and security/selinux/selinuxfs.c
Blue cat said:
I think you should remove ALL knox apk,because i never not seen security notifications on my device.
This kernel have only 2 changes.
security/selinux/Makefile and security/selinux/selinuxfs.c
Click to expand...
Click to collapse
Hi,
With my boot.img I have no this message! It is when I made out a will your that and come this message!
NB:
Your Boot and all the eliminated knoks!! (Rom deodex 5.1.1)
Alan-B said:
Your Boot and all the eliminated knoks!! (Rom deodex 5.1.1)
Click to expand...
Click to collapse
Ok,I found a solution.
You need to remove SecurityLogAgent
Bluecat, thanks for this! I wonder if you know what differences exist between the P605 and the P607T. Also, did you use the EUR_LL source from Samsung's opensource portal? Its strange that they already have the source out for the P605, but nothing yet for the P607T which received the update first. Makes me think maybe the code base is the same and its only the bloatware bundled by the carrier that differs?
I am also curious to just learn and get my hands dirty with this. Can you share the Makefile for this kernel, or just point towards the guide you used (assuming you used one) to compile this?
karthikrr said:
Bluecat, thanks for this! I wonder if you know what differences exist between the P605 and the P607T. Also, did you use the EUR_LL source from Samsung's opensource portal? Its strange that they already have the source out for the P605, but nothing yet for the P607T which received the update first. Makes me think maybe the code base is the same and its only the bloatware bundled by the carrier that differs?
I am also curious to just learn and get my hands dirty with this. Can you share the Makefile for this kernel, or just point towards the guide you used (assuming you used one) to compile this?
Click to expand...
Click to collapse
Sorry,but i dont know differences between the P605 and P607T.
Yes,sources SM-P605_EUR_LL_Opensource.zip and version OI5.
If you want check have code 607 and 605 differences or not you should check checksum both original zImage(linux kernel). Extract them from both boot.img and compare.
Version 2 use standart selinux permissive way used by mostly kernel developers,it's have many changes in code now and it's will be very long to explain how to change to permissive,just use my sources available now in first post and compare them with original sources.
If you talk about how to compile kernel...was use many guides and other forums...hard part was only create .config file
Blue cat said:
Sorry,but i dont know differences between the P605 and P607T.
Yes,sources SM-P605_EUR_LL_Opensource.zip and version OI5.
If you want check have code 607 and 605 differences or not you should check checksum both original zImage(linux kernel). Extract them from both boot.img and compare.
Version 2 use standart selinux permissive way used by mostly kernel developers,it's have many changes in code now and it's will be very long to explain how to change to permissive,just use my sources available now in first post and compare them with original sources.
If you talk about how to compile kernel...was use many guides and other forums...hard part was only create .config file
Click to expand...
Click to collapse
Will try to extract the zImage from the P607T boot.img. I do not have the P605 though, do you know if the stock boot.img is downloadable anywhere?
Thanks for uploading the source. I just finished downloading the original source from the opensource site, will compare the two and try to understand.
I do know how to complile a linux kernel, I meant can you share the .config file (not the makefile, as I wrongly stated earlier), so I can see what has changed across the entire kernel. Rather than just change one line directly in the config file to disable SELinux, I wanted to use make menuconfig and go through the whole process, just to learn more about android kernels. But since I do not know much about the hardware and driver requirements, wanted to see a stock .config as well as your changed .config to understand.
karthikrr said:
Will try to extract the zImage from the P607T boot.img. I do not have the P605 though, do you know if the stock boot.img is downloadable anywhere?
Thanks for uploading the source. I just finished downloading the original source from the opensource site, will compare the two and try to understand.
I do know how to complile a linux kernel, I meant can you share the .config file (not the makefile, as I wrongly stated earlier), so I can see what has changed across the entire kernel. Rather than just change one line directly in the config file to disable SELinux, I wanted to use make menuconfig and go through the whole process, just to learn more about android kernels. But since I do not know much about the hardware and driver requirements, wanted to see a stock .config as well as your changed .config to understand.
Click to expand...
Click to collapse
My config https://drive.google.com/file/d/0BxQroXyaGzZOSmdieTNVaFY3VjA/view?usp=sharing
Boot https://drive.google.com/file/d/0BxQroXyaGzZOVFZGZGs3YmloX2s/view?usp=sharing
I dont have original config,you can create your own on linux.
Blue cat said:
My config https://drive.google.com/file/d/0BxQroXyaGzZOSmdieTNVaFY3VjA/view?usp=sharing
Boot https://drive.google.com/file/d/0BxQroXyaGzZOVFZGZGs3YmloX2s/view?usp=sharing
I dont have original config,you can create your own on linux.
Click to expand...
Click to collapse
Brilliant! Thanks for sharing ... As and when I learn anything relevant to the issue of P605 vs. P607T, will update here.
Why does the wifi password get forgotten on every boot?
Any fix for that matter?
valexi said:
Why does the wifi password get forgotten on every boot?
Any fix for that matter?
Click to expand...
Click to collapse
Blue cat said:
Based on the first 5.1.1 sources, version OI5
Before installing the kernel required go to build.prop,find ro.securestorage.support and set the value to false. System may forget your WiFi passwords after flash custom kernel.
SecurityLogAgent has to be removed or frozen.
Flash kernel in odin.
Click to expand...
Click to collapse
Maybe you missed the update to the original post, the fix is as above, set securestorage to false. Since you have already flashed, you can still go to build.prop, make this change, reboot, and you should be fine.
karthikrr said:
Maybe you missed the update to the original post, the fix is as above, set securestorage to false. Since you have already flashed, you can still go to build.prop, make this change, reboot, and you should be fine.
Click to expand...
Click to collapse
I tried this. With ro.securestorage.support false. Still no WiFi passwords saved after reboot.
Other than that, this works great!
Xposed (for Samsung by wanam) works great!
valexi, the only thing Ive seen suggested in your case is to reflash the firmware. I do not know of any other solutions for this, because pretty much everybody with this problem seems to have solved it when they changed the securestorage thing.
BlueCat, I went ahead and compared checksums for the stock p607t and p605 kernels, they do NOT match. I also extracted the kernels themselves and the zimage files are of different sizes. I then compared the default config files of the P605_LL_EUR source with the only available source for the P607T, which is KK ... They are considerably different. I am of course going with the assumption that the core config for the kernel between KK and LL should not be TOO different, but of course, this is NOT a reliable test. Lastly, I should also say, the P607T source contained an insane number of config files in the Arch/Arm/configs folder, while the P605 source only had three files! I only compared the three that were common ... It seemed like the 607T has the config files for every possible version of the device, while the 605 one had very specific configs for that device only ... This I am speculating based on the fact that the 607T folder even had a msm8894_sec_l03ltmo_defconfig file in addition to the msm8894_sec_l03leur_defconfig file in the 605.
Will do more comparisons over the next few days, but it does seem like there are more changes under the hood between the 605 and the 607T than one would expect. I really wish samsung would release the source for the 607t, but if you check that page, there is just one single KK code there and nothing else, so it does not seem likely anytime soon
Blue cat said:
Ok,I found a solution.
You need to remove SecurityLogAgent
Click to expand...
Click to collapse
Re,
Ok remove SecurityLogAgent and folder Container it is ok...
But delete all other knox and Klm gives a problem with the playstor. (Certain protections cannot be erased)
Hey guys,
Great news around, especially with roms like Alan-B's. Thanks for sharing :good:.
Running 4.4, planning to update 5.x as soon as I'm sure I can run Linux Deploy (meaning the need of permissive kernel), though I can't find any intel about VTS (Virtual Terminal Support) enabled kernel. I've been looking for months a way to run framebuffered distros and looks like this is the solution.
I could try to make it myself but I have no experience in kernels, would someone mind give me a hand to get to this goal? At least give me a hint to "quickly" develop and try one, to see if it works and how well...
Don't even know if I'm looking the right way anymore, so thanks by advance for any help and again for the sharing :highfive:.
karthikrr said:
valexi, the only thing Ive seen suggested in your case is to reflash the firmware. I do not know of any other solutions for this, because pretty much everybody with this problem seems to have solved it when they changed the securestorage thing.
Click to expand...
Click to collapse
But when I reflash the firmware how can I set securestorage BEFORE installing permissive kernel as I don't have root to change build.prop?
valexi said:
But when I reflash the firmware how can I set securestorage BEFORE installing permissive kernel as I don't have root to change build.prop?
Click to expand...
Click to collapse
You can't. Reflash, root, edit build.prop, reboot, set wifi password once again, reboot, it SHOULD be fine. If its not after this sequence, Im not sure what else may work. Every case of this particular problem that I've seen was resolved with this solution.
Luckily I didn't reflash yet. I checked again build.prop and securestorage was true. For some reason it didn't stick first time.
I edited it again and now WiFi works as intended. So I can say that this solution works. Great kernel.
Sent from my ONE A2003 using Tapatalk