Saturday 10 October 2015

Hard Bricked Kindle Fire HD 8.9 jem BC09



Hello,

I've hardbricked a Kindle Fire HD 8.9 jem BC09 which was running 8.5.1 before it became a paperweight.

I successfully rooted the device with Bin4rys method, at which point I followed cyanogenmod's directions on installing the bootloader(otter2 CM install instructions on their website)

I verified the MD5 checksum for the bootloader before proceeding.

Here's the results of my mishap:


Quote:









Volume in drive C is Windows7_OS

Volume Serial Number is 3A6D-6FAB

Directory of C:\Users\User\Downloads

10/10/2015 03:17 PM <DIR> .
10/10/2015 03:17 PM <DIR> ..
10/10/2015 02:29 PM <DIR> Old DLs
10/10/2015 03:17 PM 8,349,292 otter2-freedom-boot-10.4.6.img
10/10/2015 03:17 PM 8,349,292 otter2-twrp-2.6.3.1-recovery.img
10/10/2015 03:13 PM 232,908 otter2-u-boot-prod-10.2.4.bin
04/29/2007 06:12 AM 591,872 WinMD5.exe
10/10/2015 03:15 PM 268,376 winmd5free.zip
5 File(s) 17,791,740 bytes
3 Dir(s) 370,367,225,856 bytes free

C:\Users\User\Downloads>fastboot -i 0x1949 flash bootloader otter2-u-
boot-prod-10.2.4.bin
< waiting for any device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (227 KB)...
OKAY [ 0.020s]
writing 'bootloader'...
OKAY [ 0.040s]
finished. total time: 0.060s

C:\Users\User\Downloads>fastboot -i 0x1949 flash recovery otter2-twrp
-2.6.3.1-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8153 KB)...
OKAY [ 0.437s]
writing 'recovery'...
OKAY [ 0.562s]
finished. total time: 1.014s

C:\Users\User\Downloads>fastboot -i 0x1949 flash boot otter2-freedom-
boot-10.4.6.img
target reported max download size of 1006632960 bytes
sending 'boot' (8153 KB)...
OKAY [ 0.452s]
writing 'boot'...
OKAY [ 0.562s]
finished. total time: 1.014s

C:\Users\User\Downloads>fastboot -i 0x1949 oem recovery
...
OKAY [ 0.000s]
finished. total time: 0.000s

C:\Users\User\Downloads>fastboot -i 0x1949 getvar product
< waiting for any device >




At the point where I attempted to reboot into recovery, the device became completely bricked. No response to power on, etc.

As I've been browsing for the past hour it seems to me that this device is virtually unbrickable aside from sending it to Amazon. I have contacted "Chris" at prokennexusa@gmail.com and am awaiting his response. In the meantime, if anyone else has any ideas of how to proceed please let me know!

Regards,
siriu5



No comments:

Post a Comment