yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] abhijit038:
Yes, I did installed my 100+ usual apps in each case after a wipe. However, I didn't use titanium restore as it requires root.What I meant to say is that stock non-rooted ICS kernels released by samsung are apparently safe. I think we should all wait for some time until we get further insight into this problem.Perhaps then we can safely root our phones, and use CWM and all.

Talking about the so-called safe kernels, two people on franco r5 bricked their phones

http://xdaforums.com/showthread.php?p=27095985#post27095985

http://xdaforums.com/showthread.php?t=1696037

I guess the cause of bricking issue is not readily apparent as it appears to be(we have been blaiming stock ICS kernels till now).
[Galaxy Note GT-N7000 General] wonsanim:
Great News!I hope this come soon my device is running LQ2 but I don't like the risk:cool:
[Galaxy Note GT-N7000 General] dbreloaded:
What about if a stock unrooted ICS user boots into recovery and factory resets? Surely that could issue the bugged command and trigger the emmc corruption? I don't think its root that is the problem i think the problem is wiping data...

IF the devs have said that all ics kernels (ALL would include those unrooted and released by Samsung) are unsafe then I think we should take note (lol) of the expert warnings and not wipe our phones if ICS is installed and if u really must wipe follow the posts and revert back to gingerbread or alternative...
[Galaxy Note GT-N7000 General] PoisonWolf:
You're either lucky or a chunk of your internal NAND blocks are close to dead from the improper wear handling.

You're one person, a nobody on the internet, a metaphorical speck of dust. Yet you're trying to refute the claim against voices directly from Google that has spoken about the brickbug.

This problem has been verified on Google's side, what more do you need? For someone to brick your phone for you?
[Galaxy Note GT-N7000 General] letters_to_cleo:
Hey let the guy speak for himself.

If he says that he hasn't brick his Note yet, then so be it. The last time I've checked here in XDA, we're still entitled to our opinions right? and nobody should try to impose or dictate one's judgment to another.

Categorically, I guess he maybe right in saying that the process or likely case your going to get that bug is for you to root your phone and upgrade to a Samsung Stock ICS (or custom ICS) and wiping your phone after. (It doesn't matter if you wipe it once or twice, the hardbrick bug can occur when you least expected it).

The process of just sticking to a non rooted Stock GB Note (even if you change GB ROMS and just sticking to GB all the time) would not get you in trouble of encountering the dreaded bug.
[Galaxy Note GT-N7000 General] abhijit038:
I guess you haven't referred to the link in my previous post.To support verity of my claim, I'd post it for you again http://xdaforums.com/showthread.php?t=1679829

May I add that hypothetical facts can never disrate credence in reality.

It might be possible that real-world tests are quite different from proposition.

Could you cite one case where a stock non-rooted user bricked his phone ? I think you couldn't.

Even if a user were to encounter a bug on non rooted stock, he'd have the warranty to get it repaired.

Why should he be paranoid about it, eh ?

Talking about your claim, it seems irrelevant in context.That one was for Galaxy nexus,isn't ? By the way,have you ever considered that architecture of two devices aren't same. There are many parameters which vary from device to device.
[Galaxy Note GT-N7000 General] PoisonWolf:
Thanks for acknowledging. Enough said.

I'll talk to you again in a few months once subsequent Samsung Official ICS ROMs disable MMC_ERASE or the chain that makes the bug possible.

Till then, keep believing that the bug doesn't exist.
[Galaxy Note GT-N7000 General] abhijit038:
Don't get me wrong. I didn't intend to say that Samsung kernels are without flaws. Perhaps after injection of root the bug becomes apparent Even I'd love to see bug free kernel.Even Samsung people are ready for help . Here is the link to the thread http://xdaforums.com/showthread.php?t=1679829
[Galaxy Note GT-N7000 General] musashiro:
Come on.. the bug exists. after all the technical stuff investigated and even google engineer is involved, you are still claiming that your little experiment proves otherwise. Do you want this thread to be cleaned by a mod as well?
[Galaxy Note GT-N7000 General] abhijit038:
Yes, bug might be present,but I guess it's only after rooting that it becomes apparent and causes bricking. Nonetheless, it's only after trials and experimentation that we may conclude a credible hypothesis. So we should test under all scenarios.
[Galaxy Note GT-N7000 General] WaveMaster1406:
Good new! Thanx man!

For the moment, in any case i'll not take the risk to flash something in my new Galaxy SII...
[Galaxy Note GT-N7000 General] letters_to_cleo:
the bug is inherent already the moment you check and find out you have those

'MAG4FA, VYL00M, or KYL00M fwrev 0x12 || 0x19 < 0x25' (you can download the 'Gotbrickbug' app that ChainFire posted on another thread on this forum.

ROOTING DOES NOT IN NO WAY TRIGGER AND CAUSES THE BRICK. It is when your in Stock ICS with an ICS kernel and doing a full dalvik/wipe of your phone that your tantamount to encounter the hardbrick bug.

A credible test I can suggest on your part I say would be to flash your phone to stock Samsung ICS firmware, and with NO ROOT, see if you can fully wipe your phone over and over, let's say 15 times.

Let's check the outcome (after you've wiped your phone 15x) shall we?

Cheers,

:p
[Galaxy Note GT-N7000 General] abhijit038:
I wouldn't be blathering about it, had I not done it by myself.

Please refer to my previous posts.I have already wiped my phone for 20 times on ZSLPF, having 100+ apps installed in each case.

I am on 0x19 too.
[Galaxy Note GT-N7000 General] letters_to_cleo:
so your main point of contention on this, is that you'll encounter the brick bug just by simply ROOTING your phone? Is that it?

have you lately tried changing ICS ROMS (still UNROOTED) and doing the full wipe again 20x? (if your main point as you say that just by ROOTING the phone causes the brickbug) then how about you give this a shot as well?

:cool:
[Galaxy Note GT-N7000 General] Entropy512:
For various reasons, pushed back to July 21... Still on, but delayed a bit. The holiday this week kind of messed up coordination a little. This was as much my fault as theirs.

In the case of the Note - that unit first shipped in Feb 2012. As far as I can tell, Samsung has kept any unit that ships with the same firmware rev. For something like this, having multiple fwrevs that can't be changed easily could be a configuration management nightmare.

It isn't TOO bad that many devices have this defective chip - as long as measures are taken to prevent that chip from seeing commands that thrash it. The fact that XXLQ5 for I9100 seems to allow erase commands to hit the chip (rendering a previously nearly-immune device at risk) and this report that sounds like stock recovery on a Tab 7.7 triggering the damage worries me greatly - At this point, Samsung is fully aware of the bug and which devices they need to be careful with. In addition, it's well established that there are methods to unambiguously prevent damage from occurring - but not only is Samsung not implementing these methods in new releases, but *removing protection measures from I9100 builds*.

Leak or not - the trigger conditions for the bug should never have even been allowed to enter the I9100 codebase from which XXLQ5 was built.

Yup, but HC recovery does not seem to include erase commands and many of these devices also seem to have measures in the kernel that prevent erase commands from hitting the chip. However, the situation with the 7.7 worries me - Tab 10.1 units could suffer damage depending on what Samsung does with their official ICS releases.
[Galaxy Note GT-N7000 General] MohElShafei:
Is there any news from SAMSUNG side regarding to a fix that we may see soon?

Thanks
[Galaxy Note GT-N7000 General] Reynaldinho111:
Entropy has already said he's possibly having a face to face meeting with a contact at Samsung next week. Relax...
[Galaxy Note GT-N7000 General] MohElShafei:
Thank you a lot for the update .. wish him best of luck :)
[Galaxy Note GT-N7000 General] tonyking:
there is nothing to apologies

even i like to be with xda forum i can't put my hand away from updates

samsung does not care about xda or any third party soft or website

because they will never accept that the device made by them has faulty emmc chipset and rooting device is away from their policies

i have sold my s2 in order to buy note but this prob does not let me to buy it for me updating the device is part of my hobby and now i should keep this fact in my mind that i can brick my device i will wait till this prob sort out and this can only be possible on xda by expert dev can't sure about samsung they just only know how to make handset, software,kernel but thay dont care about their customer wat they want and how to sort out their prob :mad::mad:
[Galaxy Note GT-N7000 General] shoey63:
Thanks for that explanation, most informative:good: I am a superbrick sufferer also (usual culprit - N7000 FW 0x19), but I didn't walk blindly into it. Did all the necessary reading up and came to the conclusion that if you flash FROM, or do wipes ON - only SAFE kernels (stock or CF-root GB, AbyssNote 1.4.2, recent CM9 or any Custom ICS kernel where MMC_CAP_ERASE is disabled) then you will stay out of trouble. And so I

did, for about 5 weeks. Flashed just about everything out there and did countless full wipes - all on safe kernels. Ran into the the odd soft brick issue, but nothing resetting or good ole PC Odin couldn't fix.

Then in one unthinking moment, I forgot what kernel I was on and did a factory reset on CWM.zip while rooting stock ICS (you know - the temp. one). The phone froze almost immediately :eek:I knew straight away what had happened - Instant SuperBrick.:mad: I got it going again using hg42's modified pit file so I could "Triangle away" flash counter. From there I re-flashed original PIT, Let PC odin freeze on factory.fs (ICS LQ2) and made a warranty claim blaming failed Samsung Kies update.(Grey retailer Kogan looking at it now) :fingers-crossed:

It just goes to show - even one wipe/flash on the wrong kernel can result in a SuperBrick:( Many thanks to Entropy and all the crew at XDA for their information and tools. (no excuses, just took my eye off the ball for one second - I've made my bed, now I have to lie in it):o
[Galaxy Note GT-N7000 General] shatroghistro:
Re

What are you talking about? Of course you can flash and wipe and do whatever the hell you want! Did you see the development forum? You think everybody is insane for doing it? You just have to be careful on what kernel you are and that's it. The reason you gave against buying the gNote is totally unfounded. What is more important to look on the gNote is whether the screen suffers too much of a black crush/clipping/pixelization.
[Galaxy Note GT-N7000 General] tonyking:
there is one word read before post did you read what i have written, i m not blaming to any one what my opinion is that due to superbrick/brickbug should i have to buy it or not and the reason you are giving is about its look

this is sure i will check all this thing but i'm talking about bug not about look

as my conversation with SST yesterday i had mentioned all prob and they said that if follow their way to upgrade i will not face prob but i dont beleive because many user had bricked their device after upgrading it

so the conversation is all about

and yes i know if i do upgrading carefully i will not loose my device

moreover thanks for your feedback

xda is about sharing and knowledge

not to get frustrated with post bro ;)
[Galaxy Note GT-N7000 General] androidindian:
Guys, samsung is updating Galaxy s2, i9220 and n7000 to 4.0.4 , some via leaks and some through official firmwares. Lets wait for the sources to be out, and lets wait for Entropy after his confirmation on the brick bug. we all know about it, lets wait for a solution, I am sure it will come by soon..till then take precautions.

will keep you posted. thanks!
[Galaxy Note GT-N7000 General] tonyking:
thanks bhai :D

tab tak gb thik h use karne k liye :laugh:

m i right? :cool:
[Galaxy Note GT-N7000 General] reinbeau:
Stick to English, please ;)

Sent from a state of Serendipity
[Galaxy Note GT-N7000 General] deviantish:
Bhai tab taak you could use ICS with one of the safer kernels, I am currently using parandroid without any problems (though it lacks the support for s-pen) :)
[Galaxy Note GT-N7000 General] tonyking:
hahahahahahahah.....lolz

sure mod

about note samsung will take time to release 4.0.4

and s2 it got leak updates
[Galaxy Note GT-N7000 General] becosemsaida:
Seem that it releases the beast a.k.a brick bug on SGSII !!! Doesn't samsung learn from it's mistakes or is it deliberatly releasing roms with it ???

Source: http://xdaforums.com/showthread.php?t=1751529&page=45
[Galaxy Note GT-N7000 General] MR.change:
I agree 100% with this ,but something doesn't make sense to me, could you be kind enough to explain it?

when you lose root (or partial root as we call it) why will CWM loose the ability to flash ROMs or even mount system partition?

this happened to me when I flashed CM9 from GB CF-rooted kernel once ,had to use ODIN to gain root again.

if recovery doesn't care about root ,then this shouldn't happen right?

or is CWM a different story and is dependent on root?
[Galaxy Note GT-N7000 General] Entropy512:
Define "fix" - As to repair - read this thread, I've been pretty clear with my status updates. I'm probably going to receive information for a fix in a face-to-face meeting with some Samsung engineers in two weeks.

However right now, the fix is not going to be too robust or reliable. In many cases the process will fix the eMMC damage, but leave you with a blank eMMC (e.g. traditional hardbrick due to no bootloaders) - at least it'll be JTAGable. AdamOutler and I are trying to convince our contacts this is a REALLY bad idea.

If you mean "release safe kernels" - I kind of yelled at my contacts in my last email to them. See below.

So far - It looks like new updates are NOT going to contain safer kernels. In fact, XXLQ5 for I9100 was the first time that device has received a dangerous kernel from Samsung. I sent my contacts a pretty harsh email when I saw that... I can understand the GNex team being firewalled from communicating with the rest of Samsung (to avoid a perception of favoritism towards Samsung by Google). I can understand it taking a while for "fixed" kernels that don't cause damage to be deployed. It is, however, totally inexcusable for dangerous kernels, even leaks, to start showing up for devices which have been previously safe. They can claim it was a leak and doesn't matter all they want, but the fact is - the trigger conditions for this bug should never have made it through any proper code review process given what is known about it now. It should never have even made it anywhere near the main production source tree.

That has NOTHING to do with "losing partial root" - whoever came up with that term didn't have a single clue what was going on, and that plague of nonsensical bull**** has spread since then.

It is simply mild filesystem corruption of the recoverable sort. If /system is partially corrupt for whatever reason, it gets mounted readonly and also seems to fail to unmount. Solution:

1) Modify recovery.rc to not mount /system on boot - CM9 did this weeks ago. As a result, it should be possible to format /system without issue when this happens.

2) Use dd to overwrite the first 1-2KB of mmcblk0p9 with zeros, reboot. System will no longer be mounted so you can format it.
[Galaxy Note GT-N7000 General] MR.change:
hmmm....but I thought you said ODIN will also fail to flash system when this happens ,maybe I'm mistaken .

anyway thanks for clarifying ,we can always count on you for busting myths :good:

as for the dd command ,could you be kind enough and write it down in full ,I have a blurred memory of it ,and well... you know how picky these linux commands tend to be ,so....please?

thanks:)
[Galaxy Note GT-N7000 General] MohElShafei:
Thank you sooooooooooooooooooo much Entropy512 for your explanation. I have a bricked SGN device that works with almost only 2GB from the 16GB. I managed to make the phone works but it is unstable and works only with CM9. I'm waiting (hopping) that you will get a solution for the devices that are already bricked and I'm confident that you will do :)

Best of luck and wish you all the success in your life for the efforts you did to every victim of Samsung bug disastrous (or Crime in my opinion).
[Galaxy Note GT-N7000 General] Entropy512:
As to Odin failing - that one is weird. I'm wondering if Odin does some sort of pre-check on the target partition before writing. This is, IMO, a bad idea since Odin is supposed to just overwrite the partition in its entirety. We'll probably never know.

dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1

Zeros the first 1M of /system

Note that the CWM implementation in CM9 kernels shouldn't need this - it'll just format /system because it doesn't pre-automount. I can't remember, I may have done a DAFUQ release with this fix.
[Galaxy Note GT-N7000 General] musashiro:
still looking for the email located "below".. :confused:
[Galaxy Note GT-N7000 General] Randomwalker:
I guess the 'see below' refers to the statement below that further unsafe kernels have been released.
[Galaxy Note GT-N7000 General] jgaviota:
Benjamin Dobell should know how or why this happens, he has researched Odin extensively while developing Heimdall.
[Galaxy Note GT-N7000 General] Entropy512:
That's correct. I'm not including the email itself for a variety of reasons... But I can assure you, I was NOT happy when I heard about XXLQ5. We were all told that Samsung was working on a fix. I've been told by my contacts that Samsung cares about quality. Adding the trigger conditions for eMMC damage to the XXLQ5 release directly conflicts with both of these claims. If the "status quo" had been merely maintained, I would have allowed the "deploying a fix takes time for testing" claim to stand. However, XXLQ5 represents a clear change (as opposed to maintaining the current state of each device as it is) and, more importantly, it is a step in the exact wrong direction.

I'll ask him about it later this week.
[Galaxy Note GT-N7000 General] nfribeiro:
Today Samsung released LPM (4.0.4) for GSII. So far nobody reported a superbrick.
[Galaxy Note GT-N7000 General] Entropy512:
You can assume that the number of brick reports will go down as time goes on, simply due to people being more careful.

For example, here in the N7000 forums, brick reports are now fairly rare - everyone knows that you just don't wipe if you're running an official Samsung kernel, and plenty of safe custom kernels have been released. On top of that, we've altered our recoveries and update-binaries such that problems are far less likely even when working with a dangerous Samsung kernel.
[Galaxy Note GT-N7000 General] nfribeiro:
Yes, you are right and I know it also. But there is always one guy that...:eek:

How can we be sure?
[Galaxy Note GT-N7000 General] nfribeiro:
@ Entropy512, both of us were right.

New LPM (4.0.4) for GSII.- 2 bricks reported from a russian forum:

http://xdaforums.com/showpost.php?p=28515511&postcount=7391

http://xdaforums.com/showthread.php?t=1602579&page=34

I don't understand what Samsung is up to...
[Galaxy Note GT-N7000 General] faisal:
Understandably brick reports on this forum may go down as the issue is repeatedly highlighted and endorsed by opinion makers here.

To me the mystery is what is happening (or not) with the vast majority:-

1. They say that 7 million N7000s have been sold

2. Can we assume that perhaps 10% have ICS running?

3. So of the 700,000 devices running ICS, perhaps 5% people would have hard reset for some reason or the other (these are all assumptions, but just trying to get a sense of the issue)

4. That is 35,000 hard resets. I am not sure what the "more than zero" risk is, but even at 1%, that is 350 bricks.

So is it that Samsung is just playing the numbers and thinking it can handle the 350 mother board replacements without making much fuss and ripples?

That could be a corporate decision - but it still does not explain the continued roll out of ICS versions.. More and more upgrades to official ICS will happen over time.. and more and more people will be hard resetting.. so this number of 350, however manageable for them at the present time, will become unmanageable later on.

Or is it that there is a mega disconnect between decision makers and the technical people?
[Galaxy Note GT-N7000 General] nfribeiro:
Same users of SGSII reported that the bug can only occur when using a custom recovery, if they use stock recovery the brick will never occur. I thought the bug was the stock kernel...

At this point I am totaly confused...
[Galaxy Note GT-N7000 General] michaelgaribaldi:
Emmc found on Skyrocket too

My Note should be arriving today. I currently have a Skyrocket, running Mod1441' s rom. Just on a lark, I downloaded the EMMC checker on the playstore and ran it on my phone and it reported the same possibly of hard brick as the note has. This issue might be a bit more widespread.
[Galaxy Note GT-N7000 General] Entropy512:
I don't know what the hell is going on - but I suspect there's a combination of major communications disconnects AND them playing a Ford-style "acceptable losses" game (http://en.wikipedia.org/wiki/Ford_Pinto#Fuel_tank_controversy for reference).

Wrong. The brick is far less likely, but there have been 3 reports across 3 different devices since midweek last week of bricks from stock recovery. Similarly, when XXLPY first dropped, 3-4 users including Robotu suffered eMMC damage from stock recovery.

Damage from stock recovery is far less likely than from CWM (secure erase vs. standard erase - secure is much more likely to cause damage), but it is not entirely safe. The only way to be guaranteed safety is to use a kernel that blocks all erase commands to the chip.

Already known. The CM9 maintainer for the Skyrocket discovered this the hard way. Fortunately, the fact that the SR has separate recovery and kernel partitions means you can run a safe kernel for recovery while booting ICS with a dangerous kernel. SR superbricks are fairly rare, same for T989. Also, the T989 sources seem to have MMC_CAP_ERASE removed from the relevant driver (msm_sdcc.c I believe)
[Galaxy Note GT-N7000 General] giri@xda:
I have disabled OTA updates by un-checking the option to from Software updates just to be on safer side - least that I can do to keep my note safe till Samsung proposes a proper fix during Entropy's F2F meeting.

Thanks to all for the efforts in getting Samsung over to discussion table. :good:
[Galaxy Note GT-N7000 General] MohElShafei:
Wish you all the luck Entropy512 in your meeting .. :)
[Galaxy Note GT-N7000 General] SpyderTracks:
Good luck entropy.
[Galaxy Note GT-N7000 General] Johev:
I would like to add that probably of the 7.000.000 people that bought the Galaxy Note, we need to count the people that have no warranty because they have either lost the papers or bought it second hand from eBay or other place like that. Not to mention that even if they do nothing in 1,5 years most of the people who bought this device will not be covered anyway by the official Samsung warranty, and by doing a perfectly normal thing they might end up breaking their device and have Samsung just say reply, you are out of luck.

This is what really pisses me off. If I was selling my Note, the first thing I would think of would be to wipe everything on it, so that my personal information could not be used by someone else. Samsung just guarantees that if I do it on their official stock kernel I might as well throw the phone away and get something new. It makes me angry, and the only luck they have is that there is no another device in this category yet, so if we want this we just have to buy the Samsung device.

Just my 2 euro cents :)