Database Users

Fix for adb not working because phone is stuck in "modem" mode

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

No usb connectivity in any mode after flashing stock rom

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.

usb not working

Hey guys I tried to connect my nexus 7 to my Windows 7 laptop but nothing popped up it just showed as charging on my n7 I've tried update the drivers and different cables and different laptops too but it's all the same, even fastboot doesn't show up or mtp in twrp, any ideas how to fix this guys?

Anyone got any idea how to fix this problem?

Hey,
Have you tried enabling USB debugging in Settings > Developer Options?

Fobos531 said:
Hey,
Have you tried enabling USB debugging in Settings > Developer Options?
Click to expand...
Click to collapse
Cheers mate but yep I tried that and nothing changed

I'm in the same boat. Had this problem for a long while, almost had my guarantee expire so I had it fixed. Not sure what caused it, or what fixed it. But couple of weeks later I was transfering some files through the now working USB port and accidently touched the cable - the device lost connection mid-transfer and since then I was unable to use the USB to transfer files, or connect the device to anything but the charger..
Along comes the 5.1 OTA which I decide to install and mid-install there was an error and the device soft-bricked - I can't boot it, it shows the Android robot with a red traingle and exclamation mark and 'No command.' written under it, at which point it reboots after a couple of minutes.
I can access recovery and fastboot mode and excecuted a factory reset but to no avail. Does anyone know how to fix the USB so that I can reflash stock and make my device work again?
Also, any ideas if one could bypass the use of the USB port in fixing the softbrick would also be helpful.

Armeddy said:
I'm in the same boat. Had this problem for a long while, almost had my guarantee expire so I had it fixed. Not sure what caused it, or what fixed it. But couple of weeks later I was transfering some files through the now working USB port and accidently touched the cable - the device lost connection mid-transfer and since then I was unable to use the USB to transfer files, or connect the device to anything but the charger..
Along comes the 5.1 OTA which I decide to install and mid-install there was an error and the device soft-bricked - I can't boot it, it shows the Android robot with a red traingle and exclamation mark and 'No command.' written under it, at which point it reboots after a couple of minutes.
I can access recovery and fastboot mode and excecuted a factory reset but to no avail. Does anyone know how to fix the USB so that I can reflash stock and make my device work again?
Also, any ideas if one could bypass the use of the USB port in fixing the softbrick would also be helpful.
Click to expand...
Click to collapse
Do you twrp installed mate?

No, I do not.

Phone not detected by PC in adb/fastboot mode

Hi, I have strange problem with my OP2. Since some time when I connect my OP2 to PC it's only connected in charging mode. I've tried different methods to solve it: tried different cables, tried different computer, event wiped data & cache but nothing seems to work. It seems that it might have something with OOS 3.1 or eventually there is some hardware issue with my phone. Currently I'm on stock OOS 3.1 without root and on stock recovery. Is there any way to root my phone without possibility to connect it to PC in ADB/Fastboot mode? Or what else can I try to make phone to connect to PC in different mode than charging?

KillyGonzales said:
Hi, I have strange problem with my OP2. Since some time when I connect my OP2 to PC it's only connected in charging mode. I've tried different methods to solve it: tried different cables, tried different computer, event wiped data & cache but nothing seems to work. It seems that it might have something with OOS 3.1 or eventually there is some hardware issue with my phone. Currently I'm on stock OOS 3.1 without root and on stock recovery. Is there any way to root my phone without possibility to connect it to PC in ADB/Fastboot mode? Or what else can I try to make phone to connect to PC in different mode than charging?
Click to expand...
Click to collapse
Try reinstall USB drivers

Reinstalled and still same situation. Phone only connects in charging mode and is not detected at all in device manager.

KillyGonzales said:
Reinstalled and still same situation. Phone only connects in charging mode and is not detected at all in device manager.
Click to expand...
Click to collapse
Connect your device in fastboot mode to your pc and go to device manager in your pc you will see a device listed as Kedacom USB device. Uninstall and delete the driver. Remove your device and connect it again.

EvenOdd said:
Connect your device in fastboot mode to your pc and go to device manager in your pc you will see a device listed as Kedacom USB device. Uninstall and delete the driver. Remove your device and connect it again.
Click to expand...
Click to collapse
Doesn't help. Even in fastboot mode phone is not listed in device manager.

KillyGonzales said:
Doesn't help. Even in fastboot mode phone is not listed in device manager.
Click to expand...
Click to collapse
Phone should be listed as Kedacom USB device.
Also try this http://forum.xda-developers.com/showthread.php?t=2588979
Download the latest version 1.4.3 from here
https://drive.google.com/open?id=0B0MKgCbUM0itNVB1elljU2NPR0k

I've tried this tool before without success. I'm afraid that there might be some hardware issue with my phone

same problem with me...i have recently updated my phone.... os 3.1.0 ...but not working with adb....after opening command prompt ...left process of adb not working

Make sure you check your device in device manager. It should be listed as Kedacom USB device uninstall and delete the driver.

Which version of windows u r using ?

I've tried on windows 10 64 bit & windows 7 64 bit.

I would try Linux

KillyGonzales said:
Hi, I have strange problem with my OP2. Since some time when I connect my OP2 to PC it's only connected in charging mode. I've tried different methods to solve it: tried different cables, tried different computer, event wiped data & cache but nothing seems to work. It seems that it might have something with OOS 3.1 or eventually there is some hardware issue with my phone. Currently I'm on stock OOS 3.1 without root and on stock recovery. Is there any way to root my phone without possibility to connect it to PC in ADB/Fastboot mode? Or what else can I try to make phone to connect to PC in different mode than charging?
Click to expand...
Click to collapse
Hi have you found any solution to this? It happened to my phone too...
Enviado do meu ONE A2003 através de Tapatalk

RCT1 said:
Hi have you found any solution to this? It happened to my phone too...
Enviado do meu ONE A2003 através de Tapatalk
Click to expand...
Click to collapse
No I haven't found anything new. After update to 3.5.5 still same situation. I think this is some kind of hardware malfunction. Have you ever used charging cable other than shipped with phone? I think maybe using other cable damaged something with usb port in phone...

My phone is Xiaomi. My phone recently have been infected by viruses that destroyed some important apps like: Play Store, Google Play Services and etc. I turned it off and then, wiped all data of it. The first configuration is actually broken in the step "Connect in the MI Account", so i tried use fastboot to activate USB Debug and define home as the default and press home button through ADB. But in the first step... My computer not found it.
My Xiaomi is Redmi-2014819. I need a answer most fast possible.

Lg G6 with the same issues. Fast charge went crazy and think this has blown something inside. Only normal charging works.
No ADB, fastboot, download mode. Can't even connect to laptop or Mac to transfer files.
Had charger replaced but it's the phone I think.
Gonna replace charge port but don't think this will fix issue.
Anyone had any luck?

Usb connection options doesn't pop up when connected to PC

I have google this for hours with nothing! I connect my Nexus 6P to my PC and it doesn't recognize it and not only that but the usb connection options doesn't show up on the phone either. I am completely lost!
I have installed the drivers multiple times, i have looked up the mtp inf drivers and nothing happens. When I connect it to the computer it only says chaging on the lockscreen thats it! I have no idea how to fix this. I am trying to go back to stock because i lost root flashing a custom nougat build. everything works except twpt won't boot up anymore and just hangs at the splash screen. and of course I don't have root. can anyone please help me! thanks

117micc said:
I have google this for hours with nothing! I connect my Nexus 6P to my PC and it doesn't recognize it and not only that but the usb connection options doesn't show up on the phone either. I am completely lost!
I have installed the drivers multiple times, i have looked up the mtp inf drivers and nothing happens. When I connect it to the computer it only says chaging on the lockscreen thats it! I have no idea how to fix this. I am trying to go back to stock because i lost root flashing a custom nougat build. everything works except twpt won't boot up anymore and just hangs at the splash screen. and of course I don't have root. can anyone please help me! thanks
Click to expand...
Click to collapse
Have you tried a different cord? If its not the cord the inspect the port on your phone to make sure no lint or crud is physically blocking some pins. Do you have developer options enabled? Maybe something got changed in there. Its never happened to me so these are just guesses. Maybe somebody smarter can help.

117micc said:
I have google this for hours with nothing! I connect my Nexus 6P to my PC and it doesn't recognize it and not only that but the usb connection options doesn't show up on the phone either. I am completely lost!
I have installed the drivers multiple times, i have looked up the mtp inf drivers and nothing happens. When I connect it to the computer it only says chaging on the lockscreen thats it! I have no idea how to fix this. I am trying to go back to stock because i lost root flashing a custom nougat build. everything works except twpt won't boot up anymore and just hangs at the splash screen. and of course I don't have root. can anyone please help me! thanks
Click to expand...
Click to collapse
Mine gives a notification that the phone is charging when I connect to computer but if I click the notification it gives me the option to transfer files instead. You do have USB Debugging enabled on the Developers Menu, correct?

Hello guys
I have the same problem on my phone i tried everything i found on google and other forums, and the last option that i couldn't do is to send my phone to replace the usb port, but i have no warranty as i bought it already used. It's a shame that no one can find a solution here especially that the other forums at least tried to fix for some people but not here on xda which is the first in the world.

driss.sadok said:
Hello guys
I have the same problem on my phone i tried everything i found on google and other forums, and the last option that i couldn't do is to send my phone to replace the usb port, but i have no warranty as i bought it already used. It's a shame that no one can find a solution here especially that the other forums at least tried to fix for some people but not here on xda which is the first in the world.
Click to expand...
Click to collapse
I've even changed my USB port and daughterboard twice. I am stumped. I got 3 laptops 2 running 10 and one running Ubuntu and mAid along with a tower running xp. I fix unfixable phones and resell them. I've tried EVERYTHING. I know this is an old thread but Any help would be appreciated.