Quote:
Originally Posted by AirRaven
In this case, I'd just used this trick to downgrade from 5.6.1.1 to 5.3.9 -
- - - - |
It is good to hear independent confirmation of that "HowTo" post.
Nice to know that there isn't an inadvertent deadly typo or missing step.
Although be sure to post an update here if you find a definite problem with the procedure.
Our readers are our best Q.A. staff.
- - - - -
After these messages:
Code:
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
You should be able to copy whatever is on the storage media with:
Code:
dd if=/dev/sdc of=brokeUSB.bin bs=4096
That will be a big file, the entire USB storage area.
But if the problem can be found in the MBR, Partition table, or Directory, then adding a count=32 to the above command should capture all of that.
If you have the disk space on your Linux machine, it might be instructive to keep a copy of whatever it is that has the machine caught in a 'fix-up' loop.
If you have the time and space to do the above, PM me, I can give you a place to sftp it to where NiLuJe and I can look at it.
- - - -
IIRC - the dmesg stopping at that point means the drive was detected, but no partition table could be found by the FAT32 driver.
But we have forensic tools that can determine the contents without the aid of the partition table (and/or directory) in the file you create from it.