View Single Post
Old 04-09-2012, 05:19 PM   #23
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Arrow PEBKAC* Error!

Quote:
Originally Posted by cscat View Post
Sometimes curiosity throws you into troubles... I just ran this script on my Touch and... tada... it bricked (I know, I know, it was stupid idea! )

I debricked it and the good thing is that I got it exactly back to the previous state (even my collections, hacks, etc.) with this. (I always keep a backup image inside my KT)

Moral of story: Do not try this script on Touch as of now (April 9th, 2012).
This tinysh script does not do anything that CAN brick your device.

Your "debricking" procedure was just a complicated way of restarting your kindle. When in doubt, restart first...

You could have restarted by holding the power button for 20 seconds to do a hard restart.

When you ran this K3 script on your Touch, it paused the framework to prevent the K3 keyboard from opening a framework search bar, and it was waiting for you to type a command on the K3 keyboard. It *does* say in the first paragraph "only for the K3", and it says that if the keyboard keys are not responding to keypresses, slide the power switch to "wake" the kindle and enable the keyboard.

Because the framework was paused, the screen contents would not change by pressing the Home or Power buttons until the framework is resumed (or the kindle restarted). You could have resumed the framework from SSH (see the "killall -CONT ..." command in the script). You could have done a reboot command from SSH. You could have restarted by holding the power button for 20 seconds.

The backup copy you installed was probably identical to what was already there (unless you installed something that changed it since the backup). Reinstalling it did not do any harm, and at least forced you to restart your kindle to restart the framework (cvm and Xorg).

SUGGESTION: If you want to play with this script on a touch, you can change the defined key codes to the "keys" that the touch supports. I suggest commenting out the "killall" lines first until you have a good way to exit. The touch generates "keypress" codes for screen touches (one and two fingers) and for orientation (rotation) events. You can find the touch keycodes from SSH with:

while:;do waitforkey;done

Of course, this script will be a LOT more useful when it has onscreen keyboard support.

UPDATE: To prevent these problems in the future, for any script that pauses the framework I will add a "trap" command to resume the framework on script termination, and I will add "exit" key detection for all kindle models. For the touch, that could be "put two fingers on the screen and press Home button" (i.e. "3-finger salute", like ctrl-alt-del). Although that makes the scripts larger, it should eliminate any chance of confusion. I have tested working script code that does these things now, and it works quite well.



Last edited by geekmaster; 04-10-2012 at 03:03 AM.
geekmaster is offline   Reply With Quote