10-11-2012, 09:50 PM
|
#16 | |
|
Official Lurker
  
Posts: 1,050
Karma: 7096675
Join Date: Apr 2012
Device: Kindle 3.4
|
Quote:
sudo ./k3flasher.bin ./mx_35to2.bin info That should work...you will need to get the ram kernel from an ATK install though... |
|
|
|
|
10-11-2012, 10:28 PM
|
#17 | |
|
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
Quote:
<Grumble> Now who would put a useless *.bin extension on an executable when the application uses *.bin to indicate (ARM binary) executable data (the "Ram kernel" being transfered in the above case)? </Grumble> No harm, no foul, just doesn't mean anything to the O.S. although often it is intended to be suggestive to the human reader, only here we see the same extension used to suggest two different things. For those who might be interested: http://www.linux-tutorial.info/modul...ent&pageid=224 And specific to my Grumble about the filename: http://www.linux-tutorial.info/modul...ntent&pageid=4 Last edited by knc1; 10-11-2012 at 10:56 PM. |
|
|
|
|
|
10-12-2012, 12:19 AM
|
#18 |
|
bookster
Posts: 28
Karma: 5304
Join Date: Jul 2011
Device: Kindle 3 Wifi+3G
|
I was referring to executing k3flasher.bin (the compiled flasher). I managed to execute it on a Live USB Linux Mint 13 MATE using terminal.
However upon following the instructions provided (./k3flasher mx35to2_mmc.bin info) I get an error which I forgot to copy and paste here. I'll get back to you on that. EDIT: I misspelled mx35to2_mmc.bin. I will try the correct name now. It's 5:30 AM, though and I have lectures in 3 hours  I might follow up tomorrow.EDIT2: For some reason k3flasher "cannot find device". I do not know how I achieved it the first time. I followed the instructions to the point. Namely: plug usb in kindle;eject; menu>settings>menu>restart; hold down Vol - button. After the above steps, the screen hangs on the kindle logo with the boy under a tree and this message - "Please wait a moment while your Kindle starts up", I got the same response the first time I tried to enter USB downloading mode. When I run k3flasher, the dots trickle in the terminal, but the kindle is not recognised... Last edited by horizon21; 10-12-2012 at 01:10 AM. |
|
|
|
|
10-12-2012, 04:54 AM
|
#19 | |
|
Wizard
Posts: 1,379
Karma: 2155307
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
|
Quote:
By the way, a reasonably equipped Linux distribution will come with the "lsusb" tool which should show you the Kindle in its USB downloader mode as a device called "Freescale <mumblesomething> SE Ringo" (from the top of my head). |
|
|
|
|
|
10-12-2012, 04:56 AM
|
#20 | |
|
Wizard
Posts: 1,379
Karma: 2155307
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
|
Quote:
|
|
|
|
|
|
10-12-2012, 10:31 AM
|
#21 |
|
bookster
Posts: 28
Karma: 5304
Join Date: Jul 2011
Device: Kindle 3 Wifi+3G
|
Yoohoo! Silly me, I only did a
sudo chmod +x k3f.bin and then ./k3f.bin. When I entered sudo chmod +x k3f.bin and then sudo ./k3f.bin (I renamed the files to 3 letters, due to ease of use), everything went well. I followed with a sudo ./k3f.bin ./mmc.bin info and I got: got device serial number <B006somethingsomething> I: got device Wifi MAC <somethingsomethingBF>. That is nice and dandy. Now I will try with sudo ./k3f.bin ./mmc.bin program kernel media/Data/Downloads/kernel.bin and hopefully I will follow with sudo ./k3f.bin ./mmc.bin program rootfs media/Data/Downloads/rootfs.bin P.S. I am typing these full commands not because I am (pick your offensive adjective here), but because someone else in need might struggle with them like I did. EDIT: Shoot. I was greeted with a sudo ./k3f.bin ./mmc.bin program kernel media/Data/Downloads/kernel.bin I: found suitable device E: opening image for flashing: No such file or directory E: aborting. It is suggested you power-cycle the device. I am assuming this has to do with the syntax of the location of kernel.bin. What am I doing wrong? Should it be preceded by a "./" (tried that, too - didn't work). Data is the name of my "D:\" drive in Windows. Downloads is the folder where I stored kernel.bin and rootfs.bin. Crossing fingers and waiting for valuable input  EDIT 2: Moved kernel.bin and rootfs.bin to a FAT32 flashdrive. I assumed k3flasher might have a problem accessing a NTFS partition. It worked! See spoiler for details: Spoiler:
Now performing a rootfs flash using the same method. Fingers crossed that my Kindle will wake up with 3.0.2 firmware EDIT 3: after 150 minutes of flashing rootfs, my Kindle booted in version 3.0.2! Success! Thanks a ton, howhill! EDIT 4: Upgrade from 3.0.2 to 3.4 has been successful. Mission accomplished! Last edited by horizon21; 10-12-2012 at 02:58 PM. Reason: Blob. |
|
|
|
 |
«
Previous Thread
|
Next Thread
»
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| kobo, google play update, calibre update | tracym | Kobo Tablets | 16 | 06-25-2012 03:24 PM |
| won't update...after completing the update cycle edge returns to the first screen | WeAreBorrg | enTourage Archive | 2 | 03-18-2011 06:39 PM |
| How can I update creation time for a title when I update the book info or convert it | setherd | Calibre | 3 | 10-30-2010 01:51 PM |
| Firmware Update Can I reinstall the official amazon update after the update file from this site ? | yuenslhk | Amazon Kindle | 2 | 06-20-2010 11:24 AM |
| Migrating Calibre from a failing hard drive - mangled my Collections data | lconover | Calibre | 4 | 03-13-2009 08:25 AM |
All times are GMT -4. The time now is 06:39 PM.