Hello all developers of NookTablet team).
I read many threads about good booting of modifitated kernels from SD card. When I compile own kernel based on stock source and then make boot.img I receive only message in UART (yes I have uart access):
Starting kernel ...
After 3-5 sec Nook reboot CPU(.
P.S. To build boot.img I use http://www.freeyourandroid.com/guide/extract-edit-repack-boot-img-windows instruction (thanks to Goncezilla)
I am newbie in Android development, but not in linux development.
Related
Hi dear personal XDA developer. I would like to understand the whole structure of the operation of the platform. Desdo beginning of the boot by the end of the boot. Understanding how it is assembled in the form of the System Tree. In Order crescente.Tipo when a kernel is installed is loaded before or after the CWM. The CWM backups restores a Kernel? The fastboot is loaded before the ROM? or is part of the ROM Fastboot? I need to understand how it works the Tree of the Order of the boot startup. What it is first loaded? A Kernel ROM and improperly installed, can block the installation of a new kernel, if so how to install a kernel when the kernel fastboot no longer installs. How do I copy my kernel for security backup?
Hello,
since I don't yet have access for the specific section I post here
I can't find how to flash a kernel built from source (aka zImage). Since fastboot is not available on GS3, I just want an alternative tech to boot my gs3 with my build zImage.
I build the source from stock kernel samsung opensource database (update 8) and receive a zImage file.
I made a backup with cwm and unpack the boot.img with a perl script, then repack a new boot.img with my zImage as kernel and the ramdick from unpack but cannot boot with new package.
Could someone maybe give me a kernel source and the right corresponding package to boot it. Or maybe just a good way to make the whole process.
My final goal is to build a custom module for the GS3, that's my I need building from source and not an already-packed-kernel. Moreover if someone can help me directly about the module, he's very welcome
Hi,
I don't try to flood, just to increase my chance to have any help
I want to build a custom module for my GTi9300. Since the module need to be compiled whith the same kernel on the phone, i tried to build and flash a kernel from source (aka zImage). Since fastboot is not available on GS3, I just want an alternative tech to boot my gs3 with my built zImage.
I build the source from stock kernel samsung opensource database (update 8) and receive the zImage file.
I made a backup with cwm and unpack the boot.img with a perl script, then repack a new boot.img with my zImage as kernel and the ramdick from unpack but cannot boot with new package.
Could someone maybe give me a kernel source and the right corresponding package to boot it. Or maybe just a good way to make the whole process.
------------------------------------------------------------------------------------------------------------------------------
Moreover if someone can help me directly about the module, he's very welcome.
Without having the same kernel on the phone, I already tried to insmod my module. I've got first some version error, with the module_layout. Even if I correct it the module still doesn't load. In the kernel source, I modify the Subversion in the kernel to match with the one on the phone. But the compilation result add a "-gc33f1bc-dirty" to the end. Maybe I miss something to do before the compilation
Please post all questions in the Q&A section.
Thread Moved and Closed as you already have a thread going for this over there.
Hi everyone,
I need some help while I try to compile my first kernel (for experiments) with the Linaro-Toolchain. I followed a youtube instruction and it works well till the point to handle a stock/original boot.img file (with $ abootimg -x boot.img)
INFO: I´m playing with the slimkernel source, Linaro toolchain and mint 17.
Well before bothering you, i tried 1000 different ways to get this boot.img. But:
- extracted stock fimware only contains a boot.bin (and size does not match)
- a boot.img form a custom kernel zip brings me "no Android Magic value. giving up"
- downloadable boot.img are for all other phones excluding i9100...
Do you have any idea how to get this f****g boot.img which is working to get the kernel compiled, or do you know what i did wrong with that??
Thanks in advance
Ambador
Have you tried to extract a boot.img from a slimrom zip?
Yes I did but gave me the same result. I tried different kernels, roms and everytime while typing abootimg x -boot.img the fail appears.
Ambador said:
Yes I did but gave me the same result. I tried different kernels, roms and everytime while typing abootimg x -boot.img the fail appears.
Click to expand...
Click to collapse
I don't know really what you are doing atm because you are compiling a kernel from the kernel sourcecode. But I think that you are going to replace the zImage in the boot.img because kernel compiling doesn't include ramdisk right? Did you ever tryed to use dsixda-kitchen, It's usefull and also easy to use with kernel extracting.
Sorry if I got you wrong.
I used that kitchen already, but gave me the same missing android magic issue.
I tried an other thing, cuz im currently using apolo 7.1 kernel:
this kernel has a zimage only. So is it a possible way to get the kernel source, make a change (add an scheduler which is not in kernel) to see if it will work, compile the zimage with linaro and just replace it in the kernel.zip??
Hi all,
I have been looking into compiling the kernel and TWRP for this device.
For the kernel, it compiles but does not boot (Will invvestigate later ).
The TWRP does not boot, most likely related to boardconfig.mk. I am unable to find the kernel base or offsets. Can anyone assist in discovering this information? I have tried unpacking boot.img and the current tools does not show this information.
Shaky156 said:
Hi all,
I have been looking into compiling the kernel and TWRP for this device.
For the kernel, it compiles but does not boot (Will invvestigate later ).
The TWRP does not boot, most likely related to boardconfig.mk. I am unable to find the kernel base or offsets. Can anyone assist in discovering this information? I have tried unpacking boot.img and the current tools does not show this information.
Click to expand...
Click to collapse
Hello. I manage to create TWRP for this device.
It is currently tested on a device running the laster firmware RUI 4.0_C.13 but it should work in RUI 3.0. Decryption works, MTP didn't yet.