My kindle is acting up..... - Page 2

qlob · 08-27-2012, 07:21 PM

by Try flashing it with a serial port connection first. I assume you mean using ATK? I never was able to figure out serial debricking...

geekmaster · 08-27-2012, 07:22 PM

Quote:

Originally Posted by knc1

The K3 (or any surface mount device thing) is **not** the place to learn to solder.

I think that "firmware error" is more likely than mechanical failure.
If the K3flasher can't take a dump of it - well then we will have to give this problem a bit more thought.

PS: @qlob - what is it with your location? Is there a resident hardware jinx or grimlin?

He said he dropped it, which is why we were discussing potential hardware solutions. Like I said earlier, I would try using the serial port debricking method if the USB method is not working, before letting a techie friend try to reflow the solder (after removing the thin glass display to keep it safe from overheating). And before reflow, I would seriously considering buying a cheap good kindle with broken display off ebay, and using the good display on it instead of fixing this one. Of course, the drop may have damaged the display causing a slow failure, but that will be determined later.

knc1 · 08-27-2012, 07:22 PM

Quote:

Originally Posted by qlob

....Time to install Winwoes, I guess......

Don't bother doing that, I will put a copy of the RAM Kernel on your Kloud.
I just have to find a copy of it, may take me awhile.

qlob · 08-27-2012, 07:23 PM

[QUOTE=knc1;2199911
PS: @qlob - what is it with your location? Is there a resident hardware jinx or grimlin?

[/QUOTE]

Never seen those words before. I will assume they mean hardware knowledgeable person and press on.

I'm home, but I do have a friend who has soldered laptops and other things and knows a good bit about hardware. He gets back Wed. or Thu...

geekmaster · 08-27-2012, 07:26 PM

Quote:

Originally Posted by qlob

Never seen those words before. I will assume they mean hardware knowledgeable person and press on.

I'm home, but I do have a friend who has soldered laptops and other things and knows a good bit about hardware. He gets back Wed. or Thu...

Bad assumption.

jinx: http://en.wikipedia.org/wiki/Jinx

gremlin: http://en.wikipedia.org/wiki/Gremlin

Those words were referring to your apparent bad luck in this case.

qlob · 08-27-2012, 07:27 PM

Quote:

Originally Posted by geekmaster

He said he dropped it, which is why we were discussing potential hardware solutions. Like I said earlier, I would try using the serial port debricking method if the USB method is not working, before letting a techie friend try to reflow the solder (after removing the thin glass display to keep it safe from overheating). And before reflow, I would seriously considering buying a cheap good kindle with broken display off ebay, and using the good display on it instead of fixing this one.

@knc1: Thanks!

I'm confused again.....
I can connect to USB download mode, I just don't have the kernel, which is being taken care of... Serial is an option (I have Seaniko7's kernel installed), but I never figured it out and the kindle sat around for a while, until Hawhill played around with ATK and posted his results....

knc1 · 08-27-2012, 07:29 PM

I lucked out, both version are there.
I wasn't sure which one you would need (mind is forgetful) so I put them both in your /Kloud thingy.

qlob · 08-27-2012, 07:29 PM

Quote:

Originally Posted by geekmaster

Bad assumption.

jinx: http://en.wikipedia.org/wiki/Jinx

gremlin: http://en.wikipedia.org/wiki/Gremlin

Oh....

I knew what those meant, I just wasn't sure if it had a special meaning in the geek world.

I'm starting to think I have a Kindle Jinx.... If I do have a gremlin, it follows me everywhere........

qlob · 08-27-2012, 07:31 PM

Quote:

Originally Posted by knc1

I lucked out, both version are there.
I wasn't sure which one you would need (mind is forgetful) so I put them both in your /Kloud thingy.

I'm pretty sure it's the *to2 one. Thanks!

knc1 · 08-27-2012, 07:32 PM

Quote:

Originally Posted by qlob

Never seen those words before. I will assume they mean hardware knowledgeable person and press on.

Sorry.
Reference is to fictitious critters that cause unexplainable hardware problems. Like duplicate UUIDs on disk drives, things that worked yesterday and tomorrow but don't work now ...

It was an attempt at humor.

qlob · 08-27-2012, 07:34 PM

Quote:

Originally Posted by knc1

Sorry.
Reference is to fictitious critters that cause unexplainable hardware problems. Like duplicate UUIDs on disk drives, things that worked yesterday and tomorrow but don't work now ...

It was an attempt at humor.

Yeah -- Sometimes I miss humor when I'm in learning mode.... xD

knc1 · 08-27-2012, 07:37 PM

Quote:

Originally Posted by qlob

I'm pretty sure it's the *to2 one. Thanks!

Those are from the ATK version 1.70 binary distribution (I don't think it will matter, the file dates are (where) 2009 something).

qlob · 08-27-2012, 07:38 PM

Quote:

Originally Posted by knc1

Those are from the ATK version 1.70 binary distribution (I don't think it will matter, the file dates are (where) 2009 something).

Gah.... It's stiill sending back 4 bytes instead of 8.

Stupid gremlins...

knc1 · 08-27-2012, 07:42 PM

No that is correct.
The "iROM kernel" is talking to you - its replys are 4 bytes
The "RAM kernel" once you download it into the kindle uses a different protocol with 8 byte replies.

qlob · 08-27-2012, 07:45 PM

Quote:

Originally Posted by knc1

No that is correct.
The "iROM kernel" is talking to you - its replys are 4 bytes
The "RAM kernel" once you download it into the kindle uses a different protocol with 8 byte replies.

Yes, I understand.....

Code:

[root@frankenboxen k3flasher]#./k3-backup.sh
This will backup your K3.
After starting this, bring your K3 into USB downloader mode.
The whole backup procedure will take about 1 hour.
W: cannot find device (is it in USB loader mode? are you root?) - waiting for it....................
I: success.
I: found suitable device
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
I: above error can be ignored, it's due to the device being in ROM kernel mode
I: RAM kernel should be running now. Trying to re-open device: .
I: got it.
I: read info
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
E: aborting. It is suggested you power-cycle the device.
I: found suitable device
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
I: above error can be ignored, it's due to the device being in ROM kernel mode
I: RAM kernel should be running now. Trying to re-open device: .
I: got it.
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
E: aborting. It is suggested you power-cycle the device.
I: found suitable device
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
I: above error can be ignored, it's due to the device being in ROM kernel mode
I: RAM kernel should be running now. Trying to re-open device: .
I: got it.
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
E: aborting. It is suggested you power-cycle the device.
I: found suitable device
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
I: above error can be ignored, it's due to the device being in ROM kernel mode
I: RAM kernel should be running now. Trying to re-open device: .
I: got it.
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
E: aborting. It is suggested you power-cycle the device.
I: found suitable device
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
I: above error can be ignored, it's due to the device being in ROM kernel mode
I: RAM kernel should be running now. Trying to re-open device: .
I: got it.
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
E: aborting. It is suggested you power-cycle the device.
I: found suitable device
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
I: above error can be ignored, it's due to the device being in ROM kernel mode
I: RAM kernel should be running now. Trying to re-open device: .
I: got it.
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
E: aborting. It is suggested you power-cycle the device.
I: found suitable device
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
I: above error can be ignored, it's due to the device being in ROM kernel mode
I: RAM kernel should be running now. Trying to re-open device: .
I: got it.
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
E: aborting. It is suggested you power-cycle the device.
I: found suitable device
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
I: above error can be ignored, it's due to the device being in ROM kernel mode
I: RAM kernel should be running now. Trying to re-open device: .
I: got it.
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
E: aborting. It is suggested you power-cycle the device.
We do not backup the userstore

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
PRS-600 Sony PRS 600 acting up	ppowell002	Sony Reader	4	07-21-2012 03:39 PM
Menu button acting up	canezila	enTourage Archive	6	02-18-2011 03:53 PM
Font's Acting Weird...	Philippe Lemay	Calibre	0	09-05-2010 01:24 AM
Highlighter acting screwy	rakista	enTourage Archive	1	06-04-2010 12:48 PM
My DX is acting up. Again.	Scott Nielsen	Amazon Kindle	4	02-27-2010 02:33 PM

08-27-2012, 07:21 PM	#16
qlob Official Lurker Posts: 1,050 Karma: 7096675 Join Date: Apr 2012 Device: Kindle 3.4	by Try flashing it with a serial port connection first. I assume you mean using ATK? I never was able to figure out serial debricking...

08-27-2012, 07:23 PM	#19
qlob Official Lurker Posts: 1,050 Karma: 7096675 Join Date: Apr 2012 Device: Kindle 3.4	[QUOTE=knc1;2199911 PS: @qlob - what is it with your location? Is there a resident hardware jinx or grimlin? [/QUOTE] Never seen those words before. I will assume they mean hardware knowledgeable person and press on. I'm home, but I do have a friend who has soldered laptops and other things and knows a good bit about hardware. He gets back Wed. or Thu...

08-27-2012, 07:29 PM	#22
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	I lucked out, both version are there. I wasn't sure which one you would need (mind is forgetful) so I put them both in your /Kloud thingy.

08-27-2012, 07:42 PM	#29
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	No that is correct. The "iROM kernel" is talking to you - its replys are 4 bytes The "RAM kernel" once you download it into the kindle uses a different protocol with 8 byte replies.