Hi everybody, I am completely new in kernel development and I have a 32-bits machine, so I can't compile JB kernels. I tried to port a 4.3 kernel to 4.2.2 (as u probably know, now I am updating MIUI V5 ROM from miui.com with kingzak34 and the more kernels we have the better for everybody) but isn't booting. Could anybody help?
What I did
I installed the proper environment. I installed java, cygwin and dsixda Kitchen.
With dsixda kitchen I unpacked the 4.3 boot.img, opened the ramdisk and init.rc.
I copied export BOOTHCLASS line from the beggining of the file.
I unpacked a 4.2.2 compatible with MIUI kernel, and replaced that export BOOTHCLASS line in 4.3 kernel.
I flashed it in recovery but bootloops. I had to restore backup
What am I missing?
Thank u everybody!!
There is more to it than just copying class paths
A 4.3 kernel will not boot with 4.2 system modules
A 4.2 rom will not boot with 4.3 system modules
For this to work you will need a 4.3 kernel, 4.3 modules and you will need to do a **** load of smali edits (since you can't work with source on miui) to the rom to accommodate the new methods the 4.3 will be expecting to use.
Or back port the 4.3 kernel to be able to use the 4.2 modules. Also a challenge
Sent from my Nexus 4 using xda app-developers app
modules and drivers, 4.2.2 wont boot without the right modules and drivers.
Related
Hey guys, I have just recently started developing and I have compiled a kernel and ramdisk into a boot image which works great on my phone. My goal is to port MIUI to my device. However, my problem is I don't see the link between kernel versions and android. I mean Gingerbread will run on a 2.6.32 and a 2.6.35 kernel version right? How is the VM and kernel linked? I'm currently on android 2.2 with kernel 2.6.32 and I want to run MIUI with 2.3.3(4). Are there settings or something that needs changing in the kernel? Any advice would be great.
I recently learned how to compile a flashable version of my Galaxy Gio stock ROM as seen here: http://forum.xda-developers.com/showthread.php?t=2109748
I was wondering if I could do the same with a Nexus 7 factory image. The one I had in mind was the 4.2 ROM as I have had the least troubles with it. Would I just decompile it, take the stock /system folder, grab a META_INF and boot.img from a 4.2 stock based ROM, then zip it all up? If not, how would I do it? Could I also make it MultiROM compatible?
Hi,
I recently started experimenting with omnirom and Samsung Galaxy N7000. The build installs perfectly fine along with Google Apps (from Paranoid Android) . However, when I try to install another Custom ROM like Paranoid Andriod-3.99-RC2 for N7000 or PACMAN ROM for N7000, it fails to install. The details:
Omnirom version: omni-4.4-20131204-n7000-NIGHTLY
Device: Samsung Galaxy Note N7000 - International / India.
Google Apps: pa_gapps-full-4.4-20131126-signed
I have attached the log (recovery.txt) for reference.
Any advise / help is appreciated.
... Prashant
This is a recently confirmed issue that I'm not sure what the solution is.
Google made a bunch of changes to how system properties are handled between 4.3 and 4.4. They created some compatibility features such that 4.4 update-binaries would flash on older (4.3 and previous) recoveries, but that doesn't work when flashing zips with 4.3 (and older) update-binaries from a recovery built with 4.4
On most devices, the solution is to just build recovery from a 4.3 tree - but since recovery and kernel are one and the same on the galaxys2 family, there's currently no good solution other than flashing a kernel with a 4.3 (or older) recovery in order to flash a 4.3 (or older) ZIP.
Or the other option which SHOULD work is to remove all the assert checks from the updater-script.
Just flash a custom CM10.2 kernel like raw kernel 4 r3p2 and reboot in recovery.
Then follow the instructions for PA or Pacman.
GALAXY NOTE N7000 // KITKAT // KRT16S
How to revert perseus kernel to stock kernel on I9500 without flash
You can use Universal kernel flasher available on playstore and you need to get boot.img file from the firmware packag of the stock rom u r using by extracting it ......
Hello i need some input and help
I bought a new galaxy s4 value edition gt-i9515
So cusom recovery root and roms work
Recovery and rom only without touch and radio
Used cwn and rom from 9505.
So i think its a kernel issue...
As the device came with kitkat and i,m migrated from mtk platform where its possible to create twrp touch with stock kernel my question is there anything similar cause cwn from 9505 works not well (after restore i had to full wipe cause everthing fc, s)
Also i know that i have to repack a kk kernel for every rom version slimkat cwm stock...
Or has this changed?
So my thoughts i take the stock kk kernel and repack it to work with slimkat and my touch problems have gone.
Please correct me if I'm wrong.
I have both kernel but no pc and don't know how to repack.
So is her someone who can help me out
The better solution would be to add support for i9515 to some custom kernel but quick and dirty repack would do.
Thanks alot
phil2sat