View Single Post
Old 10-23-2012, 04:46 PM   #802
ixtab
(offline)
ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.
 
ixtab's Avatar
 
Posts: 2,903
Karma: 6677485
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
Quote:
Originally Posted by geekmaster View Post
@kaznelson: I added your success report to the "success reports" list. Using a custom runme.sh script is the OLD way of debricking, before we started recommending simple debricking by simply flashing uncorrupted firmware images.

It is great to have the "old debricking method" working here, but I think we still need to find out how to get USB Downloader mode working. Or at least, we need a way to make using runme.sh more noob-friendly. Thanks guys!
Well... yeah, runme.sh was actually the first method discovered, but it required/requires at least a half-way working system to function.

The USB downloader method is much more powerful (and preferrable, of course), but at this time we simply don't know how to make the PW hardware enter that mode. If anybody figures out a hardware "key combination" that makes the PW show up as 15A2:0052 (or even as another unsupported device), that'll be a major breakthrough for PW debricking.
ixtab is offline   Reply With Quote