… but it worked before
So I got a new phone in and thought that maybe I could use an adb backup from my old phone to get all the settings and stuff over. I have 2 different backups, one was done with
-all, one was done with
-apk -shared -all -system (I read that apparently “all” is not actually everything and those 4 should catch the rest).
Anyway, when the new phone came in it worked fine after the initial setup (and swapping out a dodgy USB cable ), i.e. it was seen by ADB as a device to use. So I went ahead and
adb restore 20191116-apk-shared-all-system.ab, entered the password on the phone and let it run, didn’t look at it until hours later because I thought it would just do its thing.
Well, turns out it wasn’t doing its thing. I.e. no settings carried over. I restarted the phone because I thought it would need that to overwrite all the stuff, but nothing happened. And now I’m getting this:
[[email protected] ~]$ adb devices List of devices attached * daemon not running; starting now at tcp:5037 * daemon started successfully ???????????? no permissions; see [http://developer.android.com/tools/device.html]
So I restarted the phone, the PC, reconnected multiple times, even went ahead and did a factory reset on the phone and I’m still getting the same thing. Unfortunately the linked help page doesn’t help me much, or I don’t know what I’m looking for.
But, obviously, it worked before.
From what I can find on the internet the universal solution seems to be "just
sudo adb", but I can’t believe that should be the only solution since - again - it worked before.
Have I bricked something? Any ideas?