A workaround seems to be to flash stock ROM first:
Or maybe it’s not even relevant:
As for the connection error.
Try another cable first, if possible the factory one. Also try other USB ports on the computer.
As a last resort, you can try to flash the ROM via saving it to a USB drive or SD card, whatever plugs into your phone.
Then navigate to the file from the respective menue. This won’t work on all Recoveries as far as I know, but TWRP for example will handle that case. I had to do this on a Samsung tablet once.
Thank you for your help.
For the “E:can’t…” I already read the first post but not better.
For the cable, this is the factory one USB-C. It works fine for fastboot.
I’m not an android specialist and as my phone is a new one, I don’t want to brick it.
Sorry, I don’t know enough about Pixel phones to make qualified requirements from now on.
Maybe you find the solution in an XDA forum thread as those devices are very popular in the scene.
Or if you can wait, someone with further knowledge will reply here soon I’m positive.
If you are using platform-tools and you are following this guide https://doc.e.foundation/pages/install-adb.html, it is unwise to also install fastboot from Debian repos. Debian 11 will give you an older version and you will then have two different versions of the same command on your machine - https://wiki.debian.org/DontBreakDebian. Using platform-tools from the zip is not breaking Debian, the tools are being provided but not installed.
Edit. One possible cause of these errors could be that all accounts (especially Google account), locks and passwords were not removed at the time you did the essential Factory reset immediately before starting to take control of the device.
But;
E:can’t send spi message: Try again
Data wipe complete
E:can’t send spi message: Try again
Data wipe complete
As you say, I think that it’s not a problem but as it may be a secure component, I’m not completely reassured.
There’s no google ID on the device, only the pin code.
I think that I reboot because there is the /e/ logo.
I enable the adb/sideload feature in the recovery mode on the phone with the power button, but he’s waiting and nothing happens.
“Here no devices/emulators found fits with device is not in Recovery mode > sideload.” Could it be a specific adb vs fastboot driver problem?
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 .
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
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
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.
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”.
