I was able to use the AOSP Stock without any issues, however I am not able to figure out how to root to install the CWM. The ADB command is not working from my computer. Any help is appreciated.
Thanks
If it's khanning88's ROM, try running the terminal commands as noted on the 1st post of this thread http://forum.xda-developers.com/showthread.php?t=1808017 and it should work.
I also had problems running adb because after enabling USB debugging, windows didn't recognize the adb connection. i uninstalled drivers, put my device into debugging mode and reconnected. All problems were solved.
Related
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.
I'm trying to root a Kindle Fire and I don't know why but I'm having alot of trouble getting ADB and drivers set up right on my laptop. I'm not sure which packages I need to install in SDK manager. When I try to use the adb command at a command prompt it says command not recognized and I'm thinking it's because I don't have the right packages installed or installed right.I didn't have to go through this when rooting a couple other phones I've done.
http://forum.xda-developers.com/showthread.php?t=1399889
Thanks so much for the link. I ran it and I'm having a hard time getting it to recognize the device. It said it installed the correct drivers but when I attempt the temp root it will not recognize the device, make sure device is plugged in and turned on.
With kindle unplugged Go into ur comps device manager and remove the kindle fire...then install drivers. Then plug it back in. I had same problem. Windows auto installed some generic driver when I first plugged it in before installing correct driver. If still not working try a diff usb port on computer. Hope that helps
I finally got it. Thanks very much. I finally had to switch computers for some reason to get it to work.
Hello everyone. I need a little help. I am trying to install a rom on my phone. USB debugging is enabled I am currently running the new 7.1 that just came out. ADB sees the phone what it is booted up. However it will not see the phone in bootloader. I have tried uninstalling and reinstalling the drivers, manually installing the drivers. Nothing seems to work. Any ideas?
Sidewind75 said:
Hello everyone. I need a little help. I am trying to install a rom on my phone. USB debugging is enabled I am currently running the new 7.1 that just came out. ADB sees the phone what it is booted up. However it will not see the phone in bootloader. I have tried uninstalling and reinstalling the drivers, manually installing the drivers. Nothing seems to work. Any ideas?
Click to expand...
Click to collapse
Adb doesn't work in bootloader, you have to use fastboot commands, such as "fastboot devices", etc.
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.
I have a big problem with the adb driver. It works perfectly to perfection when the phone is accessed both without usb debugging or with, adb devices detect the phone, and even fastboot when booting into the bootloader. The problem is that when I get into adb sideload from the original recovery my pc (windows 10 x64 build 1703) does not detect it, there is no way to make it work. I've tried changing a pc, cable, usb port, but always the same problem. I have installed and tried every type of driver, but there is no way to run it. I think the problem is oneplus5 stock recovery.
extremeinside said:
I have a big problem with the adb driver. It works perfectly to perfection when the phone is accessed both without usb debugging or with, adb devices detect the phone, and even fastboot when booting into the bootloader. The problem is that when I get into adb sideload from the original recovery my pc (windows 10 x64 build 1703) does not detect it, there is no way to make it work. I've tried changing a pc, cable, usb port, but always the same problem. I have installed and tried every type of driver, but there is no way to run it. I think the problem is oneplus5 stock recovery.
Click to expand...
Click to collapse
Is you're device connected with a USB 3.0/3.1 port maybe ? If so try a USB 2.0 port and install the latest ADB driver
Pieter20 said:
Is you're device connected with a USB 3.0/3.1 port maybe ? If so try a USB 2.0 port and install the latest ADB driver
Click to expand...
Click to collapse
I am also facing same problem...please help me
Does the stock recovery even have adb capabilities?