yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
KFU's included version of CWM recovery does not flash ICS (and very likely JB) ROMS correctly. This is a bug known to corrupt the flash.

It not likely you'll be able to do anything meaningful with the system currently installed on your Kindle Fire. Unfortunately for you, that probably includes using idme or pushing anything that might help you change bootmodes. Of course, I may be wrong and you might find another way out of the mess, but the easiest way for you to fix this is to use a factory cable, put the KF into fastboot mode, flash TWRP, boot into recovery so you can flash a new bootloader and ROM.

factory cable...

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

fastboot mode...

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

beginner's guide...

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

supplement for rooting... installing a ROM... etc...

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

EDIT: You can try what soupmagnet suggested while I was typing out my post, but you've already shown that you cannot access the /data partition. I think it's going to be something more than simply just an unmounted partition.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
I hadn't really thought about mounting the data partition...it's worth a shot either way.
[Kindle Fire Q&A, Help & Troubleshooting] Zlatty:
Well my adventure just keeps getting worse and worse. I charged the kindle last night to ensure enough battery life for today. It is suck at the kindle fire logo now. I have the drivers loaded correctly and my computer sees the kindle. However I cannot adb or fastboot the device. It also went from composite device to adb device in the device manager.

EDIT:

Was able to install FFF and got to boot into recovery. CWM 5.2.0.7.

In adb I tried to get super user permissions

What are my options at this point. KFU cannot download and install TWRP. I cannot manually push it since I dont have su. KFU's install super user function does not work as it tries to install TWRP.
[Kindle Fire Q&A, Help & Troubleshooting] Zlatty:
Ok, so while I was in CWM, I mounted the SD card, downloaded and transfered a flashable TWRP found here http://xdaforums.com/showpost.php?p=28664718&postcount=127

I flashed the zip and now I have TWRP working.
[Kindle Fire Q&A, Help & Troubleshooting] Zlatty:
I could not get twrp to boot into normal. So I used KFU to change to 4000 mode.

***********************************************
* Activating Normal (4000) *
***********************************************

< waiting for device >
... OKAY [ 0.081s]
finished. total time: 0.082s
rebooting...
finished. total time: 0.001s

The kindle has been told to reboot in Normal Mode.

Press any key to continue . . .

Everything went better than expected.... w00t!
[Nexus 7 Q&A, Help & Troubleshooting] davidtb:
Hello all:

I recently rooted my nexus 7 so that I could OTG a thumb drive for movie/big file viewing, but battery power is quickly consumed.

Is there a way to access a thumb drive and charge the tablet at the same time?

I was looking at this thread for inspiration,http://xdaforums.com/showthread.php?t=1625291 but I got a couple of problems with it.

Any ideas/ help is something,

TIA

db.
[Nexus 7 Q&A, Help & Troubleshooting] flimsy888:
No idea here, but what someone needs to do is make a case with usb passthrough and adds storage to the device...GENIUS!
[Samsung Epic 4G Touch] jangbang88:
Hello,

I am running an ICS FF18 custom rom and I am thinking of switching to run The Blu Kuban. My question is what do I need to do to make sure that I dont brick the phone? What are the steps needed to switch safely?

Thank you all for the help!
[Samsung Epic 4G Touch] brooksyx:
Search for the el29 cwm direct boot kernel and flash via Odin. That kernel is safe to install roms and wipe data and other stuff.
[Samsung Epic 4G Touch] jayharper08:
Please post questions in the Q&A section. Thank you.
[Samsung Epic 4G Touch] jangbang88:
So can I just use mobile odin and reflash to EL26 and then flash like normal? I wont have a problem going from ICS FF18 directly to EL26?

Thanks!
[Samsung Epic 4G Touch] davidstjohn1:
I believe he said the el29 direct boot kernel
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
Alright so here's the deal, my internal SDCARD is corrupted and the /data partition is unusable.

My device is i9003 and it's running on MIUI at the moment. By default MIUI didn't detect my external SD or my internal SD but after editing "vold.fstab" I was able to mount the first partition of my external SDCARD as external memory and everything was good, I could finally use the camera and pretty much do everything else.

But I was still unable to mount the second partition of my external SDCARD as my internal memory which meant none of my messages could be saved and the phone would pretty much go back to factory settings after a reboot, this apparently is because the /data partition (present on the internal memory) stores all the user data such as the time, the theme I'm using, etc and not having a /data partition meant none of these settings were really saved.

Having no internal memory also means I cannot install any apps such as Link2SD.

Moving on, after many hours of googling I found out that it might not be possible to mount the internal memory using "vold.fstab" and the only way to do it could be by mounting the memory manually during init.

So here's what I want again, I want to use the second partition of my external SDCARD as internal memory, this is likely to solve all my problems and make my phone usable again.

Thanks for all the help, appreciate it.
[Android Q&A, Help & Troubleshooting] kuisma:
You need to edit /init.rc (or init.vendor.rc). To make the edits here stay, you'll need to create a new boot.img to flash your device with.

Have a look at an extract of mine init.<vendor>.rc:

on fs
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
#mount yaffs2 mtd@system /system
#mount yaffs2 mtd@system /system ro remount
# Use below two lines instead of above to run /system from SDcard instead of internal flash
mount ext3 /dev/block/mmcblk0p3 /system
mount ext3 /dev/block/mmcblk0p3 /system ro remount
#mount yaffs2 mtd@userdata /data nosuid nodev
mount ext3 /dev/block/mmcblk0p4 /data nosuid nodev
mount yaffs2 mtd@cache /cache nosuid nodev

Compare the lines I've commented out with the others. Here both /data and /system resides on the SDcard, you only need to care about /data. Also remember your device nodes may not be named "mmcblk0p3" etc.

But you'll need to make those changes in the initramfs in your flashed boot.img to make them stay.
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
Thanks for the reply man, mind telling me the how I can go about doing this?, I've got the ROM I flashed via CWM here with me, I could send it over to you if that would make things easier for you.

EDIT: would pulling init.rc via ADB, making the changes and pushing it back do the trick? or do I have to go for the boot.img? In case it's the latter, I'm going to need help doing it.
[Android Q&A, Help & Troubleshooting] kuisma:
You'll find a good tutorial about how to work with boot images here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

If you already got the ROM in a file, this should be easy! Got ADB and FASTBOOT as well?
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
I'm not sure I've got FASTBOOT but I've definitely got ADB and I've also got the ROM. Would pulling init.rc via ADB, making the changes and pushing it back do the trick? or do I have to go for the boot.img?.
[Android Q&A, Help & Troubleshooting] kuisma:
No. You need to reboot the phone for the init.rc script to execute, and once you reboot the phone, the root file system is overwritten by the flashed image ... Catch 22.

You'll NEED to create a new boot.img with a new initramfs containing your changes.
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
Shucks, this explains why it didn't work. Alright, so I extract boot.img from the rom, follow the tutorial.What is it that I have to edit again? "/init.rc" or "init.<vendor>.rc"?.

Thanks for the help man, appreciate it.

EDIT: Looks like the tutorial is meant for Linux, I'm currently on Windows. I might be asking for a lot here but is there any chance I could get you to do it for me?
[Android Q&A, Help & Troubleshooting] kuisma:
Of course, MIUI may have some boot hooks you could use to re-mount /data after boot. I know nothing about that ROM. Also keep in mind that each time you update the ROM, you have to remake this edit.

Also, no idea what MIUI calls its init.rc, you'll just have to see for yourself. If you've got the mount commands in init.rc, fine. Else look elsewhere.

A good first step would to make sure you really are able to flash a new boot.img. Download fastboot and verify your device understands it. Else you have to use some proprietary flash program, and I'm not familiar with Samsungs bootloaders at all. Ask in the Samsung forum if so.
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
Looks like the tutorial is meant for Linux, I'm currently on Windows. I might be asking for a lot here but is there any chance I could get you to do it for me?. ADB and I do see the file init.rc and I also see the mount commands as well. I used adb shell to run the command you sent over with a few edits for second partition and it does mount but as you said, it all goes away after reboot.
[Android Q&A, Help & Troubleshooting] kuisma:
Hmm... are you even able to create a second ext3 partition on the SDcard using Windos..?
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
haha, I used CWM to create the partitions initially, but then I used a software called MiniTool, works well. Can I get you to to do it?
[Android Q&A, Help & Troubleshooting] kuisma:
The ROM you are using requires an ext4 partition as partition #3 of the SDcard. This is mounted as /data. Repartition your SDcard #1 as FAT, #2 whatever, and #3 as ext4, and everything will work as intended. :victory:

I guess you've missed this in the ROM documentation ... ;)
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
Wah~ really?, I'll try that and get back here with the results. Thanks a lot!.

EDIT: Is it FAT or FAT32?
[Android Q&A, Help & Troubleshooting] kuisma:
FAT32.
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
Tried but didn't work out. I made three partitions, all primary - #1 FAT32, #2 FAT32, #3 EXT4. Plugged the SDCARD in and the external memory was detected as usual, but not the internal memory.

I tried changing the time, it was reset back after reboot.

After that I left the SDCARD as is and flashed the ROM again and now, neither the internal nor the external memory are detected. This is probably because the "vold.fstab" which was edited by me, was overwritten on re flashing.

I'm at a dead end, any ideas?
[Android Q&A, Help & Troubleshooting] kuisma:
Attach an output of "df", "mount", the file "/init.latona.rc" and "/etc/vold.fstab" here, and I'll have a look at it. Hmm... include the output of "dmesg" as well, to be on the safe side.
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
What bugs me is the fact that the external SD is not detected, from what little knowledge I have, external SD is unrelated to the internal SD which I currently have problems with, meaning it should be detected without a problem.

Also I have to add, CWM doesn't detect my external SD right away, when I go to recovery and go over to "Choose zip from sdcard" it says "E:Can't mount /sdcard/". The solution I've found coincidentally is to go to "mounts & storage", mount "/emmc", pull the SDCARD out plug it in again and then "mount /sdcard" this works perfectly and I'm able to flash roms from the sdcard.
[Android Q&A, Help & Troubleshooting] kuisma:
One problem at a time, please. Attach the files I requsted, so we can determine why /data failes to mount. Looking at your ROM:

$ grep " /data$" init.latona.rc
mount ext4 /dev/block/mmcblk0p3 /data

I want to know why this fails, and I guess the answer is in the dmesg output. And please before I'll get another whiskey. ;)
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
I can't seem to find "/init.latona.rc" everything else you requested I've mailed them over already :)

EDIT: the dmesg output is AFTER I mounted "/sdcard" manually as explained in my previous post.
[Android Q&A, Help & Troubleshooting] kuisma:
The files you mailed me does not correspond to the ROM you refereed.

The /etc/fstab show that /data is mounted as an rfs file system, not ext4. So either format partition #3 on the sdcard as rfs (Samsung proprietary), or edit /etc/fstab and change "rfs" to "ext4". I'd prefer the later, assuming your kernel supports ext4. Else use ext3.

/dev/block/mmcblk0p3 /data rfs rw

But you can't have flashed the ROM you told me you did. It excepted an ext4 file system ...
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
I tried mounting as ext4 via shell before, does that modify vold?, in any case, this is definitely the rom I flashed.

/dev/block/mmcblk0p3 /data rfs rw

I've tried replacing rfs with both ext3 and ext4 (after formatting the partition accordingly), neither worked. Could it be because the external SD is not detected?. it says the external SD is unavailable in "About Phone", I can fix this by editing "/system/etc/vold.fstab", should I try that?.
[Android Q&A, Help & Troubleshooting] kuisma:
Please, one problem at a time. Lets begin with /data since it's the most important.

If you try "mount -t ext4 /dev/block/mmcblk0p3 /data" at the shell, what does it do?

vold only handles removable devices, such as the sdcard first fat32 partition. Leave it for now.
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
failed: Invalid argument

EDIT: After that I manually attached "/sdcard" as I described before, and then ran the command, the output was "No such file or directory"
[Android Q&A, Help & Troubleshooting] kuisma:
Do a "cat /proc/filesystems". Maybe your kernel doesn't handle ext4.
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
Ran the command - it supports ext2,3 and 4
[Android Q&A, Help & Troubleshooting] kuisma:
Does /data exists, and is an empty directory?

Does /dev/block/mmcblk0p3 exists?

After the mount command, what does "dmesg" say?

Time to sleep here, we'll continue tomorrow.
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
/data exists and is an empty directory.

/dev/block/mmcblk0p3 exists.

This is what dmesg shows after trying to mount using "mount -t ext3 /dev/block/mmcblk0p3 /data":

http://imageshack.us/photo/my-images/641/dmesgaftermount.png/

EDIT: I've run e2fsck on the 3rd partition and now it seems to mount when I run the command from recovery. dmesg says:

EXT4-fs (mmcblk0p3): recovery complete
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. 0pts: <null>

But it still doesn't mount automatically when I boot into android, so I booted into android, enabled USB debugging and ran the same command again. dmesg gives the same output as above but the phone just hangs.
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
EDIT 2: After some quick research I found out that the above error was because of some problem with the filesystem which can be fixed by running e2fsck. I converted the filesystem from ext3 to ext4, ran e2fsck and tried mounting again and here's "dmesg" and "mount" outputs:

I'm guessing this means it was mounted successfully, same output in both recovery mode and using USB debugging, but the phone hangs when the command is run via USB debugging, same output in both mount and dmesg.

I'm trying to provide as much information as possible thinking it might make the process less difficult for you considering you don't have the phone with you, tell me when it's too much.
[Android Q&A, Help & Troubleshooting] kuisma:
Information is good. The problem here is that it's somewhat inconsistent.

The /etc/fstab you showd me with the rfs mount does not exist in your ROM. I don't know where you'd got it, but it shouldn't be there. Lets forget this file.

The df output shows sdcard mounted on mmcblk1p1, but this device node does not even exists. df must be broken in this rom (e.g. using cached data, probably from another phone!). Lets forget about df as well.

Booting in recovery mode, and /data is not supposed to be mounted. You have to tell when you're using recovery mode, and when booting normally. The file /rc.latona.rc only exists after a normal boot, and it's here /data is mounted.

Don't run e2fsck here, create an entire new ext4 file system instead.

Ok, try this.

Unzip your ROM image at your Windos machine, and push the file "make_ext4fs" to your phone using recovery mode. Then issue the following on your phone:

# chmod 755 make_ext4fs

# umount /data

# ./make_ext4 -b 4096 -g 32768 -i 8192 -I 256 -a /data /dev/block/mmcblk0p3

# sync

Shutdown the phone, reboot in normal mode. Then show me the output of the commands "dmesg", "mount" and the contents of the file "/boot.txt" and any messages the above commands resulted in.
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
mmcblk1p3 came up after I edited "vold.fstab" to detect my external SD, it's all back to normal now and I'm back to mmcblk0p3.

Didn't make any changes to the partitions after I ran e2fsck -> Issued the commands in adb shell and:

the command "unmount" wasn't found, but I made sure that "/data" was unmounted.

in the 3rd command, I assumed it was "./make_ext4fs", and running this issued the error "error: make_ext4fs: failed to reserve first 10 nodes"

dmesg is not updated with anything new but I spotted this:

Just curious, as of now I can run "mount -t ext4 /dev/block/mmcblk0p3 /data" and mount mmcblk0p3 to /data successfully, confirmed by df. Is this irrelevant to what we want to do?

This might be irrelevant information but, I said before that I can't mount "/sdcard" in recovery through "Mounts & storage", I have to mount emmc -> remove sdcard from slot -> reinsert -> and then "mount /sdcard". Reinserting the sdcard at this stage apparently changes it from "mmcblk0" to "mmcblk1" (confirmed in df) and I'm able to mount "/sdcard".
[Android Q&A, Help & Troubleshooting] kuisma:
Too many unknowns now.

I suggest you revert back to stock ROM and continues from there. Non-working /data was caused by the ROM not succeeding in mounting it as an SDcard partition, not a bad NAND memory.
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
I would if I could, I flashed MIUI because it's the only ROM that would boot up. All the rest, including stock roms give out errors on first boot and would go into bootloop.

Here's what I go through with stock roms (This was before I partitioned the external SD into 3 partitions btw):

http://xdaforums.com/showthread.php?t=1726198
[Android Q&A, Help & Troubleshooting] kuisma:
Ok, wish I had read that earlier. :)

I believe I'm understanding now. /data is supposed to reside on the internal MMC memory, but this is so broken, the kernel can not even find the device. This disk is supposed to have device id mmcblk0, and the SDcard mmcblk1. But in your phone, the internal mmc device is gone, making the SDcard the first MMC device, i.e. mmcblk0, and not mmcblk1 it's supposed to be. This is why I told you your ROM placed /data on the SDcard. It's only doing this, because it believes it's the internal MMC memory, and the stock ROM would do the same.

Still, this is kind of good.

You may fake the internal MMC using the SDcard. This is basically what we have been doing so far, unintentionally. The first partition FAT32, the third partition EXT4. Unfortunately I have no clue what so ever the second partition should be.

Well, try installing stock ROM with your 3-partition-SDcard now. The first partition already is FAT32 as it supposed to be. Hopefully will the stock installation format the third partition, since I guess you have problem formatting it with Samsungs proprietary rfs filesystem. It's worth a try.

Edit: Make the three partitions quite generous to begin with, but only format the first one, using FAT32. Since we don't really know what partition #2 is for, just let it be there and we'll see if something claims it, and if so, it's must not be too small for whatever its purpose is.
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
Flashed back to stock, the phone's indeed working, I can install apps and all that good stuff. But what I now can't do is use the camera and music app.

The ext4 partition is clearly detected as "Device Memory" but there's no SD card or USB storage under "About Phone".

Next step?
[Android Q&A, Help & Troubleshooting] kuisma:
Oh, I didn't prepare you for the next step, since I didn't think this would work so easy. :)

Let me see a "mount" and "df" output, please.
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
I think I figured it out. I'm sure this isn't the best way to go about it, but since the 3rd partition was already attached I had the other two to get attached. I changed the vold.fstab:

Internel sdcard
dev_mount sdcard /mnt/sdcard 1 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1

External sdcard
dev_mount sdcard1 /mnt/sdcard/external_sd 2 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1

And it worked, now, when the phone's connected to the PC, I see two drives. Is there anything I can do better here?.

EDIT:I can install stuff, use the camera and all that stuff but I still see the SD card as "Unavailable" at "About Phone". I've got 11GB of USB storage and 2GB of Device Memory but AD card is unavailable.

This is overkill but is there a way to fix that?, it's probably something to do with vold.fstab

Thanks for your help so far man, I couldn't possibly have done it without your help and the stuff I learned in this thread
[Android Q&A, Help & Troubleshooting] kuisma:
Yes, this is one solution. I really don't see why the phone requires the "external" SDcard, so there may be a problem with mounting the "internal" mmc, hence me wanting to see the "mount" and "df". Surely it should be possible using the camera even without the SDcard, in stock ROM using a non-defect phone..?

But if it works, and you are happy - keep up the good work!

---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------

Nah. I don't think it's vold, but the "About the phone"-activity looking at the now days non-existent mmcblk1. Cosmetics, I wouldn't care. May be a good thing, you don't want the phone to "eject" the SDcard, unmounting not only /sdcard but /data as well. :rolleyes:

This may actually be an issue connection the phone as "USB disk" to your computer. Make sure it doesn't unmount /data as well during this. If so, avoid connecting it as USB disk, and use other means of transfer (adb push/pull, ssh/scp, cloud storage etc).

The sizes of your partitions you can of course adjust to you needs, now when you know how all this work.

Quite fun and educational, I would say. But sure there were a few times I thought you were pulling my leg with all the inconsistencies. ;)
[Android Q&A, Help & Troubleshooting] PhantomPhreek:
Haha, I think I'll stick to how it is now. I've got it working and that's all I wanted from the beginning.

I tried plugging in via USB and mounting, it worked well while and after it was removed from the USB. But from past experience, I do know that removing the external SD, as things are right now, while the phone is on would ruin everything.

Thanks for all the help man, you're awesome.