Originally Posted by forest1971

I would re-flash bootloader using fastboot.

then try

fastboot oem format one more time and run parted again.

Hi,
please send to me your bootloader use.
If you can, please help me detail commands need to follow step by step how.
Thanks.

Originally Posted by chamnv

Hi,
please send to me your bootloader use.
If you can, please help me detail commands need to follow step by step how.
Thanks.

1, download hashcode's flash.zip bootloader from the development section
2. If you can get into TWRP then flash zip from there.

if you cannot get into twrp then: extract u-boot.bin file from zip file and use fastboot to flash it:
code:
fastboot flash bootloader u-boot.bin

3. Then download and flash TWRP again using fastboot or KFU. I like to use KFU to install TWRP but it can be install using fastboot:

The code to flash twrp using fastboot is (rename TWRP file as recovery.img):

fastboot flash recovery recovery.img

Also: before flash using fastboot it is better to make sure it is properly connect by issue:
code:
fastboot getvar product

If it return some number then it mean the device is connected properly.

anyone know why i can get adb shell when booted into cwmr, but not on twrp splash screen? i still have adb on splash screen.
parted is still hanging on print.

because shell is only working in cwmr i don't get idme from twrp (because no shell) or cwmr (i've also tried to push idme in cwmr) but still no joy.

does anyone know what the difference is between twrp shell & cwmr shell?

Originally Posted by lovejoy777

anyone know why i can get adb shell when booted into cwmr, but not on twrp splash screen? i still have adb on splash screen.
parted is still hanging on print.

because shell is only working in cwmr i don't get idme from twrp (because no shell) or cwmr (i've also tried to push idme in cwmr) but still no joy.

does anyone know what the difference is between twrp shell & cwmr shell?

Hashcode has the idme binary and lib files in the ics device tree, I'm actually pulling it into the gingerbread tree and going to try to rebuild the old gingerbread recovery with idme included (this obviously won't flash cm9) it should allow you to run your idme commands hopefully...

Originally Posted by james.shumaker

With a little over 24 hours of operation since its resurrection, my KF has presented two interesting anomalies that never before existed: 1) KF freezes which forces me to do a hard reset of the device - not sure if this is related to the nearly 1GB of (corrupt?) drive space requiring me to create partitions around the bad blocks, the most recent kernel, elements within the ROM, or a combination of each and 2) sluggish performance.

I'm wondering if it would be worth my while to try applying the Samsung files Hash posted, or if I should leave well-enough alone.

Samsung files???? If you mean his recovery - it's hopefully the solution to preventing eMMC damage from happening in the first place to anyone else. Currently, once it has happened, nothing short of replacing the flash chip or the whole motherboard will fix it. While a way DOES exist for resurrecting these chips, it requires "supah-secret-Samsung-info" that we don't have.

(This all assumes that the failure mode here is the same as Samsung Superbrick - is there anyone that had a failure with a flash chip other than M8G2FA?)

As to your first problem - sounds like you still have some bad areas that you haven't partitioned around.

what should i do please help

i was factory resetting my kindle fire with hash's cwm.but it was stucked at formatting/data for a long time..then i powered off the kindle by pressing power button for 20 seconds.then i turned on but it was not turning on.then i tried firekit by pokey..but always my kindle is hanging on yellow triangle and command prompt is showing waiting for device..
i have talked to pokey and he said that your mmc or ram is bad..
but this problem is created by cwm..
i think that my emmc is corrupted thats why firekit can't write twrp or fff..

i foundusing firekit i had to hold the pin shorted out all the way through install.

my emmc chip is bricked but i can still install fff & recoveries. if you need any one to run through the fk process then pm me:)

Sent from my Galaxy Nexus using xda premium

Originally Posted by Adeel1234

what should i do please help

i was factory resetting my kindle fire with hash's cwm.but it was stucked at formatting/data for a long time..then i powered off the kindle by pressing power button for 20 seconds.then i turned on but it was not turning on.then i tried firekit by pokey..but always my kindle is hanging on yellow triangle and command prompt is showing waiting for device..
i have talked to pokey and he said that your mmc or ram is bad..
but this problem is created by cwm..
i think that my emmc is corrupted thats why firekit can't write twrp or fff..

If Firekit does not help then it looks like not much can be done.

Still, I would try to use KF Utility to re-install window driver and then try to restart KF to fastboot mode and try to install u-boot.bin using fastboot. Not sure if it can be of any help but just post anyway.

Originally Posted by lovejoy777

i foundusing firekit i had to hold the pin shorted out all the way through install.

my emmc chip is bricked but i can still install fff & recoveries. if you need any one to run through the fk process then pm me:)

Sent from my Galaxy Nexus using xda premium

after i powered down my kindle by pressing power button for 20 seconds..


and connecting it to pc using data cable..

omap 4430 driver pop ups always..

i think my kindle is already in usb boot mode.

but firekit and rekindle is always showing as waiting for device even my kindle is turning on

given commands and stucking on yellow triangle
should i try it with shortening cpu or not please help i will be very thankful to u..

my pc always recognizes my kindle as omap 4430 device..

i didnt short the cpu yet..

i am using live usb ubuntu.

Lovejoy may have helped explained but incase, I come across this useful post sharing his experience about usbboot and fire kit that maybe useful for your case.

http://forum.xda-developers.com/show....php?t=1636883