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?
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.
How Fix Error 21 in adb sideload ?
Resolved
HHOOOWWWW
I have been on Android 11 DP since it was released and for the most part it has been stable. Unfortunately, my password app isn't working and could take months for it to be functional on 11.
Has anyone had success reverting back to 10 from 11? I've tried more times than I care to admit, but have not had any success.
Any suggestions would be welcomed.
G.
https://developers.google.com/android/images
Here you go
shannoncole05 said:
https://developers.google.com/android/images
Click to expand...
Click to collapse
I've tried several times, but have been unable to revert back!
Take note of which partition you are on, either A or B, check this on the main bootloader screen at the bottom of the screen. After you see if you're on A or B, flash the March factory image. As soon as the flash completes, you need to go right back to the bootloader screen and switch to the opposite partition that you are on. For example if you were on A before flashing the image, you need to switch to B and visa versa. To switch, from the bootloader screen type: fastboot --set-active=a or fastboot --set-active=b
After switching the active partition, reboot the phone and you'll be able to boot into Android 10 and will no longer be stuck on the 11 preview.
Hi there good people wonder if anyone could help me please i tried the android 11 through sideload but when i try going back to android 10 using the same method has i went to android 11 i get the following error from adb sideload
adb sideload flame-ota-qq2a.200305.003-1b5d6984.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
i have tried everything even another computer i get the same error tried different firmware i even tried uploading android 11 again has a test and that failed with the same error .... android 11 webpage say it can revert back to android 10 via adb sideload but i seam to be stuck here.... my bootloader is locked and i cannot unlock oem unlock thats why i choose adb sideload option
can anyone help me thank you
Downgrade
badwolf1972 said:
Hi there good people wonder if anyone could help me please i tried the android 11 through sideload but when i try going back to android 10 using the same method has i went to android 11 i get the following error from adb sideload
adb sideload flame-ota-qq2a.200305.003-1b5d6984.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
i have tried everything even another computer i get the same error tried different firmware i even tried uploading android 11 again has a test and that failed with the same error .... android 11 webpage say it can revert back to android 10 via adb sideload but i seam to be stuck here.... my bootloader is locked and i cannot unlock oem unlock thats why i choose adb sideload option
can anyone help me thank you
Click to expand...
Click to collapse
Did you try with latest platform here's the link.:good:
https://developer.android.com/studio/releases/platform-tools
Thank You!
caballon said:
Did you try with latest platform here's the link.:good:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I was having the same problem and this solved it! I had to download the tool from the Google site and copy/paste it into the "flash-all" folder and it worked!
klm2349 said:
I was having the same problem and this solved it! I had to download the tool from the Google site and copy/paste it into the "flash-all" folder and it worked!
Click to expand...
Click to collapse
Erased all right?
Question?
Not sure what the question is? It erased correctly and reinstalled Android 10.
Hi.
Just found an old GT-P7500 which has been laying around for for a few years.
It got TWRP 2.8.0.0 installed, but no ROM.
Trying to find the lates rom, but all links are broken...
Found a stock rom, but is unable to sideload it.
"
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
sending: 'c:\Tab 10.1\A1-p4-1.9-3G-cm.zip' 100%
adb: error response: protocol fault (couldn't read status): No error
"
Im trying to find a later TWRP update, but i can only find APK packages, which does not work for me...
Anyone who knows how i can get this tab to work again? Preperably with newers ROM available
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