how-to Setup Lineage OS on your F(x)tec Pro¹

[Slion 1,201]

I've put together a guide from knowledge I gathered over the last couple of weeks as I eventually got around trying Lineage OS on my F(x)tec Pro¹:

https://slions.net/threads/lineage-os-for-f-x-tec-pro1.90/

It takes you through the installation process from Windows setup to Magisk root and SafetyNet validation to working around prominent issues.
It will also take you through the build process from Windows environment setup to development and code contribution.

Also taking this opportunity to mention how awesome it is to be able to update, use and customize almost every aspect of you phone thanks to Lineage OS. Here is hoping that working together with the Lineage OS community of developers we will little by little keep getting a better out-of-the-box user experience on our F(x)tec Pro¹. I reckon I will soon be using Lineage OS as my daily driver.

Edited September 2, 2021 by Slion

[Hook 3,043]

Here is a guide I made for myself, edited from @tdm's original instructions.  It is a little simpler because it assumes you have USB working and all the fastboot/adb stuff installed, and that you know where to get everything.  It focuses more on just the actual flashing, showing both first time and updates.  Since I made these instructions for me, they don't include what to do with Magisk other than flashing the zip, since that is all that is needed for SU.  It may be useful for some in combination with @Slion's wonderfully detailed instructions of all the steps with all those many helpful links.

Or it may be just redundant after folks read the OP.  But it was a big help to me when I started out, so I just thought I would add it.

EDIT: I have eliminated this document as, at this point, I think it has some flaws and it doesn't match well with how Lineage sets up it's files.  At this point I recommend using the official instructions for the Pro1 or Pro1x located on the Lineage Website, links below.  They will be initially intimidating if you are a noob, but if you take some care and read and understand the instructions before you start doing things, they work nicely. 

https://wiki.lineageos.org/devices/pro1/install

https://wiki.lineageos.org/devices/pro1x/install

The nice thing is, if things change, so will these pages. 🙂

 

 

[EskeRahn 5,471]

On 9/2/2021 at 3:08 PM, Hook said:

When the update is complete, return to the main recovery screen, select "Advanced" and then
"Reboot to Recovery." This will switch the active boot slot.

I believe the last remark is not quite accurate. It is the flashing&install of the main image that also changes the active slot. Reboot to Recovery just boots to that.
If you do not want gapps/magisk/... a reboot from the main menu will also boot into slot B

[Hook 3,043]

6 hours ago, EskeRahn said:

I believe the last remark is not quite accurate. It is the flashing&install of the main image that also changes the active slot. Reboot to Recovery just boots to that.
If you do not want gapps/magisk/... a reboot from the main menu will also boot into slot B

Yeah, the semantics is off.  What is switched is what recovery indicates is the running slot.  I chose to make it a step that I always ended the install with a reboot to recovery so I wouldn't forget where I was.  😄

[EskeRahn 5,471]

2 minutes ago, Hook said:

Yeah, the semantics is off.  What is switched is what recovery indicates is the running slot.  I chose to make it a step that I always ended the install with a reboot to recovery so I wouldn't forget where I was.  😄

Yes, I guess it could be argued that it is a bug in recovery that it does not correctly reflect that installing an image might have changed the active slot, before a boot has been made.

[Slion 1,201]

6 hours ago, EskeRahn said:

Yes, I guess it could be argued that it is a bug in recovery that it does not correctly reflect that installing an image might have changed the active slot, before a boot has been made.

I wonder if you could just change the slot without reboot, from ADB?

[claude0001 1,352]

32 minutes ago, Slion said:

I wonder if you could just change the slot without reboot, from ADB?

You can, with fastboot.

fastboot --set-active=a

 

[EskeRahn 5,471]

On 9/2/2021 at 3:08 PM, Hook said:

Here is a guide I made for myself....,

In your guide it says that the step rebooting into recovery from within recovery "will switch the active boot slot", I believe that is strictly incorrect,
When I do that it says "active slot: a" (or b) NOT changing, I believe that the "apply update" from within the bootloader of the main flash that does the switch of active slot (without the header of the recovery reflecting this), and then the reboot to recover boots into that slot... Note that flashing e.g. Gapps, does NOT change the active slot, so it is part of the flashing the main 'only'.
So that a more correct wording would be e.g. "will switch into the now active boot slot"

[Hook 3,043]

5 hours ago, EskeRahn said:

In your guide it says that the step rebooting into recovery from within recovery "will switch the active boot slot", I believe that is strictly incorrect,
When I do that it says "active slot: a" (or b) NOT changing, I believe that the "apply update" from within the bootloader of the main flash that does the switch of active slot (without the header of the recovery reflecting this), and then the reboot to recover boots into that slot... Note that flashing e.g. Gapps, does NOT change the active slot, so it is part of the flashing the main 'only'.
So that a more correct wording would be e.g. "will switch into the now active boot slot"

Should have answered here instead of in the AICP thread... 😉

You are right.  The trouble with being more of a follow the recipe guy than deeply technical.  What I'm really talking about, and I will reword to make this clear, is that  I am simply going by what appears on the phone screen.  After flashing the update, it shows one slot at the top of the recovery menu (e.g., a;) and then, after rebooting to recovery, it shows the other slot at the top of the recovery menu (e.g., b). I don't know what is really going on under the hood, I just know you need to do the reboot to recovery after flashing the update if you are going to install Gapps and that the change in slot listed at the top of the screen is confirmation that you did.

So, I see, yes, the update has already changed the active slot, but you have to reboot to recovery to get recovery to switch to that active slot to make sure Gapps (and Magisk) are installed to the currently active slot).  Did I get that right?

I will post the revision later this morning.

[EskeRahn 5,471]

39 minutes ago, Hook said:

So, I see, yes, the update has already changed the active slot, but you have to reboot to recovery to get recovery to switch to that active slot to make sure Gapps (and Magisk) are installed to the currently active slot).  Did I get that right?

I will post the revision later this morning.

HA, I replied you in the other thread too....
EDIT: Cleaned up my mess, now point back here!

I'm pretty sure that is what is going on. I both tried to do multiple "Advanced", "reboot to recovery", and that did not change a/b.
Then did a new flash of AICP, and instead did "Advanced", "reboot to bootloader", and there "Recovery", and it also showed it switched, I do not know if there is any other way to get the Recovery to refresh it self than to reboot to recovery. But would be nice if it at the least gave a warning if you attempt to make a new "Apply Update", that it will NOT go to the (now) active partition... As I guess it is quite seldom you would want that.

[Hook 3,043]

2 hours ago, EskeRahn said:

HA, I replied you in the other thread too....
EDIT: Cleaned up my mess, now point back here!

I'm pretty sure that is what is going on. I both tried to do multiple "Advanced", "reboot to recovery", and that did not change a/b.
Then did a new flash of AICP, and instead did "Advanced", "reboot to bootloader", and there "Recovery", and it also showed it switched, I do not know if there is any other way to get the Recovery to refresh it self than to reboot to recovery. But would be nice if it at the least gave a warning if you attempt to make a new "Apply Update", that it will NOT go to the (now) active partition... As I guess it is quite seldom you would want that.

New version  of the pdf placed in my post at the top of the thread.  Made a bunch of revisions based on more experience.  Hopefully things are clearer, but I probably just corrected some problems and introduced new ones. 😄 I should just make it a todo list and take out all of the explanation. 🙄😂

[EskeRahn 5,471]

5 minutes ago, Hook said:

New version  of the pdf placed in my post at the top of the thread.  Made a bunch of revisions based on more experience.  Hopefully things are clearer, but I probably just corrected some problems and introduced new ones. 😄 I should just make it a todo list and take out all of the explanation. 🙄😂

Looks fine to me.
One minor detail. Flashing AICP, the 47% blah blah click yes is on the main zip, and does not appear again on the Gapps zip.
So Lineage and AICP acts slightly different here.

[Hook 3,043]

43 minutes ago, EskeRahn said:

Looks fine to me.
One minor detail. Flashing AICP, the 47% blah blah click yes is on the main zip, and does not appear again on the Gapps zip.
So Lineage and AICP acts slightly different here.

Yes, I noticed that. Next draft, I'll just make it a general statement, if anything complains about being unsigned, say yes.  😄