Thread: K5 JBPatch
View Single Post
Old 04-30-2012, 02:30 PM   #32
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: 6677559
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
Ok, so I just went suicidal and modified the file in the wrong way. ("jbpatcher.jar" instead of "jbpatch.jar").

And yes, my device is now bricked.

Update:
And here is how I unbricked it:
For a short amount of time (10 secs or so), the Kindle still shows up as a USB device, so I issued "touch /media/Kindle/ENABLE_DIAGS" in that timeframe. After two more reboots, I ended up in (SSH-enabled) diags. I ssh'ed in, and:
Code:
mount /dev/mmcblk0p1 /mnt/mmc/
vi /mnt/mmc/opt/amazon/ebook/bin/init.xargs
rm /var/local/upstart/lab126_gui.restarts
umount /mnt/mmc
idme -d --bootmode main
rm /mnt/us/ENABLE_DIAGS
sync; reboot
And all is good again. I'll update the first post with a big fat warning concerning the init.xargs editing

Last edited by ixtab; 04-30-2012 at 05:01 PM. Reason: Updated code to be more "standards-compliant"
ixtab is offline   Reply With Quote