Hello All, My Galaxy S2(i9100) is not responding any more.... And I think this is a issue which is related to Galaxy S2 and Galaxy Note's eMMC bug. Because I had upgraded the firmware to STOCK ICS 4.0.3 (I9100XWLPG) which is available here. And i had flashed with chainfire's rooted kernel CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5.zip which can be downloaded from here. After using this firmware for a couple of months, recently i came through the eMMC bug news in Galaxy S2 And Galaxy Note. After that yesterday I downloaded chainfire GotBrickBug Application and found my device's firmware to be vulnerable to this bug. Then left my phone on the table and one hour later when i came back i found my phone dead. Phone was not responding and I tried Charging but it didn't respond...I pulled the battery but the condition didn't change. I think eMMC bug is responsible for the hardbrick of my device. But my question is that I didn't wipe or format my device so how the MMC_CAP_ERASE could occur?? I have sent my phone to the service center...
istipb said:
Hello All, My Galaxy S2(i9100) is not responding any more.... And I think this is a issue which is related to Galaxy S2 and Galaxy Note's eMMC bug. Because I had upgraded the firmware to STOCK ICS 4.0.3 (I9100XWLPG) which is available here. And i had flashed with chainfire's rooted kernel CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5.zip which can be downloaded from here. After using this firmware for a couple of months, recently i came through the eMMC bug news in Galaxy S2 And Galaxy Note. After that yesterday I downloaded chainfire GotBrickBug Application and found my device's firmware to be vulnerable to this bug. Then left my phone on the table and one hour later when i came back i found my phone dead. Phone was not responding and I tried Charging but it didn't respond...I pulled the battery but the condition didn't change. I think eMMC bug is responsible for the hardbrick of my device. But my question is that I didn't wipe or format my device so how the MMC_CAP_ERASE could occur?? I have sent my phone to the service center...
Click to expand...
Click to collapse
Simple - you've hardbricked for some reason unrelated to the eMMC bug.
The only I9100 kernel I'm aware of to ever get released that triggered the bug was Siyah 3.1rc6 - all other known kernels for I9100 are safe. (You would know this if you'd bothered to read the first post of Chainfire's "got brickbug" thread along with the posts linked to from it.)
You just had very bad luck. Your problem had probably nothing to do with the brickbug. Be happy, you had warranty left so don't worry.
Entropy512 said:
Simple - you've hardbricked for some reason unrelated to the eMMC bug.
The only I9100 kernel I'm aware of to ever get released that triggered the bug was Siyah 3.1rc6 - all other known kernels for I9100 are safe. (You would know this if you'd bothered to read the first post of Chainfire's "got brickbug" thread along with the posts linked to from it.)
Click to expand...
Click to collapse
yah bro i know about that. Siyah 3.1rc6 is the only buggy kernel for galaxy s2 (i9100). So my what can be the cause for that sudden hard brick?? And another question is that i had rooted my phone and flashed a number of times and i had a unofficial kernel as a result the triangle was showing before it hard bricked and i didn't reset the count number. So can after the hard brick will the service center people able to find info about rooting? As we know that rooting the phone will void the warranty.
krnrdstrm said:
You just had very bad luck. Your problem had probably nothing to do with the brickbug. Be happy, you had warranty left so don't worry.
Click to expand...
Click to collapse
Yah bro really i had a bad luck . It was my favorite phone. But my phone was rooted and also the triangle was present so I am very much tensed about that.
Maybe, maybe not. Impossible for anyone on here to say. Cross your fingers that they don't & you get lucky/get it repaired under warranty.
istipb said:
So can after the hard brick will the service center people able to find info about rooting? As we know that rooting the phone will void the warranty.
Click to expand...
Click to collapse
istipb said:
Yah bro really i had a bad luck . It was my favorite phone. But my phone was rooted and also the triangle was present so I am very much tensed about that.
Click to expand...
Click to collapse
just have ur finger's crossed for now dude and pray god that the service center people will overlook the issue and get ur phone rectified for u
hey bro does service center guys replaced your phone or solve ypur problem ??
i too have same problem
EMMC Bug
I used ROM Manager and it caused my mobile dead.........:<
it was out of warranty, I took my phone to repairer for JTAG but next day he returned my cell and said it has emmc bug ... what does it mean? and any solution plz Help .....................
It could mean he has taken your motherboard and replaced it with one that was dead.
Thanks fOr rePly........
But i've checked my motherboard is not replaced... is there any other possibility???
Or it is completeley useless?
---------- Post added at 02:53 PM ---------- Previous post was at 02:45 PM ----------
theunderling said:
It could mean he has taken your motherboard and replaced it with one that was dead.
Click to expand...
Click to collapse
ThanKx fOr reply...
But i dont think so he changed my board because i took my phone to another repairer he didn't told me that ur motherboard is replaced it seems like new...
... Plz Help ... Is JTAG is problem solving for all dead mobiles like s2?
If you need help you should be posting your exact model and what firmware you were on and what exactly happened!.
Ive had problems with rom manager once but easy to fix.
To OP: Next time, try using a jig for resetting your flash counter, so in case of problem you won't be
liable for voiding your guarantee with custom rom flashing, if you are able to reflash a stock rom before
sending it back to customer service.
It is 2$ and worth it (as it can also fix a few lesser bricking problems)
I flashed syiah 4.1.5 over my stock 4.0.4 everything is ok so far,i want to install the RR remix rom based 4.0.4 ,is safe? or to make a downgrade before to 4.0.3 and then to flash the RR?
Since you're running Siyah kernel, you're safe.
Sent from my GT-I9100
thank you
everst1 said:
I flashed syiah 4.1.5 over my stock 4.0.4 everything is ok so far,i want to install the RR remix rom based 4.0.4 ,is safe? or to make a downgrade before to 4.0.3 and then to flash the RR?
Click to expand...
Click to collapse
Just so you know
The developer of the rr rom includes a "safe" kernel with his rom.So although you will be on 4.0.4,his kernel will be automatically installed when you flash his rom.
Related
Hey Guys,
I switched from the Iphone to Android, I just got the Galaxy s2 and I want to root it. I have been reading of the different ways to root the phone, based on what I have seen so far the GingerBreak seems to be the easiest way to do it. So I am here in the forum, my first post is requesting a confirmation from you guys, which is the easiest way for an idiot like me to root my galaxy s2 without bricking it ?
Thanks
RedCell X
There is guide here in other post.
Basically you have to flash custom kernel, reboot and flash stock kernel back.
All using Odin.
Be careful - each custom kernel flashing will be visible. There is counter that shows how many custom kernels you flashed.
I stick with stock rom this time and avoid rooting.
This counter can be reset according to this forum. It's your decision.
Sent from my GT-I9100 using XDA Premium App
Definitive SGS2 Rooting Guide for now .
http://forum.xda-developers.com/showthread.php?t=1056334
Do you need root now .
jje
Gingerbreak only worked on the pre-production SGS2 models, it no longer works on the retail versions that are shipping now.
If you need root then use the link provided above, it works like a charm and you can always reflash an official kernel once you have root (and this is probably recommended if you also update your firmware to the lasted version).
The SGS1 usb jigs do work with the SGS2 and have the added bonus of resetting the custom firmware counter which may be handy if you ever need to return your phone under warranty, I got mine off of ebay yesterday and it works a treat.
rdy2go said:
Be careful - each custom kernel flashing will be visible. There is counter that shows how many custom kernels you flashed.
I stick with stock rom this time and avoid rooting.
This counter can be reset according to this forum. It's your decision.
Click to expand...
Click to collapse
Why is resetting the counter important? For warranty purposes?
Rootinf galaxy s2 continued
Hey Guys,
Thanks for the response, I don't think i will be rooting my phone being honest I am afraid to do it. I will stick with the stock rom that came from it. I spent $850 for the phone I dont want to brick it.
Thanks to everyone that responded.
Redcellx
redcellx said:
Hey Guys,
Thanks for the response, I don't think i will be rooting my phone being honest I am afraid to do it. I will stick with the stock rom that came from it. I spent $850 for the phone I dont want to brick it.
Thanks to everyone that responded.
Redcellx
Click to expand...
Click to collapse
Dont worry about bricking your phone, even if something goes wrong with the flashing process you should always be able to get back into download mode so you can reflash either by using the keypress method or if that fails the usb jig should wake your phone up.
Then you can either use ODIN or even the Kies Recovery method to get a working ROM installed.
rwc3b said:
Why is resetting the counter important? For warranty purposes?
Click to expand...
Click to collapse
Yeah, while no has (yet) reported that they have had a warranty request rejected because of custom rom usage, its nice to know how to reset the counter to ensure any warranty requests go smoothly.
MrYiff said:
Yeah, while no has (yet) reported that they have had a warranty request rejected because of custom rom usage, its nice to know how to reset the counter to ensure any warranty requests go smoothly.
Click to expand...
Click to collapse
Take a stroll over to SGS 1 forum i replied to a post where service wanted $400 as non stock rom and their have been a fair few reported and Samsung sent out a post to SS do not repair rooted phones under warranty .
jje
Some one should post a video on YouTube a how to
JJEgan said:
Take a stroll over to SGS 1 forum i replied to a post where service wanted $400 as non stock rom and their have been a fair few reported and Samsung sent out a post to SS do not repair rooted phones under warranty .
jje
Click to expand...
Click to collapse
Ahh, that sucks then, I've never owned an SGS1 before so never looked in the SGS forum, if they have actively rejected modded phones in the past then it makes the usb jigs a very worthwhile investment then!
I have passed the last 3 hours searching about this since I saw it on another post.
What is the brick bug??
According to my readings, this is related to ICS leaks flashing for sgs2 and galaxy note on roms and based kernels...and u can hardbrick ur phone when u do wipes / resets erasing partitions on the emmc.. kind of..
Masters like Chainfire and many others (my bad i forgot their names but they know who they are).. have provided explanations and links to this info. 1+ to KennyLegend for posting the link I read in the other thread.
So, after checking my s2 with Chainfire's app. I got the damn 0x19 chip which means I have the bad one but reading and reading it seems that for kernels based on the 4update source its kinda safe... But as I am not a developer and just and user Im still confused a lil bit about this...
And I know there is info missing for the readers on this thread... Im sorry really .. Im still confused and Im opening this thread with the intention of understand better the issue, so that I beg to the real masters that please clear all our doubts..
I.e. : what are the safe kernels based on the safest update?
And are we safe running xxlpxxx stock rom??
What flashing junkies need to know??
Is it possible to brick our device now since this bug was found on may??
And many many more doubts that will come up...
Thanks
Sent from my GT-I9100 using XDA
you mean the one whereby when you are using a kernel with the brick bug in it and you clear data, cache, you will brick your phone in the process right?
Hi
I've got the same (maybe) Problem here
Also i have that
VYLOOM
Revision 0x19
eMMC Chip on my GT-I9100
I have the free German Version (Country Code DBT)
And currently using the Polish XXLPW ROM (Kies Release) flashed with Odin over the official XWLP7 also from Kies. Using Chainfires CF-Root for LPW.
Reading this thread in the Epic 4G Touch General Section
it seems that some of the Devs Kernel don't have the 'workaround' that samsung has in some of his kernels.
Maybe of my english or because i haven't the time to read all the 47 Page so far, i do not clearly understand if this bug is only happens if you use factory wipe from the CWM or could it also happens if you use the Option from the normal ROM Settings under ICS.
I will read on and seeking in other sites for more information.
regards
Christopher
We do not have to worry if we are using the international sgs2 (i9100). I think it was for the korean version of sgs2. There are people who hard bricked their device using a custom kernel where they wiped and the phone never came back (it's in the general section). It's really not the fault of the kernel developer but by samsung. So no need to worry guys.
Sent from my GT-I9100 using xda premium
Lonzo_SGS2_506 said:
I have passed the last 3 hours searching about this since I saw it on another post.
What is the brick bug??
According to my readings, this is related to ICS leaks flashing for sgs2 and galaxy note on roms and based kernels...and u can hardbrick ur phone when u do wipes / resets erasing partitions on the emmc.. kind of..
Masters like Chainfire and many others (my bad i forgot their names but they know who they are).. have provided explanations and links to this info. 1+ to KennyLegend for posting the link I read in the other thread.
So, after checking my s2 with Chainfire's app. I got the damn 0x19 chip which means I have the bad one but reading and reading it seems that for kernels based on the 4update source its kinda safe... But as I am not a developer and just and user Im still confused a lil bit about this...
And I know there is info missing for the readers on this thread... Im sorry really .. Im still confused and Im opening this thread with the intention of understand better the issue, so that I beg to the real masters that please clear all our doubts..
I.e. : what are the safe kernels based on the safest update?
And are we safe running xxlpxxx stock rom??
What flashing junkies need to know??
Is it possible to brick our device now since this bug was found on may??
And many many more doubts that will come up...
Thanks
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
can you please give a link to the chainfire app.. so we all can check.
martintspedersen said:
can you please give a link to the chainfire app.. so we all can check.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=27014974
Sent from my GT-I9100 using Tapatalk 2
BTW we don't have to worry about it now but what if any new samsung official rom have that bug?
Sent from my GT-I9100 using Tapatalk 2
Relax. There's nothing to worry about. If this happens to you (very unlikely), it will happen suddenly, and there will be nothing you can do to stop it happening. If the 0.00000000000000000000000000000000000001% chance of it happening bothers you that much & you want to be absolutely sure that it doesn't, leave your phone on stock & don't mess with it.
This is probably the least responsible piece of information/firmware/app I've seen released in the 8 mths I've been coming here :-|
---------- Post added at 04:36 PM ---------- Previous post was at 04:35 PM ----------
Samsung will be paying to fix/replace your phone.
sahibunlimited said:
BTW we don't have to worry about it now but what if any new samsung official rom have that bug?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
its brick bug
sahibunlimited said:
BTW we don't have to worry about it now but what if any new samsung official rom have that bug?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
check the attached images i m running 4.0.3 ics Aut Switzerland
tell me its brick bug i many tym wipe/ factory reset with cwm nothing happen but chainfire app say brick bug exist
The brick bug is only present in ICS 4.0.4 firmware with Samsung kernel (or stock based kernel such as CF-Root) and it's only an issue if you wipe using CWM.
If your phone is stock and you have stock recovery then you're fine. You can delete/wipe cache, factory reset as much as you like. No harm will be done.
In short: 4.0.4 firmware + CWM = Brick.
Unless you flash a 'safe' kernel such as Siyah or NEAK or Speed mod
Brick bug x19 vyloom on my sgs2
hi im new to this forum
i have vyloom x19 emmc bug on my sgs2 so just wanted to ask can i change the firmware to other region or neat firmware over that via odin is it possible?
Hello Friends,
I am in desperate need of your help.
I am a moderate user and I know how to stuffs about Rooting and flashing custom ROMs.
Today I tried to flash CM9 stable ROM for International Galaxy S2 I9100. I did it using temporary CWM.zip file and everything went just fine till the installation of ROM. But when I clicked Wipe Data, suddenly phone went off and now it doesn't start.
I tried everything, tried to enter into Download mode and Recovery mode but all was in vain.
Please help me what should I do now? And is my phone ever going to come back to life?
Additional Info
satish0101 said:
Hello Friends,
I am in desperate need of your help.
I am a moderate user and I know how to stuffs about Rooting and flashing custom ROMs.
Today I tried to flash CM9 stable ROM for International Galaxy S2 I9100. I did it using temporary CWM.zip file and everything went just fine till the installation of ROM. But when I clicked Wipe Data, suddenly phone went off and now it doesn't start.
I tried everything, tried to enter into Download mode and Recovery mode but all was in vain.
Please help me what should I do now? And is my phone ever going to come back to life?
Click to expand...
Click to collapse
To add into this.
I was using,
PDA: I9100XWLPT
CSC: I9100NEELP4
Version: 4.0.4
Do you know what kernal you had at the time, for the phone to go off during a wipe sounds like the brick bug but I didn't think it was present in LPT. Can other members clarify please. Does your phone charge when plugged into charger?
Sent from my GT-I9100 using xda premium
satish0101 said:
To add into this.
I was using,
PDA: I9100XWLPT
CSC: I9100NEELP4
Version: 4.0.4
Click to expand...
Click to collapse
I'm sorry but that's your fault.
It's being said 1 million times already, that wiping your data in CWM while running stock 4.0.4 ROM with a stock kernel will BRICK your phone.
Your inability to read might have left your phone bricked.
Read through the forum next time, ask questions if you don't understand anything and I can assure you will be luckier next time.
Swyped from my Samsung Galaxy SII
Yes there are many threads in this section and on xda portal warning you about the brick bug...
Almost all 4.0.4 have a brick bug... moreover it is caused when we do a data wipe. I believe you have bricked your device... sorry for that
Sent from my GT-I9100 using Tapatalk 2
sachidanand444 said:
Yes there are many threads in this section and on xda portal warning you about the brick bug...
Almost all 4.0.4 have a brick bug... moreover it is caused when we do a data wipe. I believe you have bricked your device... sorry for that
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Hi, I thought the brick bug was present in only the leaked firmwares and those highlighted on samfirmware eg the Russian release LQ6 I think.
Sent from my GT-I9100 using xda premium
HANDSY said:
Hi, I thought the brick bug was present in only the leaked firmwares and those highlighted on samfirmware eg the Russian release LQ6 I think.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
that's why I blamed you for this. You did not read or ask before wiping but was only guessing.
This is a sticky thread under General section warning everyone about the buck bug. Here: http://forum.xda-developers.com/showthread.php?t=1756242
I and many others have also warned people about this bug but the unfortunate thing is that most of ask these kind of questions after the problem has occurred.
Swyped from my Samsung Galaxy SII
Jokesy said:
that's why I blamed you for this. You did not read or ask before wiping but was only guessing.
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
Er I'm not the OP
Sent from my GT-I9100 using xda premium
HANDSY said:
Hi, I thought the brick bug was present in only the leaked firmwares and those highlighted on samfirmware eg the Russian release LQ6 I think.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
As far as I know all 4.0.4 ROMS have MMC_CAP_ERASE enabled, so in case of having bad chip and using wipe under temporary CWM floating around you will brick your phone. Although seems the problem is only in touch version of CWM. More detailed information can be found in 1st guide in my signature where Phil was talking with Entropy512.
Odoslané z GT-I9100 cez Tapatalk 2
Stileth said:
As far as I know all 4.0.4 ROMS have MMC_CAP_ERASE enabled, so in case of having bad chip and using wipe under temporary CWM floating around you will brick your phone. Although seems the problem is only in touch version of CWM. More detailed information can be found in 1st guide in my signature where Phil was talking with Entropy512.
Odoslané z GT-I9100 cez Tapatalk 2
Click to expand...
Click to collapse
Will do thanks
Sent from my GT-I9100 using xda premium
^^Not only with touch CWM but also with "temporary CWM" wjich is what you were using.
Take it to a service center as your phone now needs a motherboard replacement..and I hope you still have warranty..!
Sent from my GT-I9100 using Tapatalk 2
satish0101 said:
Hello Friends,
I am in desperate need of your help.
I am a moderate user and I know how to stuffs about Rooting and flashing custom ROMs.
Today I tried to flash CM9 stable ROM for International Galaxy S2 I9100. I did it using temporary CWM.zip file and everything went just fine till the installation of ROM. But when I clicked Wipe Data, suddenly phone went off and now it doesn't start.
I tried everything, tried to enter into Download mode and Recovery mode but all was in vain.
Please help me what should I do now? And is my phone ever going to come back to life?
Click to expand...
Click to collapse
Sorry dude
You might have to send your phone to device center for repairs but if you are out of warranty or wants to try to Fix things yourself, then the advise/instructions below is for you:
-boot your phone with usb jig, if you can get to download mode, then proceed to next step
-Visit this thread: http://forum.xda-developers.com/showthread.php?t=1841099
Good luck
Swyped from my Samsung Galaxy SII
Is the brick bug present in ICS? I want to upgrade from Gingerbread to ICS 4.0.3, will I be safe when flashing then?
UrbanDesigns said:
Is the brick bug present in ICS? I want to upgrade from Gingerbread to ICS 4.0.3, will I be safe when flashing then?
Click to expand...
Click to collapse
Brick bug is only present on ICS 4.0.4.
ICS 4.0.3 is safe
Swyped from my Samsung Galaxy SII
Thanks
Hi guys,
Thanks for all your replies.
I already figured it out that I have bricked my phone. But I was under impression that Data wipe with CM9 ROMs is not dangerous. At the time of failure I had already installed CM9.
Guess now I'll have to send the phone to Service center.
One thing I want to ask, "If the phone is hard bricked, is there any chance of them knowing that I had installed a custom ROM?"
If they can't then it might help me since my phone is still under 1 year manufacturer warranty.
Please reply and Thank you for your replies. The latest adventure of mine turned out to be painful one!!
satish0101 said:
Hi guys,
Thanks for all your replies.
I already figured it out that I have bricked my phone. But I was under impression that Data wipe with CM9 ROMs is not dangerous. At the time of failure I had already installed CM9.
Guess now I'll have to send the phone to Service center.
One thing I want to ask, "If the phone is hard bricked, is there any chance of them knowing that I had installed a custom ROM?"
If they can't then it might help me since my phone is still under 1 year manufacturer warranty.
Please reply and Thank you for your replies. The latest adventure of mine turned out to be painful one!!
Click to expand...
Click to collapse
I don't think so. since you can't boot into either recovery or download mode.
Even if you have an increased binary counter, it will be cleared once your device is forced with a usb jig to boot into download mode.
Swyped from my Samsung Galaxy SII
Jokesy said:
I don't think so. since you can't boot into either recovery or download mode.
Even if you have an increased binary counter, it will be cleared once your device is forced with a usb jig to boot into download mode.
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
Then USB Jig is my last hope and if that doesn't work then I have to send the phone to the service center.
So if you can't enter into download or recovery mode there is no way to find out if i have used any custom ROM or rooted the phone?
Correct me if I'm wrong.
And thank you for your reply. In this desperation every reply from community member is like gold.
satish0101 said:
Then USB Jig is my last hope and if that doesn't work then I have to send the phone to the service center.
So if you can't enter into download or recovery mode there is no way to find out if i have used any custom ROM or rooted the phone?
Correct me if I'm wrong.
And thank you for your reply. In this desperation every reply from community member is like gold.
Click to expand...
Click to collapse
Absolutely no way. You are right
Swyped from my Samsung Galaxy SII
Jokesy said:
Absolutely no way. You are right
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
Thanks buddy.
I believe I have to send the phone to Samsung Service center then!!
Jokesy said:
Absolutely no way. You are right
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
Hello guys,
After receiving positive feedback from members I have finally submitted my phone to service center.
Please pray and hope they don't find out about my little adventure!!
Hello XDA,
I was trying to flash CM9 on my Samsung Galaxy S2, was running Stock ICS XWLP7, successfully flashed it, proceeded to CWM and Wipe Data/Factory Reset unaware of the eMMC Brick Bug, went away during the wipe process, as I came back, I saw that the phone was completely bricked. Download/Recovery Modes don't work, Odin doesn't recognize anything, can't charge phone, the phone is cold and dead. Jig or JTAG don't work either.
btw. I can't get it replaced.
1. Is this the infamous superbrick?
2.If yes, what can I do about it? If no, what is it?
Yes, looks like you've encountered the infamous superbrick
The only way to revive a superbricked phone is to send it to Samsung service center.
Sent from my GT-I9100 using Tapatalk 2
Nexcore said:
Hello XDA,
I was trying to flash CM9 on my Samsung Galaxy S2, was running Stock ICS XWLP7, successfully flashed it, proceeded to CWM and Wipe Data/Factory Reset unaware of the eMMC Brick Bug, went away during the wipe process, as I came back, I saw that the phone was completely bricked. Download/Recovery Modes don't work, Odin doesn't recognize anything, can't charge phone, the phone is cold and dead. Jig or JTAG don't work either.
btw. I can't get it replaced.
1. Is this the infamous superbrick?
2.If yes, what can I do about it? If no, what is it?
Click to expand...
Click to collapse
you were on 4.0.4?
jtag service didn't brought it back to life.
hmmmm...man................cold stuff
gastonw said:
you were on 4.0.4?
jtag service didn't brought it back to life.
hmmmm...man................cold stuff
Click to expand...
Click to collapse
Yes I was, the version mentioned is wrong.
Nexcore said:
Yes I was, the version mentioned is wrong.
Click to expand...
Click to collapse
man, look into hard brick threads, maybe there's a way out.
gastonw said:
man, look into hard brick threads, maybe there's a way out.
Click to expand...
Click to collapse
What ? If it superbricked only help is mb changing
Happy new year
Paulius
Paulius7 said:
What ? If it superbricked only help is mb changing
Happy new year
Paulius
Click to expand...
Click to collapse
i'm trying to give this guy some hope.....it's saturday man.
gastonw said:
i'm trying to give this guy some hope.....it's saturday man.
Click to expand...
Click to collapse
I know dude but there only fix changing mb...
Happy new year
Paulius
Actually it's not my device, it belongs to a friend of mine, he gave it to me to fix it yet I couldn't do it
He can't get it replaced because his warranty is over.
Do your friend had warranty ?
Happy new year
Paulius
Nexcore said:
Actually it's not my device, it belongs to a friend of mine, he gave it to me to fix it yet I couldn't do it
He can't get it replaced because his warranty is over.
Click to expand...
Click to collapse
Then he needs to pay for a motherboard replacement, simple as that.
Also, by the way, why did you create this thread when we already have plenty of this exact topic? You could have diagnosed this easily by looking at one or more of the threads we already have without creating yet another one and waiting for same answers.
Is it insured under home insurance or bank/credit card? Otherwise it's buy a new phone or send back to Samsung for repair and pay. Good luck.
Sent from my GT-I9100 using xda premium
TheATHEiST said:
Then he needs to pay for a motherboard replacement, simple as that.
Also, by the way, why did you create this thread when we already have plenty of this exact topic? You could have diagnosed this easily by looking at one or more of the threads we already have without creating yet another one and waiting for same answers.
Click to expand...
Click to collapse
Because all the fixes were like, flash X from Odin, but the phone doesn't get recognized by Odin.
The phone was bought from Germany, Samsung Turkey refuses to replace it, it must be sent to Germany for replacement.(if possible)
Nexcore said:
Because all the fixes were like, flash X from Odin, but the phone doesn't get recognized by Odin.
The phone was bought from Germany, Samsung Turkey refuses to replace it, it must be sent to Germany for replacement.(if possible)
Click to expand...
Click to collapse
And in those cases the devices were never actually "bricked" at all, those were just n00bs who couldn't fix their system boot problem and like to describe their device as "soft-bricked". In your case your device is actually "bricked" what the n00bs call "hard-bricked" when in reality their is only "bricked". If you can flash via odin or recovery your device is not bricked.
In your case you wiped your device with a buggy kernel (which has been discussed at length as I said) and only option is mobo replacement.
i updated my galaxy S2 i9100 to official ics rom than rooted it via odin , than flashed a custom kernel and successfully entered to the clockwork mod then wiped data and my screen went black and my phone is dead :crying: .. . .
i tried to go to download mode and recovery but no response from the device the computer cant seems find the device while connected to the PC .. no response from the device when connected to the charger
is there i can do to turn this piece of plastic to a phone again except changing the mother board . .
shohag_prince said:
i updated my galaxy S2 i9100 to official ics rom than rooted it via odin , than flashed a custom kernel and successfully entered to the clockwork mod then wiped data and my screen went black and my phone is dead :crying: .. . .
i tried to go to download mode and recovery but no response from the device the computer cant seems find the device while connected to the PC .. no response from the device when connected to the charger
is there i can do to turn this piece of plastic to a phone again except changing the mother board . .
Click to expand...
Click to collapse
ICS 4.0.4?If so,then it's EMMC brick bug.
GamingDj said:
ICS 4.0.4?If so,then it's EMMC brick bug.
Click to expand...
Click to collapse
can it be fixed bro??? @GamingDj
I hope for your sake this is not the case.....but it sounds like another case of ics brickbug......
Can you tell us which kernel you flashed (provide a link if you can) and what (odin) method you used to root.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
keithross39 said:
I hope for your sake this is not the case.....but it sounds like another case of ics brickbug......
Can you tell us which kernel you flashed (provide a link if you can) and what (odin) method you used to root.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
i did this to my device almost 2 week ago and upgraded my HDD so unfortunately i don't have the back up and can't remember the kernel version or which file i used to root it
maybe luck is not on my side after all ... .
Ok....to recap......
Can you enter recovery mode?
Can you enter download mode?
Do you get the battery icon on the screen when you plug the charger in?
Does the area below the main camera get warm when you attempt to charge?
If your answers are 'no', 'no', 'no' and yes.....then more than likely it IS brickbug.......
Which brings me to my next question.......
Ignoring the fact that you rooted (this is now undetectable) are you under warranty?
Samsung are aware that *some* of their phones will fail if a wipe or kies update is performed on them. So as long as you tell them........
'I tried to update with kies and then the phone switched off and wouldn't switch on again'
then they *should* repair the phone under warranty.
Just DON'T mention XDA or rooting or odin or brickbug......or anything else like that and you should be ok.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Had the same problem with my old s2.The phone doesn't boot into recovery or download mode if the battery is dead,Make sure the battery is alright and try again.I had to replace my battery.
If all is well,then its EMMC brick.
Service centre.
keithross39 said:
Ok....to recap......
Can you enter recovery mode?
Can you enter download mode?
Do you get the battery icon on the screen when you plug the charger in?
Does the area below the main camera get warm when you attempt to charge?
If your answers are 'no', 'no', 'no' and yes.....then more than likely it IS brickbug.......
Which brings me to my next question.......
Ignoring the fact that you rooted (this is now undetectable) are you under warranty?
Samsung are aware that *some* of their phones will fail if a wipe or kies update is performed on them. So as long as you tell them........
'I tried to update with kies and then the phone switched off and wouldn't switch on again'
then they *should* repair the phone under warranty.
Just DON'T mention XDA or rooting or odin or brickbug......or anything else like that and you should be ok.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
the answer is "no","no","no' and "yes" and unfortunately i am out of warranty so should i assume the motherboard is permanently
dead ?? @keithross39 and tnx for answering
vish91 said:
Had the same problem with my old s2.The phone doesn't boot into recovery or download mode if the battery is dead,Make sure the battery is alright and try again.I had to replace my battery.
If all is well,then its EMMC brick.
Click to expand...
Click to collapse
after you replaced ur battery ware u able to go to download mode despite of the EMMC brick ether way i m going to change the battery and see if it works. . . thnx for replying ... @vish91
MistahBungle said:
Service centre.
Click to expand...
Click to collapse
unfortunately may be yes . . . :crying:
shohag_prince said:
the answer is "no","no","no' and "yes" and unfortunately i am out of warranty so should i assume the motherboard is permanently
dead ?? @keithross39 and tnx for answering
Click to expand...
Click to collapse
If it is the emmc brickbug (and it's looking like it is) not even samsung can bring that main board back to life...sorry mate. ..
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Painful mistake. Hate reading threads like this.
keithross39 said:
if it is the emmc brickbug (and it's looking like it is) not even samsung can bring that main board back to life...sorry mate. ..
sent from my rooted, de bloated, stock jb powered s2 via philz kernel and xda developers app
Click to expand...
Click to collapse
. .. . .
andrewwright said:
Painful mistake. Hate reading threads like this.
Click to expand...
Click to collapse
Painful indeed . . .. . .. .
was there anything i could have done to prevent this .. . ????
From what I can tell 4.0.4 was the problem. Soon as you factory reset the phone dies. Sam knows about this that makes it even worst. Sorry to hear about your dead s2
keithross39 said:
If it is the emmc brickbug (and it's looking like it is) not even samsung can bring that main board back to life...sorry mate. ..
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
was there any thing i could have done to prevent this bro .. . . .????
Stay well away from 4.0.4 firmware and factory reset. Even with a custom kernel I think is a bad move to stay on it.
andrewwright said:
From what I can tell 4.0.4 was the problem. Soon as you factory reset the phone dies. Sam knows about this that makes it even worst. Sorry to hear about your dead s2
Click to expand...
Click to collapse
at least its good to know that its not my fault . . .. tnx bro. . .:good:
Some will say its your fault for not reading. Not me this is a dirty samsung problem and they should of recalled ALL the faulty handset's as I think they are faulty and pull the 4.0.4 from every were. Can I ask were did you get that firmware from?