bgcngm / mtk-tools Goto Github PK

Hello,

I've been trying to use this tool with the ThL w100s stock rom.

Here is the output log:

./unpack-MT65xx.pl ../boot.img
MTK-Tools by Bruno Martins
MT65xx unpack script (last update: 27-01-2013)

Valid Android signature found...

Input file information:

Kernel size: 3987480 bytes / load address: 0x10008000
Ramdisk size: 704062 bytes / load address: 0x11000000
Second stage size: 0 bytes / load address: 0x10f00000
Page size: 2048 bytes
ASCIIZ product name: 'V1_WCDMA'
Command line: (none)

Kernel written to '../boot.img-kernel.img'
Ramdisk size: gzip: ../../boot.img-ramdisk.cpio.gz: No such file or directory
cpio: fim prematuro do arquivo
rm: impossível remover «../../boot.img-ramdisk.cpio.gz»: Ficheiro ou directoria inexistente
Extracted ramdisk contents to directory '../boot.img-ramdisk'

Successfully unpacked kernel and ramdisk.

Also:
md5sum boot.img
23d5751875c13d4c8d432aa94a311b6d boot.img

After some digging I've found that the initrd ramdisk is output as 'data' and not as a gunzip file.

I've heard you made a CWM build for this phone. Do you know why this is happening?

Thanks!

Binary is not executable under Yosemite 10.10.1

zsh: exec format error: ./mkbootimg.osx

bash: ./mkbootimg.osx: cannot execute binary file

Currently the unpack script outputs success even when cpio does not exist:

MTK-Tools by Bruno Martins
MT65xx unpack script (last update: 31-07-2012)

Valid Android signature found...

Kernel written to recovery.img-kernel.img
Ramdisk written to recovery.img-ramdisk.cpio.gz
Ramdisk size: sh: cpio: command not found
Extracted ramdisk contents to directory recovery.img-ramdisk

Successfully unpacked kernel and ramdisk.

A simple check and die will be nice just before line 88:

system ("gzip -d -c ../$ARGV[0]-ramdisk.cpio.gz | cpio -i");

Hey, I know this script this very old and doesn't support newer chipsets, but I really wanted to mod my logo.bin, it would be pleasure if you could look into my device's logo.bin, please message me at @moonkepler (Telegram) or email at [email protected], if you're ready, I cannot upload the file right here, thanks

fail for mt6752

Kernel written to 'boot.img-kernel.img'
�[31m
Error: the specified boot image does not appear to contain a valid gzip file!�[0m

Hello.

root@dw0rd-virtual-machine:~/Desktop/andr-kernl# ./mkbootimg
bash: ./mkbootimg: cannot execute binary file: Exec format error

full compilation log:

root@dw0rd-virtual-machine:~/Desktop/andr-kernl# ./repack-MTK.pl -boot ./boot.img-kernel.img ./boot.img-ramdisk ./my-boot.img
MTK-Tools by Bruno Martins
MTK repack script (last update: 06-01-2015)

Repacking boot image...
Ramdisk size: 3215 blocks

Build information:

Base address and offsets:

Base address: 0x10000000
Kernel offset: 0x00008000
Ramdisk offset: 0x01000000
Second stage offset: 0x00f00000
Tags offset: 0x00000100

Other:

Page size (bytes): 2048
ASCIIZ product name: '1414054265'
Command line: ''
/home/dw0rd/Desktop/andr-kernl/mkbootimg: 1: /home/dw0rd/Desktop/andr-kernl/mkbootimg: �ELF����: not found
/home/dw0rd/Desktop/andr-kernl/mkbootimg: 2: /home/dw0rd/Desktop/andr-kernl/mkbootimg: Syntax error: "(" unexpected
root@dw0rd-virtual-machine:~/Desktop/andr-kernl#

Hello.

I repack my boot (phone fly iq4516 Octa based on mtk6592). After upload phone doesn't start
(on display logo fly and nothing again, this is best result. On any pack phone set cycle reboot).

Resend orig boot to phone, phone start normal.

link to orig boot:https://www.sendspace.com/file/t5zuy1
link to mod boot(after repack): https://www.sendspace.com/file/xicqss

On ubuntu 13.10 with Perl 5.14.2

Error: could not open the specified file 'boot.img'

Hi!
We have used your tool for many MTK devices with great success. However now we have Lenovo A7-10 that we want to use and this version uses the MT8127 chip. We use CWM 6.0.30 to extract the boot.img and your tool can extract it. Then we modify the default.props and repacka it. One noticeable thing here is that the size of the original boot.img is about 6.2 MB and after repack its around 4MB. But then when we reload it and set a md5 sum we get MD5 sum missmatch. If I work around this and force the new boot.img to load the device cant boot correct and has a lot of issues.

Do you know if there is anything special with MT8127 since you dont have it in your list? Can support for this version be added?

Thanks for a great tool anyhow

Have fake Xiaomi Mi2S with MT6577 chip

Tried already 3 different unpack/repack scripts for MTK chips - all has same issue, phone cannot boot after i flash repacked kernel

Very simple test case - take original kernel 'boot.img'. Unpack it (no errors), Repack it (no errors). Take newly built boot.img (has lower size, i think because original kernel has 0-s filled end of file). Flash to phone - it will not boot. Stuck on logo. Trying to connect to PC, got 'device is not recognized.'

Using Win 8.1 x64 with latest cygwin x86 installed.

Do you have any ideas why it can happen ?