Database Info

[DEV] SSLStrip for Android , Open Source

SSLStrip for Android, is port from sslstrip(python script) to Android !
SSLStrip for Android requires a rooted device
Features included:
arpspoof
sslstrip
save sslstrip logs to sdcard
...
more is coming!
Works:
Galaxy nexus, AOKP maguro build 21 with francisco #47
Moto Atrix (stock firmware, but forget version )
Doesn't work:
Market link:
play.google.com/store/apps/details?id=com.crazyricky.androidsslstrip
Feel free to contribute on this project:
github.com/crazyricky/SSLStrip-for-Android

Works nicely on the hp touchpad. Cm9 9.0.0rc0alpha2

Excellent work buddy, what other type of goodies are you going to implement ?

Gave this a try, it seems like everything works except arpspoof (had to use actual arpspoof application separate - this caused problems but shows sslstrip itself working right).
Device used: Samsung Stratosphere

Can anyone explain what's this actually? And what it does?
Burned from my laser torch using pencil cells

The tool – called ‘SSL strip’ – is based around a man-in-the-middle attack, where the system for redirecting people from the insecure to the secure version of a web page is abused. By acting as a man-in-the-middle, the attacker can compromise any information sent between the user and the supposedly secure webpage.

Doesn't work here on sg2

It should, it works on my galaxy note.

moehawk said:
It should, it works on my galaxy note.
Click to expand...
Click to collapse
There different device although similar. Arpspoof worked for you?

Yes arpspoof works fine
jahrule said:
There different device although similar. Arpspoof worked for you?
Click to expand...
Click to collapse

moehawk said:
Yes arpspoof works fine
Click to expand...
Click to collapse
Wired I ran it both on eth0 and on wlan0 and neither did anything to my laptop on same connection

jahrule said:
Wired I ran it both on eth0 and on wlan0 and neither did anything to my laptop on same connection
Click to expand...
Click to collapse
Have you tryed installing Iptables from the play market or there could be firewalls in between?

moehawk said:
Have you tryed installing Iptables from the play market or there could be firewalls in between?
Click to expand...
Click to collapse
I for sure have iptables but forgot I was running droidwall. Will check again when I get a chance

Yea tried again with no luck. It ago detects to eth0 which is strange because my phone does not have a cat5 port lol.

Moehawk, ssltrip doesnt run in my galaxy note gingerbread xxla6 (gt-n7000). What rom use your note?? Thanks!!

Dont work (arpspoof/ssl strip) in my Xperia x10 mini with MiniCM9 (ICS).
Any ideas?? (i have ip tables)
Thanks

drakonflyfly said:
Moehawk, ssltrip doesnt run in my galaxy note gingerbread xxla6 (gt-n7000). What rom use your note?? Thanks!!
Click to expand...
Click to collapse
It was either the ICS StuNNeR or the CyanogenMod 9, i dont have a note anymore i downgraded to a one x which i regret very much.

Wow great app
Man, thanks for porting this to android your a complete super star.
Would it be possible to update the market version or someone post a recent apk here as ive noticed the market version does not have an option to save logs out, where as the github source says it does and ive got no idea where to start building the source with eclipse.
PLAzmA

Not working on HTC Desire
Hi,
I just tested it on:
-Model: HTC Desire / Bravo
-Rom: (aokp_bravo_milestone-5)
-OS: Android 4.0.4
-Kernel: 2.6.38.8 Tiamat-ICS#2
First of all, arpspoof standalone works fine. So I experimented a little with the iptable-commands out of the sourcecode and the shell reports:
"FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:450"
is this a possible reason for not showing me results in the app?

I haven't checked the code for that tool, but it seem that it may be dependent on the type WiFi chip you have (and how its implemented)? What are the device/driver dependencies for those tools?

[DEVS ONLY] CyanogenMod 11 for Samsung BCM21553 Development Discussion

WARNING: App2SD and Mounts2SD are not recommended for use with any OTA-enabled ROMs, as they break delta updates, and may cause problems during full upgrades. I suggest using my modified version of S2E, simple2ext_mod, instead.
NOTE 1: I recommend that everyone uses @Bhargav97's Google Apps package (cm11 v2.2 version or later). Other versions of gapps may cause issues or break delta updates.
NOTE 2: You must ensure that your phone is running the latest baseband available for your region, or else your device will not operate correctly when a SIM card is inserted. If you have a cooperve and tassve, you may need to flash the latest totoro baseband (which will work correctly on your device). Please see @marcussmith2626's stock ROM thread for links to the appropriate files.
Information for users:
This topic is intended only as a meeting point for other developers of the shared BCM21553 devices to discuss and solve issues related to development. If you are not a developer, please restrict your posts to the general discussion thread so that developers can maintain good communication. Thanks for your understanding.
First-time installation:
ClockworkMod v6.0.5.3 or later (MTD version) is mandatory to install CM11. If needed, download the latest recovery build here
Download the latest full OTA build for totoro from here
If necessary, flash the ClockworkMod v6 build, then reboot into recovery. If you can't flash the CWMv6 update package (.zip) in your existing recovery, use the Odin package (.tar.md5) instead.
Perform a data wipe - this is mandatory if upgrading from an older Android revision
Flash the OTA package and reboot.
How to update (via OTA):
Please consult the cm-ota instructions on Jenkins.
Current issues (06/10/2014)
OMX codecs (for accelerated audio/video - may never be solved)
SIM unlock doesn't work (you must remove your SIM lock in another device/ROM)
Video recorder
Summary of major work done:
Forked broadcomCM devices into androidarmv6 repository (forked from ics branches).
Initial changes needed for cm-11.0 have been committed to cooperve, tassve, totoro and bcm21553-common device trees.
All of Broadcom's code has been adapted for the cm-11.0 branch.
After some reverse engineering of the vendor binaries, "adbd" and "init" built from source now work correctly. ADB will now set the proper USB mode, can give a root shell, and no longer has a hardcoded dependency on /system/bin/sh, which should help a great deal with debugging. We also no longer need to use the init prebuilt binary - the source-built version is now compatible.
Implemented common kernel source for totoro, cooperve and tassve.
Implemented hybrid boot/recovery/charge ramdisk.
Fixed WiFi, Bluetooth, Bluetooth tether & mac addresses.
Fixed graphical performance regression on CM11 branch.
Fixed basic audio (speaker, microphone, software encoders/decoders)
Fixed GPS.
Fixed Gallery, wallpaper chooser, live wallpapers, RenderScript, and possible EGL crashes in other apps
Added workaround for SystemUI corruption
Fixed graphical corruption/stability issues (caused by buggy GL_EXT_discard_framebuffer extension)
Fixed RIL, telephony and audio routing to speakers, headset, earpiece, microphone and microphone mute.
Audio routing improvements/fixes, small graphics performance optimizations
Fixed camera
Fixed wifi tethering
Updated to newer bcmdhd wifi driver to resolve wifi instability
Fixed USB tethering (with caveats)
Improved audio routing and fixed BT headsets (SCO)
* = this code is work in progress, which means that it is not yet available in the OTA build.
XDA:DevDB Information
CyanogenMod 11 for Samsung BCM21553 series, ROM for the Samsung Galaxy Y GT-S5360
Contributors
psyke83
Version Information
Status: Testing
Created 2014-10-27
Last Updated 2014-10-27

I will update cooperve device tree as soon as I can. I guess @Alberto96 could adapt tassve (his device). Lets get some fun here
Enviado desde mi Xperia SP mediante Tapatalk

No problem First I'll try adb/init changes, and then adapt repo.

@psyke83 , I have created some threads regarding development of this BCM21553 devices with the information I was able to get while developing:
HW drivers: http://forum.xda-developers.com/showthread.php?t=2666566
Audio libs (source): http://forum.xda-developers.com/showthread.php?t=2682819
Enviado desde mi Xperia SP mediante Tapatalk

Ok, tested on CM9.
Hardware is fully initialized, but seems that there is an heavy memory corruption (like you said).
I/DEBUG ( 4743): debuggerd committing suicide to free the zombie!
F/libc ( 4747): Fatal signal 13 (SIGPIPE) at 0x0000128b (code=0)
F/libc ( 4748): Fatal signal 13 (SIGPIPE) at 0x0000128c (code=0)
F/libc ( 4749): Fatal signal 13 (SIGPIPE) at 0x0000128d (code=0)
F/libc ( 4750): Fatal signal 13 (SIGPIPE) at 0x0000128e (code=0)
F/libc ( 4751): Fatal signal 13 (SIGPIPE) at 0x0000128f (code=0)
F/libc ( 4752): Fatal signal 13 (SIGPIPE) at 0x00001290 (code=0)
F/libc ( 4753): Fatal signal 13 (SIGPIPE) at 0x00001291 (code=0)
F/libc ( 4754): Fatal signal 13 (SIGPIPE) at 0x00001292 (code=0)
I adapted almost all, i wasn't able to adapt just property_service.c & property_service.h so recovery/charging mode isn't working yet.
Great job @psyke83 !

Alberto96 said:
Ok, tested on CM9.
Hardware is fully initialized, but seems that there is an heavy memory corruption (like you said).
Great job @psyke83 !
Click to expand...
Click to collapse
Thanks for testing. To be clear, you're saying that CM9 boots into Android with the init built from the CM9 sources? I'm particularly curious to know if surfaceflinger is working OK. I suspected that something in the init may be causing problems either with the framebuffer or hgl libraries for CM11, but if it works on CM9, then I might be wrong.
I've merged the cm-11 bringup patches for tassve and cooperve. I can only confirm that it will allow the builds to complete (when all of the other integration patches are applied), but I imagine there will be more bugs that need fixing. If you find major bugs with the device configs, please submit them to gerrit or at least let me know,
We also need to organize a proper shared kernel source that we can integrate into the build system, and then get rid of the prebuilt kernels. Until then, you may need to recompile the kernel and modify your board files so that it doesn't use that generic "Thunderbird" name. The init.rc files are expecting the machine name to be "GT-S5360 Board", "GT-S5570I Board", etc. The init binary reads the machine name from the cmdline, and then converts to lowercase and filters spaces. So, the .rc file for the totoro would be "gt-s5360board" -> "init.gt-s5360board.rc".

psyke83 said:
Thanks for testing. To be clear, you're saying that CM9 boots into Android with the init built from the CM9 sources? I'm particularly curious to know if surfaceflinger is working OK. I suspected that something in the init may be causing problems either with the framebuffer or hgl libraries for CM11, but if it works on CM9, then I might be wrong.
I've merged the cm-11 bringup patches for tassve and cooperve. I can only confirm that it will allow the builds to complete (when all of the other integration patches are applied), but I imagine there will be more bugs that need fixing. If you find major bugs with the device configs, please submit them to gerrit or at least let me know,
We also need to organize a proper shared kernel source that we can integrate into the build system, and then get rid of the prebuilt kernels. Until then, you may need to recompile the kernel and modify your board files so that it doesn't use that generic "Thunderbird" name. The init.rc files are expecting the machine name to be "GT-S5360 Board", "GT-S5570I Board", etc. The init binary reads the machine name from the cmdline, and then converts to lowercase and filters spaces. So, the .rc file for the totoro would be "gt-s5360board" -> "init.gt-s5360board.rc".
Click to expand...
Click to collapse
Yes, CM9 with source built init & adbd binaries boots fine.
True, a proper shared kernel is better. But we also need an updated kernel source (request processing by Samsung osrc)
Sent from my GT-I9500 using Tapatalk

Good news: I just discovered that surfaceflinger works if I remove the hwcomposer.default library. However, there is some graphical distortion, and the colours are incorrect. Still, it's some progress. Will try to troubleshoot hwcomposer now.

android_native.h similiar with ANativeObjectBase.h without include <android/native_window.h>
updater-script cant run in cwm5 so need modified wanna force try to flash zip package but still not luck for boot coz messy ramdisk code.
temporary cwm6 still black screen so since its not working modified ramdisk is 1st think to do with old cwm5 (in my case) to running dualboot (stock cm) at least to make it boot 1st.
@psyke83 great work and still follow ur update from behind

Alberto96 said:
Yes, CM9 with source built init & adbd binaries boots fine.
True, a proper shared kernel is better. But we also need an updated kernel source (request processing by Samsung osrc)
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
Was there a white-screen bug with the init you built from source? I notice on my totoro that the screen turns white when the screen returns from off. It happens both in charge mode and in Android itself. I'm not sure if it's a bug caused by init or just something related to the stock kernel. I haven't been working with this device for very long, so I'm not aware of any common issues with the kernel, etc.
Ashutos1997 said:
This means cm11 boots now ?
Click to expand...
Click to collapse
-CALIBAN666- said:
sorry for offtopic,but are you back????
Click to expand...
Click to collapse
There's a general thread for off-topic posts (linked in the first paragraph of my first post)... please use it in future. This thread is supposed to be for developers to collaborate and fix bugs only.

psyke83 said:
Was there a white-screen bug with the init you built from source? I notice on my totoro that the screen turns white when the screen returns from off. It happens both in charge mode and in Android itself. I'm not sure if it's a bug caused by init or just something related to the stock kernel. I haven't been working with this device for very long, so I'm not aware of any common issues with the kernel, etc.
Click to expand...
Click to collapse
No white screen bug here. (i'm using my ramdisk but with source built init/adbd)
It should a bug related to missing backlight permissions:
chown system system /sys/class/backlight/aat1401-backlight/brightness
chown system system /sys/class/backlight/pwm-keypad-backlight.0/brightness
I had this bug when i've removed these lines

@bieltv.3, @Alberto96,
The shared kernel is working, but has only been tested with totoro. It only has basic functionality and certain drivers need updating, but for now, it can be a stable reference point. Can you please give me your current working defconfigs for your respective devices? I will update them to be compliant with CM11's configuration requirements and submit as initial defconfigs, to see if the kernel can work for your devices. Thanks.

psyke83 said:
@bieltv.3, @Alberto96,
The shared kernel is working, but has only been tested with totoro. It only has basic functionality and certain drivers need updating, but for now, it can be a stable reference point. Can you please give me your current working defconfigs for your respective devices? I will update them to be compliant with CM11's configuration requirements and submit as initial defconfigs, to see if the kernel can work for your devices. Thanks.
Click to expand...
Click to collapse
I will push cooperve kernel source this afternoon. Thanks for your work done, really appreciate. I hope I can upload tassve too, if Alberto dont mind. I will base it though on your tototo config, but on cooperve. As far as I know, cooperve need changes on its modules to get the kernel work good, as it have a different canera driver (updated one for 5 MP and flash)
Enviat des del meu Xperia SP usant Tapatalk

Kernel config source for cooperve has been updated. I'll push it gerrit as soon as I get home. I've updated on school, and I don't have the config of the server there. @psyke83 if you can take a look at it, I've made a pastebin, you can push to gerrit directly if you are OK with it, or make any changes you think are necessary:
http://pastebin.com/Svir6qtZ

psyke83 said:
@bieltv.3, @Alberto96,
The shared kernel is working, but has only been tested with totoro. It only has basic functionality and certain drivers need updating, but for now, it can be a stable reference point. Can you please give me your current working defconfigs for your respective devices? I will update them to be compliant with CM11's configuration requirements and submit as initial defconfigs, to see if the kernel can work for your devices. Thanks.
Click to expand...
Click to collapse
You can find my defconfig on github. It's updated.
https://github.com/Alberto96/androi...arch/arm/configs/cyanogenmod_tassve_defconfig
Sent from my GT-I9500 using Tapatalk

Thread cleaned. Please respect the dev's wish and do not post non development posts in this section

@psyke83 :
On CM9 using tassve kernel with built-in gememalloc there are problems (with heavy heavy heavy graphic corruption and laggy screen). (this error in logcat: [v3d_opt.c:v3d_thread:1415] wait timed out [1500]ms )
your commit (https://github.com/androidarmv6/and...mmit/17cd93229df1ff8f5f7616398b8b792a8fbd1c92) should fix this.
If i use your egl commit and use built-in gememalloc all should work but it will work as is on CM11 with heavy graphic corruption.
Without using built-in gememalloc and your egl commit CM9 runs great with much less corruption than CM11.
We should investigate more on this....something is wrong here with memory allocation.

Alberto96 said:
@psyke83 :
On CM9 using tassve kernel with built-in gememalloc there are problems (with heavy heavy heavy graphic corruption and laggy screen). (this error in logcat: [v3d_opt.c:v3d_thread:1415] wait timed out [1500]ms )
your commit (https://github.com/androidarmv6/and...mmit/17cd93229df1ff8f5f7616398b8b792a8fbd1c92) should fix this.
If i use your egl commit and use built-in gememalloc all should work but it will work as is on CM11 with heavy graphic corruption.
Without using built-in gememalloc and your egl commit CM9 runs great with much less corruption than CM11.
We should investigate more on this....something is wrong here with memory allocation.
Click to expand...
Click to collapse
Good observations, thanks. CM11 seems to work exactly the same with or without the gememalloc modules loaded (in the case in which it's not compiled-in). However, I think that the gememalloc is only a wrapper module, and a lot of functions are bypassed in favour of bmem.
I was trying to avoid this, but I think it's best for me to download the ICS source and run a build. Maybe I can get some better ideas on solving these issue with CM11. In the meantime, please let me know if you make any more progress. Thanks.

psyke83 said:
Good observations, thanks. CM11 seems to work exactly the same with or without the gememalloc modules loaded (in the case in which it's not compiled-in). However, I think that the gememalloc is only a wrapper module, and a lot of functions are bypassed in favour of bmem.
I was trying to avoid this, but I think it's best for me to download the ICS source and run a build. Maybe I can get some better ideas on solving these issue with CM11. In the meantime, please let me know if you make any more progress. Thanks.
Click to expand...
Click to collapse
Maybe I'll try something next week. I need to update first some stuff for another device (gt-i9500, samsung finally released 4.4.2 sources for it).
Sent from my GT-I9500 using Tapatalk

Alberto,
I'm up and running with ICS now. Performance is very good and I don't see graphics corruption, but it is unstable. I believe it's the same issue with bmem allocation that the alcatel code fixes.
Anyway, I'm about to test the built-in gememalloc, but something else that you can try is to disable loading of all modules in system/lib/modules with the regular kernel (no gememalloc built-in). I just tried it here on ICS, and I see absolutely no difference in graphics performance with or without the modules loaded. I suspect those modules are used for other things, possibly related to video decoding.

[KERNEL][SOON] HakyKernel 3.1.2

Will be updated soon
Issues:
Settings app: closed automatically when activate Bluetooth.
Kernel information: still appear on 3.0.101, i guess modules of MoshKernel should be updated too.
Android rebooting each 10/15 minutes.
Wifi: not working.
Code:
[*]22/04/2015:
-initial build.
-I will make zImage and use as prebuilt kernel in my roms after add arch-capri drivers.

haky 86 said:
After done some google search about to find similar devices to our phone and some guys on Whatsapp group give me some useful information about Samsung Galaxy S Duos 2 that device share same broadcom chipshet but the kernel is more updated (3.4.5), so I decide to port this version to our phone Samsung Galaxy S2.
I start some tests witnout arch-capri drivers in kernel/samsung/3.4/arch/arm just to see if Android boot or not, the result was really fantastic so from today we can port 3.4 kernel without any problems.
Issues:
Settings app: closed automatically when activate Bluetooth.
Kernel information: still appear on 3.0.101, i guess modules of MoshKernel should be updated too.
Android rebooting each 10/15 minutes.
Wifi: not working.
Code:
[*]22/04/2015:
-initial build.
-I will make zImage and use as prebuilt kernel in my roms after add arch-capri drivers.
Click to expand...
Click to collapse
Okey. Is this for stock or asop based roms?

rs tony said:
Okey. Is this for stock or asop based roms?
Click to expand...
Click to collapse
for both roms :good::good:

thanks @haky 86
I think in future u make this phone work so much better than iphone6
your one of the best developer for this phone

SmzAmir said:
thanks @haky 86
I think in future u make this phone work so much better than iphone6
your one of the best developer for this phone
Click to expand...
Click to collapse
Sure once finish 5.1.1 i can recall other devs to share experience and make 3.4 work perfect:thumbup::thumbup:
Sent from my GT-I9105P using XDA Free mobile app

haky 86 said:
for both roms :good::good:
Click to expand...
Click to collapse
amazing work :good: only a question, i am a newbie on android so what will be the difference betwen them?

cracker12 said:
amazing work :good: only a question, i am a newbie on android so what will be the difference betwen them?
Click to expand...
Click to collapse
the differences are:
-roms will be more stable.
-kernel new and updated instead of old stock and slow 3.0.101.
-antutu test result about 13000 points with some fixes may get better result.
-fast booting.
-this version could be useful for android 6 when will out.

haky 86 said:
the differences are:
-roms will be more stable.
-kernel new and updated instead of old stock and slow 3.0.101.
-antutu test result about 13000 points with some fixes may get better result.
-fast booting.
-this version could be useful for android 6 when will out.
Click to expand...
Click to collapse
Thanks... Keep up

[*]23/04/2015:
-drivers are imported without problem.
-now i'm fix compilation errors to see if will done or not.

Hey u make this
It awesome
---------- Post added at 03:40 AM ---------- Previous post was at 03:37 AM ----------
Hope you will fixed the issues in future
Do it have enhanced gpu

Man, you do a lot of great work.

thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..

left it open haky..maybe they are busy for now..we need it bro

haky 86 said:
thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..
Click to expand...
Click to collapse
sad news!
I was really looking forward if someone can port a new kernel, but as you said it's not an easy job and no devs are intrested

haky 86 said:
thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..
Click to expand...
Click to collapse
So this one is really down? Hey, man, we need you, continue your work

why me? the best succeed I got is integrate part of capri's kernel archecture into 3.4 and entire code should be readpted to work on our phone. in case of even ported, I will not release the source coz I will not do the homeworks of others

3.1.2 Kernel
-update patch like 3.0.31 -> 3.0.32 is adapted as well.
-now im apply the patch to update the code see ya.

3.1.2 in progress
I have a question dear @CoolDevelopment I manage to update the kernel of this phone from 3.0.101 to 3.1.2 using the patch of kernel.org's website.
here my questions:
-if got failed patch, should skip them in case can't found it code?
-I saw there are a lot of detected commit that already patched, should be skipped too and apply only the new code?
-is enough just downloading 3.1.2.patch and use patch -p1 method or should download kernel source too.
https://www.kernel.org/pub/linux/kernel/v3.x/
now I'm compiling a zImage seems no errors for now, if boot I will continue the port :good:
thanks in advance

haky 86 said:
I have a question dear @CoolDevelopment I manage to update the kernel of this phone from 3.0.101 to 3.1.2 using the patch of kernel.org's website.
here my questions:
-if got failed patch, should skip them in case can't found it code?
-I saw there are a lot of detected commit that already patched, should be skipped too and apply only the new code?
-is enough just downloading 3.1.2.patch and use patch -p1 method or should download kernel source too.
https://www.kernel.org/pub/linux/kernel/v3.x/
now I'm compiling a zImage seems no errors for now, if boot I will continue the port :good:
thanks in advance
Click to expand...
Click to collapse
Upload your source man, else noone can help you
I hope you don't have just changed the version numbers...

no i didn't, here my new branch
https://github.com/hak86/android_kernel_samsung_galaxys2plus-common/tree/3.1.2-lp
Compilation is work fine, now i will try to compile with make -j4 bootimage to get the modules and use them on nebula's flashable.

[KERNEL] [MTD] [TW/CM9/CM11] [DEV] Watson Kernel (MTD support on Gingerbread!)

Hello guys,
This is a project I was working on for a kernel for our SGY.
I made it with a few things in mind:
>Improve it's performance
>Be universally compatible (after I nearly given up on trying to get a snappier CM11 and after the need for a snappier SGY, I decided to go back to GB. However, BML is terrible, and it is annoying to come back to. I decided to build a MTD kernel for Gingerbread then, and it works!)
>Experiment and upgrade as much as I can (thanks @robcore!!!!)
But since I lost my device, I cannot continue developing it. I am then releasing the source code (sorry, no flashable stuff, I deleted it long ago ) for any of you to continue(?) my work if your heart so desires.
If I ever get myself another SGY (or another BCM21553 device), I will gladly continue development (and support whoever does it too), but before I lose all my data and the kernel code alongside it, I am making it available.
This kernel features:
-OC up to 1040MHz (It's questionable even today if the bcm21553 OCs really work, but I tried hacking a way that works very similarly to MarocOS's one, maybe even better. Be warned though, the source around it is messy)
-GPU hacks for performance (Again, even I don't know if they do work, probably the values are just there to be seen, I'm not sure. I do know though that increasing the CPU speed will much likely increase the speed of V3D too)
-DVFS disabled (I found out DVFS is mostly the culpirit in the "832MHz crisis" where the kernel would forcefully scale itself to 832MHz, so I eliminated any reference to it in kernel code. Apparently DVFS on the processor is only available under the bcm21553 governor, but it is present on the other drivers as well. The idea for disabling DVFS came from my friend @robcore)
-A few additional governors and a buggy interactive governor (which is the default xd)
-MTD support for Gingerbread (Thanks Samsung Epic 4G! Although it only works on TouchWiz (I tried it with SL v2 and v2.1 and it works, but under NougatME(CM7) I got no success and loads of segfaults), it works ALMOST perfectly. See bugs for details )
-Some scraped source code from Samsung's FSR I found on the internet (barely compilable, though)
Bugs:
>Gingerbread version:
-IMEI won't appear in the Status screen, I also faced problems with non-working radio for calls. Data works just fine, but calling and receiving calls is unavailable. I believe it is EFS-related. My suggestion is backing up the EFS partition's file structure, then converting it to MTD, then restoring the backup.
-TWRP will crash and panic when exiting, a workaround is force rebooting
>ICS version:
-TWRP will crash and panic when exiting (I believe fixing it here will fix the bug above too)
>KitKat version:
-Flashing images fail randomly, you may also be unable to reboot normally if you do so. I tried addressing this but I couldn't get anywhere.
DOWNLOAD THE SOURCE: Here!
Thanks to:
 @robcore - his development on the Snapdragon S4 breathes life on my dev soul!
 @zman0900 - I saw his thread on an MTD TW kernel for the Samsung Epic 4G, which led me to believe MTD on GB is possible.

nice kernel
It sound nice. I'm a newbie developer, I'm building a kernel to fix audio bug on cm9, hope it work. And thank you for the source

vdhero said:
It sound nice. I'm a newbie developer, I'm building a kernel to fix audio bug on cm9, hope it work. And thank you for the source
Click to expand...
Click to collapse
Have you gathered enough info on it? I would like to fix it too, but I couldn't get any info on whether if the audio bug is a kernel-side issue or an OS -side issue.
Best of luck for you

Building and fixing
sonickles9 said:
Have you gathered enough info on it? I would like to fix it too, but I couldn't get any info on whether if the audio bug is a kernel-side issue or an OS -side issue.
Best of luck for you
Click to expand...
Click to collapse
I don't sure so I decided to build a kernel from your source and another cm9 version from Mohamad.Afaneh's source and I'll merge the audio on both of them for the best think to fix the bug.Thank you .

Link for kernel?
(img files...)(stock/cm9/cm11)

TheRealModder said:
Link for kernel?
(img files...)(stock/cm9/cm11)
Click to expand...
Click to collapse
Compile one for yourself,man. It only takes like 15-25 mins

vdhero said:
Compile one for yourself,man. It only takes like 15-25 mins
Click to expand...
Click to collapse
I don't know how to compile....

TheRealModder said:
I don't know how to compile....
Click to expand...
Click to collapse
He wrote a script already, just add your toolchain and run the script. There's a guide in the readme

vdhero said:
He wrote a script already, just add your toolchain and run the script. There's a guide in the readme
Click to expand...
Click to collapse
Ok. The watson-kernel-bcm21553-src is used with other files?
Because i want to make cm9 mohhamad afaneh optimized version

TheRealModder said:
Ok. The watson-kernel-bcm21553-src is used with other files?
Because i want to make cm9 mohhamad afaneh optimized version
Click to expand...
Click to collapse
To make it, you have to sync the cm9 source code then add the files from his github to your localmanifest. This thing is not in anyway related to that except the MTD. This one is a kernel-compile only source

Oh man, i give up. I can't build a kernel from source, but i can modify a kernel.
Can someone give me the zimage for ics Please....
Sent from my Zenfone 2 Laser using XDA Labs

TheRealModder said:
Oh man, i give up. I can't build a kernel from source, but i can modify a kernel.
Can someone give me the zimage for ics Please....
Click to expand...
Click to collapse
zlimage? We don't have that here, we only have boot.img for kernel

vdhero said:
zlimage? We don't have that here, we only have boot.img for kernel
Click to expand...
Click to collapse
Or you can give me the extracted boot.img files. (ICS/KK)
I will rebuild it using dsixda's android kitchen.
Sent from my Zenfone 2 Laser using XDA Labs

TheRealModder said:
Or you can give me the extracted boot.img files. (ICS/KK)
I will rebuild it using dsixda's android kitchen.
Sent from my Zenfone 2 Laser using XDA Labs
Click to expand...
Click to collapse
Sorry but I can't because I'm bored of making ROMs so I switched back to Windows. I'm planning on making a ROM, I'll compile the kernel for you once I get linux installed

vdhero said:
Sorry but I can't because I'm bored of making ROMs so I switched back to Windows. I'm planning on making a ROM, I'll compile the kernel for you once I get linux installed
Click to expand...
Click to collapse
Ok. If you want to install linux i recommend using ubuntu or linux mint.
Ubuntu official website:https://www.ubuntu.com/
Linux mint official website:https://linuxmint.com/
Sent from my Zenfone 2 Laser using XDA Labs

VDHERO Please But a New Galaxy t Gt-S5360 and start the Development!
vdhero said:
To make it, you have to sync the cm9 source code then add the files from his github to your localmanifest. This thing is not in anyway related to that except the MTD. This one is a kernel-compile only source
Click to expand...
Click to collapse
VDHERO Please But a New Galaxy t Gt-S5360 and start the Development!

Assabtigle said:
VDHERO Please But a New Galaxy t Gt-S5360 and start the Development!
Click to expand...
Click to collapse
Sorry but I can't since my sgy is dead for a long time ago. I'll try to make one if I can find one. I've heard that there are some places that sell sgy for about 5 bucks, i'll find one ì possible

Be fast bro!!
vdhero said:
Sorry but I can't since my sgy is dead for a long time ago. I'll try to make one if I can find one. I've heard that there are some places that sell sgy for about 5 bucks, i'll find one ì possible
Click to expand...
Click to collapse
BE fast BRO Love U and Your WORK!!
All Your DEVELOPMENT are Faster than The ORIGINAL one Please Buy a NEW one!
and Yeah install the Stock Rom in your Phone by ODIN it will be fine!:laugh:

[KERNEL][HAVOC-OS-2.2 - 2.4]Coconut Kernel with Nethunter Support[HolyDragon Source]

Coconut Kernel for HAVOC OS - With Nethunter Support
Code:
***I'm not responsible for any problems that might occur flashing this kernel or what you do with the kernel support***
This kernel is tested on HAVOC OS 2.2 - 2.4 PIE. This is built from HolyDragon Source with added nethunter support/USB Wifi Adapter Drivers and monitor mode/packet injection
The kernel should also work on every ROM that Holydragon kernel supports.
Requirements
Oxygen OS 5.0.8 firmware is required. The wifi adapter wont work on older firmwares. Those who are using Havoc OS would most probably be on 5.0.8 firmware so this is just a remainder for others and/or anyone who have trouble making this work.
How to install
Make sure that you are rooted with magisk/supersu/any superuser
Download kernel from attachment and flash in TWRP Recovery
Reboot and download any terminal app like Termux
Plugin the USB Wifi card and open Termux
Type the command su
Then type ifconfig wlan1 up
This is how you can test whether it works or not
The kernel works fine with Nethunter as well as other chroot applications like Linux Deploy.
Note:- This kernel does not need any module to be inserted as all wifi drivers are compiled inline. So no need to insmod/modprobe
Credits
@HolyAngel for HolyDragon Kernel Source
Source
https://gitlab.com/HolyAngel/OP3

Thanks sir, this weekend, I test and i say you if I have a problem, but surely not, at this moment it is the kernel that I have but without the controller. I want to learn to compile the kernel on my own so that, in case HolyAngel updates the kernel, it dosn't depend on your work.

Victroid said:
Thanks sir, this weekend, I test and i say you if I have a problem, but surely not, at this moment it is the kernel that I have but without the controller. I want to learn to compile the kernel on my own so that, in case HolyAngel updates the kernel, it dosn't depend on your work.
Click to expand...
Click to collapse
https://forum.xda-developers.com/an...erence-how-to-compile-android-kernel-t3627297
Follow the tutorial above for kernel building.

@fredrickz
Any future build for stock oos pie like your Oreo one, it was perfect man thank you for your efforts regard to the community.?

DoN LoUhI said:
@fredrickz
Any future build for stock oos pie like your Oreo one, it was perfect man thank you for your efforts regard to the community.
Click to expand...
Click to collapse
Stock oos pie source isn't available yet man. I can build pie version from holydragon sources. I'll compile one when stock sources arw available too.

fredrickz said:
Stock oos pie source isn't available yet man. I can build pie version from holydragon sources. I'll compile one when stock sources arw available too.
Click to expand...
Click to collapse
Fair enough, thank YOU:laugh::good:

You explicitly mention this:
This is built from HolyDragon Source with added nethunter support/USB Wifi Adapter Drivers and monitor mode/packet injection
Click to expand...
Click to collapse
And the kernel source points to:
https://gitlab.com/HolyAngel/OP3
Click to expand...
Click to collapse
This can only mean 2 things:
1) you've merely taken holydragon kernel source and renamed it as your own or
2) you're actually breaking the GPL here by not releasing your changes
So which one is it?
And this leaves me no doubt that the second is very likely the case:
Note:- This kernel does not need any module to be inserted as all wifi drivers are compiled inline. So no need to insmod/modprobe
Click to expand...
Click to collapse

@Fredricks
It would be more than appreciated if you could add support for HID brother. Thanks:crying:

anupritaisno1 said:
You explicitly mention this:
And the kernel source points to:
This can only mean 2 things:
1) you've merely taken holydragon kernel source and renamed it as your own or
2) you're actually breaking the GPL here by not releasing your changes
So which one is it?
And this leaves me no doubt that the second is very likely the case:
Click to expand...
Click to collapse
I dont want to break any gpl.. the thing is that all my changes are local. Im not used to github. This kernel and all others i posted werr just for my own use. I have been using @ZaneZam kernel for oneplus3. But the Oreo kernel wasnt working fine. Thats the reason i tried to compile one my own. I shared it with a friend of mine some time ago and he insisted that i should post it so that others may also benefit. The kernel i posted doesn't have tonnes of feature list because i mostly stick to stock. I just added the wifi drivers and was using them. My friend asked me to add support for DriveDroid and i just did that. I don't know much about git and didnt have time to learn.
If this is against the rules then maybe ill post the source later. Im currently out of town.
for now if you want to know what changes i did,
1. Prepare the kernel for standalone build (except holydragon kernel)
2. Added just the wifi drivers mentioned in the nethunter wiki. I didnt add support for usb Bluetooth or sdr.
3. Added support for DriveDroid from official post in xda making changes to adapt the code to 3.18 kernel.
4. Added a fancy name to the kernel.
5. Published it.

DoN LoUhI said:
@Fredricks
It would be more than appreciated if you could add support for HID brother. Thanks:crying:
Click to expand...
Click to collapse
Im out of town bro. Ill add it when i reach home.

fredrickz said:
Im out of town bro. Ill add it when i reach home.
Click to expand...
Click to collapse
Very thankful, have a good time..:good: