This NOT MY Work.....
Thanks to nathanpc
This app will let you easily edit your Android's build.prop file using a intuitive interface.
I'm not responsible for any problem caused by editing the build.prop file.
main page here:http://forum.xda-developers.com/showthread.php?t=1479703
Requirements: This app is compatible with 2.2 or newer and of course needs root access to write to your Android's /system directory.
Related
Hey guys...heres the APK manager v4.9 by daneshm90.....its an easy way to edit apks......
So i have written a simple script to ease the process of editing apks. Got a lot of downloads so thought its in demand
Whether you're doing basic image editing or editing the smali or xml files, on average u have to use (Brut.all or JF's smali/baksmali) awesome tool to extract the apk, edit it, then sign the apk and then adb push/install it. This process is quite tiresome if you are testing a method that needs fine tweaking.
This script should make the process a LOT smoother.
Theres an option of compiling/signing/installing all in one step
Thanks:
Goes to Brut.all for his awesome tool.
Goes to JF for ofcourse, smali/baksmali
Goes to farmatito for porting this script to linux
Features:
- Extract, Zip apk's.
- Optimize pngs (ignores .9.pngs)
- Zipalign apks
- Sign apks
- Push to specific location on phone
- Incorporates brut.all's apktool
- Pull apk from phone into modding environment.
- Batch optimize apk (Zipalign,optipng,or both)
- Quick sign an apk (Batch mode supported)
- Batch Ogg optimization
- Compression level selector (monitor status above menu)
- Batch install apk from script (option 16)
- Logging on/off has been removed. Instead a log.txt is created which logs the activities of the script organized using time/date headers
- User can change the max java heap size (only use if certain large apks get stuck when decompiling/compiling apks) (Option 19)
- Improved syntax of questions/answers
- Error detection. Checks if error occured anytime u perform a task, and reports it
- Read log (Option 20)
- U can now set this script as ur default application for apks. When u do, if u double click any apk it will install it for u.
- Supports batch installation, so if u drag multiple apks into the script (not while its running) it will install them all for u. U can ofcourse drag a single apk as well
- Added framework dependent decompiling (For non propietary rom apks). (Option 10). Checks whether the dependee apk u selected is correct.
- Allows multiple projects to be modified, switch to and from.
- Allows to modify system apk's using apktool but ensures maximum compatibility in terms of signature / manifest.xml
- Stuff i forgot i guess
Instructions (Windows):
- Place apk in appropriate folder (Any filename will work, if running for first time folders will not be there, you must run and then the folders will be created)
- Run script
- Minimize the script
- Edit files inside the project folder
- Maximize the script
Instructions (Linux):
- Place apk in appropriate folder (Any filename will work, if running for first time folders will not be there, you must run and then the folders will be created)
- Open terminal and change-directory to apkmanager (Easiest way is to type "cd ")
- Chmod 755 Script.sh
- Chmod 755 all files apps inside other folder (thanks for the tip bkmo )
- Run script by typing ./Script.sh
- Minimize the script
- Edit files inside the out folder
- Maximize the script
Requirements:
Java
Adb
Future Improvements:
- Manage multiple simultaneous apk edits (choose which apk to extract/build)
- Option to optimize the apks
- Option to adb push to user defined location
- Other stuff i dont know yet.
Windows (v4.9): Download Here
Linux (v4.3): Download Here
Here's the video!!
Got problems ?
1. Make sure your path has no spaces
2. Your filename has no wierd characters
3. Java/adb are in your path
4. It's not a proprietary rom's apk (aka Sense,Motorola,Samsung) (If u are, then use option 11 and drag the required framework, eg com.htc.resources, twframework-res...etc)
5. It's not a themed apk (if it is, expect .9 png errors, use as close to stock as possible)
6. Look at the log to know whats happening
7. If all else fails, post as much info as possible and we will try to assist you.
If U like my post, press the Thumbs Up button, i.e, Thank Me!
Bad download link. Please fix?
Please download to mediafire or multiupload
thanks
actually its not death214 link or project..and all thread he started was project by others and he just copy and paste..i remember u've been scolded by owain becoz of this,right death?=)
please upload files to other site.i cant download from rapidshare.
change link
Please click here:
http://lmgtfy.com/?q=apk+manager+xda
Nice. Rapidshare link working flawless.
Here is the compatibility file to add in to the kitchen. Here is also the new updated SU files to give root to the ROM. Here is also a plugin to add "Ad Free Hosts"
Unpack the folders withing the "Kitchen" folder to your root folder. Allow it to overwrite the files. It will add the stuff I specified.
Hopefully it all works and you guys can get started!
Credits to:
dsixda for making the kitchen
Chainfire - for his SuperSU files
Like many of you, I like to keep my Android system rootless and true to stock as much as possible. However, I like to be able to enjoy the native support of layers for better look n feel. I wrote the script attached to help me with it however, it doesn't come easy without root access. There are some work cut out for you, read below.
Prerequisites:
Have extracted theme from layers theme app from Play Store. No, I'm not talking about the main theme app which is used by Layers Manager. Rather, it's the apks that go into the /vendor/overlay. I tried to extract respective apks out of the main one without using Layers Manager. However, my attempts yielded no success as I'm getting FCs all over, so I must be missing something. I current have a Nexus 9 which is rooted with Layers Manager, I use N9 for testing out and bring the /vendor/overlay/*.apk onto my N6P under /sdcard for my script to process. If you know of a better way, by all means share.
Of course, kernel which support INIT.D.
TWRP installed for root access via recovery, a MUST.
Busybox installed via flashable zip
Install:
- Download the script attached
- Rename .txt to .sh
- Have all extracted themed apks in one directory. For instance, I like fa and art layers, so my directory on sdcard as such /sdcard/0flash/layers/fa/fa_*.apk
- Change up the first few lines to match your environment
- Boot into twrp, mount /system if needed
- Drop the script into /system/etc/init.d
- chmod 755 /system/etc/init.d/01layersmanager.sh
- Create a file named ".current_theme" in /sdcard/
- In the above file (.current_theme), put the name of theme you want init.d to install. Example, if I want to install "fa" then I'll just have a line of text fa in it (same goes to art, coalesce,etc). IMPORTANT: no trailing new line.
- Reboot and test it out
- If theme successfully installed, you'll see it.
- Also, the /sdcard/.current_theme file will be updated with "current" to avoid theme installation on next reboot if you don't want to install new themes.
Troubleshoot:
See /sdcard/debug.txt for info. If you want additional information dumped, edit the init.d script to echo out more.
O bio hnki
vboyz103 said:
Like many of you, I like to keep my Android system rootless and true to stock as much as possible. However, I like to be able to enjoy the native support of layers for better look n feel. I wrote the script attached to help me with it however, it doesn't come easy without root access. There are some work cut out for you, read below.
Prerequisites:
Have extracted theme from layers theme app from Play Store. No, I'm not talking about the main theme app which is used by Layers Manager. Rather, it's the apks that go into the /vendor/overlay. I tried to extract respective apks out of the main one without using Layers Manager. However, my attempts yielded no success as I'm getting FCs all over, so I must be missing something. I current have a Nexus 9 which is rooted with Layers Manager, I use N9 for testing out and bring the /vendor/overlay/*.apk onto my N6P under /sdcard for my script to process. If you know of a better way, by all means share.
Of course, kernel which support INIT.D.
TWRP installed for root access via recovery, a MUST.
Busybox installed via flashable zip
Install:
- Download the script attached
- Rename .txt to .sh
- Have all extracted themed apks in one directory. For instance, I like fa and art layers, so my directory on sdcard as such /sdcard/0flash/layers/fa/fa_*.apk
- Change up the first few lines to match your environment
- Boot into twrp, mount /system if needed
- Drop the script into /system/etc/init.d
- chmod 755 /system/etc/init.d/01layersmanager.sh
- Create a file named ".current_theme" in /sdcard/
- In the above file (.current_theme), put the name of theme you want init.d to install. Example, if I want to install "fa" then I'll just have a line of text fa in it (same goes to art, coalesce,etc). IMPORTANT: no trailing new line.
- Reboot and test it out
- If theme successfully installed, you'll see it.
- Also, the /sdcard/.current_theme file will be updated with "current" to avoid theme installation on next reboot if you don't want to install new themes.
Troubleshoot:
See /sdcard/debug.txt for info. If you want additional information dumped, edit the init.d script to echo out more.
Click to expand...
Click to collapse
Yt? Bird :
Sent from my Nexus 6P using XDA-Developers mobile app
Welcome to SuperR's Kitchen Donate version!
This thread is intended to organize release posts. All discussion regarding this kitchen can be found in the thread linked below.
[ Windows / Linux / Mac ][DONATE] SuperR's Kitchen (v3.2.2.2 - 10-13-2021)
Disclaimer: I am not responsible for anything bad that may occur from the use of this kitchen, but I will take all the credit you can give me if it works for you :D Please read the troubleshooting in post #4 of the standard kitchen thread...
forum.xda-developers.com
v3.0.0.1
Changes:
Download and extract Android Image Kitchen (Linux) directly from the XDA thread.
Fixed extracting tar.gz files.
Fixed crash if the main tools download/extract fails.
Fixed crash in Linux when updating the kitchen launcher.
Fixed crash when running the updater if there is no update available.
Added logging to img extract operations.
Fixed crash if Java 8 is not installed on Linux.
Added check for proper java installation on Windows.
Fixed language files other than English.
v3.0.0.2
Changes:
Fixed extracting Pixel firmware.
v3.0.0.3 (Donate version)
Changes:
Fixed custom zips on Pixel devices.
Removed attempts to pip install packages from within the kitchen.
Added logging to adb operations.
v3.0.0.4
Changes:
Require kitchen restart after updating.
Fixed duplicate unmount commands in updater-script when extracting extra img files.
Fixed some language file checks from crashing.
Added official Windows launcher (superr.exe).
The kitchen should install psutil (win/linux) and colorama (win) packages now if they are not already installed.
Thanks to @Xennet for the launcher idea. It makes running the kitchen in Windows a lot easier
NOTE: You should restart the kitchen manually after the update. This will be the last time you will have to remember on your own
v3.0.0.5
Changes:
Fixed Windows kitchen trying to update the Linux launcher.
Fixed cyfile errors.
Fixed system.img.ext4 not being renamed automatically if not in an archive.
Added dialog informing we are getting the plugin list when installing a plugin.
Check for and show error message when trying to run Bash plugins in Windows.
Remove all set_metadata lines with a context of "?".
Add all files in /system/bin to the updater-script.
edit: I forgot to reset the language file in this update, so if you update you will get an error when you try to install a plugin.
Easy fix after update (fresh installs do not need this):
Misc tools >> Reset language - After restart no more error
v3.0.0.6
Changes:
Hopefully fixed crash after signing zips when checking for update-binary script.
Updated Imgextract.exe to 1.3.7.
v3.0.0.7
Changes:
Ignore commented lines in build.prop.
Do not create set_metadata lines for files/directories that do not exist.
Do not use fstab with nodata in the name.
Removed duplicate /system/vendor/firmware set_metadata line.
Fixed tar creation for future use.
v3.0.0.8
Changes:
Minor improvement to set_metadata generation in Windows.
Fixed Android O rom not building due to lack of xbin.
v3.0.0.9
Changes:
zipalign - check to make sure files exist before renaming and record in main.log.
Fixed assert getting broken when building rom.
Fixed line endings in updater-script when running in Windows (thanks to @chevycam94 for pointing it out).
NOTE: You may need to change perm types to something else and back to whatever you want to get the line endings sorted out. Fresh extract will all be good now
NOTE2: If you go to ROM Tools >> Asserts Menu >> Reset asserts to default you will get your assert back to normal if it was broken.
v3.0.1.0
Changes:
Fixed crash when choosing main menu from root zip options menu.
Fixed crash when getting by-name through adb.
v3.0.1.1
Changes:
Fixed crash in Windows when checking for app_chimera at the start of deodexing N and O.
Fixed crash when finishing deodex on M and L.
Fixed crash and show error message when entering the wrong syntax for custom asserts.
Fixed boot/AIK still being part of the repo and causing Windows tools install failure after resetting tools and boot extraction failure on Linux.
Fixed crash removing knox in Windows.
Fixed crash deleting plugins if example does not exist.
Heapsize errors now return you to heapsize options instead of Misc Tools.
Added confirmation when deleting projects.
Tried to fix META-INF1 remaining after builing rom.
Thanks to @chevycam94 for testing like a mad man
v3.0.1.2
Changes:
Fixed logs crash when check for updates on start is enabled.
v3.0.1.3
Changes:
Change root status to rooted when adding Magisk using the plugin.
v3.0.1.4
Changes:
Display root type instead of Rooted.
Fix error during deodex cleanup on L and M.
Fix crash when removing knox.
v3.0.1.5
Changes:
Disable sepolicy-inject root method for Windows.
Fixed sepolicy-inject root method for Linux.
Fixed some debloat/knox checks.
Updated smali/baksmali to v2.2.1.
v3.0.1.6
Changes:
Fix crash when signing zips that use an update-binary script in Windows.
Log zip signing in sign.log.
Fixed update-binary conversion on roms that do not use by-name.
Make a copy of *_statfile.txt after extracting img files in Windows.
Add *_statfile.txt to support zip.
Add META-INF directory to support.zip.
Fixed Downloading/installing screen that disappeared.
v3.0.1.7
Changes:
Fixed manually signing zip when there are more than one to choose from.
Added ability to convert all flashable zips to update-binary script when building.
Added per-project option in Misc Tools for update-binary script - Always convert, Never convert, Ask every time.
Added check for delete_recursive when converting to update-binary script.
Fixed mount command not getting converted to update-binary script if rom does not use by-name.
NOTE: The default of the new update-binary conversion switch is "Ask every time". Remember, this is per project so you will need to change it for all projects if you want it changed globally.
v3.0.1.8
Changes:
Windows: Use 7-zip (included) to extract img files instead of Imgextractor.
Windows: Fixed missing symlinks in updater-script.
Windows: Fixed many file contexts not being set correctly.
Windows/Linux: Fixed system/SYSTEM on devices that use SYSTEM.
Linux: Do not create metadata lines for symlinks.
I think this will fix most of the flashing problems. Let me know how it goes
WINDOWS NOTE: It is important that the tools get updated. The updater should take care of it, but if you get errors that 7z is not found, go to Misc tools > Reset tools.
IMPORTANT: Start your rom fresh and extract from system.img again. Make sure you delete 00_project_files directory if you are reusing an existing project.
v3.0.1.9
Changes:
Windows: Fixed b key press not being recognized.
Added a Back option to the root method options.
Only allow key presses that correspond to menu options.
Fixed project name adding an extra superr_ when creating new project from the project selection menu.
Set permissions of configure.sh to 777 instead of /tmp to 755.
Theming Stock Android 9 devices using Vendor Overlay app method
Effortlessly working on Asus Zenfone Max Pro M1 device.
Requirements :
Near Stock Android device with OS version 8 or 9.
Root (Magisk Systemless will support)
Es File explorer or similar root file manager
A terminal emulator app
Working :
overlay folder inside vendor folder is where the overlay apps are found which are designed to redirect the paths of the files or the commands inside the app (when system is calling them during boot).
ie; when the Android system reads the files or commands in system ui app or android system app the System will also check on vendor overlay folder for apps that provide replacements.
These replacement rules or files are then pasted over the rules provided by the System apps.
Hence theming is done using the overlay apps.
How to do:
all Informations and terminal emulator commands are found in txt files inside zip. read it properly after unzipping.