Installation advice for new Pixel 3a/3a XL owners
-
Hi,
I'm a new Pixel 3a owner and have just got UT working (awesome btw), and just wanted to give some feedback...
I'd like to think that I'm fairly techy but it's just taken me a whole day to get UT installed. And the problems all boiled down to the way I was flashing Android 9. Yes, the information is there in the locked thread https://forums.ubports.com/topic/6798/stuck-on-google-splash-screen-instead-of-going-to-recovery-mode but I think it would be great if this could be added to the 'Preparatory step' section of https://devices.ubuntu-touch.io/device/sargo/
In a nutshell (on Windows 10 at least), DON'T flash with the 'flash-all.bat' script. Instead, use the Android Flash Tool and make sure these (and only these) checkboxes are checked:
Wipe Device
Force Flash all Partitions
Disable Verify
Disable Verification
After that's done, it doesn't matter which version of the installer you use. They all seem to work, so no reason not to use the latest.Thanks,
-
Hi,
If you look at https://devices.ubuntu-touch.io/device/sargo/ :
i don't think it has just been added
Preparatory step Make sure to revert to factory image PQ3B.190801.002 before continuing: Pixel 3a: https://developers.google.com/android/images#sargo Pixel 3a XL: https://developers.google.com/android/images#bonito -
Hi @lduboeuf - thanks for the reply. I was aware though, that the 'Preparatory Step' tells us to install Android 9. But it doesn't give any info on how to install. I went for the command line method, as it seemed easier. This seemed to make it impossible to install UT afterwards and I would never have guessed that the reason was the way I'd installed Adroid 9 (until I found the info buried in the thread I linked to). Thanks.
-
@moodroid said in Installation advice for new Pixel 3a/3a XL owners:
Hi @lduboeuf - thanks for the reply. I was aware though, that the 'Preparatory Step' tells us to install Android 9. But it doesn't give any info on how to install. I went for the command line method, as it seemed easier. This seemed to make it impossible to install UT afterwards and I would never have guessed that the reason was the way I'd installed Adroid 9 (until I found the info buried in the thread I linked to). Thanks.
Installation of Android is in Android doc
But i agree first time install can be hard to tackle. unlock, flash android, then install ut, often manually reboot to bootloader, cable issue., etc... not easy
-
@moodroid
Thanks for the feedback and glad you sorted this ^^ -
I have done an install end to end on a Pixed3a having Android 12 using a VM (Virtual Box 6.1).
What you do is at your own risk
Executive summary here:- You will have an unlocked bootloader at the end of the port. That cannot change, is not a drawback in my view - but read about before you panic and compare with Google Android.
- Can switch back easily and is very very unlikely you will brick the phone (cannot think of a way but people are creative)
- By using a VM you do not need anything new installed on your main PC. You can save/archive the VM to reuse anytime. It is best on the VM to use chrome as google likes it.
- Make sure you download everything before starting
- Virtual Box 6.1 with extension pack too
- Chrome setup
- Evaluation Win 10
- ADB files
- Google drivers
- UT installer
- You will not install anything on my local PC aside of Virtual Box (presume you have it already if you read this :))
Maybe a faster way to install for newcomers (all done for me in 20min.)
1.Install your VM with Windows 10 (get a free version from MS - https://info.microsoft.com/ww-landing-windows-10-enterprise.html - just fill in the form with whatever and download).
2. Enable USB access on the VM.
3. Test that you can see your Pixel on the VM.
3.a Start here : https://developers.google.com/android/images#sargo and get adb
3.b Get the Pixel drivers too https://developer.android.com/studio/run/win-usb
3.c Tip. May want to fiddle with the Virtual Box USB filters in VM ->Settings. The way your device is seen will change as you go thru the motions.
4. Use the google sargo page listed at 3a to flash the correct version as listed (currently is PQ3B.190801.002 - may change) on your VM. If it works you have a winning setup and your install will work for sure. If you have issues you can always restart the flash, so do no not worry. Always keep 3.c on the back of your mind.
5. This is your Go-No Go gateway. If your mobile flashed OK and you can see the Pixel3a on your Windows VM you ready to install Ubuntu Touch using the UBPorts executable (it has well documented requirements that I will not enumerate) on the VM. At the end of the process your USB filter will change again (see 3.c).
6. All worked OK for me - the only catch was with the HotSpot - needed to update the APN but I guess it was to be expected.
7. If you want to go back use the same VM and web page from 3a to flash whatever Android you want. -
@moodroid ... I just bought some 3a and 3a XL for a project where I needed a Linux Phone ...
And my first experience was to be 4 hours fighting and finishing with a "bricked" 3a ... ahhhh ... just that was not bricked and I didn't understand several things about the process (I am writing my own manual with the details).
At the end, that Android 9 permanent Google splash screen after using the flash-all.bat is annoying, but not wrong. Just need to continue with the UBports installation and at the end you will have an operational Ubuntu Touch phone working.
Other thing .... the current Google instructions for backport are USELESS, as they already erased the information about the 3a or 3a XL. There is a WIRELESS version that doesn't work because it is not possible to downgrade the phone ... (Android limitation), so you need to use a FACTORY version, unpack the ZIP file and follow the instructions, to finish with the bricked phone. I found one, but after so many URLs I am not sure where I had it ... could some official Touch source to publish an official FACTORY URL for 3a (sargo) and 3a XL (bonito) images? ... again, don't say that read the Android references, because they are no longer working with these Pixel phones.
It seems that UBPorts just needs the phone to have some Android 9 things there. And well, I even erased all the phone, but rebooting it and playing with Power and Power volume buttons, makes the PC script to recognize the phone and deliver the Android 9 version.
What about another Android version? ... in my initial desperation, I also tested that, but the installation fails. So cool your head a little and just do the things with calm and everything happy.
The Flash Android tools downgraded a 3a XL without any trouble, Just Development mode, USB Debugging and the OEM Ulocking, and to accept some questions here and there and ready, Android 9.
The only I need to figure is how to turn off the Unlocking option since I have no more Android in the phone and I don't need Android there again ... maybe one of these days
