first minutes in the game and I already failed the fist test. I tried installing e-OS on my Fairphone 5 by following all the instructions. There are no more Google, WhatsApp, Signal, … accounts logged into my phone anymore, USB Debugging is active and switched to “Data Transfer”. The Computer even recognizes the phone and I get the Popup window with the PC fingerprint which I accepted. However when I click on “connect” I only get this prompt:
Error on step: device-detection
Cannot execute command connect adb
The device is not connected Failed to connect: Cannot connect ADB Cannot read properties of undefined (reading ‘deserial’)
Proposal: Check connection and that no other program is using the phone and retry.
and nothing else happens.
Any Ideas what might be causing this issue?
Kind regards and thanks in advance,
Lasse
So you say the next things I should try are:
A) Try another USB Cable
B) Reboot the device (how do I do that exactly? Lets Pretend I have no Idea when it comes to phones
C) How do I check my security patches and what do I do if they are newer than the current /e/OS version?
Und sprichst du womöglich auch deutsch? Wild guess wegen der Flagge neben deinem Icon.
Yeah, it looks like the phone is not recognized. Check first in this order.
Is a driver needed to be installed if you are on windows.
Then check cable and if the USB port is good.
Regarding security patches, check in the System settings in the device info which month it is.
Jepp, Deutsch geht aber du hast auf English angefangen.
For use with Windows, the “MTP” driver required by ADB is built-in, no user action is required other than plugging in the phone. If you see the phone appear in File Explorer, the connection and driver is working.
Fastboot requires a different driver that is not built into Windows. It should fetch it automatically from Windows Update when you put the phone in fastboot mode, but it may require manual intervention. Regardless Windows Update can handle the driver either automatically or manually.
There is one gotcha with USB debugging in that the phone needs to be awake when you plug it or you won’t see a prompt on the phone screen to enable it. If you select “always allow” the first time it won’t ask again, but the phone still needs to be awake for USB debugging to activate. I would suggest setting a longer screen timeout. Also you can set the default USB mode to file transfer in settings so it won’t ask about that either.
It worked! It was really the cable situation. My MacBook seems to be a little funny when it comes to how the devices are plugged In. I have to charge the laptop with the original USB-C cable and plug in the phone with a different cable. I don’t know why but I could have guessed, since this problem has already occurred when flashing other devices with custom firmware.
So in the end it all worked out flawlessly, except I forgot saving a backup of my contacts. A small price to pay.
I only have one more question: When I switch the phone on I still get the information my boot loader is unlocked and thereby ab security risk. I already disabled the OEM-Bootloader option in the settings again, however the prompt doesn’t disappear.
Is it recommended or even possible to lock th boot loader again or ist that prompt just part of the deal?
Could be kind of rare in the wild, I guess, but there are official Windows versions out there without the Media Player components necessary for MTP, called Windows N.
When you install with webinstaller then the ‘official’ build will be installed. ‘Official’ is also installed on devices from Murena which are sold on the shop.
With thoose devices the bootloader is locked since major updates will come with OS OTA Upgrade.
There is also ‘community’ build with which bootloader can’t be locked but you are more ‘hands on’ with updates or upgrades.
You can lock your bootloader also at a later point BUT all data on it will be lost. Please inform yourself (everything is discussed almost daily, there is alot of information) what you prefer, there is now right or wrong. Depends on the point of view I would say. Just pointed out some things which would be relevant for you right now.
Thank you so much for all your help. I guess I will leave the boot loader open then, since you also don’t seem to be that concerned about the system security.
Locking the bootloader is available only for official builds. Those builds are limited to a fairly small number of models which include the Fairphone. If using a community build the bootloader can not be locked.
Locking the bootloader is done from a Fastboot command, but there’s some caveats with that. Check the anti-rollback warning in the command line instructions.
You can leave it unlocked, the only real issue you might run into is apps with high security may reject an unlocked bootloader (such as some banking apps) In general its pretty rare you’ll run into an app that gives you problems that way.
I think people are a bit paranoid about the warning. There really is no appreciable security concern. It allows someone to install an image if your phone gets stolen, but doing so is going to wipe the drive.
