View Single Post
Old 03-20-2013, 08:02 PM   #200
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,586
Karma: 6299993
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
erk.. that sounds a little bit like the one I had that I had to send back.

Does k3flasher (used directly) report anything more sensible? like for example can you get it to run:

me@dev /usr/local/src/k3flasher $ sudo ./k3flasher mx35to2_mmc.bin info

(dont post the output obviously)

in essence KUBRICK is designed to obfuscate such details from you. a k3flasher run directly gives you a few more options as the output is more verbose.

Hope that helps.
twobob is offline   Reply With Quote