Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle > Kindle Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 08-18-2012, 03:19 AM   #1
xms
Junior Member
xms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it is
 
Posts: 9
Karma: 2304
Join Date: Aug 2012
Device: kindke dx us
Unbriking Kindle DX

Hi.

My Kindle DX (US cdma ver.2009) now doesn't want to boot.
In serial console i can see this log (below).

As i understand system partition is damaged somehow
(kinit: init not found!)

What can i do to try to repair?
As i undersatan need to use Load MMC0 over USB storage (with rootfs.img/rootfs.tar.gz) i have password (with KindleDiagnosticTool)
or maybe it is possible to browse/fix FS only by commands from console? (i can't type anything from hyperterminal now)

Can somebody help me with getting this image from DX US?
Plz help

Thanks!

bootLOG:
Spoiler:
U-Boot 1.3.0-rc3-lab126 (Jun 18 2009 - 17:03:50)

CPU: Freescale i.MX31 at 398 MHz
Board: i.MX31 Mario
S/N: B004182193220199
Board Id: NP1A000000000000
DRAM: 128 MB
Flash: 8 MB
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
boot globals: computed residue = 0xDEBB20E3, checksum = 0x0B2FFEA2
boot globals: passed
Using fallback kernel. Clearing boot globals
Booting Secondary kernel...
## Booting image at a0400000 ...
Image Name: s047290-1004221911-TN2~2.6.22.19
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1887236 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
OK


Starting kernel ...

Spoiler:
Uncompressing Linux............................................. ................
............................................ done, booting the kernel.
RCSR register - a7f0000
boot: I defcut::Atlas power cut encountered
2.6.22.19-lab126 #3 PREEMPT Thu Apr 22 19:26:59 PDT 2010 armv6l 532MHz
INFO:Using Nell keypad setting
INFO:Loaded module /lib/modules/mxc_keyb.ko kb_rev=4 (22560 bytes)
INFO:Using Turing/Nell fiveway setting
INFO:Loaded module /lib/modules/fiveway.ko SELECT_hold_timeout=0 SELECT_auto_rep
eat_time=0 fiveway_rev=2 (26896 bytes)
INFO:/dev/input/event0:keypad device opened successfully (count=1)
INFO:/dev/input/event1:keypad device opened successfully (count=2)
ERROR:/dev/input/event2:No such device(19)
ERROR:/dev/input/event3:No such device(19)
Press [ENTER] for recovery menu... 0 /INFO:Partition table verified for /d
ev/mmcblk0
INFO:Checking for updates... (auto-pilot mode)
/dev/mmcblk0p4:
CHS=4/16/111615 size=3657400320 bytes
flag type first last lba first lba size
Partition p1:
0x00 0x0b 2 <large> 2 7143358
CHS: 0/0/3 - <large>
Partition p2:
Partition p3:
Partition p4:
INFO:Setup loop device /dev/loop0 for /dev/mmcblk0p4 + 1024
INFO:No update*.bin found, no update needed.
INFO:no updates found.
BOOTING DEFAULT.
argc == 9
argv[0]: "kinit"
argv[1]: "console=ttymxc0,115200"
argv[2]: "mem=128M"
argv[3]: "ro"
argv[4]: "ip=none"
argv[5]: "root=/dev/mmcblk0p1"
argv[6]: "lpj=2654208"
argv[7]: "panic=10"
argv[8]: "quiet"
Running ipconfig
argc == 4
argv[0]: "IP-Config"
argv[1]: "-i"
argv[2]: "Linux kinit"
argv[3]: "ip=none"
IP-Config: no devices to configure
kinit: do_mounts
kinit: name_to_dev_t(/dev/mmcblk0p1) = mmcblk0p1(179,1)
kinit: root_dev = mmcblk0p1(179,1)
kinit: failed to identify filesystem /dev/root, trying all
kinit: trying to mount /dev/root on /root with type ext3
kinit: trying to mount /dev/root on /root with type cramfs
kinit: trying to mount /dev/root on /root with type msdos
kinit: trying to mount /dev/root on /root with type vfat
kinit: Unable to mount root fs on device mmcblk0p1(179,1)
Checking for init: /sbin/init
Checking for init: /bin/init
Checking for init: /etc/init
Checking for init: /sbin/init.sysvinit
Checking for init: /bin/sh
kinit: init not found!
Kernel panic - not syncing: Attempted to kill init!
kernel BUG at kernel/panic.c:101!
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = c7c64000
[00000000] *pgd=87ee0031, *pte=00000000, *ppte=00000000
Internal error: Oops: 817 [#1] PREEMPT

Last edited by dreams; 08-19-2012 at 03:16 PM. Reason: added spoilers - moderator
xms is offline   Reply With Quote
Old 08-18-2012, 03:26 AM   #2
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,819
Karma: 6314522
Join Date: Feb 2012
Device: Too many.
Please put that kernel message log inside of 'SPOILER' '/SPOILER' tags using [ and ] in place of the ' shown in this sentence.
knc1 is offline   Reply With Quote
Old 08-18-2012, 04:56 AM   #3
xms
Junior Member
xms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it is
 
Posts: 9
Karma: 2304
Join Date: Aug 2012
Device: kindke dx us
unbriking kindle dx

also when i'm trying to update via recovery menu (U - update on userstore)
console says:
ERROR: OTA version not supported.
ERROR:Could not unbundle /mnt-us/update2.bin
this is last 2.5.8.bin from amazon site (any previous like 2.3.3 also not working)
Why is this?
Thanks for ANY help!


LOG:
Spoiler:


Developer Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose: 6 /

/dev/mmcblk0p4:
CHS=4/16/111615 size=3657400320 bytes
flag type first last lba first lba size
Partition p1:
0x00 0x0b 2 <large> 2 7143358
CHS: 0/0/3 - <large>
Partition p2:
Partition p3:
Partition p4:
INFO:Setup loop device /dev/loop0 for /dev/mmcblk0p4 + 1024
INFO:Found update2.bin
INFO:Skipping battery charge check
INFO:Found bundle /mnt-us/update2.bin
uImage OK : Kernel1
uImage OK : Kernel2
u-boot OK : Bootloader1
u-boot OK : Bootloader2
INFO:Both kernel images are valid, no copying necessary.
INFO:Both kernel images are valid, no copying necessary.
INFO:*** NORMAL MODE MEANS WE UPDATE BOTH KERNELS AND ONE BOOTLOADER ***
*** CHECKING /mnt-us/update2.bin ***
ERROR: OTA version not supported.
ERROR:Could not unbundle /mnt-us/update2.bin
INFO:removing /mnt-us/update2.bin
xms is offline   Reply With Quote
Old 08-18-2012, 08:26 AM   #4
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,819
Karma: 6314522
Join Date: Feb 2012
Device: Too many.
Take a look at the first log you posted (and while looking at it, edit in some spoiler tags).

See the message from U-Boot that it could not read the environment variables?
See the message that it had to use the secondary kernel?

Either something over-wrote the start of your mmcblk0 (the raw device, before the partition table) or you had erase block failures the eMMC controller could not correct.
knc1 is offline   Reply With Quote
Old 08-19-2012, 06:35 AM   #5
xms
Junior Member
xms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it is
 
Posts: 9
Karma: 2304
Join Date: Aug 2012
Device: kindke dx us
Quote:
Originally Posted by knc1 View Post
See the message from U-Boot that it could not read the environment variables?
See the message that it had to use the secondary kernel?

Either something over-wrote the start of your mmcblk0 (the raw device, before the partition table) or you had erase block failures the eMMC controller could not correct.

So do you think that overwriting rootfs (with previous formatting)
with
3. Load MMC0 over USB storage
will not help me?

Maybe i can try to overwrite mmcblk0 with dump (if someone can provide it)
also?

(NB:anyway can someone give me the rootfs.img for DX b004 plz??)

Will
4. Erase MMC0
or
I. Initialize Partition Table (fdisk) and format FAT
help me somehow (if i'll had needed dumps from someone)?

Maybe formatting will exclude bad blocks (if they're the source of errors)?



Thanks for support.


p.s. sorry for dumbness but i can't find edit button to add [SPOILER] for my first message.
xms is offline   Reply With Quote
Old 08-19-2012, 11:10 AM   #6
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,819
Karma: 6314522
Join Date: Feb 2012
Device: Too many.
I am not familiar with the DX machine.
I do not know what you have done that got you into whatever situation you are in.
I do not know where you can get recovery images for a DX machine.

It should be obvious from the title that: 4. Erase MMC0
Is not going to improve your current situation.
Once you do that, if it does what it says, then the only firmware on the machine will be the iROM code (a very low level firmware loading command processor).

The Freescale ATK can still "talk" to your DX once you do that. So could the K3Flasher if you modified the code to include the i.MX31 related things rather than the i.MX35 stuff for the K3.

- - - -

Try looking for th edit button again, after you have made a few more posts. I think the system has a minimum of ten posts required before it turns on the edit button for a person.
knc1 is offline   Reply With Quote
Old 08-19-2012, 11:40 AM   #7
geekmaster
Всё гениальное просто.
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: 5,070
Karma: 6789001
Join Date: Nov 2011
Location: Щедрость не имеет пределов.
Device: *.*
Erasing MMC0 will also erase the bootloader. That is about as bricked as you can get. Not a good idea, and never necessary. You can flash without erasing.
geekmaster is offline   Reply With Quote
Old 08-19-2012, 02:13 PM   #8
xms
Junior Member
xms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it is
 
Posts: 9
Karma: 2304
Join Date: Aug 2012
Device: kindke dx us
Quote:
Originally Posted by knc1 View Post
I am not familiar with the DX machine.
I do not know what you have done that got you into whatever situation you are in.
I did nothing, first DX started to freeze on soft reboot, only few hardware reboots were effective and then hardware reboots also stop working
only recovery one is possible now.
By log i see that it has no access to rootfs, so i think to try to overwrite it with image (if someone can provide it)

As i understand (with help command) Uboot has no capabilities of browsing and diagnosting file systems..
Maybe i can upload and run some apps via loady/bootm cmds..

Also i have an idea of using
3.21 unofficial packet for Kindle DX
http://www.reddit.com/r/kindle/comme...stall_kindle_3
x_on_kindle_2_and_dx/
It seems overwrites rootfs with its update..

Did anybody with DX US prepared/used this 3.21 update?

Quote:
Originally Posted by knc1 View Post
I do not know where you can get recovery images for a DX machine.
That is the main problem for me..
Anybody with DX US here?? Plz help!

I can provide some instructions/packages from other forum to make backup images (if jailbreak is installed). Someday this backup can be necessary for DX US owners!

thanks!
xms is offline   Reply With Quote
Old 08-20-2012, 09:49 AM   #9
geekmaster
Всё гениальное просто.
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: 5,070
Karma: 6789001
Join Date: Nov 2011
Location: Щедрость не имеет пределов.
Device: *.*
Quote:
Originally Posted by xms View Post
Anybody with DX US here?? Plz help!

I can provide some instructions/packages from other forum to make backup images (if jailbreak is installed). Someday this backup can be necessary for DX US owners!

thanks!
Is your DX white or graphite (DXG)? They both run v2.5.8, so perhaps it does not matter.

EDIT: I see that your first post says CDMA, which would be the white DX. I suppose I could extract firmware images with dd when I get some time.

Last edited by geekmaster; 08-20-2012 at 10:30 AM.
geekmaster is offline   Reply With Quote
Old 08-20-2012, 10:26 AM   #10
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,819
Karma: 6314522
Join Date: Feb 2012
Device: Too many.
Quote:
Originally Posted by xms View Post
I can provide some instructions/packages from other forum to make backup images (if jailbreak is installed). Someday this backup can be necessary for DX US owners!

thanks!
It seems strange that you don't have a left over backup image or two on hand from when you tested those "instructions/packages".
knc1 is offline   Reply With Quote
Old 08-20-2012, 12:00 PM   #11
xms
Junior Member
xms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it is
 
Posts: 9
Karma: 2304
Join Date: Aug 2012
Device: kindke dx us
Quote:
Originally Posted by geekmaster View Post
EDIT: I see that your first post says CDMA, which would be the white DX. I suppose I could extract firmware images with dd when I get some time.[/COLOR]
My DX is US (b004) - yes, white DX, the very 1st DX produced.

It could be great if you do this images!
as i understand with somth like:
"dd if=/dev/mmcblk0 of=/mnt/us/mmcblk0_7688.dmp bs=512 count=7688"
"dd if=/dev/mmcblk0p1 of=/mnt/us/mmcblk0p1.dmp"

then as i undersatnd i need to
"3. Load MMC0 over USB storage"
it will show me 3 parttions sdx1=400mb, sdx2=24mb, sdx3=3Gb
and
"mkfs.ext3 /dev/sdX2"
"dd if=/path/to/mmcblk0p1.dmp of=/dev/sdX1 bs=1MiB"
and reboot

maybe i need to format sdx1 also to verify bad blocks?
is it ext3?

Big ThankS!

p.s. 2knc1: i start to learn all this only after DX crash..
xms is offline   Reply With Quote
Old 08-20-2012, 12:11 PM   #12
hawhill
Wizard
hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.
 
hawhill's Avatar
 
Posts: 1,179
Karma: 2116649
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
hm, you should be able to fix it with only with the "Load MMC0 over USB storage" option (if it is fixable and not a hardware defect).

That said, I'm not sure how the filesystems are laid out on the KDX b004. I guess from the sizes that sdx1 is rootfs, sdx2 is /var/... and the third one is the user store.

From the logs you have posted, the initramfs can not mount the root file system. So don't concentrate on the rest of the partitions yet, but rather check the root file system. Can you mount it on the host machine? Before messing with it, I would suggest to make a full dump of everything, i.e. the full block device (not just single partitions). And try to run e2fsck on the root file system then.
hawhill is offline   Reply With Quote
Old 08-20-2012, 02:16 PM   #13
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,819
Karma: 6314522
Join Date: Feb 2012
Device: Too many.
Quote:
Originally Posted by xms View Post
My DX is US (b004) - yes, white DX, the very 1st DX produced.

It could be great if you do this images!
as i understand with somth like:
"dd if=/dev/mmcblk0 of=/mnt/us/mmcblk0_7688.dmp bs=512 count=7688"
"dd if=/dev/mmcblk0p1 of=/mnt/us/mmcblk0p1.dmp"

then as i undersatnd i need to
"3. Load MMC0 over USB storage"
it will show me 3 parttions sdx1=400mb, sdx2=24mb, sdx3=3Gb
and
"mkfs.ext3 /dev/sdX2"
"dd if=/path/to/mmcblk0p1.dmp of=/dev/sdX1 bs=1MiB"
and reboot
No.
Not if your DX is running Linux.

You have to pay attention to the device names and naming conventions, those are not arbitrary, they mean things.

sd<anything> Scsi Device - /dev/sd<whatever> is a device holding a file system.

mmc<whatever> - this is a storage device, almost always flash, that has a "high level", embedded, controller that accepts "disk drive" commands.

Disk drives do: "Read,Write,Seek, ..."

MTD - Memory Technology Devices (here: flash) do: "Read, Erase, Re-program, ..."

"Flash" :: eeprom (electrically erasable programmable read only memory)

Add an embedded device controller to a MTD storage part == a MMC storage part != file system

With that $0.05 tour of naming conventions, you should now be able to read the above "dd" command and explain how and why you are about to trash the system storage if you use it as written.

Quote:
Originally Posted by xms View Post
maybe i need to format sdx1 also to verify bad blocks?
is it ext3?
No.
The controller of the underlying device manages the bad erase blocks (the underlaying device has "erase block" not "storage sectors" - the mmc controller is faking that).

It is using EEC to detect/correct and/or detect and retire the erase blocks in use at the storage media level.

The file system level should never see "bad blocks".

Quote:
Originally Posted by xms View Post
p.s. 2knc1: i start to learn all this only after DX crash..
So how did you test what you are intending to post?
knc1 is offline   Reply With Quote
Old 08-20-2012, 04:43 PM   #14
xms
Junior Member
xms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it is
 
Posts: 9
Karma: 2304
Join Date: Aug 2012
Device: kindke dx us
Quote:
Originally Posted by knc1 View Post
No.
Not if your DX is running Linux.
So how did you test what you are intending to post?
I did get this from here:
http://yifan.lu/2011/04/02/recoverin...rupt-kindle-2/
and other forum too (commands were near the same)
both sources had confirm this working for em.

Also I did post it here to verify and asking of where i'm wrong or right..
xms is offline   Reply With Quote
Old 08-20-2012, 04:46 PM   #15
xms
Junior Member
xms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it isxms knows what time it is
 
Posts: 9
Karma: 2304
Join Date: Aug 2012
Device: kindke dx us
Quote:
Originally Posted by knc1 View Post
No.
Not if your DX is running Linux.
So how did you test what you are intending to post?
I did get this from here:
http://yifan.lu/2011/04/02/recoverin...rupt-kindle-2/
and other forum too (commands were near the same)
both sources had confirm this working for em.

Also I did post it here to verify and asking of where i'm wrong or right..

p.s if you mean only about sdX name is wrong sure i will replace it with real name;
else i didn't understand clear what did you mean..

thanks
xms is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Kindle Touch unbriking troubles aguzman Kindle Developer's Corner 9 09-06-2012 08:23 AM
$0.01 in Kindle Store: Interactive Sudoku for Kindle 2 and Kindle DX - Volume 1 Xia Deals, Freebies, and Resources (No Self-Promotion) 2 11-07-2009 11:06 AM


All times are GMT -4. The time now is 07:22 AM.


MobileRead.com is a privately owned, operated and funded community.