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] Upgraded to CM10, lost all usb charge / data connectivity!

Hi,
So I upgraded from cm7.2 to 10 on my defy green lens. After a long and difficult upgrade, almost everything works - except any functionality of the usb port...
I'll jump right into the real deal: without usb connectivity, I cannot try to flash other SBFs to fix it! I can enter the bootloader screen just fine (says 09.10 on top, I believe that the last SBF I flashed was 3.4.2_179-002 , as recommended, before I rooted it, 2ndinit, and sucessfuly installed cm10) and the phone recognizes when I plug in a usb cable to it. but the computer always shows up a "usb device not recognized" error, and I tried on two machines, winxp/win7, and several different usb cables. I read some threads about crashing drivers between rsdlite and different tools motorola made; I never installed any of that junk but just to be on the safe side I removed all drivers and started fresh. still no go.
______________(That's the problem, now I'm just going to give more information about it)______________
The phone does not charge off a computer nor from a wall charger, with an assortment of different usb ports, cables and chargers. when connected to a computer (whether the phone is on or off) a "usb device not recognized" message comes up, on both windows xp/7 (different machines.) Seldom, when connected to wall charger, I can get the battery icon to show charging for about a second, (after a restart and plugging in to the pc briefly beforehand.) If I'm so lucky to make that happen, either it goes off in about one second, or it will change statues from charging to not charging several times very rapidly and then stay on not charging.
If the phone is off and I connect it, the white led sometimes come on, and then the phone comes on- presumably to go into battery charging screen, but instead it boots up normally. (this may be the correct behavior with this rom. idk.)
If you care for more information, let me elaborate about what I mean by "After a long and difficult upgrade":
I previously upgraded to cm10 (30/7/2012) CM10-20120730-NIGHTLY-mb525.zip,
but downgraded shortly after, back to 7.2. (I decided to wait for something a bit more functional)
Back then both the upgrade/downgrade went fine. This time I got into a bootloop (or stuck on bootscreen) after updating to 26/03/2013 God's version (oops I meant Quarx's version.)
Trying to use my nandroid backup for 7.2 I got a md5 mismatch and even after generating a new md5 file I couldn't restore /data.
Moving on. using CWM I tried installing some kernels (kernel-froyo-222-179.zip, and same thing but signed,),
then a fixed sbf (not full) 3.4.2_177-Fixed.NORDIC_DEBLUR.sbf,
and a very crappy sbf JRDNEM_U3_2.26.0_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB1B5TEL02A.0R_USAJORDANTELSTRA_P033_A017_M008_HWp3_Service1FF.sbf
** this one almost gave me a heart attack, after successful flash defy black screened with no LED indications. I was able to work my way into the bootloader and flash another SBF with rsdlite, without any indications from the device. lucky me.
Then I flashed the sbf I mentioned above and that's how I eventually got into cm10.
I can't even downgrade to stable cm7.2. Tried flashing a fresh install through CWM (wiping everything before and after, of course) and ended up stuck on boot screen. I don't know if it has anything to do with CG numbers or what, but I really can't figure out why CM7.2 wouldn't boot on the same SBF CM10 is booting fine right now.
I can't also share the SD card through CWM. (-> device not recognized)
I'm losing my marbles over here. Been working on it for two whole days and can't think of anything else I can try out... If I flashed the wrong rom using CWM I might get locked out because bootloader won't be any help!
:crying: cry for help... thanks :fingers-crossed:

Have you tried installing adb and the motorola drivers so you can try to communicate with the device?

Thanks for your word zero gravity!
Well, I thought that since "usb device not recognized", and since it shows up as unknown device under device manager (currently it disappears and reappears every 3 seconds, but I think this is a new behavior) I automatically assumed that I couldn't get proper communication with it! I guess I got to do some reading about adb commands any help with it would greatly be appreciated (No worries though I know how to google )

http://forum.xda-developers.com/showthread.php?t=1241935
Here's a simple guide for adb. Hopefully you can get some sort of communication to flash your stock sbf and start over again.

So, even though I have the drivers installed (Motorola_End_User_Driver_Installation_4.9.0_32bit.msi_.zip, and also installed MotorolaDeviceManager_2.3.9.exe,) Android SDK Tools installed, then I tried adb devices - nothing comes on.
by enabling ADB over network I can adb connect to the phone through wifi and go into shell. but I can't see how I can debug the buggy usb interface with network access.
Also tried starting the adb service through recovery - no go, won't show up.
(I plugged in a different Android phone (an Xperia), installed the drivers and had it running on adb usb in no time. So I'm doing it right.)
Any thoughts? are there commands to specifically listen and figure out what's coming from the usb port?
any other leads anyone may have? I'm listening!
Cheers, Shawn

The port must have suffered hardware damage. Examine the port for obvious conductivity hindrance. If not I'm afraid you'll have to get it repaired
As for cm7.2 after flashing just format to ext3 from boot menu(before this wipe dalvik cache), and after a reboot wipe data from stock recovery for good measure
Sent from my MB526 using xda premium

Well, thekguy seems to be on the right track.. I can fiddle around with the usb plug and get it to charge, So the problem seems to be mostly physical - if not completely.
I still can't get it to connect properly to the computer, but go figure which usb signal is dropping off. might be power, might be data.
After spraying it several times with contact cleaner the port is good enough for steady charge. No change about how it doesn't connect to a computer.
I feel like a dumbass, cus I already gutted the phone up a couple of days ago to try tracing conductivity paths through the port. the usb port is cast in plastic that is not removable from the pcb. There's no access to the USB pins, excepting four conducting points through the plastic right next to the port, but they are all connected to ground - they probably belong to a bracket that's holding the plastic to the pcb.
anyhow I did all that (I got closeup pictures if anyone's interested) but I wasn't able to check conductivity, and I didn't try fiddling with it after that. bah!
___________________________
Still wondering about one thing! The bootloader is locked, so that means it was never-ever changed since the phone was manufactured, correct? So no effect of writing different SBFs on the bootloader, correct? (minding the Efuse and CG numbers)
if so, than can I conclude only by that information (and that I cannot connect the phone to the computer anymore with bootloader) that there must be hardware/physical damage? I've just completely eliminated the software factor out of the equation. haven't I?
Did I miss anything? let me know.
P/S, I'm going to stick with this phone as it is. I can work around never having usb data connection.
Cheers

Can you try installing Linux and see if the you can mount /system or even /sdcard on Linux from bootmenu? Bootmenu mount only works in Linux. I've tried it in Ubuntu 10.10
Its worth a try, if Linux doesn't see it then it must be a hardware issue and would need a Motherboard replacement.
Use ubuntu live disk to make things easy and not mess your Windoze
Sent from my MB526 using xda premium

You're right, sbf flashing cannot break usb functionality. I'm not very well versed in mobile hardware but I think the port can be replaced, though I don't know how. It may be possible that a local mobile store could fix it.
Trying Linux is a good idea, though it may not work out from the looks of it(the phone)
Sent from my MB526 using xda premium

If anyone is reading this, I had some bad batteries and a usb port that is having physical problems. I'm flashing it with contact cleaner spray every now and again and it helps. I can get a usb connection to the computer and charge it with a bit of luck and while I keep it stationary.

[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?

Nexus 7 2012 No rom, adb or fastboot

Okay so i have a nexus 7 right? yes, but im fairly custom to rooting and all that stuff. Well im not a nub at this stuff but i need help once in a while XD, i just got the thing to turn on again i let it die completely and the charging bug decided that it wouldn't charge. I ended up jump starting the battery and now it turns on but now i plug it in it turns on right? yes it does but now i can get access to any data thats on it. (P.S there isnt any data on it since i had to wipe cyanogenmod 6.0.1 off it) and theres only twrp recovery on the tablet, i can access twrp and the boot loader (unlocked obviously) but i cant access fast boot or push files via adb. The charging port is still good on it i know that we had it tested on a friends tablet and it worked fine. OTG usb doesn't work either i cant seem to get data on the tablet but it turns on when i plug it in, it doesnt charge when plugged into a wall adapter or a pc it just turns on when plugged into a pc. Any and all info is appreciated. (sorry for my spelling errors if there is any, also i am on linux so i dont need drivers as far as i know, i also tried on windows and its a no go the device doesnt show up on either os)
nexus 7 2012 btw
-Loch

Eh just dont bother guys im pretty sure its dead, the nexus help forums didnt have anything.

download google usb driver, follow the instuctions to get fastboot working
then grab factory image and flash it

nguyenlucky said:
download google usb driver, follow the instuctions to get fastboot working
then grab factory image and flash it
Click to expand...
Click to collapse
Thanks for the help but sadly ive tried that...

As the device can go into fastboot and twrp with adb and otg without data transfer being possible I'd say most likely the port is broken.
Just to be sure no adb or fastboot commands work at all right? even those which don't transfer files. If they work then your partition layout is messed up which could be fixed
Gesendet von iPad mit Tapatalk

Did you try to charge the N7 via wall adpater or the pc? Did you use the genuine charger that comes with the device? What does it look like when you plug it into your pc? Did it show up as a mtp device (or any kind of device) ?
Try charging the N7 with genuine charger, or via pc. Make sure you install the driver for the N7 (go google it) before plugging in. Judging by your status, it appears that you're having a defective charging port or mainboard. Usually you'll end up sending it to the manufacturer to get them replaced (hope that it won't happen :3 ).
Have you used the push files and adb function on TWRP? To the best of my knowledge, these errors don't come about often in TWRP. If you don't know to use it, look it up on Google or the Xda threads. One more thing, losing fastboot is pretty rare with N7, so if you're not sure whether the fastboot is VANISHED, go to this link: http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
You can contact me for more insight if all that doesn't satisfy you: [email protected]
Glad that I could help.
John

windows 10 can't see fastboot (but can see adb) and my recovery is fried.

Trying to breathe life in this old tablet. Using current Andrdoid SDK USB driver. ADB works fine. Boot into bootloader and fastboot devices sees nothing. Been banging my head on this for hours, trying to manually modify android_winsub (which I've done in the past with various devices..but not on win 10). I've disabled device driver signing. I've added entries in the two locations, pulling the PID/VID from Device Manager.
..was going to cut and paste the changes but my desperate SDK install killed my backup copy.
basically it had no %SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4E40
for the Nexus 7 (no longer remember why). Tried pulling the values from Device Manager but no go, I should have screen shotted the error.
So without fastboot I tried using Flashfire. It failed, leaving me with no Recovery, Boot Failed when I try to enter recovery. so the TWRP app isn't working either (not sure why I didn't use that to begin with). I had 3.0.0.0 on it.
I have been googling for hours, not an uncommon problem, but no solutions have worked for me.
Help?
Here's what I see in device manager when in fastboot mode:
ok scratch that, in USB controller section there was an errored item which is gone now -- but fastboot still not working. Fastboot devices returns nothing. I;ve tried multiple cables, USB3 and USB2 ports, I really don't like not having a recovery nor means to install one......Interesting that device manager no longer shows an error though after yet another Google USB driver install. Making it even harder to troubleshoot.

If I could be given the exact dd parameters to run, I could conceivably dd TWRP 3.0.2.0 into the correct location I just realized...at risk of bricking. I'm willing to take that risk if anyone knows with 90%+ certainty the command.
I found some useful info on ways to do it, but adb remount command no longer exists so don't want to continue on those instructcions..

definitely seems like a driver issue, have you tried drivers available in wugfresh's tool?

Yes. It can't get any response from bootloader either.
I'll make a restore point and try again....
Edit: If I could find a flash_image binary that works on N7 2020 wifi (grouper) I could do this.....
abhifx said:
definitely seems like a driver issue, have you tried drivers available in wugfresh's tool?
Click to expand...
Click to collapse

And wugfresh's #1 driver recommendation.... Is Google's drivers. But I tried #2 universal drivers, no change. I noticed my Android SDK winusb.inf didn't even have a bootloader section on nexus 7. No idea why. I am on latest version. Deleting and reinstalling did bring back an entry, but not the functionality.
Sent from my Nexus 5X using Tapatalk

Bump for ideas? Windows 10 not seeing bootloader's seems a common problem, but most remedied by drivers
Sent from my Nexus 5X using Tapatalk

I have won 10 x64 and it works just fine. Install 1,2,3 adb fastboot deivers, but boot windows in mode that allows unsigned drivers.
Use original usb cable. My N7 had usb port problem, it wasn't detected as normal device

I've followed some instructions that instructed disabling driver signing, didn't help, but you may be on it with the cable. Original is long gone but we know how hit or miss cables are, and I'm using a connector/cable extender. Great idea to try a few quality cables. The current rev Google drivers DO have an entry for bootloader mode in N7 (not sure why mine were missing and I was trying to manually add them). But even then the unknown USB device in device manager reports different PID/VID than is in the inf file. Edit: But that extender could have been muddling things. Anyway, great suggestions to work on. Appreciate it.
Sent from my Nexus 5X using Tapatalk

try to cut some plastic at 45 degrees angle, so it goes all the way to the port. My S7 cable did't work well, so I went with SWR50 sony cable, cut it a lil bit and it works like the original from N7

Not sure what I would do with the plastic? Insert as a wedge into the port? My trick to getting old cables working in old connecters is use my eye tooth and bite gently down on the metal on the long side. Creates a little v crimp that brings the cable back to life. Trick is how gently you do it.
Sent from my Nexus 5X using Tapatalk