View Single Post
Old 08-06-2012, 02:29 PM   #23
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by kln View Post
Can somebody provide me with size and offsets for the K3 kernel and root fs in Kindle memory?

I'm trying to de-brick my K3 and with gitbrew being down I want to take a dump from a working K3 and flash that onto my bricked one.

The instructions for debricking the K3 using the ATK state offsets for the kernel and root fs, however, no size is specified since flashing will just stop when the image file ends.
The getkernels script will extract it automatically from the first 32MB of /dev/mmcblk0 on the kindle, or from an image file...

getkernels:
https://www.mobileread.com/forums/sho...d.php?t=174674

As the source code shows, the main kernel starts at 0x41000. Its length is obtained from the flash header at the start of the image.

To extract the RAMfs image that is inside the kernel image, there is a reference later in the getkernels thread to another offsite script that can do that.
geekmaster is offline   Reply With Quote