Thanks for reading.
I have Android Studio installed, and installed the USB drivers from Samsung's site.
On the phone (SM-J337P) I have enabled USB debugging and granted my PC access. I have also enabled OEM Unlocking.
adb works fine:
Code:
C:\Users\Stretch\Desktop> adb devices
List of devices attached
52004c578d1c16cd device
C:\Users\Stretch\Desktop>
I can easily but the phone into download mode by holding Vol-, Power, and Home. Once I have the phone in download mode, fastboot cannot see it:
Code:
C:\Users\Stretch\Desktop> fastboot devices
C:\Users\Stretch\Desktop>
When the phone is in download mode, Windows' Device Manager lists it under USB devices as "SAMSUNG Mobile USB CDC Composite Device"
If I try to update the drivers and select The Google USB Driver (from Android Studio) or the driver I downloaded from Samsung is says I already have the latest version.
How should I proceed to troubleshoot this and get fastboot to recognize the phone?
UPDATE: Never mind. I was in Odin mode, not Download mode. There is no download mode on this phone. I'm a moron.
Related
As the title suggests, bootloader unlocked no problem, tablet was connecting to ADB at the time, tried to flash recovery which as far as I can tell was not successful (I can't boot to recovery, get the injured Android icon), now I can't connect to ADB (get the "List of devices attached" result). So I'm completely stuck, can't move forward, can't go back to stock, what do I do?
Edit: Apparently it's an issue with my PC, my wife's PC worked fine, why it worked to unlock the bootloader and then stopped I have no idea. Can anyone link me to a solution to get ADB working on my PC again? I tried removing/re-installing drivers, rebooting, you name it, no luck.
With your device booted into recovery or the system do you get anything in device manager? If you get a device with a yellow exclamation mark, right click it. Go to where it allows you to choose a driver from a list on your computer. Select adb android composite (or something like that)
Sent from my Nexus 5 using XDA Free mobile app
Thanks for replying.
So before unlocking the bootloader, with USB debugging enabled I could get the tablet to connect using the ADB driver and could access it with ADB but could not access storage for file transfer, with USB debugging disabled and switching the driver manually to the MTP driver I could access storage but not ADB. I have had other device drivers installed on this PC for my Galaxy phones, I had issues initially with the tablet connecting but showing a yellow exclamation mark, then I removed all of the Android USB devices using USBDeview and installed the 15 second ADB tool to get it working, I'm on Windows 8.1 BTW.
After unlocking the bootloader, with USB debugging enabled I cannot get the tablet to connect using the ADB driver and but it does show as an ADB device with no yellow exclamation mark, I just get the "List of devices attached" result and anything that tries to access the device via ADB hangs or fails. I can still switch the driver to MTP and access the storage just fine.
My wife's PC is a Win7 box and has never had android drivers or ADB installed, I used the 15 Second ADB installer on her PC and the tablet works for ADB and storage access with USB debugging turned on, so there's something I'm missing that needs to be wiped out or reset on my box.
I tried to install Xposed through Magisk on my device and then it got stuck in a boot loop. I was going to use magisk module uninstaller with twrp but with the usb connected to my computer it only comes up as a cd drive. I tried putting it into download mode but adb wouldn't recognise it.
Edit: Hisuite asked me to install usb driver and it then it worked or it might of been me turning on mtp
Download Mode aka fastboot mode need fastboot.exe, no adb. Fastboot devices and see your phone id.
I upgraded couple of days ago to new PC - Ryzen 5 2600/rog strix b450-f gaming with clean windows 10/64 and now i have problems with adb bootloaader driver and cmd commands. Before i was on intel xeon/gigabyte motherboard socket 775 windows 7/64
I use tool all in one, install usb drivers. When phone is turn on, with usb debuging, i can enter phone storage, device manager see phone as poco,everything is ok. When i start tool all in one i can see device id,i can go into fastboot mode(phone restart and go into fastboot). When phone goes into fastboot,device manager see it as Kedacom usb device/android bootloader interface, or sometimes as android phone/android composite usb device. I have adb/fastboot files all i need on pc. When i enter some command trough cmd,for example fastboot devices,or fastboot reboot bootloader, on phone screen goes to dark and in left top corner with small font is written phone will turn off. On cmd i see afther command i set and pres enter only ??????? questionmarks. So i must again manually enter fastboot mode.
I cant get fastboot/adb to work. I try to install other adb/fastboot drivers(xiaomi and google original from tool all in one),try to connect phone cable to other usb port(2.0/3.0/3.1) at the back of pc chase,also 2.0 in front case. I try other usb cable also. Try to manually update google drivers from this forum,then i cant bcouse some ini file is missing or if i set have disc and do manualy with some other driver it cant see phone in adb-fastboot mode. I try all that fall on my mind with no luck.
At the and i goes to my friend and try to install tool all in one,install google usb drivers from that tool,install adb/fastboot files. Try to enter fastboot and do same commands as before with cmd,and everything is working fine as it was with my old pc setup. Device manager see it as Kedacom usb device/android bootloader. He also have amd cpu/chipset - but it is not ryzen with fresh w10/64
Is there any fix for my case? Does anybody have same problem?
So I'm trying to flash TWRP and it's been stuck on "<waiting for device>" for three hours. I also have the latest USB drivers from Samsung. My model is SM-G530P
Most obvious reason is a poor connection between PC and Android device: the device doesn't get detected.
Install latest ADB / Fastboot drivers
Re-boot Windows PC
Enable USB-Debugging in Android's settings -> Developer options
Re-boot Android device
I did all of that
Look inside here maybe it helps.
It seems that my computer isn't detecting my phone in download mode is there any drivers I can install
jogeiscool said:
It seems that my computer isn't detecting my phone in download mode is there any drivers I can install
Click to expand...
Click to collapse
Google search for;
"USB drivers for Samsung phones"
That should find a driver install .exe named "USB drivers for Samsung phones". Install those drivers.
If it still doesn't work, try a different computer, install the drivers and Odin on that PC then see if the device will connect.
Sent from my SM-S767VL using Tapatalk
My RealmeGt2Pro can use the data cable for ADB interaction when the phone is turned on. But after entering the Fastboot mode according to the official instructions, it cannot be operated through the data cable, because the device manager of the computer does not pop up any information about this phone.My system version is RMX3300_11_C.05 & Android 13.
XDA_194 said:
My RealmeGt2Pro can use the data cable for ADB interaction when the phone is turned on. But after entering the Fastboot mode according to the official instructions, it cannot be operated through the data cable, because the device manager of the computer does not pop up any information about this phone.My system version is RMX3300_11_C.05 & Android 13.
Click to expand...
Click to collapse
The device will not be detected in fastboot mode without fastboot drivers installed
Install the proper drivers and try again
Thank you, it's not a problem with the drive. After I changed to an original cable, I can identify the device normally in Fastboot mode.
NumberOneDz said:
The device will not be detected in fastboot mode without fastboot drivers installed
Install the proper drivers and try again
Click to expand...
Click to collapse
Thank you, it's not a problem with the drive. After I changed to an original cable, I can identify the device normally in Fastboot mode.