[Q] Custom kernel possible on the Defy? - Defy Q&A, Help & Troubleshooting

Is it possible to use a custom kernel on the defy even though it has a locked bootloader? As it is possible to load custom kernel modules which will then run in supervisor mode, it should be possible to write a kernel module that copies itself at the end of RAM, disables all interrupts so that execution doesn't jump out of the module, jumps into its own copy at the end of the RAM, loads another kernel into the start of the RAM and jumps into it, right?

defy cant run custom build kernels because of the bootloader..
but AFAIK you should be able to compile and load modules outside the kernel or something, i would really like USB host mode on defy, maybe someone skilled enough can try it??

hsrars-d said:
defy cant run custom build kernels because of the bootloader..
Click to expand...
Click to collapse
Uh, did you even read my post? I'm suggesting to first let the bootloader load the stock kernel, then let the init process load a kernel module that loads another kernel and jumps into it. No need to touch the bootloader, you'd simply put another bootloader into a kernel module.

Now I found http://forum.xda-developers.com/showthread.php?p=24918641&highlight=defy#post24918641 ... I wonder whether it's possible to carry the 3G driver's state over a reboot...

umm, sorry i was bit sleepy, dunno about kecex though
EDIT: and i found this :http://www.eternityproject.eu/topic/49-bootloader-bypass-kexec-for-motorola-razr/#entry342
EDIT2: -.- i'm still sleepy

Somewhere is a post where Quarkz confirmed that we can't use kexec. He posted a conversation with the kexec main developer to do it. Maybe on cheesecake thread.
Sent from my MB525 using xda app-developers app

Related

[Q] DROID2 custom kernel?

Are there any custom kernels out yet for the DROID2? I've searched high and low online and I'm not seeing any, the reason why is I'm looking to run Ubuntu on the Droid 2(as detailed on NexusOneHacks ) and I keep getting a no loop device error, which from what I've seen means it isn't enabled in the kernel.
pixl8d said:
Are there any custom kernels out yet for the DROID2? I've searched high and low online and I'm not seeing any, the reason why is I'm looking to run Ubuntu on the Droid 2(as detailed on NexusOneHacks ) and I keep getting a no loop device error, which from what I've seen means it isn't enabled in the kernel.
Click to expand...
Click to collapse
No. The bootloader is locked, making custom kernels impossible (unless someone figures out how to crack/bypass the signature verification process).
However, it may be possible to get Ubuntu working if you can build whatever Ubuntu requires as a module (you can load the module with insmod). You could then use the stock kernel with the mobile Ubuntu files from the N1. You would probably have to make significant modifications to the rest of the system to get it to work properly on the Droid 2.
The ROM Download page for Liquid 3.0 shows downloads for chevyno1 kernels for both the Droid2 and the DroidX.
Is it possible to flash different kernels on this device?
If so, can you please provide details and instruction or perhaps provide a link to further info?
Thanks!

Adding multi-touch as a module?

About Multi - touch
You can do multitouch driver as a module. This
kernel module to be unloaded from memory the old driver and load a new one. one person did it for the ebook.
Click to expand...
Click to collapse
Here's how to compile and add module:
http://forum.xda-developers.com/showpost.php?p=11854116&postcount=10
'andrej' has also added a sample from G1
any developer willing to help?
We need someone with knowledge in C, or give me touchscreen module sources for both X10 multitouch module and X8, and 2-3 weeks of time to try to make this work... I'd figure out differences between two modules and put mulitouch part to x8's module... I've had success in similar stuff already so why don't give it a try? We have nothing to lose... (except time, of course )
Will this work?
excellent! I'm in support for this
blagus said:
We need someone with knowledge in C, or give me touchscreen module sources for both X10 multitouch module and X8, and 2-3 weeks of time to try to make this work... I'd figure out differences between two modules and put mulitouch part to x8's module... I've had success in similar stuff already so why don't give it a try? We have nothing to lose... (except time, of course )
Click to expand...
Click to collapse
Cool. I'm no programmer but I'll try and get a developer to share the X10 module, and then you can perhaps give it a shot If a developer jumps onboard, it'll be brilliant ofc.
@Others
From what I've heard, this has been done and ought to work. Since you dont need to push a new kernel altogether, that step is bypassed.
If it worked, would it be implemented on official 2.1 only, or could it be ported to non-official roms too?
Graveir said:
If it worked, would it be implemented on official 2.1 only, or could it be ported to non-official roms too?
Click to expand...
Click to collapse
Its a bit premature to comment on that. First we need to get developers onboard. But once the kernel module is modded, it should work across all ROMs.
Relevant: http://en.wikipedia.org/wiki/Loadable_kernel_module
See the section for binary compability.
Sent from my X8 using XDA Premium App
oisteink said:
Relevant: http://en.wikipedia.org/wiki/Loadable_kernel_module
See the section for binary compability.
Sent from my X8 using XDA Premium App
Click to expand...
Click to collapse
it says
"In an attempt to combat those problems ,
symbol versioning data is placed within the
. m o d i n f o section of loadable ELF
modules . This versioning information can
be compared with that of the running
kernel before loading a module ; if the
versions are incompatible , the module will
not be loaded."
Maybe the module can be customized, and the symbol versioning data added, so that the kernel doesn't reject it?
Just a thought. Somebody has managed to.do this for another device. I'll try and get in touch with him.
Check out this thread. Here is where the discussion about such a possibility started:
http://forum.xda-developers.com/showthread.php?t=976948

[kexec exploryng][sbf checking] need help

Guys, we with Quarx now exploryng kexec module.
As far i can see, we need /proc/atags node to exist in system to use it.
Maybe you can help me.
I need that you flash all sbf that we have...
And check if such node exists(/proc/atags)
If so - we can get working kexec and custom kernels for ever.
Please ,check it.
Thanks!
Is /proc/atags just a copy of the atags struct (which comes from the CDT)? It's probably possible to create a module (using symsearch if necessary) to add that if it is all we need... but I assume quarx is aware of that approach? Worst case we just copy the bits out and fake it. Did you look into that already? In the interim, you could build a fastboot kernel that has /proc/atags for kexec testing (I assume--unless the Motorola kernel source doesn't include /proc/atags support then it will take more work and I assume none of the released kernels would have it). Time to start the grep incantations.
Edit: In arch/arm/Kconfig I see:
Code:
config ATAGS_PROC
bool "Export atags in procfs"
depends on KEXEC
default y
help
Should the atags used to boot the kernel be exported in an "atags"
file in procfs. Useful with kexec.
Default y means either that Motorola explicitly disabled it, or that it's been disabled in the OMAP tree.
boot5.img have atags support.
Already get that info to http://fjfalcon.ru/atags
It does look like /proc/atags is just a memcpy of the struct that comes from the CDT.
I think the problem is the /proc/atags depends on KEXEC support in the kernel. So needing /proc/atags is the tip of the iceberg and the iceberg is "we need a kernel that supports KEXEC". I'm guessing there's no chance in hell that's there on any kernels. I wonder if there's a way to check whether atags.c was included by looking at only the kernel images rather than flashing them all. So, I'm guessing boot5.img has KEXEC support. Or do you have a kexec module that you're injecting? They've tried kexec on Milestone a long time ago, so there must be a way around missing kexec in the kernel.
Damn, for now i used kexec-arm -e /sdcard/kernel and get phone frozen.
I need uart..
http://fjfalcon.ru/kexec_load.ko
fjfalcon said:
Guys, we with Quarx now exploryng kexec module.
As far i can see, we need /proc/atags node to exist in system to use it.
Maybe you can help me.
I need that you flash all sbf that we have...
And check if such node exists(/proc/atags)
If so - we can get working kexec and custom kernels for ever.
Please ,check it.
Thanks!
Click to expand...
Click to collapse
I check if I had /proc/atags in a nandroid backup (French stock sbf) with unyaffs but I doesn't have.
Zachary57 said:
I check if I had /proc/atags in a nandroid backup (French stock sbf) with unyaffs but I doesn't have.
Click to expand...
Click to collapse
/proc is a memory filesystem generated by the kernel after boot, unfortunately. You would have to boot the kernel to check. Nevertheless I'm pretty confident that none of our kernels has it because enabling /proc/atags in the kernel *requires* also enabling kexec in the kernel according to the XT720's kernel source. I can't think of any reason for Motorola to ever enable kexec in their kernel (kexec allows booting a second kernel from the current kernel which is why we're interested in it--motorola developers would be using engineering devices and flash whatever kernel they want directly).
fjfalcon said:
Guys, we with Quarx now exploryng kexec module.
As far i can see, we need /proc/atags node to exist in system to use it.
Maybe you can help me.
I need that you flash all sbf that we have...
And check if such node exists(/proc/atags)
If so - we can get working kexec and custom kernels for ever.
Please ,check it.
Thanks!
Click to expand...
Click to collapse
sir, there is no /proc/atags in modsbf .sbf . tqvm

[KERNEL][I8200N] Baroni-Kernel Alpha

I can give ABSOLUTLEY no gurantee!! All you do with your phone will be on your own. I'm not responsible if your phone will brick or whatever...
Attation! This kernel is for the I8200 variant ONLY... the I8190 is absolutley not compatible !!!
Kernel should be work also for I8200/I8200Q/I8200L-Variants, but can not be gurateed as the basis was I8200! If it works then a notice will be fine!
If you are not sure about the process, the data are important on your phone or you need it as a daily phone, then LET IT BEE, and wait for the messages that it is safe to use. Its important at the beginning that users with knowledge tried it at first !
Changelog:
12.02.2016: Long time ago, but now after a lot of investigating some new things comes up. Check what was done
05.01.2014: I try to work on the kernel over x-mas in my free time, but I must say that the source of samsung which was provided on opensource.samsung.com is not really funny stuff... there are so many coding errors, which was. not able for me to solve directly. So now I started to examine other kernel sources, and will try to port a more main.tained source to the i8200. From My point of view this will be the only way to produce an more accurate kernel for our device, and get the possibility to include also selinux what is needed for a kitkat-rom. Nevertheless, it is not easy to work on that stuff, because I'm not an expert on kernel work (but I learn every day more , so if you know someone with more kernel experiences, it would be very helpful to get a contact...
Baroni-V0.1 contains:
Basis of opensource from Samsung with some bugfixing
fixed recovery-boot-loop with a config-setting which must be used special in the Recovery zImage
Loglevel pushed down to minimum
Uber-Toolchain 4.9
set onDemand-Governor to standart. just to check how that works
start implementing SmartAssV2-Gonernor, but leave it inactive, due to some compile-errors.
bringing SELinux to work for future kernel releases if needed for > 4.4
Planned:
new govenors at the moment not established (will come later)
more other stuff (depending on learning-curve
Installation:
Install a recovery for safetyreasons (I prefer TWRP https://www.dropbox.com/s/d3rnfp3vabz9ee8/twrp_i8200_corrected.7z?dl=0
Read carefully the hints of the usage in the following firts post: http://forum.xda-developers.com/galaxy-s3-mini/general/s-iii-mini-ve-i8200-n-t2826565 (There also the needed Odin (3.09) can be get)
Make backups of the complete phone, and be sure that you know what you do!
Download the right Firmware for your phone from http://www.sammobile.com/firmwares/ (just to have a other safety fallback in your hand!)
Download the file, start odin as usual (all kies-tasks closed!)
extract the file, and put it to AP
put the phone in Downloadmode (Vol-down,Home-key and powerbutton), and connect the phone with PC
flash the kernel, and let the phone reboot
pray
If things go wrong, please give everytime the following information's:
what you did before
what exactly happened (its not easy to help if you say: it did not work )
which rom in which version, which recovery and which version of my Kernel you use
try to get a /proc/last_kmsg (if a unknowen reboot appears) and/or Logcat, Build prop, CPU info, Sysctl, Kmsg, Dmesg and send it to me (or as a attachment to the post) for further analyse (you can use that tool for it: https://play.google.com/store/apps/details?id=com.bassel.andylog )
Attention: First checks seem to be that I8200 (without N or L or Q) did not work atm.
Download:
kernel_i8200n-Baroni:
https://www.androidfilehost.com/?w=files&flid=47763
kernel_i8200n-Stock.7z (to getting back to stock kernel via Odin):
https://www.dropbox.com/s/xfhufcpxl5kxmue/kernel_i8200n-Stock.7z?dl=0
Recoverys (with fixed recovery boot loop):
https://www.androidfilehost.com/?w=files&flid=49834
There was a mistake in the initramfs. was corrected now. If you download the V0.7 yesterday, please dont use it... Try V0.8.
One question.
SolarPlexus said:
There was a mistake in the initramfs. was corrected now. If you download the V0.7 yesterday, please dont use it... Try V0.8.
Click to expand...
Click to collapse
My Friend.
Yesterday I tried to install its kernel but my phone did not start properly.
I wanted to do a restore from a backup that had done, but the recovery (TRWP) did not restore the data partition.
Is there any chance that I happen again the same with this version?
Danh23 said:
My Friend.
Yesterday I tried to install its kernel but my phone did not start properly.
I wanted to do a restore from a backup that had done, but the recovery (TRWP) did not restore the data partition.
Is there any chance that I happen again the same with this version?
Click to expand...
Click to collapse
Attention with TWRP-Recovery. Data-Partition restore seems to be not right. At the moment please did not use it, because it can delete your data-partition. We have to investigate it further! Other partitions seems to be ok, but its a good Idea if you copy your important data also manually to a other storage (like PC) while you trying things of this thread.
i install the kernel ans stuck into samsung logo.if i flash the stock kernel i will fix it?
stock kernel?can you upload it?
KwstPap said:
i install the kernel ans stuck into samsung logo.if i flash the stock kernel i will fix it?
stock kernel?can you upload it?
Click to expand...
Click to collapse
Did you made a backup with twrp (as described)? If yes, then make a restore only with boot marked in the list.
Otherwise, which version did you have? Plain n/l/q? Than I can make a package for Odin...
send with my Oneplus One (bacon) SlimKat Tapatalk
About the data recovery, use aroma FM to restore. Out worked for me
hahhhahaha i forgot it to take a backup hahaha .i reflashing the stock firmware... i Have i8200N
but why the kernel doesnt work on me?
KwstPap said:
hahhhahaha i forgot it to take a backup hahaha .i reflashing the stock firmware... i Have i8200N
but why the kernel doesnt work on me?
Click to expand...
Click to collapse
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.
SolarPlexus said:
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.
Click to expand...
Click to collapse
hahahahaha always forget to take a backup .but i am very stypid .i had a backup on my pc.hahah in one weak i have reflashing the stock formware 5 times and the root recovery and other staff again hahaha
thanks for the stok kernel
SolarPlexus said:
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.
Click to expand...
Click to collapse
¿which brings benefits to install this kernel?
RodsonBorja said:
¿which brings benefits to install this kernel?
Click to expand...
Click to collapse
Atm nothing... Its alpha and not working. Unfortunately I'm a little bit blocked by illness and x-mas and was not able to work on it... Maybe next week...
send with my Oneplus One (bacon) SlimKat Tapatalk
Hi to all followers of this thread.
Just to give an update: I try to work on the kernel over x-mas in my free time, but I must say that the source of samsung which was provided on opensource.samsung.com is not really funny stuff... there are so many coding errors, which was not able for me to solve directly. So now I started to examine other kernel sources, and will try to port a more maintained source to the i8200. From My point of view this will be the only way to produce an more accurate kernel for our device, and get the possebility to include also selinux what is needed for a kitkat-rom...
Nevertheless, it is not easy to work on that stuff, because I'm not an expert on kernel work (but I learn every day more , so if you know someone with more kernel experiences, it would be very helpful to invite him/her. To ask in forums (also in xda) is something what I do, but unfortunately the responding are not every time safe...
So I wish you all a happy new year, and lets work together to bring our device a little bit forward
SolarPlexus
Ask @dtrail1 he know how the kernel thing work.
Maybe he'll support you
VallNAr said:
Ask @dtrail1 he know how the kernel thing work.
Maybe he'll support you
Click to expand...
Click to collapse
Ask MARDON he made the kernel for Galaxy Ace - maybe he support Your work.
Any progress on the kernel? Is it on github?
Why does this not suport usb flash drives or can the function be ported
Gershy353
I think it must be activated on both sides. Kernel and ROM...
send with my Oneplus One (bacon) SlimKat Tapatalk
SolarPlexus said:
I think it must be activated on both sides. Kernel and ROM...
send with my Oneplus One (bacon) SlimKat Tapatalk
Click to expand...
Click to collapse
How is this done i have the sandisk dual flash drive but its useless on my device
Gershy353
Ah, you mean otg support, not sdcard seen as USB instead of mtp?
send with my Oneplus One (bacon) SlimKat Tapatalk

CPU Speed sm-j320fn kernel

Hi I have root but I can't keep all cores on or keep the CPU running max speed it keeps resetting any ideas also is there not a customer kernel I'm using Los 13 at the moment.
Thanks
No one know why I can't turn all on and keep clock speeds to the max
LanceGoss47 said:
No one know why I can't turn all on and keep clock speeds to the max
Click to expand...
Click to collapse
At a guess if say you need to write a new custom kernel that allows you to enable all cores permanently and flash that (while making sure it still works with LOS). Root alone doesn't always help of the options aren't there, I used to have a phone that used a cyanogenmod port which had control over cores integrated but it never worked properly because (those who knew about these things said) it wasn't properly implemented in the kernel.
Wulfie217 said:
At a guess if say you need to write a new custom kernel that allows you to enable all cores permanently and flash that (while making sure it still works with LOS). Root alone doesn't always help of the options aren't there, I used to have a phone that used a cyanogenmod port which had control over cores integrated but it never worked properly because (those who knew about these things said) it wasn't properly implemented in the kernel.
Click to expand...
Click to collapse
Is there a way to decompile the kernel myself? Or modify with root manually?
LanceGoss47 said:
Is there a way to decompile the kernel myself? Or modify with root manually?
Click to expand...
Click to collapse
It should be possible, [email protected] put instructions on the J320FN Lineage OS thread on how to change the boot.img (including tools for doing so) and you can work on the kernel using dsixda's android kitchen thread linked below may go some way to getting you started, obviously if you're using Linux you can use other guides to get much better functionality.
https://forum.xda-developers.com/showthread.php?t=1698582
Wulfie217 said:
It should be possible, [email protected] put instructions on the J320FN Lineage OS thread on how to change the boot.img (including tools for doing so) and you can work on the kernel using dsixda's android kitchen thread linked below may go some way to getting you started, obviously if you're using Linux you can use other guides to get much better functionality.
https://forum.xda-developers.com/showthread.php?t=1698582
Click to expand...
Click to collapse
Thanks could you link me to [email protected] instructions please

Categories

Resources