View Single Post
Old 08-05-2012, 06:10 PM   #58
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 DROM View Post
Hello,
following the instructions from this thread and the readme into k3flasher I get the next results:
Code:
./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
E: opening RAM kernel image: No such file or directory
E: error when uploading ramkernel
E: aborting. It is suggested you power-cycle the device.
The same info is given with the setup an reset parameter...
I'm completely noob with this stuff and in Linux environment. According to the result that comes out, I get the feeling that what is not working properly is precisely the kernel, since I do not get results the MAC number or serial number of the Kindle, the device can't be put into ram kernel mode, but what's the meaning of it?
I downloaded the pastebin images and trying to load the kernel on the device, I get the same errors. I did it as:
Code:
./k3flasher mx35to2_mmc.bin  0x00041000  program kernel.bin
I: Suitable device found
E: wrong transfer length, wanted to Receive 8 bytes 4 bytes But received.
I: above errors can be ignored, it's due to the ROM device Being in kernel mode
E: opening RAM kernel image: No such file or directory
E: error when uploading ramkernel
E: aborting. It is you power-cycle Suggested the device.
I'm probably doing something wrong, could someone tell me how should I proceed?
If i remember correctly, you have to obtain the RAM kernel. I'm not sure where to obtain that though. I believe it is mentioned in the readme somewhere.....
qlob is offline   Reply With Quote