I cannot run my device.
When I plug it to the charger, It boot loop forever.
I attached it to my laptop and same loop happens.
I tried to list devices or push fbmode file but no luck.
I tired to issue the following command repeatedly:
Code:
adb push fbmode /data/local/tmp
most of the time i get:
Code:
error: device '(null)' not found
but sometimes i get:
Code:
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 tired Kindle Unbrick UtilityV1.1 and repeatedly pressed the buttons so I can issue any command before the device loops and restarts.
But still no use at all.
My device is not ROOTed.
My Model is: PM98VM
Any help is appreciated.
Related
I am writing a cmd script for my fire tv and am looking to see if there is a way for me to connect with the following
Code:
adb connect 192.168.1.5:5555
(the above command works)
but loop it if the device fails to connect, or wait/ retry until connect is successful... any help? sorry if explanation is not good
what my end goal is is to have a script running in the background that can start kodi when my fire tv stick starts
what I have that i can manually insert and it works to show my progress thus far, im a noob with this stuff BTW
Code:
adb kill-server
adb start-server
adb connect 192.168.1.5:5555
adb shell am force-stop org.xbmc.kodi
adb shell monkey -p org.xbmc.kodi 1
I could also use any tips on a way to check if kodi is running / or fireTV is on and pause / loop the code, any advice?
Hi guys,
I cant use adb as it says my device is unauthorized. Treid 2 different PCs with Win 10,8 and Linux (Arch)
The issue is here:
Code:
# adb usb
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
It is not the pub key. Other things I tried deleting /data/adb/ but the folder is empty. Tried mtp, ptp, midi, charge only etc. I am missing the revoke permission option in the developer options. So no idea what to do
I know this is an old thread, but here's a potential solution (if you're rooted)
[SOLVED] ADB 'unauthorized', no RSA prompt, and no 'Revoke USB debugging' option
i am on macosx and installed android studio
the adb and fastboot and driver (kext) for android are broken in such the following ways
1. adb
it is not detecting even virtual machine , tried all the version
when i run ./adb usb or ./adb devices for the first time
it is not showing thing like
Dameon starting up bla bla
and run quietly and freezes
sudo ./adb devices
List of devices attached
*** it freezes i.e keep waiting
sudo ./adb usb
** it freezes and waiting
even
sudo ./adb kill-server
**8 it is freezing and waiting
sudo ./adb start-server
** it is waiting
i have given it all permission
chmod 777 adb
platform-tools Prodesign$ sudo ./adb start-server ** it is waiting
2. fastboot
./fastboot-mac devices
ERROR: could not get pipe properties
HQ65XBS32030 fastboot
fastboot oem get_identifier_token
ERROR: could not get pipe properties
... // i tired a htc android
not a single android in adb pr fastboot is working correctly
there is not adb_usb.ini file in sdk folder of adb also new adb does not uses adb_usb.ini file
also i added that file and device if like 0x1368 even though it is not working
Please help
After "adb shell" successfully finding the device, every "sm" command results in "Killed" response - why? It goes something like this:
Code:
1|a3y17lte:/ $ sm list-disks
Killed
I tried executing "su" command, it succeeded, but didn't change anything - still getting "Killed" responses
+++
I'm having that same problem here, have you flash the .zip from app sd to internal?
Well, I screwed up.
Spoiler: Terminal
PS D:\platform-tools> adb sideload D:\platform-tools\oriole-ota-tp1a.220624.021-a13fd9d0.zip
serving: 'D:\platform-tools\oriole-ota-tp1a.220624.021-a13fd9d0.zip' (~18%)
PS D:\platform-tools> adb devices
List of devices attached
1C151FDF600205 sideload
PS D:\platform-tools> adb sideload D:\platform-tools\oriole-ota-tp1a.220624.021-a13fd9d0.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
PS D:\platform-tools> adb sideload D:\platform-tools\oriole-ota-tp1a.220624.021-a13fd9d0.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
PS D:\platform-tools> adb devices
List of devices attached
PS D:\platform-tools> adb sideload D:\platform-tools\oriole-ota-tp1a.220624.021-a13fd9d0.zip
serving: 'D:\platform-tools\oriole-ota-tp1a.220624.021-a13fd9d0.zip' (~0%)
PS D:\platform-tools> adb sideload D:\platform-tools\oriole-ota-tp1a.220624.021-a13fd9d0.zip
adb: failed to read command: No error
PS D:\platform-tools> adb sideload D:\platform-tools\oriole-ota-tp1a.220624.021-a13fd9d0.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
PS D:\platform-tools> adb sideload D:\platform-tools\oriole-ota-tp1a.220624.021-a13fd9d0.zip
serving: 'D:\platform-tools\oriole-ota-tp1a.220624.021-a13fd9d0.zip' (~0%)
Alright, I'll run it down. So after waiting a bit the first time around, I decided to go ahead and remove the USB cable, cause it wasn't doing anything. Big mistake. It printed "Failed to read 9067738 (or some variation of that) bytes data at offset 2080374784 (or some variation of that): Transport endpoint is not connected", then printed that many times over, then the Android Droid came over and under it said "Error". Now as i retry doing it after entering sideload again, it gets stuck. Am I ****ed or is there still a chance?
Never mind, I talked with some Google reps, and all I needed to do was reboot, I was hesitant to do so because of the red warning stating "WARNING: previous installation has failed. Your device may fail to boot if you reboot or power off.", but it turned out safe .
So did you ever get past the "Verifying Update Package"?
I've seen exactly what the OP attempted and his results and observations. adb always hangs at 'verifying update package'. I was able to reboot and did a factory image install of 13.0. The magisk_patched for its boot hangs at the 'google' logo. I have the update channel set to canary for the magisk app.
Also, flashing the factory image for the last 12.1 releases fails to downgrade.