I have compiled honor 4c chm-u01 kernel source and now I have zImage file
i'm trying to unpack stock boot.img but I got this error:
Android Magic not found in boot.img
I'm using Ubuntu 14.04 and I tried many softwares like AIK-Linux, Android.Image.Kitchen, CarlivImageKitchen-Linux. but the result is always same and I got the same error.
Any help would be appreciated.
Related
Hi,
I'm currently trying to build a kernel for my GT-P5110. I have a stock Android 4.2.2 which I downloaded from sammobile. I also downloaded the kernel from Samsung Open Source. I've use split_bootimg.pl to get the ramdisk from the boot.img and mkbootimg to make a boot.img from my zImage build successfully and the ramdisk. The problem is, when I flash my boot.img, I get stuck on the Samsung Galaxy Tab 2 logo even if I use the android_espresso10_omap4430_r02_user_defconfig which is suggested by Samsung.
Is there anyone able to sucessfully flash this kernel on his device?
Update: It seems like the defconfig file included in the Samsung Open Source contains some error.
If you want a working defconfig file use this one: http://forum.xda-developers.com/showpost.php?p=37685672&postcount=12
Hey guys
Recently I bought myself a new tablet that is using Windows 8.1 (Onda V975w). I already succeeded putting grub on it and booting into Android, but I'm missing some drivers (Graphics, Touchscreen, everything I guess lol). But the good news is, that there is a Android version of the same tablet (V975i). I downloaded it's rom and tried extracting the boot.img (it contains the bzImage and the ramdisk), but I didn't succeed. It's some kind of weird format, I never seen before. I tried the tools at xda, but it keeps saying ¨wrong magic number¨ and more strange error messages.
This is what ¨file¨ says about the original file:
Code:
[email protected]:~/Desktop/v975i rom/Android_OS_V975i$ file boot.img
boot.img: DOS/MBR boot sector
After some comparing with the stock android kernel, I deleted alot bytes from the beginning and I got this:
Code:
[email protected]:~/Desktop$ file ondakernel
ondakernel: Linux kernel x86 boot executable bzImage, version 3.4.43-00010-g26cfc46-dirty ([email protected]) #1 SMP PREEMPT M, RO-rootFS, swap_dev 0x7, Normal VGA
So there is a bzImage in the boot.img file. But I don't understand how it's packed. I can't mount it, simg2img is not working, nothing.
Can somebody help me please?
Sorry for posting in the wrong thread, I wanted to post it in Dev section. But I'm not going to spam 10 messages so I can post there.
Thanks!
I found some materials to create CyanogenMod for MediaPad X2.
1. device files
https://github.com/Gibbon99/android_device_huawei_hwgemini
2. kernel source
http://download-c.huawei.com/downlo...loadId=42321&version=86254&siteCode=worldwide
3. Huawei Update Extractor
http://forum.xda-developers.com/showthread.php?t=2433454
4. How To Build CyanogenMod For Huawei Honor 5X
https://wiki.cyanogenmod.org/w/Build_for_kiwi
5. how to port CyanogenMod
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Looks like device files above #1 are for CM 12 or lower and may not use as-is for CM13.
Referring to how to port, I tried building one. But I couldn't boot Recovery correctly.
What I did was extracting Boot.img with UpdateExtractor from B211 stock rom, creating device directory with mkvendor.sh, and extracting kernel binary with Update Extractor, placing kernel binary in device/huawei/hwgemini dir, and modifying BoardConfig.mk.
Building Recovery.img with the device dir was successful but booting it was failed.
Can anyone help me with at least creating Recovery and booting it correctly?
This is a phantastic idea and i appreciate it very very much. I am not capable to support, but my best whishes and my believings in the strong support of developers is with you.
Thank you very much for your efford!
Greetz, Ray
RayfG said:
This is a phantastic idea and i appreciate it very very much. I am not capable to support, but my best whishes and my believings in the strong support of developers is with you.
Thank you very much for your efford!
Greetz, Ray
Click to expand...
Click to collapse
IMO no way... Honor 5 has Snapdragon processor where Mediapad X2 has Kirin... That's the problem.
kusutaku said:
I found some materials to create CyanogenMod for MediaPad X2.
1. device files
https://github.com/Gibbon99/android_device_huawei_hwgemini
2. kernel source
http://download-c.huawei.com/downlo...loadId=42321&version=86254&siteCode=worldwide
3. Huawei Update Extractor
http://forum.xda-developers.com/showthread.php?t=2433454
4. How To Build CyanogenMod For Huawei Honor 5X
https://wiki.cyanogenmod.org/w/Build_for_kiwi
5. how to port CyanogenMod
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Looks like device files above #1 are for CM 12 or lower and may not use as-is for CM13.
Referring to how to port, I tried building one. But I couldn't boot Recovery correctly.
What I did was extracting Boot.img with UpdateExtractor from B211 stock rom, creating device directory with mkvendor.sh, and extracting kernel binary with Update Extractor, placing kernel binary in device/huawei/hwgemini dir, and modifying BoardConfig.mk.
Building Recovery.img with the device dir was successful but booting it was failed.
Can anyone help me with at least creating Recovery and booting it correctly?
Click to expand...
Click to collapse
Not gonna happen as Huawei's kernel source is always screwed up. Even decompiling some of their apk's is next to impossible. Honestly I wouldn't even waste your time on anything with a Kirin inside. However I do appreciate and am thankful for you trying.
Hello all,
Well, I just start to compile a kernel source for my Homtom HT17 (I need UVC support).
I found a source code (google HT17 kernel git)
and I compile it with success (I hope) on arm architecture (if I am not wrong, actual rom didn't use aarch64 even if the mt6737M is 64 bits)
So I have a zimage and try to flash it.
So I try to use kitchen and I am able to get to things : a new zip update that I made from a boot.img/system.img from a stock rom and I try to flash it with twrp but I had an error message (something wrong with META-INF\com\google\android\update-script)
Then I try to flash only the boot.img I made with the zimage with twrp. The phone loop at boot... (I restore it with mt flash tool and the rom I had)..
So I am very frustrated, 'cause I spent a lot of time to be able to compile the kernel...
I search a lot on Internet how to deploy correctly my kernel zimage but as now I am not able to get it running!
The problem is like I am newbies in kernel build, I dont know if my process is incorrect or my kernel is incorrect.
So finally I search somebody who could give me steps to deploy correctly my zimage on my phone...
(HOMTOM HT17 MT6737 chip)
Thanks for your reading.
Emmanuel,
Aix En Provence, France
Greeting,
Thank you for using XDA-Assist, you might get more help by others expert in here Homtom HT17-MT6737
XDA-Assist-Team
hey guys, im new to porting new kernels to my phone
i flashed kali nethunter on my MTK device but when i try to flash the kernel it fails when it comes to decompressing boot.img and it show this error (Unpacking boot image failed) using this command :
"$bin/bootimg" xvf boot.img "$split_img"
i tried to flash this kernel in both stock and custom rom but the same error appears
i think nethunter kernel installer isn't made for MTK devices because when i decompressed boot.img it listed files that's not present in the installer like this one (boot.img-ramdisk) it only shows compressed (kernel.gz) and (ramdisk.gz) and (cpiolist) and (bootinfo) and (initrd) folder.
i saw some going modifies boot.img to make a flashable compatible kernel of nethunter depending on given boot.img so
pleaaaaaase guys help me in this situation im really excited to test my alfa in kali nethunter :crying: :crying: :crying:
my phone:
Gionee M5 Lite
kernel version: 3.18.19
rom: lineage os 14.1
nethunter generic-arm64-kalifs-full-rolling-2017.11-18-1618
boot.img:
htt ps: // drive.goo gle. com /file/d/1FN5ogaRRboCKS2ap2_dzYpLdxenJjbse/view?usp=sharing