Hi, I made a flashable zip but i need it to be able to edit some lines in the build.prop and I would like to delete some lines in the build.prop from the recovery, not manually... I have tried several scripts, but none works, thanks
Related
Hey guys
So I have messed with my last android phone and pulling/pushing different APKs to mod/theme them. But how could I make my changes to say.... framework-res.apk into a flashable zip file that can be flashed from recovery? Thanks!
Unzip and you can edit the pngs
Use 7Zip, WinZip, ect. to re zip it
Hello - I am trying to add 'Reboot' option to Power Menu by modifying the following files - framework-res.apk, framework.jar, and android.policy.jar file. I was successfully able to add additional values to the xml file inside framework-res.apk and was able to merge my changes into the original .apk file and update in /system/framework without any issues. However, the smallest changes I make in framework.jar or android.policy.jar file breaks my system. It does not go into a Reboot Loop, but rather gives a message... Unfortunately, the <app name> has stopped working... or something like that... for almost all the apps and repeatedly.
I am on a Stock ROM of Micromax A110 (Mobistel T2). Do I need to DEODEX these .jar files first or do something else? I can't find the .odex files for these two jar files. I am not sure what I am doing wrong. Please help.
I can see some .odex files in my /system/app folder, but none in /system/framework. Is this normal? I am sure I didn't do any deodexing.
GUIDE: CREATING SMALL FLASHABLE ZIPs TO RESTORE FILES OR SETTINGS WITHOUT HAVING TO DO FULL NANDROID RESTORE
This will enable you to apply MODs without having to do a FULL NANDROID restore to recover if the MOD fails or if you don't like it
This brief guide will teach you how to create a flashable ZIP file that you can use to restore your phone to pre-MOD settings if you want to revert back or if the MOD simply does not work
WITHOUT having to do a full restore of your phone.
It is a very good idea to create these backup flashable ZIPs and keep them safe to recover from mishaps or when creating/testing MODs/themes.
*************************************************************************************************************************************************
As usual: Disclaimer: I am not responsible for any loss of data or functionality on your phone. To be 100% sure, always make a NANDROID backup if you are not 100% certain you can recover.
*************************************************************************************************************************************************
There are many reasons you might want to do this, for example when testing a MOD for another ROM that is similar to yours but not exactly the same (eg: Optimus G3 vs Cloudy G3) or when upgrading your ROM to a new version and wanting to re-apply old MODs.
There are many ways to get into boot loops or fail to boot, the biggest culprit being fonts installations, but include also bootanimations and others.
INSTRUCTIONS:
Part 1: general
1. Install ZIPme app from playstore
2. Find out which files are being modified by the MOD you are trying to apply, this is usually framework-res.apk, LGSystemUI.apk, lge-res.apk, but be aware that some MODs affect a lot of files. See part 2 for more details on how to do this.
3. If you are applying a font, don't worry, the FONTs section (see part 2) should cover all Fonts.
4. If you are applying a bootanimation, don't worry, the bootanimation section (see part 4) should cover all Bootanimations.
5. For every flashable ZIP you create you can test it straight away by booting into recovery and applying the zip file. There is no reason why it should not work.
Part 2: FONTS
1. In ZIPme select the following:
- ADD FOLDER: /system/fonts
- ADD FILE: /system/etc/system_fonts.xml
2. Create the flashable zip in an /sdcard location you can access from recovery
Part 3: MODs that affect framework-res.apk, LGSystemUI.apk or any other app
1. Find out which apks are being modified:
- You should of course read the OP (instructions for the MOD)
- The easiest way to find out modified apks is to download the MOD and open it: the zip file will contain either the apk files themselves or have directories with the names of the apks being modified.
- You can always ask the developer to make sure
2. Once you have a full list of files being affected you can create the flashable zip:
- in ZIPme, simply select "ADD -> File" for every file being affected
- If you have an ODEX ROM (.odex files are present) make sure you pick those too!
- save the flashable zip in an /sdcard location you can access from recovery
Part 4: Bootanimations
1. In ZIPme select the following:
- ADD FILE: /bin/bootnimation
- ADD FILE: /system/media/bootanimation.zip
- ADD FILE: /system/media/shutdownanimation.zip
2. Create the flashable zip in an /sdcard location you can access from recovery
Part 5: Other flashable files you should always keep handy
1. Always keep with you the following files for good measure: they don't take much space but can help recover from problems without having to fully restore from NANDROID backup
- original kernel from your ROM
- flashable bootloader (if you do not know what I am talking about then DON'T do it)
- flashable baseband (if you do not know what I am talking about then DON'T do it)
- flashable recovery image (TWRP, etc)
- "Xposed-Disabler-Recovery.zip": this is created by Xposed when you install it. It is located in the root folder of your sdcard. Copy it and put it somewhere safe.
- SuperSU: keep a flashable latest SuperSU with you to recover root
Any comments, suggestions, feedback are welcome
reserved
bloof said:
Any comments, suggestions, feedback are welcome
Click to expand...
Click to collapse
good work mate, i'm out of Thanks for today.
Just tried, nice and easy to use. Thank u
does it save paired bluetooth and wifi devices?
deleted
Can you use this to make a zip of boot.img and libs? Not finding how to do that. Thanks for any information.
matusala said:
does it save paired bluetooth and wifi devices?
Click to expand...
Click to collapse
Nope. It saves what you tell it to save.
The guide as it is only saves files, was meant for modding restore, not other stuff.
If you try mods a lot and don't like a certain theme or icon set you don't need to do a full nandroid backup and full restore because you changed 3 files in your mod.
countryfolk07 said:
Can you use this to make a zip of boot.img and libs? Not finding how to do that. Thanks for any information.
Click to expand...
Click to collapse
Not with what I wrote.
The app ZIPme can do a lot more than simple file recovery, but I am not an expert at flashable zips so can't comment on more advanced uses like buildprop etc.
I would certainly not write anything about boot images, way too likely to cause someone to screw up their phone....
Pick a flashable boot/libs zip file from somewhere and try to reproduce at your own risk.
Hi.
I have a XOLO-ONE [non-rooted] and recently updated it via the "software update" option in the system information tab of settings. It runs Lollipop 5.0.0.
I noticed that before updating, it showed a prompt saying "no update.zip found in root of memory card, download?" I found out that you can download the update.zip from xolo's official site. It was about 30 mbs.
Now, i wonder if i can edit it's contents(updater-script, apps, etc...) and apply the update to my phone?
I repeat, it is NON-ROOTED.
The zip file contains the following folders:
META-INF
PATCH
SIG
SYSTEM
scatter.txt [FILE]
type.txt [FILE]
There is no boot.img.
Has anyone tried it? Was it successfull? If yes then please write. Your opinions would be appreciated.
Yes you can do so and its possible flashing a update.zip using stock recovery.
You can edit and change apps amd do anything but remember to update any changes you have done in zip to updater-script carefulley. And set correct permissions to them
Peace
:good::laugh::victory:
Thanks man.
Uh, can tell me how to edit the build.props file?
It is stored as a .p file.
Yes why not opsn the file as a text file in any text editor either on amdroid or on pc.
Now you can change the following things.
1-- change the android version
ro.build.version.release=4.4.2
Edit the number to version you want
2-- change the screen pixel density
ro.sf.lcd_density=200
Edit the value to nearby values only.MY DEFAULT WAS 240 AND I CHANGED IT TO 200 AND IT LOOKS NICE.
3-- change the delvic heap value
dalvik.vm.heapstartsize=10m
dalvik.vm.heapgrowthlimit=68m
delvik.vm.heapsize=256m
Edit the values but only multiply the default values by 2. If any value after multiplying is mord than the ram of your device itself then do mot change the value.
4-- add these lines to the build.prop in end for display enhansment
video.accelerate.hw=1
debug.sf.hw=1
debug.performance.tuning=1
debug.egl.hw=1
debug.composition.type=gpu
After doing so save the file normallt.
Zip the folders and flash them again.
Peace
I would do that but.....
Yes, I would do that but the problem is that the file has a .p extension.
I did some research and found that it is a patch file created by using a program called BSDIFF ( or something like that). The installer-script processes that file by comparing it's checksum and patching the data into the existing file..
Now I'm not sure if creating a custom build. Prop. P file and updating my. Zip file with it will be okay. What if I get into a boot loop? My xolo isn't rooted either.
But, I'm not the expert.
So, tell me about your opinion. Is it safe?
Thank you for your help. ( for before & in advance )
no just name it as build.prop and nothing else. itd a property file and not a .p file.
simply place the build.prop in zip file with this name only. no other name OK.
and flash it.
but if you are rooted then just edit the original file in aystem folder and savf it there only. just open and edit and reboot to see effects.
peace
Sent from my SM-G355H using XDA Free mobile app
- Edit - Read post 2 first
I Deodexed my framework folder with Super R's kitchen and patched services jar file to enable signature spoofing for MicroG. The flashable zip should wipe your framework folder and replace it with the new one. I can't test it right now, but try it out if you want. If the flashable doesn't work, and you want to use it, just extract the zip and use file manager in recovery to delete your whole framework folder and copy the new one there, (probably a good idea to wipe dalvik/cache).
Note about deodexing - could possibly make certain aspect of the phone slower. Only thing I have noticed so far is longer boot time...
https://mega.nz/#!E58U2AJb!j0XIq0veM3XdxjMCvjBoOZwQFRIsz3cfvi-rbrSyCU0
Update - so I tried it, and it doesn't flash properly, (some error in the script), but I also found out that it's much more stable to just replace the services jar with the deodexed one, and leave the rest of the framework as-is. So if you want to use MicroG, just extract the services jar from the zip, and then use file manager in recovery to delete the current one, and also delete the 3 services files, (odex, vdex, and art), from /system/framework/oat/arm64.
Then you can flash MicroG...
Zip attachment in first post is a custom Magisk module that was made with smali patcher. It replaces services jar file with a patched one that is deodexed (see above for instructions)...