I have only recently got a tab pro 8.4 wifi only version SM-T320, I have had Samsung phone for 6 years and have not had problems accessing recovery through ADB but this tab is causing me a problem as once in recovery mode the Tab is not recognized by ADB.
When the tab is in normal operating mode ADB works fine but as soon as you boot into recovery no device is shown as connected, can anyone tell me which driver should be installed to access the adb when is in recovery mode.
Or have Samsung blocked adb from working when the tab is booted into recovery.
install to driver ADB when the tablet mode recovery
Alexey71 said:
install to driver ADB when the tablet mode recovery
Click to expand...
Click to collapse
Translated: put the device in recovery mode, plug the usb lead in and your pc should prompt for driver install.
Sent from a stolen phone!
Alexey71 said:
install to driver ADB when the tablet mode recovery
Click to expand...
Click to collapse
shivadow said:
Translated: put the device in recovery mode, plug the usb lead in and your pc should prompt for driver install.
Sent from a stolen phone!
Click to expand...
Click to collapse
Thanks for the reply guys but that isn't the problem the one it automatically installs doesn't see the tab. It works with my S5 and S3 but the tab is not visible as soon as I boot into recovery no device is identified.
Tried to install the driers manually but I don’t get any ADB driver options from the list, it insists the driver is Google Nexus ADB Interface, this is the one that works with the S3 and S5 perfectly well but not with the Tab.
Its frustrating as it will make changing the white theme and testing the changed apk’s a long process, was hoping someone had it working and new which drivers to use as the default SDB one doesn't
Was hoping someone had their TAB working and visible in recovery mode on their computer that could tell me which drivers they were showing as being installed..
ag4751 said:
Thanks for the reply guys but that isn't the problem the one it automatically installs doesn't see the tab. It works with my S5 and S3 but the tab is not visible as soon as I boot into recovery no device is identified.
Tried to install the driers manually but I don’t get any ADB driver options from the list, it insists the driver is Google Nexus ADB Interface, this is the one that works with the S3 and S5 perfectly well but not with the Tab.
Its frustrating as it will make changing the white theme and testing the changed apk’s a long process, was hoping someone had it working and new which drivers to use as the default SDB one doesn't
Was hoping someone had their TAB working and visible in recovery mode on their computer that could tell me which drivers they were showing as being installed..
Click to expand...
Click to collapse
twrp or cwm?
Alexey71 said:
twrp or cwm?
Click to expand...
Click to collapse
Already have TWRP that works fine, thanks for the though, its the computer that can't see the tab when it is connected in recovery mode, but it can see my S5 with exactly the same diver set up.
Related
Attempting to unlock the bootloader of my brand spankin new LTE G.Nexus. I installed the samsung USB drivers, am running Windows 7 64bit. Made sure USB Debugging was on. When running ICS issuing an 'adb devices' on my windows machine shows the device there, and I can remotely reboot it into the bootloader, however as soon as it goes into the bootloader (via manual reboot or remote) I loose USB connectivity, it shows up as an unknown device in my device mangler and ADB no longer see's it.
I've tried uninstalling/reinstalling the driver, reboots, etc. Can't figure it out. Anyone else having the same issue or have any ideas?
TIA!
picklz said:
Attempting to unlock the bootloader of my brand spankin new LTE G.Nexus. I installed the samsung USB drivers, am running Windows 7 64bit. Made sure USB Debugging was on. When running ICS issuing an 'adb devices' on my windows machine shows the device there, and I can remotely reboot it into the bootloader, however as soon as it goes into the bootloader (via manual reboot or remote) I loose USB connectivity, it shows up as an unknown device in my device mangler and ADB no longer see's it.
I've tried uninstalling/reinstalling the driver, reboots, etc. Can't figure it out. Anyone else having the same issue or have any ideas?
TIA!
Click to expand...
Click to collapse
im having similar issues...im stuck in "waiting for device" in the bootloader.
I'm having the same problem and nothing I've found helps. Since I really want to unlock the bootloader, and doing so wipes the device, I'm stuck not being able to do anything with the phone until I get this worked out
I had this problem when I was unlocking the bootloader. I kept playing around with it and reinstalled the drivers multiple time. I would uninstall the driver and install the driver when the phone was in bootloader mode (I believe).
Make sure the drivers you're setting it to are new.
http://dl.dropbox.com/u/4174784/usb_driver.zip were the drivers I used. These are for GSM model, not sure if they work for the CDMA/LTE version!
Alternatively, you can install PdaNet for drivers.
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Some people also had luck by installing the windows pdanet which installs drivers that should work too.
Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
Thanks buddy!
Worked for me, I thought it was due to my HTC/Motorola device drivers, so uninstalled all of those and re-installed the Samsung...but these steps worked. Thank you again (I did also hit the thanks button too FYI!)!
Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
It worked for me. Thanks!!
i have no idea why but it is just not working :/ in that last set of instuctions above...i dont even have android bootloader interface lol which is weird cause ADB is reading my phone just fine...but when in bootloader mode it just says waiting for device. Does anyone have the fastboot drivers?
Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
That method didn't work for me either. I'm running windows XP professional and do not see 'Android Device' in the list of devices... any other ideas anyone?
Did you download the Google USB drivers as part of the Android SDK? They're at the bottom of the list of things to download when you open SDK, that's what I did.
RMarkwald said:
Did you download the Google USB drivers as part of the Android SDK? They're at the bottom of the list of things to download when you open SDK, that's what I did.
Click to expand...
Click to collapse
I did,
Tried the PDAnet method as well. Adb works fine. Once I get into the boot loader the device isn't recognized. I get the Android 1.0 install prompt and cant install it.
Oozer3993 said:
I finally got it to work. My problem was that I didn't have an updated driver for the device in bootloader mode. This is how I fixed it:
1. With your phone connected and in bootloader mode, go to your computers Device Manager (Control Panel -> Device Manager)
2. You should see an Android 1.0 device. Right click and choose Update Driver.
3. Choose Let Me Choose From This PC (or whatever it's called)
4. Click on Let Me Pick From List.
5. Choose Android Device
6. Choose Android Bootloader Interface
That's what worked for me.
Click to expand...
Click to collapse
Thanks! FWIW, I had to uninstall the Samsung driver and use the Google USB driver to find the Android Bootloader Interface one... if others are having trouble, try that.
I've been trying since last night to root my Nexus, because I want to install Jelly Bean. When I used the Galaxy Nexus Toolkit to install my drivers it did fine for adb. When I go into device manager it shows up as Android Phone like its supposed to. However, when I boot into fastboot mode, my computer no longer recognizes my Nexus and when I got into device manager, nothing shows up for it...not even Android 1.0.
Can someone please give me some tips as how to fix this issue.
P.S. I also installed the Google SDK along with the Google USB drivers afterwards, hoping that would fix the issue...but no luck...and I tried PDAnet...still no luck
The issue I was having was due to the fact that I wasnt pressing Volume Up+Volume Down+Power, so I wasnt even in fastbook, but a screen similar to it
schwartzman93 said:
I've been trying since last night to root my Nexus, because I want to install Jelly Bean. When I used the Galaxy Nexus Toolkit to install my drivers it did fine for adb. When I go into device manager it shows up as Android Phone like its supposed to. However, when I boot into fastboot mode, my computer no longer recognizes my Nexus and when I got into device manager, nothing shows up for it...not even Android 1.0.
Can someone please give me some tips as how to fix this issue.
P.S. I also installed the Google SDK along with the Google USB drivers afterwards, hoping that would fix the issue...but no luck...and I tried PDAnet...still no luck
Click to expand...
Click to collapse
The driver needs to be installed TWICE: once when you are booted normally, and once when booted in fastboot. http://forum.xda-developers.com/showpost.php?p=28060885&postcount=3
efrant said:
The driver needs to be installed TWICE: once when you are booted normally, and once when booted in fastboot. http://forum.xda-developers.com/showpost.php?p=28060885&postcount=3
Click to expand...
Click to collapse
My problem is that when I plug in my phone...while its in fastboot its not recognized as an Android phone or Android 1.0...its recognized as a "SAMSUNG Mobile USB CDC Composite Device"
schwartzman93 said:
My problem is that when I plug in my phone...while its in fastboot its not recognized as an Android phone or Android 1.0...its recognized as a "SAMSUNG Mobile USB CDC Composite Device"
Click to expand...
Click to collapse
That's because you need to uninstall all the old drivers and install the ones I link to...
Sent from my Galaxy Nexus using Tapatalk 2
FastBoot Driver- Xperia Neo
efrant said:
That's because you need to uninstall all the old drivers and install the ones I link to...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi,
I am using sony sricsson neo .587. I tried to connect my phone in fastboot mode. I connected in fastboot mode. I am not able to install drivers for that.
Steps I Followed
1. I updated google usb driver
2. Replaced "android_winusb.inf" file which is provided by Sony official
3. Connected phone in fastboot mode
4. It asked for drivers
5. I selected usb driver folder to install drivers
But It fails...
I am doing these all things on Windows 7 64 bit
Please help...
I've been spending the better part of the day trying to resolve this problem, including poring through a good chunk of the 200+ pages of the 10.1 Nightlies thread over in development. I've been trying to set up ADB over USB with CM 10.1 however it does not register at all except as a USB mass storage device. I've tried uninstalling drivers and reinstalling them both directly from Samsung in the driver package as well as via Keis, having it auto-detect in Download mode, as well as using the modified INF drivers that have been floating around but nothing seems to work. I've tried right-clicking the four unknown Android devices in the Device Manager to install the aforementioned drivers but nothing seems to take. I've also attempted to follow the instructions at .ttp://itekblog.com/cyanogenmod-10-1-with-adb-tutorial to no avail. The most recent ADB from the SDK doesn't pull it up when listing devices either; please see the attached image.
Any help with this would be greatly appreciated.
You can use adb devices in command prompt and it should show your phone or use clockworkmod app and application for computer will work . Also easy tether pro works need the app on phone and computer as well.
Sent from my SGH-T989 using Tapatalk 2
ADB devices in the command prompt displays no devices as connected. From what I've been able to find, it seems to be a driver problem but I'm at a loss as to how to get it installed correctly. I have CM10.1 as well as TWRP installed and working fine, but I've been trying to do some application development recently and this is a major stumbling block, since if I can't get this sorted out I'll probably end up having to go back to using stock.
Edit: I have since been able to fix it. Here are the steps I followed.
1. Right click on the device in the device manager.
2. Click "Update Driver Software".
3. Click "Browse my computer for driver software".
4. Click "Let me pick from a list of drivers on my computer".
5. Select Manufacturer: Google Inc. and Model: Android ADB Interface.
6. You may receive a warning at this point. Ignore it and click yes.
7. It should be working at this point.
Stromgarde said:
ADB devices in the command prompt displays no devices as connected. From what I've been able to find, it seems to be a driver problem but I'm at a loss as to how to get it installed correctly. I have CM10.1 as well as TWRP installed and working fine, but I've been trying to do some application development recently and this is a major stumbling block, since if I can't get this sorted out I'll probably end up having to go back to using stock.
Edit: I have since been able to fix it. Here are the steps I followed.
1. Right click on the device in the device manager.
2. Click "Update Driver Software".
3. Click "Browse my computer for driver software".
4. Click "Let me pick from a list of drivers on my computer".
5. Select Manufacturer: Google Inc. and Model: Android ADB Interface.
6. You may receive a warning at this point. Ignore it and click yes.
7. It should be working at this point.
Click to expand...
Click to collapse
Is this fix also for my Xperia Mini? I'm using PAC Rom which based on CM10.1 as well and I also can't connect to my phone via ADB
My ADB is working whenever the phone is in Fastboot or Recovery but not when it is fully booted.
I can't find the developer "google inc". I guess i'll have to try some of the other steps that you have taken.
EDIT: i followed this guide even though it is for a Samsung phone and I have a HTC One X
hxxp://itekblog.com/cyanogenmod-10-1-with-adb-tutorial/
Hi guys !
I rooted my phone and then tried to setup some roms. But when I try to go in the download mode, it says "Downloading... Do not turn off the target" but on my computer, it cannot recognize the usb. I setup the usb drivers, tried another ports and there is no problem about my usb cable. It works normally, but whenever I go in the download mode, this thing happens and I cant continue to Odin. Does anyone know anything about that ?
burhannde said:
Hi guys !
I rooted my phone and then tried to setup some roms. But when I try to go in the download mode, it says "Downloading... Do not turn off the target" but on my computer, it cannot recognize the usb. I setup the usb drivers, tried another ports and there is no problem about my usb cable. It works normally, but whenever I go in the download mode, this thing happens and I cant continue to Odin. Does anyone know anything about that ?
Click to expand...
Click to collapse
When you install custom ROMs, you need to go to recovery mode ( Volulme Up + Power + Home ), not to download mode
MayB4ck said:
When you install custom ROMs, you need to go to recovery mode ( Volulme Up + Power + Home ), not to download mode
Click to expand...
Click to collapse
I am trying to setup ClockWorkMode Recovery. That's why I go in to download mode
burhannde said:
I am trying to setup ClockWorkMode Recovery. That's why I go in to download mode
Click to expand...
Click to collapse
You can install it easily if your phone is rooted just
-put the downloaded recovery.img in /mnt/sdcard
-download & install "Terminal Emulator" in play store
-open it then type "su" and click enter
-allow root access..
-then type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13" then click enter
-then some text will show in bottom
-exit terminal..
check the recovery by turning off the device then turn on with volume up botton, home button, and power button pressed together..
until "Galaxy W" screen shows up, release the power button only.. then you will enter CWM
MayB4ck said:
You can install it easily if your phone is rooted just
have the same problem + a bootloop...
what should i do?!
the phone is rooted
windows cant detect it when in download mode (wich i need to connect with odin)
now i cant even get the stock rom back on my phone
Click to expand...
Click to collapse
zekare said:
MayB4ck said:
You can install it easily if your phone is rooted just
have the same problem + a bootloop...
what should i do?!
the phone is rooted
windows cant detect it when in download mode (wich i need to connect with odin)
now i cant even get the stock rom back on my phone
Click to expand...
Click to collapse
What version of windows are you running, it couldn't work on windows 8 and 8.1 so i installed 7 and all the drivers for the phone and it works, i dont have the phone now but i do beleive that will, anyway... if you have bootloop that means you are still able to pass the bootloader screen right?? then try to go to recovery and flash roms from there, having an sd card would help transfering roms from pc directly to phone....
Reply again if you need some assistance.. I'm not online very often
Click to expand...
Click to collapse
MayB4ck said:
zekare said:
What version of windows are you running, it couldn't work on windows 8 and 8.1 so i installed 7 and all the drivers for the phone and it works, i dont have the phone now but i do beleive that will, anyway... if you have bootloop that means you are still able to pass the bootloader screen right?? then try to go to recovery and flash roms from there, having an sd card would help transfering roms from pc directly to phone....
Reply again if you need some assistance.. I'm not online very often
Click to expand...
Click to collapse
i have windows 10 pro.
yes, first the samsung logo apears then the galaxy W logo.
it stays 1 or 2 minutes on this galaxy W logo screen then it reboots.
is it even possible to flash it with the original bootloader from a sd card?
and would the original bootloader detect this type of image (.tar.md5) ?
Thank you for reply
Click to expand...
Click to collapse
zekare said:
MayB4ck said:
i have windows 10 pro.
yes, first the samsung logo apears then the galaxy W logo.
it stays 1 or 2 minutes on this galaxy W logo screen then it reboots.
is it even possible to flash it with the original bootloader from a sd card?
and would the original bootloader detect this type of image (.tar.md5) ?
Thank you for reply
Click to expand...
Click to collapse
You can try putting any custom rom and flash from a custom recovery if you can access it, if not download the stock rom and get a windows 7 pc. make sure you install all the samsung drivers ( kies should do the job ) and try flashing it from odin
Click to expand...
Click to collapse
MayB4ck said:
zekare said:
You can try putting any custom rom and flash from a custom recovery if you can access it, if not download the stock rom and get a windows 7 pc. make sure you install all the samsung drivers ( kies should do the job ) and try flashing it from odin
Click to expand...
Click to collapse
so is win10 the problem ?
i tried 100 things to connect pc with the phone in downloadmode. nothing workd.
if i can find a win 7 pc i will try it. but is there any other way?
i also tried adb on windows it also not works.
then i did a ubuntu usb drive and tried to do it with heimdall but im not a coder. it was very confusing.
at least i was able to detect the device but thats it.
well, anyway thanks alot for your help.
i will try it on a win7 pc
Click to expand...
Click to collapse
Download mode Windows 8.1 10
To connect your phone in download mode on Windows 8.1 and 10 you need to apply this registry file (in my attached zip file).
Mirror Link
It happens for most old phones.
More Info: https://blogs.msdn.microsoft.com/us...ows-8-0-but-fail-on-windows-8-1-with-code-43/
Also note Odin3 (the one which is used for newer phones) doesn't work for Galaxy W! (Use Odin Multi Downloader.)
--------
Update: It seems that this registry key isn't needed. Make sure to connect the USB cable after downloading... screen appears. If it wasn't recognized try disconnect and reconnecting the USB cable or try other USB ports on PC till it gets recognized.
mat1371 said:
To connect your phone in download mode on Windows 8.1 and 10 you need to apply this registry file (in my attached zip file).
Mirror Link
It happens for most old phones.
More Info: https://blogs.msdn.microsoft.com/us...ows-8-0-but-fail-on-windows-8-1-with-code-43/
Also note Odin3 (the one which is used for newer phones) doesn't work for Galaxy W! (Use Odin Multi Downloader.)
Click to expand...
Click to collapse
still doesn't work for me, can you please post the drivers you are using ?
If you see the USB device is not recognized error it's not a driver issue.
Windows automatically downloads the drivers through Windows Update. BTW here are the drivers:
SAMSUNG.zip - 13.5 MB
deleted
mat1371 said:
Download mode Windows 8.1 10
To connect your phone in download mode on Windows 8.1 and 10 you need to apply this registry file (in my attached zip file).
Mirror Link
It happens for most old phones.
More Info: https://blogs.msdn.microsoft.com/us...ows-8-0-but-fail-on-windows-8-1-with-code-43/
Also note Odin3 (the one which is used for newer phones) doesn't work for Galaxy W! (Use Odin Multi Downloader.)
--------
Update: It seems that this registry key isn't needed. Make sure to connect the USB cable after downloading... screen appears. If it wasn't recognized try disconnect and reconnecting the USB cable or try other USB ports on PC till it gets recognized.
Click to expand...
Click to collapse
it works. thank u so much...
Hi All,
I flashed TWRP to my sm-t320 with Odin in Windows. `adb devices' (in both Windows & Linux) can recognize my device but it always show unauthorized. Does anybody know how to fix that? but it's ok when I'm in twrp (turn off the tablet, then power+volume up to go to twrp: I didn't know this before, so this is for people like me), adb devices works fine.
dxxvi said:
Hi All,
I flashed TWRP to my sm-t320 with Odin in Windows. `adb devices' (in both Windows & Linux) can recognize my device but it always show unauthorized. Does anybody know how to fix that? but it's ok when I'm in twrp (turn off the tablet, then power+volume up to go to twrp: I didn't know this before, so this is for people like me), adb devices works fine.
Click to expand...
Click to collapse
Make sure you have USB Debugging enabled on your phone if you do turn it off connect your phone to your PC turn USB Debugging on and see if you get a message to allow your PC to connect to your Tab if you do then allow it.
Also check you have the correct drivers installed when connected to your PC
If you are on windows 7 right click my computer then properties and click Device Manager, look for Samsung Android Phones in the list and expand it, this should then say Samsung Android ADB Interface.
If you don’t see Samsung Android Phones your have the incorrect drivers assigned to you TAB, the one windows installs by default is generally the wrong one.
If you see Samsung Android Phones but when expanded it doesn't say Samsung Android ADB Interface then again the wrong driver is installed.
To correct it right click and select properties, then update driver, then click browse computer, then click let me select from a list Select Samsung Android ADB Interface.
When its installed you may get messages about devices not working properly just click OK to it, unplug you Tab then plug it back in again and wait for it to connect.
Open a CMD and type ADB Devices hit return and you device should be recognised,
If you are using TWRP then when you connect to your device in Recovery mode to your PC you need different drivers for that to work properly again the ones installed by windows as default are not the proper ones, it will work with the default ones but not correctly you probably will not be able to Push or Pull files or apk's.