Changed the DPI using Android Tweaker 2 from 640 to 560, and when I rebooted somehow it set to 430, which is causing constant redraws of the screen (screen goes on off constantly) - the phone boots, and I can open the app, but it only gives me about 1 second to do something, and it's too quick for me to bring the keyboard up to set a different value.
How can I restore the default DPI or set it to 560 without reinstalling my phone. Is there a way I can do it on the computer?
Yes you can do it from your computer. You will have to edit a file called build.prop.
1: You will need ADB and the LG USB drivers. If you do not already have the Android SDK set up, download this tool to get ADB. You can get the USB driver here.
2: open a CMD window in the directory ADB is installed (seems the installer for ADB can also do this for you)
3: Go into your phone's Settings > About Phone. Tap the build number several times until it has said you have enabled developer options.
4: Go back to the main settings and go into Developer Options.
5: Find the "Android Debugging" option and turn it on. Find the "Root Access" option as well and set it to "Apps and ADB".
6: Connect your phone to your computer and type "adb devices" in the command prompt window. Hopefully, it lists a device on there.
7: Type "adb pull /system/build.prop %userprofile%\Documents"
8: Go to your computer's documents folder and open build.prop in your choice of file editor (Notepad works, but I wouldn't recommend it...)
9: Find the line "ro.sf.lcd_density" in build.prop. Change this to the number you want (540 or 640). Save the file.
10: Go back to the CMD window and type "adb push %userprofile%\Documents\build.prop /system/build.prop"
11: Reboot your phone. If all went well, your screen should be back to normal.
I can't seem to find Android Debugging or Root Access (I can only see USB Debugging which is enabled)
Also after typing "adb devices" in CMD, it lists mine but says offline.
Curleyyy said:
I can't seem to find Android Debugging or Root Access (I can only see USB Debugging which is enabled)
Also after typing "adb devices" in CMD, it lists mine but says offline.
Click to expand...
Click to collapse
USB Debugging will be the same thing.
Try typing "adb kill-server" and then "adb devices" again. Also try using a different USB port on your computer.
Related
When I try to run the "adb devices" command in the cmd prompt, its is just saying "List of devices attached", but the device Nexus 7 (2013) itself is not been listed. I am able to Kill and start the server. "adb reboot" command not working.
I checked the Device manger; It is listing the device as "Google Nexus ADB Interface" !
Also the "USB Debugging" is checked along with "MTP Device"
What could be the problem?? Any issue with drivers. I have already downloaded the adb and fastboot tools in the drive and running the cmd prompt from that path.
??
Tech2Yantra said:
When I try to run the "adb devices" command in the cmd prompt, its is just saying "List of devices attached", but the device Nexus 7 (2013) itself is not been listed. I am able to Kill and start the server. "adb reboot" command not working.
I checked the Device manger; It is listing the device as "Google Nexus ADB Interface" !
Also the "USB Debugging" is checked along with "MTP Device"
What could be the problem?? Any issue with drivers. I have already downloaded the adb and fastboot tools in the drive and running the cmd prompt from that path.
??
Click to expand...
Click to collapse
It's driver related, install these, then reboot the PC, then with the device plugged in, delete the Google Nexus ADB Interface from within device manager, delete the driver from system if prompted, and leaving the device plugged in, reboot the device, it should redetect the device properly, wait for it to boot up all the way, then unplug the device and plug it back in, and test, you will want to do this for every mode combination, as per my post found here: http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
The important part is making sure the device is plugged into your PC and set to the mtp/ptp/debug mode you want detected when you reboot the device after deleting the driver from device manager.
mdamaged said:
It's driver related, install these, then reboot the PC, then with the device plugged in, delete the Google Nexus ADB Interface from within device manager, delete the driver from system if prompted, and leaving the device plugged in, reboot the device, it should redetect the device properly, wait for it to boot up all the way, then unplug the device and plug it back in, and test, you will want to do this for every mode combination, as per my post found here: http://forum.xda-developers.com/showthread.php?p=50253887#post50253887
The important part is making sure the device is plugged into your PC and set to the mtp/ptp/debug mode you want detected when you reboot the device after deleting the driver from device manager.
Click to expand...
Click to collapse
Thank you for helping out. I found what was wrong. The drivers were ok. I had ticked the MTP device option earlier. When I ticked the Camera (PTP) instead, the ADB commands started working. I even rooted and installed custom recovery through adb interface.
Thank u once again.
Tech2Yantra said:
Thank you for helping out. I found what was wrong. The drivers were ok. I had ticked the MTP device option earlier. When I ticked the Camera (PTP) instead, the ADB commands started working. I even rooted and installed custom recovery through adb interface.
Thank u once again.
Click to expand...
Click to collapse
You're welcome, fwiw, if you follow my suggestions, you can make it so adb works in ptp and mtp, but if it's not important to you, then it's not dire.
Is there any reason that I can't get fastboot commands to work with W7 64bit ?
I've been using them fine for about 2 years but I think it was on a 32bit system.
Just got a new pc which is 64bit.
The drivers install but when I open a command box, in "platform tools", and type "fastboot devices" I don't get the serial number.
It's not the phone that's at fault because I get the serial number when I use a laptop running xp.
Cheers
Check your setup and ADB drivers. Also, when you run an adb command for the first time, you should see it starting the adb daemon. Make sure it is starting correctly, and that it is in the process list.
I will say that it works, because I just got my phone's serial number on my work machine, and last night I updated my N7 and old Galaxy S2, from a Windows 7 64-bit system.
jshamlet said:
Check your setup and ADB drivers. Also, when you run an adb command for the first time, you should see it starting the adb daemon. Make sure it is starting correctly, and that it is in the process list.
I will say that it works, because I just got my phone's serial number on my work machine, and last night I updated my N7 and old Galaxy S2, from a Windows 7 64-bit system.
Click to expand...
Click to collapse
Thanks for your reply but I can't work out what you mean in top paragraph. My fault, NOT yours.
Cheers
Edit... I've just remembered in the past seeing the "daemon starting" prompt, but didn't see it tonight.
10rdan said:
Thanks for your reply but I can't work out what you mean in top paragraph. My fault, NOT yours.
Cheers
Edit... I've just remembered in the past seeing the "daemon starting" prompt, but didn't see it tonight.
Click to expand...
Click to collapse
Depending on how you installed the adb driver and tools, you may need to ensure that the PATH is correct. For example, I installed my adb tools in the (unimaginatively named) c:\adb folder. I put that in the PATH by adding it to the Path line (My Computer -> Properties -> Advanced System Settings -> Advanced (tab) -> Environment Variables -> Path). If this is correct, you can run adb/fastboot from anywhere, which is helpful if you have multiple devices and keep all of their files in separate folders. I am using the "kit" adb file set, not the full developer version, so the only files in the folder are adb.exe, fastboot.exe, and a couple of adb DLLs.
The first time you run adb/fastboot, your system will check to see if the daemon is running. If it isn't, it will start it. If it starts it, you should see a line with the assigned port number. It varies, but is usually ~5000 (Mine was 5037 earlier). After that, it will just return the output of the command. You should be able to launch Task Manager and see adb.exe in the process list if everything is working.
Hi, i have acer e600 i nid help using fastboot ive read that if you try to hard reset using fastboot with command "fastboot -w" or "fastboot erase userdata" it will wipe ur internal storage.. The problem is the system is installed on my internal storage (2.50gb) idk if its the one they called emulated storage but is it safe to wipe my data because i forgot my password and i think it dont have recovery mode partition and usb debugging is unchecked.
Got ONE of the M8s to take fastboot commands.
Windows 7 64bit will only install "Microsoft approved drivers".
Got into "advanced settings" by constantly pressing f8 while pc boots. Selected "install unsigned drivers" or words to that effect.
Connected phone via usb, restarted into bootloader then fastboot. PC installed drivers from phone and got the "fastboot usb" flag.
Could then run fastboot commands and got phones serial number.
The pc will revert back to NOT installing drivers not approved by Microsoft after a reboot.
Problem I have now is that only one of the m8s "can be found", strange.
Edit....constantly pressing f8 on pc reboot takes you to "advanced options". That's where the option to install unsigned drivers is.
Hello all,
I have tried on different laptops, with different cables but my pixel c will not show the rsa dialog to allow access for adb/fastboot. I have tried NRT as well but the device cannot be found. The device is running the lastest software version as of 9/18/16
jasonc7649 said:
Hello all,
I have tried on different laptops, with different cables but my pixel c will not show the rsa dialog to allow access for adb/fastboot. I have tried NRT as well but the device cannot be found. The device is running the lastest software version as of 9/18/16
Click to expand...
Click to collapse
I think more detail is required. Device configured correctly? - Developer options - usb debugging enabled (also revoke debugging authorisations causes a request for RSA confirmation on a previously "connected perfectly" device). Guessing you're using Windows - what "adb" driver (if any) is shown in Device Manager
I've tried to revoke authorizations but nothing happens, and I can access the devices internal storage. However, when I plug the pixel c in, it immediately goes to charging mode and there isn't an mtp button in the storage settings in 7.0 so I can't toggle it on/off. I've also tried enabling/disabling debugging while connected and nothing happens.
I'll assume you have an "adb" driver of some form showing in Device Manager and adb.exe and fastboot.exe in a directory that I'll call "ADB".
Connect the Pixel C and unlock. By default it should have notifications for USB debugging enabled and "USB charging". Adb will work at this stage.
Open a command prompt and change to "ADB" Try the command "adb devices" and it should show your tablet.
Try "adb reboot bootloader" . I expect this command on your PC to fail because it holds no authorisation. But it should trigger:
a) get your tablet to request RSA authorisation
b) start the process of installing the "Android Composite ADB Interface" device driver (under "Android Device" in Device Manager.)
Repeat "adb reboot bootloader" and your tablet should reboot into a "waiting for fastboot command" screen
Try "fastboot devices" should show the tablet and then "fastboot reboot" will restart your tablet.
Pixel c not show up on adb devices list
Troubleshoot guide for updating the adb and fastboot drivers manually in a PC running any version of windows​
First, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
Pre-requisites:
* PC running windows 7/8/10
* Internet connection (just 20MB)
* Working USB cable
Steps:
(1) Download the [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 from XDA
Link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) Install it with "Y" confirmation for all 3 options and reboot the PC
(3) Disable the internet connection of your pc
(4) Reboot your phone to fastboot mode and plug it to your PC's USB 2.0 port (important)
(5) Open device manager on PC and scan for hardware changes from the option if your device is not listed already
(6) If it shows 'Asus android device' -> "ASUS Android Bootloader Interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) Now scan for hardware changes (magnifying glass icon)
(8) It will show 'Android' with an ! symbol
(screenshot 3)
(9) Right click -> Update driver -> Browse my computer for driver software
(10) Choose "Let me pick from a list of available drivers on my computer"
(11) Choose "Android device" or "Asus android device" or similar option and confirm it with Yes or Next option
(screenshot 4)
(12) A warning will pop up, press 'Yes'
Done
(13) Go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.
Nice... Thanks for the guide... Many people needed it... Was about to make one myself...
Great. Many many thanks bro
kickyvivi said:
troubleshoot guide for updating the adb and fastboot drivers manually in a pc running any version of windows​
first, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
pre-requisites:
* pc running windows 7/8/10
* internet connection (just 20mb)
* working usb cable
steps:
(1) download the [official][tool][windows] adb, fastboot and drivers - 15 seconds adb installer v1.4.3 from xda
link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) install it with "y" confirmation for all 3 options and reboot the pc
(3) disable the internet connection of your pc
(4) reboot your phone to fastboot mode and plug it to your pc's usb 2.0 port (important)
(5) open device manager on pc and scan for hardware changes from the option if your device is not listed already
(6) if it shows 'asus android device' -> "asus android bootloader interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) now scan for hardware changes (magnifying glass icon)
(8) it will show 'android' with an ! Symbol
(screenshot 3)
(9) right click -> update driver -> browse my computer for driver software
(10) choose "let me pick from a list of available drivers on my computer"
(11) choose "android device" or "asus android device" or similar option and confirm it with yes or next option
(screenshot 4)
(12) a warning will pop up, press 'yes'
done
(13) go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.
Click to expand...
Click to collapse
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )
Divyajeet90 said:
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )
Click to expand...
Click to collapse
I am having same problem... Did you find any solution for it?
kickyvivi said:
Troubleshoot guide for updating the adb and fastboot drivers manually in a PC running any version of windows​
First, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
Pre-requisites:
* PC running windows 7/8/10
* Internet connection (just 20MB)
* Working USB cable
Steps:
(1) Download the [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 from XDA
Link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) Install it with "Y" confirmation for all 3 options and reboot the PC
(3) Disable the internet connection of your pc
(4) Reboot your phone to fastboot mode and plug it to your PC's USB 2.0 port (important)
(5) Open device manager on PC and scan for hardware changes from the option if your device is not listed already
(6) If it shows 'Asus android device' -> "ASUS Android Bootloader Interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) Now scan for hardware changes (magnifying glass icon)
(8) It will show 'Android' with an ! symbol
(screenshot 3)
(9) Right click -> Update driver -> Browse my computer for driver software
(10) Choose "Let me pick from a list of available drivers on my computer"
(11) Choose "Android device" or "Asus android device" or similar option and confirm it with Yes or Next option
(screenshot 4)
(12) A warning will pop up, press 'Yes'
Done
(13) Go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.
Click to expand...
Click to collapse
Hello, I followed your mentioned steps but in my drivers its showing "Samsung Android Device" is that okay for my asus zenfone max pro m1 device? Or there is one portable device option, is that it?
Hi guys, specially opened an account because of this issue. I am unable to run the fastboot devices command even after following all the aforementioned steps. Phone screen turns black and a message appears on the top left stating "press any key to shutdown", while the fastboot devices command gives a "??????? fastboot" response on my PC. PLEASE HELP!
kickyvivi said:
(12) A warning will pop up, press 'Yes'
Done
Click to expand...
Click to collapse
After I completed all the steps, my phone showed on screen "press any key to shutdown" and even in device manager it shows android ADB interface as hidden. Help please. Rebooting again to fastboot mode doesn't help because it shows the same screen "press any key to shutdown" on reconnecting with PC.
May Asus x01bd can't in to the mode fastboot..how to solved it?
Kajin660 said:
May Asus x01bd can't in to the mode fastboot..how to solved it?
Click to expand...
Click to collapse
Well i learned this from somewhere but actually you need to turn off the secure boot in your PC from the BIOS. That's what helped me do it
D0CT0RFATE said:
Hi guys, specially opened an account because of this issue. I am unable to run the fastboot devices command even after following all the aforementioned steps. Phone screen turns black and a message appears on the top left stating "press any key to shutdown", while the fastboot devices command gives a "??????? fastboot" response on my PC. PLEASE HELP!
Click to expand...
Click to collapse
this same with me,, n i donk know how it is??
my phone asus x01bd
Nightmonkeyps said:
Well i learned this from somewhere but actually you need to turn off the secure boot in your PC from the BIOS. That's what helped me do it
Click to expand...
Click to collapse
can u explaining me?? sorry i dont understand what u mean??
Kajin660 said:
can u explaining me?? sorry i dont understand what u mean??
Click to expand...
Click to collapse
Well you know how there's a BIOS in your PC which contains the basic commands required to run a computer. There is a setting called secure boot inside your BIOS. You need to turn it off and then install fastboot tools. To open the BIOS, repeatedly press F10 or F8 on your computer while it is opening. This is how it worked for me atleast
Divyajeet90 said:
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )
Click to expand...
Click to collapse
this happen to me,, and i have solved this,,
step:
1. U must flash ur Phone via qfil,(*)
,than u will lost ur IMEI and SN will Change to 111111,, but dont worry thats can be back again
2. next step is u must recover ur IMEI and SN back (in tele group u wil found the step) after that U just flash stock firmware modified (via TWRP/ORFOX)n then ur phne willl back normally
Note : (*) in firmware for flash via qfil replace the recovery.img with twrp/orfox (rename To "recovery.img") this will bring u a twrp/orfox recovery after flash via qvil
i hope this can help..
help me please.
the same happens to me
crossf015 said:
help me please.
Click to expand...
Click to collapse
Explain
You need to have the correct drivers installed on you computer. Does you computer recognize your phone when you plug it into computers USB port ? If it does then install the latest ADB Fastboot software into a folder on C: drive not inside of other folders or libraries like shown in the 1st picture.
Then go to that folder and in the address bar show with arrow in 2nd picture 2) click mouse where the red arrow is to highlight like shown in 3rd picture then press delete key then type --> cmd ,like shown in 4th picture and press enter. Plug your phone into the computer with USB and type in the command terminal --> adb devices ,and you phone should be listed. From there you can reboot fastboot to see if you phone is still connected type --> fastboot devices , your phone should be listed.
My laptop only recognizes my phone when it is open and me enabling "file transfer" prompt/popup. I am om 6 pro and I can't open my phone because of the flicker issue. How can I at least access adb other than this?
oxbowlarry said:
You need to have the correct drivers installed on you computer. Does you computer recognize your phone when you plug it into computers USB port ? If it does then install the latest ADB Fastboot software into a folder on C: drive not inside of other folders or libraries like shown in the 1st picture.
Then go to that folder and in the address bar show with arrow in 2nd picture 2) click mouse where the red arrow is to highlight like shown in 3rd picture then press delete key then type --> cmd ,like shown in 4th picture and press enter. Plug your phone into the computer with USB and type in the command terminal --> adb devices ,and you phone should be listed. From there you can reboot fastboot to see if you phone is still connected type --> fastboot devices , your phone should be listed.
Click to expand...
Click to collapse