While trying to install an OS on my Pixel 2 XL using either LOS or TWRP recoveries, my PC and the 2 XL hangs after the adb sideload OSinstallpackage.zip command. I have tried installing various versions of LOS and even tried installing the last Google OTA package for this phone. TWRP just says tha the package is being installed indefinitely, LOS recovery says verifying installation file. The PC just has a blinking cursor under the sideload command line, no install progress is displayed. Up until recently, this problem didn’t exist and I don’t know what changed. Does anyone out there have any idea how to resolve this problem?
Installation hangs at verifying installation file
- Thread starter neilth
- Start date
I have waited 15-20 minutes. Typically, on the PC, you start to see the percentage of installation almost immediately when everything is working correctly.
True.
It sounds like the issue is with TWRP. If you boot into OEM recovery, are you able to sideload the OEM OTA?
Have you tried different USB cables?
Are your ADB Platform Tools up to date? Using tools like Minimal ADB is not recommended; make sure you're using the original SDK Platform Tools from here.
I am getting the same issue whether I use TWRP or LOS recovery. My ADB Platform Tools are the latest version. How do I get back to OEM recovery once I have used non OEM operating systems on the phone? And yes, I have tried several USB cables.
Hmm. Let's still try the OEM recovery.
Good.
Just reflash the stock boot image from the factory image, then use the key combo to force a boot into recovery
Well...there's only so many possibilities.
Does your USB connection transfer data fine in other cases? Maybe you just need to clean the port.
You could try connecting a USB drive directly to the phone and flash from that.
Or flash a file that's already on the phone - but that requires that TWRP can decrypt your data, and ISTR that TWRP hasn't been updated to the newest encryption scheme.
You could try connecting a USB drive directly to the phone and flash from that.
Or flash a file that's already on the phone - but that requires that TWRP can decrypt your data, and ISTR that TWRP hasn't been updated to the newest encryption scheme.
I downloaded the last released official factory OTA zip of the operating system for the Pixel 2 XL from Google. How do I proceed to get the stock boot image and install it on my phone?
Everything was fine with this phone running LOS 19.1. Last week I attempted to upgrade to the unofficial release of LOS 20 using the published LOS upgrade instructions and now I can’t even get LOS 19.1 to install again for some reason after having wiped the phone’s partitions.
Factory images and OTA images are not the same.
Factory images for Taimen
Extract, then extract the image-device-builnumber.zip inside it. You'll find the boot.img in this archive.
Yes, good advice from V0latyle. Flashing factory usually fixes things.
I downloaded and extracted the last (12/20) factory image from Google. I have the boot.img file you mentioned, how do I install it on my phone in the correct place?
Just flash everything as Google instructed on the page (flash-all or flash tool). Note that this will delete the data on your phone.
There was nothing on my phone to delete! I ran the flash-all.bat file which successfully installed the Dec. 2020 Android 11 OS, but did not resolve the issue with the adb sideload command hanging when attempting to install a non Google OS such as LOS.
Well, at least you've eliminated some possibilities. To my mind, this means that:
- the USB connection is working
- fastboot works
- hardware problem unlikely
What remains:
- wrong USB driver on the PC - I believe it uses a different driver in recovery - check device manager with the phone connected in recovery
- wrong adb version on your PC
- defective recovery (but you tried different ones, I think)
- you doing sideload wrong - post screens from phone and PC
- the USB connection is working
- fastboot works
- hardware problem unlikely
What remains:
- wrong USB driver on the PC - I believe it uses a different driver in recovery - check device manager with the phone connected in recovery
- wrong adb version on your PC
- defective recovery (but you tried different ones, I think)
- you doing sideload wrong - post screens from phone and PC
Here are your requested screenshoots of the computer’s command prompt window where I run fast boot and adb commands, the phone screen showing the LOS recovery hung at "verifying update package" and a third shot of device manager showing the presence of the Android ADB Recovery Interface while my phone is connected to my computer via USB and in Recovery. I hope that you see something that I am missing here, I don’t see anything that stands out as a problem. Thanks for your assistance.
I suspected that LeMobile driver might be the problem. I just tried using another computer after installing the latest Google Android support software on it and I finally got LOS 20 installed on it. I will be correcting the incorrect USB driver on my laptop, which I had previously been using to use adb and fastboot on the phone as needed.
I want to thank you two for your assistance with my problem here!
I want to thank you two for your assistance with my problem here!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2I suspected that LeMobile driver might be the problem. I just tried using another computer after installing the latest Google Android support software on it and I finally got LOS 20 installed on it. I will be correcting the incorrect USB driver on my laptop, which I had previously been using to use adb and fastboot on the phone as needed.
I want to thank you two for your assistance with my problem here!1
True.
It sounds like the issue is with TWRP. If you boot into OEM recovery, are you able to sideload the OEM OTA?
Have you tried different USB cables?
Are your ADB Platform Tools up to date? Using tools like Minimal ADB is not recommended; make sure you're using the original SDK Platform Tools from here.1
Hmm. Let's still try the OEM recovery.
Good.
Just reflash the stock boot image from the factory image, then use the key combo to force a boot into recovery
Well...there's only so many possibilities.1Does your USB connection transfer data fine in other cases? Maybe you just need to clean the port.
You could try connecting a USB drive directly to the phone and flash from that.
Or flash a file that's already on the phone - but that requires that TWRP can decrypt your data, and ISTR that TWRP hasn't been updated to the newest encryption scheme.
