Quote:
Originally Posted by DiapDealer
It starts. It's still registered. And it connects/syncs/browses fine (B002 prefix; latest 2.5.8 software). But it barely holds a charge. Took me 10 minutes just to remember how to restart it from the menus, and I must have tapped the screen at least 27 different times doing that much! It's like playing with one of those old LED football handheld games, but much less fun. 
Anyway. I can't begin to remember how I would go about browsing the file system. If it involves installing software on a PC, I'm afraid I'm not interested. |
Hahaha.. the muscle memory is so funny. We are now too much accustomised with a touch screen. I have the same experience when I have to use an old non-touch screen keyboard only Samsung phone because of the charger of my main phone died and the replacement did not arrive yet.
I and knc1 active in
https://www.mobileread.com/forums/sh...d.php?t=319505
In Windows, the file system is hidden. I have to use NiLuJi's jailbreak and usbnetwork in the Kindle DX; TightVNC and Putty in PC. So yes, it involved PC. Akh, pity that you won't deal with PC! But knowing that some Gen 2 survive if it is not factory reset showed something wrong with the factory reset and de-registration routines in firmware 2.5.8 plus Kindle service update.
The two directories that I pointed-out before are the directories where I believe Amazon store the certificate to connect to their server. Factory reset Kindle Gen 1-2 lost this and Amazon server currently did not hold the backup certificate. If we could find the certificate from a working Gen 2 Kindle, we might able to patch this certificate if it is public domain and not so encrypted.
What happened in 2017 was probably Amazon opened access to the backup certificate for a while and close it again with a motivation behind.