yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Happy2cu:
Im ready to start my fix .....steps would be appreciated?

E:format_volume: rfs format failed on /dev/block/mmcblkOp2

Ca't access to '/system/csc/KOR/system/',

???

How do I direct initial format?
[Captivate Android Development] aigarslv:
I also get this if I do factory reset ;)

format_volume: make_extf4fs failed on /dev/block/mmcblk0p2

error mounting /sdcard/.android_secure!

Here is plain ICS /etc/vold.fstab (I9000)

## Vold 2.0 Generic fstab
## - San Mehat (san@android.com)
##

#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################

dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2

dev_mount emmc /mnt/emmc 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0

Gingerbread stock fstab:

## Vold 2.0 Generic fstab
## - San Mehat (san@android.com)
##

#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################

# sdcard mount for the P1
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
discard = disable
asec = disable
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0

# externel sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
asec = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
#end line ## keep this line
[Captivate Android Development] tsubus:
This fixed it for me (s2, i9100). Thanks!

edit: talked to soon. at every reboot i am back to wiped /data automatically
[Captivate Android Development] aigarslv:
I am sad to hear that. At the moment I am making good progress by editing vold.fatab So far good news is that I was able to fix:

format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
error mounting /sdcard/.android_secure!

These issues mainly occur due to different mount points or Unmounted SD card
[Captivate Android Development] Happy2cu:
I think you have the right idea...how do I write this to adb or a boot file in CWM?
[Captivate Android Development] aigarslv:
Currently I have seen that external sdcard has been in following mount points:

Internal: /mnt/sdcard (label: sdcard) External: /mnt/emmc (label: emmc) - ICS CM9 (mixes up Internal SD card with External SD card)

Internal: /mnt/emmc (label: emmc) External: /mnt/sdcard (label: sdcard) ICS CM9 reversal fix

Internal: /mnt/emmc (label: emmc) External: /mnt/emmc/external_sd

Internal: /mnt/sdcard (label: sdcard) External: /mnt/sdcard/external_sd (label: sdcard1)- original Samsung spec. in Gingerbread
[Captivate Android Development] Happy2cu:
that's correct, thats where my ext sd mounts
[Captivate Android Development] aigarslv:
Please provide more details! First of all - what mount points exactly do you have and their labels, secondly on what ROM, and at last phone version.
[Captivate Android Development] Happy2cu:
Install

Dark Knight Rom

Samsung Captivate I897

16GB Samsung MSD Class 10

Right now I have EMMC Reverse set up, Im doing a clean install as we speak, will let you know what happensd

---------- Post added at 11:48 AM ---------- Previous post was at 11:42 AM ----------

Dark Knight ROm

It said:

Encryption Unsuccesful?
[Captivate Android Development] aigarslv:
I still from time to time get Encryption error - now I am more keen on thinking that it is some form of timeout... If data is not received in specific time - phone thinks that partition is encrypted and tries to decrypt it and of course - fails.
[Captivate Android Development] Demetris:
Am finishing up the uploads :)

Wait for instructions

---------- Post added at 10:35 PM ---------- Previous post was at 10:30 PM ----------

This probably needs it own space but anyway am posting it here.

http://www.filedropper.com/galaxytab

http://www.crocko.com/08C20A1D1B8144D0AC0ABBDABEB41C3D/Galaxy_TAB.rar

1st upload

Be back ;)

http://www.crocko.com/1707EC910B404989B2C8B629D726A846/Fascinate.rar

http://www.sendspace.com/file/t6xgsh

2nd Upload finished.

Instructions comming:

1st make a good back up to your efs folder.

Flash Gb Samsung rom.

Then try 1st upload with pit and file on pda, check repartition.

If it passes odin you are ok to go, if not try 2nd upload.

Time is short i be back for more... enjoy
[Captivate Android Development] minotaur507:
Tried both Fascinate and Galaxy Tab files... got NAND write failures on both. Hopefully this will work for someone else...
[Captivate Android Development] Happy2cu:
Trying now...

---------- Post added at 09:15 PM ---------- Previous post was at 08:16 PM ----------

I didnt get past Movinand...
[Captivate Android Development] parkerdjohnson:
got this for the tab files:

<OSM> All threads completed. (succeed 0 / failed 0)

<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Set PIT file..

<ID:0/004> DO NOT TURN OFF TARGET!!

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> movinand.mst

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/004> Removed!!

<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Set PIT file..

<ID:0/004> DO NOT TURN OFF TARGET!!

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> movinand.mst

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

And got this for the Fascinate files:

<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Set PIT file..

<ID:0/004> DO NOT TURN OFF TARGET!!

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> movinand.bin

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

The tab movinand file seemed to progress all the way before it failed, whereas the fascinate .bin failed at about 30%
[Captivate Android Development] ctrclckws:
Same results as parkerdjohnson.

Had just installed Dark Knight 3.

Seemed to be running nicely, might have rebooted once or twice. Then encryption unsuccessful.

Phone is 1010 refurb build.

Managed to get it to boot into KF1 Stock, Internal SD does not mount, give no option to mount in settings / SD Storage.

Attempted EEPROM reset code mentioned earlier in this thread, no effect.

CWM will not mount \data or \sdcard either.
[Captivate Android Development] Demetris:
I remember typing that you must be on a samsung GB Rom.
[Captivate Android Development] swayjd:
which exact rom did you use this with? can you link it?
[Captivate Android Development] Happy2cu:
Sasmsung GB Rom

I received the same message as (parkerdjohnson) above, with

2.3.4 and 2.3.5

UCKH3

KI2

UCKJ3

UCKK4

UCKK1
[Captivate Android Development] Demetris:
I have a vibrant so i use my own 2.3 with mix and match components from fascinate t959D leak 2.3 one.

Vibrant dont have a GB release :)
[Captivate Android Development] Happy2cu:
I think you should use Eclair 2.1 with master clear?
[Captivate Android Development] ctrclckws:
The ROM I worked with was the ODIN 1-click to stock for KF1, rooted, found in the stickie in the forum. That is a Samsung GB ROM
[Captivate Android Development] swayjd:
So you never actually used your fix on a captivate? what led you to believe this would work for us?

kinda bummed out that we don't have a fix after all.
[Captivate Android Development] Demetris:
You are Joking right?

Movinand is a movinand and its the same on fascinate,captivate,vibrant,galaxys,galaxytab.

After all the files i posted are NOT made for vibrant either :)
[Captivate Android Development] Wdustin1:
So has anybody had luck getting this fix to work?
[Captivate Android Development] swayjd:
You are missing the point. No one seems to make it work.
[Captivate Android Development] jmtheiss:
*yet.

Although the solution hasn't been quite worked out yet, it's still in process. I am happy to see demetris_l working to come up with a solution, even if it's not 100% tailored to the Captivate.

No personal attack intended, swayjd - I'm just encouraging you to be patient, as the fact that nobody's had any luck getting this to work yet is just part of the testing process.

I fully believe that we'll get this figured out, and if the answer is ultimately that it can't be fixed, it's better than not knowing.
[Captivate Android Development] Demetris:
Well spoken! 2TU
[Captivate Android Development] swayjd:
wait, don't get me wrong,

I'm not diminishing his efforts at fixing this for the rest of us.

I am just stating a fact that, for the better part of the conversation, he seems to be neglecting. Absolutely no harm intended. That post above shows that he is in a very defensive posture that, by no means, I wished to provoke.
[Captivate Android Development] parkerdjohnson:
Im using the reverse Emmc fix, and am still plagued with inability to install anything! any fix? simplystock 2.0, corn 7.0a, ext4.

Thanks!

Sent from my dingdong
[Captivate Android Development] minotaur507:
Maybe I'm just really confused or just plain ignorant of the inner workings of these ROMs, but I don't quite understand how it is possible to get a ROM working off of an external SD card using the instructions given in the OP.

I can get into CWM and I execute the partition command. I get no errors, but clearly for me the internal SDcard is not accessible so the partition command does nothing.

When I try to execute step #7, it goes through the ROM installation without any obvious errors, but since the internal sdcard seems to be inaccessible the writes don't seem to actually happen (or do they, and I just can't see things properly?). Of course the ROM is not programmed to write to the external SD, so there's really no way to force it there that I know...the reverse EMMC fix would necessitate having access to the internal sdcard memory, no?

Am I missing something, or is my completely inaccessible internal SD a different problem to which the instructions in the OP don't apply?

Any help is appreciated...willing to try anything and do whatever I can to help fix this problem at this point.
[Captivate Android Development] Happy2cu:
Getting your phone to Run a ROM after Encryption Worked for Me :)

Things needed:

Device fully charged,

microsd card,

stock rom with CWM Kernel built in-

I897UCKH3 Android 2.3.4 Gingerbread Without BLhttp://xdaforums.com/showthread.php?t=1269524

With BLhttp://www.mediafire.com/?05nemq5yyn5fuqf

I897UCKI2 Android 2.3.5 Gingerbread

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

Instal SD Card.Put your device in Download Mode or use a JIG!http://samsungcaptivate.wikia.com/wiki/Putting_the_Phone_into_Download_Mode

Then Install Stock Rom, Sometimes you will get a bootloop just remove battery and usb cable.

Press Volume Up/Down and Power Button at the same Time( wait for the screen to flash 3 times until you see the logo on the screen and let your buttons go).At this point you should be in CWM Kernel! If not try the steps again.

Now, scroll to : wipe data/factory reset (click and wait), wipe cache partition(click and wait),go to advanced Wipe Dalvik Cache (click and wait), and go to Partition SD Card and partition to at least 2GB(click and wait)!

After these steps are done go to mounts and storage scroll to mount USB storage plug your USB cable and open file and stick your Zipped ROM and Kernel onto you file folder + EMMC Reverse Fix.ziphttp://www.mediafire.com/?qfub7i9afj8f17fIMPORTANT

UnMount*Go Back to install zip from sd card and load your ROM.Reboot.

After your ROM is loaded you back to CWM: and go to install zip from sd card and load your EMMC file! Reboot.. Go to your settings and storage and you should be all set. Some times some Modded RoMs will need that EMMC file to be loaded again. Worked fro me.. try it.
[Captivate Android Development] minotaur507:
I think I answered my own question...the EMMC fix changes files in the system partition, which should be fine... I think I understand now...
[Captivate Android Development] Wdustin1:
Excited to see this worked for somebody. Anyone else have any luck
[Captivate Android Development] bimbim18:
+1 here as well thanks
[Captivate Android Development] jeff.leonard:
Encryption Unsuccessful

I also got hit with this problem & think this guide should be stickied with a title something like "Warning: All ICS based ROM Users Read This Now!". The first post should summarize the problem.

I had been running Dark Knight 3 for about two weeks without any trouble. I loaded the Glitch 14B6 kernel and the next day it froze! Upon reboot it hung at the CM graphic; the second reboot I was greeted by "Encryption Unsuccessful". I had seen the thread in the development index but hadn't looked at it because I figured it was related to encrypting data, not the end of your phone as you know it. I tried for two days to fix it, then finally gave up and cannibalized the board out of my wife's old phone with a cracked screen. I am not running ICS on it now! I hope to keep it going until the SGS III comes out or at least the One X if I am forced to "settle".

I'm curious how many people had recently swapped kernels, what kernel it was, and how long before this happened. So for me it was Glitch 14B6 and about 14 hours since the swap.

The only other change I had made was reloading all my music, pics, & videos onto the internal SD. Did anyone else make major changes to the data on the internal SD just prior?

The issue could be completely random as many have suggested. I haven't seen much discussion about what may have been the cause. Maybe we will stumble on a cause, then can find someone that can fix it.

**Again please sticky this thread with an updated title & first post summary**
[Captivate Android Development] Nirmalspeed:
i had this problem on my vibrant and its stuck in the stock recovery screen now from eugene's unbrickable rom.... any ideas on how to get CWM working?
[Captivate Android Development] Demetris:
Sure,

Flash jfd put in an sd card with cwm in update zip.

Get into samsung recovery and click that update from internal sd card.

2-3 time and you are in cwm.

Put also a custom rom in it before and use that to update to it.
[Captivate Android Development] minotaur507:
I just want to extend a very big Thank You to cgugino and Happy2CU. Following the posted instructions, you can bring your cappy back to life and make it somewhat functional again.

I would also like to support the idea of making this thread a sticky, especially as heads-up for other users wishing to adopt Captivate ICS...

Now to figure out how to get that sdcard filesystem back...
[Captivate Android Development] minotaur507:
I found this today, and thought it might be of some use to those with more encryption experience than I...

https://github.com/guardianproject/LUKS/wiki

https://github.com/guardianproject/LUKS/tree/master/app/boot/luksunlock
[Captivate Android Development] Demetris:
I laugh at this:

""The trouble you're most likely going to have is with MTD on the data partition, although an MMC might **** up as well."

And this:

"Probably should make a script run during shutdown to cleanly "luksClose" the encrypted partition and then umount them. Not doing this is probably very crazy "
[Captivate Android Development] Happy2cu:
Encryption

Experiment: I re installed ICS today and encrypted the device from settings, after reboot, the device "ASKED FOR A PASSWORD TO DECRY PT THE INTERNAL DRIVE"...ANY IDEAS?
[Captivate Android Development] Nirmalspeed:
you can flash update.zip from an external sd card too? didnt know that.... thanks!

EDIT: i cannot select any option from eugene's recovery. any ideas on how to do that?
[Captivate Android Development] Demetris:
Go to Vibrant q&a, i think i said to you flash jfd.
[Captivate Android Development] amtrakcn:
Among all the recoveries I tried, only boog's work.
[Captivate Android Development] DaNaRkI:
This is supposed to be what ever is your normal screen unlock password. Also, it is supposed to not let you encrypt unless said password is already present. At least according to how Google expects the whole thing to work...
[Captivate Android Development] bballer182:
I wonder if 4.0.4 (IMM30B) is going to fix this problem. There is already a ROM out with 4.0.4 and I guess CM9 and AOKP are working on merging the changes. Maybe something in 4.0.4 will prevent the encryption issue.
[Captivate Android Development] jeff.leonard:
I was running Dark Knight 3 which was based on 4.0.4 when I got hit; so no such luck so far.
[Captivate Android Development] bballer182:
Damn
[Captivate Android Development] cthulhu.hpl:
So, after quite some time spent trying to solve this (and seemingly bricking my SGS till I found boog's GB) I'm back to where the first post of this thread will take me - meaning I'm able to boot my SGS from my external MMC problem is...performance is dismal, really cant practically use the phone, since each command takes seconds to perform (as in "I'm waiting for this prompt.........timeout!"

I know that either I have a hardware fck'd internal MMC, or it's "just" some kind of corruption that stopped me from booting etc etc etc

So, I'm kind of limited, but is there any way where we can mount raw the internal MMC, do a diskcheck, then repartition? I don't really care if I loose whatever is in there (it's probably lost at this point, anyway).

The phone is rooted, and I could theoretically run the commands from the terminal.

Any clues?
[Captivate Android Development] Happy2cu:
OUT of LUCK

Everyone reading this post, is out of luck if your device internal drive is encrypted. I have been researching for over a month with no answers. You either have to buy a new board or use a fast SD card. Its not just these device but anyone who tried to run ICS on a non ICS device.

CM9 site has no real answers for us but it did work on a XOOM and a Tab device.

Just wait for someone to find a way around the encryption before your device is obsolete...thats all i have.
[Captivate Android Development] jmtheiss:
I could be mistaken (and perhaps b-eock will chime in), but I believe that Dark Knight was a 4.0.4 build done outside of the official source that was just recently released. If I'm correct, there's still a possibility that something within that may have corrected this issue.

As of right now, I'm just waiting for someone to release an ICS rom with a custom kernel that disables the encryption altogether. I'd gladly trade encryption capability for a guaranteed functionality.
[Captivate Android Development] jeff.leonard:
Before I posted that reply I looked into Dark Knight 4 (I was on version 3); there is nothing in the changelog to suggest there is any sort of fix related to the encryption problem.

I also would love to see encryption disabled!

My gut tells me it is kernel related more than the actual ROM causing this. I would like to hear from more people about which kernel they were on and if they had recently changed it.
[Captivate Android Development] jmtheiss:
Interesting - I'm not sure if it would have been picked up in the change log for two reasons: it's a change done at the source code level (as opposed to the build level), and it's a relatively uncommon occurrence.

I just asked sixstringsg over in the Icy Glitch thread, and he's saying that this issue is not a kernel issue, as encryption isn't handled by the kernel, but rather, by the ROM.
[Captivate Android Development] minotaur507:
According to this from google, it is implemented in the kernel...the below article is from Honeycomb, but I can't imagine it changed all that much in ICS...

http://source.android.com/tech/encryption/android_crypto_implementation.html
[Captivate Android Development] jeff.leonard:
I just saw the sixstringsg comment too; blows my theory about it being kernel related out of the water. I think he would be someone that would know....

I have seen several people commenting that it is device related; I think it will eventually happen to everyone running ICS until it is fixed. My phone was running for two weeks on ICS before it happened. Therefore I don't think it will remain an uncommon occurrence!

I hope you are right and it is fixed but I am not willing to try on my second captivate....YET!
[Captivate Android Development] jmtheiss:
Reading a little further up in that article, I came across this:

Not sure if it matters, but as this is all open source, is the idea of rebuilding vold to use these functions possible?

Also, this article provided some insight as to why pulling the battery prior to hitting "reset device" matters:

If I'm reading that right, it looks like the "reset device" screen might be opening the door for Android to finish its encryption mess:

So... is there a way to tell init to knock it off and stop assuming that?

I can't say I fully understand all of this, but reading that document does appear to leave open some options for getting around all of this.
[Captivate Android Development] bballer182:
So here is the question I pose. What is stopping us (captivate users) from turning our phones into nexus s (i9020a)s? Our hardware is identical isnt it? The Nexus S is native to ICS and they don't have encryption problems... And I see they are now on IMM76D.
[Captivate Android Development] aigarslv:
For me the problem was hardware related... Problem with internal memory card. Only way to fix this for me is to make Android use external SD card instead of Internal SD card.

Good indicator of hardware problem is that Odin stays at Set partition when you try to flash ROM with repartitioning using .pit file.
[Captivate Android Development] stayintwisted:
but how about for those of us whose phones are not encrypted currently,,would it be possible or reasonable to make our phones think they are i9020's and prevent the encryption risk? or would this even work?
[Captivate Android Development] helikido:
Just a big wow on #3. Suck a rule doesn't exist as questions like the ones he posted are crucial to development. So stfu if u don't know what your talking about...:mad: people like u tend to piss me off these days..
[Captivate Android Development] RootTheMachine:
They're not exactly identical... They just have the same core specifications. You can't just simply slap on a Nexus ROM and kernel and expect the phone to work. I suppose it would be possible to run nexus bootloaders (having UBM of course), but getting it all to work would take work. Even if we could do that, I don't think it would rid us of the problem. Dark Knight is a port straight from galaxy nexus, yet people have still reported this issue. I know I rejected it before, but this almost sounds like a hardware issue with the way ICS is set up. I think we need to investigate more with the Nexus S though; like comparing the way the phone handles init tasks like mounting data.

Sent from my CM9 ICS i897 Captivate
[Captivate Android Development] bballer182:
Yeah, I remember a while back when Adam released the UBM, Connexion was attempting to get nexus firmware and bootloaders going on a captivate but I think that plan got stalled out. I bumped that topic on the UBM thread but no one acknowledged the question... thanks for the reply.
[Captivate Android Development] schwick:
This would be the most HELPFUL post I've read here in XDA. :rolleyes:

OP, thanks for this guide. If that encryption crap popped up in my phone now I know what to do.
[Captivate Android Development] Happy2cu:
follow post 221.