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

[Q] Galaxy S5 CANT FIND USB

Im in England and the phone for S5 for America, how do you find the USB "connection as camera" its not in the notification panel ? im trying to get on Kies, but i cant.

ron101 said:
Im in England and the phone for S5 for America, how do you find the USB "connection as camera" its not in the notification panel ? im trying to get on Kies, but i cant.
Click to expand...
Click to collapse
Do you have the usb drivers installed correctly? Or try another usb port/ cable.

IVE put the USB driver in the c drive along sid the KIES and still it says its (USB) not recognised. Is there something else i could use instead ,i didnt like kies anyway.I tried to get airdroid to work (ive had that for 3 years) but it doesnt handle software (my phone) 4.4.2 it only does 4.3. It says FORBIDEN.FAILED TO SEND MESSAGE on my PC.

Most likely you are using an outdated version of Kies. There are multiple versions of Kies, ensure that you install the latest version of Kies. Then open Kies and have it detect your phone. That is by far the easiest way to install the proper driver for your S5 model. After the driver is in place you can close Kies and never use it again. Or uninstall it if you wish.
Do not use an USB hub, connect directly to your phone. If you have ongoing issues, use a different USB cable and port. Ensure that you are using a data cable, not a charging (only) cable that has the data lines shorted. If your PC has USB driver issues in general, then you'll need to resolve those issues first or use a different PC.
.

fffft said:
Most likely you are using an outdated version of Kies. There are multiple versions of Kies, ensure that you install the latest version of Kies. Then open Kies and have it detect your phone. That is by far the easiest way to install the proper driver for your S5 model. After the driver is in place you can close Kies and never use it again. Or uninstall it if you wish.
Do not use an USB hub, connect directly to your phone. If you have ongoing issues, use a different USB cable and port. Ensure that you are using a data cable, not a charging (only) cable that has the data lines shorted. If your PC has USB driver issues in general, then you'll need to resolve those issues first or use a different PC.
.
Click to expand...
Click to collapse
KIES V3. The trouble is i cant find the USB i now it should be there in the notif panel but it is not, ive got developer options & usb debugging ticked but thats all, have i got to do anything else (hair pulling time) i dont think so?
1) Should i plug it in the mains or usb on the pc
2) Im using the cable that came with the S5 is that good enough.
3) The S5 sits on a cradle shall i take it of.
4) How do i tell data cable, not a charging (only) cable that has the data lines shorted
5) Ive tried 4 different USB software and it gives the message DEVICE DRIVER SOFTWARE WAS NOT SUCCESSFULLY INSTALLED every time
6) Ive done a reboot every time the drivers are put it
ron

ron101 said:
KIES V3. The trouble is i cant find the USB i now it should be there in the notif panel but it is not, ive got developer options & usb debugging ticked but thats all, have i got to do anything else (hair pulling time) i dont think so?
1) Should i plug it in the mains or usb on the pc
2) Im using the cable that came with the S5 is that good enough.
3) The S5 sits on a cradle shall i take it of.
4) How do i tell data cable, not a charging (only) cable that has the data lines shorted
5) Ive tried 4 different USB software and it gives the message DEVICE DRIVER SOFTWARE WAS NOT SUCCESSFULLY INSTALLED every time
6) Ive done a reboot every time the drivers are put it
ron
Click to expand...
Click to collapse
If you use Windows 8(.1) you have to disable driver signature verification to get the usb drivers installed. Here is a tut. https://learn.sparkfun.com/tutorial...abling-signed-driver-enforcement-on-windows-8.

gee2012 said:
If you use Windows 8(.1) you have to disable driver signature verification to get the usb drivers installed. Here is a tut. https://learn.sparkfun.com/tutorial...abling-signed-driver-enforcement-on-windows-8.
Click to expand...
Click to collapse
Noooop its not that i have win 7 pro
ron

You are juggling too many unnecessary variables. Try to simply that and don't skip checking any of the points.
I have no idea what you mean by plug it in the mains? And at least until you solve this you should not be using a cradle, hub or anything else. As I suggested earlier, connect the phone directly to your computer USB hub. And if you have ongoing problems, try a different cable, USB port or even PC.
Making an assumption that the cable that came with the phone is good enough is counter productive. It's not impossible that it may be damaged or have some problem. Borrow or buy another cable, to eliminate one more possible cause of your issue.
Retrace and double check each step. As soon as you make an assumption that it's not worth checking x step because it couldn't possibly be the cause, you are skipping a possible solution. Make sure that you are using the latest Odin, make sure that you installed it from windows administrator mode, connect directly to the PC's USB port, different cable, etc. If you are methodical, you'll resolve the problem.
Good luck
.

Have you activated developer oprions and usb debug?

ron101 said:
IVE put the USB driver in the c drive along sid the KIES and still it says its (USB) not recognised. Is there something else i could use instead ,i didnt like kies anyway.I tried to get airdroid to work (ive had that for 3 years) but it doesnt handle software (my phone) 4.4.2 it only does 4.3. It says FORBIDEN.FAILED TO SEND MESSAGE on my PC.
Click to expand...
Click to collapse
If you haven't given AirDroid permissions to send SMS directly, "FORBIDEN.FAILED TO SEND MESSAGE" might appear. Change the permissions in phone's settings for a try

fffft said:
You are juggling too many unnecessary variables. Try to simply that and don't skip checking any of the points.
I have no idea what you mean by plug it in the mains? And at least until you solve this you should not be using a cradle, hub or anything else. As I suggested earlier, connect the phone directly to your computer USB hub. And if you have ongoing problems, try a different cable, USB port or even PC.
Making an assumption that the cable that came with the phone is good enough is counter productive. It's not impossible that it may be damaged or have some problem. Borrow or buy another cable, to eliminate one more possible cause of your issue.
Retrace and double check each step. As soon as you make an assumption that it's not worth checking x step because it couldn't possibly be the cause, you are skipping a possible solution. Make sure that you are using the latest Odin, make sure that you installed it from windows administrator mode, connect directly to the PC's USB port, different cable, etc. If you are methodical, you'll resolve the problem.
Good luck
.
Click to expand...
Click to collapse
AFTER last nite i started again this morning (im disabled completely down the right side of my body) with a new spirit fffft i got stuck in.So here we go first i put the USB cable in another usb port (one that i havent used) and the phone came alive and that was that it was done.So i tried another usb cable,that also came alive, so that was that it was the usb port that i was using wasnt suitable simple as that. Thank you for all of your help fffft and the rest it was essential for me THANK YOU.

[Q] HELP with recovery, no usb access to nexus 7, not detecting with official cable.

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?

Bricked Lenovo Vibe Z2 Pro / K920

I was trying to fix a camera issue while on holiday with my phone but accidentally wiped some partitions during the rewrite of my rom my dad pulled the cable out and now my phone is totally unresponsive. If I plug it into my windows 10 laptop I get a device descriptor request failed error and I am unable to fix it. From reading an article on androidbrick I would post a link but I don't have enough posts it looks like it should show up as a com port but it does not for some reason all the drivers are installed and I have tried forcing the driver onto the device and it won't accept them. The fix I need is a way to get the com port to display so I can reflash and program the bootloader. I am still on holiday so currently have limited equipment basically the phone, usb cable and my laptop and sometimes wifi.
Any help would be appreciated a this issue is driving me crazy. :crying:

bobthemac said:
I was trying to fix a camera issue while on holiday with my phone but accidentally wiped some partitions during the rewrite of my rom my dad pulled the cable out and now my phone is totally unresponsive. If I plug it into my windows 10 laptop I get a device descriptor request failed error and I am unable to fix it. From reading an article on androidbrick I would post a link but I don't have enough posts it looks like it should show up as a com port but it does not for some reason all the drivers are installed and I have tried forcing the driver onto the device and it won't accept them. The fix I need is a way to get the com port to display so I can reflash and program the bootloader. I am still on holiday so currently have limited equipment basically the phone, usb cable and my laptop and sometimes wifi.
Any help would be appreciated a this issue is driving me crazy. :crying:
Click to expand...
Click to collapse
Sorry as this may be not much of a help to you but rather my experience with pretty much the same situation.
I couldn't turn on the phone and there were no signs of life when connecting it to a PC (only a message that USB was not recognized with the same description as you mentioned - device descriptor request...).
I tried to connect the phone on different PCs with different OSs (from XP to Windows 10), different drivers/tools, but there was always the same USB error displayed.
Eventually, I had to return it to the service center (it was under warranty) but they couldn't repair it, so luckily they sent me a new one

PC won't detect S7, all conventional fixes exhausted!!

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