Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle > Kindle Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 10-11-2012, 10:50 PM   #16
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,048
Karma: 7096675
Join Date: Apr 2012
Device: Kindle 3.4
Quote:
Originally Posted by horizon21 View Post
Awesome! Thanks, hawhill!
P.S. Replacing the 4 files with my backups did not work. Now I have to figure out how to run a .bin file in Linux Mint. Google is my friend At least the frustration with the compiling was spared by the generously provided precompiled k3flasher by hawhill.
try doing:

sudo ./k3flasher.bin ./mx_35to2.bin info

That should work...you will need to get the ram kernel from an ATK install though...
qlob is offline   Reply With Quote
Old 10-11-2012, 11:28 PM   #17
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 7,000
Karma: 6327868
Join Date: Feb 2012
Device: Too many.
Quote:
Originally Posted by qlob View Post
try doing:

sudo ./k3flasher.bin ./mx_35to2.bin info

That should work...you will need to get the ram kernel from an ATK install though...
OK, that tells me what was meant by the mystery sentence.

<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 11:56 PM.
knc1 is offline   Reply With Quote
 
Advertisement
Old 10-12-2012, 01:19 AM   #18
horizon21
bookster
horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!
 
horizon21's Avatar
 
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 02:10 AM.
horizon21 is offline   Reply With Quote
Old 10-12-2012, 05:54 AM   #19
hawhill
Wizard
hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.
 
hawhill's Avatar
 
Posts: 1,218
Karma: 2124593
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
Quote:
Originally Posted by horizon21 View Post
When I run k3flasher, the dots trickle in the terminal, but the kindle is not recognised...
That error message is a bit too specific, as probably it's just not equipped with enough permissions. You didn't quote the full command line (given that your shell displays an informational prompt), but just to make sure: That has to be run with sufficient permissions, in the simplest case just run it as root (either by using "sudo" or "su" from a simple user account).

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).
hawhill is offline   Reply With Quote
Old 10-12-2012, 05:56 AM   #20
hawhill
Wizard
hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.
 
hawhill's Avatar
 
Posts: 1,218
Karma: 2124593
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
Quote:
Originally Posted by knc1 View Post
<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>
Teehee, I've grumbled too. Mobileread has a notion of "file extensions" when it comes to allowed uploadable files. Not that it really checks their content....
hawhill is offline   Reply With Quote
Old 10-12-2012, 11:31 AM   #21
horizon21
bookster
horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!horizon21 , Klaatu Barada Niktu!
 
horizon21's Avatar
 
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:
sudo ./k3f.bin ./mmc.bin program kernel /media/bytestor/kernel.bin
I: found suitable device
I: flashing 0x00340000 (=3407872) bytes
I: writing 0x00200000 (=2097152) bytes to address 0x00041000, waiting for completion...
I: wrote 0x00200000 (=2097152) bytes, waiting for completion...
I: flashed 0x00010000 (=65536) bytes
I: flashed 0x00020000 (=131072) bytes
I: flashed 0x00030000 (=196608) bytes
I: flashed 0x00040000 (=262144) bytes
I: flashed 0x00050000 (=327680) bytes
I: flashed 0x00060000 (=393216) bytes
I: flashed 0x00070000 (=458752) bytes
I: flashed 0x00080000 (=524288) bytes
I: flashed 0x00090000 (=589824) bytes
I: flashed 0x000a0000 (=655360) bytes
I: flashed 0x000b0000 (=720896) bytes
I: flashed 0x000c0000 (=786432) bytes
I: flashed 0x000d0000 (=851968) bytes
I: flashed 0x000e0000 (=917504) bytes
I: flashed 0x000f0000 (=983040) bytes
I: flashed 0x00100000 (=1048576) bytes
I: flashed 0x00110000 (=1114112) bytes
I: flashed 0x00120000 (=1179648) bytes
I: flashed 0x00130000 (=1245184) bytes
I: flashed 0x00140000 (=1310720) bytes
I: flashed 0x00150000 (=1376256) bytes
I: flashed 0x00160000 (=1441792) bytes
I: flashed 0x00170000 (=1507328) bytes
I: flashed 0x00180000 (=1572864) bytes
I: flashed 0x00190000 (=1638400) bytes
I: flashed 0x001a0000 (=1703936) bytes
I: flashed 0x001b0000 (=1769472) bytes
I: flashed 0x001c0000 (=1835008) bytes
I: flashed 0x001d0000 (=1900544) bytes
I: flashed 0x001e0000 (=1966080) bytes
I: flashed 0x001f0000 (=2031616) bytes
I: flashed 0x00200000 (=2097152) bytes
I: flashing of 0x00200000 (=2097152) bytes complete
I: writing 0x00140000 (=1310720) bytes to address 0x00241000, waiting for completion...
I: wrote 0x00140000 (=1310720) bytes, waiting for completion...
I: flashed 0x00010000 (=65536) bytes
I: flashed 0x00020000 (=131072) bytes
I: flashed 0x00030000 (=196608) bytes
I: flashed 0x00040000 (=262144) bytes
I: flashed 0x00050000 (=327680) bytes
I: flashed 0x00060000 (=393216) bytes
I: flashed 0x00070000 (=458752) bytes
I: flashed 0x00080000 (=524288) bytes
I: flashed 0x00090000 (=589824) bytes
I: flashed 0x000a0000 (=655360) bytes
I: flashed 0x000b0000 (=720896) bytes
I: flashed 0x000c0000 (=786432) bytes
I: flashed 0x000d0000 (=851968) bytes
I: flashed 0x000e0000 (=917504) bytes
I: flashed 0x000f0000 (=983040) bytes
I: flashed 0x00100000 (=1048576) bytes
I: flashed 0x00110000 (=1114112) bytes
I: flashed 0x00120000 (=1179648) bytes
I: flashed 0x00130000 (=1245184) bytes
I: flashed 0x00140000 (=1310720) bytes
I: flashing of 0x00140000 (=1310720) bytes complete

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 03:58 PM. Reason: Blob.
horizon21 is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
kobo, google play update, calibre update tracym Kobo Tablets 16 06-25-2012 04:24 PM
won't update...after completing the update cycle edge returns to the first screen WeAreBorrg enTourage Archive 2 03-18-2011 07: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 02: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 12:24 PM
Migrating Calibre from a failing hard drive - mangled my Collections data lconover Calibre 4 03-13-2009 09:25 AM


All times are GMT -4. The time now is 12:57 PM.


MobileRead.com is a privately owned, operated and funded community.