Hook

Hope does strange things to perception. 😉

Thanks to @mosen, this link... https://www.protectionfilms24.com/article/2x-brotect-flex-full-cover-screen-protectorfxtec-pro-1-x-5145664.html

Sorry, we'll just have to agree to disagree. Where you see "intentional false information," I see overly-optimistic estimations, which, when they don't pan out, they get beat over the head with it. No wonder they kept communication less frequent until they got close to a real production phase. And of course hardware "quirks" would affect software, if the software has to use that hardware that is being fixed. My guess would be a that pre-production models went out in June. I don't know this, but that seems to be about when hardware tweaking was mostly done and the big concern was g

I assume you have gone to Settings, apps, Advanced, default apps and specifically set your "Home app" to Nova? I don't usually have to do that with Android 11 and before, but I did have to do it with Lineage 19, so I wonder if Google has changed something up.

Okay, an hour later 😄 ,,, The OTA update to the 20220615 nightly went smoothly (took the full hour, which is, sadly, normal). Has the 05 AUG security patch. Only odd thing is it added a second time and date widget to my Nova Launcher and asked me to set up Google (which I declined). Never seen those things happen after fist install. So far, everything seems good.

I'm trying this now just OTA. I'll report back my result (but you know this takes a while, lol). You mentioned something about a 3 part flash. I was getting that from AICP-S. AICP-R and Lineage has always given me a 2 part flash when flashing from recovery. Don't know if there's any relationship.

Might also see if @Sean McCreary has any clues he can give us.

For what it's worth, Key Attestation" on my Pro1 with Lineage and Magisk shows "Not supported by this device." Not a big surprise. It has had Lineage or AICP on it since early 2020 and I've never gone back to Stock, so of course I've never noticed. It will likely be the same with my Pro1x. I will probably keep it on stock until Lineage is available. I plan on using my Pro1 as my experimental device (read that learning device). If I find a setup I really like and is stable on the Pro1, then I will try to bring it to the Pro1x. I will see if I can backup the persist partition when I get

This is how it was with the Pro1. Took me a while, but then it became second nature. Lift slightly in back and push, as @brunoais mentioned, is easiest. I can now even do it one-handed (though I don't recommend that if you haven't done something to make the back less slick. I have a skin on the back of mine,).

I believe we do know the screen assembly is the same

First thing I did on my Pro1 in 2019 😄

Sure there is. Money. As @EskeRahn pointed out, what is said on the Indegogo pages should be changed. But all of this goes back to what keeps being referred to, appropriately, as "the swindle." The Pro1x was created to be a limited edition Pro1 with a blue case and an option for more memory. Lineage was already available and UT was close. They had secured and paid for the SD835 SOCs they were going to need. Then, they were informed that the supplier, who had been paid, was not going to give them the chips and, as an older chip, they couldn't find another supplier. So now, along with

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

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. 🙄😂

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 fl

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 c

@EskeRahn No joy (using the LOS 18 boot image you posted), although some things changed. When aicp-s was flashing it said only 2 parts, not 3 and did not announce itself as Android 11 at the end of the screen dump. However after flashing mtg12 and rebooting, I got the error screen again after the 7 boot loops. I tried taking the offer to factory reset (I did before flashing aicp-s, but what they hey at this point), but that just sent me to the bootloader where picking "Reboot to Revovery" just returned me to the bootloader, so somehow recovery wiped itself out on the factory reset. 😄

Okay, not too far rebuilding. Might try the experiment, just to see. Will have to be later tonight.

For this experiment, I used the recovery for Lineage 18 from 20220425 as that is what I had stored away in my archive. Newer than yours, but to be honest, I don't think it makes a difference. It's possible the recovery for Lineage 19 has more of a problem with AICP-S because it is more sensitive to whatever is wrong, so it could be that something that was changed later in 18 could be a problem.

I use the set of instructions I have always used, based on TDM, which I posted here and you have inked to in the ROM thread. They have always worked with me, including up through AICP-R. I double checked everything. I'm back on Lineage 19. Everything went smoothly and I'm rebuilding. There is something hinky about the files being supplied as AICP-S, I'm convinced. I'm staying away for now as I only have onePro1. 😄

@EskeRahnOkay, I think there is a real problem here. I noticed this time, watching tiny text on th ePro1 as "AICP-S" installs that it announces itself at the end of the run as Android 11. But I also noticed it has 3 parts to the install where, I believe (but haven't verified) that LOS and previous versions of AICP have all had two parts. When I clean install "AICP-S" with MTG12 (both with and without Magisk), at the final bootloop I get the recovery screen that says it can't load Android system. If I try "AICP-S" with MTM-11, the gapps of course, won't install. Whatever this thin

Okay, that was a weird and interesting result. I installed the boot image for LOS 18 (from last April). AICP-R with MTG11 (and Magisk-- I really don't think it muddies anything) installed smoothly and I did the initial setup including using my google account and got myself to the desktop. So I then dirty flash aicp-s, with MTG12. I get the 7 bootloops, but here is what is interesting. For the last bootloop, after getting a different AICP boot animation on all previous bootloops (I assume the S animation), I get the AICP-R boot animation on the last boot-up and it boots right into AICP-R w

Getting on it now. Will let you know what happens. 🙂 Do I need to go through the initial setup, or just see if it boots? Edit: Going ahead and doingh the most basic setup to take me to the desktop. That's it.

This was already posted as a separate thread. The email went to everyone.