MobileRead Forums - View Single Post

B1bliomania · 12-13-2019, 07:02 PM

Oh hello there, autoscript maintainer

While it happened during the KoReader auto-installation, I'm not entirely sure it's KoReader's fault. I would, however, say that KoReader didn't install properly with the autoscript which led to retrying and rebooting the ebook reader several times - which resulted in bricking.

Please note that my OS is Linux Mint 19.2 and my Kobo Aura H2O had the latest firmware that can be downloaded through Sync function. I would also like to mention that I felt the stability went down with frequent auto-reset after the major firmware update that changed the loading dots from 4 square to 3 circles (sorry for not having better description).

I used the 'One-click install package' with the build that contains both KoReader and Plato. The installation itself went successful but the app icons were not listed in the Kobo menu and what seemed to be the app assets seemed to be scattered across the collection (I believe your thread had a posting with similar incident). I deleted those and the installation folder, then tried again - with same result. So I thought, "hmm ok so the script might be not suppressing the reader from accessing the app folders. This time I'll manually check if the script is adding the necessary code line before taking the reader off the computer'. In order to do so, I clean up the files again and rebooted. At this point, it bricked.

Currently, when I plug my ebook to any power source or computer, the screen would flicker a few times like a reboot but nothing will come on (= I do not see the loading dots). It is unresponsive to screen touch or factory reset attempts, and the my computer would not recognize it. And I think it's not even charging properly.

I read through the forum post entries but the cases of similar incidents didn't really have any solution in it. Seeing as I'm poor at the moment with tons of stuff to need to be read

, I decided to pop the reader open to fix. Any tips on opening up the reader or how to properly use the sd image are welcome.

(P.S Should I keep the original sd card and its content, or replace/overwritting would be just fine?)

12-13-2019, 07:02 PM	#7
B1bliomania Junior Member Posts: 4 Karma: 10 Join Date: Dec 2019 Device: Kobo Aura H2O (Gen 1)	Oh hello there, autoscript maintainer While it happened during the KoReader auto-installation, I'm not entirely sure it's KoReader's fault. I would, however, say that KoReader didn't install properly with the autoscript which led to retrying and rebooting the ebook reader several times - which resulted in bricking. Please note that my OS is Linux Mint 19.2 and my Kobo Aura H2O had the latest firmware that can be downloaded through Sync function. I would also like to mention that I felt the stability went down with frequent auto-reset after the major firmware update that changed the loading dots from 4 square to 3 circles (sorry for not having better description). I used the 'One-click install package' with the build that contains both KoReader and Plato. The installation itself went successful but the app icons were not listed in the Kobo menu and what seemed to be the app assets seemed to be scattered across the collection (I believe your thread had a posting with similar incident). I deleted those and the installation folder, then tried again - with same result. So I thought, "hmm ok so the script might be not suppressing the reader from accessing the app folders. This time I'll manually check if the script is adding the necessary code line before taking the reader off the computer'. In order to do so, I clean up the files again and rebooted. At this point, it bricked. Currently, when I plug my ebook to any power source or computer, the screen would flicker a few times like a reboot but nothing will come on (= I do not see the loading dots). It is unresponsive to screen touch or factory reset attempts, and the my computer would not recognize it. And I think it's not even charging properly. I read through the forum post entries but the cases of similar incidents didn't really have any solution in it. Seeing as I'm poor at the moment with tons of stuff to need to be read , I decided to pop the reader open to fix. Any tips on opening up the reader or how to properly use the sd image are welcome. (P.S Should I keep the original sd card and its content, or replace/overwritting would be just fine?)