[Q] Totally bricked kindle after 1st attempt at adding TWRP. No power on at all.

Search This thread

Fly_Trap

New member
Nov 12, 2009
1
0
I was following the steps on the lilputing dot com website (I cant provide links yet) to install TWRP so I could then install Cynogenmod.

These are the exact commands I entered, I got a "No space left on device" error at one point, something I noticed after I bricked the device. I'm sure this is the cause of the problem:


Code:
C:\u-boot-firefirefire-1.2>adb push u-boot.bin /sdcard/
[I][COLOR="DimGray"]2251 KB/s (216164 bytes in 0.093s)[/COLOR][/I]

C:\u-boot-firefirefire-1.2>adb push openrecovery-twrp-2.2.0-blaze.img /sdcard/
[I][COLOR="DimGray"]3962 KB/s (5578752 bytes in 1.375s)[/COLOR][/I]

C:\u-boot-firefirefire-1.2>adb shell
shell@android:/ $ su
su
shell@android:/ # dd if=/sdcard/openrecovery-twrp-2.2.0-blaze.img of=/dev/block/mmcblk0p5 
[COLOR="DimGray"][I]p-2.2.0-blaze.img of=/dev/block/mmcblk0p5                                     
[B]/dev/block/mmcblk0p5: write error: No space left on device[/B]
129+0 records in
128+0 records out
65536 bytes transferred in 0.011 secs (5957818 bytes/sec)[/I][/COLOR]

shell@android:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
[COLOR="DimGray"][I]dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
422+1 records in
422+1 records out
216164 bytes transferred in 0.061 secs (3543672 bytes/sec)[/I][/COLOR]
shell@android:/ # exit

C:\u-boot-firefirefire-1.2>adb reboot

After the reboot statement the device shut down but never came back.

I fear I have killed the Kindle (my sons Kindle :(). It is not recognised at all via usb into the computer. There is no power light when I put on charge. Have tried holding down power button for over a minute but still nothing. Would I be right in thinking this is totally unrecoverable?
 
A

androvista

Guest
I was following the steps on the lilputing dot com website (I cant provide links yet) to install TWRP so I could then install Cynogenmod.

These are the exact commands I entered, I got a "No space left on device" error at one point, something I noticed after I bricked the device. I'm sure this is the cause of the problem:


Code:
C:\u-boot-firefirefire-1.2>adb push u-boot.bin /sdcard/
[I][COLOR="DimGray"]2251 KB/s (216164 bytes in 0.093s)[/COLOR][/I]

C:\u-boot-firefirefire-1.2>adb push openrecovery-twrp-2.2.0-blaze.img /sdcard/
[I][COLOR="DimGray"]3962 KB/s (5578752 bytes in 1.375s)[/COLOR][/I]

C:\u-boot-firefirefire-1.2>adb shell
shell@android:/ $ su
su
shell@android:/ # dd if=/sdcard/openrecovery-twrp-2.2.0-blaze.img of=/dev/block/mmcblk0p5 
[COLOR="DimGray"][I]p-2.2.0-blaze.img of=/dev/block/mmcblk0p5                                     
[B]/dev/block/mmcblk0p5: write error: No space left on device[/B]
129+0 records in
128+0 records out
65536 bytes transferred in 0.011 secs (5957818 bytes/sec)[/I][/COLOR]

shell@android:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
[COLOR="DimGray"][I]dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
422+1 records in
422+1 records out
216164 bytes transferred in 0.061 secs (3543672 bytes/sec)[/I][/COLOR]
shell@android:/ # exit

C:\u-boot-firefirefire-1.2>adb reboot

After the reboot statement the device shut down but never came back.

I fear I have killed the Kindle (my sons Kindle :(). It is not recognised at all via usb into the computer. There is no power light when I put on charge. Have tried holding down power button for over a minute but still nothing. Would I be right in thinking this is totally unrecoverable?
Cause of the problem is that the above method does not work for the latest software version 6.3.2
 

ferrouskid

Senior Member
Mar 12, 2014
105
26
I was following the steps on the lilputing dot com website (I cant provide links yet) to install TWRP so I could then install Cynogenmod.

These are the exact commands I entered, I got a "No space left on device" error at one point, something I noticed after I bricked the device. I'm sure this is the cause of the problem:


Code:
C:\u-boot-firefirefire-1.2>adb push u-boot.bin /sdcard/
[I][COLOR="DimGray"]2251 KB/s (216164 bytes in 0.093s)[/COLOR][/I]

C:\u-boot-firefirefire-1.2>adb push openrecovery-twrp-2.2.0-blaze.img /sdcard/
[I][COLOR="DimGray"]3962 KB/s (5578752 bytes in 1.375s)[/COLOR][/I]

C:\u-boot-firefirefire-1.2>adb shell
shell@android:/ $ su
su
shell@android:/ # dd if=/sdcard/openrecovery-twrp-2.2.0-blaze.img of=/dev/block/mmcblk0p5 
[COLOR="DimGray"][I]p-2.2.0-blaze.img of=/dev/block/mmcblk0p5                                     
[B]/dev/block/mmcblk0p5: write error: No space left on device[/B]
129+0 records in
128+0 records out
65536 bytes transferred in 0.011 secs (5957818 bytes/sec)[/I][/COLOR]

shell@android:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
[COLOR="DimGray"][I]dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
422+1 records in
422+1 records out
216164 bytes transferred in 0.061 secs (3543672 bytes/sec)[/I][/COLOR]
shell@android:/ # exit

C:\u-boot-firefirefire-1.2>adb reboot

After the reboot statement the device shut down but never came back.

I fear I have killed the Kindle (my sons Kindle :(). It is not recognised at all via usb into the computer. There is no power light when I put on charge. Have tried holding down power button for over a minute but still nothing. Would I be right in thinking this is totally unrecoverable?



Hello
You can try doing the following
Install Minimal Fastboot and ADB, you can find a thread here on xda.
Type in when connected to kindle from pc, abd devices.
If you see any long serial number type in adb reboot recovery
Then adb reboot bootloader, either way the kindle should go into recovery after step one, and there you could get factory reset. It worked for me. Just check out the link, thanks to SnegovikRZN http://xdaforums.com/showthread.php?t=2530623