EskeRahn

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.

Bad news! This ALSO seems to hit stock Android 11 on the Pro1X 😭 ADD: Though it seems that unplugging and re-plugging here several times can suddenly bring it back to normal, so not as bad as what we see on Lineage. and AICP.

(For what it is worth, we might have similar issues with newer boot images for AICP-S for the Pro1, see this thread)

For a limited time I put up the old recovery image here. lineage_18.1-20210913-recovery-pro1.img

It might. See this post, though not on AICP

Thanks for the tests. Yes your guide is very close to what I do, also based on what TDM taught us. And indeed something sounds fishy. What is the recovery boot image you are using? And I also noticed tht the seventh boot is different. Already before the yellow AICP comes up, the 'flickering' of the FxTec logo is different. And it goes to a blue logo before it boots AICP (under some circumstances requesting a reset during the process),

....On the length of the name: I use a batch I call FlashAICP-S.bat, that only takes the DATE as the argument (in the yyyymmdd format), to avoid messing with the long filenames e.g. FlashAicpS 20220810 @%~DP0\FlashBase_MindTheGapps12.bat %~dp0Pro1_ROM\AICP_taken_from_lineage_18.1-20210913-recovery-pro1.img %~dp0Pro1_ROM\aicp_pro1_s-17.1-WEEKLY-%1.zip calling @if NOT %2.==. %~dp0FlashBase.bat %1 %2 %~dp0Pro1_ROM\MindTheGapps-12.1.0-arm64-20220605_112439.zip %3 (And obviously a number of similar one-line batches for the other combos)

@Hook Are you sure you are flashing to the A/B you are booting into? I use the below bat, to do stuff. Notice the a in these two lines: fastboot flash boot_a %1 fastboot --set-active=a (I assume they could just as well both have been b, and that the important thing is that they are equal) @ECHO off if %2.==. goto :EOF ECHO * Wait for boot to bootloader to finish (or do manually holding VolDown+Power) adb reboot bootloader pause echo * sending %~n1 fastboot flash boot_a %1 shift fastboot --set-active=a REM fastboot reboot recovery does not work, so do manually

....And if it does not work, and you have more time to spare,please try the gapps-free AICP-R -> AICP-S , thanks 🙂

Yes, please do the full optimistic dirty flash, that is AICP-R + MTG 11 -> AICP-S + MTG 12, if that works we are 99% sure a gapps-free AICP-R -> AICP-S would also work.

As well as LineageOS 19.1 and AICP-S (And the box can even be navigated in with arrow-keys and selected with Space or Ente plus Esc for cancel, if you want to avoid touch)

If you are Gapps-free, please start on AICP-R so we will know if it can upgrade to S without a reset. I suspect that it is OpenGapps, that blocked my attempt,

See ANOTHER THREAD for WORKING AICP-S :

AICP-S 17.1 for Pro1 ADD: They have broken AICP-S so it does not work at all in the versions available, even after extracting the boot.img from the zip it self. See my post later in this thread 2023-04-05. They had a few versions that worked (almost) though, the last being aicp_pro1_s-17.1-WEEKLY-20220914.zip . --------------------------------------------------------------------------------------------------------- New version of AICP-S 17.1 based on Android 12 is available for download here: https://dwnld.aicp-rom.com/ aicp_pro1_s-17.1-WEEKLY-20220810.zip It is VERY

Correct @Casey just confirmed it a quarter ago 😉

(OpenCamera supports it too, but obciously this is Pro1 and not Pro1X)

Tried with the old boot-image from lineage 18.1 20210913 (That is the one I used for AICP-R!), with a reset, got he bootloop and request for another reset BUT the splash screen is gone!! So DO NOT use one for 19.1 though it matches Android 12, Use the same as for AICP-R (matching Andoid 11) !! I will update this thread accordingly... (Or parhaps make a new one, closing this done...)

Just tried to reflash starting with the 20220426 boot-image from Lineage 19.1 - required a factory reset, but the same splash screen non the less...

The Pro1X in blue, would make it easier to keep track on which is Pro1 and Which is Pro1X... 😁 I currently have one retail Pro1 I bought, one final sample Pro1 and an early preproduction Pro1. And today got a 'verification sample' of the Pro1X (black), and will (hopefully soon) get the retail Pro1X I perked for...

It most certainly can! 😄 I have been using it since 2019... See e.g. the slo-mo video where I use one from the 'open' thread here. I have a lot of blah blah in this thread in my blog, and we have a long thread in here as well. Sure it is DIY, but we are talking a few minutes of work that anyone can do (no special skills required at all) YouCut_20200123_155044091.mp4

It is a bit odd that there are no more security updates on AICP-R, since June. And on the other hand the security patch level for AICP-S is March, so I guess they see S as still in development? I would also like to know if it is me that are doing something wrong or they see the same splash screen? Should I e.g. use a different boot-image than I do? I copied the most recent boot-image available at the time of the first AICP-S: lineage-19.1-20220711-recovery-pro1.img should I use an earlier or a newer? (I have saved a few older 0426, 0502, 0530, 0627)

Flashed today's release aicp_pro1_s-17.1-WEEKLY-20220810.zip, Security patch March 5 and MindTheGapps-12.1.0-arm64-20220605_112439.zip (without factory reset) And it is the same error as above. Boot-loop some ten 10 times, , Boots with error screen, and all seems to work, except this splash screen on each boot. (But to make things clear, it is 'only' on the first try after flash that it requires a reset)

Interesting that there should be a difference there, Note that not all camera apps support the half way click. But yes it work, it just takes some getting used to that when the button is pressed slightly and is thus 'free' betweens its in and out position, it is in the 'halfpressed' state. I have seen some compact cameras working in the exact same way.

Correct. IF we could get a fully covering 3D-curved tempered glass protector (as was/is available for e.g. the BB priv and Samsung S8) Then you can be lucky that it takes the impact and scatter, leaving the display intact. But I have not seen those available for the Pro1 or the Elephone U using the same screen. I tried to cut one for a S8+, but it is really hard to cut it without it just scattering, I tried to cut a couple (using a diamond glass-cutter) to no avail, and then tried to make several cuts shortening the remaining to practise - I never succeeded

If there is no OS it find as bootable, you'll need this bootloader screen to fastload a boot image, and EITHER fastload the rest too, OR boot into the recovery mode from the bootloader and "adb sideload" a zip file with the packed images (the zio is how e.g. LineageOS and AICP usually is flashed)