MobileRead Forums - View Single Post

AusTim · 07-15-2012, 05:53 AM

I have a Kindle DX and I think the primary problem is that 3G isn't working. I have been through three levels of support with amazon, now I'm waiting for an Engineer to get in touch with me... I'm wondering if anyone here has any suggestions though, as the support people I spoke to didn't seem particularly knowledgeable (although they were very polite and responsive I'll admit).

The Problem

Primarily 3G seems to be buggered, it seems to try to connect but just gets no connection and turns off again. This means I can't register my kindle (it was registered, but I tried a factory reset).
Last book read and a few other things don't seem to be persisting, although it's possibly because of the 3G issue.

Some things I have tried

Restarting the device via Settings > Menu > Restart
Restarting the device by holding power for 30 seconds
Resetting the device to factory default via Settings > Menu
I updated the firmware (to 2.5.8) and tried all of the above
311 from settings: Scans for carriers but then doesn't show a list and goes straight back to the settings screen
411 from settings: The "Radio Serial Number" is blank, "Roaming Version Number" is -1. If I turn 3G on before doing it, then it waits saying "Retrieving data" until 3G goes off again.
611: Says "Sorry – WAN info is not available at this time"
I definitely have mobile coverage, I used to be able to access 3G here (and I can from my phone). My problems just started one day and I haven't been able to connect to 3G anywhere since then.

Some pictures
https://docs.google.com/open?id=0BxZ...Hp0Wk9uMmFxaTQ
https://docs.google.com/open?id=0BxZ...2pHWWNZWUU3QXM

Any advice would be appreciated, even if it's just comparing your 411 info to mine. I'd like to know if your "Radio Serial Number" appears all the time or just when 3G is on.

I don't mind getting my hands dirty as I think it's probably out of warranty any way so if it's possible that rooting it to get SSH access will help me debug the problem then I'd be open to it.

07-15-2012, 05:53 AM	#1
AusTim Junior Member Posts: 3 Karma: 10 Join Date: Jul 2012 Device: Kindle DX	Kindle DX 3G Dead I have a Kindle DX and I think the primary problem is that 3G isn't working. I have been through three levels of support with amazon, now I'm waiting for an Engineer to get in touch with me... I'm wondering if anyone here has any suggestions though, as the support people I spoke to didn't seem particularly knowledgeable (although they were very polite and responsive I'll admit). The Problem Primarily 3G seems to be buggered, it seems to try to connect but just gets no connection and turns off again. This means I can't register my kindle (it was registered, but I tried a factory reset). Last book read and a few other things don't seem to be persisting, although it's possibly because of the 3G issue. Some things I have tried Restarting the device via Settings > Menu > Restart Restarting the device by holding power for 30 seconds Resetting the device to factory default via Settings > Menu I updated the firmware (to 2.5.8) and tried all of the above 311 from settings: Scans for carriers but then doesn't show a list and goes straight back to the settings screen 411 from settings: The "Radio Serial Number" is blank, "Roaming Version Number" is -1. If I turn 3G on before doing it, then it waits saying "Retrieving data" until 3G goes off again. 611: Says "Sorry – WAN info is not available at this time" I definitely have mobile coverage, I used to be able to access 3G here (and I can from my phone). My problems just started one day and I haven't been able to connect to 3G anywhere since then. Some pictures https://docs.google.com/open?id=0BxZ...Hp0Wk9uMmFxaTQ https://docs.google.com/open?id=0BxZ...2pHWWNZWUU3QXM Any advice would be appreciated, even if it's just comparing your 411 info to mine. I'd like to know if your "Radio Serial Number" appears all the time or just when 3G is on. I don't mind getting my hands dirty as I think it's probably out of warranty any way so if it's possible that rooting it to get SSH access will help me debug the problem then I'd be open to it.