[Replicant] Unauthorized on Recovery
amuza
amuza at riseup.net
Sun May 31 23:26:00 UTC 2020
Denis 'GNUtoo' Carikli:
> On Sun, 31 May 2020 15:29:00 +0000
> amuza <amuza at riseup.net> wrote:
>
>> Hello!
> Hi,
>>> I would like to backup my Replicant. According to what I have read, I
>> should do that from Recovery, but I don't manage to adb in Recovery.
>>
>> I think I have to mount /system
>>
>> So, I go to Recovery and do:
>>
>> Advanced -> Mount /system
>>
>> I don't see any message saying that it has been successfully mounted,
>> but probably that is ok, I don't know.
>>
>> "adb devices" lists my device but says "unauthorized".
>>
>> "adb shell" gives me:
>>
>> error: device unauthorized.
>> This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that
>> seems wrong.
>> Otherwise check for a confirmation dialog on your device.
>>
>> I get the same results when adding the sudo command.
>>
>> I have also tried to troubleshoot by:
>>
>> rm -Rf ~/.android
> .android has things like adbkey and adbkey.pub, so after that you
> probably don't have the authorized key anymore.
>
Thank you Denis.
The problem was already there when I tried that for troubleshooting
purposes. But I was not correct, I did not delete that directory, I just
renamed it. It recreated another one automatically. I saw it did not
solve anything, so I restored the original directory, just in case.
So I guess that is not really the problem.
But to be 100% sure, if you know how to verify there is no problem with
those adbkey and adbkey.pub, I'd be happy to know it.
(Please remember that I only have the problem when I am in Recovery,
when the OS is running I can adb it without a problem.)
>> db kill-server
>> sudo adb start-server
>>
>> I have then allowed USB debugging permissions and checked the box that
>> says "Always allow from this computer".
>>
>> But all that made no difference, when going into Recovery I keep being
>> unauthorized : /
>>
>> Any suggestion?
> If you can boot Replicant, try to re-check "Always allow from this
> computer".
Yes, I did that and I am doing it in my tests, thanks.
>
> I'm also not sure if setting root access to "adb" or "applications and
> abd" is required or not to get root access in the recovery.
>
I have tested it with root access for "adb" and "apps" and without. No
difference.
When doing some tests, I think once I get a different result. When
running "adb devices" I got the device listed (as always) but that time
saying "no permissions" instead of "unauthorized". (Talking always when
in Recovery, no problem when the OS is running)
I kept testing things and at one moment it went back to be listed as
"unauthorized"... sorry for not being very accurate here.
When searching for a solution I found this
https://www.janosgyerik.com/adding-udev-rules-for-usb-debugging-android-devices/
I followed it and created my udev rule for my Replicant device. It made
no difference : (
Any other suggestion I could try?
Is this something normal?
Do you know more cases of users being unauthorized only in Recovery?
I guess it must be something easy I am not paying attention to, but
can't find it!
> Denis.
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osuosl.org/pipermail/replicant/attachments/20200531/8cb4289a/attachment.asc>
More information about the Replicant
mailing list