Thread: K4NT severely bricked
View Single Post
Old 04-27-2013, 12:44 PM   #1
akula169
Junior Member
akula169 knows the difference between 'who' and 'whom'akula169 knows the difference between 'who' and 'whom'akula169 knows the difference between 'who' and 'whom'akula169 knows the difference between 'who' and 'whom'akula169 knows the difference between 'who' and 'whom'akula169 knows the difference between 'who' and 'whom'akula169 knows the difference between 'who' and 'whom'akula169 knows the difference between 'who' and 'whom'akula169 knows the difference between 'who' and 'whom'akula169 knows the difference between 'who' and 'whom'akula169 knows the difference between 'who' and 'whom'
 
Posts: 2
Karma: 10000
Join Date: Apr 2013
Device: K4NT
K4NT severely bricked [FIXED]
First off, thanks to all for the wonderful resources contained within this forum. It has been most helpful in my Kindle hacking efforts. Yet, in attempting to get SSH going on my Black K4NT (4.1.1), I'm at an impasse.

I was able to get past step one of the Kubrick process (I'm assuming it entered Fastboot mode), but it never was recognized by the computer after that.

The "hold power until LED turns off" has never worked for me. It is always remains amber when USB is plugged in.

I have also charged it on a wall charger overnight. That doesn't seem to have made a difference.

I have read that extreme cases require a "manual debricking", but I'm not sure how I can proceed if the USB device is never seen by the OS (How do I know? I've checked dmesg and /var/log/messages on a linux box)
Last edited by akula169; 04-27-2013 at 01:46 PM.
akula169 is offline   Reply With Quote