How Fix Error 21 in adb sideload ?
Resolved
HHOOOWWWW
Related
I had a problem and my wifi tablet is now bootlooping. So I looked into using adb sideload to re-install a rom.
When I enter sideload (twrp) and do adb devices it lists my device with sideload beside it.
C:\Windows\system32>adb devices
List of devices attached
0123456789ABCDEF sideload
when I try to sideload the rom adb c:\rom.zip I get error closed.
I tried adb usb to reset the usb but getting error closed.
C:\Windows\system32>adb usb
error: closed
By the way I am running windows 8
Really stuck any ideas!
I have been able to download the stock image and use fastboot to flash so I think I have the issue sorted!
I had the same problem three days ago. Try this method. It works for me write this on command " adb sideload filename.zip" hit enter don't put quote. If this not for you, go head try
adb push filename/data/media/
If you are on 4.2.2
adb push filename/data/media/0/
Good luck
Sent from my SPH-D710 using xda premium
Sideload mode is just a subfunction of your recovery. Create a blank .zip file and push it to the device using adb push C:\pathtozip\whatever.zip to abort. You'll be kicked back to your recovery and will be able to reboot.
Hi everybody, I'm trying to flash the zenfone 3 by adb giving the command adb sideload (filename) .zip is not working. Note: The bootloader is unlocked. But I would also like to block again.
When issuing adb root I get the error message adbd cannot run as root in production builds.
I'm on 7.1.1 Build NF426J, with root and TWRP.
I tried patching adbd with chainfires insecure adbd which seems to not work on Nougat.
What else could I do to be able to adb root && adb remount?
I always used it to load updates, I can't succeed with Android 11 DP2.1
Deamon is started, adb devices shows the phone, but sideload fails with:
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Suggestions, please?
Hi everyone
Already done:
"New" OnePlus 6t, bootloader unlocked (confirmed), successfully flashed via adb "fastboot boot twrp.img" (=temp TWRP), installed twrp.zip via twrp file explorer (persistent twrp), installed magisk.zip.
Then reboot into recovery, reboot system, android gui ok, reboot into bootloader (fastboot), wipe Dalvik/Cache, Data, System (accidentally).
Then:
adb sideload lineage-18.1-20220303-nightly-fajita-signed.zip
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Again adb sideload lineage-18.1-20220303-nightly-fajita-signed.zip
Total xfer: 1.00x
When I try to boot android-gui I get the message that there is no system installed (obviously, because of wiped system and not successfully installed lineageos).
adb push /z/Downloads/Android/System/OnePlus-6T/ROM-Flash/lineage-18.1-20220303-nightly-fajita-signed.zip /storage/Download/lineage-18.1-20220303-nightly-fajita-signed.zip
(584355703 bytes in 15.260s)
TWRP > file explorer > install > lineage-18.1-20220303-nightly-fajita-signed.zip without success.
How can I fix this?
Try flashing the lineage recovery image via
fastboot flash boot lineage-18.1-20220303-recovery-fajita.img
After that, boot into your new recovery and go to the adb update option and I think you should be good from there.
If you wiped the system, I think you'll have to use msm tool to get oos installed again, unlock bootloader again, then flash lineage