View Single Post
Old 05-05-2013, 03:04 AM   #27
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,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by DNSB View Post
In the case of the Glo, that is what happened when I tried a factory reset.
Since this thread started, I had the "luck" to need to do the investigation.

The factory reset runs "/etc/init.d/rcS". This:

- installs U-Boot and kernal using dd commands
- reformats the other two partitions
- unpacks "/upgrade/fs.tgz" to the rootfs
- unpacks "/upgrade/db.tgz" to the data partition

That is essentially what is done when the firmware is updated, minus the reformatting.
davidfor is offline   Reply With Quote