View Single Post
Old 02-22-2013, 02:47 PM   #201
twobob
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.
 
twobob's Avatar
 
Posts: 6,552
Karma: 6021142
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
Quote:
Originally Posted by hawhill View Post
(-_-): You need a terminal window and you'll have to use the shell. Switch to the path where the k3flasher binary is stored. Make sure it can be executed: "chmod +x k3flasher". Make a backup of the current state of your device, no matter if it is broken. Call the backup script in order to do so: "sh k3-backup.sh", or better, dpavlin's included Perl script: "perl k3flasher-incremental-backup.pl". Then use k3flasher to write a clean rootfs, kernel or bootloader (depending on what is broken).
That is EXCELLENT advice for all.

Noted.
twobob is offline   Reply With Quote