Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle > Kindle Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 01-09-2024, 02:27 PM   #1
derivativeoflog7
Member
derivativeoflog7 began at the beginning.
 
derivativeoflog7's Avatar
 
Posts: 13
Karma: 10
Join Date: Jan 2024
Location: Italy
Device: Kindle Touch (K5)
Talking [FIXED] Kindle Touch still bricked even after using Kubrick

I got a bricked Kindle Touch, showing the "Your Kindle needs repair" screen
When I got it, when I plugged it in my computer, it would reboot (again to the error screen), but it would show as a drive for about a minute
I found about Kubrick, so I got an old PC and ran it, checking the Install jailbreak option and both erase/format options (since I wanted to wipe it anyway)
Once it was done, it rebooted to the language select screen, then it rebooted a few times with a flashing loading bar and the startup message... and now it's back to the same error screen. However, now it won't even show up properly on the computer, it shows as an empty drive!

https://imgur.com/a/RWV4Eaw

What could I try now? Any diagnostics I should run?

Last edited by derivativeoflog7; 11-25-2024 at 12:20 PM.
derivativeoflog7 is offline   Reply With Quote
Old 01-09-2024, 02:35 PM   #2
mergen3107
Wizard
mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.
 
mergen3107's Avatar
 
Posts: 1,356
Karma: 4753060
Join Date: Feb 2012
Location: Cape Canaveral
Device: Kindle Scribe
Maybe the storage is dead for good?
mergen3107 is offline   Reply With Quote
Advert
Old 01-09-2024, 02:39 PM   #3
dhdurgee
Guru
dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.
 
Posts: 847
Karma: 2525050
Join Date: Jun 2010
Device: K3W, PW4
Quote:
Originally Posted by mergen3107 View Post
Maybe the storage is dead for good?
Sounds likely. Guess the only way to be sure would be to open it up and get serial access while booting to see what errors are reported.

Dave
dhdurgee is offline   Reply With Quote
Old 01-09-2024, 03:56 PM   #4
derivativeoflog7
Member
derivativeoflog7 began at the beginning.
 
derivativeoflog7's Avatar
 
Posts: 13
Karma: 10
Join Date: Jan 2024
Location: Italy
Device: Kindle Touch (K5)
Thanks guys, I'll see what I can do to attach to the serial port... that connector seems irritating to use tho. Honestly it would've been easier if it just had bare pads for the serial like most other devices!
derivativeoflog7 is offline   Reply With Quote
Old 01-10-2024, 10:23 AM   #5
derivativeoflog7
Member
derivativeoflog7 began at the beginning.
 
derivativeoflog7's Avatar
 
Posts: 13
Karma: 10
Join Date: Jan 2024
Location: Italy
Device: Kindle Touch (K5)
After a McGyvered serial connection setup I managed to get the boot log
The error screen appears after
Code:
info shutdown_showimage:screen:waiting for cust_service screen to come up:
Another issue now is that I only had a 3.3V adapter so I only connected to the Kindle's Tx for safety
Here's the log:
Spoiler:
Code:
U-Boot 2009.08-lab126 (Apr 04 2012 - 20:06:50)

CPU:   Freescale i.MX50 family 1.1V at 800 MHz
mx50 pll1: 800MHz
mx50 pll2: 400MHz
mx50 pll3: 216MHz
ipg clock     : 50000000Hz
ipg per clock : 50000000Hz
uart clock    : 24000000Hz
ahb clock     : 100000000Hz
axi_a clock   : 400000000Hz
axi_b clock   : 200000000Hz
weim_clock    : 100000000Hz
ddr clock     : 800000000Hz
esdhc1 clock  : 80000000Hz
esdhc2 clock  : 80000000Hz
esdhc3 clock  : 80000000Hz
esdhc4 clock  : 80000000Hz
MMC:  FSL_ESDHC: 0, FSL_ESDHC: 1
Board: Whitney WFO
Boot Reason: [POR]
Boot Device: MMC
Board Id: 0061405114850Q5W
S/N: B0111408210505H1
DRAM:  256 MB
Using default environment

In:    serial
Out:   logbuff
Err:   logbuff
Quick Memory Test 0x70000000, 0xfffe000
POST done in 13 ms
Hit any key to stop autoboot:  1  0 
## Booting kernel from Legacy Image at 70800000 ...
   Image Name:   Linux-2.6.31-rt11-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5181440 Bytes =  4.9 MB
   Load Address: 70008000
   Entry Point:  70008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
Starting kernel ...
mxc_spi mxc_spi.0: chipselect 0 already in use
2.6.31-rt11-lab126 #1 Tue Jul 17 16:55:47 PDT 2012 armv7l
INFO:Loaded module /lib/modules/eink_fb_waveform.ko  (36300 bytes)
mxc_epdc_fb mxc_epdc_fb: not use_builtin_cmap !!
INFO:Loaded module /lib/modules/mxc_epdc_fb.ko default_panel_hw_init=1 default_update_mode=1 (49672 bytes)
INFO:eink initialized... (486400 bytes)
INFO:Using default keypad setting. (not passing "kb_rev" to module)
INFO:Loaded module /lib/modules/whitney_button.ko  (9268 bytes)
Press [ENTER] for recovery menu...       0 /INFO:*** Partition table verified for /dev/mmcblk0 ***
INFO:Checking for updates... (auto-pilot mode)
/dev/mmcblk0p4:
CHS=4/16/105536 size=3458203648 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    6754288
    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 == 10
  argv[0]: "kinit"
  argv[1]: "consoleblank=0"
  argv[2]: "rootwait"
  argv[3]: "ro"
  argv[4]: "ip=off"
  argv[5]: "root=/dev/mmcblk0p1"
  argv[6]: "quiet"
  argv[7]: "eink=fslepdc"
  argv[8]: "video=mxcepdcfb:E60,bpp=8,x_mem=2M"
  argv[9]: "console=ttymxc0,115200"
  argc == 4
  argv[0]: "IP-Config"
  argv[1]: "-i"
  argv[2]: "Linux kinit"
  argv[3]: "ip=off"
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 ext3 filesystem
kinit: trying to mount /dev/root on /root with type ext3
kinit: Mounted root (ext3 filesystem) readonly.
info modules:modprobe:loading module g_file_storage:
init.exe: recevent pre-start process (520) terminated with status 1
info system:start:time=4240:
info hardware:no_wan::WiFi only device. No WAN found
info modules:modprobe:loading module fuse:
info system:config:platform=yoshi,board=whitney,rev=20,proto=N,wifi=Y,wan=N:
info modules:modprobe:loading module ppp_async:
info modules:modprobe:loading module whitney_button:
info zforce:start:version=2.0b0r12:
info system:done:time=5640:
info userstore:run:time=5890,action=start:
info userstore:found_shutdown_flag::Found SHUTDOWN flag file
info display:started:time=6070:
info battery:charged:cap=63,mV=3817,mAH=733:



Welcome to Kindle!

kindle login: info hardware:no_wan::WiFi only device. No WAN found
info hardware:no_wan::WiFi only device. No WAN found
info X:load:time=7360:
info X:xorg.conf:Generating xorg.conf:
warn ttsd:upstart_ttsd_exited::
info X:makexconfig:Whitney Input device detection status:
info X:makexconfig:Keypad: OK:
info X:makexconfig:Touch device: OK:
info X:makexconfig:Accelerometer device: N/A !!:
info X:xorg.conf:xorg.conf generated:
info X:starting:time=8500:
info X:started:time=14320:
info blanket_f:module already loaded:splash:
info locale:read:lang=it_IT.utf8,lc_all=it_IT.utf8:Retrieved Language
crit lab126_gui:reboots=2,max=2:shutting down and showing customer service page:
info shutdown:begin:level=0,halt=1,special=cust_service:
info shutdown:closing password dialog::
info blanket_f:loading blanket module:shutdown:
info shutdown_showimage:screen:splashing screen:cust_service
info shutdown_showimage:screen:waiting for cust_service screen to come up:
info upstart_f:stopping_job:job=lab126:
info upstart_f:stopping_job:job=x:
info upstart_f:jobs_stopped:elapsed_ms=4410,timeout_ms=45000:
info shutdown:cust_service:starting:
info ss_cust_service:nothing to do for this shutdown mode:"cust_service":
info ss_cust_service:completed successfully::
info shutdown:cust_service:done:
info upstart_f:stopping_job:job=filesystems:
info filesystem:unmount_userstore:Unmounting UserStore:
info userstore:run:time=23850,action=stop:
info userstore:found_bootup_flag::Found BOOTUP flag file
info filesystem:rotate_log:Rotating Logs:
info filesystem:unmount_varLocal:Unmounting VarLocal:
info upstart_f:jobs_stopped:elapsed_ms=4350,timeout_ms=30000:
info shutdown:mounting root filesystem read-only::
info shutdown:syncing disks::
info shutdown:end:level=0,halt=1:
System halted.
Halting ...
derivativeoflog7 is offline   Reply With Quote
Advert
Old 01-10-2024, 12:42 PM   #6
dhdurgee
Guru
dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.dhdurgee ought to be getting tired of karma fortunes by now.
 
Posts: 847
Karma: 2525050
Join Date: Jun 2010
Device: K3W, PW4
Quote:
Originally Posted by derivativeoflog7 View Post
After a McGyvered serial connection setup I managed to get the boot log
The error screen appears after
Code:
info shutdown_showimage:screen:waiting for cust_service screen to come up:
Another issue now is that I only had a 3.3V adapter so I only connected to the Kindle's Tx for safety
Here's the log:
Spoiler:
Code:
U-Boot 2009.08-lab126 (Apr 04 2012 - 20:06:50)

CPU:   Freescale i.MX50 family 1.1V at 800 MHz
mx50 pll1: 800MHz
mx50 pll2: 400MHz
mx50 pll3: 216MHz
ipg clock     : 50000000Hz
ipg per clock : 50000000Hz
uart clock    : 24000000Hz
ahb clock     : 100000000Hz
axi_a clock   : 400000000Hz
axi_b clock   : 200000000Hz
weim_clock    : 100000000Hz
ddr clock     : 800000000Hz
esdhc1 clock  : 80000000Hz
esdhc2 clock  : 80000000Hz
esdhc3 clock  : 80000000Hz
esdhc4 clock  : 80000000Hz
MMC:  FSL_ESDHC: 0, FSL_ESDHC: 1
Board: Whitney WFO
Boot Reason: [POR]
Boot Device: MMC
Board Id: 0061405114850Q5W
S/N: B0111408210505H1
DRAM:  256 MB
Using default environment

In:    serial
Out:   logbuff
Err:   logbuff
Quick Memory Test 0x70000000, 0xfffe000
POST done in 13 ms
Hit any key to stop autoboot:  1  0 
## Booting kernel from Legacy Image at 70800000 ...
   Image Name:   Linux-2.6.31-rt11-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5181440 Bytes =  4.9 MB
   Load Address: 70008000
   Entry Point:  70008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
Starting kernel ...
mxc_spi mxc_spi.0: chipselect 0 already in use
2.6.31-rt11-lab126 #1 Tue Jul 17 16:55:47 PDT 2012 armv7l
INFO:Loaded module /lib/modules/eink_fb_waveform.ko  (36300 bytes)
mxc_epdc_fb mxc_epdc_fb: not use_builtin_cmap !!
INFO:Loaded module /lib/modules/mxc_epdc_fb.ko default_panel_hw_init=1 default_update_mode=1 (49672 bytes)
INFO:eink initialized... (486400 bytes)
INFO:Using default keypad setting. (not passing "kb_rev" to module)
INFO:Loaded module /lib/modules/whitney_button.ko  (9268 bytes)
Press [ENTER] for recovery menu...       0 /INFO:*** Partition table verified for /dev/mmcblk0 ***
INFO:Checking for updates... (auto-pilot mode)
/dev/mmcblk0p4:
CHS=4/16/105536 size=3458203648 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    6754288
    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 == 10
  argv[0]: "kinit"
  argv[1]: "consoleblank=0"
  argv[2]: "rootwait"
  argv[3]: "ro"
  argv[4]: "ip=off"
  argv[5]: "root=/dev/mmcblk0p1"
  argv[6]: "quiet"
  argv[7]: "eink=fslepdc"
  argv[8]: "video=mxcepdcfb:E60,bpp=8,x_mem=2M"
  argv[9]: "console=ttymxc0,115200"
  argc == 4
  argv[0]: "IP-Config"
  argv[1]: "-i"
  argv[2]: "Linux kinit"
  argv[3]: "ip=off"
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 ext3 filesystem
kinit: trying to mount /dev/root on /root with type ext3
kinit: Mounted root (ext3 filesystem) readonly.
info modules:modprobe:loading module g_file_storage:
init.exe: recevent pre-start process (520) terminated with status 1
info system:start:time=4240:
info hardware:no_wan::WiFi only device. No WAN found
info modules:modprobe:loading module fuse:
info system:config:platform=yoshi,board=whitney,rev=20,proto=N,wifi=Y,wan=N:
info modules:modprobe:loading module ppp_async:
info modules:modprobe:loading module whitney_button:
info zforce:start:version=2.0b0r12:
info system:done:time=5640:
info userstore:run:time=5890,action=start:
info userstore:found_shutdown_flag::Found SHUTDOWN flag file
info display:started:time=6070:
info battery:charged:cap=63,mV=3817,mAH=733:



Welcome to Kindle!

kindle login: info hardware:no_wan::WiFi only device. No WAN found
info hardware:no_wan::WiFi only device. No WAN found
info X:load:time=7360:
info X:xorg.conf:Generating xorg.conf:
warn ttsd:upstart_ttsd_exited::
info X:makexconfig:Whitney Input device detection status:
info X:makexconfig:Keypad: OK:
info X:makexconfig:Touch device: OK:
info X:makexconfig:Accelerometer device: N/A !!:
info X:xorg.conf:xorg.conf generated:
info X:starting:time=8500:
info X:started:time=14320:
info blanket_f:module already loaded:splash:
info locale:read:lang=it_IT.utf8,lc_all=it_IT.utf8:Retrieved Language
crit lab126_gui:reboots=2,max=2:shutting down and showing customer service page:
info shutdown:begin:level=0,halt=1,special=cust_service:
info shutdown:closing password dialog::
info blanket_f:loading blanket module:shutdown:
info shutdown_showimage:screen:splashing screen:cust_service
info shutdown_showimage:screen:waiting for cust_service screen to come up:
info upstart_f:stopping_job:job=lab126:
info upstart_f:stopping_job:job=x:
info upstart_f:jobs_stopped:elapsed_ms=4410,timeout_ms=45000:
info shutdown:cust_service:starting:
info ss_cust_service:nothing to do for this shutdown mode:"cust_service":
info ss_cust_service:completed successfully::
info shutdown:cust_service:done:
info upstart_f:stopping_job:job=filesystems:
info filesystem:unmount_userstore:Unmounting UserStore:
info userstore:run:time=23850,action=stop:
info userstore:found_bootup_flag::Found BOOTUP flag file
info filesystem:rotate_log:Rotating Logs:
info filesystem:unmount_varLocal:Unmounting VarLocal:
info upstart_f:jobs_stopped:elapsed_ms=4350,timeout_ms=30000:
info shutdown:mounting root filesystem read-only::
info shutdown:syncing disks::
info shutdown:end:level=0,halt=1:
System halted.
Halting ...
Hmm. Someone more experienced than I in reading this log will need to confirm this, but this line stands out to me:

Code:
info userstore:found_shutdown_flag::Found SHUTDOWN flag file
This appears immediately before it starts to shut things down. If this indeed is the problem, you will need to invoke the recovery menu, open a terminal window and remove this file.

Dave
dhdurgee is offline   Reply With Quote
Old 01-10-2024, 02:47 PM   #7
derivativeoflog7
Member
derivativeoflog7 began at the beginning.
 
derivativeoflog7's Avatar
 
Posts: 13
Karma: 10
Join Date: Jan 2024
Location: Italy
Device: Kindle Touch (K5)
Quote:
Originally Posted by dhdurgee View Post
Hmm. Someone more experienced than I in reading this log will need to confirm this, but this line stands out to me:

Code:
info userstore:found_shutdown_flag::Found SHUTDOWN flag file
This appears immediately before it starts to shut things down. If this indeed is the problem, you will need to invoke the recovery menu, open a terminal window and remove this file.

Dave
I saw that too, but how would've it survived two tries with Kubrick?

This stands out to me too:
Code:
info X:makexconfig:Accelerometer device: N/A !!:
The thing is, while I was in diags following Kubrick for the second time, I ran the diagnostics out of curiosity, and the accelerometer was working

Also, as for the serial adapter, I ordered one that also supports 1.8V from AliExpress, let's hope it arrives soon
derivativeoflog7 is offline   Reply With Quote
Old 01-10-2024, 03:02 PM   #8
derivativeoflog7
Member
derivativeoflog7 began at the beginning.
 
derivativeoflog7's Avatar
 
Posts: 13
Karma: 10
Join Date: Jan 2024
Location: Italy
Device: Kindle Touch (K5)
Maybe someone with a working KT can post their boot log for comparison? Or there's one available somewhere
derivativeoflog7 is offline   Reply With Quote
Old 02-19-2024, 02:14 PM   #9
derivativeoflog7
Member
derivativeoflog7 began at the beginning.
 
derivativeoflog7's Avatar
 
Posts: 13
Karma: 10
Join Date: Jan 2024
Location: Italy
Device: Kindle Touch (K5)
I finally got the adapter, but I'm extremely busy this week and I won't have time for this Kindle... if anyone has some ideas about what I should try when I can, let me know!
derivativeoflog7 is offline   Reply With Quote
Old 02-19-2024, 04:19 PM   #10
derivativeoflog7
Member
derivativeoflog7 began at the beginning.
 
derivativeoflog7's Avatar
 
Posts: 13
Karma: 10
Join Date: Jan 2024
Location: Italy
Device: Kindle Touch (K5)
Well okay, curiosity got the best of me
I can interrupt the booting process in two stages

First one is when it says Hit any key to stop autoboot:, I get the following menu
Code:
uboot > help
?       - alias for 'help'
bist    - start Built In Self Test
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootm   - boot application image from memory
go      - start application at address 'addr'
help    - print online help
idme    - idme    - Set nv ram variables


log     - manipulate logbuffer
printenv- print environment variables
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
setenv  - set environment variables
version - print monitor version
One thing I notice is that, if I run idme, i get this:
Code:
serial: B0111408210505H1
accel:
mac: 28EF01689168
sec: EJ7OF378VSQVG3KJC4B2
pcbsn: 0061405114850Q5W
bootmode: main
postmode: normal
I'm VERY sketched out by that accel: <empty> because, as I said before, running a diagnostics from the recovery mode using Kubrick seems to confirm it does actually work! Maybe writing a variable there will fix the issue? I have no idea what to set it to though... maybe if someone gives me a known value I can try that

The second one is when it says Press [ENTER] for recovery menu..., and I get this:
Code:
Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
But nothing here seems to be useful in my case
derivativeoflog7 is offline   Reply With Quote
Old 02-24-2024, 03:12 PM   #11
derivativeoflog7
Member
derivativeoflog7 began at the beginning.
 
derivativeoflog7's Avatar
 
Posts: 13
Karma: 10
Join Date: Jan 2024
Location: Italy
Device: Kindle Touch (K5)
Quote:
Originally Posted by dhdurgee View Post
you will need to invoke the recovery menu, open a terminal window and remove this file.
I don't know how to navigate in the recovery menu to delete this file, could you help me?
derivativeoflog7 is offline   Reply With Quote
Old 09-12-2024, 09:48 AM   #12
amocus
Member
amocus can tie a knot in a cherry stem with his or her tongueamocus can tie a knot in a cherry stem with his or her tongueamocus can tie a knot in a cherry stem with his or her tongueamocus can tie a knot in a cherry stem with his or her tongueamocus can tie a knot in a cherry stem with his or her tongueamocus can tie a knot in a cherry stem with his or her tongueamocus can tie a knot in a cherry stem with his or her tongueamocus can tie a knot in a cherry stem with his or her tongueamocus can tie a knot in a cherry stem with his or her tongueamocus can tie a knot in a cherry stem with his or her tongueamocus can tie a knot in a cherry stem with his or her tongue
 
Posts: 15
Karma: 22344
Join Date: Nov 2014
Location: Poland
Device: K4Black, PW1
What I did for Paperwhite:

Download latest firmware from Amazon, rename it to update.bin.
While in serial in Recovery Menu, select
E. Export FAT partition

next attach USB to your PC, load update.bin into main directory, safely disconnect kindle from PC, in console select
1. done

back in recovery menu select
U. Update using update*.bin file on FAT partition

it should restart and load latest firmware. I found this metod the fastest - not searching SHUTDOWN flag file
amocus is offline   Reply With Quote
Old 11-25-2024, 12:20 PM   #13
derivativeoflog7
Member
derivativeoflog7 began at the beginning.
 
derivativeoflog7's Avatar
 
Posts: 13
Karma: 10
Join Date: Jan 2024
Location: Italy
Device: Kindle Touch (K5)
Quote:
Originally Posted by amocus View Post
What I did for Paperwhite:

Download latest firmware from Amazon, rename it to update.bin.
While in serial in Recovery Menu, select
E. Export FAT partition

next attach USB to your PC, load update.bin into main directory, safely disconnect kindle from PC, in console select
1. done

back in recovery menu select
U. Update using update*.bin file on FAT partition

it should restart and load latest firmware. I found this metod the fastest - not searching SHUTDOWN flag file
Ok so, this is really weird
I wanted to try this, so I dug out the Kindle and got Kubrick again to get it into diags
I copied the update file, but then couldn't find an update option in the K5's diags
Nevertheless, I had Kubrick reflash the firmware again, then I skipped all the optional stuff (jailbreak, reformat, etc)
Kubrick then rebooted the Kindle, and it went to an update screen, but it errored out with UPDATE ERROR 3
And then it rebooted again, and I was fully expecting it to just immediately go to the error "your Kindle needs repair" screen again... except... it didn't, it booted and is now working perfectly fine
So... I guess problem solved? Still have no idea why it didn't work 10 months ago
derivativeoflog7 is offline   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Kindle 3 bricked, Kubrick not helping, help appreciated axm Kindle Developer's Corner 7 09-16-2022 05:32 AM
Kindle 3 bricked - Kubrick no use - any ideas? jadrake Kindle Developer's Corner 9 04-29-2020 12:12 PM
Use KuBrick to install 5.0.0 in Kindle Touch? MHaensel Kindle Developer's Corner 7 02-10-2015 09:18 AM
Kindle Touch (5.3.2) bricked after using Kubrick LiveCD musicguyguy Kindle Developer's Corner 2 05-31-2013 09:36 AM


All times are GMT -4. The time now is 03:18 AM.


MobileRead.com is a privately owned, operated and funded community.