yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mmalka:
Same problem, with JB

Last Saturday afternoon I decided to update the ROM on my wife's Captivate. It was running Hellybean 20121006 and I flashed Hellybean 20130215. Everything went well, I updated GAPPS and a few apps.

The phone was working fine, and stayed on all night long, in the cradle. Sunday morning, it was working and in the afternoon she took it and left. When she came back she told me the phone was not turning on. Indeed, it only turned on after I removed the battery and put it back (later on I realized it was on, but nothing showing on the screen). Then it booted directly into recovery mode and when I tried to reboot, nothing happened.

Thinking the problem could have been a bad flash, and since it was already in recovery mode, I decided to reflash the ROM. For my surprise, it was not there. It looked like as if everything had been erased.

I then put the ROM on an external microSD card, and tried to flash it from there. Did not work either. It gave me a message like "your storage not prepared yet". I then put it in download mode and tried to flash it back to stock (Froyo 2.2). Odin worked but the phone would reboot, show the AT&T splash and then power off.

Next I tried to flash an old Gingerbread ROM with PIT and bootloaders. Odin worked again, but the phone booted into recovery mode and again gave me a bunch of messages starting with "your storage not prepared yet " instead of actually installing the ROM.

Until then, I had no idea of what was going on. I posted the problem on the ROM's forum and someone pointed me to here. After reading all the 1000+ posts here, I understand that I am one of the few "lucky" ones able to get the problem with a Jelly Bean ROM...

I don't know if the phone ever showed the encryption message but it does not matter. I was able to implement the workaround posted here and now it is working off a 16Gb microSD card (class 4).

I installed Slim-I897-4.2.1.stable.1.0-OFFICIAL and the phone seems to be even faster than before (may be the placebo effect).

I hope some day the internal sdcard will resurrect, but I am not holding my breath.

A big thank you to everyone in this thread that contributed to the discussion and to the workaround.
[Captivate Android Development] leezrd:
Don't feel bad I'm the first one I know to get it on jb... I am waiting to... the lazy bug bit me bad and didn't back up my sister wedding photos..lol
[Captivate Android Development] BxingFetus:
I would like to bring attention to Josh @ mobiletechvideos.com he seems to be in the beginnings of repairing emmc chips in phones. For those hit, check it out.

Sent From The Land Of Frag
[Captivate Android Development] Demetris:
http://www.mobiletechvideos.com/blog/2013/02/24/full-blown-emmc-chip-repair-coming-very-soon/

You don't have to put new emmc, all is needed is take out faulty one put it in a device that can have example usb connection to pc format emmc in whatever filesystem put back on phones board flash phone with odin with rom and pit, repartition checked.

You seem to miss the point. How much for all this to happen and how much the phone cost today. :)

So is for newer phones only that cost much more than SGS 1 Line.

So SD card method is here to stay!
[Captivate Android Development] Bane99:
Decided to flash an ICS ROM on a whim, and got the encryption unsuccessful message. Didn't know this topic was here and pressed that button.

Either way, used my jig and went back to KK4. Don't seem to have any problems with the internal storage and ROMs install fine. Phone is slightly more laggy than usual, but could just be in my head. Hope to not have any issues with internal storage. If I do, then I know to come back here and use a microSD :)
[Captivate Android Development] caddi234:
The CWM doesn´t have the option 'Partition SD Card' what should i do? What kernel to flash? I mean, i only can flash things over ODIN...
[Captivate Android Development] JoeCastellon:
I'm having the same issue...
[Captivate Android Development] DerTeufel1980:
AW: [Guide] Encryption Unsuccessful - Reset Android [ICS Issue]

Flash stratosk kernel tar by using odin
[Captivate Android Development] caddi234:
Thanks Joe, it works. I could install a ROM in the new partition, and everything looks like it´s fine. But i can´t get the phone to start, it still shows the at&t screen and then goes to recovery... Can you, or someone here, help me? :P
[Captivate Android Development] caddi234:
Can i do those steps in a Jelly Bean 4.2.2 rom? I mean i flashed "CAPTIVATING(Xperia Theme) [Milestone3]" Jelly Bean ROM and i´m wondering if the steps are the same for JB...! Thanks!
[Captivate Android Development] leezrd:
I flashed jb ROM no problem
[Captivate Android Development] caddi234:
And... Can you take photos? I cannot get the camera to work... I mean, Android can't write on external sd card... I did all the steps in the thread, but nothing... :/
[Captivate Android Development] 6mail:
Camera and Gallery did not work too... or some of software like Swiftkey. Hellybean 4.2.
[Captivate Android Development] leezrd:
Did you use ex SD switch first here for ics because jb one is different and one you need. I take pictures no problems and that one I can repost when get home around 16:30 est
[Captivate Android Development] caddi234:
Repost it, please! That fix would be awesome!!! :D
[Captivate Android Development] leezrd:
Here you go Bo just flash in recovery and good http://www.4shared.com/zip/nRa7kD-E/EMMC_Reverse_Fix_Jellybeans.html
[Captivate Android Development] caddi234:
THANKS!!!!!!! It totally works!!! :D
[Captivate Android Development] leezrd:
No problem.
[Captivate Android Development] giongto500:
You might want to double check if your internal SD card is still accessible. If yes, try taking out the external SD and flash a new rom on the internal one. If the EU screen still shows up, if the internal SD is still accessible, try reflashing the rom. That's what I did.

It happened to my Cappy a few days ago when I realized that my internal SD is back after 5 months. lol :D
[Captivate Android Development] leezrd:
Don't quiet understand what trying to say please elaborate
[Captivate Android Development] qaler2010:
Wish I could be that lucky as you...

---------- Post added at 08:42 AM ---------- Previous post was at 08:29 AM ----------

So strange, yesterday my cap was ok as usual ,but when I got up this morning and it couldn't light up the screen no matter what physical button I hit. So I did flashing but it results in nothing.

Use I897UCJF6-final-OCD-REV0 and my phone can boot up but screen comes black during boot animation

Use 3FileKF1NOBOOT or JF6_secure, my phone just gets stuck on the first boot screen

Use custom recovery, then (E:failed to mount /data (file exists) E:delete_data_files: can't mount /data your storage not prepared yet, please use ui menu for format and reboot actions)

I was not using ICS but Slim 4.2.2 without encryption, and I have done some searched and find out it is probably the problem of internal storage corrupted or ,even worse , dead.

It looks like many of galaxy s 1 users encountered this situation, Sumsang's fault?
[Captivate Android Development] leezrd:
Use this firmware http://www.mediafire.com/?ru40sbbm8n90uc3. It is ucki2 no boot loader with boot kernel then when finish flashing hold Boyle buttons till at&t then let go.. Once in recovery partition it.. Next flash the ROM u want.. It will probably reboot when it does flash it again then the jb emmc fix I posted from last page then good... Only one i can get to work for me
[Captivate Android Development] qaler2010:
Thanks for your kindness.

However , I do know how to get to recovery and flash roms. What I am really concernd about is how to get my internal storage back alive ,or at least, restore my data from the dead internal storage...
[Captivate Android Development] leezrd:
Ooh well I didn't understand what he meant and tried with no luck mabey he will elaborate better next time signs on
[Captivate Android Development] pradeeppk:
Hai,

Now my cappy running with cm.10. Internal and external SD cards are working fine. Can I use this method to avoid the encryption unsuccessful bug in my captivate
[Captivate Android Development] qaler2010:
Hell! Exactly same here!
[Captivate Android Development] beer-2k:
I had Captivating X4 with devil kernel running on my son's cappy. Yesterday I rebooted it into recovery to make nandroid backup. I was getting error mounting sdcard. Even putting an external micro sdcard was giving me error mounting. Rebooting the phone only boots into recovery mode. I used the File Manager in the recovery and sdcard folder has 0 files. Well, looks like I'm going to have to try a few stuff here using download mode....
[Captivate Android Development] fb767:
So I was able to get CM7 running as nothing else was working at all (couldn't even get Odin, error after error). And the internal memory says 0.00B, is this normal? Can't install/save anything :S.
[Captivate Android Development] leezrd:
Sound like eu bug

Edit: try flashing aokp then partition then Odin
[Captivate Android Development] fb767:
Thanks for the reply, when you say partition do I do that through CWM or through Android?

Also I can't get Odin to work, it doesn't recognize the phone when I plug it into my PC have tried my desktop and laptop.
[Captivate Android Development] leezrd:
With aokp's glitch kernel that ones cwm hot mine to partition ex-sd when the other ones wouldn't... That and corn kernel cwm. By partition I mean the part of the micro SD cart that it uses for the ROM to flash to. Once you get that partitioned and flashed you have a base to then get working in Odin.
[Captivate Android Development] ItsJono:
I'm having this issue but the weird thing is I actually have access to my internal SDCard.

Basically what happened as yesterday I flashed the newest copy of SHOstock3 for my i777, flashed Cerberus on top of it, booted up, and I went into settings so I could encrypt my phone for the first time. For some weird reason it failed and it wouldn't get past the "!" yellow triangle when booting up the phone. So I flashed back using ODIN to a Stock ROM but rooted and the phone works fine. Yet every time I try to flash SHOstock3, it fails and goes back to that screen.

I used the ADB command,

"adb shell "dmesg | grep mmc0"

and was returned with:

grep: not found
write: Broken pipe

-

So I have access to my internal SDCard as it is not entirely corrupted. In CWM recovery, while searching for .zip's to instal, it says that the path is /emmc/ so and i'm browsing it without any issue, it seems to be accurate. So i'm confused as to why this is continuing to happen.

A weird bug I noticed is that when I went back to Stock Gingerbread 2.3.6, with the phone plugged in via USB, it said "USB Mass Storage" and "MTP-Connected"... That doesn't seem right... What's even stranger is that this issue is for ICS users, but I was on Jellybean when this happened. So my problem is different yet the same?

Edit: Flashed the latest AOKP - Successfully working? Took a picture, saved successfully - Able to write to Internal SD

Edit 2: Flashing to ShoStock3-XWLSN-v3.0.2 from AOKP in hopes that having flashed AOKP successfully, may have removed invalid entries it's still referring to? -- ENCRYPTION FAILED message again. So whatever it is, ShoStock is still trying access it?
[Captivate Android Development] billyjed:
This is pretty much a captivate specific issue here. Go check the shostock thread in the I777 forum for help.

Sent from my Apple IIe
[Captivate Android Development] anwarkhan25:
Just wondering if this is a ICS issue only or can it happen on JB..? :confused:
[Captivate Android Development] leezrd:
Got mine on jellybean
[Captivate Android Development] laughingT:
Which ROM?

sent by the scare crow, tin man, and cowardly lion on the yellow brickfree cm10.1 road.
[Captivate Android Development] leezrd:
It happened back in October so don't remember specifics but was usually OK AOKP then
[Captivate Android Development] laughingT:
So, I recall reading somewhere that the culprit may have been in the way CWM builds the partitions, and that the partitioning scheme in JB and the later version on CWM make the EU error improbable.

Your the first JB case I've heard of.

We're you running ICS before JB?

Or did you come straight from GB ROM?

Thanks.

sent by the scare crow, tin man, and cowardly lion on the yellow brickfree cm10.1 road.
[Captivate Android Development] leezrd:
I think ICS but not 100% I posted it earlier in October

Edit: here is why I think might not b be why happens http://xdaforums.com/showthread.php?p=35116587

This is what I was on http://xdaforums.com/showthread.php?p=8601
[Captivate Android Development] laughingT:
You second link got clipped. Bad link

sent by the scare crow, tin man, and cowardly lion on the yellow brickfree cm10.1 road.
[Captivate Android Development] leezrd:
Sorry.... http://xdaforums.com/showthread.php?p=33278601
[Captivate Android Development] thebulletfromhell:
If I may ask a question, can anyone tell me if this problem is exclusive to the captivate, universal to the Galaxy S line or is on all ICS android device? I'm deciding between a Vibrant, a i9000 and a Captivate and this is a big game changer
[Captivate Android Development] laughingT:
Yes, vibrant, however, there is a non SD card fix for vibrant and at least one captivate user who tried it reported success, fully restoring access-

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

I'm assuming Cannondale flashed the captivate version of Semaphore.

Sent from the wholly ROMin' empire. SGH-I897 CM10.1
[Captivate Android Development] thebulletfromhell:
Thanks for the quick response. So, does any other Galaxy S variant get affected? (Like the International variant/i9000, and the various advance and plus one/i9003, etc..) I don't really want to spend more cash on a HTC with worse spec(crappy budget, I'm on a really old S60v5 nokia)
[Captivate Android Development] DerTeufel1980:
Ics is outdated compared to cm10.1 (jellybean), which does not seem to have this issue.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Captivate Android Development] gcamp0730:
Yes, I thought this as well. And then last night, while running cm10.1, my phone died this horrible death. I'm going to try some of the recovery processes mentioned in this thread and will report back with my results. For the record, I heard about this issue early on and have *never* loaded ICS on this phone. The phone went from Froyo -> Gingerbread -> JB.

Edit: And my screen never showed the EU message. I was in the process of updating apps through the store and when I looked back around the screen was black (but the buttons would light up). After several attempts to get the device to respond I finally had to remove the battery. When I put it back in the phone wouldn't boot and I couldn't get into recovery. I tried to Odin back to stock but the phone just boot-loops.
[Captivate Android Development] DerTeufel1980:
You could successfully flash stock rom by using odin? If odin didn't error out, this is another issue than the one in this thread.

Also, galaxy s variants are getting old... Hardware always can die

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Captivate Android Development] gcamp0730:
I'm not sure I would call it a successful flash with Odin. Using a link from a few pages back, I flashed I897UCKI2_Boogs_Kernel. It would boot-loop, but I could get into recovery. Then using this ( http://xdaforums.com/showthread.php?t=2210299 ) as a guide I flashed the Semaphore kernel, entered recovery, and attempted to run "parted /dev/block/mmcblk0". Unfortunately it told me file not found or some other nonsense. I tried to mount /data in recovery and was told the partition didn't exist. Both /data and /sdcard will not mount due to the partitions not existing. So next step is to get a SD card, partition it, and follow the rest of the directions in this thread for getting a ROM installed in that manner.
[Captivate Android Development] DerTeufel1980:
And what about your: odin back to stock.

Did you get an error while doing this?

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Captivate Android Development] gcamp0730:
I'm not sure what point you are trying to make. Is there some test you'd like me to perform on my phone? I've been following this thread since the beginning. And I've gone back and re-read many of the posts. As far as I can tell my experience is not different from what others have encountered: my ability to odin back to stock, /data and /sdcard not mounting in recovery, etc. etc. Following the instructions in the OP I've been able to use an 8gb card I had to get the latest cm 10.1 back on the phone, so I'm sad part of the device is borked, but glad I was able to implement the workaround.

Anyway, if there's something you'd like me to do on my phone (and show you the output) I'd be happy to do it. Otherwise let's stop with these non-useful back and forth posts.
[Captivate Android Development] DerTeufel1980:
It's long time since I was reading the thread.

I just thought, that odin would fail while trying to format data. That's why I was asking. Maybe i don't remember correctly. Sorry

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Captivate Android Development] gcamp0730:
No problem. It certainly make sense that odin (or anything else) would fail trying to format /data. I know I saw behavior like that in recovery when trying to mount /data. But I don't remember exactly what was displayed on the screen when I did a wipe / factory reset. But now that you mention it, that is strange that odin just silently skips over the fact that it cannot format /data.
[Captivate Android Development] blazedj:
Hi there!

Will it make sense if I try to flash stock image with "repartition" checked in Odin? What do you think?
[Captivate Android Development] gcamp0730:
Hmm. I'm not sure. Personally I have always left that unchecked.
[Captivate Android Development] blazedj:
In theory, this would create new /system and /data partitions but I don't see if anyone tried this yet :confused:
[Captivate Android Development] leezrd:
I think it repartitions the system data so probably won't matter... I had same problem and at first didn't say encryption error but wouldn't Mount in recovery then said that about EU bug.
[Captivate Android Development] gcamp0730:
Right, but if /data (more accurately the device behind the mount-point /data) is not accessible then a repartition won't succeed. But as long as you have a valid .pit file you should try it and let us know if you are successful or not.
[Captivate Android Development] leezrd:
I've tried a couple of times and still no go without ex SD
[Captivate Android Development] SuperKeeper:
Hey, I've had this encryption unsuccessful issue with my Dell Streak.

Now this device doesn't officially run ICS, we have a number of AOPK ports of CM9 which are mostly functional. I've never had this problem before with this ROM before and this problem was seen as I noticed the device was lagging so I decided to wipe the dalvik cache in CWM. No problems but I did notice it was slow in between menus. Upon reboot the aforementioned encryption unsucessful message which I DID click reboot.

I left it overnight as it was hot and only going to get me angry. This morning I tried going back into CWM to the android picture flashing and mirrored going mad. So I am unable to get into recovery mode.

I'm not sure what sucess other people have had on non Samsung devices but would it be worth me trying these steps? Or should I try reflashing the recovery and flashing a "normal" GB ROM?

UPDATE-

Hmm, all I did was boot my device into fastboot mode (this is for installing recoveries for the Dell Streak etc) just to check I still could. And upon restart I went into recovery mode to take a picture of the error in CWM but I found it could actually get into recovery mode! Hence I flashed a GB ROM and all is well. I did a check of the internal and external SD cards and it says all is fine. The SD card I had in the device works fine and didn't lose any data either. Odd.
[Captivate Android Development] blazedj:
Hmm, that's curious. Thanks for the info.
[Captivate Android Development] thebulletfromhell:
Has anyone considered hardware failure on the cases where the phone came back to life? Maybe the Internal SD just failed on them, leading to the symptom here, and one day it just worked again.
[Captivate Android Development] leezrd:
That Is my thoughts as well.
[Captivate Android Development] DaNaRkI:
It had been a consideration at the very beginning, but we have no means of isolating and checking the internal memory. I think it was settled on faulty design and a series of bad instructions causing the memory to get stuck.

-xda app, too lazy for something interesting to say-
[Captivate Android Development] cannondaleV2000:
Its not hardware failure. Its that the internal memory is mounted as read only. And as of right now there is no way to mount as read wright to repartition it. Same thing over in the vibrant section. I'm working on a fix for this who have it
[Captivate Android Development] mx828:
So I decided to try and encrypt my phone after thinking it was a bad idea but much to my surprise it says its encrypted! Not sure what problems everyone else is having with encryption. Hopefully I will be providing a picture tommorow because its late where I live and need to sleep. I will also say that I am not a developer and in no way did I write nor hack anything to get it to work. All I did was push encrypt on a full battery connected to the power cable as soon as I confirm after the warning it rebooted thinking I now had a big paperweight I went to my PC to look up something that might help. After leaving for no more than five minutes I come to find it on a screen asking me for my password to decrypt so I do and then the android encryption logo appears with a black background after 15 minutes of staring at it I decide to hope for the best and simply removed the power cable and took out the battery. When I put it back in it asked me for my password again after the boot screen and then it rebooted into the os where I had to again enter my password to unlock so I did and here I am.:)

Sorry for writing so much but I had to get all of the details down as I realize that this might help anyone who cares to try encrypting and also to any dev out there interested. like i said hope to have a picture or two up soon and maybe even a video showing my phone on boot unencrypting screen.

And yes I am telling the truth.

---------- Post added at 12:13 AM ---------- Previous post was at 12:01 AM ----------

By the way I have captivate sgh-i897 android 4.1.2 running CyanogenMod 10.1.2, stock kernel, stock CPU clock, stock io scheduler only weird thing that might have anything that could have affected it is that I installed the xposed installer enabled the framework and installed the fix provided in the xprivacy thread. That's all I can think of right now.
[Captivate Android Development] mx828:
some pics
[Captivate Android Development] thebulletfromhell:
Its not the encryption, which is fine. The Encryption Unsuccessful screen is a byproduct of the /data and /sdcard partition locking up, resulting in the phone thinking the data is encryption, when in reality its just locked up/the hardware failed.
[Captivate Android Development] thebulletfromhell:
Bump, since I want to ask something:

Is it possible to use the vold.fstab fix with a working Internal SD? I'd like to test out JB, but I don't really want to brick my Cappy
[Captivate Android Development] laughingT:
if i am not mistaken, the CM10 install scripts test for the internal sd fail and execute the swap if found. so if you keep a flashable CM10 zip file on your external sd, and a current nandroid backup, you should be covered. ideally, a 16 GB or larger external sd card. also periodically backup your apps, data, and internal sd contents to cloud or via usb - and you are covered, IMHO.

Sent via Monty Pythons Flying Circus
[Captivate Android Development] thebulletfromhell:
But that still leave a chance for the Internal SD borked. I want to avoid touching the Internal SD altogether. The workaround is OK, but I don't really want to cut my storage space by half.