EskeRahn

There is a difference between "Enter Fastboot" and "Reboot to boatloader". I'm pretty sure you want the second

Ah you youngsters. started before there was dos. 1KB memory + plug to a TV and a tape recorder. (ZX81) A few years later I had the first PC with not one but TWO floppy drives so I could have source on one, compile to another, swap the first, and link the object-code back to the first drive. Later that was upgraded with what I saw as an almost infinite big harddisk - it was a whooping 10Mb 🤣👴 👴

as I have not have found the time to install something else on the unit, I fetched and installed 20230118. Same issues as earlier. (including finite boot loop, still reverted to Android 11, and despite changelog claims otherwise still old security stamp)

(lineage-20.0-20230123-nightly-pro1-signed.zip on January 5 security patch installed smoothly using adb sideload and MindTheGapps-13.0.0-arm64-20221025_100653)

Thanks for the info, perhaps I should have guessed from the name that it was a fishy political stunt.

Just saw this on a new allegedly very clean AOSP fork BharOS. Would be interesting, if some of the hardware related stuff made for LineeageOS for Pro1/Pro1X could be reused.... So we could have that too - I bet that at the least some of the old Blackberry users would be highly interested. EDIT: See below, most likely merely political stunt...

A few has, but it is not a fast process, see the IGG update a few comments above (merged you post in here)

It was about half a year between we saw the first unofficial v16 for the Pro1 to an officially released 16.0. I have no idea if that is representative or not. I hope that at the least some logic (e.g. around the keyboard) can be reused from the Pro1, and thus simplifying the development.

(lineage-20.0-20230116-nightly-pro1-signed.zip on January 5 security patch installed smoothly using adb sideload and MindTheGapps-13.0.0-arm64-20221025_100653)

Lineage usually do not publish images at early stages, as I understand it.

Good news that alternative OS development are still progressing. I had feared it was stalled awaiting the stock fixes.

Indeed frustration. The newest we know is this, that @Scoopy quoted on IGG

Please note that drivers also matters. It is a puzzle really to get things working, we have other threads on it in here...

I'm not even sure it is USB2, it was a tiny Chinese 'no-name' thing I bought ages ago. Looks like this one: https://www.skout.com.au/item/80001544 (less the branding) I think I found it on ebay.... ...But can not recommend it, flashing was REALLY slow.

Indeed. I do not know if you are aware of the full story, but the Pro1X was originally intended as a slight variation of the Pro1, with more ram and in a blue cabinet. FxTec was swindled by those they ordered and paid the 835 chipset from. And it was impossible to source them elsewhere as Qualcomm had stopped production, so they had to redesign the whole inner phone for a different chipset. And as one side effect the existing software will not work on the Pro1X as it ended.... If your question is how you can support LineageOS development, I guess you should start here, if you mean finan

I found it impossible to flash directly from my "Lenovo Thinkpad Yoga X1 Gen6, 20XY", BUT if I let it connect through an external HUB, things suddenly works. I both tried an ancient cheap one I had in a deep drawer and ports on the Lenovo Thunderbolt 4 Docking. All works. (the cheap old one was USB1 I guess, the flashing was extremely slow - but it worked...) So my first suggestion would be to try a hub (and/or different cables). Some screens got a build in hub, if you have not got other alternatives. If that does not work either, try to look for an older hub, to make sure it is plain a

(Split @CornholioGSM's hint on 20.0 for original Pro1 to separate thread here)

(lineage-20.0-20230109-nightly-pro1-signed.zip on January 5 security patch installed smoothly using adb sideload and MindTheGapps-13.0.0-arm64-20221025_100653)

I certainly hope so - or that they got the 'drawings' so that they can have them produced. It is very likely that most of us at some point will need it for our Pro1. That is unless there will be a successor we will buy and use instead.

For some odd reason a 'factory reset' is needed after the flash of stock.

Odd that they did not have those as a spare part on IGG. Be aware that that the port is NOT at the same position in the frame for pro1 and proX (sits higher on the X), so MIGHT be different pcb as well.

Awesome you got it working too. It would be great if someone would combine this in a step-by step guide, for future references for others (I will add a link to it in the main flash post) (It does not have to be super detailed, just with the steps that are not obvious)

(I merged the two threads, with edited title)

Thanks for that, I copied this into @Casey's post (as comments are disabled, even for a moderator)

They made an official guide here https://community.fxtec.com/topic/3643-pro1-x-flashing-stock-android-with-qfil-windows-pc-only/ It is a bit complex. There might be easier ways to do it, but unfortunately there isn't (currently ?) a simple version with a zip file (like the one you used for the Pro1 Lineage), I have asked for that, and hopefully we will get it at some point...