Any body has repack tool for galaxy s5(SM-G900S) kernel?
I do have unpack tool, but repack tool I have is not working.
When I use unmkbootimg made by kuisma below messages shown.
Code:
unmkbootimg version 1.2 - Mikael Q Kuisma <[email protected]>
Kernel size 8360752
Kernel address 0x8000
Ramdisk size 1764107
Ramdisk address 0x2000000
Secondary size 0
Secondary address 0xf00000
Kernel tags address 0x1e00000
Flash page size 2048
Board name is ""
Command line "console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3"
*** WARNING ****
This image is built using NON-standard mkbootimg!
OFF_KERNEL_ADDR is 0xFE208100
OFF_RAMDISK_ADDR is 0x00200100
OFF_SECOND_ADDR is 0xFF100100
Please modify mkbootimg.c using the above values to build your image.
****************
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x1dfff00 --cmdline 'console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' -o new_boot.img
---------------
But I don't know where to get mkbootimg.c source mentioned in message.
I've tried to mkbootimg with --base 0x8000 --ramdiskaddr 0x2000000 and --base -x1dfff00 but both didn't work.
Anybody has a solutoin? Help me plz.
SMG900F repack problem
Hi
Any update with that issue. I experience similar problem.
Thanks
I have unpacked some boot.img files and wanted to repack them after editing the ramdisk. Does anyone know the proper command to repack for the LG G2?
I am currently using:
./bins/mkbootimg --kernel $kernel --ramdisk $ramdisk \
--cmdline "console=ttyHSL0,115200,n8 androidboot.hardware=g2 user_debug=31 msm_rtb.filter=0x0 mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_g2_lgd_cmd" \
--base 0x00000000 --pagesize 2048 --tags-addr 0x4800000 --offset 0x5000000 \
--dt ./bins/dt_g2.img --output new_boot.img
(From a script I modified)
It builds the correct addresses but the phone goes into a bootloop. Before I got the addresses right, I got fastboot. If tried the above command (which I modified). I've also tried using the command the unpack tool said to use. In addition, if tried the command in the script used to build the bootimg when omnirom is compiling. I've tried varying combos.
Yes, I am using the custom mkbootimg. I fished it out of the kernel objects directory after a successful recovery compile.
Thanks!
There are many great guides online on how to compile a kernel, but they often skimp on the last and most important part, how to get it into a working img. Therefore, without further ado, these are the steps
Prerequisites:
-Linux
-Good-ish command line experience
-Mkbootimg https://github.com/Team-DevElite/mkbootimg-python3
-you will need this https://forum.xda-developers.com/showthread.php?t=2073775
-Python 3
Step 1:
-Extract image kitchen
-Download a working kernel and extract boot image
-Place it into image kitchen's folder
-Type this into the terminal(of course, set permissions first)
Code:
./unpackimg.sh <boot image>
You will now get something similar to this.
Code:
BOARD_KERNEL_CMDLINE androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected] coherent_pool=2M enforcing=0
BOARD_KERNEL_BASE 80000000
BOARD_NAME
BOARD_PAGE_SIZE 4096
BOARD_HASH_TYPE sha1
BOARD_KERNEL_OFFSET 00008000
BOARD_RAMDISK_OFFSET 02200000
BOARD_SECOND_OFFSET 00f00000
BOARD_TAGS_OFFSET 02000000
SAVE THE OUTPUT INTO A TEXT FILE
Step 2: Getting the Ramdisk
-Go to the folder, split_img
-Copy ramdisk.cpio.gz into a conveinient folder
Step 3:
Now, get the values from Step 1
-Seperate them like this and get rid of whitespace between the \s
Code:
--ramdisk <ramdisk location> \
--cmdline "androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected] coherent_pool=2M enforcing=0" \
--base 0x80000000 \
--pagesize 4096 \
--ramdisk_offset 0x02200000 \
--tags_offset 0x02000000 \
Now Figure out the directory of your compiled kernel
64bit
Code:
arch/arm64/boot/
32bit
Code:
arch/arm/boot
Depending on your kernel, the kernel file will either be image-gz.dtb or zImage.
Either way its the same step.
Next, add this argument to the one we made above
Code:
--kernel <path to kernel output file>
Step 4 FINAL:
-Set the permissons for mkbootimg
-add this argument to the one above
Code:
--output boot.img
Now your arguments list should look something like this
Code:
--kernel <kernel file> \
--ramdisk <ramdisk file> \
--cmdline "androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected]
coherent_pool=2M enforcing=0" \
--base 0x80000000 \
--pagesize 4096 \
--ramdisk_offset 0x02200000 \
--tags_offset 0x02000000 \
--output boot.img \
-cd into the directory containing mkbootimg
-Now add ./mkbootimg to the front of it and execute!
-Check that it looks something like this
Code:
./mkbootimg \
--kernel <kernel file> \
--ramdisk <ramdisk file> \
--cmdline "androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected] coherent_pool=2M enforcing=0" \
--base 0x80000000 \
--pagesize 4096 \
--ramdisk_offset 0x02200000 \
--tags_offset 0x02000000 \
--output boot.img \
you should now see a boot.img generated
HIT Thanks if I helped
thanks to @osm0sis for his awesome tools!
Thanks for nice and easy guide
Manjot xda said:
There are many great guides online on how to compile a kernel, but they often skimp on the last and most
Thanks for nice and easy guide
Click to expand...
Click to collapse
Thank you, and please don't quote the op, please edit and shorten your post.
Regards
-LLJY
Sry mostly i use other forums there is no rule like don't quote whole op so ignore that post edited. Again nice tutorial
Missed the ramdisk flag while building the new image and my device failed to boot multiple times. Thanks for the detailed guide (pressed the button )!
Can you make a guide video ? And this can not work on Windows ?
shinigami_tsin said:
Can you make a guide video ? And this can not work on Windows ?
Click to expand...
Click to collapse
No to both
I know this is a rather old thread, but I just wanted to say thank you for this. I do a lot of modding and other tricks and hacks on Amazon Fire HD 10 (we were just recently able to unlock them) and it was nice to read a small and straight forward guide without anything being deleted or commented out. As such, I was able to use this method to make a fresh boot.img and it booted the very first time. It's an awesome feeling when that happens, given we often do more unintentional (or intentional) destruction to them.
I've success compiling with gcc aarch64 4.9 for my zen3 and after it i'm packing with mkbootimg with command
mkbootimg --kernel Image --ramdisk boot-img.ramdisk.gz --cmdline "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 androidboot.bootdevice=7824900.sdhci earlycon=msm_hsl_uart,0x78af000" --base 0x80000000 --pagesize 2048 --kernel_offset 0x00008000 --ramdisk_offset 0x01000000 --second_offset 0x00f00000 -o new.img , but i've problem when flashing, boot.img not work , device is booting, but bootlop . Whether i'm wrong something ? i'm customing kernel for adding mode monitor . Anyone know how to fix it ? Thanks
Hi,
I comiled a 5x kernel and created a DTB file for the Nexus. Problem is when I try to boot it from fastboot nothing happens. Screen goes immediately dark, looks like the tablet is powering off. No error in fastboot.
For now I'm testing a very basic DTB that should be able to print something on the screen. I use a very simple initramfs image. I think I applied the right parameters to build the image (I got them from a Linegae boot image)
I'm stuck and I don't see any way to debug that. It's a pitty because the Exynos 5250 is well supported in mainline now. See below the script I use to build the boot image.
Code:
#! /bin/sh
MKBOOTIMG="`dirname $0`/mkbootimg/mkbootimg.py"
MKBOOTIMG_ARGS="--header_version 0 --os_version 10.0.0 --os_patch_level 2022-05 --pagesize 0x00000800 --base 0x00000000 --kernel_offset 0x10008000 --ramdisk_offset 0x11000000 --second_offset 0x10f00000 --tags_offset 0x10000100 --cmdline buildvariant=userdebug"
KERNEL_SRC="`pwd`"
RAMDISK="`dirname $0`/ramdisk/$1.img"
$MKBOOTIMG $MKBOOTIMG_ARGS --kernel $KERNEL_SRC/arch/arm/boot/zImage --dtb $KERNEL_SRC/arch/arm/boot/dts/exynos5250-manta.dtb --ramdisk $RAMDISK --output boot.img
ideas ?