01-30-2021, 02:37 PM | #1 |
Member
Posts: 11
Karma: 10
Join Date: Jan 2021
Device: Kindle 3
|
Bricked K3 stuck in bootloop
Hi everyone,
I have a big trouble flashing Kindle 3. I've bought a K3 with a broken screen. Replaced screen with a brand new ED060SCE display. Than it occured that this reader restarts every minute or less. With a fully charged battery it stayed turned on for 30 minutes, now only rebooting. I tried flashing with Kubrick but it only flashes 1% and shows flashing done. I have few questions 1. Could it be battery isue? 2. How long it should stay in downloader mode ? Because it leaves downloader mode after minute. 3. What can I do more? |
02-01-2021, 06:11 AM | #2 |
Groupie
Posts: 198
Karma: 123456
Join Date: Jan 2018
Device: Too Much Kindle :-)
|
K3 has two common faults. The first is a stuck power switch, the second is broken balls under the CPU. To eliminate the first case, just open the switch, it is on the latches and extract the badge from inside. This model turns on automatically when the battery is connected, so nothing else is needed for testing. If it is not, try pressing your finger on the CPU and see if then the Kindle works longer. If so, 99% reflow is enough.
|
Advert | |
|
02-01-2021, 10:36 AM | #3 |
Member
Posts: 11
Karma: 10
Join Date: Jan 2021
Device: Kindle 3
|
Possibly it helped a bit because it is not rebooting. Everything it makes now is here. Before disassembling power switch it was still looping
U-Boot 1.3.0-rc3-lab126 (Apr 16 2011 - 20:15:23) CPU: Freescale i.MX35 at 532 MHz Board: MX35 Luigi [ POR] WDOG_WCR = 0xff31 WDOG_WMCR = 0x0 Board Id: SP1B000000000000 S/N: B00AA0A0122203LP DRAM: 256 MB Using default environment In: serial Out: serial Err: serial No ethernet found. i.MX35 CPU board version 2.0 Net: No ethernet found. Hit any key to stop autoboot: 0 ## Booting image at 87f40400 ... Image Name: Linux-2.6.26-rt-lab126 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2151348 Bytes = 2.1 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK Starting kernel ... Uncompressing Linux............................................. ................ .................................................. .......... done, booting the k ernel. boot: I def:bcut:15 second battery cut Encountered: 2.6.26-rt-lab126 #5 Mon Dec 27 17:42:43 PST 2010 armv6l INFO:Using default keypad setting. (not passing "kb_rev" to module) INFO:Loaded module /lib/modules/mxc_keyb.ko (22508 bytes) Press [ENTER] for recovery menu... 0 /ERROR:whole_file_read(/sys/devices/s ystem/luigi_battery/luigi_battery0/battery_error): failed to open file: No such file or directory (2) ERROR:luigigas_charge_percent: failed to read from gasgauge error file ERROR:critical_battery_check: gasgauge_get_charge_percent failed with error code 2 INFO:Partition table verified for /dev/mmcblk0 INFO:Checking for updates... (auto-pilot mode) /dev/mmcblk0p4: CHS=4/16/100167 size=3282272256 bytes flag type first last lba first lba size Partition p1: 0x00 0x0b 16 <large> 16 6410672 CHS: 0/1/1 - <large> Partition p2: Partition p3: Partition p4: INFO:Setup loop device /dev/loop0 for /dev/mmcblk0p4 + 8192 INFO:No update*.bin found; no update needed. INFO:no updates found. BOOTING DEFAULT. argc == 9 argv[0]: "kinit" argv[1]: "console=ttymxc0,115200" argv[2]: "mem=256M" argv[3]: "panic=10" argv[4]: "root=/dev/mmcblk0p1" argv[5]: "ro" argv[6]: "ip=none" EXT3-fs: error loading journal. argv[7]: "quiet" argv[8]: "lpj=2555904" Running ipconfig argc == 4 argv[0]: "IP-Config" argv[1]: "-i" argv[2]: "Linux kinit" EXT3-fs: error loading journal. argv[3]: "ip=none" IP-Config: no devices to configure kinit: do_mounts kinit: name_to_dev_t(/dev/mmcblk0p1) = dev(179,1) kinit: root_dev = dev(179,1) kinit: /dev/root appears to be a exEXT2-fs error (device mmcblk0p1): ext2_check_ page: t3 filesystem kinit: trying to bad entry in directory #308: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0mount /dev/root on /root with ty pe ext3 kinit: failed to identify filesystem /dev/root, trying all kinit: trying to mount /dev/root on /root with type ext3 kinit: trying to mount /dev/root on /root with type ext2 kinit: Mounted root (ext2 filesystem) readonly. Checking for init: /sbin/init Checking for init: /bin/init Checking for init: /etc/init Checking for init: /sbin/init.sysvinit Checking for init: /bin/sh kinit: init not found! Kernel panic - not syncing: Attempted to kill init! Unable to handle kernel NULL pointer dereference at virtual address 00000000 pgd = cfa5c000 [00000000] *pgd=8fa48031, *pte=00000000, *ppte=00000000 Internal error: Oops: 817 [#1] last sysfs file: /sys/devices/virtual/net/lo/flags Modules linked in: [last unloaded: mxc_keyb] CPU: 0 Not tainted (2.6.26-rt-lab126 #5) PC is at panic+0x6c/0x12c LR is at 0x0 pc : [<c00c8d38>] lr : [<00000000>] psr: 60000013 sp : cf81ff58 ip : 00000000 fp : cf81ff6c r10: 00000001 r9 : cf81e000 r8 : c00a3c08 r7 : 00000001 r6 : 00000200 r5 : cf814c40 r4 : 00000000 r3 : 00000000 r2 : c03b6e5c r1 : 00000000 r0 : 00000000 Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user Control: 00c5387f Table: 8fa5c008 DAC: 00000015 Process kinit (pid: 1, stack limit = 0xcf81e260) Stack: (0xcf81ff58 to 0xcf820000) ff40: cf8eeee0 cf81ff74 ff60: cf81ff94 cf81ff80 c00cbee8 c00c8cdc c035063c cf814c40 c039c098 c039c098 ff80: cf81e000 00000000 cf81ffa4 cf81ff98 c00cc578 c00cbe90 00000000 cf81ffa8 ffa0: c00a3a60 c00cc56c 00000001 beb26fd9 00000002 00005409 00000001 01835910 ffc0: 00000001 beb26fd9 beb26f34 00000001 00000000 00000000 00000000 00000000 ffe0: 00000000 beb26f20 018211ac 01820efc 60000010 00000002 ffdeffff ffffffff Backtrace: [<c00c8ccc>] (panic+0x0/0x12c) from [<c00cbee8>] (do_exit+0x64/0x614) r3:c039c098 r2:c039c098 r1:cf814c40 r0:c035063c [<c00cbe84>] (do_exit+0x0/0x614) from [<c00cc578>] (complete_and_exit+0x0/0x24) [<c00cc560>] (sys_exit+0x0/0x18) from [<c00a3a60>] (ret_fast_syscall+0x0/0x2c) Code: eb006147 e59f20b0 e3a04000 e5923000 (e5844000) ---[ end trace eb141d860fc4c84e ]--- Fixing recursive fault but reboot is needed! I will try again kubrick now maybe |
02-01-2021, 11:05 AM | #4 |
Groupie
Posts: 198
Karma: 123456
Join Date: Jan 2018
Device: Too Much Kindle :-)
|
This is probably because kubrick started flashing earlier but the power was cut off so now the filesystem is corrupted.
|
02-03-2021, 02:23 AM | #5 |
Member
Posts: 11
Karma: 10
Join Date: Jan 2021
Device: Kindle 3
|
It worked Thank you for your help Does anybody knows why it is unable to see any WiFi network ? No matter if it is 5Ghz or 2.4.
|
Advert | |
|
02-03-2021, 03:41 AM | #6 |
Groupie
Posts: 198
Karma: 123456
Join Date: Jan 2018
Device: Too Much Kindle :-)
|
Try to do a factory reset. If that doesn't help, check the motherboard carefully, preferably under a microscope, pay attention to signs of water damage or broken connections. Especially around the atheros chip. Kindle is 2.4GHz only.
Last edited by eddie.t.h; 02-03-2021 at 09:53 AM. |
02-05-2021, 02:11 PM | #7 |
Member
Posts: 11
Karma: 10
Join Date: Jan 2021
Device: Kindle 3
|
Thank you Eddie, it helped
|
05-03-2021, 08:52 AM | #8 |
Junior Member
Posts: 2
Karma: 10
Join Date: May 2021
Location: Melbourne, AU
Device: Kindle 3
|
Noob here. My Kindle Keyboard suddenly started restart loops. After unsuccessfully trying all possible soft/hard reset methods, tried Kubrick and it "Finished" flashing at 6%. Now it doesn't boot at all and doesn't respond to any mode of reset. Just one unresponsive white page. Tried Kubrick again and now it doesn't get past 1% and says "finished".
I feel like I may have the same power switch problem. But I'm not sure what it means to disassemble the power switch. I'd really appreciate if any details can be provided on this. |
05-04-2021, 12:36 PM | #9 |
Groupie
Posts: 198
Karma: 123456
Join Date: Jan 2018
Device: Too Much Kindle :-)
|
Well, disassembly means disassembly :-) See the photos. Check the inside of the switch carefully. It likes to collect dirt, which makes a short circuit.
|
05-07-2021, 05:11 AM | #10 |
Junior Member
Posts: 2
Karma: 10
Join Date: May 2021
Location: Melbourne, AU
Device: Kindle 3
|
Thank you. I'll try this. I didn't realise you could take apart that tiny switch. Looks like I'll need some good magnifying glasses or a way to hold my phone in position in macro mode.
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kindle 4 Bricked and stuck | e-book-boy | Kindle Developer's Corner | 11 | 10-26-2019 10:42 AM |
bricked? stuck on language selection screen | n1kn0k | Kindle Developer's Corner | 11 | 06-10-2019 04:09 PM |
Boox C67ML stuck in bootloop after update to 1.8.0 | arboon | Onyx Boox | 19 | 03-16-2019 06:31 AM |
KT3 Kindle e-reader(KT3) stuck in Bootloop | Kus | Kindle Developer's Corner | 7 | 10-12-2018 01:22 PM |
Troubleshooting Kindle Voyage stuck in a bootloop | SaddFox | Amazon Kindle | 2 | 11-24-2017 10:31 AM |