Does anyone know if the 10E update still lets you use ADB commands? That is how I am changing my DPI and if it does not work in the new update I will not update it.
Just a question, isn't the Settings/Display/Display size change the DPI also ? Why do you need to use fastboot commands?
adit9989 said:
Just a question, isn't the Settings/Display/Display size change the DPI also ? Why do you need to use fastboot commands?
Click to expand...
Click to collapse
Because I like it a crap ton smaller than what the settings allow me to take it down to. On stock android you can change the smallest width in dev options but that setting is not visible. So the fastboot command basically lets you modify that setting because it exists but is not available to be edited.
jaedenhudson14 said:
Because I like it a crap ton smaller than what the settings allow me to take it down to. On stock android you can change the smallest width in dev options but that setting is not visible. So the fastboot command basically lets you modify that setting because it exists but is not available to be edited.
Click to expand...
Click to collapse
I Thought the dpi change was done with adb instead of fastboot. Correct me if im wrong.
R800x_user said:
I Thought the dpi change was done with adb instead of fastboot. Correct me if im wrong.
Click to expand...
Click to collapse
Yes. ADB. NOT fastboot. My error. You can change the smallest width setting in adb commands. Another thread in here explains how to do that.
ADB commands aren't neutered. It's the fastboot commands that are.
I'm still sitting on 10c, waiting for something from T-Mobile hoping to fix the SMS glitches that keep deleting my messages.
Related
Intro
This is a guide for people who want to make some modifications to config files, or other files, on System partition but do not want to root their phone or install custom recovery in order to keep OTAs and some apps, which don't play nicely with rooted phones, working. Examples of those config mods could be changing DPI or changing volume levels etc, which you would only do once and forget about it.
While root allows you to do those kinds of changes from within android, this methods would require a PC.
If you are familiar with temporary booting into a custom recovery, skip to step 5.
The usual i am not responsible for any of your actions / bricked phones disclaimer applies.
Prerequisites
- A working adb / fastboot environment. Please use Android SDK, if you installed your adb and fastboot using other tools, things might not work, so please just install SDK, install Google USB Driver from SDK manager, install Platform-Tools from SDK manager (should be installed by default) and then add your sdk platform-tools path to your PATH environment variable to have it available in cmd in every path.
- Unlocked bootloader
- TWRP image for you phone (.img) https://twrp.me/devices/huaweinexus6p.html
Follow the [GUIDE] Unlock/Root/Flash for Nexus 6P for that.
Instructions
Here is an example of modifying DPI. I prefer build.prop method of modifying DPI because using the adb wm density command usually caused some issues for me, but modifying via build.prop didn't.
1 - With you phone ON, connect it to the PC and make sure adb is working by running
Code:
adb devices
and making sure that device is listed
2 - Reboot into bootloader. and make sure fastboot is good to go too. Run commands one at a time:
Code:
adb reboot bootloader
fastboot devices
3 - Place your TWRP image file in some easily accessible folder, for the sake of this example i will use C:\Mods.
4 - Temporary boot into TWRP (we are not flashing it here at all).
Code:
fastboot boot c:\Mods\twrp-2.8.7.0-angler.img
Here is where things may not work. If you don't see your phone boot into TWRP then either your adb / fastboot environment not setup correctly (installed via a tool instead of SDK) or your img file is corrupt.
One thing that works for me when TWRP refuses to boot is to restart cmd and issue the command again this closes and reopens adb/fastboot daemon.
5 - Once TWRP is up on your phone it may display a warning saying "TWRP has detected an unmounted system partition". Swipe to allow modifications at the bottom. This screen may not come up at all.
6 - Go to Mount >>> Tick System >>> Make sure "Only Mount System Read Only" is unticked >>> Press Back button
7 - Back on your PC check if your device is listed
Code:
adb devices
8 - Pull the file you need to modify from system partition to your PC. Please note the direction of the slashes:
Code:
adb pull /system/build.prop c:/Mods
9 - Now you should see build.prop in your c:\Mods folder. Use Notepad++ or something like that to edit the file. Find the line with lcd_density= and change it's value to whatever you need and save the file.
10 - Push the file back to your phone:
Code:
adb push c:/Mods/build.prop /system
11 - Reboot
Code:
adb reboot
12 - Profit.
Hope this will help anyone who is looking to do some mods without installing custom recovery and rooting your phone.
Cheers.
Would this work for adding the tethering bypass line in the build prop?
Yes it will. What's the line again I was looking for it the other day and couldn't find it...
Works are per OP's original post, tested and boosted the headphone volume without a problem.
Headphone path is /system/etc/mixer_paths.xml
So as per OP's example to pull: adb pull /system/etc/mixer_paths.xml c:/Mods
push: adb push c:/Mods/mixer_paths.xml /system/etc
I'm using the OP's "Mods" folder to demonstrate the file path but this may vary on your PC.
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
skrowl said:
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
Click to expand...
Click to collapse
You can certainly push the files to system partition and they will retain there after reboot. So if you know which files have to be pushed for SuperSU then give that a go. It shouldn't break anything.
I haven't tried pushing SuperSU files to system partition before so I can't guarantee that OTAs will work after this. The only way to find out is to try it i guess...
Can you run nandroids?
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
NCguy said:
Can you run nandroids?
Click to expand...
Click to collapse
Im not sure what you mean?
rohit25 said:
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
Click to expand...
Click to collapse
If it's on the system partition then I yes you can.
locolbd said:
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
Click to expand...
Click to collapse
I've never had a problem with changing DPI using this method on a nexus phone if that helps.
denk said:
Im not sure what you mean?
Click to expand...
Click to collapse
Can you run nandroids backups from TWRP by just booting into it?
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
I got this too when I flashed MOAB via adb sideload. I'm just wondering if the same warning appears with the adb push method. Also, the file's permissions don't need to be set after adb push?
My main concern is if Android Pay still works with the red triangle warning. Anyone?
FYI Flashing back to stock is no issue for me.
NCguy said:
Can you run nandroids backups from TWRP by just booting into it?
Click to expand...
Click to collapse
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
Thanks for trying it out! Sometimes OTA notifications take a little while to come up after reboot. But based on the warning Im afraid that they might be disabled now. It looks like it runs some sort of a check on the system partition to verify its legitimacy. So modifying files would be fine on it using this method but looks like adding them won't work.
TWRP just released their recovery with decryption support so you can just follow the standard procedure or just temporary booting into TWRP and rooting from there which works as well.
denk said:
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
Click to expand...
Click to collapse
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
NCguy said:
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
Click to expand...
Click to collapse
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
denk said:
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
Click to expand...
Click to collapse
Thanks a lot for that. I didn't unlock the bootloader. Ugh. Time to start over. To me nandroids alone make it worth the effort.
Adjusting Screen Resolution:
Isn't there a way to adjust screen size or resolution, I feel the default image on the desktop gets cut at the bottom and was curious to see if I can play with resolution like we used to do on a windows desktop where we also adjust the icon sizes!!?
I used the DPI= kernel option for Remix OS. Without it I couldn't see my screen because it is 4k resolution, needed a magnifying glass. Think there are some apps in the play store that will allow you to adjust this. Not sure if they require root though. Now I am curious..........
Checked the Play Store and the DPI changer apps do require root.
erickh said:
I used the DPI= kernel option for Remix OS. Without it I couldn't see my screen because it is 4k resolution, needed a magnifying glass. Think there are some apps in the play store that will allow you to adjust this. Not sure if they require root though. Now I am curious..........
Checked the Play Store and the DPI changer apps do require root.
Click to expand...
Click to collapse
thanks very useful insight!
Hi Sany,
If you want a little more information on the subject you can go here http://technicalcultivation.weebly.com/android . I wrote a short article on the subject of changing your DPI on Android.
erickh said:
Hi Sany,
If you want a little more information on the subject you can go here http://technicalcultivation.weebly.com/android . I wrote a short article on the subject of changing your DPI on Android.
Click to expand...
Click to collapse
Your article is wrong you can set the resolution on android; via wm ie wm size 1204x768 and you can set dpi with wm density 140; and these don't require root afaik.
Thanks for the info, i'll look into it and update.
Alt+F1 to open the command console
wm density (dpi here), then enter
wm size (resolution here), then enter
Alt+F7 to close command window
(Note : This is very experimental. Be very cautious doing it inside open applications as well, and it does persist through reboots. You can easily muck up your display settings, and be forced into reinstalling a new data partition/full install, and it DOES have bearing on open applications, often leading into boot loops per few minutes).
HypoTurtle said:
Your article is wrong you can set the resolution on android; via wm ie wm size 1204x768 and you can set dpi with wm density 140; and these don't require root afaik.
Click to expand...
Click to collapse
How can I access those commands, wm size or wm density ??
chapa_9 said:
How can I access those commands, wm size or wm density ??
Click to expand...
Click to collapse
See post above.
Zeronomous said:
Alt+F1 to open the command console
wm density (dpi here), then enter
wm size (resolution here), then enter
Alt+F7 to close command window
(Note : This is very experimental. Be very cautious doing it inside open applications as well, and it does persist through reboots. You can easily muck up your display settings, and be forced into reinstalling a new data partition/full install, and it DOES have bearing on open applications, often leading into boot loops per few minutes).
Click to expand...
Click to collapse
Hello,
I get a permission error (java.lang.SecurityExcpetion: must hold permission android.permission.WRITE_SECURE_SETTINGS) if i use this command.
Do I have to root Remix OS for it?
G-DaX said:
Hello,
I get a permission error (java.lang.SecurityExcpetion: must hold permission android.permission.WRITE_SECURE_SETTINGS) if i use this command.
Do I have to root Remix OS for it?
Click to expand...
Click to collapse
I have the same error.
what should be done?
If you have installed GRUB, you can edit the start line (first tab, then follow the instructions so you can 'e' edit)
For an interactive choice you can add vga=ask, that will give an overview of the available modes.
If you want to add it permanently, you'll have to modify grub/menu.lst (using a live linux CD or so) and add vga=<your mode in decimal>
Only caveat is that vga=ask shows the mode in hex and you have to add it in decimal to menu.lst
flemlion13 said:
If you have installed GRUB, you can edit the start line (first tab, then follow the instructions so you can 'e' edit)
For an interactive choice you can add vga=ask, that will give an overview of the available modes.
If you want to add it permanently, you'll have to modify grub/menu.lst (using a live linux CD or so) and add vga=<your mode in decimal>
Only caveat is that vga=ask shows the mode in hex and you have to add it in decimal to menu.lst
Click to expand...
Click to collapse
and there is some or team to flip the image from portrait to landscape?
Please reference the thread mentioned
http://forum.xda-developers.com/axon-7/how-to/guides-info-info-a2017u-bootloader-t3440254
swissdre said:
This allowed me to edit build.prop (to properly change my DPI, with root of course) with ease. Haven't done much else with it, thought I'd share.
run this command in adb shell or terminal
adb reboot disemmcwp
to re-enable write protection issue this command
adb reboot emmcwpenab
I have changed my DPI to 540 through both wm shell and build.prop with no graphical glitches. Done on a rooted a2017u with b27 update.
Click to expand...
Click to collapse
???? I see you didn't do a search before opening a thread,
This been known for quite a while now.
http://forum.xda-developers.com/axon-7/how-to/guides-info-info-a2017u-bootloader-t3440254
"Make Root Changes Persistent after Reboot"
DrakenFX said:
???? I see you didn't do a search before opening a thread,
This been known for quite a while now.
Click to expand...
Click to collapse
Apologies. Requesting a removal.
Closed as a duplicated topic
Has anyone been able to successfully change the DPI or resolution? I haven't actually tried any of the apps from the Play Store, I saw a few brick warnings; not for FHD6, but, just being cautious. Any ideas or suggestions about how to do this; safely? Apps you've used? Math used? etc., Im on the latest OS, rooted.
---------- edit ----------
I came across this approach which requires the Xposed Framework and a module called App Status; which can be used to change the dpi of a specific app.
Can anyone confirm if this is possible coming from the latest, rooted FireOS/Lollipop? I like the idea of changing the dpi per app oppossed to the entire device, so this would be ideal. Specifically using the @bibikalka 453 method?
Something like this?
# install xposed apk + app settings module
$ adb install de.robv.android.xposed.mods.appsettings_v29_70ccc5.apk
$ adb install XposedInstaller_3.1.1.apk
# get to twrp
453_key-images.zip method via @bibikalka
# flash xposed in twrp (is this correct file?)
xposed-v87-sdk22-arm.zip
# flash the 5.5.2 bootloaders in twrp and reboot back to Lollipop
5.5.2_1534_stock_recovery_uboot.zip
Thoughts?
Thanks!
@vvxx_
This dpi change will work, pretty uneventfully too. Just make sure you flash the correct FireOS5 bootloaders back after 453 bootloaders & TWRP !
This dpi change will work, pretty uneventfully too. Just make sure you flash the correct FireOS5 bootloaders back after 453 bootloaders & TWRP !
Click to expand...
Click to collapse
10-4; thanks. Going to flash that exact file listed; same one I used to get to the latest OS. I just need the dpi change to work for 1 game, so hopefully it does just that; not really concerned about changing dpi/resolution of anything else.
I'm Back on XDA!
So, are you tired of the small amount of informations that you can have on your HUGE screen? You are in the right place.
WHAT DO I NEED?
First things first, you need to enable Debug usb under Developer Options (if you don't know how to enable Dev. Options this isn't your place)
After that, you need ADB installed on your computer (Windows/Linux/Mac), you can find it here [url]https://forum.xda-developers.com/showthread.php?t=2588979[/URL]
HOW TO
With Developer Options ENABLED, connect your phone to your pc and launch adb. In ADB type this command
Code:
adb shell wm density xxx
where xxx is your custom DPI value. I found that values BELOW 527 will bug your quick toggles*
*It could depend by your installed theme, Thanks to @SPIDER-7 for reporting that.
HOW DO I RETURN TO THE DEFAULTS VALUES?
Cave_diver said:
To return to the defaults just use the sliders in settings-display-display size
Click to expand...
Click to collapse
SCREENSHOTS
http://i.imgur.com/JyodBYe.png
http://i.imgur.com/fsW1Qtd.png
DISCLAIMER
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS MOD OR IF
YOU DO A MISTAKE DURING THIS PROCESS
I'm Italian so don't blame me for my english.
it works just fine! Thanks, @gsadv . keep it up!
Btw, I'm on value '500 and didn't notice any bugs . will challenge my G6 with lower values .
SPIDER-7 said:
it works just fine! Thanks, @gsadv . keep it up!
Btw, I'm on value '500 and didn't notice any bugs . will challenge my G6 with lower values .
Click to expand...
Click to collapse
Bugs on quick setting may depend by themes. For me 527 is fine, next step is try to get a smaller navbar
i'm going to try 527, but what is the default value if i decided to go back?
To return to the defaults just use the sliders in settings-display-display size
Sent from my LG-H870 using Tapatalk
Cave_diver said:
To return to the defaults just use the sliders in settings-display-display size
Sent from my LG-H870 using Tapatalk
Click to expand...
Click to collapse
original size 640