Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,777,893 Members 49,557 Now Online
XDA Developers Android and Mobile Development Forum

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

Tip us?
 
Fly_Trap
Old
#1  
Junior Member - OP
Thanks Meter 0
Posts: 1
Join Date: Nov 2009
Unhappy [Q] Totally bricked kindle after 1st attempt at adding TWRP. No power on at all.

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/
2251 KB/s (216164 bytes in 0.093s)

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

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 
p-2.2.0-blaze.img of=/dev/block/mmcblk0p5                                     
/dev/block/mmcblk0p5: write error: No space left on device
129+0 records in
128+0 records out
65536 bytes transferred in 0.011 secs (5957818 bytes/sec)

shell@android:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
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)
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?
 
jma9454
Old
#2  
jma9454's Avatar
Senior Member
Thanks Meter 96
Posts: 587
Join Date: Apr 2012
Location: Seattle
If there is to be a solution to your problem, it will get figured out here:
http://forum.xda-developers.com/show....php?t=2622218

Sent from my Nexus 7 using Tapatalk
I am just a guy that is trying to learn a little coding and all. Don't go crying to your mommy that something I said was wrong.
Current: Nexus 7 running stock 4.4 (CM11 soon)
Retired: Kindle Fire running Jellybean CM10.1 / Android 4.2.2
 
androvista
Old
#3  
androvista's Avatar
Senior Member
Thanks Meter 327
Posts: 709
Join Date: Aug 2013
Location: Mumbai
Quote:
Originally Posted by Fly_Trap View Post
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/
2251 KB/s (216164 bytes in 0.093s)

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

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 
p-2.2.0-blaze.img of=/dev/block/mmcblk0p5                                     
/dev/block/mmcblk0p5: write error: No space left on device
129+0 records in
128+0 records out
65536 bytes transferred in 0.011 secs (5957818 bytes/sec)

shell@android:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
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)
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


Hey, I'm androvista, head of the InFriction ROM team.
InFriction ROM team head - androvista is AwesomePress the Thanks button To Support my Hard Work
 
jma9454
Old
#4  
jma9454's Avatar
Senior Member
Thanks Meter 96
Posts: 587
Join Date: Apr 2012
Location: Seattle
Quote:
Originally Posted by androvista View Post
Cause of the problem is that the above method does not work for the latest software version 6.3.2
So, @androvista, is there a solution?

Sent from my Nexus 7 using Tapatalk
I am just a guy that is trying to learn a little coding and all. Don't go crying to your mommy that something I said was wrong.
Current: Nexus 7 running stock 4.4 (CM11 soon)
Retired: Kindle Fire running Jellybean CM10.1 / Android 4.2.2
 
dlow8
Old
#5  
Junior Member
Thanks Meter 0
Posts: 2
Join Date: May 2013
Quote:
Originally Posted by jma9454 View Post
So, @androvista, is there a solution?

Sent from my Nexus 7 using Tapatalk
did you get it figured out? i have same prob
 
ferrouskid
Old
#6  
Member
Thanks Meter 25
Posts: 85
Join Date: Mar 2014
Quote:
Originally Posted by Fly_Trap View Post
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/
2251 KB/s (216164 bytes in 0.093s)

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

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 
p-2.2.0-blaze.img of=/dev/block/mmcblk0p5                                     
/dev/block/mmcblk0p5: write error: No space left on device
129+0 records in
128+0 records out
65536 bytes transferred in 0.011 secs (5957818 bytes/sec)

shell@android:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
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)
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://forum.xda-developers.com/show....php?t=2530623
Tags
kindle bricked twrp
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Software Build Automation with Jenkins – XDA Developer TV

Many members of the XDA community come to learn and begin in the exciting … more

Add Bits and Pieces of Honami to Your Current ROM

In the last few months, we’ve talked about quite a few Sony Honami-related projects. … more

Always Enter the Correct Password with HideNoPasswords

If you’ve ever entered apassword on your mobile device, you’ve surely … more

Revert to Stock Recovery Effortless with Simple Recovery Switcher

Android updates released as OTA packages are very easy to apply,but they … more