View Single Post
Old 04-10-2012, 04:45 PM   #5
geekmaster
Всё гениальное просто.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 5,069
Karma: 6789001
Join Date: Nov 2011
Location: Щедрость не имеет пределов.
Device: *.*
Quote:
Originally Posted by sohmc View Post
To a point. The part that I don't get is this part:


I don't know how to "get my bricked kindle into fastboot mode". After that, everything else makes sense.



I haven't reviewed the fastboot for mac/windows source code but I assume it contains some sort of magic to figure out what device the kindle is using.

Most of the command examples I've seen seem to just have fastboot cmd something with no indication of device location or name.

thanks!
If you can see the kindle as a USB drive, you can save a file ENABLE_DIAGS on it and reboot to diagnostics mode. In that menu, there is an "Exit" option that contains "Install fastboot package" (or something like that). That enables fastboot, which changes the kindle USB VID/PID to 0x1949/0xD0D0, which is the USB device that fastboot waits to see.

If you cannot get to diags, then you can go directly to fastboot mode with MfgTool (for windows), but fastboot mode will drop out if the USB connection gets disconnected or reset.
geekmaster is offline   Reply With Quote