As the title states I am looking for a developer who is the very best(in their eyes) at selinux and can crack it wide open. DO NOT REPLY IF YOU JUST WANT TO TEST STUFF.
me2151 said:
As the title states I am looking for a developer who is the very best(in their eyes) at selinux and can crack it wide open. DO NOT REPLY IF YOU JUST WANT TO TEST STUFF.
Click to expand...
Click to collapse
We need kernel developers
Since we have userspace....wouldn't it be possible to load a kexec module and soft reboot into a custom kernel? I'm new to Android kernels but, not Linux kernels. So, correct me if this has been patched or not possible?
I know that secure bootloaders only allow signed kernels to boot. But, what if we had a signed stock kernel repackaged with a custom initramfs that loaded the custom kernel?
dazemc said:
Since we have userspace....wouldn't it be possible to load a kexec module and soft reboot into a custom kernel? I'm new to Android kernels but, not Linux kernels. So, correct me if this has been patched or not possible?
I know that secure bootloaders only allow signed kernels to boot. But, what if we had a signed stock kernel repackaged with a custom initramfs that loaded the custom kernel?
Click to expand...
Click to collapse
kexec is disabled on our kernel
me2151 said:
kexec is disabled on our kernel
Click to expand...
Click to collapse
I know but, couldn't we load a user made module using insmod at runtime?
Nope. must be a signed module
Related
Quick question i am using a custom rom and I have to flash a kernel to get my wifi working. Is their a way to flash it into the rom so i don't have to flash it every time i do a wipe. Sort of out box tweak
We can't flash kernels by recovery so you shouldn't have to worry about having to reflash the same kernel over again.
Sent from my HTC Amaze 4G using xda premium
Binary100100 said:
We can't flash kernels by recovery so you shouldn't have to worry about having to reflash the same kernel over again.
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
I thought so, every time i use the super wipe function and i install the rom i have to reflash the kernel to get my wifi working.
nofroyo said:
I thought so, every time i use the super wipe function and i install the rom i have to reflash the kernel to get my wifi working.
Click to expand...
Click to collapse
That's because the kernel modules are different than the rom modules.
So which kernel is best to use that will work on all amaze roms ? One that will wrk with all if possible
Also roms that have stock kernel should wrk with all amazes right?
nofroyo said:
So which kernel is best to use that will work on all amaze roms ? One that will wrk with all if possible
Also roms that have stock kernel should wrk with all amazes right?
Click to expand...
Click to collapse
You only have a few to chose from.
You have the stock and you have Faux123 kernel.
You may need to use the computer to flash the Faux123 kernel since the Flash Image GUI app doesn't always properly flash the modules.
Using command prompt or terminal right?
One last question if I flash using terminal will that allow me to switch roms and not have to keep on reflashing the kernel everytime ?
Thanks for all your help it's much appreciated
nofroyo said:
Using command prompt or terminal right?
One last question if I flash using terminal will that allow me to switch roms and not have to keep on reflashing the kernel everytime ?
Thanks for all your help it's much appreciated
Click to expand...
Click to collapse
It's suggested to use the Easy Kernel Flasher if it's a dedicated kernel.
If you're trying to flash the kernel that came with the rom then you can use the Flash Image GUI app on the Market.
I actually just composed an even easier kernel flasher for Faux123's latest kernel.
If you want to try it?
All you should need to do is double click, plug your phone in and click Install.
Let me know if it works or not should you decide to try it.
Faux123 Easier Kernel Updater Executable
I am going to try it right now.
Binary100100 said:
It's suggested to use the Easy Kernel Flasher if it's a dedicated kernel.
If you're trying to flash the kernel that came with the rom then you can use the Flash Image GUI app on the Market.
I actually just composed an even easier kernel flasher for Faux123's latest kernel.
If you want to try it?
All you should need to do is double click, plug your phone in and click Install.
Let me know if it works or not should you decide to try it.
Faux123 Easier Kernel Updater Executable
Click to expand...
Click to collapse
nofroyo said:
I am going to try it right now.
Click to expand...
Click to collapse
Okay just let me know how well it works for you.
You're a tester.
Binary100100 said:
It's suggested to use the Easy Kernel Flasher if it's a dedicated kernel.
If you're trying to flash the kernel that came with the rom then you can use the Flash Image GUI app on the Market.
I actually just composed an even easier kernel flasher for Faux123's latest kernel.
If you want to try it?
All you should need to do is double click, plug your phone in and click Install.
Let me know if it works or not should you decide to try it.
Faux123 Easier Kernel Updater Executable
Click to expand...
Click to collapse
it works perfectly, just plugged in and it did all the work. i rebooted and wifi is working as usual. good job.
hopefully i wont have to reflash the kernel every time i need to wipe haha
nofroyo said:
it works perfectly, just plugged in and it did all the work. i rebooted and wifi is working as usual. good job
Click to expand...
Click to collapse
Thanks for the update. I don't think that I can set it up any easier.
Binary100100 said:
Thanks for the update. I don't think that I can set it up any easier.
Click to expand...
Click to collapse
No worries if you need to test anything else i am willing to test
Binary100100 said:
You only have a few to chose from.
You have the stock and you have Faux123 kernel.
You may need to use the computer to flash the Faux123 kernel since the Flash Image GUI app doesn't always properly flash the modules.
Click to expand...
Click to collapse
I haven't heard of this issue or bug report yet from the over 6k active users of the application. I'm all for fixing the issue but I can't afford to buy all android devices to test with so I rely heavily on users reporting issues and a few knowlegdable testers!
Can you provide an example where Flash Image GUI doesn't properly flash the modules? A link to the .zip file would be most helpful along with the specific module/modules which didn't properly load?
nofroyo said:
So which kernel is best to use that will work on all amaze roms ? One that will wrk with all if possible
Also roms that have stock kernel should wrk with all amazes right?
Click to expand...
Click to collapse
I've been answering this exact question on the EVO 3D boards since HTC released their unlock method back in August. The best answer I've been able to formulate, and feel free to critique or post additional questions is as follows:
http://forum.xda-developers.com/showpost.php?p=18793336&postcount=2
The WiFi error is caused by a mismatch between the WiFi module and the currently loaded kernel. The WiFi module is stored in /system/lib/modules/bcm4330.ko (bcm4329.ko is for EVO 3D) . The kernel is stored in the boot partition.
When booted into the custom recovery through the traditional methods, reboot recovery, bootloader -> recovery, etc., HTC unlock method does not unlock *kernel* write access but does unlock *system* write access.
The result is the kernel module for WiFi is loaded but the kernel itself is not loaded. This creates a mismatch between a WiFi module loaded from the ROM and the matching kernel not being loaded as HTC does not allow it to be loaded from the traditional recovery boot method.
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes:
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery.
Hope that helps!
Edit: If you're curious and want to do some reading on previous WiFi error issues with the EVO 3D on this Q&A board where I replied, here are some similar posts:
http://forum.xda-developers.com/showthread.php?p=17681402
http://forum.xda-developers.com/showthread.php?p=16990247
http://forum.xda-developers.com/showthread.php?p=18624865
http://forum.xda-developers.com/showthread.php?t=1265467
http://forum.xda-developers.com/showthread.php?p=18807723
Click to expand...
Click to collapse
In summary, there is no WiFi module which will work across all kernels as the WiFi module is compiled at the same time the kernel is compiled and are required to be used together as a pair.
Hope that helps clarify!
joeykrim said:
I haven't heard of this issue or bug report yet from the over 6k active users of the application. I'm all for fixing the issue but I can't afford to buy all android devices to test with so I rely heavily on users reporting issues and a few knowlegdable testers!
Can you provide an example where Flash Image GUI doesn't properly flash the modules? A link to the .zip file would be most helpful along with the specific module/modules which didn't properly load?
Click to expand...
Click to collapse
I noticed the issue while applying the Faux123 kernel with the Energy ROM
It's likely because it's not set up to be flashed by recovery but by a computer script.
The directory of the kernel flashing script directory goes like this
Amaze-EKF-008b13-sense
-Kernel-Here
---boot.img
-Modules
---system
-----etc
--------init.post_boot.sh
--------st_drv.ko
--------thermald.conf
--------ti_hci_drv.ko
-----lib
--------modules
-----------kineto_gan.ko
-----------tiap_drv.ko
-----------tiwlan_drv.ko
joeykrim said:
I haven't heard of this issue or bug report yet from the over 6k active users of the application. I'm all for fixing the issue but I can't afford to buy all android devices to test with so I rely heavily on users reporting issues and a few knowlegdable testers!
Can you provide an example where Flash Image GUI doesn't properly flash the modules? A link to the .zip file would be most helpful along with the specific module/modules which didn't properly load?
I've been answering this exact question on the EVO 3D boards since HTC released their unlock method back in August. The best answer I've been able to formulate, and feel free to critique or post additional questions is as follows:
http://forum.xda-developers.com/showpost.php?p=18793336&postcount=2
In summary, there is no WiFi module which will work across all kernels as the WiFi module is compiled at the same time the kernel is compiled and are required to be used together as a pair.
Hope that helps clarify!
Click to expand...
Click to collapse
Once again thanks for this information it clearly answers my questions I had. The app you made solved my initial inquiry and works perfectly. Thanks for all you help and support :=)
Binary100100 said:
I noticed the issue while applying the Faux123 kernel with the Energy ROM
It's likely because it's not set up to be flashed by recovery but by a computer script.
The directory of the kernel flashing script directory goes like this
Amaze-EKF-008b13-sense
-Kernel-Here
---boot.img
-Modules
---system
-----etc
--------init.post_boot.sh
--------st_drv.ko
--------thermald.conf
--------ti_hci_drv.ko
-----lib
--------modules
-----------kineto_gan.ko
-----------tiap_drv.ko
-----------tiwlan_drv.ko
Click to expand...
Click to collapse
Yea, definitely not designed to be flashed by the recovery. They're using unique scripts which could easily be modified to follow the same standards as required by a recovery .zip. In fact, it is very easy to package up one .zip file which will do both, be flashable in recovery but also contain all the files and scripts to be flashable from a desktop via adb/fastboot.
Appreciate the link and info. Made it very easy to narrow down the issue!
Will definitely keep this in mind. Good to see/know there are some unique kernel .zip files be distributed which don't follow the "standards".
nofroyo said:
Once again thanks for this information it clearly answers my questions I had. The app you made solved my initial inquiry and works perfectly. Thanks for all you help and support :=)
Click to expand...
Click to collapse
Glad the information helped and appreciate the feedback!
I tried all GB and ICS kernels for LWW , all of them dont have netfilter so I could't make transparent proxy work??
even the stock based kernel like extended ICS kernel don't have this module!! noting that the stock's support netfilter by defult!!
what is the secret here??
and is there any flashable zip to enable it on custom ons'e ?
Kernels cannot be edited via Recovery.
Are you saying that stock has it and custom kernels don't? I hardly believe it, as all custom kernels are built from the stock source.
Someguyfromhell said:
Kernels cannot be edited via Recovery.
Are you saying that stock has it and custom kernels don't? I hardly believe it, as all custom kernels are built from the stock source.
Click to expand...
Click to collapse
Yep I test it with all custom kernels here, and faild to enable transparent proxy
I tried custom kernels with stock rom, and with custom rom but no luck
Any ideas????
Sent from my WT19i using XDA
do i must flash the kernel?
if i run the stock rom on STOCK-partition on the ss3 recovery,
does custom-kernel rom installation effects on the stock-one?
i just curious about this kernel.
No, afaik the kernel is already inside kexec roms
Sent from my SCH-I535 using xda premium
UduBobo said:
do i must flash the kernel?
if i run the stock rom on STOCK-partition on the ss3 recovery,
does custom-kernel rom installation effects on the stock-one?
i just curious about this kernel.
Click to expand...
Click to collapse
The kernel is part of the ROM flashing.
If you install kexec on slot 1 it will not affect your stock rom.
App data and Apps are specific and exclusive to each ROM slot installation with the exception of what you have specified to backup to google. (ie. contacts and calendar, etc) those will download (restore) and sync to your google account for each slot installation if you set up your google account on the new ROM installation.
UduBobo said:
do i must flash the kernel?
if i run the stock rom on STOCK-partition on the ss3 recovery,
does custom-kernel rom installation effects on the stock-one?
i just curious about this kernel.
Click to expand...
Click to collapse
Kexec is NOT A ROM or a KERNEL !!!
First of all you need understand the word KeExec ( KErnel EXECution ) its a mechanism of the Linux kernel that allows "live" booting of a new kernel "over" the currently running kernel. kexec skips the bootloader stage (hardware initialization phase by the firmware ) and directly loads the new kernel into memory, where it starts executing immediately.
And yes you can have a stock based and a kexec based version with SafeStrap 3 .. We must thank HashCode for this
I hope this clears your doubt
Hello,
before flashing a new kernel is it recommanded to use a tool like GS2KernelWipe Script. I played with a lot of different kernel with my Galaxy SII, and I'm wondering if it's necessary with my beloved Nexus 10 ?
FredC94 said:
Hello,
before flashing a new kernel is it recommanded to use a tool like GS2KernelWipe Script. I played with a lot of different kernel with my Galaxy SII, and I'm wondering if it's necessary with my beloved Nexus 10 ?
Click to expand...
Click to collapse
Necessary? No. I have switched kernels without using the script for the n10. (It is around somewhere on here, in the Apps section I think) But it does FEEL better when you do.
If you have a kernel installed that uses its own ram disk and want to install a different kernel, you need to reflash the ROM then flash the new kernel.
But if its the same kernel (updated) then flash without wiping anything because they will use the same ram disk (if they use one anyway).
iKarido said:
If you have a kernel installed that uses its own ram disk and want to install a different kernel, you need to reflash the ROM then flash the new kernel.
Click to expand...
Click to collapse
Only if the new kernel you are moving to does not include its own ramdisk.
If you flash a ROM, it has its own ramdisk. This would be considered the "stock" one for the ROM you are running. Flashing a kernel with its own ramdisk will override the one that comes with the ROM and you then use the new kernel one. Flashing yet another new kernel later on that also has its own ramdisk will again override the one you currently have. You dont have to re-flash the ROM in between because you are just going to overwrite portions once again anyway.
I believe KTManta and Franco both have their own ramdisks, I know that Trinity does not. So if you are on either Franco or KTManta you can either flash Trinity on top and then have a sort of hybrid of both kernels (with the majority of options and tunables being from the newest flashed kernel) or you can re-flash the ROM to get the stock ramdisk back and then flash Trinity so as to keep it "just" the Trinity kernel instead of a hybrid of it and your last used kernel.
EniGmA1987 said:
Only if the new kernel you are moving to does not include its own ramdisk.
If you flash a ROM, it has its own ramdisk. This would be considered the "stock" one for the ROM you are running. Flashing a kernel with its own ramdisk will override the one that comes with the ROM and you then use the new kernel one. Flashing yet another new kernel later on that also has its own ramdisk will again override the one you currently have. You dont have to re-flash the ROM in between because you are just going to overwrite portions once again anyway.
I believe KTManta and Franco both have their own ramdisks, I know that Trinity does not. So if you are on either Franco or KTManta you can either flash Trinity on top and then have a sort of hybrid of both kernels (with the majority of options and tunables being from the newest flashed kernel) or you can re-flash the ROM to get the stock ramdisk back and then flash Trinity so as to keep it "just" the Trinity kernel instead of a hybrid of it and your last used kernel.
Click to expand...
Click to collapse
If I have KTManta or Franco kernel and I flash Trinity on top without reflashing ROM, the ram disk will still have the mods (or whatever) the previous kernel had. So it will either boot with conflicting problems with Trinity and that ram disk and won't function properly, or it will just boot loop. Most of the time it will boot loop anyway.
This is a known fact that pops on trinity kernels thread a lot :d
Sent from my Galaxy Nexus
iKarido said:
If I have KTManta or Franco kernel and I flash Trinity on top without reflashing ROM, the ram disk will still have the mods (or whatever) the previous kernel had. So it will either boot with conflicting problems with Trinity and that ram disk and won't function properly, or it will just boot loop. Most of the time it will boot loop anyway.
This is a known fact that pops on trinity kernels thread a lot :d
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Never had a boot loop, and never had KT manta's extra governor/scheduler options flashing Trinity over it, because that would have been awesome. But I've never bricked a device either. Guess I'm lucky that way.
brees75 said:
Never had a boot loop, and never had KT manta's extra governor/scheduler options flashing Trinity over it, because that would have been awesome. But I've never bricked a device either. Guess I'm lucky that way.
Click to expand...
Click to collapse
Maybe KTManta uses the ROM ramdisk? I don't know for sure because I only use Trinity. And don't worry, you won't brick your device because of that.
---------- Post added at 07:56 AM ---------- Previous post was at 07:44 AM ----------
Memp2Atl85 said:
Do I simply flash the zip file in clockwork mod or what? Currently using Franco and want to give Trinity a try
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
morfic said:
Unless he replaces the ramdisk like on all other devices, then flashing trinity straight over Franco would create a FrankenTrinity
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Straight from the Trinity Ten Thread.
iKarido said:
If I have KTManta or Franco kernel and I flash Trinity on top without reflashing ROM, the ram disk will still have the mods (or whatever) the previous kernel had.
Click to expand...
Click to collapse
I know... Thats what I had just said.
iKarido said:
So it will either boot with conflicting problems with Trinity and that ram disk and won't function properly, or it will just boot loop. Most of the time it will boot loop anyway.
This is a known fact that pops on trinity kernels thread a lot :d
Click to expand...
Click to collapse
In my experience bootloop problems from kernel incompatibility with flashing over each other is pretty rare. I actually used to use a combo on Franco's ramdisk with the glados kernel on my phone and it worked perfectly fine. Even Morfic (the maker of Trinity kernel) said you can flash his kernel on top of Franco's and it will give you a sort of hybrid of them both. See here:
morfic said:
Unless he replaces the ramdisk like on all other devices, then flashing trinity straight over Franco would create a FrankenTrinity
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
brees75 said:
Never had a boot loop, and never had KT manta's extra governor/scheduler options flashing Trinity over it, because that would have been awesome. But I've never bricked a device either. Guess I'm lucky that way.
Click to expand...
Click to collapse
The governors and such arent part of the ramdisk, thats why. It would be nice to be able to load up the specific governors you want in any kernel, but sadly thats not possible. Those are part of the actual kernel itself and the ramdisk stuff is usually performance tweaks and mods to the system.
EniGmA1987 said:
Only if the new kernel you are moving to does not include its own ramdisk.
If you flash a ROM, it has its own ramdisk. This would be considered the "stock" one for the ROM you are running. Flashing a kernel with its own ramdisk will override the one that comes with the ROM and you then use the new kernel one. Flashing yet another new kernel later on that also has its own ramdisk will again override the one you currently have. You dont have to re-flash the ROM in between because you are just going to overwrite portions once again anyway.
I believe KTManta and Franco both have their own ramdisks, I know that Trinity does not. So if you are on either Franco or KTManta you can either flash Trinity on top and then have a sort of hybrid of both kernels (with the majority of options and tunables being from the newest flashed kernel) or you can re-flash the ROM to get the stock ramdisk back and then flash Trinity so as to keep it "just" the Trinity kernel instead of a hybrid of it and your last used kernel.
Click to expand...
Click to collapse
Ok, I think I understand.
Just to be sure, and regarding my original post, if I come from KTManta and want to give a test to Trinity, instead of flashing the ROM (CM10.1 ATM) can I use a kernel wiping script like GS2KernelWipe ?
Thank you
FredC94 said:
Ok, I think I understand.
Just to be sure, and regarding my original post, if I come from KTManta and want to give a test to Trinity, instead of flashing the ROM (CM10.1 ATM) can I use a kernel wiping script like GS2KernelWipe ?
Thank you
Click to expand...
Click to collapse
It does not look like that script wipes the ramdisk, which is a good thing really because if you wipe (delete) the ramdisk and then flash a new kernel that does not contain a new ramdisk then you will have serious problems. The only way to get back a stock ramdisk is to flash the ROM again.
iKarido said:
Maybe KTManta uses the ROM ramdisk? I don't know for sure because I only use Trinity. And don't worry, you won't brick your device because of that.
Click to expand...
Click to collapse
I am not worried. I have never bricked because I know what I am doing. The lucky part was sarcasm.
EniGmA1987 said:
It does not look like that script wipes the ramdisk, which is a good thing really because if you wipe (delete) the ramdisk and then flash a new kernel that does not contain a new ramdisk then you will have serious problems. The only way to get back a stock ramdisk is to flash the ROM again.
Click to expand...
Click to collapse
That's clear, thanks a lot :good:
Another thing I just thought of is you can make a Nandroid backup of just the boot image as soon as you flash a ROM, give it a name of whatever ROM you are on "-kernel" and then you can restore that boot image whenever you want to restore back to your stock kernel + ramdisk. Alternatively, you can save a backup of your kernel in Trickster MOD and restore it that way at a later point. But both of these methods first require that you still be running your stock kernel and ramdisk that came with the ROM you are on. If you already flashed something else, you will have to re-flash the ROM again to get back to the stock files first
You could just grab the kernel from the rom and throw it into a flashable zip if you don't have a backup, instead of flashing the entire ROM again.
I want to start developing my own kernel but I need some basic information about Android Kernel. First thing I wonder if I flash corrupted kernel image, what would happen? Will device goes black screen and become hardware bricked or just turns on and you can see splash screen and not boot up or something like that? I'm asking this because I have Samsung device (which has Odin mode (like other Samsung devices)) and I read in several sites that saying unless you don't corrupt Odin mode partition you can do whatever you want. I really wonder if it's true.
veli.tasali said:
I want to start developing my own kernel but I need some basic information about Android Kernel. First thing I wonder if I flash corrupted kernel image, what would happen? Will device goes black screen and become hardware bricked or just turns on and you can see splash screen and not boot up or something like that? I'm asking this because I have Samsung device (which has Odin mode (like other Samsung devices)) and I read in several sites that saying unless you don't corrupt Odin mode partition you can do whatever you want. I really wonder if it's true.
Click to expand...
Click to collapse
Read this..
http://forum.xda-developers.com/showthread.php?t=3429355
This will help I'm sure.
Sent from my SM-G800F using Tapatalk
spookcity138 said:
Read this..
http://forum.xda-developers.com/showthread.php?t=3429355
This will help I'm sure.
Sent from my SM-G800F using Tapatalk
Click to expand...
Click to collapse
I compiled a kernel but I still have questions. Do I have to use NDK version used by kernel that I'm compiling? Why we are have to install wireless module separately? And do recovery mode work separate from kernel. These question are essential for me. Thanks you a lot.
veli.tasali said:
I compiled a kernel but I still have questions. Do I have to use NDK version used by kernel that I'm compiling? Why we are have to install wireless module separately? And do recovery mode work separate from kernel. These question are essential for me. Thanks you a lot.
Click to expand...
Click to collapse
Well, I will answer best I can .I'm no expert,but have compiled kernels for a few devices..
1. I guess you mean the NDK toolchain,either way,you do not. I don't use NDK.
2. Really depends on the kernel I think whether or not you need to add the WiFi module separately. I have never needed to,but its not hard to if you need to I don't think.
3. Also not fully sure what you mean. You will need a custom recovery ,TWRP or such to flash the kernel,but you do not need to build the recovery image with the kernel like you would with a full ROM.
Sent from my SM-G800F using Tapatalk