Related
Just ran into a problem which took me some time to solve. Thought I would share it to save other people some frustration.
After an adb reboot the i5800 got stuck in "modem" mode. i.e. android booted fine but gave a modem and a serial port over usb rather than adb. Reboots did not solve the problem.
The solution is to enter recovery screen:
reboot recovery
OR
press proper buttons to get into recovery mode
And then perform a reboot from there
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
miki.antena said:
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
Click to expand...
Click to collapse
Thanks so much for this!!!! After helping hack a friends build.prop to enable Apparatus compatibility in the Market, I found USB wasn't working properly anymore. Resetting changes in the phone didn't help (I had to do this via the phone terminal) although I at least managed to buy Apparatus before the sale ended.
After initially getting confused due to a lack of drivers and the occasional 'nH' showing up devices without drivers which made me think something was borked, I worked out from the VID & PID it was just the lack of drivers making (well I'm not sure why it did the 'nH' sometimes it got serial something instead), once I installed the drivers all was fine.
Except still mass storage wasn't showing and the Samsung connect manager didn't show up on my phone when I connected USB, nor did ADB work at all. In fact, it didn't even show up in the phone menu as debugging mode if I didn't start phone with it connected (or something like that). Funnily enough when I did get it the debugging to show up I did get the USB mass storage to show up in the phone, but it didn't help (it just unmounted the card which I think is all it ever does).
Anyway after a bit more fooling around I eventuall came across http://forum.xda-developers.com/showthread.php?t=1215103 and the stuff about modem and mkasick's post which sounded a lot like it could be my problem. The code for that Samsung phone didn't work so I searched for the 5800 and came across this giving me the right code. Sure enough UART (but not USB) was set to modem instead of PDA. I was unsure whether that was wrong but changed it anyway and yep that fixed it!
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times. In fact most of the stuff except install a superuser update has been more or less repeated. I guess it was just some strange rare occurence that it somehow got changed. I did have to reconnect the USB while working the first time, not sure why but ADB lost connection then I found couldn't connect. Perhaps that's somehow related. Now that I know what to do, it's trivial but very annoying when I didn't. I still don't get why Samsung decided to make the connect manager (my phone doesn't have that) only to have some hidden option where it can be set to modem or USB.
Partially because of this, I never got to get Tilestorm HD become compatible in time for the sale although my friend wasn't so interested in that. (Eventually I worked out using the THC Tattoo modded market which reports a fake resolution enables it. Well, I also modified the build.prop but I don't know if that was necessary. I wasn't able to do it solely by the build.prop. But it was way too late by then to buy Tilestorm HD cheap.)
Nil Einne said:
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times.
Click to expand...
Click to collapse
This may sound like crazy idea, but is your USB port/connector clean?
(The USB port allows for dozens of different phone functions when using very specific resistance between data pins.)
i bought a LG D802 32gb last night as i was using a 16 gb before i wanted to flash cloudy g3.. so i tried to install custome recovery twrp...
now i am in fast boot mode..
it says :
[880]fastboot mode started
[910]udc_start()
when i attach usb cable
[1100]-reset-
[1110]-portchange-
[1120]-reset-
[1130]-portchange-
[1140]-fastboot: processing commands
i tried holding volume + and and attaching the usb cable but no luck ... so now i have NO RECOVERY, NO DOWNLOAD MODE, AND MY WINDOWS PICKING UP MY PHONE AS "USB MODEM PHONE ADB PORT"
please help
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.
I'm not sure when this problem first appeared. For whatever reason, my phone doesn't show up at all when connected to either of my two PCs. It must have when I first rooted the phone (to load ChainSU) but I'm not sure if the problem is recent or occurred immediately thereafter.
USB debugging is disabled. When I plug my phone into a computer, it attempts to install the MTP Driver and fails. When I uninstall my device, it disappears and I'm unable to manually install the driver's I've downloaded from other threads. When I load into the Bootloader, my device is recognized by Fastboot.
I'm hesitant to factory reset as this will leave me unable to root if the problem persists, which is important to me as I can get rid of the yellow tint on this screen.
Any thoughts?
Edit: $10 via Paypal for anyone who successfully helps me to a solution!
Are you definitely sure usb debugging is disabled? The phone should install as a portable device on your pc. Also ensure to enter your password onto your phone when connected otherwise the phone will not show up its contents.
Make sure for windows media player to be updated to the latest, for the windows mtp driver.
duraeas said:
I'm not sure when this problem first appeared. For whatever reason, my phone doesn't show up at all when connected to either of my two PCs. It must have when I first rooted the phone (to load ChainSU) but I'm not sure if the problem is recent or occurred immediately thereafter.
USB debugging is disabled. When I plug my phone into a computer, it attempts to install the MTP Driver and fails. When I uninstall my device, it disappears and I'm unable to manually install the driver's I've downloaded from other threads. When I load into the Bootloader, my device is recognized by Fastboot.
I'm hesitant to factory reset as this will leave me unable to root if the problem persists, which is important to me as I can get rid of the yellow tint on this screen.
Any thoughts?
Edit: $10 via Paypal for anyone who successfully helps me to a solution!
Click to expand...
Click to collapse
There are a few things you can try. Have you tried uninstalling the drivers completely then reinstalling from the toolkit? In the past, I've had issues where the phone wouldn't be accessible in some way on one computer but would be fine on another, so maybe try a different computer to try to narrow down the problem as to whether it's an issue with the phone or the computer? Also, this may sound a bit ridiculous, but simply switching USB cables and / or ports has fixed detection issues for me in the past as well--something to consider.
Sent via Morse code from my Nexus 4
Remove any existing drivers (while phone is connected), do the same for other android devices if you have any, then reboot and install Universal Naked Drivers. Have always had success with this driver pack.
Rizy7 said:
Are you definitely sure usb debugging is disabled? The phone should install as a portable device on your pc. Also ensure to enter your password onto your phone when connected otherwise the phone will not show up its contents.
Click to expand...
Click to collapse
100% sure on both counts.
I have this same issue with my rooted nexus 4, I've tried 3 different computers and several cables and it never connects to the PC and only charges the phone. It doesn't even give me option to choose media files.
I've had this issue before, my Nexus/Computer was acting in complete stupidity. When connecting the phone to your computer you will see a notification saying "Connected as a media device" on your phone, just touch it, and change it to "Camera (PTP)". It might access the camera for you, but It actually accessed the storage for me.
YeledKaki said:
I've had this issue before, my Nexus/Computer was acting in complete stupidity. When connecting the phone to your computer you will see a notification saying "Connected as a media device" on your phone, just touch it, and change it to "Camera (PTP)". It might access the camera for you, but It actually accessed the storage for me.
Click to expand...
Click to collapse
Thats not the problem, it doesn't give any option. It doesn't show up on the computer at all and only charges. It's the same for every computer.
yuriorkis said:
I have this same issue with my rooted nexus 4, I've tried 3 different computers and several cables and it never connects to the PC and only charges the phone. It doesn't even give me option to choose media files.
Click to expand...
Click to collapse
I'm thinking we've screwed something up with the phone's side of the MTP protocol - mine is totally independent of the cord/computer used. All the correct drivers installed.
Have you tried Factory Resetting? I'm really hoping this is a workable option.
If you have a recovery back up the current Rom and flash stock and see if it's working
Sent from my KFTT using xda premium
if the phone is locked with a pin/password/pattern unlock it.
I had same problem on my pc yesterday. Even if the drivers installer showed up that installation was successful, somehow for a mtp mode system was using some other Microsoft driver. Correct one was only used in ptp mode. So when I connected n4 in mtp mode storage wasn't available, when I switched to ptp mode everything was fine. Turn on your usb debug, switch on mtp and connect. Go to device manager in system, find your nexus there and rmb on it and manually reinstall driver. After this my n4 is visible in system in mtp mode again.
Sent from my Nexus 7 using Tapatalk HD
my screen is cracked and phone is useless now (replacement coming tomorrow) can i connect it and wipe it back to factory before i have to send it out?
K0v4L said:
I had same problem on my pc yesterday. Even if the drivers installer showed up that installation was successful, somehow for a mtp mode system was using some other Microsoft driver. Correct one was only used in ptp mode. So when I connected n4 in mtp mode storage wasn't available, when I switched to ptp mode everything was fine. Turn on your usb debug, switch on mtp and connect. Go to device manager in system, find your nexus there and rmb on it and manually reinstall driver. After this my n4 is visible in system in mtp mode again.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
The problem is that even if I switch between MTP and PTP it still does nothing, I have tried multiple cables, computers and have reflashed the ROM and wiped the device but it still does not connect with the PC. This is frustrating.
yuriorkis said:
The problem is that even if I switch between MTP and PTP it still does nothing, I have tried multiple cables, computers and have reflashed the ROM and wiped the device but it still does not connect with the PC. This is frustrating.
Click to expand...
Click to collapse
Is yours able to connect during Bootloader/Recovery? Fastboot/ADB have no trouble recognizing my device.
It's really odd that if these things work, meaning your USB connection is fine, replacing the all of software fixed nothing... unless MTP occurs at a much lower level of the OS (maybe kernel is corrupted?)
I've got a similar problem that others have posted - PCs not detecting my N4. I got it last Friday (2/1) from Google and after the registering process and updating to 4.2.1, I connected it to my Win7 laptop and it showed on the PC as a drive. But since I couldn't copy/paste Office docs to that drive and had to do that through Dropbox, I didn't bother trying to reconnect until Monday, at which time the PC didn't detect it. Neither will one other Win7 nor two XP (both with WMP10) PCs. Have tried multiple cables, all of which work with other Android devices (pre 3.0). I've seen several suggestions on this and other threads, but one major issue I'm having is that some of the fixes require enabling USB Debugging. For the life of me I can't find that option in the N4's Settings. Unlike my other phones, there is no Applications subcategory under Settings on my N4 (4.2.1, Build JOP40D). Can anyone help me find that option? TIA.
Edit - Found answer. Click on Build in About Phone setting 7 times. That activated Developer options. Now to try the fixes which require USB Debugging mode turned on.
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?
I was recently gifted an S7 Edge that won't seem to connect properly to my PC. It had Marshmellow when I got it, and after some tinkering, attempts, to root, and some bootlooping, I ended up flashing Nougat (g935vvru4bqa2 from Sammobile). My PC can't seem to read files from it (before AND after tinkering). Samsung switch asks me to put it in MTP mode even when it already is, and on the rare occasions I've gotten the memory to show in windows explorer, all the files have no name and I get an error message when I try to open them. I've tried reinstalling android drivers several times to no avail. This is concerning for a few reasons but primarily because I have no way of backing up my phone currently. Any help would be appreciated.
Edit: Interesting development. I hadn't tried the phone with another computer for some reason. It is working fine on my laptop.
Sometimes it can be a usb port I have three on my laptop and only one recognizes my phone or sometime certain usb cables don't have the right specs to flow data back and forth I've had that issue as well
Sent from my SM-G935U using Tapatalk