Database Users

I just Killed my SII

I tried to put a PIT wih odin on my galaxy and something stucks . I CANT START UP MY PHONE.
-download mode - not working
-recovery mode - not working
-jig - not working
When i plug in the phone get worms
Same posts:
http://forum.xda-developers.com/showthread.php?t=1125162
http://forum.xda-developers.com/showthread.php?t=1183454
http://forum.xda-developers.com/showthread.php?t=1120692
I tried this tutorial:
http://androidworld.nl/forum/samsung-galaxy-s/16227-odin-rom-litening-rom-v5-odin-editie.html
Any solutions?

your phone is stuffed, first of all you flashed the wrong PIT and firmware for the wrong phone the one you flashed is for Galaxy S not S2, you can try the usb jib but 99% sure it wont work, youll have to send it back to samsung or get it repaired at a repair center

My warranty is lost? And what did happen so wrong that the phone cant go on?

sebyku said:
My warranty is lost? And what did happen so wrong that the phone cant go on?
Click to expand...
Click to collapse
Read the post above yours.
You flashed galaxy S software, not galaxy s2. Different software for different hardware.
Its like filling up with diesel when your car runs on unleaded.
Sent from my GT-I9100 using XDA Premium App

You can try mobile tech videos. They charge $60 for unbricking.

sebyku said:
My warranty is lost? And what did happen so wrong that the phone cant go on?
Click to expand...
Click to collapse
You flashed the wrong software and the wrong partition table to it... You should've read up on the links you gave in your first post before flashing. Second if you'd read up on the flashing instructions on this site you would've known not to use a pit file unless absolutely necesary. And finaly when you encounter a file named s1_odin_20100512.pit which clearly has S1 (meaning Galaxy S1) and the date 12-05-2010 (which is before the S2 was even announced) that should've made you a little suspecious as to whether you had the right files.
You can send the phone to Smasung and hope they don't find out what happened. If they don't they'll repair it for free, if they do you're screwd and you'll have to pay for the repair.

ok mate,
u have 1 of 2 options:
1- u need to send it back for the service centre
2- send it for a JTAG service close to ur place
http://www.youtube.com/watch?v=zN7le4GmxZs

Omg, what a waste of a great phone.
Why didn't you actually study everything properly before doing anything like this to a top of the market phone?
Transmitted from a Galaxy far far away via XDA telepathy.

Yet another motivation why I won't bother with Rooting, roms or just flashing in General.
Flashing should be a once a in blue thing, this phone is way to fast, does not need at ALL any speed enhancements, you Should fine just experimenting apps. I highly encourage everyone not to flash daily, enjoy what you have. don't loose $800 for nothing or have regrets.

Extreme184X said:
Yet another motivation why I won't bother with Rooting, roms or just flashing in General.
Flashing should be a once a in blue thing, this phone is way to fast, does not need at ALL any speed enhancements, you Should fine just experimenting apps. I highly encourage everyone not to flash daily, enjoy what you have. don't loose $800 for nothing or have regrets.
Click to expand...
Click to collapse
Flashing is safe as long as you are able to read simple text and perform the task without errors by understanding the instructions.
Transmitted from a Galaxy far far away via XDA telepathy.

Extreme184X said:
Yet another motivation why I won't bother with Rooting, roms or just flashing in General.
Flashing should be a once a in blue thing, this phone is way to fast, does not need at ALL any speed enhancements, you Should fine just experimenting apps. I highly encourage everyone not to flash daily, enjoy what you have. don't loose $800 for nothing or have regrets.
Click to expand...
Click to collapse
Driving a car is pretty dangerous too

Extreme184X said:
Yet another motivation why I won't bother with Rooting, roms or just flashing in General.
Flashing should be a once a in blue thing, this phone is way to fast, does not need at ALL any speed enhancements, you Should fine just experimenting apps. I highly encourage everyone not to flash daily, enjoy what you have. don't loose $800 for nothing or have regrets.
Click to expand...
Click to collapse
I'm pretty sure our devices are idiot proof unless you go about doing absolutely absurd things like flashing the wrong files and repartitioning your device with a table of an other device. If the people would just read the risk is minimal. Like this OP who did his research AFTER bricking, if only he did it before hand. And what gets me the most, in 2 of the 3 threads he links to the answer is present. Wrong pit file need JTAG programming. But yet again instead of reading through the threads he opts to start yet another thread...
Sent from my GT-I9100 using XDA Premium App

Extreme184X said:
Yet another motivation why I won't bother with Rooting, roms or just flashing in General.
Flashing should be a once a in blue thing, this phone is way to fast, does not need at ALL any speed enhancements, you Should fine just experimenting apps. I highly encourage everyone not to flash daily, enjoy what you have. don't loose $800 for nothing or have regrets.
Click to expand...
Click to collapse
No way. I'm totally new to this and it's brain dead simple if you read at all. A million people have said don't use a pit file. But people do it anyway.

GIR said:
I'm pretty sure our devices are idiot proof
Click to expand...
Click to collapse
No such thing, no matter what you do someone will make a better idiot. Exhibit A: this thread.

Idiot number 3 with a galaxy S pit, if you are keeping count.
Darwin would be proud
Sent from my GT-I9100 using XDA Premium App

Extreme184X said:
Yet another motivation why I won't bother with Rooting, roms or just flashing in General.
Flashing should be a once a in blue thing, this phone is way to fast, does not need at ALL any speed enhancements, you Should fine just experimenting apps. I highly encourage everyone not to flash daily, enjoy what you have. don't loose $800 for nothing or have regrets.
Click to expand...
Click to collapse
yes i know but people won't listen
http://forum.xda-developers.com/showthread.php?t=1195250

The Post was in deutch .. i just copied the text and put it in google translate ... and i didn`t see in that site .. use only for galaxy s .. sorry my mistake .. i will send it to warranty ..

sebyku said:
The Post was in deutch .. i just copied the text and put it in google translate ... and i didn`t see in that site .. use only for galaxy s .. sorry my mistake .. i will send it to warranty ..
Click to expand...
Click to collapse
Good luck with that - your warranty is very much null, void and gone...

sebyku said:
The Post was in deutch .. i just copied the text and put it in google translate ... and i didn`t see in that site .. use only for galaxy s .. sorry my mistake .. i will send it to warranty ..
Click to expand...
Click to collapse
Google probably translated it incorrectly because it's Dutch.

B3311 said:
Good luck with that - your warranty is very much null, void and gone...
Click to expand...
Click to collapse
Unless they don't notice!
Just say it was a kies update gone wrong!
Then pray

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.

Its been a good run.

Well, after some misinformed past rumors, I am finally leaving the Evo. I make this thread not because I feel like I'm 'important' or that anyone will care, but because of the community. Despite the past ICS fallout between users and developers, the Evo community has been one of the best on XDA, and can say that it was nice being apart of it. Made some good friends, and a few enemies, but comes with the territory. I'll still pop in from time to time, but I know I will see some of you in my new home, the Galaxy S III [will be here tomorrow]. Do keep the Evo name standing, as its a great device.

See ya around You know where to find me if you need anything...hahahaha

mazdarider23 said:
See ya around You know where to find me if you need anything...hahahaha
Click to expand...
Click to collapse
Oh yea. I'm on the grid...just a different sector.

Well, I'm stuck with an Evo for 6 more months, so I doubt I'll be on the GSIII next, but good times here, mate and thx for everything!

HipKat said:
Well, I'm stuck with an Evo for 6 more months, so I doubt I'll be on the GSIII next, but good times here, mate and thx for everything!
Click to expand...
Click to collapse
And the same to you man, you got me on my feet so I could actually 'talk' about MIUI, instead taking a back seat educated speculation.

gtfo noob juust messing i'll be over shortly

Awwww, this makes me sad. I haven't been around much anyway, but I'll still miss you
If I ever happen to be on GTalk, hit me up. I doubt I'll be moving to the S III, but I am eligible for an upgrade so don't know... haven't really done my research yet. Send me a message and let me know how you like it once you've got it broken in.
Even if we don't have the same device, I'm sure I'll see you around. You've taught me a lot, even when you didn't realize it, and no one else has been as nice to me as you have, so thank you.

plainjane said:
Awwww, this makes me sad. I haven't been around much anyway, but I'll still miss you
If I ever happen to be on GTalk, hit me up. I doubt I'll be moving to the S III, but I am eligible for an upgrade so don't know... haven't really done my research yet. Send me a message and let me know how you like it once you've got it broken in.
Even if we don't have the same device, I'm sure I'll see you around. You've taught me a lot, even when you didn't realize it, and no one else has been as nice to me as you have, so thank you.
Click to expand...
Click to collapse
No need to be sad, and you can always hit me up on gtalk when you're on. You've got a ton of gold stars now, I've lost count. And I've seen you helping others, when you may not have thought me around. And you're very welcome, I'm glad to hear that...made me smile.
I'm still going to be around here, as I have a horded amount of knowledge...this was my first smart phone, and I think I made a great choice. I'll definitely let you know about the review, and can send you spec info.

plainjane said:
Awwww, this makes me sad. I haven't been around much anyway, but I'll still miss you
If I ever happen to be on GTalk, hit me up. I doubt I'll be moving to the S III, but I am eligible for an upgrade so don't know... haven't really done my research yet. Send me a message and let me know how you like it once you've got it broken in.
Even if we don't have the same device, I'm sure I'll see you around. You've taught me a lot, even when you didn't realize it, and no one else has been as nice to me as you have, so thank you.
Click to expand...
Click to collapse
Yeah! Where the hell HAVE you been?? (In my nicest voice)

If you're keeping your Evo you can be like me and be a forum whore lol. I'm on 7 sub forums right now, but only following on a few of them and active on 3. Mostly lurk on the others just for info. You can add me on gtalk of ya want my donation email in my profile is my gtalk name, if u got any questions about Samsung feel free to hit me up. Flashing and such is a little different than HTC and will take some time and questions to get the hang of. Got recovery, Odin and mobile Odin for your flashing needs, no more ruu's and no more unlocking bootloaders with an exploit. Odin takes care of those areas. :beer:
We are legion, for we are many.

-EViL-KoNCEPTz- said:
If you're keeping your Evo you can be like me and be a forum whore lol. I'm on 7 sub forums right now, but only following on a few of them and active on 3. Mostly lurk on the others just for info. You can add me on gtalk of ya want my donation email in my profile is my gtalk name, if u got any questions about Samsung feel free to hit me up. Flashing and such is a little different than HTC and will take some time and questions to get the hang of. Got recovery, Odin and mobile Odin for your flashing needs, no more ruu's and no more unlocking bootloaders with an exploit. Odin takes care of those areas. :beer:
We are legion, for we are many.
Click to expand...
Click to collapse
Oh yea, can do. And actually won't keep the evo [in my possession]; sending it home to my dad. He's on an optimus S and hates it, so big upgrade for him, and will do more than it needs for him. I'm actually pretty good with Odin, rooted a Galaxy S for this girl not too long ago. Odin is different, but its not bad once you get used to it, and mobile odin and triangle away do seem like a good investment.

add me on gtalk anytime, bro
https://plus.google.com/101894158128702445895

Breaks my heart. The guy that enlightened me in the ways of android and taught me everything I know and answered all my dumb question is finally.moving on . I might be joining you also on the gs3 when I have my upgrade in november. Good thing about getting a new phone is meeting and getting to know all the new people in that phones sub forum. So best of luck to you in your journey to a new galaxy
Sent from my PC36100 using XDA

HipKat said:
add me on gtalk anytime, bro
https://plus.google.com/101894158128702445895
Click to expand...
Click to collapse
*Salutes* Shall do
evo4gnoob said:
Breaks my heart. The guy that enlightened me in the ways of android and taught me everything I know and answered all my dumb question is finally.moving on . I might be joining you also on the gs3 when I have my upgrade in november. Good thing about getting a new phone is meeting and getting to know all the new people in that phones sub forum. So best of luck to you in your journey to a new galaxy
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
No worries man; you've learned a lot. And I'm still gona be here to help out. I'm free this weekend, you can pwn me in some MW3...lol. And you'll have some friends waiting for you.
But at this moment *new futurama*

teh roxxorz said:
Oh yea, can do. And actually won't keep the evo [in my possession]; sending it home to my dad. He's on an optimus S and hates it, so big upgrade for him, and will do more than it needs for him. I'm actually pretty good with Odin, rooted a Galaxy S for this girl not too long ago. Odin is different, but its not bad once you get used to it, and mobile odin and triangle away do seem like a good investment.
Click to expand...
Click to collapse
Best investment you can make on a galaxy device man, should be the first apps you purchase once you decide you're keeping the device. Yea Odin is a bit tricky at first, the things you'll probably have more questions with are the dreaded brick bug(idk if the sgs3 is plagued with that nuisance or not, I hope not) and how to avoid it, since its a permabrick if it hits you. The whole method of doing stuff on Samsung is just alien when coming from HTC. Took me a few weeks b4 I was back to flashing like a junkie again with out reading and rereading every step over and over prior to trying something new. I've had a few months with the sgs2 now so if you have questions about samsungs whole crazy zimage/recovery and how recovery is baked into the kernel and changes every time you change kernels I'm more than happy to answer em the best I can or point you in the direction of your answers atleast. :thumbup:
We are legion, for we are many.

-EViL-KoNCEPTz- said:
Best investment you can make on a galaxy device man, should be the first apps you purchase once you decide you're keeping the device. Yea Odin is a bit tricky at first, the things you'll probably have more questions with are the dreaded brick bug(idk if the sgs3 is plagued with that nuisance or not, I hope not) and how to avoid it, since its a permabrick if it hits you. The whole method of doing stuff on Samsung is just alien when coming from HTC. Took me a few weeks b4 I was back to flashing like a junkie again with out reading and rereading every step over and over prior to trying something new. I've had a few months with the sgs2 now so if you have questions about samsungs whole crazy zimage/recovery and how recovery is baked into the kernel and changes every time you change kernels I'm more than happy to answer em the best I can or point you in the direction of your answers atleast. :thumbup:
We are legion, for we are many.
Click to expand...
Click to collapse
Much appreciated man, and actually been doing some reason: the kernel and boot image on the G S III were separated so its actually a lot safer to root. In addition I've looked up the G S III root [international version] and actually QUITE painless, even using Odin. Since there were minimal hardware specs, aside from processor of course, but I believe the root will be the same or extremely similar. I originally was going to buy the original galaxy S, but I refused to get the epic with a hard keyboard, so I went with the Evo; though not like it was a bad choice.

teh roxxorz said:
Much appreciated man, and actually been doing some reason: the kernel and boot image on the G S III were separated so its actually a lot safer to root. In addition I've looked up the G S III root [international version] and actually QUITE painless, even using Odin. Since there were minimal hardware specs, aside from processor of course, but I believe the root will be the same or extremely similar. I originally was going to buy the original galaxy S, but I refused to get the epic with a hard keyboard, so I went with the Evo; though not like it was a bad choice.
Click to expand...
Click to collapse
That's cool they seperated the kernel from the recovery now, on the ET4G there's no normal boot.img its called a zImage and has the kernel and recovery in the same partition so flashing a kernel changes your recovery. It can get quite confusing going from rom to rom and build to build and having to remember which recovery which backup was made with so you can Odin it to restore we still don't have official ICS or kernel source yet so flashing ICS roms requires first flashing a GB kernel with pure CWM to avoid a blue light of death brick. Talk about confusing, it took me a week of reading before I had the balls to try ICS but now I can mOdin el26+cwm kernel and flash ICS in my sleep. I've been running aokp since march never went back to gb except the few times I bootlooped and had to Odin to el29(latest GB ota) and start fresh. Once you get a feel for it and get any questions you have lingering out of the way its painless but the first few times you're sweating missles waiting to it to flash and boot and praying you didn't just brick, LOL. My first venture to ICS I chewed off all my nails while flashing it, I was so nervous I forgot something and was gonna fry my eMMC chip and be bricked.
ETA: what's even worse for me is I have 4 different manufacturers devices all different methods of flashing and its hard keeping it all straight, going from HTC, to Amazon to Motorola to Samsung and trying to remember which one you flash how is an exercise in frustration :banghead:
We are legion, for we are many.

-EViL-KoNCEPTz- said:
Best investment you can make on a galaxy device man, should be the first apps you purchase once you decide you're keeping the device. Yea Odin is a bit tricky at first, the things you'll probably have more questions with are the dreaded brick bug(idk if the sgs3 is plagued with that nuisance or not, I hope not) and how to avoid it, since its a permabrick if it hits you. The whole method of doing stuff on Samsung is just alien when coming from HTC. Took me a few weeks b4 I was back to flashing like a junkie again with out reading and rereading every step over and over prior to trying something new. I've had a few months with the sgs2 now so if you have questions about samsungs whole crazy zimage/recovery and how recovery is baked into the kernel and changes every time you change kernels I'm more than happy to answer em the best I can or point you in the direction of your answers atleast. :thumbup:
We are legion, for we are many.
Click to expand...
Click to collapse
Having dev'd on the Moment, I remember the zimage! Actually the best way to work with adding a kernel to a ROM

HipKat said:
Having dev'd on the Moment, I remember the zimage! Actually the best way to work with adding a kernel to a ROM
Click to expand...
Click to collapse
Its just a pain in the ass for recovery, only because every time you change kernels if the new one has a different recovery your recovery then changes. On the et4g we have cwm, rogue and acs custom recoveries, and not all backups are compatible across all recoveries so you gotta try and keep track of what goes with what since we have to use the el26 kernel with pure cwm recovery to safely flash ICS without bricking I use it for everything recovery, but that requires me to Odin the el26 kernel everytime I need to do something in recovery and since I run ICS I then have to flash an ICS kernel to reboot my phone. Its more of a hassle/annoyance than anything just cuz of all the extra steps required to flash/backup etc
We are legion, for we are many.

Do not forget us! Do not forget us! Good Luck in that new Galaxy.
Sent from my PC36100

I just cant brick my phone - WARNING ON ODIN -

Dear all,
Maybe strange.........
I just cant brick my note! Not that i want to but how? before i knew the brickbug i did:
Odin flash to a leak ICS
Rebooted in CWM And wiped Factory default.. No problem
At one time i even formatted EMMC however its called.
At this time ICS brickbug shows up in this forum and i downloaded the APK brickbug app and i seem to be vulnarable.
Today a friend comes in with a bricked note.. tellin me he was flshing from odin and it hung on first part of flash without starting. He removed phone after 30 secs.
please take notice that it can take up to 2 minutes to start flashing.
any thoughts on this story?

jeroen180 said:
Dear all,
Maybe strange.........
I just cant brick my note! Not that i want to but how? before i knew the brickbug i did:
Odin flash to a leak ICS
Rebooted in CWM And wiped Factory default.. No problem
At one time i even formatted EMMC however its called.
At this time ICS brickbug shows up in this forum and i downloaded the APK brickbug app and i seem to be vulnarable.
Today a friend comes in with a bricked note.. tellin me he was flshing from odin and it hung on first part of flash without starting. He removed phone after 30 secs.
please take notice that it can take up to 2 minutes to start flashing.
any thoughts on this story?
Click to expand...
Click to collapse
Go to the church and donate 10 euros...
You might not be so lucky next time around.
Because you didn't brick doing 1 wipe, doesn't mean that you cannot brick..
It's like getting struck by lightning, maybe you will survive the first, but it
might not save you a second time...

Well, it is a brick bug, so it is only a chance - not definitive. I have stock ICS infected with the bug, but haven't nor plan on flashing or anything like that so...

friedje said:
Go to the church and donate 10 euros...
You might not be so lucky next time around.
Because you didn't brick doing 1 wipe, doesn't mean that you cannot brick..
It's like getting struck by lightning, maybe you will survive the first, but it
might not save you a second time...
Click to expand...
Click to collapse
Back on first HTC android phone )G1) i got it bricked 3 times by flashing SPL 3 times. Anywayz Android is much better (for me) then IOS from crapple. Only HTC dreams where crap in quality since the board has been replaced 5 times due hardware failures...
Now back on business:
I know im lucky. But still .. what causes the randomness of bricking. I mean it is there or it is not? Maybe god exists. I love my note too much to brick it

jeroen180 said:
Back on first HTC android phone )G1) i got it bricked 3 times by flashing SPL 3 times. Anywayz Android is much better (for me) then IOS from crapple. Only HTC dreams where crap in quality since the board has been replaced 5 times due hardware failures...
Now back on business:
I know im lucky. But still .. what causes the randomness of bricking. I mean it is there or it is not? Maybe god exists. I love my note too much to brick it
Click to expand...
Click to collapse
It isn't random. There are just multiple conditions that need to come together to trigger it. Read the thread about it to understand better the hows and why's.

friedje said:
It isn't random. There are just multiple conditions that need to come together to trigger it. Read the thread about it to understand better the hows and why's.
Click to expand...
Click to collapse
Even if all the conditions are met there's still a good chance it won't happen. IIRC there are also versions of emmc chips that don't have the brickbug.

pboesboes said:
Even if all the conditions are met there's still a good chance it won't happen. IIRC there are also versions of emmc chips that don't have the brickbug.
Click to expand...
Click to collapse
Well the fact of having a dangerous chip is one of the conditions....
So if you don't have it then not ALL the conditions are met..
Believe me if all the conditions are met, it will brick, it"s not random.
Then, Jeroen stated that he tested with Chainfires app, and he does have the faulty chip.
Finally I haven't seen a Note in the wild yet that doesn't have a faulty chip.

I feel like the OP. Before I knew of the bug I flashed and wiped many times. But I only flash stock roms. I don't know if that helped or not.
Sent from my GT-N7000 using xda premium

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