After you do all of above, look at your phone. It will have a popup message asking you to authorize your new connection.
Device unauthorized in Recovery mode
- Thread starter TomekUser
- Start date
OK, so I see that you have problem with adb unauthorized. In cmd or in terminal type adb devices. If you don't have installed adb drivers install it. If it says "unauthorized" that means that you don't have allowed to usb debugging. On your android device will pop up message to allow usb debugging.
Attachments
try this this might help you. https://forum.xda-developers.com/t/...t-and-no-revoke-usb-debugging-option.3693961/
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
12
after a bit of research (by which i mean google/trial/error) i now feel VERY dumb, but let me share my results with you - for what it’s worth, and maybe it is/was the same problem for you:No, I did not
apparently to sideload an OTA the device in recovery does NOT have to show "authorized"! (tried everything (creating new keys, checking the local key against the device-key manually, etc) and still it said "unauthorized".)
it turns out i tried to get the authorized-status on the screen where the android robot fell down and said "no command", so kinda "before" the actual recovery mode! get out of that screen (holding power button long, pressing vol-up short, letting go the power button) to get into the "menu" mode of recovery. still unauthorized, yes. then/there choose "sideload via adb" until the device says "waiting for input .." or something, and - TADAA - "adb devices" now tells you "sideload" next to the device id (instead of "unauthorized"). which is not only correct and "as expected", but actually works (for me) for sideloading an OTA!
mind blown, more or less. all the time i tried to get it "authorized" before checking if the actual OTA needs that anyway.3
Sir you have no clue how much it is helpful for everyone like me who were scratching their heads on this error.after a bit of research (by which i mean google/trial/error) i now feel VERY dumb, but let me share my results with you - for what it’s worth, and maybe it is/was the same problem for you:
apparently to sideload an OTA the device in recovery does NOT have to show "authorized"! (tried everything (creating new keys, checking the local key against the device-key manually, etc) and still it said "unauthorized".)
it turns out i tried to get the authorized-status on the screen where the android robot fell down and said "no command", so kinda "before" the actual recovery mode! get out of that screen (holding power button long, pressing vol-up short, letting go the power button) to get into the "menu" mode of recovery. still unauthorized, yes. then/there choose "sideload via adb" until the device says "waiting for input .." or something, and - TADAA - "adb devices" now tells you "sideload" next to the device id (instead of "unauthorized"). which is not only correct and "as expected", but actually works (for me) for sideloading an OTA!
mind blown, more or less. all the time i tried to get it "authorized" before checking if the actual OTA needs that anyway.
1I'm having the same issue...
you did what?
man, i miss the times where anyone could update his google phone without being a developer1
I don't have time to read whole thread to verify it. For sure you can find version matching your system version here:the one from here?
[Tutorial] Unlock Bootloader, get root and valid Safetynet
04/09/21 v2 Just install this Module via...
forum.xda-developers.com
[Stock/Rooted Boot Images] Pixel 4a [NOV 02]
We have stock factory boot images, I'm only...
forum.xda-developers.com
1
your a life saver. I was totally stuck in recovery for updating ota of pixel 6 pro.after a bit of research (by which i mean google/trial/error) i now feel VERY dumb, but let me share my results with you - for what it’s worth, and maybe it is/was the same problem for you:
apparently to sideload an OTA the device in recovery does NOT have to show "authorized"! (tried everything (creating new keys, checking the local key against the device-key manually, etc) and still it said "unauthorized".)
it turns out i tried to get the authorized-status on the screen where the android robot fell down and said "no command", so kinda "before" the actual recovery mode! get out of that screen (holding power button long, pressing vol-up short, letting go the power button) to get into the "menu" mode of recovery. still unauthorized, yes. then/there choose "sideload via adb" until the device says "waiting for input .." or something, and - TADAA - "adb devices" now tells you "sideload" next to the device id (instead of "unauthorized"). which is not only correct and "as expected", but actually works (for me) for sideloading an OTA!
mind blown, more or less. all the time i tried to get it "authorized" before checking if the actual OTA needs that anyway.
New posts
-
Question Is there a way to get 90 FPS on pubg mobile on my POCO X5 pro?- Latest: Abdul Kareem Seyal
-
-
