Hello everyone, first I'd like to thank you all for the resources compiled in this forum. I've spent the last few days lurking trying to get my Kindle touch up and running and reading about debricking and different methods around this forum.
The Kindle Touch was not jailbroken, but it was sideloaded with a lot of Calibre epubs. After normal use it gave me the dreaded "Your Kindle Needs Repair" screen and I let it sit on my bookshelf for several months since. Now I find myself in between jobs with a wish to dig back into reading on my Kindle. Unfortunately connecting to the serial interface is impossible with my equipment. I am currently working with Windows 10, a Windows 7 vm and Ubuntu.
Yesterday, after a couple hours researching on the forum and charging my kindle I navigated to K:/ (which was only accessible for around 20 seconds before it would disappear in windows explorer) and deposited a 0byte file "DO_FACTORY_RESET" (or was it restore? still, I definitely used the correct form) and to my amazement, the kindle gave me a different screen for the first time in months. That sweetness soon turned into sour when after several minutes of waiting I arrived back at the "Your Kindle Needs Repair" screen. Darn.
The kicker is that the Kindle is now stuck in what I believe is called "Fake USB Mode" where all it displays is a 0byte Disk image in explorer that never fully loads. Uninstalling in device manager proves fruitless (even with automatic driver installation turned off) as it asserts itself as a disk image) There is also a separate entry in device manager under "mobile devices" called "K:/" that appears along with the Kindle. Uninstalling both of these in hopes of loading a driver that can read from the Kindle again has been useless thus far.
After more reading I looked into Kubrick (Kubrick could not detect my kindle) After Kubrick I tried MFGtool in windows 10 (crashes at USB setup). Then I tried MFGtool in a Windows 7 virtual machine. At this point, with the proper filters it did see my kindle but it would disconnect before it could do finish doing anything useful. At most I saw it freeze on the Treeboy splash screen.
Ubuntu is having a tough time making anything out of the plugged in Kindle. lsusb was listing the Kindle for a few seconds each time I would restart the device. I used imx usb loader but it did not cause any changes on the kindle.
I am now having problems getting the kindle to properly recognize in a virtual machine. But in my normal Windows installation, the problem hasn't changed at all (empty disk, leading me to believe that it's just my inexperience with virtualbox causing me grief). But it should be noted that the device doesn't show up in ubuntu when I list devices either, now. I feel like i'm just making it worse at this point.
:help: I'm desperate to get this thing working. Is there something I've missed or vitally misconstrued? Am I looking at a irreparibly bricked device? Does anyone have a spare kindle collecting dust and a few stamps laying around?:rolleyes:
Thank you in advance for the help!
The Kindle Touch was not jailbroken, but it was sideloaded with a lot of Calibre epubs. After normal use it gave me the dreaded "Your Kindle Needs Repair" screen and I let it sit on my bookshelf for several months since. Now I find myself in between jobs with a wish to dig back into reading on my Kindle. Unfortunately connecting to the serial interface is impossible with my equipment. I am currently working with Windows 10, a Windows 7 vm and Ubuntu.
Yesterday, after a couple hours researching on the forum and charging my kindle I navigated to K:/ (which was only accessible for around 20 seconds before it would disappear in windows explorer) and deposited a 0byte file "DO_FACTORY_RESET" (or was it restore? still, I definitely used the correct form) and to my amazement, the kindle gave me a different screen for the first time in months. That sweetness soon turned into sour when after several minutes of waiting I arrived back at the "Your Kindle Needs Repair" screen. Darn.
The kicker is that the Kindle is now stuck in what I believe is called "Fake USB Mode" where all it displays is a 0byte Disk image in explorer that never fully loads. Uninstalling in device manager proves fruitless (even with automatic driver installation turned off) as it asserts itself as a disk image) There is also a separate entry in device manager under "mobile devices" called "K:/" that appears along with the Kindle. Uninstalling both of these in hopes of loading a driver that can read from the Kindle again has been useless thus far.
After more reading I looked into Kubrick (Kubrick could not detect my kindle) After Kubrick I tried MFGtool in windows 10 (crashes at USB setup). Then I tried MFGtool in a Windows 7 virtual machine. At this point, with the proper filters it did see my kindle but it would disconnect before it could do finish doing anything useful. At most I saw it freeze on the Treeboy splash screen.
Ubuntu is having a tough time making anything out of the plugged in Kindle. lsusb was listing the Kindle for a few seconds each time I would restart the device. I used imx usb loader but it did not cause any changes on the kindle.
I am now having problems getting the kindle to properly recognize in a virtual machine. But in my normal Windows installation, the problem hasn't changed at all (empty disk, leading me to believe that it's just my inexperience with virtualbox causing me grief). But it should be noted that the device doesn't show up in ubuntu when I list devices either, now. I feel like i'm just making it worse at this point.
:help: I'm desperate to get this thing working. Is there something I've missed or vitally misconstrued? Am I looking at a irreparibly bricked device? Does anyone have a spare kindle collecting dust and a few stamps laying around?:rolleyes:
Thank you in advance for the help!