Guest black_dez Posted November 28, 2010 Report Posted November 28, 2010 Tell me please, with what program can extract the binary firmware Acer Liquid. I could not find anything. In advance, thank you.
Guest Andrea1Liquid Posted November 28, 2010 Report Posted November 28, 2010 The Acer Liquid Bin's format is a proprietary format made by Acer, so the way to extract them is not public.
Guest Dario93 Posted November 28, 2010 Report Posted November 28, 2010 Tell me please, with what program can extract the binary firmware Acer Liquid. I could not find anything. In advance, thank you. +1 on what said by Andrea,but if you want a specific file,we have dumps,so i can upload it for you
Guest black_dez Posted November 28, 2010 Report Posted November 28, 2010 I wanted to learn how to make their firmware, so I think that can be extracted from a binary file. Then tell me, why should you start?
Guest Dario93 Posted November 28, 2010 Report Posted November 28, 2010 I wanted to learn how to make their firmware, so I think that can be extracted from a binary file. Then tell me, why should you start? Well,if you want to make a Custom ROM,you need a Kitchen like this : http://forum.xda-developers.com/showthread.php?t=633246 Follow the instructions,and if you want you can use as base my Dario93's ROM v1.6,that's very similar to an Acer firmware. If you need more help,we can use Gtalk or something like that :P
Guest Harness Posted November 28, 2010 Report Posted November 28, 2010 Also; look up "Avabox". It's an awesome tool kit for all things linux. To extract .bin files, start the tool, and as soon as you click start before it does anything to your phone yank the USB out, the bin will be in a folder like SDCAAPZ or something like that wherever your .bin file was. If you don't want to do that, install the phone, and do a nandroid backup from Malez right away.
Guest Borkata Posted November 29, 2010 Report Posted November 29, 2010 I think .bin files are just binary merged the separate files. So using HEX editor you can find the starting point of each separate file and copy it. For example system.img can be extracted and then you can binary copy all file together with modified system.img :P (maybe this is what mcboy is doing to make preloaded bin).
Guest Harness Posted November 29, 2010 Report Posted November 29, 2010 (edited) I think .bin files are just binary merged the separate files. So using HEX editor you can find the starting point of each separate file and copy it. For example system.img can be extracted and then you can binary copy all file together with modified system.img :P (maybe this is what mcboy is doing to make preloaded bin). I'm curious to know about this. I'd be willing to try it, I just don't know what I'd be looking for, although it wouldn't be hard to find out. Edit: I'll try it at some point today. Edited November 29, 2010 by Harness
Guest black_dez Posted November 29, 2010 Report Posted November 29, 2010 (edited) Thank you all for the help, but I have a problem with unpacking the ramdisk. Displays the following gzip: .. / boot.img-ramdisk.gz: not in gzip format Used to extract the script split_bootimg.pl and kitchen with XDA. Boot.img file was obtained using nandroid Edited November 29, 2010 by black_dez
Guest Dario93 Posted November 29, 2010 Report Posted November 29, 2010 Thank you all for the help, but I have a problem with unpacking the ramdisk. Displays the following Used to extract the script split_bootimg.pl and kitchen with XDA. Boot.img file was obtained using nandroid Try this: http://android-dls.com/wiki/index.php?titl...ack_Boot_Images :P Hope it helps, Dario
Guest Piter1225 Posted November 29, 2010 Report Posted November 29, 2010 I think .bin files are just binary merged the separate files. So using HEX editor you can find the starting point of each separate file and copy it. For example system.img can be extracted and then you can binary copy all file together with modified system.img :P (maybe this is what mcboy is doing to make preloaded bin). Could be true. for 4.002.14.EMEA.GEN1_A22F_A_256.bin: boot.img starts at offset: 18960BC lenght: 26B454 if we compare this part of bin with extracted boot.img to /SDCAPPZ we can see that they are identical, so nothing easier than just copy - modify - paste same goes for system.img starts at offset: 1B01510 lenght: 9706154 also identical to extracted system.img
Guest tmp_do Posted November 29, 2010 Report Posted November 29, 2010 do not foget about encryption, i think that binary anal-signed. we can easy extract ant pack it, but couldnt flash
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now