Develop Bugs

Having weird troubles trying to connect the phone by usb

I have installed and reinstalled the samsung windows drivers about four times.
My phone has not yet been activated and I'm not sure I'm going to attach it to service for the foreseeable future instead of possibly using it as an ipod touch with a keyboard.
I have connected the phone to my laptop one time. I feel asleep with the phone searching for drivers (the drivers had already been installed but the status bar message said it was searching anyway) and when I woke up it seemed fully connected. I was able to cwm3 root the phone but bricked it I think by putting an ext4 filesystem on without moving immediately to an ext4 rom.
I've restored it to stock and through wifi updated it over the air to ec05
Ever since then I have never been able to connect using any of the usb ports, trying two different usb cables, the oem and a generic micro-usb cable and using either windows vista or ubuntu on this computer.
Clockworkmod reports that the phone is not connected and I am not able to see the phone as a hard drive when I set it to mass transfer mode.
In download mode, odin is able to communicate with the phone reliably.
I've repeatedly tried all ##8778# settings and I've set debugging mode off and on. Device manager shows that the phone is connected to port COM7.
Is it possible that the activation program is preventing the USB connection? I would think not because the activation status has not changed since the one time it did connect, but I'm at a total loss for any explanation.
My next step is to try another computer but I don't have one handy.
Is it possible to root a phone only through odin, or to put a file onto the sd card that can root without the use of the computer?

garyf said:
I have installed and reinstalled the samsung windows drivers about four times.
My phone has not yet been activated and I'm not sure I'm going to attach it to service for the foreseeable future instead of possibly using it as an ipod touch with a keyboard.
I have connected the phone to my laptop one time. I feel asleep with the phone searching for drivers (the drivers had already been installed but the status bar message said it was searching anyway) and when I woke up it seemed fully connected. I was able to cwm3 root the phone but bricked it I think by putting an ext4 filesystem on without moving immediately to an ext4 rom.
I've restored it to stock and through wifi updated it over the air to ec05
Ever since then I have never been able to connect using any of the usb ports, trying two different usb cables, the oem and a generic micro-usb cable and using either windows vista or ubuntu on this computer.
Clockworkmod reports that the phone is not connected and I am not able to see the phone as a hard drive when I set it to mass transfer mode.
In download mode, odin is able to communicate with the phone reliably.
I've repeatedly tried all ##8778# settings and I've set debugging mode off and on. Device manager shows that the phone is connected to port COM7.
Is it possible that the activation program is preventing the USB connection? I would think not because the activation status has not changed since the one time it did connect, but I'm at a total loss for any explanation.
My next step is to try another computer but I don't have one handy.
Is it possible to root a phone only through odin, or to put a file onto the sd card that can root without the use of the computer?
Click to expand...
Click to collapse
This thread had a pre-rooted EC05 that you can flash through Odin
http://forum.xda-developers.com/showthread.php?t=1021305

budderocks said:
This thread had a pre-rooted EC05 that you can flash through Odin
http://forum.xda-developers.com/showthread.php?t=1021305
Click to expand...
Click to collapse
Thanks. I'm on ec05 now, so I'm OK with that. I'd like to root either with or without resolving the usb connection issue.
Is that possible at all?

garyf said:
Is it possible to root a phone only through odin, or to put a file onto the sd card that can root without the use of the computer?
Click to expand...
Click to collapse
budderocks said:
This thread had a pre-rooted EC05 that you can flash through Odin
http://forum.xda-developers.com/showthread.php?t=1021305
Click to expand...
Click to collapse
garyf said:
Thanks. I'm on ec05 now, so I'm OK with that. I'd like to root either with or without resolving the usb connection issue.
Is that possible at all?
Click to expand...
Click to collapse
While it isn't JUST a root that you are doing, as stated by budderocks, you can flash the pre-rooted EC05 tar file through Odin, although it will require you to reinstall any apps you currently have. This will start you out with either a stock(ish) setup, with root already included (not sure about Clockwork though), or you can use the one modified for the ext4 filesystem with CWM 3.0.0.6 included which will convert it to ext4 the first time you boot into recovery.

garyf said:
I have installed and reinstalled the samsung windows drivers about four times.
My phone has not yet been activated and I'm not sure I'm going to attach it to service for the foreseeable future instead of possibly using it as an ipod touch with a keyboard.
I have connected the phone to my laptop one time. I feel asleep with the phone searching for drivers (the drivers had already been installed but the status bar message said it was searching anyway) and when I woke up it seemed fully connected. I was able to cwm3 root the phone but bricked it I think by putting an ext4 filesystem on without moving immediately to an ext4 rom.
I've restored it to stock and through wifi updated it over the air to ec05
Ever since then I have never been able to connect using any of the usb ports, trying two different usb cables, the oem and a generic micro-usb cable and using either windows vista or ubuntu on this computer.
Clockworkmod reports that the phone is not connected and I am not able to see the phone as a hard drive when I set it to mass transfer mode.
In download mode, odin is able to communicate with the phone reliably.
I've repeatedly tried all ##8778# settings and I've set debugging mode off and on. Device manager shows that the phone is connected to port COM7.
Is it possible that the activation program is preventing the USB connection? I would think not because the activation status has not changed since the one time it did connect, but I'm at a total loss for any explanation.
My next step is to try another computer but I don't have one handy.
Is it possible to root a phone only through odin, or to put a file onto the sd card that can root without the use of the computer?
Click to expand...
Click to collapse
I have been through this myself and came short of beating my head against a wall before reading that it "may" be a cable issue.
Well, after tyring everything else, (because it couldn't be something as simple as changing to a different cable, right??!!) I pulled out an old cable from my Blackberry days and BAM - my laptop searched for and loaded the needed drivers and sees my phone everytime I plug it in now. I have also used a cable from a friends phone (not a Blackberry) and my laptop still sees the phone so I'm not advocating for Blackberry cables specifically.
Bottom line is - the Samsung cable is a piece of crap. It may work for a day or a month, but it will soon (for 98% of Epic owners) become nothing more than a charging cable before long.
Try using a different cable (not a Samsung model ) and see if that works. If so, then ODIN/one-clicks become your best friend(s)!!
Hope this helps!
-J

[Solved] [Q] I9250M not recognized by fastboot or adb.

Hi guys,
I'm using the I9250M for work, and attempted an update through Kies with usb debugging off. The update failed, and now I'm left with a yellow triangle with an exclamation mark.
I've tried holding both volume up/down buttons and power, but cannot get into download mode or any other mode. I've taken out the battery and held the power button down for 30 seconds, then replaced the battery, but still nothing.
It seems that there is no communication between the pc and phone regardless of the drivers being found and installed.
Things I've tried:
Connecting with Kies - Installed drivers through device manager using windows update. Kies is stuck on "Connecting". Only the OMAP4440 driver could not be found so had to install the OMAP4460 driver.
OMAPFlash - this seems to work ok but not sure what to do when it says "Press any key". There is no mode change after flashing (I still have the yellow triangle).
After looking through the stickies and other tutorials I've tried using the Galaxy Nexus toolkit, PDANet, Odin and WugFresh tools, but they all seem to need usb debugging on, which I can't get to.
From past experience (with windows mobile), I've usually been able to unbrick a phone if it is recognized by a windows pc, so even though this is an android phone, I'm hoping that I can do something to get this phone back in working order.
Further info: The two Samsung usb drivers installed on my windows 7 64 bit machine are modem and CDC. I've also tried using a couple of the adb interface drivers in device manager with no luck.
If I can somehow get to the download mode, that would be half the battle won.
Any suggestions.
Cheers!

You need Odin.
Beamed from my Grouper

Thanks for your reply Mach3.2.
As mentioned in my first post, I tried Odin 1.85 and 1.87 already but the phone wasn't recognized. So, I decided to try Odin 1.87 on XP, and hey presto, the phone was recognized.
So that was my problem, I needed to use Odin on Windows XP. Hope this helps someone.
Thanks!!!

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.

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