View Single Post
Old 12-25-2010, 09:39 PM   #9
yifanlu
Kindle Dissector
yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.yifanlu ought to be getting tired of karma fortunes by now.
 
Posts: 662
Karma: 475607
Join Date: Jul 2010
Device: Amazon Kindle 3
I actually got 3.0.1 working on the Kindle 2. I bricked it doing other stupid stuff later so I lost all the work (it's still on the dead kindle. If I get get the recovery port working, I can post exactly what I did). From what I remember, I did stuff like (don't do just that and expect it to work, I spent a week trying different things. The most extreme was recompiling java, so I'm generalizing ALOT):

1) Replace /etc /usr /opt /bin /sbin and /usr from my Kindle 3 to the Kindle 2. Also copy/replace everything from /lib EXCEPT modules
1a) The filesystem is not large enough on the K2, so I deleted TTS files.
2) In /etc/kdb.src, I made a new folder "mario", copied everything from "luigi" and customized the settings to match that of K2 (a pain finding the old settings from various folders), then modified the kdb settings to use mario.
3) Ran /etc/init.d/framework restart, while in another session I kept "dmesg"-ing to find what errors if any. After correcting all errors, it should be working.

I had everything pretty much working. Browser was extremely buggy and slow (probity not enough ram), and PDF crashes (maybe ram problem, maybe a library link problem, I never checked). And I even got a "Thanks for upgrading to Kindle 3" notice.

Also, I think to get everything working, you need a newer kernel (I think the browser and the pdf reader uses a newer framebuffer driver). You'll need to take the kindle 3 kernel source, find all the changes (diff), modify them to match kindle 2. Then take the kindle 2 kernel source, get the mario.conf file, modify it to include features in the kindle 3 kernel, but keep features for the kindle 2 (keypad, etc) and cross-compile it.

BEWARE: This is for really advanced kindle hackers only. If you don't have access to the recovery ports, DO NOT do this. After I bricked my Kindle, I now always make sure to get recovery ports working first before doing any hacks. Also back up you rootfs if you're going to do this.


P.S: The "open source" is useless. All the actual kindle OS stuff (the UI you see) are proprietary java code and not open source. The open source is the backend including the bootloader, the linux kernel, and various linux tools. They are all incompatible with the kindle 2 anyways, so it's pretty useless unless you want to recompile the kernel.



EDIT: If you just want the new PDF reader, I think it would be easier to just recompile the kernel to be newer (see above), then replace the libpdfs in /usr/lib and/or /lib with the newer ones, and possibly decompile the kindlelet os and make the pdf launcher load the new class name and replace the pdf kindlet jar. (Not really easy, but I think it's easier). Personally, I would just wait for the Kindle 3 DX.

Last edited by yifanlu; 12-25-2010 at 09:46 PM.
yifanlu is offline   Reply With Quote