Hi all, I installed 4.1.83 and could not access adb anymore, I flashed the 4.1.26 retail SBF and still I don't have ADB access.
Things I have done:
1. I downloaded the SDK to a different folder and tried from there
2. I tried to install the motorola drivers/sdk on a different PC with the same results.
3. I flashed 4.1.57 SBF , same thing.
I am now on 4.1.83 with no sideloading so I cannot run gingerbreak and restore the nandroid backup i have.
Anyone lost access to ADB in their atrix or have any idea?
•Switch usb ports to one on the back of the pc.
•One thing that worked for me was copying a shortcut of cmd into the same folder that moto's adb drivers were installed into and just opening cmd from there it gave me adb right away
•other than that I'm out of juice no one else seems to have reported this I would double check the basics you know debugging mode usb set to none and if you had used gladroot before run after update on 1.83 I heard it brings root back. Could solve your whole issue and save you the mess of a possibly formatted sd card
But thats just my 2 cents
Sent from my Atrix
Thanks for the reply.
* I switched PCs so the port is not the issue.
* Tried it
* USB debugging is enabled and Gladroot can't help if "ADB devices" returns an empty list.
Thanks for all the ideas though.
If you're using front ports sometimes they don't push enough power to the device try a rear port
But thats just my 2 cents
Sent from my Atrix
try a different cable. I had a problem with one of my cables, whilst it worked on my HTC something it didnt work on my atrix
Tried that too with n success, thanks.
Solved:
I had to undo the usb debugging and enable it again, for some reason it does not stick after reboot.
Related
Hi XDA. I have a problem and could use your help.
In order to make flashing ROM’s easier for myself I thought it would be a good idea to place them in the first folder listed on the internal sd card. In order to do this I placed a “.” befor the name of the folder. After wiping everything I learned CWM 5.8.1.8 (touch) does not see folders with dots(“.”) at the beginning. So I now am in recovery with no ROM to flash
I then proceeded to dig an even deeper hole for myself. In my attempts to install drivers for my device I have done something; now my computer fails to recognize that the device is plugged into the USB at all. Prior to my messing with it I would hear the USB input chime and Device Manager would show an “unknown device”. Now when I plug in my device nothing happens. I have tried two computers and both Win7 and Ubuntu.
I read that Linux might be able to see my device so I installed Ubuntu then the Android SDK as per this thread. It did not work for me. I still cannot see my tf101 but I can see my Nexus s with the “adb devices” command.
I bought my tf101 refurbished and can’t find the “B” version written on the device. I think I initially rooted with razorclaw...not %100 sure. I am not sure adb debugging was checked when I wiped...not sure it makes a difference at this point.
I am now looking at these NvFlash instructions but I can’t get past the 2nd step (I am a noob...obviously)
- run “./blobunpack recovery-clockwork-5.8.2.1-tf101.img” (Replace “recovery-clockwork-5.8.2.1-tf101.img” with the name of your downloaded file”)
Will this NvFlash tutorial work if the computer can’t see the device?
Any ideas?
Thanks for your time!
Try those steps from this website Reverting to Stock ROM (unroot and remove CWM recovery)
this is easier for you when u try to nvFlash your tf101. remember update driver, run as administrator on program
Thanks for the info!
I am away until tomorrow evening. I will try it then.
Hi,
I am still having problems.
Can I install drivers if the device is not listed in device manager? How?
Thanks again!
it will be reinstall or request when you unplug and plugin back your connect from tablet to PC
if your driver had been load or connected just go to Devices and Printers to check your connection, after that update your driver
Hi. Thanks for trying to help.
My problem is my computer is not seeing the device at all. No USB input chime. Nothing showing up in device manager. No nothing!
Could be the chord I guess but I don't think so. I was getting "unknown device" in device manager initially after I wiped the ROM. After attempts to install drivers I stopped getting any sign of the tf101 in device manager.
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
DTTD said:
Hello All,
Basically, while Nexus is on it does not charge or even recognize a charge from anything, and it also does not recognize when plugged in via USB to my PC.
This occurred a week ago, noticeably a few days after installing MultiROM for testing. I thought MultiROM may have been the cause so went entirely back to stock ROM but still not working.
Couple things that I have noticed... When using MultiROM my drivers are no longer recognized as they should, but instead as Andriod bootloader. I had uninstalled and reinstalled new drivers to allow the flash and correction to Stock, which did work, but now nothing even remotely similar to my Nexus is showing up in my Devices. I have double checked with multiple cords, still no luck... I will say that I have not Enabled USB Debugging because I cannot. Every time I attempt to enable USB Debugging, the Nexus freezes up and reboots... I'm thinking this is the root cause of the issue or there is a fluke bad pin issue in my internals of the Nexus...
It seems that I cannot work in fastboot or adp mode as the USB is not recognized...
I've searched for several days for hours at a time for more info on this, but no luck! Any thoughts and help would be helpful!
Thanks!
Click to expand...
Click to collapse
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Fallon9111 said:
Try doing a factory reset first, then see if USB debugging works.
If it won't work, could you try downloading a normal recovery on your device and installing without fastboot and adb connection with computer (I think that is possible, not sure). Is download, boot into recovery and flash like a ROM. Sorry if that's all wrong, I did Google but found nothing, yet I'm sure I did that to install a newer version of twrp???
Also, if you have root, could you try using adb over WiFi, this should work the same, although there is no fastboot.
Good luck!
Click to expand...
Click to collapse
Thanks for providing more information on this. I have done a Factory Reset via Settings and also via Recovery, but still not available.
I think I'm making progress with adb via Ubuntu over USB, but USB Debugging still gives the Epic crash and still will not charge while On, which is more just annoying than anything else.
Asus/Google Support are saying it is a physical pin issue, but that doesn't explain why USB Debugging is failing. Does anyone know where the USB files are contained? I'm wondering if I've messed up at the Kernel level. Any thoughts?
About my Nexus - More Info
I forgot that I should provide more information about what I'm running:
Phone: Nexus 7
Android Version: 4.2.2
Kernel version: 3.1.10-g05b777c
Build number: JDQ39
Prior to issue also had:
Recovery: TWRP
ROM: Stock JDQ39
MultiROM: Yes
UPDATE
So after more work on my Ubuntu we have found more information and seem to have narrowed down the issue! :fingers-crossed:
I have been able to flash via Fastboot just fine, which has thus allowed me to get TWRP installed and now I'm back rooted. I still cannot adb via USB though. We've double checked with multiple Nexus 7's of the same type, which allow command: adb devices and their devices will show, while it does not for my device. (Side note: my version of Ubuntu does not "see" the adb command in its pwd so... But tests have been done on other machines and worked...)
So after sifting down to adb issues, we found that in /data/property I'm missing persist.sys.root_access and persist.sys.usb.config ... But creation of persist.sys.usb.config didn't do anything...
Since my Moto X already received its KitKat OTA, I finally got impatient tonight (and had a little free time) so I decided to sideload KK onto my stock/unrooted Nexus 10. Unfortunately, this has not turned out well for me.
Since I received the previous OTAs so quickly, I never setup ABD/Drivers/etc. for the N10. After fumbling through that (missing hardware ID in .inf file, etc.) I'm finally to the point where everything looks like it should work. ADB recognizes my device in recovery mode, various ADB commands seem to work without issue, and so on. However, when I fire off the adb sideload KitKat.zip command, all I see on my PC is:
sending: 'KitKat.zip' 1%
On my N10, nothing changes. All I see is the normal:
Now send the package you want to apply
to the device with "adb sideload <filename>" ...
I've rebooted both my PC and my N10 at least a dozen times. I've tried switching back and forth between the Google USB drivers and Koush's universal drivers, but the behavior is always the same.
I've done a bit of googling on this issue without any luck. Anybody have any pointers beyond just being patient for the OTA?
This may sound crazy, but try another USB cable. I had the same exact problem. And since adb recognized it and it charged fine when plugged into my PC, I thought it couldn't be the cable. I tried everything including koush's universal adb drivers as well as 2 other PC's with no luck. But I tried a different USB cable and it worked fine.
Same problem...
I have exactly the same problem here with a Samsung Galaxy SII. It's just stuck at 1%. Tried with another USB cable with no luck. Have you sorted out what the problem was? Tnx!
TWRP or CWM? Also, you could try the adb push command and push it to the internal storage and install it from there.
Sent from my Nexus 10 using XDA Premium 4 mobile app
Alternative to sideload...
anthony2424 said:
TWRP or CWM? Also, you could try the adb push command and push it to the internal storage and install it from there.
Click to expand...
Click to collapse
Solved!
Tried everything to get this sideload to work, without success. In the end, I flashed it through Heimdall. Not one of my favorite ways to flash but hey, phone works like a charm again :good:
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
All along ADB was working fine. Now when I enabled it, nothing is detected on the computer. The phone went entirely missing. If I turn it off, the phone comes back. Anyone encountered this?
With ADB turned off
- Phone works in PTP Mode to PC
- Phone works in MTP Mode to PC
- Phone works in MIDI to PC
With ADB turned on
- No phone device detected at all. So I am not even able to change to any of the ADB drivers
mobileman88 said:
All along ADB was working fine. Now when I enabled it, nothing is detected on the computer. The phone went entirely missing. If I turn it off, the phone comes back. Anyone encountered this?
With ADB turned off
- Phone works in PTP Mode to PC
- Phone works in MTP Mode to PC
- Phone works in MIDI to PC
With ADB turned on
- No phone device detected at all. So I am not even able to change to any of the ADB drivers
Click to expand...
Click to collapse
What do you mean by "ADB turned off" and "ADB turned on"?
Are you talking about USB Debug?
Sent from my interstellar 6P
CyberZeus1977 said:
What do you mean by "ADB turned off" and "ADB turned on"?
Are you talking about USB Debug?
Sent from my interstellar 6P
Click to expand...
Click to collapse
Yes, USB debug in development menu, even turning it on/off, revoke does not seem to make it work again. it just does not show up on my PC.
Further tests done.
Fastboot works.
Adb works in recovery mode when booted into TWRP 3.0.2-3.
Think I need a way to reset the ADB /usb debug settings within the phone as it looks more and more to be an issue from the phone rather than Windows (v7 x64 sp1)
mobileman88 said:
Further tests done.
Fastboot works.
Adb works in recovery mode when booted into TWRP 3.0.2-3.
Think I need a way to reset the ADB /usb debug settings within the phone as it looks more and more to be an issue from the phone rather than Windows (v7 x64 sp1)
Click to expand...
Click to collapse
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.
v12xke said:
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.
Click to expand...
Click to collapse
Shall give it a whirl. Previously it was incorrect driver issue years ago but everything has been working fine on all my Android devices till yesterday when I can't seem to ADB to my 6P. I have the latest USB drivers installed via Android SDK Manager.
v12xke said:
Not the way I read it. Sounds to me like the exact opposite.... a driver issue with your PC/OS, not the phone. In order for the phone to have adb/fastboot capabilities, the correct drivers need to be installed and actually working on the PC. Without going into detail, you could use a few different tools to REMOVE and install the correct PC drivers. Wug's NRT Toolkit has a very good step-by-step driver configuration guide with verification. I now just use the 15 second ADB installer here on XDA because it is minimalist, and just works. That being said, the NRT has a USB removal tool to rid your system of old USB entries that are likely causing your problem. Give it a whirl.
Click to expand...
Click to collapse
Still no go. There's no device at all where I need to change/delete/update driver if I turn on ADB USB mode. Phone is only seen by Windows Device Manager when I turn off USB debugging in developer menu. I still feel it might well be something in the developer menu causing this issue.
I am checking on the folder /data/misc/adb . Permissions is rwxr-s--- . What's the permissions you have for this folder?
Using USBDeview (trying to compare between 2 sets of 6P, both with the December 7.1.1 roms)
6P that works over ADB
Reported VID and PID is 18d1 / 4ee2
6P that does not work over ADB
Reported VID and PID is 18d1 and PID is 4ee1, 4ee5 and 4ee8 depending on which mode (PTP/MTP/MIDI).
Nothing gets reported to be connected at all when I used USBDeview while the 6P that does not connect over ADB USB has USB debugging turned on.
Problem fixed. No idea what was the cause. Hopefully it will help someone else who gets this down the road.
Steps performed
- Clean up SU
- Reboot
- No go
- Reboot to Recovery
- Reflash EFS backup
- Reboot
- No go
- Reboot to recovery
- Clear cache, clear dalvik
- Reboot
- No go
- Reboot to fastboot
- Reflash System, Vendor, Boot
- Reboot
- Works
- Reflash Magisk and PHH
- Still works
Puzzling.
Glad you got it fixed.
v12xke said:
Glad you got it fixed.
Click to expand...
Click to collapse
Yeah, would have done a full factory reset if all else fails since the hardware was indeed able to connect to my PC properly. Glad the various flashing worked out.