Database Users

plz vote ( are u with LPY ICS or going back to GB)

THERE IS ANOTHER POST AND POLL THIS IS REDUNDANT
~~~THREAD CLOSED~~~
plz vote ( are u with ICS or going back to GB)

There is already a post with this exact same question and a poll to answer.
Pointless waste of a thread.
On topic: LPY ICS !

Using stock ics latest update and ....hell no! No never gb for me. This rom is f!cking great. All i need now is a custom kernel(thats made with original sourses). No home made brick kernels with no wifi, black camera screen, buggy speaker.

updated to LPY two days ago... loving it so far...
wifi is good, battery life is good, no overheating problems...
The only 'complaint' i have is that it seems to be a bit of a memory hog... but i can wait for a strimmed down custom Rom based on this one to take care of that issue...
overall, pretty damn happy with it
M

Was on stock ics rooted with a few home made improvements and loving it but ......... I brought my note outright without contract so should anything go wrong I'm looking at a £400 paper weight, not worth the risk so..... I'm back to CM9 for now

just i want to know the no of bricked phones compared to all

ratcom said:
Was on stock ics rooted with a few home made improvements and loving it but ......... I brought my note outright without contract so should anything go wrong I'm looking at a £400 paper weight, not worth the risk so..... I'm back to CM9 for now
Click to expand...
Click to collapse
Considering what we've seen CM9, repacked i9220 kernel, or home made kernel has been the common denominator in every brick

Totally using official ics and loving it. ;-)
Sent from my GT-N7000 using XDA Premium HD app

Note_E said:
Considering what we've seen CM9 has been the common denominator in every brick
Click to expand...
Click to collapse
so i am lucky i didnt try CM9 till now and having no problems with lpy now
but shall i do a factory reset or wipe ?

If it ain' broken, DON'T FIX IT!!!
Zapped through server hops to XDA forums

sehooo said:
so i am lucky i didnt try CM9 till now and having no problems with lpy now
but shall i do a factory reset or wipe ?
Click to expand...
Click to collapse
Are you rooted with CWM?

Youhou another useless post about lpy supposed bug.
Seriously, just make the moderator make a post-it and it'll be enough, no need to open 100 post a day about that.
And what is this poll supposed to do ? Found a solution ? There arent enough "discussions" about it yet ?

Ueihtam said:
Youhou another useless post about lpy supposed bug.
Seriously, just make the moderator make a post-it and it'll be enough, no need to open 100 post a day about that.
And what is this poll supposed to do ? Found a solution ? There arent enough "discussions" about it yet ?
Click to expand...
Click to collapse
On one level I agree with you. However when you have a trusted dev saying it's bugged and that his home grown kernel is not, yet all bricks lead back to CM9/repacked i9220, it makes it hard for me to believe that source considering the amount of donations. I look at what's happening and the results of the numerous upgrades being flashed over the past few days to use that as an indicator. Until LPY kernel source is released and the experts can comb through it, there is no real answer. I don't use CM, it's just not my flavor...but I really mean no disrespect to the work put forth by the many people who do work on CM.
It's ok for the community to collaborate and come to a unified consensus.

Note_E said:
Are you rooted with CWM?
Click to expand...
Click to collapse
just flashed LPY and not rooted till now

sehooo said:
just flashed LPY and not rooted till now
Click to expand...
Click to collapse
There should be no reason to do a full wipe if you're not getting force closes or other weird screen issues like pixel salads or SODs (screen of death where screen stays black for a good minute with responding).

Note_E said:
On one level I agree with you. However when you have a trusted dev saying it's bugged, but his home grown kernel is not, but all bricks lead back to CM9/repacked i9220, it makes it hard for me to trust that source considering it's a source of donations.
It's ok for the community to collaborate and come to a unified consensus.
Click to expand...
Click to collapse
just i want to know no of bricked phones as there are alot of rumors and i read alot and didn't find the solution to get back to gb OR stay on LPY and go for root

Note_E said:
On one level I agree with you. However when you have a trusted dev saying it's bugged and that his home grown kernel is not, yet all bricks lead back to CM9/repacked i9220, it makes it hard for me to trust that source considering the amount of donations. I don't use CM, it's just not my flavor...but I really mean not disrespect to the work put forth by the many people who do work on CM.
It's ok for the community to collaborate and come to a unified consensus.
Click to expand...
Click to collapse
Correction: only 1 brick was tied to CM9 and still no guarantee that cm9 was the cause in any way.
The leaked kernel? Yes bricks are confirmed to be related to wipes and stuff using that kernel.
There is 0 evidence than CM9 has anything to do with a single brick. Just because people that have bricked have previously used CM9 is not a factor. If that was the case then why not say that official samsung gb was the cause, after all, Every Brick thats been reported was running that rom at some point.
Your arguement is invalid.
Note: CM9 is great, fix the few issues with speaker and whatnot and I will never use stock again!

Note_E said:
There should be no reason to do a full wipe if you're not getting force closes or other weird screen issues like pixel salads or SODs (screen of death where screen stays black for a good minute with responding).
Click to expand...
Click to collapse
i got force close with some applications like youtube and applications which need root which i setuped before on rooted GB before upgrading

vetchems said:
Correction: only 1 brick was tied to CM9 and still no guarantee that cm9 was the cause in any way.
The leaked kernel? Yes bricks are confirmed to be related to wipes and stuff using that kernel.
There is 0 evidence than CM9 has anything to do with a single brick. Just because people that have bricked have previously used CM9 is not a factor. If that was the case then why not say that official samsung gb was the cause, after all, Every Brick thats been reported was running that rom at some point.
Your arguement is invalid.
Note: CM9 is great, fix the few issues with speaker and whatnot and I will never use stock again!
Click to expand...
Click to collapse
Correction: before "official" CM9 there was imilkas...which bricked many others. then there was xplod's donated device during kernel development which you can take that as you will.
My argument is valid...I'm using common denominators. But if you read my whole post, I said there is no real answer...so I'm not trying to be "right"...it's my opinion/observation

I moved back my sister phone to GB because of the brick issues in LPY ICS and high battery usage !
Sent from my GT-I9100 using Tapatalk

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

Odin & Kies for noobs

The GS3 will be my first Samsung smartphone and I've heard a little bit about Odin and Kies but not really sure what they are. Anybody care to explain them to me?

ODIN good explanation in this thread .
http://forum.xda-developers.com/showthread.php?t=1671969
jje

Thank you sir

916x10 said:
Thank you sir
Click to expand...
Click to collapse
Read carefully use it with a bad cable or the wrong download and you will have hours of fun trying to wake your phone back up.
Sent from my SGH-T959 using XDA

accordex said:
Read carefully use it with a bad cable or the wrong download and you will have hours of fun trying to wake your phone back up.
Click to expand...
Click to collapse
Thanks for the heads up. I'm the kind of person who will ask questions just to make sure before I take on such a task since I don't have money to just go and buy another one on a whim if I mess it up so hopefully I'll never run into the wrong download issue. Coming from the A2, we used RSDLite to flash firmwares to our phones, very similar to ODIN although nowhere near as advanced and polished.

916x10 said:
Thanks for the heads up. I'm the kind of person who will ask questions just to make sure before I take on such a task since I don't have money to just go and buy another one on a whim if I mess it up so hopefully I'll never run into the wrong download issue. Coming from the A2, we used RSDLite to flash firmwares to our phones, very similar to ODIN although nowhere near as advanced and polished.
Click to expand...
Click to collapse
np... most roms / kernels /...anything flashable will include an md5 check... use that as well...
Another heads up is sometimes op will say remove all ticks from odin... this refers to re-partition auto reboot and reset time...do that but ask first because I've flashed things such as stock factory images that generally need re-partition checked and op will either not mention it or say remove all ticks...
Sent from my SGH-T959 using XDA

accordex said:
np... most roms / kernels /...anything flashable will include an md5 check... use that as well...
Another heads up is sometimes op will say remove all ticks from odin... this refers to re-partition auto reboot and reset time...do that but ask first because I've flashed things such as stock factory images that generally need re-partition checked and op will either not mention it or say remove all ticks...
Click to expand...
Click to collapse
Oh wow...a bit more involved with these roms and stuff but glad you brought this to my attention. Can't wait to get the first one under my belt so I can get the hang of it.

Is the GS3 unbrickable or not? I read with the GS2 flashing anything with an ICS recovery could brick your phone, because the firmware had a command to destroy certain sectors. Or something like that.
I'm asking because I've also read Samsung phones are pretty much unbrickable, unlike e.g. HTC phones which could get bricked for instance if you pulled the battery while flashing a radio.

ECrispy said:
Is the GS3 unbrickable or not? I read with the GS2 flashing anything with an ICS recovery could brick your phone, because the firmware had a command to destroy certain sectors. Or something like that.
I'm asking because I've also read Samsung phones are pretty much unbrickable, unlike e.g. HTC phones which could get bricked for instance if you pulled the battery while flashing a radio.
Click to expand...
Click to collapse
It's always a gamble.... vibrant was unbrickable...then Ics came along and coasted for a while now people are getting bricks due to it destroying the interal sd... my theory is always wait for wrinkles to get worked out...haven't checked in a while but I'm sure it's fixed or being worked on...Either way for the first few months stick with source based roms...
Anything with the word "ported" in it could be risky...eg...miui,cm9 and others.... but yes you will have much better odds with Samsung over other phones as they are much easier to recover.
Sent from my SGH-T959 using XDA
---------- Post added at 10:40 PM ---------- Previous post was at 10:27 PM ----------
Haven't kept up with GS2....
That is really interesting tho...where did you read that? I wonder if Sammy is throwing **** out there to mess up phones?
It always pisses me off when even to this day I read articles about ICS updates and manufacturers stating in official press pieces, the fact that phones like GS1 and equivalents "hardware cannot support" ics...biggest bunch of BS ever...when in fact the ICS ports that have been available for months now, and worked, until the recent problems, have made these phones scream and actually usable with very little lag/annoyances ...they are beyond capable of handling it. It's a marketing ploy and everyone knows it.
They've been called out on it plenty, it just get's swept under the rug for some reason.

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.

Samsung and the emmc chips

Well, I recently was talking to a friend who got a Galaxy S III some time ago.. And his device suddenly had some kind of SOD..
He was stock TW and non rooted.. He's like the 99% of the people out there whom will never flash a custom rom So he gave me the device to see if I could fix it..
First thing I noticed was I could not enter to recovery or odin mode, changed battery, connected to pc and nothing.. Was completely dead.. So i started reading about on sIII forums and seems like SIII its infected with a bug called SDS (sudden death syndrome) i was like wtf?.. The bug consist in: you could be either charging your device or happily using it and when the screen goes off the device will never ever again will turn on.. The effect of the bug? It burns the emmc chip and you either lose your device (like him because he bought it in Europe and we are from Venezuela so no warranty) or if you have warranty you will receive a new device..
Thing its that after seeing that.. Damn our mmc_cap_erase bug its nothing compared to that..
What the hell its samsung doing with the quality control and the engineering?
Devs in SIII forums already patched the bug in the kernel but hey that's a preventive solutions.. Not a fix for already bug triggered devices.
So if any of you have an SIII or a family member.. Go read about it and patch it
Edit: here a link to the issue http://forum.xda-developers.com/showthread.php?t=2091045
Tapatalking on my n7000

msedek said:
Well, I recently was talking to a friend who got a Galaxy S III some time ago.. And his device suddenly had some kind of SOD..
He was stock TW and non rooted.. He's like the 99% of the people out there whom will never flash a custom rom So he gave me the device to see if I could fix it..
First thing I noticed was I could not enter to recovery or odin mode, changed battery, connected to pc and nothing.. Was completely dead.. So i started reading about on sIII forums and seems like SIII its infected with a bug called SDS (sudden death syndrome) i was like wtf?.. The bug consist in: you could be either charging your device or happily using it and when the screen goes off the device will never ever again will turn on.. The effect of the bug? It burns the emmc chip and you either lose your device (like him because he bought it in Europe and we are from Venezuela so no warranty) or if you have warranty you will receive a new device..
Thing its that after seeing that.. Damn our mmc_cap_erase bug its nothing compared to that..
What the hell its samsung doing with the quality control and the engineering?
Devs in SIII forums already patched the bug in the kernel but hey that's a preventive solutions.. Not a fix for already bug triggered devices.
So if any of you have an SIII or a family member.. Go read about it and patch it
Tapatalking on my n7000
Click to expand...
Click to collapse
Thanks.my cousin just bought one but it has warranty.i think i cant make him trust me.what if i brick the phone?or what if after some time he bricks the phone?so their will be no warranty for a phone that is modified
I think i should warn him and let him decide
Sent from my GT-N7000 using xda premium

Samsung :thumbdown: for that..
click THANKS BUTTON if I helped…
Recognized Distributor™

i know of a close relative with a white s3 , after two months of purchase the set stopped charging from wall socket, the charging worked with laptop ......since he had warranty he was told the motherboard needed replacement and he got that done. the back of it has a spider-like faint grey mark and he asks me if its cracked or what ....he doesnt want to go back to service centre and wont let me root it and he doesnt have patience for xda. he is on 411 still.
he didnt pay for it himself, doesnt have a job yet and its not a gift...pretty chaotic situation if u ask me !!

bloody money grubber *** *****. Poor quality control. There's still no permanent solution for N7000 emmc brick bug.

sepehrthegreat-iran said:
Thanks.my cousin just bought one but it has warranty.i think i cant make him trust me.what if i brick the phone?or what if after some time he bricks the phone?so their will be no warranty for a phone that is modified
I think i should warn him and let him decide
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Talk to him and make him read about it here
http://forum.xda-developers.com/showthread.php?t=2091045
Check if he have an affected device..
Tapatalking on my n7000

I sold My s3, a few days ago, which was my first choice and bought note.
Now I read about brick bug. Wtf?
Can I buy device and be safe and peacefull?!
Sent from my GT-N7000 using xda app-developers app

krivinash said:
I sold My s3, a few days ago, which was my first choice and bought note.
Now I read about brick bug. Wtf?
Can I buy device and be safe and peacefull?!
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Just flash a safe kernel according to your rom and live in peace
Tapatalking on my n7000

msedek said:
Just flash a safe kernel according to your rom and live in peace
Tapatalking on my n7000
Click to expand...
Click to collapse
The brick bug on the Note shouldn't be a problem anymore. Just flash the PhilZ kernel which gives you root without increasing the flash counter and you're Note is fixed. You can also download Chainfires got brick bug app.to see if your Note is affected at all. Or you download the brick bug app from the play store which does the same.
Sent from my revived Galaxy Note

N7000
My Samsung Galaxy Note is on JB Alliance Rom XXLSC Beta1.1 which comes with it's own kernel and I don't think PhilZ is supporting it, PhilZ and Alliance Cook had a minor misunderstanding/fallout, (I could be getting my Roms mixed up) I've flashed different Roms 10+ times. Started to worry reading threads on here so downloaded the eMMC Brickbug Check app. All's good here

Maybe you wiped on STOCK ICS KERNEL which is known to cause the Brickbug
click THANKS BUTTON if I helped…
Recognized Distributor™

Arobase40 said:
The brick bug on Note is just a legend... ^^
The only safe kernel I'm aware of is the stock one !
The sole time I flashed a non stock kernel I got my Note fully bricked !!!
Click to expand...
Click to collapse
Yeh you are right!so can you post a video wiping on your stock kernel???!!!
I really appreciate the job that Phil and other Devs are doing
Sent from my GT-N7000 using xda premium

Wrong forum yo dicuss it, but u have a good point. I have also discussed this on s3 forum, but seems like some regions got that buggy phone or maybe this is the samsungs way of self killing the device....whatever it is one should get what they paid for.
Well for my note i have that brick bug thing but i factory resetted my stock rom so many times and my device is fine. So i think stock roms are harmless and this emmc_cap was put to prevent users from using a custom ics in the initial days ,which definitely the devs figured out and fix it in their custom kernel.
Sent from my GT-N7000 using xda app-developers app

qazibasit said:
Wrong forum yo dicuss it, but u have a good point. I have also discussed this on s3 forum, but seems like some regions got that buggy phone or maybe this is the samsungs way of self killing the device....whatever it is one should get what they paid for.
Well for my note i have that brick bug thing but i factory resetted my stock rom so many times and my device is fine. So i think stock roms are harmless and this emmc_cap was put to prevent users from using a custom ics in the initial days ,which definitely the devs figured out and fix it in their custom kernel.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
What you believe it's completely different from what's a FACT... The bug its not some legend based on empirical trials.. It's been proved that mmc_cap_erase triggers the bug because the mmc chip can't handle secure erase formating .. Simple the chip gets damaged..
The bug was introduced on ICS kernels.. And it's so true that Samsung even disabled secure erase from JB kernels because they say that insecure erase its not harmful...
We disagree because it hasn't been proven (that insecure erase its safe) .. So the best way to be safe its disabling mmc_cap_erase and no formating at all..
To everyone talking nonsense about wiping on stock ICS kernels, next time I'll report you all because that's misleading.. Maybe you have been lucky wiping but that's the problem.. It can happen on wipe number 1 or wipe number 1000.. Who knows..
Tapatalking on my n7000

msedek said:
What you believe it's completely different from what's a fact... The bug its not some legend based on empirical trials.. It's been proved that mmc_cap_erase triggers the bug because the mmc chip can't handle secure erase commands.. Simple the chip gets damaged..
The bug was introduced on ICS kernels.. And it's so true that Samsung even disabled secure erase from JB kernels because they say that insecure erase its not harmful...
We disagree because it hasn't been proven (that insecure erase its safe) .. So the best way to be safe its disabling mmc_cap_erase and no formating at all..
To everyone talking nonsense about wiping on stock ICS kernels, next time I'll report you all because that's misleading.. Maybe you have been lucky wiping but that's the problem.. It can happen on wipe number 1 or wipe number 1000.. Who knows..
Tapatalking on my n7000
Click to expand...
Click to collapse
Agree with the misleading but a little bit respect for the people sharing own experience with us is not so bad!
Any user who reads this attention:
<<do not,under any condition,I repeat do not wipe from your stock ICS recovery>>
sent from galaxy s4(testing dev edition) using xda premium

sepehrthegreat-iran said:
Agree with the misleading but a little bit respect for the people sharing own experience with us is not so bad!
Any user who reads this attention:
sent from galaxy s4(testing dev edition) using xda premium
Click to expand...
Click to collapse
I'm not disrespecting anyone.. Own experience it's bullcrap.. Software developing and electronics engineering its not popular believes or "experiences" everything its done by scientific methods, procedures and knowledge of how things works..
A clear example could be that an engine its build to reach [email protected] if you force the engine beyond that it will get damaged...
Now some people could force it to 160kph and maybe it will work some times.. But at some point it will break.. And you know this because engineers made the engine to work Max at those speeds and RPMs..
It's matter of design.. Not "experiences"
Tapatalking on my n7000

Its been reported that stock ICS is unsafe, since the day it was released, people know about it and avoid it, so anyone saying that it is safe is talking nonsense, if they wanna take the risk and brick their device then thats their choice.
Moving back on to the S3 chips, my GF has had hers several months now and luckily havent encountered any issues at all, I tend to only find device faults AFTER ive purchased them !! i really need to research more before buying
the S3 is 100% stock, my GF wont let me mod it but luckily the device has warranty for the lenght of the contract which is 24 months, so if it ever breaks within this time they'll just fix it for me free of charge
Still, it makes me wonder WTF are a giant company like Samsung doing about this issue ? SGS 2, SGS 3, SGN 1 (unsure about SGN2)
this isnt acceptable from Samsung, regardless if <5% of devices suffer this, I would expect sudden death and insane chips from a cheap chinese knock off, but not a £500 smart phone.

If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app

qazibasit said:
If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
They knew about it. It was fixed in Galaxy Nexus eMMC firmware but yet they kept shipping other devices with the same firmware.
Cut the crap: Do you know more about the emmc brick bug than some elite and recognized devs here ?

qazibasit said:
If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Before ICS (gb and older) , Android used recursive deletion.. (no mmc_cap_erase procedures in the kernel).. Samsung didn't know about it because the chip was designed under another required process and there's no way to know this kind of things until you produce something in big scales.. As you said you could spend months wiping everyday on stock ICS and never get brick, but after 6 months of doing it the next day you brick...
Entropy went to samsung and he tried several times to brick a note in front of samsung engineers with no luck.. But the bug its there from the first ICS firmware to the very last and considering we are still officially on ICS, i dont think it's a "retro" information...
Exynos source has nothing to do with the emmc chip and what kind of delete/formating methods will damage it.. Heck even deleting big files (over 500 mb) could trigger the bug.
Once again you are talking nonsense
Tapatalking on my n7000