Enabling USB Debugging through ADB? Im Stuck at Black Screen W/ "Unauthorized" in ADB
So I've had a few problems lately, all leading up to my Kindle being Bricked at Black screen after Recovery reboot attempt.
Using ADB, My Device is showing up, however I am getting "Unauthorized" and cannot access any root functions, or push commands to the Kindle.
I'm trying to do a Reset/Brick Fix by flashing the OTA update and start from scratch(Stock), but have no way of doing so via ADB because I can't push anything to my once rooted device, now saying it's UnAuthorized.
Is there an ADB command to either Root this thing, or even just to enable debugging mode via usb without actually going into the system? My System appears to be missing, or not running for whatever reason.
Is there ANYTHING I can do to get this thing up and running again? ADB Is Recognizing the device, but "ADB Shell" is giving me the same Unauthorized error.
Mcfinnipoop said:
So I've had a few problems lately, all leading up to my Kindle being Bricked at Black screen after Recovery reboot attempt.
Using ADB, My Device is showing up, however I am getting "Unauthorized" and cannot access any root functions, or push commands to the Kindle.
I'm trying to do a Reset/Brick Fix by flashing the OTA update and start from scratch(Stock), but have no way of doing so via ADB because I can't push anything to my once rooted device, now saying it's UnAuthorized.
Is there an ADB command to either Root this thing, or even just to enable debugging mode via usb without actually going into the system? My System appears to be missing, or not running for whatever reason.
Is there ANYTHING I can do to get this thing up and running again? ADB Is Recognizing the device, but "ADB Shell" is giving me the same Unauthorized error.
Click to expand...
Click to collapse
Same problem - can't boot into the os so can't enable USB debugging to get to adb access.
adb devices returns the SN with "unauthorized"
macstibs said:
Same problem - can't boot into the os so can't enable USB debugging to get to adb access.
adb devices returns the SN with "unauthorized"
Click to expand...
Click to collapse
No recovery if bootloader remains locked.
Davey126 said:
No recovery if bootloader remains locked.
Click to expand...
Click to collapse
Still a pretty nice tablet - sucks that there's seemingly no fix to this (especially after I paid $100 for a new lcd)...
Related
Should I be able to find my adb device while my phone is only booting to HBOOT 0.93.0001?
Been stuck on this for days...and it's killing me!
PS. When I plug my phone in to
PC it says "Android ADB interface installed" "Ready to use"
But when I cmd the adb to find devices "adb devices" it shows blank
P.S. Phone: HTC Desire
Unrooted
S-ON
Unable to boot, can only get to HBOOT.(so cant turn debugging on)
Trying to get a goldcard to flash a new rom and see if i can unbrick
Reason for unable to boot is - It had been rebooting itself for weeks, slowly getting worse, until now, when I cant get it booted at all.
budron said:
Should I be able to find my adb device while my phone is only booting to HBOOT 0.93.0001?
Been stuck on this for days...and it's killing me!
PS. When I plug my phone in to
PC it says "Android ADB interface installed" "Ready to use"
But when I cmd the adb to find devices "adb devices" it shows blank
P.S. Phone: HTC Desire
Unrooted
S-ON
Unable to boot, can only get to HBOOT.(so cant turn debugging on)
Trying to get a goldcard to flash a new rom and see if i can unbrick
Reason for unable to boot is - It had been rebooting itself for weeks, slowly getting worse, until now, when I cant get it booted at all.
Click to expand...
Click to collapse
adb won't work when you are in bootloader (It won't work until Linux is up). "fastboot" will work over USB in bootloader->Fastboot.
I believe RUU will work on fastboot mode.
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
anyone knows?
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
Yes, you can access ADB while in a bootloop.
Theonew said:
Yes, you can access ADB while in a bootloop.
Click to expand...
Click to collapse
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
runingwild said:
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
Click to expand...
Click to collapse
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
yes you can I have this before and it's working
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again
Click to expand...
Click to collapse
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
mustafah822000 said:
yes you can I have this before and it's working
Click to expand...
Click to collapse
that can be helpful for me. How did you do it?? was it in bootloop too? not rooted?
Theonew said:
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
Click to expand...
Click to collapse
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
Click to expand...
Click to collapse
Theonew said:
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
Click to expand...
Click to collapse
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
runingwild said:
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
Click to expand...
Click to collapse
Its a driver issue. Check device manager for your "unknown device," then associate adb drivers with it.
you can use adb once the kernel has loaded so root or any other factor shouldn't affect it
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
runingwild said:
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
Click to expand...
Click to collapse
if u are bale to get into fastboot flash a stock ruu and it should work fine
well, what if i cannot access recovery mode or fastboot menu as you have said so. my HTC desire 310 is having bootloop and cant enter recovery. HELP PLEASE!!
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Tommyboy77 said:
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Click to expand...
Click to collapse
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
es0tericcha0s said:
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
Click to expand...
Click to collapse
adb devces does not work in clockwork mod either.....what is the easiest way to get this custom rom sent to my internal sd card if the phone wont boot up and os is wiped off the phone? it is an htc one...
adb should work in CWM... You might have to manually load the driver. Even if every driver works when the phone is booted and all, Windows can still have issues finding the right one in recovery. Check in your device manager. If that doesn't work, then you'll have to see if your recovery supports USB OTG and see if you can load like that. If none of that works, you'll have to reload the OS via RUU and start over with root/recovery/etc.
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
C13v3r0n3 said:
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Neither of those things are options for the OP. He can't boot, so he can't mount USB (mounting USB in recovery hasn't worked for most phones since JB where most phones don't support USB mount - only MTP) and he can't sideload because he hasn't been able to get ADB working.
His options now are:
Find out why the adb driver isn't loading so he can just adb commands to push the file or sideload
USB OTG
Return to stock via RUU
I'm in the middle of restoring an HTC One M7 Sprint phone to stock from CM11. Since I don't have S-Off, I tried using the minimal package from HTC1Guru, the Reset Download. I have TWRP Recovery, so I copied the Reset Download utility to the phone and ran it. That went ok, except the screen was unresponsive and I had to use a mouse. So, I tried to get an OTA (after relocking the bootloader) to get all current stock. A few minutes into the install of the OTA, it just locked up and there I sat, with the White HTC screen and nothing happening.
So I've tried several things. But a side effect of this condition is I could NOT run ADB. Now I do have a USB connection and it works; In Fastboot if I issue the FASTBOOT DEVICES command I get the device id back. But I could not get ADB to work at all, even though the cable is connected and all that (since Fastboot works). Oh, and ADB worked before this locked up. ADB Devices returns no devices. BUT (it gets weirder) I went back to Fastboot and flashed TWRP REcovery again, and if I enter RECOVERY, I can issue ADB Commands from recovery fine. But outside of recovery, I can't. And, more importantly, PROGRAMS CAN'T DETECT ADB. I tried Rumrunner's program to turn S-OFF, and I tried the ARUWizard RUU utility from Viperboy, and both said to check the USB cable, that ADB could not be found. But I went right to it, booted recovery, and there was ADB!
So, what could cause ADB to be present if I'm booted to recovery, but not from bootloader screen? since right now I can boot to REcovery but not to the ROM, I'm totally dead in the water.
Steve
Steve Thomas said:
So, what could cause ADB to be present if I'm booted to recovery, but not from bootloader screen?
Click to expand...
Click to collapse
ADB never works in the bootloader (that's why you have fastboot to talk to it). ADB talks to the ADB daemon, which is running when a ROM or a recovery is booted.
_that said:
ADB never works in the bootloader (that's why you have fastboot to talk to it). ADB talks to the ADB daemon, which is running when a ROM or a recovery is booted.
Click to expand...
Click to collapse
I thought I must be doing something wrong running ADB with the phone in Recovery since Rumrunner keeps failing with "No ADB Connection". But maybe it's something else.
Thanks!
I have Samsung Galaxy Tab S2 that I attempted to root earlier today. I used Odin and CF auto root method. Everything appeared to go fine, until it restarted itself after it was done. When it booted back up, the WiFi was not working. When I turn it on, it is simply stuck on "Turning on...." and nothing happens.
Problem 2: When I connect the tablet to a computer via USB cable, it does not recognize it. I'll hear a chime, so it detects it, but it does not show up in the file explorer. The tablet is set for a MTP USB configuration.
I tried a factory reset, but that did nothing.
I'm not sure what to do now. I do have a micro SD card, so I'm able to move it back and forth from the tablet to my PC to install APKs and other files. I'd like to try flashing a custom ROM to see if that fixes it, but now I'm not rooted. I used the SD card to install a couple of the one click root apps, but they were either unsuccessful, or require an internet connection to use.
I don't know if it's possible to actually install a custom ROM on a device that doesn't have internet access and can't use a USB cable.
If anyone has suggestions as to either of my problems, I'd love to hear it, because as of now I can't do anything with my tablet.
You can try to:
wipe data/cache from recovery and reboot it again to see if the wifi error still exists, or you can flash it again.
You can get and use adb/fastboot, if you haven't already, and check if fastboot (execute fastboot devices in cmd) recognizes your device after the chime sound. If you're lucky and your device is displayed, you can flash it again. All the best!
daphr said:
You can try to:
wipe data/cache from recovery and reboot it again to see if the wifi error still exists, or you can flash it again.
You can get and use adb/fastboot, if you haven't already, and check if fastboot (execute fastboot devices in cmd) recognizes your device after the chime sound. If you're lucky and your device is displayed, you can flash it again. All the best!
Click to expand...
Click to collapse
Thanks. Executing "fastboot devices" returns an empty list, however "ADB devices" returns some sort of serial number with "offline" next to it.
edit: I've been running adb kill-server and adb-start server commands, followed by adb devices, and that will switch the device status from "offline" to "unauthorized". I'm not sure how to fix that. I navigated to my .android folder on my PC and deleted the adbkey file but that didn't help.
In developer settings Enable USB debugging, revoke current USB debug authorizations and allow your PC's fingerprint. You can also enable OEM unlock in case you plan to play with the bootloader and custom ROMs.
Next in cmd after plugging the device in, check if it gets detected: adb devices
If you get the list you've mentioned, execute: adb reboot bootloader
This should boot your device into the fastboot mode where you have full access to your phone, so be careful what you're doing.
If you need more info on fastboot and adb, check out the forums.
Good luck!
daphr said:
In developer settings Enable USB debugging, revoke current USB debug authorizations and allow your PC's fingerprint. You can also enable OEM unlock in case you plan to play with the bootloader and custom ROMs.
Next in cmd after plugging the device in, check if it gets detected: adb devices
If you get the list you've mentioned, execute: adb reboot bootloader
This should boot your device into the fastboot mode where you have full access to your phone, so be careful what you're doing.
If you need more info on fastboot and adb, check out the forums.
Good luck!
Click to expand...
Click to collapse
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
febtober said:
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
Click to expand...
Click to collapse
Have you been asked for a new computer ID to accept after revoking old ones and plugging the device in again?
As long as you don't add new fingerprint of your computer to the device, your device will be unauthorized.
febtober said:
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
Click to expand...
Click to collapse
You need to restock your tablet via odin (to put modem back aka Wifi)
After you restock Install Twrp and install magisk to root, instead of cf-root like you did (this will not breaking the safety net or knox even the modem)
(Note:before install magisk backup your "BOOT" via TWRP)