Related
This thread is now obsolete.
Kernel sources for build 5.26.0 have been released:
https://opensource.motorola.com/sf/go/projects.milestone/frs.milestone_source_froyo
I've pushed some new pre-compiled modules to github, though beware, I haven't had time to test all of them on device yet:
https://github.com/nadlabak/android...mmit/b300803348705d3fc5ce76d8c88d57186748a370
As the kernel sources are not yet available from the Motorola's open source project, here is an outline how I compiled the overclock and cpufreq governor modules. (Btw., the overclock module needed a substantial adaptation, see the source here: http://android.doshaska.net/2.6.32oc )
I'm using the sources from this AOSP repo:
Code:
git clone git://android.git.kernel.org/kernel/omap.git
git checkout --track -b android-omap-2.6.32 origin/android-omap-2.6.32
Use the sholes config:
Code:
make sholes_defconfig
flags that need to be disabled:
CONFIG_LOCALVERSION_AUTO
CONFIG_MODVERSIONS
CONFIG_DEBUG_MUTEXES
CONFIG_SCHEDSTATS
CONFIG_SCHED_DEBUG
[updated on 17.01.2011, thanks go to Skrilax_CZ]
At least the ext2 will work without panics when compiled using this config.
For tun, cifs and nfs there is still some additional config mismatch that prevents the modules to work without null pointer dereference oops.
Also, even when no custom kernel module is used, you can get the kernel panic very easily, try to enable wifi and do:
Code:
cat /proc/kallsyms
If you're interested in a more detailed android kernel compilation guide, you can e.g. roughly follow this Droid kernel guide: http://www.droidforums.net/forum/rescue-squad-guides/31452-how-compile-your-own-kernel.html
Thanks for starting this thread kabaldan! It is a great starting point in tackling the issue of adding tun support to the new kernel (tun.ko module). I am not as good as many others in this, but trying won't hurt. Meanwhile if someone else is working on tun support - share experience here!
If kernel seems to be ok, sometimes mounting with new version of busybox won't work.
I used to get kernel panic when use newer version of busybox (not Android kernel but my own embedded linux)
Hey Nadlabak can you add DLNA function of CM6?
same problem using droidx kernel sources. insmod ok, mount reboots the phone
yantz
I tried droid2 kernel module - doesn't work either
I noticed OpenVPN included in CM6 also relies on this kernel module. Hence doesn't work. I guess we won't (ever) see kernel sources for that leaked kernel we are now using. I assume Motorola will release the sources sooner or later, but not before official Froyo layout. The waiting is killing me! kabaldan, can't you try to do some magic as you did with the overclock module? The beer is from me!!!
Can you test this attached tun.ko?
Insmod is OK, but I currently don't have time for any further tests...
EDIT: don't bother, kernel panic as usual
Module loads fine, but when attempt to use it, phone reboots, just like with the module compiled from DroidX sources..
leobg said:
Module loads fine, but when attempt to use it, phone reboots, just like with the module compiled from DroidX sources..
Click to expand...
Click to collapse
So, I got it loaded - insmod works just great, just like it did on the 2.1 kernel.
I'm trying to use the CM6 built-in OVPN settings, but I can't find any documentation on the setup. How did you get it set up?
I have
/sdcard/openvpn/
cert.crt
ca.crt
config.conf
config.ovpn
pem.key
I realize that config.conf and config.ovpn are the same file- but I use this VPN on windows and on Mac, and I wasn't sure the requirements on Linux.
If I can't find some documentation I'll try downloading the OpenVPN settings app from the market and playing with that.
Also, I don't know if it's true or not, but I heard the Milestone2 source compiled driver could work.
Are you trying the module kabaldan provided? It doesn't seem to work, at least for me. Loads fine, but phone crashes when setting up tun interface. I couldn't get OpenVPN in CM6 0.3 to work so far. I am testing the tun.ko with the cisco vpn package (which worked great on the old kernel with CM6 0.2) vpnc. When I initiate the connection, phone reboots if the attached here tun.ko is used. I also tried with tun.ko compiled from DroidX sources - same thing - phone reboots. I am not sure where did kabaldan take/compile this module from.
Sent from my Milestone using Tapatalk
I was using the same one, I was thinking maybe he could use the info from more than one phone. I'll try get-a-robot or OpenVPN Installer, but I won't hold my breathe. I was just hoping to use the built-in functionality of the ROM.
*edit* Just saw he removed it because it doesn't work yet, oh well.
the kernel doesnt seem to like any other fs not built into it. i've tried several, ext2, ext3, ext4, cifs, jffs, reiserfs etc. all modules would load without a problem but system will reboot during mount. heck i even tried creating logical volume on the partition. volume created fine, but when time to mount, it reboot
i ended up using a 2nd vfat partition for apps2vfat, on top of native froyo move to sd. moved my debian arm there and manually, yes manually, replace many symlinks in libs to copied files
hopefully next froyo release for other regions would provide a different kernel
yantz
hey kabaldan wondering if you've had another chance to look at an updated tun.ko
Finally some breakthrough. The great Skrilax_CZ has made some hard debugging and one very good guess:
CONFIG_DEBUG_MUTEXES must be disabled in the kernel config.
At least the ext2 module compiled this way is working without panics now.
Congrats to Skrilax!
EDIT: Tun nor nfs not tested yet..., cifs unfortunately still not working.
kabaldan said:
Finally some breakthrough. The great Skrilax_CZ has made some hard debugging and one very good guess:
CONFIG_DEBUG_MUTEXES must be disabled in the kernel config.
At least the ext2 module compiled this way is working without panics now.
Congrats to Skrilax!
EDIT: Tun nor nfs not tested yet..., cifs unfortunately still not working.
Click to expand...
Click to collapse
This means that now the app2ext work?
Where are the modules for we test?!
Thanks for the news!
Modules for testing:
ext2 - http://code.google.com/p/cyanogenmod4milestone/issues/detail?id=197#c19
tun - http://code.google.com/p/cyanogenmod4milestone/issues/detail?id=222#c4
Hi sort of a newbie here... So does this mean that data2ext will work?
Sent from my Milestone using XDA App
Hi Nadlabak...maybe you already know.
For the cifs module, how about slow-work is made available as a module.
as is done at this link
http://forum.xda-developers.com/showpost.php?p=9271775&postcount=4
after further testing:
ext2 mounting now works, reading from ext2 partition too, but writing still causes panic
tun causes panic too
Let's hope for a soon kernel source release, as it looks like we won't get much further without it.
edowar: thanks for the link
@kabaldan
Could it be possible to create a swap module for milestone ?
It seems that running kernels does not have this feature yet and i'm not sure motorola to implement it for next 2.2 release so .... well just wondering !
Hi,
avetny asked me to take a look at the g2x kernel to add OC/UV, so i did build a kernel with oc/uv added. You can read more about the kernel on the o2x thread. With this kernel you should be able to use Pimp My Cpu to manage cpuspeed/voltages on the fly.
I do not own a g2x device so i could not test this kernel, try at your own risk.
g2x-kernel-2.6.32.9-fakeShmoo-cpasjuste.5.zip : db7a11365e8520424f1ed579b666623f
EDIT :
Since i do not have the device, if someone wants to continue the work (fix wifi/bt) you'll find the sources and changes here : https://github.com/Cpasjuste/android_kernel_lg_p999/commits/fakeShmoo
Note that you NEED to add "init.d" support to the kernel initramfs :
Add at the end of the init.rc script :
Code:
# Execute files in /etc/init.d before booting
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
And maybe the "99complete" script to "/system/etc/init.d" :
Code:
#!/system/bin/sh
sync;
setprop mcr.filesystem.ready 1;
Thanks a lot for this. Look forward to giving it a go
Kernel boots fine, however,it breaks wifi. Will continue testing and see how everything else it
jlevy73 said:
Kernel boots fine, however,it breaks wifi. Will continue testing and see how everything else it
Click to expand...
Click to collapse
Arg that's strange, i don't see why wifi would be broken :/
Cpasjuste said:
Arg that's strange, i don't see why wifi would be broken :/
Click to expand...
Click to collapse
It is...when I flashed I say the wifi modules loading.
But wow, this kernel is fast. Smartbench just shot through the roof.
jlevy73 said:
It is...when I flashed I say the wifi modules loading.
But wow, this kernel is fast. Smartbench just shot through the roof.
Click to expand...
Click to collapse
Note that it's not OC by default. Could you try Pimp My Cpu on it to see if it work ? Thanks
For the wifi module, i'll wait for "avetny" if he knows anything.
Cpasjuste said:
Note that it's not OC by default. Could you try Pimp My Cpu on it to see if it work ? Thanks
For the wifi module, i'll wait for "avetny" if he knows anything.
Click to expand...
Click to collapse
That's what I mean by wow it's fast. I installed pimp my cpu and have it running @ 1200/300 while I do some benchmarking. Pimp my cpu is working very well.
jlevy73 said:
That's what I mean by wow it's fast. I installed pimp my cpu and have it running @ 1200/300 while I do some benchmarking. Pimp my cpu is working very well.
Click to expand...
Click to collapse
Ha that's very cool. Many thanks for the "bravery"
Just need to fix wifi now :x
I won't be able to do so myself without a device to test so some help will be required. The recovery install script just copy the "drivers/net/wireless/bcm4329/wireless.ko" module to "/system/lib/modules/wireless.ko" on the device. Maybe on the g2x the modules are located somewhere else.
Cpasjuste said:
Ha that's very cool. Many thanks for the "bravery"
Just need to fix wifi now :x
I won't be able to do so myself without a device to test so some help will be required. The recovery install script just copy the "drivers/net/wireless/bcm4329/wireless.ko" module to "/system/lib/modules/wireless.ko" on the device. Maybe on the g2x the modules are located somewhere else.
Click to expand...
Click to collapse
Let me check to see where the drivers are located.
jlevy73 said:
Let me check to see where the drivers are located.
Click to expand...
Click to collapse
Update: Yep it's located in /system/lib/modules
Upon quick look it appears as though the permissions for the .ko file might be incorrect. Let me try something to see if it helps.
jlevy73 said:
Update: Yep it's located in /system/lib/modules
Upon quick look it appears as though the permissions for the .ko file might be incorrect. Let me try something to see if it helps.
Click to expand...
Click to collapse
Your right, this could maybe be the problem.
jlevy73 said:
Kernel boots fine, however,it breaks wifi. Will continue testing and see how everything else it
Click to expand...
Click to collapse
Getting the same wifi problem.
But besides that everything seems to be working fine.
Tried playing around with the permissions but that didn't seem to help. Also BT appears to be break with this kernel.
Also confirmed wifi is broken with this kernel.
flak0 said:
Also confirmed wifi is broken with this kernel.
Click to expand...
Click to collapse
Can you try turning on BT and seeing if that's broken for you as well? Thanks
Is dmesg spitting out anything of interest?
Confirmed. I wonder if we push the original wireless.ko if.it will work?
Since i do not have the device, if someone wants to continue the work you'll find the sources and changes here : https://github.com/Cpasjuste/android_kernel_lg_p999/commits/fakeShmoo
Note that you NEED to add "init.d" support to the kernel initramfs :
Add at the end of the init.rc script :
Code:
# Execute files in /etc/init.d before booting
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot
And maybe the "99complete" script to "/system/etc/init.d" :
Code:
#!/system/bin/sh
sync;
setprop mcr.filesystem.ready 1;
Checking dmsg now
I can also confirm that the kernel works well with OC/UV but WiFi does not work. Bluetooth isn't working for me either.
Hi,
Help me compile cifs.ko and nls_utf8.ko for CifsManager.
Desire S original ROM: 1.47.401.4, kernel 2.6.35.10-g2ee27f5
Thx
p.s. S-OFF, root on, error "no such device".
please help!
For compiling kernel modules you need a working toolchain for your cpu architecture.
Try to find kernel for your device, where this module already present.
problem is solved.
1. download "2.6.35.10-gdd56551" files nls_utf8.ko, cifs.ko from
http://forum.xda-developers.com/showthread.php?t=1039004
2. edited HEX-string gdd56551 to g2ee27f5.
3. enjoy!
Sorry for my ignorance, but what exactly does cif do?
i saw this feature present in leedroid
dimkew said:
problem is solved.
1. download "2.6.35.10-gdd56551" files nls_utf8.ko, cifs.ko from
http://forum.xda-developers.com/showthread.php?t=1039004
2. edited HEX-string gdd56551 to g2ee27f5.
3. enjoy!
Click to expand...
Click to collapse
Hey dimkew - I just tried this per your suggestion, however I wasn't as successful as you. After files hex'ed, then put in /system/lib/modules, then set CifsManager to insmod them, it still didn't work.
olyloh6696 said:
Sorry for my ignorance, but what exactly does cif do?
i saw this feature present in leedroid
Click to expand...
Click to collapse
Common Internet File System. Using the app CifsManager you can set file system mounts to mount a folder on your Android device to mount an SMB/CIFS Windows type network file share. You can also just use Linux commands to the mounting; but CifsManager is quick and easy to use only requiring a couple screen taps to get connected once your mounts/network shares are setup.
If you are on Android 4 and Sense ROM use my kernel it has cifs support
Sent from my HTC Desire S
Hi guys!
As some of you must have noticed, latest Samsung GT-I9500 firmwares carry a kernel configuration supposed to prevent SETUID privilege elevation.
Stock unmodified firmware with root is my preferred setup but also a strong dependency for all my development, for me this change is a massive setback if not a dealbreaker.
While poking around I found in about an hour something weird that reveled being a vulnerability, so I created a little thing to make it useful for now.
README:
Stupid SU: Galaxy S4 root helper by François SIMOND aka @supercurio
Circumvent an extremely weak false-security "Anti Root" mechanism implemented
on latest Samsung Galaxy S4 devices (on both Exynos and Qualcomm versions)
Preventing proper root function on official firmware breaks all my Voodoo apps
requiring stock+root and is a move that's hostile to both users and developers.
Samsung security might be embarassed by this proof of concept, as it defeats
their mechanism in a single line... not even with complex ARM assembler
but *one* line of shell script.
However, the goal here is to show Superuser solutions developers how to
deal with those devices for now, and provide a working solution to people who
bought a Galaxy S4 expecting to root it cleanly and easily but cannot.
This proof of concept is slightly slowing down Superuser calls, but its
"plain text" implementation has the merit of showing how stupid this exploit is.
SELinux configuration stays unmodified and active.
Features:
- Detect and supports both SuperSU and Koush's Superuser
- Installs Super SU binary by default
Make sure you have one of those Superuser apps installed:
- https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
- https://play.google.com/store/apps/details?id=eu.chainfire.supersu
Root feature doesn't rely on a "StupidSU kernel" which is only an installer.
Feel free to flash back Samsung's original boot.img from their official firmware
after booting at least once.
Important Note:
This "exploit" is so lame that it will be fixed in no time, making updated S4
a pain to root again.
I wish Samsung will reconsider their "Anti Root" approach, which is damageable
in every regard and defective by design as demonstrated here.
Also, I'm simply not interested developing for and promoting devices from
manufacturers hostile to developers: It's just a waste of valuable time.
Click to expand...
Click to collapse
INSTALL
1/ copy rooting/ directory in your initramfs
Make sure "root.sh" file is has an executable permission (chmod 744 recommended)
2/ Add those lines at init.universal5410.rc end:
# Stupid SU
service rooting /stupidsu/root.sh
class main
user root
group root
oneshot
3/ Assemble your initramfs with the associated Samsung official kernel binary
of choice in a regular boot image
4/ flash as boot.img
5/ At each boot, Superuser app are detected automatically and su binary adjusted
accordingly.
Click to expand...
Click to collapse
Source code
On GitHub
License
Kernels downloads, only for demo purposes of the concept, you can flash back original Samsung boot.img once rooted
GT-I9500 Stock + root StupidSU v4 UBUAMDE
GT-I9500 Stock + root StupidSU v4 XXUAMDK
GT-I9500 Stock + root StupidSU v4 XXUAME1
What's next
Owners of Qualcomm Galaxy S 4 devices experiencing the same dificulties with Samsung the anti root strategy might want to try this method, please let me know if you're ready for some experimentations.
Supercurio pleas add thraed t General section i think ther well bee lots of testers for i9505.thx for suport
Sent from my LG-P500 using xda app-developers app
Going to try this on latest LE1 stock kernel now .....thread is in correct section
edit: did not work on LE1 kernel. I will try once again. DId any one tried the MDK kernel..I am having again the problem with SU binaries installation..
Edit: Thanks bro. working on ME1 kernel now. Did mistake while doing tar. Appreciate it! Root is working fine but cant update the binaries of Supersu, still the root works fine.
Here comes the master welcome to SGS4 development forum mate.. (rahulzeven from twitter here )
So the BEST thing's just happened?!:laugh::good:
i repacked the kernel of Samsung-Updates.com-KERNEL-GT-I9500-XSE-I9500XXUAME1-1367637350 using supercurio method. Root works fine. All we need to is install it from ODIN and dont update the binaries of supersu.
Download Link
Edit: New file uploaded
grgsiocl said:
i repacked the kernel of Samsung-Updates.com-KERNEL-GT-I9500-XSE-I9500XXUAME1-1367637350 using supercurio method. Root works fine. All we need to is install it from ODIN and dont update the binaries of supersu.
Download Link
Click to expand...
Click to collapse
Thanks fo much! Will Titanium Backup work on this kernel?
Hope chainfire will start working on mobileOdin soon. So much easier to flash than.
... tapat*lked
GSeeker said:
Thanks fo much! Will Titanium Backup work on this kernel?
Click to expand...
Click to collapse
wrong file uploaded. Please download the same in 5 minutes. Uploading is on and the kernel date should be MAY 04
---------- Post added at 12:33 PM ---------- Previous post was at 12:28 PM ----------
GSeeker said:
Thanks fo much! Will Titanium Backup work on this kernel?
Click to expand...
Click to collapse
it should work as i dont use titanium backup and instead i use gobackup pro and it works fine anyway
MDK from OP working good, thanks
grgsiocl said:
i repacked the kernel of Samsung-Updates.com-KERNEL-GT-I9500-XSE-I9500XXUAME1-1367637350 using supercurio method. Root works fine. All we need to is install it from ODIN and dont update the binaries of supersu.
Download Link
Edit: New file uploaded
Click to expand...
Click to collapse
I'm trying to repack the kernel of korean gs4,
but I am a noob in kernel devs.
I can edit ramdisc, but fist trying in initramfs, zImage.
Is rooting directory means both root.sh and files(folder)?
and paste them on first class route?
hope you give some advices.. thanks
aslak89 said:
I'm trying to repack the kernel of korean gs4,
but I am a noob in kernel devs.
I can edit ramdisc, but fist trying in initramfs, zImage.
Is rooting directory means both root.sh and files(folder)?
and paste them on first class route?
hope you give some advices.. thanks
Click to expand...
Click to collapse
when you unpack the kernel you will have two folders one is ramdisk and other one is split_img (zimage). You need to copy the folder stupidsu folder in ramdisk and modify the init.universal5410.rc as per OP stated and repack the image
grgsiocl said:
when you unpack the kernel you will have two folders one is ramdisk and other one is split_img (zimage). You need to copy the folder stupidsu folder in ramdisk and modify the init.universal5410.rc as per OP stated and repack the image
Click to expand...
Click to collapse
then, is not necessary to recompile zImage?
ok I m going to try it right now, thank you grgsiocl
muhamet said:
Supercurio pleas add thraed t General section i think ther well bee lots of testers for i9505.thx for suport
Click to expand...
Click to collapse
Yes in fact I was hesitating, but as soon as someone is ready to assist me to try on a Qualcomm device (I9505 or T-Mobile Galaxy S4) I'll make a thread here too.
grgsiocl said:
Going to try this on latest LE1 stock kernel now .....thread is in correct section
edit: did not work on LE1 kernel. I will try once again. DId any one tried the MDK kernel..I am having again the problem with SU binaries installation..
Edit: Thanks bro. working on ME1 kernel now. Did mistake while doing tar. Appreciate it! Root is working fine but cant update the binaries of Supersu, still the root works fine.
Click to expand...
Click to collapse
Great then
aslak89 said:
then, is not necessary to recompile zImage?
ok I m going to try it right now, thank you grgsiocl
Click to expand...
Click to collapse
The point here is to have stock (unmodified Samsung binary) kernel running, with associated modules and no other modification.
Which gives you several usage options:
keep the StupidSU stock+root kernel (same kernel binary, same kernel modules, only very slightly initramfs scripts) that will auto-root depending on which Superuser APK you installed
you can flash back the official kernel and still enjoy root the same.
supercurio said:
The point here is to have stock (unmodified Samsung binary) kernel running, with associated modules and no other modification.
Which gives you several usage options:
keep the StupidSU stock+root kernel (same kernel binary, same kernel modules, only very slightly initramfs scripts) that will auto-root depending on which Superuser APK you installed
you can flash back the official kernel and still enjoy root the same.
Click to expand...
Click to collapse
Thank you for awsering
then I repacked my kernel but still not work.
copyed stupidsu and edited init.universal5410.rc in ramdisk and repacked boot.img.
I guess permission is the thing,
attach my shots
hope you loot at once.
Sent from my SHV-E300S using XDA Premium HD app
walda said:
Hope chainfire will start working on mobileOdin soon. So much easier to flash than.
... tapat*lked
Click to expand...
Click to collapse
He will after he will come back from his vacation.
I'll look into a fixed CF-Auto-Root for the I9505 as soon as I'm back on Sunday. I imagine that will be tested by Sunday evening, with a I9500 test version available sometime Monday. If all is well
In StupidSU environment and for this initial release Koush's Superuser app would
be preffered as SuperSU main UI refuses to launch because it cannot detect its
original su binary. Aside from that both work as expected.
Click to expand...
Click to collapse
This is because you're not installing the backup su binary. The UI app detects this is missing and triggers an update. Bug in StupidSU
aslak89 said:
Thank you for awsering
then I repacked my kernel but still not work.
copyed stupidsu and edited init.universal5410.rc in ramdisk and repacked boot.img.
I guess permission is the thing,
attach my shots
hope you loot at once.p
Click to expand...
Click to collapse
Alright I'm adding some logging in my scripts so you'll be able to see what's happening − or not
supercurio said:
Yes in fact I was hesitating, but as soon as someone is ready to assist me to try on a Qualcomm device (I9505 or T-Mobile Galaxy S4) I'll make a thread here too.
Click to expand...
Click to collapse
Brilliant news!!!! Thanks a LOT!!
Let's make it work!! It will be AWESOME if I could use latest STOCK Kernel in my ROM's......
I'll give you a hand
Hi all
This post will hopefully serve two purposes, one to help me find what Im looking for and the second to help other find similar.
Im looking for an N5 kernel that supports both CIFS and NFS, either built in or in the form of loadable modules. I have so far tried Faux and Franco, latest versions of both. I cant mount CIFS or NFS using the mount command with either of them. Are there any kernels on the N5 that support this properly?
If anyone knows any perhaps we can compile a list here so its clear which kernels support which features, searching high and low and trawling through kernel changelogs to find what I need is becoming quite laborious. Kind of makes me wonder why most kernel devs dont seem to want to publish a comprehensive feature list for their kernels, some do but most unfortunately dont.
Thanks in advance.
From what I can see there are kernels that support cifs - look in /system/lib/modules/ for cifs.ko.
[
I have not yet found a viable nfs module for the stock nexus, nor have I found a way to get the mount command to work.
It looks as if CM based roms may be able to deal with this, though.
Could you compile your own? If you want just to be able to simply transfer files ES File Explorer supports at least CIFS.
Sent from my Nexus 5 using xda app-developers app
Thus far I've found that Faux supports NFS, I'm able to mount directly via the busybox mount command, it just required a slight modification to the syntax. Unfortunately I've still not found any that support CIFS not even one that has the loadable modules for it. And I need these for shell scripts I'm using, which operate independently of apps so the usual file manager apps are of no use.
Sent from my Nexus 5 using Tapatalk
phobox360 said:
Thus far I've found that Faux supports NFS, I'm able to mount directly via the busybox mount command, it just required a slight modification to the syntax.
Click to expand...
Click to collapse
@phobox360 could you please post your command for NFS mount? I installed hammerhead-lp-faux123-024u kernel, tried both 'mount' and 'busybox mount' , with and w/o su, but still not able to mount NFS exports. Thanks in advance.