View Single Post
Old 10-22-2012, 10:47 PM   #11
David28227
Member
David28227 began at the beginning.
 
Posts: 12
Karma: 10
Join Date: Oct 2012
Device: Kindle Touch
Quote:
Originally Posted by ixtab View Post
Then try the following: post what happens in syslog when you restart the device in usb downloader mode.

The output on my device looks like this:
Code:
Oct 18 19:10:32 mbp kernel: [587025.494257] usb 1-2: USB disconnect, device number 23
Oct 18 19:10:34 mbp kernel: [587028.240208] usb 1-2: new high speed USB device number 24 using ehci_hcd
Oct 18 19:10:35 mbp kernel: [587028.393004] generic-usb: probe of 0003:15A2:0052.0012 failed with error -22
^C

# The RED part is actually the important one: this is how your device
# should be identifying itself.
# Below is just bonus info (how to use the Linux replacement for mfgtool)
root@mbp:/home/ixtab/kindle-touch/tools/imx_usb_loader# ./imx_usb img/main.bin 
parse mx50_usb_work.conf
dcd
plug
header
jump
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
jump_mode 2
img/main.bin
No dcd table, barker=402000d1
dcd_ptr=0x00000000

loading binary file(img/main.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
noplug, continue
jump_mode 2
img/main.bin
header_max=1000

loading binary file(img/main.bin) to f8007000, skip=0, fsize=fed0 type=aa

<<<65232, 65232 bytes>>>
jumping to 0xf800742c
You could try to use imx_tool on Linux, as I did (it's linked from the debricking thread) - there's no need for Windows driver hell.

Okay, I actually don't know how I'd go about doing that...


Quote:
Originally Posted by knc1 View Post
What else was different between this time, when it did not work and the previous time when it did work with mfgtool?

Different machine? Different USB cable?
Something was different, thinking of what it was might help lead to a solution now.
I tried doing everything the same, same USB Cable, same computer (it's been through a Windows Reset since then though...) I've tried a brand new USB Cable, I've tried using a new cable on a new computer, I've tried every combination of USB ports to Computers to USB Cables I have. I don't usually like to post on forums to help unless I've exhausted everything I can think of. I am pretty unfamiliar with this kind of dev style work, the closest I've came to doing this was ADB on android.. So Even that "Noob" guide is a little over my head. I follow guides for Android stuff all the time and I can easily follow directions, but with these guides I think there's some sort of underlying concept that I just an oblivious to.
David28227 is offline   Reply With Quote