You can use the command to pull the patched boot image from the device to the PC.ĭevelopers often go through cycles of testing and debugging during the development process, and also after it, to iron out bugs/issues. And this is when the ADB Pull command can specifically be helpful. Transferring the image via MTP/File Transfer mode is known to corrupt the file. Now before you can flash the patched boot image to your device, you must first transfer it from your device’s storage to the PC. So, you can use the ADB Push command to transfer zip files to a temporary directory ( /tmp/*) and flash it right from there.Īnother situation is while you’re installing Magisk on your device, in where you patch the stock boot image using Magisk. But that shouldn’t stop you from flashing files either.
TWRP for your specific device could still be in development.
This is quite common with newer Android devices running the latest Android version (e.g. Sometimes, TWRP cannot even decrypt the data partition, which means you could not access your phone’s internal storage to flash ZIP files. In such a case, you can just connect your Android device to the PC and use the ADB Push command to copy files from your PC to your device. You’d realize that the flashable ZIP of the custom ROM that you transferred has been erased (Don’t worry, it happens to the best of us). Let’s say you’re in the midst of flashing a custom ROM which requires you to wipe the OS in TWRP, sometimes even the data partition/internal storage. For an Android enthusiast (a.k.a flashaholic) But it makes sense to be acquainted with these commands just in case you might need them.Ģ. Note:This is not the ultimate solution, you’d still need to troubleshoot your PC and resolve the issue with the USB drivers.īasically, using ADB Push and Pull commands isn’t something that an average Android user might need.