Core recovery files for the Team Win Recovery Project (T.W.R.P) - this is not up to date, please see https://github.com/TeamWin/android_bootable_recovery/
[x] I have searched for my issue and it does not already exist
Device codename: a5y17lte
TWRP version: 3.5.2
WHAT STEPS WILL REPRODUCE THE PROBLEM?
adb push and adb sideload of large file will fail, due to short data received.
WHAT IS THE EXPECTED RESULT?
The ADB server in TWRP must ignore so-called Zero Length Packets, ZLPs, received via USB.
Google updated their ADB client to send ZLPs to flush data buffers regularly, due to a change in RX buffering in their ADB server.
Device codename: a5y17lte TWRP version: 3.5.2
WHAT STEPS WILL REPRODUCE THE PROBLEM?
adb push and adb sideload of large file will fail, due to short data received.
WHAT IS THE EXPECTED RESULT?
The ADB server in TWRP must ignore so-called Zero Length Packets, ZLPs, received via USB. Google updated their ADB client to send ZLPs to flush data buffers regularly, due to a change in RX buffering in their ADB server.
Refer to the function should_perform_zero_transfer() at: https://github.com/aosp-mirror/platform_system_core/blob/platform-tools-29.0.6/adb/client/usb_libusb.cpp#L188
I can probably make a patch if someone can point out the USB code used for ADB in TWRP.
WHAT HAPPENS INSTEAD?
Transfer aborted. Google has confirmed this is a new feature and not a bug.