Jump to content


Photo

How to extract u-boot boot.img for amlogic mx devices?


  • Please log in to reply
3 replies to this topic

#1 fly-away

fly-away

    Member

  • Jr. Member
  • PipPip
  • 13 posts

Posted 05 June 2013 - 04:05 AM

I want to repack fire-tp-fix.rar to create boot.img to reflash touchscreen on novo 10 hero with new firmware and get it working.

Ive try to use this scripts
github Amlogic M3 unpack-uimage.sh
But no luck - initramfs looks nice, kernel looks broken.
So repack script create unworked uImage.
All python unpacking script that Ive use cant even unpack initramfs.
Some diagnostics:
$ file boot.img
boot.img: u-boot legacy uImage, Linux-3.0.8, Linux/ARM, OS Kernel Image (lzma), 3997994 bytes, Sat Oct 20 17:32:35 2012, Load Address: 0x80008000, Entry Point: 0x80008000, Header CRC: 0x9656ACBA, Data CRC: 0xF9943BEA

$ mkimage -l boot.img
Image Name:   Linux-3.0.8
Created:      Sat Oct 20 17:32:35 2012
Image Type:   ARM Linux Kernel Image (lzma compressed)
Data Size:    3997994 Bytes = 3904.29 kB = 3.81 MB
Load Address: 80008000
Entry Point:  80008000

$ unpack-uimage.sh boot.img
Checking for uImage magic word...
1+0 records in
0+1 records out
4 bytes (4 <img src='http://www.slatedroid.com/public/style_emoticons/<#EMO_DIR#>/cool.gif' class='bbc_emoticon' alt='B)' /> copied, 0.000458878 s, 8.7 kB/s
uImage recognized.
Extracting data...
62468+1 records in
7808+1 records out
3997994 bytes (4.0 MB) copied, 0.0656765 s, 60.9 MB/s
Checking for ARM mach-type...
3+0 records in
0+1 records out
3 bytes (3 <img src='http://www.slatedroid.com/public/style_emoticons/<#EMO_DIR#>/cool.gif' class='bbc_emoticon' alt='B)' /> copied, 0.000457504 s, 6.6 kB/s
Checking for zImage...
1+0 records in
0+1 records out
4 bytes (4 <img src='http://www.slatedroid.com/public/style_emoticons/<#EMO_DIR#>/cool.gif' class='bbc_emoticon' alt='B)' /> copied, 0.00043781 s, 9.1 kB/s
>>> ../boot.img extracted to Image
>>> Image unlzma'd to Image-ext
Extracting initramfs image (start = 159672, end = 9746614)
9586942+0 records in
9586942+0 records out
9586942 bytes (9.6 MB) copied, 25.0827 s, 382 kB/s
4357 blocks
initramfs.cpio extracted

$ ls initramfs
boot          dev                  init.goldfish.rc  proc  system
data          init                 initlogo.rle.bak  sbin  ueventd.goldfish.rc
default.prop  init.factorytest.rc  init.rc           sys   ueventd.rc

$ file Image-ext 
Image-ext: data


Please, any ideas about correct kernel extraction are welcome

Edited by fly-away, 06 June 2013 - 02:11 AM.


#2 vampirefo

vampirefo

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 96 posts

Posted 05 June 2013 - 09:08 PM

Why would you want to repack a boot.img that wont boot on your tablet? all this is doing is flashing the correct boot.img to the correct device so to fix your problem, get novo 10 hero boot.img and flash it.
Best Regards
Vampirefo

#3 fly-away

fly-away

    Member

  • Jr. Member
  • PipPip
  • 13 posts

Posted 06 June 2013 - 02:16 AM

Why would you want to repack a boot.img that wont boot on your tablet? all this is doing is flashing the correct boot.img to the correct device so to fix your problem, get novo 10 hero boot.img and flash it.


There is no touchscreen fix firmware for novo 10 hero.

This boot.img booting, but unusable for me as far as have touchscreen firmware for ft5406 instead of ft5606 used in novo 10 hero.

So I need to replace couple of files in ramdisk and pack boot.img back.

The other way is build boot.img manually from kernel sources, but I havent seen yet any howto for this, even for novo 7 fire.

Edited by fly-away, 06 June 2013 - 02:17 AM.


#4 vampirefo

vampirefo

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 96 posts

Posted 06 June 2013 - 08:59 AM

Here are the scripts I use, they work well.

http://www.slatedroi...post__p__382051
Best Regards
Vampirefo