View Single Post
Old 01-04-2014, 08:03 AM   #5
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by exachillus View Post
Hey thanks I think that was it. It makes sense that it checks for it. Who wants corrupt binaries nowadays.
I am not sure whether this was really the cause. With FW 3.0.1 [and I guess also with later FWs ] nickel reboots if it finds KoboRoot.tgz in .kobo (at least this is what I have observed on my Touch). Therefore, if KoboRoot.tgz is not processed because of low energy, and therefore not removed from .kobo before nickel is started, this should result in a reboot loop until the battery is empty. Maybe nickel does not reboot in this situation, if one connects the device to a PC via USB (I did not try).
Did you observe anything like that? Or did your Glo only refuse to process the KoboRoot.tgz, and behaved normally otherwise.
tshering is offline   Reply With Quote