yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] raz123:
Showpart output is present in the log posted above..

Starting at the line that says "==== PARTITION INFORMATION ===="
[Captivate Android Development] skull2040:
I followed the steps described in first post... But hell no... No change... Please help... I am lost... Partition happened and then installation was successful... STILL SAME Encryption Unsuccessful...

Thanks...
[Captivate Android Development] swayjd:
Sorry to hear that.

unfortunately no one can really help you at the moment as there is no real fix for the issue. As bad as it sounds, all you can do is wait.
[Captivate Android Development] skull2040:
Dear All,

Somebody in my cell forum... Msgd me to flash

KPE --> KPU --> CF-ROOT-KPU --> CM9 -->GAPPS

Lets hope for the best....
[Captivate Android Development] Demetris:
Report back.
[Captivate Android Development] jmtheiss:
Could you please clarify what those steps are? I'm not familiar with KPE or KPU (although I'm guessing they're some sort of ROM builds). Where can we get the files you mention - specifically KPE and KPU?
[Captivate Android Development] bballer182:
Quick Google revealed KPE is a galaxy ace S5830 ROM and KPU is a galaxy SL i9003 ROM.
[Captivate Android Development] skull2040:
U can get KPU in general forum... use this and then cf root it with Odin.. then flash ICS by dhiru....
[Captivate Android Development] raz123:
How about you stop hijacking this thread with your I9003-related posts?
[Captivate Android Development] Demetris:
I think you are in the wrong forum. :)
[Captivate Android Development] jmtheiss:
Am I correct in guessing that since there hasn't been any announcement from Adam about a full resolution for this issue that he's still working on it?

Not asking for an ETA or anything, just don't want to see this thread and issue get buried in the Development section.
[Captivate Android Development] chavocarlos:
This issue has consequences in all Galaxy S I family right?
[Captivate Android Development] swayjd:
I don't think so. At least not to the extent that the captivate suffers, internal mmc unusable. Otherwise I would assume developers would be looking at this much more seriously if i9000s were dropping dead from ICS like cappys are.
[Captivate Android Development] Happy2cu:
Read post 221, it might help!
[Captivate Android Development] ctrclckws:
Followed steps in 221.

The phone is alive, but barely usable (to slow to do anything other than phone calls)

I tried Dark Knight ICS, and I think Pinnacle 1.3 Gingerbread.

Good thing this is not my primary any more.

Edit: waiting patiently for those with more knowledge and better tools to come up with a solution, instead of a work - around.
[Captivate Android Development] cyanogen:
We were just discussing this on IRC.

What's happening is that your /data partition is corrupt. If Android is unable to mount /data during boot, and it's not wiped, it will assume the partition is encrypted and start the decryption process. You might be able to salvage it by booting into recovery and running e2fsck -f on the partition.

https://github.com/CyanogenMod/android_system_core/blob/ics/init/builtins.c#L442

There isn't a good way to know if a partition is encrypted or just corrupt to the point where it can't be mounted. All filesystems normally have some "magic bytes" at the beginning to declare what kind of filesystems they are. In the case of an encrypted partition, there is no such thing because you don't want to give away the fact that your partition is actually encrypted. An evil secret agent would just see garbage covering the entire disk, making it appear that it is useless. Android's behavior is technically correct, but not very user-friendly in the case where something goes horribly wrong.
[Captivate Android Development] jmtheiss:
This is very useful information - thanks.

Would the command need to be issued on the device inside of recovery, or would it be done via an ADB shell?
[Captivate Android Development] cyanogen:
You'd need to ADB shell into the device while it's in recovery mode. CWM has the e2fsck utility, so something like "e2fsck -f /dev/block/mmcblk0pXX" where XX is the partition number. CWM usually has the full partition list in /etc/fstab.
[Captivate Android Development] jmtheiss:
Anyone with an affected device available to give this a try?

(Incidentally, e2fsck man page.)
[Captivate Android Development] chavocarlos:
I have seen the code in github, I think almost understand (C++ and Java have very similar sintaxis), so if the issue presents I think it can be successfully avoided it flashing again another ROM with full wipe or format SD card... but in the thread saw that some people are unable to recover the phone reflashing ... or maybe they have taped "Reset Phone" button?
[Captivate Android Development] bimbim18:
1007 rev 0.4

---------- Post added at 08:07 PM ---------- Previous post was at 07:59 PM ----------

1007

Serendipity 6.4 stable for about a year

one click 2.3.4

CM 7 build 16(?) to get to 2.3.5 and get newer CWM

CM9 to get newer CWM again

Slim ICS 1.8

all within about 2 days

got the problem about 5 days in.
[Captivate Android Development] raz123:
I have yet to see evidence of this.

How do you explain that the internal SD (movinand chip) constantly responds with a busy flag when it is asked for its status, and consequently no data-exchanging mmc commands ever take place?

EDIT: Please see this post
[Captivate Android Development] s0ul_ali:
I was on ICS since 2/3 month but suddenly when I rebooted my phone error pop's up "Encryption unsuccessful" Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible................ , Reset phone. Then I went recovery and i can't access my internal SD CARD. after reviewing this Thread I understand that my internal SD card is gone until some one's found any solution. But when I was viewing Google android forum, found out this post.

Re: [android-building] Encryption unsuccessful

Probably you might have got the solution by this time but I too faced the same issue, where I used my modified xloader/uboot and kernel and was avoiding fastboot

Problem is due to cryptfs looks for another partition for footer and key initially. Generally we make two partitions 1) xloader/uboot/kernel 2) Android fs.

For disabling encryption I disabled the feature from system/core/init/builtins.c where it sets the property for crypto

In do_mount()

- property_set("ro.crypto.state","encrypted");

+ property_set("ro.crypto.state","unencrypted");

- property_set("vold.decrypt",1);

Android ICS boots without encryption on panda and on blaze-mdp.

cheers!

Source: http://android-code.blogspot.com/2012/03/re-android-building-encryption.html
[Captivate Android Development] Demetris:
Am very glad you are stepping in, in this issue.

Thing is ,android doesnt see the mmcblk0 (mmc0) as it tried to initialize the block on boot with failed 110 error.

So on /dev/block/ we dont have any reference to mmcblkxx.

We should have there:

/dev/block/mmcblk0 (movinand)

with 2 partitions on it:

/dev/block/mmcblkp1 (data) 2gb

/dev/block/mmcblkp2 (fat32) 13gb Internal SD

Would mknod command help us out in anyway?

Thanks.
[Captivate Android Development] mechanical tool:
S0ul_ali, what is the build date of your phone? (its a 4 digit code under your battery, something like 10.10). So far it looks like all failed phones have been 10.10 or older (Oct 2010).
[Captivate Android Development] mechanical tool:
What speed of micro sd did you use? I haven't seen it mentioned in this thread, but I would expect using a class 4 vs a class 10 would make a big difference in performance.
[Captivate Android Development] s0ul_ali:
1009

So what does it mean? If a Phone older then 10.10 ICS is not recommended ?
[Captivate Android Development] minotaur507:
Yes, it is older...1009 was manufactured in September (09) of 2010. 1010 was manufactured in October (10) of 2010...
[Captivate Android Development] ciwrl:
I don't think your results and cyanogen's response are all that apart actually.

From JBQ on http://goo.gl/C8Qce: "with encryption support in ICS, Android has become a lot more picky about having all the filesystems initialized with valid data, and mistakenly assumes that anything that's not zero or valid is encrypted, refusing to go any further."

Whether it is via /data corruption or the movinand chip failing to respond, the result of either in ICS would be the behavior folks in this thread are seeing.
[Captivate Android Development] ctrclckws:
Class 4, because that's what I had handy. I agree a class 10 would probably be better. Money and time. And I have a different phone for primary.
[Captivate Android Development] DaNaRkI:
No, they are very different. Cyanogen's is a case of one bad partition on the memory chip, to what raz says is that memory chip itself.

We know of plenty of reasons why people get the error, we arn't trying to figure out that part anymore. Any simple fix like what Cyanogen suggests has already been mentioned in a different way, tried and failed. We are looking for a fix for the folks remaining. The people whom there is something much deeper going on with the memory chip itself, not just a part of it.
[Captivate Android Development] raz123:
Correct.

If AdamOutler attempts the mmctest function (in the SBL) and it returns an error, we will know for certain that the problem goes beyond anything Android is causing, for this function appears to directly test the hardware without relying on any Android component/feature.
[Captivate Android Development] jcjcc:
Exactly. There is no encryption involved in this problem. The thread title is probably misleading.

Yes, it goes beyond anything Android is causing, which many on this thread still don't understand. As I mentioned I saw a few cases of defective internal SD from before ICS ever came out.

My opinion on the issue is that ICS is giving the moviNAND more voltage than Gingerbread did, or something similar, causing the chip to fail prematurely. The chip was failing (very rarely) before ICS, it's just that ICS is somehow making failure much more likely. If not the chip burning up from voltage above specs, then something else along those lines.

Alternatively, the NAND life may have run out. Remember, NAND (such as SSDs) have a limited lifetime. I can't relate this to ICS though.
[Captivate Android Development] ClubOK:
No problem. Build 1006
[Captivate Android Development] bballer182:
No problems yet for me. Flashed ICS 4 times now with about 6-7 kernel flashes. Build 1010.
[Captivate Android Development] visionlogic:
Older builds with no problems... It just gets curiouser and curiouser. Wish I was more knowledgeable and could help nail down the problem(s) and fix(es). :confused:
[Captivate Android Development] jvc73:
A worrying idea.

Running slim ics since about a week, no issues. Phone is 1007.
[Captivate Android Development] s0ul_ali:
Actually I was on ICS for more then a month or probably two & I flasded over 50 times. Never had any issue but suddenly it happens.
[Captivate Android Development] shaker2k:
What is your build number?
[Captivate Android Development] cyanogen:
Sorry, I was just giving a more general case. Obviously your issue is device-specific, probably kernel or hardware related. The root cause is still the same, though.
[Captivate Android Development] Demetris:
So Cyanogen, is there any way out of this?

Or we are stuck with it for the rest of our phone's life.
[Captivate Android Development] jgaviota:
Has anyone looked into the source code of that Reset Phone button?

If we knew exactly what actions are taken that render the movinand unusable there is a greater chance of coming up with a fix I'd think.

Another thing, is the movinand chip or the memory controller any different from the I9000's?
[Captivate Android Development] ctechbob:
1007 Build here with no issues. ICS for about 2 months now.

*knocks on wood*
[Captivate Android Development] Demetris:
It seems is a Google and samsung fault!

http://www.chainfire.eu/articles/113/Is_Google_blocking_apps_writing_to_SD_cards_/

http://www.xda-developers.com/andro...-preventing-write-access-to-external-storage/
[Captivate Android Development] DaNaRkI:
NO, wrong. ICS is messing up the memory chip, then the false encryption shows. By the time a person gets that screen the memory chip is already borked.

And, no. They are the same.

How does this relate to the problem? All this talks about is an in-ability to use the removable SD memory (/sdcard/external_sd & /emmc) not the internal one. Really all this does is give them a cover story for why Nexus phones don't have the removeable memory. And also as to why Samsung based ROMs hid the external SD inside the internal instead of giving it it's own like on ICS (ASOP).

The fact that it is read-only makes some sense, in google's mind it's meant for something like playing music from, not app use. The system-only permission works because they need it to allow saving apps to external (for old phones with a small internal). Google has shown that they don't like apps freely writing to the memory, that's why they increased the size of apps to 2GB (they say "everything you do with an app should be enclosed within the app"). Yet their system is one developers have already been using for some time now. (ie. GunBros, where you have a secondary download in-game. But this/these are outside the app and remain after the app is uninstalled.) If anyone is at fault it's the manufacturers who went and tried to add an ability without taking it up with Google first, so that Google could make core changes. And or, ignoring what ever is Google's official reason for not allowing such.

In case it got lost: How does this relate to the fact that ICS is killing the internal memory chip?
[Captivate Android Development] raz123:
It doesn't.

Lots of noise going on in the thread.

Let's set things clear: Whenever Android is unable to access the data partition (be it because of encryption gone wrong, missing/faulty SD, etc), it will present the "Encryption Unsuccessful" screen.

In the case of our Captivates, the internal SD (aka mmc0, aka movinand chip) is becoming faulty.

Once the defect occurs, the hardware damage seems permanent (or semi-permanent?). Going back to a GB kernel/BL/ROM will *not* fix the issue.

I think by now we have fairly well established that this issue is not discriminating between hardware build numbers or ICS ROMs. I'd ask that people please stop posting that they are/aren't affected by it.

Oh, and demetris_I, please stop posting nonsense.
[Captivate Android Development] jcjcc:
Hopefully we'll be able to find the change from GB to ICS that causes this, and get it merged into CM9.

Exactly! In the case of this issue, whether or not you press the Reset Phone button is of no consequence. I never pressed the Reset Phone button. What the button does is try to format /data -- impossible because /data is inaccessible. The button does nothing.

There is way too much noise in this thread, it would be VERY helpful if everyone would read raz's post before replying (or someone start a new thread?).
[Captivate Android Development] visionlogic:
Does it still appear to discriminate between ICS ROMS and GB ROMS, with the likelihood of borking being greater with the former than the latter? Or are there too few data points to make such a determination? Serious question, not intending to be a smartass... just wanting education.
[Captivate Android Development] lowgoz:
This is how i fixed mine:

for future users who have this problem

1) get into ADB and mount your SD card as your Data partition:

ADB Shell

# mount /dev/block/mmcblk1p1 /data

This will make your SD card readable

2) download superwipe http://xda3.androidrevolution.nl/db_...ull_EeePad.zip

3) push superwipe to your sd card

adb push superwipe.zip /data/media/superwipe.zip

4) run superwipe from your CWM - it should be able to access your SD card now

5) push a stock rom to your SD using the adb push method above. Flash said rom

6) TF101 now works as advertised!
[Captivate Android Development] swayjd:
Noise or no noise, ICS is breaking phones. Doesn't really matter if the average Joe knows exactly what's happening. Wether or not pressing the Reset Button actually changes anything is of no relevance when the phone is broken for good.
[Captivate Android Development] mechanical tool:
I don't remember seeing anyone affected who was running newer than a build 10.10 phone. I could have missed it though with all the noise.
[Captivate Android Development] jeff.leonard:
Warning: Quoted post is more NOISE!

If your device actually had this problem you couldn't communicate with the internal SD; regardless of any application to include superwipe. It is not responding to requests at the hardware level, period.

I'm not saying you didn't fix your tablet with superwipe; just if you did it didn't have this problem.
[Captivate Android Development] gilpdawg:
That guy had the issue on a TF 101, not a phone. As I also have a TF 101, I've been watching that thread as well. It seems to be repairable on that tablet, and probably not the same issue Cappys are having, but I don't know that for sure. Be careful using that advice, as it's not our device.
[Captivate Android Development] s0ul_ali:
When I did #mount/dev/block/mmcblk1p1/data it says not found then I used adb oush/media/superwipe.zip it says .... in 0.450s. but still CWM could't found my internal SD card.

---------- Post added at 12:00 PM ---------- Previous post was at 11:42 AM ----------

I think TF101 is having a different issue, as in captivate's case we can't access internal SD card probably due to hardware failure .. and external SD card is only way out.
[Captivate Android Development] raz123:
I was expecting AdamOutler to update this thread with his results, but since he hasn't, I'll spill the beans:

1. He was unable to fix the internal SD/MMC issue of the device sent to him.

2. The "mmctest" command present in the SBL returned an error.

This means that the missing internal SD cannot be restored with an Android patch/fix.

At this point, the only "fix" is to use an external SD card partitioned as per OP.

Alternatively, there might be a chance of hope with this method:
[Captivate Android Development] jeff.leonard:
I've been looking for his update, that is terrible news.

The next logical step for this thread is to figure out what is actually causing it. Does anyone have any progress in that area?
[Captivate Android Development] kind3rgarten:
10.12 here.

Just happened. Turned on Wifi-AP to make myself a hotspot for my laptop, put the phone down and tried to use the internet on my laptop but it wouldn't load anything even though it said it was connected. I then picked the phone back up and realized the Cyanogenmod boot screen was up(phone crashed). I thought nothing of it and just thought it was a crash from overclocking.

After rebooting...

I got to a encryption unsuccessful/reset prompt, pulled battery and tried to Odin back with no avail.
[Captivate Android Development] Wdustin1:
So with people's phone just dieing out of nowhere it may just be hardware :( that SUCKS

Sent from my AOKP Captivate.
[Captivate Android Development] visionlogic:
:eek: Not good at all! So sorry you've suffered this.

I've got 1012 build also. Been relishing SlimICS on it. But I can't take the chance of rolling those dice anymore.

Adios ICS goodness - I've just now completed a nandroid restore of CM7.
[Captivate Android Development] raz123:
Not so worried about the lost files, but sucks that the internal SD would suddenly appear dead.

1008 rev0.4 here, no warranty.

I'm fairly confident that this is a software issue; in which case the "unbrickable mod" could restore, wouldn't ya think, or does that method not take care of formatting/partitioning the internal sd? (noob here, if you couldn't tell)

I was running CM9 build15 and Glitch V14B at the moment it happened, had OC enabled. Pulled it out of my pocket, reset, you know the rest.. have tried countless things.

EDIT: *Looks* like the "UnBrickable Ressurector" uploads the code that puts you in "Download Mode", after which you can use Odin/Heimdall. Doesn't seem like it does any work on the internal sdcard, and thus wouldn't be useful for our cases. Will contact the author to confirm.
[Captivate Android Development] cgugino:
I agree that something on the software side triggered this, but I can't say what. If you look at /dev/block/platform/ on a working phone, you will see 3 entries. On our phones, there is one missing (s3c-sdhci.0).

We would probably have to look into the core kernel to see how these block devices are populated, to see if we could recover them somehow.

No ODIN or Heimdall packages even touch the /sdcard partition with the exception of an ODIN Master Clear. I don't remember trying that, actually. Care to give it a shot? You'll need to be fully booted up into Android with USB debugging on, if I remember correctly. Note: This may just end up wiping your external sdcard, so back EVERYTHING up. :D
[Captivate Android Development] raz123:
I remember seeing another member here post something about using "Master Clear", but it won't work in my case because the phone does not even make it to Android.. This is the member, check out his posts (I believe you already have, seeing by your replies to some of his posts): http://xdaforums.com/search.php?do=finduser&u=3682535

If you can guide me into making it to Android, I'd happily give it a shot :P

EDIT: Seems to be happening on more than just the Captivate: http://xdaforums.com/showthread.php?t=1264603
[Captivate Android Development] cgugino:
Did you try the steps in my original post?

Can you get to CWM? If not, what *can* you get to?
[Captivate Android Development] raz123:
Alright, I got "Darky's ROM Resurrection" to install.

I'm now in Android and no internal sdcard is mounted.

I enabled debugging and ran Odin's "Master Clear".

Internal card still not enabled :\

EDIT: I wonder how Samsung's Kies (update utility) would fare?
[Captivate Android Development] ursubpar:
Would this issue only occur on encrypted phones? or is this issue present on all devices (encrypted or not)?
[Captivate Android Development] raz123:
The issue happens by itself, without a request for encryption ever being submitted.

The common factor across all phones that have had this issue seems to be:

- CM9 Alpha

EDIT: As more and more people join the club, perhaps CM9 devs will have a look at the issue..
[Captivate Android Development] ursubpar:
Should I run into this situation, would the recommended way to fix is to:

a. reboot without external SD as stated in OP, or.

b. Factory reset through CWM

Can't live without internal SD so I need to be careful on CM9.

Sent from my Vibrant on ICS.
[Captivate Android Development] raz123:
I don't know if continuously rebooting like OP suggests works. It didn't work for me (and I did not have an ext SD to begin with).

Factory reset didn't help my case either.

I had to follow OP's instructions of using an ext SD to install and run the OS on. The internal SD is invisible to the OS.
[Captivate Android Development] ursubpar:
Alright man, thanks for the info.

Flashing to CM7 skangs later, will flash back to CM9 when this issue is cleared.

Take care,

-Phillip
[Captivate Android Development] spalding1028:
Not to derail the thread, but I've got the new transformer prime and it's giving me the same issues. I'm running stock 4.0.3, sometimes it powers off and restarts fine, but other times it will give me the encryption unsuccessful message. I'm taking a wild guess here and saying it's either cyanogenmod and asus' ROM building skills, or Google borked ics
[Captivate Android Development] raz123:
In our cases, the internal SD partition gets completely lost (and becomes invisible to the OS).

I haven't seen this problem with the 'other' (ICSSGS) ICS build, so I blame it on CM9, for now.
[Captivate Android Development] RichMD:
Has anyone seen this issue on Cappy ROMs other than CM9 Alpha? I thought it had happened on others like DemonWav's, etc so I have avoided ICS ROMs until they mature a bit. A search of the forum only shows hits for this thread and CM9 Alpha so it appears to be true.