yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] lovejoy777:
ok just had the hang at waiting for omap44xx devices, this is how i got out of it.

pull battery terminal

perform usb_fix from firekit

when it says waiting for omap44xx device short pin and insert usb cable. if it doesn't work. (it normally starts 2nd stage bla bla bla),

normally ends with waiting for omap again(if no script at all runs try unplugging usb and re-shorting pins then reconnect usb), at this point

plug in battery, this should start the installs etc

Edit: I always keep pin shorted throughout the process.

notes: it is best to always start from scratch after each attempt ie. if its hanging anywhere, unplug kindle and close terminal, reopen terminal and start again.

I hope this helps

---------- Post added at 05:48 PM ---------- Previous post was at 05:45 PM ----------

no parted just hangs on print but i tried the scripts anyway. (i know it wont help just wanted to know why 12 returned different.

now i know:-)

Edit: if i run commands in parted (except print) I always get things returning in terminal. does this mean the commands are being performed?
[Kindle Fire Android Development] forest1971:
If you have been able to install bootloader then try to:

fastboot oem format

If works it will restore partition structure and in that case parted should be able to see it.
[Kindle Fire Android Development] lovejoy777:
I wish I was that lucky:-)

I've been trying everything for days lol.

whilst i still have bootloader and some sort of adb/fastboot i will keep trying.

if anyone wants to test any bootloaders or anything else a blocked emmc chip can do, let me know.
[Kindle Fire Android Development] james.shumaker:
In my case, the resurrection is starting to not look so good. Although initially the re-partioning around the bad blocks was working, it now appears that there is some spillover from the adjacent bad blocks as my KF is beginning to lock up more often and even a system wipe with a fresh install came after great pain and crossed fingers. I think I'm witnessing the slow demise of this KF ... that new Lenovo IdeaTab is starting to look sweeter and sweeter ...

Thanks again to all.
[Kindle Fire Android Development] lovejoy777:
steve@lovejoyub:~$ adb shell

~ # for F in /sys/block/mmcblk0/mmcblk0p*

> do

> echo $F

> cat $F/partition_name $F/start $F/size

> done

/sys/block/mmcblk0/mmcblk0p1

xloader

256

256

/sys/block/mmcblk0/mmcblk0p10

userdata

1657856

2328576

/sys/block/mmcblk0/mmcblk0p11

cache

3986432

524288

/sys/block/mmcblk0/mmcblk0p12

media

4510720

10508288

/sys/block/mmcblk0/mmcblk0p2

bootloader

512

512

/sys/block/mmcblk0/mmcblk0p3

dkernel

1024

20480

/sys/block/mmcblk0/mmcblk0p4

dfs

21504

393216

/sys/block/mmcblk0/mmcblk0p5

recovery

414720

32768

/sys/block/mmcblk0/mmcblk0p6

backup

447488

131072

/sys/block/mmcblk0/mmcblk0p7

boot

578560

20480

/sys/block/mmcblk0/mmcblk0p8

splash

599040

10240

/sys/block/mmcblk0/mmcblk0p9

system

609280

1048576

~ #
[Kindle Fire Android Development] jsantiago.antonio:
Tried everything on this thread i still seem unable to find a solution, bummer. Can i push SU files to adb? Could it be that's the reason i'm unable to work with the partitions? I get the feeling that i'm not rooted and i'm currently locked out and its blocking commands im running via some sort of permission set.
[Kindle Fire Android Development] lovejoy777:
I've had the same thought.

---------- Post added at 11:47 PM ---------- Previous post was at 11:41 PM ----------

for some reason im doubting its the sammy superbrick.

on all there posts about the brick it stats most seem to have a bad return on this command. but we seem ok?

dmesg | grep mmc0
[Kindle Fire Android Development] forest1971:
I am not sure about the status of your KF yet.

If it can boot and can get into TWRP then parted should work and it can help deal with faulty partition if there is. (please confirm if it can boot and get into TWRP).

Before bootloader and TWRP work parted is of no use.

cheers
[Kindle Fire Android Development] lovejoy777:
forest do yo know why i can get shell in cwmr but not when im on the twrp splash screen. it did work when all these fun & games started, but at some point i lost it.

i can reflash any recovery or bootloader. any version of cwmr loads complete but twrp sticks on splash screen.

because idme is not in cwmr and i have no shell in twrp i have to change recoveries between using adb shell & fastboot.
[Kindle Fire Android Development] forest1971:
Lovejoy: I haven't got any clear idea about this situation yet. Hope that someone can throw in some light. One of my thought is: could it be something to do with the size of the TWRP and that of CWM that could fit in the partly-damaged recovery partition (this sound naive isn't it). Anyway, I feel it is better to exchange some idea, to have better understanding of the problem and maybe solution, than not trying. Have you tried with both twrp 2.0.0 and 2.1.0 yet? I bet you did. cheers.
[Kindle Fire Android Development] lovejoy777:
thanks for reply

yes i keep trying different recoveries, the only one i can get adb shell now is doomlords original touch version (red ui). i wonder what that version has/does different?

edit: utterchaos-cwm5-touch-v01-final-1_recovery.img
[Kindle Fire Android Development] forest1971:
It's interesting to know. Thanks.

btw: with CWM can you mount sdcard/usb to PC?

And any effort to install bootloader.zip through CWM still no luck? or unable to push the file to sdcard?

cheers.
[Kindle Fire Android Development] lovejoy777:
no mounts just returns error

i can flash different bootloaders with fastboot

i can adb push roms etc to sdcard and they seem to take?
[Kindle Fire Android Development] chamnv:
Hi,

I do follow with you:

It show only, nothing.

I do it this command

KF hang print print, nothing show.

When i flash twrp but KF hang in TWRP splash screen. I flash CWM 5.0.27, but kf can not mount.

How i do? Please intro for me.
[Kindle Fire Android Development] forest1971:
Hi: it seemed you made a mistake with this one:

c:\adb>fastboot -i 0x1949 boot twrp.img

< waiting for device >

downloading 'boot.img'...

OKAY [ 2.670s]

booting...

OKAY [ -0.000s]

finished. total time: 2.670s

The twrp.img is recovery and should only be flash to recovery partition.

The boot partition is to be flashed with kernel (such as Hashcode's kernel 3.0 for ICS or Intersecraven kernel for GB). It can be a zip file (to be flash using twrp or cwm), or it can be the boot.img (to be flashed with fastboot.

Still that may not be a big problem since you have not flash the wrong thing to bootloader.

I guess it is better to flash the correct boot.img kernel to its place if possible.

One more thing it looks like the first time you run adb when device is in fastboot mode.

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

c:\adb>adb shell

* daemon not running. starting it now *

* daemon started successfully *

error: device not found

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

adb can only work when device is in TWRP (or CWM). it looks like you did it second time but it was not clear if you run it with TWRP flash screen or with CWM.

For the other part, haven't got a clue yet.
[Kindle Fire Android Development] lovejoy777:
i would guess its effected your media partition because that seems to be the onlyone that erases far to quickly.

mine is cache
[Kindle Fire Android Development] lovejoy777:
is there a way to run a rom etc off a usb/external sdcard, if the kindle was in usb boot mode.

just a random thought of a way to utilize my kindle
[Kindle Fire Android Development] chamnv:
Hi,

I've done as you directed, but it still is

file: boot.img: i get from stock rom 6.3.1.

file: recovery.img: it is twrp 2.1.1.img

file u-boot.bin: i get from fff-u-boot_v1.4a.zip file

At TWRP, KF still hang TWRP splash screen.

idme? nothing show

(parted) print => nothing shown, hang print print.
[Kindle Fire Android Development] lovejoy777:
just a quick one.

did everyone still with a brick do (1). a restore of backup or (2).a format of some sort to get in this emmc brick.

the sammy superbrick effects in two different ways (one activated by restore of backup the other by format/erase).

it seems the two effect two different partitions.

i did mine by a restore of backup. (it would be interesting to know if those that managed to reserect there kindles if they did a format).

edit: for people who struggle with waiting for omap device in firekit, try this.

i've found out that some versions of fff boot when you plug in usb cable (this normaly means the firekit will fail due to the kindle booting fff as soon as you apply the usb).

to sort this first use the option within firkit to install_fff_twrp, this will flash a version that doesn't boot fff when trying to do the short trick.

after you install fff & twrp through fk then power off (30 sec hold) and close terminal. start again with usb_fix and this time it should work:-)
[Kindle Fire Android Development] vbdss:
I remebered one thing, i tried to make that dd if=.... of=... to make the partitions be filled with "0" i think

maybe this can help?

just search the thread, it all started from page 5 or 6
[Kindle Fire Android Development] pokey9000:
The Fire should always go into USB boot mode if you short the pin and hold the power button for 30 seconds. The best way to do this imho is to leave the USB plugged in, run the firekit command, short the pin, and hold down the power button until firekit shows a connection.

It is possible to reprogram the PMIC to not reset when you hold the power button down, but that would be dumb, and I'm sure none of the newer FFFs would do that.
[Kindle Fire Android Development] forest1971:
In anther thought I suspect that in the case of lovejoy and chamnv there might be some partial damage to the recovery partition that prevent twrp from full installation and running. I am thinking that maybe copy a healthy recovery partition over the existing one, using dd command, could be usefull to get twrp to function? It may be worth a try?
[Kindle Fire Android Development] chamnv:
I see Nook Tablet. NT had dd command to create partion.

http://xdaforums.com/showthread.php?t=1570022

---------- Post added at 03:00 PM ---------- Previous post was at 02:45 PM ----------

When i try this command, my KF is show the same.
[Kindle Fire Android Development] Entropy512:
Please be specific - WHICH version of CWM were you using? The one that was in the OP of this thread but was later pulled, or the build from Hashcode's May 31 post?

No, many people suffering from Sammy Superbrick are still able to boot and get information from their MMC chip. Some hardbricked, some only lost /system, some only lost /data.
[Kindle Fire Android Development] lovejoy777:
thanks forest.

no joy though, i tried everything but still no parted or full twrp.

how do i dd a new recovery partition?

I still can only gain shell with doomlords version of cwmr (adb & fb both work on all recoveries?

:-)my new kindle just arrived:-)

will be rooting tonight:-) apart from cwmr what eles should i avoid? (don't want to brick this one on day 1. lol
[Kindle Fire Android Development] pbailey212:
Are you sure you want to root? You must have a forgiving wife. If i Mega bricked my kindle my wife would never left me root anything again. Then I would get the "this is why we can't have nice things" speech

sent from my Nokia 5110
[Kindle Fire Android Development] lovejoy777:
shhh she doesn't know its here yet and by the morning it will be to late:-)

(sorry for the out of topic post but the last week has been like living with part of my soul missing).lol.

thanks again to all who helped me, i will keep trying any new approaches .

Steve
[Kindle Fire Android Development] lovejoy777:
now i have a new kindle can i use it in anyway to help with my otherone?

sent from my new non bricked kindle:-)
[Kindle Fire Android Development] Hashcode:
That's a good question. I think there is some good stuff in this thread. But its kind of buried and hard to organize.
[Kindle Fire Android Development] chamnv:
If you can, please backup mmcblk0p* and mmcblk0 for me. I will try dd command to re-create mmc partition.

thank you.
[Kindle Fire Android Development] foxdog66:
I generally understand what it's going on with these experimental things we do and have kept using this recovery avoiding the things that cause damage. It's worked fine for installing zip's and whatnot and loved the convince of ROM manager's option to make a install query. Anyway, I installed something that added more quick settings toggles and made a backup strictly to have one to extract data from. listening to music while going to bed one night, using this sleep timer app that fades the music out after the set time, time ran out and I wasn't asleep quite yet so I tried restating the timer app and found that I couldn't get the thing out of a muted state so, half asleep, without thinking, loaded up ROM manager and tapped the restore button and woke up some 20 minutes later to find it stuck trying to restore the data partition. I hard reset the thing and that was the last time it ever turned on, this thing is fried haha. I'm rather surprised that even my special factory style cable does absolutely nothing. Picked up another one today bit haven't even opened it yet :rolleyes:
[Kindle Fire Android Development] forest1971:
Partition image

Hi:

Attached is the image of key partitions of a healthy KF. (1,2,3,5,7,8). In case it is useful for someone to restore their partitions.

I think the code to restore partition 1 to your KF is:

~ # dd if=/sdcard/p1.img of=/dev/block/mmcblk0p1

cheers.
[Kindle Fire Android Development] lovejoy777:
ok so i adb push file to sdcard? then issue the dd commands 1x1 in shell?
[Kindle Fire Android Development] forest1971:
Yes Lovejoy,

adb push the image file to root folder of sdcard. No idea if restore partition will help your KF, though.

cheers
[Kindle Fire Android Development] lovejoy777:
sorry to hear that.

cwmr restore is how i did mine, it just hung on data.

don't use that recovery for anything else when you get it booted again.

it is the wipe/formating that is killing the chip, even on a restore it wipes the partitions first.

all i can suggest if you have already tried holding power button for 30 seconds, is to use pokeys usb firekit trick to get it powered up again. this will install twrp &fff again. then try "fastboot oem format", this should restore your kindles partitions back to factory set.

the firekit should work to get you powered back on and then you need to assess the damage done to your partitions. from what we have learn,t, has long as you don't do any more erases/wipes with the cwmr it won't get any worse and may be fixable (maybe with some block damage).

try the firekit (and follow it to the t) no shortcuts, then post back here with any queries etc.

sent from my new non bricked kindle:-)

---------- Post added at 04:53 PM ---------- Previous post was at 04:25 PM ----------

steve@lovejoyub:~$ adb shell

~ # dd if=/sdcard/p1.img of=/dev/block/mmcblk0p1

dd: writing '/dev/block/mmcblk0p1': I/O error

1+0 records in

0+0 records out

0 bytes (0B) copied, 2.452240 seconds, 0B/s

~ # dd if=/sdcard/p2.img of=/dev/block/mmcblk0p2

dd: writing '/dev/block/mmcblk0p2': I/O error

1+0 records in

0+0 records out

0 bytes (0B) copied, 2.452301 seconds, 0B/s

~ # dd if=/sdcard/p3.img of=/dev/block/mmcblk0p3

dd: writing '/dev/block/mmcblk0p3': I/O error

1+0 records in

0+0 records out

0 bytes (0B) copied, 2.452759 seconds, 0B/s

~ #

am i doing this right as there is an I/O error

thanks again

Steve
[Kindle Fire Android Development] foxdog66:
The firekit trick requires taking it apart, correct? I've had some bad experiences taking some other electronics apart so I think I'll pass if that's the case. I'm writing this experience off as a lesson to not mess with things when I'm half asleep :rolleyes:
[Kindle Fire Android Development] forest1971:
[/COLOR]

steve@lovejoyub:~$ adb shell

~ # dd if=/sdcard/p1.img of=/dev/block/mmcblk0p1

dd: writing '/dev/block/mmcblk0p1': I/O error

1+0 records in

0+0 records out

0 bytes (0B) copied, 2.452240 seconds, 0B/s

~ # dd if=/sdcard/p2.img of=/dev/block/mmcblk0p2

dd: writing '/dev/block/mmcblk0p2': I/O error

1+0 records in

0+0 records out

0 bytes (0B) copied, 2.452301 seconds, 0B/s

~ # dd if=/sdcard/p3.img of=/dev/block/mmcblk0p3

dd: writing '/dev/block/mmcblk0p3': I/O error

1+0 records in

0+0 records out

0 bytes (0B) copied, 2.452759 seconds, 0B/s

~ #

am i doing this right as there is an I/O error

thanks again

Steve[/QUOTE]

Not sure what cause the I/O error. We need some expert advice at this stage.

When we do re-partition using parted if there is I/O error when creating partition it signal there is bad block in the area. In this case have no clue yet.

Maybe try with partition 3 and 8 to see if any luck.

cheers.
[Kindle Fire Android Development] lovejoy777:
ok something good happend i zeroed out the partitions first then pushed all p.img's (still with I/O error then, then "fastboot oem format" then fastboot flashed twrp 2.1.1 and i now have adb shell again in twrp. im going to try parted etc again.

for all the shell scripts i had to use doomlords touch version of cwmr (it was the only one i had shell)(strange)

Edit used shell a couple of scripts then it just hung. after closing terminal then reopening i have no shell again in twrp??
[Kindle Fire Android Development] kinfauns:
Although I don't have this specific issue with my Kindle Fire, I've been curious about the progress of all of your repair attempts, so I've been quietly following along.

I understand the logic of trying to map the partitions out around the potentially affected areas. Had the problem occurred on a mechanical hard drive, this procedure would be perfectly sound and I'm sure it would work. The big question mark for me is that the process is being attempted on a solid state storage device with wear leveling capabilities. I don't know the specifics on wear leveling algorithms, but the basic/generic concept (as I know it) is that any logical block can be re-mapped out to any physical block at any moment.

So, to all of you hardware gurus watching this thread...

It seems to me that even if the repartitioning worked initially, these devices are at a high risk of failure. The controller can suddenly decide to do some remapping and start using the affected areas once again. Am I missing something here? Is the controller actively marking off bad blocks while performing its wear leveling tasks that these areas can't be used again? I'm guessing "no" because nobody is saying that parted or anything else is reporting a different storage capacity than before.

Is there a way to force these bad block checks and get the controller to prohibit the use of these blocks? Doing something like that would be the ideal fix for any affected KF. You'd end up with a smaller storage device in the long run, but it would be reliable with the space available.
[Kindle Fire Android Development] lovejoy777:
maybe a dumb question:-)

is there a way to install everything on a usbpen (running off external hub)which i could usbboot into?

is this how the nook tab works off external sdcard?

if so does it need a whole new kernel etc or could the bootloader & meta-inf file etc just be altered like the dualboot roms/partitioning.

is there a way to get all firmware etc onto a pendrive?

if this is a crazy thought please don't laugh.:-)
[Kindle Fire Android Development] lovejoy777:
lovejoys dmesg

can someone have a look at this for me and see if it tells them anything.

cheers

https://dl.dropbox.com/u/75065013/lovejoysdmesg1.odt
[Kindle Fire Android Development] Entropy512:
That's why repartitioning has been, in general, NOT considered a valid fix for people in the SPH-D710 and GT-N7000 communities (the hardest hit by this issue, IF it is the same issue.)

Of interest - IF it is the same issue, there is no physical damage to the flash memory. The memory cells themselves are fine - the problem is that the wear leveler's internal data structures were corrupted by a low-level bug in the wear leveller, and now the wear leveller goes into la-la-land if you access those corrupted structures.

It's unknown whether the corruption can spread.

Those who have experienced issues:

1) If you run the following command, do you see anything different than M8G2FA?

cat /sys/class/block/mmcblk0/device/name

2) Has anyone who tried Hashcode's updated version with a candidate for a fix had issues? (Obviously, if you already have experienced damage, that won't help you.) - I'm going to switch tonight, but the problem is I have an MMC08G flash chip, and so far no one who experienced problems seems to have one of those.
[Kindle Fire Android Development] lovejoy777:
this is my new kindle does this mean i'm safe from the superbrick?

steve@lovejoyub:~$ adb shell

~ # dmesg | grep mmc0

<6>[ 2.437347] mmc0: new high speed DDR MMC card at address 0001

<6>[ 2.506011] mmcblk0: mmc0:0001 MMC08G 7.28 GiB

Edit sorry didn't see above post.:-)

Edit2 my brick has M8G2FA:-(
[Kindle Fire Android Development] kinfauns:
Ah... OK. I misunderstood the actual problem, but I guess the end result is roughly the same. Sounds like there's been no real fix discovered to "reset" the leveling data either.

Good luck to all those with a sick KF.
[Kindle Fire Android Development] forest1971:
Hi: your investigation to the root cause of the problem and introduction of a prevention measure in the kernel is truly great! And it will be fantastic if there will be a "valid" fix to the problem. But for the time being few dozen of people have now got their GT N-7000 revived from bricks thanks to re-partitioning workaround (which is reversible) and they are very happy, while no one knows if and when a fundamental fix will come.

cheers.
[Kindle Fire Android Development] smirkis:
these errors pleaged the mytouch4g a while back. it was happening during restores from cwm

I read about them for weeks, then it happened to mine. I warrentied it but same emmc errors, same can't mountaint errors, it never got resolved over there. they all chalked it up as a loss lol.
[Kindle Fire Android Development] Entropy512:
Right now, I can't guarantee that you're safe, HOWEVER, *IF* it is the same bug, you're safe in two ways if you use the updated zip Hashcode posted a page or two ago:

1) Not using a defective Samsung flash chip

2) That version has a kernel with MMC_CAP_ERASE removed - so it SHOULD be safe even on devices with Samsung M8G2FA.

Of course, again, this is assuming that the issue here is the same bug. There's no way to really know without putting many devices at risk.

I'm going to switch over to hash's "fix test" version tonight, but I have MMC08G and so far I have not seen anyone with MMC08G report issues.
[Kindle Fire Android Development] garwynn:
Sorry to jump into this so late in the game, but for those having partition issues - is it causing your device to freeze where it requires a power cycle to correct?

If yes, this may be the same bug as seen with the Note/GS2. This is one of the dead giveaways according to what I have from Mr. Sumrall at Google. (We've seen in E4GT testing that even after the original lockup trying to access the area of memory that triggers this will do it every time.)

If no could it be borked metadata in the ext4 partitions? Since I don't own a Fire I'm not sure if it's possible, but you would ideally want to wipe the eMMC clean (ex. write all zeros or fully format the device) which if this is the cause should fix it.

Again, I'm jumping into this a little blind so please understand if I'm not catching everything right away - but hope this helps figure out what is going on.