Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Samsung working on Emmc brick fix

OP androidindian

8th June 2012, 11:33 AM   |  #1  
androidindian's Avatar
OP Senior Member
Flag New Delhi
Thanks Meter: 819
 
1,810 posts
Join Date:Joined: Nov 2010
More
More info and source credits here, thanks to codeworkx https://plus.google.com/111398485184...ts/21pTYfTsCkB.


Quote:

ATTENTION:
We've contacted Samsung about the problem where performing a mmc erase could hardbrick your phone (i9100, i9100g, n7000, m250 - MAG4FA, VYL00M, and KYL00M with firmware revision 0x19 // T989 and I727 with fw rev 0x12) if it's having a faulty emmc chip.
Read this thread for more informations about it: http://forum.xda-developers.com/show....php?t=1644364

They're working as hard as possible on a clean solution which will be ready soon.

Please be patient and try to not flash any leaked kernels or kernels based on sources where MMC_CAP_ERASE is present.

This app http://forum.xda-developers.com/show...74&postcount=1 can be used to identify if your phone is affected or not.

CM9 kernels are safe to flash.

Please share!

Update 14:56 CEST:
Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time.

New Clarifications by Entropy : http://forum.xda-developers.com/show...&postcount=403 - Must Read.

To check whether your phone has the brick bug, download the Got Brickbug app from Chainfire: http://forum.xda-developers.com/show....php?t=1693704

Also do read the article on xda for more info.: http://www.xda-developers.com/androi...hardbrick-fix/
Last edited by androidindian; 8th July 2012 at 07:26 AM.
The Following 52 Users Say Thank You to androidindian For This Useful Post: [ View ]
8th June 2012, 11:40 AM   |  #2  
Senior Member
Flag Warszawa
Thanks Meter: 12
 
112 posts
Join Date:Joined: Sep 2009
More
Nice!
8th June 2012, 11:46 AM   |  #3  
Senior Member
Flag Mumbai
Thanks Meter: 37
 
335 posts
Join Date:Joined: Jul 2010
More
That is a really good news after some time.

Sent from my GT-N7000 using Tapatalk 2
8th June 2012, 12:06 PM   |  #4  
Member
Thanks Meter: 5
 
40 posts
Join Date:Joined: Apr 2012
More
Good news!
Looking forward to see how Samsung solve this nightmare

Sent from my GT-N7000 using xda premium
8th June 2012, 12:17 PM   |  #5  
gominolo2002's Avatar
Senior Member
Flag Madrid
Thanks Meter: 44
 
275 posts
Join Date:Joined: Dec 2010
Donate to Me
More
How many time to fix this Samsung BUG? How maby people need ti brick our 600? If samsung knows why no first before? Grrrrr...

All hard work its from XDA devs!!!! Thank you devs!!

Enviado desde mi GT-N7000 usando Tapatalk 2
8th June 2012, 12:17 PM   |  #6  
nandihno's Avatar
Senior Member
Flag Brisbane
Thanks Meter: 101
 
1,009 posts
Join Date:Joined: Jul 2010
More
Hmmm don't want to get my hopes up
But hmmm ok let's hope saw but how do we know is true ?


Sent from my iPad using Tapatalk
8th June 2012, 01:29 PM   |  #7  
androidindian's Avatar
OP Senior Member
Flag New Delhi
Thanks Meter: 819
 
1,810 posts
Join Date:Joined: Nov 2010
More
Quote:
Originally Posted by nandihno

Hmmm don't want to get my hopes up
But hmmm ok let's hope saw but how do we know is true ?


Sent from my iPad using Tapatalk

Teamhacksung dev codeworkx been in touch with Sammy guys so its genuine news...check link in op :)



Sent from my GT-N7000 using xda premium
8th June 2012, 01:58 PM   |  #8  
jermitano's Avatar
Recognized Contributor
Flag Manila
Thanks Meter: 858
 
1,295 posts
Join Date:Joined: Oct 2011
More
at least we now have some hope...hopefully...
8th June 2012, 03:13 PM   |  #9  
Senior Member
Thanks Meter: 11
 
102 posts
Join Date:Joined: Aug 2006
So to be clear...
Can someone confirm the following is correct please?

I have a N7000 on official (german) ICS, with the dodgy mmc chip. I must have been lucky since ive flashed a bunch of roms (including CM9, back to gingerbread, then official ICS) without issue. Ive also done a few CWM backup and restores... phew!

1. Flashing anything from the phone itself (eg using mobile odin or CWM recovery) is a no-go (assuming it issues the erase command)

2. Flashing from the PC is OK ??? (via desktop ODIN)?

If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?

thanks

George
8th June 2012, 03:36 PM   |  #10  
nandihno's Avatar
Senior Member
Flag Brisbane
Thanks Meter: 101
 
1,009 posts
Join Date:Joined: Jul 2010
More
Quote:
Originally Posted by ripnetuk

Can someone confirm the following is correct please?

I have a N7000 on official (german) ICS, with the dodgy mmc chip. I must have been lucky since ive flashed a bunch of roms (including CM9, back to gingerbread, then official ICS) without issue. Ive also done a few CWM backup and restores... phew!

1. Flashing anything from the phone itself (eg using mobile odin or CWM recovery) is a no-go (assuming it issues the erase command)

2. Flashing from the PC is OK ??? (via desktop ODIN)?

If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?

thanks

George

Flashing is not the problem but wiping is
So if they release a new update then simply don't wipe on your ics but wipe only after you install the new update
If however you want to be extra careful like I am
Flash a gb rom via odin then wipe that then flash said ics update via Odin


Sent from my iPad using Tapatalk

The Following User Says Thank You to nandihno For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes