Kindle DX memory extension

nergal11 · 11-10-2014, 01:19 AM

I have a Kindle DXG bought in 2013, international version.

I may want to increase its memory.

I saw in some battery replacement videos, (like this http://www.youtube.com/watch?v=5SoQZ0kD5Zk) that only things to replace fast in DX are, battery and, wireless module.

I may want to disable the wireless module, to use its sockets for memory. Any kind of memory, only thing necessary is that it will work.

And what about firmware? How it can be possible to adjust the firmware accordingly?

hawhill · 11-10-2014, 04:19 AM

The WAN module is connected via Mini-PCI-E connector, and is a half-size card, I think. It does *not* use the PCI-E bus, since there is no PCI-E bus. The connector standard specifies USB connections via that connector, and that is what is being used, AFAIK (re-check by issuing "lsusb" on the command line on your KDX).

Thus, you should be able to replace it with something like this: http://www.amazon.com/Express-Bracke.../dp/B00MTIOF1Q

I'm not aware if it had been done before, but it seems straightforward.

A thing I would check before going on is how the system reacts to the WAN module being missing.

When you have done the installation part, there are some ways I can think of to integrate it with the firmware:

- try to use it instead of the internal eMMC for the user data store. Could prove to be difficult, OTOH might not be too hard - I'd try with just "mount --bind" of the new block device over the user data partition block device. Or change all the references in the scripts. A benefit of doing it this way would be continued USB mass storage access (well, at least I think so).

- just mount it into the user store. Straightforward, needs just one new line in the boot scripts. Or even make it user-triggerable, say, via a launchpad script. Downside: You can not work on the files using USB mass storage. If you're using your device more "hacker-style" anyway, that might not bother you since you could use USB networking plus SCP/SFTP to access the files.

The latter part needs a bit of insight into scripting on Unix/Linux systems. Oh, and you might need to build a USB mass storage host driver for the kernel. The hardware part seems straightforward.

knc1 · 11-10-2014, 08:21 AM

You might want to keep in mind that we have never found the "magic key" on the DX or DXG required to de-brick them.

hawhill · 11-10-2014, 08:34 AM

Yep, important hint. So keeping everything in non-permanent storage and working on what has been tested (launchpad, usb networking) is probably the way to go.

11-10-2014, 01:19 AM	#1
nergal11 Junior Member Posts: 1 Karma: 10 Join Date: Nov 2014 Device: kindle	Kindle DX memory extension I have a Kindle DXG bought in 2013, international version. I may want to increase its memory. I saw in some battery replacement videos, (like this http://www.youtube.com/watch?v=5SoQZ0kD5Zk) that only things to replace fast in DX are, battery and, wireless module. I may want to disable the wireless module, to use its sockets for memory. Any kind of memory, only thing necessary is that it will work. And what about firmware? How it can be possible to adjust the firmware accordingly? Last edited by nergal11; 11-10-2014 at 03:18 AM.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Kindle Touch]Extension of Mplayer, sdmplayer-kt	SotongDJ	Kindle Developer's Corner	7	11-03-2012 02:47 AM
Image Viewer: An extension for GUI Launcher on Kindle Touch 5.1	starsy	Kindle Developer's Corner	20	08-04-2012 04:15 PM
Chrome Browser and send to Kindle extension	janrey	Amazon Kindle	14	12-08-2011 02:50 PM
Send websites / links to Kindle - extension for browser?	scenox	Kindle Developer's Corner	0	12-20-2010 12:23 PM

11-10-2014, 04:19 AM	#2
hawhill Wizard Posts: 1,379 Karma: 2155307 Join Date: Nov 2010 Location: Goettingen, Germany Device: Kindle Paperwhite, Kobo Mini	The WAN module is connected via Mini-PCI-E connector, and is a half-size card, I think. It does not use the PCI-E bus, since there is no PCI-E bus. The connector standard specifies USB connections via that connector, and that is what is being used, AFAIK (re-check by issuing "lsusb" on the command line on your KDX). Thus, you should be able to replace it with something like this: http://www.amazon.com/Express-Bracke.../dp/B00MTIOF1Q I'm not aware if it had been done before, but it seems straightforward. A thing I would check before going on is how the system reacts to the WAN module being missing. When you have done the installation part, there are some ways I can think of to integrate it with the firmware: - try to use it instead of the internal eMMC for the user data store. Could prove to be difficult, OTOH might not be too hard - I'd try with just "mount --bind" of the new block device over the user data partition block device. Or change all the references in the scripts. A benefit of doing it this way would be continued USB mass storage access (well, at least I think so). - just mount it into the user store. Straightforward, needs just one new line in the boot scripts. Or even make it user-triggerable, say, via a launchpad script. Downside: You can not work on the files using USB mass storage. If you're using your device more "hacker-style" anyway, that might not bother you since you could use USB networking plus SCP/SFTP to access the files. The latter part needs a bit of insight into scripting on Unix/Linux systems. Oh, and you might need to build a USB mass storage host driver for the kernel. The hardware part seems straightforward.

11-10-2014, 08:21 AM	#3
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	You might want to keep in mind that we have never found the "magic key" on the DX or DXG required to de-brick them.

11-10-2014, 08:34 AM	#4
hawhill Wizard Posts: 1,379 Karma: 2155307 Join Date: Nov 2010 Location: Goettingen, Germany Device: Kindle Paperwhite, Kobo Mini	Yep, important hint. So keeping everything in non-permanent storage and working on what has been tested (launchpad, usb networking) is probably the way to go.