yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] vbdss:
Glad to see that someone else is getting progress too.

forest1971 you have been very helpful.

For the guys doing the repartition, if the command hangs or dont appear anything, reboot, go to recovery again, run parted and try to change start and end of partition

Right now my partition table is like this

[cdoe](parted) print

print

print

Model: MMC M8G2FA (sd/mmc)

Disk /dev/block/mmcblk0: 7734MB

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Number Start End Size File system Name Flags

1 131kB 262kB 131kB xloader

2 262kB 524kB 262kB bootloader

3 524kB 11.0MB 10.5MB dkernel

4 11.0MB 212MB 201MB ext4 dfs

5 212MB 229MB 16.8MB recovery

6 229MB 296MB 67.1MB ext4 backup

7 296MB 307MB 10.5MB boot

8 307MB 312MB 5243kB ext4 splash

9 312MB 849MB 537MB ext4 system

10 2150MB 3000MB 850MB ext4 userdata

11 3000MB 3256MB 256MB ext4 cache

12 3256MB 7690MB 4434MB fat32 media msftres[/code]
[Kindle Fire Android Development] bowen873:
You guys have all been great. I would have been lost without your help. I think I may have a bigger bad sector than vbdss. As he asked earlier, I wish there was a way to tell what was bad. I removed 10, 11, and 12. I've been trying different start and end combinations of mkpartfs primary ext2 for 10 without any luck. The last one I tried was how vbdss has his setup (2150-3000) and it's hanging at 32%. I know that I can always redo the partitions, but I'm afraid I'm going to lose a lot of space by the time I'm done.
[Kindle Fire Android Development] lovejoy777:
ok ive got a read error is there a way to sort this.

steve@lovejoyub:~$ adb shell

~ # cd /sys/bus/mmc/devices/mmc0:0001

/sys/devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001 # cat cid

1501004d384732464111f00833217e17

/sys/devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001 # cat csd

d02701320f5903fff6dbffef8a404067

/sys/devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001 # cat block/mmcblk0

cat: read error: Is a directory

/sys/devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001 #
[Kindle Fire Android Development] kostos:
i have noticed that when i erase cache (alone or with other partitions) then reboot in device manager continiously connects and at once disconnects an unknown device OMAP4430 and kindle doesn't boot

when i erase media and userdata (without cache) then reboot kindle boots and hang again in twrp logo (oem format doesn't influence on the result)

(parted) print also hangs rm 9, 10, 11 hangs too

may be i have wrong boot partition? should it be flashed over fastboot?

PLS give me someone link for cwrecovery_5.5.0.4_05-12.img for testing with it not twrp
[Kindle Fire Android Development] bowen873:
Ok, I've followed the instructions forest provided but p10 is still showing as ext2, not ext4.

Number Start End Size File system Name

1 131kB 262kB 131kB xloader

2 262kB 524kB 262kB bootloade

3 524kB 11.0MB 10.5MB dkernel

4 11.0MB 212MB 201MB ext4 dfs

5 212MB 229MB 16.8MB recovery

6 229MB 296MB 67.1MB ext4 backup

7 296MB 307MB 10.5MB boot

8 307MB 312MB 5243kB ext4 splash

9 312MB 849MB 537MB ext4 system

10 849MB 1049MB 200MB ext2 userdata

I ran these commands, but had to restart CMD after each one to do the next bc it wasn't giving me the prompt:

~ # tune2fs -j /dev/block/mmcblk0p10

~ # e2fsck -fDp /dev/block/mmcblk0p10

~ # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p10

~ # e2fsck -fDp /dev/block/mmcblk0p10

If anyone is willing to help me out and take a look I could setup a GoToMeeting.
[Kindle Fire Android Development] lovejoy777:
i've lost adb shell now.

think i have full lockup of chip.

adb devices returns the device but adb shell just hangs?

---------- Post added at 10:54 PM ---------- Previous post was at 10:18 PM ----------

steve@lovejoyub:~$ adb devices

List of devices attached

4FC6000600000001	recovery

steve@lovejoyub:~$ adb shell

error: protocol fault (no status)

steve@lovejoyub:~$
[Kindle Fire Android Development] lovejoy777:
i've tried every thing (ordered a new one) 2 weeks though:-(

steve@lovejoyub:~$ fastboot oem format

... OKAY

steve@lovejoyub:~$ bull****.

bull****.: command not found

steve@lovejoyub:~$ fastboot please make my f%$%ing kindle work again

usage: fastboot [ <option> ] <command>

commands:

i don't understand why that last command didn't work?

thankyou all so much. I have learn't so much from you guy's.

I will keep reading the threads and when my new one arrives "i will be back" LoL

Thanks again.

Steve:)
[Kindle Fire Android Development] james.shumaker:
Final Status

Thanks for the help forest1971! Took a while to work around the bad sectors, but here's the final result (Hash's CM9 build is up and running) and yes, I lost a crap load of space:

OLD Partition Table

Model: MMC M8G2FA (sd/mmc)

Disk /dev/block/mmcblk0: 7734MB

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Number Start End Size File system Name Flags

1 131kB 262kB 131kB xloader

2 262kB 524kB 262kB bootloader

3 524kB 11.0MB 10.5MB dkernel

4 11.0MB 212MB 201MB ext4 dfs

5 212MB 229MB 16.8MB recovery

6 229MB 296MB 67.1MB ext4 backup

7 296MB 307MB 10.5MB boot

8 307MB 312MB 5243kB ext4 splash

9 312MB 849MB 537MB system

10 849MB 2041MB 1192MB userdata

11 2041MB 2309MB 268MB cache

12 2309MB 7690MB 5380MB ext4 media

NEW Partition table

Model: MMC M8G2FA (sd/mmc)

Disk /dev/block/mmcblk0: 7734MB

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Number Start End Size File system Name Flags

1 131kB 262kB 131kB xloader

2 262kB 524kB 262kB bootloader

3 524kB 11.0MB 10.5MB dkernel

4 11.0MB 212MB 201MB ext4 dfs

5 212MB 229MB 16.8MB recovery

6 229MB 296MB 67.1MB ext4 backup

7 296MB 307MB 10.5MB boot

8 307MB 312MB 5243kB ext4 splash

9 312MB 849MB 537MB ext4 system

10 849MB 1200MB 351MB ext4 userdata

11 2400MB 2670MB 270MB ext4 cache

12 2670MB 7690MB 5020MB fat32 media msftres
[Kindle Fire Android Development] forest1971:
Thanks for the help forest1971! Took a while to work around the bad sectors, but here's the final result (Hash's CM9 build is up and running) and yes, I lost a crap load of space:

NEW Partition table

Model: MMC M8G2FA (sd/mmc)

Disk /dev/block/mmcblk0: 7734MB

Sector size (logical/physical): 512B/512B

Partition Table: gpt

Number Start End Size File system Name Flags

1 131kB 262kB 131kB xloader

2 262kB 524kB 262kB bootloader

3 524kB 11.0MB 10.5MB dkernel

4 11.0MB 212MB 201MB ext4 dfs

5 212MB 229MB 16.8MB recovery

6 229MB 296MB 67.1MB ext4 backup

7 296MB 307MB 10.5MB boot

8 307MB 312MB 5243kB ext4 splash

9 312MB 849MB 537MB ext4 system

10 849MB 1200MB 351MB ext4 userdata

11 2400MB 2670MB 270MB ext4 cache

12 2670MB 7690MB 5020MB fat32 media msftres[/QUOTE]

-----------

Looks good! I am very happy for you :)!

congratulation!

Ah, we should thank many many times to Eldarerathis who wrote the guide on re-partition for our KF. His guide has helped revised many phones (not only KF) that has faulty area in some partitions.
[Kindle Fire Android Development] lovejoy777:
if i buy a new motherboard would it come pre installed with the loader, part table etc. ie. do i just plug it in and root etc or is it blank? how does it work? is it worth it?

looking here.

http://www.powerbookmedic.com/Kindle-Fire-Mother-Board-p-21510.html
[Kindle Fire Android Development] forest1971:
My guess is it come pre-installed. Otherwise it should allow easy install with the tools from our expert in the forum. Hope you take it easy with your almost-gone KF. It has given you great skill on dealing with software and hardware issues, hasn't it?
[Kindle Fire Android Development] vbdss:
Probably on the last command, something like you should run e2fsck manual, just take out the -p

put like this e2fsck -fD /dev/block/mmcblk0p10 and follow the script
[Kindle Fire Android Development] bowen873:
I actually tried it that way too. Not sure what I'm missing, but I'll keep trying.
[Kindle Fire Android Development] Entropy512:
If it IS the same problem as Samsung users have been experiencing on Exynos devices recently (all of the evidence so far says it is...) - The eMMC chip completely locking up when you touch an affected part of the chip is another symptom of the problem.
[Kindle Fire Android Development] forest1971:
Perhaps posting some screenshot or log text of adb sessions may be useful for us to see if you missed somethings. cheers.
[Kindle Fire Android Development] bowen873:
I eventually got 10, 11, + 12 added and formatted correctly. I couldn't find a good block of more than 200 between 1000 and 6800. I was able to get the stock update flashed and I'm going to have to return it. It'll work, but with no storage space it's pretty much worthless. Thanks again to all of you for your help - much appreciated.
[Kindle Fire Android Development] forest1971:
Thanks for the update of partial success.

btw, any idea/suspicion of anything you have done that may have caused the problem with a large area of your emmc space? Just hope we can avoid that if find the reasons. cheers.
[Kindle Fire Android Development] bowen873:
Again, not being that technical I was just following the ideas all of you gave me. I realized later on that I think I did fastboot wipe userdata and cache before I started following this thread. And according to Entropy, that could have made things worse.
[Kindle Fire Android Development] fleurdelisxliv:
so i guess this is how i got myself a brick :(
[Kindle Fire Android Development] vbdss:
Sorry to hear that, but maybe you can restore the amazon os and try to return.

Maybe you should try other start and ends for your partitions, maybe this way, it will be completed.

Well, for me, fastboot erase didnt do anything, actually got better after fastboot erase...

Maybe yes, maybe not, you only know when you try.

------------------------

I am really trying to help you guys, but i dont remember everything ive done, i just used a lot of bootloader and recovery combinations, FFF 1.2, CWMR 5.0.2.1, TWRP 2.0.0....

And the commands that i found on my search about the problems.

But i cant remember anything really working before hashcode said to fastboot erase and then fastboot oem format, thats when thing started to work. Parted print returned me something, idme ? was working.

I am no master of android, adb and fastboot, i can only say to you try everything that is on this thread.

Everytime i tried something, ive put a answer here to try to document all things that i have done.

Sorry if i cant be more helpful.
[Kindle Fire Android Development] lovejoy777:
thank you (sorry out of thanks).
[Kindle Fire Android Development] pokey9000:
If what entropy512 suspects is the problem, this will affect everyone differently. I doubt that this procedure will work for everyone, though it's worth a try. The write levelization metadata gets corrupted at random when erasing, so everyone will have a different block or set of blocks that cause it to asplode.
[Kindle Fire Android Development] Hashcode:
Here is a rebuilt version of the 5.5.0.4 using a kernel that has CAP_ERASE disabled for emmc (which was the solution for the Samsung devices):

http://rombot.droidhive.com/ROMs/otter/kernel/cwrecovery_5.5.0.4_05-31.img (Image file)

http://rombot.droidhive.com/ROMs/otter/kernel/cwrecovery_5.5.0.4_05-31.zip (.zip file for flashing -- this won't work if you have a bad /cache partition)

These are to be considered dangerous until it's been proven (somehow) that they won't cause more damage.
[Kindle Fire Android Development] Entropy512:
Yup. On Samsungs - some people lost just /data, some lost /data and /system, some people had the damage "spill over" to their secondary bootloader leading to a fullblown hardbrick.

Those who just lost /data - Some lost nearly all of it, some just lost a little bit.
[Kindle Fire Android Development] lovejoy777:
which section would wipe out adb shell but leave adb working?
[Kindle Fire Android Development] james.shumaker:
Interesting Post-Resurrection Update: Two Problems

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.
[Kindle Fire Android Development] vbdss:
Well, for me, everything is working like it should. No performance degradation or anything like it
[Kindle Fire Android Development] chamnv:
Hi vbdss,

I've done fastboot erase commands as you guide. It reported success (only data, sdcard is fail). But when I boot from TWRP, it still hangs TWRP screen, boot from CWM is ok but the error as before. I tried the command # idme but it does not appear at all the information (no information about the machine, only the column headings). I execute the command # parted / dev/block/mmcblk0, then type the command (parthed) print it does not appear that anything, it just print the letters, in addition none at all. How can I do? Please guide me.
[Kindle Fire Android Development] vbdss:
Maybe now try the fastboot oem format

Try fastboot erase system, cache, data, userdata too
[Kindle Fire Android Development] chamnv:
hi,

I had try

fastboot erase system (ok)

fastboot erase cache (ok)

fastboot erase userdata (ok)

fastboot erase data ( fail)

fastboot erase sdcard ( fail)

fastboot erase media (ok)

fastboot oem format (ok)

fastboot reboot ( kf not reboot complete, i see when i enter, kf led power still light)
[Kindle Fire Android Development] forest1971:
Have you tried to run parted again yet?

Or do you mean KF would not turn on after fastboot erase?
[Kindle Fire Android Development] chamnv:
Hi,

I had try parted mmcblk0p0 and type print, but print not show nothing, it still print print.
[Kindle Fire Android Development] forest1971:
That could be a bad sign. But the code does not look right. it should be:

~ # parted /dev/block/mmcblk0
[Kindle Fire Android Development] chamnv:
Oh yes,

I type

~ # parted /dev/block/mmcblk0

it show

(parterd) print

print

It only show print print, nothing.
[Kindle Fire Android Development] forest1971:
I would re-flash bootloader using fastboot.

then try

fastboot oem format one more time and run parted again.
[Kindle Fire Android Development] kostos:
you should try to flash recovery posted on the previous page

in twrp parted print hangs at all
[Kindle Fire Android Development] vbdss:
Here i was using FFF 1.4a and TWRP 2.1.1
[Kindle Fire Android Development] :
Delete
[Kindle Fire Android Development] Sblood86:
Just click through and tell it you installed 3x
[Kindle Fire Android Development] BrooksBlood:
Just flashed this, fricken sweet! only question i have is when i chose anything in rom manager it prompts me that i first must download CWM Recovery through rom manager before continuing. Has any else experienced this?
[Kindle Fire Android Development] Hashcode:
I believe you select the cwm 3x(+) option and then it will let you flash using my version.

As soon as I fix the touchscreen driver to be fully ICS compatible, I'll work with Koush to get an official ClockworkMod built.
[Kindle Fire Android Development] BrooksBlood:
I assumed that was what you would do but didn't want to do something and have it screw me over :-P just used it for the first time. Absolutely flawless Hash! Bravo!!
[Kindle Fire Android Development] sasquatch080:
Thank you sir. Working flawless.
[Kindle Fire Android Development] teookie:
Looks great!

The reboot options don't appear to properly set the bootmode. I'm stuck in bootmode 5001 and can't get out because few weeks ago I reloaded the OS on my dev machine and lost all my fastboot files. :-( Anyone got a link? LOL I'm such a dork. :p
[Kindle Fire Android Development] pbailey212:
I haven't used rom manager for ever, but I believe if you go to munual flash override you can chose your own recovery

sent from my Nokia 5110
[Kindle Fire Android Development] smirkis:
hash, did u incorporate fbmode and rcmode and nbmode like twrp2.1.1 and the other cwmtouch did in the ramdisk?
[Kindle Fire Android Development] Hashcode:
No. Recovery shouldn't need to set any bootmodes. Neither should the roms. The only trigger for entering recover is the "postmode 1" idme setting.
[Kindle Fire Android Development] Hashcode:
If you can load FFF 1.4a, you can use the "reset bootmode" menu option to reset to bootmode 4000.
[Kindle Fire Android Development] swedeking:
Flashed zip works great. Thank you sir.
[Kindle Fire Android Development] Stage:
Can someone please tel me what I'm doing wrong? I flashed this as a zip in old CWM recovery. I'm running CM9 Hellfire. But it tells it can't install it and operation aborted.

It says "error in /sdcard/cwrecovery_5.5.0.4_-12.zip (status 7)

Any ideas?
[Kindle Fire Android Development] Evo_Shift:
Try redownloading it. I was using doomlords cwm and this one flashed fine.
[Kindle Fire Android Development] Stage:
Just tries redownloading it. Same as before.
[Kindle Fire Android Development] Evo_Shift:
I have tried doing two backups now and it keeps hanging on traces.txt during the data part of the backup process. I haven't been able to complete a backup yet. I left it 15 minutes the second time before rebooting.
[Kindle Fire Android Development] foxdog66:
O yeah this is sweet! Installed this recovery with twrp 2.1.1 then in ROM manager I did a manual flash overwrite and choose 3.x and enabled advanced mode that let me make a install query where I then chose the updated ROM followed by the updated kernel, allowed ROM manager superuser permissions and it preceded to reboot into clockwork and install each zip and reboot back to the OS.... Beautiful, simply beautiful :)
[Kindle Fire Android Development] TexasRules777:
Downloaded a rom..backup, flash via rom manager... simplicity. Brilliant work hash.
[Kindle Fire Android Development] pbailey212:
If you are using recovery to flash this Make sure you check md5. If you get a bad download/flash you will be left without a recovery.
[Kindle Fire Android Development] Stage:
Ok fixed it. Flashed the new fire fire fire and flashed Hellfires new CM9 rom and it worked great
[Kindle Fire Android Development] 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.
[Kindle Fire Android Development] forest1971:
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.
[Kindle Fire Android Development] 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?
[Kindle Fire Android Development] Sblood86:
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...
[Kindle Fire Android Development] Entropy512:
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.
[Kindle Fire Android Development] 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..
[Kindle Fire Android Development] 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:-)
[Kindle Fire Android Development] forest1971:
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.
[Kindle Fire Android Development] Adeel1234:
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.
[Kindle Fire Android Development] forest1971:
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://xdaforums.com/showthread.php?t=1636883
[Kindle Fire Android Development] lovejoy777:
all other partitions come back different?

does this tell me anything?

steve@lovejoyub:~$ adb shell

~ # mke2fs -T ext4 /dev/block/mmcblk0p12

mke2fs: lseek: Value too large for defined data type

~ #
[Kindle Fire Android Development] forest1971:
You mean have been able to get parted running now? that is a good sign if yes.

can you post the partition table using (parted) print?

Also, the above code should not be used for partition 12 because it is media partition and format is fat32.