how to change Navigation Bar dpi? - Sony Xperia ZR

I Edit the framework-res.apk\res\values\dimens.xml but it has keep rebooting

a546109781 said:
I Edit the framework-res.apk\res\values\dimens.xml but it has keep rebooting
Click to expand...
Click to collapse
go here:
http://forum.xda-developers.com/showthread.php?p=40214768
it required the installation of Exposed framework first:
only root needed, works for locked odexed deviced, no need for cwm.
works for my device with stock 244.

No need of exposed framework.. just push the following apk to /system/vendor/overlay/ folder
I have used 28 dp, but decompile that and change to whatever you want

shardul_seth said:
No need of exposed framework.. just push the following apk to /system/vendor/overlay/ folder
I have used 28 dp, but decompile that and change to whatever you want
Click to expand...
Click to collapse
YES,
This was the best method ever thanks no need to deodexed and no need to touch framework-res.apk

sijav said:
YES,
This was the best method ever thanks no need to deodexed and no need to touch framework-res.apk
Click to expand...
Click to collapse
happy it worked, though i don't see the problem with xposed, it doesn't ruin anything and you can add new mods when they come up easely with no need to flash anything.

Related

[Q] Bootloop after editing a few XMLs?

So after decompiling framework-res.apk and editing statusbar.xml, statusbarextended.xml, and statusbarlatesteventcontent.xml I get stuck in a bootloop right after installing the ROM fresh from stock and a MC. So what could be the problem? Why would changing the text color of the statusbar cause a bootloop?
ih4ckback said:
So after decompiling framework-res.apk and editing statusbar.xml, statusbarextended.xml, and statusbarlatesteventcontent.xml I get stuck in a bootloop right after installing the ROM fresh from stock and a MC. So what could be the problem? Why would changing the text color of the statusbar cause a bootloop?
Click to expand...
Click to collapse
How did you decompile/recompile? When you recompiled, did you use the same filestructure?
Ex: /framework-res/res/drawable-hdpi instead of /res/drawable-hdpi
Did you keep the same lines and just edit the color codes? You need to give more info to let us know what you did. Any tiny mistake in editing framework-res.apk will result in a bootloop, so your case isn't diagnosable unless you tell us what you did.
.Candy said:
How did you decompile/recompile? When you recompiled, did you use the same filestructure?
Ex: /framework-res/res/drawable-hdpi instead of /res/drawable-hdpi
Did you keep the same lines and just edit the color codes? You need to give more info to let us know what you did. Any tiny mistake in editing framework-res.apk will result in a bootloop, so your case isn't diagnosable unless you tell us what you did.
Click to expand...
Click to collapse
I used apkmanager, decompiled, edited color codes only, recompiled, installed, bootloop and yes the filestructure is the same.
ih4ckback said:
I used apkmanager, decompiled, edited color codes only, recompiled, installed, bootloop and yes the filestructure is the same.
Click to expand...
Click to collapse
How did you install it. Using APK Manager? If so, that's probably the issue. I don't trust certain APK Manager options. To be safe, in the future you should only use it for decompiling, recompiling, and signing if necessary, never for re-install the APK.
Anyway, did you attempt to sign the file? framework-res.apk doesn't need to be signed, and if you do sign it, I believe it will create a boot-loop.
Also, when you recompiled it, did you go through the step that creates the "keep" folder where you delete the files that you edited? If not, then that's probably the issue. If you don't do that step, then your edited file will only contain the files that you edited. At least that's what I understand from my experience.
I copied the apk to my /system/framework folder within my custom rom and flashed the zip. I did sign the file. I'll retry without signing it and yes I did the keep step.
ih4ckback said:
I copied the apk to my /system/framework folder within my custom rom and flashed the zip. I did sign the file. I'll retry without signing it and yes I did the keep step.
Click to expand...
Click to collapse
dont sign system apks
Pirateghost said:
dont sign system apks
Click to expand...
Click to collapse
thats a good tip lol thanks I'll remember that next time I do any modding.

[Q] Kitchen - problem flashing

i have tried to modify the froyobylaszlo by removing a couple of system/app
and put my own apps
after that i tried to flash it but i had some errors im not familiar with
hope someone could help me out
im attaching the recovery.log files
EDIT: btw im a complete idiot hahaha... im just starting out
marchking said:
i have tried to modify the froyobylaszlo by removing a couple of system/app
and put my own apps
after that i tried to flash it but i had some errors im not familiar with
hope someone could help me out
im attaching the recovery.log files
EDIT: btw im a complete idiot hahaha... im just starting out
Click to expand...
Click to collapse
which apps did u place in system apps?
did u remove the apps fromm data/app as well?
maximo360 said:
which apps did u place in system apps?
did u remove the apps fromm data/app as well?
Click to expand...
Click to collapse
yeah i think only 1 app is there in data/app = gallery i think i removed that thinking that it was the gallery3d
i changed the launcher and a couple of things in the system/app
are there limitations of which apps that i could put there...
btw is it ok if i change the updater-script to update-script?
or i shouldnt have change that... the kitchen was requesting to change it
hey if you are only removing some apk's you dont need kitchen.. just unzip file.. take out what you want than re-zip and than Sign it! should be able to flash no problem
marchking said:
yeah i think only 1 app is there in data/app = gallery i think i removed that thinking that it was the gallery3d
i changed the launcher and a couple of things in the system/app
are there limitations of which apps that i could put there...
btw is it ok if i change the updater-script to update-script?
or i shouldnt have change that... the kitchen was requesting to change it
Click to expand...
Click to collapse
You should just do what LDrifta said if your still having problems.
OH and regarding the update-script, heres your answer straight from the op of the kitchen:
QUESTION: Why do I need to convert the ROM's updater-script to an update-script when using the kitchen?
The kitchen can only perform operations on an update-script. UpdateR-scripts are too complicated to check because there are so many combinations of parameters for every command and for different devices; plus they can be written in different formatting styles. Thus the kitchen converts them to update-script so that there is one universal method to modify any device's configuration. If we didn't convert the updater-script then it would take months of work to overhaul the dozens of scripts (plus doubling my work) to accept updater-scripts, which would really NOT make a difference in the end anyway and would likely slow down the kitchen due to extra checks made in the updater-script. So please do not request this again and again, there is no gain in doing it (I also don't have that much free time ...).
When you build the ROM you have the option of converting it back to an updater-script, or the kitchen will convert it automatically if it decides it's necessary. The conversion back to the original updater-script is near-perfect, as I have already spent months on the implementation to get it right.
QUESTION: I have converted my update-script to an updater-script, but after flashing I still have the original ROM on the device.
That means your updater-script did not have the proper mount points defined for the system (and/or data) partition. Refer to this post for more info.
QUESTION: My device only supports ROMs with the updater-script/update-binary files but not the update-script
If you extract a ROM that contains an updater-script, then the kitchen will ask you if it should convert it to an update-script. You *must* use an update-script while customizing the ROM, as the kitchen is not capable of modifying updater-scripts. When you are ready to build the ROM, though, you will need to convert it back to an updater-script if the device requires it. Use the option in the Advanced menu to convert update-script to updater-script, or else the kitchen will ask you to convert it while building the ROM.
Click to expand...
Click to collapse
ldrifta said:
hey if you are only removing some apk's you dont need kitchen.. just unzip file.. take out what you want than re-zip and than Sign it! should be able to flash no problem
Click to expand...
Click to collapse
ok... so im also adding a few apks at the system/app what you suggested will that still work?
btw
just to clarify, i unzip, then remove the apks
then zip it again
then i put it in the kitchen to get signed?
marchking said:
ok... so im also adding a few apks at the system/app what you suggested will that still work?
btw
just to clarify, i unzip, then remove the apks
then zip it again
then i put it in the kitchen to get signed?
Click to expand...
Click to collapse
ok well depending on what apk's you are putting in.. if they are system required like a sense app.. it wont work on a froyo base rom.. but if its something like superuser or mail or something and is compatible with your rom than put it in system/app folder.. if its something that you want the choice to uninstall later on like a 'task killer' apk or something, place it in data/app folder..
and to sign it you dont need kitchen, you can download an auto-sign.zip file for windows here on xda.. all you do is unzip it directly to C: drive, place zip file in filder rename it to 'update.zip' than run the 'sign.bat' and it will sign the zip file. than you can flash it
marchking said:
ok... so im also adding a few apks at the system/app what you suggested will that still work?
btw
just to clarify, i unzip, then remove the apks
then zip it again
then i put it in the kitchen to get signed?
Click to expand...
Click to collapse
did u do this on Kitchen?
If you want to add Market or non-stock apps (*.apk) to your ROM (which can be uninstalled or updated from your device later) then select the kitchen's menu option that adds "/data/app functionality". Afterwards you can copy these .apk files to the new /data/app folder of your working folder.
EDIT; After your done adding/deleting all the apps, dont forget to use the sign apk command to sign.
maximo360 said:
did u do this on Kitchen?
If you want to add Market or non-stock apps (*.apk) to your ROM (which can be uninstalled or updated from your device later) then select the kitchen's menu option that adds "/data/app functionality". Afterwards you can copy these .apk files to the new /data/app folder of your working folder.
EDIT; After your done adding/deleting all the apps, dont forget to use the sign apk command to sign.
Click to expand...
Click to collapse
would apps from a 2.2 hero would work? they have a mdpi format???
or do you think i will encounter lots of problems? ^_^
marchking said:
would apps from a 2.2 hero would work? they have a mdpi format???
or do you think i will encounter lots of problems? ^_^
Click to expand...
Click to collapse
Which kind of apps? Like sense apps? I guess they might work, try it out, make a nand backup first tho.
Sent from my COS-DS using XDA App
maximo360 said:
Which kind of apps? Like sense apps? I guess they might work, try it out, make a nand backup first tho.
Sent from my COS-DS using XDA App
Click to expand...
Click to collapse
its actually system/app from miui ported to mdpi...
i was able to flash it but its going into a bootloop...
im not sure how to gather logcat... i dont use adb hahaha...
i only use droid explorer... anyways
i checked the logcat console while it was on the bootloop
it appears to me that the apps that i used is not signed...
any suggestions?
marchking said:
its actually system/app from miui ported to mdpi...
i was able to flash it but its going into a bootloop...
im not sure how to gather logcat... i dont use adb hahaha...
i only use droid explorer... anyways
i checked the logcat console while it was on the bootloop
it appears to me that the apps that i used is not signed...
any suggestions?
Click to expand...
Click to collapse
sign them using the sign apk/zip command in the kitchen
maximo360 said:
sign them using the sign apk/zip command in the kitchen
Click to expand...
Click to collapse
i signed them that seemed to be one problem... based on what im seeing on the logcat it seems now its having lots of problems while installing... FYI im trying to make a miui ported from nexus 1 to hero... trying to make it run on froyo by laszlo... i think there is much more complications here not as easy as i think it would be... but i like challenges ^_^ do you have any idea how we could do this maximo? try checking this link http://forum.xda-developers.com/showthread.php?t=858935
marchking said:
i signed them that seemed to be one problem... based on what im seeing on the logcat it seems now its having lots of problems while installing... FYI im trying to make a miui ported from nexus 1 to hero... trying to make it run on froyo by laszlo... i think there is much more complications here not as easy as i think it would be... but i like challenges ^_^ do you have any idea how we could do this maximo? try checking this link http://forum.xda-developers.com/showthread.php?t=858935
Click to expand...
Click to collapse
I read the thread, and he said he dropped some of the phones he was porting miui for, he was still doing the eris/hero. So seems to me he maybe dropped the g1, not sure tho. I guess you're gonna have to wait til either delsa is done porting it to the g1 or drakko.
Sent from my COS-DS using XDA App

[Q] Creating a theme for a stock phone + root

Is it possible? Since to gain access to the frameworkres.apk root is required, is it possible to just copy it, mod the apk and then reapply it without having CWM installed and needing a zip file to flash it?
the problem is that you need to deodex the rom. if you do that, yes, you can theme it without flashing anything
learn how to use ADB
Even to do just an image swap in the apk it needs to be deodexed? Do I need ADB to deodex it?
jonnyg1097 said:
Even to do just an image swap in the apk it needs to be deodexed? Do I need ADB to deodex it?
Click to expand...
Click to collapse
Based on this question I am going to suggest you do some reading.
Sent from my atrix

Patching core.jar & service.jar in Kit Kat

Manual how to apply patches android, for those who do not get it in the standard way. News for firmware based CM11, KitKat, 4.4.4 and others...
We will need 1 ) Root Explorer or another file manager. 2 ) Lucky Patcher.
And so, we go through the Root Explorer to system/framework and look there for a couple of files with names core.jar and services.jar, found means to copy to SD card for further action with them.
Go to Lucky Patcher and select the function to "Rebuild and install". We are looking for in the open filemanager copied our files, click on each of them and choose the function "Patch file firmware", patched both files close Lucky Patcher.
Open Root Explorer find our patched copy and rename them from the core-patched.jar in the core.jar, and so did a services-patched.jar in services.jar.
Put them in the firmware in two ways.
The first :
Through the Root Explorer to replace the first system/framework file core.jar and put it right (rw-r - r--).
Reboot and look at the first two Lucky Patcher android patch applied. Good!!!
Replace the same in system/framework file services.jar and the phone itself will go into a reboot may reboot itself again, nothing wrong with that.
Go through the Root Explorer on the road system/framework to the file services.jar and give him the right to (rw-r - r--).
Watch in Lucky Patcher all three patch applied android.
The second method:
For him, we need the establishment of recovery TWRP or CWM and Aroma Filemanager. Earnest request before to do something, then test Aroma FM on your device !!!
We go in and start recovery Aroma Filemanager. After that, everything just as in Root Explorer, substitute core.jar on patched us exhibiting rights (rw-r - r--) and reboot.
Again in recovery and launch Aroma Filemanager. And substitution of services.jar but rights can and should be put immediately (rw-r - r--).
Reboot and you're done.
One piece of advice if something goes wrong as we would like it keep copies non patching core.jar and services.jar.
You can always get them back into place and put right through Aroma Filemanager.
Addition to those who have odex firmware :
In odex firmware need to copy the core.odex and sevices.odex on sdcard.
Go to Lucky Patcher, and on the bottom panel to select "Install and rebuild".
Then, select a file core.odex and select to patch the firmware file, then select services.odex and also choose to patch the firmware file, then rename and put them back into the system/framework.
Ms_Julia said:
Manual how to apply patches android, for those who do not get it in the standard way. News for firmware based CM11, KitKat, 4.4.4 and others
Click to expand...
Click to collapse
Why patch these files?
AXDFREEDOM said:
Why patch these files?
Click to expand...
Click to collapse
To disable signature verification in the package manager.
AXDFREEDOM said:
Why patch these files?
Click to expand...
Click to collapse
...
Ms_Julia said:
...
Click to expand...
Click to collapse
Which ROM you now use??
No need to patch this files, because you can install paid apps from google without this, playstore dont chech it for verificatio, better leave this files alone, I dont know how to say. Xd
You dont need to patch anything.
And if you dont know Lucky patcher is illegal on xda.
Your guide is good
But, that dont need to do.
Paget96 said:
Which ROM you now use??
No need to patch this files, because you can install paid apps from google without this, playstore dont chech it for verificatio, better leave this files alone, I dont know how to say. Xd
You dont need to patch anything.
And if you dont know Lucky patcher is illegal on xda.
Your guide is good
But, that dont need to do.
Click to expand...
Click to collapse
Thank you, I know it. But sometimes it is necessary for example to amend the application to the best of his work. And to set it is necessary to use patches to disable signature verification.
Ms_Julia said:
Thank you, I know it. But sometimes it is necessary for example to amend the application to the best of his work. And to set it is necessary to use patches to disable signature verification.
Click to expand...
Click to collapse
That can make problems in ROM, that is maybe good with some apps, but I dont know which app need this??
Paget96 said:
That can make problems in ROM, that is maybe good with some apps, but I dont know which app need this??
Click to expand...
Click to collapse
I think u don't need to use these patches. As u said they lead to illegal activities. I have no key problems they cause only help with all applications. Because I have a direct hands. How well do u know the android ?
Ms_Julia said:
I think u don't need to use these patches. As u said they lead to illegal activities. I have no key problems they cause only help with all applications. Because I have a direct hands. How well do u know the android ?
Click to expand...
Click to collapse
I know pretty much, but I dont know anythig about coding.
Paget96 said:
I know pretty much, but I dont know anythig about coding.
Click to expand...
Click to collapse
U know the only thing is the top of android. But the essence of not even examined, it's clear that u are not a programmer or developer. Just once again I say to u for u my user guide is useless , unless u want to learn everything. And to know a lot more than it is now at the moment.
Ms_Julia said:
U know the only thing is the top of android. But the essence of not even examined, it's clear that u are not a programmer or developer. Just once again I say to u for u my user guide is useless , unless u want to learn everything. And to know a lot more than it is now at the moment.
Click to expand...
Click to collapse
I dont understand you.
Paget96 said:
I dont understand you.
Click to expand...
Click to collapse
These patches are needed for a more complete control over the android. Do you understand now?
Big thanx for this great tutorial,its very usefull.but one request i have about patching with lucky.maybe its possible to patch the service.jar for full tweaking like v6 supercharger etc. As we know zeppelinrox is working on it and we can do it by hand with very anoying smalipatches one by one,so maybe its possible to make it with luckypatcher too?
GREETZ FROM TEAM-OPTIMA!!!
NmAa said:
I guess what she's trying to impost is that we must own our phone because it's ours not Google and we must live in our own...
#LG #P705
#RECOVERY: TWRP 2.6.3.0/P700
#ROM:CM11/IMER
Click to expand...
Click to collapse
YES!!! :thumbup:
-CALIBAN666- said:
Big thanx for this great tutorial,its very usefull.but one request i have about patching with lucky.maybe its possible to patch the service.jar for full tweaking like v6 supercharger etc. As we know zeppelinrox is working on it and we can do it by hand with very anoying smalipatches one by one,so maybe its possible to make it with luckypatcher too?
GREETZ FROM TEAM-OPTIMA!!!
Click to expand...
Click to collapse
Did not think about it yet, but ask the creator of the LP.
Ms_Julia said:
Manual how to apply patches android, for those who do not get it in the standard way. News for firmware based CM11, KitKat, 4.4.4 and others...
.
Click to expand...
Click to collapse
thank you for this i been working hard trying to get this ported for the nexus 7 2013 "flo" now its patched and working. i tryed to manually edit services.jar my self but resulted in a billion force closing apps. now i am able to sign my apps and they boot p.s this post has been the most helpful than any others
i cant patch the copied files (core.jar and services.jar ) in SD card plz help...!!
Ms_Julia said:
Manual how to apply patches android, for those who do not get it in the standard way. News for firmware based CM11, KitKat, 4.4.4 and others...
We will need 1 ) Root Explorer or another file manager. 2 ) Lucky Patcher.
And so, we go through the Root Explorer to system/framework and look there for a couple of files with names core.jar and services.jar, found means to copy to SD card for further action with them.
Go to Lucky Patcher and select the function to "Rebuild and install". We are looking for in the open filemanager copied our files, click on each of them and choose the function "Patch file firmware", patched both files close Lucky Patcher.
Open Root Explorer find our patched copy and rename them from the core-patched.jar in the core.jar, and so did a services-patched.jar in services.jar.
Put them in the firmware in two ways.
The first :
Through the Root Explorer to replace the first system/framework file core.jar and put it right (rw-r - r--).
Reboot and look at the first two Lucky Patcher android patch applied. Good!!!
Replace the same in system/framework file services.jar and the phone itself will go into a reboot may reboot itself again, nothing wrong with that.
Go through the Root Explorer on the road system/framework to the file services.jar and give him the right to (rw-r - r--).
Watch in Lucky Patcher all three patch applied android.
The second method:
For him, we need the establishment of recovery TWRP or CWM and Aroma Filemanager. Earnest request before to do something, then test Aroma FM on your device !!!
We go in and start recovery Aroma Filemanager. After that, everything just as in Root Explorer, substitute core.jar on patched us exhibiting rights (rw-r - r--) and reboot.
Again in recovery and launch Aroma Filemanager. And substitution of services.jar but rights can and should be put immediately (rw-r - r--).
Reboot and you're done.
One piece of advice if something goes wrong as we would like it keep copies non patching core.jar and services.jar.
You can always get them back into place and put right through Aroma Filemanager.
Addition to those who have odex firmware :
In odex firmware need to copy the core.odex and sevices.odex on sdcard.
Go to Lucky Patcher, and on the bottom panel to select "Install and rebuild".
Then, select a file core.odex and select to patch the firmware file, then select services.odex and also choose to patch the firmware file, then rename and put them back into the system/framework.
Click to expand...
Click to collapse
i cant patch the copied files (core.jar and services.jar ) in SD card plz help...!!
it says a warning
the file ".jar" doesnt contain classes.dex for patch . try patch ".odex" file for this ".jar" file
what to do..?? plz help
Prem_414 said:
i cant patch the copied files (core.jar and services.jar ) in SD card plz help...!!
it says a warning
the file ".jar" doesnt contain classes.dex for patch . try patch ".odex" file for this ".jar" file
what to do..?? plz help
Click to expand...
Click to collapse
Do exactly what the error said. Also are you deodexed? I was able to patch this my self on nexus 7 and my s3 touchwiz.
Sent from my SGH-T999 using XDA Free mobile app
Android 5.0.2
there are this cores...
miguelrivas said:
Android 5.0.2
there are this cores...
Click to expand...
Click to collapse
I'm not sure if the signing is the same way for lollipop as in 4.4 and below I have tried it but it didn't work. You can try and see but you will only have art core to use your os doesn't support davlik anymore
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

Question Build.prop

I am rooted with Busybox installed via magisk. SU root check was done and i am rooted for sure. However i cannot seem to modify the build.prop file. Can anyone advice please
Install Solid Explorer and try again edit with this file explorer
Trevorek said:
Install Solid Explorer and try again edit with this file explorer
Click to expand...
Click to collapse
Good looking app however it can not copy the cache to the system/build.prop.
In other words, it can not save changes like everything else
FKX1997 said:
Good looking app however it can not copy the cache to the system/build.prop.
In other words, it can not save changes like everything else
Click to expand...
Click to collapse
i had this problem with new version of magisk (23 beta+)
now i use older version ,everything work fine (full control on system files)
(i use mixplorer)
loopypalm said:
i had this problem with new version of magisk (23 beta+)
now i use older version ,everything work fine (full control on system files)
(i use mixplorer)
Click to expand...
Click to collapse
Which version are you using please
Update, checked my root and it is all working as it should be, yet i can not write to system. I have access to ADB but i need to add "ro.debuggable=1" to build.prop to do more work on the phone
FKX1997 said:
Which version are you using please
Click to expand...
Click to collapse
right now i use 21.1
loopypalm said:
right now i use 21.1
Click to expand...
Click to collapse
Just add the prop edit to a magisk flashable zip
In magisk flashable zip empty go to common/system.prop edit with text editor and add the prop you want to change then flash zip
toolhas4degrees said:
Just add the prop edit to a magisk flashable zip
In magisk flashable zip empty go to common/system.prop edit with text editor and add the prop you want to change then flash zip
Click to expand...
Click to collapse
Too many things to just edit a prop ...
plus the prop was not the only problem i got, i could not write to some folders in system
i think he fixed the problem in 24 ,but i'll keep using 21.1 anyway ...
loopypalm said:
Too many things to just edit a prop ...
plus the prop was not the only problem i got, i could not write to some folders in system
i think he fixed the problem in 24 ,but i'll keep using 21.1 anyway ...
Click to expand...
Click to collapse
Really it's not to many things it literally takes 20 seconds. I know the issue. And the dynamic part one are mainly it. That's why I suggested what I told you.
toolhas4degrees said:
Really it's not to many things it literally takes 20 seconds. I know the issue. And the dynamic part one are mainly it. That's why I suggested what I told you.
Click to expand...
Click to collapse
I think he'd rather take the chance of boot looping your advice was the best so far
loopypalm said:
Too many things to just edit a prop ...
plus the prop was not the only problem i got, i could not write to some folders in system
i think he fixed the problem in 24 ,but i'll keep using 21.1 anyway ...
Click to expand...
Click to collapse
Sadly the issue persists and i haven't made a magisk module before so i may need some help on that one please
I added it to the cloudflare 2.7 zip, i expect i shouldn't see it in the build.prop still but it would be loaded in memory? as i have it in the build.prop, the line i wish to have but set to 0 when i have set it to 1 on the system.prop file
(to clarify the line was in the build,prop by stock set to 0)

Categories

Resources