Quote:
Originally Posted by knc1
Because it is a dual boot system, not a concurrent boot system.
(gm probably will not answer you, he passed away last summer.)
|
Oh .. that makes two of the elite devs ... ixtab and geekmaster ...
May their souls rest in peace, they've certainly been a helping hand to lots of people out there ...

It's really touching when you re-read the words of a person you've thought to be alive, after you get the news of their death ... it's almost like you've known them in person.
Quote:
Originally Posted by NiLuJe
CRP also helps in that you don't even have to have access to the FS anymore: boot with a cable plugged in => diags.
Although, IIRC, that doesn't actually work all that well on the Touch, so, just saying that for future ref ;p.
|
Exactly ... it didn't work at all on my Touch.
To update you on my progress, I have done the transplant. And as you have expected, it didn't boot.
Initially, I flashed my own fixed-up version of
rootfs.img. I basically mounted it, searched for files with
yoshime in their names, and replaced them with Kindle Touch versions.
This is the list of files
from the Touch that had
yoshi in their names:
Quote:
./opt/amazon/ebook/config/framework.yoshi.conf
./opt/ar6k/target/AR6003/hw2.1.1/bin/athwlan.bin.yoshi
./var/local/java/default/7/content/com/amazon/ebook/booklet/reader/impl/ui/resources/assets/yoshime3
./var/local/java/default/7/content/com/amazon/ebook/booklet/reader/impl/ui/resources/assets/yoshi
./var/local/java/default/7/content/com/amazon/ebook/booklet/reader/impl/ui/resources/assets/en/yoshime3
./var/local/java/default/7/content/com/amazon/ebook/booklet/reader/impl/ui/resources/assets/en/yoshi
./etc/modules.yoshi
./etc/kdb.src/yoshi (in reality, /etc/kdb.src*)
./lib/firmware/zforce/yoshi_2.0b0r12.hex
|
This is the list of files
from the Paperwhite image that had
yoshime* in their names:
Quote:
./lib/modules/2.6.31-rt11-lab126/kernel/drivers/usb/gadget/arcotg_udc_yoshime.ko
./opt/ar6k/target/AR6003/hw2.1.1/bin/yoshime3
./opt/amazon/ebook/config/framework.yoshime3.conf
./etc/modprobe.d/yoshime3.conf
|
I replaced the
yoshime* files with their
yoshi counterparts, then added the
yoshi files that did were absent from the PW image.
That did
not work.
Nor did flashing the verbatim image from the Paperwhite
In both cases, it's stuck at the tree with the 'Kindle' logo. No signs of life, nothing when plugging USB.
The power button would trigger the LED when pressed.
Note that I have not flashed the Paperwhite kernel. I feared that the Paperwhite kernel might do something nasty and permanent to the hardware ... and on Android devices, this happens.
What now?