need help: I select Erase MMC0 in my kindle gen 8 recovery menu..

[cxg2014]

I download fastboot.exe from https://www.mobileread.com/forums/sh....php?p=2000997

And here is my custom Kindle-fastboot.inf:

; Kindle-fastboot.inf
; Copyright (c) 2010 libusb-win32 (GNU LGPL)
[Strings]
DeviceName = "Kindle-fastboot"
VendorName = "Lab126"
SourceName = "Kindle-fastboot Install Disk"
DeviceID   = "VID_1949&PID_D0D0"
DeviceGUID = "{2E9D86BD-468E-47E6-B9E0-F82B24535F2A}"

[Version]
Signature   = "$Windows NT$"
Class       = "libusb-win32 devices"
ClassGuid   = {EB781AAF-9C70-4523-A5DF-642A87ECA567}
Provider    = "libusb-win32"
CatalogFile = Kindle-fastboot.cat
DriverVer   = 01/18/2012, 1.2.6.0

[ClassInstall32]
Addreg = libusb_class_install_add_reg

[libusb_class_install_add_reg]
HKR,,,0,"libusb-win32 devices"
HKR,,Icon,,-20

[Manufacturer]
%VendorName% = Devices, NT, NTAMD64, NTIA64

;--------------------------------------------------------------------------
; libusb-win32 files
;--------------------------------------------------------------------------

[SourceDisksNames]
1 = %SourceName%

[SourceDisksFiles.x86]
libusb0.sys     = 1,x86
libusb0_x86.dll = 1,x86

[SourceDisksFiles.amd64]
libusb0.sys     = 1,amd64
libusb0.dll     = 1,amd64
libusb0_x86.dll = 1,x86

[SourceDisksFiles.ia64]
libusb0.sys     = 1,ia64
libusb0.dll     = 1,ia64
libusb0_x86.dll = 1,x86

[DestinationDirs]
libusb_files_sys       = 10,system32\drivers
libusb_files_dll       = 10,system32
libusb_files_dll_wow64 = 10,syswow64
libusb_files_dll_x86   = 10,system32

[libusb_files_sys]
libusb0.sys

[libusb_files_dll]
libusb0.dll

[libusb_files_dll_x86]
libusb0.dll, libusb0_x86.dll

[libusb_files_dll_wow64]
libusb0.dll, libusb0_x86.dll

;--------------------------------------------------------------------------
; libusb-win32 device driver
;--------------------------------------------------------------------------

[LIBUSB_WIN32_DEV.NT]
CopyFiles = libusb_files_sys, libusb_files_dll_x86

[LIBUSB_WIN32_DEV.NTAMD64]
CopyFiles = libusb_files_sys, libusb_files_dll, libusb_files_dll_wow64

[LIBUSB_WIN32_DEV.NTIA64]
CopyFiles = libusb_files_sys, libusb_files_dll, libusb_files_dll_wow64

[LIBUSB_WIN32_DEV.NT.HW]
DelReg = libusb_del_reg_hw
AddReg = libusb_add_reg_hw

[LIBUSB_WIN32_DEV.NTAMD64.HW]
DelReg = libusb_del_reg_hw
AddReg = libusb_add_reg_hw

[LIBUSB_WIN32_DEV.NTIA64.HW]
DelReg = libusb_del_reg_hw
AddReg = libusb_add_reg_hw

[LIBUSB_WIN32_DEV.NT.Services]
AddService = libusb0, 0x00000002, libusb_add_service

[LIBUSB_WIN32_DEV.NTAMD64.Services]
AddService = libusb0, 0x00000002, libusb_add_service

[LIBUSB_WIN32_DEV.NTIA64.Services]
AddService = libusb0, 0x00000002, libusb_add_service

; Older versions of this .inf file installed filter drivers. They are not
; needed any more and must be removed
[libusb_del_reg_hw]
HKR,,LowerFilters
HKR,,UpperFilters

; libusb-win32 device properties
[libusb_add_reg_hw]
HKR,,SurpriseRemovalOK,0x00010001,1

; (Optional) the usb configuration value to select when this device
; is started.  If this key does not exist the first config is selected.
;HKR,,InitialConfigValue,0x00010001,<your config value>

;--------------------------------------------------------------------------
; libusb-win32 service
;--------------------------------------------------------------------------

[libusb_add_service]
DisplayName   = "libusb-win32 - Kernel Driver 01/18/2012 1.2.6.0"
ServiceType   = 1
StartType     = 3
ErrorControl  = 0
ServiceBinary = %12%\libusb0.sys

;--------------------------------------------------------------------------
; libusb-win32 devices
;--------------------------------------------------------------------------

; Hardware IDs in a 'Devices' section can be installed by libusb-win32
; using usb_install_driver_np(), usb_install_driver_np_rundll(), or the
; inf-wizard utility.
;
[Devices]
%DeviceName% = LIBUSB_WIN32_DEV, USB\%DeviceID%

[Devices.NT]
%DeviceName% = LIBUSB_WIN32_DEV.NT, USB\%DeviceID%

[Devices.NTAMD64]
%DeviceName% = LIBUSB_WIN32_DEV.NTAMD64, USB\%DeviceID%

[Devices.NTIA64]
%DeviceName% = LIBUSB_WIN32_DEV.NTIA64, USB\%DeviceID%

After install driver, I execute command 'fastboot.exe flash kernel uImage' im cmd console, and it shows that:

C:\Users\dev\Desktop>fastboot.exe flash kernel uImage
< waiting for device >
downloading 'kernel'...
FAILED (command write failed (No error))
finished. total time: 0.000s

C:\Users\dev\Desktop>

Thanks for your help

[cxg2014]

I want my kindle to be used normally, so I want to recover it from my wrong choice(erase MMC0)...

[knc1]

Originally Posted by cxg2014

I want my kindle to be used normally, so I want to recover it from my wrong choice(erase MMC0)...

That does not tell much.

To use the Kindle normally does not require a serial port connection, the entry into the alternate OS (diags), nor fiddling around with the recovery menu.
You MUST have had another goal that you where trying to reach before you screwed it up.

Telling us what you where attempting to do **might** give us some idea of where to look for your problem.

No info, no help - that is the only thing logically possible.

[knc1]

Originally Posted by cxg2014

I download fastboot.exe from https://www.mobileread.com/forums/sh....php?p=2000997
- - - -

That archive contains both a binary and the source code.

Did you use the binary or did you rebuild from the source code?
What version of Windows are you using?
Is that on real hardware or in a VM?
If in a VM, what VM?

What have you done to test if the eMMC is writable (other than trying this copy of fastboot)?
What was the result?
Have you done anything else to check if the message you receive might be correct or wrong?

Please start volunteering relevant information.

Making me ask you every possible related question is not a nice thing to do and I have better things to waste my time on.

[cxg2014]

I want to format and overwrite FAT partition, but I chose erase all..

I download binary form that post, and tried real hardware win10, VM windows xp x86, windows 7 x86, and download binary from https://www.mobileread.com/forums/sh...d.php?t=205430 for my ubuntu 16.04 vm, all did not work.

I did not do any testing for eMMC, I execute 'fastboot.exe pass' to change the Led, but not work,

[knc1]

Originally Posted by cxg2014

I want to format and overwrite FAT partition, but I chose erase all..

I download binary form that post, and tried real hardware win10, VM windows xp x86, windows 7 x86, and download binary from https://www.mobileread.com/forums/sh...d.php?t=205430 for my ubuntu 16.04 vm, all did not work.

I did not do any testing for eMMC, I execute 'fastboot.exe pass' to change the Led, but not work,

Use the various u-boot features to test if the eMMC can be written.
Keep in mind there are two u-boot builds installed.
The initial one and the one you enter by the 'bist' command.
They have different command line features available.

From all of the things you have tried, it is likely that the error message is correct.
Doubly likely if the battery ran down while the Kindle was executing 'erase all' and its related write activity.

Losing power during one of the eMMC's internal erase, write cycles corrupts its internal controller code.
Making the device only good for the scrap value of the beach sand (silicon) it contains.

There is a thread here on how to replace the eMMC chip.

[cxg2014]

can I using command "loady" to download uImage to board and boot from it? I tried but seems not work...

uboot > loady
## Ready for binary (ymodem) download to 0x80800000 at 115200 bps...
xyzModem - CRC mode, 37315(SH
)/0(STX)/0(CAN) packets, 1 retries
## Total Size      = 0x0048e0a0 = 4776096 Bytes
uboot > iminfo
uboot > iminfo

## Checking Image at 80800000 ...
Unknown image format!
uboot > bootm
Wrong Image Format for bootm command
ERROR: can't get kernel image!
uboot > go 80800000
## Starting application at 0x80800000 ...
undefined instruction
pc : [<80800004>]	   lr : [<9ffc3e78>]
sp : 9fcb9b90  ip : 00000030	 fp : 9fcba100
r10: 00000002  r9 : 9fcb9cdc	 r8 : 9ffeea84
r7 : 9fcbb890  r6 : 80800000	 r5 : 00000002  r4 : 9fcbb894
r3 : 80800000  r2 : 9fcbb894	 r1 : 9fcbb894  r0 : 00000001
Flags: nZCv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...

resetting ...


U-Boot 2014.04 (Jan 16 2017 - 03:45:34)


CPU:   Freescale i.MX6SL rev1.3 at 792 MHz
CPU:   Temperature 41 C, calibration data: 0x5835065f
Reset cause: POR
FRED::: EXTCSD177=0, 179=48FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
Board: Heisenberg
Board Id: P0011807624202QJ
S/N: G000K905624*****
I2C:   ready
DRAM:  MR5=0x3,MR6=0x1 512 MiB
WARNING: Caches not enabled
MMC:   FRED::: EXTCSD177=0, 179=48FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
REBOOTMODE: 0
using default bootcmdNormal Boot
Hit any key to stop autoboot:  0 
uboot >

[knc1]

Why in the world when the message says the image is wrong do you repeatedly try to run it? That is just plain stupid.

List it for sale as: "Used, For parts only" on some network sales site.
The display is probably still good unless you broke that up also.

[cxg2014]

....Okay, thanks for your help..

[cxg2014]

Hi, I tried another way now my kindle worked well. I'm not naive English speaker, so please forgive my bad English speaking skill.

First, get uImage file from update_kindle_8th_5.8.5.bin, and use command loady to send it to kindle. My uImage file size is 4778496, blk len is 512, so 4778496/512=9333=0x2475

Second, execute command mmc write 0x80800000 0x208 0x2475

Now, press your kindle power button until kindle reboot, then you can entry recovery system, select e to export fat partition, and copy update_kindle_8th_5.8.5.bin into it, enter 1, and select u, wait for some time, your kindle 8th will back ^_^

thanks for your help

[coplate]

Originally Posted by cxg2014

Hi, I tried another way now my kindle worked well. I'm not naive English speaker, so please forgive my bad English speaking skill.

First, get uImage file from update_kindle_8th_5.8.5.bin, and use command loady to send it to kindle. My uImage file size is 4778496, blk len is 512, so 4778496/512=9333=0x2475

Second, execute command mmc write 0x80800000 0x208 0x2475

Now, press your kindle power button until kindle reboot, then you can entry recovery system, select e to export fat partition, and copy update_kindle_8th_5.8.5.bin into it, enter 1, and select u, wait for some time, your kindle 8th will back ^_^

thanks for your help

this is great info, congratulations on the success!

I know what the '0x80800000 '( loady storage address ) and '0x2475' ( size of uImage ), but what is the '0x208' address, where did you get it. I am guessign it is the memory address in the MMC of where the uImage should go, but fore anyone who reads this thread in the future, it is good to know where you got that.


I also have a question for you. on my Paperwhite, the normal uboot does not have the 'loady' command. did you manage to install a custom uboot, or was that already available when you connected the serial port?

[knc1]

Your Kindle has two u-boot builds in it.
The first one that you see, which is intended to require only internal ram to run ...
And the fuller featured u-boot 'bist' .
At the first level u-boot that you see, enter the command:
bist
Which will load and run the 'other' u-boot build.
loady (ymodem load) and friends are built-in commands of the 'bist' u-boot.

ymodem did not used to work, but they must have fixed it sometime after the K5.

[coplate]

Originally Posted by knc1

Your Kindle has two u-boot builds in it.
The first one that you see, which is intended to require only internal ram to run ...
And the fuller featured u-boot 'bist' .
At the first level u-boot that you see, enter the command:
bist
Which will load and run the 'other' u-boot build.
loady (ymodem load) and friends are built-in commands of the 'bist' u-boot.

ymodem did not used to work, but they must have fixed it sometime after the K5.

It looks like OP ran the 'loady' command from the main uboot though:

Originally Posted by cxg2014

uboot > loady
## Ready for binary (ymodem) download to 0x80800000 at 115200 bps...
xyzModem - CRC mode, 37315(SH
)/0(STX)/0(CAN) packets, 1 retries
## Total Size = 0x0048e0a0 = 4776096 Bytes
uboot > iminfo

On my PW3, when I issue the bist command, the prompt changes from 'uboot >' to 'bist >'

Mybe that's just a version thing.

Ah, here it is, this is definitely not the uboot I have on my device, last time I checked.

Originally Posted by cxg2014

U-Boot 2014.04 (Jan 16 2017 - 03:45:34)

Maybe they have updated the viersion officially, or maybe he had built it form source or got it form some of the other posts here.

[knc1]

On your device (why would I give you directions for his device?) . . .
loady is in the bist command set (at least it was last time I looked).
enter:
bist
then enter:
help

- - - -

But due to the fact that is was broken (ymodem protocol) for so long, you may be looking at u-boot build with it remove.
When you updated to 5.8.9.2, one of the things the update did was install a u-boot built for the firmware version.

- - - -

The bootloader (u-boot) lives in a hardware, write protected, area of the eMMC, which you normally can not even see (its mapped out by the eMMC hardware).

The way to install a new (or at least a different) u-boot is to load it to memory, execute it, perform an 'erase all' function.
Part of that function is (after erasing the entire eMMC device) to copy the currently executing u-boot into its protected storage.

(I don't recall anyone verifying that things still work that way now, that was how 5.3.x (or something like that) once worked.)

[coplate]

I'd just love to see @cxg2014 come back and confirm all the steps he took, for other people having the same issue on the same device.


I have disassembled the 'update_kindle_8th_5.8.7.0.1', and I am suprised to see that they do in fact ship with "U-Boot 2014.04 (Jan 16 2017 - 03:45:34)", while the PW3 update 'update_kindle_all_new_paperwhite_5.8.9.2.bin' still has "U-Boot 2009.08-lab126 (May 04 2017 - 10:02:34)"

I now realize that they are newer devices, I just assumed that they used the same basic platfom as the PW3. But I clearly have not been paying enough attention.

In general, this could be a good thing, making some steps of recovery easier, if they start shipping this on more devices that have serial ports ( as far as wiring up a serial port is considered "easy" )

At any rate, congratulations on getting your KT3 up and working again @cxg2014