I've been doing a lot of reading about this samsung brick bug. It has just appeared on the GS2. Does anyone know for sure if the GS3 is free of this brick bug? I couldn't find anything that's 100% and been looking for hours.
Thanks in advance.
i dont think its present on the s3..and even on the s2 it was random..not everyone got bricked i think it was just sheer luck on either getting bricked or not.
No reports of the bug on SGS3 .
Incidence of bricked phones on SGS2 was very small .
jje
JJEgan said:
No reports of the bug on SGS3 .
Incidence of bricked phones on SGS2 was very small .
jje
Click to expand...
Click to collapse
But on the note lots of people Got their phones bricked with ics kernels. There is an app in the galaxy note section (Got Brick Bug ?) to check whether your chip infected or not.
More people bricked their phones by failing to follow the instructions than by the bug .Bug was relatively new bricked phones been here since SGS1 .
jje
The brick bug is in the eMMC in the exynos 4210 SoC used by the sgs2 and note and some others, the eMMC module has a conflict with the wipe command and thats why the phone bricks during flashing. Most ppl bricked because they failed to read the flash instructions (first flash safe kernel then flash rom).
I hope uncle sam did not use the same eMMC memory chips in the sgs3 exynos SoC.
Sent from my GT-N7000 using xda app-developers app
Bricked phones have been around a lot longer than that. As to the brick “bug" you can find a little app that will check down in development. Last I looked no one had.
---------- Post added at 05:34 AM ---------- Previous post was at 05:24 AM ----------
SquirtingCherry said:
The brick bug is in the eMMC in the exynos 4210 SoC used by the sgs2 and note and some others, the eMMC module has a conflict with the wipe command and thats why the phone bricks during flashing. Most ppl bricked because they failed to read the flash instructions (first flash safe kernel then flash rom).
I hope uncle sam did not use the same eMMC memory chips in the sgs3 exynos SoC.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
No many bricked before the problem was figured out. More followed who did not read up on and hence use the workaround you describe. Not a hard thing to do since it was not discussed in the op on many of the Rom threads and someone who was not keeping up regularly could easily miss it.
Related
I have passed the last 3 hours searching about this since I saw it on another post.
What is the brick bug??
According to my readings, this is related to ICS leaks flashing for sgs2 and galaxy note on roms and based kernels...and u can hardbrick ur phone when u do wipes / resets erasing partitions on the emmc.. kind of..
Masters like Chainfire and many others (my bad i forgot their names but they know who they are).. have provided explanations and links to this info. 1+ to KennyLegend for posting the link I read in the other thread.
So, after checking my s2 with Chainfire's app. I got the damn 0x19 chip which means I have the bad one but reading and reading it seems that for kernels based on the 4update source its kinda safe... But as I am not a developer and just and user Im still confused a lil bit about this...
And I know there is info missing for the readers on this thread... Im sorry really .. Im still confused and Im opening this thread with the intention of understand better the issue, so that I beg to the real masters that please clear all our doubts..
I.e. : what are the safe kernels based on the safest update?
And are we safe running xxlpxxx stock rom??
What flashing junkies need to know??
Is it possible to brick our device now since this bug was found on may??
And many many more doubts that will come up...
Thanks
Sent from my GT-I9100 using XDA
you mean the one whereby when you are using a kernel with the brick bug in it and you clear data, cache, you will brick your phone in the process right?
Hi
I've got the same (maybe) Problem here
Also i have that
VYLOOM
Revision 0x19
eMMC Chip on my GT-I9100
I have the free German Version (Country Code DBT)
And currently using the Polish XXLPW ROM (Kies Release) flashed with Odin over the official XWLP7 also from Kies. Using Chainfires CF-Root for LPW.
Reading this thread in the Epic 4G Touch General Section
it seems that some of the Devs Kernel don't have the 'workaround' that samsung has in some of his kernels.
Maybe of my english or because i haven't the time to read all the 47 Page so far, i do not clearly understand if this bug is only happens if you use factory wipe from the CWM or could it also happens if you use the Option from the normal ROM Settings under ICS.
I will read on and seeking in other sites for more information.
regards
Christopher
We do not have to worry if we are using the international sgs2 (i9100). I think it was for the korean version of sgs2. There are people who hard bricked their device using a custom kernel where they wiped and the phone never came back (it's in the general section). It's really not the fault of the kernel developer but by samsung. So no need to worry guys.
Sent from my GT-I9100 using xda premium
Lonzo_SGS2_506 said:
I have passed the last 3 hours searching about this since I saw it on another post.
What is the brick bug??
According to my readings, this is related to ICS leaks flashing for sgs2 and galaxy note on roms and based kernels...and u can hardbrick ur phone when u do wipes / resets erasing partitions on the emmc.. kind of..
Masters like Chainfire and many others (my bad i forgot their names but they know who they are).. have provided explanations and links to this info. 1+ to KennyLegend for posting the link I read in the other thread.
So, after checking my s2 with Chainfire's app. I got the damn 0x19 chip which means I have the bad one but reading and reading it seems that for kernels based on the 4update source its kinda safe... But as I am not a developer and just and user Im still confused a lil bit about this...
And I know there is info missing for the readers on this thread... Im sorry really .. Im still confused and Im opening this thread with the intention of understand better the issue, so that I beg to the real masters that please clear all our doubts..
I.e. : what are the safe kernels based on the safest update?
And are we safe running xxlpxxx stock rom??
What flashing junkies need to know??
Is it possible to brick our device now since this bug was found on may??
And many many more doubts that will come up...
Thanks
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
can you please give a link to the chainfire app.. so we all can check.
martintspedersen said:
can you please give a link to the chainfire app.. so we all can check.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=27014974
Sent from my GT-I9100 using Tapatalk 2
BTW we don't have to worry about it now but what if any new samsung official rom have that bug?
Sent from my GT-I9100 using Tapatalk 2
Relax. There's nothing to worry about. If this happens to you (very unlikely), it will happen suddenly, and there will be nothing you can do to stop it happening. If the 0.00000000000000000000000000000000000001% chance of it happening bothers you that much & you want to be absolutely sure that it doesn't, leave your phone on stock & don't mess with it.
This is probably the least responsible piece of information/firmware/app I've seen released in the 8 mths I've been coming here :-|
---------- Post added at 04:36 PM ---------- Previous post was at 04:35 PM ----------
Samsung will be paying to fix/replace your phone.
sahibunlimited said:
BTW we don't have to worry about it now but what if any new samsung official rom have that bug?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
its brick bug
sahibunlimited said:
BTW we don't have to worry about it now but what if any new samsung official rom have that bug?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
check the attached images i m running 4.0.3 ics Aut Switzerland
tell me its brick bug i many tym wipe/ factory reset with cwm nothing happen but chainfire app say brick bug exist
The brick bug is only present in ICS 4.0.4 firmware with Samsung kernel (or stock based kernel such as CF-Root) and it's only an issue if you wipe using CWM.
If your phone is stock and you have stock recovery then you're fine. You can delete/wipe cache, factory reset as much as you like. No harm will be done.
In short: 4.0.4 firmware + CWM = Brick.
Unless you flash a 'safe' kernel such as Siyah or NEAK or Speed mod
Brick bug x19 vyloom on my sgs2
hi im new to this forum
i have vyloom x19 emmc bug on my sgs2 so just wanted to ask can i change the firmware to other region or neat firmware over that via odin is it possible?
Hello All, My Galaxy S2(i9100) is not responding any more.... And I think this is a issue which is related to Galaxy S2 and Galaxy Note's eMMC bug. Because I had upgraded the firmware to STOCK ICS 4.0.3 (I9100XWLPG) which is available here. And i had flashed with chainfire's rooted kernel CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5.zip which can be downloaded from here. After using this firmware for a couple of months, recently i came through the eMMC bug news in Galaxy S2 And Galaxy Note. After that yesterday I downloaded chainfire GotBrickBug Application and found my device's firmware to be vulnerable to this bug. Then left my phone on the table and one hour later when i came back i found my phone dead. Phone was not responding and I tried Charging but it didn't respond...I pulled the battery but the condition didn't change. I think eMMC bug is responsible for the hardbrick of my device. But my question is that I didn't wipe or format my device so how the MMC_CAP_ERASE could occur?? I have sent my phone to the service center...
istipb said:
Hello All, My Galaxy S2(i9100) is not responding any more.... And I think this is a issue which is related to Galaxy S2 and Galaxy Note's eMMC bug. Because I had upgraded the firmware to STOCK ICS 4.0.3 (I9100XWLPG) which is available here. And i had flashed with chainfire's rooted kernel CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5.zip which can be downloaded from here. After using this firmware for a couple of months, recently i came through the eMMC bug news in Galaxy S2 And Galaxy Note. After that yesterday I downloaded chainfire GotBrickBug Application and found my device's firmware to be vulnerable to this bug. Then left my phone on the table and one hour later when i came back i found my phone dead. Phone was not responding and I tried Charging but it didn't respond...I pulled the battery but the condition didn't change. I think eMMC bug is responsible for the hardbrick of my device. But my question is that I didn't wipe or format my device so how the MMC_CAP_ERASE could occur?? I have sent my phone to the service center...
Click to expand...
Click to collapse
Simple - you've hardbricked for some reason unrelated to the eMMC bug.
The only I9100 kernel I'm aware of to ever get released that triggered the bug was Siyah 3.1rc6 - all other known kernels for I9100 are safe. (You would know this if you'd bothered to read the first post of Chainfire's "got brickbug" thread along with the posts linked to from it.)
You just had very bad luck. Your problem had probably nothing to do with the brickbug. Be happy, you had warranty left so don't worry.
Entropy512 said:
Simple - you've hardbricked for some reason unrelated to the eMMC bug.
The only I9100 kernel I'm aware of to ever get released that triggered the bug was Siyah 3.1rc6 - all other known kernels for I9100 are safe. (You would know this if you'd bothered to read the first post of Chainfire's "got brickbug" thread along with the posts linked to from it.)
Click to expand...
Click to collapse
yah bro i know about that. Siyah 3.1rc6 is the only buggy kernel for galaxy s2 (i9100). So my what can be the cause for that sudden hard brick?? And another question is that i had rooted my phone and flashed a number of times and i had a unofficial kernel as a result the triangle was showing before it hard bricked and i didn't reset the count number. So can after the hard brick will the service center people able to find info about rooting? As we know that rooting the phone will void the warranty.
krnrdstrm said:
You just had very bad luck. Your problem had probably nothing to do with the brickbug. Be happy, you had warranty left so don't worry.
Click to expand...
Click to collapse
Yah bro really i had a bad luck . It was my favorite phone. But my phone was rooted and also the triangle was present so I am very much tensed about that.
Maybe, maybe not. Impossible for anyone on here to say. Cross your fingers that they don't & you get lucky/get it repaired under warranty.
istipb said:
So can after the hard brick will the service center people able to find info about rooting? As we know that rooting the phone will void the warranty.
Click to expand...
Click to collapse
istipb said:
Yah bro really i had a bad luck . It was my favorite phone. But my phone was rooted and also the triangle was present so I am very much tensed about that.
Click to expand...
Click to collapse
just have ur finger's crossed for now dude and pray god that the service center people will overlook the issue and get ur phone rectified for u
hey bro does service center guys replaced your phone or solve ypur problem ??
i too have same problem
EMMC Bug
I used ROM Manager and it caused my mobile dead.........:<
it was out of warranty, I took my phone to repairer for JTAG but next day he returned my cell and said it has emmc bug ... what does it mean? and any solution plz Help .....................
It could mean he has taken your motherboard and replaced it with one that was dead.
Thanks fOr rePly........
But i've checked my motherboard is not replaced... is there any other possibility???
Or it is completeley useless?
---------- Post added at 02:53 PM ---------- Previous post was at 02:45 PM ----------
theunderling said:
It could mean he has taken your motherboard and replaced it with one that was dead.
Click to expand...
Click to collapse
ThanKx fOr reply...
But i dont think so he changed my board because i took my phone to another repairer he didn't told me that ur motherboard is replaced it seems like new...
... Plz Help ... Is JTAG is problem solving for all dead mobiles like s2?
If you need help you should be posting your exact model and what firmware you were on and what exactly happened!.
Ive had problems with rom manager once but easy to fix.
To OP: Next time, try using a jig for resetting your flash counter, so in case of problem you won't be
liable for voiding your guarantee with custom rom flashing, if you are able to reflash a stock rom before
sending it back to customer service.
It is 2$ and worth it (as it can also fix a few lesser bricking problems)
I flashed syiah 4.1.5 over my stock 4.0.4 everything is ok so far,i want to install the RR remix rom based 4.0.4 ,is safe? or to make a downgrade before to 4.0.3 and then to flash the RR?
Since you're running Siyah kernel, you're safe.
Sent from my GT-I9100
thank you
everst1 said:
I flashed syiah 4.1.5 over my stock 4.0.4 everything is ok so far,i want to install the RR remix rom based 4.0.4 ,is safe? or to make a downgrade before to 4.0.3 and then to flash the RR?
Click to expand...
Click to collapse
Just so you know
The developer of the rr rom includes a "safe" kernel with his rom.So although you will be on 4.0.4,his kernel will be automatically installed when you flash his rom.
Hello I am a proud owner of the SIII and I was wondering how brickable this devices is.
I had a Xperia X10 and Xperia Play before and restoring to stock was very easy and the phones were unbrickable even mid flashing I could still restore to stock.
How does the SIII go with this ?
With my previous devices I just needed to flash them with SEUS and that's it to go to stock now I read for samsung you need odin to flash back to stock and there is a flash counter you can reset the flash counter with triangle away I know that been reading much .
But yea using those methods and such is this device brickable or not or is it possible to flash it in recovery withouth any problems even with using triangle away? would be very disapointed if I would brick my device
Kind Regards
arcticmedia
unbrickable NO, but if you use commen sense you can flash away with odin/mobile odin for stock.....and CWM for any custom roms.
only bricks i have seen are people in the wrong forums flashing US firmwares or vise versa
arcticmedia said:
Hello I am a proud owner of the SIII and I was wondering how brickable this devices is.
I had a Xperia X10 and Xperia Play before and restoring to stock was very easy and the phones were unbrickable even mid flashing I could still restore to stock.
How does the SIII go with this ?
With my previous devices I just needed to flash them with SEUS and that's it to go to stock now I read for samsung you need odin to flash back to stock and there is a flash counter you can reset the flash counter with triangle away I know that been reading much .
But yea using those methods and such is this device brickable or not or is it possible to flash it in recovery withouth any problems even with using triangle away? would be very disapointed if I would brick my device
Kind Regards
arcticmedia
Click to expand...
Click to collapse
Samsung phones are known unbrickable( read Adam outler).except superbrick
Yes u can flash from cwm without increasing flash counter,also use "mobile Odin" without increasing flash counter.
And make a nandroid so u always can restore if problems occur during flashing
preety unbrickable if you use common sense and the right device. This fprum is for i-9300 international version.
With common sense in the highest gear: Almost unbrickable.*
Complete lack of common sense and using the wrong device (say GT-i9300T in a i9300 forum), then it's approx. 95% brickable*
Lack of common sense but with the right device: 68.5% brickable.*
* The statistics are made up and only for aesthetics.
I think everyone has already said it buddy, just use common sense and don't go flashing firmware for the US variant on a European/Asian device because inevitably....you will brick your phone, and when switching roms....take the time to sync with Google, it does help for when you come to restore your Google account. And when switching roms, although you don't have to, but I always do a full wipe to get rid of anything that might not be compatible with the version of Android you're about to flash, and then let Google decide what's restored and what isn't.
Remember....a £500 phone + common sense is better than no common sense and a phone that's useless. Because if you brick it....SAMSUNG WILL NOT REPAIR OR REPLACE IT lol
Sent from my GT-I9300 using xda premium
Samsung can repair it,at the same price as a new phone..
But search "j-tag" and a US firm comes up,for 40$(+postage) they will repair your phone,except superbrick(emmc corrupt)
Nearly unbrickable but a fair few users try really really hard to brick it .
First question is do you have an International I9300 if so proceed .
Many do not and flash I9300 on a non I9300 phone .
jje
JJEgan said:
Nearly unbrickable but a fair few users try really really hard to brick it .
First question is do you have an International I9300 if so proceed .
Many do not and flash I9300 on a non I9300 phone .
jje
Click to expand...
Click to collapse
Yup I have the international version GT-I9300 running I9300XXLH1
One bit of advice, to root,, use the cf-root, simple, easy, fool proof
If you use the correct thigs etc. for GT-I9300 you won't brick your phone, so mind using the right things and read and do the installation or whatever exactly like it's told in the turotials.
But nobody can garantee it! But you must be a big hero to brick your phone unrepairable
Does eMMC bug apply to newer versions of sgs2? i mean i bought mine 2 mounths ago brand new.
Read this post http://forum.xda-developers.com/showthread.php?p=28388184
If your phone runs 4.0.4 and one of those firmwares, it is susceptible to the bug.
Alternatively, you can download the got brick bug app and check if you have it.
Sent from my GT-I9100 using xda app-developers app.
If noobs on xda have taught me one thing, its that smartphones just aren't for everyone.
HAXTREME said:
Read this post http://forum.xda-developers.com/showthread.php?p=28388184
If your phone runs 4.0.4 and one of those firmwares, it is susceptible to the bug.
Alternatively, you can download the got brick bug app and check if you have it.
Sent from my GT-I9100 using xda app-developers app.
If noobs on xda have taught me one thing, its that smartphones just aren't for everyone.
Click to expand...
Click to collapse
neah i got i9100bulp8
and when i tested it with the got brick bug apk it sayd unknown or something like that .
evilian said:
neah i got i9100bulp8
and when i tested it with the got brick bug apk it sayd unknown or something like that .
Click to expand...
Click to collapse
Firstly, do you plan to flash custom roms/ kernels to your phone? If not, then you're worrying about the emmc bug for no reason at all.
If you are, and are worried about the bug, the simplest solution to ensuring you're in no risk of having your phone bricked 'coz of the emmc bug is to flash a 'safe' custom kernel like siyah or dorimanx via Odin. (tutorials for this can be found on searching the thread) That'll root your phone and you won't run the risk of your phone getting bricked due to the emmc bug even if the bug affects the firmware you're using.
evilian said:
neah i got i9100bulp8
and when i tested it with the got brick bug apk it sayd unknown or something like that .
Click to expand...
Click to collapse
Yeah mine got unknow too
i have samsung galay s2, ICS installed on it. instead of showing its internal USB storage as 11Gb , its showing 4.11Gb. i installed an app called
"exynos-mem bug checker". it says "this device is affected by the 'exynos-mem' bug issue".
what is actually the problem ? and whats the solution ?
whats the best way to get my lost memory back ??
m much worried abt it ..because i recently bought it.
kindly reply asap
Never heard of that but a flash or factory reset would do the trick.
Of course you might get bricked if you factory reset on 4.0.4.
Siyah v5 would help you get to the safe side tho.
Sent from the little guy
Bug Is better know as brick bug. You on firmware 4.0.4? Flash with Odin firmware 4.1.2 and you won't have the brick bug. Whatever you do don't factory reset your phone while on ICS. You need to read a lot more if your on that firmware. Sammobile is were you will get 4.1.2 jelly bean firmware. And don't mess up flashing with Odin. Before you do that read :thumbup:
Oh, you're right, I got mixed up with the internal space thing.
I stand corrected, I did hear about Brick bug.
Sent from the little guy
Judging by what you said in the OP, your phone IS affected by brickbug.
Just so you are 100% clear on this......
Brickbug IS a phone killer....no way back from it....as @andrewwright and @gastonw have both said.....DO NOT under ANY circumstances, perform ANY wipe while on ICS 4.0.4.
upgrade to JB 4.1.2 or roll back to ICS 4.0.3 as soon as safely possible.
Visit sammobile for the firmware and use Odin to flash it......but before using Odin, read everything you can find about it.....don't just rush blindly in, or you are likely to have other problems......good luck
Sent from my GT-I9100 using xda app-developers app
usb storage issue
hi guys .thanx a lot for quick response.i have upgraded to JB.
now the "exynos-mem bug" is gone.
BUT
the issue of USB storage still presist.. it still shows 4.11 GB of USB storage.
kindly suggest me a good some good solution to retrieve my memory. or atleast any way to get back the memory more than 4 Gb if not whole.
thanx in advance
maddie77 said:
hi guys .thanx a lot for quick response.i have upgraded to JB.
now the "exynos-mem bug" is gone.
BUT
the issue of USB storage still presist.. it still shows 4.11 GB of USB storage.
kindly suggest me a good some good solution to retrieve my memory. or atleast any way to get back the memory more than 4 Gb if not whole.
thanx in advance
Click to expand...
Click to collapse
dont you guys here have some 16 gb pit file for your devices, that shall allow to repartition the phone with odin.
tapatalked
rajman said:
dont you guys here have some 16 gb pit file for your devices, that shall allow to repartition the phone with odin.
tapatalked
Click to expand...
Click to collapse
hi there... i didnt get you ... please tell me the solution in detail if you know one !
rajman said:
dont you guys here have some 16 gb pit file for your devices, that shall allow to repartition the phone with odin.
tapatalked
Click to expand...
Click to collapse
The theory behind that idea is sound.....
But......
Flashing a pit file is seen as a LAST resort....
If it goes wrong, it'll have pretty much the same effect as a brickbug wipe.....turn the phone into an expensive paperweight.......
Sent from my GT-I9100 using xda app-developers app
Try out master clean of play store.
keithross39 said:
The theory behind that idea is sound.....
But......
Flashing a pit file is seen as a LAST resort....
If it goes wrong, it'll have pretty much the same effect as a brickbug wipe.....turn the phone into an expensive paperweight.......
so please tell me if therez a safe solution ?
Click to expand...
Click to collapse
alternate
keithross39 said:
The theory behind that idea is sound.....
But......
Flashing a pit file is seen as a LAST resort....
If it goes wrong, it'll have pretty much the same effect as a brickbug wipe.....turn the phone into an expensive paperweight.......
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
so please tell me if therez a safe solution ?
Not certain if this would work, but you could try odin flashing the JB leak test firmware @gastonw should be able to link you to it.......
I believe it formats (and repartitions?) during the flash, so it *could* be the solution you're looking for......somebody cmiiw
Edit.....here's the link.....
http://www.sammobile.com/2012/11/15/i9100xxlsj-–-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
It's a 3 part firmware, so it's not as simple as adding a single file to Odin, but if you read and follow the instructions in that link, you should be OK........
Sent from my GT-I9100 using xda app-developers app
gastonw said:
Oh, you're right, I got mixed up with the internal space thing.
I stand corrected, I did hear about Brick bug.
Sent from the little guy
Click to expand...
Click to collapse
brick bug issue is resolved now but
the issue of USB storage still presist.. it still shows 4.11 GB of USB storage.
kindly suggest me a good some good solution to retrieve my memory. or atleast any way to get back the memory more than 4 Gb if not whole.
kindly explain the solution in detail.
thanx in advance
Read my last comment fella.........
Sent from my GT-I9100 using xda app-developers app
---------- Post added at 09:14 PM ---------- Previous post was at 08:55 PM ----------
Actually.....just had a rethink about this.......
Here are the 'known' facts.......
1) you WERE on ICS 4.0.4
2) your phone was classed as 'at risk' from brickbug
3) you appear to have lost some storage space.
My (worst case scenario) guess is that you performed some sort of data wipe, and while it didn't kill your phone, it corrupted a portion of your storage. I'm guessing that if you now try to repartition the storage, you'll run into issues where the repartition *could* fail.......and you'll be left with an unusable phone......as it stands, you CAN use the phone, I'd be tempted to leave it that way, and maybe claim warranty with Samsung. Maybe @theunderling or @andrewwright or @gastonw or @Hopper8 can comment on this theory........
Sent from my GT-I9100 using xda app-developers app
Yeah, storage doesn't just go away.
Is there something you're not telling us? If there isn't, contact samsung/warranty.
Sent from the little guy
we've been facing the same issue on s advance while flashing 16 gb version without a specific pit file or checking repartition without one.
if you guys saying its risky on s2 i got that, it was just a clue how we solved it in s advance. flashing firmware with odin and correct pit file solved the memory shrinkage issue.
tapatalked
keithross39 said:
Read my last comment fella.........
Sent from my GT-I9100 using xda app-developers app
---------- Post added at 09:14 PM ---------- Previous post was at 08:55 PM ----------
Actually.....just had a rethink about this.......
Here are the 'known' facts.......
1) you WERE on ICS 4.0.4
2) your phone was classed as 'at risk' from brickbug
3) you appear to have lost some storage space.
My (worst case scenario) guess is that you performed some sort of data wipe, and while it didn't kill your phone, it corrupted a portion of your storage. I'm guessing that if you now try to repartition the storage, you'll run into issues where the repartition *could* fail.......and you'll be left with an unusable phone......as it stands, you CAN use the phone, I'd be tempted to leave it that way, and maybe claim warranty with Samsung. Maybe @theunderling or @andrewwright or @gastonw or @Hopper8 can comment on this theory........
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
okay ... let me more clear. i bought it from olx. at time of purchasing i didnt checked the USB storage. later on i realized that its showing less space. perhaps that guy(seller) did something to cellphone unknowingly. m not sure what he did.
PS: its warrenty is expired.
rajman said:
we've been facing the same issue on s advance while flashing 16 gb version without a specific pit file or checking repartition without one.
if you guys saying its risky on s2 i got that, it was just a clue how we solved it in s advance. flashing firmware with odin and correct pit file solved the memory shrinkage issue.
tapatalked
Click to expand...
Click to collapse
if you have previous experience that the method you explained did work then please explain the process step by step so that i can get rid of the problem.
maddie77 said:
if you have previous experience that the method you explained did work then please explain the process step by step so that i can get rid of the problem.
Click to expand...
Click to collapse
as i said b4, i have no experience with galaxy s2, what i've don is fixing s advance.