ok, ima try to make this short and sweet. Im attempting to extract the contents of system.img from an official samsung firmware using unyaffs2
this is quite literallly the FIRST time using my android skills since setting up my linux laptop.
ive done the following so far
running ubuntu 10 something
android sdk, eclipse
downloaded two versions of yaffs neither work as i would have expected.
now, trying to extract the system.img from this file (samsung note 3 kitkat official firmware)
https://doc-04-5g-docs.googleusercontent.com/docs/securesc/ha0ro937gcuc7l7deffksulhg5h7mbp1/met8j7ju751f78fpes2risgambd0mblc/1390788000000/16903193897035115666/*/0B84fZ-6xuKyyMmRMTHhjMldINDA?h=16653014193614665626&e=download
im running into this error
image size is not a multiple of 2048 64
it continues to extract the files saying each one has failed and then into the folder i specified there are a couple of files, none of which look recognizable or usable.
what am i doing wrong here?
DEVICE: LG REVOLUTION (VS910V6)
MY RECOVERY PARTITION IS GONE, BUT I DID FIND A ROM DUMP OF THE SHIPPING ROM FOR MY DEVICE. ITS A ZIP FILE. IS THERE SOME WAY THAT I CAN SOMEHOW CREATE A FLASHABLE ZIP FROM THE DUMP FILE TO BE ABLE TO FIX MY PHONE? MY PHONE IS PRETTY OLD. I HAVE TRACKED DOWN A HANDFUL OF DIFFERENT FILES FOR MY PHONE AND I WOULD HAVE FLASHED ANY OF THE OTHER POSSIBILITIES OF COMPATIBLE ROMS, FACTORY FIRMWARE, ETC. THE PROBLEM WITH THAT IS FOR EVERY FILE I FOUND THE DOWNLOAD LINK FOR, IT'S OUTDATED AND DOENS'T WORK ANYMORE. SO I'M HOPING THERE MIGHT BE A POSSIBILITY GOING THIS ROUTE.....? ANY SUGGESTIONS WOULD SURELY BE APPRECIATED!! :fingers-crossed:
Ok so i have searched online many times.. tried many tools i found.
I take it they are ext4 images ?
I mean the separate images in the stock firmware packages.
i especially would like to get at the fsg.mbn files..
if i look on the root fsg folder i think i see what is in the .mbn
i opened some with WinRar (packed .gz's) and i find more packed images (signed)
i believe those are the carrier config settings.
since i have had issues with my carrier connection being setup properly i have been investigating..
I am stuck using GSM when my phone should be using cdma.
and if i force the phone to use cdma it won't connect.
but if i restore the stock firmware on 5.0.2 then i have cdma back normal.
my carrier did not put out 5.1
so i have installed the US Retail.
tried many variations of modems.. no matter what i do only thing working is GSM
so i want to make my digging easier for getting at stock files.
having to install them onto my phone to get at them is dumb.
i'd rather just unpack my various firmware packages and compare etc..
any idea people ?
has any of you unpacked an .img (on WIndows)
Try this...
http://forum.xda-developers.com/showthread.php?t=2073775
Can I just delete APKs from an .img and then flash it?
I've got an Onda V96 3G tablet - a MediaTek 6582 based device. By default it comes with a lot of "interesting" APKs preinstalled - Chinese app stores etc.
I've downloaded (and flashed) the original firmware - which also contains the bloatware.
I've mounted the filesytem and can see an "app" folder with a bunch of APK and ODEX files.
Is it safe for me to delete the bloatware from the .img file, repack it, and then flash it onto my tablet? I'm using the SP Flash tool for Linux if that makes a difference. Thanks
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Downunder35m said:
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Click to expand...
Click to collapse
Thank you for this explanation, but the explanation of the video to better understand everyone
Will see if I can at least add some pics while working on Nougat.
Hello,
Thanks for you tutorial.
I have a h96 Pro+ and the last firmware was a .img file... (Link of the firmware : https://mega.nz/#F!d1tHVZgA!Qc0mAom7FBHT9HDv3rGtGQ )
Is there a good guy who can convert this .img to a .zip file please ?
A lot of users are asking for this, me too and if you can help me to do this it will be really cool and appreciate
Thank you,
Carmin.
Thanks for your explanation im trting to port 7.1.1 to my tv box and i have found one funcional the only troble is the wi fi drivers not working ill give it a try latter today
Sent from my SM-N9300 using Tapatalk