Cannot install, help!

Keneda

@abananaman
Did you select the wipe options in the installer ?

abananaman

Yes, I have tried with and without wipe, makes no difference.

MrT10001

Is the phone unlocked, ie SIM unlocked from a Cell (Mobile) provider?

abananaman

Yes, I am able to install any other OS without issue, I can OEM Unlock from within Android, bootloader confirms I'm unlocked.

EDIT Also, I purchased this device brand new direct from Google when the 2 was still 'new'. I am the only owner of this particular phone.

rocket2nfinity

Did you use the factory, not OTA, image from google?

Calyx and Graphene changes something about the partitions if I recall, that can only be fixed by flashing non-OTA stock image.

Also use installer version .88 or .89
Later versions are broken

abananaman

Yes, I used the factory image from https://developers.google.com/android/images and had it reflash all partitions, since I was aware Calyx did some stuff to mess with partitions.

I attempted with .8.8 and .9.1 on Windows, and with .8.9 on Fedora. All with same result. I did not try with .8.9 on Windows yet, I will try that.

Process will be as follows: Reflash PQ3A.190801.002
Unlock and enable USB Debugging.
Download .8.9 installer.
Attempt to install UT.

I'll update with result.

abananaman

Ok, manually flashed bootloader, radio, and os for PQ3A.190801.002.
Left bootloader unlocked.
Booted phone, verified OEM unlocking was turned on, and turned on USB Debugging.
Downloaded new copy of .8.9 installer and ran.
Accepted (and remembered) USB Debugging request on phone.
Selected stable UT, with wipe and bootloader flashing or however that checkbox is worded both selected.
Installer flashed recovery.
Rebooted to recovery, waiting until windows recognized the phone again and clicked continue on installer.
Now it is sitting again at "Mounting partitions..." with no indication it's going to move, ever. It's currently been about 10 minutes at this step. Phone is sitting in recovery and installer is sitting on that screen, nothing happens.

Alter

@abananaman When I tried to install my phone (Volla, so not same brand), also had to try different versions of installer on my PC (with Ubuntu 20.04 desktop OS). In logfiles of the installer there was useful information. In my case, the image from Volla site could not be downloaded. I downloaded it manually and put it in the place that was specified by the installer. Then tried again to start install. Several attemps, but worked for me. Advise: look at log files.

flohack

@abananaman Did you remove eventual encryption?

flohack

@abananaman Please grab installer logfile from .cache folder, somewhere there it should be

txmoose

Hey there, this seems to be the same issues I'm having, as well, so I figured posting here would be better than starting a new thread. I've been fighting with this for a couple nights now, but I'm not getting anywhere. I've flashed PQ3A.190801.002 via the chrome WebUSB flash link for the Factory Image (not OTA), attempted the 0.8.9-beta snap and the 0.9.1-beta AUR install, run the snap install with sudo, etc... Still getting the same behavior. It hangs at "Mounting Partitions..."

Any idea what I might be able to do to get past this?

I'm happy to attach my log file or send it where I need to, please just let me know the best route for that. I don't seem to be able to attach it here as a file, and copy/pasting the whole log seems like bad form? Happy to be told I'm wrong on that, though. Here's the last 10 lines, at least:

{"level":"info","message":"Downloaded file 8 of 12"}
{"level":"info","message":"Downloaded file 9 of 12"}
{"level":"info","message":"Downloaded file 10 of 12"}
{"level":"info","message":"Downloaded file 11 of 12"}
{"level":"info","message":"Downloaded file 12 of 12"}
{"level":"verbose","message":"running core action write"}
{"level":"verbose","message":"running adb action wait"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"wait-for-any-any\"]}"}
{"level":"command","message":"exec: {\"cmd\":[\"adb\",\"-P\",5037,\"get-state\"],\"stdout\":\"recovery\"}"}
{"level":"verbose","message":"running adb action preparesystemimage"}

Thanks in advance!

flohack

@txmoose Well can it be that partitions are already encrpyted? (Happens on 1st Android start) - you would need to use TWRP and wipe all partitions AND format data to ext4.

txmoose

@flohack Hey thanks for the reply. I attempted to wipe all partitions with TWRP, and formatted data as ext4, but I'm still hanging at Mounting Partitions. Anything else I can try? I could probably find a Windows computer to try to install from, but I suspect that is not going to be a solve. What is ubports-installer doing under the hood at the "mounting partitions" step? Is there a way I can attempt that step manually to get more verbose output?

Thanks again.

dhrunia

@abananaman @Flohack I am having the exact same issue. I have flashed android 9 (PQ3A.190801.002) using flash.android.com, made sure oem unlocking and usb debuggin are enabled on android 9. Installed ubports-installer (0.9.2-beta .deb package) and followed instructions. Now I am in ubports recovery screen on phone and the installer is stuck at mounting partitions...

Keneda

@dhrunia
Did you also select all the wiping options possible in ubports installer ?
As your phone come straight from android, better is to select all the wiping options in ubports installer.

dhrunia

@keneda yes I have selected the wipe option in installer but that didn't help. I have also tried wiping all partitions and formatting data to ext4 using twrp as suggested by @Flohack but that didn't help either. It always gets stuck at the mounting partitions step.

MrT10001

No issues installing on the Pixel 2 but here are things to try:

Use a Windows PC (yes use a Windows PC) and use the Android Flash tool through Chrome to downgrade the firmware to the correct version from here and click on Flash.

Tick the following before install:
Force flash all partitions - ticked
Disable verification - ticked
Disable verity - ticked

I ticked these for an issue on the Pixel 3 and it worked and it may work for the Pixel 2

Then boot into Android, do the usual before rebooting to the bootloader and try the UT installer.

I know not everyone has access to a windows PC or just hates using it, but it is really helpful to have something like this to assist with fault finding and other issues. The other thing I find is most programmers/software people immediately use the CLI, which is fine, but can complicate things. Stepping back and reconsidering things is always worthwhile to resolve an issue. The number of people I have trained who batter the keyboard at a 100miles an hour and make a mistake in syntax, then wonder why they have an issue and take 4 times as long to resolve it. It took me a while to learn to put things aside and sleep on the issue. I would usually resolve it the next day.

dhrunia

@mrt10001 I did try with those three options ticked that didn't help either.

MrT10001

@dhrunia OK, that's good to know.

MrT10001

Have you checked this out?