EskeRahn

I Just tried to reflash AICP-S on top of AICP-S, with NO factory reset, and this goes much better, though not 100% smooth. It still enters a boot-loop attempting to boot after the flash is done... BUT it eventually DO boot into AICP-S with things preserved from last time. 😁 It still present the splash screen that something is terribly wrong on boot... BUT after that, things seem to work fine (until you do the next boot). 😁 So though severe bugs they are NOT show-stoppers any more. You will still need a factory reset going from AICP-R to AICP-S, But though sad, that is

I personally use the below batchfile on Windows to help myself doing things correctly, without forgetting something. Called with two parameters. [1] recovery image to flash and [2] the main zip to flash. Followed by other packages needed, e.g. GAPPS. LineageOS supply both as a pair, for other OS it might be different. @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 %1 fastboot --set-active=a fastboot flash boot %1 REM fastboot reboot recovery does not work, so do manu

Welcome on board 🙂 I have not got a Pro1X my self (yet), but from the Pro1, indeed the software is very close to stock Android with only minor differences for handling the slide out and the keyboard, and a few other details. And I expect the same for the Pro1X For the Pro1 we need to use the Yellow arrow (fn) key, to access the yellow symbols. I expect the same goes for the Pro1X. How FxTec handled different language layouts this time I do not know, but I expect we have got rid of the odd problems related to the letter shift of the original Pro1 qwertY layout. But do not know yet.

I use the one linked next to the large zip here: https://download.lineageos.org/pro1 I always download both (it is quite small), though they are not identical, I expect they might work within he same android version , I use a batchfil to remember the right steps. See the comment here https://community.fxtec.com/topic/3207-various-roms-available-to-the-pro1pro1x-available-for-download-links/

Thanks, link added to

Apart from the obvious of writing to FxTec, I would suggest that you also contact FedEx and have them halt the parcel, so it is not delivered, until things are cleared up. Then Fedex can contact FxTec, and have them contact you to verify the typo. Unless someone with the same name live at the other address, I assume Fedex will be cooperative in clearing up the matter. For obvious reasons they are unlikely to just take your word for it, unless you got a really unusual name.So they will have to verify backwards to the sender, and worst case return it..

We do not know how big a part of batch 1 FedEx actually have processed yet. So we could still be in Batch 1 without knowing.. In the 'voting' less than a score has 'voted', and similar numbers posted on IGG (of whom some can be the same) so likely only a fraction of batch 1 have got the mail yet.

Well the difference in delivery between first and last within batch one was likely expected to be in days, so hardly worth the trouble, to split it further. As so many times before this project was hit by unexpected delays, this time of the shipping out being slow..... The main point is that all the old orders should be handled in the first batch, so handled before the majority of the IGG perks. I doubt that FxTec has any influence on how Expansys/Fedex handle stuff in their queues, including the order. Most likely they handle stuff from various sources to the same country/region collectively,

I do not see any order in how Expansys/Fedex process the orders. And as they seem to be doing it so slowly, they might have the Batch 2 in queue also before finishing shipping Batch 1....

ARGH!!! Tried to move comments to this common thread - that did not go well... Stealing an old post, And merging it in here fixed it.... *LOL*

Well we can prove that it was much cheaper back then, from the bank statement, but the big question is how long that fight will delay the delivery.

Indeed, I also expect a customs bill around €150-200, including the exorbitant 'handling fee' the carriers usually add... on top of the US$539 I paid for a Super Early Bird.

We just on IGG have had one reporting shipping info on a qwertZ and one to Austria, so my theory was wrong.

Split the voting options so we can see any differences between the orders and the perks. There where already two 'votes' on "No", but being so early, I assume they were Orders, If not, sorry....

I think I have seen a github link somewhere in here, but could remember wrong....

I assume you mean Pro1X? The ROM mentioned in this thread is NOT for the Pro1X but the Pro1. Though we do expect that there should be one for the Pro1X too soon. And almost certainly the same considerations on rooting and the like will go for both. Will keep the ROMs thread updated, so keep an eye out there for new ROMS for the Pro1X.

(I adjusted the ROM-page, added link to this. Thanks! ) If you could pack it in a zip loadable by the Recovery Mode (like we have for Lineage and Aicp for the Pro1), it would be awesome. The numerous single operations we got for the Pro1 stock is a bit tedious.

(sorry guys merged the old thread into the new, should have been the other way, renamed)

See also other threads, e.g. these https://community.fxtec.com/topic/3513-time-to-take-action-us-carrier-whitelisting-verizon-and-att/ https://community.fxtec.com/topic/3404-att-wireless-us-is-expelling-devices-including-the-pro-1-from-its-network/ (Unfortunately the forum search does not work for something as short as "ATT" or "AT&T", making it harder to find relevant stuff, but "carrier" and "mule" give some related)

Just to be sure, have you tried other nfc-items? That is do we know if it is general or specific to yubikey ? I tried my Titan slim on Android 11, and nfc works out of the box. I will try to install installed AICP-R and AICP S, on my test unit Pro1 to see it it is related to Android 11 / 12 ADD I, just tried AICP-R on a Pro1, and it worked out of the box installing "NFC tools" for test. ADD II, just tried the broken AICP-S on a Pro1, and it worked out of the box (well after the boot-loop) installing "NFC tools" for test. So the issues seems to be related to Pro1X, (or your spe

The reader is working on my Pro1 with Stock Android. And yes,at the top (seen in portrait) I believe it is between the logo and the camera

Flashed today's release aicp_pro1_s-17.1-WEEKLY-20220803.zip, with factory reset and no Gapps And it is the same error as above. Boot-loop some ten 10 times, asks for Reset, 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)

Is this Pro1 or Pro1X?

Maybe they changed something for the worse? That could be why it was so relatively easy to trigger it here too? (reposting this as i had to steal an old post....)

Thanks for the workaround, I have marked your post as recommended, hopping that other will see it. And pinned this thread.