Go Back   Android Forums > Android Phones > Samsung Galaxy S2 (International) > Galaxy S2 (International) - All Things Root

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

test: Reply
 
LinkBack Thread Tools
Old June 9th, 2012, 09:54 AM   #1 (permalink)
Senior Member
Thread Author (OP)
 
Hawker's Avatar
 
Join Date: Aug 2011
Location: UK
Posts: 3,749
 
Device(s): GT-I9505 Firmware: Danvdh GE 4.4.2 Kernel: KT BL: MGA GSM: XXUFNC9 LTE: XXUBMH1
Carrier: EE UK (4G)

Thanks: 536
Thanked 1,712 Times in 1,049 Posts
Default Has your GS2 got the "Brick Bug"?

It is possible that flashing ICS kernels can brick your device. GB kernels were safe, but not so for ICS. It occurs if a bad kernel issues a certain erase method, whereby your device will lose all ability to boot thereafter.

This problem mainly effects the Galaxy Note, but it is possible certain GS2's can also be affected (depending on what chip you have and what kernel you flash)

Good old Chainfire has written an app that can detect if your GS2's chip to see if it can be affected or not. The app can be downloaded in his Brick Bug Thread

According to this app, mine is affected! I will now need to be very careful what kernels I flash in future. I will now only ever flash Siyah, and I will also make sure any ROMs I flash only come with Chainfire or Siyah kernels.

__________________
Device: Samsung GT-I9505 ROM: Danvdh GE 4.4.2 Kernel: KT GSM: XXUFNC9 LTE: XXUBMH1 B/L: MGA

My Scripts
My Web Site
Hawker is online now  
Last edited by Hawker; June 9th, 2012 at 10:13 AM.
Reply With Quote
The Following 4 Users Say Thank You to Hawker For This Useful Post:
hippityhop (June 11th, 2012), ironass (June 11th, 2012), lotsip81 (June 9th, 2012), naith_kk (June 11th, 2012)
sponsored links
Old June 9th, 2012, 10:11 AM   #2 (permalink)
Member
 
jayroller's Avatar
 
Join Date: Sep 2010
Location: South of Heaven
Gender: Male
Posts: 102
 
Device(s): Samsung Galaxy S2 (NeatROM Lite v4.2), Ainol Novo7 Elf (Elvish 0.4)
Carrier: giffgaff

Thanks: 10
Thanked 26 Times in 23 Posts
Default

Quite true, and mine falls into the "ohnoes!" category also, however, Entropy's post says
Quote:
GT-I9100 users are in the least danger - No leak, official binary release, or source code release for this device has been dangerous. Only one I9100 kernel has ever proven dangerous and that was quickly pulled by its developer.
and
Quote:
I've received an email from a contact at Samsung who has indicated they are working on some sort of fix to be deployed to devices with an "UNSAFE" configuration listed above. I have requested that I receive an explicit list of which binary builds contain this fix, as without that I cannot know for sure which builds are fixed and which are not. Fixes are not yet deployed to affected devices.
Of course as you say, there could be a danger with an unknown, new kernel but then there's always been a danger present in that situation anyway, to my mind. So I'm not too concerned (honest guv!), but it's good to have the info - just in case...
jayroller is offline  
Reply With Quote
Old June 9th, 2012, 10:27 AM   #3 (permalink)
Disabled
 
Join Date: Nov 2011
Location: Geocache
Posts: 306
 
Device(s): SE Xperia X8, HTC Desire S, Samsung Galaxy S2
Carrier: Not Provided

Thanks: 33
Thanked 75 Times in 66 Posts
Default

Same here. Probably most are in same boat unless they show as unknown. I'll stick to cm9 builds as they seem safe enough. I must have flashed over 30 roms in the last 6 months.......ignorance is indeed bliss.
Logan47 is offline  
Reply With Quote
Old June 9th, 2012, 01:39 PM   #4 (permalink)
Senior Member
Thread Author (OP)
 
Hawker's Avatar
 
Join Date: Aug 2011
Location: UK
Posts: 3,749
 
Device(s): GT-I9505 Firmware: Danvdh GE 4.4.2 Kernel: KT BL: MGA GSM: XXUFNC9 LTE: XXUBMH1
Carrier: EE UK (4G)

Thanks: 536
Thanked 1,712 Times in 1,049 Posts
Default

Ok been doing a bit of further digging.

It seems the problem exists when a wipe data/factory reset is issued in CWM or you do a CWM restore. The problem lies with the existing kernel, and not the kernel you are flashing.

I think (and I stress THINK) ROM Nuke script would be safe as far as factory reset etc. is concerned, as this contains a GB update-binary. I've been doing a ROM Nuke all the time between ROMs anyway. I can't say for certain this is definitely safe, but I can say its definitely safer than doing it manually via CWM.

Until Samsung iron out the problem and the fixes get passed on between ROMs and kernels and developers, the only 100% safe way is to use Odin as this does not interact with your current kernel, but no ROMs are in .tar/md5 format these days barring Lite'ning.

Providing we stick with Siyah (which is know to be safe, not having MMC_CAP_ERASE enabled) we should be safe whatever we do. The problem may arise when we flash a ROM that may be bundled with an unsafe kernel.

GS2Wiper is safe to use regardless of if you have an unsafe kernel or not. Not only does it have the GB update-binary, but it no longer issues any format commands (for cache/dalvik)

Upshot for now is, don't use stock kernels, or chainfire kernels (as these are pure stock kernels with CWM attached), use ROM Nuke, dont use CWM to factory reset (or even via the settings menu of the running handset) and stick to Siyah. (Neak I would think is safe too)

I have to stress however, that the I9100 is at the very lowest risk category compared to all other devices, so the chances are extremely slim, so you can almost guarantee all kernels to be safe.
Hawker is online now  
Last edited by Hawker; June 9th, 2012 at 01:41 PM.
Reply With Quote
Old June 9th, 2012, 05:04 PM   #5 (permalink)
Member
 
Join Date: Feb 2012
Posts: 311
 
Device(s):
Carrier: Not Provided

Thanks: 37
Thanked 12 Times in 12 Posts
Default

i have the brick problem too. maybe i am gonna stop flashing or trying a diff rom as of the moment?
caloyzki is offline  
Reply With Quote
Old June 9th, 2012, 11:36 PM   #6 (permalink)
Junior Member
 
Join Date: Mar 2012
Posts: 77
 
Device(s):
Carrier: Not Provided

Thanks: 50
Thanked 6 Times in 6 Posts
Default

I'm sorry Hawker but I'm kinda skeptical on this. Maybe it's an overblown issue. Is this bug something that was just created, or something that has lay benign? Most of us, of course including you, have been flashing roms and kernels for at least half a year, and 99.9% definitely have not bricked our phones. I dont understand why suddenly, out of the blue we have this problem.
hippityhop is offline  
Reply With Quote
Old June 10th, 2012, 01:31 AM   #7 (permalink)
Senior Member
Thread Author (OP)
 
Hawker's Avatar
 
Join Date: Aug 2011
Location: UK
Posts: 3,749
 
Device(s): GT-I9505 Firmware: Danvdh GE 4.4.2 Kernel: KT BL: MGA GSM: XXUFNC9 LTE: XXUBMH1
Carrier: EE UK (4G)

Thanks: 536
Thanked 1,712 Times in 1,049 Posts
Default

I've already said our devices are right down at the very lowest end of the risk table. It's just that since ics has rolled out, its possible certain ics kernels could trigger the bug. Gb kernels could not exploit the problem code in the chip.

There is no harm in making you all aware of the issue.
Hawker is online now  
Last edited by Hawker; June 10th, 2012 at 01:34 AM.
Reply With Quote
The Following 2 Users Say Thank You to Hawker For This Useful Post:
hippityhop (June 12th, 2012), Kaddoble (July 10th, 2012)
Old June 10th, 2012, 01:57 AM   #8 (permalink)
Member
 
lotsip81's Avatar
 
Join Date: Feb 2012
Posts: 234
 
Device(s): Samsung GT-I9100 Firmware:NeatRomLite XWLSW Kernel:Siyah 6.0beta4 Baseband:XXLS8
Carrier: Not Provided

Thanks: 66
Thanked 37 Times in 31 Posts
Default

After reading this I checked mine out, and mine is one that is affected as well. I can say from my own personal experience that I have use CWM to do the 4 wipes as well as Hawkers program as well. So far I have had no issues. I generally stay with the more well known rom and kernel makers, but I have also to dabble other places as well.

But what I can say is this, Chanfire and Hawker have a lot more experience in programming and coding than most of us do. If they tell us there is a possibility that flashing could brick our devices, then I believe the chance is there. But after reading CF and Hawkers postings about this, it does indeed seem our chances are low.

I for one appreciate the heads up and am grateful to have the knowledge that this could happen. Hopefully it never does, but at least if it does I have an idea of why.
lotsip81 is offline  
Reply With Quote
Old June 11th, 2012, 04:21 AM   #9 (permalink)
Member
 
naith_kk's Avatar
 
Join Date: Jul 2011
Posts: 186
 
Device(s): Galaxy S-II
Carrier: Not Provided

Thanks: 13
Thanked 28 Times in 26 Posts
Default

So, as long as the drivers/mmc/host/mshci.c source code of any kernel used has MMC_CAP_ERASE removed or disabled by developer default, then the kernel is most likely a safe kernel.

This is good to know... at least when experimenting flashing new kernels.

Reference: Entropy512 (Conditions: Point no.3)
__________________

naith_kk is offline  
Last edited by naith_kk; June 11th, 2012 at 04:35 AM. Reason: ref.links.
Reply With Quote
The Following User Says Thank You to naith_kk For This Useful Post:
Hawker (June 11th, 2012)
Old June 11th, 2012, 08:19 AM   #10 (permalink)
New Member
 
Join Date: Jul 2011
Posts: 12
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 2 Times in 2 Posts
Default

It's funny that some are saying to only stick to chainfire or siyah, when the siyah rc6 (quickly pulled) was the only known kernel for sgs2 that had the issue.

So this app just confirms that your phone is susceptible, not that you have a bad kernel. Sounds like most people will be susceptible, but almost 0 will have a bad kernel currently installed.
MatchstiK is offline  
Reply With Quote
sponsored links
Old June 11th, 2012, 01:01 PM   #11 (permalink)
Member
 
naith_kk's Avatar
 
Join Date: Jul 2011
Posts: 186
 
Device(s): Galaxy S-II
Carrier: Not Provided

Thanks: 13
Thanked 28 Times in 26 Posts
Default

Gokhanmoral said that he implemented a patch in 3.2.5.2 that was coded by Samsung on the matter of eMMC chip issue... I'm guessing thats the issue that Entropy512 was describing about.

Quote:
[MMC] Patch the firmware of certain Samsung emmc parts to fix a bug
Patch the firmware in certain Samsung emmc chips after every power-on to workaround a bug in the wear leveling code. Patch provided by Samsung Semiconductor, and the code to apply the patch was originally written by Jeonghwan Min of Samsung.
What I want to know is... is this patch permanent and flashes the problematic chip to function as it should; or does it mean only to protect Siyah kernel binaries from making a fatal mistake?
naith_kk is offline  
Reply With Quote
The Following User Says Thank You to naith_kk For This Useful Post:
ironass (June 11th, 2012)
Old June 11th, 2012, 01:01 PM   #12 (permalink)
Senior Member
 
ironass's Avatar
 
Join Date: Aug 2010
Location: Cotswolds, England
Gender: Male
Posts: 8,009
 
Device(s): SGS4 GT-i9505. Rooted. GE KitKat 4.4.2 Danvdh ROM. Baseband: NC9. Kernel: ktoonsez+PhilZ
Carrier: Vodafone

Thanks: 1,088
Thanked 3,613 Times in 2,395 Posts
Default

I do not think that Hawker intended this thread to spread alarm and panic.

Rather it should be treated as a FYI, (For Your Information).

Firstly so that you are aware that the possibility exists and secondly to exercise good judgement when it comes to flashing kernels or ROM's with kernels, particularly if it is from a previously unknown developer.

It's a bit like that advice about not standing under an oak tree during a thunder and lightning storm... unlikely that you'll be struck... but why push your luck!
__________________
Did you know that hitting the Thanks button is quicker than typing it and the Search button is your friend.

Dummies Guides Rooting Galaxy S4 * Know Your S4 * Update Problems * Knox Security * Bloatware * GPS
ironass is online now  
Reply With Quote
The Following 2 Users Say Thank You to ironass For This Useful Post:
hippityhop (June 12th, 2012), Logan47 (June 12th, 2012)
Old June 12th, 2012, 09:34 PM   #13 (permalink)
Disabled
 
Join Date: Nov 2011
Location: Geocache
Posts: 306
 
Device(s): SE Xperia X8, HTC Desire S, Samsung Galaxy S2
Carrier: Not Provided

Thanks: 33
Thanked 75 Times in 66 Posts
Default

Indeed. I'll still be flashing roms but not everything under the sun and probably pay more attention to kernel specifics. A unfortunate set of circumstances has to be met for this to befall anyone. If we wants a total comfort zone then best to stick to one rom, but where's the fun in that?
Logan47 is offline  
Reply With Quote
Old June 13th, 2012, 08:11 AM   #14 (permalink)
Member
 
Join Date: Apr 2012
Location: Ireland
Gender: Male
Posts: 140
 
Device(s): Samsung Galaxy S4 GT-I9505, Samsung Galaxy S2 GT-I9100, Samsung Galaxy Tab 2 10.1
Carrier: 3 Ireland

Thanks: 8
Thanked 20 Times in 17 Posts
Default

I tested my S2 today and it is affected.

Would I be right in saying that if I keep my kernel as siyah then I could use any ROM or am I missing the point entirely.

Incidentally I have been using CAN to do my wipes.
Romulous is offline  
Reply With Quote
Old June 13th, 2012, 04:09 PM   #15 (permalink)
Member
 
Sword Fish's Avatar
 
Join Date: Oct 2011
Location: Calgary, AB
Posts: 329
 
Device(s): Galaxy S3 GT-i9300 White 16g Galaxy S3 SCH-i747M Blue 16g
Carrier: Not Provided

Thanks: 32
Thanked 41 Times in 34 Posts
Default

I have been flashing 2-3 new ICS ROMS every week and havent had any issues. I mainly use Siyah but have tried fluxi and abyss kernels without issues. I preordered my S3 and it is supposed to be here in one week so if I do have an issue, I shouldn't be out for long...
__________________
Samsung Galaxy S2 GT-I9100 16g w/32G SD
Samsung Galaxy S3 16g Blue SCH-I747M w/32G SD - SIM Unlocked
Samsung Galaxy S3 16g White GT-I9300 w/32G SD
Sword Fish is offline  
Reply With Quote
Old July 8th, 2012, 09:56 AM   #16 (permalink)
Member
 
Join Date: Jan 2012
Location: Buenos Aires, Argentina
Posts: 173
 
Device(s): Galaxy S2 International. ROM: I9100_4.4.2_AOSP_NeatROM_v3.10
Carrier: Not Provided

Thanks: 89
Thanked 4 Times in 4 Posts
Default

Very interesting Hawker. Thanks for the post.

So What should we do now?

Thank you!
glore2002 is offline  
Reply With Quote
Old July 8th, 2012, 10:05 AM   #17 (permalink)
Senior Member
 
ironass's Avatar
 
Join Date: Aug 2010
Location: Cotswolds, England
Gender: Male
Posts: 8,009
 
Device(s): SGS4 GT-i9505. Rooted. GE KitKat 4.4.2 Danvdh ROM. Baseband: NC9. Kernel: ktoonsez+PhilZ
Carrier: Vodafone

Thanks: 1,088
Thanked 3,613 Times in 2,395 Posts
Default

Quote:
Originally Posted by glore2002 View Post
Very interesting Hawker. Thanks for the post.

So What should we do now?

Thank you!
Adopt the crash position as displayed on the aircraft in-flight, safety cards, and bend over and place your head firmly between your knees...





and kiss your ass goodbye!


I think the easy answer is NOT to install the LQ5 firmware and, wherever possible, use a kernel, such as Siyah, that has the anti brick patch.
ironass is online now  
Reply With Quote
The Following User Says Thank You to ironass For This Useful Post:
glore2002 (July 8th, 2012)
Old July 8th, 2012, 10:07 AM   #18 (permalink)
Senior Member
 
Rudedawg's Avatar
 
Join Date: Jun 2011
Location: Southampton UK
Posts: 853
 
Device(s): Samsung Galaxy S4 I9505 DjeMBeY MGA ROM
Carrier: EE

Thanks: 163
Thanked 93 Times in 78 Posts
Default

Yay im in the endangered club! Party!!!
Rudedawg is offline  
Reply With Quote
Reply
Tags
my handy threads


Go Back   Android Forums > Android Phones > Samsung Galaxy S2 (International) > Galaxy S2 (International) - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 08:15 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.