yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] Princeomi:
Reminds me of Toyota with their acceleration problem. Even they could not reproduce the problem, until faced with a class action suit. Maybe Samsung also needs one. If this is the way Asian companies operate, I dread when mainland Chinese Companies like zte, etc become dominant.

Sent from my GT-N7000
[Galaxy Note GT-N7000 General] M3TALLICA:
"...Samsung fixed the firmware in released GNex devices. However they continue shipping known defective MAG4FA/VYL00M fwrev 0x19 in Exynos devices."

And if Entropy's tests prove that stock recovery too has the bug...

well then I'm studying mercantile laws, law-suite is not impossible.

----

@nCoder,

You would not find a 'virgin' mobile on XDA.

Lets put this technical **** aside,

Can samsung answer this... why there were ZERO super bricks with Gingerbread roms ?

I (and other people too, I'm sure) used to flash GB roms, perform nandroid restore, wipe data/factory reset like a mad zombie but I never bricked my phone.

----

Edit

---

@nCoder

Does it mean samsung is aware of the bug ?

Or you are just trolling ?
[Galaxy Note GT-N7000 General] nCoder:
Hi

Keep in mind that this thread is about a open privileged channel to Samsung Developers support that are willing to test and escalate the problem and make sure is fixed, but they need our help to be able to reproduce it and escalate.

They have been very kind and doing their best to help escalating the problem, but all tests do do on stock devices fail to reproduce the problem.

"Lets put this technical **** aside,

Can samsung answer this... why there were ZERO super bricks with Gingerbread roms ?"

The problem is that if you can't find a single case here of a factory standard device never rooted or flashed in alternative ways that has been bricked in this forum. From their prespective, the modifications to the kernel, root, or whatever changes to the system are the most probable cause.

You cannot have any class action if there isn't anybody that can corroborate (by witnessing a brick on a stock device) the thesis of problematic ROM or buggy emmc fw.

I believe that even if the problem is manifested only in modified roms, Samsung is willing to fix it. But if it's the case, it will not have the same priority as if it was in a stock ROM already deployed to half a million devices already.

"Does it mean samsung is aware of the bug? "

There should be some missunderstanding here. Until Entropy makes his tests, we don't know for sure if the problems (2) found by the Android engineer are 100% indeed the problem. What we know is that if all these 3 conditions mentioned by Entropy exist, they most likely that's indeed the problem. But that wouldn't explain why only modified ROMs are affected.

As explained above, I don't know if they (HQ) are aware of the root-cause, but the Samsung guys I'm talking to, are not aware of these problems, and are willing to help us prove its existence, by making any test we ask them to do and see if it bricks.

BTW: Franco was referring to the Android engineer, not Samsung's (honest mistake) ;) He also mentions "it's a workaround that

migh

t prevent it from happening.

It's not confirmed

" i.e. we are not sure that is the problem. ;)

Are you able to provide any useful information to the case?
[Galaxy Note GT-N7000 General] Princeomi:
If they fixed the same problem with Nexus with a firmware update, why act dumb now? May be the people with whom you are talking are unaware of the problem but Samsung knows this!

Sent from my GT-N7000
[Galaxy Note GT-N7000 General] jonpaslim:
Is Ics safe if it remain unrooted, because of samsung developers reply regarding their testing that came out negative of superbrick bug.:rolleyes:
[Galaxy Note GT-N7000 General] vijai2011:
That means do you say I dont want to flash stock ICS and brick my phone???
[Galaxy Note GT-N7000 General] nandihno:
if you do this..and find that you are indeed able to verify ...can u not create a patch and send them the patch for them to verify?

dont know the details..but will you be doing a simulation of a wipe? as in mocking the calls in the kernel

it will be great if you can get it to run on a x number of iterations ;)
[Galaxy Note GT-N7000 General] opsakas:
In any business I have been, you really can not say anything before you KNOW for sure.

BTW, I am still wondering why there is no word in forums about bricked stock Notes... Because the problem really isn't that widespread? Because the stock installation behaves in certain way as far as it is not rooted?

No, I do not love Samsung. But to be fair, such scaremongering isn't going to do any good at all.
[Galaxy Note GT-N7000 General] Markuzy:
It could also be the fact that those with stock are less likely to factory reset or wipe than others

Sent from my GT-N7000 using Xparent ICS Tapatalk 2
[Galaxy Note GT-N7000 General] rraaka:
hey guys ,

reading this im so reminded of my experience on Daily Mobile forums ( wonderful community of Nokia 5800 ). The Hellox hack app was working wonders on s60v3 and s60v5 devices but all the time Nokia was cooking up a real bug and introduced it in the next firmware upgrade (one which had all the youngsters drooling over the kinetic scrolling in the menus for the very first time !!) and bang ...the magic was gone !!

Of course, the effervescent youngsters and experts found out a workaround, through flashing prehacked firmware files but it was complicated...just not the same anymore ( it wasnt a lethal attack either as there were no bricks )

Is this BS....maybe. Am I off topic ...fcourse NO !!!!
[Galaxy Note GT-N7000 General] nCoder:
Definitelly.

How many newbies know there is a Recovery menu? :)
[Galaxy Note GT-N7000 General] Braxos:
Difference from recovery and *2767*3855#?
[Galaxy Note GT-N7000 General] vijai2011:
Absolutely.

If you need any help,I'm ready to help.Fell free to contact me.Anything which causes a brick too...I'm ready to help for xda.
[Galaxy Note GT-N7000 General] Latoc:
How many noobs know about *2767*3855# ?

Even I don't know about it...

It's true normal people only wipe if they have big problems with their phones, and even then many people don't even know they can reboot their phone every once in a while to recover performance and stability...
[Galaxy Note GT-N7000 General] Entropy512:
Exactly. Most people here probably went and installed CWM immediately.

Most people who run full-blown stock don't even do a wipe. Stock factory reset/wipe is likely a fairly rarely used function.

We've seen multiple reports of stock recovery killing devices, but they're rare due to the fact that not many people wipe with stock recovery. So the thing that remains is to prove that stock recovery provides the third of the three prerequisites for danger. I've seen enough stock recovery brick reports that I will be absolutely shocked if my test fails.
[Galaxy Note GT-N7000 General] straycat:
AMEN!!!
[Galaxy Note GT-N7000 General] nCoder:
Hi Entropy,

+1

BTW: Could you please post a link to one of those reports?

Thanks in advance
[Galaxy Note GT-N7000 General] jgaviota:
I'm waiting for your results also, it's the only sure way to see if Samsung's recovery is truly safe. But I haven't seen credible reports of people bricking on stock, as you said most people installed CWM immediately. So with that coupled with the reports of Samsung's techs not able to reproduce the bricks, I think they might have reverted to using GB recovery or something like it for the official releases.

Nevertheless I cannot risk wiping from stock and bricking my Note, it is not truly mine but my office's.

In any case THANK YOU for all the investigation that has gone into this.
[Galaxy Note GT-N7000 General] opsakas:
I would like to see such a post also. A nice clear post that shows the aspects and excludes the user error (eg in PC Odin: repartition tick when not needed, wrong files, etc), excludes root.

I mean, come on, this topic has been active for several weeks and all I have seen is a report about Robotu and even he states that " i do have CWM" after brick... And of course, I have seen several times someone telling without any proof that they "have seen SOOO many bricked stocks or stocked bricks"...

And no proof whatsoever.

Of course, you are making sense in speaking about eMMC. But at the same time also Arobase40 is making sense when he says, that if that would have been the case, there would be bricks all over the world. After all, 7 000 000 Notes have been sold since November and the general users of Notes are a bit more high-end users than eg Nokia 2730 users. It is not that users that do not want root would not want ICS and would not wipe/stock restore. Yes they would. And because they are generally younger ones and well connected (well that is the reason they bought the Note in the first place!) the information would rage all over. But what I see... None. Zero. Nothing. Only the bricks with modified software.

Are you 100 % sure that your modifications allow stock kernel to work EXACTLY like it was meant to work? Can you tell to all of those fancy nimcompoops that bricked the phones using all these custom-tailored ROMs that your soft has NOTHING to do with that?
[Galaxy Note GT-N7000 General] Entropy512:
I already linked to robotu's report in the thread on Samsung's forums.
[Galaxy Note GT-N7000 General] nCoder:
Thanks Entropy

Checking his previous posts, in particular the original report:

http://xdaforums.com/showpost.php?p=26040825&postcount=134

His phone and flashing methods were not really "clean" to be used as a case to prove nothing.

Is there any other case? I'm confident that there should be more

I've been flashing custom ROMs for the last 7 years, and this is the first time I feel really worried about custom ROMs.

Today, for the first time I flashed Stock ICS in the Note using Mobile Odin, CWM and and the CF-root - and something as simple as that and My Wifi was not working anymore!!! Something tells me that there is a lot of things that we don't know about these new stock ROMs - Probably Samsung bugs, or old methods are not so safe any more.

Anyway, please correct me - I'm loosing my faith on this case :(
[Galaxy Note GT-N7000 General] becosemsaida:
Well things are being blow-up with this thread. Many people refer to this exact thread to make excuses for.........anything.

I remember that iphone was releasing updates just so that people couldn't jailbreak the device..... Maybe, although it's open source, samsung did encoded some failsafe?? Allright i didn't do my homework and don't know where odin is from nor who wrote it, maybe something is triggered while flashing with odin??

I for one did already two wipes on my note, stock ics (German lpy), no root and updated with kies (blah). Haven't used odin nor other flash app !!!

What i really find strange, and it was already highlighted here, that samsung sold over 7 million devices if of those 7 million devices only 1 million is installing custom roms we should have a much higher count of bricked devices....

Maybe someone with more experience in flashing mmc cards (eMMC) can figure out why. As it seems the blocks are just ignored and returning a false parameter. How do they write to it and why is it impossible for us to write to them?? Other possibility is that while wiping there is a power surge, too much or too less may also have something to do with it. For all i know and found that the memory is "just" a flash card on the main board. From all the posts i've read everybody says the same: missing sectors = loss of memory.

I know that the card can be defragmented, formated and "rebuilt" but i don't know how, nor do others so far. There are reports from people that had "the bug" and were able to revive their note with a substantial loss os memory (~5Gb). still there must be a way to isolate the memory, defragment it, format it and install the original files.

becosemsaida
[Galaxy Note GT-N7000 General] nCoder:
BRAVO Entropy

You are the best. :)
[Galaxy Note GT-N7000 General] Entropy512:
Samsung has only deployed ICS in a select few countries. Also, users who run full-blown stock don't enter recovery to wipe very often. Even if they did brick on wipe, they'd just go to a service center instead of coming here to report.

As stated by Mr. Sumrall himself, the ERASE bug in fwrev 0x19 is intermittent - it's not guaranteed to happen. That's why some people in the E4GT community were able to wipe 10-20 times before experiencing damage. Other people got unlucky and got toasted the first time around.
[Galaxy Note GT-N7000 General] becosemsaida:
Instead of just hitting the thanks button i wanted to saY: thank you.

I know it's a lot of work doing this and i don't think, in the end, you will be remembered as the saviour of the note ...

Hope that this problem is going to be solved, with your help and all the others.

Now with evidence that the firmware is defective samsung has to implement some kind of solution. Hope they will do it soon but i'm sure i will find it here first.

becosemsaida
[Galaxy Note GT-N7000 General] nCoder:
First of all, thank you so much for your precious investigation.

Now that we know, that Factory Reset in Stock Recovery (Also in settings menu?) can trigger the problematic command in the eMMC, there shouldn't be any reason for Samsung to be able to reproduce the problem.

The question, is, how many times they need to test the scenario, and if it is possible that the ERASE instruction only causes problems if there are any attenuating circumstances? i.e. dead locks, asynchronous writes (timming), voltage peaks, under-voltage due to battery low, buffer overrun...

Anyway - Well done. Could you please post these details in the Samsung Developers Thread?

If we could log a brick, it would be the cherry on top of the cake. :)
[Galaxy Note GT-N7000 General] Entropy512:
Just posted it. It shows as a reply to the original post, not as additional details beyond my previous post.

My guess is they'll have better luck reproducing this if /data is reasonably full, but I'm not sure.
[Galaxy Note GT-N7000 General] sujal:
From whatever little knowledge that I have, I think its the kernel that makes things work on the device. Rooting DOES NOT affect the kernel. I don't know about CWM though, I think it does.

So, if I were Samsung, I would rather do this:

1. Get a brand new note, running GB.

2. Root it. (Warranty gone but kernel still unaffected).

3. Flash official ICS ROM, get root.

4. Several factory resets and wipe from stock recovery.

If I get a brick, its some kind of a problem with Samsung and Samsung should fix it, if not then I don't think Samsung should be blamed. Rooting does not do anything but to give you root privileges. Its what you do with the privileges that matters.

The only counter argument to my own argument I have is if rooting does not do anything, we should be able to get hard bricks on unrooted devices too, right? Its all too confusing. :/
[Galaxy Note GT-N7000 General] becosemsaida:
There must be some reason that you will loose you warranty if you root or even mention it !!!!!!

If you say to them: "root the device" all the credibility will be lost.

As far as i know no ROOTED devices are being repaired under warranty.

becosemsaida
[Galaxy Note GT-N7000 General] lurchbyrep:
Do we really think Samsung devs are going to root one of their own phones as an official test case? The moment you ask them to do this, you stamp "irrelevancy" all over your own forehead.
[Galaxy Note GT-N7000 General] :
I did get rid of the binary counter, the triangle and installed a stock kernel on Note!

Actually on Telmet in Oporto the lady that got my Note said to me that didn't matter if you actually rooted your Note... it wouldn't influence the warranty... but honestly i did get rid of the binary counter and installed a stock kernel... don't wanna risk it!

I lost 5Gb in bad sectors that's why i had to take it to samsung center to replace the motherboard, and i did take it there because the guys from Samsung warned me that the replacement of the mobo would be something like 350€ for me!

But warranty makes it completely free :D

I should get it in time for my birthday in 8 of June :p

PS: She told me that it wouldn't avoid warranty... but you know... she is just a secretary... don't risk it!

And i did play dumb... talk about updating thru Kies... don't even talk about PC Odin or wathever.. play the dumb role!
[Galaxy Note GT-N7000 General] chasmodo:
Interesting post. Summary of what you say would be

1. there is a lot of stuff I know nothing about

2. there is a lot of stuff that makes me wonder

3. points 1 and 2 lead me to conclude that the people posting in this thread exaggerate
[Galaxy Note GT-N7000 General] sujal:
I don't know how to put it but to get to the 'root' of the problem, Samsung should try it. Yes it voids the warranty and everything but are we talking about the warranty here? We just need to know what's causing these bricks, if its a problem with completely stock ROM, Samsung has got to fix it, if not then I will gladly pay them to repair my phone, even if just rooting caused it because I myself agreed to voiding my warranty..
[Galaxy Note GT-N7000 General] opsakas:
So you ppl admit that the brick is connected to rooting?
[Galaxy Note GT-N7000 General] becosemsaida:
I don't want to question your knowledge or anything else ok??? I have and will always RESPECT all the work there has been done by people who know and do more for this forum than me !!!

As for your comments:

1- In almost all forums if they talk about bricked gnote they refer to this particular thread,

2- How many threads are here about bricked / revive / solutions etc. etc.? More then in others.

3- I try to learn and know more about this, not because i hava a note but i find it interesting, my choise.

4- Known it's a MMC problem and reading that the internal memory is like a flash-card and since i had a lot of problemas with these and "lost" a lot of time with learning how they work i really want to know more about the solution, processes and handling on a smartphone.

This thread has only a few contributors in finding a solution, others (me included !!!) are just tagging along. But if it makes you happy i will just sit here quitly and try not to interfere.......... I've done this for a while (yes, i read but don't interfere since 2008 BUT learned alot) and can continue.

Once again i wasn't questioning your knowledge so don't be offended, many devices refer to this particular thread that was all i stated.

becosemsaida
[Galaxy Note GT-N7000 General] chasmodo:
nCoder, here is your case: http://xdaforums.com/showpost.php?p=26000792&postcount=1
[Galaxy Note GT-N7000 General] M3TALLICA:
Thanks a lot Entropy and other devs who warned about superbrick and were persistant that the bug existed. Thanks a lot for finding a workaround :)

And now afters Entropy's tests it proves that stock ICS is dangerous.

----

PS

To Samsh!t trolls and fanboys, no more hate posts from me.

Keep whining about root.

Meanwhile I'll see how this evolves and decide (about Note and my future phones)
[Galaxy Note GT-N7000 General] nCoder:
Thanks chasmodo but this is another example of a "messed up" device - the device was, in no way "virgin".

We're looking for a never rooted, never CWMed, stock ROM installed either Kies or OTA.

At least that guy have another example how things are being handled by must Samsung Service Centers:
[Galaxy Note GT-N7000 General] Markuzy:
I feel like going to my local telco store and run the OTA over their display gingerbread Notes.

Sent from my GT-N7000 using Xparent ICS Tapatalk 2
[Galaxy Note GT-N7000 General] opsakas:
"I decided to reflash the ICS rom."

But, what is the procedure used for reflash?

And did he have root? Yes or No.

And how do you know that the deffect was not activated BEFORE ics upgrade? After all, with any device, with any software, hard bricks happen and sometimes these are "normal" hardware failures.

Interesting is that the device was "laggy" right after first upgrade. The reason?
[Galaxy Note GT-N7000 General] jimmod:
I don't think we can find hardbricked galaxy note user that never root his phone posting their issue on xda-developers or maybe on internet.

Those people will just directly go to Samsung Service Center and replace their board (warranty).

So this debate will going nowhere
[Galaxy Note GT-N7000 General] Gaugerer:
I found your post interesting because you have flashed several official stock roms without root and no problems. I flashed ICS LPY over GB on my UK rom without root and now I cannot get Odin to detect my Note and many people are in the same position.
[Galaxy Note GT-N7000 General] opsakas:
Now, try this:

Google search:

Galaxy note bricked -xda

You might want to look:

galaxy note bricked ics -xda

The results are telling a story.

Well, what some of the devs are saying is that the stock ICS should not be installed on the phone at any cost. More correct way would be say: stock ICS should not be trusted if you are going to root it.

There are several, a lot of stories about how the battery is not good under ICS and how it gets better after wiping (oh no, not really!) and factory reset. But no stories about bricking, except that "according xda you may brick your phone with ICS".

Not all people are satisfied with Galaxy Note stock ICS but it seems that the bricking issue is not the question with the.

Oh, sorry, there are brickings like: my laptop froze during update and now the phone is dead.

My point is not telling you that you should not blame Samsung for the eMMC bug. Do as you like. But stop telling people that phones with stock configuration, using stock ICS are destined to brick sooner or later.

And as for you Gaugerer, didn't you try to flash with PC Odin without proper Windows 7 drivers installed first?

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

Again, misinformation. What is the point of it and why are you doing it?
[Galaxy Note GT-N7000 General] Gaugerer:
I Installed and ran Kies which I understand installs the correct drivers for Odin. I have no problem detecting the Note from Kies or Windows. I am not spreading misinformation, but just explaining my experience in case some one can help me and others in the same situation. I had already flashed the LPY ROM using Odin so I definitely used the correct working drivers.
[Galaxy Note GT-N7000 General] stoney73:
Seeing as you are an expert, pray tell what is the problem then?
[Galaxy Note GT-N7000 General] coolfire:
Yeah, expert by searching google.
[Galaxy Note GT-N7000 General] unkeen:
Drivers

@Gaugerer:

Windows 7, XP, 2000, 3.11?? Windows 8 preview?

Did you try with disconnected Phone: uninstalling drivers via device manager, reboot, stop/unload kies and kiestrayagent via taskmanager; THEN connect your device in USB Development mode, afterwards in Download mode.

Are all drivers installed correctly now, meaning no warnings in Device manager?

Have you installed adb (included in Android SDK)?

First try the above mentioned than post again.

:eek: If you even don't manage to install the drivers properly, you shouldn't try to flash anything via odin/ heimdall :eek:
[Galaxy Note GT-N7000 General] Gaugerer:
[/COLOR]

Thanks for your reply. I've not uninstalled the drivers via device manager for fear of doing something wrong which cannot be easily fixed. I have removed Kies and re-started the PC then installed and updated Kies. I then connected my Note to the PC and it installed 4 drivers without any errors. I then tried to connect to Odin in download mode but no yellow COM box. I've also used the Task Manager to remove any running Kies software which made no diffrence. I'm not sure what you mean by connect in USB Development mode but I am using USB Debugging mode.