Introducing XDA:DevCon – A Conference For Developers By Developers
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
danieldmm
Old
#131  
danieldmm's Avatar
Senior Member
Thanks Meter 935
Posts: 1,371
Join Date: Dec 2008
Location: France

 
DONATE TO ME
Quote:
Originally Posted by Gillion View Post
Does your phone have a faulty eMMC chip ?

You can check by using the GotBrickBug.apk application. It will tell you and us if your phone is one of the safe ones.
My friend that tested and record video Wipe data in Stock Kernel and also CF ROOT have the brick bug, screenshot attached.

They did one more Wipe data in CF ROOT and a backup nandroid, he did not try the restore option.

Cheers
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2012-07-08-16-11-58.jpg
Views:	342
Size:	34.0 KB
ID:	1184923  


If you like my work dont say thanks press also Thanks Button...
 
cpl.Bower
Old
(Last edited by cpl.Bower; 8th July 2012 at 04:12 PM.)
#132  
Senior Member
Thanks Meter 19
Posts: 136
Join Date: May 2012
Quote:
Originally Posted by ManDone.vRs View Post
I flashed 5 times on my SGS2 LQ5 4.0.4 and no brick !!!!
what files did you flashed?. That include the PIT file?. Did you have some issues? Like SOD (or whatever is called)?. Probably you were playing russian roulette and you didnt knew

could you please try this? http://forum.xda-developers.com/show....php?t=1693704

its Got Brickbug ?

please post the screenshot of that
 
ciph1
Old
#133  
Junior Member
Thanks Meter 2
Posts: 15
Join Date: Apr 2011
Cant anybody say if resurrection remix is safe? would ask directly in its thread, but im not allowed to ask...
 
BrandoHD
Old
#134  
BrandoHD's Avatar
Senior Member
Thanks Meter 288
Posts: 1,219
Join Date: Aug 2009
Location: Arima
Quote:
Originally Posted by ciph1 View Post
Cant anybody say if resurrection remix is safe? would ask directly in its thread, but im not allowed to ask...
It's mostly a kernel issue, so check and double check the kernel, if it's based purely on update 4 sources, it's safe.

To those above thinking that wiping a few times without brick is good, it is not, once the code is enabled in kernel, the brick is inevitable, not necessarily on first or second tries.

There is a thread dedicated to the issue, read it.

Samsung Galaxy S II Tapatalk2
 
BrandoHD
Old
#135  
BrandoHD's Avatar
Senior Member
Thanks Meter 288
Posts: 1,219
Join Date: Aug 2009
Location: Arima
Quote:
Originally Posted by googy_anas View Post
Please can you give the source of this information, it could be a light of hope ...
It's all in the thread dedicated to the issue, I'm on tapatalk, so hard to link that.

Samsung Galaxy S II Tapatalk2
 
GFXi0N
Old
#136  
GFXi0N's Avatar
Senior Member
Thanks Meter 123
Posts: 622
Join Date: Aug 2010
Quote:
Originally Posted by googy_anas View Post
Please can you give the source of this information, it could be a light of hope ...
I came across this info yesterday but it will be quite difficult for me to find it. It's in galaxy note sub forum in the thread talking about this brick bug, i'd like to find the post that states that the solution exists but Samsung is holding it back and does not allow its publication but I'm currently in a hospital and my only way of browsing is via Tapatalk, and the reception is very crappy.... Anyway, I will give it a try and see if I find that specific info... If I understood properly it could all be a matter of updating the damn Emmc chip to a different version. I'm not that pro and i could be mistaken,.... As said, I will do my best to retrieve that chunk of info (or you could help me find it)

Sent from my GT-I9100 using Tapatalk 2
Phone: Google LG Nexus 4 16GB - Rom: Stock Original Google 4.2.2
 
cpl.Bower
Old
#137  
Senior Member
Thanks Meter 19
Posts: 136
Join Date: May 2012
this Got Brickbug? should be on the 1st post. To warn ppl if they have a faulty chip that leads to permanently destroy your phone with this stupid rom...
 
iozzo
Old
#138  
Member
Thanks Meter 20
Posts: 40
Join Date: Mar 2012
So many questions ... I'll try my best to be short

I did flash 4.0.4 and I am (so far) fine (and quite happy with it to be honest).
I have used mobile odin and did NOT use the .pit file. Using Mobile Odin I didn't do any wipe before flashing but I did select to wipe into Mobile odin. Everything went fine.

eMMMc check says that "Brick Bug ? = YES. Insane chip".

Am I risking a bricked S2 or am I fine since I have used Mobile Odin (hence didn't wipe from CWM)?

If I have to go back to 4.0.3, I read that I have to avoid Mobile Odin and I don't have to wipe before flashing. So basically I just have to :
  • Put device into Download MODE (Home + Volume Down + Power)
  • Click PDA and select I9100_CODE_I9100XXLQ5_CL753921_REV02_user_low_ship .tar.md5
  • Click PHONE and select MODEM_I9100XXLQ5_REV_02_CL1165929.tar.md5
  • Click CSC and select GT-I9100-MULTI-CSC-OXALQ5.tar.md5
  • Then finally click START

Am I right?
Can I do a Wipe Data/Factory reset + a Wipe Cache after I have flashed a 4.0.3 back ?

Thanks in advance, 4.0.4 was too good to be true
 
GFXi0N
Old
#139  
GFXi0N's Avatar
Senior Member
Thanks Meter 123
Posts: 622
Join Date: Aug 2010
Just use Cyanogenmod and you will be safe.... The thing is that the unsafe versions are the official ones, lol!
Need more reasons for leaving Sammy rom behind than risking your overpriced phone?
I don't...

Sent from my GT-I9100 using Tapatalk 2
Phone: Google LG Nexus 4 16GB - Rom: Stock Original Google 4.2.2
 
cpl.Bower
Old
#140  
Senior Member
Thanks Meter 19
Posts: 136
Join Date: May 2012
Quote:
Originally Posted by iozzo View Post
Thanks in advance, 4.0.4 was too good to be true
if you wanna stay on 4.0.4 then flash CM9, which according with its author is MMC_CAP_ERASE free.
I dont know about if you now could wipe/factory reset, I wouldnt.
This happend because this was a leaked ROM that shouldnt be posted as official since the beginning.
I dont know, if jelly bean would be released first than 4.0.4, anyway, we need to learn from this lesson, NEVER flash a leaked/unofficial ROM or ANY rom based on this release. Every beta ROM has this MMC_CAP_ERASE "feature", I have no idea why.

 
Post Reply+
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

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

Go to top of page...