i'm trying to flash CM12, but every adb command errors out and my devices is listed as "unauthorized" when i run adb devices. i understand that normally i would restart in Android and allow USB debugging. but.. i accidentally wiped my device while i was in Recovery mode.
According to the CM docs on secure USB debugging:
if you see error: device unauthorized while attempting to use adb in recovery, restart to Android and authorize the connection.
Click to expand...
Click to collapse
but since I wiped my device, I am stuck in recovery with USB debugging disabled. i tried booting from sd, but it just errors out . so i'm stuck. anyone have any advice?
Related
I unlocked, and rooted my nexus 7 using the Nexus Root Toolkit.
Everything was good until, after a few days, I tried turning on my device but got stuck on the "X" loading screen. After googling for a bit, I figured a factory reset would do the trick. I tried to factory reset the device in TWRP, but was confused by the two buttons and accidentally wiped everything (in adv wipe with everything checked).
Now the next problem is that I don't have USB debugging enabled (I recall turning it off for some reason). When i run "adb devices", nothing comes up and so i can't push anything to the device (and everything is wiped). Is there a command i can run, or file i can edit while in TWRP recovery mode to enable it? It seems i can't do anything without it enabled.
I did the same thing. This will help you get back to square one.
http://forum.xda-developers.com/showthread.php?t=2382618
Sent from my Nexus 7 using Tapatalk 2
poootythang said:
Now the next problem is that I don't have USB debugging enabled (I recall turning it off for some reason). When i run "adb devices", nothing comes up and so i can't push anything to the device (and everything is wiped). Is there a command i can run, or file i can edit while in TWRP recovery mode to enable it? It seems i can't do anything without it enabled.
Click to expand...
Click to collapse
Regarding how to most quickly get you back up and running, it is probably easier to just flash the stock images as mentioned above.
Regarding your adb issue, if you can boot into TWRP and are using a known good USB 2.0 port (sometimes 3.0 gives issues), then adb should already be running (ie what usb debugging enables is running)
You probably don't have drivers installed for adb running under recovery. The regular drivers don't work.
See this post:
http://forum.xda-developers.com/showthread.php?t=2391236
The ADB drivers from SDK is only for when in Bootloader and booted into ROM for needing USB Debugging. This is the driver you need in addition to what you have you've already installed to use ADB while in recovery otherwise you will see "Flo" under Unknown Devices in your computer Device Manager.
Thank you everyone. The new drivers and restore guide worked perfectly.
adb devices returns no listed devices,
One_X_All-In-One_Kit says device not found.
Tested with different drivers (HTC drivers from One_X_All-In-One_Kit,and Universal_Naked_Driver_0.72), phone is detected by Windows, in bootloader it says fastboot usb, but I can't do sh*t And it used to work just fine a month ago.
Tested on 2 different computers with different USB cables... (Win 7 and 8 run as admin).
One strange thing is that I remember updating TWRP to 2.6.0.0 and now it's 2.4.something. What happened, what can I do?
Just want to update boot.img so I can install CM10.2, currently on CM10.1.
No ideas?
I can connect adb over WiFi, but ofcourse it says offline.
USB debugging ticked?
A
Adb doesn't work in the bootloader. Only fastboot commands
Iceax123 said:
USB debugging ticked?
A
Click to expand...
Click to collapse
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
kbal said:
Yes, I did this a few times before, I know how to do it. But now, there is no way to flash boot.img from PC.
I reboot phone in to Bootloader, connect it to PC (phone says fastboot USB), I can see ADB device in device manager, if I 'adb device' in Command Prompt there are none (except when I connect it with WiFi adb).
Click to expand...
Click to collapse
adb does not work in bootloader...
of that doesnt help, try another USB port... I know this sounds ridiculous but trust me, it helped me once before.
Well, i managed to get my phone be detected in adb and fastboot, by manually installing Nexus adb drivers (have a disk option).
Drivers that used to work- HTC drivers, won't do anymore. Don't know why.
Hey all,
I've been rooting phones for a little bit, so when I got my Nexus 7 a couple weeks ago and found that it was as simple as "fastboot oem unlock", I was thrilled. However, it ended up not being that simple, of course.
At first I couldn't get the device to show up for ADB or fastboot at all, even though Windows recognized the device. I downloaded the zip file of the drivers from Google, no luck. Downloaded a new version of the Android SDK, and used the adb/fastboot from it, and then ADB was able to see the N7 and was able to reboot it into the bootloader. However, once in the bootloader, it stops recognizing that the N7 is connected again. Trying "fastboot oem unlock" just causes the program to display <waiting for device> indefinitely.
So that's where I'm stuck now, I haven't been able to find any concrete details on this that are for the N7 2013 (pretty much everything I've found has either not been helpful or has been related to the original N7). Anyone able to help from here? Thanks!
Do u have USB debugging enabled in developer settings? Try turning your USB computer connection to PTP from MTP if you haven't already in storage settings. Then a pop-up will come on your n7 asking to approve your computer to see it. Tell it yes
>^.^< Sent From Meow HTC One
DowntownJeffBrown said:
Do u have USB debugging enabled in developer settings? Try turning your USB computer connection to PTP from MTP if you haven't already in storage settings. Then a pop-up will come on your n7 asking to approve your computer to see it. Tell it yes
>^.^< Sent From Meow HTC One
Click to expand...
Click to collapse
Thanks for the suggestions. Alas, I tried these things. The problem exists now when I'm in the bootloader, which is where fastboot won't recognize that the device is attached.
tigerxchaos said:
Thanks for the suggestions. Alas, I tried these things. The problem exists now when I'm in the bootloader, which is where fastboot won't recognize that the device is attached.
Click to expand...
Click to collapse
When you have the device connected to your computer when it's at the Bootloader screen, what does Device Manager show on your computer? Does it recognize the tablet but doesn't know what it is? You may need to install the drivers when you have the device in the Bootloader menu. I use the Google USB Driver (which you can download in the SDK Manager), right click on the device in Device Manager, select "Update Driver Software", "Browse my computer for driver software", "Let me pick from a list of device drivers on my computer", then browse the list. It may be listed under Android Device, Google...just look down the list, then select the appropriate driver. I believe from there you can select "Android Bootloader Interface", and that should let fastboot commands work.
You may need to reboot the computer.
Make sure you are using the usb cable that came from asus.
Thanks for the help. I tried the process again on a different computer, and eventually got it to work. I was able to unlock bootloader and flash TWRP 2.6.3.0. However, I was only able to mount System, Cache, and USB-OTG as partitions in TWRP, so I couldn't figure out where to drop the SuperSU binary .zip file. I tried rebooting, and (this may have been a mistake) installed the TWRP SU binaries on the way out. Now the device is stuck in a bootloop. Not sure if it was related to the SU binaries or the fact that I couldn't load any sort of data partition. Any thoughts?
EDIT: Apparently the root instructions don't make it clear that you will lock your data partition if you don't boot the device after unlocking the bootloader. I went straight into TWRP from the bootloader after unlocking it, and got a password request. Hit "Cancel" and it let me into TWRP, but factory reset failed. I had to wipe data, wipe cache, then reboot, then do a factory reset and now I'm back in.
hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Put in fastboot mode, connect to computer and manually select fastboot interface from the device manager "install device/update driver manually" box. That worked for me.
JusTeN_ said:
hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Click to expand...
Click to collapse
Its fine just search for fastboot devices and see if your device comes up. Mine was showing the same thing and i continued and it worked
"""""""""""""""""""""""""''Help Help Help Help"""""""""""""""""'''''''''’'''''
I am having Moto M XT1663 phone I bought was already boot unlocked so i decided to Install recovery and Root so that I can enjoy rooted things.
The problem is that the phone not detectable in Fastboot mode phone can only be detected in ADB mode. When I write command "ADB devices" it shows my device.
If I want to reboot into boat loader and use fastboot devices after hitting enter it shows nothing and no error appears.
I google about my phone's drivers that should be installed in order to use fastboot mode. So I installed them but no success.
One thing I notice that In fast boot mode my laptop giveys USB detection error and also tells me ADB interface failed.
Tried below mentioned things in order to get my phone detected in fastboot mode:
1) tried 3 different laptops(my Nexus 6p is detectable on all three laptops).
2) changed USB cable.
3) FDR using recovery.
EDIT: Problem solve by install Mediatek driver from windows update