IMO there are two possible reasons for this: either something with the copying went wrong or something with the chip is wrong. I don’t know the tools you’ve used so I cannot say for sure if your copy process worked or not. It is the most likely culprit though.
Assuming the copy is indeed perfect, then there must be something different with the chip. They may be using a modified/customized version with a different address/id/… They wouldn’t be the first manufacturer to do such things. This would mean you cannot easily replace the chip.
You could hook up a logic analyzer to the data lines and capture a working and a non-working startup sequence. There must be a difference; maybe this is the quickest way to find it (a protocol analyzer could easily tell you if Nextion was reading the chip properties or its content).
@Max Thank you for your answer.
The manufacturer seems to have worked to prevent copying the chip.
I’ll test it out in various ways.
Thank you again for your kind reply.
This forum is in no way affiliated with NEXTION®, ITEAD STUDIO®, TJC®, or anyone else really. All product names, logos, and brands are property of their respective owners. All company, product, and service names used in this website are for identification purposes only. Use of these names, logos, and brands does not imply endorsement from the respective rights holder(s).