Database Users

/system/build.prop tweaks

I'm not responsible to any damage which is caused by applying any modification listed below to your phone.
Backup
If you made mistake to this file, you phone will not boot in gui, so you should always backup the file before you make any change to it. Just use any file manager to copy the file to your sd card or your pc.
Restore
If you have a Linux machine you can mount the /system partition while plugging in with the purple screen (vol up + vol down + power).
Easiest way: get Ubuntu, put your phone in purple screen, plug in with USB, you will see the system partition at your Ubuntu desktop.
The hard way: if the /system partition is no accessible under purple screen mode (such as in the latest 528 rom), you can use adb push the backup file back, search the web for details about how to use adb.
I'm digging the build.prop, some apps can do some of these tweaks for you, but I prefer typing myself. You need to reboot the phone to take effect.
1. windowsmgr.max_events_per_sec=75
add this new line to make UI more responsive, the bigger the value the more responsive, I've tried 90, too fast, fall back to 75, still quite fast
2. ro.config.hw_menu_unlockscreen=false
change value from "false" to "true" to enable menu key unlocking screen
3. ro.sf.lcd_density=240
change to 225 to increase the resolution of display, as a result, the size of icon on home page and fonts of list (of file manager or contact) become smaller, the smaller the value the smaller size of icon and fonts
4. dalvik.vm.heapsize=24m
increase the value to 32m~48m to increase stability and performance, tested but doesn't see much effect so far

all so if you tried games like nova or brother in arms that have black screen or graphic probs do this they now all work
go to /system/build.prop and edit it to this then close and turn the phone off / on do a build.prop DO A BUILD.PROP BACKUP FIRST ALLWAYS A MUST BEFOR PLAYING AROUND.
once the phone is on go to settings about phone model number and it will say Desire HD.
Then download games for the htc desire hd and it works.
if you want it back to standed just replace it with the backup

i think the suggestions are great!
big thx!!!

thanks for the share

Do I just change the name, where it says build.prop now?

sorry there are still some games that wont work like brother in arms 2 and modern combat black pegasus but all the others work like
splinter cell
sandstorm
n.o.v.a.
and so on

your phone hast to be rooted and use root explorer and go to
/system/build.prop and open and edit the text then reboot your phone

backed up the build.prop and made the changes. On restart it hangs on boot screen (huawei name and logo) I have to remove the battery to switch off. tried connecting to the PC to restore build.prop but it doesnt load the phone memory. Only launches the mobile partner autostart. Also tried updating by adding update.zip to sd card but says signature verification failed. Tried lading general update from huaweidevice.com onto dload directory on sd card, Just shows purple screen on booting with power, vol up and down. Please advice.

adrdsouza said:
backed up the build.prop and made the changes. On restart it hangs on boot screen (huawei name and logo) I have to remove the battery to switch off. tried connecting to the PC to restore build.prop but it doesnt load the phone memory. Only launches the mobile partner autostart. Also tried updating by adding update.zip to sd card but says signature verification failed. Tried lading general update from huaweidevice.com onto dload directory on sd card, Just shows purple screen on booting with power, vol up and down. Please advice.
Click to expand...
Click to collapse
If you have a Linux machine you can mount the /system partition while plugging in with the purple screen (vol up + vol down + power).
Easiest way: get Ubuntu, put your phone in purple screen, plug in with USB, you will see the system partition at your Ubuntu desktop.

Thank you..a mate uses linux so went over and it worked like a charm. I hadn't put the 'm' at the end in 'dalvik.vm.heapsize=24m' but it is sorted now. Thanks again.

Hi there.Is there any value in build.prop file to decrease the time that the screen rotates?I measure that the default time is about 1sec.I want it 500ms or lower.

ive root and root explorer, but when i try to edit the build.prob it says that its read only rom .
whats the problem?
sry for my bad english

In the top right hand corner there is a button which says 'mount r/w' press it and your filesystem will be read/write. Then make the changes to build.prop then press the button again then reboot.

volume headphones?
Where can I find the file corresponding to the volume of the sound through headphones? A similar problem occurred on the ZTE, but was repaired in the new ROM.

Piron said:
Where can I find the file corresponding to the volume of the sound through headphones? A similar problem occurred on the ZTE, but was repaired in the new ROM.
Click to expand...
Click to collapse
/system/etc/hwVolumeFactor.cfg

iamelton said:
/system/etc/hwVolumeFactor.cfg
Click to expand...
Click to collapse
I found the compination of speaker=80 and wired_headset=80 pretty cool.Has anyone found a better setting?

headphone volume
80 is too much. For me the best settings are:
- speaker 75 (default)
- Headphones 70 (higher values ​​will cause the overload of sound)
With this setup is really cool .

Swype
The original ROM is installed Swype keyboard, but not in the Polish language. It is not possible to uninstall Swype and you can not install a new keyboard. Despite the ROOT system does not allow the removal of the keyboard ("cust/hw/ideos_x5/app / "). Does anyone know how to remove the keyboard, or where to replace your dictionary?

adrdsouza said:
Thank you..a mate uses linux so went over and it worked like a charm. I hadn't put the 'm' at the end in 'dalvik.vm.heapsize=24m' but it is sorted now. Thanks again.
Click to expand...
Click to collapse
unfortunately I've got the same problem with you, I changed a file's name in the system/ directory now the phone bricks. I mounted it on mu ubuntu laptop and found that file but it says I have no permission to change it back...what should do now?
edit: never mind, I got it solved with sudo. I am a stupid linux noobie.

I just opened the file, but there's no "windowsmgr.max_events_per_sec" in it, i found the rest (2-4), does someone know why?
Edit: after applying the B160 ROM, i found this line, works great

[Q] HELP! Nexus 4 won't boot up

Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan

Restore your Nandroid.
Edit: just saw that you said you didn't make one. Lesson learned, I guess. You can adb sideload files from within recovery. Do this, sideload a stock rom, flash it, and it will give you a normal build.prop.
Sent from my iPad 4

Use adb to push the backup build.prop and overwrite the current one.
I'm assuming that u have the backup on your PC? If not, then download the stock ROM and extract the build.prop from /system.
Use the following command to push it:
Code:
adb push /path/to/build.prop \system
Sent from my HTC Desire using xda app-developers app

megaman1574 said:
Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan
Click to expand...
Click to collapse
If it's stock android, you could actually just wipe /system , then using adb in recovery you can push up a zip of the stock 4.2.2 isntall, and just flash that.
If build.prop is all you changed in /system then that should be fine to do, which will be especially easy if you can just grab a pre-rooted flashable zip of 4.2.2 stock.

megaman1574 said:
Hi.
I have a Nexus 4 running stock Android 4.2.2. The bootloader is unlocked and it's rooted using TWRP to install Super SU.
Just recently I decided I didn't like the soft keys (navigation bar) and researched how to remove it (just it, not the notification bar). The simplest solution I found was to use ROM Toolkit Lite to add "qemu.hw.mainkeys=1" to build.prop, and rebooting.
Eventually I found too many problems with removing the soft keys and wanted them back so today I went back in to ROM Toolkit to remove that line. The problem was that I couldn't figure out how to do this. ROM Toolkit lets you add lines to build.prop by tapping "new entry" which brings up a box that had "property name" and "property value" like this:
When I went to remove the entry, I couldn't work out how to delete it (I now know you tap menu>edit and it comes up as a text file). What I ended up doing was just removing the property name and changing property value to 0. That meant that build.prop had "=0" at the end. When I rebooted, it just sits endlessly showing the Nexus logo.
My question is how do I restore build.prop? Factory resetting doesn't work because it doesn't change the Android system files. I actually have a backup of build.prop made by ROM Toolkit but how do I overwrite the broken one? All I can do is use recovery mode (TWRP).
Is there a flashable zip with the default build.prop?
Can I make my own flashable zip from the backup of build.prop?
How do I put files onto my Nexus using recovery?
I have no system backup.
Thanks,
Lachlan
Click to expand...
Click to collapse
Ok, I can pull the backup of build.prop from my phone using adb and I found how to make a flashable zip, pushed it back and flashed it but still no boot up. I don't understand, I've replaced the offending file, why does it still not work?

megaman1574 said:
Ok, I can pull the backup of build.prop from my phone using adb and I found how to make a flashable zip, pushed it back and flashed it but still no boot up. I don't understand, I've replaced the offending file, why does it still not work?
Click to expand...
Click to collapse
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).

kbeezie said:
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).
Click to expand...
Click to collapse
Where should I look to get a stock rom?

megaman1574 said:
Where should I look to get a stock rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2147281
[ROM][OTA][mako]Android 4.2.2 JDQ39: Rooted Busybox Deodexed/Odexed (2/13/13)
Sent from my iPad 4

mitchdickson said:
just saw that you said you didn't make one. Lesson learned, I guess.
Click to expand...
Click to collapse
Yes, definitely. I can't remember why I didn't make a backup...

mitchdickson said:
http://forum.xda-developers.com/showthread.php?t=2147281
[ROM][OTA][mako]Android 4.2.2 JDQ39: Rooted Busybox Deodexed/Odexed (2/13/13)
Sent from my iPad 4
Click to expand...
Click to collapse
Ok, if I can't fix it by tonight I'll download this and flash it (My download limit during the day is too small to download it. That's why I'm trying to fix it without doing that)

kbeezie said:
Could be permissions or a number of other things, If you can I would run adb logcat while plugged in, assuming it even gets past the point of starting the adb daemon.
The alternative if you didn't mess with much more than the build.prop (like install system apps), is to simply wipe /system and flash on the stock rom (or pre-rooted version of it).
Click to expand...
Click to collapse
I'm not that good with Android, how and when do use this "logcat"?

megaman1574 said:
I'm not that good with Android, how and when do use this "logcat"?
Click to expand...
Click to collapse
adb should be second nature to anyone who has rooted/unlocked their phone or flashed custom roms. (But I'm guessing you just used a toolkit).
ie: phone plugged in while it's booting, you'd type
adb logcat
and if adbd is launched on the phone you'll see the logs as they are produced which might offer some clues as to where it's failing.

kbeezie said:
adb should be second nature to anyone who has rooted/unlocked their phone or flashed custom roms. (But I'm guessing you just used a toolkit).
ie: phone plugged in while it's booting, you'd type
adb logcat
and if adbd is launched on the phone you'll see the logs as they are produced which might offer some clues as to where it's failing.
Click to expand...
Click to collapse
I actually rooted it manually because A: The toolkit I had didn't work, and B: It's more fun. But I had never used the logcat command. I figured out how to call the command but it kept saying "file not found" or something because I didn't think to have it booting. I'm trying that now. Ok, it says
C:\Users\Lachlan>adb logcat
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
- waiting for device -
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
- waiting for device -
adb server is out of date. killing...
* daemon started successfully *
And then sits there with a flashing cursor after the last line.

megaman1574 said:
I actually rooted it manually because A: The toolkit I had didn't work, and B: It's more fun. But I had never used the logcat command. I figured out how to call the command but it kept saying "file not found" or something because I didn't think to have it booting. I'm trying that now. Ok, it says
C:\Users\Lachlan>adb logcat
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
- waiting for device -
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
- waiting for device -
adb server is out of date. killing...
* daemon started successfully *
And then sits there with a flashing cursor after the last line.
Click to expand...
Click to collapse
It tells you what the problem is right here:
adb server is out of date. killing...
adb is out of date, update it. (on OSX or Linux you would just run android update adb, I assume the same probably works on windows for the SDK).

kbeezie said:
It tells you what the problem is right here:
adb server is out of date. killing...
adb is out of date, update it. (on OSX or Linux you would just run android update adb, I assume the same probably works on windows for the SDK).
Click to expand...
Click to collapse
My adb version is 1.0.31. As far as I know that is the latest version. I don't actually have the Android SDK because I had trouble installing it. I installed adb separately. Plus, with all the other commands it says it's out of date but then works anyway.

megaman1574 said:
My adb version is 1.0.31. As far as I know that is the latest version. I don't actually have the Android SDK because I had trouble installing it. I installed adb separately. Plus, with all the other commands it says it's out of date but then works anyway.
Click to expand...
Click to collapse
Weird, but far as the SDK goes, all I did was unpack the SDK onto my desktop. And just hit up the platform-tools folder, type the command android , to bring up the java app so I can choose what I want installed (updating can be done without the GUI by doing android update sdk --no-ui , or can remove the last part if you want to see the window).
So to me it wasn't much different on windows as it was on my mac (just easier to add adb/fastboot to my path variable in OSX).
PS: You're correct, the latest version does appear to be 1.0.31

kbeezie said:
Weird, but far as the SDK goes, all I did was unpack the SDK onto my desktop. And just hit up the platform-tools folder, type the command android , to bring up the java app so I can choose what I want installed (updating can be done without the GUI by doing android update sdk --no-ui , or can remove the last part if you want to see the window).
So to me it wasn't much different on windows as it was on my mac (just easier to add adb/fastboot to my path variable in OSX).
PS: You're correct, the latest version does appear to be 1.0.31
Click to expand...
Click to collapse
Ok, after much fiddling I still can't make it boot so I'll have to download the stock rom tonight. Should I get odexed or deodexed? Will I be able to restore my data backup after flashing the rom? And will OTA updates work after flashing?

megaman1574 said:
Ok, after much fiddling I still can't make it boot so I'll have to download the stock rom tonight. Should I get odexed or deodexed? Will I be able to restore my data backup after flashing the rom? And will OTA updates work after flashing?
Click to expand...
Click to collapse
I haven't done it myself, but I don't think the OTA update will work if you have a custom recovery (and if the OTA update does go thru, it can possibly unroot your install). odexed is usually the original state.
Odexed are optimized (can be faster to load etc), where as deodexed are easier to modify/theme (most are originally odex'd as they're not intended to be modified later).
If you were already on stock, and you flash a stock rom (with just rooted being the difference) then the data you already have in /data should work. You can basically wipe /system but not /data and just flash the rom and boot up. (just be sure to make a backup of the data first if you can).

Ok... I had managed to move the backup of build.prop into system using TWRP's file manager but after THAT it wouldn't even show the Nexus logo. Hence the reason I said nothing about this (I thought it to be a dead end). Just as I was about to give up, I was reading an obscure post on Androidforums.com and came across a post telling the guy to pull build.prop, edit it, push it back, and chmod it to 644. I haven't the FAINTEST clue what the hell that is, but I remembered that "chmod" and "chmod 755" were two options when you tap on a file in TWRP's file manager. So I raced back in there, deleted the broken build.prop, moved the backup into system, tapped on it and pressed "chmod 755" rebooted and it worked! Anyone have any idea what is was that I did? What is chmod? But basically:
I FIXED IT YAY!!!
Thanks everyone for your help. I've been desperate to fix it, in fact, when I broke it was an hour before I had to leave for a weekend trip, so I had no phone.

kbeezie said:
I haven't done it myself, but I don't think the OTA update will work if you have a custom recovery (and if the OTA update does go thru, it can possibly unroot your install). odexed is usually the original state.
Odexed are optimized (can be faster to load etc), where as deodexed are easier to modify/theme (most are originally odex'd as they're not intended to be modified later).
If you were already on stock, and you flash a stock rom (with just rooted being the difference) then the data you already have in /data should work. You can basically wipe /system but not /data and just flash the rom and boot up. (just be sure to make a backup of the data first if you can).
Click to expand...
Click to collapse
My Nexus 7 is rooted with TWRP and it received an OTA update. But anyway, if you refer to my last post I fixed it.
Edit: However, it did unroot it. (not hard to reroot though)

DPI setting help

Hey guys was just wondering if anyone can post a video with a changed DPI? I'm not routes and I heard it can be done without root but wanted to see what it looks like first would really appreciate it

syphern said:
Hey guys was just wondering if anyone can post a video with a changed DPI? I'm not routes and I heard it can be done without root but wanted to see what it looks like first would really appreciate it
Click to expand...
Click to collapse
Not sure where you heard it can be done without root. Because it simply can't. Without root you cannot modify system files.
Sent from my Nexus 6P using Tapatalk

It can be done without root but needs to be done using ADB on a PC.
On your PC while the phone is connected:
ADB shell
WM density 480 (or whatever you want for your device)
Restart your device to complete.

Just try it. U can easily go back to default. But i promise, u dont want :b

I am rooted on my Nexus 6P, although I cannot get it to change the dpi settings.
I tried using texdroider_dpi, tried the adb method and even went to /system/build.prop and changed it via ES File Explorer.
When I set the DPI to anything but 560 my SwiftKey Keyboard breaks but the overall screen density doesn't change.
The value I entered is still displayed in the build.prop though ..
I had it changed already, but when I updated to the latest security patch 2016 I had to reinstall my phone since I flamingod something I guess.
Went ahead with Heisenbergs guide and followed Step 11 (http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) to get my phone back to work. Only thing not working now is the dpi change ..
Any help?

Are you mounting system as R/W and saving the build.prop after you change the value?

dastinger said:
Are you mounting system as R/W and saving the build.prop after you change the value?
Click to expand...
Click to collapse
I didn't specifially mount the system as R/W - but when I restart the device afterwards the change is still persistent.

Try using another File Explorer (Fx with the root add-on for example) and make the change with that one mounting as R/W before doing anything else.

dastinger said:
Try using another File Explorer (Fx with the root add-on for example) and make the change with that one mounting as R/W before doing anything else.
Click to expand...
Click to collapse
I love you. #nohomo
Thank you very much.

[emoji4]
No problem, mate.

clubtech said:
It can be done without root but needs to be done using ADB on a PC.
On your PC while the phone is connected:
ADB shell
WM density 480 (or whatever you want for your device)
Restart your device to complete.
Click to expand...
Click to collapse
I do this but my Swiftkey is broken and some image elements are huge.
Does anyone know why something like texdroider used to work perfectly scaling everything and now it does not?
Before this update, after flashing the SuperSU 2.66 my twrp would give me the warning my phone was not rooted. Now, I do not receive this warning.
Sent from my Nexus 6P using Tapatalk

Any way to change dpi without adb ?

I have rooted my BTV-W09 model. When I use 'adb shell wm density 320' from my computer terminal, the dpi setting is adjusted correctly, but it doesn't survive a reboot.
I tried to change the dpi setting with a build.prop editor directly on the tablet and with the Textdroider DPI app, but it doesn't work, it goes back to whatever DPI settings was implied by the display settings (from Small-400dpi to Large-480dpi).
Is there a way to permanently change the DPI setting to 320, or at least a way to do it directly from the tablet (without a computer)?

Why you not reading neighbor topics? Install Xposed, install App Settings module from here for example, activate it and setup whatever DPI you wish.

Thanks Slavon, but I'm speaking of a system-wide change, not just app by app. English is not my first language, sorry if it wasn't clear.

Sorry if I was a bit rude. Try "Pimp my rom" utility. Find it on Google Play. I worked for me and now I'm thinking of how to revert
Edit: if I got it right, this utility adds (modifies?) this key in build.prop: ro.sf.lcd_density

Not at all, I understand how it seemed like I was asking a duplicate question without looking in others threads, sorry again
And thanks a lot for the advice, I'll try Pimp my rom right away !

wlausrsker said:
Not at all, I understand how it seemed like I was asking a duplicate question without looking in others threads, sorry again
And thanks a lot for the advice, I'll try Pimp my rom right away !
Click to expand...
Click to collapse
If you just need to change density, you'd better try changing the value in build.prop first. And in case of any problems after, change the value of the key I wrote previously or restore the original build.prop from backup. Good luck.

Slavon-93 said:
If you just need to change density, you'd better try changing the value in build.prop first. And in case of any problems after, change the value of the key I wrote previously or restore the original build.prop from backup. Good luck.
Click to expand...
Click to collapse
I've tried this morning to change ro.sf.lcd_density to 320 in the build.prop and reboot. After reboot, ro.sf.lcd_density is still set to 320 but the display is still at 400dpi.
It's like ro.sf.lcd_density has no impact on the display dpi except for the display mode (tablet, phone, etc.).
Screen settings/Small + ro.sf.lcd_density=320 -> tablet mode in Chrome and 400dpi
Screen settings/Small + ro.sf.lcd_density=400 -> phone mode in Chrome and 400dpi
Screen settings/Large + ro.sf.lcd_density=320 -> tablet mode in Chrome and 480dpi
Screen settings/Large + ro.sf.lcd_density=400 -> phone mode in Chrome and 480dpi
I think maybe the DPI setting from build.prop is replaced during boot with the screen setting (Small:400dpi, Medium:440dpi, Large:480dpi). Could a init.d script could change the value after boot? I'll try tonight if the tablet allows init.d scripts to run.

Well, ok. I only quickly looked through the decompiled code. Change dpi with the app then, it'll make a backup of build. prop and try to compare both files - new and backup. I could have missed something. Just to mention, I didn't like the way tablet had behaved after changing DPI. EMUI is not well-designed for this. It's much better to set DPI for apps and leave it unmodified for system.

@wlausrsker this is covered in the apps running in phone mode thread. I posted there that the adb dpi change settings will stick after rebooting if you run the command "adb shell wm density 340 && adb reboot"*
*Use whatever density works best for you, I have found that 330 works best for me with the view mode and font set to large.

Slavon-93 said:
Change dpi with the app then, it'll make a backup of build. prop and try to compare both files - new and backup. I could have missed something.
Click to expand...
Click to collapse
johje said:
@wlausrskerI posted there that the adb dpi change settings will stick after rebooting if you run the command "adb shell wm density 340 && adb reboot"
Click to expand...
Click to collapse
johje, thanks but I tried it first and it doesn't survive reboot ("./adb shell wm density 320 && ./adb reboot" since I'm on Mac, it reboots in 400dpi).
Slavon, I've compared the files from before and after changing the dpi setting with the app, only ro.sf.lcd_density is changed, so you didn't miss anything.
Since methods successfully used by you and others don't work for me, it must be something I did differently on setting up my tablet. I used greatslon mod of TWRP and then flashed via TWRP the latest SuperSU (v2.79-SR1). Finally, I installed XposedInstaller and got xposed-v87-sdk23-arm64. Did any of you with reboot-surviving custom dpi setting used something different? (like the SRK Tool)
I'm off this weekend but I'll try next week to start over from scratch.

the reason adb change dpi and even build.prop change doesn't work is because huawei has set lcd_density in boot image. check content of /init.6x.rc
these init files are part of boot.img and will be overwritten at every boot. so what u need is a modified boot.img where this set lcd_density line is removed. Once you install that boot, you can set whatever dpi in build.prop and it will work. even adb dpi change will be persistent.
if you are on b026, i can share my edited boot.img

Thanks for the explanation bark1234, I now understand why everything I tried didn't survive reboot!
Thanks also for proposing your edited B026 boot.img but I'm on BTV-W09C100B005 and I can't find any B026 download for BTV-W09. From what I understand from other threads the latest Chinese OTA for the BTV-W09 is the BTV-W09C233B022, so I couldn't use it. Nevertheless, if you could maybe share it for others, it could help someone with the same problem on a BTV-DL09.
I tried to edit my boot.img but I'm a newbie. I've tried to extract my boot.img but I have no result with "cat /proc/mtd", so I extracted mmcblk0boot0 as a best guess. I tried to install abootimg to edit it but there's not blkid.h on Mac OS so I can't build it. If I give you what I extracted, could you maybe edit it like you did with yours? You would save me from applying at random a bunch of tutorials like I just did and hoping it will result in something usable In the meantime, I'll try and learn how to edit a boot.ini with my setup.

bark1234 said:
the reason adb change dpi and even build.prop change doesn't work is because huawei has set lcd_density in boot image. check content of /init.6x.rc
these init files are part of boot.img and will be overwritten at every boot. so what u need is a modified boot.img where this set lcd_density line is removed. Once you install that boot, you can set whatever dpi in build.prop and it will work. even adb dpi change will be persistent.
if you are on b026, i can share my edited boot.img
Click to expand...
Click to collapse
Just as an FYI, the adb dpi change initiated along with the reboot command has stuck for me after multiple reboots.

wlausrsker said:
Thanks for the explanation bark1234, I now understand why everything I tried didn't survive reboot!
Thanks also for proposing your edited B026 boot.img but I'm on BTV-W09C100B005 and I can't find any B026 download for BTV-W09. From what I understand from other threads the latest Chinese OTA for the BTV-W09 is the BTV-W09C233B022, so I couldn't use it. Nevertheless, if you could maybe share it for others, it could help someone with the same problem on a BTV-DL09.
I tried to edit my boot.img but I'm a newbie. I've tried to extract my boot.img but I have no result with "cat /proc/mtd", so I extracted mmcblk0boot0 as a best guess. I tried to install abootimg to edit it but there's not blkid.h on Mac OS so I can't build it. If I give you what I extracted, could you maybe edit it like you did with yours? You would save me from applying at random a bunch of tutorials like I just did and hoping it will result in something usable In the meantime, I'll try and learn how to edit a boot.ini with my setup.
Click to expand...
Click to collapse
If you are rooted, use flashfire app to get ur current boot.img from ur phone. and then copy it out to edit.
The tool i use for editing works on windows. i too have mac only, i have windows on vm in it.
https://www.dropbox.com/s/x46q5nzv49iauwi/Android Image Kitchen.rar?dl=1
Use above link to download tool i use.
unpackimg.bat will unpack boot img.
your init.x files will be in ramdisk, edit it there.
and then use repackimg.bat, it will create new boot.img.

johje said:
Just as an FYI, the adb dpi change initiated along with the reboot command has stuck for me after multiple reboots.
Click to expand...
Click to collapse
bark1234 said:
If you are rooted, use flashfire app to get ur current boot.img from ur phone. and then copy it out to edit.
The tool i use for editing works on windows. i too have mac only, i have windows on vm in it.
https://www.dropbox.com/s/x46q5nzv49iauwi/Android Image Kitchen.rar?dl=1
Use above link to download tool i use.
unpackimg.bat will unpack boot img.
your init.x files will be in ramdisk, edit it there.
and then use repackimg.bat, it will create new boot.img.
Click to expand...
Click to collapse
johje, it won't stuck for me, no matter how I try. Did you root by flashing the latest SuperSU? Did you installed xposed framework?
bark1234, thank you very much for the detailled explanation, I'll use Flashfire app to extract my boot.img and I'll try tomorrow at work on my Windows machine to edit it.

@wlausrsker I have not yet rooted my tablet. Once I got the dpi/phone apps issue fixed, it reduced my urgency for rooting. However, I will be rooting it soon, since a way has been found to enable the 5Ghz wireless adapter for the US version of the tablet. I will let you know if I am able to keep the dpi settings after rooting.

bark1234 said:
If you are rooted, use flashfire app to get ur current boot.img from ur phone. and then copy it out to edit.
unpackimg.bat will unpack boot img.
your init.x files will be in ramdisk, edit it there.
and then use repackimg.bat, it will create new boot.img.
Click to expand...
Click to collapse
Thanks again for the link and the explanation, it was really a painless process.
I used Flashfire app on my tablet to backup my boot.img (it resulted in a boot.lz4 file).
On my Windows machine, in a cmd window:
Code:
lz4 boot.lz4
unpackimg.bat boot
I then opened in Notepad++ the /ramdisk/init.61262.rc file to remove the line setprop ro.sf.lcd_density 560 in the on early-init and on boot sections of the file and saved.
In the cmd window:
Code:
repackimg.bat
rename image-new.img boot.img
I now have an edited boot.img to flash in TWRP. Does it seems to you that I did the editing correctly? The edited boot.img is 13.35Mb (about the same as the boot.lz4) but the extracted boot file before the unpacking was 32.77Mb. Is it normal?

13.9 is correct size. install this boot.img

For those of us following along. Does the edited boot image have to be flashed by TWRP in zip form? Or can we use Fastboot to flash it? or both will work?
I've done the edit's and have what I believe is a flashable zip. I personally like to use fastboot.
I have DPI set and holding by adb as I mentioned before but this is still nice to have.
Thanks

OP - here's a really easy way to change dpi and make it stick: https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi
I'm using it on my MediaPad M3 without issues. PS - 320 is my preferred dpi as well, but I found it caused some issues like Settings would crash. I'm using 322 now without any issue for the last couple weeks. Enjoy

Bootlooped my phone by editing system

Hi there
Apologies if this is the wrong place. I did something dumb. I played with jOnePlus to change the accent color of my rooted OnePlus 5 with Oreo oxygenOS.
Then I ran the command
adb shell settings put system oem_black_mode_accent_color '#xxxxxxxxxxxx'
I cut and pasted and forgot to change the xxxxxxxx to a real hex colour. Then I got a System UI has stopped and now my phone tries to boot, goes to the Oxygen logo then goes to TWRP. I try to boot to system but it fails and goes to TWRP. I wiped cache and Dalvik to no avail.
Can I edit the shell settings inside of TWRP? Can I repair the settings somehow. Yes, I am dumb, but any help would be really appreciated.
EDIT--------------FIXED----------------
Hi all. Thank you all very much for your advice. I was determined not to dirty or clean flash, so I persevered .
I did a lot of research and fumbling, and I managed to edit the correct file so that the phone now boots and my data is preserved.
I downloaded PuTTYTray so that I could navigate and edit easily. See Stackoverflow for details (can't post link).
Then I booted into TWRP and opened PuTTYTray, then I navigated to:
data/system/users/0
where there are a lot XML settings files. I found a file called settings_system.xml and went looking through it.
I saw:
<setting id="44341" name="oem_black_mode_accent_color" value="#xxxxxxxxxxxxx" package="com.android.shell" defaultValue="#ff42a5f5" defaultSysSet="true" />
and changed it to value="ff0000"
Then rebooted and the phone was fine.
Thanks to Stackexchange (can't post link) also.

If you have backup, try to restore it or Dirty flash the rom.

There's a terminal available in TWRP, you should try to use that.
May I ask why you decided to change the accent colour via command? I believe you can now select any colour you want with the built in menu.

daviddosa said:
There's a terminal available in TWRP, you should try to use that.
May I ask why you decided to change the accent colour via command? I believe you can now select any colour you want with the built in menu.
Click to expand...
Click to collapse
he mentioned that he's using oreo oos..
it doesn't have this feature on oreo. only basic colors are available.
as of the op problem, i suggest to clean install.. as dirty flashing may keep ur settings and preferences so it won't help.