Help debugging two kindle 3's with frozen screens, but otherwise functional.

[spelufo]

Hi. First, thanks for all the work you do here, I've been able to make the most out of my kindle because of your hacks. Unfortunately now the screen on my k3 has stopped working.

A while ago I got another k3 from a family member in the same condition as mine is now. Both are responsive as diagnosed by the led and turning on the voice guide, and USB access. Also, mine is rooted and has the USBnetwork hack installed (and other hacks too). Apart from the screen they both seem perfectly fine. Also, the screens look fine too! Could they might still be broken even though I can't see it, in which case I'm out of luck...

When I first got the old one, and mine was still fine, I disassembled them and swapped the screens to check if buying a new screen would help (I had already cracked mine's original screen and successfully replaced it). But neither the old one with mine's then fine screen, nor mine with the old one's frozen one worked. This was weird. I expected the old one to work with a functional screen, but it didn't, so I didn't buy another screen for it, since I was still using mine. (Maybe the two screens were not compatible or something, which would mean that I got lucky when replacing the original cracked screen).

Now that one has frozen. I've rebooted it many times with no luck. I think I got into diags mode by holding the HOME button when powering up, and then out of it with x (googled for screenshot of diags mode), with no change in the screen. I didn't want to use the ENABLE_DIAGS method because I might get stuck with no usb mode, and besides, I can run the diags via ssh anyway, right?

Tried clearing the screen with `eips -c`, but no luck. Tried running /opt/eink/scripts/diag and I get:

eips: pixel_in_range> (612, 580) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 580) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (636, 580) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (648, 580) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (660, 580) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 580) pixel not in range (0..600, 0..800)

I haven't done a factory reset on mine because I would loose all the hacks, right?, and I don't know if it would help since it didn't help the other one.

Any ideas on what might be wrong? Are the screens physically dead even though I can't see damage? Anything else I can run to diagnose the problem?

Thank you very much, sorry for the long post.

[knc1]

This seems to be a common failure mode for older K3 devices.

There was recently one poster who was trying to Kubrick the device (without any luck) and they stumbled onto what might hint at the cause (I can't find the link, so will paraphrase):

**Without** stressing the screen, squeeze / flex the case around the edges.
That restored operation for that one poster.

This hints at a possible manufacturing problem, way back when - -
If the manufacturing process is not exactly right, the solder connections of BGA parts can "age" - I.E: crack.

The major parts of the hardware system on the mother board are BGA mounted parts.

I am not the first to have this insight, a (couple?) few years ago, a poster came to the same conclusion - and tried to "reseat" the BGA parts by heat-soaking them in a toaster oven (actually a recognized repair procedure).

That poster did not have any luck with that trial.
But there are a lot of things that can go wrong when you heat-soak a motherboard (not the case, not the screen).

= = = =

You might just have to consider these Kindles dead or spare parts.

[thatworkshop]

Originally Posted by spelufo

I haven't done a factory reset on mine because I would loose all the hacks, right?, and I don't know if it would help since it didn't help the other one.

Can you delete this file on the one you have USBnet access and see what happens? : /var/local/eink/usid without touching other files in that folder.

[spelufo]

I opened it up and the rubber from the led was loose over the capacitors on the back of the ribbon cable on the screen. Maybe there was some static discharge? Maybe its unrelated.

The screen updates if I press on the connector! Does this confirm what you suspected? Is there any way to determine if the problem is with the screen or with the moderboard? Any way to make the connection better, maybe clean it with something...? I could add something between the case and the connector to keep it pressed down but I don't think it would press it hard enough.

@idoit What is that file? I'm now pretty sure the problem is with the hardware... Thanks, though.

[knc1]

Originally Posted by spelufo

- - - -
The screen updates if I press on the connector!
Does this confirm what you suspected?
- - - -

Yes, it does.

I don't recall what that connector looks like or where it is at.

Perhaps put a small piece of foam between connector and case so it is always pushed once the case is closed?

The 'real' fix would be to remove and re-install the connector.
But that requires special hot-air, SMT rework, tools and high skill.

So try just wedging that thing in there tighter.

= = = =

Thanks for the tip.
I'll find time to go fondle the guts of the 'broken' K3 devices I have on-hand.

[spelufo]

It only worked a few times, now they are both gone... You need to trigger a screen update with some other action while pressing on the connector, of course.

I'm looking to buy a new device, I used my k3 daily. I think it'll be a kobo aura h2o, I hope this isn't considered high treason here . The screen is a little bigger, I wish kindle had kept selling a bigger device.

[knc1]

Originally Posted by spelufo

It only worked a few times, now they are both gone... You need to trigger a screen update with some other action while pressing on the connector, of course.

I'm looking to buy a new device, I used my k3 daily. I think it'll be a kobo aura h2o, I hope this isn't considered high treason here . The screen is a little bigger, I wish kindle had kept selling a bigger device.

Scroll to bottom of page:
https://www.mobileread.com/forums/sho...d.php?t=225030

Amazon does still support listings for the DXG (used, sold by others):
http://www.amazon.com/Kindle-DX-Wire.../dp/B002GYWHSQ