yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] swayjd:
Just to clear things yup, cause we have enough confusion.

When you say it has been solved, do you mean that someone with a broke sd card successfully fixed it with consistent results? (I mean he was able to do this on several phones)
[Captivate Android Development] Woody:
He got the bug multiple times and was able to pull out of it each time, at least from what I have read. It was also on an I-9000, so it is essentially the same as Cappy and Vibrant.

Please note that this is a preliminary statement and as I said before, we don't have all the info. Trying to get more but as if now all we have is the thread I linked above and the statements from the author regarding that he solved the bug.

I wished I had more to tell but at this point I don't yet. Once I get more, trust that I will definitely keep you up to date.

Somebody might want to browse the I-9000 forums to see if anything pops up about it or the bug in general.
[Captivate Android Development] FaultException:
Like me and MP said before, this may not be the same bug. Please note that the "Encryption Unsuccessful" does not just come up when you hit just our bug. On Jelly Bean they were probably hitting the same screen because they had the /data mount commented out.
[Captivate Android Development] ableeker:
To me it sounds like they were wondering why their JB kernel didn't boot, until someone noticed the data and cache partitions weren't mounted because the commands were commented out in init.rc. The kernel worked when they uncommented the lines.

The thing is that the kernel didn't come up with an error message saying the data partition wasn't mounted, but came up with the EU screen. However I think this screen was caused by the missing partitions, not by the EU bug.
[Captivate Android Development] Woody:
I agree. I an wondering though if we can use any if their information since one if the first symptoms that I have seen recently is that the blk02 won't mount. I'm still reading though.

Edit :: IIRC a few who have come back from the coma seem to have switched or flashed a different kernel. I'd hate to go in circles again but...are the mounting procedures in the kernel related to the trip that causes the bug?

Example:: Why have so many users who use SubZero kernels not been effected? There are some, don't get me wrong, but we all flash kernels more frequently than ROMs. Is there something in this kernel that isn't in that one? Blah, blah, blah.

**Not an endorsement or condemnation of SubZero it any other kernel, just that name came to mind bc it's the one I use.
[Captivate Android Development] azunino:
Your comment about SubZero kernels is really interesting. AFAIK SubZero is based on Devil, which in turn is based on the android kernel v3.1. On the other hand, the CM9 kernel is based on v3.0. Maybe v3.1-based kernels have some fix or access sdcards differently???

BTW, I've running CM9 and AOKP from /data on the external SD with zero problems so far (CM9 kernel and Devil 0.92).
[Captivate Android Development] melvinaury:
Thinking about what you said. My Cappy came to live when I install devil kernel, using the .tar file I don't remember the release number.
[Captivate Android Development] Red_81:
Maybe some of the affected users can flash SubZero or Devil and report back. Who knows, you might get your SD back.
[Captivate Android Development] tahoeski:
Just got the dreaded EU bug. :( I am trying to get running via the OP guide, but I can't seem to get a ROM to get past the EU screen. It looks like partitioning my microSD under #4 using CWM 5.5.0.4 but it is not working (permission denied error).

I have tried it with CWM and Devil Recovery and no go. Anyone have any ideas to get my microSD repartitioned? CWM or Kernal versions that have worked for others?

EDIT:-- Got microSD partitioned using CWM that comes with latest SlimICS. No just trying to get RootExplorer loaded.
[Captivate Android Development] azunino:
That's really sad. Which ROM and Kernel were you using when the EU screen appeared?

For all of you that have not been hit by the EU bug, take a look here: http://xdaforums.com/showthread.php?t=1711150

Better safe than sorry.
[Captivate Android Development] M973:
Also was wondering what ROM/kernel you were running at the time.
[Captivate Android Development] Woody:
I am thinking that since he just got the bug that this would be a good time to do some experiments before the fix is applied. Mainly trying to flash some different kernels to see of that brings back the internal mount. Hopefully he'll stop back in and see this.

Since I don't own a Cappy can anyone suggest some kernels for him to try?

Maybe since the fix is applied to the external and if you take it out the bug is still there, someone who has the bug could try this also.?.
[Captivate Android Development] azunino:
Try flashing Devil or Semaphore because some people reported that the internal SD was fixed by these.
[Captivate Android Development] tahoeski:
I was running Doc's V12 ROM and Semaphore 1.2.5sc Kernal when EU appeared. EU in the morning after being on a charger all night. Overcharge?

I tried flashing Devil and Semaphore to no avail. While I have gotten ICS back up by partition of MicroSD, I am still getting errors from various apps (Gallery, Dropbox, etc. ) that say no external storage found even though in "Storage" menu my card shows up as USB Storage -> SD Card with 5.5GB of space. I did make the edits to the vold.fstab file an reboot.

Sorry I did not get these replys in time to do some testing to help out, but i am just glad to be able to use my phone again...

Can someone tell me if all apps are working fine one the vold.fstab file fix is applied.
[Captivate Android Development] azunino:
Semaphone is based on 3.0.17. Maybe there is a pattern. I'll re-read the thread to find if there is some correlation between kernel version (3.0, 3.1) and the EU bug.

BTW, all apps are working fine with the modified vold.fstab. In fact I've been using a similar hack to avoid *using* the internal SD at all on fully working phones just to avoid the mess the EU bug causes. So far so good.

If you have time could you please flash Devil, reboot, turn off, turn on and check if /emmc is there (for example using a file manager or from Settings->Storage)

Thanks
[Captivate Android Development] melvinaury:
When it happen to me I was just installing semaphore. In the first boot I received the error.

When the sdcard came from dead you will notice, because of all the weird errors that appear when you boot the phone. It appear that after the internal sdcard is back the phone goes there first. In my case I don't notice that on time and just did a full wipe and install from zero again. When finish I notice the internal sd. The issue that I still not correct was to repartition my external sd back to normal. Right now I'm just using half that space of the external sd.
[Captivate Android Development] cgugino:
Hey everybody!

If there's anything helpful for people running into this that is worth putting in the original post, please PM me with it and I'll add it.

Love,

Me
[Captivate Android Development] gocats7:
I just got this message for the first time.....man thats a horrible feeling! I had just flashed to stock and then loaded slim ics. The message occurred on first boot. Luckily I didnt hit reset phone. I tried rebooting about 10 times...message always returned. I rebooted into recovery again, performed a factory reset, fixed permissions, reinstalled SlimICS...rebooted and the message was gone. No idea what fixed it, perhaps nothing but luck but I thought I would share.

EDIT: I had to flash back to stock again and then after reflashing slim ics I got the message AGAIN. I shut the phone off, booted into recovery, performed a factory reset and the message went away.
[Captivate Android Development] HapaBiH:
I have the same problem on my Galaxy tab 7.7 after ICS upgrade. Is the micro SD partition method possible for my device too?
[Captivate Android Development] lesterkravitz:
Everytime I pull my micro sdcard and turn on my phone it gives me the encryption unsuccessful screen, so I put the card in and encrypted since I have nothing to lose at this point.

Now when I turn the phone on with no micro sdcard it gives the screen to enter encryption password but does not accept the password. I don't know where this is going if anywhere just sharing.
[Captivate Android Development] swayjd:
So, you came across a situation where you could have possibly broken your phone for good and your reaction was to flash ICS again and keep crossing fingers? Good Luck!
[Captivate Android Development] lesterkravitz:
Delete
[Captivate Android Development] Demetris:
I think a solution is found but needs testing.

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

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

I hope good news will arrive soon ;)
[Captivate Android Development] jcjcc:
Thanks. But it doesn't seem to be the same problem, and their solutions won't work for us. Phone can't talk to the internal sdcard chip at all, so /dev/block/mmc0p* devices don't exist. Neither can download mode/Odin/Heimdall touch the chip.

For some people the chip suddenly starts working again -- give your phone a good whack and hope for the best?

Anyways, I've been hanging around since this thread was created, and what's shocking is that the bug in ICS that fries our internal sdcards still has not been found.
[Captivate Android Development] visionlogic:
Or, the bug in our hardware that allows ICS to fry our internal sdcards has still not been found.

Either way it sux.

.
[Captivate Android Development] azunino:
Or... some philosophy next... you have been warned

re-reading about the EU bug I found these (and many more):

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

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

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

http://xdaforums.com/showthread.php?t=973687&page=3

http://xdaforums.com/showthread.php?t=1611394&highlight=internal+sd

http://xdaforums.com/showthread.php?t=1625830&highlight=internal+sd

taking about non-working internal SDs on i9000 devices with GB, ICS, Froyo, ... Considering the variations, no software seem to be involved (or all android versions do have the bug which is unlikely)

What if... the SDs are just dying of "natural causes" and the EU screen is just a visible symptom that makes us point fingers at ICS-based ROMS (all the other Android versions in presence of "the bug" just do not boot/hang/crash/FC like crazy/...)?

BTW, I'm happily not risking my cappy by running ICS from a cheap sandisk external SD. ;)
[Captivate Android Development] Demetris:
I just dont thing my 8 months old Vibrant died of "natural causes", i refuse to.
[Captivate Android Development] swayjd:
This is it basically, these phones are rock solid and this was never an issue, untill ICS.

The links azunino posted, to some extent seem to be either bugs that got corrected with new versions of software and natural causes cause they exist aswelll, obviously. It seems that the cases were ignorable and now its more like mass murder.
[Captivate Android Development] melvinaury:
When my Cappy die I only has it for 2 months, I buy it at .99 cents online. Thank God it comes back to life after 4 months using the external sd solution. It happened when I install semaphore, one of the first releases. Now I'm on Devil, by the way it comes to live after I install Devil Kernel ans turn it off. When I turn on it comes to live.
[Captivate Android Development] jcjcc:
Yeah, I actually also thought that perhaps the internal sdcard deaths were unrelated to ICS. After the test kernel I compiled (waay back in the thread...) showed that the chip was not responding to initialization commands, the natural conclusion is natural death.

But when we looked into it, there were so few until ICS. And many threads were a different problem (solved by ROM flash etc.) than ours.

Anyways, I believe we compared voltages and clocks with non-ICS, and examined the debug registers, and found nothing wrong. I thought the chips were definitely being fried because ICS was giving it more voltage than GB or something, but we couldn't find anything.

Well, there still are some tricks we haven't tried -- there are some diagnostic and vendor-specific commands we found in the moviNAND (internal sdcard chip) spec sheet. It's still a mystery as to what ICS is doing different from GB that fries our internal sdcards.

But hey, if you get a good quality microSD card that has faster I/O than the internal card, your phone's performance will increase, since it can access your app data faster. I know they even have (full-size, at least) UHS-I cards that can pull off some 50MB/s. Think of it like a PC component upgrade. It's like getting faster RAM or upgrading to an SSD.

Optimism :D
[Captivate Android Development] mechanical tool:
The most likely explanation seems to me to be the bugs in the additional commands in the firmware of the internal sd. If these commands are only called from ics that would explain the sudden onset of the issue with ics.

Similar to the problem with other Samsung phones, even if the revision/id/etc of the firmware is actually different.

I don't know if it's easy or even possible to rewrite the sd access code to only use the commands that were used in gb.
[Captivate Android Development] azunino:
A possible step to try to answer this question could be to determine the differences between the drivers of the mmc devices of our phones. Right?

If that is correct, then the question is where to look at? Maybe in this subtree?: https://github.com/CyanogenMod/android_kernel_samsung_aries/tree/android-samsung-3.0-ics/drivers/mmc, and in particular the files related to s3c-sdhci?

Ideas?
[Captivate Android Development] :
From what I always assumed, this can happen regardless of if I use and external SD or not? Like if I don't use an external SD I can still get the encryption bug?
[Captivate Android Development] azunino:
that's right
[Captivate Android Development] topiratiko:
Knock on wood me and a buddy with a captivate have flashed literally everything there is and I boot into recovery n fiddle with stuff on a daily basis and we've NEVER seen this issue. Do build dates possibly have anything to do with it?

Sent from my Galaxy S Captivate on Slim Rom 4.2 powered by Semaphore 1.2.6sc. Project BUTTER
[Captivate Android Development] :
Same here. I even got it once a while ago, hit the button and nothing happened, thank god. I don't know about build dates, but someone mentioned JB fixing it.
[Captivate Android Development] azunino:
That's why I said "What if... ": http://xdaforums.com/showpost.php?p=28614530&postcount=763

BTW, I tried to motivate some brainstorming, because I (and many more) want a reasonable explanation for the damaged SDs. In my profession there are causes and effects... so at least from a professional point of view I don't believe in coincidences. However, so far there are no patterns telling us how avoid the problem.

nygfan760, JB did not fix the EU bug. AFAIK, the EU screen was a symptom of some wrong config files.
[Captivate Android Development] :
Oh wow, I was reading something else and I mistook some info. Do you see any type of negative effects to running off the MicroSD?
[Captivate Android Development] azunino:
No negative effects. I mean... if the Micro SD is slow the experience might be not that good. I'm using a super-cheap Chinese 16GB Class ??? card... and my wife a SanDisk class 4 and everything is as smooth and fast as the normal ICS, battery lasts 2 days, no reboots at all. I mean, I would not risk making my wife mad at me... ;-) At worst the SD cards will wear out sooner that using them "normally".
[Captivate Android Development] :
That's fine with me lol, I have an old class 2 I might try out just for kicks even though it will be slow. If I can find a way to format it on my mac to ext4 that is.
[Captivate Android Development] azunino:
I think the OS X Disk Utility can do that.
[Captivate Android Development] :
Sadly it can't. I found a wat I thought worked but it didn't. I'll just vm windows really quickly.
[Captivate Android Development] kind3rgarten:
Okay, so my Captivate broke a long time ago and I thought it was done for and bought a GSM Galaxy Nexus. So while browsing, I decided to check out this thread and tried the steps on my Captivate and after I installed CM9 I try to restart, the phone just boots into CWM. I did everything verbatim. I haven't done step 10 yet as I cannot even boot up.
[Captivate Android Development] jrhsu529:
Instead of going through steps 8+/9+ everytime we flash a rom can we just edit void.fstb in the ROM before flashing it?
[Captivate Android Development] raz123:
As the OP says: No, because: "flashing overwrites the vold.fstab file".

What you could do is edit it once, make a copy (on your ext SD or PC), and once you flash, copy it back in the system folder, overwriting the new vold.fstab.

EDIT: Oh, if you meant edit the vold.fstab in the ROM file to be flashed, then I suppose you could. Not 100% certain. Try and let us know.

EDIT2: Unrelated, but I noticed that the reply for CMD1 that our defective units are giving (despite always returning busy), is indicating that the MMC is under 2Gb, which is wrong. It is returning "00xxxxxx" (while busy), whereas it should be returning "40xxxxxx" (while busy). Reference: "devices shall respond with a fixed pattern of either 0x00FF 8080 (capacity less than or equal to 2GB [ie: use byte mode]) or 0x40FF 8080 (capacity greater than 2GB [ie: use sector mode]) if device is busy". At this point, we really need a log from a working device.
[Captivate Android Development] DaNaRkI:
Tomorrow or the next day (depending on how busy I end up being), I'll set my phone back to CM9 and try to set up my PC, (loaded Linux but never set up adb) and get you a the info.

Is there a specific build you want me to load?

leaked from my

ICS

- FUSED SGS I897 contaminating you via XDA app.
[Captivate Android Development] jcjcc:
Wow, so flashing to stock (and master clearing?) has worked for at least 2 people then. Can you point to exactly which Odin/one-click you used, what options you checked, and anything you did after (master clear from the menu)? I think I'll try it one more time.

On the other hand we might just have different issues that both happen to show the same Encryption screen, but I'm hopeful.

Re: raz's PM and the updated sdhci driver, it should be in Glitch 14. Last time I tried (few weeks ago), I couldn't get Glitch 14 to compile without downloading and building the huge CM9 repos (13.1 compiled great without the repos, with a few tweaks to the build scripts), any tips? I don't like messing with the CM tree when all I want is a kernel.

DaNaRkI: any build of CM7 (like the latest stable or nightly#181).
[Captivate Android Development] DaNaRkI:
CM7, not ICS? Ok.

Something I wish to clearify: raz's phone = already encrypted & benji's = not encrypted but is getting the "encryption unsuccessful"? So if you both flash to something non-ICS raz = no internal sd & benji = fully fictional internal sd?

leaked from my

ICS

- FUSED SGS I897 contaminating you via XDA app.
[Captivate Android Development] raz123:
I believe benji's device and mine share the same symptoms (my log matches his).

The internal sd/mmc never gets out of its initialization mode, always responding that it is busy, and thus refuses to answer further data commands.

We cannot mount such an mmc, regardless of kernel/bootloader/rom -- stock or not. This has been my experience.
[Captivate Android Development] sleeper994:
So I used this workaround and my phone is running on external SD card. However I got some other issues with ICS rom, and I was wondering if doing Odin one click back to stock would be safe to do on phone running this workaround ???
[Captivate Android Development] DaNaRkI:
No reason why it would not be safe. As OP states, odin won't fix this so you'll have to re-edit the necessary files.
[Captivate Android Development] uhs74:
Vibrant -got Encryption unscessfully after installation of ics v13 on first boot

I did following stpes

Note: during whole process i didn't use external SD card in phone.

1)go to stock (android 2.1) using ODIN based on following link

http://rootzwiki.com/topic/605-guid...nja-apps-everything/page__p__11106#entry11106

2) using following link used update.zip (2nd one in topic) to root and install CWM,backup & install custom rom of IcS euphoria

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

3) after successfully installation , it is rebooted and bootup animation appears

4) immediately after that i see above screen "Encryption unsuccessfull"

5) i didnt click on "Reset". I tried reboot again but again i see same screen.

6)i reboot in recovery and install ICS passion v13rc1 ROM

7) again i got same screen after boot animation

8) went to download and got back to stock using step 1

Now what steps i need to do in order to avoid this screen while installing custom rom.

any quick input will be great.
[Captivate Android Development] DaNaRkI:
No one knows, yet. raz and benji are picking through the current theory. Some say an odin master clear makes a difference, and allows them to load ICS.

Again, No solution has been found yet.
[Captivate Android Development] HoberShort:
Having just read through this thread from the first post, the only reference to master clear was a link to my posts page, but I'm not sure why. Master clear did nothing to help me. Sorry if I'm missing something, I just didn't want people to waste time on a dead end.

My symptoms started with what this thread has documented, but as I tried to recover from that, I eventually got to a state where I could also not mount my external SD card, so I couldn't even use this workaround. At that point it looked an awful lot like a hardware failure.

I sent it to Samsung for a "reflash", and when that didn't work, they started replacing components, finally fixing it by replacing the "PBA", which the various forums tell me is the motherboard.

So now I've got my Captivate back and fully working, running Apex 12.3 (Gingerbread), and wanting to flash back to ICS, but not wanting to get burned by the same error again.
[Captivate Android Development] DaNaRkI:
Honestly this is still my position, namely because it is few and far between. Given Samsung's track record with the cappy, I have no doubt that it is a hardware issue.

leaked from my

ICS

- FUSED SGS I897 contaminating you via XDA app.
[Captivate Android Development] stayintwisted:
I do not understand why if it was a hardware problem my phone was saved (apparently of course ) by using odin back to stock from the point at which all the phone would do was boot to the AOKP boot screen then the "encryption unsuccessful" screen,, and I am now running ics slim on that handset with no apparent problems,,,oh and I have never installed the straight cm9 ics on the handset but was using the glitch kernel