Google Pixel 4a - Install

No problems with “SIM pincode”, (by experience)
but “no Device pincode” is a requirement in the documentation.

I don’t put a SIM on it.
I only enter a pincode for the first boot to enable USB debugging

Part of the problem here may be that the stock android was not updated to the latest android 11 before flashing e. You have a June date; the last android 11 was October.

It’s easy to return to stock from the stage you are at now and I can find some links for you .

So, in my opinion, the device is now locked by this PIN and that’s why the device is not recognized by adb

You must re-install the brand stock firmware, and then start from scratch,

Previously, I had done a test by updating via the play store and wifi but I fear a switch to version 12.

How enable debugging USB without enter a pincode ?

I can understand that!

Returning to stock is done through fastboot so you just need to get the phone in fastboot mode at the beginning of the process. You can do this button press combo: with device powered off, hold vol down and press power to start the phone . Or with cable in phone hold vol down and plug other end into pc. Same thing.

I’ll just get some more info…

download the last android 11 for sunfish from here

https://developers.google.com/android/images#sunfish

The instructions for flashing are at the top of the download page but I can help if you need it.

Here is a log of the last time I flashed 11 on a pixel 5 this way, so you know what to expect as output in the terminal. Ah I can’t seem to post it I’ll try again in a bit!

Hmm, the forum will not process .txt file and I don’t want to paste the entire contents here; there’s about 140 lines of text.

I install the latest 11 version : RQ3A.211001.001 (7641976) from official android site : OK
→ Usb cable : OK

I have read for the 999 time the /e/, official android and lineageOS procedures.
I notice that the official android procedure only uses fastboot :

#!/bin/sh

# Copyright 2012 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#      http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

if ! [ $($(which fastboot) --version | grep "version" | cut -c18-23 | sed 's/\.//g' ) -ge 2802 ]; then
  echo "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
  exit 1
fi
fastboot flash bootloader bootloader-sunfish-s5-0.3-7357976.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-sunfish-g7150-00047-210319-b-7220401.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-sunfish-rq3a.211001.001.zip

why is /e/ procedure different?

No short answer to that.

flashing stock google flashes all partitions whereas custom roms only a few.

E is installed by sideloading a zip file containing everything required on this device. On some other e devices fastboot is used. Sideloading is quite easy, normal and widely used for installing custom roms.

If you follow the instructions you should be ok.

Set usb debugging, remove pin/passwords for unlocking,plug the phone into pc m’board, make sure adb enabled and get into fastboot with adb reboot bootloader. Follow instructions.

After flashing recovery I usually unplug device (so it is powered off) and reboot recovery with button presses > power and hold vol down. Replug when in recovery. the rest of the process is as per instructions.

I reinstalled the latest 11 version : RQ3A.211001.001 (7641976) from official android site : OK

I flashed and boot the custom recovery : OK

I formatted the data : same strange message !!

-- Wiping data...
E:Open failed: /metadata/ota: No such file or directory
Formatting /data...
Formatting /metadata...
Wiping Titan M...
E:can't send spi message: Try again
Data wipe complete

I try to install /e/OS : same issue

phone

Now send the package you want to apply
to the device with "adb sideload <filename>"...

terminal

pierre@asus:~/pixel.4.a/e.foundation$ adb sideload e-0.18-r-20210901132813-dev-sunfish.zip
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found

I’m trying to enable adb in Advanced » Enable adb → same issue

I reboot android and do not enter any pincode → same issue

I disconnect and reboot device → same issue

Sorry something is wrong but I don’t know what…

Can anyone confirm that they were able to flash their Pixel 4a?

If you were try this again, please can you do

adb devices and fastboot devices

at each change of booting mode to check you actually have full contact with the device in both adb and fastboot.

The first time I enter an adb command I have this message

pierre@asus:~/pixel.4.a/e.foundation$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

I have validated a popup on android to authorize my PC

How is it working in recovery mode ?

“fastboot devices” is always working not “adb devices”.

This is not the nicest presentation ever, but he includes a video to help make his point - but it looks like he is describing a situation very close to yours. Found with other similar explanations by searching this.

This adb server's $ADB_VENDOR_KEYS is not set

https://krispitech.com/adb-vendor-keys-not-set/

Edit, if I follow this correctly (I am not sure) but is your PC now seeing the same device with a different identity? Would this be why you must now delete some history?

Yes!
So easy :wink: Just unplug and plug in the USB without rebooting anything.
The device is detected again.

All that remains is to try…

Thanks everyone.

Pierre

1 Like

I do a “fastboot flashing lock”.
The phone boot with “Can’t find valid operating system.”
The device will not start.

If I press Power + Volume Down, I can select :

Restart Bootloader
Start
Power off
BaCode
Rescue mode
Recovery mode

PLEASE HELP

I am reading this thread. Good that you got some progress.

I’m ready. T.Y.

I unlock the bootloader and the device boot again.

Why can’t I lock the bootloader again ?

Great!

Why can’t I lock the bootloader again ?

Because it is not in the instructions would be good enough for me! :blush:

Speculation Google never wanted you to liberate their hardware!

Only a few Android phones allow to relock bootloader safely in my experience.

It is not written ok, but the opposite either…
I’m not sure but I think that calyxos do it.

What’s the risk about an unlock bootloader?
Can an application modify it?

Google never wanted you to liberate their hardware!

Vote E.U. law !!! :rage:

I see the lock more like this. The system is proprietary; it had a verified boot; it had a lock to seal the system.

Google make claims that everyone can trust the sealed and verified system.

You have liberated it.

It is a different ball park.

Can an application modify it?

I have never thought a 9mm thick highly networked mini computer was secure.

Edit. I am in danger of starting something here on locking! If you copy the Google method and have a “signed system” you can lock the bootloader as done for example by Divestos!

The risk is always an estimate that differs according to the system but especially the person who estimates it.
To try to have a precise estimate, it is necessary to try to know as precisely as possible the studied system.

There’s no safe system, but you can try. ( a Debian daily user :wink: )

1 Like