Hello Everyone!
Can somebody inform me on how to activate USB debugging when the screen is locked with a pin and the phone has stock software? Samsung phone with Nougat SW.
...
I have gotten this far with my windows 10 laptop which has adb tools installed:
Boot the phone the phone into Recovery Mode.
Select System Mount
Connect to PC and open CMD and change folder path where adb tools is located.
type adb devices in terminal
Now, the issue is that I see is a number followed by "unauthorized". I am trying to use commands such as adb shell, but seems like I am not allowed? I'm assuming it's because the phone is not USB Debug Enabled. I have a different phone which has USB Debug Enabled and adb shell commands are working perfectly. Any way to use shell commands or work arounds? Thanks in advance!
It is not possible to activate Debugging Mode with a locked screen. AFAIK it never was and it never will. And this is good as it is.
RossTeagan said:
3. Boot your phone into ClockworkMod Recovery, by pressing and holding the Power Button + Home Button + Volume Up or Down, depending on your phone
[/url]
Click to expand...
Click to collapse
Why or even HOW should he have ClockworkMod installed? your guide also is for making a Backup out of cwm when the touch is broken and not for activating debug mode
jaannnis said:
It is not possible to activate Debugging Mode with a locked screen. AFAIK it never was and it never will. And this is good as it is.
Why or even HOW should he have ClockworkMod installed? your guide also is for making a Backup out of cwm when the touch is broken and not for activating debug mode
Click to expand...
Click to collapse
Sorry, I thought it would help you...
Related
I have a broken screen and digitiser - I can see nothing at all on the screen and it does not recognise any touch movements.
The phone does appear to turn on and is recognised by my computer.
I want to retrieve all my data - photos, videos etc - from the internal SD card.
Unfortunately I did not have USB debugging enabled when the screen broke.
Is there a solution to achieve thiis?
COLDrum said:
I have a broken screen and digitiser - I can see nothing at all on the screen and it does not recognise any touch movements.
The phone does appear to turn on and is recognised by my computer.
I want to retrieve all my data - photos, videos etc - from the internal SD card.
Unfortunately I did not have USB debugging enabled when the screen broke.
Is there a solution to achieve thiis?
Click to expand...
Click to collapse
Connect with usb and copy your files to the pc You don`t need usb for that.
Thanks for your reply Gee but that was, oddly enough, the first thing I tried.
The computer recognises the device as a portable media player and there are no files found in the device.
COLDrum said:
Thanks for your reply Gee but that was, oddly enough, the first thing I tried.
The computer recognises the device as a portable media player and there are no files found in the device.
Click to expand...
Click to collapse
Maybe my original post wasn't too clear.
I need to retrieve all my data from the S4, and the conventional method of plugging in to my computer via USB does not recognise any data. Would I possibly have to select to mount the card to view? Either way, this is not an option due to the broken screen.
My next thought was to use ADB to transfer over all the content of the internal SD card, however, my S4 is not recognised using ADB (I assume as USB debugging was not enabled when my phone broke?)
So, is it possible to enable USB debugging without use of the screen on this device?
COLDrum said:
Maybe my original post wasn't too clear.
I need to retrieve all my data from the S4, and the conventional method of plugging in to my computer via USB does not recognise any data. Would I possibly have to select to mount the card to view? Either way, this is not an option due to the broken screen.
My next thought was to use ADB to transfer over all the content of the internal SD card, however, my S4 is not recognised using ADB (I assume as USB debugging was not enabled when my phone broke?)
So, is it possible to enable USB debugging without use of the screen on this device?
Click to expand...
Click to collapse
do you have custom recovery on your phone??
No, the phone is entirely stock.
I'm still holding out hope that someone has seen this happen before and knows of a solution for me to retrieve my data?
Can anyone help me with this?
COLDrum said:
Can anyone help me with this?
Click to expand...
Click to collapse
Impossible bro.
gee2012 said:
Impossible bro.
Click to expand...
Click to collapse
So, I have lost all my photos etc that are on my phone?
COLDrum said:
So, I have lost all my photos etc that are on my phone?
Click to expand...
Click to collapse
i think there is a way if you flash custom recovery
samersh72 said:
i think there is a way if you flash custom recovery
Click to expand...
Click to collapse
Can I flash customer recovery, though, as I can't see my screen?
You could install ClockworkMod Recovery and use ADB to retrieve your data while it's in recovery. You can put your phone in download mode by pressing and holding Volume Down, Home and Power buttons till it vibrates. Then press Volume Up to confirm that you want to enter download mode. You should then be able to use Odin to install ClockworkMod Recovery.
COLDrum said:
Can I flash customer recovery, though, as I can't see my screen?
Click to expand...
Click to collapse
you can boot in download mode and flash it without screen. see if odin recognize it
In my opinion if u could turn on usb debugging that would not bring back your lost data. Not really sure though. You could do that by connecting a micro usb to hdmi cable to your tv and then i guess you could use the phone there, not sure if the touchscreen would work though but worth a try..
Sent from my GT-I9500 using xda premium
Thanks - I have flashed CWM via Odin successfully.
I have installed ADB but my device does not get recognised as an ADB device - have I missed something?
COLDrum said:
Thanks - I have flashed CWM via Odin successfully.
I have installed ADB but my device does not get recognised as an ADB device - have I missed something?
Click to expand...
Click to collapse
be sure that you boot in custom recovery, connect your phone, open cmd in adb folder (shift + right click) and type (no need to enable usb debug):
Code:
adb devices
you must see the serial number (in recovery mode)
Code:
adb pull /sdcard/
use attached adb folder
samersh72 said:
be sure that you boot in custom recovery
Click to expand...
Click to collapse
Because I can't see the phone I'm not sure the state it's in.
Is it just Volume-up + Home + Power to access customer recovery?
I can now see the device in ADB.
When I run the adb pull /sdcard/ command I get an
error: device unauthorised. Please check the confirmation dialog on your device.
COLDrum said:
I can now see the device in ADB.
When I run the adb pull /sdcard/ command I get an
error: device unauthorised. Please check the confirmation dialog on your device.
Click to expand...
Click to collapse
hmmm do you read "recovery" in command line after the serial number?
there is a dialog box showed on your broken screen, try to tap on, maybe you will hit confirmation
EDIT: your digitizer is broken!......no way to recognize touch.....
Current problems:
Developer options not enabled and USB debugging mode not on.
Anyone know how to solve this?
What are you trying to do? You can flash a custom recovery from fastboot and use adb in that, none of that requires a working digitizer.
DrFredPhD said:
What are you trying to do? You can flash a custom recovery from fastboot and use adb in that, none of that requires a working digitizer.
Click to expand...
Click to collapse
The problem lies with the phone not being detected by the computer because USB debugging isn't enabled.
ItsBeepo said:
The problem lies with the phone not being detected by the computer because USB debugging isn't enabled.
Click to expand...
Click to collapse
What are you trying to do? Why do you think you need USB debugging enabled?
DrFredPhD said:
What are you trying to do? Why do you think you need USB debugging enabled?
Click to expand...
Click to collapse
Well I'm trying to install AirDroid so I can use my phone without using the digitizer since it's broken.
I plug it into the computer and try to push adb commands but can't.
I did find another way to work it by booting into Recovery which allows me to push in commands but not sure of what to do from here.
From recovery. 'adb install airdroid.apk' (or whatever your file is called)
DrFredPhD said:
From recovery. 'adb install airdroid.apk' (or whatever your file is called)
Click to expand...
Click to collapse
How would I actually start up the App though when I'm back on?
Edit:
Sigh, I'm sooo lost.
Wish I can just use an OTG wire and navigate with my mouse but no, Google has taken that away from me too
Can anyone else help?
You can get applications to start at boot a few ways.
http://stackoverflow.com/questions/4567904/how-to-start-an-application-using-android-adb-tools
Hello all,
I recently dropped my phone, shattering the screen and rendering the LCD useless. I need to use my phone to access some important messages, so I am trying to use Android Control to emulate my phone until I can get a new one. The problem is I didn't have USB debugging turned on when I dropped it. To fix that, I am trying to use ADB and recovery mode to turn it on, but ADB can't/won't recognize my device. I have installed the universal adb driver and my phone shows up in the device manager, but when I run "adb devices" in the command prompt, nothing comes up. Any help is much appreciated!
Thanks!
lonshlon said:
Hello all,
I recently dropped my phone, shattering the screen and rendering the LCD useless. I need to use my phone to access some important messages, so I am trying to use Android Control to emulate my phone until I can get a new one. The problem is I didn't have USB debugging turned on when I dropped it. To fix that, I am trying to use ADB and recovery mode to turn it on, but ADB can't/won't recognize my device. I have installed the universal adb driver and my phone shows up in the device manager, but when I run "adb devices" in the command prompt, nothing comes up. Any help is much appreciated!
Thanks!
Click to expand...
Click to collapse
Did you have TWRP installed? (Unlocked bootloader?)
If not, I don't know of any way to turn on ADB.
If TWRP is installed you boot into recovery and you are good.
tech_head said:
Did you have TWRP installed? (Unlocked bootloader?)
If not, I don't know of any way to turn on ADB.
If TWRP is installed you boot into recovery and you are good.
Click to expand...
Click to collapse
Unfortunately I don't have TWRP installed
Unfortunately I don't have TWRP installed
No USB debugging and no twrp and no LCD ....
That's a no go.
Hi, my 6p will not show up on my PC. Have tried installing drivers, different PC, different cable but nothing works.
I recently upgraded to android O. I extracted the files from system image and flashed boot image, vendor image, and system. But now when I try to go into recovery it says no command and I lost root access but my bootloader is unlocked. I never flashed the recovery thinking TWRP would stay intact but I guess I was wrong. Normally I would just use ADB and fix it but hence my problem. Is there any way to root without PC or any way I can fix my situation?
Having the same exact issue here, hope someone has a way to fix it.
sonysingh1983 said:
Hi, my 6p will not show up on my PC. Have tried installing drivers, different PC, different cable but nothing works.
I recently upgraded to android O. I extracted the files from system image and flashed boot image, vendor image, and system. But now when I try to go into recovery it says no command and I lost root access but my bootloader is unlocked. I never flashed the recovery thinking TWRP would stay intact but I guess I was wrong. Normally I would just use ADB and fix it but hence my problem. Is there any way to root without PC or any way I can fix my situation?
Click to expand...
Click to collapse
So your phone will boot into the OS, or not? If so, make sure USB debugging is set to "on" in Developer Settings. Can you put your device in fastboot mode by holding down the volume down button before hitting the power button? The "no command" means you are in (stock) recovery. You then have to hold the power button down while using the volume buttons to navigate. Power button is confirm. Get your phone into bootloader mode and use ADB to flash TWRP again. @meoshe
v12xke said:
So your phone will boot into the OS, or not? If so, make sure USB debugging is set to "on" in Developer Settings. Can you put your device in fastboot mode by holding down the volume down button before hitting the power button? The "no command" means you are in (stock) recovery. You then have to hold the power button down while using the volume buttons to navigate. Power button is confirm. Get your phone into bootloader mode and use ADB to flash TWRP again. @meoshe
Click to expand...
Click to collapse
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
sonysingh1983 said:
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
Click to expand...
Click to collapse
Gotcha. What about the other points? Entering bootloader mode from a powered off state, and that you are in Recovery mode (no command), and navigating thru it with the power+volume buttons?
v12xke said:
Gotcha. What about the other points? Entering bootloader mode from a powered off state, and that you are in Recovery mode (no command), and navigating thru it with the power+volume buttons?
Click to expand...
Click to collapse
Yes that works. Thank you. But still can't root phone and can't flash TWRP. Was looking at a root APK but not sure if they will work with O. If I could root then I could install TWRP thru it's app but I need root for that.
You can't root the phone until you have a working custom recovery. Focus on either fastboot flashing or fastboot booting TWRP.img
v12xke said:
You can't root the phone until you have a working custom recovery. Focus on either fastboot flashing or fastboot booting TWRP.img
Click to expand...
Click to collapse
How do I go about fastboot booting TWRP image?
I can get into bootloader from phone but I can't use a PC.
I did read your OP, but this sounds like a driver issue. There are two drivers that need to be installed first the USB and then fastboot. Since you can boot the device and use it, maybe you should try NRT by Wugfresh to install, test and confirm the drivers are properly installed. Booting or flashing TWRP is just a different command. Instead of fastboot flash recovery twrp.img, you use fastboot boot recovery recovery.img. The NRT toolkit can also either boot or flash a recovery image.
EDIT: Also try "Revoking ADB debugging" and re-enabling @sonysingh1983
sonysingh1983 said:
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
Click to expand...
Click to collapse
Hi, just tried the mtp setting in developer options. Didn't get it the first time but now am able to access internal storage. I have plug sound app from play installed and I get a notification sound when plugging and unplugging. First try there was no sound when changing from charging to mtp. Ok after repeating it. Hope that helps.
Just as a follow up I got my win10 pc to recognize my O flashed nexus. I booted into bootloader after I had updated my sdk and drivers through android studio. It recognized the phone but nothing was happening. I rebooted into the os and the access allow prompt popped up on the phone and adb was able to see it under listed devices.
Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk
There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.
madbat99 said:
There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.
Click to expand...
Click to collapse
Few other thoughts:
- try a different cable; a cable that works for charging and adb communication may not work with fastboot
- avoid external hubs if possible
- be sure to reboot both devices after switching drivers if communication isn't immediately established
Marc_Xperia said:
Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk
Click to expand...
Click to collapse
When you say you booted to fastboot what do you mean ?
Did use adb and your phone was recognized and then you issued adb command or what method are you using ....
You need to ensure you establish USB debugging connection first & grant authorization ...once link with authorization has been established run adb ...from adb check if recognized run command to boot to fastboot
So start from the top && go down
ARE YOU CERTAIN YOU USED CORRECT METHOD TO TURN OFF DRIVER VERIFICATION ON WINDOWS 10 && YOUR DRIVER ACTUALLY INSTALLED
Last noteworthy point ... when unlocking my motoE4 I had to boot to bootloader ONLY to use fastboot NOT "FASTBOOT"
Hold power + volume button
Excellent troubleshooting from our community. OP has not come back yet to confirm, ask another question, or simply a thanks. (Maybe he got it) Hopefully he gets it sorted.
Maybe the junior members underestimate just how quick and helpful our little community can be.
@Marc_Xperia Do not forget to install AndroidBootloaderInterface Driver Software. *android_winusb.inf*
Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.
Marc_Xperia said:
Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.
Click to expand...
Click to collapse
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works
KevMetal said:
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works
Click to expand...
Click to collapse
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.
Marc_Xperia said:
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.
Click to expand...
Click to collapse
Why select meta mode ? When you are in bootloader you use your volume keys to navigate between meta, recovery& factory reset & meta and you use your power key to select different modes ...what do you want to do in meta mode ?
When you are in bootloader you are essentially in fastboot mode too so it isn't necessary to choose any of the other options unless you are trying to get into recovery which is pointless if you haven't flashed custom recovery yet ..
I Succeded. I Booted into Bootloader with ADB and took a look at Device Manager to install the Driver Properly.
i followed this guide https://forum.xda-developers.com/moto-e4/how-to/guide-unlock-moto-e4-bootloader-unique-t3654275.
Thank you for all of your Replys.
Moto e4 magisk manger trying to instal magisk hide props config says install failed
happymedium22026 said:
Moto e4 magisk manger trying to instal magisk hide props config says install failed
Click to expand...
Click to collapse
Download manually and flash inside recovery yourself
Safety net says the response is invalid does that affect ny device being rooted
happymedium22026 said:
Safety net says the response is invalid does that affect ny device being rooted
Click to expand...
Click to collapse
No it doesn't. That's an error in magisk manager when you hide the manager app itself. Just use a different safetynet checker app if you want to check safetynet.
Why are you posting this stuff in this thread?