View Single Post
Old 04-04-2022, 06:00 AM   #6
NullNix
Guru
NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.
 
Posts: 929
Karma: 15576314
Join Date: Jan 2013
Location: Ely, Cambridgeshire, UK
Device: Kindle Oasis 3, Kindle Oasis 1
Quote:
Originally Posted by AlexPartridge View Post
Code:
U-Boot 2009.08-lab126 (Feb 19 2012 - 05:03:11)

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
Err -19 on send ext_csd

Warning: fail to get ext csd for MMC!
idme_get_var ERROR: couldn't switch to boot partition
Err -19 on send ext_csd

Warning: fail to get ext csd for MMC!
idme_get_var ERROR: couldn't switch to boot partition
Board: Unknown
Boot Reason: [POR]
Boot Device: MMC
Board Id: 0000000000000000
S/N: 0000000000000000
*** TODO: Dump protected MMC here ***
Invalid board id!  Can't determine system type for RAM init.. bailing!
DRAM:   0 kB
Using default environment
I'm not overly sure what this means for the potential of recovering my device, but hopefully it could shed some light on what's wrong!

Thanks!
Indeed it does, but there's not much hope of recovery. Error -19 is -ENODEV, "No such device". Your flash chip ("MMC") has failed so hard that you're not just getting write errors: it's not even appearing on the bus. With no flash chip on the bus, the CPU has nothing to boot from, and booting inevitably fails. Since the flash chip has not only, well, the entire Kindle operating system and all your books on it but also identifiers unique to this specific Kindle without which it won't talk to Amazon and can't decrypt (the majority of) its own books, simply replacing the flash with the Flash from another Kindle wouldn't help, either (not that doing that would buy you much: you lose one Kindle in the process of gaining another!). I don't really see how merely sitting without power could do this: I wonder if the battery has corroded some trace or other on the board. It might be worth looking for bad traces...

(As a side note, here the Kindle is showing its age and relatively limited budget: it has a discrete flash chip, and a separate CPU! Seeing this in a modern retail mobile device is like seeing a dinosaur in the wild to me. Most modern mobile systems, even ones built for easy repair like the Fairphone, have absolutely everything in a single chip, sorry, "package"; usually if that fails, well, you'll see nothing at all because not only is all the flash missing but so is all the RAM and oh yes the CPU as well, and probably all the mobile stuff other than the actual antenna. It's more or less impossible for just part of a package like that to vanish in a coherent lump like this. Random failures due to age-related failures or electromigration or unfortunate overvoltage incidents, sure. Sudden failure of "the flash" but not of any other part of the package? Not going to happen.)
NullNix is offline   Reply With Quote