MobileRead Forums - View Single Post

gk31 · 08-15-2012, 08:44 AM

My KT was updated to the latest 5.1.2 fw, running jbpatch 2.2.1, kindlet, and jailbreak 1.2. The screen would freeze and stay stuck on screensaver, or even during regular use. I got it out by rebooting most of the time, or connecting to usb and disconnecting, but after a few times it just BRICKED.
The last time my KT worked was after a fastboot flash of kernel and main images, whereupon the screensaver just froze in place. After entering and exiting diagnostic succesfully the screen froze again, and wouldn't make it past the tree screen. I'm now at attempt to debrick #5 - the KT is stuck on a diagnostic screen after trying to flash the main partition - it just won't reboot.
I'm using the n00b's guide to debricking v3 (from here). I followed the instructions to the T.
The last attempt was with 5.1.0 images: kernel 5.1.0, mmcblk0p1 5.1.0, diags mmcblk0p2 5.1.0 (here).
I got the KT in diagnostic mode using fastboot (now after 5 attempts and counting - i think something may be corrupted).
Typed: fastboot flash diags mmcblk0p2_ssh.img then
fastboot flash kernel kernel-5.1.0.img then
fastboot setvar bootmode diags
fastboot reboot

The device entered Diagnostic mode succesfully. Entered usb drive mode, copied mmcblk0p1 5.1.0 to it.
Got it to be Linux USB Ethernet/RNDIS Gadget, connected via putty no problems.
Typed: dd if=/mnt/us/mmcblk0p1.img of=/dev/mmcblk0p1 bs=4K after a while it finished no problems. Then: dd if=/dev/zero of=/dev/mmcblk0p3 bs=4K count=1K told me something like no room to write or something...not sure exactly.
Typed: rm /mnt/us/ENABLE_DIAGS gave me this error:
rm: can’t remove ‘/mnt/us/ENABLE_DIAGS’: No such file or directory.
Then typed idme -d --bootmode and then main
reboot. No respone from KT - still frozen. Help anyone?
I seem to be missing a crucial step somehow. If so, I lack the diags_kernel of 5.1 if someone could provide me with the link.
Also I wanted to try and flash to 5.0.0 but I am unable to procure the 5.0.0 mmcblk0p1 img, because github is down. If someone can provide that image, I will try with 5.0.0 and provide feedback.
Thanks all.
I first posted in the jbpatch thread saying the patch was crashing my KT, but even after I uninstalled it, it crashed and Bricked. Here is the link to my original post, and i would like to apologize if i insinuated that the jbpatch crashed my device. Most likely it didn't.

08-15-2012, 08:44 AM	#1
gk31 Junior Member Posts: 6 Karma: 10 Join Date: Jan 2011 Device: iPhone / iPad/ Kindle	Bricked In My KT was updated to the latest 5.1.2 fw, running jbpatch 2.2.1, kindlet, and jailbreak 1.2. The screen would freeze and stay stuck on screensaver, or even during regular use. I got it out by rebooting most of the time, or connecting to usb and disconnecting, but after a few times it just BRICKED. The last time my KT worked was after a fastboot flash of kernel and main images, whereupon the screensaver just froze in place. After entering and exiting diagnostic succesfully the screen froze again, and wouldn't make it past the tree screen. I'm now at attempt to debrick #5 - the KT is stuck on a diagnostic screen after trying to flash the main partition - it just won't reboot. I'm using the n00b's guide to debricking v3 (from here). I followed the instructions to the T. The last attempt was with 5.1.0 images: kernel 5.1.0, mmcblk0p1 5.1.0, diags mmcblk0p2 5.1.0 (here). I got the KT in diagnostic mode using fastboot (now after 5 attempts and counting - i think something may be corrupted). Typed: fastboot flash diags mmcblk0p2_ssh.img then fastboot flash kernel kernel-5.1.0.img then fastboot setvar bootmode diags fastboot reboot The device entered Diagnostic mode succesfully. Entered usb drive mode, copied mmcblk0p1 5.1.0 to it. Got it to be Linux USB Ethernet/RNDIS Gadget, connected via putty no problems. Typed: dd if=/mnt/us/mmcblk0p1.img of=/dev/mmcblk0p1 bs=4K after a while it finished no problems. Then: dd if=/dev/zero of=/dev/mmcblk0p3 bs=4K count=1K told me something like no room to write or something...not sure exactly. Typed: rm /mnt/us/ENABLE_DIAGS gave me this error: rm: can’t remove ‘/mnt/us/ENABLE_DIAGS’: No such file or directory. Then typed idme -d --bootmode and then main reboot. No respone from KT - still frozen. Help anyone? I seem to be missing a crucial step somehow. If so, I lack the diags_kernel of 5.1 if someone could provide me with the link. Also I wanted to try and flash to 5.0.0 but I am unable to procure the 5.0.0 mmcblk0p1 img, because github is down. If someone can provide that image, I will try with 5.0.0 and provide feedback. Thanks all. I first posted in the jbpatch thread saying the patch was crashing my KT, but even after I uninstalled it, it crashed and Bricked. Here is the link to my original post, and i would like to apologize if i insinuated that the jbpatch crashed my device. Most likely it didn't. Last edited by gk31; 08-15-2012 at 08:48 AM.