yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] letters_to_cleo:
It's easier to stay out, than get out of it...;)
[Galaxy Note GT-N7000 General] friedje:
We have a saying in the Netherlands : "you heard the clock chime, but you don't know where the clapper hangs"...
[Galaxy Note GT-N7000 General] paiseleht:
You nailed it. It is your flat world and my beliefs certainly will not matter to you.
[Galaxy Note GT-N7000 General] friedje:
As I said before, you THINK you understood, but you are a bit off track.

However you are close enough to the truth.
[Galaxy Note GT-N7000 General] abhijit038:
This link has already been viewed by many of us.No official acknowledgement of the bug has been done yet.

By the way, may I ask you that were you rooted prior to performing the update?
[Galaxy Note GT-N7000 General] b16h22:
gsmarena.com/samsung_responds_to_galaxy_s_ii___note_emmc_bug_problem-news-4394.php

sent while doin' some burnouts
[Galaxy Note GT-N7000 General] reinbeau:
Thread closed

There is a better thread discussing this issue, this one is descending into bitterness.
[Galaxy Note GT-N7000 General] nCoder:
I think the response from Samsung is very reasonable. Having someone from Samsung publicly willing to verify and escalate our claims, is a opportunity that we should embrace.

I had a similar response from Samsung Ireland, that in keeping contact and already escalated and is waiting for further information.

From my experience (previously with a GS1, and before a Omnia2), I can tell you that at least Samsung listen to what we say, and even if they don't admit publicly that there is a problem, they do their best to fix it.

Just lets not spoil this opportunity ;)
[Galaxy Note GT-N7000 General] Alexanderbooth:
I agree samsung have the right attitude, you can't expect them to put time and effort into fixing a problem they did not create. No one has a clue what is causing the issue, until it keeps happening to lots of phones on stock roms, you can safely say samsung wont accept its there fault. Is there anyone at all that has bricked there phone having never rooted or installed anything other than stock firmware? I think when you find that person you have the smoking gun until that happens, you cab pretty much say for sure it isn't samsungs fault this is happening.
[Galaxy Note GT-N7000 General] M3TALLICA:
Welcome Samsung reps.

Have you read Mr Sumrall's post?

There is one case with stock recovery, root is not responsible for Superbrick.

Samsung, you better send some devs. Not MBA graduates or Lawyers.
[Galaxy Note GT-N7000 General] Braxos:
Root = modified........... So they care alot, NOT. It is a risk you take when you have modified any of the normal scripts. If the device is working as intended then qq somewhere else theydont want to hear it.
[Galaxy Note GT-N7000 General] M3TALLICA:
BS. I installed car decals kit does not mean it's the reason if gas tank explodes.
[Galaxy Note GT-N7000 General] Alexanderbooth:
What he means is when you root your phone, you can modify anything, modifying things can cause bricks. Samsung has no idea what has been changed on a rooted phone. So that is why they wont accept anything other than stock unrooted brick.
[Galaxy Note GT-N7000 General] Zamboney:
If i recall correctly Entropy verified from the official Samsung ICS sources that the ROM was issuing the buggy erase command. Isn't that proof enough together with the fact that 0x19 firmware can destroy the flash using that command?
[Galaxy Note GT-N7000 General] .h3:
Hi guys, first post here on xda forums but I follow you from february when i bought this awesome phone.

Actually I guess Samsung already know about this bug, and what makes me think is the fact their ics rollout is very slow, especially in europe when at this time a suspicious bug-affected version of ics is available only in germany. So yeah I guess this kind of faky response from mail is a sort of facade vs users which has already found a bug that virtually it wasn't supposed to be found, since they obtain ics not when samsung wants them to obtain it. All in order to mantain the brand reputation high, as someone already said.

I think they are working on a fix, or at least I hope so... what worries me a lot is this lag on a product that was already in late.

Forgive my english.
[Galaxy Note GT-N7000 General] Alexanderbooth:
Yeah but didn't he also say that gb roms also have the same active command, so others factors are at play?
[Galaxy Note GT-N7000 General] M3TALLICA:
Please see my post on page 2.

The guy who bricked his phone had stock kernel and stock recovery.

Root happens out side of the kernel. You root a stock kernel does not mean you recompile the kernel. Whatever Samsung put in it is still there.

The guy bricked his phone by performing data wipe in stock recovery. Now superuser.apk and su binaries has nothing to do with this damage.

Hope you get this.
[Galaxy Note GT-N7000 General] hagba:
A very big part of Android is the Rooting itself,I myself havent seen anyone around me who havent rooted his device in a way or another,beside the open source reputation is one of the biggest selling point for Android,So I doubt that Samsung would not care for a potentioal solution if they could reproduce it even if it envolved the Rooted devices alone,

If someone doesnt come forward with a solid arguement and a proof looks like a closed case to me.
[Galaxy Note GT-N7000 General] Alexanderbooth:
Yeah but you can flash new kernels when rooted, like I said samsung has no idea what you have done to your phone when rooted. This is why rooting voids your warranty. There's no point arguing over it, I agree just rooting can't affect the kernel. But its the things you can do while rooted thats the problem here. Even if someone said they had defo not rooted and stuck to stock roms, I would be highly scepticle because a person that doesnt root and flash probably wouldn't really know if they had superbricked there phone or not because people who stick to stock are usually wouldn't have the knowledge to try and retrieve the state by using odin. I know its a **** situation and samsungs kernels are probably to blame. Im just tryingto explain that samsung wont do anything unless its happened on an unrooted stock phone.
[Galaxy Note GT-N7000 General] friedje:
What you don't want to understand is that from the moment tht you root the phone you can do whatever you want to the kernel or the system......

Samsung doesn't say that it is the cause of your problem, but they have no way of knowing if you p**d inside the kernel or whatever......So they won't take your scouts honour for granted...
[Galaxy Note GT-N7000 General] nCoder:
Focus

Right. :)

But the point here is helping them to reproduce the problem in a Stock ROM. Samsung is not saying the problem doesn't exist, they want to help up report the problem efficiently.

If you know someone that never rooted the phone, and after a standard upgrade, has a hard brick after a factory reset, then, we need to know exactly what he did.

(The forum also has a lot of reports of users that flashed JPY and performed Factory Reset several times without bricking the phone).

I'm a senior developer for the last 18 years (Windows), and if the user simply tells me the computer doesn't start any more after installing my application, I'll ask for more details, so I can debug the application while trying to reproduce the problem.

Also, QA is not able to test every possible scenario, before releasing a phone or a new ROM.

Any real developer understands what I mean.

We are all assuming there is a problem in the stock ROM, and probably is true, but there is a chance that the problem is not in the Stock ROM - We know about cases of bricks while flashing official ROMs in other phones in the past - users simply go to service centres and problem solved.

Again: Lets focus on constructive comments, and help Samsung Developers reproduce and find the problem.

Cheers

PS: Any other reliable source confirming the problem would be valuable as well (I read somewhere that Sprint admitted the problem exists...)
[Galaxy Note GT-N7000 General] Entropy512:
We got more information from Mr. Sumrall, and to brick requires three components:

1) Buggy eMMC firmware, specifically MAG4FA or VYL00M fwrev 0x19 (KYL00M fwrev 0x19 probably also affected). Confirmed on basically every Samsung Exynos device with 16GB storage. The bugginess of fwrev 0x19 was confirmed by Google during Galaxy Nexus development, and Samsung fixed the firmware in released GNex devices. However they continue shipping known defective MAG4FA/VYL00M fwrev 0x19 in Exynos devices.

2) MMC_CAP_ERASE enabled in the kernel - confirmed for everything but I9100 Update4 sources - If it's disabled, mmc_erase() will error out if called.

3) A recovery that causes mmc_erase() to get called in the kernel - This was added by Google to improve privacy (a normal partition format doesn't actually erase your data) in ICS. Robotu semi-confirmed this - later this week I'll work on fully confirming it by instrumenting a kernel to safely trap mmc_erase calls and print when they occur without issuing ERASE commands to the MMC chip. This upstream change by Google is why Gingerbread is apparently safe.
[Galaxy Note GT-N7000 General] M3TALLICA:
It means Samsung knows what the problem is, they still risked it by selling devices with borked eMMC firmware, by providing affected kernels and recoveries.

I don't think we would get anywhere if these people keep talking about ROOT.

PS

Samsung, thanks for the great hardware, luckily we have ROOT, XDA and Cyanogenmod.
[Galaxy Note GT-N7000 General] rjrjzozo:
try on uggies's thread or hg42's one. many hardbricked and revived there.
[Galaxy Note GT-N7000 General] nCoder:
Hi

Who wrote this to Samsung Devs?

anyone here?
[Galaxy Note GT-N7000 General] porcusor:
Quote from Robotu's post:

"[...]Before install LPY i did a factory reset (with wipe every thing), as i read over XDA, i installed over Odin PC, before login i did another factory reset with Wipe every thing, than i loged in, it worked, though a bit slower than GB, i rooted with Ketan methot withoth CWM i played with rom a few hours than i decided to do app restore with Titanium[...]"

So he rooted the device.

I'm asking the same question someone else did in this thread:

Is there anyone that did not root their device at any time and updated only through kies/ota? If so, he/she needs to provide samsung with as much details as possible.

I actually did not see a single person here that bricked their devices without rooting or using 3rd party software (oddin, cwm, etc) to flash official/unofficial roms.

From Samsung's point of view they are safe as can be until proven the contrary.

If however we find out that the official ROMs are safe to use wipe on, and that the root or custom kernels are to be blamed, then we could concentrate on improving our own tools - root method and custom kernels. And by 'we' I'm referring to XDA developers.
[Galaxy Note GT-N7000 General] :
I guess I'm the minority of users that hasn't rooted. Hasn't flashed and is still running entirely stock GB. I can't goto ICS as officially it hasnt released here yet...
[Galaxy Note GT-N7000 General] nandihno:
as a seniour app dev too..

i respect what the Samsung engineers are asking.

it is not that ROOT is the cause for the bricks

but with ROOT you may give access to things that the kernel was not intended to do under normal circumstances.

I have wipe cache and wipe system on stock on ICS LPY and on LPF with no root..and have not had a problem (had flashed 4 times stock ICS (trying LPY then LPF then LP9 then LPF again)

so ppl take this as an opportunity..because it sounds like they are listening...for once and if anyone has bricked their devices with no root...

then simply send them a logcat.
[Galaxy Note GT-N7000 General] porcusor:
lol how to send logcat with their bricked device? also logcat requires root from what I know.

THey should just reach out to samsung on the link the OP posted. If they only go to service centers they will get their mobo replaced and that's it. It's easy to ask someone who just damaged their pricey device to try and do some additional steps to help others as they are busy with crying over their bricked Note. But maybe there are a few out there who are willing to help..
[Galaxy Note GT-N7000 General] nandihno:
you can get logcat printed via connecting your phone via adb to eclipse and android plugin has the ability for you to view logcat

the icon for it even has flying cat in eclipse ! lol :D
[Galaxy Note GT-N7000 General] porcusor:
lol the samsung support guys know about this? I wish.. OK, now we're waiting for someone who actually bricked their device in standard circumstances.. will be a long wait...
[Galaxy Note GT-N7000 General] M3TALLICA:
We don't need to argue or provide any info to these people. They will keep whining about root.

Read entropy's last post, Samsung fixed the bug in gnex fw.

But they still continued sell other devices with same **** emmc fw, kernels and recoveries that triggered the bug.

I hope a lot of people get to know this and samsh!t apologizes publicly.
[Galaxy Note GT-N7000 General] andreww88:
I understand Samsung can't cover users who root because of warranty issues. I understand that totally. And I'm pretty sure ROOT is not the cause of the bricks. I agree with you it may give access to the things in the kernel that do cause the bricks. So my thing is, Samsung should still take ownership and at least fix the bug for those users that DON'T want to remain stock, at least just to keep them around longer and keep them buying Samsung phones.

Just my thoughts.
[Galaxy Note GT-N7000 General] musashiro:
http://xdaforums.com/showpost.php?p=26686480&postcount=2660

bricked on stock LP9 recovery (im not sure if he is on full stock so i PMed him regarding the steps on how he met the devastating bick bug)...

i will report here once he replies to me..

i really can't see why samsung failed to reproduce this effing bug..
[Galaxy Note GT-N7000 General] loloudoudara:
Software engineer here too. I think what would help in the interim would be the bug fix details to the gnex. If we cant consistently reproduce the bug, we could still integrate the gnex fix to the galaxy note kernel.
[Galaxy Note GT-N7000 General] praetorius:
Their concern is stock, untouched mobile and firmware. And since this complain is localized in XDA, most of the devices have had a history of flashing non-official roms or rooted. Samsung will have none of that since the fault could somewhere be in the previous flashing procedure or how the rom was 'cooked'.

Zapped through server hops to XDA forums
[Galaxy Note GT-N7000 General] praetorius:
Car decal = wallpaper

Rooting = turbochargers

Zapped through server hops to XDA forums
[Galaxy Note GT-N7000 General] knightnz:
If it's superbricked then the phone is not accessible via adb, if it is then it's only softbricked.
[Galaxy Note GT-N7000 General] chasmodo:
This complaint is not localized to XDA. XDA is the biggest forum for English-speaking users. There's lots and lots of local Android forums for guys who do not speak the lingo. And this bricking tsunami hit them pretty hard too. I remember a Russian guy posting here that they have had 30-odd ICS bricks reported in a matter of a couple of days in one of the Russian forums.

And those non-official ICS releases were leaked by whom...? By you and me?

So, Samsung leak b0rked stuff, then they sit back and watch the mess, and in the end claim that it's OUR fault for using something they have leaked themselves in the first place? That's business ethics, I suppose?

A lot of users got their bricks on stock rooted Roms. And stock Roms were cooked by Samsung, were they not?
[Galaxy Note GT-N7000 General] kromosto:
if samsung has no option to upgrade or fix 0x19 firmware then it is right thing for them to deny it.
[Galaxy Note GT-N7000 General] praetorius:
Can you point me please to an incident where an untouched Note bricked while on official ICS? Thats what they are trying to isolate. Tainted devices and firmwares are not the responsibility of samsung.

Leaked firmwares are just that.... Not meant for the general population.

Dont get me wrong, im all for the resolution of this fiasco. But samsung devs has a point when they cannot replicate the issue on untouched Notes. So, as far as they are concerned, the bug may exist but does not wreak havoc to unmodified units.

Zapped through server hops to XDA forums
[Galaxy Note GT-N7000 General] biliskner:
Well said. I want a resolution to this also. But all bricks have first had their device rooted (then custom rom, and cwm whatever). As ncoder pointed out, we need a stock gb to stock ics, and without rooting. If I remember right, zergrushing my device was at my own risk, so Samsung of course is not going to zerg rush any of their devices to reproduce the bug. That's not to say the bug is nonexistent, it's just Sammy won't do nothing about it....because they don't play starcraft.

It seems the only 2ways about this is:

1. Petition. We go ape about it and force their hand this way.

2. We go through the Android dev who confirmed this bug.

Or... Find an actual post of someone **Non Rooted** using Kies or whatever Sam uses to upgrade gb to ics.
[Galaxy Note GT-N7000 General] Alexanderbooth:
Original poster!!!!! If no one comes forward can you not just ask them to install the German ics, then tell them to wipe the device in recovery 10 times. If that doesn't cause the brick for them then maybe something that is left behind by people flashing other stuff is causing the issue.
[Galaxy Note GT-N7000 General] musashiro:
whats wrong with you people?? i posted a link where a person on LP9 got bricked.... check it out..
[Galaxy Note GT-N7000 General] nCoder:
I understand that they did that already, also using several devices and several ICS ROMs. :(
[Galaxy Note GT-N7000 General] Alexanderbooth:
Havent they rooted or flashed other roms previously though? Thats the smoking gun we need to tinkering wth the phone at all.

---------- Post added at 10:06 AM ---------- Previous post was at 10:00 AM ----------

Oh ok I see sorry, well ist this starting to get a little fishy then, how can it be samsung if its only happening on phones that have been messed around with? I have no idea about this stuff I just come on here to read cause im interested, I don't flash roms I just root and update via mobile odin, so I have no idea about how it all works really. Isn't there something else that could be causing the issue?
[Galaxy Note GT-N7000 General] Markuzy:
As I have read through the numerous threads about this, the issue is that there is a probability of a fatal brick, perhaps Samsung didn't test on a large enough sample size. In fact like mentioned in previous posts, the brick does happen on stock unrooted.

Sent from my GT-N7000 using Xparent ICS Tapatalk 2
[Galaxy Note GT-N7000 General] biliskner:
Did he root? He just posts 1 line and that's it, it's almost as bad as Samsung's "replies".
[Galaxy Note GT-N7000 General] nCoder:
We know that the emmc firmware has a couple of bugs that could cause the hard-brick. I'm no expert on the matter, bat, Samsung could have known about it and could have some sort of dirty workaround in the stock ROM that would be affected by a lot of causes (i.e. the rooting method used, CWM, the flashing method, re-creating partitions, etc, etc...)
[Galaxy Note GT-N7000 General] M3TALLICA:
Why the blazes you keep talking about root?

None of you (Samsung lawyers?) replied to Entropy's last post?

What about the **** emmc ? Stock kernel and recovery that trigger the bug?

Emmc bug was corrected in SGNexus, why do we have the same borked chip?

To the guy who posted previously,

TurboCharger = Custom Kernel + Custom Recovery

Decals = Stock kernel + root.

If you don't know what rooted stock kernel means, back off :)
[Galaxy Note GT-N7000 General] Alexanderbooth:
Has no one pulled together all the bricked phones info, like what roms they haeinstalled what rooting methods they used, the recovery they used etc to find the common denominator? Maybe its that leaked Chinese one that came out? Wonder if they all installed that at one time or another, thats what mess up there emmc then it was just a ticking time bomb until the brick happened?
[Galaxy Note GT-N7000 General] M3TALLICA:
I don't use Facebook but I might join and start a campaign / circle (whatever they call it).

People who bought and who will be buying this phone need to know this.

Needless to say there are screen issues as well.
[Galaxy Note GT-N7000 General] nCoder:
Latest feedback from Samsung Developers, after someone sent more information on additional test cases:
[Galaxy Note GT-N7000 General] chasmodo:
It's most certainly not the Chinese leak. There were at least 10 users who purchased their Notes 2-3 days before they got them bricked. And the official ICS was very much out when that happened.
[Galaxy Note GT-N7000 General] Alexanderbooth:
The reason I didn't reply to that post is because I have not idea what he's talking about hahaha, but after reading several posts from him, he still only thinks thats what the issue could be doesn't he? The impression I get from reading his posts is that it could be the issue but not definitely, am I right in saying that? There seems to be a lot of people on here spounting a lot of stuff using his posts as proof when even he the expert isn't 100% sure. It must be a nightmare trying to find these kinds of bugs especially with so many scenarios. I find it hilarious how every argues on here like they no all about it from reading posts, when in fact like me they hasn't got a clue about coding firmware, kernels, roms. Hope this issue gets sorted soon, for many of you flashers, I tend to stick to stock and now im on ics im happy so should be fine if I don't wipe.
[Galaxy Note GT-N7000 General] nCoder:
Check this post from that same guy:

http://xdaforums.com/showpost.php?p=26495625&postcount=23
[Galaxy Note GT-N7000 General] Alexanderbooth:
Well at least they are trying to help, I guess they must keep there eyes closely fix on forums like this anyway to see any issues that are arising.

---------- Post added at 10:37 AM ---------- Previous post was at 10:35 AM ----------

Do you have links or info on these 10 people, maybe tey could help?
[Galaxy Note GT-N7000 General] jgaviota:
Have them post the file /cache/recovery/last_log after a full wipe. There should be two lines that indicate a format, one for /data and one for /cache. If after the formats there is a line that says:

warning: wipe_block_device: Discard failed

Then they have indeed fixed the hardbrick bug from factory reset in STOCK ICS

For a thorough analysis of the bug and causes and possible fixes see the last couple of posts from sfhub in this thread:

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

So what Samsung developer should check is if mmc_erase gets called by a factory rest. If it isn't then they fixed STOCK ICS.

We cannot check that because we don't have their recovery sources.
[Galaxy Note GT-N7000 General] biliskner:
Apparently not. If you actually read Samsung's replies then root is the difference between them "not being able to reproduce this bug" vs "all of XDA seeing this bug left right and centre."

That's why.

But here's to hoping they keep flashing and wiping and flashing and hoping they get a brick in their HQ (which again, reading their replies, they apparently have not).

---------- Post added at 09:35 PM ---------- Previous post was at 09:34 PM ----------

Exactly.
[Galaxy Note GT-N7000 General] nCoder:
Requested. Waiting reply now ;)