While using eOS v1.5 R on my paid FP3+, I wanted to use eOS on my wife’s Shiftphone Shift6mq, which is supported by Murena.
It was the first time ever I open a command prompt but I figured out how it work to command the phone from there. I followed the guide attached to my device. The device was found with the command “adb devices”. Then I needed to run the “adb reboot bootloader”, which was a success. But then, from the fastboot mode, the device is not found anymore and the command is waiting indefinitively for a device. The device is for this reason still locked
I tried to update the Android drivers but nothing is ever found (and I didn’t as well on the web). The adb/fastboot are up to date from the link provided in the documentation. Really, I don’t know how to continue. But I’m keen to try if any one could be of some help. Ah and I’m running Windows 10.
“Waiting for device” might be different from the conclusion that the device is locked, idk … but you might use Windows device manager to ensure you have fully dealt with the drivers issue.
You may be of some help with this question : when I’m restarting the phone, it says that the phone is unlock. I don’t have such message on my paid FP3+. Do I need to relock it via Command Prompt and is it not possible in order to run eOS properly ? I’m not sure .
In addition, I did not have always the same message as described in the installation guide. Any clue who / how could I forward my own experience to allow others to benefit from it ?
Good to hear that /e/ installed successfully for you.
The install instructions would include the instruction to lock the bootloader if both the device and the /e/ ROM were suitable. In the case of this phone relocking the bootloader is not included and it would be a mistake to try. You cannot currently relock the bootloader on this device when the /e/ ROM is installed.
FP3 is one of the few phones where relocking the bootloader is available for /e/.
Another significant thing is that Android requires that the device announce when the bootloader is unlocked. On some device one might see something like a little padlock sign, on other devices it might be a much more intrusive text based warning.
I was talking about this message “Script succeeded result was [1.000000]”. In the guide, it says that a message similar to this should appears while the installation is completed. In my case, i just got a 1/2 followed by 2/2 and nothing else. I founded hard to be sure the package was installed completely or not. Furthermore, while going back, within the eOS Recovery, the Command Prompt windows showed something like “installation 0.” instead of the descripted “Script succeeded result was [1.000000]”, which as a beginner, is a bit confusing. Even if everything went well and I’m happy for it !
I guess this is a feature / bug of adb. One difficulty is that adb has to be able to work across many host PCs and many Android devices. The important thing is that the actual data was transferred successfully bur perhaps the exact “acknowledgement” return signals are not exactly interpreted.
A response including
something like “installation 0”
does include the UNIX concept that there was no error, but the longer wording on the install page details a set of responses to a script.
.
.