yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] DaNaRkI:
If one really has to try and explain:

A. Intermittent laps in communication between components, older versions of android would ignore it and keep going with some second agent successfully getting a response thus no problems once the OS is fully running. ICS is specifically designed to stop at that first lack of response because so far it is Android's only way to tell something is encrypted. This is only checked at boot so if you can make it past boot your free till next reboot. If you intentionally make the phone reboot after a few tries it might get stuck again with the second agent never engaging the cards and it staying stuck. (this would be along johnsondr's idea of an app forcing communication, it world mean a life-time of random reliability)

B. The memory chip is faulty, the chip is starting to wear and that when electricity is passed through it does not respond the way it is supposed to. This would lead to a lack of response or an inappropriate response depending on what is starting to fail. If the main circuitry of memory chip were starting to fail it would not respond and seem dead. If it is only parts of the "memory" in the chip that fail then there would be an incorrect response, either a partial response or something gibberish. A more powerful wave of electricity from something like an Odin flash would awaken the circuitry and it will be fine till it gets stuck again or fully fails. (this is my idea of the memory chip going bad, and means it's only a matter of time till the circuitry wares to a point of no response and is literally dead)

C. Would be similar to B, but that it is circuitry other then the memory chip. This would be what HoberShort experienced where eventually the phone lost ability to communicate to both the internal and external memory and was totally unusable. Again a stronger jolt of electricity would free the "stuck" switch for a span of time, but it would soon fail again. It is possible that by forcing the circuity to run a different path then it is designed that we are stressing the system and hastening the wearing process meaning that, it losses ability to communicate to the external quicker then it might have on a similarly faulty device that is not on ICS.

For all 3 there is a possibility for a full boot to let the system continue because in a full boot there would be multiple attempts to communicate to the memory in a rather short succession. Where as during such an early stage of the boot up it only tries once or twice. It might take 10~15 hits before the electronics respond, a fully booted system would do this in seconds but a partical boot that is specifically waiting for a lack of response will only try 2 or 3 times then assume it is "locked."

One final note:

All of this is only reverent to initially triggering ICS to fault, this is in no way related to the behavior of something once it is encrypted. Encrypted SD cards are a whole different moster.
[Captivate Android Development] stayintwisted:
ok well I am still having problems with the hardware idea,, took me a few days to do it again,,not completely sure what I did,,to my OTHER captivate,, was installing ice cream zenwich and once again got the encryption screen,,so that makes two captivates did it at the same point in the installation of two different ICS roms,,both phones are functioning now,,both times followed the same procedure,,pulled battery,,odined back to stock (once KJ3 the other time back to 2.1 ) unfortunately I do not know enough to be able to give you any more information,,I just follow instructions and flash carefully,,any suggestions
[Captivate Android Development] DaNaRkI:
Well it is still all theory. The other other reason I consider hardware over software is that when a problem is software it will effect far more people and is easy to reproduce.

This has been few and far between and random. If this phone had any other history we would not consider hardware problems, but Samsung was flat out horrible with it.

leaked from my

ICS

- FUSED SGS I897 contaminating you via XDA app.
[Captivate Android Development] stayintwisted:
is there any SIMPLE way I can provide more information,,I unfortunately am not really computer literate,,and have not been able to find anybody in my close region that can help,,my local computer shop doesn't do android,, I have already asked,,I think until somebody can come up with something that explains this just a little better I will stay away from ICS for a while,,from all I have read having had this happen twice,,on two handsets installing two different roms,,the glitch kernel is all I can think of that was the same in both situations,,and I have been using it pretty steady with several different roms so am hesitant to suggest it oh and my phones are a build 1101 and 1102
[Captivate Android Development] uhs74:
I did same steps again i was successful but there was one diff. during recovery mode before selecting zip file for rom ,by mistake i also formatted internal "SDCard" along with format "system" step.

so during recovery mode, with "adb" (phone was connected to pc and recognized phone)command i copied again zip file and able to install rom.

but again not sure formatting sdcard is helpful or not.
[Captivate Android Development] HoberShort:
Has there been any confirmation on whether this is only happening with the CM9-based builds, or if it's all ICS builds for the Captivate?
[Captivate Android Development] simple man:
Other ICS builds besides CM9.
[Captivate Android Development] :
Try running this? http://xdaforums.com/showthread.php?t=1711150
[Captivate Android Development] azunino:
Please note:

*** This MOD only works with phones with working internal SD ***
[Captivate Android Development] :
Oh wow didn't see that.
[Captivate Android Development] kind3rgarten:
Do you have any other suggestions?
[Captivate Android Development] :
I have no idea. Edit the file before flashing it maybe?
[Captivate Android Development] azunino:
Do you want to try something "experimental"?

It's a kernel (Devil) recompiled for phones with broken SD cards so that a modified vold.fstab is not required. First, partition the external SD as the OP says. Then, you just need to replace the boot.img file of any ICS based ROM (for example AOKP) and replace it with the boot.img file of the Devil kernel from here. Am I clear?

I've tried these steps with MIUI and AOKP (not CM9, but I suspect in CM9 it is necessary to change the internal/external from Settings->Storage->Menu after booting)

good luck
[Captivate Android Development] kind3rgarten:
Thanks for the reply, and sure, I'll try it. What have I got to lose at this point? Lol.

What level repercussion is this on the Captivate?

What could happen if this messes up? Corrupted bootloader?

I mean, like I said, I don't have too much to lose as this Captivate has been a paper wait for the past ~year, but I would like to have this working to give to a family member who broke his iPhone.

So I guess what are the repercussions of this?
[Captivate Android Development] azunino:
At worst you will get a bootloop or a EU screen, so first verify you can enter download mode and recovery by using the typical key combinations. In other words this kernel won't hardbrick your phone.
[Captivate Android Development] kind3rgarten:
Okay, I'll pm you
[Captivate Android Development] HapaBiH:
Can this sd partition be made with some pc program or it needs cwm? For some reason I can't format with cwm :/
[Captivate Android Development] :
Mini Tool Partition Wizard is free and works for me.
[Captivate Android Development] HapaBiH:
Ok. Can you tell me how many partitions and in what order should I create them? If you can write some tips.

Tnx
[Captivate Android Development] :
First is a fat32 partition of whatever size > 1 gig to act as your SD. Second is an ext4 of whatever size >1 gig to act as your new data partition.
[Captivate Android Development] HapaBiH:
Ok, thanks. I'll try it.
[Captivate Android Development] :
Any news on if it worked?
[Captivate Android Development] HapaBiH:
Should I make both partitions Primary?
[Captivate Android Development] azunino:
Yes
[Captivate Android Development] HapaBiH:
This method does not work for me, I tried it as a desperate move for my galaxy tab 7.7 as I have the same problem as you after flashing ICS. When trying to partition from cwm it tries to partition internal sd not the ext sd. I used recommended pc software and after partitioning and installing android system again uses internal sd with the same message. I know this does not belong here and I'm sorry but I had to try to repair my device.
[Captivate Android Development] :
Obviously it uses internal unless you have a modified rom to switch the internal and external SD mounts.
[Captivate Android Development] HapaBiH:
I managed to repair my device using STOCK recovery. After flashing it I did factory reset and my tab came back to life. For some reason CWM didn't wipe data properly or something.
[Captivate Android Development] wwcjr91:
So.. After doing some reading of both the guide and references (Thanks korockinout and azunino!) I'm still wondering a couple things.

Nobody has been able to diagnose the problem with certainty, correct? Specifically what caused the problem?

I got into ICS back in March, and didn't hear of the eu bug until months later. Luckily it didn't affect me. I started with Nostalgia, and basically had a taste of everything ICS-wise in the captivate development forum. Then about a month ago I saw korockinout's thread and read the horror stories.

Could this still happen to me at any point in time? I've been thinking about trying out some of the GB captivate roms, but I worry that if I wanted to come back into ICS, I would face the same risk. Should I just chill with ICS, be thankful I'm not affected, and wait for JB to set in?
[Captivate Android Development] azunino:
Right, the cause of the problem is still unknown.

Apparently this EU screen appears as soon as the /data partition cannot be mounted (several possible causes may trigger it). I've got it several times while modifying cm9 for using /data on the external SD, but I wasn't scared... because, in theory, I wasn't even touching the internal SD... Luckily nothing severe happened :-)

I hope to have some time to take a look (and hopefully understand... which is not very likely) the real causes that trigger the EU screen by reading cm9 source code, and also the differences between the mmc drivers in cm7 and cm9. I have no idea about hardware, drivers and low level stuff like these... (in fact my expertise is in much higher levels of abstraction) but... my curiosity is killing me.

GB or ICS... that's an interesting question. ICS is so good. Even when I really enjoyed GB (cm7), all the nice improvements in ICS really make a difference. However, I like my cappy enough to not take significant risks... so... ????? I use my cm9 patched to use /data on the external sd, which is far from perfect, first because it requires an external sd, second because it requires modified kernels (which may introduce more bugs...), and third because I have no idea about low level software/hardware. For me that's a good trade off.

If JB fixes this or not is also a big "?"
[Captivate Android Development] lesterkravitz:
I would like to try jellybean but don't know how to do the workaround for it. Does anyone know?
[Captivate Android Development] parkerdjohnson:
Would love to know!!
[Captivate Android Development] fagnerkof:
I tried the workaround for JB rom posted by silvercrown266 in this thread but it didn't boot with the modified vold.fstab; stayed like forever on the boot screen (nexus logo). With the default vold.fstab the JB rom boot properly but didn't read my memory, internal or external. Any ideas?
[Captivate Android Development] swayjd:
meh, I'm honestly just praying that this version of google doesn't outright kill our phones.

We have no way to know though. Other than to wait till someone gets burned or JB goes mainstream and there is no casualties over a good period of time.
[Captivate Android Development] s0ul_ali:
2 days back is was recovering my Laptop HDD partition, then I plug in mobile and the recovery software suddenly found my dead partition, but it couldn't access it. Just like a dead memory chip. Now my hope's for getting dead partition back are almost zer0. Now i m anxiously waiting JB work around and I hope goggle probably have removed the chip frying element in new version.
[Captivate Android Development] Demetris:
I made one with Jelly Beans Emmc Reverse.

Test and Report.

It works Just fine for me on CM10.
[Captivate Android Development] s0ul_ali:
let me check.. !
[Captivate Android Development] greygoose425:
Wow I just dodged the bullet. I was on ICS way back in the early days of ICS. It ran perfect for 3 months, but I got scared and decided to go back to GB to avoid "the bug". I grew some balls earlier and I decided to chance fate with a flash of the latest RemICS 1.3.1 build. Sure enough on the first boot after install I got the dreaded EU screen. I immediately pulled the battery and put my phone into download mode via a jig I have. I then Heimdall one-clicked back to stock and was able to save my phone.

The people running ICS and JB make it sound so inviting. Oh well, I guess I'll stick with GB until I get my S3 in a month or two.
[Captivate Android Development] wwcjr91:
Have there been any reported instances of this bug on JB? I couldn't find anything by searching.
[Captivate Android Development] Wdustin1:
Got the EU screen pulled battery and flashed back to stock kk4. Phone is saved, but now I'm to scarred to go back to ICS lol. Gonna have to suffer on kk4 till my gnex gets here.
[Captivate Android Development] crt60:
So just to ask. You copied the RemICS rom to your sdcard then flashed it, then it happened and you were on gb at the time?

What were you doing at the time? Did it just show up out of the blue? Did at anytime before, were you plugged into the PC?
[Captivate Android Development] Wdustin1:
I was just upgrading from aokp b40 to m6. And I got the screen. And yes I was plugged into the PC right before to transfer pics off my phone
[Captivate Android Development] swayjd:
Well, everyone, at some point, has plugged his phone to the PC. Since 2.1. This isn't it.
[Captivate Android Development] crt60:
I don't believe it is just something random, there is always cause and effect. I know a prevailing action is the phone was mounted as usb mass storage to copy a rom or copy files before the phone was rebooted.

It is known that the sdcard is in a "busy" state when the eu error appears. If the sdcard is not unmounted properly from the pc, it can show in a busy state and not appear to properly unmount at all. It doesn't mean the eu bug will show up if the sdcard is not unmounted properly as usb mass storage, but it is a bet, it is what causes it.

It has to do with the mounting of internal memory, the /data partition will not mount.

Everything about eu bug points to the mounting/unmounting of internal storage.

And I doubt a kernel would cause this when it mounts, unmounts the internal storage, unless the sdcard was first mounted externally to a pc.
[Captivate Android Development] swayjd:
Of course it's not something random. but ICS is what changed, not people's behavior. We didn't have a problem before ICS and now we do. Also, were that the case, people would get the error as they unplug the device.

And say they unplug, unknowingly they ****ed the phone, they reboot into recovery oblivious to what just happened. if the phone had been bricked, they wouldn't be able to access the sdcard within the recovery! Thats not the case, Its only when they boot into ICS that it bricks!

I've been following this thread for a very long time, a lot of people got this in the middle of the day. saying it was cause on a rainy Tuesday last month they unplugged the phone too quick is just throwing dust under the carpet.

Our discussion but in different terms, You got new shoes and your feet hurt. I say, It's the new shoes. You say, can't be the shoes, they're so shiny. It's gotta be because I put them on too fast!
[Captivate Android Development] stayintwisted:
I agree that peoples actions haven't changed but it is the phones response to the peoples actions that appears to have been changed,therefor changing the peoples actions might well have an affect on the situation,which is why it appears that being connected to the computer has bearing,it is not the peoples actions but the phones reactions to what the people do ( or at least that is what it appears to me the people smarter than me are saying)
[Captivate Android Development] crt60:
Which is why it is called a bug. Of course it is ics, Google enabled the encryption feature in the rom, so there are no coded safeguards for any phone that does not get ics from the manufacturer that is blessed by high payed programmers and proprietary libraries. Unfortunately peoples behavior does need to change. They need to eject/unmount their phone from the pc on the pc first before they unplug the cable.
[Captivate Android Development] greygoose425:
To answer your question crt60. I was on your Legend 5 w/ Corn 6.03 rom just before flashing ICS. I copied the zip files to my phone via USB. I unmounted the sd card via the phone but I did NOT eject via the PC (I wish I would have read that before hand). I then proceeded to reboot into recovery to do all of the appropriate wiping, reformatting and flashing. On the initial boot of ICS I got the EU screen and that's when I proceeded to do the battery pull, download mode via jig and Hiemdall one-click to stock.

Hope this helps
[Captivate Android Development] crt60:
Yeah, when you unmount from the phone, it does send a term signal but it doesn't always register completely that the connection was disabled on the pc, this is even more true with linux than windows, you have to eject from the pc, because it will verify the connection has been disable whereas just turning off usb storage from the phone doesn't.

Obviously the same thing happens on Gingerbread except there is code to deal with it and there is also no encryption enabled in Gingerbread like there is in ICS.

Like I've said before, I've damaged thumb drives by just pulling them out of the usb port without ejecting it first, also I see in the question and answer threads where peeps say parts of their sdcard can't be read or formatted, no mater what, so the same thing does happen on Gingerbread, just no EU screen pops up.

If the EU screen does ever show up I'd do like you did and immediately pull the battery and get into download mode, flash back to stock and start over. Cuz my guess is if you kept trying to reflash or boot ICS, you could have toasted your phones sdcard.

I would be on the safe side and just eject/unmount the phone, on the pc, before you unplug it, no matter what ROM you're running.
[Captivate Android Development] DerTeufel1980:
Is anyone running my kernel for devices with "broken sd"?

If so, please pn me. Too my bad I don't remember the name whome I originally gave the kernel to.
[Captivate Android Development] azunino:
There is one user here:

http://xdaforums.com/showpost.php?p=29979036&postcount=102
[Captivate Android Development] swayjd:
So his phone is running Gb when he unplugged from the PC.

Nothing happens, he reboots, flashes and yet when ICS is first booting there is some line of code that goes "wait, this fellow unplugged 10min ago in a different system altogether without ejecting, I'm gonna burn his sd card"

Is this what you are suggesting? That the bad unplug information carries on indefinitely? Just seems way too farfetched. Doesn't it? Am I alone in this?
[Captivate Android Development] billyjed:
I once pulled my cappy off the computer without un mounting/ejecting it and it borked mh external sd. Media Scanner would go nuts on it and I couldn't read/write to it from my phone.
[Captivate Android Development] TheSchatz:
It wasn't me, but for what its worth I'm using your most recent Helly Bean ROM and kernel (all in one from 8-13) and everything works great
[Captivate Android Development] crt60:
Not sure why you think its far fetch, and it doesn't happen everytime, the sdcard will unmount so it can be mounted again. Not everyone that unplugs their phone without ejecting from the pc first is going to get the EU error or fry their sdcard. Adam Outler tried and tried to reproduce the eu error and couldn't, but then all of a sudden, it hit, and his test phone became unusable.

I've unplugged my thumbdrive many times without ejecting with no consequence, except windows kept wanting to scan it.

All it takes it just one time, the sdcard won't unmount, or there is damage to the sdcard circuitry.

I'm just saying, it is a reasonable explanation to why it happens.

You can take it or leave it.
[Captivate Android Development] Woody:
@CRT60. Glad you are are trying to help out. This bug has plagued many users on many different devices. Many of us have been working on this diligently and maybe we just need some fresh eyes to look at the problem.

It has been my contention that it was a PC mounting issue from the start, but (there is always a but) we could never get in deep enough to know what was causing it to lock up if you grip it and rip it and pray or unmount properly. Meaning what is the difference or why does one cause the bug or not (code/logcat speaking of course)? Here is my intial post in this thread to hopefully shed some more light on your fresh perspective.

Keep in mind that Azunino was able to create a ROM that would use the External SD and bypass the internal completely (as a safeguard for those who want to run ICS but not worry about getting the bug).

Devices that I know of and links to some of their posts (this is older and could be updated but I don't know anymore or havent heard of anymore because well frankly, I don't own any of the one not on this list):

Samsung Captivate~~~(Roms->Infinitum 2.2 (CM9) with 3.1.10_IcyGlitch, Slim ICS 3.6 w/ Semaphore 1.1.1sc, Cyantablet 9)

Samsung Vibrant ~~~~ (ROMs-> CM9, AOKP, Zenwich, Passion, Euphoria, Doc's)

Asus Transformer TF101 ~~~~ (ROMs ->CM9)

Asus Transformer TF101g [3g version] ~~~~ (ROMs ->CM9)

Nook Color [not Nook Tablet] ~~~~ (ROMs ->Rack's Dual Boot Cm7/CM9)

Samsung Galaxy SII <--This seems to hark that something is wrong with the EFS but Adam Outler tried something along the similar lines and it didn't pan out.

More details can be found here --> [REF][ICS] Encryption Unsuccessful Reference, but this thread is somewhat abandoned because I think that people are frustrated and just plain tired of this and have either moved on to another device, reverted back as a preemptive strike against the bug or are using the work-around.

****

I would also be interested in know if anyone running JB has got the EU yet or at all. Haven't heard either way as of now.
[Captivate Android Development] swayjd:
question, from all of those, only captivates and vibrants are getting their sd cards blown right? Others just need a fresh start right?
[Captivate Android Development] Woody:
Well yes and no.

*The Vibes and Cappys (Cappies?) SD are still there, just unaccessable cause we have seen some come out of the coma.

*The Transformers were able to get back to "normal" by using the SuperWipe and SuperWipe lite from this OP (it is at the bottom of the link for that ROM but works on all TF ROMs-WDustin1 should know about this too, as he has a TF101). Otherwise their internal (/data/media) was locked up just like ours. Might be something to de-construct from the SuperWipe scripts maybe?

*My wife's Nook Color was an exception because I was able to pull the bootable SD card where the encryption was and reformat it completely and then re-burn the ROM img on it. (Btw, since then, she won't let me do anything more than maintenance on her tablet. "You want to screw around with that stuff, do it on your own device." She is savvy enough that she can get aways with that. One of the rare spouses who knows what a kernel is or an custom recovery/ROM. Keeper).