Quote:
Originally Posted by qlob
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).....