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?
Related
I'm wondering if anyone has run into this problem before?
I'm trying to unlock the bootloader on my friend's Photon Q, I downloaded the SDK and installed the Motorola drivers. But when I put his phone into Fastboot mode, the "fastboot oem get_unlock_data" command does not work and CMD just says waiting for devices.
Yes I'm shift+right clicking on the platform-tools folder in the SDK to run the Command Prompt and I did download the correct Fastboot file. The command "adb devices" shows nothing when his phone is plugged in, but it shows my own phone (A Motorola Droid Bionic) when it's plugged into the USB cable. RSD Lite also recognizes both phones when powered on or in Fastboot mode.
I have no idea what to do at this point, we just need to get that unlock data to plug into the Moto site. Would it be possible to use someone else's unlock key or is each one randomized individually for the device? Or would that even work because my computer can't do the command for the unlock data, so maybe it couldn't push the unlock key onto the phone?
quick thought: did you enable usb debugging on the device?
edit: i guess that wouldn't make any difference in fastboot mode...
anyway, yeah, i'm pretty sure each device has it's own unique code. it's odd that fastboot recognizes the device, but the command isn't working. i bet you will get it somehow tho. a similar thing actually does happen to me sometimes, and in my case, it is because my usb ports are going bad and the computer loses connection with the phone.
Man nobody has anything eh? That's a crying shame. I tried using a different computer and went through the same course and still nothing.
I did try USB debugging on and off on both machines, didn't change a thing.
In order for the drivers (and therefore adb) to pick up the phone, I needed usb debugging *and* the phone not to be in charge only mode. Maybe that will help?
If not, when you reboot to fastboot and connect the cable, look at the devices installing list (if win 7) or device manager, and confirm the pc sees the fastboot device. If not you may need to reinstall the driver. Strange I know, but I needed to after getting my unlock data, holding off on unlocking due to the warranty voiding note, then trying again a couple days later where it wouldn't recognize. Seems to be finicky drivers to match a finicky device. But I do love this keyboard lol...
Sent from my XT897 using Tapatalk 2
We've only ever tried it in MTP mode and USB debugging enabled. This is day three of plugging it in and pulling it out and still no go. This is a royal pain, that is for sure.
Download Motorola Device Manager from the website, install, plug in phone. Place the phone into mass storage mode WITHOUT debugging enabled, then other modes, then back into bootloader mode then into fastboot mode. This will install EVERY driver, I didn't see that as one of the things tried.
Once you are in those modes, Android ADB device driver will install.
Hope that helps...
Sent from my XT897 using xda premium
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:
Dear all,
Please Help me. My One plus one is on CM12 official rom (rooted). Problem is when I connect my phone to computer and use ADB it is detected (adb devices: number & devices detected) but when in fastboot (fastboot devices : nothing is detected) I check in my device manager (yellow triangle on android ) My problem is why CAN it be detected when my phone is on but NOT during fastboot.
Necessary checks done : USB debugging, Universal driver, SDK installed, USB driver reinstalled again, tried changing usb ports on computer, tried on 2 laptops)
I am helpless, tried checking on forums can not find the answer.
CalvinVeez said:
Dear all,
Please Help me. My One plus one is on CM12 official rom (rooted). Problem is when I connect my phone to computer and use ADB it is detected (adb devices: number & devices detected) but when in fastboot (fastboot devices : nothing is detected) I check in my device manager (yellow triangle on android ) My problem is why CAN it be detected when my phone is on but NOT during fastboot.
Necessary checks done : USB debugging, Universal driver, SDK installed, USB driver reinstalled again, tried changing usb ports on computer, tried on 2 laptops)
I am helpless, tried checking on forums can not find the answer.
Click to expand...
Click to collapse
Have test to fastboot commands?
In fastboot be unplugged
Write
fastboot reboot
for test
Will answer wait for device
Plug device to test
My pc also does not recognise but work fine
with commands
geowolf1000 said:
Have test to fastboot commands?
In fastboot be unplugged
Write
fastboot reboot
for test
Will answer wait for device
Plug device to test
My pc also does not recognise but work fine
with commands
Click to expand...
Click to collapse
Tried adb reboot bootloader then phone boots into fastboot mode but from here..
is total no connection. Tried checking fastboot devices (nothing), fastboot reboot (waiting)
then i tried as u said unplug & plug in (not recognize) from here adb cannot be written anymore. (no more commands can be typed). Tried others like down loading Pdanet ,force install driver..Nothing works. Thinking ,did I corupt the bootloader while I was rooting it last time.?
I think if something was wrong with bootloader you could not either boot .
Do you use antivirus to pc?
Try without antivirus
What happening the false is from computer
Mine is reverse issue. When in fastboot mode, pc recognizes OPO, but when OPO is normally connected to pc, adb is not working. Its charging and can transfer data through USB, but OPO is not recognized through adb commands. Device Manager too recognizes my OPO only when it is in fastboot mode and not when normally connected via USB for data transfer.
I have a software, through which I can REVERSE TETHER my PC's internet to my mobile via USB. Because my OPO is not recognized via USB in normal mode, I can't do that. Any idea, what's wrong with my OPO.
(I have installed Android SDK and google usb drivers, for my OPO to work in fastboot. I have rooted. My pc runs on win7)
mrsureshisha said:
Mine is reverse issue. When in fastboot mode, pc recognizes OPO, but when OPO is normally connected to pc, adb is not working. Its charging and can transfer data through USB, but OPO is not recognized through adb commands. Device Manager too recognizes my OPO only when it is in fastboot mode and not when normally connected via USB for data transfer.
I have a software, through which I can REVERSE TETHER my PC's internet to my mobile via USB. Because my OPO is not recognized via USB in normal mode, I can't do that. Any idea, what's wrong with my OPO.
(I have installed Android SDK and google usb drivers, for my OPO to work in fastboot. I have rooted. My pc runs on win7)
Click to expand...
Click to collapse
Install pdanet+ for win
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.
Hey guys,
I am Currently attempting to unlock the bootloader on my Pixel 6a, but when I attempt to connect via fastboot in the bootloader my PC shows nothing connected? I can push commands through ADB while the device is booted and have full functionality, but as soon as I reboot the device into the bootloader I lose connection to my PC. OEM Unlocking is enabled in the settings and I have toyed with updating it to the latest update and factory resetting the device. It shows correctly in device manager as 'Pixel 6a' while USB Debugging is disabled and as 'android composite ADB interface' while it is enabled.
To clarify as I am sure many have seen this issue before I do not believe it do be a driver issue as the device will not show up at all in device manager, not even showing with the incorrect driver (No ding to indicate a device has been connected). I have tried using 2 different USB C -> A cables in all slots of two entirely seperate PC's (Both running Windows 10). When I enter fastboot with OEM Unlocking disabled it acts no different to when it is enabled.
I appreciate any help or insight any of you folks can give me.
Device is currently running Android 13 Build number TQ2A.230505.002 if you need anymore info please let me know.
The OEM Unlocking toggle does not affect whether USB function works. It is only a "safety" that allows unlocking the bootloader.
Have you ensured you've installed the correct drivers? Google USB Drivers
I have spent a long time looking at drivers, but I have no device to install the drivers to as the connection drops out once I eneter the bootloader. I have used Zadig in the past to install the correct drivers for devices but when I reconnect the device while I have it open it cannot even detect a new device being connected to the PC. (Also no audible tone which would be heard even with incorrect drivers) I actually only recently used Zadig to install the correct WinUSB drivers for my S10e in which I connected it to my PC in download mode (Queue audible ding) and used Zadig to overwrite the incorrect driver with the correct one. It's almost as if the device will not communicate while it is in Bootloader mode?
I assume you have checked with the 'fastboot devices' command to see if your device is connected when in fastboot mode?