[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]

Search This thread
By:
Advanced…
crt60

crt60

Senior Member
Jan 31, 2008
1,153
2,755
St. Louis
greygoose425 said:
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
Click to expand...
Click to collapse

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.
 
Last edited:
  • Like
Reactions: Woody, daskanda and greygoose425
DerTeufel1980

DerTeufel1980

Inactive Recognized Developer
Jul 31, 2011
10,368
27,668
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.

Sent from my GT-I9000 using Tapatalk 2
 
  • Like
Reactions: daskanda
swayjd

swayjd

Senior Member
Aug 10, 2011
271
39
Dublin
crt60 said:
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.
Click to expand...
Click to collapse


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?

Sent from my SGH-I897 using xda app-developers app
 
billyjed

billyjed

Senior Member
Jan 29, 2012
384
113
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.

Sent from my SGH-I777 using xda premium
 
TheSchatz

TheSchatz

Senior Member
Apr 3, 2012
263
120
DerTeufel1980 said:
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.

Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse

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
 
crt60

crt60

Senior Member
Jan 31, 2008
1,153
2,755
St. Louis
swayjd said:
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?

Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse

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.
 
Last edited:
  • Like
Reactions: simple man, daskanda, melvinaury and 1 other person
Woody

Woody

Retired Admin - Vacationing in Nanda Parbat
Nov 18, 2010
8,842
16,519
Immersed in Dark Matter
@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.
 
Last edited:
  • Like
Reactions: daskanda, 4-2ndtwin, crt60 and 2 others
swayjd

swayjd

Senior Member
Aug 10, 2011
271
39
Dublin
Woodrube said:
@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.
Click to expand...
Click to collapse


question, from all of those, only captivates and vibrants are getting their sd cards blown right? Others just need a fresh start right?
 
Woody

Woody

Retired Admin - Vacationing in Nanda Parbat
Nov 18, 2010
8,842
16,519
Immersed in Dark Matter
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).
 
Last edited:
  • Like
Reactions: yosup, daskanda and 4-2ndtwin
swayjd

swayjd

Senior Member
Aug 10, 2011
271
39
Dublin
ChrisCTX said:
Galaxy Tab (the original), specially CDMA (Sprint / Verizon) variants suffer from it a lot, a couple of people are "working" on a external booting kernel image, but non have delivered so far...
Click to expand...
Click to collapse

Can you be a tad more specific? Suffer how? Anyone has gotten his internal storage permanently unusable? Like it happens with the captivate.

Sent from my SGH-I897 using xda app-developers app
 
J

jcjcc

Senior Member
Sep 13, 2010
90
34
Woodrube said:
@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.
Click to expand...
Click to collapse

Hey Woodrube, anyone on the reference thread report a fried internal SD on vanilla CM9 with no custom kernel?
Just a thought, but CM9 was about when everybody's custom kernels started doing LiveOC... e.g. dangerous messing with internal voltages.
(I know I had an epic 130% stable live OC going on my phone before the sdcard died...)

Also, in the entire course of the thread, has anybody ever grabbed a logcat right at the moment the screen dims and the bootanimation starts looping (then, when you reboot you get EU)? I feel like that would be an extremely crucial clue (although difficult to obtain) and I don't think we can do anything but conjecture unless we have that log.

Re: people abandoning this problem, yeah, it's very frustrating, and it's been going on for such a long time that most people have moved on (including me, I wish the One X had more development though). My captivate is still a very good backup device and saved my skin in Japan (where docomo does imei filtering... yikes, and here I thought at&t was bad).
 
R

ReDaved

Member
Mar 19, 2011
41
5
Sequoia
file structure question

Ok maybe this is lame, and this is how it always is...

I have a path of /sdcard
and a seemingly identical path of /mnt/sdcard

Are these the same thing, copies, or is this the crapped EU fix trickery.

I've had issues with heat, crashing, and have had difficulties getting things back up and running, but it's running now...

thanks!
dave
 
Woody

Woody

Retired Admin - Vacationing in Nanda Parbat
Nov 18, 2010
8,842
16,519
Immersed in Dark Matter
ReDaved said:
Ok maybe this is lame, and this is how it always is...

I have a path of /sdcard
and a seemingly identical path of /mnt/sdcard

Are these the same thing, copies, or is this the crapped EU fix trickery.
Click to expand...
Click to collapse

They are the same thing. #nosorcery

jcjcc said:
Hey Woodrube, anyone on the reference thread report a fried internal SD on vanilla CM9 with no custom kernel?
Just a thought, but CM9 was about when everybody's custom kernels started doing LiveOC... e.g. dangerous messing with internal voltages.
(I know I had an epic 130% stable live OC going on my phone before the sdcard died...)

Also, in the entire course of the thread, has anybody ever grabbed a logcat right at the moment the screen dims and the bootanimation starts looping (then, when you reboot you get EU)? I feel like that would be an extremely crucial clue (although difficult to obtain) and I don't think we can do anything but conjecture unless we have that
Click to expand...
Click to collapse

There was some mention not too long ago about overclocking to higher CPU frequencies essentially frying the internal chips but nothing ever came from it. Makes sense about the relationship to CM9 and it variants but Cyanogen himself gave up on this bug too (there is a link buried in here somewhere) .

But you do bring up a good idea/plan. I wonder if anyone who already has the EU and done the work around has tried to capture a logcat? It would have to be done on a PC with ADB.

Can someone with ADB try this? Power down and pull your external SD (presuming the fix has already been applied to the vold). Fire up ADB and get a logcat running. Plug in your phone and power it up (phone doesn't need to be on before to have ADB recognize it). Since you pulled the external you should get the EU bug straightaway. Catch the log, save it and post here. Then you should be able to put your external back in and it would be business as usual.
 
  • Like
Reactions: yosup, daskanda and 4-2ndtwin
A

ableeker

Senior Member
Nov 20, 2010
239
34
I have a Galaxy Tab 7 (the original), and I have seen the EU screen numerous times when I was running ICS (a modified beta CM9, and for a short time an AOKP). The EU screens were annoying, but I wasn't worried at the beginning, because all it did was wipe the phone, like a factory reset. However, they seemed to occur more and more frequently, so I got a bit worried. More so because I wondered why I sometimes couldn't flash back to stock, and failed while it was flashing the hidden file. Last time I was running an AOKP, when I rebooted it because GPS wasn't working. I got the EU screen again, and being sick of the screen decided to flash to an unofficial CM7 that was being created for the Tab. I restocked to Froyo, because I have a version that's recognised by Kies and will update to GB over the air. This time however, the OTA update failed, and Kies suggested to do a emergency recovery. Luckily this worked after some tries and I was able to flash CM7. This was a month ago or so, and I started to look up this phenomenon, and then I really started to worry...

So yes, it only happens on ICS, I have had no problem whatsoever with CM7, even though I flash newer versions almost weekly. And no, the EU screen hasn't permanently damaged the internal storage, even though I've seen it a dozen times so far. It "just" does a wipe. However, I am inclined to think it may damage the internal storage if I keep running ICS. This is just a gut feeling though. I do wonder though, because I've seen reports on the Tab's forum where people are having problems like internal being storage being read only, and flashing failing that sure looks like it's caused by internal storage being damaged...

I also don't think it's caused by pulling the Tab without unmounting it first, at least not in my case. I've been running and administering Windows and Linux computers for literally decades now, and I never pull a device without unmounting it. It's ingrained in my system.

I have read here somewhere that ICS uses a storage command that GB never has used, and that the new command triggers a bug that's present in certain versions of the controller. And that Google and Samsung know about it and have acknowledged its existence. Has that come to something?

I'm hoping this bug has been solved in Jellybean...
 
Last edited:
  • Like
Reactions: Thunder22, Woody and yosup
yosup

yosup

Senior Member
Dec 9, 2011
559
509
ableeker said:
I have a Galaxy Tab 7 (the original) ...
Click to expand...
Click to collapse

Thanks for the detailed comment. It's good to see SGT7 added to the knowledgebase here. Btw, are you using the CDMA (VZW/Sprint) or GSM (P1000) version?

What puzzles me (about the SGT7) is a lot of CDMA 7" Tab users were reporting mount failure issues in recovery ... and many posts without any mention of the EU screen.

Typical example:
rlund said:
... SPH-P100 (Sprint).

... Here's the issues:
- Continuous loop of Samsung logo on boot
- From Recovery screen, I performed a factory reset, but it didn't help - same logo loop
- In the Recovery screen, I get errors similar to the ones quoted above:
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory) ...
Click to expand...
Click to collapse

Then consider djmikebrady's post mentioning he had never rooted or flashed his "stock" rom:

djmikebrady said:
My P100 started this problem last night, which was the first time it's been turned in in several days. It's fully stock, never had any rooting or flashing performed on it.

Booting into recovery mode shows failed mounts on everything it tries to do, and all the options for recovery also fail - except for "reboot system now", which does reboot it, but then it just sits on the pulsing Samsung logo endlessly. And I do mean endlessly, I let it go four hours last night, after which the battery ran out. Plugged it in after that, and it's right back to the same thing.

Every other thread I've found with this problem listed it as an after-effect of having attempted to flash a new ROM, but that is not the case with mine ...
Click to expand...
Click to collapse

I wonder if something more extreme is happening in the SGT7's??
 
  • Like
Reactions: Woody
T

trevd

Inactive Recognized Developer
Jul 19, 2011
895
1,271
Hull
Samsung Galaxy Tab 4
yosup said:
Thanks for the detailed comment. It's good to see SGT7 added to the knowledgebase here. Btw, are you using the CDMA (VZW/Sprint) or GSM (P1000) version?

What puzzles me (about the SGT7) is a lot of CDMA 7" Tab users were reporting mount failure issues in recovery ... and many posts without any mention of the EU screen.
....
I wonder if something more extreme is happening in the SGT7's??
Click to expand...
Click to collapse

Hi Folks,

Here's my thread from the Galaxy Tab Forum Which Worked Around Internal SDCard Damage [FIX] [UPDATED] Internal SDCARD Damaged Essentially it's the Same as the OP,
Thought I share it as reference,
The Error was this:
Code: 
mmc0:* error -110 whilst initialising MMC card.
Which I took at face value as an hardware failure and I thought no more about actually "Fixing" the Internal SD.

I would think it is "Something more extreme" on the SGT7 because the problem ( dmesg ) manifested it self long before ICS in the Summer of 2011. It just took me a while to learn how to fix it :) , Plus it seems the EU srceen is more a symptom than a cause.

I'm purely throwing in my 2cents worth as I own neither device ;
If as Some have suggested that the hardware is pyshically still good, than the problem is no where else than the kernel. That gives a couple of options.
1. Adjust / patch the IO Scheduling on the mmc driver Here is an example of something similar done with the Rasperberry PI
2 Fully back port the mmc drivers to the devices kernel, Probably not a trivial task as internal structure and privates api's tend to be pretty fluid in the linux kernel. The arm code for the mmc driver is here for anyone whos curious.
3. Upgrade Your devices Kernel to the Latest Stable or somewhere close. The that end Google have a 3.4 tree that from how I understand it has had the android patches applied to it ( GoogleSource ) you would than need to apply samsungs patches and make sure you have the correct board configs etc but it might be a "goer"

Building Custom Android Kernels is something I'm currently researching, Although It's not something I have any level of knowledge In really and when I say "Custom Kernels" I'm talking about applying the Android patches etc to a Vanilla Kernel, Not downloading a devices Kernel Source grabbing a /proc/.config.gz and running make menuconfig. ;)

Hopefully that's some food for thought and I've not grabbed the stick by the wrong end
 
Last edited:
  • Like
Reactions: Woody, yosup and daskanda
A

ableeker

Senior Member
Nov 20, 2010
239
34
How silly of me, I never mentioned that! Mine's the GSM P1000, the one used in Europe, the one that has phone functionality. It's a P1000 meant for The Netherlands, GT-P1000CWAPHN. The latest official Samsung update was to Gingerbread 2.3.6, P1000XWJQ8, modem P1000XXJPZ, CSC P1000PHNJQ1. After that I've been running mainly modified CM9 beta builds.
 
M

matase

Senior Member
May 19, 2011
362
8
any way to do this without an sd card?I don't have one and don't feel like ordering it online because it would take a few days to get it shipped.
 
You must log in or register to reply here.

Similar threads

atinm
[ROM][ICS][IML74K] teamhacksung's CM9 ALPHA for Captivate (BUILD 17)
Replies
7K
Views
2M
RootTheMachine
RootTheMachine
designgears
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
Replies
2K
Views
2M
carbon12
carbon12
designgears
  • Locked
[ROM]Cognition v2.3b8
Replies
13K
Views
2M
LMSarmiento
LMSarmiento
atinm
[NIGHTLY][ROM] CyanogenMod 7 for Samsung Captivate (captivatemtd)
Replies
13K
Views
3M
ajeesh vijayan
ajeesh vijayan
designgears
[ROM][2.2] »» Cognition 4.5.3 «« | The Original Captivate Rom
Replies
7K
Views
1M
Avikar
Avikar

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 40
    C
    cgugino
    Note: This guide is geared toward the Samsung Captivate. If you have a different device, try your device's forum, or search this thread.

    Are you using ICS and pulled your phone out of your pocket only to find that it had this screen, saying "Encryption unsuccessful" and your only option a button that said "Reset Phone"? Don't press it! Try rebooting a few times with your external sdcard out first. Sometimes that will fix the issue. If not, take a deep breath and follow the guide below to get your phone usable again:


    IMG_2301.JPG
    Too late? Already hit the button? Then you know this screen:
    image


    Here's the bad news:
    Your partitions for /data and /sdcard are no longer accessible. Latest news points to a bug in the firmware for the memory card in your phone. ICS uses a new function that doesn't work correctly with the affected phones.

    Good news:
    I found a *workaround* to get my phone to at least work again. Note: You will need to perform steps 9-11 every time you flash a ROM or ROM update, because flashing overwrites the vold.fstab file.

    Here were my steps to get your phone working again:

    1. Realize that you may have just lost whatever was on your sdcard and it's your own fault. For me, this was acceptance that *I* installed ICS on my phone and now CWM backups, photos, and more were gone. Once your realization has set in, move forward.
    2. Acquire an micro SD card that you will put into your phone. This will contain your new /data partition as well as your new /sdcard partition. I recommend at least 8GB. If you already have a card, backup whatever is currently on your micro SD card - you *WILL LOSE* everything on this card in the next few steps.
    3. Boot into clockwork mod, using either 'adb reboot recovery', or some other combination of buttons.
    4. Partition your mircosd card through CWM. This will be 'advanced' then 'Partition SD Card'. The first size you choose will be the size of your /data partition. I have a 16GB card and chose 2GB for /data. This will leave me with (16GB-2GB) 14GB for /sdcard. You can choose a different size if you like, depending on how big you want your internal data partition to be. Choose 0M for swap. This process will take a few minutes, so keep waiting, you impatient jerk.
    5. Download the latest build of ICS for your phone and put it on your micro SD card. (You can mount it to your computer at this point in CWM with 'mounts and storage' 'Mount USB storage')
    6. Create a full backup. Just in case. Put it on a computer, dropbox, whatever. Your phone isn't a safe place for backups.
    7. Wipe user data, cache, & system. Now install the ICS package you just put on your card and reboot.
    8. The first boot will take a while, as all first boots do, but after a while you should be back in ICS. Exhale (If you're not exhaling at this point, post something in this thread and I or someone else will help get you running)
    9. Check Settings > Storage and see if your new /sdcard partition (For me it was about 14GB) shows up as 'USB Storage' or 'SD Card' If it's USB storage, then your micro sd mounted to /sdcard successfully and you're done. You should be able to take a picture and have it save. If not...
    10. Edit etc/vold.fstab with whatever you use personally (root explorer for me) and swap paths for /emmc and /sdcard (the part that starts with /devices/platform...). Someone more intelligent than me can probably make this a CWM zip. This step is telling ICS to swap your /sdcard (broken internal sdcard) and your /emmc (working external sdcard). It will probably look like this when you're done:

      Code: 
      # internal sdcard that is no longer working
dev_mount emmc /mnt/emmc 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0

# external sdcard
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
    11. Reboot with your new vold.fstab and check your storage amount in ICS and test your camera (easy test to see if Android can write to the sdcard). Hopefully now this is working for you.

    Let me know if you have any questions or (hopefully not) problems!


    Notes for myself and devs:
    ICS is a lot pickier about mounting filesystems, and if it can't mount /data correctly, it assumes it is encrypted. It really isn't, firing off https://source.android.com/tech/encryption/android_crypto_implementation.html an misleading encryption message.

    In ICS and in CWM, when I look at /dev/block/platform/ I only see s3c-sdhci.2 and s5pc110-onenand. The s3c-sdhci.0 block is missing completely. I'm not sure how to even touch the /data or /sdcard filesystem at *ALL*

    Oh well.
    View
    16
    F
    FocuseD83
    May have found a glitch solution, or an anomaly

    Uhhh guys, I had something weird happen... I encountered the dreaded encryption unsuccessful message over a month ago. Since then, I used this OP to create a partition on my external sdcard. Anywayz, I was experimenting with a B7 version kernel I kinda edited, (just placed the boot.img i extracted from Doc's Master Rom and put it in a B6 zip). It resulted in having all the B7 settings, but the clockwork recovery looked like normal cm9. Well, today, I was going to flash a gps fix zip, so i go into recovery and to install zip from sdcard, and I saw all of my old files!!!!!!! They are still there!!!! So I reboot, and it says that its upgrading, like i wiped the cache or something, and when I fully reboot, I get some conflicts and apps not working (also wifi not working). I then reverted the etc/vold.fstab to what it originally was and rebooted. My old stuff is back! My phone was borked over a month eazy, maybe 2. But this may mean its a software access problem, but all my files are back, that may mean that all phones data is recoverable!!! I will update with any new info i get. :eek::eek::eek:

    edit: wifi working again too
    on i897 bootloaders
    Slim 3.5
    View
    13
    F
    freshjr
    In another thread, they found the cause (and a potential solution) to seemingly the same issue we are having. The issue was acknowledged by sprint, samsung, AND even google. Everyone was involved because devolperes were trying to contact everyone so the bug information could reach the proper place to get corrected. This bug was even present in OTA ics releases. More on this later since there could be two different bugs (or maybe they are the same bug). This effect of the bug depend's on what EMMC firmware the phone contains. We have the fireware that locks up the card :mad:.

    Here is my summary on all the information I have read scattered EVERYWHERE on the issue. I hope it helps some dev. I do not have the knowledge to further apply it.

    The Issue:
    The issue we are seeing is that the EMMC is locking up when being accessed. This happens only at certain portions within the EMMC card.

    The Cause

    The lockup is happening because of a wear leveling algorithm bug inside the EMMC firmware.

    Some background:

    Inside flash memory, each bit can only be written a finite amount of times before it goes bad. Because of this flash manufactures spread writes all around the card to level off the wear and extend life.

    Inside conventional harddrive's writing new data by rewriting existing data or writing the new data to emptied (zero'd) data happens at the same speed. But inside flash memory, it is faster to write to zero'd data than existing data. The issue now is wheter the OS should handle where all data is exactly written to, or will it cooperate with the embedded controllers and let some operations occur low level.

    Developers have found that the issue is most likely coming from the kernal changes in ICS that deal with how files are deleted on the EMMC card. The kernal itself is not buggy but the low level firmware in the EMMC card that handles file operations is.

    It is speculated that the TRIM command and even the MMC_CAP_ERASE command are the ones triggering the issue. Older kernels such as (GB, etc) didn't support these commands.

    It is also said that the I9100 ICS kernel doesn't support the TRIM or ERASE commands either. Mabye for now we should try switching to this kernal for our ICS builds?

    The issue expanded

    It is said that on EMMC cards that have firmware 0x19 (hexadecimal), that when the commands above are triggered they have the potential to lockup/brick the card. We are not sure what is causing the lockup.

    For EMMC cards with firmware 0x25, samsung has coded up a fix to take care of the locking up issue but on this firmware version a potential for data curruption (on the order of 32KB) each time still remains.

    Yet these two seperate bugs may be one and the same. It could be the but it is speculated that critical data structures on FW 0x19 are being overwritten by the 32kb of zeroes and that is why the card locks up. They data structures are not overwritten by the kernel but by the low level controller due to a bug.

    We are not sure if it is the same issue in both 0x19 and 0x25, but for now we know that 0x19 locks up with those commands, and 0x25 has the data curruption problem.

    Here is a link the FW 0x25 patch provided by an engineer from google, but was coded by an engineer from samsung to fix the 32kb of zeroes issue. This cannot be applied to our 0x19 firmware version since it was coded specifically for the 0x25 firmware. Possible black hole, phone blowing up, but most likely it just wont work.

    https://bitbucket.org/franciscofranco/android-tuna-omap/changeset/cea631bdac53

    Seemingly, we just need to disable the commands to stop the issue. That or samsung fix their damn buggy hardware or invent a workaround in the kernal.

    Google says from their side, all of their code is okay and this mess is a result of samsung's buggy hardware.

    Furthurmore this issue has been pushed closer to attention to samsung and sprint. It has been brought to their attention that large files operations on OTA ICS builds such as wiping from recovery manager could also brick phones. This is because these operations execute the same commands. Sprint/Samsung has developed another patch (maybe the same one from before *I don't know*) and tested with it a batch of phones with it.

    Samsung/Sprint have tested 20 devices. 14 were with the patch, 6 were without. All 14 with the patch passed. Out of the 6 without, 4 of them bricked. All of them bricked since the error does not happen everytime the command is ran. It was done with sprint since the patch was for their epic 4g. They have been suffering from the same issue and bricking before us.


    ... Final words...

    I see all of this is a lot of progress from and a lot of positive information compared to our lack of knowledge before. It could be that we suffering from the same bug and we are seeing it officially being fixed on some models. I hope we can learn and apply their fix.

    It could be the same issue. What is see is that we are wiping using our safe non trim/MMC_ERASE commands. We are then installing the new kernal with the buggy commands. The google dev said that curruption happens in the /data location since it is the most used. It could be that its the 32kb of zeores at the wrong place locked up the card. Or something else to do with those commands locking up the card.

    On a positive note, the google dev said that he has fixed the 0x19 firmware card by doing a full wipe but he cannot release his fix without authorization since it is proprietary information. Presumably to fix, we would have to make the card enter some special vendor mode, and clear EVERYTHING, then blast it with a working flash configuration.

    As I mentioned in the previous post, firmware rev 0x19 has a bug where the emmc chip can lockup after an erase command is given. Not every time, but often enough. Usually, the device can reboot after this, but then lockup during the boot process. Very rarely, it can lockup even before fastboot is loaded. Your tester was unlucky. Since you can't even start fastboot, the device is probably bricked. :-( If he could run fastboot, then the device could probably be recovered with the firmware update code I have, assuming I can share it. I'll ask.
    Click to expand...
    Click to collapse

    I hope we can learn from the sprint/samsung released patch. Or maybe even the earlier released patch by samsung to google.

    For now, lets try using I9100 ICS kernals. (or is that what he had the whole time).
    View
    10
    azunino
    azunino
    CM9 with /data on the external SD working!

    Hi,
    finally got the time to modify and compile CM9 to use /data on the external SD. I've just installed my modified CM9 running with /data on a partitioned SanDisk class 4 SD card with good performance (off course slower than from the internal SD...)

    To those of you that have not been following this very long thread I proposed a workaround to avoid crippling our phones with ICS: forcing CM9 to use /data on the external SD instead of the internal. In this way I hope the EU bug will corrupt/break the external SD instead of the internal. Considering that my patched CM9 does not even mount /data on the internal SD and mounts the external SD FAT partition as /sdcard, it does not even require the internal 16GB FAT partition... well in theory it is less likely that the EU will kill the internal SD...

    Tomorrow I will post a new thread with the hacked CM9 and some short instructions to make it work. Keep in mind that I have no idea what I'm doing since I'm not a developer and I've asked around, but I did not receive any technical feedback so far.

    The sad news... it is not possible to use any other kernel with my modified CM9 because AFAIK the mapping of /data -> external SD is part of the kernel boot.img... In theory it is possible to extract from a boot.img file the init.rc file with the mappings and modify it, but I have not idea how (some help devs?). Well, if we can solve that, I can write a shell script to convert any(?) ICS based rom or kernel and modify it to use /data on the external sd.

    Going to sleep now
    View
    10
    Woody
    Woody
    swayjd said:
    I think we should find a way to raise awareness for this issue. tons of people running around completely oblivious of how serious this is.

    I used ics for a couple months before learning about this, quickly rolled back cause I'm not one to play with fire.

    ROM threads have the responsibility dump in big bold letters as we all know, but they all know about this and it seems they chose to close their eyes to it hoping it goes away. A simple warning would hurt their downloads but would do wonders fire their character.
    Click to expand...
    Click to collapse

    I cannot agree more with this post and many levels.

    Once the gravity of this thing hit yours and our sides, I put a BIG FAT WARNING in my ICS install guide about it and links to this thread and on on our side. There are only a handful of ROM threads that have it acknowledged in their OPs in the Vibrant fora.

    I was thinking about compiling all our data and the stuff recently found out about TRIM,...and the things in KRock's [REF] thread and putting it together and submitting it to an XDA news writer to see if we can get something on the front page. Maybe someone out there who hardly ever reads the Cappy/Vibrant General/Q&A threads will see it and something wil go off. We have so many bright people working on this but we just can't get past the one thing that is eluding us. If we could catch a break somewhere, I have no doubt that it could be fixed. I mean isn't that what XDA is all about?

    What do you guys think about something like that? We could take all our info and dump it on them and they could write about it or we could write it and show our references (flashback to my college days :eek::eek::mad::eek::cool:).

    I have no problem writing it if you want but it is going to take some time to compile and I am sure I will miss something here or there. You could PM me post links and a *short* reason why you are sending it and then I'll put it all together and PM out for proof-reading. Will/could take a few weeks or so bc of my schedule but at this point we need more exposure. if anyone else wants to do it by all means but I agree with swayjd, it is time to get it more out there.
    View

New posts