Thread: Aura ONE Factory reset v. manual reset
View Single Post
Old 07-27-2020, 10:46 PM   #3
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by geek1011 View Post
I'm not sure exactly which reset you are referring to (e.g. the one Kobo is referring to changed behaviour last year). For sync issues, a sign-out should be enough to fix it.

Signing out is the simplest type of reset. It only clears the KOBOeReader partition, which is then regenerated on the next reboot, and requires you to sign in and add your books again. It also clears some config files from the rootfs, but this isn't really relevant for users. It is generally used to fix database issue. I don't remember if it preserves sideloaded books or not (by only removing the .kobo folder).
This doesn't touch the sideloaded books. They will still be there and get imported after the setup is done. Some of the changes in the config files in the rootfs do affect the user, as it will remove any saved WiFi networks.
Quote:
The next type is the factory reset from the device info settings page. This one is pretty much the same thing on recent firmware versions.
It wipes the book partition. I assume that it formats it, but, I've never checked.
Quote:
Finally, there is the hard/manual reset, which is triggered from the developer options (or the device info page on older firmware versions), the boot process, or the critical error screen. This reset will also restore the firmware in the rootfs from fs.tgz in the recoveryfs partition. This will work in all cases, except for if /bin/busybox (including /bin/sh and other symlinks), /etc/u-boot/*, and /usr/local/Kobo/pickel are missing on the rootfs on certain devices which don't seem to be able to trigger it directly from u-boot. There is a small risk when doing this kind of reset since the bootloader is overwritten and restored during the process (I once ran into this issue when resetting my Mini).
I think the risk is pretty minimal. And it probably is mainly for people fiddling under the covers. Or, if the internal storage is failing. The biggest risk might be the battery running out at exactly the wrong time.


@issybird: To me, it depends on how much time you have, and what you have already done. I tend to do the signout, and if it fails, just go to the full factory reset. I haven't had the latter fail on me.

It is interesting that purchased books are syncing, but OD books. That to me suggests the link between your OD and Kobo account has been lost. You could sign out of that and back in. But, at this point, I think I'd cut my losses and do the factory reset.
davidfor is offline   Reply With Quote