View Single Post
Old 12-08-2015, 09:02 AM   #20
frostschutz
Linux User
frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.
 
frostschutz's Avatar
 
Posts: 2,282
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
Quote:
Originally Posted by rashkae View Post
No, Manually installing effectively bricks your device (Untill you go through the normal setup, or a new workaround is found.)
Thanks for the heads-up. I made a complete backup before updating.

I've had this issue for a while now, but ... I get random USB bus resets with the Kobo H2O connected to Linux PC. This caused read errors while making the backup (and device redetected under a different name). So I had to re-mount and re-run the backup. And this happened again after copying the update data on and umounting the device. So I had to mount again and verify the update files were correct.

That aside the update itself went without a hitch. Although it turns out the Kobo was registered properly at the time I tried it. I forgot to unregister it after testing my autoshelf shelf sync behaviour some time ago.

So I can't say whether it would brick when not properly registered... but the USB resets worry me.

Emptying registration after the update: device itself works, but when trying to go to settings->account, nickel hangs with 100% CPU usage. So it definitely doesn't seem to like something about it...

Putting crap in the fields instead of leaving them empty '' raises the "critical error" you mentioned. So it seems you can still use fake registration if you stick to empty fields and avoid the "accounts" dialog in the setting.

Last edited by frostschutz; 12-08-2015 at 09:18 AM.
frostschutz is offline   Reply With Quote