does not return a device.
Amongst others, the command
adb shell
returns ‘error: no devices/emulators found’.
I did enable USB debugging.
Although FP2 is connected to pc, windows explorer (WE) does not show a FP2 node
(when connecting my nokialumia I’m used to seeing a node for it in WE).
I don’t know it this is related to the somewhat instable FP2 (FP Open OS ).
How can I make sure ADB recognizes the FP2 when connected to pc (through usb)?
Cheers,
AbangL
PS. Somewhere along the way I somehow got the TWRP-screen on FP2. At that point I was called away and when I returned the screen was gone, FP2 switched off.
This is normal. You should see the phone in Explorer once you select MTP as the USB connection mode instead of Charging (which is the default for security reasons) on the phone. There should be a notification to tap to get to this choice.
As for the adb command … can you boot into dic:fastboot mode with the phone connected to the PC and check whether the command fastboot devices finds your phone?
This should show whether the connection isn’t there or whether ADB needs further investigating in Windows.
Today I gave it another try, but no luck ( start to be like work a bit ).
I did learn that #dic:fastboot is the link to the fastboot entry in the dictionary, here on this forum. .
I did reset FP2 to factory settings.
In FP2 settings I set USB debugging on an USB transfer mode to MTP.
I opened several dos-boxes, as Admin.
And I did manage to reboot with fastboot.
On windows pc, in device manager, under ‘other devices’ node, I see one node ‘FP2’.
This node’s icon has a yellow triangle with an exclamation mark in it.
Under properties I see that no driver for this device is installed (Dutch “De stuurprogramma’s voor dit apparaat zijn niet geïnstalleerd. (Code 28)”).
This here was done because MTP didn’t work when TWRP was booted, but it could serve as a generic driver repair … (ignore the TWRP part and just boot the phone) …
So, several hours down the line again,
again no luck.
Pc and fp2 have been rebooted several the times the later in recovery as well as dic:fastboot mode (also know as #dic:bootloader mode!).
Tried not to forget to check whether fp2 was in usb-debugging mode and that usb-mode was mtp. In case I forgot, went back and tried same step with these options properly set.
On pc wiped all programs that had adb.exe and/or fastboot.exe.
Downloaded latest Android SDK platform tools.
Installed twrp.img (twrp-3.3.1-1-FP2.img) again.
In the properties of lineage-16.0-20200209-nightly-FP2-signed.zip I removed some security blocking
( in Dutch “Dit bestand is afkomstig van een andere computer en wordt mogelijke geblokkeerd om deze computer beter te beveiligen”, so it was blocked to since it came from other computer for security’s sake of my pc ).
The command I used was : adb sideload C:\temp\lineage-16.0-20200209-nightly-FP2-signed.zip
On FP2, recovery (right?) mode the screen looks like this:
{yellow text on a black background} Android Recovery Fairphone/FP2/FP2 7.1.2/19.11.2/sibon-24df0be9 userdebug/release-keys Use volume up/down and power.
{/yellow text on a black background}
{blue text on a black background}
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Mount /system
View recovery logs
Run graphics test
Power off
{/blue text on a black background}
Is that where I disable Signature verification in TWRP’s settings?
Redownloading is possible, I’ll try that.
My wish to have a working FP2 compelled me to change that setting.
Now I know it has no effect I won’t do that with the newly downloaded file.
What you describe is the stock Android recovery, not TWRP (see here for some TWRP screenshots).
You could try that again. Make sure after installing TWRP to directly boot into TWRP to let it make itself resident. If you boot Fairphone Open OS inbetween, it may replace the new TWRP with its own recovery again.
In Install LineageOS on FP2 | LineageOS Wiki this is point 6 in “Installing a custom recovery using fastboot”. Don’t miss it.
).
.
