yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 General] shatroghistro:
This is some good news, I am glad I did not do any wipes while I was on stock ICS.

Entropy, if there is an opportunity, say something about the black crush issues. Thx
[Galaxy Note GT-N7000 General] MohElShafei:
Perfect news Entropy512, great job my friend .. Wish you all the luck and really appreciate what you are doing .. Thanks a lot my dear friend.
[Galaxy Note GT-N7000 General] orobin:
Hi,

it gives me a question :

is there a way to have, later (when samsung will have found a solution ?) a galaxy note stable, without any risk to brick it (I know, flashing rom is always a risk, but I have flashed several device : LG, HTC DEsire HD, Galaxy spica, etc... without any bug, so I was hoping to find a way to have a Note possible to custom, without having the risk of killing it.

thanks

Olivier
[Galaxy Note GT-N7000 General] alvinasnow:
Respected Sir Antropy512.

Right now I have a Note (got superbricked and resurrected by employing hg42 thread http://xdaforums.com/showthread.php?t=1667886 ) and i also had to sacrifice 3+GB space. Given ur summary, should i hope I might be able to regain the full available space once again?

Thanx for all of ur earnest efforts. God Bless you
[Galaxy Note GT-N7000 General] Entropy512:
As it is we're not getting what we need from Samsung for a critical issue like this, I'm not going to dilute the conversation by bringing up unrelated minor issues.

Right now, most likely yes, HOWEVER: There is a good chance the process will fail in a way that requires you to have your phone JTAGed back to life. However, once JTAGed, it will have all space back.

If Samsung can't even reliably OTA-update bootloaders (see the pile of T-Mobile Nexus S units that bricked during an OTA), there's no way I'm going to reliably wipe/repartition/rewrite bootloaders for all devices.

Also, keep in mind that this lack of USB booting is going to delay the deployment of a solution significantly. While it is possible to repartition a device and repopulate the bootloaders from the kernel, it is difficult and not something I've ever done before. Instead of allowing reuse of existing tools (Heimdall/Odin combined with a PIT file and files to flash), Samsung is forcing many parts of this solution to be developed from scratch.
[Galaxy Note GT-N7000 General] becosemsaida:
At last !! Some good news, and a sign that your hardwork isn't for nothing.

Just one question: Like me there are many users that are on lpy (for example) and didn't n flash yet because they are waiting for a solution "online". Is there going to be a solution for this with the next update ??

If there is not, the only way to be "safe" is reverting to GB and use a rom from this forum... Think it's time to invest in a jtag. Don't want to be "triangeled".......

becosemsaida
[Galaxy Note GT-N7000 General] Entropy512:
I'm not sure what Samsung is planning to deploy. We've made it clear that any solution which does not block secure erase at the kernel level is one that we will continue to consider dangerous and list as such in lists such as my post in the Got Brickbug? app thread.

There's debate over whether non-secure erase is OK. Samsung thinks it is safe, I have seen enough reports of damage from stock recovery that I disagree with this assessment. The thing is, to truly know whether it is safe or not require a mass deployment of non-secure erase wiping to a community that wipes frequently and will report the results (such as here on XDA) - but in the event that it proves non-secure erase is NOT safe, that means I am now responsible for a potentially unrecoverable brick of users' devices.

If we had the ability to USB bootload devices, which means that any device is resurrectable by the end user with a bit of effort, then I would be willing to take the risk above. However, with the current proposals, I cannot. As a result there is a possibility that the safety of Samsung stock kernels will never be established.

Where I work, we frequently go through a process known as risk management. Risks to a project are identified, and then evaluated with both probability and impact on a high/medium/low scale. Probability is, of course, the chance that a risk will actually impact you. Impact is how badly you will be impacted if the risk event occurs. Samsung has convinced me that the probability is low, and keeps trying to argue about the probability. My issue is that the impact remains high - a low-probability high-impact risk is one that must be mitigated or planned for. Right now, this mitigation is to assume that non-secure erase is dangerous - less so than secure erase, but still dangerous. If the impact were medium (a user needs to go through a fairly technical procedure to recover, but can recover without sending their device to a service center or out for JTAG), I'd go forward with a large-scale deployment of non-secure erase - but so far, the impact is and will remain high.
[Galaxy Note GT-N7000 General] nfribeiro:
I agree 100% with you, we must focus on what is more important for the all community.

But there is something that I cannot understand. The solution for this critical issue have for me two important but different steps:

- one is the release of a fix in the form of updated official stock firmware to avoid MORE superbricks;

- other (also very important of course) is the development of solutions to repair damage devices.

What I cannot understand, and forgive me if I'm seeing things badly, is why we only can speak with Samsung about repairing and not about a release of a patch to fix the problem in the source.

I think that Samsung already have a patch and they are testing, which takes longer time.

But I also think that now we must ask also: When the patch will be rolling out?
[Galaxy Note GT-N7000 General] forest1971:
Subscribed B-)
[Galaxy Note GT-N7000 General] shatroghistro:
Re

That's why I said 'If there is an opportunity' , if they somehow ask you 'are there any issues we should fix, too?' :)

And I would have to disagree that black crush is a minor issue- it renders many pictures/videos unwatchable and unlike bricking, nobody recovered their screen from it. But I definitely agree that this brick bug should be resolved first, and we all appreciate your efforts more than you think. Thank you again, and remember, for black crush, I said for a highly hypothetical situation, not in any way being disrespectful.

All the best,

Shgh
[Galaxy Note GT-N7000 General] nfribeiro:
This black crush is more difficult than you think. Some users os the Galaxy S3 reported the same issue.
[Galaxy Note GT-N7000 General] shatroghistro:
Re

No, I am pretty familiar with it and I know that it is not an easy task, it is even more dificult to fix than on s3. It's the amoled screens only that make these problems, some more, some less.

But let's drop the subject and focus on the bricking issue :)

Cheers, bro
[Galaxy Note GT-N7000 General] sangalaviral:
We should never forget that face to face meetings are more productive than phone calls.

I wish you all the luck Entropy. I hope you will be able to get the ready to share the Binary blobs or whatever info is needed to deliver a end user mechanism to fix the already harmed devices and to create unbrickable mod :)
[Galaxy Note GT-N7000 General] alvinasnow:
Thank You Antropy for quick reply. I hope to find a self-implementable solution for superbricked devices through your sincere efforts. I have never followed a post so anxiously and continiously than this one. I stay on it and keep refreshing it to hope that upon one certain refresh i will find a post from antropy telling us that Samsung has provided us with what we need :fingers-crossed:

Always praying for all my esteemed developers.
[Galaxy Note GT-N7000 General] shatroghistro:
Re

Can you at least spell his name right? Entropy, not Antropy. This was not the first time you got it wrong
[Galaxy Note GT-N7000 General] endingcolt007:
Sorry to interupt the discussion but i have a small question that i need help with: I am currently having this eMMC bug on my note and currently im running the stock ICS 4.0.3 ROM with the Speedmod k3 kernel. as far as i know this kernel is safe but to be 100% safe most people told me to downgrade to GB and flash abyssnote 4.2 kernel(correct me if im wrong). Will this make my Note 100% safe? If it will then can anyone tell me if i should use ODIN or any other app to flash the GB ROM?

Secondly are all GB ROMs safe or only the stock GB ROMs?
[Galaxy Note GT-N7000 General] Final5k:
All GB roms are safe and there is no need to flash any kernels if you only want stock GB. I was also on UK ICS and flashed back to UK GB with PC Odin.
[Galaxy Note GT-N7000 General] Roy_W:
Hi Entropy,

I am unsure which level of developer/team leader/manager that you will be communicating with but where possible can you request that they provide us with a means to identify official un-bugged kernels.

I presume that Samsung will eventually compile kernels that have the MMC_CAPS code disabled, at the very least they could provide us with a list or signal to us

which kernel versions are released bug free.

It's only a suggestion and I understand that your primary goal should

remain in focus.

Cheers

R
[Galaxy Note GT-N7000 General] Entropy512:
At least it's not Entrophy... People are ALWAYS doing that...

Speedmod is safe. In fact it may be safer than GB due to having MMC_CAP_ERASE clearly disabled. Similarly, CM9 is safe for the same reasons. See the I9100 community as an example - with the exception of the SiyahKernel 3.1rc6 incident (which was caused by an attempt to use Korean sources with MMC_CAP_ERASE enabled), this issue is unheard of in that community.

That is one item I intend to continue pursuing. Since Samsung kernels don't always match the source, (even though legally, they should) and there's no way to tell which tree a binary was built from (e.g. when we have two source trees available - either one could be the tree for a given kernel and they would still be GPL compliant), verification is difficult.

Potentially it could be implemented as an #ifdef that is triggered by a defconfig change. This combined with enabling /proc/config.gz would allow for verification that a kernel has the fix.
[Galaxy Note GT-N7000 General] alvinasnow:
Ooops. language problem. my apologies from Sir Entropy :o
[Galaxy Note GT-N7000 General] panyan:
+1 :D
[Galaxy Note GT-N7000 General] bindo:
Going thru various threads on this issue I found the post by Forest 1971 in the following a great help. I've to study it fully before venturing

http://xdaforums.com/showthread.php?t=1661590
[Galaxy Note GT-N7000 General] alvinasnow:
superbrick enthusiast :D
[Galaxy Note GT-N7000 General] friedje:
Somebody just managed to superbrick his galaxy tab 7.7 by doing a wipe on the new ICS 4.0.4 rom. So it seems likely when it will arrive for the note any day now it won't be safe either...
[Galaxy Note GT-N7000 General] musashiro:
Samsung Galaxy s2 4.0.4 LEAK

WTF?? really?? can you please provide a link?

edit: did a little searching and got the thread link.. check here. scr*w you Samsung... i'm really starting to lose confidence on Samsung. they know the issue yet they continue to spread dangerous firmwares... :@
[Galaxy Note GT-N7000 General] Asrafiel:
Coming Soon they said..
[Galaxy Note GT-N7000 General] jgaviota:
The correct link for the bricked Tab 7.7 is Hard bricked 7.7

And indeed it seems a brick using stock kernel and maybe custom recovery.
[Galaxy Note GT-N7000 General] tonyking:
hello guys today i had sold my s2 and now i'm planning to buy note but i really scared of this fact that most of note encountered with brickbug problem :rolleyes:

what should i do should i buy it or not as well as if i buy it keeping it on gb with root access is this could cause brick prob or should i not to root it :silly:

this is in my knowledge that new ics firmware is not suitable for note till brick bug prob sort out :crying:

on xda many user are expert and mostly dev are genius :good:

a best reply and help is highly appreciated plz suggest me guys :(
[Galaxy Note GT-N7000 General] Moon2:
Staying on gb and rooting is fine, there's only the same risk of bricking as any other device out there if you do this.
[Galaxy Note GT-N7000 General] tonyking:
i think i should buy it and keep it on gb(without root) and wait for solution for emmc brick prob this could be better in every way, hhahah lolz :laugh:

moreover thnaks for your help dude :good:
[Galaxy Note GT-N7000 General] Entropy512:
Not entirely confirmed. Remember - for some odd reason, if /system gets mildly corrupted, Odin will fail to flash the partition even though it should just overwrite what is there regardless of current content. This happens to Note users occasionally, and if it is that failure, just formatting /system in recovery fixes the issue. This issue is why I modified the recovery init scripts to not automount /system so it can be more easily formatted. Some people mistakingly called it "lost partial root" even though it has nothing to do with root access.

I'm working on collecting more info. If it is truly superbrick, and occurred when wiping in stock recovery, I'm going to try and have that guy's unit sent to my contacts at Samsung. They are still of the opinion that only secure erase can cause damage - but I've seen enough reports that I don't think normal non-secure erase or TRIM is safe.
[Galaxy Note GT-N7000 General] remorema:
my phone died after full wipe in recovery, including mounts and storage system,data,cache. full details here http://xdaforums.com/showthread.php?p=28342963#post28342963

does this have anything to do with this emmc brick ? :(
[Galaxy Note GT-N7000 General] SpyderTracks:
You have s2 is that right? S2 kernels are not affected imho.
[Galaxy Note GT-N7000 General] Entropy512:
This may have just changed with the I9100's latest leak if this report is correct.
[Galaxy Note GT-N7000 General] SpyderTracks:
Oh christ, well done samsung...
[Galaxy Note GT-N7000 General] :
:facepalm: to Samsung! :rolleyes:
[Galaxy Note GT-N7000 General] tonyking:
info

guys one information which i want to share with you

yesterday i put mail to CEO of samsung mobile and told every thing related to faulty ics firmware, kernel prob, emmc-brickbug prob and all information about the user who had bricked their device

today i got call from SSC the person to whom i was taking told me that there is nothing to worry about ics firmware and kernel does not contain any fault like this both sgs2 and note are highly up gradable set and to upgrade note you should have speed of 3.0 mbps if yu upgrade it through kies or upgrade it from service center and if there is any prob found after update samsung technician are ready to help us

one thing more as everyone know that ics has more battery drain prob than gb so there is nothing to worry about and rooting the device is third party software and samsung does not provide any help if you root your device and got it bricked so be care full and enjoy upgrading

btw- upgrading is at your own risk if you do it manually
[Galaxy Note GT-N7000 General] alvinasnow:
Your information is handy for many, but no offence, didn't emuse me much, (personal opinion :) Don't mind. Because people at xda, generally like to play with their devices. If they ought to follow Samsung's rules, then there is no point of xda's existence at the first place. We all know that if we upgrade according to Samsung's directions, we are good to go, but frankly speaking very few would want to use those option-less Stock Roms whether GB or ICS.

The guy, who talked to you failed to realize this fact that the phone's under question, when factory reset with ICS Kernels are bound to brick. :( I think his was a typical customer satisfaction talk.

My apologies for my opinion (which may be wrong)

Cheers.
[Galaxy Note GT-N7000 General] tribalkg:
You have to understand that they won't admit it so easily because that would be bad marketing. If they are working with Entropy (and maybe more people), that means that they want to find solution and keep it low from the wider range of customers.

Not everybody in Samsung knows about this problem, especially not customer service workers and community managers.
[Galaxy Note GT-N7000 General] iraqi4ever80:
does this include the official rom

Hi everybody,

Does this problem include official roms, I have galaxy note GT-N7000 middle east version it is running GB till now but i want to upgrade it using samsung kies.

my question is did samsung solve this issue or i should wait more time.

thanx in advance
[Galaxy Note GT-N7000 General] deviantish:
From what I understand based on this thread and the posts made by people who know more about this issue, some one from Android development team at Google has also confirmed the presence of the emmc_bug. However, that developer cannot release the code without proper approval from management in Google and Samsung. At this point most developers agree on its presence and those who have been doing research into this topic believe a system call in the kernel is the root cause.

I doubt Samsung would ever acknowledge the presence of this bug as it would scare off too many customers. But denying the existence of this bug puts people into a false sense of security, and we go our normal business until someone does a wipe on ICS and gets effected by it.

I personally feel, at this point, xda developers know more about this issue than Samsung Management. Also, this bug is not limited to the Note but other Samsung mobiles have been effected by it.

I think this thread was supposed to be more like an "update" on the current state of things. Maybe mods should lock this and allow only senior developers to comment on this issue while the rest of us wait for Samsung to fix things at their end.

Cheers.
[Galaxy Note GT-N7000 General] shinzi:
now i am using 4.04 China version~it's a official version.i upgrade my note via ota.

here is 2 screenshots

seem as if samsung hadn't fixed the bug :(
[Galaxy Note GT-N7000 General] sonkameja:
Why upgrade then ?

Sent from my GT-N7000
[Galaxy Note GT-N7000 General] friedje:
Is it SO HARD to understand ?

The app made by chainfire only reads which Emmc Chip is inside your

your phone, and what firmware it runs...

You could flash Android Lollypop 8.5 on your phone whenever google/samsung releases it, it won't change anything on the outcome of your test.......

Even if this 4.0.4 rom would contain a fix, it wouldn't change anything on the outcome of your test....
[Galaxy Note GT-N7000 General] Entropy512:
Yes. The **** really hit the fan here when official XXLPY went live - first time outside of Korea that an official release was capable of triggering the problem.
[Galaxy Note GT-N7000 General] Entropy512:
Whoever you talked to had no ****ing clue, or was lying through their teeth... That's about the best way I can describe it.
[Galaxy Note GT-N7000 General] abhijit038:
Even I got similar response from a tier 3 representative. Incidentally, I have wiped endless times on different stock firmwares released so far. I didn't get bricked. However, when I asked her about wiping after rooting, she just said that it would void the warranty and do it at your own risk. Can anyone elucidate why wiping on rooted rom is so risky?
[Galaxy Note GT-N7000 General] iraqi4ever80:
thanx for your rapid response I appreciate that

i will not upgrade and wait and see what will happen

hoping for a solution as soon as possible
[Galaxy Note GT-N7000 General] shatroghistro:
RE

I never liked samsung, and this issue is only making it worse. I feel like selling my Note and never again buy a cellphone that costs more than 100 euros.
[Galaxy Note GT-N7000 General] shinzi:
oh,i see, i am sorry for the last post in this thread,is my fault,my english is bad,so i made a mistake.
[Galaxy Note GT-N7000 General] Entropy512:
Root has zero effect despite her claim. When you are in recovery, the only thing that matters is the kernel initramfs - contents of /system do not matter. When you are in recovery, "root" is just another file in /system, indistinguishable from any other as far as wiping algorithms go. In fact, her claim that root voids your warranty is incorrect in many countries. For example, in the United States, her claim is in direct conflict with the Magnusson-Moss Warranty Act, which states that a manufacturer must prove that modifications were the cause of damage before denying warranty service. (This was passed decades ago due to lobbying efforts by SEMA, an association of vendors of aftermarket modifications for vehicles - but it applies to phones too.)

CWM, if wipe isn't suppressed, can be more dangerous than Samsung stock recovery - Samsung believes that only secure erase (done by default in Google-originated source code) is dangerous. However the experiences of Robotu and others have me convinced that while non-secure erase (done by stock recovery) is less dangerous, it is not 100% safe. Also note that even CWM's secure erase doesn't always cause damage - some I777 developers wiped multiple times using CWM on the UCLD3 leak without issues, and Gokhanmoral tested wiping with SiyahKernel 3.1rc6 on the I9100 multiple times without issue - but plenty of users suffered damage. One example of what appears to be damage due to wiping on stock ICS is at http://xdaforums.com/showthread.php?t=1752468 - The Tab 7.7 gets to join the party now.
[Galaxy Note GT-N7000 General] abhijit038:
I wish they followed same policy in my country too. Nonetheless, thanks for quick response and throwing light on this subject.
[Galaxy Note GT-N7000 General] garwynn:
This

is the part that rubs me raw. We haven't seen this with the 10.1 and to be honest I don't know what eMMC it has.... but I wouldn't be surprised to see that join the party. It's the only device missing from the Galaxy 2011 lineup.

What's even more frustrating is that some devices got the firmware update such as the GNex and AT&T Note prior to shipping. We know the GNex wasn't patched until Google hit the lockup - that explains that device. I really am curious how the Note got it when everything else seems not to have? Perhaps AT&T noticed a high brick rate in initial testing?

I really hope your meeting next week is productive and that they're willing to help with results. (It's still on, right?)
[Galaxy Note GT-N7000 General] friedje:
Galaxy tabs 10.1 and 8.9 use the MAG4FA chip with FW version 0x12.

So they are potentially in risk too..
[Galaxy Note GT-N7000 General] abhijit038:
They would only make any endeavour if the bug is present in stock Roms ,which seems unlikely.Apparently Samsung has already tested their Stock Roms and the results were negative.

---------- Post added at 12:22 AM ---------- Previous post was at 12:19 AM ----------

There is a similar thread about this topic http://xdaforums.com/showthread.php?t=1679829
[Galaxy Note GT-N7000 General] mdrjr:
The SuperBrick bug does affect stock rom.
[Galaxy Note GT-N7000 General] abhijit038:
Oh..I meant stock NON ROOTED Rom.Incidentally, I tested it myself. I have wiped my phone from factory recovery for over 20 times; I am on ZSLPF.

By the way, there hasn't been an incident reported so far where a person on stock non rooted ICS ROM bricked his phone.Even Samsung dev. were unable to reproduce the bug.Please refer to the link.aforementioned in my last post.
[Galaxy Note GT-N7000 General] PoisonWolf:
When you wiped 20 so called times, did you wipe, boot into the rom, install apps or do a titanium restore, then go into recovery and then only wipe? Or did you simply hit wipe 20 consecutive times?
[Galaxy Note GT-N7000 General] M3TALLICA:
Great news.

Considering how slow samsung is on software updates, I think we'll get it in Q4 2012

cough...cough...

Thanks a lot Entropy, Chainfire and all other devs.

You guys are real heros. :)
[Galaxy Note GT-N7000 General] panyan:
I imagine this will be a priority because of the scope of affected devices and the possible backlash from this