MobileRead Forums - View Single Post

ixtab · 09-25-2012, 08:19 PM

This is great! Thanks a lot, eureka - finally we don't need to jump through all those Windoze hoops anymore.

I just tried it, and it works smoothly. Just for reference again, here's what I did:

Clone repository: cd /tmp; git clone https://github.com/boundarydevices/imx_usb_loader.git
Compile: cd imx_usb_loader; make
Create mx50_usb_work.conf as explained in eureka's post
Copy main.bin, diags.bin, and fastboot.bin from the MfgTool profiles folders
Boot K5 into USB recovery mode, and execute sudo ./imx_usb diags.bin

Spoiler:

Now here's the $ 10⁶ question: How will one be able to boot the KPW into USB recovery mode, if there's no physical "magic" button on the device?

Of course I know it's all gonna be speculation because nobody has the device yet - just wondering how it could work in principle. Need to open the device? Or, maybe, a "really long press" of the power button? Morse codes with the power button?

... ?

EDIT:
For some reason, if you want to run it entirely through the configuration file (instead of giving a file from the command line), you need two lines for it to complete:

Code:

KindleTouch
hid,1024,0x70000000,256M,0xF8000000,128K
img/main.bin:dcd,plug
img/main.bin:jumpheader

"dcd,plug,jumpheader" in just a single line doesn't work. BTW, you can write "jumpheader" or "jump header" - with or without space seems to be ok

09-25-2012, 08:19 PM	#228
ixtab (offline) Posts: 2,907 Karma: 6736092 Join Date: Dec 2011 Device: K3, K4, K5, KPW, KPW2	Confirmed working This is great! Thanks a lot, eureka - finally we don't need to jump through all those Windoze hoops anymore. I just tried it, and it works smoothly. Just for reference again, here's what I did: Clone repository: cd /tmp; git clone https://github.com/boundarydevices/imx_usb_loader.git Compile: cd imx_usb_loader; make Create mx50_usb_work.conf as explained in eureka's post Copy main.bin, diags.bin, and fastboot.bin from the MfgTool profiles folders Boot K5 into USB recovery mode, and execute sudo ./imx_usb diags.bin Spoiler: $ sudo ./imx_usb diags.bin parse mx50_usb_work.conf 15a2:0052(KindleTouch) bConfigurationValue =1 Interface 0 claimed report 1, wrote 16 bytes, err=0 report 3, read 4 bytes, err=0 read=56 78 78 56 diags.bin No dcd table, barker=402000d1 dcd_ptr=0x00000000 loading binary file(diags.bin) to f8006000, skip=0, fsize=800 type=aa <<<2048, 2048 bytes>>> jumping to 0xf8006400 report 1, wrote 16 bytes, err=0 report 3, read 4 bytes, err=0 read=56 78 78 56 jump_mode 2 plug=1 err=0 diags.bin header_max=1000 loading binary file(diags.bin) to f8007000, skip=0, fsize=fed0 type=aa <<<65232, 65232 bytes>>> jumping to 0xf800742c Now here's the $ 10⁶ question: How will one be able to boot the KPW into USB recovery mode, if there's no physical "magic" button on the device? Of course I know it's all gonna be speculation because nobody has the device yet - just wondering how it could work in principle. Need to open the device? Or, maybe, a "really long press" of the power button? Morse codes with the power button? ... ? EDIT: For some reason, if you want to run it entirely through the configuration file (instead of giving a file from the command line), you need two lines for it to complete: Code: KindleTouch hid,1024,0x70000000,256M,0xF8000000,128K img/main.bin:dcd,plug img/main.bin:jumpheader "dcd,plug,jumpheader" in just a single line doesn't work. BTW, you can write "jumpheader" or "jump header" - with or without space seems to be ok Last edited by ixtab; 09-25-2012 at 09:56 PM.