You should always backup your data as it may become lost or corrupted due to hardware failure, user’s mistakes, or bad actors. However, if your data appears to be truly lost, and backup is not available, it’s possible to use data recovery software such as Wondershare Recoverit Data Recovery available for Windows and Mac OS. The program will scan your computer or specific folder/storage device to locate any kind of deleted or corrupted files and ask you which files or/and folders to retrieve. This works on drives that have been corrupted due to a crash or power failure, formatted by mistake, and so on and the program can handle both internal and external drives. Wondershare has recently released Recoverit 8.0 version with various new features and improvements: Simpler and more user-friendly interface – Recoverit 8.0 comes with a simpler and more user-friendly design as shown above. The software will show […]
How to extract kernel.img with mkboot script
As I tried instructions to install Linux on Amlogic S905 Android TV boxes yesterday, I wanted to extract kernel.img file found in Android firmware, but Google did not help that much until I found mkboot part of mkbootimg_tools scripts. But first let’s see how kernel.img is created… Google provide a Python script called mkbootimg that combine the kernel image (e,.g. zImage), a rootfs/ramdisk and the device tree (DTB) file with a command line that looks like:
1 |
./mkbootimg --base=0 --kernel_offset=0x01080000 --kernel ${KERNEL} --ramdisk_offset=0x01000000 --ramdisk ./${ROOTFS} --second ${DTBFILE} --output ./kernel.img |
However, AFAIK the company does not provide a “unmkbootimg” script, and mkbootimg can only be used to create kernel.img, not decompile it. But that’s what mkboot does, and it works for kernel.img and recovery.img. Let’s retrieve the necessary files first:
1 |
git clone https://github.com/xiaolu/mkbootimg_tools |
mkboot is a bash script so we can use it right away:
1 2 3 4 5 6 7 8 9 10 11 |
cd mkbootimg_tools ./mkboot <Unpack and repack boot.img tool> ---------------------------------------------------------------------- Not enough parameters or parameter error! unpack boot.img & decompress ramdisk: mkboot [img] [output dir] mkboot boot.img boot20130905 Use the unpacked directory repack boot.img(img_info): mkboot [unpacked dir] [newbootfile] mkboot boot20130905 newboot.img |
So it can be used both for unpacking and repacking kernel.img to/from the output directory. Let’s run the command […]
Droid Stick A2 mini PC Recovery with AMLogic’s Hardware Flash Tool
In some circumstances, for example by installing the wrong firmware or doing something wrong by playing god (as a root user), it’s possible to brick your device. This happened to me with one of my Droid Stick A2 mini PCs based on AMLogic AML8726-MX. I changed some files in /system/etc/permissions directory, lost Wi-Fi access, and even replacing my changes with the backup files would not solve the problem. It also changed some permissions in the system, and it was not possible to restore the firmware the usual way. At the end of last month, dbtablets left a comment with download links to “Amlogic USB Burning tool”, but I only decided to give it a try today, and after some efforts I was successful. Just make sure you only use this method as last resort, i.e. a standard firmware upgrade does not work, and you’re about to throw your device in […]