Help recovering kindle paperwhite after 'eraseall'

[knc1]

There will be output on the serial port, up to the message:
unable to start DRAM
At which point the SoC code powers the chip down.

The thread on replacing the eMMC has the solutions to all of these questions.
Searching for that thread is left as a DIY exercise, after all, my Kindle isn't the one that is broke.

[dram]

Originally Posted by knc1

There will be output on the serial port, up to the message:
unable to start DRAM
At which point the SoC code powers the chip down.

The thread on replacing the eMMC has the solutions to all of these questions.
Searching for that thread is left as a DIY exercise, after all, my Kindle isn't the one that is broke.

I'm pretty much sure that serial port is ok, because I have used it without any problem until executing "eraseall" command. After that I got message "resetting" and that was the last message over serial.
Now I have tried to hold button for 30 sec and orange LED next to USB port starts to flash after about 10 seconds and nothing happens. I have checked dmesg after I reset device and it look a little bit different that after first time I connect it to mu PC:

[11431.849746] usb 2-1: USB disconnect, device number 5
[11432.255469] usb 2-1: new high-speed USB device number 6 using xhci_hcd
[11432.384085] usb 2-1: New USB device found, idVendor=15a2, idProduct=0063
[11432.384088] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[11432.384089] usb 2-1: Product: SE Blank MEGREZ
[11432.384090] usb 2-1: Manufacturer: Freescale SemiConductor Inc 
[11432.384977] hid-generic 0003:15A2:0063.0007: hiddev0,hidraw2: USB HID v1.10 Device [Freescale SemiConductor Inc  SE Blank MEGREZ] on usb-0000:00:14.0-1/input0

I found that it might be possible to flash it over USB by using mfg tool, but device 15A2:0063 is not supported, so now I'm really lost.

[geekmaster]

Originally Posted by dram

I found that it might be possible to flash it over USB by using mfg tool, but device 15A2:0063 is not supported, so now I'm really lost.

The old version of MfgTool packaged in the "Kindle Select Boot" thread probably does not recognize the USB VID/PID for newer kindles. However, some folks are having problems with a new MfgTool utility with i.MX6 SoCs:
https://community.freescale.com/thread/385070

I do not have a newer kindle so I cannot support it (no way to explore and test available debricking options). Donations of working (or non-working) PW (or newer) kindles are welcome, so I can support them.

[dram]

I have found recent version of imx_loader-master and it supports 15A2:0063 device, but trying to download fastboot.img is not working as I would like to:

config file <./imx_usb.conf>
vid=0x066f pid=0x3780 file_name=mx23_usb_work.conf
vid=0x15a2 pid=0x004f file_name=mx28_usb_work.conf
vid=0x15a2 pid=0x0052 file_name=mx50_usb_work.conf
vid=0x15a2 pid=0x0054 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0061 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0063 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0041 file_name=mx51_usb_work.conf
vid=0x15a2 pid=0x004e file_name=mx53_usb_work.conf
vid=0x15a2 pid=0x006a file_name=vybrid_usb_work.conf
vid=0x066f pid=0x37ff file_name=linux_gadget.conf
config file <./mx6_usb_work.conf>
parse ./mx6_usb_work.conf
15a2:0063(mx6_qsb) bConfigurationValue =1
Interface 0 claimed
HAB security state: development mode (0x56787856)
== work item
filename ./fastboot.bin
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 2
jump_addr 0x00000000
== end work item
No dcd table, barker=402000d1

loading binary file(./fastboot.bin) to f8006000, skip=0, fsize=800 type=aa
out err=-7, last_trans=0 cnt=0x800 max=0x400 transferSize=0x0 retry=0
out err=-7, last_trans=0 cnt=0x800 max=0x200 transferSize=0x0 retry=1
out err=-7, last_trans=0 cnt=0x800 max=0x100 transferSize=0x0 retry=2
out err=-7, last_trans=0 cnt=0x800 max=0x80 transferSize=0x0 retry=3
out err=-7, last_trans=0 cnt=0x800 max=0x40 transferSize=0x0 retry=4
out err=-7, last_trans=0 cnt=0x800 max=0x20 transferSize=0x0 retry=5
out err=-7, last_trans=0 cnt=0x800 max=0x10 transferSize=0x0 retry=6
out err=-7, last_trans=0 cnt=0x800 max=0x8 transferSize=0x0 retry=7
out err=-7, last_trans=0 cnt=0x800 max=0x10 transferSize=0x0 retry=8
out err=-7, last_trans=0 cnt=0x800 max=0x8 transferSize=0x0 retry=9
out err=-7, last_trans=0 cnt=0x800 max=0x10 transferSize=0x0 retry=10
Giving up
HAB security state: development mode (0x00000000)

Either I try to download wrong file, either mx6 config file contains wrong addresses and I do not know the correct ones.

[knc1]

Originally Posted by dram

I'm pretty much sure that serial port is ok, because I have used it without any problem until executing "eraseall" command. After that I got message "resetting" and that was the last message over serial.
Now I have tried to hold button for 30 sec and orange LED next to USB port starts to flash after about 10 seconds and nothing happens. I have checked dmesg after I reset device and it look a little bit different that after first time I connect it to mu PC:

[11431.849746] usb 2-1: USB disconnect, device number 5
[11432.255469] usb 2-1: new high-speed USB device number 6 using xhci_hcd
[11432.384085] usb 2-1: New USB device found, idVendor=15a2, idProduct=0063
[11432.384088] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[11432.384089] usb 2-1: Product: SE Blank MEGREZ
[11432.384090] usb 2-1: Manufacturer: Freescale SemiConductor Inc 
[11432.384977] hid-generic 0003:15A2:0063.0007: hiddev0,hidraw2: USB HID v1.10 Device [Freescale SemiConductor Inc  SE Blank MEGREZ] on usb-0000:00:14.0-1/input0

I found that it might be possible to flash it over USB by using mfg tool, but device 15A2:0063 is not supported, so now I'm really lost.

Thou shall not boot with the USB cable connected

[dram]

Tried without - no output on serial port

[knc1]

Originally Posted by dram

Tried without - no output on serial port

Describe your hardware setup of the serial port connection.
Include a pic' if possible.

It is far more likely that you have fried the serial port interface than destroyed the silicon inside of the SoC.

[dram]

I'm using this converter: http://www.tiaowiki.com/w/TIAO_USB_M...r's_Manual
TTL level selector is in correct position. I use pins 1,2 and 12 on TTL connector. I've tried to swap Rx and Tx wires just to test it. Nothing happened. Absolutely same setup was used on the same computer with the same operating system before executing 'eraseall' command. After that I get absolutely nothing on serial port. I still use same serial port settings - 115200 8N1.

[geekmaster]

Originally Posted by dram

I'm using this converter: http://www.tiaowiki.com/w/TIAO_USB_M...r's_Manual
TTL level selector is in correct position. I use pins 1,2 and 12 on TTL connector. I've tried to swap Rx and Tx wires just to test it. Nothing happened. Absolutely same setup was used on the same computer with the same operating system before executing 'eraseall' command. After that I get absolutely nothing on serial port. I still use same serial port settings - 115200 8N1.

The device at that link describes itself as 3.3v operation, which is NOT compatible with the 1.8v TTL used in (all but the oldest) kindle models. You need a level shifter such as shown in my Kindle serial adapter level shifter circuit thread, or you need a serial adapter directly supports 1.8v TTL serial.

Also, the device at your link shows pads for (and describes usage of) RX and TX LEDs. As I mentioned in my "level shifter" thread (link provided above), the kindle TxD cannot sink enough current to light an LED, and cannot pull the logic level down to a 1.8v TTL zero with an LED in that part of the circuit. I had to remove the LED and pull that line up with an appropriate resistor. If your adapter contains such LEDs (as described at your link), you will almost certainly have the same problem.

Also, as I discovered on some kindle models, the GND pin on the serial connection is inadequate, and I was able to get by without part of the level shifter circuit if I used a better GND point in the kindle (such as an RF or USB shield).

EDIT: This page confirms that the device at your link has a "3.3v to 5v TTL serial link", which is NOT compatible with 1.8v kindle serial TTL, unless you convert the TTL levels:
http://www.diygadget.com/tiao-usb-mu...2c-serial.html

[dram]

How then it could work before executing 'eraseall'? That was biggest confusion about my converter. It was working without any problem, so I didn't think that it might be the reason.

[geekmaster]

Originally Posted by dram

How then it could work before executing 'eraseall'? That was biggest confusion about my converter. It was working without any problem, so I didn't think that it might be the reason.

With a good ground in the kindle (not on the TTL serial connector), I found that TTL worked okay in ONE DIRECTION, but not the other. It could be that your TxD and RxD LEDs are buffered, rather than being directly driven by the kindle TxD line. Or perhaps your LEDs are using a higher value of resistor than mine did. Consider yourself lucky if it "just worked", when the linked info showed it as a 3.3v (minimum) adapter.

On a K5 (Touch) or earlier, erasing your entire flash would be relatively trivial to fix, because you press a "magic key" during hard reset to enter USB downloader mode. Though the PW uses the same processor (i.MX508) as the K5, it has no keys (and therefore no "magic key").

However, the "magic key" is likely wired to one of the inputs on the SoC that determine boot mode, and finding that pin on the PW SoC (especially somewhere on the PCB that you can connect to) may allow you to enable USB downloader mode even on a PW (or later). AFAIK nobody has done this yet, but it may be possible.

Meanwhile, erasing all your flash on a newer kindle is like playing Russian Roulette with all chambers loaded.

[knc1]

Originally Posted by dram

How then it could work before executing 'eraseall'? That was biggest confusion about my converter. It was working without any problem, so I didn't think that it might be the reason.

Same way your porch light worked before it burned out, and now it doesn't work.