Thread: k3flasher, a USB download mode utility
View Single Post
Old 08-29-2012, 12:15 PM   #134
qlob
Official Lurker
qlob ought to be getting tired of karma fortunes by now.qlob ought to be getting tired of karma fortunes by now.qlob ought to be getting tired of karma fortunes by now.qlob ought to be getting tired of karma fortunes by now.qlob ought to be getting tired of karma fortunes by now.qlob ought to be getting tired of karma fortunes by now.qlob ought to be getting tired of karma fortunes by now.qlob ought to be getting tired of karma fortunes by now.qlob ought to be getting tired of karma fortunes by now.qlob ought to be getting tired of karma fortunes by now.qlob ought to be getting tired of karma fortunes by now.
 
qlob's Avatar
 
Posts: 1,050
Karma: 7096675
Join Date: Apr 2012
Device: Kindle 3.4
Quote:
Originally Posted by qlob View Post
Hrm......
Got it to work now, but this could be a bad sign:
Code:
[root@frankenboxen k3flasher]# sudo ./k3flasher mx35to2_mmc.bin info
I: found suitable device
E: wrong transfer length, wanted to receive 8 bytes but received 4 bytes.
I: above error can be ignored, it's due to the device being in ROM kernel mode
I: RAM kernel should be running now. Trying to re-open device: .
I: got it.
I: read info
<long pause>
E: reading data from device: LIBUSB_ERROR_NO_DEVICE
E: aborting. It is suggested you power-cycle the device.
Got the same results running it with the other RAM kernel (mx35to1.bin).....
qlob is offline   Reply With Quote