EskeRahn

We have just yesterday learned that this is not enough....

Thanks so we now know that it is important but NOT sufficient to backup the persist partition, so now the big question is what ALSO should be backed up? (And without the ability to add key-attestation, it is hard for us to test, unless we initially backup EVERYTHING from a device that still got the keys....)

Personally I had hoped that when they redesigned the main board, they had added an eSim. But might have been too expensive, or might not be supported by the SoC?

Ah I see, so not only suspending battery charging, but suspending power input completely. So the discriptive wording ought to be adjusted slightly. Maybe something like suspending power input (and thus battery charging)

I wonder if that suspended battery charging could be related to the issue behind this:

Ah sorry! that option is for Lineage and AICP not stock android DAMNED!!, so the whole idea crashes, and I believe there is no recovery image to boot into by stock either... So it will require a weird approach of flashing the bootloader for LineageOS or AICP first, to fetch the Persist that way.... Then it is getting (almost) as complex as the edl

On Droidian, note that @Benni has discovered this

My fault, I replied to the post by @VaZso , i can see, sorry. Sad to hear that it seems to be hardware related. I guess you will have to send it in. 😭

Ah well 'proved' was a very hard word. 'suggested' might be better 😉 Just to be sure, did you restore on top of a freshly reflashed stock image (following casey's guide) - before booting it? Or did you do something else?

So we better tag @Casey here as this means some extra tests are needed, that only sensibly can be made by someone that can easily add new key-attestation when lost, and I guess that means internally at FxTec.

So does this mean that you have proved that restoring a saved persist image is NOT enough to keep key-attestation, as we thought?

If you are talking the Pro1X, then yes. 😉

We got it on LineageOS for the Pro1, I do not know if it can easily be added to stock android though.

Thanks for the warning!

I made three 'polls' so we can see the progress of the deliveries of the Pro1X. So please 'vote' so others can see how things progress. It is divided into three individual polls for technical reasons: 1/3 Shipping Info 2/3 Surcharges 3/3 Delivered Open discussion on this in this thread:

You have already been pointed to the long thread, but the tl:dr version is: Any soft cases fitting a Huawei P20 Pro can easily be modified in minutes No special skills required. (Do not take stiff cases though, as the slight slant of the Pro1X's back towards the edges makes them a poor fit). For a number of my DIY experiments see here.

Flashed aicp_pro1_s-17.1-WEEKLY-20220817.zip on security update 2022-03-05 Seems much the same. Still initial boot-loop after flash, Issues with using the keyboard for other than US, no matter if I select one or more (It does respect the qwerty/qwertz layout selection though). Ctrl+space for swapping languages is (also) ignored. ADD: This proved to be related to an app. Accesibility requirement by "Android Assistant" messes with the keyboard-functionality - had exactly the same on the Pro1X (on stock android 11) But that aside things seem to work.

Also check if Caps changes. And if you are in E.g.Settings search (at the top), does the fake keyboard disappear when you slide open the real one. (Trying to find out if it is the light in it self that is the issue, or it does not detect the keyboard being opened)

Nice. I wonder why, I could be wrong, but tapping on the backplates, I suspect the Pro1 back to be more massive than the Pro1X?

Have not even tried the build in camera app. Open camera works fine with landscape

(I took the liberty to move some posts comparing the two devices over from the Pro1X LineageOS thread)

I moved the comparisons over to separate thread here

Nope. There were early unit as early as spring 2019. So some half year after that for the first test build an another half year for release bulid of 16 AND that was for a chipset where there were other devices... I do not know how early they have had test units for developers on the Pro1X. At the earliest this spring would be my guess. Does anyone know if there are any 662 powered phones with LineageOS currently

Tried to do them on a Pro1 and Pro1X single core Pro1: 394 Pro1X: 307 multi-core Pro1: 1604 Pro1X: 1294 compute (opencl) Pro1: 1943 Pro1X: 383 compute (vulkan): pro1: Fails, 408 (0 on Horizon detection) pro1X: Crashes the entire app And the big difference is in the GPU parts only

If I recall right @tdm and a few other did the LineageOS 16 for the Pro1 before going public, though they at some point showed some test-versions, see this