Im going to install linux on my android phone.
It wants a feature named "Device Loop" in the kernel.
I checked mine with "Decice Loop Checker" and the results was negative.
I have browsed some kernels but didnt seen any of them telling that their kernel has "Device Loop" feature.
So i have some questions:
1_ what kernel has "device loop" feature for D5803?
2_Can i add it to stock kernel by some tweaks or simple edits?
Stock kernel
Slimm rom
Android M
Related
Someone have studies "Kexec" solution for locked bootloader ?
Kexec : http://en.wikipedia.org/wiki/Kexec
We keep our stock kernel with bootloader locked (not unlocked allowed), but at start (early), we run the kexec process witch kill in memory the stock kernel, and run custom kernel and custom rom
It's elegant, and like CWM process.
Someone have informations ?
Well, i answer myself.
Kexec need 2 parts to run.
1/ A patched stock kernel, or a patch for stock to be flashed by recovery.
This patch is needed to reinitialize CPU without a full memory scratch.
This is necessary to keep kexec alive in memory and finish to load new kernel.
A example of patch here : https://gist.github.com/Tasssadar/6687647
and here : https://gist.github.com/4558647
These patch are for S4Pro APQ8064 CPU
Config Option :
•CONFIG_KEXEC=y
•CONFIG_KEXEC_HARDBOOT=y
•CONFIG_ATAGS_PROC=y
•CONFIG_GROUPER_HARDBOOT_RECOVERY=n
2/ Kernel loader
It is a userspace binary.
The command to boot is :
kexec --load-hardboot zImage --initrd=initrd.img --mem-min=0x85000000 --command-line="$(cat /proc/cmdline)"
kexec -e
This binary "kexec" drop the memory from current stock kernel (even with a locked bootloader),
and load new kernel "initrd.img" to boot.
The command interpreter is called by command-line
To work, we need to dev a patch for stock current kernel.
The rest is easy... "just" modify a CWM to create userspace for kernels and roms on sdcard1, and the load option to boot onto
Please help us to found documentations
I think the devs will be more interested in making the camera work after an unlock.
DooMLoRD is working hard (As he always does for xperia devices) on making a recovery for LB, then I think he will spend time updating DooMKerneL to the same level as it is for other devices, then if he gets time he will work on Kexec, but he has said its low down on his todo list...
I'm waiting for a long time when you are able to load other kernel on my phone locked, if you find a solution I would be very grateful, I'm even willing donate for it
Google translator
I have the same Situation, and i would donate too
Hi!
I just started using Spegelius' Google edition rom for my S4A and I love it! But I have a question about when I boot my phone. It says "kernel is not seandroid enforcing" with a red font at the start but it boots just fine and everything works as far as I see. Should I worry about this or is it fine to leave it like this?
-Sindre
Boot sector is recognizing a rooted kernel. SElinux Enforcing is protection against malware and rootkits.
Not possible or need to change.
http://www.androidpolice.com/2013/1...-than-permissive-other-new-security-features/
Current AOSP 4.4.4 (0.9.6 stable)
http://forum.xda-developers.com/showthread.php?p=54174595
and CM11 (pretty stable 20140806)
http://forum.xda-developers.com/showthread.php?p=50552814
has functional root credentials (su/superuser)
Both developed by a nice guy from the land of thousands of lakes @spegelius
- en ålreit fyr
CWM is running a rooted kernel and will trigger red message. You will find 6.0.4.7 on his Gdrive
There are few kernel config options related to SELinux and enforcing it. I haven't studied the mechanism, or tried to to change those kernel options, but root is needed for too many users currently. If turning SELinux on affects root functionality, that would mean another build without root and SELinux enforcing... but that's not current, first we need to have a stable builds.
I got the red text after i flashed NE5 rom and bootloader was updated. I haven't seen any adverse effects related to it...
Thanks for the answers! Still using the rom and I am very satisfied. The battery life is so much better now. When I go to bed the phone is still at around 35-40% (up from <10%).
Thanks again!
Hello guys, how are you? I hope you are doing fine.
I've been trying and doing my best to setup xposed on my Samsung J700m. I use the Android 5.1.1 and the stock rom of Samsung *touchwiz* deoxed.
I've tested many tutorials from here, but when I flash the last version available for my device "xposed-v86.0-sdk22-arm64-custom-build-by-wanam-20160709" nothing happens. It shows, in the boot: "no command" and then the recovery mode appears normally, like nothing happened, and when I open xposed installer it says that none framework was installed. So I'm pretty confused right now.
My Samsung J700M ins rooted, I've enabled all the needed options in the "develop mode" like depuration, OEM and also allowed to setup apps from unknow sources.
SOME EXTRA INFORMATION:
System: Android 5.1.1 (32-bit)
CPU: 64-bit
Kernel Archtecture: aarch64
(not sure if I should go for the 32 or 64-bit version but I have tested both and I receive the same error:
Installing system updates > NO COMMAND > and then Recovery Mode)
So I would really appreciate an updated answer about it, is it compartible with my phone or not? If so, can you help me to make it?
BIG THANKS
Hi. Is there any such custom kernel built? I can't find any. They all seem to be <3.1. Even ones which were built this year.
Is it impossible/unfeasible to build such kernel?
I want it because I'm installing Arch on Android(in chroot) - it works fine, but I can't update it. Because when I update glibc, everything fails - I get "FATAL: kernel too old" message. And if I won't update glibc, I won't be able to install/update software which requires recent glibc - like gcc. I probably could meddle with glibc(compile it myself manually and relax kernel restrictions), but I'd prefer to just update kernel.
Same thing
I'm in the same situation.
I could not find any kernel higher than 3.0.x
I was happy using Arch on N7000 (using Linux Deploy), but after an update I get "FATAL: kernel too old" for all commands.
It's possible and not so infeasible, just not worth it.
EDIT: I posted this in the S10+ forum but then realized this forum is probably better
Hey all, for some development work I am required to build a custom kernel with some non-standard features on the Samsung S10 SM-G973F Exynos model. Could anyone point me to the best way to get this done? I have a feeling I have way over-thought this issue... I was trying to just build the code from the Samsung open source resource center, but haven't really had any luck.
I have tried many different kernel configs. Getting the kernel built for my phone's ROM version is not the issue, it's actually getting it to boot. I've disabled a lot of the security features (not all) and either the phone goes into a boot loop, or Heimdall/ODIN cannot finish the boot flash because I get that "You can only run samsung images" error message (paraphrased), which ends up with the "OEM unlocking" developer option going missing until I factory reset and screw around with the phone's date. Also noticed topjohnwu of Magisk posted some details about this as a challenge that had to be overcome for S10 support.
Anyway Im just wondering if maybe I am missing anything really obvious: like can I do this somehow with Magisk (replace the kernel magisk uses? i know magisk does some kind of kernel patching, but not sure if its different for the S10.) or, maybe someone else has gotten a custom kernel going via different means? Any tips would be welcome and much appreciated!
Thanks in advance!
mikecc said:
EDIT: I posted this in the S10+ forum but then realized this forum is probably better
Hey all, for some development work I am required to build a custom kernel with some non-standard features on the Samsung S10 SM-G973F Exynos model. Could anyone point me to the best way to get this done? I have a feeling I have way over-thought this issue... I was trying to just build the code from the Samsung open source resource center, but haven't really had any luck.
I have tried many different kernel configs. Getting the kernel built for my phone's ROM version is not the issue, it's actually getting it to boot. I've disabled a lot of the security features (not all) and either the phone goes into a boot loop, or Heimdall/ODIN cannot finish the boot flash because I get that "You can only run samsung images" error message (paraphrased), which ends up with the "OEM unlocking" developer option going missing until I factory reset and screw around with the phone's date. Also noticed topjohnwu of Magisk posted some details about this as a challenge that had to be overcome for S10 support.
Anyway Im just wondering if maybe I am missing anything really obvious: like can I do this somehow with Magisk (replace the kernel magisk uses? i know magisk does some kind of kernel patching, but not sure if its different for the S10.) or, maybe someone else has gotten a custom kernel going via different means? Any tips would be welcome and much appreciated!
Thanks in advance!
Click to expand...
Click to collapse
If you have your kernel image,try to patch it with magisk.Look at the kernel :HeliosPie Kernel 3.1 for J5 2017.You will see it replaces and deletes some libraries in the phone. Try to do that manually or copy the code from META-INF.