yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Android Development] jsantiago.antonio:
Speaking of bad /data & /cache partitions.. My kindle went berserk when i flashed this recovery from TWRP. I' feel like the mistake was on my end and im seeking help on how to correct it, in case no one seen the thread. I'm completely unable to flash anything from the SD card.. it's quite the bummer =[

http://xdaforums.com/showthread.php?t=1654498
[Kindle Fire Android Development] Hashcode:
Can you put something on /data instead and reflash back to TWRP?
[Kindle Fire Android Development] jsantiago.antonio:
I can't even run adb shell, i'm certain it's running because windows automatically runs the drivers within windows.

So i can't print partitions nor push any files to /data if that's what your asking.
[Kindle Fire Android Development] spartan018:
I'm getting:

assert failed: getprop("ro.product.device") == "blaze" || getprop("ro.build.product") == "blaze" || getprop("ro.product.board") == "blaze"

when attempting to flash any ROMs using this recovery. Reverting back to DooMLoRD's 5.0.2.7 recovery fixes it.
[Kindle Fire Android Development] sthomas38:
Isn't it because now it's otter instead of blaze?

Envoyé depuis mon GT-I9000 avec Tapatalk
[Kindle Fire Android Development] Sblood86:
CM9 is otter yeah, CM7 has been blaze since before 9 started being developed and noone (Jackpot, Whistlestop or myself) ever changed it, mainly cause (at least at the time) there wasn't a direct need to.

I presume that's CM7 though as that's the first line in the update script...

What do you think hashcode, do I need to update all the cm7 stuff to say otter? lol
[Kindle Fire Android Development] Hashcode:
Hmm. I think I can probably change the build.prop in this recovery to support 1 of those asserts so that it doesn't fail.
[Kindle Fire Android Development] Sblood86:
That or there may even be a way to remove the need for the asserts anyway I would think but I'm still not extremely familiar with how the build controls things like the updater script.

Whatever you think is best you definitely have a better grasp on this than myself (afterall my code experience is limited to LPC muds).
[Kindle Fire Android Development] x0xhellx0x:
Found a fix to this the problem is that the clockwordmod only accepts this device as otter not blaze what we need to do is set up a new cm7 device tree but with otter not blaze this will fix the issue because we need a single device name anyways otter should be what both are named
[Kindle Fire Android Development] jsantiago.antonio:
Is there a script or option that this recovery could run that could potentially repair partitions?
[Kindle Fire Android Development] foxdog66:
You want the bootloader thread, you can run "fastboot oem format" to return the partition layout to the stock layout
[Kindle Fire Android Development] Jdom58:
Ok hope this isn't a dumb question but can I flash roms that say are TWRP specific with this recovery?

Very nice recovery BTW!!
[Kindle Fire Android Development] Nightly Suicide:
I don't think it really makes a difference. Some just prefer it, is all.
[Kindle Fire Android Development] Jdom58:
I'm thinking the same thing, I wanted to try gedemis's ROM but it specifically says MUST use TWRP :confused:
[Kindle Fire Android Development] Hashcode:
This recovery can flash the 3.0 ROMs. Other versions of CWRecovery may have issues.
[Kindle Fire Android Development] GoSooners345:
Would flashing cwm via rom manager work
[Kindle Fire Android Development] Sblood86:
We know what's causing the issue the question is more of if that is actually the

best

way to fix it... If Hashcode doesn't come up with any ideas soon I will probably go through and start updating the cm7 tree (might do so anyway I've been considering it just to bring the two more in line with each other (if you would like to help pull requests are always welcome : offending repos (device)(vendor_amazon)(vendor_cyanogen) incidentally I want to update the build process as well, I've learned a bit since I initially set up that tree and would like to clean it up a bit)

Rom manager will not be able to flash this recovery or any current recovery for the kindle for that matter (both current versions of CWM do work in rom manager with fff 1.4a and the new postmode changes for the recovery boot), you will have to install recovery than tell rom manager that you flashed 3.x
[Kindle Fire Android Development] Hashcode:
I'm going to do a new version of this recovery which will be compatible w/ stock and CM7 builds.

No sense in going back and trying to change every old ROM.
[Kindle Fire Android Development] sthomas38:
Will it fix the reboot system bug Hash ? :)

Yes, I know, no ETA or other kind of ****s, don't blame me :p.
[Kindle Fire Android Development] kostos:
pls hlp

after erasing data and cache in this recovery i've now got an error in recovery that

i've tried all things described in the forum about such error nothing helps

any ideas?
[Kindle Fire Android Development] Nightly Suicide:
Try factory reset, anytime you wipe everything you always want to do a factory reset.
[Kindle Fire Android Development] kostos:
in cwmr

factory reset brings nothing

waiting for some seconds and then again are errors mounting /cache/recovery/command
[Kindle Fire Android Development] shantam:
Kindle Fire not powering On problem after stucked at format/data cwm

i have installed cwm 5.0 by hashcode and was factory resetting kindle fire

but it stucked at formatting/data..

after this i switched off it by pressing power button for 20 seconds..

and now its not turning on..when i connect it to pc..

pc asks for omap 4430 drivers..

what happened to my kindle is it bricked or dead,,plz help
[Kindle Fire Android Development] smirkis:
ur emmc might be dead. this is a bad trend
[Kindle Fire Android Development] johnwayne007:
This just happened to my kindle using this CWM, i wont be using any CWM on the kindle for a long time now. Luckily i was able to take it back to bestbuy and they did a warranty exchange!
[Kindle Fire Android Development] shantam:
clock work recovery is still in beta stages..its giving problems to us..i have bricked my kindle because it was hanged at formatting/data in cwm..so i powered it off by 20 seconds pressing power button.but now its not powering up neither on charger or pc usb..

people should avoid using cwm for now.and use twrp which is very good and stable with 0 errors..
[Kindle Fire Android Development] xolanir:
I've been using CWM now for about 4 months and haven't experienced any issues. Sorry to here about what's going on. The reason a lot of people have been switching to CWM was that twrp hadn't been maintained or updated in a while. What other methods have you tried to revive your KF?
[Kindle Fire Android Development] johnwayne007:
I tried putting TWRP back, that didn't work it wouldn't even load just showed the blue TWRP Screen. I put CWM Final on, and it just kept telling me it that it couldn't mount any of the partitions. I than tried to fastboot oem format, that completed but when i would go back into CWM it still said that it couldn't mount the the partitions. I tried using the unbrick utility to try and flash back to stock, and it would format the cache partition successfully, but than would hang at formatting data. After i tried all the things i could think of to try and recover it was when I finally gave up and took it back.
[Kindle Fire Android Development] Stage:
Are you using a gingerbread or stock based ROM?
[Kindle Fire Android Development] Hashcode:
While I've never seen any errors like the ones described, I'm concerned that there maybe an issue somewhere in the recovery/kernel combo.

Should I pull this link for now?
[Kindle Fire Android Development] dnathan13:
It has been working great for me. Honestly the issue the guy has been describing with hanging on format /data sounds like a partition issue because he then had no way to get back into anything. If recovery/kernel was causing this I believe you would see a larger percentage of people having the issue. I would have been interested to see what would have happened if he checked his partition sizes or wiped them and redid them (similar to elderathis method of manually repartitioning). May have done nothing, but if it was hanging on /data it should not have ruined his whole kindle without a different underlying problem.
[Kindle Fire Android Development] shantam:
i was using twrp before this and it was giving me awesome performance with zero error when i switched to cwm it gave me following error

i am stucked at waiting for device

i bricked my kindle when i factory resetted with cwm recovery and it stucked at formatting/data

then i powered off the device by pressing down the power button for 20 seconds.then i pressed power button and it did''nt booted up..

now i have installed firekit live usb and issued the command for usb_fix_install_fff_twrp

and plugged the device.

device powered on and in terminal it was showing that

sending 2nd stage to target

waiting for 2nd stage response

sending image

fixing paritiions

and its showing waiting for device

and i stucked there for 30 minutes but nothing happened.then i unplugged the kindle and powered it off

i have issued every command listed on the terminal

one thing is that i have not transferred any fff bootloader,twrp or rom file to root of drive..

should i transfer the files it requires like twrp,fff,or roms

now what should i do for getting my kindle to life

i have tried this for about 4 to 5 times with no success..
[Kindle Fire Android Development] webdroidmt:
Have you seen Sblood's latest post on his CWM Touch for K 3.0? Maybe relevant?

http://xdaforums.com/showpost.php?p=26221918&postcount=139

Mike T
[Kindle Fire Android Development] Sblood86:
Probably not too much, codewise the handling of factory reset isn't really all that different from the other versions of CWM, I was considering pulling the source for this and looking at the differences (I've diffed the cm7 and cm9 recovery before though not much outside of UI handling and the retouch binaries).

Other than that the next main difference would be the kernel, my recovery is (for some reason) using the kernel for the old cm7 tree (I'm not entirely sure why I swtiched this from the lite kernel that DooMLorD was using {have been considering switching it back actually} lol).
[Kindle Fire Android Development] xolanir:
Sounds like your data partition is corrupt, but then again I may be wrong. You could try GNU parted and take a look at your partitions, and maybe you may need to repartition your KF to fix the data partition. In the dev section, there's a guide that talks about repartitioning the KF for storage reasons, but I'm not sure if it'll be a remedy in your case. Good luck!
[Kindle Fire Android Development] johnwayne007:
Yeah i read through that guide and even downloaded and compiled fireparted, which wouldn't even load the partitions it just hanged while in CWM. While inside CWM, I went into mounts and tried mounting all the options and got unable to mount partition. I no longer have that kindle, and am still at a loss as to what actually happened. I'm wondering if the people who are having similar problems used the zip to install, and if that may be the culprit? Also I plugged it into a USB cable and turned it on, it never showed up in Device manager/ADB devices even after 30+ minutes of it being on.
[Kindle Fire Android Development] kostos:
i have the same problem while formatting data/cache in this recovery and shutting down the device in the process

one good explaination is described in this thread

so after many manipulations to my device i understood that the emmc should be replaced

but i didn't try to make new partition table by hands (cause i don't now how yet)

another off-t question is what emmc to choose
[Kindle Fire Android Development] dnathan13:
It is a really bad idea to ever turn off in the middle of a format. The only way you should is if was stuck there for 30 minutes or more. Cwm takes longer than TWRP so have patience. If you have to do something try connecting to usb and see if adb works, don't just shut down!

If you already have it messed up try repartitioning manually. It is a little confusing, but if you read the directions step by step you can do it.
[Kindle Fire Android Development] kostos:
repartition doesn't work, emmc is fried

cwmr made it flawlessly
[Kindle Fire Android Development] xolanir:
Man that's rough. I used the zip flashable myself and it installed without a hitch. The only issue I had though or maybe let me say that the recovery didn't like my rooted stock KF. Anytime I tried to do a backup, it would hang and stop at some point during the backup of the data. So I reverted back to Doomlord's cwmr in the meantime. Sorry that things didn't work out for you.
[Kindle Fire Android Development] james.shumaker:
CWMR Brick

Out of the coutless number of times I have used CWMR to flash various "ROM" flavors across several devices, this is the first time I have ended up with a brick. I can fastboot and flash TWRP, but TWRP never goes beyond the splash screen. If I fastboot flash back to CWMR, I can get "in", but cannot mount any of the mount points. ADB shell can return the eMMC name, but nothing else. In effect, its as if everything except the recovery is gone. No partitions, nothing. Any clues on how to bring back to life?
[Kindle Fire Android Development] smirkis:
return it and buy a new one.
[Kindle Fire Android Development] james.shumaker:
Returning not an option

Yeah ... unfortunately, that isn't an option I have available - the receipt train left the station a long time ago sometime during my move after retiring from the Navy.

I can send a slew of fastboot and adb commands, but nothing that will get me to where I can load ROM because the entire drive is somehow unpartitioned - this as a result of simply running a factor wipe. Unlike Windows 7's Explorer, Ubuntu recognizes it immediately as an unpartioned 14GB drive with the mount point being "/dev/loop0." Hell, I even got Ubuntu to change the volume label, but it won't let me reformat the system in order to rebuild the partition table because it cannot unmount the partition. Again, not sure what CWMR did/failed to do right this time around, but it certainly seems all but FUBAR at this point.

It's a cheap gadget that I have enjoyed, but I would still prefer to salvage it if possible.
[Kindle Fire Android Development] dnathan13:
So are you saying you can't build the partition tables yourself? I ask because at one point there was a program to change the sizes of partitions, but it was messed up and deleted all my partitions except recovery. I used the thread to then manually rebuild the tables myself and thus get unbricked.
[Kindle Fire Android Development] dnathan13:
I just bumped a thread that talks about it, but if you can't even adb and access your tables then idk
[Kindle Fire Android Development] coachmai:
not sure what (this) cwmr did to the flash memory when a factory reset is selected. but looks like the partitions for the recovery and bootloader is fine - maybe physically separated. everything else is completely messed up - parted cannot read the device and formatting individual partition don't work.

Anyway, if your kindle is still under warranty (within a yr), you can still restore the stock recovery and bootloader (in that order) and exchange it with amazon assuming you have the fff bootloader.
[Kindle Fire Android Development] james.shumaker:
Thanks

Much appreciated, bro. eMMC is clearly jacked:), but because I can still get to the recovery section, I can flash stock recovery and boot and go the warranty route.

Thanks to the everyone else who tried to point me in the right direction.
[Kindle Fire Android Development] vbdss:
I tried to wipe everything and the trhing frozed on /data format.

Now i cant mount or format anything, i am able to enter CWR, but cant do anything.

It gives something like make_extf4fs failed on /dev/block/mmcblk0p10

What can i do?
[Kindle Fire Android Development] smirkis:
how about pulling the download for now hashcode? even tho I'm using it with pout issues, others are literally bricking their kindles.
[Kindle Fire Android Development] dnathan13:
Really?... Read the last like 2-3 pages
[Kindle Fire Android Development] vbdss:
Thank you for helping with nothing

Btw, i was using a CM9 Rom, Gedemis to be exactly.

I can access ADB, when i issue adb devices, it says my device is in Recovery, which i am now when on CWR.

Cant use Fastboot, i dont now why, but issue the command adb reboot bootloader doesnt help.

On Parted if i use print it returns /dev/block/mmcblk0 unrecognised disk label

if i issue on shell fdisk -l /dev/block/mmcblk0 it return I/O error

if i try to format /dev/block/mmcblk0 will i screw everything even more?
[Kindle Fire Android Development] smirkis:
with adb, use fbmode from 6.3 root

adb push fbmode /data/local

adb push fbmode /data/local/fbmode

adb shell chmod 755 /data/local/fbmode

adb shell /data/local/fbmode

adb reboot

u should end up in fastboot

fastboot OEM format

see if it works. if it rebuilds your partition table reflash the stock 6.3.1 bin and reroot.
[Kindle Fire Android Development] vbdss:
When using adb push fbmode /data/local/fbmode, it says not a directory, but i can push to adb push fbmode /data/local

dont know if it helps, but using Android Commander, i get this screen on CWR

Do the Fastboot oem format command takes a long time to finish?

because after i press enter and the command is passed to the device, it appears a message saying it was succesful with only 0.60 seconds.
[Kindle Fire Android Development] vbdss:
I think that everyone that have the problem, have a brick now.

Dammit, i was really enjoying the kindle fire and hashcode efforts to make a better kindle fire.

It were 2 great months with my kindle.
[Kindle Fire Android Development] Hashcode:
Download pulled. Apologies to those who are experiencing problems right now.

I'll see what I can do to diagnose what is happening to better understand how to solve it.
[Kindle Fire Android Development] vbdss:
I can only thank you, you cant be responsible for this, we can only hope that a way to fix it is found and dont take lots of money (which i dont have anyway)

One more thing, if you wanna know if your emmc is fried, use the command on adb shell ---------> dmesg | grep mmc0

Mine is like this

~ # dmesg | grep mmc0

dmesg | grep mmc0

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

<6>[ 2.199096] mmcblk0: mmc0:0001 M8G2FA 7.20 GiB

<0>[ 33.236663] last sysfs file: /sys/devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/name

And then again, is it possible to format /dev/block/mmcblk0 to ext4? Maybe this could help? And after it rebuild the other partitions
[Kindle Fire Android Development] YaKillaCJ:
If Ubuntu can recognize the partition. Then thats a start. Hmm, sometimes I had issues formatting while in Ubuntu. Give GParted Live Disk a shot to format. My thing is this, when they build the thing, its wiped. So they did something to get it up. Maybe a factory cable.

No expert on this tho. Just trowing out ideas.
[Kindle Fire Android Development] vbdss:
I think we need to format the master partition, /dev/block/mmcblk0

if we could do this, maybe we have a chance i think, but dont know if doing this it will screw everything up

fastboot oem format runs in about 0.6 seconds and returns success. Tried Firekit too, samething
[Kindle Fire Android Development] corlygunnz:
How can I go back to twrp? The easiest way
[Kindle Fire Android Development] Thepooch:
its a shame that its not like a cell phone just sbf it back to stock in linux I`m confused why there isnt a process like this for the kindle a kinda no brainer plug in sbf unplug use. if it were only that easy Im sure it would have been done and redone a dozen times by now.

---------- Post added at 06:55 AM ---------- Previous post was at 06:54 AM ----------

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

---------- Post added at 07:00 AM ---------- Previous post was at 06:55 AM ----------

smirkits scripts are great and really easy to use
[Kindle Fire Android Development] zando2712:
I went back to TWRP 2.1.1 using Kindle Fire Utility

http://xdaforums.com/showthread.php?t=1399889
[Kindle Fire Android Development] abundantmussel:
I have updated the Development Thread with a Warning flag next to this for now.

@Hashcode - Let me know when to remove the flag.
[Kindle Fire Android Development] linktohack:
+1

Gửi từ Kindle Lửa của tôi qua Tapatalk 2
[Kindle Fire Android Development] Stage:
Is there any way to install an older version of CWR using this or am I just screwed?
[Kindle Fire Android Development] james.shumaker:
No apologies required, Hash!

It's all good - no need for apologies, bro. It all goes with the territory and devs **** you put in MASSIVE amounts of personal time to produce quality products pro bono. As end-users, WE alone have responsibility given that each product is issued with an explicit caveat. It can never be said that we aren't forewarned. Perhaps a true de-bricking solution can be found, so I'm not ready to throw my Fire under my back tire just yet, but I might run out and grab another tablet with hope that I can revive the Kindle and at least give it to my son.

THANKS FOR THE GOOD AND DEDICATED WORK.
[Kindle Fire Android Development] Hashcode:
I'm going to try contacting Pokey9000 and work out an sbf-like system supported at the bootloader/usbboot level which will do a full emmc partition restore. Not sure how long it will take to work out, and there may be an issue of recovering the serial #/mac idme info stored at the base of emmc.
[Kindle Fire Android Development] lovejoy777:
can i just flash a recovery.img from cwm?
[Kindle Fire Android Development] lovejoy777:
i think ive joined the club of messed partitions,. with the new 1.4a bootloader how do i get into fastboot?
[Kindle Fire Android Development] droidman101:
http://xdaforums.com/showthread.php?p=26602296#post26602296

A thread full of people that will be more than willing to test anything you guys come up with
[Kindle Fire Android Development] pbailey212:
Again? LoL goods luck

sent from my Nokia 5110
[Kindle Fire Android Development] smirkis:
dang, connect ur device and turn your device off. issue fastboot OEM format and u should get waiting for devices

turn ur device on and it should catch it.
[Kindle Fire Android Development] Stage:
Queston, I've successfully installed this version and successfully run a backup on it. Do I need to be concerned about flashing a new ROM? Is this where people are getting stuck?
[Kindle Fire Android Development] lovejoy777:
does 1.4a have the initial fastboot setting as mine hasn't ever seemed to work since my last f%%k up.

i've got the same as everyone eles ie.

E:Can't mount /cache/recovery/command

E:can't mount /cache/recovery/log

E bla bla bla

all i did was try to install new rom and POW it froze up on installing data.

after reboot i mounted usb storage a couple of times and had problems of freezing up and alsorts and now i can mount usb storage in cwm but my ubuntu only sees it in disk utility as a linux file cd gadget, its not seen at all with gparted.

log shows W:mmcblk0p11 (invalid argument)

W:can't unlink /cache/recovery/log

W:failed to mount /dev/block/mmcblk0p11 (invalid argument)

E:can't mount bla bla bla.

i can get a adb shell

i can push files to sdcard it appears, just can't mount sdcard.

i think we are all in the same boat and i will be hovering over that f5 key every waking minute. lol

thanks for all your dedication hash and all.

my main problem is my mrs ("I told you to leave it alone after the last bricking attempt") lol

edit is there a way to oem format with adb?
[Kindle Fire Android Development] Hashcode:
Has anyone tried to dd if=/dev/null of=/dev/block/mmcblk0p11 bs=(forget the block size)

That would zero out the partition.

I realize this probably wont work if its a bad partition table tho.
[Kindle Fire Android Development] vbdss:
But we need the block size to use this command right? i dont know the block size

dd if=/dev/null of=/dev/block/mmcblk0p10

0+0 records in

0+0 records out

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