yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] matmanchu5:
If you have the same issue I do Odin will not work because it needs a working data partition or it will just stop when trying to flash it. I used Odin to flash a kernel (semaphore). Then partition SD and move ROM to phone via cwm USB storage mode. The only ROM that I could get to flash was the last two part ROM slimrom made before switching to the one zip cwmflash file. You also have to flash gapps before first boot or it will not boot. That's how I did it and it worked but I still have no efs folder, and the only way I know how to get it back is to Odin back to stock:mad:

Sent from my SGH-I897
[Captivate Android Development] do_long_ky:
Hi,

I've followed the instruction at first page of this thread, but not working. It seems not formatting my micro SD card (it is 8GB one)

My phone can't connect to Odin via Download mode, but it CAN connect via Heimdall, so it is in Rom stock UCKK4 2.3.5 now. And Heimdall seemed to install ROM on micro SD card already. But I can't access both internal and external memory, just 1.79GB for data location.

Now I can use my phone to call and SMS normally, but can not use camera, or install some apps requiring SD card.

What I have to do now to use all the amount of micro SD

Hope to hear from you soon. Thank you.
[Captivate Android Development] s0ul_ali:
Had the same issue, tried many 4.1 roms nothing worked. Than I flashed LANIGHT V8.5 from here http://xdaforums.com/showthread.php?t=1867484 follow the instructions given in forum and flashed Semaphore_JB_2.5.0c it worked. Now it's booting normally. Try it and reply.
[Captivate Android Development] sgdva:
Noob question: If I do the encryption at first, can I get this error still? I have read that is because android can't mount /data and assumes it's encrypted but what about if it's encrypted already? I wouldn't mind encrypt and get my pass everytime the device boots to avoid this.
[Captivate Android Development] RootTheMachine:
This issue has nothing to do with actual encryption.
[Captivate Android Development] sgdva:
Meh, I'll have to stick with CM10, OT: but on my device doesn't have the drivers for HW acceleration on JB:crying:.

Though it doesn't worth to get ICS again due to this error.
[Captivate Android Development] matmanchu5:
I would like to say that I was able to get Odin to flash my phone back to stock. Why after trying it like a million times it decided to work I have no idea. It worked with no sdcard inserted and my efs folder survived through flashing cm9 and slim bean 3.0 All is well now but still imei is generic. Isn't there an easy way to fix this ?

Sent from my SGH-I897
[Captivate Android Development] do_long_ky:
Any idea ? Thanks
[Captivate Android Development] raz123:
Seems to be only CM9-based builds (stock CM9, AOKP, Fusion) so far.
[Captivate Android Development] newredness:
Thank you

thank you alot my friend

it's worked finally

taaaaaaaaaaaaaaaaaaanx
[Captivate Android Development] Demetris:
I am in the same boat on a vibrant. AOPK v27 rom did this to me not cm9.

So now what to do next, any thoughts?
[Captivate Android Development] Demetris:
I had a search and all i can say we are sc**ed.

Read here:

http://ecryptfs.sourceforge.net/ecryptfs-faq.html

Especially here:

Q. I forgot my password/lost my key! What can I do to recover my data?

Nothing; you're scr*w*d.

If you have forgotten your passphrase, your only hope is that you chose a weak passphrase in the first place. There is an outside chance that you might be able to perform a successful dictionary attack to recover your passphrase. If you manage to recover your passphrase that way, then you may as well have not been bothering to encrypt your data in the first place, since a malicious attacker could have done the exact same thing to recover your passphrase.

If you selected a strong passphrase or lost your key file, you are completely out of luck. Nobody can help you recover your data.
[Captivate Android Development] DaNaRkI:
Interesting find, but it sounds like this style of encryption is not what google employs. Based on this article and what google says android is using the other form that encrypts whole blocks, eCryptfs sounds as if it can encrypt files individually android is not doing that.

I think google is using dm-crypt, based on the commands mentioned at the android site.
[Captivate Android Development] AdamOutler:
Hey.. Have you guys tried this?

WARNING: this will totally format SDCard, Data, Cache and everything else non-critical to booting.

Enter in dialer after you get the device running: *2767*3855#
[Captivate Android Development] Demetris:
Is encrypting a whole filesystem at once aka /data partition

---------- Post added at 10:26 PM ---------- Previous post was at 10:24 PM ----------

Thanks for responding so fast but it cant format something is not there.

The os cant see the nand /data partition, cant even see the internal sdcard.

Just found out that that android fallen robot with red triangle is the build in recovery implemented into OS.

Nexus phones have it.

And when there they press Vol up or power to get them inside recovery and then are able to reset phone.

So its a feature half done on our roms.
[Captivate Android Development] AdamOutler:
That should be irrelevant. Get into download mode, flash with Heimdall One-Click KB2 Rooted version, Use the code.

The device is encrypted, not missing.
[Captivate Android Development] Demetris:
*2767*3855# -> Full EEPROM Reset

Nice!

Problem is am on Vibrant and we cant boot into Samsung rom in anyway.

May I try the captivate one?, removing the bootloaders before of course.

Thanks adam

P.s

Any Captivate user able to recover after trying this please post here so others will follow, thanks.
[Captivate Android Development] raz123:
Adam, I appreciate your insight.

MMC devices go through an internal initialization phase (invisible to any code), which preps them for communication. During that phase, the only useful command that they will respond to is "What's your status?" (eg: are you done initialization?).

The kernel's job is to ask the MMC (using CMD1). If it has [completed initialization], further communication then takes place. If not, the kernel keeps asking the MMC.

In our cases, our MMC device (internal 16Gb moviNAND) never finishes internal initialization. The kernel therefore does not communicate with it beyond that point, and no single piece of data is extracted from the MMC.

AOKP is based on CM9.
[Captivate Android Development] RootTheMachine:
Today I flashed a friend's cappy to CM9, and I got the Encryption Unsuccessful message. Having seen this thread before, I knew not to press reset phone. I tried the advice given by the op, but it didn't work. I did a data wipe and the problem was fixed simply by doing that. That is always my first response to data issues because I have seen a lot of problems getting /data to mount, on my own phone and on the forums in general.
[Captivate Android Development] TRusselo:
i clicked it anyway on ICS to see what happens. nothing everything was fine.
[Captivate Android Development] Slayer_b:
Today I have this issue too, I didn't press Reset, tried to reboot, no effect, wipe data and still no effect. Now i'm unable to boot into any stock rom. /data mount failed message appeared in recovery when I'm trying to wipe it. Internal SD unavailable too....
[Captivate Android Development] DaNaRkI:
hmm... and how do you currently go about unlocking your phone? Well how did you go about unlocking it once ICS was loaded, but before the error came up? (unless some people are getting this right at first boot...?)
[Captivate Android Development] TRusselo:
yes right at first boot, of flashing a new ICS over a different ICS without wiping my user data... i think from what i remember.. it was my dev cappy with a cracked screen so i really dont mind trying things the hard way... lol
[Captivate Android Development] DaNaRkI:
Hmm... That goes along with korockinout13's way to fix it, so what about my other question.
[Captivate Android Development] Demetris:
Here is a logat from booting up the phone, am posting only the interested part.

------- beginning of /dev/log/system

I/Vold ( 115): Vold 2.1 (the revenge) firing up

I/Netd ( 118): Netd 1.0 starting

D/Vold ( 115): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)

D/Vold ( 115): Volume emmc state changing -1 (Initializing) -> 0 (No-Media)

I/ ( 122): ServiceManager: 0x13b0910

W/SystemServer( 187): Device encrypted - only parsing core apps

I/ActivityManager( 187): START {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10000000 cmp=com.android.settings/.CryptKeeper} from pid 0

I/ActivityManager( 187): Start proc com.android.settings for activity com.android.settings/.CryptKeeper: pid=372 uid=1000 gids={1015, 3002, 3001, 3003, 1006}

CryptKeeper( 372): Validating encryption state.

VoldCmdListener( 115): cryptfs cryptocomplete

E/Cryptfs ( 115): Cannot open footer file /efs/userdata_footer

E/Cryptfs ( 115): Error getting crypt footer and key

W/CryptKeeper( 372): Incomplete, or corrupted encryption detected. Prompting user to wipe.

---------- Post added at 05:47 AM ---------- Previous post was at 05:45 AM ----------

E/Cryptfs ( 115): Cannot open footer file /efs/userdata_footer

This is the interesting part.

Maybe pushing that file there will help to continue booting without encryption and we have our sdcard back.
[Captivate Android Development] DaNaRkI:
All this tells us is that your phone did not complete the encryption process. The file your looking at is the identifier that android uses to tell if the encryption was completed. It can't be found because you never told the phone to encrypt.

As far as I can tell that file can only have 1 of 3 states: finished, incomplete, and other/error. It does not exist on a non-encrypted phone because there is no reason for it, under normal boot android can mount all the blocks and continues. Google says they added the step of "make sure the phone is properly encrypted" so it needs that reference file to tell it this.

Of those 3 states the only one that will allow it to boot is if it reports as "completed" which then android will ask for a password. Problem is unless you were using a PIN or password as your regular phone unlock there is none, or we don't know what the "default/built-in" one is.

leaked from my

ICS

- FUSED SGS I897 contaminating you via XDA app.
[Captivate Android Development] RootTheMachine:
Yes, but that would make sense only if the phone was encrypted in the first place. It sounds like most people haven't even touched encryption but still get the message.

The above quote coincides with my suspicions. There are issues backing up /data during nandroid, and every time I restore a nandroid without reflashing CM9, my /data gets corrupted and the phone will no longer get past the CM9 boot animation. Going into recovery, at this point any backup operation will result in "Error: Cant mount /data!" The same happens if I try to format /data. Usually I can get it to mount again by going back and forth between mounting and formatting /data until one of them actually works. So since there are troubles mounting /data sometimes,

So that would be enough to give us the "Encryption Unsuccessful" message on a phone that isn't encrypted. I feel like it isn't a hardware issue, but rather an ICS issue.

I realize I may have just posted a bunch of nonsense, but I feel like there is enough evidence to conclude that there is something funky going on in general with /data in ICS.
[Captivate Android Development] DaNaRkI:
No, it makes sense as is due to how google designed Android to be able to support encryption.

Most of it is indeed an ICS problem, google has only begun on the encryption front. Android currently makes a lot of very bold assumptions, this whole process is rather poorly implemented. Also keep in mind that this is probably the most bare bones, simplistic way to detect and allow for encryption. It's such a "dumb" setup that we are probably over-thinking the solution.

The rest of what you've said is good, and rational. I've not had any such problems getting anything to mount, I don't touch the topic due to my ignorance of it. Most of what I've said hardware wise is the "possible" causes, I don't speculate about software related communication issues because my knowledge base is in hardware.

The only things we know for certain at this point is:

1 Android 3.0 and up will assume that any block/partition it can't mount is encrypted. That Android assumes that the only reason it can't mount is because it IS encrypted, it's not written to consider any other possibility (at this time).

2 That in problem phones the blocks/partitions are not mounting.

3. That because the blocks/partitions are not mounting Linux can't do anything with them nor to them. To Linux a drive/folder/block/partition (any piece of hardware) it can't mount/communicate to, means it does not exist.

There are two separate problems at this point, and two different solutions needed. One for -good- devices that are not communicating. One for getting back the access to an encrypted block/partition.

The goal would be. "Step 1" a fix to try for -good- devices. "Step 2" a way to get back a locked partition. "Step 3" the work around in the OP. As it stands now, the "fix" in the OP is to bypass the hardware using a different memory chip to hold the necessary partitions.

Now to explain one last part, an already encrypted partition is going to give similar "busy" response to the kernel as a "stuck" one. You can fix the stuck one by reboots or "going back and fourth between mounting and formatting." You can't fix an encrypted "locked" one this way because it will never respond until it gets communication from the encryption program, and only the program. It respond as "busy" so that the kernel knows it does exist, but it is waiting for a very specific message from the encryption program.

Note: my hardware based explanation about the memory chip starting to wear and getting "stuck" is still a valid possibility at this point because as I said "multiple attempts can free up the circuit" aka going back and fourth between mount (sending a command and thus a jolt of electricity) and format (sending a command and thus a jolt of electricity).

leaked from my

ICS

- FUSED SGS I897 contaminating you via XDA app.
[Captivate Android Development] s0ul_ali:
Which KERNEL & ROM are you using ?
[Captivate Android Development] do_long_ky:
I've used Heimdall to get the phone back to UCKK4 Rom stock. Kernel, I'm not sure, the kernel seems to be Samsung default or something like that ?
[Captivate Android Development] s0ul_ali:
That's the problem, flash latest Kernel and then try it will work :)
[Captivate Android Development] do_long_ky:
I've tried to enter Recovery mode, and now I even can't visit the ROM as noramal. It only visit Recovery mode directly after turning on (but can not install Zip file from SD card). Using Heimdall to installing UCKK4 but it failed in formatting step (Error: E:format_volume: rfs format failed on /dev/block/mmcblk0p2)

Somebody helps me, please.
[Captivate Android Development] BWolf56:
You have to use a different USB port for Odin as Heimdall installs it's own drivers on the port you use it.

Also, could try to factory reset, go in DL mode and try again to flash stock KK4
[Captivate Android Development] s0ul_ali:
Install Samsung drivers properly before trying Odin..
[Captivate Android Development] surendar1863:
Unable to install apps from Market

Got this phone from a friend after internal sd card corruption with Encryption issue.

Installed Heimdall One click UCKK4 and swapped internal and external sd card as per post #1.

Everything is working fine except i am unable to install apps from .apk files stored in memory card. Phone just restarts.

Apps from Google Market are downloading and when installing phone screen goes blank and i had to remove battery and put it again and

applications not getting installed.

But I am able to install apps through adb command...

Any tweaks in vold.fstab to make installation working??

Thanks.
[Captivate Android Development] s0ul_ali:
It's seems to be ROM issue rather than encryption bug. Try flashing any latest built ROM than try.
[Captivate Android Development] leezrd:
That iswhat I was going to say jb milestone 1 works fine on mine by sixstrings

---------- Post added at 10:47 PM ---------- Previous post was at 10:43 PM ----------

On a note. .. I did replicate encryption error on ex sd card by encrypting it then partially the way through then taking out external sd card... so I think might be from in background encrypting and then unmounting... might be wrong
[Captivate Android Development] do_long_ky:
I already installed it into my computer. Since I can connect it normally before getting EU. I believe it's not the problem with drivers.
[Captivate Android Development] surendar1863:
@ s0ul_ali and leezrd

I tried Slim Bean 3.0.1 JB with Semaphore 2.6.5sc and its working great...

Thanks.
[Captivate Android Development] s0ul_ali:
Can't understand you issue please describe more briefly.
[Captivate Android Development] khan_frd2002:
hi friends eu bug is like the emmc bug of note n7000

anyone want to try note emmc bug fix guide on captivate

here is the link

xdaforums.com/showpost.php?p=26285877&postcount=12
[Captivate Android Development] barch27:
Did anyone manage to successfully get Slim Bean with Semaphore installed on emmc? I get stuck at the Semaphore screen at boot. Tried flashing the EMMC fix but no dice. Step by step instructions would be really nice! Thanks!
[Captivate Android Development] surendar1863:
Installation steps

This is what i did.. I presume u have a ext4 partition already...

1. Flash a stock Rom from the link below via ODIN...

http://xdaforums.com/showthread.php?t=1447303&page=23

(I installed this ->With BLhttp://www.mediafire.com/?05nemq5yyn5fuqf)

2. Root it by flashing Cornkernel v7.06 through odin.

3. Reboot to Recovery.

4. Flash EMMC fix.

5. wipe data/factory reset

6. wipe cache partition

7. Goto -> mounts and storage -> Format System and Wipe Dalvik cache too..

7. Install Semaphore Kernel

8. Install Slim Bean

9. Reboot the phone..

10. To make mass storage work reboot to recovery and Flash EMMC JB fix.

This is what i followed .. Try and see if it works ...
[Captivate Android Development] Demetris:
Someone must try push this to Cm gerrit code if they don't implement it already, so we dont get more EU bug hits happening and save some phones.

Samsung emmc bug fix for all

https://github.com/cozybit/aosp-omap-kernel/commit/cea631bdac53f85cc3bfd720da04f726aae33eaa
[Captivate Android Development] fagnerkof:
This is just for preventing EU bug to happen, right?
[Captivate Android Development] Demetris:
Yeap exactly.
[Captivate Android Development] kamikaze_in:
i am facing the same issue Error mounting SD card

so does this mean that my internal storage will never be recovered?
[Captivate Android Development] gsx-r:
Did you need to Partition SD? I have tried to partition but i don't know to partition the external card or the internal sd. And how to know the partition has been done correctly. The Semaphore kernel is only has one option for partition the SD card and i cannot find the partition for ext card.
[Captivate Android Development] leezrd:
Go to http://xdaforums.com/showthread.php?t=1300843. Get 2.3.5 with blog kernel injected with cwm..flash with ex SD card in... go to partition SD card... after it partitions (it should take about 5 minutesish) you can check and if windows shows 16gig card as like11 gig then it worked.. next reflash that firmware I linked then any ROM u want.. also might want to flash the emmc reverse zip
[Captivate Android Development] gsx-r:
I followed your instruction, but Partition SD took very quick (about a second), i think something wrong here. My ext card still in and with this kernel, when mounting storage i can't acess both sd and ext card although i can see the two drives in pc. My ext card is 8GB. I have formated the ext card but no help.

With latest JB Semaphore kernel i can access to the ext card (certainly the internal sd is still dead) but JB Semaphore doesn't have Partition SD function. My Cappy is being still dead now :(
[Captivate Android Development] surendar1863:
Partition tool for Windows

Put the sd card in memory card reader.

Used MiniTool Partition Wizard - Home Edition (Its free.. can find it on cnet.com).

After making the necessary partitions (ext4 and FAT32). i made 2GB partition for ext4 and rest for FAT32.Both Partition should be primary

partitions.

Click Apply..

will take about 5-10 minutes.

After Partitioning remove and insert the memory card reader to PC. It will show only FAT32 partition with its corresponding size.

All other steps i mentioned before was done only after partitioning by the above method.

Hope it helps u.
[Captivate Android Development] leezrd:
Any luck on recovery SD card yet?
[Captivate Android Development] maoten:
i successfully made it working following the steps, am i able to update to CM10 now?
[Captivate Android Development] tquang620:
Plz help me, This is to my topic http://xdaforums.com/showthread.php?p=36222842#post36222842

I have a big question here, If I encounter this issue, is that my internal memory gone forever? And I must use a SD to make my phone working?

Thanks so much for your help
[Captivate Android Development] RootTheMachine:
Sounds like you flashed JB, so it's not the same issue.
[Captivate Android Development] leezrd:
I got encryption on jb
[Captivate Android Development] bimbim18:
I got the encryption unsuccessful thing a long time ago (last march??) and after the emmc fix (repartitioned SD to 2G, installed ROM on SD etc.) and have been running SLIM ICS 2.8 on it just fine since. last week most of my apps started crashing sporatically and it eventually just wouldnt boot past the ROM bootup screen. after trying a few things I just decided to flash SLIM ICS 2.8 again and it worked fine for a day but died again (won't boot past SLIM splash screen. Flashing the ROM again doesn't seem to help anymore. how should I proceed to troubleshoot? I would like to salvage this phone for a while longer (waiting for Galaxy 4 :)
[Captivate Android Development] bimbim18:
I got my EMMC to work too (before I read the last few pages.

Out of frustration I just wiped my phone after it not working for a week. wiped all caches, reformatted with 2gb partition installed an old SLIMICS2.8 I had on my desktop. I was so happy to see my EMMC finally working after it not working for a year. right now running the new Slim-I897-4.2.1.Beta.2-OFFICIAL

but I have no browser or market.
[Captivate Android Development] matmanchu5:
Yes it is gone forever but still you can make phone fully functioning. Just partition your removable SD card on your PC or with corn kernel via Odin (easy) Then with partitioned sdcard inserted, flash a stock ROM one-click (flash boot loaders if not running at least gb) (this will ensure your imei is intact). Then reflash corn kernel w/ Odin (to regain recovery). Next you can use three button combo to access recovery and flash a rom making sure to follow all install instructions for the ROM you want.

You must know what files go where to flash a kernel with Odin (kernels go in the PDA slot and must be a .tar file and leave reboot unchecked so you can unplug, remove battery, and use three button combo(vol+&vol-&then power hold until logo) to get to recovery!)

Sent from my SGH-I897

---------- Post added at 08:58 PM ---------- Previous post was at 08:57 PM ----------

Last post in response to this post

Sent from my SGH-I897
[Captivate Android Development] Demetris:
Something interesting came up :D

https://github.com/glewarne/Note2Co...mmit/b2f4aa21c39c3eb4570865aed6899192b2f2659a
[Captivate Android Development] minhchick:
my captivate had the same problem here.

but I can't mount SD card
[Captivate Android Development] ReDaved:
yikes!!!

Interesting, or scary

not reading code very well, but now owning a Note2

what the heck does that mean?!!?