MobileRead Forums - View Single Post - PW1 Brick Recovery - Rescue Pack installed, stuck on Tree/Logo Screen

AirRaven · 08-04-2015, 04:51 PM

Hey,

This is, obviously, self-inflicted - I was attempting to install the Screensaver Hack's Python package on my (downgraded) 5.3.9 Paperwhite 1 using MRPackageInstaller, and the installation process hung for upward of ten minutes - having taken leave of my senses, I decided to force-reboot the Kindle at that point to try and escape that process.

The result's that my Kindle's now hanging on the Kindle Logo/Tree screen with a spinning progress wheel underneath it - with no progress beyond that. I've already tried discharging/fully recharging my battery- obviously, that wouldn't have helped in this case, but it cropped up in every prior thread I could find as the first thing that ought to be tried.

I'd just installed the Rescue Pack package a single reboot before this happened, and I was hoping to be able to activate that - but the Kindle doesn't show up as an accessible drive in Windows Explorer. It's clearly recognised as a USB Storage device, and shows up in Explorer as a grayed-out drive, but attempting to open it doesn't seem to make anything happen. Thus, I've no immediately obvious way of getting into Diags mode/forcing a factory reset, since they require the ability to push files to the device to activate.

However, since something is being recognised at the other end of the USB link, I went and booted into Linux to check some logs. Here's the output of /var/log/syslog upon plugging in the Kindle:

Code:

Aug  4 20:04:07 ubuntu kernel: [  600.398194] usb 1-1: new high-speed USB device number 7 using xhci_hcd
Aug  4 20:04:07 ubuntu kernel: [  600.532601] usb 1-1: New USB device found, idVendor=1949, idProduct=0004
Aug  4 20:04:07 ubuntu kernel: [  600.532611] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug  4 20:04:07 ubuntu kernel: [  600.532617] usb 1-1: Product: Amazon Kindle
Aug  4 20:04:07 ubuntu kernel: [  600.532622] usb 1-1: Manufacturer: Amazon
Aug  4 20:04:07 ubuntu kernel: [  600.532626] usb 1-1: SerialNumber: B0241502247402Q0
Aug  4 20:04:07 ubuntu kernel: [  600.536671] usb-storage 1-1:1.0: USB Mass Storage device detected
Aug  4 20:04:07 ubuntu kernel: [  600.537055] scsi host10: usb-storage 1-1:1.0
Aug  4 20:04:07 ubuntu mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0/usb1/1-1"
Aug  4 20:04:07 ubuntu mtp-probe: bus: 1, device: 7 was not an MTP device
Aug  4 20:04:08 ubuntu kernel: [  601.536494] scsi 10:0:0:0: Direct-Access     Kindle   Internal Storage 0100 PQ: 0 ANSI: 2
Aug  4 20:04:08 ubuntu kernel: [  601.537770] sd 10:0:0:0: Attached scsi generic sg3 type 0
Aug  4 20:04:08 ubuntu kernel: [  601.546385] sd 10:0:0:0: [sdc] Attached SCSI removable disk
Aug  4 20:04:08 ubuntu systemd-udevd[4074]: error: /dev/sdc: No medium found

Is there any way forward possible here without a serial cable? Perhaps a way of forcing it to mount the device manually?

I mean, I'm probably out of luck here given the nature of what caused this in the first place- but it would be nice to know for certain.

08-04-2015, 04:51 PM	#1
AirRaven Member Posts: 12 Karma: 10 Join Date: Aug 2015 Device: Kindle Paperwhite (1st gen), Kindle 3 (3G)	PW1 Brick Recovery - Rescue Pack installed, stuck on Tree/Logo Screen Hey, This is, obviously, self-inflicted - I was attempting to install the Screensaver Hack's Python package on my (downgraded) 5.3.9 Paperwhite 1 using MRPackageInstaller, and the installation process hung for upward of ten minutes - having taken leave of my senses, I decided to force-reboot the Kindle at that point to try and escape that process. The result's that my Kindle's now hanging on the Kindle Logo/Tree screen with a spinning progress wheel underneath it - with no progress beyond that. I've already tried discharging/fully recharging my battery- obviously, that wouldn't have helped in this case, but it cropped up in every prior thread I could find as the first thing that ought to be tried. I'd just installed the Rescue Pack package a single reboot before this happened, and I was hoping to be able to activate that - but the Kindle doesn't show up as an accessible drive in Windows Explorer. It's clearly recognised as a USB Storage device, and shows up in Explorer as a grayed-out drive, but attempting to open it doesn't seem to make anything happen. Thus, I've no immediately obvious way of getting into Diags mode/forcing a factory reset, since they require the ability to push files to the device to activate. However, since something is being recognised at the other end of the USB link, I went and booted into Linux to check some logs. Here's the output of /var/log/syslog upon plugging in the Kindle: Code: Aug 4 20:04:07 ubuntu kernel: [ 600.398194] usb 1-1: new high-speed USB device number 7 using xhci_hcd Aug 4 20:04:07 ubuntu kernel: [ 600.532601] usb 1-1: New USB device found, idVendor=1949, idProduct=0004 Aug 4 20:04:07 ubuntu kernel: [ 600.532611] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 4 20:04:07 ubuntu kernel: [ 600.532617] usb 1-1: Product: Amazon Kindle Aug 4 20:04:07 ubuntu kernel: [ 600.532622] usb 1-1: Manufacturer: Amazon Aug 4 20:04:07 ubuntu kernel: [ 600.532626] usb 1-1: SerialNumber: B0241502247402Q0 Aug 4 20:04:07 ubuntu kernel: [ 600.536671] usb-storage 1-1:1.0: USB Mass Storage device detected Aug 4 20:04:07 ubuntu kernel: [ 600.537055] scsi host10: usb-storage 1-1:1.0 Aug 4 20:04:07 ubuntu mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0/usb1/1-1" Aug 4 20:04:07 ubuntu mtp-probe: bus: 1, device: 7 was not an MTP device Aug 4 20:04:08 ubuntu kernel: [ 601.536494] scsi 10:0:0:0: Direct-Access Kindle Internal Storage 0100 PQ: 0 ANSI: 2 Aug 4 20:04:08 ubuntu kernel: [ 601.537770] sd 10:0:0:0: Attached scsi generic sg3 type 0 Aug 4 20:04:08 ubuntu kernel: [ 601.546385] sd 10:0:0:0: [sdc] Attached SCSI removable disk Aug 4 20:04:08 ubuntu systemd-udevd[4074]: error: /dev/sdc: No medium found Is there any way forward possible here without a serial cable? Perhaps a way of forcing it to mount the device manually? I mean, I'm probably out of luck here given the nature of what caused this in the first place- but it would be nice to know for certain.