yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] smirkis:
if u like cwm I suggest using sbloods cannabil recovery. its cwm based with a 2.6 kernel that doesn't have what caused issues in this one. if that was the only reason for the issue.
[Kindle Fire Android Development] Sblood86:
The other option of course is to check what emmc chip you have; if you have the effected chip than I would suggest you stop using the original release of this recovery immediately (you can use the remake that is posted a few pages but only if you are feeling brave enough to be a tester)

See the following for info on how to check this...
[Kindle Fire Android Development] Veritass:
How would I go about finding my chip out
[Kindle Fire Android Development] ammubarak:
Issue the following command using term console:

cat /sys/class/block/mmcblk0/device/name
[Kindle Fire Android Development] Veritass:
I get app_35@android:/ # cat /sys/class/block/mmcblk0/device/name

M8G2FA
[Kindle Fire Android Development] lovejoy777:
thats the chip which is susceptible
[Kindle Fire Android Development] smirkis:
its just a matter of time.
[Kindle Fire Android Development] vbdss:
A matter of time if he uses the CWM recovery based on Kernel 3.0

Keep using TWRP 2 and be good
[Kindle Fire Android Development] fleurdelisxliv:
mine is still dead also :(
[Kindle Fire Android Development] Veritass:
Oh **** son ima switch to twrp once Im done sending files via ftp. Thanks for the help. I don't wanna brick =(
[Kindle Fire Android Development] Dasanko:
What happened to this attitude?
[Kindle Fire Android Development] lovejoy777:
i wouldn't even do a backup, just install twrp 2.1. (its not worth the risk)

sent from my new non bricked kindle:-)
[Kindle Fire Android Development] Veritass:
Well seeing how I wasn't scared then and am Now..... Didn't think i was affected. I'm on a twrp now no problems
[Kindle Fire Android Development] minieod:
hope to hear something soon!
[Kindle Fire Android Development] Jdom58:
Anyone know of anyone fixing these, I'll be glad to give a donation :fingers-crossed:
[Kindle Fire Android Development] Adeel1234:
i am also looking for a fix for my bricked kindle
[Kindle Fire Android Development] forest1971:
If kf can still get into twrp, then maybe revived using parted.
[Kindle Fire Android Development] OhioDroid80:
I hope this isn't a very stupid question, but what about using CWM 5.0.2.x for installing ics on my wife's fire.
[Kindle Fire Android Development] smirkis:
if u want to use cwm, flash sbloods cannibal open touch.
[Kindle Fire Android Development] psiwar:
Replace Hardware parts

Hashcode, Thank you for all you have done. I have been waiting for some fix to my broken kindle fire, how have you fixed yours?, is it posible to replace the component parts compromised? how can we do it?.
[Kindle Fire Android Development] Adeel1234:
yes if we can replace internal sd than we can surely revive our kindle fire
[Kindle Fire Android Development] veeman:
Good luck with that. It would be easier to replace the motherboard.
[Kindle Fire Android Development] Adeel1234:
motherboard will be half priced of kindle fire..

so its easier and less pricy than replacing whole motherboard

i have seen a member of xda developers replaced internal sd of desire hd and

got it working again...
[Kindle Fire Android Development] smirkis:
replacing the emmc would be difficult. swapping motherboards wit a unit that has a busted screen, would b easier
[Kindle Fire Android Development] Entropy512:
Yup. There may be a chance that damaged eMMC chips can be salvaged after this weekend. No guarantees though...
[Kindle Fire Android Development] lovejoy777:
Wow that would be awesome
[Kindle Fire Android Development] Thepooch:
Indeed do tell many are still waiting for the fix:-)
[Kindle Fire Android Development] kostos:
it will be a long weeeeekend
[Kindle Fire Android Development] lovejoy777:
Unfortunately I don't think it's a matter of telling yet. More a matter of finding out. (But I have all my toes & fingers crossed).

Thanks for all your effort in this Entropy if you need a Guinea pig then I'm up for it, just let me know.

Thanks again

Steve
[Kindle Fire Android Development] Entropy512:
Yeah. I'm hoping the information is generic enough to apply to devices other than Samsung's own mobile products. I still don't know whether I'll be getting documentation, source code, or compiled binaries. :)
[Kindle Fire Android Development] fleurdelisxliv:
cant wait to see what happens i miss my kindle! ive held on to it to see where this would go :fingers-crossed:
[Kindle Fire Android Development] lovejoy777:
The weekend has started,

Let the games begin :)

(Not being inpatient, just exited)
[Kindle Fire Android Development] lovejoy777:
OK its a no go, I think. (Just read a post in another thread by entropy)

Samsung are not releasing the fix as it can potentially make things worse (if its used on a chip that doesn't currently have block damage). :(

Thank entropy for all his hard work in this matter.

So if anyone has/ can get a good mother board that they can ship to England I would appreciate it.

Cheers

Steve
[Kindle Fire Android Development] jsisaev:
can i get download link to test CWM recovery?
[Kindle Fire Android Development] lovejoy777:
Why would you want to?

It can brick your kindle.

( or are you a dev who wants to test?)
[Kindle Fire Android Development] jsisaev:
i want to test my kernel.
[Kindle Fire Android Development] lovejoy777:
You don't need this to determine weather you have the susceptible chip.

Read this thread and you will understand.

I suggest not to install this recovery.

Sblood has a safe cwmr , or stick to twrp to be extra safe.
[Kindle Fire Android Development] Thepooch:
I`ll be checking around for you lovejoy777 see if I cant score one at the local pawn shops:)
[Kindle Fire Android Development] lovejoy777:
thanks mate. I had the use of one for a couple of weeks. and now find myself kindle less again. I am finding it almost impossible to get another. and have been quoted £80 shipping.

so if you could get me a cheap one and only send the motherboard you can keep the spare screen & battery.

cheers

steve
[Kindle Fire Android Development] Thepooch:
Your welcome Steve :)

cheers

Michael
[Kindle Fire Android Development] fleurdelisxliv:
bout to have to let it go for parts :(
[Kindle Fire Android Development] forest1971:
Can you get into recovery or nothinh turn on at all. If still have recovery, then there is a chance. If nothing at all, then probably only good for parts.

Sent from my phone
[Kindle Fire Android Development] minieod:
Yea? How?

:(

Sent from XDA app
[Kindle Fire Android Development] forest1971:
The brick in the case encounter in this thread seem to cause damage in some partitions. That can be fixed using repartition workaround. some key steps are below:

1. start KF in twrp

2. connect KF to pc in adb (pc need to have driver installed and a adb folder)

3. run abd shell and parted to print the partition table.

~ # parted /dev/block/mmcblk0

4. use dd command to check if there faulty blocks in key partitions: 9, 10, 11, 12

for partition 9:

~ # dd if=/dev/block/mmcblk0p9 of=/dev/null

it will freeze or report I/O error when encounter faulty blocks in a partition.

similarly for partitions 10, 11, 12

then once damaged partition is identified then can do repartition workaround using parted to leave the faulty area unused.

some details are in page 27 of this thread onward and in the repartition guide by Eldarerathis http://xdaforums.com/showthread.php?t=1388996

cheers.
[Kindle Fire Android Development] loCe45:
Can we expect CWM in future on 3.0 kernel based roms ? Is anybody working on solving current issues or is CWM development being halted ?

I just got used to CWM on my phone, and i expected to have it on kindle :S
[Kindle Fire Android Development] Sblood86:
Until someone confirms with absolute certainty that the superbrick issue has been resolved by removing the max_cap_erase option in the kernel I personally will not be developing a 3.0 based CWM (can't speak for Hashcode, or anyone else)... Having said that CannibalOpenTouch is hybridized from gingerbread, ics and a bit of jellybean in the next release; we made a few changes to the UI but it's closer to CWM than TWRP for example. You might check it out if you haven't (not to sound conceited but I'm quite happy with it lol).
[Kindle Fire Android Development] webdroidmt:
I know you have the thread at android central but just curious as to why you haven't opened a thread here for COTR? I've been using it since v 2.0 with twa's JB rom and it's been working fine. I'm sure there are lots of people who don't even know about COTR and would like to have an alternative to TWRP. I know smirkis has COTR in his thread but I think it would be good for COTR to have its own thread by the dev. Just my opinion. LOL

Do you have any concerns that there may be some issues between COTR and JB roms? Anyway, so far for the time I've used COTR, it's done the things I needed without issue. That is, flashing JB roms, backup/restore and mounting USB storage. Thanks.

Mike T
[Kindle Fire Android Development] Sblood86:
JB Roms should work fine, Drew and I had to create a symlink to sdcard so that the JB mount points passed by Goo Manager actually worked but beyond that should be good. As why the thread is @ AC that was done out of respect to the original creator of the Dooderbutt image and the collaborative nature of the project; I may mirror it here on XDA though come next release simply to try to raise awareness. For now I don't want to hijack this thread so I won't really go into it much more here I just figured I'd mention it as an alternative to TWRP.
[Kindle Fire Android Development] webdroidmt:
Yeah, I remember you mentioning the issue with the JB mount points in another thread. As for your reasoning for only having it on AC at this time...I understand! Thanks for your reply.

Mike T
[Kindle Fire Android Development] sthomas38:
http://xdaforums.com/showthread.php?t=1823918

Can it be usefull ?
[Kindle Fire Android Development] Entropy512:
Only for confirming when you're screwed. Most people already know that at this point, since no dangerous recovery has been available for Fire for months.
[Kindle Fire Android Development] Entropy512:
One can never be absolutely certain here - however I'm 99% certain that removal of MMC_CAP_ERASE will do the trick. ALL of the evidence says that the damage here was Samsung Superbrick, and I'm 100% certain removal of MMC_CAP_ERASE from the appropriate host driver will do the trick. There's the slight 1% chance or so that this issue is something else - but I don't think so.

As an extra layer of protection, recoveries and update-binaries should be built with BOARD_SUPPRESS_EMMC_WIPE set to true in BoardConfig.mk (see galaxys2-common device tree for example.)
[Kindle Fire Android Development] Sblood86:
Forgive me if I'm still a little skittish lol... I may fiddle with that later though; the touch code we're using for COTR has issues w/ a lot of devices; I think one of the main issues is that we're using Gingerbread as our base (there's an obvious reason for this as mentioned previously but that doesn't mean I wouldn't like to rebase it a bit). The touch code implemented by Gweedo (that Hashcode has used here) is much cleaner in it's event handling (that's partly do to the updated event handling in ICS and Jellybean in the first place not just the touch code itself).
[Kindle Fire Android Development] soupmagnet:
I just wanted to thank all of the people here who worked, and are still working to find a solution to this problem. I had an old completely bricked Kindle that I decided to try and get running again. I first had to restore it with Firekit, and that was only the start of my problems. Long story short, the things I learned from studying this thread helped me to identify the problem, repartition the file system and bring this otherwise unusable Kindle back from the grave. I can't say enough how proud I am to be a part of this community. You guys f*cking rock!
[Kindle Fire Android Development] Jdom58:
I have a bricked kindle due to the eMMC bug with CWM, if anybody wants to give it a shot at reviving it let me know, I have exhausted my limited talents and have come up empty.
[Kindle Fire Android Development] soupmagnet:
Well...what have you done so far?
[Kindle Fire Android Development] Jdom58:
Hi Soup, I have tried everything to get it to power on (charging for days, button combination, USB via PC (wont recognize) and as a last resort openning the Kindle up removing the battery and trying to bypass the eMMC with the paperclip connection via USB. Not really sure what other measures there are, just keep checking here to see if anyhting new has developed.
[Kindle Fire Android Development] soupmagnet:
If it won't power up at all (no screen, no backlight, no LED, etc.) then Firekit w/shorting trick is what you most likely need to do.
[Kindle Fire Android Development] Jdom58:
This is what I was trying, the usb trick of opening up the back of the kindle to short out the connection and after MULTIPLE tries got it just right but it went as far as

sending 2nd stage to target...

waiting for second stage response...

sending image to target...

fixing partitions...

<waiting for device>

then nothing happened for about 5-10 minutes so I tried again from the begining and got the same results, any ideas?

Thanks in advance
[Kindle Fire Android Development] soupmagnet:
From my experience, you have to hold the short throughout the whole process and it may take a few tries to get it right. Also, try to use a safety pin rather than a paperclip. It will help keep it in the same spot while you're plugging it in.
[Kindle Fire Android Development] Jdom58:
I must have attempted it 100 times and when the PC acknowledges the USB connection it's always the same outcome.

The way Entropy512 explained it to me was:

"That sounds a lot like symptoms of the eMMC brick bug - it looks like it boots, and then starts to try and write new bootloader/partitions to your device, then it hits a corrupted part of the chip, which causes the eMMC chip to hang."

So I've been trying to figure out a way to get past that <waiting for device> part of the boot without any luck so far.
[Kindle Fire Android Development] soupmagnet:
If Entropy512 was speaking in the sense of using Firekit, by choosing "usb_fix_parts_install_twrp_fff", then it would be the case because of the "fix_parts" portion of the command. You need to choose the "usb_install_twrp_fff" command instead.
[Kindle Fire Android Development] Jdom58:
Arghhhh still no luck on my end, like I said, if anyone wants to try and bring this back to life let me know. I'm sure there are alot of others with the same scenario that would love a success story.
[Kindle Fire Android Development] Jdom58:
One last bump to see if there is any hope for these :fingers-crossed:
[Kindle Fire Android Development] fx3000se:
Dear hashcode,

I (http://xdaforums.com/showthread.php?t=2063359) seem to be very badly eMMC-plagued. All my partitions seem to be affected...

Did any of your ideas "grow"? I would be mainly (but not only ;) ) interested in this "approach"

Thnx

Clemens
[Kindle Fire Android Development] Hashcode:
Nope, the Kindle I did this too is still broken today. :/
[Kindle Fire Android Development] shantam:
Haaah we are robbed

200$ wasted:banghead:

***//'?'\\***
[Kindle Fire Android Development] xolanir:
Just flashed and everything went well. One question though, not sure if I did something wrong, but the only options I see in the recovery are just the virtual buttons and no choice selections. Thx in advance for the help. :confused:

Update: nevermind, nothing a reboot couldn't fix.
[Kindle Fire Android Development] BrooksBlood:
Anybody else experience issues when trying to use rom manager premium? Since its a system app I tried to uninstall the pre installed version clear the data and reinstall the premium apk but it still prompts me to download the premium when I choose certain settings. Thanks in advance.

Edit: Never mind I finally got it to work. I went into root browser, renamed the pre installed apk file with .bak after. Then I moved my premium from manager apk into the system/apps folder and replaced it. It still wouldn't work so then I went into settings and hit the apps tab, found rom manager and when I pressed it it said uninstall update instead of just uninstall so I pressed it. It got rid of rom manager altogether so I had to redownload the premium via play store and it worked. Sorry for the novel haha :-P
[Kindle Fire Android Development] foxdog66:
Try setting up the web connect and restart the app
[Kindle Fire Android Development] smirkis:
doubtful. it checks md5 hash before flashing.

works like a charm. nice
[Kindle Fire Android Development] linktohack:
Oops, wrong thread.

Gửi từ Kindle Lửa của tôi qua Tapatalk 2
[Kindle Fire Android Development] pbailey212:
That's right, I forgot about that. Well I guess it doesn't hurt to double check. I'm old school, we didn't have tools like that back in my day ;-)

sent from my Nokia 5110
[Kindle Fire Android Development] c5satellite2:
Try a different charger if you have one around. What happens if you charge with the phone off?
[Kindle Fire Android Development] portezbie:
When I try and backup with this version it gets stuck on "zipalign.log" and just hangs....

Anyone else having this problem?
[Kindle Fire Android Development] smirkis:
I just did a backup and everything went fine.
[Kindle Fire Android Development] portezbie:
Shrug, I dunno tried three times and it happened each time. Went back to the previous version and it worked fine again.
[Kindle Fire Android Development] gunshipmlr00:
I flashed this recovery and now I can't get out of it. I have tried wiping cache/dalvik/fix permissions and reflashing the rom I am using. I also can't get it to show adb so I can't just fix it. Please help.

EDIT: I figured it out. Please feel free to delete this post. I'm sorry.
[Kindle Fire Android Development] gweedo767:
Awesome work, glad to see it getting used more!
[Kindle Fire Android Development] teookie:
How did you get adb to work? I'm having trouble with this. I've added 0x1949 to my adb_usb.ini file and tried updating the drivers but device manager still shows a yellow exclamation point on "Other device" "Amazon".

...and I have FFF loaded but fastboot can't see the kindle either. I need a set of USB drivers that work with whatever vendor ID is on this recovery.

EDIT: Never mind, got it working literally 30 seconds after posting this. It was a windows problem...
[Kindle Fire Android Development] Evo_Shift:
Happens to me with traces.txt. I had to reflash my old CWM. I am also using a stock rom if that matters. Maybe these problems are only when trying to back up stock roms? I didn't try with a cm based rom. Not a big deal to me really since I don't want to try any CM9 roms yet.
[Kindle Fire Android Development] portezbie:
Im using Hellfire CM7 so I don't think it's that.
[Kindle Fire Android Development] jacewt:
I backed up modaco with no problem. It seemed to take a long time but it did it. Got stuck on the data part for quite a while.
[Kindle Fire Android Development] xolanir:
Just tried the back up as well and have need stuck on the traces.txt for like 10mins. What is the traces.txt referring to? I'm currently running the Modaco gr8 myself. Thx in advance for the help.
[Kindle Fire Android Development] Pkt_Lnt:
@Hashcode "owns" my Fire completely now, and that's good! Thank you.

Kindle Fire w Hashcode ICS ROM + 3.0 kernel & Tapatalk 2
[Kindle Fire Android Development] foxdog66:
Looks like it's getting stuck the data partition where all the apps from play store install to , this partition can be rather large depending on how many apps you have installed and how large they are. Are you sure you have enuf space on the sdcard to make a backup? You might be running out of space and it just stopping because of it
[Kindle Fire Android Development] xolanir:
I have like 2.57GB of space left on the sd partition. How big are the backup files once it's done running?
[Kindle Fire Android Development] fleurdelisxliv:
Ok maybe this can help some of us with the emmc bug! One of the guys in the N7000 general thread replaced his emmc chip and his note is working fine. just an idea ima try and find a chip i think he ordered it from china. Worth a shot if it dont cost to much :thumbup:
[Kindle Fire Android Development] fleurdelisxliv:
Well its dead but yea lol
[Kindle Fire Android Development] mkhtfld76:
Lol
[Kindle Fire Android Development] Hashcode:
EMMC CORRUPTION REPAIR INSTRUCTIONS MOVED:

http://xdaforums.com/showthread.php?t=2413453
[Kindle Fire Android Development] Evo_Shift:
That's not it. The older cwm works fine as does twrp. Something in the new one isn't handling certain files very well. That traces file is a really long text file even though I don't have many apps(and it isn't present in cm roms) Maybe the zipalign.log file that other person had a problem with is a long text file too which doesnt appear to be present in stock roms, at least not mine.
[Kindle Fire Android Development] Sblood86:
This is true (only reason I kept those tools in my other release was for possible backwards compatibility)... Unfortunately it's this change that will keep this from working with other forms of FFF so it is imperative that people upgrade to FFF1.4 or above before using this recovery or they will likely end up with the CWM bootloops I've seen described.

Also older roms will have issues accessing recovery do to the board changes for post mode (this is how it should be just the old roms were compiled for the old method); I have a fix on my cm7 tree I just haven't had a chance to rebuild and upload it, will try to do so tonight so that people using CM7 can use this recovery option.
[Kindle Fire Android Development] Nightly Suicide:
The backing up must have something to do with the KF Stock ROM. I just backed up my gedeROM in less than 5 mins. Maybe this recovery is only for CM9's. Has anyone backed up with a CM7 yet?
[Kindle Fire Android Development] xolanir:
Thx for your input. I'm wondering what that difference might be cos there's another user on Modaco that was able to successfully make a backup. I guess I'll go back to my previous cwm till this issue can be resolved or until I figure out what it is about those two files make the backup process hang for that long. :banghead:
[Kindle Fire Android Development] foxdog66:
that should be plenty of space. The largest I've had was just over a gig so it must be something else that is the problem
[Kindle Fire Android Development] xolanir:
There's another user on the Modaco ROM which is an optomized and tweaked stock ROM. They were able to do a backup successfully. I'm just trying to figure out what could be the difference between the Modaco I'm running and his. :confused:
[Kindle Fire Android Development] xolanir:
Yup...it's got me a little baffled.
[Kindle Fire Android Development] Hashcode:
Could you check /cache/recovery/last_log? and the other file in there for hints as to what happened?
[Kindle Fire Android Development] xolanir:
Here is the recovery log. Not sure what you're looking for but hope it will explain what the issue is. Thx for helping me look into it.

Update: so I think there's an issue with the new cwmr with stock rooted ROM's. I just tried both doomlords and sbloods CWM recoveries, and both were able to produce backups. I really hope this bug in hashcodes cwmr can be squished so we can all enjoy it equally. :D
[Kindle Fire Android Development] Evo_Shift:
Here is mine as well. Running stock rooted 6.3.1.

This last time I got hung up on a file called "tombstone_02" which I thought was fitting :) There were no other files in the recovery folder nor the lost+found folder in the cache.
[Kindle Fire Android Development] Hashcode:
I have a feeling that there's a file system setting in the 3.0 kernel that is missing and / or messing with the 2.6 based /data and /system partitions.

Checking the logs.
[Kindle Fire Android Development] xolanir:
Thanks brother! I appreciate all your hard work. You're the man dawg!