Uploaded the ramdisk contents from build 23.0.A.2.93 to this Github repo
Enjoy!
Related
Hi
I am used to rebuild boot images with unkmbootimg/mkbootimg on my S4 mini. When I repack a G900F a working stock boot.img and flash it with Odin, the device boots into download mode. I didn't made any changes in the ramfs, the sources are binary the same, but when I repack it to the boot.img it's different to the stock.
Is my bootloader locked? Do I need a special mkbootimg to enable SEAndroid enforcing? It does not matter if I disable it in the ramfs. Do I have to modify the kernel too?
Regards
It seems, that not the boot image is the problem but the cpio initramfs.
I can use the command
Code:
abootimg -u boot.img -r initrd.img
to replace the ramdisk in a working boot image. This works only if a replace the current initramfs with the original initramfs. If I unpack the initramfs too and repack the exact same sources, it won't boot. The sources are binary the same, but the packed initramfs is totally different.
I use the following command to repack my initramfs:
Code:
find . | cpio -o -H newc | gzip > ../initrd.img
cloooned said:
It seems, that not the boot image is the problem but the cpio initramfs.
I can use the command
Code:
abootimg -u boot.img -r initrd.img
to replace the ramdisk in a working boot image. This works only if a replace the current initramfs with the original initramfs. If I unpack the initramfs too and repack the exact same sources, it won't boot. The sources are binary the same, but the packed initramfs is totally different.
I use the following command to repack my initramfs:
Code:
find . | cpio -o -H newc | gzip > ../initrd.img
Click to expand...
Click to collapse
I don't know if this is still relevant to you, but I have found that so far the only tool that repacks s5 kernel properly is the Osm0sis kernel kitchen. I am working on linux and I was able to pack my compiled zimage and modified ramdisk using his tool. You can read more on his original thread here .
I hope thos help you.
Hello.
I'm trying adding several drivers into my SM-N9005 firmware. My phone runs Omega ROM v21, whose kernel doesn't support kernel module drivers, so I decided to recompile Omega's kernel from sources with needed options. The sources were taken from here:
https://github.com/omega-roms/N9005_Omega_Kernel_KK_4.4.2
The compilation was easy, the drivers were compiled too, I have my zImage now.
I downloaded Omega's flashable kernel-only zip N9005_Omega_Kernel_KK_v1.1_XXUFNF4_ramdisk.zip from Omega's repo, unpacked boot.img from the zip and tried disassembling it with split_boot script from bootimg_tools found here:
http://forum.xda-developers.com/showthread.php?t=2319018
I got the following output:
Page size: 2048 (0x00000800)
Kernel size: 8259720 (0x007e0888)
Ramdisk size: 1581598 (0x0018221e)
Second size: 0 (0x00000000)
Board name:
Command line: 'console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3'
Base address: (0x01dfff00)
Writing boot/boot.img-kernel ... complete.
Writing boot/boot.img-ramdisk.cpio.gz ... complete.
Unpacking ramdisk... complete.
So I got original Omega's kernel boot.img-kernel and ramdisk boot.img-ramdisk.cpio.gz. Next I decided to reassemble it and flush back, coz' if it works - my kernel might work too.
I took mkbootimg tool from the same package and created new boot.img with it, using parameters I got previously from split_boot script:
./mkbootimg --kernel boot/boot.img-kernel --ramdisk boot/boot.img-ramdisk.cpio.gz --cmdline 'console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3' --base 0x01dfff00 --pagesize 2048 -o boot.img
So I got new boot.img with size 9846784 bytes, whereas original Omega's boot is 11149312 bytes.
I packed my boot.img into original Omega's kernel zip N9005_Omega_Kernel_KK_v1.1_XXUFNF4_ramdisk.zip, replacing existing original boot.img inside, renamed the zip and flushed with recovery.
Now my phone falls into download mode, saying 'Could not do normal boot'. Flashing back original Omega's kernel restores the phone to normal state, so the problem is with reassembling boot.img
What am I missing? Please, help.
The answer was easy: Android Image Kitchen v1.6 for Linux from http://forum.xda-developers.com/showthread.php?t=2073775
My kernel is rebuilt and my device is now working ok! Thanks to the authors.
jeweller_by said:
The answer was easy: Android Image Kitchen v1.6 for Linux from http://forum.xda-developers.com/showthread.php?t=2073775
My kernel is rebuilt and my device is now working ok! Thanks to the authors.
Click to expand...
Click to collapse
Thanks!
APK Inspector
Find permissions and dependencies used by an Android application.
Read more on our [GitHub page].
Installation
This project currently depends on APKTool. APKTool is an open source library that allows disassembly of APKs.
Follow the installation instructions on their [website].
Install the other project dependencies with `yarn`.
Usage
Install the script globally with `npm install -g` and then run with the command with `apki`.
Otherwise run the script from the project directory with the command `node index.js`.
Examples
apki -r https://pathtoapk.io -x camera
apki -l ./Downloads/myapk.apk -d
node index.js
License
APK Inspector is under the MIT License.
XDA:DevDB Information
APK Inspector, Tool/Utility for all devices (see above for details)
Contributors
ECloud7, The CameraKit Team
Source Code: https://github.com/CameraKit/apk-inspector/tree/master
Version Information
Status: Alpha
Created 2018-12-27
Last Updated 2018-12-27
APK Inspector
Find permissions and dependencies used by an Android application.
Read more on our [GitHub page].
Installation
This project currently depends on APKTool. APKTool is an open source library that allows disassembly of APKs.
Follow the installation instructions on their [website].
Install the other project dependencies with `yarn`.
Usage
Install the script globally with `npm install -g` and then run with the command with `apki`.
Otherwise run the script from the project directory with the command `node index.js`.
Examples
apki -r https://pathtoapk.io -x camera
apki -l ./Downloads/myapk.apk -d
node index.js
License
APK Inspector is under the MIT License.
XDA:DevDB Information
APK Inspector, Tool/Utility for all devices (see above for details)
Contributors
ECloud7, The CameraKit Team
Source Code: https://github.com/CameraKit/apk-inspector/tree/master
Version Information
Status: Alpha
Created 2018-12-27
Last Updated 2018-12-27
Just another utility for repacking kernel images.
Based on utilities from Magisk.
Root is needed.
It can be used as a basis for updater.zip patches.
It does not have an interface.
Using:
-- If an image has been transferred for processing, it will be unpacked into a directory located at the same level as the image. Directory name will be
Code:
<image_name>-unpacked
Now you can make the necessary changes to the files. To repack the image, you must pass the same line to the utility as for unpacking. The new image will be on a par with the original and have a name
Code:
new-<image_name>
Usage example:
Code:
/data/local/kpack ./boot.img
/data/local/kpack /data/local/recovery.img
-- If a logical partition is passed for processing, it will be unpacked into a directory
Code:
/dev/kpacktmp/<partition_name>-unpacked
Now you can make the necessary changes to the files. To repackage the image, you must pass the same line to the utility as for unpacking. The new image will be in the directory
Code:
/dev/kpacktmp
and have a name
Code:
new-<partition_name>
Usage example:
Code:
/data/local/kpack /dev/block/bootdevice/by-name/boot
/data/local/kpack /dev/bl*/boo*/by*/recovery
-- If a cpio file is transferred for processing, it will be unpacked into a directory
Code:
<file_name>-unpacked
Now you can make the necessary changes to the files. For repacking in cpio, you must pass the same line to the utility as for unpacking. The new file will be on the same level as the original and have the name
Code:
new-<file_name>
Usage example:
Code:
/data/local/kpack ./ramdisk.cpio
/data/local/kpack /data/local/my-archive.cpio
-- Starting without arguments will display a message that once again reminds you of the ease of use of the utility.
XDA:DevDB Information
kpack, Tool/Utility for all devices (see above for details)
Contributors
nonamer1990
Source Code: https://drive.google.com/drive/folders/1p07eL12SpT9qXBDq-pYcpncX9k-hlmFm
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2020-05-12
Created 2020-05-12
Last Updated 2020-05-12