FORUMS
Remove All Ads from XDA

[05.09.2012] Got Brickbug ? v1.2

11,416 posts
Thanks Meter: 88,049
 
By Chainfire, Moderator Emeritus / Senior Recognized Developer - Where is my shirt? on 5th June 2012, 04:47 PM
Post Reply Email Thread
5th June 2012, 10:10 PM |#41  
Senior Member
Flag Mobile, AL
Thanks Meter: 306
 
More
Quote:
Originally Posted by KennyLegend

So flash last GB, wipe data, flash ics? Cool.


Excellent tip Chainfire
Thx

Or just flash last GB and stay on it and don't worry about flashing ICS.

---------- Post added at 04:08 PM ---------- Previous post was at 04:07 PM ----------

Quote:
Originally Posted by Northern-Loop

Is this only effecting Samsung ROMs or CM9 source as well?

Should I stop flashing Nightlys until the day or 2 later to make sure everything is okay?

CM9 ROMs and kernels are SAFE. You do not have to stop flashing the nightlies. The Samsung official and leaked ROMs and kernels are the faulty ones. Franco and Speedmod kernels are safe as well.

---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------

Quote:
Originally Posted by mamaams

my SII is 0x19 so I've tried to read abot this issue but i didn't understand anything actually could anyone explain the issue and how to avoid it ?

The emmc bug is on the official and leaked Samsung ROMs and kernels. On the Note, CM9 is safe. I'm not sure which ROMs are safe for SII but I'm sure CM9 is one of them. Avoid wiping data on the Samsung ROMs, or in my opinion, avoid Samsung ROMs entirely.
The Following 5 Users Say Thank You to andreww88 For This Useful Post: [ View ] Gift andreww88 Ad-Free
 
 
5th June 2012, 10:11 PM |#42  
KennyLegend's Avatar
Senior Member
Flag Cork
Thanks Meter: 1,238
 
More
Quote:
Originally Posted by adv1sory



+1 I heard the only way to find out is by reading the bad sectors which in turn would then brick it.

Sent from my GT-N7000 using Tapatalk 2

This is interesting..... if u flash a stock GB rom, do u then, in theory, make the corrupted sectors if any good again? A question for Chainfire me thinks ...

Sent from my GT-I9100 using xda premium
5th June 2012, 10:54 PM |#43  
Junior Member
Thanks Meter: 9
 
More
A method called JTAG bit blasting, which is supposed to bypass all but hardware issues, is known not to work.

Flashing a rom probably won't fix any sectors. I'm sure people have tried it and if it worked XDA would be awash with posts jumping for joy over the relatively simple fix. My understanding is hazy, but the eMMC chip seems to get corrupted internally because its wear leveling code is bugged. Wear leveling is low level stuff independent of write methods used during a flash. It can be recovered, but the code to do so is only known to developers who aren't permitted to share it.

Source: http://forum.xda-developers.com/show...&postcount=159

Incidently, chainfire had already provided a link with tons of background on this issue including a link to this very post that says:

Quote:

As I mention above, the revision 0x19 firmware had a bug that after an emmc erase command, it could leave the internal data structures of the emmc chip in a bad state that cause the chip to lock up when a particular sector was accessed. The only fix was to wipe the chip, and update the firmware. I have code to do that, but I don't know if I can share it. I'll ask.

5th June 2012, 11:06 PM |#44  
Senior Member
Flag Mobile, AL
Thanks Meter: 306
 
More
Quote:
Originally Posted by Namida

A method called JTAG bit blasting, which is supposed to bypass all but hardware issues, is known not to work.

Flashing a rom probably won't fix any sectors. I'm sure people have tried it and it it worked XDA would be awash with posts jumping for joy over the relatively simple fix. My understanding is hazy, but the eMMC chip seems to get corrupted internally because its wear leveling code is bugged. Wear leveling is low level stuff independent of write methods used during a flash. It can be recovered, but the code to do so is only known to developers who aren't permitted to share it.

Source: http://forum.xda-developers.com/show...&postcount=159

Incidently, chainfire had already provided a link with tons of background on this issue including a link to this very post that says:

Yeah, the Android Developers, like Mr. Sumrall, have the means of fixing the emmc chip by basically reformatting it (bad terminology) but Samsung hasn't given permission to release it yet.
5th June 2012, 11:30 PM |#45  
JoshuaTumanda's Avatar
Senior Member
Flag Cebu City
Thanks Meter: 52
 
More
Quote:
Originally Posted by andreww88

CM9 ROMs and kernels are SAFE. You do not have to stop flashing the nightlies. The Samsung official and leaked ROMs and kernels are the faulty ones. Franco and Speedmod kernels are safe as well.

Gives me a heartbreak for a while, but reading this post took it. Thank man!
The Following User Says Thank You to JoshuaTumanda For This Useful Post: [ View ] Gift JoshuaTumanda Ad-Free
6th June 2012, 01:16 AM |#46  
BrandoHD's Avatar
Senior Member
Flag Arima
Thanks Meter: 445
 
More
Quote:
Originally Posted by andreww88

CM9 ROMs and kernels are SAFE. You do not have to stop flashing the nightlies. The Samsung official and leaked ROMs and kernels are the faulty ones. Franco and Speedmod kernels are safe as well.

The emmc bug is on the official and leaked Samsung ROMs and kernels. On the Note, CM9 is safe. I'm not sure which ROMs are safe for SII but I'm sure CM9 is one of them. Avoid wiping data on the Samsung ROMs, or in my opinion, avoid Samsung ROMs entirely.

You are advising people to stay away from Samsung ROMS, are you sure this is correct?

Is this issue not a Kernel issue, therefore the ROM is of no consequence, but the kernel/recovery is what is really responsible for the issue

As far as my understanding goes, and from reading in the relevant thread that is dealing with this issue, ROMS were never discussed, Kernels were, you can use any ROM you like, the fix is at a kernel level

On another note, since Chainfire was able to release this tool that can check if your hardware is the one affected, is it at all possible to release a tool that can check to see if the kernel you are running has the dangerous code disabled???
The Following 2 Users Say Thank You to BrandoHD For This Useful Post: [ View ] Gift BrandoHD Ad-Free
6th June 2012, 02:41 AM |#47  
Senior Member
Thanks Meter: 37
 
More
Bingo! I got the bug! ha ha. Thanks for letting me know.

Sent from my GT-N7000 using xda premium
6th June 2012, 03:12 AM |#48  
Junior Member
Thanks Meter: 9
 
More
It's important to understand that the source of this problem is bad firmware in the eMMC chip. There is nothing technically wrong with the kernel itself. The eMMC claims to support a method of erasure that causes it to write bad data when it's used.

To achieve safety, you either fix the chip so that it supports the method it claims to properly or avoid using that method of erasure.

Cyanogenmod 9 is safe because it doesn't erase using that method. They use their own kernel built from their own source code.

Samsung ICS kernels are not safe because they call the best method the eMMC claims to support when erasing, which is bugged within the chip's firmware.

Anyone who uses the official Samsung ICS kernel or the ICS leaks of Samsung's kernel are at risk. Chainfire's kernel is risky because Chainfire uses Samsung's official kernels and adds Clockwork Mod to them at the binary level. He doesn't have source to modify to make his kernels safe. Samsung must make their kernel safe before Chainfire can release a safe one himself. What Chainfire has done is modify the recovery so that it won't ask the kernel to erase the eMMC in a potentially dangerous way, but it won't stop sources other than that recovery from asking for a potentially bricking erase operation because the kernel hasn't been modified and will still do it if asked to.

Because we know something of which versions of the eMMC chip are affected by this flaw, we can determine if a user is at risk simply by asking the chip to identify itself.

Decompiling a kernel is a completely different ball of wax. I wouldn't hold my breath for a tool that can do that and identify if your kernel is patched or not. Besides that, the source of the problem is now known with certainty and can be avoided by not flashing Samsung kernels until Samsung gets off their lazy butt and fixes theirs, or provides the code that can be used to fix the eMMC chip that is the source of all our troubles.
The Following 9 Users Say Thank You to Namida For This Useful Post: [ View ] Gift Namida Ad-Free
6th June 2012, 03:21 AM |#49  
Senior Member
Thanks Meter: 53
 
More
@CF: i know this prolly is asking too much, but is there a way u could scan for bad sectors? Could u possibly have such a tool?

@others, just coz u hv this firmware doesnt mean u r bricked, if u been using a safe kernel. My device got fried, n it only came evident whild trying to go back tl gb via odin.

Replacement i got under warrenty has been running happily under CM9 and official ICS with Speedmod.

Sent from my GT-N7000 using XDA
6th June 2012, 03:38 AM |#50  
aneeqkhan's Avatar
Senior Member
Flag Karachi
Thanks Meter: 96
 
More


I have an unknown chip see the screenshot. Now dont know should b happy or not...
Sent from my GT-I9300 using Tapatalk 2
6th June 2012, 03:43 AM |#51  
Senior Member
Thanks Meter: 528
 
More
Quote:
Originally Posted by aneeqkhan


I have an unknown chip see the screenshot. Now dont know should b happy or not...
Sent from my GT-I9300 using Tapatalk 2

Do you want to exchange your note with mine?
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes