Firmware: Chameleon (1.0.41) Firmware [18 APR 2016] | Gecko (20151106) Firmware [13 NOV 2015]


Post Reply 
Let's Start - Open the Firmware Image
12-09-2014, 12:08 PM (This post was last modified: 12-09-2014 12:24 PM by schumaku.)
Post: #1
Let's Start - Open the Firmware Image
Different form other mainstream Android devices, the firmware images are packaged in a special format for the low-cost Rock Chip stuff. That's OK - but disappointing the vendor does not publish any information or references.

After wasting a lot of time with a lot of well-meant junk from the net. I've ended up here (this has dependencies on openssl-devel and crypo-devel)

# git clone https://github.com/rk3066/rk-tools.git
Cloning into 'rk-tools'...
remote: Counting objects: 56, done.
remote: Total 56 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (56/56), done.
Checking connectivity... done.
# cd rk-tools/
# make
make: Warning: File `Makefile' has modification time 4262177 s in the future
gcc -g -O2 -DUSE_OPENSSL -o afptool afptool.c -lcrypto
gcc -g -O2 -DUSE_OPENSSL -o img_maker img_maker.c -lcrypto
gcc -g -O2 -DUSE_OPENSSL -o img_unpack img_unpack.c -lcrypto
gcc -g -O2 -DUSE_OPENSSL -o rkkernel rkkernel.c -lcrypto
gcc -g -O2 -DUSE_OPENSSL -o rkcrc rkcrc.c -lcrypto
make: warning: Clock skew detected. Your build may be incomplete.

# cd /home/user/chameleon/
# ls
update_open_hour_chameleon_android_4.4.2_20141119_1.0.7.zip
# unzip update_open_hour_chameleon_android_4.4.2_20141119_1.0.7.zip
Archive: update_open_hour_chameleon_android_4.4.2_20141119_1.0.7.zip
inflating: update.img

# /mnt/git/rk-tools/img_unpack update.img update_unpack.img
rom header code: 1060000
rom version: 4.4.2
build time: 2014-11-19 17:11:51
chip: 80
checking md5sum....OK

# /mnt/git/rk-tools/afptool -unpack update_unpack.img 107
Check file...OK
------- UNPACK -------
package-file 0x00000800 0x0000029F
RK3288Loader_uboot_V2.17.02.bin 0x00001000 0x0005A14E
rk3288-3.10-uboot-data1G.parameter.txt 0x0005B800 0x000005C0
Image/misc.img 0x0005C000 0x0000C000
Image/kernel.img 0x00068800 0x0053DE0C
Image/resource.img 0x005A6800 0x0001C600
Image/boot.img 0x005C3000 0x00145D8B
Image/recovery.img 0x00709000 0x0097C000
Image/system.img 0x01085800 0x213C3000
Image/vendor.img 0x22449000 0x012F4C00
RESERVED 0x00000000 0x00000000
update-script 0x2373E000 0x000003A5
recover-script 0x2373E800 0x0000010A
UnPack OK!

From here, standard Android image exploration.

Have not tested re-building an image using the reversed process.

Please note: In this example I'm working with the _update_ image, not the SD Card image.

As expected, the same process does _not_ work to unpack, modify, and re-create a full SD image: We expect the vendor to publish a workable process ASAP.
Find all posts by this user
Add Thank You Quote this message in a reply
[+] 3 users say Thank You to schumaku for this post
12-09-2014, 03:51 PM
Post: #2
RE: Let's Start - Open the Firmware Image
Yes and that they make only one partition, so that we only have one BIG storage on our SD-Card.
Find all posts by this user
Add Thank You Quote this message in a reply
[+] 1 user says Thank You to AmigaWolf for this post
12-09-2014, 06:08 PM
Post: #3
RE: Let's Start - Open the Firmware Image
Let's see what we will be able to change. Just strange seeing the forum amnins open a 3rd party firmware forum before providing anything required. My time and "criminal" energy is limited to reverse engineer what Rock Chip and Cloud Media does not want to document, to implement, and to share with the customers and the Open Source community. For now - all vendors listed in thus post are suspect criminals....
Find all posts by this user
Add Thank You Quote this message in a reply
[+] 2 users say Thank You to schumaku for this post
12-10-2014, 12:24 AM
Post: #4
RE: Let's Start - Open the Firmware Image
after you ran afptool -pack

did you run img_maker -rk32 ?
Find all posts by this user
Add Thank You Quote this message in a reply
12-10-2014, 05:20 AM
Post: #5
RE: Let's Start - Open the Firmware Image
This is the steps we use to generate bootable SD Card image from update.img.

http://wiki.openhourlab.com/index.php/Co...D_Card_Img

Hope this helps.
Find all posts by this user
Add Thank You Quote this message in a reply
12-10-2014, 07:47 PM
Post: #6
RE: Let's Start - Open the Firmware Image
Seems to be a slow teething process. Subject is "Open the Firmware Image" ... packaging follows later.

How can we unpack the provided initial install SD card image? Or can you provide initial installation images as held in the SD Card image and packed using the SdiImageTools please?

Thanks for providing another colored stone for the mosaic anyway - this might help in the future. A long way to go! For now we expect nothing more then a documented way to unpack your image, an access to the open source repository holding the code for 1.0.7 (as released, available in the Internet ...).
Find all posts by this user
Add Thank You Quote this message in a reply
[+] 1 user says Thank You to schumaku for this post
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  OHC not stable - best firmware version? canaan 5 517 05-15-2017 04:03 PM
Last Post: canaan
  open hour chameleon help donkie25 2 1,202 04-21-2016 11:32 PM
Last Post: chris57
  Two questions / Which Firmware and Sky Go App adamdb 1 1,119 11-29-2015 12:46 AM
Last Post: chris57
Information Chameleon firmware 1.0.27 and 1.0.33 - My feedback (includes bugs and suggestions) GFORCE100 4 2,319 11-24-2015 08:39 PM
Last Post: Willem55
  What are the dimensions of the Open Hour Chameleon ? Rambler 3 2,772 11-23-2015 08:44 PM
Last Post: GFORCE100
  when going out a new firmware? nickjack-pt 1 1,292 11-23-2015 08:33 PM
Last Post: GFORCE100
  Yikes New Open Hour grimmace92 25 9,818 09-17-2015 11:51 PM
Last Post: chris57
  Open Hour (and RockChip) Android Open Source - git schumaku 11 9,834 08-21-2015 11:17 AM
Last Post: Willem55
  My New Use for My Open Hour Kyocero 18 7,642 08-01-2015 11:05 AM
Last Post: chris57
  Displaying full 4k still image? ferrywd 4 2,249 01-27-2015 09:02 AM
Last Post: Willem55

Forum Jump:


User(s) browsing this thread: 1 Guest(s)