MobileRead Forums - View Single Post - PRS-T1 Reader does not work anymore

Sing Sing · 08-27-2018, 09:51 AM

Sorry I copied the link from the wiki without checking it. Here's one that works:
https://projects.mobileread.com/read...scue/20121208/

Try to boot it and access the T1's shell with PuTTY.

Damage to SETTING shouldn't be fatal, that's partition 7. For Windows to see any USB device, the T1 has to boot up and load it's linux kernel, for that it needs the first part of the eMMC to be intact, up to and including partition 1. It also needs a root filesystem, which is what rupor-rescue is on the SD-card.

So if you do get it to boot, don't repartition it with Windows tools. If you damage the boot loader or the first partition you won't be able to get the device back.

If you can't get rupor rescue to boot, then maybe you wrote the SETTING image to the first part of the eMMC, in which case the boot loader is already damaged.

08-27-2018, 09:51 AM	#4
Sing Sing Member Posts: 17 Karma: 196 Join Date: Aug 2018 Device: none	Sorry I copied the link from the wiki without checking it. Here's one that works: https://projects.mobileread.com/read...scue/20121208/ Try to boot it and access the T1's shell with PuTTY. Damage to SETTING shouldn't be fatal, that's partition 7. For Windows to see any USB device, the T1 has to boot up and load it's linux kernel, for that it needs the first part of the eMMC to be intact, up to and including partition 1. It also needs a root filesystem, which is what rupor-rescue is on the SD-card. So if you do get it to boot, don't repartition it with Windows tools. If you damage the boot loader or the first partition you won't be able to get the device back. If you can't get rupor rescue to boot, then maybe you wrote the SETTING image to the first part of the eMMC, in which case the boot loader is already damaged.