Related
Okay, I managed to fix the sources and got it compiled.
This is based on 4.06/4.08 sources with 4.08 ramdisk.
Use it at your own risk. If you brick your phone, it will be your fault, not mine.
I do not own a Dell Venue and therefore cannot test this.
zImage :
fastboot flash zimage zImage
fastboot reboot
boot.img :
fastboot flash boot boot.img
fastboot reboot
Download :
dell-venue-dbg1.zip
dell-venue-dbg2.zip
dell-venue-dbg3.zip
WiFi module :
dhd.ko-dbg1.zip
Thanks.
Yes, we would.
Cool, right now I have a hard time finding the right defconfig.
In case someone could point me to the right file :
https://github.com/adridu59/dell-venue-kernel/tree/master/arch/arm/configs
Edit :
It seems to be codenamed "toucan".
adridu59 said:
Cool, right now I have a hard time finding the right defconfig.
In case someone could point me to the right file :
https://github.com/adridu59/dell-venue-kernel/tree/master/arch/arm/configs
Edit :
It seems to be codenamed "toucan".
Click to expand...
Click to collapse
I think you'll try all of them, then test on your real device and.....
)
nguyen_vh said:
I think you'll try all of them, then test on your real device and.....
)
Click to expand...
Click to collapse
I made an overlap comparaison and I think that this is it.
Right now I am fixing the sources, they are crap tbh.
adridu59 said:
i made an overlap comparaison and i think that this is it.
Right now i am fixing the sources, they are crap tbh.
Click to expand...
Click to collapse
thanks for your effort :d
Yes
Venue have Custom Kernel! I have one
Kinda busy right now working on my own device but you can contribute if ya want. github.com/adridu59
I'm excited about this topic! Please keep me up to date with this. BTW, I also think that v4.06 source from Dell OpenSource is crappy. Could you please public your change list after you complete the work, it's very helpful to us.
chacona said:
I'm excited about this topic! Please keep me up to date with this. BTW, I also think that v4.06 source from Dell OpenSource is crappy. Could you please public your change list after you complete the work, it's very helpful to us.
Click to expand...
Click to collapse
Well check my github, I haven't worked on this for a while but I'm not letting it down.
First build on first post, follow instructions. Thanks.
406 and 408 apparently use the same kernel according to dell. Though we've had the suspicion that there were differences, apparently there isnt.
TheManii said:
406 and 408 apparently use the same kernel according to dell. Though we've had the suspicion that there were differences, apparently there isnt.
Click to expand...
Click to collapse
Yes, that's what I was thinking. And otherwise they would've published the sources.
I tried to flash your zImage, what I received is "Flashing Error -2", in red background in fast boot mode.
BTW, I would like to ask the way you build the kernel. Did you build directly from /kernel folder (with .config), or you build from ROM's source tree (/kernel folder's parent, using "build/envsetup", then "choosecombo")? I would like to get my hands dirty with this work too!
If my dev pc wasnt broken at the moment, I could glue it together with the stock ramdisk and make a flashable zip.
Here's the stock 408 kernel: boot-408.img
You can glue it together with that ram disk if desired, but shouldnt it also generate a ramdisk when building the kernel?
Just as much the ramdisk's contents arnt that unusual, you could prob guess at a few things and reconstruct it without issue.
chacona said:
I tried to flash your zImage, what I received is "Flashing Error -2", in red background in fast boot mode.
BTW, I would like to ask the way you build the kernel. Did you build directly from /kernel folder (with .config), or you build from ROM's source tree (/kernel folder's parent, using "build/envsetup", then "choosecombo")? I would like to get my hands dirty with this work too!
Click to expand...
Click to collapse
Thanks for testing.
I just use the corresponding defconfig, that is the usual way to do it.
I don't really see what you mean by ROM source tree...
TheManii said:
If my dev pc wasnt broken at the moment, I could glue it together with the stock ramdisk and make a flashable zip.
Here's the stock 408 kernel: boot-408.img
You can glue it together with that ram disk if desired, but shouldnt it also generate a ramdisk when building the kernel?
Just as much the ramdisk's contents arnt that unusual, you could prob guess at a few things and reconstruct it without issue.
Click to expand...
Click to collapse
Nao, the ramdisk isn't compiled code. Usually you extract it from the stock kernel and build with mkbootimg or any similar tool.
Thanks for the link BTW.
Okay, I built the boot.img. Offset is 0x20000000.
Check first post, thanks.
adridu59 said:
Thanks for testing.
I just use the corresponding defconfig, that is the usual way to do it.
I don't really see what you mean by ROM source tree...
Thanks for the link BTW.
Click to expand...
Click to collapse
Sorry for not making it clear. By saying "from ROM source tree", I mean the way below (ftp.dell.com/opensource/venue/v4.06/Venue-HOW-TO-BUILD.txt)
Code:
kernel
1) download source tree of android froyo from Qualcomm.
2) replace kernel
3) build kernel by
. build/envsetup.sh
choosecombo
...
5) make -j4 kernel
# update on 4/27/2012 - 23:18 GMT+7
I built an update.zip, with all the files including boot.img and system/lib/modules. What I got is, the Dell logo is hung there like being fallen into an infinite loop.
chacona said:
Sorry for not making it clear. By saying "from ROM source tree", I mean the way below (ftp.dell.com/opensource/venue/v4.06/Venue-HOW-TO-BUILD.txt)
Code:
kernel
1) download source tree of android froyo from Qualcomm.
2) replace kernel
3) build kernel by
. build/envsetup.sh
choosecombo
...
5) make -j4 kernel
Click to expand...
Click to collapse
First time I see this kind of instructions.
Code:
export ARCH=arm
export CROSS_COMPILE=~/toolchains/arm-eabi-4.4.3/prebuilt/linux-x86/bin/arm-eabi-
make toucan-perf_defconfig
make
chacona said:
# update on 4/27/2012 - 23:18 GMT+7
I built an update.zip, with all the files including boot.img and system/lib/modules. What I got is, the Dell logo is hung there like being fallen into an infinite loop.
Click to expand...
Click to collapse
Would you try again using fastboot please ? thanks.
@Adridu59: still fail, flashing boot.img using fastboot gives the same result as I described above. I will try to get your config files and build a copy myself to see what's going on!
Hello,
This is a stock SeLinux permissive kernel and init.d activated for Samsung Galaxy Note Edge (N915F) for Lollipop 5.0.1.
There are inputs that is working also on N915FY.
The kernel was compiled from Samsung source LL_CIS kernel using Google toolcahin v4.8.
If you want to test it, please flash in cwm the attached file and report back. Please make a backup of your actual kernel (boot.img) befor flashing this one.
Special thanks to @Micky387 who advised me to update the source kernel (MH driverI), @Wuby986 for his support and guidance and @daxgirl for his advices.
My kernel source for N915F (N915FOXE1BOC6) is here.
Happy flashing.
PS. Kernel updated. Same functionality but some different info in "About".
Well you got further than I did .. Kept getting some driver file referenced so it would not complied.. Thanks for effort I hope you work it out soon.. Unfortunately I don't have time at the moment ..
starbucks2010 said:
Hello,
Since few days I struggle to build a SeLinux permissive kernel for Samsung Galaxy Note Edge with Lollipop 5.0.1 but without success. Or with partial success.
I followed several guides from xda and other sites but it seems that everyone has his different way of doing it.
What I have done so far:
- I installed Ubuntu 14.04 with all updates and apt-get xxx
- I installed the Google toolchain arm-eabi-4.8
- I Installed Samsung kernel source for N915F_CIS from here
- I changed the path to the toolchain in Makefile and build_kernel.sh
- I run from kernel source folder: ./build_kernel.sh
- After 10-15 min of compilation I get a zImage file in //output/arch/arm/boot of ~ 9.8 Mb
- Using Android Image Kitchen v2.2 I integrated the zImage into a boot.img to be flashed with cwm
I flashed this new boot.img but the phone is rebooting every minute and in about I have "unknown"as baseband.
Anyone have an idea how to fix this?
Thank you in advance.
Click to expand...
Click to collapse
hi man. How are you ?
So many thing are change in lollipop . the modem and firmware modem dont call same as KK ROM.
So be sure you are this commit https://github.com/CyanogenMod/andr...mmit/784aa9a84b77090fa591bff77045341c3e3c6293
and add MHI module into tblte_defconfig
https://github.com/CyanogenMod/andr...mmit/1dd44659ee26c2d8b313c1346192e2bfa2ac7bb9
dont delete 18 and 19 line if you build for TW rom .
Try and report
micky387 said:
hi man. How are you ?
So many thing are change in lollipop . the modem and firmware modem dont call same as KK ROM.
So be sure you are this commit https://github.com/CyanogenMod/andr...mmit/784aa9a84b77090fa591bff77045341c3e3c6293
and add MHI module into tblte_defconfig
https://github.com/CyanogenMod/andr...mmit/1dd44659ee26c2d8b313c1346192e2bfa2ac7bb9
dont delete 18 and 19 line if you build for TW rom .
Try and report
Click to expand...
Click to collapse
Bonjour Mickey,
Thank you for your advice. I'll try it and let you know how it goes. Do you know if I have to flash also the modules together with the new kernel or only the boot.img alone ?
Merci.
starbucks2010 said:
Bonjour Mickey,
Thank you for your advice. I'll try it and let you know how it goes. Do you know if I have to flash also the modules together with the new kernel or only the boot.img alone ?
Merci.
Click to expand...
Click to collapse
No need to flash module. The MHI module will be in the kernel so you have boot.img with all inside.
starbucks2010 said:
Hello,
Since few days I struggle to build a SeLinux permissive kernel for Samsung Galaxy Note Edge with Lollipop 5.0.1 but without success. Or with partial success.
I followed several guides from xda and other sites but it seems that everyone has his different way of doing it.
What I have done so far:
- I installed Ubuntu 14.04 with all updates and apt-get xxx
- I installed the Google toolchain arm-eabi-4.8
- I Installed Samsung kernel source for N915F_CIS from here
- I changed the path to the toolchain in Makefile and build_kernel.sh
- I run from kernel source folder: ./build_kernel.sh
- After 10-15 min of compilation I get a zImage file in //output/arch/arm/boot of ~ 9.8 Mb
- Using Android Image Kitchen v2.2 I integrated the zImage into a boot.img to be flashed with cwm
I flashed this new boot.img but the phone is rebooting every minute and in about I have "unknown"as baseband.
Anyone have an idea how to fix this?
Thank you in advance.
Click to expand...
Click to collapse
Wait one more day..
Or maybe earlier
Finally done.
Make backup of your actual kernel, flash the attached zip from post 1in cwm and please report back.I didn't check the init.d support but it should work.
Good, I'll try.
Dev.
Just a small request please.
If you could please make sure a link to YOUR kernel sources in OP.
Any Linux kernel publicly released must have source to compile the exact binary (zImage) as repacked into your distributed boot.img. This must be current at time of every released version.
This is not just a XDA rule, but a legal GPL requirement, applying to all, even if modification is only minor. This is open-source
I would suggest the use of a github repo that helps keep track of your changes (commits), promotes open transparency, sharing and colaboration
If you have any questions on how to go about this, i would be happy to help via pm (but currently away with work), but would suggest to contact our friendly forum Mod.
Best of luck with your project. :thumbup:
Cheers.
UITA
Any chance that you would be willing to make this kernel compatible with the Sprint variety? Man.... I need my viper4android bro. Please. Lol
UpInTheAir said:
Dev.
Just a small request please.
If you could please make sure a link to YOUR kernel sources in OP.
Any Linux kernel publicly released must have source to compile the exact binary (zImage) as repacked into your distributed boot.img. This must be current at time of every released version.
This is not just a XDA rule, but a legal GPL requirement, applying to all, even if modification is only minor. This is open-source
I would suggest the use of a github repo that helps keep track of your changes (commits), promotes open transparency, sharing and colaboration
If you have any questions on how to go about this, i would be happy to help via pm (but currently away with work), but would suggest to contact our friendly forum Mod.
Best of luck with your project. :thumbup:
Cheers.
UITA
Click to expand...
Click to collapse
Thank you for your advices.The link to Samsung kernel source was already there . Anyway, I added it one more time just to be sure that is more visible.
For the github repo, I have to create an account and then I'll upload the files.
Best regards.
Well done mate ..... Yea
---------- Post added at 08:32 AM ---------- Previous post was at 07:36 AM ----------
Boot and works fine , nice one
Can this be used on N915FY as well?
I don't have any reports from N915FY users. You can try and tell us
Don't forget to make a backup first.
starbucks2010 said:
Thank you for your advices.The link to Samsung kernel source was already there . Anyway, I added it one more time just to be sure that is more visible.
For the github repo, I have to create an account and then I'll upload the files.
Best regards.
Click to expand...
Click to collapse
Hey, no problem.
Just to clarify....
If you've made any (even minor) change to "Samsung" source, then you have to upload "your" complete source and link "your" source, not "Samsung" So if you've made the kernel permissive or even use a different toolchain or path, technically you have modified from original and is now "your" source If you use a custom defconfig, don't forget it too
github is well worth the pain I Google for answers all the time (how to do this and that), but still screw things up (sometimes majorly) now and then.
dubart said:
Can this be used on N915FY as well?
Click to expand...
Click to collapse
Using this kernel with a N915FY. Great job btw I can finally use viper audio which I've missed so much. Major props dude!
I'm gonna flash this on sprint variant either that or throw this device out my window
dinaps86 said:
I'm gonna flash this on sprint variant either that or throw this device out my window
Click to expand...
Click to collapse
Lol it booted just no data. Yaaayyy!!!
I see that there are other people who are interested in Selinux permissive kernels.
So, if you want, I can add selinux permissive to any samsung kernel as long as you provide me 2 files: your original kernel (boot.img) from the ROM you want to flash and the Kernel.tar.gz - source kernel from Samsung site. In order to get Kernel.tar.gz file you'll need to download the kernel source file (~ 1Gb) from Samsung site, open the archive and upload ONLY the Kernel.tar.gz (~ 100-150 Mb) and the readme file from the archive to some sharing site. Then, I'll try to compile that kernel for you.
There are also downsides. I cannot stay up to date will all new commits done to the kernel source so I'll compile your kernels only with info that I have at that date. If you fork the github and find kernel source updates, I can add them.
PS. I only set up a working PC with Ubuntu and Google toolchain v4.8. If you find any information that this setup is not suitable for compiling your kernel, then there is no point of providing me the above files.
Best regards.
OP updated with some Antutu screen shots.
Hi,
I would like to request some testers who are currently running stock MIUI to test the stock kernel. Feel free to comment below.
Instructions:
- You should be on CWM
- Download zip
- Flash kernel
- reboot
- cross your fingers
What to check:
- WLAN -> see if it works
Source:
https://github.com/emceethemouth/kernel_cancro/tree/mi-stock
WLAN:
git://codeaurora.org/platform/vendor/qcom-opensource/wlan/prima/
blah blah blah
Wifi not working after flashing the kernel.
Armin_van_buuren said:
Wifi not working after flashing the kernel.
Click to expand...
Click to collapse
Hold on I'm uploading a new one.
Edit:
Attachment updated
Wifi doesn't work, everything else does.
alphoz said:
Wifi doesn't work, everything else does.
Click to expand...
Click to collapse
Ok thanks, seems MIUI still has no proper fix for it. Anyways will keep this thread posted for any updates. Thanks!
Gnome said:
Ok thanks, seems MIUI still has no proper fix for it. Anyways will keep this thread posted for any updates. Thanks!
Click to expand...
Click to collapse
Thanks to you, and all your hard work. I would also like to mention that the miband unlocking worked a lot better with your kernel than the MIUI stock one. Thanks again.
Wow. Thanks GNOME... Good to kernel for miui
Sent from my MI 3W using Tapatalk
Audahudi also build stock miui kernel. This also has same bugs, no WiFi, cit etc menu take while to open.
One bug I have doubt of is, whether all 4 cores work simultaneously. In my testing I saw most time 2 work, sometimes 3. Benchmarks also give scores like that. Also CPU performance control pro, which can set individual frequency of all cores could make 2 cores work together.
Any app you know which can monitor every core usage over period of time?
The 2nd bug is what I'm curious off, as I don't have WiFi lol.
Plus these miui kernel can be used in some custom Chinese KitKat ROMs. Iuni is 1 example, fiui I havent tested.
Gnome said:
Ok thanks, seems MIUI still has no proper fix for it. Anyways will keep this thread posted for any updates. Thanks!
Click to expand...
Click to collapse
Thanks for your hard work. But did you read this? https://github.com/MiCode/Xiaomi_Kernel_OpenSource/wiki/How-To-Use
I tried to compile kernel according to this instructions. Compilation through without problems. But kernel freeze while booting. I am not kernel developer, so don't have experience, how to debug it. If you find time, please can you try it?
Thanks
Pepe.II said:
Thanks for your hard work. But did you read this? https://github.com/MiCode/Xiaomi_Kernel_OpenSource/wiki/How-To-Use
I tried to compile kernel according to this instructions. Compilation through without problems. But kernel freeze while booting. I am not kernel developer, so don't have experience, how to debug it. If you find time, please can you try it?
Thanks
Click to expand...
Click to collapse
That happened to me when I did all that.
I found no solution, so I left it.
@Pepe.II you should see the issues section, I'm always there.
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/issues/16
@Gnome
on what miui we should try stable or developer ?
Stable just to be safe.
Edit: @alexret, can you try the instructions on that misleading turorial but use my kernel source? Branch is mi-stable. I have a feeling it'll work
@Gnome anything with the bug I have doubt of?
@Gnome I tried to flash your kernel STX-MI-PRIMA-TEST-2015-06-24 from first post attachment.
Its only kernel, no modules included. This has a effect, that no modules are loaded while booting. When i try load module manually, it crashes with this message:
[email protected]:/ # insmod /system/lib/modules/wlan.ko
insmod: init_module '/system/lib/modules/wlan.ko' failed (Exec format error)
Please, can you compile kernel with modules? Thanks
@Me_Ashish_ its MIUIs kernel source, its incomplete it needs a lot of patches. And yes this kernel is just stock MIUI I added nothing to it just the opensource wlan from qualcomm w/c they claim works.
@Pepe.II thats the idea, the kernel should have it by default already, no need for the modules to be included in the package. The Modules are being built with the zImage-dtb itself, adding those modules to rhe zip package is very wrong. Adding it to the kernel package for CM Bases ROMs are just a work around, and I tell you know it wont work on stock MIUI ROM, unless you build MIUI from source and use my kernel source to be built with it.
Gnome said:
@Me_Ashish_ its MIUIs kernel source, its incomplete it needs a lot of patches. And yes this kernel is just stock MIUI I added nothing to it just the opensource wlan from qualcomm w/c they claim works.
@Pepe.II thats the idea, the kernel should have it by default already, no need for the modules to be included in the package. The Modules are being built with the zImage-dtb itself, adding those modules to rhe zip package is very wrong. Adding it to the kernel package for CM Bases ROMs are just a work around, and I tell you know it wont work on stock MIUI ROM, unless you build MIUI from source and use my kernel source to be built with it.
Click to expand...
Click to collapse
As far as I understand it, you did not compile drivers as modules but compile them as part of the kernel?. Ok. But why, when I look in to kmesg log (/proc/kmesg), I find not a single mention about the WLAN. That's weird. Are you sure, that WLAN part is compiled correctly?
@Pepe.II if Im building kernels wrong, by all means please guide me on how to build kernels correctly.
Well if I'm getting this kind of critisczm might as well stop this. Anyways thanks for all that tested, I'm dropping this.
Gnome said:
@Pepe.II if Im building kernels wrong, by all means please guide me on how to build kernels correctly.
Well if I'm getting this kind of critisczm might as well stop this. Anyways thanks for all that tested, I'm dropping this.
Click to expand...
Click to collapse
Sorry, I only asking, because I do not understand how you work with drivers. Prima WLAN you set as a module but I do not see any module in a flashable zip. You assume that your kernel will use modules from stock MIUI kernel?
I do not criticize, just asking. if this sounds like criticism, so it is due to my poor English and i am sorry.
Installing and running Kernel DorimanX V10.43 v100 works fine.
The problem is, that I have to compile it myself,
because I need additional kernel features.
Compiling works, but the kernel does not boot.
I had a bootloop and had to flash the pre-built v100 kernel
again to stop the bootloop.
The ROM is Cyanogenmod 11 / KitKat.
How to build a bootable DorimanX V10 kernel?
I used the official git repository from DorimanX.
G. J. Wucherpfennig said:
Installing and running Kernel DorimanX V10.43 v100 works fine.
The problem is, that I have to compile it myself,
because I need additional kernel features.
Compiling works, but the kernel does not boot.
I had a bootloop and had to flash the pre-built v100 kernel
again to stop the bootloop.
The ROM is Cyanogenmod 11 / KitKat.
How to build a bootable DorimanX V10 kernel?
I used the official git repository from DorimanX.
Click to expand...
Click to collapse
Hi fellow kernel builder,
did you follow the guide properly given in the repo?
What is your build environment?
Did you clone the right repos (it's best to start with cybernetus' repo or mine)?
Did you change anything prior to building the kernel?
gsstudios
gsstudios said:
Hi fellow kernel builder,
did you follow the guide properly given in the repo?
What is your build environment?
Did you clone the right repos (it's best to start with cybernetus' repo or mine)?
Did you change anything prior to building the kernel?
gsstudios
Click to expand...
Click to collapse
The build-system is Arch Linux, with make 4.1 replaced by make 3.x
I renamed /usr/bin/python, because it is a link to python3 and
created a link to python2.
The repository is:
https://github.com/dorimanx/Dorimanx-SG2-I9100-Kernel.git
I used the default branch "master-maliv3"
By the way, the updater script in:
Dorimanx-SG2-I9100-Kernel/READY-JB/META-INF/com/google/android/updater-script
has two incorrect lines:
set_perm(0, 0, 0755, "/system/bin/tune2fs.static");
set_perm(0, 0, 06755, "/system/xbin/su");
The tune2fs.static does not exist on my phone (because of the suffix ".static").
and su has wrong file permissions: it has to be 6755 instead of 06755.
The initramfs diretory is smaller than 14MB.
I tested both:
https://github.com/dorimanx/initramfs3.git
and
https://github.com/Lanchon/IsoRec-Dorimanx-initramfs3.git
Compiling worked fine, but
I could never produce a bootable zImage.
I used the compiler that is bundled with:
https://github.com/dorimanx/Dorimanx-SG2-I9100-Kernel.git
in
Dorimanx-SG2-I9100-Kernel/android-toolchain
Now I used the exact commands of build_kernel.sh and
flashed the kernel and now the system freezes
while showing the Galaxy SII logo. Even no reboot!
No download mode via Vol-up + Home + Power possible.
The device is soft-bricked. But download mode via
unbrick-dongle is still possible
I reflashed the prebuilt DorimanX kernel (the zImage).
Can you help be to compile a bootable DorimanX v10
kernel for my Galaxy S2 i9100 / CyanogenMod 11 KitKat smartphone?
@G. J. Wucherpfennig
I have no experience with arch Linux, because I only use Ubuntu to build the kernel. However it may be as simple as changing the file permissions of kernel files to fix this issue.
I do recommend trying a different distro like bbqlinux or Ubuntu and see if you can produce a working kernel zip.
gsstudios
gsstudios said:
@G. J. Wucherpfennig
I have no experience with arch Linux, because I only use Ubuntu to build the kernel. However it may be as simple as changing the file permissions of kernel files to fix this issue.
I do recommend trying a different distro like bbqlinux or Ubuntu and see if you can produce a working kernel zip.
gsstudios
Click to expand...
Click to collapse
BBQLinux is based on Arch Linux.
G. J. Wucherpfennig said:
BBQLinux is based on Arch Linux.
Click to expand...
Click to collapse
Whoops, what I meant was Ubuntu (forgot )
gsstudios said:
Whoops, what I meant was Ubuntu (forgot )
Click to expand...
Click to collapse
I was able to compile the full CyanogenMod 11 repository with the integrated Kernel.
I flashed it and it works!
I suppose that the integrated android-toolchain of the
DorimanX kernel repository does not work with my Arch Linux.
I will try to follow:
http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building
Maybe I can compile DorimanX with the build environment
provided by CyanogenMod 11.
gsstudios said:
Hi fellow kernel builder,
did you follow the guide properly given in the repo?
What is your build environment?
Did you clone the right repos (it's best to start with cybernetus' repo or mine)?
Did you change anything prior to building the kernel?
gsstudios
Click to expand...
Click to collapse
Where is your repository and cybernetus one ?
Are they compatible to CyanogenMod 11 ?
Are they better than the kernel from
the repository of DorimanX ?
Programming
G. J. Wucherpfennig said:
Where is your repository and cybernetus one ?
Are they compatible to CyanogenMod 11 ?
Are they better than the kernel from
the repository of DorimanX ?
Click to expand...
Click to collapse
github.com/gsstudios
github.com/ataliba
Both are compatible with cm11. My repo has newer commits and changes. But you will need to change the branch to master-maliv3 and master for kernel and initramfs respectively.
gsstudios
gsstudios said:
Programming
github.com/gsstudios
github.com/ataliba
Both are compatible with cm11. My repo has newer commits and changes. But you will need to change the branch to master-maliv3 and master for kernel and initramfs respectively.
gsstudios
Click to expand...
Click to collapse
I compiled a kernel from your kernel repository sources.
I didn't use ccache so I had to edit the top-level Makefile
and delete "ccache" before gcc and g++.
Everything worked fine, but the kernel still doesn't boot.
Again a bootloop.
It surprises me that CyanogenMod 11 with the default
smdk4212 kernel compiled fine on my Arch Linux system.
I hestiate to witch to Ubuntu, because Arch Linux is a
much better operating system. I even tried to compile
the custom kernel with the prebuilt compiler from
CyanogenMod, it still results in a non-bootable kernel.
gsstudios said:
Whoops, what I meant was Ubuntu (forgot )
Click to expand...
Click to collapse
I have built your kernel in BBQ Linux and in Ubuntu 14.04 (in Virtualbox) with the same result.
An unbootable kernel and a bootloop. I really do not know what to do next.
Please help.
G. J. Wucherpfennig said:
I have built your kernel in BBQ Linux and in Ubuntu 14.04 (in Virtualbox) with the same result.
An unbootable kernel and a bootloop. I really do not know what to do next.
Please help.
Click to expand...
Click to collapse
That's weird, if you've followed everything exactly in the guide, it should build a working kernel. Are you sure there are no errors during compilation? Something sounds not right about how you are building it. I would start by going through the guide again. You may have missed something.
gsstudios
gsstudios said:
Whoops, what I meant was Ubuntu (forgot )
Click to expand...
Click to collapse
Now it works!
I had to do "sudo" for build_kernel.sh
(root privileges)
Please change the README file.
Installing ia32-libs is not possible any more
since Ubuntu 14.04. Please instead add
"lib32z1 lib32ncurses5 lib32bz2-1.0 make"
to the apt-get install directive!
Please change build_kernel.sh
"chmod -R 777 /tmp" is not acceptable
on a production operating system.
gsstudios said:
Programming
github.com/gsstudios
github.com/ataliba
Both are compatible with cm11. My repo has newer commits and changes. But you will need to change the branch to master-maliv3 and master for kernel and initramfs respectively.
gsstudios
Click to expand...
Click to collapse
Your DorimanX v10 kernel does not seem to be very stabil.
My smartphone switched off over night.
Please give me instructions about how to check this.
Are there any log files with information about this issue?
G. J. Wucherpfennig said:
Your DorimanX v10 kernel does not seem to be very stabil.
My smartphone switched off over night.
Please give me instructions about how to check this.
Are there any log files with information about this issue?
Click to expand...
Click to collapse
Which kernel are you using? Compiled by gsstudios or yourself?
I used and tested the latest V10.50v005 extensively and found it to be very stable. Also a couple of V10.45's were very stable as well
G. J. Wucherpfennig said:
Your DorimanX v10 kernel does not seem to be very stabil.
My smartphone switched off over night.
Please give me instructions about how to check this.
Are there any log files with information about this issue?
Click to expand...
Click to collapse
Are you sure? I'm running it here right now on my phone and it is stable.
Please check again.
Ensure you have reset your profiles and make sure you have wiped cache.
Log files that may help you include the kmsg, dmesg. Logcat may help as well, but mostly to diagnose issues with cortexbrain and app related issues.
gsstudios
gsstudios said:
Are you sure? I'm running it here right now on my phone and it is stable.
Please check again.
Ensure you have reset your profiles and make sure you have wiped cache.
Log files that may help you include the kmsg, dmesg. Logcat may help as well, but mostly to diagnose issues with cortexbrain and app related issues.
gsstudios
Click to expand...
Click to collapse
I'm sorry, I forgot to wiped the cache after upgrading the kernel!
I still haven't reset my profile. I think I've only upgraded the kernel
and _not_ the whole operating system and resetting the profile
should not be required... or am I wrong in this case?
I could not find these log files that you mentioned.
/data/log is empty.
Running dmesg is not an option in such a case
as the kernel is not running any more...
I will investigate this issue further and
when there are problems I will write here again...
noppy22 said:
Which kernel are you using? Compiled by gsstudios or yourself?
I used and tested the latest V10.50v005 extensively and found it to be very stable. Also a couple of V10.45's were very stable as well
Click to expand...
Click to collapse
Well everything seems to be OK now. The kernel is a self compiled V10.50v005 from gsstudios git.
Thanks.
G. J. Wucherpfennig said:
I'm sorry, I forgot to wiped the cache after upgrading the kernel!
I still haven't reset my profile. I think I've only upgraded the kernel
and _not_ the whole operating system and resetting the profile
should not be required... or am I wrong in this case?
I could not find these log files that you mentioned.
/data/log is empty.
Running dmesg is not an option in such a case
as the kernel is not running any more...
I will investigate this issue further and
when there are problems I will write here again...
Thanks.
Click to expand...
Click to collapse
It's good practice to reset profiles just in-case anything went wrong or to refect any changes the developer has made. I might have forced a reset in one of my builds so it may have not been required.
gsstudios said:
It's good practice to reset profiles just in-case anything went wrong or to refect any changes the developer has made. I might have forced a reset in one of my builds so it may have not been required.
Click to expand...
Click to collapse
It's already the 5th time that my smartphone suddenly was switched off.
I think this is because of the Dorimanx kernel, but I can not prove this.
Before installing the Dorimanx kernel this never happened.
Running dmesg is not an option, because I cannot access the smartphone.
Every time this happens I have to push the power button for a long
time. Then the smartphone boots normally.
G. J. Wucherpfennig said:
It's already the 5th time that my smartphone suddenly was switched off.
I think this is because of the Dorimanx kernel, but I can not prove this.
Before installing the Dorimanx kernel this never happened.
Running dmesg is not an option, because I cannot access the smartphone.
Every time this happens I have to push the power button for a long
time. Then the smartphone boots normally.
Click to expand...
Click to collapse
Please test my KK kernel builds and see if you get the same problem.
gsstudios
Hi guys im proud to present you my newest work for Galaxy S6 and S6Edge
THE KALI NETHUNTER
Nethunter is The Kali Linux Android Rom addon that allows you to perform various attacks
HOW TO INSTALL NETHUNTER ?
Just flash the zip over your existing Stock Rom installation it will add all the Nethunter stuff to it
DOWNLOADS
ROM PATCH
CREDITS
ME (J0SH1X)
Noxxxious (for his kernel which i used as base)
Kali dev team
BUGSYou tell me
Can you explaine what is this ?
Sent from my SM-G920F using Tapatalk
tazaga said:
Can you explaine what is this ?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
you know kali linux ?
that linux to hack stuff and so network attacks thats me mobile variant of it
Thanks for this! I've been waiting for a while for a Nethunter release for my S6 ill give it a try and post the bugs i encounter!
Do we need particular rom to run it? Or this zip can be flashed on every rom?
erghetto said:
Do we need particular rom to run it? Or this zip can be flashed on every rom?
Click to expand...
Click to collapse
your rom will work i guess because your using the kernel i used as base
J0SH1X said:
your rom will work i guess because your using the kernel i used as base
Click to expand...
Click to collapse
My signature is much outdated xD now i am on tn rom with tn kernel (N5 port, so i suppose it won't work).
Thanks anyway ^^
Finally someone made it. Thank you VERY MUCH!
can u tell us plz what it gives ? what options ? ty
im coming from griffin rom with nog kernel
morad23 said:
can u tell us plz what it gives ? what options ? ty
im coming from griffin rom with nog kernel
Click to expand...
Click to collapse
This isn't a rom, it just gives you access to kali nethunter tools, these tools are used to test network security if that is what you wish to do, it can also allow you to attack networks, you'll probably need to learn how to use this,, Google kali nethunter to learn more
Hi, I installed the kali and the installation worked well. However, I can´t open the terminal and some of the features that use the terminal also dont work. e.g: Wifite.
PS: I tested it in two different roms: Nano rom and Stock rom and the device is a SM-G920F
@erghetto: what version of tn rom are u using. Just asking, because I'm downloading it and wondering what version is better. 5,7-5,9 or 5,1-5,2?
Will it work on TouchWiz based roms?
JeOZ said:
Will it work on TouchWiz based roms?
Click to expand...
Click to collapse
Yes it will work on stock roms
Is there a way for it to make phone bootloop if installed on a "wrong" kernel?
I want to test it on the XstreSto Lite ROM with the N0G33K kernel but I'm kind of worried about failing it because of the kernel
_Nexus8_ said:
Is there a way for it to make phone bootloop if installed on a "wrong" kernel?
I want to test it on the XstreSto Lite ROM with the N0G33K kernel but I'm kind of worried about failing it because of the kernel
Click to expand...
Click to collapse
Speaking from experience, you can brick your device in many different ways toying around with Nethunter installations. I can't speak for the OP's post but I just finished porting Nethunter to the SM-T580 (Tab A) and I made use of the back-ups I had on hand a few times. I wouldn't advise messing around with this unless you are able to back up your boot (kernel), recovery, system, and data and store them safely off your device. and are confident in troubleshooting bootloops. As long as you are oem unlocked and have a factory ota to restore from, its pretty hard to hard brick these days.
REtails said:
Speaking from experience, you can brick your device in many different ways toying around with Nethunter installations. I can't speak for the OP's post but I just finished porting Nethunter to the SM-T580 (Tab A) and I made use of the back-ups I had on hand a few times. I wouldn't advise messing around with this unless you are able to back up your boot (kernel), recovery, system, and data and store them safely off your device. and are confident in troubleshooting bootloops. As long as you are oem unlocked and have a factory ota to restore from, its pretty hard to hard brick these days.
Click to expand...
Click to collapse
Okay, I'm going to backup all my data then try to flash the ZIP and if it bricks I'll flash a factory ROM
I keep you updated
Does this works on any grace ux rom?
I got this installed but terminal stop working when I try any command :/
Edit : nevermind, I got this working after a reboot
Is there a s6 edge plus version?