Download the MagiskHide Props Config Module and change your device fingerprint to a certified one.
You'll need to also download Terminal Emulator and run the command ”props” to load the module.
Thanks. I ended up having to return my handset with screen flicker issues and then a second exchange for one with blue pixels issues so got a refund and went for a stock dual sim variant now. Will consider this workaround for a potential root
I don't think you can upgrade via FH to C432, AFAIK only C636 is available. FH copied the same firmware package under all LYA device branches. Can you post an About Phone screenshot?
As above I ended up returning this handset. It was originally on c432 but was stuck on 153 because of o2 so used FH to put it to 187 and that took it to c636 and then with safety net error. I then managed to use FH to sort out that one and made it back to c432 but still was uncertified after that. I selected the c432 on FH to do it and it did put me on such after flashing it twice over. On the second exchange I got I updated from 153 to 187 using the dload folder method and using the project menu. It did keep as a c432 but it also didnt mess up the safetynet on the 2nd device by using dload method (this info could be benefiical to someone who wants to do an update without breaking safetynet so if anyone wants further info then quote me and ask and I can try help!

) . I was wondering personally if I had then used the dload method on the 1st handset which was then uncertified whether it would have fixed safetynet but I dont have it now so cannot test that but I am curious. Im now on handset three which is a dual sim from Three which has 187 as an ota so have no real rush to go flashing that yet unless 3 drag their heels too much on approving software updates.