yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy R i9103] mj.vikram:
Dude mine is bricked on the first wipe itself, i totally agree with what Entropy512 said, it may brick on first time or 100th time also and in your case you are luck may be your chip is safe one.....
[Samsung Galaxy R i9103] parajsinghal:
Maybe I am not able to express myself correctly. I totally understand that so I'll try one final time :)

My first point is why and what are people testing? If we don't know which revisions are faulty. If ten people try 500 times and get no brick it still doesn't mean kernel is safe now. It could just be a case where they had sane chips? Right?

Secondly I have concerns over your testing after you receive back from SSC becoz it may be a sane chip after replacement?

So our efforts should be going into finding which chip revisions are buggy and creating our own emmc check app. Although I have no idea how to do that ;)

Please feel free to correct me if I am missing something.
[Samsung Galaxy R i9103] mj.vikram:
Who knows may be they will give me Android 5.0 Key Lime Pie ;)....

yes buddy i also feel the same we are not having the correct/proper app to check for sane or insane chip...

people who are testing may have sane chip so if they do it for 100 times also they will not brick there device but we can not tell that kernel is safe....

if possible we need to request Chinefire for the help in creating the app to check sane or insane chip for Galaxy R, i think Galaxy S2/Note one is not working on our device...

---------- Post added at 11:58 AM ---------- Previous post was at 11:30 AM ----------

Friends, Have any one tried to downgraded to GB ROM with the help of ODIN when you are running ICS....

I am asking this because i found some users of Samsung Captivate Glide who have downgraded to GB with help of ODIN are also having the problems like stuck on the Samsung Splash screen and booting Issues...

Both our Devices are using the same chip set and even i had the problem only after flashing the Stock Indian ROM with help of ODIN...
[Samsung Galaxy R i9103] parajsinghal:
Like I have mentioned before in one of my comments, I did that 2 times with from stock ICS and it worked fine for me.
[Samsung Galaxy R i9103] bhargav143:
I have done it twice too...
[Samsung Galaxy R i9103] drarunmmc:
I tried. ..

But getting error in odin. .

Royal. ........
[Samsung Galaxy R i9103] mj.vikram:
Just to inform you all, people who's Galaxy R is not covered under warranty please be careful because spare parts are not available with Samsung also.

I am telling this because today morning i went to Samsung Service Center for knowing the status about my mobile (because they told that they will replace mother board and it will be done by Friday (24th Aug) and still i didn't get any call form them).

Morning i went and asked about my mobile and they told that it will take other 3 to 4 days then i asked them that your manager told that it will done by last Friday itself and you are telling it will take other 4 day can i know the reason for delay then they told that "Mother Board is out of stock and they have order it to head office and if it is available they will ship it and they didn't get any response from head office it seems so they are waiting for Mother Board".

so i asked about what if my mobile is not under warranty then she told me that Galaxy R spare parts are not available/produced by Samsung any more so if something goes wrong it's difficult to get spare parts, if it is available also they will charge for shipping and laber charges also so it will be almost double the price.

And reg the ICS she thought it as Galaxy SII and told me that they will install the ICS but then she realize that its not SII and told me that she don't have any idea of ICS update for Galaxy R.
[Samsung Galaxy R i9103] vipul12389mehta:
Thanks for the Info...

We all ppl need to use it very cautiosly.... once our warranty expires...!!
[Samsung Galaxy R i9103] parmarket:
Same thing happened with me. phone bricked and gave to SSC on 01/08/12, they promised to be done within a week, after 1 week they got MoBo. but they broke my screen in process later they took 2 weeks and gave me phone on 21/08/12. :(
[Samsung Galaxy R i9103] emanoj.i9103:
I confirm the same. They took 10 days to get my lcd replaced. They also informed they have ordered spare request from Noida when i checked for status during interim period.
[Samsung Galaxy R i9103] drarunmmc:
I want the link for cwm flashable ics rom..

Please someone..

I searched but couldnt find..
[Samsung Galaxy R i9103] mj.vikram:
Both ROM and Kernel....

http://xdaforums.com/showthread.php?t=1838812
[Samsung Galaxy R i9103] bhargav143:
But, dude... There is legal rules... To have spare parts for 5 years from date of sale... If they deny, we can take legal action on them...

I got to know this from my dealer.. That time... I was in a mood to get my Galaxy R replaced with an S2, when I did not receive my phone for 15 days from the service centre.... Due to unavailability of MoBo...

He assured me that spare parts will be available for 5 years. Its is a legal provision....

Sent from my GT-I9103
[Samsung Galaxy R i9103] vipul12389mehta:
If its a legal rule then can you please provide with some source ???

and u really cant take these legal action in india..!!
[Samsung Galaxy R i9103] coldbeermt:
At Europe we have similar legal rules about consumer protection but... they have no importance, because they could say "we have your MoBo in stock after 4 years but it costs to you 450USD" so in the real world, you could have that MoBo, but you can't purchase it.
[Samsung Galaxy R i9103] bhargav143:
Five yr is a bit too long.. 2yrs will be good enough for me...

And...after two yrs.. I dont think.. I would bother for a tegra2 anymore..

And..if ur device works well for 2 years there is certainly no chance that it will brick in future..unless u play with the device.....

Btw.. I dont think..it will be charged that high...however due to the cheaper devices in market it would seem too pricey after 2-3 years....

And about the source of such legal information... I will try googling for the same as I get to my pc... And try to update u...

Sent from my GT-I9103
[Samsung Galaxy R i9103] mj.vikram:
Just now received a call from SSC that my mobile is ready :D .....

Downloaded all the files related to ICS, Now i will get it from SSC and flash ICS ( I am also joining the party with you guys ;)) .....
[Samsung Galaxy R i9103] bhargav143:
Cool...welcome back mj...

Sent from my GT-I9103
[Samsung Galaxy R i9103] vrajan:
Congrats bro. Dare to do wipe factory reset in Stock kernel again ?? :D:D

Sent from my GT-I9103
[Samsung Galaxy R i9103] mj.vikram:
Now Ardatdat's safe kernel is avilable so i can wipe what ever i want know ;).....

No i got Motherboard which is made in 09/11, so hope its safe one.....
[Samsung Galaxy R i9103] bluesky747:
Congrats bro!:D:thumbup:
[Samsung Galaxy R i9103] vipul12389mehta:
did you confirmed wether its GB or ICS ??
[Samsung Galaxy R i9103] mj.vikram:
Its GB 2.3.5 :crying: only, No issues now any how we are having ICS :)....

Friends can some please confirm me before i flash ICS (For safer side i am asking again)...

1. i will flash CWM Backup of Machram.

2. Flash Ardatdat's safe kernel.

3. Wipe data, Cache and Dalvick cache.

4. Then i can flash any of our custom ROM's.....
[Samsung Galaxy R i9103] karthik050782:
You are in right track... do the 4 points... Hope ur phone won't go again to SSC...
[Samsung Galaxy R i9103] drarunmmc:
Buddy..

Why are you installing leaked ics..?

We already have official rom ..

Flash that ..
[Samsung Galaxy R i9103] mj.vikram:
But we dont have Custom ROM's based on the new official ROM, so i am planning to Flash the Leaked one ......
[Samsung Galaxy R i9103] vipul12389mehta:
didnt get you...we dont have custom rom or mod ???

but you anyways flash some basic things TW UX and Rooting process....isint it ??

and both the version, leaked and official are odexed, rite ??

so whats the real diff between them ??
[Samsung Galaxy R i9103] drarunmmc:
Differences in baseband
[Samsung Galaxy R i9103] mj.vikram:
Better you stay on ICS only dont flash GB ROM, i am planning to give it in SSC...

God only can help me in this :confused:....
[Samsung Galaxy R i9103] xlm13x:
Don't worry SSC will replce ur mother board (its the only option to recover from emmc brick). Amd they can't check that what fw u were having because u phone can't be booted anyhow. Just make sure that counter is zero.

If SSC is not having spare mother boards than they will give u new phone or in replcement another phone in same price group.
[Samsung Galaxy R i9103] ardatdat:
I am still unsure about the kernel MMC_CAP_ERASE bug.

Since when you boot into CWM, actually, it does not load up your kernel!

Say for example, if you have flashed an un-bootable kernel or wrong kernel, you can still boot into CWM. So, I doubt whether a single flag of MMC_CAP_ERASE kernel is the root cause to the problem. Let's discuss. :cool:
[Samsung Galaxy R i9103] 'cooleagle':
As far as I've read up till now it seems that there is a bug in the firmware of the eMMC chip which can corrupt the emmc chip to the point of no return.

- In other handsets of Samsung the faulty firmware chips had a firmware revision of 0x19 / 0x25.

- I would request everyone to post a screenshot of the version of the emmc firmware their chip currently has by using the eMMC Brickbug app available in the Play Store.

- Just Run the app & take a screenshot of the information displayed.

@mj.vikram if you have a screenshot of the information that was displayed when you had checked using emmc Brickbug app do share with us here. It'll really help in understanding the problem at hand.

Let's hope we can get identify & eliminate this bug asap without more devices being bricked. :good:
[Samsung Galaxy R i9103] vijai2011:
Doesn't your phone boot at all??because it shouldn't happen while flashing from with odin...
[Samsung Galaxy R i9103] :
Mj.vikram I am sorry, I don't want to question what you wrote above. But I don't think you bricked your phone by downgrading. Brickprocess must have started before you run Odin (one of your partitions was already corrupted before you tried to rescue with Odin). Problems with Odin were just a consequence of previous operations that Odin couldn't solve. If we're talking about emmc brickbug it's never Odin that can cause this process and activate damage of your chip. But restoring a nand backup or wiping is well known trigger and it can brick your device for real. Restoring a backup is thus far more dangerous than running Odin. It's actually equally dangerous like factory reset in this case.

To install GB directly via Odin (or safe kernel) without previous wiping is known to be the the safest method to get rid of dangerous firmware. (It's really not me who found out this) Many people bricked their phones during restoring nand backups and thus any sort of operations in CWM is not recommended at all when you deal with this bug.
[Samsung Galaxy R i9103] vipul12389mehta:
Just lemme know, i can upload my cwm...its a 1gig of backup...

But my cwm contains lods of cracked apk..too...

So lemme know...i can do it..if u guys say..
[Samsung Galaxy R i9103] selva.simple:
True Buddy. As far as i know, flashing via Odin is the safest method for downgrading than restore nand backups. May be a full data wipe while being on ICS might b a reasn for bricking.??!!
[Samsung Galaxy R i9103] vipul12389mehta:
@m.kochan and @mj.vikram wat sould i add in op ??
[Samsung Galaxy R i9103] data55:
Report

1. I bougth my phone in china with the stock rom ZCLA1 (not 100% sure)

2. flashed XWLA4 Odin

3. flashed CMW 5 Odin

4. flashed NeO then MaZel CWM

5. install 4.0.4 with CWM backup ad did all 3 wipes (data, cache, dalvik cache)

6. when I tried to root with RootRecovery_v4 i got an error in CWM and it showed the dead android, but when i rebooted the phon i had SU.

7. phone freeze when I used some apps (reboot by pulling battery)

8. flashed TheFrankenstain^MOD 4.0 with all 3 wipes

9. when I got the OTA update CWM showed the dead android again.

10. use emmc brickbug
[Samsung Galaxy R i9103] silenth86:
My screenshot

This is my screen I hope so myy fone dont brick ;/ Only a have a problem with battery ;/
[Samsung Galaxy R i9103] :
Assuming that we are all the time talking about emmc brickbug...(which we're still not 100% sure) and according to information we have.... yes, full wipe while being on this ICS version was most likely the reason of partition corruption (or emmc chip damage). That could end up with immediate brick or sort abnormal behavior and not being able to perform some major operations. It could happen for the first or one hundread first time.
[Samsung Galaxy R i9103] karthik050782:
Mine is here.. No issues.. Only lagging while playing games...
[Samsung Galaxy R i9103] :
I think the best idea is to add some of these, so everybody can read about it.

These are some informative posts:

http://xdaforums.com/showpost.php?p=27074278&postcount=69

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

http://xdaforums.com/showpost.php?p=28416723&postcount=403

http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/

And do not recommend formatting/wiping/restoring...(backup should work fine though) via CWM.
[Samsung Galaxy R i9103] selva.simple:
The links seems to be mistyped buddy. Its not opening up. Please check and correct it.

EDIT : Oopsy. It seems to be working now. Sorry for that.
[Samsung Galaxy R i9103] :
Yeah they didn't work originally so I had to add them again ;)
[Samsung Galaxy R i9103] mj.vikram:
No buddy i have wiped data and downgraded to GB using CWM once and nothing happened to me and then again i flashed fresh ICS back and this time i Downgraded using ODIN and it started nothing is working except download mode..

Our Brick Bug is totally different from SII and Note, Brick bug app is not working on our Galaxy R....
[Samsung Galaxy R i9103] :
Buddy I do believe u and I don't mean to argue but I am almost sure your problem started after you performed those wiping/restoring and you would see consequences even without using Odin. Just because everything seemed to work fine right after doesn't mean that it was like that. After using Odin it just became evident, but it seems really doubtful that Odin triggered the brick.

At this point none of us can prove its right. I can only assume. I respect your point of view.

Nevertheless I think it's the same problem here like on s2 and note. The reason why application is useless in case of galaxy r is because Galaxy R is not among supported devices and thus none has ever examined those emmc chips.

With best reagards

m.kochan10 and I hope they'll fix your mobile ASAP.
[Samsung Galaxy R i9103] 'cooleagle':
Guys et girls,

I've contacted a few devs of other Samsung Devices like Epic4G Touch, Galaxy S2 / Note which had identified the this Superbrick bug. Let's hope they respond & could help us sail through these tricky waters.

Will update if I get a response / They might show up here directly as I've linked this thread in the Message. So just post the emmc Brickbug app's screenshots which could help in identifying the faulty chips.

Thanks to m.kochan & vijai2011 who provided info about their experience with this Brickbug. :)
[Samsung Galaxy R i9103] mj.vikram:
Friends i don't want to disappoint you guys, just telling my experience eMMC Brick Bug have shown my mobile also as sane chip ...

This app is not working on our Galaxy R and we are having different chip from Note and SII and our Brick Bug is also different from the other mobiles...
[Samsung Galaxy R i9103] Birki96:
Wow does that mean ur device is now dead forever? ! Do u have to throw away now? I have ics too... sh1t

I want gb back. .......

Don't want phone dead.

:(:(:(:(:(:(
[Samsung Galaxy R i9103] mj.vikram:
Yes mine is totally dead now, i am planning to take to SSC..
[Samsung Galaxy R i9103] 'cooleagle':
Sigh.

I'm not asking for screen shots to check whether it displays Sane chip or not buddy. I'm asking cause in other handsets (like Note) a faulty version of the Firmware revision was identified viz. 0x19 / 0x25 & along with the Type (1st field).

So if everyone posts a screenshot we'll get an idea what firmware revisions our devices are running on. And incase god forbid if anyone gets a hard bricked we'll at least be able to identity the faulty chips details so others with the same faulty chip version can be careful.

Even if someone does get bricked most of Galaxy R handsets are in warranty so it'll be a win win situation for everyone, as the person whose handset was bricked will hopefully get a replaced motherboard while we get to identify a faulty eMMC chip revision.

Hope you understand now.

Guys please keep posting the screenshots. :)
[Samsung Galaxy R i9103] mj.vikram:
yup understood thanks for explaining it in detail...
[Samsung Galaxy R i9103] selva.simple:
eMMC chip details

Here is mine. :cowboy:
[Samsung Galaxy R i9103] vijai2011:
The app was very first made by Chainfire here.So I would recommend using it.A little quote from that thread:

So brick bug might be there as it says its unknown.And I have attached screenshot of note having brickbug.

And may I know why and how do you say so?
[Samsung Galaxy R i9103] mj.vikram:
I don't have Pic :crying:, But i remember the details :cool:...

Chip : Valoom.

made : 08/2011

Brick : No, sane chip.
[Samsung Galaxy R i9103] selva.simple:
Same as mine buddy :eek:

But my fwrev is 0x11. Luckily not 0x12
[Samsung Galaxy R i9103] xlm13x:
U remember fw revision?
[Samsung Galaxy R i9103] CallMeVentus:
If it's the same as his it should be the same....

Note to all fwrev >0x11:

If you want ICS , DO NOT WIPE ANYTHING NOT EVEN SDCARD

"Friends forever." - Ventus
[Samsung Galaxy R i9103] :
Not even restore, cos restore means previous erasing, and it's equally dangerous. And remember friends....Just because someone succeded to wipe without any bad consequences it doesn't mean that its next try wouldn't be his last.

There are known two examples of brick already while the one is the classic typical example of superbrick as it was in case of Note and S2, and another differs but still there are some similarities.

At this point (with the statistical and empirical information we have about chips, kernel) there's no way to state that sgr brick is by any means different than other devices or exaclty same.

Right now one blindman is leading another. There are more assumptions and looking for logical analogies than raw facts. So be very careful guys!
[Samsung Galaxy R i9103] 'cooleagle':
Maybe I missed something but how did you come to that conclusion ? Kindly tell in detail cause it's important that we come to a conclusion only after an indepth analysis of the data available.

As of now no one has been able to confirm that we indeed do have MMC_ERASE_ CAP enabled but we're assuming it's the same problem as it's having the same effect, let's hope it's something else.
[Samsung Galaxy R i9103] Tha TechnoCrat:
Does this imply to the rom posted by ardatdat
[Samsung Galaxy R i9103] dr.ngk:
What can v do if we find that a chip has a bug? And is it just emmc bug or are there any other bugs as well
[Samsung Galaxy R i9103] coldbeermt:
eMMC check:

Chainfire's Got Brickbug:

I could say I wiped everything from CWM and from settings on my R with no brick at all. :laugh:

I did it on friday night :angel:. At this moment, I'm not sure if I would be able to do it again :cool:
[Samsung Galaxy R i9103] Entropy512:
No, it was later confirmed that deleting large files is currently safe (It was initially suspected to be a possible problem until more was known about the bug) - Samsung has not been using the "discard" mount option. Until they do, there is no chance that deleting a large file could cause a problem.

Below is what I was originally writing as a private reply to cooleagle, but it should be public:

To check the eMMC chip - Use Chainfire's "Got Brickbug" app. This is device-independent - if you have a known bad chip on a given device it WILL detect it. However, unknown chips are... unknown. :)

To check the kernel - http://www.xda-developers.com/android/another-way-to-detect-the-infamous-brick-bug/ - However, this isn't guaranteed to properly detect whether MMC_CAP_ERASE is present or not.

To fix recovery - Rebuild it from source using BOARD_SUPPRESS_EMMC_WIPE in BoardConfig.mk - Then run "strings" on the binary to ensure that you see "Wipe via secure discard suppressed due to bug in EMMC firmware" (Reference: http://review.cyanogenmod.com/#/c/17326/1/ext4_utils/wipe.c )

Warning - if you ONLY fix recovery, users can still experience damage if they flash a ZIP that contains a dangerous update-binary and executes formats in the updater-script. To check if an update-binary is safe, do the same "strings" check mentioned above.

All of the symptoms described above sound like Superbrick. It's not guaranteed that you will experience damage on a wipe - also, if you survive the first wipe you're much more likely to survive the next. (If you wipe a second time without writing to the partition, you'll never see damage.) When I was trying to intentionally reproduce this with Samsung a few weeks ago, we were unable to intentionally force it to happen. Meanwhile, other people brick their devices 4 hours after opening the box (xplodwild's Galaxy Note got nailed this way.)

Don't trust eMMC Check here - it reports unknown chips as sane... :( Given that this is a device from approximately the same era as other affected devices and the symptoms described, I'm fairly certain it's the same bug. Maybe my contacts at Samsung can give confirmation of this chip... I'll email them tonight.
[Samsung Galaxy R i9103] vijai2011:
Ah entrophy is here....guys consider that you are saved from super brick....;)
[Samsung Galaxy R i9103] Entropy512:
I can help protect but not save... Removing all the possible causes of damage on N7000 has proven nearly impossible, for example. Similarly some firmware developers on the I9100 are still releasing dangerous update-binaries (which reminds me, I need to download the latest Resurrection Remix release to see if westcrip fixed it yet...)
[Samsung Galaxy R i9103] CaptainKidd:
eMMc check

Mine is 0x11
[Samsung Galaxy R i9103] CallMeVentus:
Firmware revisions 0x12 to 0x19 are considered dangerous because they have a bug in their eMMC firmware , which can cause a Superbrick .

0x20 to 0x24 are unknown

0x25 is the safe one as we know it.....but goddammit Sammy

"Friends forever." - Ventus
[Samsung Galaxy R i9103] :
Entropy that's very interesting. I'm not trying to (God forbid!) question anything, cos all my s.c. knowledge about this bug I base on...well your posts in Note and S2 section ;) I am just curious. In S2 section there is general conviction (and I am not sure if I didn't read it in one of your first posts, I cannot find it now though, so If I am wrong about it so sorry.) that if all 3 conditions (faulty chip, mmc_cap_erase on, wipe from cwm/or even stock recovery) are fulfilled the brick is practically inevitable, question is only when. There are couple of cases where people reported bricks after 4,5th wipe (S2 section - infamous 4.0.4 leak).

I'm just curious if the information above is some sort of update and we were all wrong about it before.
[Samsung Galaxy R i9103] 'cooleagle':
Thanks for the response. :)

If you need any help / further info just post here or PM me, we'll provide you with all the information you / contacts at Samsung may require to help in identifying the exact problem. Hope it gets solved soon & no user gets bricked till then.
[Samsung Galaxy R i9103] vijai2011:
@entropy:Is it Mr.sumral?the guy who showed light to us(note users)??

Just curious.
[Samsung Galaxy R i9103] F3niX:
Mine is 0x11. Guess I am safe
[Samsung Galaxy R i9103] chandrus1983:
:highfive: same here, Mine is 0x11 :highfive::highfive:
[Samsung Galaxy R i9103] xlm13x:
As SGR is not suppprted by emmc check app it shows sane chip. But in app there is another option to check bad sectors which needs root to do the process. It takes about 300 seconds and show below results for me, is this process is helpful in checking that mmc chip is safe or not?