Installing to Pixel 3a
-
@Fizz Ok, Linux, a bit more. I tend to run from the Command line in the Platform-Tools folder... However, install ADB and fastboot in the CLI. You have to use Chrome Browser (not any other inc. Chromium) to run the Android recovery tool.
The recovery tool won't see your phone as it needs ADB and fastboot installed.
What flavour of Linux are you running?
-
@MrT10001
I am running Linux Mint 20.3.OK, so i'll install both fastboot and ADB via the command line first. Then i'll try Vivaldi and Brave again, and failing those, install Chrome.
sudo apt install fastboot sudo apt install adbLooks like i already had adb installed, just not Fastboot.
-Fizz
-
@Fizz If you unzip the factory image PQ3B.190801.002 to the platform tools folder, then run the flash-all.sh from there you won't need to use Chrome and the Android recovery tool (it only works on Chrome, tried it on others it won't work).
-
@MrT10001
OK, so i have downloaded platform-tools and unzipped it into its own folder.I have also installed fastboot via the command line, and adb was already installed.
So now i'm moved the factory image to the platform-tools folder. So my platform-tools directory contains the following:
bootloader-sargo-bootloader-sargo-b4s4-0.1-5653622.img
flash-all.sh
flash-all.bat
flash-base-sh
image-sargo-pq3b.190801.002.zip
radio-sargo-g670-00011-190411-b-5457439.imgAlso there is the lib64 folder, files adb, fastboot, and all the others that came with platform-tools.
My phone is connected via usb, it's in Fastboot Mode.
Do i first need to unlock with fastboot oem unlock? Or do i go straight to flash-all.sh ?
Sorry if i'm being annoying with excessive questions. I want to be sure i understand things completely, as I've not done this before and i don't want a brick.
-Fizz
-
@Fizz Unlock the bootloader first (try fastboot oem unlock).
Reboot to Android, set it up again when you have done that, reboot to fastboot mode.
When in fastboot mode run the flash-all.sh command.
Let it run, when it finishes the phone will reboot.
Set Android up on the phone again (again) and enable developer options and USB debugging.
Then run the UT installer and follow the onscreen instructions.
-
@MrT10001
Thanks for all your help. If i end up with a brick i'll track you down... lol.
OK, here goes....-Fizz
-
@Fizz You won't brick it, I haven't had an unrecoverable brick yet.
If your Pixel 3a hangs at the Google logo see my previous mentioned thread.
Be patient, UT takes time to install.
-
@MrT10001
Well, the first step went well, i was able to unlock the bootloader. Note the exact command was actually "fastboot flashing unlock".I let Android reboot, went through the basic setup, etc. Once that was done i rebooted to Fastboot Mode.
But I just tried to run flash-all, and my laptop tells me the command is not found. I've tried "flash-all.sh" as well as "flash-all", but neither is recognized. The file is right there in the current folder. What've i done wrong?
-Fizz
-
@Fizz Try sudo flash-all.sh. I am not on my Linux system so I cannot remember the exact command. If sudo soesn't work try sh flash-all.sh or ./flash-all.sh.
-
@MrT10001
Hmmm.... the latter two suggestions work- it executes. But now it tells me:
fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.htmlBut that link just redirects to the same file that i downloaded and unzipped earlier.
Hrmmm... so not sure what i need to do here...
-Fizz
-
@Fizz On your laptop, you are in the platform tools folder and you have the unzipped Android ROM - factory image PQ3B.190801.002 - in there too? You have opened a command prompt in that folder as well?
-
@MrT10001
Yes, i created a folder named platform-tools, which has the contents from android's site (https://developer.android.com/tools/releases/platform-tools ).In that same folder i have moved the contents of the image download ( from https://developers.google.com/android/images#sargo ).
So the contents of the folder are:
lib (folder)
adb
etc1tool
fastboot
hpor-conv
mak_f2fs
mak_f2fs_casefold
mke2fs
mke2fsconf
NOTICE.txt
source.properties
sqlite3
bootloader-sargo-bootloader-sargo-b4s4-0.1-5653622.img
flash-all.sh
flash-all.bat
flash-base-sh
image-sargo-pq3b.190801.002.zip
radio-sargo-g670-00011-190411-b-5457439.imgI know there is still a .zip file in that folder, but from what i read that should be left alone- not unzipped.
In the terminal, i am in that same directory, platform-tools, where all the files are.
-Fizz
-
@Fizz Odd it should work? Maybe someone more advanced on Linux could chip in?
I downgraded generally with chrome and the android tool on Windows 11(
Yes I know), it has worked for me. -
@MrT10001
Well, what i'll try next is installing Chrome on my laptop, and seeing if the flashing will work through the flash tool. Will let you know how it goes.-Fizz
-
@MrT10001
Well, the Chrome method seems to be working- it has recognized the device and i've pointed it to the correct build.Quick question- the flasher is asking me:
You are downgrading your bootloader, which normally means you are flashing an older build. This usually requires a factory reset to successfully boot the device.
Would you like to factory reset your device?Do i want to do this? I've no data on the device i care about.
-Fizz
-
@Fizz Yes. It is best too.
-
@MrT10001
Well, things aren't going well so far. It does the download of the desired image. But i run into problems shortly after the install attempt.When it starts the install, it says Rebooting Device into Bootloader. The phone screen flashes briefly, but comes back to the Fastbook Mode screen almost immediately.
A few seconds later, the installer says
Flash Failed
Timed out waiting for device to disconnectIt gives me the option to "retry", but it never works. The only way i can really start it again is to close Chrome (per the instructions the installer gives), re-open it and try again. In that case, it does a full download of the image again. And unfortunately this pattern just repeats.
I'm on my third attempt now, downloading the image again. The install definitely did something, as the phone won't boot Android at all anymore- i can only get it to Fastboot Mode. But it's not getting far with the install either. Ugh.
UPDATE- well third time it made it a lot farther. It got through few stages of writing the image, and appeared to be loading Android (white page with Google logo), but then i again got the Flash Failed Timed out waiting for device to disconnect error.
-Fizz
-
@MrT10001
Being that i am stuck at the Google splash screen, i am looking at your earlier link. Do you mean i should now try the UT installer- that the old version of Android is now sufficiently installed that i can try installing UT?-Fizz
-
@MrT10001
Hmmm.... i now notice that the Android Flash Tool no longer detects the phone at all (not even when using Chrome). So does that mean my only option is to try the UT installer now? Or is there something else i need to do first?-Fizz
-
@Fizz No, it looks like the required version of Android has failed to install for whatever reason on your hardware.
Take a step back and don't try and batter on through it as it won't work.
In the platform-tools folder open a command prompt.
Ensure the phone is in fastboot mode and connect to PC
In the command prompt run the command fastboot devices
It will pick the device up and show its serial number
If it doesn't, reboot the device to fastboot and try again
If it is still not picked up, then try another USB cable on a different port.
If it does get picked up, good.Then you can either try the flash-all.sh in the platform tools folder or rerun the android recovery tool in chrome. If it disconnects in the middle of it there will be something on the laptop interfering. If it does, unplug the phone and reconnect it and see if it continues.
This is what my platform tools folder looks like in windows, Linux will use the same (I use Ubuntu).
Right click and open your terminal in this folder and run your fastboot and flash-all.sh from here.
You must allow the device to boot fully into Android and ensure that
a) you are on the correct ROM
b) your bootloader is unlocked
c)developer options are enabled so you can enable USB debugging.This is why I have a Windows system (ugh), my Ubuntu system and a mac too hand. If I cannot get it working on one, I will on another (and I have to use Windows as where I work, most people don't know Linux exists, even though they use it on one system).
