12-27-2017, 05:03 PM | #1 |
Junior Member
Posts: 2
Karma: 10
Join Date: Dec 2017
Device: none
|
Kindle Keyboard 3 3G/WiFi Won't Boot
I found a Kindle 3, model d00901, with a broken screen in the e-waste bin at work. I took it home and replaced the screen and battery. Unfortunately, those weren't the only issues. It's currently stuck at "Please wait a moment while your Kindle starts up".
I can get to the reset screen by holding the power for 30+ seconds and then pressing Home. I can type at this screen, but pressing DEL or RESET does nothing but go to the "Please wait..." screen indefinitely. I ran the Kubrick program on it, but it didn't seem to fix it. When it copies the main partition, it completes in 10 seconds while it indicates it may take one to three hours. I suspect the nv memory may be corrupt. This is the output of the serial port after doing a hard reboot. Any thoughts on how to get this working again? Code:
mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 sending read/wr0 end_request: I/O error, dev mmcblk0, sector 556611 EXT3-fs error (device mmcblk0p1): ext3_get_inode_loc: unable to read inode bloc1 INIT: cannot execute "/sbin/getty" mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 sending read/wr0 end_request: I/O error, dev mmcblk0, sector 556610 mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 sending read/wr0 end_request: I/O error, dev mmcblk0, sector 556611 EXT3-fs error (device mmcblk0p1): ext3_get_inode_loc: unable to read inode bloc1 INIT: cannot execute "/sbin/getty" mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 sending read/wr0 end_request: I/O error, dev mmcblk0, sector 556611 EXT3-fs error (device mmcblk0p1): ext3_get_inode_loc: unable to read inode bloc1 INIT: cannot execute "/sbin/getty" mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 sending read/wr0 end_request: I/O error, dev mmcblk0, sector 556610 mmcblk0: error -110 sending status comand<3>mmcblk0: error -110 sending read/wr0 end_request: I/O error, dev mmcblk0, sector 556611 EXT3-fs error (device mmcblk0p1): ext3_get_inode_loc: unable to read inode bloc1 INIT: cannot ex˒V�.]'HYZ�X,[Y��for 5 minutes INIT: no more processes left in this runlevel |
12-27-2017, 05:06 PM | #2 |
Just a Yellow Smiley.
Posts: 19,161
Karma: 83862859
Join Date: Jul 2015
Location: Texas
Device: K4, K5, fire, kobo, galaxy
|
Did you charge it for at least 24 hours?
|
Advert | |
|
12-27-2017, 05:23 PM | #3 |
Junior Member
Posts: 2
Karma: 10
Join Date: Dec 2017
Device: none
|
|
12-27-2017, 06:16 PM | #4 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Put it back in the e-bin.
|
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kindle Voyage won't boot, could serial port help me? | Worthing | Kindle Developer's Corner | 6 | 02-28-2017 06:58 PM |
Pls help! Kindle keyboard does Not boot! | veryczn | Amazon Kindle | 10 | 10-21-2012 01:41 PM |
Bricked Kindle Touch; Won't boot into diags/fastboot | kerotan | Kindle Developer's Corner | 3 | 05-19-2012 10:58 AM |
Kindle Touch Won't Boot | teekay | Kindle Developer's Corner | 3 | 12-10-2011 12:51 AM |