adb unauthorized, attempting to debloat - Sony Xperia XZ1 Compact Questions & Answers

no matter what I do, my xz1c remains unauthorized whenever I attempt to connect via adb. I've scoured the internet and tried everything. has anyone had this issue with their xz1c and resolved it? I'd like to debloat my phone, but cannot because I cannot fully use adb. any ideas?

bleggy said:
no matter what I do, my xz1c remains unauthorized whenever I attempt to connect via adb. I've scoured the internet and tried everything. has anyone had this issue with their xz1c and resolved it? I'd like to debloat my phone, but cannot because I cannot fully use adb. any ideas?
Click to expand...
Click to collapse
enable developer options - enable usb debug

1. Turn off usb debugging and developer options
2. Restart your phone
3. Turn on developer options and usb debugging
4. Plug in usb cable
5. Watch your phone screen carefully for an authorization dialog - and accept this. If you skip it, or cancel it by accident then you need repeat above steps.
6. ADB is now authorized.

I tried exactly this. Still "unauthorized".
Maybe current update of Android 9 blocks it.
Dean F said:
1. Turn off usb debugging and developer options
2. Restart your phone
3. Turn on developer options and usb debugging
4. Plug in usb cable
5. Watch your phone screen carefully for an authorization dialog - and accept this. If you skip it, or cancel it by accident then you need repeat above steps.
6. ADB is now authorized.
Click to expand...
Click to collapse

Related

[Q] My Galaxy S not booting after updating via kies

Today I updated my phone using kies. After the update was done the phone tried to boot but it couldn't get past the screen that says "Galaxy S GT-I9000".
So far I have tried to enter recovery/download modes, with no success.
Tried to connect the phone on my computer*, which recognized it (you could hear the "bleep" sound windows makes when a device is connected through usb.) but it didn't appear at Computer menu. Also kies recognized that there was phone connected but it keeps saying "Connecting" under Connected Devices tab.
*I'm using 64bit Windows 7 Ultimate
You'll need to either build or buy a Jig to get it into download mode and then you can reflash with Odin.
Did you ever use a custom rom on the phone? I assume not, but want to make sure.
If not, then you at least have warranty (don't you?) and can send it back for Samsung to revive your phone. Should you consider this, it would probably be wisest to not even try to repair your phone yourself.
However if you want to, here are three tips I found:
1) Connect your phone to your computer, open adb and type 'adb reboot download'. Your phone should reboot into download mode.
2) Originally posted here with a link to the mentioned ZIP: http://forum.xda-developers.com/showthread.php?t=728754 (look under "Manual Method")
For people that don't have the 3 button combo i made a script and a quick tutorial for doing it with ADB
ADB reboot recovery:
a) Download the easy reboot recovery.zip script and unzip it somewhere
b) In your phone's settings make sure USB Debugging is on (in settings -> applications -> development)
c) Connect phone with USB cable to pc
d) Wait until all the drivers are installed
e) Start reboot recovery.bat
f) The phone will now start in recovery
g) Follow step 7 of the normal tutorial
- If this does not work make sure USB debuging is enabled, kies is totally closed, the phone is connected and all the drivers are installed
3) This is from androidforums.com:
- Plug USB cable
- Remove battery
- Press AND HOLD volume down, power and menu key at the same time
- While pressing and holding the mentioned buttons, reinsert the battery (quite fiddly, I know)
- Let go of the buttons and you should go into Download mode.
Please tell me if anything helped.
Thanks for your help guys!
A.G. said:
1) Connect your phone to your computer, open adb and type 'adb reboot download'. Your phone should reboot into download mode.
Click to expand...
Click to collapse
Didn't work, adb gave me error "device not found", which would probably mean that the device isn't properly connected to my computer even though Windows did that bleep voice.
2) Originally posted here with a link to the mentioned ZIP: http://forum.xda-developers.com/showthread.php?t=728754 (look under "Manual Method")
For people that don't have the 3 button combo i made a script and a quick tutorial for doing it with ADB
ADB reboot recovery:
a) Download the easy reboot recovery.zip script and unzip it somewhere
b) In your phone's settings make sure USB Debugging is on (in settings -> applications -> development)
c) Connect phone with USB cable to pc
d) Wait until all the drivers are installed
e) Start reboot recovery.bat
f) The phone will now start in recovery
g) Follow step 7 of the normal tutorial
- If this does not work make sure USB debuging is enabled, kies is totally closed, the phone is connected and all the drivers are installed
Click to expand...
Click to collapse
This is something I didn't even try because I can't turn my phones USB debugging on. (can't access my settings )
3) This is from androidforums.com:
- Plug USB cable
- Remove battery
- Press AND HOLD volume down, power and menu key at the same time
- While pressing and holding the mentioned buttons, reinsert the battery (quite fiddly, I know)
- Let go of the buttons and you should go into Download mode.
Click to expand...
Click to collapse
Didn't work.
And no I have never used any custom ROMs on my phone. Probably taking my phone to the place I bought it from and see if I can get it fixed under warranty. Unfortunately that means I'm not going to have a phone to use for a while since I have no time to go there until sometime next week. If I can't get this thing fixed under warranty I'll probably just order a JIG and fix it that way.
If someone has more ideas please post them anyway, I want to fix this problem as fast as I can.
maybe a stupid question but you know how to get in dowload mode......
vol. down / home / power....
here are samsung drivers for your phone, uninstall everythin having to do with kies and install samsung drivers.
see if you can connect to ODIN now.
http://dl.dropbox.com/u/19506141/flash en drivers/SAMSUNG_USB_Driver_for_Mobile_Phones.exe

Help With ADT-1

Hi,
I am trying to enable casting with 3rd party apps on my adt-1. However, first I have to figure out how to connect it with adb. I lost the developer cable, and have been trying to debug wirelessly. Developer mode is enabled, and usb debugging is enabled.
I have tried rebooting the device into fastboot, and just normally start it, but nothing works.
I have tried "adb connect 10.1.1.67:4321" and "adb connect 10.1.1.67", but they always say unable to connect.
Is there somewhere I can buy a dev cable, or just get wireless debugging working?
RedyTedy said:
Hi,
I am trying to enable casting with 3rd party apps on my adt-1. However, first I have to figure out how to connect it with adb. I lost the developer cable, and have been trying to debug wirelessly. Developer mode is enabled, and usb debugging is enabled.
I have tried rebooting the device into fastboot, and just normally start it, but nothing works.
I have tried "adb connect 10.1.1.67:4321" and "adb connect 10.1.1.67", but they always say unable to connect.
Is there somewhere I can buy a dev cable, or just get wireless debugging working?
Click to expand...
Click to collapse
Google disabled ADB over wifi in the latest update.. If you re-enable it like with terminal emulator and USB keyboard you should be ok. I'll try to post how-to later. I think its in the build.prop
If anyone is still working with this device (I plan to attempt to build LOS 15.1 soon), I just got mine without a developer cable. I'm not sure what command death2all110 is referring to in a terminal but what I did was transfer over a chinese root apk, root it with a USB mouse (sideways) and install TWRP with dd. Note mine came bootloader unlocked, I don't know if they all come that way or if the previous owner did.
(Extra sidenote: Developer cable/charing port appears to be EC U6 but I haven't tested the pinout.)
fyi, they were bootloader unlocked from the factory. pin-out for the connector has been found. check out the adt-1 dev community on g+ for more detail.
I also lost my developer cable and bricked the device recently. The EC U6 cable is nir working, as there is no external power and dosent power on. Anyway anyone can help?.

[HELP] Problems trying to flash to stock, to flash to Android N

So I am currently rooted on a Motorla Nexus 6 in Android 5.1.1, I started up the Nexus Root Toolkit and when it finishes downloading stock Android 60.1 to restore my device ready for Android N it sends the adb reboot bootloader command but my device then says in the bootloader menu "Connect USB Data Cable"
Since I cannot post the image link of what the toolkit says then I will just write it below...
"FASTBOOT device was not found
STEP #1: Connect your device via USB:
- Utilize the OEM USB cable if available
- Try an alternative USB port.
STEP #2: Manually Boot your device into bootloader mode:
- Power your device down completely:
- Press and hold the volume down button, them press and hold the power button t the same time until the phone turns on. You'll see the word 'start' with an arrow around it/
STEP #3: Install drivers:
- Utilize the 'initial setup' if you not done so already.
- USB debugging is NOT required for connectivity in bootloader mode.
- Just follow the the instructions in the guide for configuring your device in bootloader mode.
- For example: if you are using driver solution #3, start on step 7.
Alternatively you may just need to recheck connection.
Press 'OK' to recheck device connectivity.
Press 'Cancel' to exit this script"
If anyone has any info on how to get around or resolve this issue as I cannot proceed with the stock flash unless the Fastboot connectivity is working, then that would be great
(if it helps I already have Android Studio installed with all its components)
Lucas_Stone said:
So I am currently rooted on a Motorla Nexus 6 in Android 5.1.1, I started up the Nexus Root Toolkit and when it finishes downloading stock Android 60.1 to restore my device ready for Android N it sends the adb reboot bootloader command but my device then says in the bootloader menu "Connect USB Data Cable"
Since I cannot post the image link of what the toolkit says then I will just write it below...
"FASTBOOT device was not found
STEP #1: Connect your device via USB:
- Utilize the OEM USB cable if available
- Try an alternative USB port.
STEP #2: Manually Boot your device into bootloader mode:
- Power your device down completely:
- Press and hold the volume down button, them press and hold the power button t the same time until the phone turns on. You'll see the word 'start' with an arrow around it/
STEP #3: Install drivers:
- Utilize the 'initial setup' if you not done so already.
- USB debugging is NOT required for connectivity in bootloader mode.
- Just follow the the instructions in the guide for configuring your device in bootloader mode.
- For example: if you are using driver solution #3, start on step 7.
Alternatively you may just need to recheck connection.
Press 'OK' to recheck device connectivity.
Press 'Cancel' to exit this script"
If anyone has any info on how to get around or resolve this issue as I cannot proceed with the stock flash unless the Fastboot connectivity is working, then that would be great
(if it helps I already have Android Studio installed with all its components)
Click to expand...
Click to collapse
Make sure you have develops options unlocked and usb debugging enabled.. Then unplug cord and plug it back in.
kwdan said:
Make sure you have develops options unlocked and usb debugging enabled.. Then unplug cord and plug it back in.
Click to expand...
Click to collapse
Got the same error again (I always have USB Debugging on)
Lucas_Stone said:
Got the same error again (I always have USB Debugging on)
Click to expand...
Click to collapse
Try a different port on the computer
kwdan said:
Try a different port on the computer
Click to expand...
Click to collapse
Still the same man, my Laptop has the Google Nexus ADB drivers installed but for some reason the Root Toolkit does not detect Fastboot in my phone
Lucas_Stone said:
Still the same man, my Laptop has the Google Nexus ADB drivers installed but for some reason the Root Toolkit does not detect Fastboot in my phone
Click to expand...
Click to collapse
did you install adb and fastboot onto your computer? it doesnt matter if you have the driver installed if you dont have the actual program installed onto your computer. and anyways, learn to do it right instead of using a toolkit, its very easy.
simms22 said:
did you install adb and fastboot onto your computer? it doesnt matter if you have the driver installed if you dont have the actual program installed onto your computer. and anyways, learn to do it right instead of using a toolkit, its very easy.
Click to expand...
Click to collapse
All sorted now I think lol, I will close this thread when I finish. if it fails horribly then I will let you know (p.s I use the cmd most the time it's just I use the Toolkit to download and install stock)
Lucas_Stone said:
All sorted now I think lol, I will close this thread when I finish. if it fails horribly then I will let you know (p.s I use the cmd most the time it's just I use the Toolkit to download and install stock)
Click to expand...
Click to collapse
please dont close the thread, people always have issues, maybe someone will read this thread and it will help them.
and about toolkits, i dont recommend using them, but feel free to. its just many dont take the time to learn to do it the "right" way. but if you do know it, a toolkit is alright usually.
simms22 said:
please dont close the thread, people always have issues, maybe someone will read this thread and it will help them.
and about toolkits, i dont recommend using them, but feel free to. its just many dont take the time to learn to do it the "right" way. but if you do know it, a toolkit is alright usually.
Click to expand...
Click to collapse
Okay, I will keep it open and also everything is fine now, I am now on Android N preview (had it for 5 mins and I love it)

Galaxy Note5 N910T won't keep USB debugging checked after reboot

I've done a lot of googling so far, and I haven't seen anyone having this problem yet.
This phone is not yet rooted, and is still running the stock rom and recovery. I haven't been able to get to first base and unlock the bootloader with it because once I boot into Odin/download/fastboot mode, ADB can't see the device anymore.
Although I can turn USB debugging on and verify that ADB can see and list my device, if I reboot, and return to my Developer options menu, it will not still be checked. The problem, I believe, that's creating is that rebooting into Odin mode means that ADB can no longer see my device, because USB debugging has already been turned off. I don't think an app is doing this, because booting into safe mode, turning on USB debugging, and then rebooting into safemode again yields the same result: USB debugging has still been turned off. From the command prompt issuing "adb reboot fastboot" just yields a reboot back to the normal home screen.
EDIT: Upon further inquiry, do I even need USB debugging to get TWRP installed? According to:
http://www.cyanogenmods.org/forums/topic/install-twrp-recovery-samsung-android-using-odin/
they make no mention of USB debugging, only OEM Unlock which does not appear in the Developer Options for my phone...

trying to get OTA of 20X from 20Q

formerly rooted H811. I unrooted with supersu and attempted to relock the bootloader. But It didn't take. It appears to be in some in between galaxy.
I get into fastboot, but "fastboot devices" comes up empty.
Would like to lock to update to 20X. No PC, only Mac.
LG Bridge sees USB, but not phone.
Help appreciated.
You do realize locking the bootloader will perform factory reset and wipe your data. Are you trying fastboot through MAC, not sure how it is different from PC so if that is causing the issue can't help much.
Is usb debugging enabled, and you have given permission in the pop-up that pops up on phone screen when you connect it to MAC/Computer the very first time? It is possible you missed that permission pop-up the first time and now permission is denied permanently. You may wanna uninstall and reinstall LG driver/device, connect phone again, and look for that permission pop-up on phone screen and allow it. Try connecting usb cable in different usb port too, that might make the pop-up appear again. Also, remember if bootloader is altered or you got custom recovery, phone will possibly soft brick and you will need to use LG Bridge or LG UP with phone in download mode to reflash kdz. Hope this helps.
Edit: For the permission pop-up to show, the phone needs to be turned on, be in mtp mode, and usb debugging to be enabled. Then once you have given permission, you use adb command to reboot into bootloader or i think with phone off, hold the volume down button while you connect to usb cable and not let go of the volume down button till phone is in fastboot menu.

Categories

Resources