Database Users

[newbie]how to solve frezze problem for my t-mo hd2

1.) I just bought my T-mo htc hd2 a week ago and i didnt install anything into it yet and the phone will frezze 2,3 times a day when i try to unlock it from stand by mode. what sould i do to solve this problem?
2.) If i want my hd2 can able to read and write chinese what program or rom i should put it in?
3.) If i want to put rom into my hd2 the first thing is to install hspl and then the bootloader is that right?
please HELP!!!
OS 5.2.21889
Manila 2.5.20121412.1
rom ver 2.10.531.1
radio 2.08.50.08_2
ram size 576mb
flash size 1024mb

I am having that same problem too, I feel like throwing the phone at the wall am getting really pissed about this.

I got this from the Tmobile forums
After talking with some phone tech friends of mine.... unfortunately cant say which company in Austin, TX they work for..... I found out that the first batch of HD2s that were sent out had a corrupt file in them that was causing all kinds of freez ups and other issues. They told me about how to tell if mine was in the first flawed batch or the the batches that were sent after that been fixed by HTC prior to shipping them to tmobile. Here's how to tell:
If you remove the back battery cover and look for the factory reset button which is located below the battery to the left near the left edge where the cover snaps in place, you will be able to see that it is colored. If the color of the button is red, it is part of the first flawed batch that came out. If the button is yellow or any other color then it is part of the batches that had the problem fixed before they were sent out by HTC.
I am not sure if this info has been posted yet or not but if it hasn't then I hope this may give some insight to thoes who have been having some problems with their HD2. I am just guessing that if you were to sent your HD2 back for a new updated one, that tmobile would honor this issue and exchange it for you.
Thanks for all the info that ya'll post on here, it has come in handy!
Click to expand...
Click to collapse
http://forums.t-mobile.com/t5/HTC-H...d-some-don-t/m-p/354378/highlight/true#M11337
I just called customer service and they are going to exchange my phone for me.

help
is there any more people can give me some more advise ? Cause my phone still like that keeps on freezing every single day , can someone please help . Thank you

I got a new HD2 last evening from my Tmobile store. The soft reset button on my firsrt one was red, it had HORRIBLE problems, a freakin headache. This new one has a yellow soft reset button and it crashed really bad last night after I turn it off and on. SENSI UI didn't load for like 10mins and it was glitching from Start Menu to the Sense UI menu. Ive only had the phone for 7hours, stock ROM too. This is fustrating.

mine got a red dot but it's not freezing for the past month.

I've had mine 7 days. Yellow reset button. Stock Rom.
No freezing at all. Battery sucks. I turned off a few things in Sense UI yesterday and the seems to have improved.
From what I've read, most of the freezing problems are due to the slow MicroSD or with large number op SMS or Music files.
Try taking out your card for a few hours and see if its still freezing. If it is, ask for a new card.

Do yourself a favor return the phone your still with in the 14 day period. All of these problems are Sense U.I related and only custom roms can be fixed but your warranty will be voided..I wish i didnt buy this from Ebay and bought it from a corp store, so i could have returned it..

even with custom ROM.. less freezing but yes.. usually on the texting.. i think htc just released a new tmo rom the 26

ajftl said:
even with custom ROM.. less freezing but yes.. usually on the texting.. i think htc just released a new tmo rom the 26
Click to expand...
Click to collapse
That one is for Tmo in europe, not the US, won't work on the US model. (just wanted to be clear )

ajftl said:
even with custom ROM.. less freezing but yes.. usually on the texting.. i think htc just released a new tmo rom the 26
Click to expand...
Click to collapse
that rom might kill your phone. be careful.

I called HTC and was told they know about the freezing issues.It uss with T-MOBILE HD2 only and they are working ona firmware fix. I have yellow reset button and lots of freezes. wondering off I should return this and get the Incredible from Verizon. Its Android so much better?

get a new faster micro sd that will solve your problem for sure

mumbo_jumbo said:
get a new faster micro sd that will solve your problem for sure
Click to expand...
Click to collapse
New faster? What does that mean? Are you saying to get a new 1GB microSD instead of using the 16GB microSDHC card that came with the phone?
A card isn't "fast", the thing that determines the speed of which a card can be "read" is the size of the card (32GB would be "slower" than 16GB).

Snarksneeze said:
New faster? What does that mean? Are you saying to get a new 1GB microSD instead of using the 16GB microSDHC card that came with the phone?
A card isn't "fast", the thing that determines the speed of which a card can be "read" is the size of the card (32GB would be "slower" than 16GB).
Click to expand...
Click to collapse
Actually the speed that an SD card can be read at is rated by "class" (2, 4, 6, 8, and even some at 10 now)....the higher the class, the faster it can be read from. Unfortunately, HTC saw fit to provide us with a class-2 16GB from the factory, which can contribute to a number of issues, so even a class-4 card of any size would provide better performance than that

I upgraded to a class 6 8 gb micro sd and all freezing issues have ended except for sms freezing. I hope tmobile comes up with a firmware fix for it

the ugly truth is...
HTC did not do a lot to upgrade the ROM they sent to the US. Even with having a 6 month start and KNOWING the issues and complaints they were receiving overseas. Yes, you can flash, yes there are multiple tweaks, yes the people here are great at helping. However, the basic functionality that "should" but, did not come with the phone (sms lags, music skipping, sytem crashes when using proprietary sense UI) is really quite bad. Everone does not have these problems but there are more and more people asking the same questions.
I am going to wait until T-mo and htc get their @$$e$ in gear and release a fix. No timetable yet for it, but they have heard and earfull and are doing something . Then I will flash after all the manufacturers cures are applied.

ryan562 said:
I upgraded to a class 6 8 gb micro sd and all freezing issues have ended except for sms freezing. I hope tmobile comes up with a firmware fix for it
Click to expand...
Click to collapse
Have you tried cleaning up your inbox? I had 700+ messages in there and cleaned it up, haven't had a SMS/MMS-related crash since...

ryan562 said:
I upgraded to a class 6 8 gb micro sd and all freezing issues have ended except for sms freezing. I hope tmobile comes up with a firmware fix for it
Click to expand...
Click to collapse
I too just purchased mine. Class 2 file transfer for a 16 gig card is ridiculous. For this phone anyway. Also waiting for that sms freezing fix. It is definitely swype related and for some reason, swype (unlike any other input format) needs all messages loaded prior to being able to function. Blah...these are the ONLY issues I am having with the phone. Have had it since March 25th.

kenroy112 said:
I am having that same problem too, I feel like throwing the phone at the wall am getting really pissed about this.
Click to expand...
Click to collapse
I am ready to throw it on the wall, I thought I had found a fix until the phone restarted all by itself when I was listening to music.
FTL

->[B e l l - i 9 0 0 0 M - S u r v e y]<- [Help Keep This On Front Page]

Warning : This survey is only for i9000M (Aka Bell Samsung Vibrant)
Hey,
So i know theres already another thread. Problem is, only those who have got corrupted internal sd's ever visit that thread, and hence we end up with a lot of "non working" data.
I want both sides of the story. What causes it to screw up and what causes it not to.
Ive created a form at Link
The data from the form is at Link
These questions are a lot more focussed than the ones in the original thread.
Current Maintainers in charge of modifying data upon a user-request / Keeping data clean:
wang1chung
daneshm90
Suggestions are welcome to improve the questionnaire.
Hopefully this will help us find out what is causing these corruptions.

bump... keep this on the first page so that we get more and more data entries...

Interesting poll. Hope we get a bigger data set.
Sent from my GT-I9000M using XDA App

aphoebic said:
Interesting poll. Hope we get a bigger data set.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Yea we've gotten a lot of entries so far.
So far seems as though anything through odin eventually screws up these phones :S

Replied (oops, set name as groan instead of Groaner. Owner can correct this if you want.)
Nice to see.
it seems it's all over the board and does not matter if you had made changes or not. rooted, lagfix, Rom...makes no diff. i didnt change anythign and got the problem.
At one point there were no SGS's to be found. this dry period of about 2 weeks before a new shipment came in. Could they have corrected some hardware issues for this 2nd batch (i think it was in September)?
I'd like to know how many phones after the dry period are experiencing this issue.

groaner said:
Replied (oops, set name as groan instead of Groaner. Owner can correct this if you want.)
Nice to see.
it seems it's all over the board and does not matter if you had made changes or not. rooted, lagfix, Rom...makes no diff. i didnt change anythign and got the problem.
At one point there were no SGS's to be found. this dry period of about 2 weeks before a new shipment came in. Could they have corrected some hardware issues for this 2nd batch (i think it was in September)?
I'd like to know how many phones after the dry period are experiencing this issue.
Click to expand...
Click to collapse
Im starting to consider whether those who say they didn't do nething and it still bricked have "used phones" where the previous user mightve flashed stuff.
Yea ill change ur name on it.

I added my info..and bumping the thread at the same time.

I forgot to put in other that i removed OCLF after a couple weeks due to all the problems I saw ppl were having. You can update my info if you'd like

by the looks of things, im REALLY glad ive never used odin

evil-doer said:
by the looks of things, im REALLY glad ive never used odin
Click to expand...
Click to collapse
I know eh. By the looks of it, odin screws up our phones, aside from a few odd cases where even stock phones got corrupted :S
But yea im on my 3rd sgs and im just using stock + voodoo. Gonna wait it out for froyo.

My first entry, row 52, was an error.
I repartitioned with odin last month while returning to stock JH2 from the aborted Scandanavian Froyo. No problems yet with an August 21st battery manufacturing date.

Good idea !
I've been lucky with my phone. I flashed twice with ODIN using the JH2 rom. Once with re partition and it's been ok.

From the looks of things there is no real rule as to if you flash then your phone will screw up... But seems like the chances of getting a brick increasing with flashing. If thats the case, then whats the point of having this phone... it sucks all the fun out of android (to me atleast...)

Whats the warranty on these things ?
1 yr no ???

Here are the 2 combos im interested in :
1. Has anyone bricked their i9000m using only heimdall ?
2. Has anyone bricked their i9000m w/o using odin but flashing roms/stuff through recovery (for eg Doc's rom)

from my understanding, heimdall doesn't repartition, so it would be equivalent to using odin without repartition.
i'm going to have to agree though, when i get my phone back, no more odin flashing. only clockwork. clearly, there's a pattern there.

AvatarReborn said:
Whats the warranty on these things ?
1 yr no ???
Click to expand...
Click to collapse
Yea there is 1 year warranty...

Hi everyone...I just wanted to suggest that the form should also include a manufacture date field (the battery or the phone's doesn't really matter) because if it is a faulty batch of memory (internal sd), then maybe we can pinpoint the timeframe in which that faulty batch was present. btw: my battery says 28 august.
EDIT: on #43 on the results says that the battery is manufactured in sept but the phones bought in aug... a new battery?

B-1P said:
Hi everyone...I just wanted to suggest that the form should also include a manufacture date field (the battery or the phone's doesn't really matter) because if it is a faulty batch of memory (internal sd), then maybe we can pinpoint the timeframe in which that faulty batch was present. btw: my battery says 28 august.
Click to expand...
Click to collapse
I did consider adding that before. Thing is how do you find this info ?
Are you going by manufacturer date on battery ?
Cuz in a lot of cases if sent for repair the battery is not replaced.
Also the battery manufacture date has no relation with the phone's manufacture date.

submitted.

Telus Fascinate Users - How's The Internal Memory or Other Froyo Bugs?

Hi guys my Telus version of the Fascinate is coming this week and I'm looking forward to it.
Unfortunately I had the Bell Vibrant SGS version before this phone and my phone fell victim to the infamous internal memory issue and my phone turned into a giant paperweight.
More info about that here:
http://forum.xda-developers.com/showthread.php?t=793404
Anywhoo... How is the Telus Fascinate? Any Bugs or other issues especially after upgrading to Froyo?
Thanks!...

No problems, flashed the update the day it was officially released.

Only problem I had with the update was mentioning that it existed.....
Works great on my Telus phone and I upgraded my bro's Bell phone and his works great as well. Noticeable speed up on the Bell phone (IIRC around 800 on Quadrant before the upgrade ane 850 after - still not the 1000 I get on the Telus phone....) Also really like the ability to now mount the external SD card as well as turn the data off/on with the power/side menu.

I've read that Froyo has slowed the phone down and also made GPS worse?
My experience with Froyo so far:
HTC Desire - Phone speed seemed the same and battery improved.
Bell Vibrant - Phone seemed slower, GPS still broken, and battery slightly worse.
^ (then the phone died within the week with the infamous internal memory Bell bug of death)
My Fascinate is still in transit but would you guys say that things are better, same, or worse with Froyo over Eclair on the Telus Fascinate?
*Edit* Also one more thing what are you guys using for Root since I really want to get the update and then the root hammered out on Day 1?... TIA!

^ Anyone...

I've had no problems with 2.2 other then the occasional slowdown. I think I'm lucky that my GPS has always worked... nothing wrong with my turn by turn directions. However, on maps the little blue dot that indicates where you are has always been weird.

So there is no internal SD card corruption error?
I'm thinking of selling my Bell i9000M and getting the TELUS Fascinate... the only downside is that there isn't as big a development group for the Fascinate...

slaman said:
So there is no internal SD card corruption error?
I'm thinking of selling my Bell i9000M and getting the TELUS Fascinate... the only downside is that there isn't as big a development group for the Fascinate...
Click to expand...
Click to collapse
I already went through 2 Bell phones that died because of internal memory failure I'm done with the i9000M series forever.
Anywhoo What are you guys using for root on the Telus Fascinate?...

ccrows said:
Hi guys my Telus version of the Fascinate is coming this week and I'm looking forward to it.
Unfortunately I had the Bell Vibrant SGS version before this phone and my phone fell victim to the infamous internal memory issue and my phone turned into a giant paperweight.
More info about that here:
http://forum.xda-developers.com/showthread.php?t=793404
phone is mint just foundout how o put voodoo on it
Anywhoo... How is the Telus Fascinate? Any Bugs or other issues especially after upgrading to Froyo?
Thanks!...
Click to expand...
Click to collapse
honestly i just found a way to get voodoo on my telus fascinate that i will b posting once i get 8 posts

[Analysis] EC09 SD Card Survey Preliminary Analysis

So far (as of 11AM, 7/7/11), there have been 29 unique users who have voted in this survey. While the SD card bug has not been isolated as of yet, my preliminary analysis did turn up some significant trends. The 2nd post will analyze what those whose cards are still working had in common, and the 3rd post will analyze trends among those whose cards have experienced failure.

What Those Whose Cards are Still Working Had in Common
There have been four users (as of 11AM, 7/7/11) who posted that their cards were still working when they voted in the poll, who also posted more details about their experience flashing EC09. Unfortunately, the things they all had in common were also shared with some who have lost their SD cards. Nevertheless, following their steps **may** give you a greater chance of preserving your card. First I will list what all four had in common. Next I will list what three out of four had in common.
1. They all...
...previously ran UKB (Community Rom) 2.x
...used the stock EC09 kernel that came with the original leak
...had a working stock video player (Obviously, you can't control this but if your video player is working that's at least a good sign
...had more than 4GB available on their cards
2. Three out of four...
...flashed the stock EC09 leak (no custom ROM)
...wiped data, cache and Dalvik in CWM in addition to Odin (which also wipes all three)
...restored their apps with Titanium Backup rather than reinstalling them manually through the Market
As stated before, THERE IS NO GUARANTEE THAT FOLLOWING THESE STEPS WILL PREVENT YOUR CARD FROM BEING DISABLED. For the time being, there is no confirmed fix for this very serious issue. Even though every developer reminds you that you flash their ROMs at your own risk, flashing EC09 in any form is especially risky and far more dangerous. As more results come in, more trends may come up that at least help narrow down the causes of this issue.

Trends Among Those Whose SD Cards Were Disabled by EC09
There are some notable trends among those who have had their cards disabled by EC09. In this post, I will note the things that resulted in SD card failure for everyone who did or experienced them, and I will note other notable trends. It must be pointed out that this is a PRELIMINARY analysis of a NON-SCIENTIFIC poll, so these results should be taken as guidelines, not facts or rules etched in stone.
1. Things that users did that always led to SD card failure as of 7/7/11 (please also notice the disclaimers):
...All came from NON-UKB (Community ROM) 2.x builds (even some who WERE on UKB 2.x lost their cards)
...All were either on Nameless 4.0 or TechnoROM (but some of those who used stock EC09 and Nameless 4.1 also lost their cards)
...All used the recommended CWM recoveries posted on the Nameless ROM and TechnoROM threads (by the OP). Again, many who did not use these CWM recoveries also lost their cards.
...All flashed the Nameless custom kernel (many of those who used stock EC09 kernels also lost their cards)
...All had non-working stock video players (obviously, you can't control whether your video player works after flashing EC09, and many who had working video players also lost their cards - nevertheless, if your video player is not working, I strongly recommend getting off EC09 immediately - and I hope you already backed up your SD card's contents)
...All had less than 4GB available on their SD cards before flashing EC09 (most of those who had more than 4GB also lost their cards, but having less than 4GB has so far yielded a 100% rate of failure)
2. Other trends:
...9 users lost their cards right away or within a day (I CAN'T EMPHASIZE THIS ENOUGH - BACK UP YOUR CARD BEFORE TAKING THE PLUNGE!)
...12 users lost their cards within a few days (even if you didn't lose your card right away, you're definitely not in the clear)
...4 users lost their cards after a week or more of running EC09 (even after a week, there are no guarantees that you're safe)
...11 users lost their cards while their phones were running, and 11 users lost their cards while booting up (the conclusion is obvious, isn't it?)
Unfortunately, nothing conclusive has been found as to the cause of the SD card failures, but there are some things noted above that I strongly recommend avoiding, as they have yielded 100% failure rates so far. Actually, I strongly recommend against flashing EC09 at all, unless you have some spare SD cards and back your data up religiously (oh no! I said the "R" word!). Every developer I've talked to has said the bug has not been found and appears to be quite random. Please take this into consideration when you decide whether to flash anything EC09.

Given the number of voters and items and the fact that these things were also shared by people who did lose their sdcards, it seems likely that what your seeing is random noise rather than a causal connection.

drnihili said:
Given the number of voters and items and the fact that these things were also shared by people who did lose their sdcards, it seems likely that what your seeing is random noise rather than a causal connection.
Click to expand...
Click to collapse
Unfortunately, that is also the conclusion I came to

So of 29 reporting users, only 4 did not lose their cards. Even taking into account reporting bias (people without problems tend not to report that) that suggests a very high failure rate. Given that, the problem is likely something that is common in the system itself rather than in how users implement the system. For example, it may have something to do with the way that the leak examines, and perhaps tries to repair, media on the sdcard. (I know nothing about how the internals work, this is just an example idea.)
I commend you for taking the time to go through all this, but I agree, there's nothing terribly instructive in the results. Alas, research doesn't always yield the results we hope for. (As a suggestion, you may want to reword the items in point 1 of your third post. "All came from non-UKB" sounds like everyone who had a failed card came from non-UKB. I'd say something like "All who came from non-UKB".)

Good info. I wish there was some sort of smoking gun. Lots of desirable things are built into EC09.
That being said, I'm still waiting for mine to fail. Ran the first week with the stock 16GB card and no issues, went back to CM7 then back to EC09 with a spare 4GB card. Still no issues.
One thing you may want to add to the poll, is ask who had "auto rotate" disabled and if they did, was the SD card failure still there. That's a known issue with the package since it causes a HUGE cpu draw. Could be related, or may not be. Who knows.

sarkozy said:
Good info. I wish there was some sort of smoking gun. Lots of desirable things are built into EC09.
That being said, I'm still waiting for mine to fail. Ran the first week with the stock 16GB card and no issues, went back to CM7 then back to EC09 with a spare 4GB card. Still no issues.
One thing you may want to add to the poll, is ask who had "auto rotate" disabled and if they did, was the SD card failure still there. That's a known issue with the package since it causes a HUGE cpu draw. Could be related, or may not be. Who knows.
Click to expand...
Click to collapse
Good question! I may add that to this thread later (can't add to the original survey thread though)

sarkozy said:
Good info. I wish there was some sort of smoking gun. Lots of desirable things are built into EC09.
That being said, I'm still waiting for mine to fail. Ran the first week with the stock 16GB card and no issues, went back to CM7 then back to EC09 with a spare 4GB card. Still no issues.
One thing you may want to add to the poll, is ask who had "auto rotate" disabled and if they did, was the SD card failure still there. That's a known issue with the package since it causes a HUGE cpu draw. Could be related, or may not be. Who knows.
Click to expand...
Click to collapse
There is no guarantee that your card will fail. However, it appears that this situation is worse than I first thought. Assuming at least hundred people flashed, and at least 25+ had failed cards... it isn't looking good. Thank you skynet for your poll, but I really think that it will go nowhere. It most likely has little to do with the procedure one follows (like if they ran UKB). Probably the only thing that would matter is if they flashed the ODIN leak and then a custom, just a custom, or just the ODIN leak. It is probably just an issue within the system that may or may not be able to be fixed without source code.
Back when I updated the TechnoROM OP to warn about the extent of the SD Card bug, I pretty much stopped development. There is no reason to flash this leak (EC09) with the amount and severity of bugs. Not only does the SD Card have issues, but the auto-rotate causes excessive cpu usage. Other issues include wake lock permission issues (which may or may not be fixable without source).
More importantly, logcats and any debugging reports could be of help, so don't be afraid to post.

Yeah, looks like you're right, jptech. Nothing conclusive has resulted from the poll, and as you said it likely has nothing to do with user procedures. Just thought I'd try... Do you think there may be any correlation between the autorotate issue and the fried sd cards? Like, maybe, autorotate maxes the CPU which then causes the phone to spazz out and bork the sd card? Just grasping at straws...

skynet11 said:
Yeah, looks like you're right, jptech. Nothing conclusive has resulted from the poll, and as you said it likely has nothing to do with user procedures. Just thought I'd try... Do you think there may be any correlation between the autorotate issue and the fried sd cards? Like, maybe, autorotate maxes the CPU which then causes the phone to spazz out and bork the sd card? Just grasping at straws...
Click to expand...
Click to collapse
Does autorotate engage during boot? The proximal trigger seems to engage at a lot of different times. I'd start by looking at what happens during boot as that's likely to have the least amount of variation. However, the variability in the onset strongly suggests that there is also some interaction effect or random element to account for also.
Do we know that the SD failures are of the same type? Are they all fried in the same way or to the same degree?

The hard part with this survey ( and by no means is this your fault) is that you will inherently get more responses from those who had failed SD cards than those who are running just fine. Failure likes to promote itself while success does not. Again, not bashing you....just point out the obvious which I am sure you already know.
I do commend you for even attempting this and the results are interesting. Not really a clearly defined answer yet. Hopefully more will vote.

I may be 100% wrong in this assumption, but what if this is why Verizon has been quiet about our gb update? Maybe they saw the bug and are trying to fix it?
Sent from my SCH-I500 using XDA App

DirgeExtinction said:
I may be 100% wrong in this assumption, but what if this is why Verizon has been quiet about our gb update? Maybe they saw the bug and are trying to fix it?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Makes sense - remember how buggy DL30 and EB01 were? Of course, neither one had a bug anywhere near as serious as this one.
Another Fascinating post by my XDA app...

Didn't get in on the vote but I will add my expierence with EC09 in hopes it can help. I ran it for couple weeks and had no SD failure, I went back to ComRom because couldn't play videos and the gallery didn't work properly. Here was my upgrade and downgrade procedure.
1.Odined EC09 full stock leak while running ComRom 2.1
2.Odined CWM 3-30 fix all, installed Superuser ran couple days there.
3.Tried nameless for a couple days, didn't care for it (sorry nameless but good job)
4.Odined back to stock EC09 and rooted again same procedure as above.
5.Finally Odined back to EB01 then built back to current setup with ComRom
Hope this can help in some way.

EU bug

I keep on hearing this EU bug here and there .....I have some questions regarding this .....
1,why does this happen?
2,will it affect only vibrant running ics or even jellybean?
3.how can I bring back my vibrant to normal? (don't post me regarding those guide I need breif steps).........thanks for helping

Answers (sort of):
akarshfrevr said:
1,why does this happen?
Click to expand...
Click to collapse
1. No one knows why it happens yet. Seems the earliest case had been around February for the Vibrant (before it got a real name like EUbug. Happened to Jasonhunterx)
akarshfrevr said:
2,will it affect only vibrant running ics or even jellybean?
Click to expand...
Click to collapse
2. There has been a crap-ton (this isn't metric or imperial but is a valid form of volume in my realm) amount of speculation, attempts, theories, support, more speculation all in the [Guide] Encryption Unsuccessful - Reset Android thread in the Captivate side of things. Me, Yosup, Mr_Psycho, DerT, Silvercrown, Swehes,...have all contributed to it over time but no one can get to the *root* of the problem. Even Adam Outler and Cyanogen themselves don't know why. There is also a Reference thread going too and is located here ---> [REF][ICS] Encryption Unsuccessful Reference
Here is a recent post I had over there with a brief synopsis of devices effected and ROMs/Kernel.
Bottom line, is there is no solution yet, although some users have reported getting their /data back but have no idea why or how. Further bottom line would be, if you don't want to get hit or roll the dice with the EU bug, STAY ON FROYO OR GB builds. **Sorry for the Bold CAPs but that is an important part that many should read. So far I haven't heard anyone on JB get hit with it, but that doesn't mean it isn't out there. Was Months before ICS users realized what was happening and then it was too late.
akarshfrevr said:
how can I bring back my vibrant to normal?
Click to expand...
Click to collapse
Short answer: You can't (yet). Some really bright minds are working on it but many users on both sides have left the Vibrants and Cappy's behind in pursuit of newer and shiny models. I fear that we might not find a solution and if we do, this device will be close to 3 years old and while it still rocks hard, is considered a dinosaur in mobile phone tech. And that to me is too bad.

agreed @ WOOD im yet to upgrade /update or renew my contract with Tmobile i dont know what i want to do anymore ever since the Vibrant it was like now all i think of is ..is there DEVing going on with this and that phone lol i wanted the Blaze 4g because the dual core SNAP Dragon s3 but i saw little to no dev on there still trooping out the Vibrant hardcore lol with great deal of DEV's was so sad to c FISH leave my heart SANK lol

Woodrube said:
Short answer: You can't (yet). Some really bright minds are working on it but many users on both sides have left the Vibrants and Cappy's behind in pursuit of newer and shiny models. I fear that we might not find a solution and if we do, this device will be close to 3 years old and while it still rocks hard, is considered a dinosaur in mobile phone tech. And that to me is too bad.
Click to expand...
Click to collapse
Since it happened to me also (read my testimony here), I could say this bug is somehow reversible UNLESS ONE HITS THE "RESET PHONE" BUTTON. Do not press it! Pull the battery out and boot to recovery through button combo and restore a nandroid. If you are a flasher and not a noob, always keep a working nandroid backup (it saved me). I'm not sure if I could flash anything else, perhaps it's the same flashing process somehow getting corrupted?

ioancr said:
... I could say this bug is somehow reversible UNLESS ONE HITS THE "RESET PHONE" BUTTON. Do not press it! ...
Click to expand...
Click to collapse
I never pressed Reset (and knew beforehand not to thanks to advice from Woodrube, et al) ... yet I still succumbed to EU.
No one knows a sure fire way to make this "reversible" unfortunately. Those who have had their internal sd's restored seem to have been more lucky than anything else - ie. there's no common thread to link nor duplicate their results.
Maybe one day, this thing gets figured out.

yosup said:
I never pressed Reset (and knew beforehand not to thanks to advice from Woodrube, et al) ... yet I still succumbed to EU.
No one knows a sure fire way to make this "reversible" unfortunately. Those who have had their internal sd's restored seem to have been more lucky than anything else - ie. there's no common thread to link nor duplicate their results.
Maybe one day, this thing gets figured out.
Click to expand...
Click to collapse
Wow, I didn't know that, it seems really worse than I thought of. Sorry if I ask it, but you still were able to get to recovery weren't you? Also, did you have a nandroid backup to try a restore?
Then I was yes very lucky, sorry for you guys and hope someday someone will save your phones too...

ioancr said:
... Sorry if I ask it, but you still were able to get to recovery weren't you? Also, did you have a nandroid backup to try a restore? ...
Click to expand...
Click to collapse
Yes, I could get to recovery, but I couldn't mount the internal sd anymore (and haven't been able to yet to date). So, I couldn't restore a nandroid backup or flash any of the roms I had downloaded on the int sd.
The vold.fstab emmc swap method at least let's me use the phone normally (albeit without the int sd), but I'm keeping my fingers crossed Woodrube & The Gang figure out how to restore access to the int sd ... some day.

I got scared by this bug i left ics itself and now I'm running helly bean ...........I don't have an ext memory card and should I get one? you know just in case if something goes wrong I can use the roms from ext memory card or nandroid backup and come back to normal ...........

This bug appears to be similar to the emmc bug on the note. Essentially, the eprom (programmable chip) on the motherboard of your phone.... for some reason it writes additional bits of code (like 2 bits or 8 bits) on the chip which then basically changes how the cpu sees the index... which then Bricks the phones.
Like Woodrube said...... The Vibe is 3 years old and it Totally Amazes me how great this phone really is.......... it is one of the few that could get ICS or JB ....... think about it this thing was released with Eclair (2.1)...... and still running like that lil bunny......
Oh and BTW CONGRATS TO WOODRUBE..... He is now the latest addition to the Moderator's group here at XDA Congrats to Woodrube.
:victory::victory::victory::victory::victory: ~~~~~ oka1
Woodrube said:
Answers (sort of):
Short answer: You can't (yet). Some really bright minds are working on it but many users on both sides have left the Vibrants and Cappy's behind in pursuit of newer and shiny models. I fear that we might not find a solution and if we do, this device will be close to 3 years old and while it still rocks hard, is considered a dinosaur in mobile phone tech. And that to me is too bad.
Click to expand...
Click to collapse

oka1 said:
... Oh and BTW CONGRATS TO WOODRUBE..... He is now the latest addition to the Moderator's group here at XDA Congrats to Woodrube.
:victory::victory::victory::victory::victory: ~~~~~ oka1
Click to expand...
Click to collapse
:thumbup::thumbup: Congrats, Woodman!! :thumbup::thumbup:
Very worthy bump-in-pay-grade for one of the all-time "counselors" that roam these halls. Great to see that good guys do win.

Note: I'm not sure if the following information is 100% valid for our device, but I've been digging into the problem and how others have gotten it.
How to reproduce:
- After bootup perform sudden power removal
- boot-up interup and reboot.
Click to expand...
Click to collapse
Yup, 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.
In Gingerbread and before, anything that wasn't valid was expected to
be invalid, and Android would just re-initialize it, regardless of
whether it was zero or not.
Click to expand...
Click to collapse

theexel said:
Note: I'm not sure if the following information is 100% valid for our device, but I've been digging into the problem and how others have gotten it.
Click to expand...
Click to collapse
Interesting stuff. I wonder what would cause part of the file system to become invalid though, seemingly during normal usage.

Not trying to thread jack but I read this quote on team-passion by the dev:
The encryption bug is due to a partition going bad. If it happens to the internal SD then you're done. It's not an ICS bug. It happens on all ROMs and all phones. ICS makes an effort at fixing it. Previous versions don't, or don't make themselves apparent. Bricks have been happening for ever. The Vibrant is 2 years old. Hardware fails. Just like in your PC. This kind of error come up on stock OTA updates, on other devices, as well. Not for SD, as far as I could find. But OTA updates of ICS are for new devices. If there are any corruptions the phone gets returned
Click to expand...
Click to collapse
Is there any truth to this? Can the EU bug happen on any rom? Is ICS as safe as any other rom?

crazexr7 said:
Not trying to thread jack but I read this quote on team-passion by the dev:
Is there any truth to this? Can the EU bug happen on any rom? Is ICS as safe as any other rom?
Click to expand...
Click to collapse
till date it has only occurred on ics roms ......jb roms not even a single case reported .....I'm hoping it won't come to jb .....I got scared by this bug and I moved from ics to jb .......2.2 and 2.3 are safe to escape from this bug

crazexr7 said:
Not trying to thread jack but I read this quote on team-passion by the dev:
Is there any truth to this? Can the EU bug happen on any rom? Is ICS as safe as any other rom?
Click to expand...
Click to collapse
No, there is no truth to this (see my earlier post in this thread for more info).
Not 1 single Froyo or Gingerbread build hsa ever gotten the bug (fact).
The EU bug occurred in early ICS builds for the first time (fact).
It occurred more frequently in Passion versions b1-v13 more than any other ROM out for the Vibrant (fact).
Sounds like there is some spin doctor action going on over there (speculation based on fact).
No one has yet to figure out why,how or when this happens. BUT, it is not from hardware degradation, except for the very small chance that overclocking puts extra heat and strain on the Nand chip (fact and speculation).
Ok so OKA1 said something about the EMMC chip corruption on the Note (which he owns). I was allocated my new forums and lo and behold, one was the Galaxy Tab 8.9 and guess what? They are having a major problem with....CWR and kernels that are making the machines nearly un-usable. Here is a link to the General section that might have some more info with it's multiple threads about the same thing (for now. Muhahaha!)

Woodrube said:
No, there is no truth to this (see my earlier post in this thread for more info).
Not 1 single Froyo or Gingerbread build hsa ever gotten the bug (fact).
The EU bug occurred in early ICS builds for the first time (fact).
It occurred more frequently in Passion versions b1-v13 more than any other ROM out for the Vibrant (fact).
Sounds like there is some spin doctor action going on over there (speculation based on fact).
No one has yet to figure out why,how or when this happens. BUT, it is not from hardware degradation, except for the very small chance that overclocking puts extra heat and strain on the Nand chip (fact and speculation).
Ok so OKA1 said something about the EMMC chip corruption on the Note (which he owns). I was allocated my new forums and lo and behold, one was the Galaxy Tab 8.9 and guess what? They are having a major problem with....CWR and kernels that are making the machines nearly un-usable. Here is a link to the General section that might have some more info with it's multiple threads about the same thing (for now. Muhahaha!)
Click to expand...
Click to collapse
ok so I'm running chimera v1.1 if I want to flash froyo again can I just flash a froyo rom from ics and be ok? or do I have to odin back to stock and go from there?

Gingerbread/Ice Cream Sandwich/Jellybean to Froyo with just a ROM flash = Brick waiting to happen.
ODIN back to stock, bud.

You can go from:
Froyo <-> Froyo:good:
Froyo -> Gingerbread :good:
Gingerbread <-> Gingerbread/MIUI:good:
Froyo/Gingerbread -> ICS/JB:good:
ICS <-> ICS:good:
ICS ->JB:good:
JB <-> JB:good:
ICS/JB -> Froyo/Eclair:bad:
Gingerbread -> Froyo/Eclair:bad:
Do NOT restore cross-OS Nandroids either. Meaning that you cannot restore a Froyo while you are on GB/ICS/JB.

Woodrube said:
You can go from:
Froyo <-> Froyo:good:
Froyo -> Gingerbread :good:
Gingerbread <-> Gingerbread/MIUI:good:
Froyo/Gingerbread -> ICS/JB:good:
ICS <-> ICS:good:
ICS ->JB:good:
JB <-> JB:good:
ICS/JB -> Froyo/Eclair:bad:
Gingerbread -> Froyo/Eclair:bad:
Do NOT restore cross-OS Nandroids either. Meaning that you cannot restore a Froyo while you are on GB/ICS/JB.
Click to expand...
Click to collapse
Thanks guys I'm going to miss ICS but it's just not worth keeping. I would love to flash to JB but GPS and 911 issues are scaring me away.