Hello,
I broke my screen and I want to use the androidscreencast in order to recover some data on my Samsung GT-I9195.
I installed ADB version 1.4.2.
When I plug my phone on my computer (win7), the phone is recognized and I can browse its content.
But the command adb devices returns nothing:
"List of devices attached:
"
Edit: I first tried to recover my phone with Kies but the phone is not recognized.
Can somebody help me?
Thanks in advance.
V.
vzhache said:
Hello, I broke my screen and I want to use the androidscreencast in order to recover some data on my Samsung GT-I9195.
I installed ADB version 1.4.2.
When I plug my phone on my computer (win7), the phone is recognized and I can browse its content.
But the command adb devices returns nothing:
"List of devices attached:"
Can somebody help me?
Thanks in advance.
V.
Click to expand...
Click to collapse
Before I start suggesting soloutions/ideas was USB Debugging enabled through developer options before the screen smashed as if not there's not much you can do via ADB.
TechMinerUK said:
Before I start suggesting soloutions/ideas was USB Debugging enabled through developer options before the screen smashed as if not there's not much you can do via ADB.
Click to expand...
Click to collapse
Unfortunately, debugging mode is not activated.
Is the activation of debugging mode mandatory for connecting a mobile thanks to adb?
vzhache said:
Unfortunately, debugging mode is not activated.
Is the activation of debugging mode mandatory for connecting a mobile thanks to adb?
Click to expand...
Click to collapse
I'm afraid that debugging mode is necessary for an adb connection to the device.
TechMinerUK said:
I'm afraid that debugging mode is necessary for an adb connection to the device.
Click to expand...
Click to collapse
I may probably dream, but is there a chance to activate the debug mode with a broken screen?
vzhache said:
I may probably dream, but is there a chance to activate the debug mode with a broken screen?
Click to expand...
Click to collapse
You would need very good gueswork :crying:
Related
Hello,
I'm trying to make my PC find an Allview E4 lite in fastboot mode, using ADB, but it says "No device found". I installed the usb drivers, google drivers, it won't work.
Could you give me some tips please?
Thanks in advance
stormeye25 said:
Hello,
I'm trying to make my PC find an Allview E4 lite in fastboot mode, using ADB, but it says "No device found". I installed the usb drivers, google drivers, it won't work.
Could you give me some tips please?
Thanks in advance
Click to expand...
Click to collapse
Hello,
Do you Android SDK installed? Or which fastboot tool are you using?
Also is USB Debugging checked in the developers option of your device?
Regards
Vatsal,
Forum Moderator.
Hello,
Thank you for your reply.
Yes, I do have the Android SDK installed. The USB debugging is not checked and I can't enable it due to pattern lock.
I turned the phone off, kept volume + pressed and power button, then selected fastboot. Afterwards I tried inputting command from here (http://forum.xda-developers.com/showthread.php?t=2620456), but the ADB won't locate my device.
Also, the phone does not have any recovery mode.
Thank you
stormeye25 said:
Hello,
Thank you for your reply.
Yes, I do have the Android SDK installed. The USB debugging is not checked and I can't enable it due to pattern lock.
I turned the phone off, kept volume + pressed and power button, then selected fastboot. Afterwards I tried inputting command from here (http://forum.xda-developers.com/showthread.php?t=2620456), but the ADB won't locate my device.
Also, the phone does not have any recovery mode.
Thank you
Click to expand...
Click to collapse
Hello,
Unless you have USB debugging enabled, adb won't detect your device.
Regards
Vatsal,
Forum Moderator.
I found a workaround with the aroma, thank you for replying.
Hey Guys,
I have currently the stock NXTL29C432B320 firmware on my mate 8.
I want to unlock the bootloader, but my laptop can't see my Mate 8.
I installed HiSuite & adb universal drivers, but i cant connect with HiSuit. File transfer is possible but the DC unlocker tool and every other tool cant see it.
Also tried to install the HiSuit apk manually on my phone.
Usb debugging is activated and HiSuite HDB option also.
In adb it shows unauthorized
C:\adb>adb devices
List of devices attached
DLQ0215C25012187 unauthorized
Can someone help me?
Thanks
karakatos said:
Hey Guys,
I have currently the stock NXTL29C432B320 firmware on my mate 8.
I want to unlock the bootloader, but my laptop can't see my Mate 8.
I installed HiSuite & adb universal drivers, but i cant connect with HiSuit. File transfer is possible but the DC unlocker tool and every other tool cant see it.
Also tried to install the HiSuit apk manually on my phone.
Usb debugging is activated and HiSuite HDB option also.
In adb it shows unauthorized
C:\adb>adb devices
List of devices attached
DLQ0215C25012187 unauthorized
Can someone help me?
Thanks
Click to expand...
Click to collapse
Developer mode turned on??
p51d007 said:
Developer mode turned on??
Click to expand...
Click to collapse
Yes sure.
Did you allow access on your phone when you want to connect it to the ADB console on your PC?
I accidentality flashed a wrong oreo Chinese firmware on my international mate (nxt-L29), with that I'm stuck with booth bootloader and FRP lock ("enable OEM unlock" option in developer mode sitting is greyed).
in attempt to resolve this problem I'm asked to put USB ports setting on Manufacture mode in ProjectMenu witch i can't access via *#*#2846579#*#* code on phone.
it shows nothing.
help please....
is there any other method to enable Manufacture mode in usb setting like adb command ?????
note:
when i was in the upgrade mode (phone off, press the tow volume button up and down then connect the micro usb cable) i noticed the device respond to ADB commands and it's detected but unauthorized.
is there a way to make adb works.
tarekcod said:
note:
when i was in the upgrade mode (phone off, press the tow volume button up and down then connect the micro usb cable) i noticed the device respond to ADB commands and it's detected but unauthorized.
is there a way to make adb works.
Click to expand...
Click to collapse
you need to activate usb debugging first in the setting then it will give authorized
ceriqdesign said:
you need to activate usb debugging first in the setting then it will give authorized
Click to expand...
Click to collapse
I'm talking about the upgrade mode here.
tarekcod said:
I'm talking about the upgrade mode here.
Click to expand...
Click to collapse
Haha..#2nd post you said about adb unauthorized..so i respond to the question..
I'm already experienced in custom ROMs and root... However this time the adb tools can't detect my phone even if it's attached by the original cable, and also the drivers are installed correctly + i allowed the USB debugging.
Any suggestions?
Or Sdk platform tools alternatives
Btw i want to reinstall a custom recovery for the phone.
Does phone connect in MTP mode?
jwoegerbauer said:
Does phone connect in MTP mode?
Click to expand...
Click to collapse
No
My guess is you havent't installed the "Android USB Driver" suitable to your phone.
BTW: ADB Tools? I've never heard / read of them.
I rooted my Samsung A9 2018 SM-A920F, but now i have problems with smalipatcher to mock gps. I installed Java, but an error occurs. NO ABD devices found. I tried it with platform tools, in device manager i tried to update drivers, but keeps saying best drivers are installed, but the phone is still not recognised. OEM debug and OEM unlock is on, tried to revoke oem debug as well, but smalipatcher still cant find phone. Tried different cables as well. Someone that can help me?
Add Samsung A9 2018 SM-A920F to this thread's title thus mainly owners of such device get addressed.
Lucvdkant said:
I rooted my Samsung A9 2018 SM-A920F, but now i have problems with smalipatcher to mock gps. I installed Java, but an error occurs. NO ABD devices found. I tried it with platform tools, in device manager i tried to update drivers, but keeps saying best drivers are installed, but the phone is still not recognised. OEM debug and OEM unlock is on, tried to revoke oem debug as well, but smalipatcher still cant find phone. Tried different cables as well. Someone that can help me?
Click to expand...
Click to collapse
What does
Code:
adb devices
return?
jwoegerbauer said:
What does
Code:
adb devices
return?
Click to expand...
Click to collapse
Nothing. Gives no number. I rebooted my usb drivers as well. When I connect the usb and check device manager it adds Samsung Android Phone en when i open it gives Samsung Android ADB interface. My phone does not pop up as Samsung A9 but as MTP-USB-device
Lucvdkant said:
Nothing. Gives no number. I rebooted my usb drivers as well. When I connect the usb and check device manager it adds Samsung Android Phone en when i open it gives Samsung Android ADB interface. My phone does not pop up as Samsung A9 but as MTP-USB-device
Click to expand...
Click to collapse
You have to switch phone's USB mode to ADB.
jwoegerbauer said:
You have to switch phone's USB mode to ADB.
Click to expand...
Click to collapse
OEM unlocking and USB debugging are on, I put default usb configuration on Transferring files. Is that what you Megan? How do I put it on ADB?
Lucvdkant said:
OEM unlocking and USB debugging are on, I put default usb configuration on Transferring files. Is that what you Megan? How do I put it on ADB?
Click to expand...
Click to collapse
Your phone is configured to connect to phone via USB in Media Transfer Protocol (MTP) mode what is for transfering files.
As already said you have to configure phone that it connects via USB in Android Debug Bridge (ADB) mode.
IDK how you can achieve this because I don't have a phone as yours.
Follow my advice given in post #2
jwoegerbauer said:
Your phone is configured to connect to phone via USB in Media Transfer Protocol (MTP) mode what is for transfering files.
As already said you have to configure phone that it connects via USB in Android Debug Bridge (ADB) mode.
IDK how you can achieve this because I don't have a phone as yours.
Follow my advice given in post #2
Click to expand...
Click to collapse
Thanks, My device is not found in platform tools using the adb devices command, but it's on OEM unlock and USB Debugging is on. I added the phone in the tiltle, hope someone had an solution for my problem. Don't understand why it's not working. When I connect phone without the USB debugging it get's recognised, but with debugging mode on, nothing to find
Lucvdkant said:
Thanks, My device is not found in platform tools using the adb devices command, but it's on OEM unlock and USB Debugging is on. I added the phone in the tiltle, hope someone had an solution for my problem. Don't understand why it's not working. When I connect phone without the USB debugging it get's recognised, but with debugging mode on, nothing to find
Click to expand...
Click to collapse
Enabling OEM Unlock and/or USB Debugging simply sets an allowance flag, nothing else. It doesn't configure phone's USB mode.
I tried it on the laptop from work and there the phone is recognized in adb. But sadly I don't have administrator rights on that laptop to open Smalipatcher. Is there an alternative or work around available?