DieBruine

Fingerprint issue was a stock thing as far as I know (and experienced).

Flash LOS and you'll be much happier 👍🏾

I would be very happy with half a bumper for just the back tailored to Pro1-spec instead of P20 Pro 😑.

Yeah, well with less than 2000 devices out there, we won't get any cases soon. Which is pretty strange since I'm pretty sure the factory should have some shells they could hand-off to the any of the manufacturers within a square mile...

My bad... I hope. I forgot to run adb root 😅. Now I will reboot and hope everything is fine... Give me a couple of minutes. After a reboot my fingerprints are gone again. Unable to find nor delete /persist/data/fingerprint. Which was completely my mistake. I forgot to run adb root 🥴 rm * /persist/data/fingerprint did the trick for me... Thanks anyway for the response. By the way, are there plans to enable unlocking before boot back in LOS? I think it was removed in 14.x.

Keep pressing volume down+power and do not let go until you see the Fastboot mode (should take about 10 seconds). After that start all over again. fastboot devices (to check whether it is connected) fastboot flashing unlock (error already unlocked) fastboot flash boot lineage-16.0-20200803-recovery-pro1.img Volume Up + Power Perform a factory reset in Recovery Apply update via ADB sideload adb sideload lineage-16.0-20200803-nightly-pro1-signed.zip Reboot to Recovery if you want to flash gapps adb sideload MindTheGapps-9.0.0-arm64-20190615_0

Why test? Do you mean 17? Or just nightly? Anyway, nice to see you succeeded!

These two: https://www.ebay.de/itm/254181243108 And yes the P20 Pro versions. The first one is pretty thick. The second one feels thinner but also cheaper. Nonetheless, it (2nd) will fit the Snakehive and suit it well I think. I'll probably just drill a small hole in the back for the NC-mic on the back. And afterwards maybe use some epoxy or something alike to protect the hole. I'm certainly not going to sow that small hole as Snakehive has done 😅. I am still using the second one (Ebay/right on in the picture below) because overall it's thinner. I think it is 0.6~0.8mm thinner. And I

As I stated in the other topic. When you used the instructions on Lineage, the unlock command should be fastboot flashing unlock. I just received a Pro1, booted it and it was already unlocked. So there was no need for that. To help you figure 💩 out, I used a different clean laptop. I installed everything as described on https://wiki.lineageos.org/devices/pro1/install. After installation and connection via ADB, I changed the driver manually to "Google Nexus ADB interface". I don't remember which one was selected, but it sure as Hell wasn't Google Nexus ADB interface. So as _DW_ stated, ch

If you order and use a bumper case, for a P20 Pro, you just have to touch it gently and it will slide open...

Yeah, but this issue was valid on stock. And it continued on LOS. After reboot, fingerprints are gone. I'm not the only one.

If you don't like it, I'm pretty sure you can sell it without any loss 😉 I am very happy with mine. And I'm sure the rest of my family and friends will. As soon as the rest is delivered.

Fuck You FxTec, really Fuck You. pfff one deliverd out of three.... Edit 1: I let it get the best of me. But, I'm still very disappointed and angry right now. Edit 2: So, lightning fast response... Apologies (accepted) and tracking info on the additional phones within the week. I will keep you informed.

Delivery scheduled for 18:00 today. Still 1.5LBS / 0,68kg 🤬

@tdm Did you add the rm /persist/data/fingerprint tot the new nightly? I ask because I'm having the same issues with my fingerprints being forgotten. I tried rm /persist/data/fingerprint via ADB. Permission denied is what I got. So just to be sure I sideloaded SU-arm64 and searched for /persist/data/fingerprint.... Nowhere to be found. Which is why I'm hoping you added your script. Otherwise I have no idea what's happening here. I will add my fingerprints and reboot again, see what happens. After a reboot my fingerprints are gone again. Unable to find nor delete /persist/data/finger

If it's a DHCP issue, you could try fixed IP. Under WIFI settings on the phone apply the IP, subnet mask, gateway and DNS you used for the reservation. If you don't know what that is and/or cannot find it. Just use the IP, subnet mask and use the router's IP address as default gateway. For DNS use 1.1.1.1. That's an easy way to rule out DHCP issues. You can change these settings when you modify a known/saved WiFi network on your phone. BTW, your basic logging on the router should at least show password incorrect/rejected and a DHCP request from your phone...

If possible switch to 5GHz only. I had a similar issue on my provider-provided-router, but only on 2.4GHz. I have tested it on my Ubiquity routers, no problems there. But that whatever-brand-it-is-router, that one made my phone reboot. I alway make a distinction in SSID between 2.4GHz and 5GHz. Also, my 2.4GHz network is fixed on channel 1 and 20MHz. No reboots since (Ubiquity).

Since our phones are on the way I took the liberty of unpacking the Snakehive wallets as suggested (by Slion) in this topic. Pffff those bumpers are a real piece of 💩. First of all, the phone doesn't fit very well. Apart from that, it's the lowest quality silicone I have ever dealt with. I started modding all the current and required holes with a Dremel. These bumpers have some flex! It took me hours to mod them. But, I still don't trust them. The phones come out to easily. So, I've ordered the Ebay bumper noted earlier by EskeRahn, which I also purchased previously. For the time being I

Yup, same for me. 18:17 moving again. Well I hadn't noticed the 5 hours delay on Saturday. So it doesn't seem all that strange the delivery will be delayed by at least a day. It was destined to arrive at the hub at 23:00, not 04:35. You can't expect a delivery as promised when it's that late. I'll be expecting it tomorrow. It's a 5 hour drive to my local hub. So fingers crossed for delivery tomorrow.

My point exactly... It should contain three! 😑 I'll keep my fingers crossed.

Mine changed from 18:00 to unknown. Someone mind telling me what your shipment weight is? Mine is 1.5LBS. That doesn't compute.

Check EskeRahn's response...

Have you tried "fastboot flashing unlock" again? And does your phone still boot? If so, check under Developer options if Android Debugging is still enabled. Otherwise my next suggestion would be to contact support.

Before you flash issue :"fastboot -aa" or "fastboot -ab". This should set your active slot to either a or b. I had a similar issue with my friends FairPhone 3 couple of weeks ago. You can issue "fastboot getvar all" to check the current active slot. The output somewhere in the beginning should state "bootloader current-slot = a/b". When I experienced similar issues on the FP3, the current active slot was "-". After I set it manually I could flash the phone again. And maybe, just maybe, LOS will flash now. Check if you have an active slot. Because that (not having an active slot) would exp

Which for me does not work! It won't update. I will try from recovery. Edit: So after a manual reboot (wasn't prompted for reboot), my phone was updated to 0803. Weird behavior if you ask me 🙂