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.
Related
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.
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?
I'm trying to sideload a pandora apk and i'm running into an adb error that i don't understand.
Steps taken:
adb installed on PC
drivers installed on PC
phone has USB debugging ON
phone connected via USB to PC
adb devices: shows my device attached properly
adb shell generates a prompt: "OnePlus6T:/$
pm install -i "com.android.vending" -r /sdcard/download/pandora.apk
The last command to install generates the following error: <avc: denied (read) for scontext=u:r:system_server:s0... (see attached screenshot).
I've tried different locations such as /sdcard/pandora.apk and tried different apk files with the same result.
I can not reinstall any os tried to install dotos and get adb: failed to read command: No error on pc on phone I get failed to bind mount