Quote:
Originally Posted by Atter
Thanks Knc1!
I've ordered another Voyage which is in working condition but i can experiment on it february 8th week.
Then i'll open it up, make a backup and use it to recover this one :)
And i can check if the display is really working (replacing the motherboards).
My toughts about the backup procedure:
1. Take the working Voyage and do a factory restore from the GUI.
2. After reboot, backup the following partitions with a Linux machine:
diags_kernel: diags_kernel.img
kernel: main_kernel.img
system: mmcblk0p1.img
diags: mmcblk0p2.img
3. Flash the backup images with fastboot to the faulty Kindle.
Is there a manual how to backup these images?
Can i still use Geekmaster's getkernels script to get the main_kernel and diags_kernel?
And what about mmcblk0p1 and mmcblk0p2?
|
#0) Before anything else (well, you have to pick language and select set-up wifi/register continue later) -
Make a copy of the raw storage (this time we should capture the current factory install image as a deleted file).
You mentioned already reading my step-by-step to grab a forensic image. That is #0 thing to at first power-on.
Then I or Niluje will compare that one with the Oct., 2014 one to see what has changed that might have trashed the 'diags' filesystem.
#1) No
The mmcblk0p1 image is more useful jail broken.
We can always get a non-jail broken image from Amazon with KindleTool.
#2) Yes.
#2.1) Make a copy of the device/personal information outside of the partitioned area (do not distribute, or copy to another device).
dd if=/dev/mmcblk0 of=/mnt/us/some-name.img bs=4096 count=32
#2.2) Just for curiosities' sake you might want a copy of /var/local (/dev/mmcblk0p3)
That is persistent temporary storage. Annotations, Bookmarks, misc. system settings.
Not intended to be distributed, Not required to run, the system will re-create if missing.
#3) Almost.
The main system image (/dev/mmcblk0p1) is too large for fast boot.
#3.1a) If you don't want the restored device to be jail broken:
Do just like you did before signing in here -
Use the recovery menu to install an Amazon posted update file.
#3.1b) if you do want the restored device to be jail broken:
From 'diags' -
dd if=/mnt/us/some-named-mmcblk0p1.img of=/dev/mmcblk0p1 bs=4096
#4) Somewhere there is.
But it is just using dd to copy from (if:in-file) to (of:out-file) in eraseblock chunks (bs=4096).
#5) Yes.
The posted one will copy additional memory, less than a full erase block, but of all 1's (a flash drive's version of blank).
So just ignore that - the fastboot installer will also.
#6) by now (after 0..5) you can answer this one yourself.
Use dd, in-file (if=) either /dev/mmcblk0p1 or /dev/mmcblk0p2 out-file (of=) some distinctive name as /mnt/us/distinctive-name bs=4096
- - - -
PS: The touch screen **must** be working - your using it with the Recovery Menu.
Don't chance breaking tiny connectors by swapping motherboards.
Note: a broken tiny connector is probably your original KV's problem - too many hands in the internals.
Although your original KV can not run until you re-initialize USB storage.
The condition it is in, the system can't detect that it needs to be rebuilt during boot and yet it can't use it at run time.
Your most likely in a file system error loop.
- - - -
:offtopic:
I wonder how many readers realize how difficult it is to repair a computer system from 6 or more time zones away?