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
Related
Hey Guys,
I'm in need of some really n00b friendly advice.
When you flash a new ROM (i.e. CM9) in CWM the tutorials tell you to flash the file named Update.zip. My problem is that I can't seem to find one in the zip file I downloaded for my xperia mini.
I downloaded FXP131, and found the zip file to contain a boot.img, which will be the kernel. And 2 other folders named META-INF and System.
I know how to flash the kernel and expect it was just left in there for easy transportation.
But where in the world is 'update.zip'?
Am I meant to unpackage the kernel then re-zip the META-INF and System folder and then call that 'Update.zip'?
I've flashed roms for some of my other devices before, but they've always used flashtool or samsungs flashtool.
Please help me guys, I don't like sounding this inexperienced
update.zip
I'm wondering if the ROM I am trying to flash needs to be renamed as update.zip in order to work. It is krook's v.6 of JB for the Lenovo K1 tablet. Since the download site has to distinguish between wifi and 3G versions, as well as nvflash versions there are a number of different filenames, however does it need to be renamed after putting it on my SD card?
Generally speaking "update.zip" is used as a generic name. For example the update.zip I just flashed is actually named "rascarlo_maguro_ota_2012-11-01.zip". When you flash a custom ROM in a custom recovery you should be able to browse & flash whichever file you need.
The FXP131.zip file that contains the boot.img and 2 other folders named META-INF and System is the "update.zip"
solved
My problem was an incomplete download. I compared file sizes, and checked md5sums and determined the correct ROM and it is now in the middle of finishing the upgrade/optimization process.
Thx
I am looking for ways that i can capture an android rom (.img file) and restore it to other same devices by using Rockchip Batch Tool 1.7
Here is my situation:
We have lot of android devices need to be deployed (MK 902). The original rom was 4.2 and I use Rockchip Batch Tool 1.7 to reload a rooted 4.4.2 img file. then I installed some APPs we needed. I dont want to go through app installation on all devices. So I am looking for a way that i can capture the img file after all APPs installed, then later on i can only use that Rockchip Tool to restore my img into rest of devices, just like Windows image restore.
I did some researches but didnot find any easy way to do so. looks like i have to unpack the image, modify it then repack it again. ....... I dont know how to modify the img file so i am looking for an easy way to do this.
Anyone knows any App or easy way?
I'm using V7 MIUI rom, I downloaded V8 rom from miui.com (both of them are Chinese's rom). I find that I can copy apk files in "Data" folder and install it normally. But apk files in "System"--->"Data" and "Priv-Data" cant do like that. I cant install them like files in "Data" folder does, and I notice that those file have a folder in same directory, inside that folder have a ".odex" file.
So, i wonder that those file must be install in special ways? And How can I install them?
Thank you for my poor english.:good:
Those system apk files usualy need to be flashed. You could copy and paste them in in a ROM.ZIP you are currently using and install them via a recovery (TWRP or CWM).
How it is actually done I am not realy sure (no experience) but in theory it should work this way.
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
Hey all. Currently working on my Moto One 5G Ace. Bootloader unlocked, have achieved root.
However, since Android 10 has this messed up file system that does not allow any writing of the system files, I want to know what tool can I use to Unpack Super.Sparsechunk files and then repack them so I can flash them as stock via fastboot. All I want to do is delete the stock ringtones on this phone and replace them with my own .ogg files (as I've done on every Moto I've ever had). Thanks.
Use simg2img, then lpunpack to unpack it.