Database Users

Flashing firmware asian to european- for ppl who have flashed

Hey guys in my earlier thread some ppl told me that i could update from asian firmware to european firmware. I would like to knw if there would be any problems by doing that, and would like to know ur experiece after flashing.. Thanx for ur replies. I don mind waiting an extra month for asian firmware release if u feel flashing can be problematic, if not i'll b happy to flash.
Ps: I knw a thread like this is available but there are no conclusive answers there. Thanx.

I like to know too. I hope no issue here other than losing the Asian keyboards. I assume one could still get a third party keyboard for say, chinese characters input.

Ya i recieved a reply in hardware zone forum, ppl have upgraded their firmwares from dd or dx to xx, xw (european). No problems were found, infact performance increased a little bit. One of the guys told me not to update cause firmwares released in europe tend to be buggy like beta versions, only final versions are released in asia and other places thats why updates are few. So if i were u i'd wait for firmware to release in my region.. Wat's u take on this? Do u still wanna flash ur phone or do u wanna wait a month extra......

I personally haven't had any issues with the euro fw to speak of. Like doomsdaycs mentioned I definitely experienced performance increase and even more once i installed the modaco rom. I ran the latest JG3 for a few days and it was great then i wanted the modaco rom so I reflashed with JG1 and it's still had no problems. Hope that helps...

doomsdaycs said:
Ya i recieved a reply in hardware zone forum, ppl have upgraded their firmwares from dd or dx to xx, xw (european). No problems were found, infact performance increased a little bit. One of the guys told me not to update cause firmwares released in europe tend to be buggy like beta versions, only final versions are released in asia and other places thats why updates are few. So if i were u i'd wait for firmware to release in my region.. Wat's u take on this? Do u still wanna flash ur phone or do u wanna wait a month extra......
Click to expand...
Click to collapse
That's utter rubbish.
Went from APAC to Euro firmwares, and never looked back.

Let me ask you guys who have gone over to the European firmware a few questions:
1) Has it fixed the 3G/wifi connection problem? (I hope you do not dispute that there is problem )
2) Has the lags/pause gone away? Or just minimized?
3) Has your GPS started to work accurately yet?
4) Does your email still takes ages to load? Or just become less slow?
5) Does the music playing still pause/freeze once in a while?
6) Anyone still able to install stuffs like Chinese keyboards from the Android market place after adopting the Europe firmware?
7) Do you have problem with the market place like what these people say?
http://forum.xda-developers.com/showthread.php?p=7232231#post7232231
Thanks for sharing.

Let me ask you guys who have gone over to the European firmware a few questions:
1) Has it fixed the 3G/wifi connection problem? (I hope you do not dispute that there is problem )
Answer: You need to create a new APN in order to use the 3G network. As for WIFI.. I am able to connect to any WIFI as long as I have the password.
2) Has the lags/pause gone away? Or just minimized?
Answer: Kinda but you will still experience it even with the JG5 firmware.. rumor has it that samsung will release an official fix for this on the end of july but there is no official word from samsung.. all we can do is cross our fingers and hope or best alternative.. use modaco's fix.
3) Has your GPS started to work accurately yet?
Answer: Yup, compared to the stock firmware, it is able to identify my location within a 5 meter radius.
** upgrade to the latest google maps version.
4) Does your email still takes ages to load? Or just become less slow?
Answer: Google.. first time setup.. yes. But now, depending on your location and signal strength.. takes about 8 - 15 seconds.. longer with 2 bars on my phone.. about 30 seconds or so. [GMAIL]
5) Does the music playing still pause/freeze once in a while?
Answer: When I am playing Let's Golf with very low volume then listening to music using the default player at level 6 - 7 volume. I do experience it sometime..
6) Anyone still able to install stuffs like Chinese keyboards from the Android market place after adopting the Europe firmware?
Answer: I am able to install Google Pinyin.. the qwerty keyboard still shows ABC but when you press each letter.. it will show the chinese character equivalent.
7) Do you have problem with the market place like what these people say?
http://forum.xda-developers.com/showthread.php?p=7232231#post7232231
Answer: Weird case, never experienced that issue on my SGS after doing 3 firmware upgrades.
And no, I haven't rooted my phone yet.. hoping to hear from samsung by the month's end to know if they finally release a firmware fix for the memory transfer issue [NAND].

kenkiller said:
That's utter rubbish.
Went from APAC to Euro firmwares, and never looked back.
Click to expand...
Click to collapse
I second that.
The ASIAN version to be honest.. is full of crap from the TELCO's which renders the phone perform slower.. and I'd like to add that, my phone starts and loads faster now without the singtel crap.

Thank you M3keni. I'm glad it looks so positive.

kenkiller said:
That's utter rubbish.
Went from APAC to Euro firmwares, and never looked back.
Click to expand...
Click to collapse
eaglesteve said:
Thank you M3keni. I'm glad it looks so positive.
Click to expand...
Click to collapse
You are welcome bro.
Disclaimer though.. other users may have a different take on my experience with my SGS.. hehehe.
..seriously, samsung should fix the NAND issue with an update firmware soon.
..but we have hardworking developers to go to for MODS.. iLike!
Before you decide and buy the SGS, visit your nearest telco showroom to try and feel the phone. Will help in your decision.
Have a good weekend!

Thanx for the info i'll be flashing madoco rom too.. cheers..

I'm waiting for the Froyo that's supposedly 3 times faster than iPhone 3GS. As it is now, it is a lot slower than even iPhone 3G. The black screen and long pauses is beginning to get to me.
I'm hesitant to root now as I'm uncertain about the hardware aspect of GPS, and my fear that the process might not be fully reversible, hence voiding the warranty potentially.

i have a question that how to upgrade the firmware from Asian to EUR use kies without root??????
i want to change that but have no idea, thx

yes please, even I need to know how to flash my Singtel FW to the eu version like the friends above mentioned. Mainly I want to do this without rooting...!!
And once after upgrading, will it allow me to upgrade to froyo when it is officially released!!! via Kies or OTA.

kenkiller said:
That's utter rubbish.
Went from APAC to Euro firmwares, and never looked back.
Click to expand...
Click to collapse
Can you suggest the fw number of the official euro firmware that you are using now so I can install as well.

No problem at all dude.
Flashed from DDJF3 to XWJG1 (Indian to some European country)... JF3 had major issues... JG1 is good... not great though. Most of the problems of the stock firmware were resolved by Modaco's Custom ROM... try it out!

You guys should give the new firmware JM1 or JM2 a twirl. The difference is night and day...no joke..and that's before root and any modifications.
@netboyhk I initially used this as my starting point http://www.youtube.com/watch?v=PpWcM44On88
Note that in the video he says it HAS to be on a specific com port....ignore that part. It's all relative to how many usb ports u have and how many devices plugged in etc etc. From my experiences it's REALLY hard to brick this phone but your mileage may vary

I think you mean JM1 and JM2 - unless Samsung's moving faster on firmware than I thought...

flamingpitofhell said:
I think you mean JM1 and JM2 - unless Samsung's moving faster on firmware than I thought...
Click to expand...
Click to collapse
Yea thanks.
Sent from my GT-I9000 using XDA App

eaglesteve said:
I'm waiting for the Froyo that's supposedly 3 times faster than iPhone 3GS. As it is now, it is a lot slower than even iPhone 3G. The black screen and long pauses is beginning to get to me.
I'm hesitant to root now as I'm uncertain about the hardware aspect of GPS, and my fear that the process might not be fully reversible, hence voiding the warranty potentially.
Click to expand...
Click to collapse
I can confirm that it IS FULLY REVERSIBLE. You just need to reformat using ODIN while putting an official ROM.

Any news on a proper fix for lag

I was wondering if Samsung even know off this problem and when they plan to fix it

Updating to JG5 firmware pretty much makes it disappear. I suppose the formal JF6 firmware that's supposed to be released to europe somewhere during the next 2 weeks won't have it as well.

if you are are affected then do this
http://forum.xda-developers.com/showthread.php?t=724251
else wait for the official fix.
i was never affected, but i did it anyways to gain a bit of extra speed

AllGamer; said:
if you are are affected then do this
http://forum.xda-developers.com/showthread.php?t=724251
else wait for the official fix.
i was never affected, but i did it anyways to gain a bit of extra speed
Click to expand...
Click to collapse
That thread is for semi god, not for ordinary human beings LOL.
The slow speed is really wearing me down. I hope 2.2 come up fast. I'm actually wondering if I could wait so long before I decide to get rid of my SGS.

I have got Jg5 firmware and have done the lag fix in that forum but it hasn't got rid of it properly, i still get it and find my phone slows down and needs rebooting.
I guess am a bit disappointed coming from a snappy Desire which in all honesty feels miles faster atm, i wasn't expecting this issue from what was said on all review sites as the fastest Android phone and this problem was never picked up on.

I know what you mean, Jabby. I was also blown away by the review on speed. But since we've already bought it, let's see if we can solve this problem.
Have you tried the solution mentioned in the following thread yet?
http://forum.xda-developers.com/showthread.php?t=731695
I'm in the middle of it.

what is the spec of your SD card?
Jabbypants said:
I have got Jg5 firmware and have done the lag fix in that forum but it hasn't got rid of it properly, i still get it and find my phone slows down and needs rebooting.
I guess am a bit disappointed coming from a snappy Desire which in all honesty feels miles faster atm, i wasn't expecting this issue from what was said on all review sites as the fastest Android phone and this problem was never picked up on.
Click to expand...
Click to collapse

Bell Canada finally admit the GPS bug!!!

I bought a Galaxy S from Bell Canada in august. Made the update to JH2 trough kies. Had the GPS bug (locked fine, but was sometimes way off (1-3 streets off)).
I told Bell. They said they didn't know any GPS problem affecting their device.
I tried many differents things, but I still had the problem so I recorded tracks with both my Hero and my Galaxy S to prove that the Galaxy S has a bug.
I called Samsung. I told them that I had a bug with the GPS. They said that they were not aware of any GPS bug affecting the GT-i9000M (the canadian version).
I went to Bell and asked for a repair. Seems like I was the first in Canada to report the problem because they told me again that there was no report on such problem, so it must be a specific problem with my device. They give me a Samsung Omnia II for the time of the repair. Worst touch screen ever, almost useless compared to a Galaxy S.
My device came back "repaired" (what they did was a factory reset and allegedly a ROM update, but it was JH2 before and after the repair, so this is bull****). In short they did nothing but loose my time.
Of course, I still have the exact same bug, the repair guy probably didn't even test it.
I call Bell again. Shock! Horror! They admit that there is a problem with ALL Galaxy S. Finally! Not that I told them since August... And it's not only in Canada, according to the tech support agent, it affects devices from all around the world. And that I shouldn't worry because the update to 2.2 will be released everywhere in the world in November and will fix that. Great!
Oh wait. The update to 2.2 is already released in some parts of Europe. I am not even sure that it fixes the GPS. At least I have an audio recording of Bell telling me that the bug will be fixed with an update in November. Better than nothing I guess.

+1
Two thumbs up for your effort. Hopefully canadian sgs froyo update comes on November like the rest of the world....
Sent from my GT-I9000M using XDA App

Great job on the audio recording too, nice move

Good job. Please keep us posted when froyo released.
Sent from my GT-I9000M Ver. UGJH2 using XDA App on Bell Mobility Network

sorry to say but some tech reps are more informed than others because they take time to do their own independant research. One tech i talked to barley knew a thing about the galaxy S, while another rep was fascinated by it and couldnt wait to get their own. Mine is in repair for faulty internal SD, lets hope froyo will fix the gps, as i didnt send it in for that issue.

Those who know something about the Galaxy S (and other smartphones) are the so-called "data" support.
1-877-328-2123 (choose language and then select the first option in the menu)

I agree data support are the only ones that know anything. I called customer service like 5 times before they gave me someone that knew anything, ala data support.
Sent from my GT-I9000M using XDA App

Well, I think that of course the response is "we haven't heard about any bugs". It's business -- they aren't allowed to admit to anything unless an order comes from the top to announce that a certain bug .. or a few bugs have been found. I haven't seen any admittals from Samsung that SGS is slow, laggy and the 2.2 update is crap. Or that there are any bugs at all. That would crash sales.

Same here
I got pretty much the same info. been through the same ordeal. I don't think I can last til the end of november for a maybe fix that might not fix anything or might get pushed back to january or even february or??? At least now with them endorsing the issue it should not be as hard to fight for an exchange, maybe get a Z.....

root your bell sgs, go to /system/etc, open gps.conf
change from:
NTP_SERVER=north-america.pool.ntp.org
To:
NTP_SERVER=xtra1.gpsonextra.net
you don't even have to change *#1472365#*. I get lock to 10 sat in Montreal within 30sec. give it a try!

sbcmp3 said:
root your bell sgs, go to /system/etc, open gps.conf
change from:
NTP_SERVER=north-america.pool.ntp.org
To:
NTP_SERVER=xtra1.gpsonextra.net
you don't even have to change *#1472365#*. I get lock to 10 sat in Montreal within 30sec. give it a try!
Click to expand...
Click to collapse
Well that's not the GPS bug I am talking about. My GPS locks just fine (as already said). The problem is that it is not always precise. But anyways xtra1.gpsonextra.net seems farther aways (mesured by ping times) than north-america.pool.ntp.org, so it should not fix anything.
And north-america.pool.ntp.org works just fine on my HTC Hero.

thurtig said:
Well, I think that of course the response is "we haven't heard about any bugs". It's business -- they aren't allowed to admit to anything unless an order comes from the top to announce that a certain bug .. or a few bugs have been found. I haven't seen any admittals from Samsung that SGS is slow, laggy and the 2.2 update is crap. Or that there are any bugs at all. That would crash sales.
Click to expand...
Click to collapse
Well the thing is, when you know that there is a bug and you hide it to increase your sales, you do not deserve any customers.

zorxd said:
At least I have an audio recording of Bell telling me that the bug will be fixed with an update in November. Better than nothing I guess.
Click to expand...
Click to collapse
I am very curious as to what software you used to record that call?
You didn't use a Korean Galaxy S (SHW-M110S) by any chance, did you? Because its firmware has a native call recorder function that I would die to get my hands on, but unfortunately Samsung doesn't allow international Galaxy S users to flash to the Korean firmware Send me a PM if you know how to force flash it!

dillovic said:
I am very curious as to what software you used to record that call?
You didn't use a Korean Galaxy S (SHW-M110S) by any chance, did you? Because its firmware has a native call recorder function that I would die to get my hands on, but unfortunately Samsung doesn't allow international Galaxy S users to flash to the Korean firmware Send me a PM if you know how to force flash it!
Click to expand...
Click to collapse
I am a proud user of the Asterisk PBX, which I installed on my OpenWRT router . I used that to record, not my cell phone.

zorxd said:
Well the thing is, when you know that there is a bug and you hide it to increase your sales, you do not deserve any customers.
Click to expand...
Click to collapse
All companies do that. Focusing on all the bugs takes the attention from the good to the bad. Basic stuff. All the companies that made you any of the things you own operate on the same principle. This is business. This is life.
But this does not mean they are not working hard on fixing the issues -- believe me, they are. Our comments and complaints are very important in bringing these things out. Stuff that gets discussed here on XDA dev is _vital_.

sbcmp3 said:
root your bell sgs, go to /system/etc, open gps.conf
change from:
NTP_SERVER=north-america.pool.ntp.org
To:
NTP_SERVER=xtra1.gpsonextra.net
you don't even have to change *#1472365#*. I get lock to 10 sat in Montreal within 30sec. give it a try!
Click to expand...
Click to collapse
Interesting- this is one fix I hadn't seen before. Where did you read about it?

zorxd said:
Oh wait. The update to 2.2 is already released in some parts of Europe. I am not even sure that it fixes the GPS. At least I have an audio recording of Bell telling me that the bug will be fixed with an update in November. Better than nothing I guess.
Click to expand...
Click to collapse
thats rite live in the uk and upgraded ma android to 2.2 using kies reg mod and guess what it made the GPS worst. it wont go two streets without losing gps signal. theres no hope i heard it may even be a hardware fault.

why sammy still roll out many new ics for many country if ics got kernel brick proble

share your idea, i not sure would i update my phone with safe or risk firmware

The Samsung official updates are risk free... Bricks occur by doing wipes in CWM..

Those who bricked even doing the regular factory reset has a HISTORY of flashing modified firmware. Virgin phones are not affected, imho.
Zapped through server hops to XDA forums

praetorius said:
Those who bricked even doing the regular factory reset has a HISTORY of flashing modified firmware. Virgin phones are not affected, imho.
Zapped through server hops to XDA forums
Click to expand...
Click to collapse
Virgins don't use Gnotes, they would be scared of something so big

friedje said:
Virgins don't use Gnotes, they would be scared of something so big
Click to expand...
Click to collapse
+1

vivek2701 said:
The Samsung official updates are risk free... Bricks occur by doing wipes in CWM..
Click to expand...
Click to collapse
it's not true

friedje said:
Virgins don't use Gnotes, they would be scared of something so big
Click to expand...
Click to collapse
Good one lol
Elle est bonne celle la

friedje said:
Virgins don't use Gnotes, they would be scared of something so big
Click to expand...
Click to collapse
+1 that means you have to risk to get what you wanted.

vivek2701 said:
The Samsung official updates are risk free... Bricks occur by doing wipes in CWM..
Click to expand...
Click to collapse
You should know that this isnt true... Brick with ICS stock have happened... no CWM involved at all.

I guess they depend on that OTA and Kies update are not Wipe upgrade so no one will have a problem. Still, it's not a good idea to give people a poisoned Ice Cream!

So far in my country (Singapore), I have not heard of super bricks on the local forums yet.
They warned about no cwm wipes though .
Closest so far was someone who softbricked at bootloader after OTA update, then WIPED and FACTORY RESET his phone, and failed too.
Saved by flashing ICS via Odin.
Time will tell over the weekend about this issue.

vivek2701 said:
The Samsung official updates are risk free... Bricks occur by doing wipes in CWM..
Click to expand...
Click to collapse
WRONG. There are reported instances of people bricking in stock factory reset.

praetorius said:
Those who bricked even doing the regular factory reset has a HISTORY of flashing modified firmware. Virgin phones are not affected, imho.
Zapped through server hops to XDA forums
Click to expand...
Click to collapse
Is this true? I updated OTA and did a full wipe in stock recovery (how could I imagine that was risky?). Never flashed anything onto this Note before. Now, everything works (except for the heating and the poor battery life, due to wakelocks, i guess) but I'm scared to death, so i haven't even tried to go back to GB via pc odin.
Has anybody got a hard brick doing factory reset in a "virgin" Note??

oscarsalgar said:
Is this true? I updated OTA and did a full wipe in stock recovery (how could I imagine that was risky?). Never flashed anything onto this Note before. Now, everything works (except for the heating and the poor battery life, due to wakelocks, i guess) but I'm scared to death, so i haven't even tried to go back to GB via pc odin.
Has anybody got a hard brick doing factory reset in a "virgin" Note??
Click to expand...
Click to collapse
Seems to be lots of guess work going on. I have been checking my local forums, so far nothing out of the ordinary. Not sure about the other regions though.
The thing is that the bug has a probability of bricking your phone each time a wipe occurs, making it practically difficult to tell whether our OTAs are actually immune or we are being lucky thus far.

iihito702 said:
share your idea, i not sure would i update my phone with safe or risk firmware
Click to expand...
Click to collapse
Because its SAMSUNG
Slow (on updates)
Absurd (with end user policies)
Meaningless (this does not need an explanation)
Selfish and shameless (won't admit there's a bug)
Unreliable (isn't it?)
Neglected (end users are always neglected)
Garbage (garbage software on great hardware)
I hope this helps, OP.

Well I guess that Samsung are looking at it like this.
Problem nearly only occurs in CWM during wipe/reset so people effected are nearly "only" the ones that have moddified there phones. I dont think its because Samsung does not care about the "modding/developer" comunity but this is only a very small percent of the total number of customers who buy Note's.
Secondly.
As far as I have seen all official OTA roll-out have been non-wipe. Which mean most people will never wipe there phone. Even then out of these only a VERY few will actually have any problem and I guess Samsung will simply take those warrenty costs that might come from that.

Boy124 said:
Because its SAMSUNG
Slow (on updates)
Absurd (with end user policies)
Meaningless (this does not need an explanation)
Selfish and shameless (won't admit there's a bug)
Unreliable (isn't it?)
Neglected (end users are always neglected)
Garbage (garbage software on great hardware)
I hope this helps, OP.
Click to expand...
Click to collapse
Bahhh they all suck. I'm coming from all HTC and this phone to factory support ain't no different..
I remember the little game HTC played with us EVO users when they limited our fps to 30 and tried stroking us it was a limitation due to HDMI out or whatever..
Then someone here cracked it and they changed their tune.
At least we aren't dealing with locked boot loaders. All these companies suck so I buy the best hardware I can and run a cyanogenmod variant.
Sent from my GT-N7000

senectus said:
You should know that this isnt true... Brick with ICS stock have happened... no CWM involved at all.
Click to expand...
Click to collapse
Anyone you personally know who've experienced this?
Sent from my GT-N7000 using Tapatalk 2

Entropy512 said:
WRONG. There are reported instances of people bricking in stock factory reset.
Click to expand...
Click to collapse
Reported but never really confirmed. Could be just a case of user error.
Sent from my GT-N7000 using Tapatalk 2

Honestly, there have been a lot of "reported" bricks even before lpy came out due to user error. It's just now that it's being highlighted because a few hardcore flashers experienced it. I personally think it's being blown out of proportion. Just my opinion i'm a member of a lot of note forums with regular people who don't do hardcore stuff except flash stock roms and never do i see them posting that thier phones got bricked due to lpy or any stock ics roms released by samsung.
Sent from my GT-N7000 using Tapatalk 2

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.