yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] ballmead:
It's an awesome ROM.

There's zero issues if you keep it stock.

I won't be signing.
[Galaxy S II General] mozzer2k4:
yeah, its a brilliant rom, just flash it as a stock rom with no root or modified kernel, and DO NOT include the pit
[Galaxy S II General] android_isda_shit:
hey everyone, Vertumus has signed the petition =)
[Galaxy S II General] Prashanthme:
Ya exactly ppl who dont know flashing and stuff will be safe. It bricks only if u try formatting using a recovery which has MMC whatever that stuff.. Removing is not a gud idea but we can tell others dont install if u using Custom ROMs because it hard bricks the phone... Simply removing doesnt help it..
[Galaxy S II General] android_isda_shit:
my friends, other 4.0.4 releases will show up, why hurry and risk your device, lets just wait for another release, and hopefully a more stable release, and this release isnt official as we all know, i heard samsung was going to make the 4.0.4 release TWUX, so why hurry, why take the risk
[Galaxy S II General] Juoin1001:
Instead of a petition to remove it, why don't you petition sammobile to put a big warning there instead? Surely its easier for them to include a warning than to remove it complete. I've used it and successfully went back to stock and I find it a great rom. So instead of wanting it removed, why not just stick a big warning next to it, those who want to flash it would then know the risks and procedures to revert back to stock.

Just a thought.
[Galaxy S II General] Brotuck:
Guys grow up

We are on a developers site.

Leaks are happening here all the time, sammobile is only one site that has a copy.

This firmware does not have issues with bricks. PERIOD.

It's only cwm that is giving issues with it.

But CWM is a developers tool never made by Samsung. (i think it was a CM9 app?)

If we want to fix anything here, it is the general knowledge here of what a leak is all about. And with it the risks it can bring when used wrongly.
[Galaxy S II General] android_isda_shit:
yeah it was a leak, not finished yet, not released, has anyone updated there phone to XXLQ5 via KIE'S??

we will get it when they finish it, it is surely not wort the risk, and yes i will change the petition goal, so that they put a BIG warning sign, good idea my friend =)

cheers
[Galaxy S II General] saobang3886:
I agree with a warning! don't need to remove it, I use this Rom until now with no problem and fill good with it. So, I will stay with this Rom and wait for new release :D
[Galaxy S II General] tariq2kn:
I too have flashed the day it was released. But i haven't flashed any custom kernel/cwm/root as it wasn't made available. Later, I read bricking of phones & didn't try rooting it.

I am still on stock XXLQ5 & it's working fine, no issues.
[Galaxy S II General] Juoin1001:
Since you've changed it to a warning petition, I'll gladly sign it. ;)
[Galaxy S II General] pulser_g2:
XDA has had a warning in place on the S2 forums since yesterday when it came to my attention that there was an issue :)

There's no reason to outright remove access to this ROM, so long as people are aware that it causes the hardbrick issue.
[Galaxy S II General] atifsh:
And there is no need to sign it, Sammobile already showing warning since yesterday. In red colour if that will be your next complain.
[Galaxy S II General] superleeds27:
Totally agree with Pulser.

Its leaked, Samsung havent exactly said to users , Hey, come and flash this!

Its the same with the JB port. Should we ban that too?
[Galaxy S II General] Sideromelane:
Lol

Ban a rom that works FINE if you follow the instructions on the website, and that five minutes of reading about on XDA highlights issues with, and also presents FIXES so it CAN be used safely?

Hahahhahahahaha no

If you are stupid enough not to follow the developers instructions, and don't like the disclaimer telling you not to install it if you are thick, then DON'T FLASH IT!

And if you ARE thick, install it anyway without following the instructions and brick your phone, then serves you right.

If we banned everything because of some moron hurting themselves with it we would all be living in plastic bubbles.
[Galaxy S II General] _Sale_:
Signed.
[Galaxy S II General] rjsmer:
In...
[Galaxy S II General] nakanase:
signed!! done!1:D
[Galaxy S II General] johnfranz29:
Signed
[Galaxy S II General] atifsh:
You guys are blind or something? Sammobile posted warning yesterday.
[Galaxy S II General] drelite08:
Risks you take when flashing a pre release firmware. Doesn't take a Stephen hawking to work out there are risks. Don't wanna risk it, then don't flash it. Simple.
[Galaxy S II General] :
People are aware, but they don't learn. If you put a bad kernel and aware [famous one] that is programmed to brick, people still download it. If you put a first 4.0.4 ROM doesn't matter if they are leaked or not, doesn't matter if you warn everyone. I totally agree that those downloads should be deleted, otherwise, we will continue to see crying people at q&a. I also think that potentially risky stuff here should be deleted. If not, the only thing we can do, is repeat several times: "You were warned!!" and it's not cool.
[Galaxy S II General] beston94:
This isn't about people looking for fun arguments, this is about this petition not making any sense :D Do you know what leaked means? It means that it got out but wasn't supposed to get out.
[Galaxy S II General] StevenBX:
This thread is ridiculous.

Anyone flashing non-official ROMs should be aware and accept the risks involved. If you bricked your phone, it's your own fault. End of story.

Even if anyone were to take you seriously (they won't), your petition doesn't even make sense AT ALL. You haven't even addressed it to anyone. You start "they must remove...". Who are "they," supposed to be exactly? Samsung? SamMobile? XDA?

If you're going to throw a tantrum because YOU bricked your phone because of not following instructions, or aren't prepared to take the responsibility for doing so, you should at the very least know who you're complaining to..
[Galaxy S II General] Warren.D:
This is the best Rom I've used since KI4!! Without modding anything or root!
[Galaxy S II General] CuBG:
There is official 4.0.4 for russia.

Product Code: GT-I9100LKASER

Latest firmware: I9100XWLPM/I9100OXELP8/I9100XXLQ6/I9100XWLPM

Modified: 6.7.2012 г. 11:20:40 ч.

I think there is time to move on to official stuff only :)

Check CheckFus App for the ROM
[Galaxy S II General] android_isda_shit:
i havent bricked my phone, i made this petition because i opened up the Q&A section today,

HAVE YOU??

have you seen our fellow xda members, sad becouse of there devices, no one to help,

if it wasn't for this F***in leak, than we would have had things just the way they were,

people want to flash things, people dont read instructions,

people press ctrl+F and type "download", they just want to try things out, and now

that they bricked there devices, they are looking up to us to fix it for them like always,

im just saying that they should return the leak where they found it, and just leave it

things can then go back how they were
[Galaxy S II General] DD-Ripper:
Sammobile should probably test their leaked firmwares before releasing it to public or put it into beta testing mode untill its stable enough to be released it to the public.

Bro, like here in XDA before 4.0.3 ICS was officially released for S2, there were many 4.0.3 leaked beta firmwares released by the developers here. Did it hardbrick anyone's phone ??? HARDLY one or two because maybe it was on pre alpha stage.

And Sammobile ??? I never trusted any of their firmwares nor should you guys, because if it bricks your Phone, they aint going to help you out in any way like we people in XDA do to help anyone in need.

Literally its upto you people to flash it or not. Its your choice. Dont let the greed get better of you. Wait for the official 4.0.4 release and flash it then.

Sent from my GT-i9100 equipped with Grenade Launcher and ZN6 Prototype
[Galaxy S II General] Baldilocks:
To quote someone wise...

"..what has been done, cannot be undone....."
[Galaxy S II General] Tuqano:
Okay guys, I make a simile: there are two markets for weapons, an official (Official Samsung Kies-Rom) and an unofficial (Odin leaked Sammobile-Rom).

Well, I decide to buy a "magnum" (Install a Rom), I can choose to:

-go to the official and legal armory and not run the risk that I burst my gun in my hands (I Do not Brick the phone):cyclops:

-go to the unofficial and illegal armory and run the risk that the weapon will explode (I Brick the phone):crying:

If I choose to buy the gun in the unofficial armory, and the gun broke, I certainly can not sue someone or ask someone to withdraw the gun from the "black market", because when I bought the gun "of contraband "I knew the risks I was running.

Moral of the story: We all know the risks we run by installing "Leaked Rom". If we're not sure we should not install them and wait for the official ROM.

Sorry 4 my english!!:silly: :good::D
[Galaxy S II General] Entropy512:
Wrong. I've seen at least one report of eMMC damage from stock recovery with this kernel.

Despite Samsung's claims that nonsecure erase is safe, it's pretty clear that it isn't. I've seen 3 cases of eMMC damage from *stock* recovery since Thursday across three devices (One Tab 7.7, one SGH-I777, one GT-I9100).
[Galaxy S II General] android_isda_shit:
YES SO WE SHOULD PUT A WARNING ON THE SAMMOBILE.COM SITE, there are other forums than xda you know

i would post a bunch here but i think it's against the rules

people from other countries go to different forums because of there lack of English

do you think anyone is warning people about the XXLQ5 rom there, NO,

so we need to put a warning on the source, we need to let people know before downloading, people all over the world

and the something as we all know happened to the SGN after a update from Samsung was released (leaked)

not 4.0.4 but it still had a bad pit file, and bad kernel, so it caused many problems,

and with you with the 4.0.4 firmware, please check, do you guys have your serial number?

Samsung really did it this time, now they will really know if your warranty is gone or not

no more jigs or triangle away after this one guys, the triangle is gone, so is the odin counter

but they will still see that your serial number is gone
[Galaxy S II General] DD-Ripper:
Absolutely Agree with you. There is no other forum in the whole internet other than XDA where people care for others more than themselves and make sure that no one does the same mistake they did which costed them in having their phone hard bricked.

Sent from my GT-i9100 equipped with Grenade Launcher and ZN6 Prototype
[Galaxy S II General] atifsh:
stop here! you are so so so wrong, and i know even if i prove to you that stock recovery is safe you still wont believe because you are the people who trust more when read somewhere than actually listening to what the people using i9100 saying.

bythe way search the i9100 general form theres a youtube video showing same, if you cant fine ill be happy to flash and wipe using stock recovery on LQ5
[Galaxy S II General] android_isda_shit:
my friend, do you expect people who know how to use odin, to stay unrooted?

you may, but im 100 percent sure that most people flashed a kernel right after flashing

im not bricked, neither do i have the bug, im just looking out for others, now please,

either support the petition, or make a petition with 100 names, to take down this petition :D
[Galaxy S II General] drelite08:
As already said before, officials have started. Move on and forget it :D
[Galaxy S II General] karendar:
You know what? I'd believe Entropy512 over you any day of the week. ;) No offense. But it's not because ONE phone didn't brick that all phones are safe. Your assumptions are missing a key element: Some of these phones have a vulnerable emmc and CAN have issues. Better be safe than sorry, to be honest. The ROM will still be avaiable to everyone who wants to risk it, it's all over the internet by now.
[Galaxy S II General] cyberon:
I have flashed this rom, didn't liked it so wiped everything and restored a nandroid backup of CM9.

I have tested my phone with chainfire`s app, and it is supposedly affected by the issue.

My phone is not bricked.
[Galaxy S II General] kenfrancoise:
Signed.. Full support to the creator of the ROM I am using :)

Sent from my Calculator Casio ES003
[Galaxy S II General] dadyal:
i am on xxlq5 and its working great atleast for me
[Galaxy S II General] voornaam3884:
Take it away

Consider it signed. Away with damaging software.
[Galaxy S II General] jrsoft:
Edited
[Galaxy S II General] android_isda_shit:
ok its raining stock roms back at sammobile.com

Model	PDA	Version	Date	CSC	Country/Carrier

GT-I9100	I9100XWLPD	Android 4.0.3	2012 June	I9100PROLP1	Belgium / Luxemburg

GT-I9100	I9100BULPD	Android 4.0.3	2012 June	I9100SWCLP4	Switzerland (Swisscom)

GT-I9100	I9100JPLPF	Android 4.0.3	2012 June	I9100OJPLPC	United Arab Emirates

GT-I9100	I9100XWLPM	Android 4.0.4	2012 July	I9100OXELP8	Russia

GT-I9100	I9100BULPD	Android 4.0.3	2012 June	I9100VD2LP9	Germany (Vodafone)

GT-I9100	I9100BULPD	Android 4.0.3	2012 June	I9100VODLP9	United Kingdom (Vodafone)
[Galaxy S II General] angelomaldito:
AFAIK, on LQ5 if you wipe/factory reset your device on system settings/privacy, you may trigger the brickbug. I was using it and I was loving it, but I think it doesn't worth the risks involved, i.e. my phone's motherboard:cool:
[Galaxy S II General] elemenofi:
Signing
[Galaxy S II General] fatjivi:
I signed even minimal risks should be displayed just like at the back of drug even if it's 0.0002% user should know the risks...I'm not so impatient I'd rather wait for a confirmed stable build rather than turn my phone into a paperweight
[Galaxy S II General] heldchen:
what more and more people seem to forget lately is that xda is meant as resources for developers not end users. you are risking your devices, especially when using leaked firmwares. if you're not willing to take that risk, then don't flash it. but please, do not make decisions what is good or not good for me - i'm old enough to decide by myself, i do not need censors.
[Galaxy S II General] angelomaldito:
You're completely right in this point. However, leaving the trap online awaiting for people that are unaware of the issues is not a good idea. At least a good disclaimer should be put (and already is on sammobile website's download link) in order to inform users of the known risks involved.

This petition *may* encourage more responsibility on the part of those who make leaks available, as well as of those who spread them online. That's my opinion.
[Galaxy S II General] iekansh:
^

Okay, so according to you, this petition is against the guys who make the leaks available? You're petitioning against an individual you don't know?
[Galaxy S II General] The Undertakerr:
Yeaazzzzz, these ROM leaks aren't meant for end-users! But they are great for development purposes!

XDA is a development site! Developers are using these Rom leaks for sources and info!

So you say: Don't give the developers on a development site rom leaks, because there's also a bunch of kids playing with their phones and they're bricking their phones...

Threads like this should be closed on a development site...
[Galaxy S II General] :
I'm completly against publishing leaked stuff. SamMobile should have been more responsable and separate leaked fw in other section. And on XDA, it should been banned if conclude it is dangerous. People like taking risks. Remember me, what's the fun of living? ;)
[Galaxy S II General] naturist:
though you shouldn't blame anyone for your own brick devices, they are the one's who are releasing updates before Samsung but still signed the petition just now, sammobile shouldn't publish articles blindly, atleast a warning should be there.

I love sammobile though.
[Galaxy S II General] Jarmezrocks:
I am all for joining a majority to have a voice...but I am not sure what the problem is? I have been using LQ5 now for the past couple of days and its running flawlessly. Aside from the packaged pit file I think its the most smoothest and best running firmware Samsung has ever released to tell the truth. Only those that don't have an understanding of what moving to a similar file system as the GS3 incurs, would totally understand what I mean.

As soon as I saw the .pit file I knew that there was no way I was going to flash it. I knew what the consequences would be. Samsung them selves don't host this firmware anyway.....its sammobile that uploads it. It is uploaded to a public file host facility. I highly doubt this kind of negative publicity is going to do XDA any good.

It's considered a privilege to have access to firmwares such as the ones posted, it is not an obligation. At most someone could contact the site administrator and asked that a warning be put on the download (prior to leaving the sammobile site to be redirected) AT MOST. Fronting with a partition is only going to ruffle feathers that I don't want ruffled.

Please do not smudge the reputation of XDA because your pissed off at flashing leaked firmware or firmware you knew nothing about. That is your own problem...not Samsungs, not Sammobile nor anyone else. I had sorrow for your losses, but it only heads warning to those that are ill informed and too hasty

There is not a single thing (that I am yet to find anyway?) that is wrong with this firmware? I would have to say that this build I have of this firmware went off and flashed without a hitch. Actually I lie...there is no screen capture feature that I can see? It's probably there but I am not sure what the button combination is?...if someone knows please PM me.

Btw there is no title "Android is Upgrading" and it takes possibly 3 times longer to build the dalvik cache on this firmware and that is deceiving because what looks to be bootlooping is actually infact not at all! Phone boots and runs perfectly!!! After first build of dalvik not a problem. USB host mode - perfect! Perfect data transfer. Perfect wifi connectivity. I would say its the first firmware Samsung didn't f*&% up royally on except for the pit. (edit did anyone bother flashing the stock kernel and all stock firmware WITHOUT the .PIT file?)

Who knows....the pit may have been packaged by accident? It may not have been packaged by Samsung either? I never ready instructions to say that my phone needed to be re partitioned? I don't suffer from any lags and the ICS operating system is far from being a heavyweight on these types of devices. I diverse.

Please remove this Petition and do not risk it for those members of XDA who would like to keep relations strong with Samsung and its affiliates by gaining access to early releases. Thanks

James
[Galaxy S II General] :
After a warning, we can blame users. We can't blame SamMobile, true, they were trying to do us a favor. If a user reads the warning, flashes and brick, it's his fault. It's should be a lesson, every firmware, leaked or not, always read the last pages.
[Galaxy S II General] droid_1989:
I'm not signing for the simple reason, as it's a leaked version, the clue is in 'leaked' why not wait till the official release?

Plus if someone has posted it out on XDA? you break all of the rules by being a n00b and not reading that it could possibly brick the phone, after all it's been stated here.

Ok, they need to warn people, but if more than likely you get your rom sources from XDA or other modding forums, everyone should just read, it's infront of your eyes.
[Galaxy S II General] angelomaldito:
"At least a good disclaimer..."
[Galaxy S II General] dajumper:
I go sign to because my phone was bricked also. I send it today to repair center
[Galaxy S II General] Pan Tralaliński:
ONE LETTER ??????????????? 'brickbug' i wide covered by many sites including xda-developers main site article as well chainfirexda quite known developer around here talks about it since first bricks appares, even samsung-updates.com fansite asked sammobiles to at least warn users thaat it could brick the device, check out the anserw :)

https://twitter.com/#!/BoskiByczyByk/media/slideshow?url=pic.twitter.com/gNrjZebs

well said " weve #warned they #loled and you are #bricked "

---------- Post added at 06:12 PM ---------- Previous post was at 06:08 PM ----------

and btw brick happens with no root and no cwm - just on pure stock firmware untouched if you happen to have affected chip

also doent matter from what you flash it
[Galaxy S II General] angelomaldito:
I believe that "against" is not the word, "to" would suit better in this case. The "unknown" "individual" is obviously sammobile website as they've leaked LQ5. They've already put a sort of disclaimer with the respective download link, so now anyone who get there will know at least that there's something wrong with the file.

Please don't get me wrong, I'm in favour of leaks, and usually flash them (and I've indeed flashed LQ5 as well as many others from sammobile). However, I think that if they know that there is a specific danger, they should state that on a disclaimer within the donwload link (as now they did, by putting an exclamation sign, albeit without further details). Not everybody that get updates from sammobile read the XDA forums (where there's a dozen of threads alerting people to be aware of the issue).
[Galaxy S II General] Pan Tralaliński:
the description is wrong
[Galaxy S II General] android_isda_shit:
its not about XDA, its about the other fourms, whos giving disclaimers there?

no one!!, we need to put a disclaimer on the source, and no the word leak does not mean warning, so SIGN
[Galaxy S II General] Wololo7:
Signed. Simply because some inexperienced people can brick phones leading to hiiiiiigh repair costs.
[Galaxy S II General] Adrian.K:
Count 1 more!
[Galaxy S II General] Jarmezrocks:
Whats a petition going to bring other than soured relationships. I contacted Sammobile, I am sure that my single voice and how I proposed it will be more forthcoming and heard that your 100, 1000, 10,000 voices all rolled into one. Someone crying waaaaaaaambulance will get a roll of the eyes response, someone helpfully suggesting a minor change and a possible solution to ALL future "mistakes" (cause thats all it was....nothing more) can be avoided.

Solved. Pull the petition down please.

No need for petition. See attached! I fixed this by contacting them my self
[Galaxy S II General] Entropy512:
Yup. Even with the most dangerous form of erase (secure erase), damage does not always happen during a wipe.

That's the problem - Damage doesn't always happen, so one person wipes and says "I wiped - you're all safe!" - If you recall, when the SiyahKernel 3.1rc6 incident happened, Gokhanmoral wiped and flashed with CWM multiple times without issue - then when he released it to the wild, the bricks started piling up.

Note: This is the EXACT same bug GM tripped over with Siyah 3.1rc6
[Galaxy S II General] angelomaldito:
if you place your mouse pointer over the exclamation sign, you'll see the following message:

"Warning: If you flash this from custom rom or stock do not wipe/factory reset. But flash a stock Gingerbread Rom trough odin first before you flash this rom. In Gingerbread you can."

IMHO, they could have done better if they were more clear about the issue. Nonetheless, better than nothing.
[Galaxy S II General] Jarmezrocks:
Agreed ^^^ but some warning is better than none.

I have since found some show stoppers from releasing this version to use. Bluetooth enablement :( Phone USB all of a sudden unrecognised by PC? I feel this is either a driver issue or Kernel related to framework? I have flashed back to LPF until I can debug these issues. Otherwise ROM is perfect (as a modded ROM I am saying not as a standard version flashed from Odin). Very fast, very smooth!
[Galaxy S II General] atifsh:
hats off to your most senseless thread!

hey start another one please, this time to Samsung, checkfus because the official xwlpm has same bug. lol
[Galaxy S II General] Jarmezrocks:
I have firmware working now WITH bluetooth, WITH root, WITH USB mass storage working, recognised by PC also. Not yet a custom recovery implemented as yet....but working on that now too ;)