While preparing JB Style for XXLSJ I've seen that we needed a proper VRTheme templatefor the new partitions ( /preload ) in our new systems. This will probably change in the future as Samsung releases the final version... but meanwhile... you can use this template to build mods.
No need to replace the entire SystemUI for battery images. This is not my work, I just simply adapted the original template.
Source:
http://forum.xda-developers.com/showthread.php?t=1207017
http://www.villainrom.co.uk/forum/threads/about-villaintheme-system.4971/
Download:
http://depositfiles.com/files/6lj80t3aa
Crussader said:
While preparing JB Style for XXLSJ I've seen that we needed a proper VRTheme templatefor the new partitions ( /preload ) in our new systems. This will probably change in the future as Samsung releases the final version... but meanwhile... you can use this template to build mods.
No need to replace the entire SystemUI for battery images. This is not my work, I just simply adapted the original template.
Source:
http://forum.xda-developers.com/showthread.php?t=1207017
http://www.villainrom.co.uk/forum/threads/about-villaintheme-system.4971/
Download:
http://depositfiles.com/files/6lj80t3aa
Click to expand...
Click to collapse
Thanks for sharing this Mods for Create new things.
dark_zhero said:
Thanks for sharing this Mods for Create new things.
Click to expand...
Click to collapse
i tried using it but went into boot loop..
all system\app files including systemui.apk which were before in systems\apps will be now in preload\symlink\system\app ??
or will the systemui.apk reside somewhere else ??
and the folders with the modified pngs will be named like systemui.apk ?? with the the extension ??
Thanks
xinfinityoO said:
i tried using it but went into boot loop..
all system\app files including systemui.apk which were before in systems\apps will be now in preload\symlink\system\app ??
or will the systemui.apk reside somewhere else ??
Click to expand...
Click to collapse
exactly... in deodexed ROMs they're located in there ( preload\symlink\system\app ). If I recall correctly, in odexed ( stock fro sammobile source ) they're still on system/app.... check where they are before patching using a root file manager.
xinfinityoO said:
and the folders with the modified pngs will be named like systemui.apk ?? with the the extension ??
Thanks
Click to expand...
Click to collapse
you have to recreate the folder structure of the file you're trying to mod
SystemUI.apk / res / drawable-hdpi ( for example )
Check one of my mods to see what I mean
Crussader said:
exactly... in deodexed ROMs they're located in there ( preload\symlink\system\app ). If I recall correctly, in odexed ( stock fro sammobile source ) they're still on system/app.... check where they are before patching using a root file manager.
you have to recreate the folder structure of the file you're trying to mod
SystemUI.apk / res / drawable-hdpi ( for example )
Check one of my mods to see what I mean
Click to expand...
Click to collapse
i did as what you have said ..but boot loop ..will check the systemui.apk location and try again
thanks
xinfinityoO said:
i did as what you have said ..but boot loop ..will check the systemui.apk location and try again
thanks
Click to expand...
Click to collapse
are you using .9.png files? They must be compiled before so you can use them
Crussader said:
are you using .9.png files? They must be compiled before so you can use them
Click to expand...
Click to collapse
Is that so? I never knew that
So quick question... If I change the hue of. 9 image I can't drop straight into an apk? It has to be recompiled 1st? If that's the case, that explains a lot. Thanks for the heads up on this. Every time I did this previously the image got distorted so i gave up touching them and just changed normal pngs.
How do i edit my build.prop to make it at&t again? im using a verizon multicarrier rom and people said select verizon then install it, chane the framework res apk and then edit the build.prop . How do i change t to AT&T?
Tyler.Boston1 said:
How do i edit my build.prop to make it at&t again? im using a verizon multicarrier rom and people said select verizon then install it, chane the framework res apk and then edit the build.prop . How do i change t to AT&T?
Click to expand...
Click to collapse
Make a nandroid.
Use root explorer or adb only to edit the build.prop (located in /system) and change your device values to:
ro.product.model=SAMSUNG-SGH-I747
ro.product.name=d2uc
ro.product.device=d2att
Reboot.
Hello!
I'll admit its very stupid of me to try edit build.prop without any backup. Please can anyone upload a flashable zip file of build.prop file of version 20d?
Thanks a bunch in advance!
DrGoat said:
Hello!
I'll admit its very stupid of me to try edit build.prop without any backup. Please can anyone upload a flashable zip file of build.prop file of version 20d?
Thanks a bunch in advance!
Click to expand...
Click to collapse
Here is the Build prop file
Thank you very much
Can someone pls help me? I've messed up my build.prop using texdroider and lot's of stuff isn't working atm. Keyboard is one of them, so restoring the original values is nigh impossible through the app. If someone could post a flashable zip file with the G4 original build.prop that would be awesome... or maybe help me get my original build.prop restored using ADB? Thx!
Have you tried changing it in twrp?
Yeah... ofcourse! Thanks for the tip, simply forgot about that...
This work is adapted from info that has been around for some time - originator unknown. So thanks to whoever did the original groundwork:good:
There are 2 files that need to be replaced - backup of originals is your responsibility
Unzip the files first - they are only zipped to allow upload to XDA.
File 1. powermenu gets copied into /system/media/theme/default overwriting the original
This file is common to all MIUI8 versions.
File 2. android.policy.jar gets copied into /system/framework overwriting the original
This file is compiled for each different MIUI version. I will add files for recent and popular versions with the ROM identifier added to the zip filename.
If you want this for a particular ROM, provide me with the version i.e. MIUI EU 61229 and the android.policy.jar from the ROM. No guarantees that I will do it of course
Sorry - I can not do it for odexed ROMs which will have around a 309 byte file size. This means original factory ROMs are out of the question.
MR, EU and SU versions are all de-odexed so no problems with them.
Can you add manual method to edit android.policy.jar?
works fine, thanks. (Es File Explorer won't work, so use Root Explorer)
Very useful!!! Thanks. No need to reboot.
Inviato dal mio Redmi Note 2 utilizzando Tapatalk
@vetriolo You don't need to reboot to see the new menu but you need to reboot to get the new android.policy.jar into dalvik.
@barni090 Why would ES File Explorer not work unless it hasn't got root?
@Dinolek Too much like hard work to write up a how to so I have attached the edited file that goes into android.policy.jar. It is advisable to do a file compare first because we are never sure what changes occur at every new version. So far, in what I have processed, the files start off identical.
I don't know, wasn't working, maybe some problems with my device.
The 8130 jar file plus powermenu doesn't work on my EU-8130. Before rebooting, you just get the 4 icons with no text, and, after rebooting, you get nothing at all (device just reboots if you hold the power button down for long enough). The original 8130 files are in the attached.
@DarthJabba9 Double-checked the original mod - it is correct. Haven't tested your installer but put the appropriate files in the appropriate places for you to try again.
jajk said:
@DarthJabba9 Double-checked the original mod - it is correct. Haven't tested your installer but put the appropriate files in the appropriate places for you to try again.
Click to expand...
Click to collapse
Installing your zip via TWRP did the job. But if the files are exactly the same, why wouldn't a manual installation work, but a TWRP install works?
DarthJabba9 said:
Installing your zip via TWRP did the job. But if the files are exactly the same, why wouldn't a manual installation work, but a TWRP install works?
Click to expand...
Click to collapse
Same here.. integrated this mod into ROMs and Stable 8.1.3.0 it's the only one that doesn't work. Pressing Tap to Recovery in Powermenu does nothing..
@Gyovany96 @DarthJabba9 I have re-uploaded the file for 8130 just in case there was some corruption - decompile -recompile is not 100% perfect for MIUI stuff. Try again on the fresh copy and see if that does the job.
jajk said:
@Gyovany96 @DarthJabba9 I have re-uploaded the file for 8130 just in case there was some corruption - decompile -recompile is not 100% perfect for MIUI stuff. Try again on the fresh copy and see if that does the job.
Click to expand...
Click to collapse
Now it works just fine ! Thanks again:good:
EU 61117 version attached
@gyovanny96 EU 7.2.9 version attached
MR 7550 version attached with added goodness. All debugging and logging of included services is disabled. Reboot may be slow as Dalvik rebuilds.
Remember to pick up the powermenu file from O.P and put it where it needs to be
7.3.16 EU + Spanish strings
Decompress powermenu.zip and replace in /system/media/theme/default
Replace android.policy.jar in /system/framework
↓See attachments↓
Deic said:
Decompress powermenu.zip and replace in /system/media/theme/default
Replace android.policy.jar in /system/framework
↓See attachments↓
Click to expand...
Click to collapse
I have created a flashable zip of this (and also of the stock files in case one needs to revert to stock). I am happy to post if anyone is interested.
7.3.23 EU
Remove .zip of powermenu.zip and replace in /system/media/theme/default
Replace android.policy.jar in /system/framework
↓See attachments↓
I will make a script or flashable zip to patch your android.policy.jar and powermenu, to not need to download patched ones by me (and I can rest xd)...
Deic said:
I will make a script or flashable zip to patch your android.policy.jar and powermenu
Click to expand...
Click to collapse
A script would be nice! :fingers-crossed:
@Deic Thanks for adding updates to this thread:good: