Develop Bugs

Windows 8.1/7 won't detect Galaxy Tab S in download mode

Hi All,
I recently purchased two Galaxy Tab S tablets (10.5, SM-T800) which I have been trying to root for the past couple of days but have been getting nowhere.
The issue stems from the inability of my computers being able to detect the tablets in Download Mode.
I have tried the following:
I have tried installing different versions of Odin
I have download kies.
I have tried re-installing the Samsung usb drivers on numerous ocations in two different computers.
I have tried different usb cables to include the cable that came with the tablet.
If Tablet is powered on however, the computer will detected it and thus so will Odin. This is only happens in Download Mode.
If googled this issue and it seems to be a none issue however I have yet to find a fix to this. I was hoping I would have better luck in this forum.

Have you tryed using a different usb port? How about using a different pc? Does it even connect when you tab s is on? My pc can detect my tab s fine but had some issues with windows 8.1 and odin crashing. My guess would be trying on a pc that can detect other devices in download mode just fine. Did you also enable usb debugging?

I'm stumped given what you have tried. I'm assuming you are using CF-autoroot. On Windows 7, Odin wouldn't see download mode until I installed the Samsung drivers downloaded from Samsung. Then everything went fine (after which I rolled Windows back to the previous restore point because the Sammy drivers messed up my Nexus 5 connection. Also, if it matters, I used Odin 3.0.9 but with Chainfire's Odin.ini file.
Are you waiting to plug the tablet in until after you have entered download mode? I don't know why, but the instructions for CF-autoroot were very explicit about that.

coolguycarlos said:
Hi All,
I recently purchased two Galaxy Tab S tablets (10.5, SM-T800) which I have been trying to root for the past couple of days but have been getting nowhere.
The issue stems from the inability of my computers being able to detect the tablets in Download Mode.
I have tried the following:
I have tried installing different versions of Odin
I have download kies.
I have tried re-installing the Samsung usb drivers on numerous ocations in two different computers.
I have tried different usb cables to include the cable that came with the tablet.
If Tablet is powered on however, the computer will detected it and thus so will Odin. This is only happens in Download Mode.
If googled this issue and it seems to be a none issue however I have yet to find a fix to this. I was hoping I would have better luck in this forum.
Click to expand...
Click to collapse
Dont mean to patronize...but you have enabled usb debugging in developer options and installed the adb driver right? Coz odin wont see anything until you do this.

pdolton2000 said:
Dont mean to patronize...but you have enabled usb debugging in developer options and installed the adb driver right? Coz odin wont see anything until you do this.
Click to expand...
Click to collapse
You dont need adb as it worked fine without adb for me. Usb debugging does the trick. But installing adb could help

Yes I already tried different USB ports. Different USB cables. Different computers. USB Debugging is enabled.
Again Odin does detect the tablet as long as the tablet is booted up to Android. Odin detects is, Windows Detects it, Kies Detects it.
As soon as I reboot the tablet into Download Mode and plug it back into the computer, is as if nothing is plugged in. No driver gets installed. No new hardware is detected and thus Odin wont detect it.

FIXED!!!!!
Ok so what essential was happening is I was turning off the tablet. Putting it into download mode using VolDown+Home+Power. However that seemed to be actually taking me to recovery and now download mode.
I ended up booting back into android with usb debugging mode enabled and running the following adb command
adb reboot download
This rebooted the tablet into download mode which looks totally different than the recovery, it then installed the drivers and Odin was able to finally detect it!
Thank you all for your assistance!

coolguycarlos said:
FIXED!!!!!
Ok so what essential was happening is I was turning off the tablet. Putting it into download mode using VolDown+Home+Power. However that seemed to be actually taking me to recovery and now download mode.
I ended up booting back into android with usb debugging mode enabled and running the following adb command
adb reboot download
This rebooted the tablet into download mode which looks totally different than the recovery, it then installed the drivers and Odin was able to finally detect it!
Thank you all for your assistance!
Click to expand...
Click to collapse
Nice one pal glad it all worked, thought you might not of been in dwnload mode coz thw only reason odin wouldnt detect it is that reason....strange how vol down was taking you into recovery though, usually thats vol up...mad
---------- Post added at 07:35 AM ---------- Previous post was at 07:32 AM ----------
DUHAsianSKILLZ said:
You dont need adb as it worked fine without adb for me. Usb debugging does the trick. But installing adb could help
Click to expand...
Click to collapse
Adb drivers are active regardless when usb debugging is enabled ....some times though you have to install them manually....but as hehad installed samsung software the drivers got installed.

SM-P607T charges but will not connect to any PC - won't even try

I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!

I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.

Hi i have a similar problem as you, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
bigillz said:
I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!
Click to expand...
Click to collapse
---------- Post added at 11:04 AM ---------- Previous post was at 11:02 AM ----------
I am confused what you mean by calculator, I am on Win 10 and have a similar problem, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse

shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse
thank you very much. it worked.

Pixel XL Fastboot Works to Flash Stock ROM+TWRP. Unseen as USB in TWRP or OS

I have 3 of these devices I'd successfully flashed TWRP to months ago. I can plug the other 2 into any of my Win10 PCs and they are functional as MTP devices in TWRP or the OS. Something is wrong with this device in that fastboot works fine, yet it is not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView. I was unsure if this device received an OTA update so I went ahead and flashed the latest stock firmware as of 5/24/2017
It successfully flashed albeit unusually slow (even though Nirsoft USBDevView showed it connected at USB 2.0 and not 1.1). It also successfully flashed the latest Pixel XL Marlin-3.1.0-0RC2
Even if I attempt to toggle MTP in TWRP there is no response in Windows (on any of my PCs) nor is there any response when it's booted to Android 7.1.2. Same when toggled to PTP. Same w/ USB Debugging enabled. The device charges fine. Checking OTA updates shows none available. Factory reset option in bootloader didn't help.
I'm sure I'm missing something like I somehow have the incorrect firmware loaded for something. Anyone know what specifically is responsible for the USB at the firmware level that would allow it to function in fastboot mode yet fail to detect when booted TWRP or OS???

Pay_It_Forward_Pete said:
I have 3 of these devices I'd successfully flashed TWRP to months ago. I can plug the other 2 into any of my Win10 PCs and they are functional as MTP devices in TWRP or the OS. Something is wrong with this device in that fastboot works fine, yet it is not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView. I was unsure if this device received an OTA update so I went ahead and flashed the latest stock firmware as of 5/24/2017
It successfully flashed albeit unusually slow (even though Nirsoft USBDevView showed it connected at USB 2.0 and not 1.1). It also successfully flashed the latest Pixel XL Marlin-3.1.0-0RC2
Even if I attempt to toggle MTP in TWRP there is no response in Windows (on any of my PCs) nor is there any response when it's booted to Android 7.1.2. Same when toggled to PTP. Same w/ USB Debugging enabled. The device charges fine. Checking OTA updates shows none available. Factory reset option in bootloader didn't help.
I'm sure I'm missing something like I somehow have the incorrect firmware loaded for something. Anyone know what specifically is responsible for the USB at the firmware level that would allow it to function in fastboot mode yet fail to detect when booted TWRP or OS???
Click to expand...
Click to collapse
When booted into the OS and plugged into PC, do you have a notification on the pixel that the device is connected and an option to change how to interact with the PC?

TheBobMiller said:
When booted into the OS and plugged into PC, do you have a notification on the pixel that the device is connected and an option to change how to interact with the PC?
Click to expand...
Click to collapse
I can plug it into the PC and charge it up and receive a full charged reached message in the notification bar. Unfortunately I do not receive any other acknowledgement in the notification bar that it's connect to the PC and to toggle from "charge only" to PC MTP connection like most other phones present.
Its not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView.
Yet I can flash it successfully all day long in fastboot mode ... so strange.

Pay_It_Forward_Pete said:
I can plug it into the PC and charge it up and receive a full charged reached message in the notification bar. Unfortunately I do not receive any other acknowledgement in the notification bar that it's connect to the PC and to toggle from "charge only" to PC MTP connection like most other phones present.
Its not recognized as a USB device at all in Windows. No device detected ding. No yellow exclamation point in device manager. Nothing in Nirsoft's USB DevView.
Yet I can flash it successfully all day long in fastboot mode ... so strange.
Click to expand...
Click to collapse
What happens when you change the default USB Configuration in Developer Options to MTP or PTP and the plug in the phone to the computer?

TheBobMiller said:
What happens when you change the default USB Configuration in Developer Options to MTP or PTP and the plug in the phone to the computer?
Click to expand...
Click to collapse
No response on the phone or PC when set to MTP or PTP. Same w/ USB debugging off or enabled.

Pay_It_Forward_Pete said:
No response on the phone or PC when set to MTP or PTP. Same w/ USB debugging off or enabled.
Click to expand...
Click to collapse
I know this may seem like a stupid question, but have you tried using a different cable? If the phone recognizes fastboot mode commands but not PTP or MTP, then perhaps the cable is going bad. I would blame it on your drivers but fastboot mode wouldn't work if the drivers were malfunctioning.

TheBobMiller said:
I know this may seem like a stupid question, but have you tried using a different cable? If the phone recognizes fastboot mode commands but not PTP or MTP, then perhaps the cable is going bad. I would blame it on your drivers but fastboot mode wouldn't work if the drivers were malfunctioning.
Click to expand...
Click to collapse
Same behavior with a different cable. I've also tested on USB 2.0 and USB 3.0 ports. Also different PCs. Up until today I couldn't get Windows to acknowledge anything. Today I observed Windows a couple times present "usb device not recognized. the last usb device you connected to this computer malfunctioned and windows does not recognize it."
However even after it did that once on one PC today and again on another PC today, I couldn't get Windows to present that message any subsequent times. Even when that message did appear as a system tray notification in Windows, Windows still wasn't showing the phone with a yellow exclamation point in device manager like it sometimes can for many other devices it would otherwise present such a message for. (I just speak from past experience with older PCs)

Pay_It_Forward_Pete said:
Same behavior with a different cable. I've also tested on USB 2.0 and USB 3.0 ports. Also different PCs. Up until today I couldn't get Windows to acknowledge anything. Today I observed Windows a couple times present "usb device not recognized. the last usb device you connected to this computer malfunctioned and windows does not recognize it."
However even after it did that once on one PC today and again on another PC today, I couldn't get Windows to present that message any subsequent times. Even when that message did appear as a system tray notification in Windows, Windows still wasn't showing the phone with a yellow exclamation point in device manager like it sometimes can for many other devices it would otherwise present such a message for. (I just speak from past experience with older PCs)
Click to expand...
Click to collapse
Wow...that's puzzling then. You said in your op that you factory reset using bootloader menu but have you tried flashing factory image with fastboot in bootloader? Maybe the firmware that's malfunctioning could be fixed with a factory image flash...

TheBobMiller said:
Wow...that's puzzling then. You said in your op that you factory reset using bootloader menu but have you tried flashing factory image with fastboot in bootloader? Maybe the firmware that's malfunctioning could be fixed with a factory image flash...
Click to expand...
Click to collapse
That's what's killing me. I can successfully factory image flash (same I've flashed on the other handsets). Yet the USB doesn't work in the OS. When this initially happened I thought for sure USB was going to work like usual in TWRP (works on the others) but it doesn't work there either.
The only other thing I can think of out of desperation is flash Pure Nexus ROM or Resurrection remix in the hopes that somehow affects a USB bit setting at the firmware level. (Mind you flashing factory nor TWRP helped).
My exotic theory is that fastboot driver has an ability to work in USB 1 mode and TWRP or OS level driver can only work in USB 2.0/3.0 mode. Even though I don't see any visual defects to the pinout on this handset I'm guessing my pins for charging and for USB 1 mode is fine whereas my pins for USB 2.0/3.0 are electrically damaged or something.

Pay_It_Forward_Pete said:
That's what's killing me. I can successfully factory image flash (same I've flashed on the other handsets). Yet the USB doesn't work in the OS. When this initially happened I thought for sure USB was going to work like usual in TWRP (works on the others) but it doesn't work there either.
The only other thing I can think of out of desperation is flash Pure Nexus ROM or Resurrection remix in the hopes that somehow affects a USB bit setting at the firmware level. (Mind you flashing factory nor TWRP helped).
My exotic theory is that fastboot driver has an ability to work in USB 1 mode and TWRP or OS level driver can only work in USB 2.0/3.0 mode. Even though I don't see any visual defects to the pinout on this handset I'm guessing my pins for charging and for USB 1 mode is fine whereas my pins for USB 2.0/3.0 are electrically damaged or something.
Click to expand...
Click to collapse
Well i guess you could try some ROM flashing and see if that works and if not, try contacting Google and see if they will honor a warranty or something. Good luck to ya!

TheBobMiller said:
Well i guess you could try some ROM flashing and see if that works and if not, try contacting Google and see if they will honor a warranty or something. Good luck to ya!
Click to expand...
Click to collapse
@TheBobMiller I appreciate all your thoughtful suggestions and well wishes. Have an awesome weekend!

Unique USB Data Issue

I have the d2spr with OctOS 7.1.1 installed (from April 2017 I think). This rom has been awesome and I have been able to connect via USB and transfer files in the past but now I cannot. When I plug in USB I always get a charging indication on the phone but no evidence of a data connection either at the phone or the PC. I have the USB mode set to MTP but when I plug in the phone it acts as though I have Charging Only selected. Windows device manager shows no activity. There are no UNKOWN devices listed and the PC shows no sign of hardrive or processor activity when I connect the phone. I have tested with 5 different USB cables and three different PC's. They all behave identically. Additionally I have plugged the phone in while in DOWNLOAD MODE and still the behavior is identical. I have fresh samsung phone drivers installed. One of these PC's have seen this phone before the other two have not. I'm beginning to think my micro usb port on the phone has taken a biff but it has always and still does charged perfectly.
I could try a factory reset but that doesn't seem to jive with getting nothing in DOWNLOAD MODE. I haven't loaded ODIN to see if it sees the phone but even without odin loaded it should still load a bunch of devices in device manager.
EDIT: I have also booted into recovery and it also behaves identically when plugged into the PC - no response but it charges
Any ideas? I have searched the forums but no one I could find has this exact issue of absolutely no response from the PC.
Thanks in advance!

I have had this for quite awhile. USB port is done. It's also a very difficult repair. Now I use flashfire instead of Odin because of this. But flashfire doesn't do bootloader and modems are iffy. So only flashfire a version you are already on (nd8, ndc, etc.)

UPDATE: I was able to adjust the usb cable to just the right position for Odin to see it and was able to flash via Odin. The weird thing is no amount of wiggle gets windows to recognized it. Thanks for your response.

PC cannot see phone

Hi
I would appreciate any input/help on this issue.
I bought the Korean Note 10 + 5g exynos (SM-N976N), specifically for the purposes of being able to root it. I would prefer to use the Magisk approach, because I would like to be able to use Google Pay, amongst others
Try as I might, I cannot get my PC to "see" the android phone. I have engaged developer mode, checked USB debugging, checked the the USB connection as MTP mode, and gone through several cables, going by the advice of "experts" I consulted. I even went as far as returning my original phone and buying a new one, again, on the advice of an "expert" who determined that my original phone was faulty (unlikely, since I had literally taken it out of the box and attempted the rooting before trying to load my multiple software). I am using Windows 10, 64k, with all current Microsoft updates.
I have reloaded the Samsung USB drivers, rebooted both the phone and PC several times, to no avail. When I connect, in download mode, the USB cable between the two devices, I hear the "ping" on the PC, indicating that the two have made contact, but then - nothing. I have established that the cable works fine, by connecting my Note 8 to the PC, where it shows up as a device with two drives (int and SD card)
I have installed Magisk on the 10+, and modified the stock ROM with Magisk, and then copied that over to the PC, as advised by the rooting solution; the problem is that I cannot use Odin to flash that modified ROM because Odin does not recognize any phone attached to it!
Help, Please!!

Could be the Odin version your using

Perhaps, I hadn't thought of that. I am using 3.13.1. Do you have a suggestion about using a more stable/useful one? My only issue with your answer is that it's not just Odin that isn't responding- it's the entire computer - it's as if the phone doesn't exist when connected.

I'm guessing you are using a USB 3.0 port on pc? If you have access to USB 2.0 try that....
Next thing I'd suggest (with note plugged in while in download mode)....go into device manager (right click This PC)
Find device under Modem, open properties Ports tab, Advanced Settings and manually change the port setting to a lower port assignment (preferably between 1 & 5). Reboot pc and just for kicks reset the phone into Download Mode again....Give odin a try now.
Hope one or a combination of these methods help.
Sent from my [device_name] using XDA-Developers Legacy app