EskeRahn

This is one possibility: https://www.indiegogo.com/projects/pro1-x-smartphone-functionality-choice-control/x/16576339 though they do not expect to ship before March. Note that the campaign ends in less than a week!

I think you should try to find some USB2. Perhaps a USB2 hub, between your newer pc's USB3 port and the Pro1

Indeed. I'm guessing here but they could have a person with rather limited tech-knowledge scanning mails versus an internal FAQ list with predefined answers, thus speeding up response times and also freeing up more knowledgeable staff for more complex tasks.

Formatting the card in a pc to exFAT, and it works fine it seems. If I choose to to reformat it in the phone, it is formatted back to fat16 (not FAT32). Though formatting to FAT32 on a pc, that is supported too.

....I found a (by 2020 standards) small 1GB card, formatting does not ask about what format. It formats it as "vFat"

This installed smoothly, thanks. 👍 I will see if I can find a sufficient empty card to test. 🙂

Interesting. I wonder if the priority is higher with the 17.1 implementation when "priortise update processs" is deselected? Or have you enabled this?

Forgot that it is supposed to do incremental now, so flashed back to 20201130, and tried OTA, and it only presented me with a 720MB full package, so will manually flash it to 20201207.... 😒

(lineage-17.1-20201207-nightly-pro1-signed.zip on November security patch installed smoothly using adb sideload)

Well for my part that is what I feel. The issues I experience are all pure software. (though I have improved it with a few strategically places tiny self-adhesive rubber stickers) But sure as many have stated there are faulty units (would have been a miracle otherwise), but the handling of those certainly seem like it could have been better. And the same goes for the software bugs. But as they are a dedicated team I do still believe the later will be ironed out. Also remember that a forum like this will always present a disproportional amount of bugs, as people (for obvious reasons

I tried the new again both with and without sim+SD inserted (same result) and flashed back to 20201114 (that works fine)

A new download gave same files, and a new flash with newest opengapps nano (20201205) give the same result. It is still on Q, so Wipe should not be needed, right?

The 20201206 seemed to flash smoothly. But it was over ten minutes in the boot state while displaying the animated aicp logo.... (I did not wipe, and flashed the same opengapps nano from 20201119) So tried to restart it again - same result.... Reflashed - same result. Have downloaded newest opengaps, and will try again.... ADD: Reflashed back to 20201114, and it rebooted normally within a minute. Will try to download again, compare and flash the 20201206 again

But it is still very relevant as I bet that quite a number of (potential) pro1 owners have (had) a Priv too. I for one bought the Priv back then as the least bad available keyboard slider - despite its keyboard being in the wrong direction.

It is generally very hard to take good images of light. Taking images of light shinning on something is much easier, but that is not really relevant for what you are asking. I guess it ought to be possible to make a set-up with the light shinning through a suitable small thin piece of paper, I have tried that too - but not with a usable result either,

Keep my fingers crossed. As some are saying that the loader thing is very picky on the ports and cables, I would not be at all surprised if too old/slow could also posse a problem, as USB2.0 is newer than 1997, so most likely it is USB1.X

Try some of the hardware suggestions. Perhaps an old usb-hub nut supporting usb3.

I do not see this. (Also using K9) Perhaps clear the cache of swiftkey, or even uninstall and reinstall swiftkey if it really has messed it self up.

(I split the posts on Lineage 18 into a separate thread here)

I think we better tag @Waxberry here, I just naïvely added the link to the August package in the OP. Other things in the guide might need to be adjusted too. e.g. I guess it should have one (and not both) of these (I do not know which) fastboot set_active a fastboot set_active b and/or fastboot --set-active=a fastboot --set-active=b ...But I'm a noob here, others have to help here

Note the @tdm reply in another thread:

No, that is the way I deliberately can put it in this mode. 😉 My wild guess was if your volume keys (seen from the phone) appeared as being constantly pressed, that might prevent it from ever trying to boot. Pocket lint that crept in could be an issue, so that is why I asked if they felt moving 'normally'. (And positive sign that it charges with 1A 5V too, that is totally normal, and reduces when above something like 90% charged)

(merged the two threads)

Just curious. Any particular reason for not upgrading to 17.1 ?

As it can be seen from a computer as in loader mode, I would say that it is very unlikely that it is the USB-port. And as you reported it as 75% shortly before becoming unavailable, I do not think that it is (or at the least not was) depleted. Why you are not allowed to flash it once it is connected in loader-mode is really beyond me. My best suggestion would be to follow the advices from others and try from different computers. (And/or with different cables) Especially slightly older computers with a USB-2 and not USB-3 port, as I repeatedly seen this reported as helping others. (gene