Hi !
I already installed e os on a samsung, and it was almost easy !
but now I am trying to install it on a shift6qm, and I am stucked at the beginning !
On the fastboot mode, i have :
DEVICE STATE - locked
Git bash can’t see the phone.
So I tried to unlock it with adb > fastboot flashing unlock
But it say “waiting for any device”
you probably miss the fastboot driver for your device,
open the “windows device manager” (with the phone plugged, booted in fastboot mode)
in the list, select the device with a yellow triangle,
launch a windows update…
So you installed this Universal ADB driver the install guide links to? I was interested in whether this works, because I’ve only seen ADB and fastboot drivers being separate drivers on my machines, and this driver claims to be both, ADB “(and fastboot)”.
Sounds not too promising then, but they don’t claim that it would work for every possible device either.
Here’s an animation for this generic process from a Fairphone support page (vendor doesn’t matter in this case) … the phone has to be in fastboot mode when connected to the computer for this to work … and mind that the drivers to install get listed in “optional updates” …
Yes I installed the universal ADB driver but it didn’t seem to work !
But thanks for your animation, it worked !
So, I could do the “fastboot flashing unlock” with ADB.
And I could instal the OS with Git Bash…
BUT : another issue is coming !
GIt bash says :
“INFO: Done. The device will reboot now.
Rebooting
Finished. Total time: 0.000s
INFO: You can unplug the USB cable now.”
But on my phone I have the e recovery screen saying “Can’t load android system. your data my be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device”
Hi, I actually have a last issue…
When I restart my phone, I had a message telling me to relock the bootloader, I forgot to do it !
So I went back here : Install /e/OS on a SHIFT SHIFT6mq - “axolotl”
and I follow the last part “Locking the Bootloader”
but when my phone is on fastboot mode and I type the command “fastboot erase avb_custom_key”, I have this message back :
Erasing ‘avb_custom_key’ FAILED (Write to device failed (no link))
fastboot: error: Command failed
And not relocking has security implications.
It’s a case of pick your poison.
Are you sure you are in fastboot mode and not in fastbootd when you try this?
(Somebody in the Shiftphone forum reported such an error message when in fastbootd instead of fastboot mode.)
Does the fastboot devices command find your phone?
I read your both messages too late ! It finally worked :
I was in fastboot mode and it doesnt work. I rebooted in fastboot mode again, and it worked…
I thought it was too dangerous to not relock. What are the annoying aspects @piero ?
you cannot install root permission availability without wipping the /data partition.
you cannot replace the actual custom recovery by another one without wipping the /data partition.