A custom recovery is a modified version of the stock recovery that includes several advanced features like taking backups, flashing files, partitioning file system and many more. A custom recovery is capable of flashing files with the .Zip extension, but not all the files with Zip format are flashable.
Have you ever thought, what makes these Zip files flashable and why don’t your podcast Zip won’t flash? Actually its a bit simple, the custom recovery identifies the updater scripts in the folder named META-INF of the Zip files which tell the recovery what to do. So if you’re interested in making your own flash-able Zip to flash files on your device, then simply follow our guide.
Create Flashable Zips for CWM/TWRP Recovery
Download the Sample Zip file for the flashing purpose →
Open the downloaded Zip file (don’t extract it). You will see the following folders:
META-INF
system
META-INF is the folder that contains the updater scripts. You will find these two files in the META-INF\com\google\android\ directory.
update-binary
updater-script
The Update-binary consists the source code of the actions to be performed according to the updater-script. We can edit the updater-script to define our own process, but to just flash the files the sample Zip is enough. So don’t tamper any of these two files.
Now the other folder we saw is the system folder. As you can see it is the System folder of the Android, so you can add any file of the System partition to this folder.
For instance, if you have edited the SystemUI.apk for a theme and now you want to flash it. So you have to add it to the system/app/ which means you have to create a folder named app and then paste the SystemUI.apk in it.
Similarly check the file paths in your Android device and add the files in their corresponding path by creating folders and sub folders in the process. You can add any proper file (flashing improper files may brick your device) in this system folder with proper names and paths.
As Android is Linux-based, everything is case-sensitive. So make sure of the Capital and Small letters of the file names and folder names which you’re adding to the system folder.
Once you add everything to the system folder, close the Zip transfer it to your device and flash it via a custom recovery.
That’s it, you’ve learned how to create your own flashable Zip for your mods and tweaks.
Create Flashable Zips for CWM/TWRP Recovery
Download the Sample Zip file for the flashing purpose →
Open the downloaded Zip file (don’t extract it). You will see the following folders:
META-INF
system
META-INF is the folder that contains the updater scripts. You will find these two files in the META-INF\com\google\android\ directory.
update-binary
updater-script
The Update-binary consists the source code of the actions to be performed according to the updater-script. We can edit the updater-script to define our own process, but to just flash the files the sample Zip is enough. So don’t tamper any of these two files.
Now the other folder we saw is the system folder. As you can see it is the System folder of the Android, so you can add any file of the System partition to this folder.
For instance, if you have edited the SystemUI.apk for a theme and now you want to flash it. So you have to add it to the system/app/ which means you have to create a folder named app and then paste the SystemUI.apk in it.
Similarly check the file paths in your Android device and add the files in their corresponding path by creating folders and sub folders in the process. You can add any proper file (flashing improper files may brick your device) in this system folder with proper names and paths.
As Android is Linux-based, everything is case-sensitive. So make sure of the Capital and Small letters of the file names and folder names which you’re adding to the system folder.
Once you add everything to the system folder, close the Zip transfer it to your device and flash it via a custom recovery.
That’s it, you’ve learned how to create your own flashable Zip for your mods and tweaks.
>DOWNLOAD LINK
Credits :@SHIVAM
Credits :@SHIVAM
No comments:
Post a Comment