Related
Ever since I rooted I can not get my Epic to connect to a computer period. I'm about to give up and just deal with what I got, hopefully someone can tell me what I'm doing wrong. Before anyone decides to be a smart ass I have used the search function literally for days and have tried tons of things recommended with no result. I am the first to admit I'm an idiot when it comes to anything involving computers but I'm pretty determained to learn.
This has to be the phone because I have tried to connect to 2 desktops (1 running Windows 00 and 1 running the most updated Ubuntu), and 3 laptops (Windows xp, Windows Vista and Ubuntu). When I rooted I used the Vista computer and connected fine (can't anymore). I didn't have the space on the C drive to install the Android SDK so I switched to Ubuntu (first time user btw lol). Somehow when I was backing my SD card I lost any access to it or the notification bar. I never got my SD back til I rebooted but I haven't been able to connect to any PC since. When I charge (even in the car) it always tries to stay in mass storage mode. I basically charge in my car with my phone off hoping it will just charge and not mount my sd card to my car or wall lol. Yes I wiped 3 times, partitioned sd, tried several different cables (but my husband used mine and no problems on his Motorola) I'm sure I've done something wrong when I rooted or mounted to Ubuntu.
I also can't use adb. I followed the directions to the t (a few times lol) but when I run any commands it says "no such file or directory" I didn't have adb on the windows pc when I di noobnl's one click so I never ran the (adb shell ect) commands. I now can't do jack. I am now running noobnl's DI18 ROM with modem.bin flashed thru Clockworkmod.
I have tried all the basics you will find wit 2 days of web search.
My goal is DK28 (dream on Erica lol)...Thanks for any help and for anyone sparing me a lashing ;-)
Sent from my SPH-D700 using Tapatalk
When you plug in on your windows pcs...in Device manager..do you see anything appear? also do you have USB debugging on the phone?
USB debugging on?
Have you tried reinstalling the drivers for the Epic?
Rebooted phone and PC? (Sometimes it helps)
Used Odin?
Something might have been screwed up during one of your downloads, bad file maybe. Try reinstalling your drivers first, use Odin (phone must be in download mode), and see if it recognizes te device. If it does then Odin the stock .tar file and go from there. It'll give you a fresh start.
That's all I can think of right now.
Sent from my SPH-D700 using XDA App
I bet your USB debugging is on since most root's requier it. Even tho it says connect to pc if usb debugging is on it wont connect to my windows 7 box
I would suggest, if you're really having this many issues, just boot into download mode (1 on the keyboard + power button) and odin back to di18.
Just for kicks have you tried Settings > Privacy > Factory data reset? I assume that wiping does the same thing if not more but it's worth it to see if it somehow resets a setting that might be the issue.
What's left - software issue or Hardware issue.
Software:
hmmm...yeah gotta try connecting through Odin which uses downloader mode instead of USB modes...
Can Odin see your phone? Run Odin as admin with antivirus off, and proper samsung drivers installed. Then boot phone holding down 1 key into downloader mode. Connect to computer through USB port on back of computer (i.e. directly to motherboard) - does Odin identify something attached to USB port?
Yes - flash the dk28!
No - with Odin still on, unplug the USB cable, pause, and reconnect it. Still No? Try a different USB port on computer. Also try uninstalling and reinstalling the drivers - be sure to reboot the PC. If still No, then try on another computer, and as you did before, try different cables. Still No?? --> hardware problem with phone.
Hardware problem with phone: Look at the usb port in the phone - is there any junk in there that might interefere with the connection?
Yes - clean it out
No: phone perhaps internally damaged:
Solution for hardware damage:
You and husband clean up and go to sprint store.
At store - tech will know phone is rooted, so:
--Tech more likely to like you? You handle it, maybe even blame husband. Husband can silently attend and look sheepish, playing the part of 'me man, me dominate environment, me break fancy tech of wife, me sorry." Try to get free replacement phone while simultaneously promising never to let your husband root the phone again, or even touch it.
--Tech more likely to like husband? He goes alone, cops to the true story of how you rooted it and then was backing stuff up when it suddenly stopped working [truth from men? so sincere!]. Try to get free replacement phone while simultaneously promising not to let you in the house should you even attempt to root again.
P.S. forgot to add you might turn off the PCs firewall while testing, as well.
quik99 said:
I bet your USB debugging is on since most root's requier it. Even tho it says connect to pc if usb debugging is on it wont connect to my windows 7 box
Click to expand...
Click to collapse
same here. I tried out the free tethering app the other day and with usb debugging on i coudl never get it to install the proper drivers. Without it on and the 64bit drivers installed Odin worked just fine.
I have seen many Galaxy S devices not connect to a computer because of a faulty USB cable. Had my girlfriends sister switch out 3 Vibrants only to accidentally try and connect it to a laptop with a different USB cable and I've seen two others not connect with the stock Samsung USB cable.
How I fixed the tethering issue
I've had the same problem with my galaxy s - connecting to the PC (Win7 32bit) just doesn't do anything. As a test, I had a friend with the same phone/rom (froyo, rooted) connect - and he was able to! It installed the drivers and it just worked. He disconnected, I connected, and now it's fine.
So, see if you can find someone with the same phone and see if they can connect. Makes no sense to me, but it worked.
I've had my Epic fail to mount before. Interestingly any time I had an issue it was with a Mac - it always mounts on a PC. I'll stop now before I open up a can of worms.
Best advice I have is get a Dropbox account. You can use that guy to move files from a computer to the SD card without having to mount to the computer. Perhaps you can get a factory ROM (with root of course) on your phone that way?
You can get a app from the market called SWIFTP (free) & connect to your sdcard via ftp server. This can be a temporary fix till you get your connection error resolved.
I have 1 USB port on my laptop that the Epic shows up as "unknown device" on. Works on every other port, and everything else works just fine on the same port. The factory USB cable is finicky!
Hello all,
I have a Samsung galaxy S II purchased in Israel from Cellcom.
In my ill advised attempt to unbrand, and thus accelerate, improve memory and battery consumption, I flashed a stock ROM which I believed to be the latest.
The phone works great, with one exception. There seems to be no way to connect it to PC, be it WIN7 32bit or ubuntu 32bit. original usb cable or other cable, my stationary workstation or my laptop, be it USB Storage mode, USB Debugging, that stupid Kies mode, and most importantly because i'd like to flush it back, no Odin Mode. (in win32 - any mode gets "unknown device" status like the device doesn't publish it's name correctly or similar.)
moments before the flash the phone connected in all modes.
I think i've pretty much covered all of the obvious. and there is no problem with my latest sdk and drivers as my Nexus S still connects to both PC's with great success.
SO some info - and what I have already researched.
from http://forum.xda-developers.com/showthread.php?t=1113928, I gather that the PDA on my Cellcome bought SGS2 is either JIKG3 or JIKJ1. and that it's a GT19100T and I gather that denotes some kind of hardware specification.
the ROM I've flushed to my phone has this name:
GT-I9100_XEU_I9100XWKJ3_I9100XEUKH2_I9100XXKI3.tar.md5
everything seems wrong about this ROM in hindsight but, the worst is that it has no T, and probably isn't very hardware compatible. (though the telephony, wifi, camera, sensors and anything I tried works).
The phone is not rooted as after flushing I have lost any USB connectivity. I therefore cannot try and manipulate system files, to try to recover that way.
I have tried to root with the exploit apk. to no effect. I gather it's a statistically challenged way of rooting so I'll try my luck a lot more during the wait for your answer, and report any success.
**Edited**
the "Easy Rooting Toolkit" on http://forum.xda-developers.com/showthread.php?t=1319653
I'll try to run it as best I can, with the shell emulator, instead of on adb, but with debugging enabled.. although it's not a very East Toolkit, when I use it this way..
I'll still report any progress..
**/Edited**
I have seen no one on the internet with this problem. it's really a very stupid problem to have. but a problem nevertheless.
Any insight as to the moves I can try next will be greatly appreciated.
Any information I can add with my limited usb connectivity will be gladly shared. (my "Kies air" works so I can upload to storage that way.. plus i have a shell emulator installed..)
Regards,
Alex.
In ur Device Manager dose it show several unknown devices when connected?
teenvista said:
In ur Device Manager dose it show several unknown devices when connected?
Click to expand...
Click to collapse
just the single one.
There is absolutely nothing wrong with the ROM itself as I have been using it on my phone for a couple weeks now.
The problem exists between your phone and your PC, the PC is stating that it's an unknown device after all.
What I would try is to un-install the device in Device Manager, unplug the device and restart the PC and then plug the phone in again, if that does not work, I would throw in a factory reset of the device itself while repeating the above steps
I think i've pretty much covered all of the obvious. and there is no problem with my latest sdk and drivers as my Nexus S still connects to both PC's with great success.
Click to expand...
Click to collapse
What do you mean by that? The nexus drivers have nothing to do with the galaxy drivers. Only if you run an AOSP rom you will need those drivers. Not if you run a stock rom.
Am I right that your pc sees the phone, but does not recognize it? Did you try reinstalling kies? And then from within kies tried to reinstall the phone drivers?
your PC may not recognize the device after the radio or kernel is changed. what I did was uninstall every single usb device from device manager and reboot, fixed.
Reply to all
jamesyb0i said:
your PC may not recognize the device after the radio or kernel is changed. what I did was uninstall every single usb device from device manager and reboot, fixed.
Click to expand...
Click to collapse
jamesyb0i - I saw that some people have been successful after uninstalling all usb devices, I'm challenged in this task as my keyboard and mouse are USB. I will try it on my laptop as soon as I'll get access to it, though because of the wide range of computer and OS I've tried I'm pretty sure the effort will be ultimately futile.
Lennyz1988 said:
What do you mean by that? The nexus drivers have nothing to do with the galaxy drivers. Only if you run an AOSP rom you will need those drivers. Not if you run a stock rom.
Am I right that your pc sees the phone, but does not recognize it? Did you try reinstalling kies? And then from within kies tried to reinstall the phone drivers?
Click to expand...
Click to collapse
Lennyz1988 - I see your point about the ADB Driver for the Nexus S, but as for the other advice.
As I said, I extensively tried to run it on multiple PC's multiple OS's.
I did try to uninstall / reinstall kies, and kies drivers.
after that didn't help. I got an SGS2 from a friend, just to try it on my computer.
it worked just fine.
achillies400 said:
There is absolutely nothing wrong with the ROM itself as I have been using it on my phone for a couple weeks now.
The problem exists between your phone and your PC, the PC is stating that it's an unknown device after all.
What I would try is to un-install the device in Device Manager, unplug the device and restart the PC and then plug the phone in again, if that does not work, I would throw in a factory reset of the device itself while repeating the above steps
Click to expand...
Click to collapse
The problem I believe is specifically because of the GTI9100/GTI19100T differences
I'm sure as achillies400 said that there is nothing wrong with the ROM itself. BUT the problem is not with my PC's it is more likely the different hardware, and the hardware driver on the phone itself that makes my phone become an "unknown device".
Regards,
Alex.
You could try this exploit.
http://forum.xda-developers.com/showthread.php?t=1296916
Don't know if it will work for you but it's worth a try.
Extract the .zip to /data/local/ on your phone and run the commands.
alex.feigin said:
Hello all,
I have a Samsung galaxy S II purchased in Israel from Cellcom.
In my ill advised attempt to unbrand, and thus accelerate, improve memory and battery consumption, I flashed a stock ROM which I believed to be the latest.
The phone works great, with one exception. There seems to be no way to connect it to PC, be it WIN7 32bit or ubuntu 32bit. original usb cable or other cable, my stationary workstation or my laptop, be it USB Storage mode, USB Debugging, that stupid Kies mode, and most importantly because i'd like to flush it back, no Odin Mode. (in win32 - any mode gets "unknown device" status like the device doesn't publish it's name correctly or similar.)
moments before the flash the phone connected in all modes.
I think i've pretty much covered all of the obvious. and there is no problem with my latest sdk and drivers as my Nexus S still connects to both PC's with great success.
SO some info - and what I have already researched.
from http://forum.xda-developers.com/showthread.php?t=1113928, I gather that the PDA on my Cellcome bought SGS2 is either JIKG3 or JIKJ1. and that it's a GT19100T and I gather that denotes some kind of hardware specification.
the ROM I've flushed to my phone has this name:
GT-I9100_XEU_I9100XWKJ3_I9100XEUKH2_I9100XXKI3.tar.md5
everything seems wrong about this ROM in hindsight but, the worst is that it has no T, and probably isn't very hardware compatible. (though the telephony, wifi, camera, sensors and anything I tried works).
The phone is not rooted as after flushing I have lost any USB connectivity. I therefore cannot try and manipulate system files, to try to recover that way.
I have tried to root with the exploit apk. to no effect. I gather it's a statistically challenged way of rooting so I'll try my luck a lot more during the wait for your answer, and report any success.
**Edited**
the "Easy Rooting Toolkit" on http://forum.xda-developers.com/showthread.php?t=1319653
I'll try to run it as best I can, with the shell emulator, instead of on adb, but with debugging enabled.. although it's not a very East Toolkit, when I use it this way..
I'll still report any progress..
**/Edited**
I have seen no one on the internet with this problem. it's really a very stupid problem to have. but a problem nevertheless.
Any insight as to the moves I can try next will be greatly appreciated.
Any information I can add with my limited usb connectivity will be gladly shared. (my "Kies air" works so I can upload to storage that way.. plus i have a shell emulator installed..)
Regards,
Alex.
Click to expand...
Click to collapse
!!!!!!!!!!!!!!!
I have the same problem, and I couldn't find anyone else w/ it or with answers either.
almost all the same scenario except I have an SGSII AT&T I777 that started out as UCKJ1 and is now UCKH7
My phone started coming up as unknown device. I can not find any remedy to the solution.
Here's my scenario: http://forum.xda-developers.com/showthread.php?t=1372171
My guess is I might try to uninstall "new" programs that I added to the phone and PC, uninstall kies etc. and drivers, and maybe try and do a restore or refresh or something on my phone and see if I can get to "scratch" and re-start from there.
I installed winamp on phone and reinstalled it on PC for wifi, and it kept mounting/unmounting my SD card from phone to computer each time I plugged it in (I think that messed with my card possibly giving it "unknown")
Or also when I changed my Kernel may have made the phone unknown. Those are the only 2 changes I can assume did this to my phone =/
any update on your phone?
UPD: My kernel was causing all my problems. Restored to an earlier backup and it had older kernel. All problems were relieved.
Hi, background is this..
I have a D802-10C G2 that i rooted the stock 4.2.2 rom a while back using the post chinese method. Easy enough, all worked fine. no complaints. A couple of weeks ago i got offered the OTA 4.4 update, this failed due to the root. I then removed the root using the feature in super su. that seems to have worked as no apps or file managers etc could get root access. However, the OTA still wont work.
Now my problem is my phone will no longer be recognized by any operating system, on multiple computers. I have tried many ADB drivers, Windows 7 wont even detect the device, i've used every PC connect mode, USB debugging. However always the same result, it's as if i'm plugging in a blank usb cable into the computer. Nothing at all.
The only thing that does happen when i connect the phone to a computer is the phone starts to trickle charge. There is nothing detected in Device Manager in Windows 7 I've tried connecting in download mode, nothing. I've tried the LG support tool, PC sync. Nothing.
WiFi does connect to the PC suite fine BTW and other than that the phone is working perfectly. I've also tried connecting multiple usb cables on multiple ports.
I haven't been able to find a single case of the same problem in the week or so i've been looking. Hoping someone can help, i'm thinking i may have soft bricked my phone. I really do not think this is a driver issue.
Any help would be great. cheers
Paul
+1
i have the same problem plz help
cambies said:
Hi, background is this..
I have a D802-10C G2 that i rooted the stock 4.2.2 rom a while back using the post chinese method. Easy enough, all worked fine. no complaints. A couple of weeks ago i got offered the OTA 4.4 update, this failed due to the root. I then removed the root using the feature in super su. that seems to have worked as no apps or file managers etc could get root access. However, the OTA still wont work.
Now my problem is my phone will no longer be recognized by any operating system, on multiple computers. I have tried many ADB drivers, Windows 7 wont even detect the device, i've used every PC connect mode, USB debugging. However always the same result, it's as if i'm plugging in a blank usb cable into the computer. Nothing at all.
The only thing that does happen when i connect the phone to a computer is the phone starts to trickle charge. There is nothing detected in Device Manager in Windows 7 I've tried connecting in download mode, nothing. I've tried the LG support tool, PC sync. Nothing.
WiFi does connect to the PC suite fine BTW and other than that the phone is working perfectly. I've also tried connecting multiple usb cables on multiple ports.
I haven't been able to find a single case of the same problem in the week or so i've been looking. Hoping someone can help, i'm thinking i may have soft bricked my phone. I really do not think this is a driver issue.
Any help would be great. cheers
Paul
Click to expand...
Click to collapse
YOu can try checking the device manager or use other USB port on your phone.
buenarc said:
YOu can try checking the device manager or use other USB port on your phone.
Click to expand...
Click to collapse
The problem is not like the usual ones you will see about "computer not being able to see device" I don't think it's a driver or software issue, or if it is it's unlike any i have found in the weeks i've been searching the net for a solution. Here's why....
When i connect the phone to Windows 7 and 8 ( on 3 different computers) No hardware is detected, nothing in the Device Manager, no yellow question marks indicating 'Unknown Hardware'. Nothing, all it does is start trickle charging.
Now even with no ADB, or any driver at all installed, the computer should still detect the phone. Mine does not.
The same thing happens using OSX and Linux Mint 16 (again multiple computers) No devices or mounted or volumes shown at all. Linux terminal command "$ lsusb" does not list my hardware.
This is why i'm pretty much convinced that there is something wrong with the USB port on the phone. Because, if Linux can't see it then surely it's a hardware problem right?
The only other thing i can think of is, i have messed up the phones firmware while trying to unroot it? but only because the timing of all this is just too uncanny.
I think i'll have to suck it up and admit defeat here. Funny thing is the phone works perfectly and charges fine.
Stuck on 4.2 , with no ADB functionality. Perhaps i'll sell it cheap to someone who doesn't care.
Cheers for the reply mate.
Same problem here!
Only my G2 is not rooted, it is still on factory OS and recently updated to 4.4.2.
I have tried on several computers, different ports and no help.
On the first connection to a PC not connected before windows reports "USB device not recognized" problem.
After that every time I connect the phone to the same computer the phone itself only recognizes that it is using USB charging mode, it does not recognize the computer connection (known by the USB ison on android system tray) even with "Ask upon connection option checked".
Even when I manualy change the Android mode in Settings --> PC Connection from MTP to PTP or even LG software, nothing happens.
Definetly there seems to be a problem with the phone, but I don't beleive it's a software but a firmware problem.
Please help if anyone knows what to do.
same thing happened after installing T-mobile rom thrugh twrp. but my device boots into fastboot and i tryed falshing :
laf.img, boot.img, aboot.img, recovery.img, laf.img
but after reboot my LS980 dissapear from device manager and stucked on LG logo.
Dont know what to do now.
I'm no expert, but given there are a lot of them here and none have weighed in on this with any ideas for a fix, i'm going to assume it's a hardware problem.
Anyone else agree? Hardware problem not software?
Cheers
I guess that you already wiped everything right? Apart from that, i'll suggest you to go to some tech supp and ask them if they can verify that each pin of the micro usb is properly working.
Sorry for my english, hope it helps!
Sent from my LG-D802 using XDA Free mobile app
I will try to check the connector although i dont think that it is a hardware issue.
BTW I can enter the download mode after flashing the mentioned partitions and i can also enter the stock LG recovery but when i do the factory reset it keeps showing Factory reset processing ... for ever
It has happened to me the same thing :crying:, and is a problem with the boot.img, if by chance your G2 version 4.4.2 and the the 4.2.2 boot.img, goodbye.
The only solution is to take it to repair a service official, there will change you the card, with the consequent change of IMEI.quent change of IMEI.
Homero2 said:
It has happened to me the same thing :crying:, and is a problem with the boot.img, if by chance your G2 version 4.4.2 and the the 4.2.2 boot.img, goodbye.
The only solution is to take it to repair a service official, there will change you the card, with the consequent change of IMEI.quent change of IMEI.
Click to expand...
Click to collapse
where are you going to repair your G2?
and how much have you paid the repair?
THANKS
Any fix for this guys i have same problem!
Here I'm getting the yellow !, any suggestion?
Sirs, I flashed the baseband (https://www.androidfilehost.com/?w=files&flid=12880) then it got working back.
solved for me
I have some kinds of that problem, let try:
Settings -> General -> PC Connection -> Select USB connection method -> Media device (MTP) (or whatever)
Got this same issue after flashing cloudy g3 rom. Then later flashing dirty unicorns, which requires jelly bean baseband. But even restoring g3 and 24a baseband, still doesn't work. No pc tethering and no on the go usb. My usb port is basically charge only.
---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------
Everything else works fine...I actually never even noticed this bc I never tether to pc. But now I have to bc I want flask kdz
Help me please
someone have a solution to this problem?
My Lg G2 D803 still on boot loop (LG logo) and thats all ... no usb connection , reset factory doesnt work ...
HELP PLEASE ...
Thank you
Anyone has an idea how to fix this problem?
same problem
I have a LG G2 . recently updated from vs98027a to vs98039a 5.0 lollipop. Since the update my computer won't recognize my device in download mode and I don't have superuser ppermissions. Help plz
I also have the same problem.
It happened when I tried to backup info through LG PC Suite: the phone disconnected during the process, and now it's not recognized by any PC (http://forum.xda-developers.com/lg-g2/help/lg-g2-recognized-windows-backup-t3155323).
Also found a description of the same problem here: https://www.reddit.com/r/lgg2/comments/2urpnw/lg_g2_usb_only_charging_not_recognized_by_pc/ - no solutions, too.
Did anyone manage to fix this?
Ok so long story short, i have a nexus 7 2012 which a rooted and installed cyanogen mod.
I was using it as a car install and works perfect, i'm using an otg cable to mount usb sticks, triggering soft shutdown and powering the nexus etc. So usb seems to be working fine.
Basically i removed the tablet it to modify the bootloader to turn on automatically with ac power applied, if the battery runs out i have to manually power on with button, but now i'm running into a problem.
Ever since taking the tablet out and trying to connect over usb, none of my computers detect the tablet.
I've tried different operating systems, drivers, cables etc etc.
Also changed from mtp to ptp in storage and also turned on usb debugging mode. If i connect an otg cable the nexus see's the otg and i can mount usb's etc.
So i thought i might try recover the nexus back to factory, maybe there was an issue with the rom corrupted etc, I've downloaded the original 4.2.2 firmware which is currently installed.
Booted into recovery and tried re-installing the 4.2.2 zip, it keeps aborting. A guy in work tried to use sideloader and connect via adb. no luck.
I'm not very familiar with the android platform so i've no other ideas what to do and other idea's how to recover now.
The guy i work with mentioned using a usb jig, would that be the way to go or can anyone else suggest some else that might help.
Thanks
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Does adb see the device
jadesse said:
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Click to expand...
Click to collapse
I last connected the nexus to the laptop a few monts back to load some music onto it, didn't have a problem. It's only been connected to a computer maybe 3 times. once to root/rom it then another few times to load music etc.
I can't see why the usb board maybe faulty as i can read data from a usb key when the otg cable is connected.
It's a strange one. You could be right, i might try pick up a broken nexus and swap some parts. Usb board etc.
crusrod said:
Does adb see the device
Click to expand...
Click to collapse
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
foster182 said:
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
Click to expand...
Click to collapse
I am having this same problem on my (unrooted) HTC One after attempting to "convert" it from an AT&T to a Google Play Edition device with the procedure described here.
As part of the procedure, I attempted to flash the stock Google Play Edition ROM using fastboot commands, but I got an error message. The instructions say to just try the flash again, but the phone no longer connects properly via USB (error 10) while in bootloader mode. While in bootloader mode, the phone indicates there is some sort of problem (a line showing the OS version is highlighted in red), and attempting to enter recovery mode does nothing but display a phone with a big red X in it. The phone seems to operate fine and responds to ADB commands when the phone is fully booted, albeit with the old OS (not Google Play Edition) still in place.
Any Android device could theoretically get in this state. We're sort of "paralyzed", because everything we want to do to regain control of the bootloader and fix the situation seems to require issuing fastboot commands from a computer connected to the phone while it's in bootloader mode. Yet entering recovery mode or getting a computer to connect to it via USB no longer seems possible.
I wonder if there's another way to issue fastboot commands without relying on the USB connection to a computer?
I've got 5 S7s on my desk, all Canadian variant, all from the same manufacturer all the same model. - SM-G930W8
All are recognised by my PC but one and I can't work out why not!
Plugging the phone into the PC makes no noise from the PC but the phone seems to detect a regular charger not a PC.
I have plugged it in using different cables including the one in its box and the ones used on other devices that were recognised and only this phone doesn't work with any of them.
I have plugged in, unplugged and rebooted many times.
I have set the USB configuration to MTP (Media Transfer Protocol)/Transferring files.
USB Debugging is ON and OEM unlocking is ON.
I have tried booting into stock recovery and wiping cache AND factory resetting.
When phone is turned on "adb devices" returns nothing.
I have installed Samsung Kies and Samsung Smart Switch to reinstall the drivers.
NOTHING IS WORKING!
All threads I find tell me to do the things I have listed above and have people saying these have worked but all of them I had already tried and double tried and nothing is working.
The cables are correct and working with other S7s of the same model.
All the correct drivers are installed and have been uninstalled and reinstalled.
All the correct setting are selected and OEM unlock and USB debugging enabled.
Phone was fresh out the box as were the other four and all cables.
Samsungs apps installed on PC to ensure best drivers installed.
Would really appreciate some guidance or consolation that its not something stupid I'm doing! I work with these phones everyday and this has never happened! Just banging my head against a brick wall trying to resolve it
maybe faulty usb port, my nephew had S6 with the same issue, service replaced usb port and it started
to work with PC.
try download mode and see if odin see your phone.
try to move the cable a lil bit and see if sth appears for a second.
yaro666 said:
maybe faulty usb port, my nephew had S6 with the same issue, service replaced usb port and it started
to work with PC.
try download mode and see if odin see your phone.
try to move the cable a lil bit and see if sth appears for a second.
Click to expand...
Click to collapse
Thanks but unfortunately Odin doesn't recognise in download mode.
Could it be a USB port problem if I used the same port for the other 4 devices and have no issue?
I'm considering sending the phone back to manufacturer to be honest I think it may just be a faulty device or something!
I bet its microusb port fault
Had a similar issue on Windows 10 , if that's what your running let the phone be connected, uninstall the driver from device manager, and then install driver select have disk and select the basic mtp , if this doesn't help connect to Microsoft support and they'll guide you through it , worked for me , my phone used to detect on other laptops but mine , also I could connect other phones on mine but not my phone, hope this helps
same issue here