View Single Post
Old 09-07-2017, 08:27 AM   #19
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by coplate View Post
Code:
Board Id: 027XXXXXXXXXXXXX
S/N: 901722XXXXXXXXXXX
If he can get the serial number and such off the mmc, is it worth trying to flash main back?
At least part of the mmc is working, right?

Do those errors with cmd resp code and the IO error definitely mean the magic smoke has come out of the chip?
Yes, they do.
Note that the example above is the result of read commands, not of write commands.

Flash chips do not support "write" operations (the hardware and/or software is faking it).
All they can do is read, erase, merge new and old data, then re-program complete "erase block" sections.
They are actually an eeeprom (electrically erasable, electrically programmable, read only memory) behind an included micro-controller with built-in high voltage generator for the erasing.

They can sense (some types) of erase block failures, and do have spare erase blocks that they can substitute.
But they only have those in a limited supply.
When they run out of spares and good (programmable) erase blocks, their useful life is over with.

No, it did not smoke.
The battery ran out of charge during that internal sequence of operations that fake 'write' operations once too often.
The usual sort of failure is the micro-controller has recorded an erase block as 'erased' (while the erase sequencer was erasing it) and the high voltage (erase voltage) generator lost power before completing the erase sequence.

So now a non-erased, erase block is recorded in the list of erased blocks, when its turn comes to be used, it will not program (an eeeprom has to be erased (all 1's) before it can be programmed (0's written where required)).

The micro-controller in an eMMC is not sophisticated enough to recover from such a situation.
The micro-controller in SSD devices is considerably more sophisticated.
The micro-controller in a USB flash stick is considerably less sophisticated.
The specifics of the micro-controller and its programming are trade secrets of each manufacturer.

Quote:
Originally Posted by Daavo View Post
How can i flash diag file system to my Kindle?
You can not flash anything to a flash memory that does not work.
  1. Replace the flash memory chip that has failed.
    We have (in the developer's sub-forum) a thread with directions.
  2. Follow directions to flash the proper (for this purpose) u-boot to the new chip.
    Directions in the same thread.
  3. Follow directions to flash the proper diags kernel to the new chip.
    Directions in the same thread.
  4. Use the kernel's initramfs ("Recovery Mode") to flash the diags system to the new chip.
    Directions in the same thread.
  5. Use the 'Diags' system to flash the kernel and file system of the 'main' system to the new chip.
    Directions in the same thread.


You are in the wrong forum for getting extensive repair directions, use the sub-forum (where the threads you will need already exist).

OR

List the device for sale as: "Not working, for parts only"
Sell it for the display and touch screen.

Last edited by knc1; 09-07-2017 at 09:03 AM.
knc1 is offline   Reply With Quote