I have been using adb and fastboot for about 6 years now and have never had an issue with ADB. ....Now all of a sudden i cannot for the life of me get it to work or should i say for it to authorize my phone. WTF do i need to do? Im boiling over here and my phone is about to become an expensive baseball.
I have read three or four forums on people with similar issues and the "fix" doesnt work at all.
I have deleted the RSA keys from PC.
Reinstalled drivers
Rebooted phone and serverf
I have no option in my phone to revoke computer.
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
For some reason, I can no longer get any computer to recognize my Nexus 4 when connected by USB. I can charge but cannot get the phone recognized.
A couple weeks ago, everything was working fine. I was running Cataclysm (November build based on 4.3). I upgraded to the Nexus 5 and decided to give the Nexus 4 to my daughter. I was able to connect the Nexus 4 to the computer and move all my photos and music etc off of the phone. After moving my files off and doing a Titanium backup and Nandroid just in case, I did a complete wipe on CMW (6.0.3.5). Everything fired up fine and I had no reason at the time to test the USB.
However, last week, my daughter was complaining about bad battery life and I decided to take a look and go ahead and update the phone to the latest (Dec. 12) Cataclysm build based on 4.4.2. Before flashing the new build, I connected the phone to the computer by USB but could not get the computer to recognize the phone. The phone charges, but is not recognized in device manager and does not connect.
I've done everything I can think of to troubleshoot the issue - all without luck - including:
Turned USB debugging on and off. No luck.
Changed the USB storage mode from MTP to PTP and back. No luck.
Confirmed fast charging isn't somehow enabled. It isn't.
Tried several different USB cables. No luck.
Tried a different Nexus 4 and my Nexus 5 on the same computer. They work.
Tried the subject phone on a different computer running Windows. No luck.
Tried the subject phone on a computer running Mac OS. No luck.
I did go ahead and flash the latest Cataclsym build (I did a full wipe again) but sill no change. I don't see any evidence of physical damage to the micro USB port but I took a small toothrush and gently cleaned the contacts with rubbing alcohol.
At this point, I believe the problem is either the a) the port is bad or b) somehow, the phone software/ROM is screwed up.
Is there any way to determine whether the physical port is bad? Any other ideas. I'm kind of at the end of my capability here.
can adb recognize it?
Code:
adb devices
Riro Zizo said:
can adb recognize it?
Code:
adb devices
Click to expand...
Click to collapse
I don't think so. I'll have to check tonight when I get home. I tried to get Wug's toolkit to recognize the phone with no luck but haven't tried that command on its own.
Riro Zizo said:
can adb recognize it?
Code:
adb devices
Click to expand...
Click to collapse
No luck. I attached the Nexus 4 to the computer, entered a command prompt to navigate to the platform tools director that has the adb files and entered the "adb devices" command. The response was "List of devices attached" with no phone (or anything else) listed.
I have that issue too. I´m on windows 8 and to root and being able to recognize by the pc I changed it to PTP. It only works in PTP and I have to pass all the data to the camera folder to send info
Gildegan said:
I have that issue too. I´m on windows 8 and to root and being able to recognize by the pc I changed it to PTP. It only works in PTP and I have to pass all the data to the camera folder to send info
Click to expand...
Click to collapse
I don't think I've got the same issue. I cannot get any computer to recognize the phone under any mode (storage, photo, debugging on, debugging off). Nada. At this point, I'm pretty sure it's the port gone bad. I just wiped the phone again and clean flashed the stock 4.4.2 ROM, radio and bootloader. Still no connection.
Argh.
SHPhone said:
I don't think I've got the same issue. I cannot get any computer to recognize the phone under any mode (storage, photo, debugging on, debugging off). Nada. At this point, I'm pretty sure it's the port gone bad. I just wiped the phone again and clean flashed the stock 4.4.2 ROM, radio and bootloader. Still no connection.
Argh.
Click to expand...
Click to collapse
can you try going to recovery, then type adb devices?
Sent from my Nexus 4
I had this problem and i found away to fix it. Plugin your phone to a computer. Start > right click on my computer > properties > device manager. Look for Samsung > expanded it you will find Nexus 4. Right click on it and choose uninstall and check uninstall driver. Unplug your phone and restart the computer. Re-plug the phone and wait for the drivers to install.
Sent from my Nexus 4 using Tapatalk
I know that there is countless posts out there on how to do just this, but for me it is just not working.
I just got this phone via warranty replacement one week ago and all of a sudden the screen is unresponsive. The whole phone works, can open camera, take screen shots, everything. I just can't touch the screen.
Through the last 3 hours or so I've been trying everything and I finally found someone that had a solution, to delete NextSMS from the phone. Apparently that app has caused other screens to stop responding, my only problem is that I can't figure out how to uninstall it if I can't touch the screen. If I get adb running on my computer and on my phone, and type "adb devices", it returns:
"numbers/letters" sideload
But then when I type "adb uninstall com.handcent.nextsms" it returns "waiting for device..." and nothing happens. the phone never receives a command at all. I have enabled usb debugging before on my phone, but I fear that I changed the usb mode to charging only so when I had it plugged into my car it wouldn't try to read the device. The only thing I haven't tried is a factory reset because I have pictures and videos on my phone that would kill me if they got deleted. I never got the chance to back it up and already sent my old phone back. My phone is not rooted and is up to date, I have not done anything to it besides doing the SmartSwitch with the previous device to get all my **** onto this phone. I have tried to boot into safe mode as also suggested, but that hasn't worked either, this led me to believe it wasn't apps and actually a faulty phone but the other post I read about the whole handcent thing also tried booting in safe mode and it didn't work either.
To recap I have tried:
restarting
letting the phone die completely
recharging the phone completely
booting into safe mode
deleting the app via adb
opening bootloader (whenever I choose this option, my phone just reboots normally)
deleting via Play Store on my computer (saw guides for this, and I feel like they updated the website to actually take this feature away...)
should I try to install a custom rom? is there anything ATT can do? I'm reluctant to install a custom rom because I don't want to lose the warranty.
I'm slowly coming to the conclusion that since USB debugging isn't on, there's nothing I can do and all my data is lost... Please someone prove me wrong.
Also forgot to mention, when I plug my phone into my computer, it recognizes it as a Samsung-SM-G298A but show it as an empty device with no storage at all. Which basically proves it's not in usb debugging mode iirc.
sound like a hardware issue to me , sent it back for warranty ?
So I plugged my phone in this morning to my work computer, to copy some files on to it, and the whole mtp storage thing didn't pop up. No sound or anything. I set it to MTP in developer options, still nothing. So I tried it on my laptop, same thing. Then went and borrowed another usb c cable from a coworker. Tried it on all the machines and still nothing. So I ran around the office trying it on every windows pc I could find. I stopped after it didn't work on the 7th.
So I am running LOS so I updated to the latest nightly. Still nothing. So I boot into recovery to back everything up and to flash stock. But I remember you can mount MTP from within TWRP. So I tried that and it still didn't work. Then I tried ADB while in recovery and THAT didn't work. Booted back into OS and tried ADB and it didn't work (this was working earlier this week). Tried this all on redundant pcs and cables. Not one machine made the sound you usually hear when you plug something into it. So I cancelled the back up and booted fastboot. THAT WORKS!
What do you guys think? Has anyone ever seen this behavior?
This is currently my 3rd Axon. I am not sheepish about getting this thing back to stock to do the warranty, as I've done it 2 times. Both times were hardware issues.
TL;DR My phone will not work when connected to any windows pc. I've tried MTP storage and adb. The PC doesn't even register that something was plugged in. Tried multiple cables/pcs. FASTBOOT DOES WORK HOWEVER.
The other day I was trying to flash my 6p back to stock so I can sell it, and I was flashing everything through cmd, until all of a sudden cmd stopped working towards the end for some reason. Now my phone only boots into fastboot mode and is NOT being detected by my pc. When it's plugged in, the fastboot menu says to connect the data cable. I've tried restarting my computer and reinstalling the drivers, but nothing seems to work. When I go into cmd and type adb devices, nothing shows up when it's plugged in, and device manager doesn't show any changes whether it's plugged in or not.
I've called local cellphone repair shops, but apparently if it's not Samsung or iPhone they can't help
Btw I've searched the forums and haven't found a solution to this problem.
Robertdudeman said:
The other day I was trying to flash my 6p back to stock so I can sell it, and I was flashing everything through cmd, until all of a sudden cmd stopped working towards the end for some reason. Now my phone only boots into fastboot mode and is NOT being detected by my pc. When it's plugged in, the fastboot menu says to connect the data cable. I've tried restarting my computer and reinstalling the drivers, but nothing seems to work. When I go into cmd and type adb devices, nothing shows up when it's plugged in, and device manager doesn't show any changes whether it's plugged in or not.
I've called local cellphone repair shops, but apparently if it's not Samsung or iPhone they can't help
Btw I've searched the forums and haven't found a solution to this problem.
Click to expand...
Click to collapse
Can you enter recovery?
No I can't enter recovery