yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] ropiana:
I flashed my fon with the leaked rom with the pit file and my fon freeze on the android logo with the progress bar on the bottom and all you can do is remove the battery.

Tried to solved it, so I flash it again with the LPJ stock rom, my previous rom without any pit file cause when I downloaded it in sammobile there's no pit file included.

I noticed, all my pictures and musics are gone, meaning the lq5 pit compress your storage into 8gb and when I tried to take a picture, the file cannot be saved.

Final solution, I flashed it with gingerbread stock rom with pit file and success.. then after, I flashed it with the lq5 leaked rom without the pit file and everything is smooth with the correct storage capacity..
[Galaxy S II General] bombaybadboy:
i have been looking up about this bug but i suppose this Link is old news to some of you but thought it was interesting reading
[Galaxy S II General] hawkn:
When my phone died it was on stock LQ5 with stock recovery so there ya go !

I flashed LQ5 and tried it with siyah 3.3.2 kernel, then flashed back to stock kernel and recovery, still worked.

Then tried flashing stock LPG rom -----> EPIC FAIL!
[Galaxy S II General] cpl.Bower:
after flashing something, your warranty is void
[Galaxy S II General] Brotuck:
How did you flash LPG ? With mobile odin ?
[Galaxy S II General] cpl.Bower:
LQ5 was official too... Hours later was a "leak" and it was too late, the damage was already done.
[Galaxy S II General] Scarface1991:
I really thought about flashing the new CheckRom V7 which is based on the leaked Firmware from Sammy but NO WAY after reading such reports. I hope you guys can revive your phones somehow and thank you for reporting, so it won`t happen to users who can read :D
[Galaxy S II General] hawkn:
No, Download Mode = Vol - + Home + Pwr. always use that mode.

I have mobile odin, but haven't used it since...well, I don't recall using it to flash anything since Siyah kernel 3.1 or something.

The problem just took a new turn.

I managed to flash GB and CF-root.

Then when trying to mount/format stuff:

https://dl.dropbox.com/u/10646701/SGS2/20120709_165829.jpg

If picture is loading slow or some error shows. the message when trying to format anything is: E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p9, blk0p10 and blk0p7 namely /system, /data and /cache.

Formatting /emmc on the other hand completes and shows "Done.!" message.

I'm not sure, but my guess is that there is a way to do this.

I don't have the "know-how"....yet, but I'll get there within a year on my own or some time today with help :)

---------- Post added at 03:12 PM ---------- Previous post was at 03:11 PM ----------

Probably the best choise you've done so far this year :cyclops:
[Galaxy S II General] cpl.Bower:
How? Im trying to find something but nothing if you dont have the source...

drivers/mmc/host/mshci.c

^ there
[Galaxy S II General] Gillion:
It was official only for CHINA.

I suspect the Chinese devices do not have the eMMC firmware bug.

The leak was not official in any way shape or form for non China devices until this morning.
[Galaxy S II General] Pan Tralaliński:
show me where and when it was at kies ???
[Galaxy S II General] hakaz:
It was never available via Kies, you are right ... but XWLPM is, so let's see ... :fingers-crossed:
[Galaxy S II General] hawkn:
Finally I've got ADB limping here.

I'm able to push files to the internal SDcard, but when trying to install from stock recovery it fails. (has never worked on GB roms for me :P anyways)

Checked size of sd and it seems correct.

I had 2x /system folders, /system and /system1 and /sdcard + /sdcard1

I deleted /system1, pushed some files like CWM, SU and a few more onto the internal memory.

Still struggling with the ability to flash beyond GB XXKI8 rom (wich was the stock rom kept safe from last year)

Also struggling with getting CWM working properly.

Just a heads up. :)

P.S. does anyone know of a way to fix partitions/format partitions etc. from adb ? I feel like a total n00b asking the question :)
[Galaxy S II General] :
Sorry if you've been already asked about it ...but have you tried to re-partition with GB .pit like the one attached with XXKLI1 (full filename: u1_02_20110310_emmc_EXT4.pit). The error message you got in CWM indicates clearly that partitions are messed up. So maybe flashing the FW mentioned above together with repartition would somehow help you. I assume your DM works fine. Just recovery...fails.
[Galaxy S II General] fs1023:
Thanks googy anas.

Too late for me though, mine has been bricked since Thursday after doing a nandroid backup after installing leaked LQ5.

At least I can take some comfort in knowing it was not my fault so to speak as had been getting along well with rooting, roms etc till I put the firmware on my phone. Just a pity I had not held back but I suppose once you start getting confident with this stuff you just go ahead with things and try to take care.

Waiting for phone to be sent back.

Will it survive warranty test??

Thanks initial poster for taking the time to find out what happened to phones after LQ5 update.
[Galaxy S II General] Entropy512:
And if you really insist on having an I9100 report - http://xdaforums.com/showpost.php?p=28462386&postcount=675

Tab 7.7 - http://xdaforums.com/showthread.php?t=1752468

I777 - http://xdaforums.com/showthread.php?t=1757972

You're not guaranteed to suffer damage when wiping with stock recovery - even with secure erase (CWM that hasn't been rendered safe), some people could wipe a few times without suffering damage.

The damage rate from stock recovery (non-secure erase) is far lower than unsafe CWM (secure erase), but it is clearly not zero.

The problem is, once you discover you are one of the unlucky ones, it is too late. There is currently no repair methodology, and right now it looks like I will only be receiving information on a partial repair when I meet with my contacts in two weeks. I'll be able to take "superbricks" and make them into JTAG-recoverable hardbricks (repairing the damage wipes the entire chip according to everything I have been told so far), but without bringing AdamOutler's Unbrickable mod to Exynos devices (which is not possible without Samsung cooperation), a full robust repair solution will not be possible.
[Galaxy S II General] Entropy512:
Possible? Yes, however the process fully wipes the chip. In addition, Samsung considers that information to be even more proprietary than the reset-without-upgrade sequence, which alone is proving difficult to get.

The underlying bug can be rendered a non-issue by protecting the chip from ever seeing dangerous commands (which is why I9100 kernels previous to this one were safe). I am extremely disappointed in Samsung in that they claimed to be working on deploying a fix for this issue, but took a previously unaffected device and added the trigger conditions to its kernel.
[Galaxy S II General] rcmerlo:
Hi Guys,

I installed lq5 with mobile odin, did a wipe and root by mobile odin and still with stock kernel. I also restore all apps and data by titanium, everthing is working fine, no problem at all.

I read all posts in this thread, but I'm confused, how can I flash anything in my phone to make sure I'm safe?

Thank you for your help.
[Galaxy S II General] :
Dude no offense but it has been already posted several times, even in this thread. If you really read all posts here you would have know that already. If you're not afraid and decided to run LQ5 u must stay away from CWM recovery and especially wiping functions/ restoring backups. If you don't do it you're most likely gonna brick your device.
[Galaxy S II General] hawkn:
DM works like a charm, and I've collected a few pit files now and tried re-part. mem, but for some reason it hangs when writing data.img trough odin.

And another thing I noticed, when I flash ICS rom, and it fails, I go to DM again, flash siyah kernel with CWM or any other CWM image, then reload with vol + home and pwr combo, I get the S2 logo, and then the screen goes black, this is where it gets strange.

I'm able to use EFS pro and ADB based utils to read info on the phone.

This is how I pushed file to it, but still, it won't boot at all.

I'll do some more testing with several pit files and GB roms and see if I can get something to work better.

I also noticed one thing, not sure it's worth mentioning, but anyways.

Whan using key combo for DM, it says ODIN MODE in red fonts up left on the screen, when using my usb jig it says factory modes some times.

I'm sitting here waiting for a GB install to finish, XXKH3, wich has gone beyond the point where it always has stopped before with other ICS/GB roms, I smell a possible repair, but I'm not a huge optimist here :P
[Galaxy S II General] :
Man...it's scary :) Lykke til ;)
[Galaxy S II General] BeBeLuShuL:
:laugh:
[Galaxy S II General] hawkn:
And yes, my partitions are screwed, but my guess is that with the right pit file and rom +++ everything will be fixed.....at some point, either a new phone or this one getting a cure.
[Galaxy S II General] :
I noticed the same, so I guess it's normal. "Factory mode" with jig and, "Odin mode" with key combo...on ICS bootloader. I don't remember how it was on GB.
[Galaxy S II General] angelomaldito:
Check this thread and find out: http://xdaforums.com/showthread.php?t=1693704
[Galaxy S II General] 00raq00:
Thx. My device is unsafe. Is possible to check if installed kernel is safe?

Wysłane z mojego GT-I9100 za pomocą Tapatalk
[Galaxy S II General] Entropy512:
If it is a custom kernel, ensure that MMC_CAP_ERASE is not present in drivers/mmc/host/mshci.c

All I9100 custom kernels fit in this category so far, as do all official I9100 leaks and releases prior to mid-June 2012 or so. XXLQ5 is the first confirmed "dangerous" I9100 kernel, but I wouldn't trust anything newer than mid-June just to be sure.
[Galaxy S II General] cpl.Bower:
there is any way to edit that file or do something?
[Galaxy S II General] DaReDeViL:
Sorry for your S2, I wish if I could have been able to warn you before but it took me 24h after the LQ5 leak to decide to go back to LPG (and wipe all via cwm) and to face my first hard brick since my first android 2.1 phones.

To give you some more comfort, let me tell you that I bought my S2 (used) 8 days ago thinking it would be a better experience than with my (sold) HTC sensation XE (which I flashed a hundred times without worries) !!!!

But we can't blame samsung for this as we all flashed a leaked version which wasn't supposed to be used by the end-user. End of story !
[Galaxy S II General] danieldmm:
Officialy one XWLPM have Brick Bug... Attention to every one...
[Galaxy S II General] DaReDeViL:
Thank you for info, someone bricked his phone with XWLPM ?
[Galaxy S II General] DaReDeViL:
1# post updated : Listing references of confirmed dangerous firmwares ...
[Galaxy S II General] danieldmm:
It seems already 2 brick in Stock Recovery performing Wipe Data..

Cheers
[Galaxy S II General] Tuqano:
I have now the LPQ5 without ROOT, if I want to change it, what's the procedure? Flash a different kernel e.x. Siyah and then flash a different ROM or just flash a different Rom e.x. LPF, without flash kernel first?:confused:
[Galaxy S II General] DaReDeViL:
@ MODERATORS : isn't time to stick this thread so nobody misses the warning ? Thanks
[Galaxy S II General] veyka:
Yeh... because moderators actually see messages left to them in threads like this.

Just report the post with your request or send all the section mods a pm.
[Galaxy S II General] :
I flashed back LPG directly, without previous wiping, once installation was done I wiped data /cache from stock recovery (to avoid bootloop) and voila. I think it's one of the safest methods.

1)Flash different (safe) FW (DO NOT WIPE BEFORE) via Odin

2)Once it's done wipe data/cache from stock recovery (otherwise bootloop).
[Galaxy S II General] DubbyDum:
samsung and google are well aware of this bug for quite some time now

www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels

and i highly dubt that they would risk pushing a bugged firmware to such huge marker as russia with a possibility of so many devices going back to service centers to get replaced

i would not be the one to test that tho :)

but i will not belive those reports suggesting that officiaal kies firmware is dngerous - just remember the chimpansee that dryed sgs3 in mircrowve and then tryed to tell us that the phone got on fire by itself ... it just have to be checked by anyone with a knowledge on the matter - not by some random from some forum

well it is good now to brick your device and get it replaced for free adding few months to warranty - i guess many will traa to pull this one off
[Galaxy S II General] DaReDeViL:
already done, sent to both moderators of the section but prbassplayer is in vacation and reinbeau didn't respond positively or negatively

Anyway, I don't expect any benefit from it, just wanting to help ....
[Galaxy S II General] Jarmezrocks:
LOL could not have said it better my self.....sarcasm for humour at no extra cost lol.

Seriously who decides to flash any firmware after this version of 4.04 without first repartitioning back using the Gingerbread .pit file? That is just silly.

That ROM install of AOKP would have scattered bits of ROM in all sorts of nooks and crannies of the device. Have fun cleaning that up. jtag and stock recovery I think are the best bets here from this sort of disaster.
[Galaxy S II General] ptesmoke:
This needs to be stickied. It would a have saved me...

Also op please add bells LD3 firmware..
[Galaxy S II General] Subtract:
Here you go: http://xdaforums.com/showthread.php?t=1457458

or this one: http://www.droidreader.com/2012/05/how-to-un-brick-or-fix-soft-bricked.html
[Galaxy S II General] Tuqano:
TNX mate!! :good::D
[Galaxy S II General] Stevemeister:
I'm so lucky, I whiped my device twice after installing this leak and I have the faulty chip but my device is still running. Than I saw this thread...man Im lucky.
[Galaxy S II General] sgs2FTW:
my s2 is rooted with CF-Root and im on salman rom, do i have to unroot to be able to uppdate to official 4.0.4 ?:confused:
[Galaxy S II General] hakaz:
After bricking my S2 on Saturday I returned it to Sammy Service Center on Monday. They changed the MB within one hour under warranty, luckily I'm back in the game. ;)

Looking into the new MB/eMMC I found:

Memory check was o.k. .

And looking around I discovered in the N7000s forums:

http://xdaforums.com/showpost.php?p=28441668&postcount=307

So possible eMMC VIS00M with FW Revision 0x09 is one answer to the brick bug, Sammy seems to assume it safe. But please don't take that as a proof even if we find no phone bricked with this FW.
[Galaxy S II General] karendar:
One really has to wonder, as it's been stated before, if this is just an unloyal tactic to force some phones into early retirement... Or just a stupid move by a Samsung dev:

Dev #1: I fixed the brickbug! Compiled a version, try it out guys.

Dev# 2: I leaked the ROM, don't tell anyone!

Dev #1: Hey... Why is my phone not booting?

Dev Team Lead: Hey guys? You're both fired.

*Facepalm*
[Galaxy S II General] cpl.Bower:
No, this crap is/was on KIES!...
[Galaxy S II General] Entropy512:
If you have source for a kernel - yes. That's why all custom kernels for the GT-N7000 are safe - developers rendered them safe. Same for the CM9 kernels for I9100, I777, and N7000 - They were initially built from the "safe" I9100 Update4 source code, but then the N7000 MMC driver was pulled in to allow for a new wifi driver. While this new driver was dangerous in its original form, removal of MMC_CAP_ERASE from the file in question has rendered those kernels safe.

Right now, at this point, the only way to guarantee safety is to be running a custom kernel that was built from source code which allows you to verify that the kernel will not allow MMC ERASE commands to hit the chip.

Links to specific reports please? I'm trying to get as much detail on the stock bricks as possible to provide to my contacts at Samsung. They still believe that stock recovery is safe, but I've seen too much evidence to the contrary so far.
[Galaxy S II General] DubbyDum:
what was the story youve sold to service center ???

Samsung and Google are well aware of this issue since May and are working on a fix since, but as they said fix is being developed and needs extensive testing and who knows how long could it take

so as much your initiative is ok ... it is completley useless as Samsung is well aware of chips that they ordered and witch of those are affected.

got also all the information on what causes this issue - now they just need to develop a stable working fix and push it public

or maybe they did their numbers and it came out that percent of the devices/mb/chips affected is ok to just handle it via service center repairs

oh, and they well know that it is a isue wit stock samung recovery or whatever you call it - the one that comes with firmware - so your source is hmm wierd :)

---------- Post added at 05:11 PM ---------- Previous post was at 05:01 PM ----------

ref -> plus.google.com/111398485184813224730/posts/21pTYfTsCkB
[Galaxy S II General] karendar:
A 7 post user contradicting Entropy... A big ROFLCOPTER comes to mind.

---------- Post added at 05:21 PM ---------- Previous post was at 05:20 PM ----------

It was leaked initially. Keep that in mind. Too bad I couldn't make you laugh. ;)
[Galaxy S II General] Entropy512:
Well, you're apparently quite clueless, since the contacts at Samsung referenced in that post ARE the ones I'm talking to.

And no, they are NOT aware that people are suffering damage in stock recovery. They believe that it is totally safe, and have asked me to try and find devices that have suffered damage from stock recovery for analysis. I've passed 3 reports to them so far, but if there are two reports of stock XWLPM doing damage, that's more evidence that nonsecure erase isn't as safe as they think it is.

Also, XXLQ5 is evidence that they, unfortunately, have not been working as hard on the fix as claimed... I've indicated to my contacts that the XDA community is extremely disappointed with this recent development. We were told one thing back in May, but the results with XXLQ5 are the exact opposite - instead of having fixes deployed, a previously safe device has been put in danger.
[Galaxy S II General] fr3nlysmil3:
i have a brickbug too.......rooted via temporary cwm.....wipe via temp cwm and the only thing i didnot do was restore a nand backup :)

guess i was lucky :/
[Galaxy S II General] karendar:
I'd donate my phone to the cause if it was still under warranty and Samsung could promise that they'll repair it once it's bricked. Sadly, warranty ended 2 months ago. The disadvantage of buying the phone on release, I guess.
[Galaxy S II General] jomaga:
I have this chip too, eMMC check report it as safe, but gotbrickbug? (chainfire) report it as unknown, but don't know if it's dangerous

I heve passed eMMC memory check without poblems too
[Galaxy S II General] sachidanand444:
Thanks buddy...

I was just about to do this... I have already flashed the leaked firmware. I was about to root it with CW kernel... I am lucky that I saw this post... Thanks once again...
[Galaxy S II General] danieldmm:
Here:

http://xdaforums.com/showthread.php?t=1762974

And i did see in the thread of CF ROOT some one say this 2 bricks story...

Cheers
[Galaxy S II General] bidboy:
Does this mean my kernel is safe. Factory resets etc.,. ?

On LQ5 at the moment.
[Galaxy S II General] veyka:
If it says sane, its safe.

So yes, you are fine.
[Galaxy S II General] hakaz:
I have this eMMC chip revision since the MB replacement yesterday, my original MB had the eMMC FW 0x19 (brick bug) which I ignored successfully :p.

The VIS00M chip seems to be a new variant available in replacement boards and newer S2 phones sold within the last weeks, up to now I haven't found anything about bricked phones with this specific chip (what is no proof at all, but as you say eMMC check reports it safe). :fingers-crossed:
[Galaxy S II General] WandersonGD:
Now I'm afraid to flash it... I await future updates.
[Galaxy S II General] hello33:
Is it safe ?

Hello,

I'm on LQ5, no root, i just flashed the 3 firmware files with the new corrected PIT file.

as you can see in the screen shots, i have the brick issue ?

is this related to the firmware or the hardware ?

if i change the rom i will get rid of the brick ?

thank you.
[Galaxy S II General] balb0wa73:
Mine says insane , ive flashed back to LPG, and its still there
[Galaxy S II General] bombaybadboy:
Sorry but are you saying that newer devices wont have the brick bug. I passed the eMMC check as sane chip and i got this phone 6 weeks ago. So what ever i flash and however many times i flash wont affect my chip. Sorry for newb question but the brickbug is a new thing for me
[Galaxy S II General] hawkn:
Thanks mate, but the sad thing is...it didn't work, talked to a dealer in town today, they will send the phone in to a service center and well take it from there.

I told him that I was upgrading with KIES and it failed and the phone was dead :)

I've flashed stock 1-part file after this with the latest release for nordics, think it was LPG or something, and then I flashed the stock kernel to this release, and used my little jig to boot download mode with erasing download info resetting counters and such ;)

Hopefully the service center will accept a swap and not bother that I've changed the housing on the phone (did this right after I got the phone because the original housing cracked when I dropped the phone on the floor :)

2-4 weeks they say, man service in norway sux !
[Galaxy S II General] veyka:
That's the idea, that samsung have fixed the bug on newer hardware with newer firmware, but those of us with older (think last year, I got mine late june), are still stuck with a buggy chip and no way to update the firmware at this time, so just be careful if you have a brickbug chip.
[Galaxy S II General] WhoIsJohnGalt1979:
Hello mate, I was on LQ5 stock rom with stock kernel for four days, rooted through pushing cwm and su+binary from stock recovery. Now, am not very sure but when you do a *2767*3855# does that categorize under data wipe from stock recovery or settings or is this something else? Reason I ask is I have done a factory format using the number code for 5 to 6 times on the above stock rom and have been all good.....:confused:
[Galaxy S II General] DubbyDum:
fun fun fun indeed

99/100 here with "Recognized" are hmmm idiots so i ignore that tag as an indicator of knowledge

that is also why my post count is so small if you know wht i mean

i guess you are talking with clueless person at your local branch of samsung delegted to talk-to-people, post twitter/fb/g+ updates :)

i also have such contacts :) everybody does, please ...

think mate, why samsung would care on fixing THIRD PARTY recovery, modified one. WHY would they care about it

they do not - it is not their buisness to fix outside recoverys - their work ends on stock recovery and stock firmware

they do not care bout xdadevelopers so 'your disappointment' vanih in the air

such sites brings more 'pain' to the user phone experience than real benefits (insecure roots or some code hacking;)

XXLQ5 is some inside build

how do you know it is not a build made to check if the brickbug exists on pecific chip - you do not know that

this revision should never leave samsung at first place

your motive to let as many people know bout the dnger of flashing leaks is ok

but the whole reporting and samsung do not know bout stock recovery

well no moar comment on that :)
[Galaxy S II General] Subtract:
That's a factory reset, basically from the settings thought.

@DubbyDum It was on kies.
[Galaxy S II General] :
He was talking about STOCK and not THIRD PARTY (CWM) recovery in the part you quoted if you didn't notice....That's even stock recovery wipe that can cause the brick...my dear "non-idiot" :silly: