EskeRahn

Sadly flashing the Pro1X will NOT fix the screen. It MUST be attached to a Pro1 not Pro1X. There are NO known method we can do on a Pro1X alone. Follow the pinned post first in the forum, it points to various stuff including a disassemble video and a step by step guide showing things with word. I used it two weeks ago for the first time disassembling a Pro1.

It will be interesting to see how the Leaderboard reacts when there are no activity for weeks... 😜

Sad about the display. The rubberband-trick is for the Pro1X not the Pro1. If you got a Pro1X things is a bit more complex getting the full touch area of the display. The only way to initialize it properly is attaching it to a Pro1 (not Pro1X) first, and do a reflash of that (there should be a lengthy step by step guide if you follow the links in the first pinned post in here). The reinitialisation of a Pro1 includes a step that setup the display correctly, and sadly no one has found a way to isolate this code so it can run on a Pro1X... If I remember correcly @jsreed5 offered/offer

PS To tag a specific person you would need to start with an @, e.g. @jsreed5. Or you could send a PM.

Sad. If I remember correctly @CornholioGSM offered this service. I have no idea if he still does this, nor if anyone else offers it.

Great to hear you found the cause and a way to get the data out. We have in other threads looked for the battery, but AFAIK no perfect match have been found, sadly.

Too bad. Any special circumstances? Could it be water/moisture that got in and messed something? It sounds like a hardware failure of some kind to me. (Let us try to ping @CornholioGSM that got experience fixing PRO1/PRO1X)

Necromancing this thread with a dog I got yesterday...

I'm not sure I've seen anyone attemting this before, so can not say if it is a principal error or related to your specimen. If a prinicipal error it could be related to the LineageOS implementation.

I use fastboot for flashing pro1/QX1000 just fine. Why does it not work for yours? I have no idea on the edl file. Will check if I got one downloaded somewhere, but i doubt it.

Have you tried following the guide linked by my initial post pinned in here?

Would be great if someone did, but the amount of users that would notice and fetch are likely to be really low, a handful perhaps..... Actually 22.1 is fine too, it is 22.2 that is totally borked AFAIK.

Just checked the official download page, and currently it only contains ONE build. I wonder if that is a sign that it is soon dropped completely?

If I remember correctly, the imei is part of the persist.img. So sharing would mean you used the same imei, and that is not advisable...

I whined about multiple bugs with 22.2 in the LOS thread here. The 22.1 is fine, so I would suggest to start to go for 22.1, before travelling further backwards. Last 22.1 was: lineage-22.1-20250405-nightly-pro1-signed.zip That can be found here: https://lineage-archive.timschumi.net/build/29528