Related
I am going to return it because of problems of phone shutting itself off automatically. This is my 3rd one, and they all did this. If I wait till october (after 2.2), will I be buying a different phone (hardware wise), or the exact same thing? Maybe a newer batch will be less glitchy? (gps, lag, shutdowns)
i was wondering if perhaps the phones that are rolling out in october/november, will work flawlessly out of the box? Maybe some hardware changes?
Thing is i got a good deal on a 3 year plan (the worker at bestbuy messed up and gave it to me $50 less than what he's supposed to), and if i return it now (since the 14 day return expires tomorrow), i will pay $50 more for it if i decide to buy it again in october.
My carrier will put my hardware upgrade back onto my account, and i can buy whatever phone i want at a later date (WILL NOT BUY AN IPHONE...EVER). But i dont think any good new phones better than SGS are coming out soon...are there any? thanks
I got no lag, never ever had a restart and gps should be fixed to some extent. October you will see the g2, will it be flawless ? No nothing usually is..
The lag I hear about but don't have myself so I can understand that, but the restarts have to be something you installed or a lemon. I'f you had that happen on all 3? Definitely something you installed
Dude, what are you doing to your phone(S)???? I have never had my phone reboot/shutdown unless I was messing around with installing system apps from another rom... and that was a super easy fix.
$10 says OP had crap like setCPU on his or her phone. Samsung has already tried to make it harder to get into recovery and download mode.....hmmm I wonder why?
s15274n said:
Dude, what are you doing to your phone(S)???? I have never had my phone reboot/shutdown unless I was messing around with installing system apps from another rom... and that was a super easy fix.
Click to expand...
Click to collapse
dont have any apps installed except for adobe reader. Someone mentioned it could be my sim card, so i changed it and it has not happened since...but...its only been 4 days, and this shutoff thing happens every 3 to 5 days anyways..so if i wait to see if it was perhaps my sim card all along, then it will be too late. «9refund policy).
If you go over to the captivate forum, you will see that many people (almost one third of people) have this issue. It could just be bad sim cards, but i dont know for sure.
Singhman said:
dont have any apps installed except for adobe reader. Someone mentioned it could be my sim card, so i changed it and it has not happened since...but...its only been 4 days, and this shutoff thing happens every 3 to 5 days anyways..so if i wait to see if it was perhaps my sim card all along, then it will be too late. «9refund policy).
If you go over to the captivate forum, you will see that many people (almost one third of people) have this issue. It could just be bad sim cards, but i dont know for sure.
Click to expand...
Click to collapse
There you go, adobe reader. Be sure to give it a 1 star review, and I apologize for my previous rude remark.
Sent from my SGH-T959 using XDA App
Not a god idea because more phones will be out at that time and you won't be able to decide. Like the person above me. If adobe reader is the only app installed then that's most likely the culprit.
Why not just use thinkfree pdf reader? Works just as god as adobe's.
Sent from my SGH-T959 using XDA App
Your sd card may be corrupt too.
To answer the OP question, I think it's worth returning the phone even if you have to eat the 50 bucks. The G2 is coming out this month and the MyTouch HD in November. Both phones could be strong contenders. If you can hold out til then you might even be able to get the vibrant for a reduced price.
WOw dude
never had my phone reset
that's sounds serious
yea i find it hard to believe all 3 have the same problem did u buy them all from the same place? i know the phone has it's problem but Ive never herd anyone have one were it randomly restarts on them.
It is because of adobe, others have had the same exact problem.
Sent from my SGH-T959 using XDA App
Chalup said:
$10 says OP had crap like setCPU on his or her phone. Samsung has already tried to make it harder to get into recovery and download mode.....hmmm I wonder why?
Click to expand...
Click to collapse
why do you think setCPU is a crap app?
Had the same problem with mine uninstall adobe and I'm good. Use thinkfree or vudroid
Sent from my SGH-T959 using XDA App
*charles barkley voice*
Man, thats turrrrible..
I'd be less eager to point fingers at Abobe, personally. Userspace (i.e. non-kernel) code shouldn't be able to lock up phones in this manner. I can understand slating SetCPU - over-clocking is never guaranteed to be safe. But simple apps like a PDF reader? Even utilising SetCPU to just scale down CPU clock speed should be absolutely safe...
I've had my phone now for just under a month and in the last week it's developed this issue where it'll crash/shutdown when left idle. And no, I'm not running any stability-compromising apps, zero mods, nada. Not even rooted it. Just stock firmware and a handful of apps - apps I've not even run since installing them weeks ago. And for what it's worth, I wiped my handset this evening and after roughly 15 minutes of being left idle while I was eating dinner, it died again.
Now I've not got a Vibrant myself; I'm an SGS owner. But if you search the Samsung sub-forums here at xda-developers, or do a Google search, you'll find hundreds of Vibrant, Epic and Galaxy S users who are reporting exactly the same issues. Which leads me to think that this really has nothing to do with userspace code at all. Instead it points back to Samsung's sloppy business practices of releasing Android-based phones before they're fully cooked...
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.
Im gonna try to make this short because im sure alot of people have expirienced this.
Almost every Epic rom i ever flashed sooner or later i get "process com.google.process.gapps has stopped unexpectedly" or "Android.process.acore" fc or some similar bull**** that has to do with Google Frameworks usualy.
Like today i started getting Frameworks fc,so i cleared date/cache for almost all apps trying to fix it.I rebooted and now on top of Frameworks fc i get Android Acorn fc and Gingerbread MTF fc!
So im like fck it im just gonna do system restore(which i was trying to avoid).
Did system restore wiped data/cache/sdcard/dalvic cache 3 times and what happens?I get same damn Google Frameworks/Acorn/MTG fc's after reboot!
Only way to fix this problem is to reflash the rom.
What causes it?IDK,i suspect its bacause my girlfriend(bacause it happens mostly when she has it) lets the phone's battery die while txting/calling but my roms are Journaled so that shouldnt be a problem,right?
Anyways is there a fix/prevantion for this sht without having to reflash?
Just when i think i found the right rom it happens again.This happens sooner or later on any rom,or is this something that android users gotta live with?
Update:
WTF i just reflashed and now im stuck at Samsung logo,i guess its Odin time and hate to say this but might be WP7/WebOS/iPhone time.
Don't mean to be a deuscher or anything but have you tried deodexed stock? Never had those issues on my heavily modified stock before.. (Might as well be my own cooked rom, though changed/tweaked realtime with my cell on) lol. =)
Shinydude100 said:
Don't mean to be a deuscher or anything but have you tried deodexed stock? Never had those issues on my heavily modified stock before.. (Might as well be my own cooked rom, though changed/tweaked realtime with my cell on) lol. =)
Click to expand...
Click to collapse
Thanx,im might try that.I think it might be ext4 that does it because i dont think i had them problems on rfs-i cant even remember last time i used rfs.
I kange my own roms too but i always prefered to use lightweight roms like Syndicate for foundation.But if stock rfs is more stable than it will be a good trade.
I always get gapps errors when I copy something to the system\app folder. I have started to use flashable zips instead and clear Dalvik before booting and have not seen that problem again. It doesn't sound like you are doing any of that but any theme or mod that is flashed and doesn't wipe Dalvik may cause this as well. Hope this helps. You may also just have a finicky phone...lol.
My phone isn't rooted and I got that. Fo me it had to do with the gmail app sync. Once I stopped that no more fc. I use the samsung email app that on the phone now.
Sent from my non-rooted Epic 4G using the free XDA App
I blame my girlfriend too.
Sent from the future.
Take this how you want. I had this problem span over 5 nand backups one day, 5 that I knew where all good when I did a backup (and had restored before with no FC's. Then one day on eg22 all hell broke out, I was doing so much that day I can't narrow down what happened. Then I restored a backup,,, what, still getting framework fc's; Tried another, then another. 5 times same problem. I odined back to DI18 and let it OTA, then installed cwm and restored my laszt backup. Everything has worked since.
I have this problem every so often on srf. Only fix I know is to reflash the rom then restore a backup. This usually happens when my phone reaches 0% and dies. Has happened over 10x
Sent from my SPH-D700 using XDA App
lviv73 said:
i suspect its bacause my girlfriend(bacause it happens mostly when she has it) lets the phone's battery die while txting/calling but my roms are Journaled so that shouldnt be a problem,right?
Click to expand...
Click to collapse
Journaling isn't a panacea.
When there's sudden power loss (battery pull or death) on a journaled file system, the file system should be in a consistent state on bootup, but individual files can still become corrupt.
If that happens, doing a "Clear data" on all apps that force close should fix it. In the worst case, a "Factory data reset" should work as well, without having to resort to a reflash.
I don't know if RFS does full data journaling or not, but I suspect it does. Anecodtally, these types of issues appear to be much rarer on RFS, which is part of the tradeoff to RFS suffering from additional lag (to ensure writes happen timely).
As general advice, if you are going to run ext4, journaled or not, avoid power loss as much as possible.
puff601 said:
I have this problem every so often on srf. Only fix I know is to reflash the rom then restore a backup. This usually happens when my phone reaches 0% and dies. Has happened over 10x
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Just as i suspected.It happens on rfs too or just ext4?
I would think thats what Journaling was for so something like this wouldnt happen.
So this is a problem on any android phone i take it,google needs to fix this.
What regular nontech people supposed to do?System restore everytime their phone dies?lol.
mkasick said:
Journaling isn't a panacea.
When there's sudden power loss (battery pull or death) on a journaled file system, the file system should be in a consistent state on bootup, but individual files can still become corrupt.
If that happens, doing a "Clear data" on all apps that force close should fix it. In the worst case, a "Factory data reset" should work as well, without having to resort to a reflash.
I don't know if RFS does full data journaling or not, but I suspect it does. Anecodtally, these types of issues appear to be much rarer on RFS, which is part of the tradeoff to RFS suffering from additional lag (to ensure writes happen timely).
As general advice, if you are going to run ext4, journaled or not, avoid power loss as much as possible.
Click to expand...
Click to collapse
Thats exactly how i tried to fix it,wiping data and cache on all system apps and all that got me was even more unfixible fc's.
For example:After i cleared cache for frameworks i started getting more anoying Gingerbread MTF fc every 20 seconds,lol.Yeah i tried clearing Gingerbread MTF cache/data and i still got the fc's even after system reset.
Now i see why Android is not doin good in corporate world,people need something reliable.
lviv73 said:
Thats exactly how i tried to fix it,wiping data and cache on all system apps and all that got me was even more unfixible fc's.
For example:After i cleared cache for frameworks i started getting more anoying Gingerbread MTF fc every 20 seconds,lol.Yeah i tried clearing Gingerbread MTF cache/data and i still got the fc's even after system reset.
Now i see why Android is not doin good in corporate world,people need something reliable.
Click to expand...
Click to collapse
How many 'Berrys on corp accounts do you see that are as heavily modified as our androids??? And to be fair, the Epic still really isn't even 'done'... by the time they released EC05, it was pretty obvious that they were already planning GB, so maybe after GS2 launch, we will get source, CYM, Miui, etc... and a stable stock rom of course... then i can feel comfortable giving this to my GF when I get a GS2 I love my epic, but I hate her intercept more than any phone I have ever witnessed. Point is, kind of a bad phone to use as reference for relating it to business phones, also as we are on a hack site, most companies either prefer or insist you dont **** with their phones. I think it has been said that android will be getting more and more stable... by what, everyone? You just happen to have an early adopter phone, we are the guinea pigs who pay for R&D and find the flaws. The way the android world is shaping up, it looks as if its only getting better. I love that I was in work training, for a relatively technical position, and all but 2 out of 12 people had androids, the others had iphones and little to contribute to the BS discussions.
ungovernable1977 said:
How many 'Berrys on corp accounts do you see that are as heavily modified as our androids??? And to be fair, the Epic still really isn't even 'done'... by the time they released EC05, it was pretty obvious that they were already planning GB, so maybe after GS2 launch, we will get source, CYM, Miui, etc... and a stable stock rom of course... then i can feel comfortable giving this to my GF when I get a GS2 I love my epic, but I hate her intercept more than any phone I have ever witnessed. Point is, kind of a bad phone to use as reference for relating it to business phones, also as we are on a hack site, most companies either prefer or insist you dont **** with their phones. I think it has been said that android will be getting more and more stable... by what, everyone? You just happen to have an early adopter phone, we are the guinea pigs who pay for R&D and find the flaws. The way the android world is shaping up, it looks as if its only getting better. I love that I was in work training, for a relatively technical position, and all but 2 out of 12 people had androids, the others had iphones and little to contribute to the BS discussions.
Click to expand...
Click to collapse
Easy man,lol.Im only stating an article that i read on one of the android sites about android os not doing good in corprate world and ios and bb beating them at it.
Lviv, did you read everything in the rom's you installed? I'm pretty sure as someone mentioned in this thread somewhere it said turn of sync. These rom's are built on leaked sources. Unless your on froyo none of gb rom's are built on an official release.
Sent from my SPH-D700 using xda premium
edfunkycold said:
Lviv, did you read everything in the rom's you installed? I'm pretty sure as someone mentioned in this thread somewhere it said turn of sync. These rom's are built on leaked sources. Unless your on froyo none of gb rom's are built on an official release.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
They all froyo.This just happened to me on Revolution rom which is really nice if not the best i used so far.It also happened to me on few Syndicate roms and Bonsai and few more.
Plus i always have my sync off or just background data on,i never leave auto sync on because it drains battery.
Like someone said on here its brobably because phone's battery reaches zero while performing some task or Sprint spyware removal might have something do with it or ext4.
Im gonna try rfs and stock and see what the problem is.
Its just rediculous because my roms never lasted for more than two months without this happening,and as someone stated before that it happened to them even on stock unrooted phone.
There are threads all over the internet on this problem with different fixes that mostly dont work.
I experianced the same thing with two different roms this week and went back to acs bamboozle with eho6 modem and its all working perfect now.
Sent from my SPH-D700 using xda premium
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.
I have a 2012 nexus 7. When I go into the the about tablet menu in settings theres no update button/check for update button. i'm on 4.2.2 and i've heard android 4.3 fixes the lagginess of the device. My nexus 7 is unlocked, rooted, and running AOPK. I think AOPK might be the problem, but otherwise I have absolutely no idea why the update button isn't there.
Also, I know virtually nothing about android, so if anyone has solutions, please use basic step by step instructions and explain any advanced terminology.
Any help would be greatly appreciated.
Thanks.
You need to manually install Android 4.3 when you're on AOKP. CyanogenMod and ParanoidAndroid are both already based on Android 4.3, but you may also choose to install the stock factory images using the guide here
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using xda app-developers app
Tired of it, so i bricked it.
Remcotjuuh said:
You need to manually install Android 4.3 when you're on AOKP. CyanogenMod and ParanoidAndroid are both already based on Android 4.3, but you may also choose to install the stock factory images using the guide here
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help, but my nexus 7 has caused me nothing but grief for the couple of months I had it. So i did some stuff to it trying to fix, knowing, yeah i'm gonna brick this thing. and I bricked it. or it could be the battery died... not sure yet. But I figure at 250, i'll just give Asus another chance and go out and buy the new version.
thanks though.
Well I guess i could have fixed it...
stock factory images, didn't catch that part... my god that article would have helped a lot, then i could re-root and re-install AOKP. Oh well, it's not like the tablet actually did me any good, i spent more time screaming at it then actually using it. *Sigh* I knew i should have waited a couple of months and gone with a Tab 3. Call me crazy, but i just freaking love touchwiz.
Anyways thanks again for the link... knowing i could have fixed if i had the patience left with the stupid thing makes me feel better... the lag was just so bad, i heard it was almost a lag apocalypse with the 2012 nexus 7s running 4.2.2, after I bought the thing of course.
Thanks again.
Strange that you're talking about lag so much. I don't experience any, or at least not enough for it to be really noticed.
The lag was so bad that I kinda wanted the thing to die
It's all over the net about how the 2012 nexus 7s are virtually unusable due to lag caused by 4.2.2. Not all of the devices running this version of android have this problem, but unfortunately a heck of a lot of them, from what I can tell, do. It just pisses me off because A: in essence this should be a fairly powerful device, with tegra 3 processor and a gig of ram, it just should be... but mine at least isn't. And B: this is the device I got to try android for the first time, I'm more of an apple guy myself and it's especially unfortunate that i was essentially just handed a bad nexus 7 in this particular scenario. Technically I'm the one who broke it completely but still... Lisa, or whatever her name is, in one of her mobile tech review videos on youtube said they had a nexus 7 without any problems... It's sad though because I really wanted to like the stupid thing, I mean it had really good build quality, and coming from me that's high praise, and the price point was amazing... I can't imagine google was making a ton of money for such a device going that cheap.
Thanks again, I more than anything just wanted to rant!!!
josephstc9 said:
It's all over the net about how the 2012 nexus 7s are virtually unusable due to lag caused by 4.2.2. Not all of the devices running this version of android have this problem, but unfortunately a heck of a lot of them, from what I can tell, do. It just pisses me off because A: in essence this should be a fairly powerful device, with tegra 3 processor and a gig of ram, it just should be... but mine at least isn't. And B: this is the device I got to try android for the first time, I'm more of an apple guy myself and it's especially unfortunate that i was essentially just handed a bad nexus 7 in this particular scenario. Technically I'm the one who broke it completely but still... Lisa, or whatever her name is, in one of her mobile tech review videos on youtube said they had a nexus 7 without any problems... It's sad though because I really wanted to like the stupid thing, I mean it had really good build quality, and coming from me that's high praise, and the price point was amazing... I can't imagine google was making a ton of money for such a device going that cheap.
Thanks again, I more than anything just wanted to rant!!!
Click to expand...
Click to collapse
nice post, very well seated :good: i myself never experience lag issues on 4.2.x i think i noticed a slight glitchyness but stoped google currents auto-updating in background rectified the problem 100%
also what r u doin with the bricked nexus? why not get someone to skype video- walk you through some step to get it working? i always wonder why we struggle to text explain things when we can just skype video walk-through each other lol
I can access the bootloader
chismay said:
nice post, very well seated :good: i myself never experience lag issues on 4.2.x i think i noticed a slight glitchyness but stoped google currents auto-updating in background rectified the problem 100%
also what r u doin with the bricked nexus? why not get someone to skype video- walk you through some step to get it working? i always wonder why we struggle to text explain things when we can just skype video walk-through each other lol
Click to expand...
Click to collapse
I'll find a guide on how to flash 4.3 on the stupid thing, and if that dosen't fix the issues i have been having with it i'll sell it
Sticky at the top, how to flash an image using fastboot/return to stock. If that can't help you, there is no helping you.
Sent from my Nexus 7(2012) that has zero issues.
I have access to the bootloader so i should be able to do it via the windows command line, right? In any case, i'm going to wait a bit and learn more about android so i don't completely screw my chances of fixing it.