yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mr_psycho:
Yes. This appears to be a Google (G1, Nexus, etc) thing. Samsung Galaxy S doesn't support "FastBoot". Instead, we have "Download Mode".

How we go about this might be decided by careful examination of an external micro sd card's partition after it has been hit with the bug.

If we pull apart the boot.img and separate the kernel from the ramdisk and recovery, we might be able to see if there are significant changes within the ramdisks (and/or kernel config) that might help to explain this anomaly.

Also, the bug in recovery that broke Nandroids in some kernels was supposedly traced back to using the FIOS scheduler as the default.

If the phone is in Download mode, I think internal sd card mounting is no-longer a requirement. That said, the --movinand option is there for different phones, I believe. Galaxy S uses a OneNAND chip, so maybe exploring methods to interface with OneNAND STL devices would be useful.

The PIT shows that the Vibrant has the following valid partitions:

IBL+PBL

PIT

EFS

SBL

SBL2

PARAM

KERNEL

RECOVERY

FACTORYFS

DBDATAFS

CACHE

MODEM

So, unfortunately, no MOVINAND partition.

Were you able to make an image of the external SD card before reformating it? Or where you able to examine the card at all to check the partition/file system integrity? We are all curious to look at an external card that had the problem, to see if it could shed a bit more light on what the state of the internal sd card is in.

Thanks,

MP
[Captivate Android Development] D J Richert:
Encryption Unsuccessful message

I was installing ICS last night and got the dreaded EU message, at the time I did'nt know what it was so I shut off the phone and powered it back up and had blue recovery. I wiped the dalvik cache and re-installed gummy then rebooted and everthing came up fine. except for the home button issue that is that I fixed by installing gapps. Now I may have dodged a bullet here but I don't want to stay on this rom if one day its gunna fry my phone out of the blue. Can I just Odin it back to Stock Froyo?
[Captivate Android Development] ctrclckws:
I did, on the phone that didn't get hit.
[Captivate Android Development] swayjd:
You can safely use GB no need to go that far back.
[Captivate Android Development] minotaur507:
I tried extracting Doc's boot.img and inserting into a Glitch b6 installation CWM zip as FocuseD83 indicated...I'm still unable to mount /emmc (Reverse fix applied) either from within the recovery or within Root Explorer...

Well, it was something to try anyway...
[Captivate Android Development] gcamp0730:
I just caught that you mention it was a B7 kernel that you 'kinda' edited. What does that mean exactly? Maybe you should upload the unique file you created. That is, unless I'm reading that statement incorrectly. :)
[Captivate Android Development] Demetris:
@mr_psycho

When placed into pc coulnt access sd card so i think cannot make image.

Windows asked to format it but went with sd card formatter.
[Captivate Android Development] mr_psycho:
So, the partition may be getting corrupted, or something similar.

MP
[Captivate Android Development] azunino:
Windows requires a file system for accessing the SD card. You should try using the command dd on Linux to dump the raw SD image.
[Captivate Android Development] Demetris:
What would you do with a 32gb raw image without filesystem on it?
[Captivate Android Development] azunino:
I suspect some parts of the fs structure may be still there, but windows requires it to be perfectly well to be mounted.
[Captivate Android Development] AdamOutler:
Guys, Galaxy Nexus has Odin3, Fastboot and Recovery modes. I think we need someone to port the fastboot bootloader.... Nexus S has this...

Anyone have this problem with an UnBrickable mod device? Try the Nexus S resurrector and run the fastboot from there :)
[Captivate Android Development] b-eock:
I pointed this out earlier. Saying we could use UBoot to port fast boot and have it on the Captivate. I wonder how hard it could be. I don't have this problem, but I wanna try to get this fixed for others.
[Captivate Android Development] RootTheMachine:
Somebody on GS II got "encryption unsuccessful" from an actual failed encryption. They didn't get borked, as GB roms still worked fine, but ICS would throw the same error. It was fixed by flashing an efs fix. Not sure if this is relevant to us at all. http://xdaforums.com/showthread.php?t=1621835

Sent from my ICS Samsung Captivate
[Captivate Android Development] s0ul_ali:
Thanks you suggestion, I will try it tomorrow with captivate stock ROM.
[Captivate Android Development] AdamOutler:
If an EFS is all that's requried.... Here is my own EFS which anyone may use.

Warning: This will change your Serial Number!!!]Download Captivate EFS One-Click --link removed as it was not effective.[

Please test this out and post if it works. If not, I'll remove it so everyone with this problem isn't running around with this problem AND my old serial number.
[Captivate Android Development] RootTheMachine:
After reading the other thread again, I'm not sure if it will help, since they never lost access to the sdcard or data. Maybe still worth a try
[Captivate Android Development] cgugino:
Just checking in -- any fix for this yet? Anything worthy of putting in the OP?
[Captivate Android Development] Thunder22:
I tried Adam outlets efs one click. Unfortunately it didn't work for me.
[Captivate Android Development] RootTheMachine:
Somebody got their files back two months after they lost them due to this error. It was fixed by using an extracted version of Glitch kernel, and the files were right where they were before on the Sdcard. It seems to have been buried in the thread though.

I think you should add more steps to the op of things to try when you get this error, like wiping data (worked for me) and such so people don't dig themselves a deeper hole.
[Captivate Android Development] Wdustin1:
I just saw in the general section that somebody has been able to fix this problems. Reproduced it and fixed it again. Maybe we should get in touch with him. http://xdaforums.com/showthread.php?p=25836539
[Captivate Android Development] octavia:
Just so I won't get my hopes up, the possible fix mentioned in the last few pages refer to fixing the data on the SD card or recovering the internal card (which is my main concern).
[Captivate Android Development] AdamOutler:
Ok. I took down the link to that file. Thank you for trying it.
[Captivate Android Development] jgaviota:
From the post of the user that got his files back, I think he jolted the internal sdcard with all that overclocking and different volting he was doing a the time, so the "fix" was not the glitch kernel but all the circuit jolting. Of course you could more easily fry the chip trying to do that.
[Captivate Android Development] jonnyg1097:
If anybody that is having this problem with their phone and isnt under warranty anymore with Samsung and considering a full repair of the phone. (At least in Canada with Service Absolute) the repair would cost about 300 dollars to replace the mainboard in it.

So I thought that I'd just mention that to those considering it. Looks like its up to xda now to get this going again. Go devs! :D
[Captivate Android Development] Woody:
I think Adam might be on to something with the efs fix. Check out this thread in the SGSII that someone was able to get out of it. Has some downloads that I'll take a look at and rip apart and see if we can swap Cappy / Vibe files. Silvertag knows the thread too.

Obviously it is Mother's Day weekend and I'll be out of town and away from my PC but when i get back, it is Junior Rodeo On (Big Bang Theory reference on case you missed it)
[Captivate Android Development] RootTheMachine:
Well it didn't work for somebody. I linked to the above thread in here earlier but I figured it wouldn't work since the circumstances were different.

Oh yeah, it would be nice if we could make a list in the OP that compiles all of the useful information. Like maybe a list of the different cases of EU, how they might have happened, and if/how they were resolved, in addition to references to other related threads that may contain useful information.
[Captivate Android Development] Woody:
Maybe we could start a [ref] reference thread and put in big bold in the OP to put theories, problems and general dismay in this thread and only cross reference-able FACTs, ROMs/kernels, when and how it happened, ... in the new thread. I would but I just got a huge promotion at work so my time during the day will be limited. Night is still open though.
[Captivate Android Development] RootTheMachine:
I can do that if you think it'd be a good idea. A lot of potentially useful things are getting buried in this thread.
[Captivate Android Development] Woody:
I do think it would be a good idea but I can't stress enough to make it known that that thread needs to be clean and all other conjectures need to stay in this thread. Otherwise it will be this thread redux.

What I can think of off the top of my head is MTP, recent glitch kernel boot swap, the OP "fix", anything Adam suggests, hitting reboot so many times your phone forgets about the error altogether, ...I would do one post for OP and maybe a 2nd and/or 3rd for more info and possible solutions.
[Captivate Android Development] RootTheMachine:
http://xdaforums.com/showthread.php?p=25993613#post25993613

Okay, if you want, you can reserve the third post
[Captivate Android Development] mr_psycho:
Have people with this problem been yanking their batteries and letting the phone sit for long periods of time? Just wondering if keeping the phone powered (or sitting with a charged batt) is keeping some kind of state. Probably nothing, but might be worth a shot. I can't imagine that person who got out of the error after a long wait had his phone charged the whole time.

MP

--

Life is the bubbles.
[Captivate Android Development] yosup:
Interesting ... how long would you suggest to keep the battery pulled?
[Captivate Android Development] mr_psycho:
If you don't need to use your phone, I'd say a day or two at least. *shrug*

Not saying this will work, but who knows?

MP

--

Life is the bubbles.
[Captivate Android Development] AtoZ0to9:
Anyone NOT using an external SD experienced this?
[Captivate Android Development] RootTheMachine:
Would anybody be willing to try this, at risk of getting EU?
[Captivate Android Development] mcyorian:
this post must to have a poll on top with a list of ROMS and people who gets the error vote for the afected rom... this give us an idea of what roms are susceptible on the fail

(if anybody understand this post please be free a re-write it in better english)

---------- Post added at 04:41 AM ---------- Previous post was at 04:37 AM ----------

this post should be placed at the top with a poll all affected roms.

People with the error must vote for the rom you use.

That way we will know better how many of the roms are more susceptible in the error.
[Captivate Android Development] RootTheMachine:
I don't think it matters; this is happening across a wide range of ICS ROMs and devices
[Captivate Android Development] matmanchu5:
UBMOD a possible fix?

I ran across this issue when rnning IMM74K 4.0.3

Tried to factory reset via CWM= NO LUCK

Tried flashing Kernel, Rom, using odin and heimdall = NO LUCK

-all flashing stops at data

-is possible to flash kernel

Phone says data partition can not be flashed (error w/RFS format)?

Download mode is achievable

After two months of reaching for my phone only to find a useless piece of plastic and stuff and junk....I gave up...

Then I sent my phone to get UBMODded.(I dont have the tools)

and now the phone is on its way back and (hopefully) better than ever!

Not sure because i dont have the phone back yet, but I have faith it is fixed.

I didnt ask, well actually i hinted, but i guess they wouldn't charge for the service if everybody new the solution.

Besides, after reading what is possible with UBMOD its like a freakin double-whammy!

I wont mention who fixed my phone. I wont be responsible. It shouldnt be to hard too figure out. Just google it.
[Captivate Android Development] octavia:
The internal card is now available from my phone. When I first got the reset problem, I couldn't access the internal card at all. And today, all of a sudden, I started getting a bunch of error messages like 'Unfortunately X program has stopped' and most widgets are not even showing.

Then I realized that my internal card with all its contents were available from the file manager. Is that supposed to happen? I didn't do anything.
[Captivate Android Development] RootTheMachine:
What ROM/kernel are you running, and what have you flashed since getting the error? Also, how long ago did you get the error? Is both the sd card and /data accessible?
[Captivate Android Development] octavia:
I'm using Glitch (3.1.10_IcyGlitch

v14-b6-I896-I897) with Infinitum (2.2 when the problem started and when the card re-appeared; I re-flashed with LBRv1.0.1 and the cards were still there)

I don't know what happened or even which card is which. All I know is that now I can see two cards from the explorer:

1) Home>mnt>emmc (which is also shown as Home>emmc, the files are the same)

2) Home>sdcard

On Storage I see:

1) Internal Storage 1.85GB

2) USB Storage 13.03GB

3) SD Card 12.92 GB

I didn't do anything but if there's anything I can do to help others recover their cards, let me know.​
[Captivate Android Development] RootTheMachine:
Can you access /data?​
[Captivate Android Development] octavia:
I see /data but it's empty and I tried to paste something but it didn't work.

Edit:I got the error about two weeks ago and I used the solution at the beginning of this thread, but I wasn't able to recover the internal card until it re-appeared by itself.
[Captivate Android Development] ReDaved:
strange changes?

I seemed to have a similar situation that octavia had. I woke up this morning, and it appeared the battery was dead, [later it was confirmed at '0'] I Put in a fresh battery, turned it on, and proceeded to get a whole bunch or error messages [x program stopped] for many apps including account manager. when all this finished, all my 'desktop' app shortcuts were gone.

I was more than mildly concerned and worried.

I booted to recovery wiped dalvik cache [i thought why not]

all the apps seemed to work, but the shortcuts were still gone.

I came back to this [as i do at least twice a day hoping for a fix] and read this.

so.... using Root Explorer, I can get to what says /data and all the subfolders under... including one called /data/data that is dated 22 Apr, which i think is before the big EU Reset crap happened.

Am i getting to the internal storage?

Currently i'm using CM9 4-19 [which i had to flash back to when i figured out about the file structure change that affected the ext sd

?????:confused:
[Captivate Android Development] RootTheMachine:
You know where to find it, right?

That's weird if it's empty... If you try installing an app, where does it install to?

Yes, sounds like internal storage. So your apps and sdcard files are back then?

What ROM/kernel are you on, and what were you on when you got the error?

Swyped from my ICS Samsung Captivate
[Captivate Android Development] Red_81:
Did your battery also die? Or was your phone without power for some time?
[Captivate Android Development] ReDaved:
Kernel Version:

3.0.8-g... blinky-ghost

ROM:

CM9 20120419-NIGHTLY

I spent a LOT of time getting things back to normal, and also google installs everything back, and i use 'the cloud' for so much, I'm having a hard time figuring out if it is truly back.

I suppose i could take my external SD card out and see what happens?

I am quite a bit gun shy at this point, and it does work as is, I'm a bit hesitant to fiddle too much.

If i did take the card out... I'm not in a position to spend much time fiddleing until the weekend...
[Captivate Android Development] raz123:
benji22210,

I looked at my Captivate that's currently running the workaround (using an ext SD) -- I have the exact same messages that you posted from your log.

Yep, looks like I used the term "moviNAND" whereas the correct one should have been "oneNAND". My bet remains that one or more files present on the oneNAND is the source of our woes; which is why I am suggesting copying system-crucial partitions from a working phone to ours, and see if that fixes our issue. Anything wrong with that reasoning?
[Captivate Android Development] jcjcc:
Compiled a kernel with CONFIG_MMC_DEBUG set and looking through the logs and the code.

The card doesn't seem to be dead; it's responding to MMC CMD1 (SEND_OP_COND) like it should. Initially I thought there might be a problem with the clock but that seems to be somehow in line with the spec sheet for the moviNAND.

<7>[ 5.730107] s3c-sdhci s3c-sdhci.0: clk 2: rate 51307692, want 400000, got 200420
<7>[ 5.730242] s3c-sdhci s3c-sdhci.0: selected source 2, clock 400000, delta 199580

200420 is pretty off from 400000, though. :/

This might just be what the issue is. I tracked down that the error raised is -ETIMEDOUT (-110) from mmc_send_op_cond() in drivers/mmc/core/mmc_ops.c.

The thing is, we've mostly all tried flashing back to stock (I did an Odin repartition with a PIT file) which should completely reset the oneNAND... then again, it doesn't touch EFS, so there is hope in that reasoning :]

For now, I'm running cgugino's workaround with a very old 2GB microSD that I dug up with 1GB for /data/.
[Captivate Android Development] raz123:
Good to hear. Are you able to read data? (CMD16, CMD17, CMD18)

I was under the impression that there were many partitions (bml and stl) that Odin did not touch?
[Captivate Android Development] jcjcc:
Nope, couldn't get it to initialize no matter how long of a timeout I set (response to CMD1 never unset idle bit). Seems irrepairable, not going to investigate further.

Conceivably you could probe the registers and use Samsung's vendor-specific commands to try and figure out why it won't initialize.

Afaik bml* and stl* refer to the same partitions, they are just different driver layers built on top of each other (to deal with bad blocks, wear leveling, etc).
[Captivate Android Development] raz123:
benji22210,

Why do you suppose that the clock couldn't be the issue?

I believe this is what it should look like on working devices:

s3c-sdhci s3c-sdhci.0: clk 2: rate 51307692, want 51307692, got 51307692
s3c-sdhci s3c-sdhci.0: selected source 2, clock 51307692, delta 0

Moreover, would you be able to post your boot log (while in debug) from the first instance of "mmc0"?
[Captivate Android Development] jcjcc:
Well, could be. I didn't have anyone I could ask for a working-device log, it would be great if you could get one from someone and see if this is the issue.

Sure.

http://pastebin.com/udn1HWmx
[Captivate Android Development] raz123:
Right. Will have to ask around.

In the meantime, here is a log from a Samsung Wave (S8500). Very similar to the Captivate (same chipset, screen) -- but 2 Gb of internal SD instead of 16 Gb.

http://code.google.com/p/badadroid/source/browse/trunk/FOTA/kernel_boot.ASM.log?spec=svn147&r=147

As you can see, different clock.
[Captivate Android Development] mechanical tool:
I have been following this thread with interest since I would like to run ICS, but have no interest in wreaking my internal sd card.

I currently have a working captivate running JVR and TalonDEV kernel. I'm interested in helping out can could post the log. It might be a while before I get a chance to however. It will either be tonight or next week.

Any detailed steps to log it would help.

I was also thinking maybe it would work to apply the fix immediately and run ICS from the external sd and just bypass the working internal sd. It might prevent the internal from being used at all and possibly disabled/wreaked.

I'm not sure how it would affect the procedure to go back to stock/Samsung based ROM.
[Captivate Android Development] jmtheiss:
I just had a very minor success with this situation.

I was flashing the Fusion ICS build, and got the dreaded encryption screen. Following the instructions here, I pulled my external SD, didn't hit the "reset device" button, but instead rebooted a few times. It wouldn't change, so I rebooted to download mode and flashed a KH3 Heimdall one-click that I had. It flashed fine, booted up, but the My Files application said I didn't have a card inserted.

However, when I connected it to my computer, my computer recognized the Internal SD. I'm now backing up all my stuff to a safe place. Not really sure where to go from here, but at least I've got my stuff backed up.

UPDATE: Unplugged USB cable, Media scanner ran, files now showing up on phone!
[Captivate Android Development] cgugino:
I'll put this into the first post
[Captivate Android Development] jmtheiss:
Thanks - hopefully this helps someone else fix this issue.

I've now flashed a new ROM (Mosaic 9), and the repair stuck. Looks like I'm ok (at least for now).
[Captivate Android Development] DaNaRkI:
Doubt it, google says that checking for encryption is part of the boot-up process. Not something that can happen once the phone is already running. The issue is not that android thinks the partition is empty, it can't find the partition.

I'm banking on hardware starting to fail. Loss of those partitions would cause the reboot and an inability to mount would cause the encryption response.

The only files I know of that could prevent the kernel from mounting a partition would the MBR (master boot record) or whatever linux calls it. It doesn't get touched unless re-partitioning (under normal operations, there is the possibility of someone messing with it intentionally), but a few sectors of the memory chip failing and not responding would easily cause the issue. If one such bad sector happens to hold the beginning of say /data, it's considered gone. There is no such thing as "searching for a partition header," if it's not where the MBR says it does not exist.

You could try changing the partition sizes so that they fall on different sectors of the memory chip, but conditions of the memory chip will vary from person to person. Failing is not dead, so it can respond after a few reboots, and flashing a different ROM remaps the partitions and can moves the starting points.

As for once you press the reset button

So anything trying to work within the linux environment is going to see that the partition is protected and will not touch it. Encryption is not new, just that since 3.0 google figured out a way to check for it and enter a password without the full system booting; it's been in the kernel long before android. So the only fix here is to use something non-linux or a modded/old linux kernel that does not recgonize encrypted partitions and write over it.

Alternatly

if this can be done via adb or CWM you could change the password to something known.

It might be a good idea to incorporate encryption and unlocking partitions into future CWM/recovery. Else once someone does encrypt a partition CWM can't touch it and they can be stuck on their current ROM.

What I would suggest: is to change how framework responds to the "-1 internal error" from vold. Maybe add an "ignore and boot" command, the partition is not actually encrypted so it won't have any problem reading it. Tho if it is hardware, then the data might get corrupted or the partition still not respond.