MobileRead Forums - View Single Post

zkat · 01-28-2012, 02:19 PM

Hey,

I installed the latest jailbreak on a new Kindle Touch (got it yesterday), and everything went well. I played around with the system a bit, (most importantly, I disabled logging altogether, which may have been a bad idea) and then downloaded the Launchpad installer, put it in the root of the filesystem, and rebooted. I got an update error 3, and now my Touch won't complete boot. I've tried forcing a reboot several times, leaving the kindle alone for a while, and it's just staying on the screen with the tree, no progress bar or anything.

It gets a little worse, though, because even though dmesg shows that the OS recognized the Kindle as a removable disk ('[sde] Attached SCSI removable disk'), I'm unable to actually mount the partition to try to fix the issue. I suspect this may have to do with having been a bit overeager with things and configured USB networking to automatically start (using option #1 in https://wiki.mobileread.com/wiki/Kind...USB_Networking). Unfortunately, I can't connect to the Kindle using USB Networking, either (or at least I don't have a device called usb0).

Any ideas on what I can do? I've seen threads talking about how some bricks give you filesystem access for a few seconds so you can drop a repair script in there, and others talking about needing a serial cable to be able to do anything.

Thanks in advance.

01-28-2012, 02:19 PM	#1
zkat Member Posts: 19 Karma: 10 Join Date: Jan 2012 Device: Kindle Touch	Bricked Kindle Touch Hey, I installed the latest jailbreak on a new Kindle Touch (got it yesterday), and everything went well. I played around with the system a bit, (most importantly, I disabled logging altogether, which may have been a bad idea) and then downloaded the Launchpad installer, put it in the root of the filesystem, and rebooted. I got an update error 3, and now my Touch won't complete boot. I've tried forcing a reboot several times, leaving the kindle alone for a while, and it's just staying on the screen with the tree, no progress bar or anything. It gets a little worse, though, because even though dmesg shows that the OS recognized the Kindle as a removable disk ('[sde] Attached SCSI removable disk'), I'm unable to actually mount the partition to try to fix the issue. I suspect this may have to do with having been a bit overeager with things and configured USB networking to automatically start (using option #1 in https://wiki.mobileread.com/wiki/Kind...USB_Networking). Unfortunately, I can't connect to the Kindle using USB Networking, either (or at least I don't have a device called usb0). Any ideas on what I can do? I've seen threads talking about how some bricks give you filesystem access for a few seconds so you can drop a repair script in there, and others talking about needing a serial cable to be able to do anything. Thanks in advance.