yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] highlander317:
I recently udated to stock 4.0.4 and then re rooted, was going to try the latest neutrino rom. Is it safe to go ahead, just checked the emmc brick bug app and it said sane chip. Should I flash to siyah kernal first?

Appreciate any help

Cheers
[Galaxy S II General] ariarman:
you can restore you'r backup or flash another rom throw odin .

i use both way and nothing happen for me.
[Galaxy S II General] antunes20:
you can flash XWLPO via odin without change kernel cause is NO WIPE, but for more security flash first siyah by odin and then flash XWLPO by odin.
[Galaxy S II General] mr_zuff:
thanks mate!! btw, i've just another quest :)

i dwnloaded the siyah kernel8galaxy s2- v4.0.1) from the official page of siyah. now can I just flash the .tar file via Odin using the PDA button? or have I to do some other things before?

sorry, it's my first kernel's flash of all time :D
[Galaxy S II General] allocen:
So in conclusion, you can edit the tar file to delete the kernel and put instead of it a safe kernel like siyah or galaxian? :eek:. So in that way you'll flash more safely the ics 4.0.4 firmware? :eek:
[Galaxy S II General] antunes20:
just flash the .tar file via Odin using the PDA button

---------- Post added at 07:52 PM ---------- Previous post was at 07:46 PM ----------

you can flash 4.0.4 firm without any problem. After flash it you shouldnt do wipes with stock kernel,

in other words:

1º flash last firm 4.0.4( XWLPT) via odin.

2º flash siyah kernel.

now you can do wipes.
[Galaxy S II General] mr_zuff:
Thank you!! Now that i know what to do, it'll be much easyer to try custom roms, or just to not have the emmc bug :D

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II General] antunes20:
when you have siyah kernel you are safe, so you can flash via cwm a custom rom or do wipes
[Galaxy S II General] SverreMV:
What if I want to flash LQ6 (or any of the unsafe ones), would this be a correct way, or is there no way to be safe?

Flash LQ6 via ODIN without rebboting the phone

Flash Syiah 4.x via ODIN
[Galaxy S II General] lasic.2000:
Ok so I'm confiused.

So You say that Siyah 4.1b4 ( my favourite kernel ;p ) is safe.But i downloaded this app eMMC Brickbug Check.It show that I have brick bug.

So guys can you tell me Can I flash Custom roms or mods with wipe,or am I safe ??

Thanks
[Galaxy S II General] egps2:
Hi this is completely normal! As long as you have a safe kernel like Siyah or SM it won't be an issue. It just means you should stay away from kernels that have cap_erase enabled as you might be at risk. So you should be able to wipe but only on a safe kernel! Quick addition: the app tells you that your chip is at risk, not if your kernel is safe. Hope that makes sense :)
[Galaxy S II General] Dragonalvaro:
About 2 gb :S
[Galaxy S II General] lasic.2000:
Thanks man :) Now I understand.
[Galaxy S II General] NIK3SH:
This post is so horrible.

I also upgraded mine to 4.0.4 with official kernel but having only one issue of brightness controller.

I always kept automatic and after some hours it gone to any custom level.

Little issue I know.

But will sure read forums and posts before using any OTA next time.

Thanx BTW.

---------- Post added at 10:07 PM ---------- Previous post was at 09:49 PM ----------

Hello all,

Mine device running,

Baseband- I9100XXLQ6

Kernal- 3.0.15-I9100XWLPT-CL941023

Everything is official in my phone no root, no custom kernel installed.

Will my device also be bricked if I format it ?
[Galaxy S II General] adderxp:
im on ics 4.0.4 firmware and have just flashed speedmod kernal as to avoid the bricking chip

ive also downloaded the emmc check app and it tells me i still have the bricking chip does that mean it hasnt worked

am i safe now or not any advise please :fingers-crossed:
[Galaxy S II General] Stileth:
You can't change your chip. You can only change your kernel for safe one which will prevent executing the bricking CAP_ERASE command.
[Galaxy S II General] Mittaa:
I too have ICS 4.0.4 firmware and have flashed speedmod kernel as to avoid eMMC brick (have insane chip).

Tried to make a NanDroid backup using Rom Manager ... but it didn't work.

Also tried to make a backup manually ... but manual boot into recovery only lead me to standard Samsung Recovery mode "Downloading ... do not detach target".

I really would like to make a NanDroid backup ... any idea?
[Galaxy S II General] Stileth:
ROM manager is known to have issues with SGS2. You can make it by using temporary CWM. For one and how to use it look in 1st guide in my signature.
[Galaxy S II General] Mittaa:
Managed to make backup from CWM ... and Rom Manager will be dumped at least for now :)

Thanks
[Galaxy S II General] Berecki2:
Myn Got Bricked to.

My Galaxy S2 got bricked to. I connect it to the computer, it recognizes it and throws it out in 1-2 mins. I have to get the battery out and put it back so I can connect it to the PC. And after I connect still the same, 1-2 mins and its thrown out.
[Galaxy S II General] egps2:
Hi your phone may very well be bricked and I am sorry to hear that but please check your usb cable as well. I doubt this is the root of your problem but there is a small chance that you may only be soft bricked and coincidentally have a faulty usb cable. I had very similar symptoms (not on this phone) and it turned out that my usb cable was damaged. Like I said, I doubt this is relevant but I definitely hope so for your case!
[Galaxy S II General] NIK3SH:
Have u try to change/wipe anything or used clock work recovery mode ?

If not then issue will be minor.

But if yes then it must be bricked and you will need to leave default partition of 2 GB due to corruption and need to make another one using custom pit file.
[Galaxy S II General] maijinace:
i also bricked my phone :( i got a massage to do an update and i want to make back up with cwm before i do a update. i was on 4.0.4. while i was making backup it bricked :(

damn what did i do!!! i should read more here before i do something :(

i will bring it to samsung store to restore it .... do you think they can find out that the phone is rooted? i dont have any cfw and i have the origin stock ...
[Galaxy S II General] danividalg:
Please Urgent Help! :(

Hi,

I have got my Galaxy S2 Hard Bricked but I DO NOT MAKE ANY WIPE :eek::crying:

My S2 have:

- SiyahKernel S2-v4.1beta6

- Dual Boot activated

- Rom 1: Stock XWLPG with Android 4.0.3 with JKay framework and some gestures defined (script loaded afterboot with script manager) (daily)

- Rom 2: ParanoidAndroid JB 1.97 with Android 4.1.1 (only for test, only loaded 3-4 times)

How hard brick happened:

- Rom 1 loaded, low of battery (last time I see it was 18%)

- One hour later (aprox) I try to make a call with my S2 and see that is off and do not respond.

- I suppose that it is battery out.

- I try to charge it with a portable usb battery (as many times I do it).

- Some minutes later it does not appear the battery charging icon.

- Try to turn on the phone, it does not respond.

- Left charging for some more time on my pocket.

- Tried again but do not turn on.

- Tried to remove the battery and put it again. No turn on.

- Realized that the phone is hot (near camera) and portable battery is hot too.

- Disconected from the battery and left it on my pocket.

- One or two hours later reach my car and tried to charge the phone with a cigarette lighter USB charger.

- No turn on and no battery charging icon.

- Reach home and tried to charge with original wall charger.

- Tried to remove battery several times.

- Tried to enter dowload mode with USB jig (removing battery too)

- Sad and angry because of I think my phone is dead :crying: :mad:

Today I will take my S2 to service support, I suppose that they will repair my phone under warranty.

Now my ask for HELP:

- Please, could anyone tell me if it is possible to save, keep or copy my phone's Internal SD memmory data?

There are some important data that I do not want to loose and I'm afraid that if they replace the motherboard to repair the phone then internal SD memmory is replaced too because it's integrated in the motherboard.

- Could anyone confirm if the internal SD memmory is integrated in the motherboard?

- Could anyone confirm if there is any way to backup the internal SD data somehow?

Thanks in advance and best regards :)
[Galaxy S II General] snas281:
omg i saw that to late... my phone is brick

i buy from amazon that Repair Reset jig Stecker für Samsung Galaxy S NEU S2 i9100 i9100G N7000 auch für ICS 4.0.3 i hope it´s work
[Galaxy S II General] hakaz:
Could be hardbrick bug but maybe not ... have you tried changing the battery against another one?

What was your last action before charging from 18% upwards?

Were you ever on a 4.0.4 ROM?

When was your last wipe action?

AND YES hardbrick means inaccessible so if they have to replace the board your internal data are gone forever, sorry mate!
[Galaxy S II General] danividalg:
Hi,

Thanks for reply :)

Answers:

- I do not have another battery to try, but it's strange that battery could be broken

- Last time I see my phone alive I was reading an email, then push power button to lock the phone and then put it on my pocket. One hour later (aprox) I try to wake up my phone pushing home button but it does not wake up anymore :(

- I never have flashed a 4.0.4 rom, only a 4.1.1 rom in the secondary boot rom of the siyah dualboot

- I wiped secondary rom last Friday August 10 (I was on Siyah S2 v4.0.1), but problem was on Tuesday August 14 (with Siyah S2 v4.1.beta6). I have rebooted my phone several times from 10 to 14. Only thing is that I installed Siyah S2 v4.1.beta6 on Tuesday August 14. Could it be the problem?

Are you sure that my internal SD data are completely lost?

I have readed something like that eMMC is not hardware brockened, that it is neccesary to be wiped but it is neccesary some special samsung commands, so, could it be possible that my phone could be repaired without replacing the motherboard?

Thanks again and best regards.
[Galaxy S II General] hakaz:
Sorry again mate, but if your SGS2 has hardbricked this way it is not accessible by any means afaik (only JTAGging works in some other cases but not with hardbrick bug). I also read the info that your way of bricking is possible and well known. In Sammy's Service Center they will try to restore your board's functionality anyway before changing it but even if it's not that way hardbricked this thread is all about they will factory reset it normally (try to tell them about your data).
[Galaxy S II General] danividalg:
Ok, thanks for your answers :)

Best regards.
[Galaxy S II General] Entropy512:
There's a possibility you might have a hardbrick unrelated to eMMC damage. If you do, JTAG might be able to resurrect your device.

If it's eMMC damage - your internal eMMC is toast and contents are unrecoverable.
[Galaxy S II General] Kakamarsson:
Want to avoid the brick

Ok, i installed 4.0.4 (UK) but after that i´ve not done any wipes. And have the "WLPT" kernel and im not rooted.

The eMMC check said i have an "insane chip". What should i do then?

If i flash the SiyahKernel S2-v4.0.1 will i be safe of that bug?

What will i loose with that Kernel in terms of functionality comparing with what i have now. Touch sensibility? Battery duration? Or i will loose nothing at all?

The flash procedure is just this? Download the kernel, put my cellphone in download mode and use Odin to flash the kernel? Just that simple? No previous uninstallation or something like that?

Thank O.P for the warning. Thank all for any help.
[Galaxy S II General] mr_zuff:
hi! :) i had the same problem as you have, i've been answered, so now i THINK i can answer you! :)

_ yes, the siyah kernel 4.0.1 is bug free: no eemc cap erase, no risk for hard brick

_you will lose anything! at least, you will earn something! it's smoother and you have more functions(cpu,gpu,screen..)

_touch is changeble ;)

_battery is pretty the same, but you can set the phone in "high" power saving(underclock,undervolt)

_the procedure is the one you wrote up above ;) (use PDA button on ODIN!)

and finally,

_yeah, nothing else. just flash the kernel and enjoy the cwm recovery + the rooted phone! ;)

thanks button is just under this line! :D
[Galaxy S II General] Kakamarsson:
Thank you Mr. Zuff. Can´t find the "Thank you" button.Isn´t it just for the O.P to thank who replies his post?

One more question: you said "you will lose anything". Sorry for my bad english but did you mean "you will lose nothing!" or "you will lose everything!". ´I´m guessing number one...
[Galaxy S II General] mr_zuff:
oh god! my mistake! i'm italian and my mom is not english! :D lol

btw, you will lose nothing at all! all your apps and settings will remain the same;)
[Galaxy S II General] ohwarumbloss:
Victim :( A TruE StorY

Hardbricked after 3 days !

Here is what I did :

- Went to o2 Shop and bought a brand new shiny S2

- Went home and unpacked it

- Upgraded to stock 4.0.3 (Kies)

- Found out Samsung Stock sucked

- Downloaded latest MIUI from MIUI-Germany.de

- rooted and flashed Siyah Kernel

- Flashed MIUI 2.x (can´t remember)

- after 2 days I got a bit bored and

- on the 3rd day I decided to flash 4.0.4 from samfirmware.com (I9100XWLPI_I9100XXLPX_I9100DBTLP6_HOME.tar)

- after a very short Process in Odin I had a black S2

- NOTHING HAPPENED ANY MORE !!!!!

- After 3 years of Android Phones and hundreds of custom ROMS flashed

- I felt totally STUPID !!!!!

- I kept feeling this way

- I went to o2 again and told the Dude (nice guy) my story

- he exchanged the Phone without any trouble

- I still felt stupid but lucky now

- After I promised I never flash anything again (yesterday)

- right now I am on cMIUI

- Resume : I am a flash-a-holic and I really need a therapy

Greetings !

Oh and thanks to the OP for the warning, it should be shown up each time someone new enters the S2 Section ;)

(pushed the button of course)
[Galaxy S II General] Darkmind1:
If you want to keep using Samsung-based ROMs you might want to have a look at AllianceRom, as far as I know the Kernels they use are based on Samsung but I believe they did a workaround and they are safe from brickbug. I can't guarantee for sure, though, but you should have a look.

I personally prefer using AOSP or AOKP-based roms. Cyanogenmod kernels are perfectly safe.

Also, you should bear in mind the need to use the Triangle Away app, which I suspect may be dangerous to use as well on such kernels, though I have no info on that, it's merely my own thought.
[Galaxy S II General] karendar:
Triangle away is in no way dangerous of superbrick on any kernel. It has its own risk (Accessing a boot partition and modifying a value on it), but it does not evoke any wipe command. Please don't spread false rumors...
[Galaxy S II General] Darkmind1:
Wasn't sure about the info that's why I did specify it's merely my own thought and not confirmed info.
[Galaxy S II General] ohwarumbloss:
No Problem guys :)

As I said, it was my first brick since 2009 so I guess it had to happen lol

Now here is what I did this time :

Downloaded the superSu zip file from this Forum and rooted my phone with stock recovery.

Then I used the CWM.zip from this Forum, too and booted into it.

Once there I did a factory reset, wiped cache and Dalvik Cache, then installed cMiui which has Aroma Installer and gives the choice of 2 Kernels.

After I like the Dual Boot and the Kernel in general I used Siyah Kernel and finishes flashing.

Now I have a good Kernel without that ugly Triangle at boot.

Don't ask me why and how but that's how it worked :)

Greetings

@OP : Sorry for off-topic, just wanted to tell how it worked safe.
[Galaxy S II General] Force Close:
Just to clarify, am I right in saying that doing a factory reset through the stock 3e recovery should not invoke a superbrick as it does not use the MMC_CAP_ERASE() function?
[Galaxy S II General] ohwarumbloss:
I didn't wipe with stock but with the CWM.zip ( can't remember the Version of CWM) everything was just fine.

But...if it was possible to brick your S2 with the stock recovery that would be a hardcore failure lol....

As far as I can see now, the only dangerous and very wrong thing to do, was flashing the leaked 4.0.4 software instead of the 4.0.3.

That's what I did and will never ever do again ;)

Greetings!
[Galaxy S II General] Force Close:
The problem is that I am seeing a lot of contradicting information. Entropy512 has made various references to "Samsung engineers not believing that 3e can cause a brick". I especially am interested because I sent my phone in for the repair of a dead pixel. The repair center updated my phone to the XEU XWLPT. I could just install Siyah through Odin and be happy, but I want to have the peace of mind that the stock recovery shouldn't cause any problems unless a faulty update-binary is used (such as the CWM.zip you mentioned) if I ever come back to stock XWLPT (which I might do thanks to it's nice and smooth feel). That, and I do not want to touch the update counter so soon when I am happy with stock.

I did find a thread on samsunggalaxysforums.com where multiple users did not seem to have a problem after factory resetting through 3e after running into various ota-update related problems (corrupt apps, camera issues).

It also seems extremely stupid to think a company like Samsung would release a firmware through official channels when a brick could be caused without any unauthorized modifications.
[Galaxy S II General] ohwarumbloss:
I think I got your point now and, maybe I have a solution :

Use ktools from market that allows you to dump your current ( in your case stock) kernel and also restore it. Then, use CWM to make a backup of your stock Rom. Save both to a save place. Now you can do whatever you like, flash kernels, custom Roms...

If you want, or need to come back to the original Rom you should be able to do this by a) restoring the Rom backup and b) restoring the stock kernel using ktool again.

Please note, this is just pretty theoretical since I didn't try it. But I have my backups of the files and will try ;)

Let me know what you think about this..
[Galaxy S II General] hakaz:
1. All 4.0.4 stock ROMs have kernels with MMC_CAP_ERASE enabled for secure erasing of data.

2. Any wipe/reset (3e, CWM, wipe script) which calls a secure erase must use the underlying kernel to run this request.

3. If you have an eMMC chip on board which is at risk (please test e.g using eMMC check app) then your phone may hardbrick during any wipe/reset action which calls the kernel's MMC_CAP_ERASE function.

So installing a kernel with MMC_CAP_ERASE disabled is the only way to protect your phone if you plan to stay on 4.0.4. Cheers!
[Galaxy S II General] Force Close:
Thanks, although I didn't need the help. I was just in need of clarification that 3e would also cause a superbrick.

Also, wouldn't a much simpler method to return to stock from a rooted kernel be to use a jig/TriangleAway to reset the counter and download a stock firmware using CheckFusDownloader? That is what I did earlier when I gave my phone in for repair (the custom binary counter was at 94:cyclops:).

Thanks! Guess I shoulod just use a kernel with MMC_CAP_ERASE disabled :). I only asked becuase of the mention of a "high-level recovery-based fix" on this thread.
[Galaxy S II General] ohwarumbloss:
Ok. I think this is to high for me.

The emmc brick check app tells me I have an insane chip :(

Please, factoryreset/fullwipe is ok on Siyah Kernel, right?

Duh, moved from ArcS to S2 and now I figure out that it's very easy to turn this princess into a paperweight. :(
[Galaxy S II General] hakaz:
This recovery procedure works indeed but at cost of memory space. They use a customized PIT file to avoid any damaged area in the eMMC chip. Problem is that before a superhardbrick occurs memory areas in the chip can be damaged by MMC_CAP_ERASE usage but the chip itself remains partly accessible. That kind of repartitioning is a clever workaround to revive such a partly bricked phone (e.g. data area is damaged and has 2GB so you will loose that amount of internal sd capacity but have won it for an alternative space installing the new data area).

---------- Post added at 10:50 PM ---------- Previous post was at 10:48 PM ----------

Siyah is safe as well as SpeedMod is (and several others out there ...) The stock kernel can kill your beauty ;)
[Galaxy S II General] mr_zuff:
Hi! I was in your same situation and I was a lot afraid to brick everything!

Then I found a solution in this forum!:)

Just flash the siyah kernel 4.0.1 using odin,and then you are safe! Before doing something stupid(lol),flash this kernel:it is safe from CAP-ERASE and the kernel roots the phone!

Trust me: is simple and is the best choise you can make now;)

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II General] Skrilow:
Hi

And what about custom roms ?

I want to try AllianceRom,then flash phenomenal kernel.

Is there a brick risk if I want to turn back to another rom ?
[Galaxy S II General] graemeg:
The question still remains that in the uk our air time suppliers like 3, and companies like cpw are still releasing 404 roms for the galaxy s2, so why are these roms been released when they will brick our phones, i struggle to understand that.

Does this brick problem only apply to peeps who are rooted, using cwm etc etc, or if i install the 404 update from 3 and stayed purely stock without any root, would i be safe?.

I am still running GB, reason for that was because i did own a note until similar issues occurred, i really dont want to risk the life of my awesome s2 on an upgrade until i know it is completely safe to do so, so any advice on wether its safe to upgrade when stock would be appreciated.
[Galaxy S II General] Stileth:
Yes, if you stay stock then you are safe with 4.0.4 ROMS. Samsung would not be releasing it if they would expect any increase in PCB changes due to damaged eMMC chip. The thing is that normal regular user will not get nowhere near recovery or download mode. He will use Kies and if anything goes wrong during the update he just takes it where he bought it. And I don't think that using Kies or doing OTA update can brick your phone due to damaged eMMC chip. There may be soft brick, but that can be easily solved by service center.

The bad command is invoked by CWM recovery and as was also mentioned elsewhere the problem is only with the touch version of it. At least as far as SGS2 is concerned.

Odoslané z GT-I9100 cez Tapatalk 2
[Galaxy S II General] aashgaur:
im using wanamlite 12.3 (4.0.4) with speedmod !! it wont hardbrick my fone !! will it ?? if i change my rom ??
[Galaxy S II General] ariarman:
i don't think changing rom cause brick .

because i do change several roms such as an ics 4.0.3 $ 4.0.4 $ jb costume in about 3 weeks.

the only thing remain is bad lock.

i used this roms:

official lq6 4.0.4

official lpm 4.0.4

omega ics lpg 4.0.3

x-teame cm10 v1 4.1.1

kaffe4tech v4 4.1.1

pfittech rom 4.1.1

portal rom 4.0.4 v2.3

speedwizz2 4.0.4 v3.1

wanamlite 4.0.4 v12.3

official wlpt 4.0.4

dilidroid 4.0.3

and always i came back to my favorite rom OMEGA lpg v15
[Galaxy S II General] Marcb:
Thats was also a doubt a had...

If a have a 4.0.3 Stock ROM with stock kernel and stock recovery, then update to a 4.0.4 ROM, stay completely stock and then full wipe my phone, I'm safe then? If what you are saying is true I won't have any problem whatsoever if a stay completely stock! Correct?
[Galaxy S II General] Mittaa:
I wouldn't do any kind of wipe using stock 4.0.4 kernel...

Stock 4.0.3 is save stock 4.0.4 IS NOT !!!

I have flashed Speedmod in order to avoid eMMC brick and BTW will avoid any kind of wipe if possible.
[Galaxy S II General] mpbtejada:
Hi. I'm currently on XWLPT 4.0.4, having upgraded from 4.0.3 via OTA. I tried out the eMMC Brickbug Check and it said that I have a SANE CHIP. Does this mean that I'm safe from this bug already? I' just bought my phone and with this apparent issue, I'm overly cautious to root/customize my phone nay further.
[Galaxy S II General] Stileth:
Yes, it means you are safe :)
[Galaxy S II General] webjunky:
i wonder when i will get my 4.0.4 update since im still on a roted STOCK 4.0.3 with stock kernel and 4.1 will be releast end of september/october ?