I have been using Evolution X for a while but loved E/os on my other older phones and thought that it is time to use it on my 6a yet after trying to flash the dtbo after successfully flashing the boot.img and then trying to flash the dtbo.img i get:
Writing ‘boot_b’ (bootloader) invalid boot magic
FAILED (remote: ‘failed to flash partition (boot_b): -7’)
fastboot: error: Command failed
i have tried reverting to stock rom and then retrying but still no luck. Would love it if someone could help explain as to why this is happening
Does your bluejay meet
Before following these instructions please ensure that the device is on the latest Android 13 firmware.
$ fastboot --version
The phone is unlocked ?? … and after unlock
Since the device resets completely, you will need to re-enable USB debugging to continue.
Yes the device is unlocked and has been running android 14 for the past 5 or so months i don’t know if i would have to downgrade to 13 first before installing e/os but it is running android 14 as of right now as i have reinstalled the stock firmware.
even after booting back in and re enabling usb debugging i am still getting the same error once i am back in fastboot mode and try to flash the dtbo.
the fastboot version is 35.0.1-11580240
So if it is running Android 14 now, the install will fail. You cannot use /e/OS to downgrade Android version.
There is a guide to Downgrade and images here Factory Images for Nexus and Pixel Devices, or some use Android Flash Tool.
I have now tried both downgrading to android 12 as well as 13 and yet i still cannot get the dtbo to flash.
I now get this error:
Writing ‘boot_b’ (bootloader) invalid boot magic
FAILED (remote: ‘failed to flash partition (boot_b)’)
fastboot: error: Command failed
Beware, there are warnings against downgrading Pixel 6 from 13 → 12.
Quoting from “Factory images” link above:
Warning: The Android 13 update for Pixel 6, Pixel 6 Pro, and the Pixel 6a contains a bootloader update that increments the anti-roll back version for the bootloader. This prevents the device from rolling back to previous vulnerable versions of the bootloader. After flashing an Android 13 build on these devices you will not be able to flash and boot older Android 12 builds. For developers who need to develop and test against an Android 12 environment, a special Developer Support Build that contains the bootloader update should be used.
Please be very sure to use only “the latest Android 13 firmware.”
FAILED (remote: ‘failed to flash partition (boot_b)’)
fastboot: error: Command failed.
An internet search, https://www.reddit.com/r/essential/comments/kpe3oa/how_to_solve_the_failed_remote_error_flashing/, suggests use another cable.
i went from having no os as after flashing dtbo i always have to use android flash tool to get back to a normal state and even when i installed fresh android 13( upgrading from 12 not downgrading but upgrading from 12) i am still getting this error
So, pre-requites :
- android 13 based Gogol firmware is now already installed.
- is bootloader unlocked ?
in a terminal copy/paste :
fastboot oem device-info
It must answer something else than :
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.002s]
Finished. Total time: 0.003s
- then flash boot, dtbo, recovery-e
I have tried running this command multiple times now in cmd as i am doing this on windows and the output i get is this:
FAILED (remote: ‘Invalid oem command device-info’)
fastboot: error: Command failed
The device is running android 13 ( this to be exact )
TQ3A.230901.001 (10750268)
bluejay-user (signed)
13.0.0 (Android 13)
API level 33
The bootloader is unlocked as it says both on the device device state Unlocked (this is ofcourse because i unlocked it using fastboot flashing unlock ).
I hope this will help :
Keyword inactive slot
Read this: Updating … Pixel 6a devices to Android 13 for the first time
After taking an Android 13 update and successfully booting the device post update, an Android 12 build resides in the inactive slot […] Since the inactive slot contains the older bootloader, the device enters an unbootable state.
1 Like
my pixel has been on android 14 for months but… when i came to issues with trying to install e/os i downgraded it initially to android 12 then used android flash tool again to upgrade to android 13 so theoretically would that residing build still be there as i did not use the phone to update but i used the flash tool instead meaning it was erased including the super partition
this doesnt really help in my case (not trying to be rude) as i have done everything which he has said in his revised version of the install. I have had no issues with installing e/os on my sony xperia XA2 and Xiaomi Mi A1 so i do have a decent amount of knowledge when it comes to flashing roms but this just isnt making any senses
My recommendation is: First a clean install of ‘bluejay’ with stock Android 13.0.0 via Goolag Android Flash Tool
Select build 13.0.0 (TQ3A.230901.001, September 2023)
Additionally activate the options Wipe + Force Flash
Then try the installation of /e/OS-T V2.2 again.
wipe + Force flash are not options it is what the program does anyway and i have tried this 5 times now.
My Pixel 6 (oriole) upgrade from stock Android 13 to 14 was successful according to my specifications with the WIPE and FORCE FLASH options.
i have been told by my friend who is also someone who has tried installing custom roms on pixles before that it has something to do with the keys as the device thinks that a custom rom is being installed and so makes the command fail as it does not allow the dtbo to be written as it is not signed or something to do with that. I ave been told by him to wipe the keys but if i do this with the stock rom installed the device would brick itself as it has no clue what to boot into at that point so if anyone understands that better than i do can you please help
I have a suggestion :
Problems with version 2.xx are repported for some devices…
May you try to install latest 1.21 to see if it works better. Then you should use the system updater