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
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.
i have a samsung galaxy 2 I9100 and i updated to andorid 4.0.4 then yesterday i tray to wipe using ClockWorkMod Recovery Touch v5.8.1.5 [I9100].zip and when i select wipe data my mobile shutdown and never start again even i want to start with Odin mode or Recover Mode but nothing my phone remains off i need help please
sorry to say but your SII is bricked ..the official ICS roms had this bug and many users ended with the same fate as you....i guess you missed all the warning sign boards here.
anto.danny said:
sorry to say but your SII is bricked ..the official ICS roms had this bug and many users ended with the same fate as you....i guess you missed all the warning sign boards here.
Click to expand...
Click to collapse
but there is no solution to my problem?
sir_blas said:
but there is no solution to my problem?
Click to expand...
Click to collapse
Yes there is, you need to send it in to service centre and have the motherboard replaced.
Didn't you see the brick bug about that rom splashed all over the threads here???
sir_blas said:
but there is no solution to my problem?
Click to expand...
Click to collapse
Samsung warranty. Or else a JTAG or whatever it is called. else board change.
drraptor said:
Samsung warranty. Or else a JTAG or whatever it is called. else board change.
Click to expand...
Click to collapse
If its the infamous brick bug, which it definitely looks to be, then JTAG is useless.
NanoSurfer said:
Yes there is, you need to send it in to service centre and have the motherboard replaced.
Didn't you see the brick bug about that rom splashed all over the threads here???
Click to expand...
Click to collapse
no i never see it im new at this forum thanks to all for the respouses thank you very much...
Will the device brick if I do "Factory reset" from Settings option?
Sent from my Thoughts using Telepathy :banghead:
ghadap said:
Will the device brick if I do "Factory reset" from Settings option?
Sent from my Thoughts using Telepathy :banghead:
Click to expand...
Click to collapse
Most likely if you're on stock 4.0.4.
i just test my device and its say that i have insane chip but memory test PASS without problem. Does its mean that my chip is from "damage line" but its not damage
If I have full stock firmware and kernel, and if I update phone via Kies only, Is there still brick bug possibility if I make factory reset?
Because this is scary and sick if this scenario is possible
Sent from my GT-I9100 using xda premium
PINki92 said:
If I have full stock firmware and kernel, and if I update phone via Kies only, Is there still brick bug possibility if I make factory reset?
Because this is scary and sick if this scenario is possible
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Only if you have stock 4.0.4.
4.0.3. is completely safe.
Sent from my GT-I9100
so i read on twitter the fix is on the way and someone told me that it's already here
read the general thread but couldn't find exactly what ROM or version solves this
can someone point it out for me so i can prevent a tragic death on my beloved s3?
thanks
RorixRebel said:
so i read on twitter the fix is on the way and someone told me that it's already here
read the general thread but couldn't find exactly what ROM or version solves this
can someone point it out for me so i can prevent a tragic death on my beloved s3?
thanks
Click to expand...
Click to collapse
This one. I9300XXELLA (4.1.2)
http://forum.xda-developers.com/showthread.php?t=1646610
Make sure you collect all info about it before you upgrade.
Why? Because people are saying that new boatloaders have new security patch which makes triangle away not to work.
thanks for the reply - i'll download it later on today and flash
not worried about the counter or anything, not like im planning to get rid of my s3 in the near future
RorixRebel said:
thanks for the reply - i'll download it later on today and flash
not worried about the counter or anything, not like im planning to get rid of my s3 in the near future
Click to expand...
Click to collapse
No need to worry about counter if you use stock recovery and stock kernel.
This boatloaders automatically set counter to 1 if you use custom kernel and custom recovery like CWM.
If you keep your phone in stock conditions then you are good.
rl421403 said:
This one. I9300XXELLA (4.1.2)
http://forum.xda-developers.com/showthread.php?t=1646610
Make sure you collect all info about it before you upgrade.
Why? Because people are saying that new boatloaders have new security patch which makes triangle away not to work.
Click to expand...
Click to collapse
Hello
Does this firmware patch fix the sudden death thing? I'm on supernexus rom, if I flash the stock one you posted, and then reflash the supernexus rom, will it still be fixed?
Thank you
Sent by GT-I9300 SuperNexus
omgbuffguy said:
Hello
Does this firmware patch fix the sudden death thing? I'm on supernexus rom, if I flash the stock one you posted, and then reflash the supernexus rom, will it still be fixed?
Thank you
Sent by GT-I9300 SuperNexus
Click to expand...
Click to collapse
Yes, it fixes sudden death as well as EXYNOS bug.
If you flash this stock rom then it means you are loading new bootloaders. So the changes in bootloaders will be permanent. If you flash your rom again then it will not effect bootloaders and you are protected for these bugs.
But just to be clear, new bootloaders have a new security measure. If you have CWM/custom recovery and custom kernel then your flash counter will never be 0. means you will void your warranty. Although it will not make any effect on functioning of your phone. So be warned.
Are you sure it's in the new bootloaders ? Coz I never flashed the new bootloaders and us the same with the old ones (bl) and my count is always same on custom recovery.
Sent from my GT-I9300 using Tapatalk 2
rl421403 said:
Yes, it fixes sudden death.
Click to expand...
Click to collapse
You don't know that, nobody can confirm this yet.
Enviado desde mi GT-I9300 usando Tapatalk 2
This hasn't been confirmed as a fix for sudden death yet. So far it's all speculation.
Sent from my GT-I9305 using xda app-developers app
Obagleyfreer said:
This hasn't been confirmed as a fix for sudden death yet. So far it's all speculation.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Wild speculation at that.
The hysteria around this is wholly without evidence and anyone stating that this is a fix is guilty of seriously misleading folk - rl421403 as charged.
See here for an informed view by Andrew Dodd http://forum.xda-developers.com/showpost.php?p=36242164&postcount=395
hi,
I was about to root my s3 using the toolkit, i've been reading guides and stuff. I'm not new to rooting but do it just in case so that i don't take any wrong steps.
I've come across many threads where people have lost their imei after flashing roms. most of those threads were on us based carrier s3.
so just wanted to ask if international s3 - uk version is also prone to deleting its imei.. haha because i think i will avoid rooting if it is.
Battery life for me has been an issue since the start. I'm a heavy user so maybe rooting and installing another kernel, undervolting etc would give me few hours etc.
thanks :laugh:
tele27 said:
hi,
I was about to root my s3 using the toolkit, i've been reading guides and stuff. I'm not new to rooting but do it just in case so that i don't take any wrong steps.
I've come across many threads where people have lost their imei after flashing roms. most of those threads were on us based carrier s3.
so just wanted to ask if international s3 - uk version is also prone to deleting its imei.. haha because i think i will avoid rooting if it is.
Battery life for me has been an issue since the start. I'm a heavy user so maybe rooting and installing another kernel, undervolting etc would give me few hours etc.
thanks :laugh:
Click to expand...
Click to collapse
Yes, just make sure you take an EFS backup. Losing IMEI is the least of the GT-i9300's problems
Philz recovery does EFS backups. I recommend you use this recovery http://forum.xda-developers.com/showthread.php?t=2002953
great thanks for you reply... i will follow the guide!
rootSU said:
Yes, just make sure you take an EFS backup. Losing IMEI is the least of the GT-i9300's problems
Philz recovery does EFS backups. I recommend you use this recovery http://forum.xda-developers.com/showthread.php?t=2002953
Click to expand...
Click to collapse
Then whats the worse of the S3 issue's? :b
SnowPluralism said:
Then whats the worse of the S3 issue's? :b
Click to expand...
Click to collapse
The wear levelling eMMC catastrophic failure bug in 0xf1 eMMC firmware, or SDS if you will.
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
The wear levelling eMMC catastrophic failure bug in 0xf1 eMMC firmware, or SDS if you will.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I knew you were going to say that
And i agree
And it get me angry as hell since i have it ...
And sometimes i feel like ... "gonna try cm10.1" and then i remember that my phone can die at any time and i have to be on stock ... even they say they patched the bootloader and kernel with update 7 to fix the issue ... i dont feel safe even so ...
Sent from my GT-I9300 using xda premium
SnowPluralism said:
I knew you were going to say that
And i agree
And it get me angry as hell since i have it ...
And sometimes i feel like ... "gonna try cm10.1" and then i remember that my phone can die at any time and i have to be on stock ... even they say they patched the bootloader and kernel with update 7 to fix the issue ... i dont feel safe even so ...
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
you're just as safe on stock as on CM. If there's any fix in the stock kernel - it's included in all custom kernels too
Glebun said:
you're just as safe on stock as on CM. If there's any fix in the stock kernel - it's included in all custom kernels too
Click to expand...
Click to collapse
Yes but service center will see the red triangle since i have the new bootloader if he stucks on bootloop
Sent from my GT-I9300 using xda premium
wait, wait, let me get this straight - you're a recognized contributor on xda but you're running a fully stock non-rooted phone without a custom recovery? really?
all the evidence points to the fact that the fix is in the kernel, not the bootloader, so you can downgrade the bootloader with a simple cwm flash
Glebun said:
wait, wait, let me get this straight - you're a recognized contributor on xda but you're running a fully stock non-rooted phone without a custom recovery? really?
all the evidence points to the fact that the fix is in the kernel, not the bootloader, so you can downgrade the bootloader with a simple cwm flash
Click to expand...
Click to collapse
Helll no xDDDD !!!
Syah kernel rooted with syah modded cwm xD
And now everything about that i just prefer to play safe until its prooven that sds is "fixed"
Sent from my GT-I9300 using xda premium
phew
SnowPluralism said:
i just prefer to play safe until its prooven that sds is "fixed"
Click to expand...
Click to collapse
but you just said you're on Siyah. But you don't use CM because of SDS? either I misunderstood you or this makes no sense
Glebun said:
phew
but you just said you're on Siyah. But you don't use CM because of SDS? either I misunderstood you or this makes no sense
Click to expand...
Click to collapse
No theres no misunderstooding ... i think its better ... if he has to die. To die in stock but that is just for know the phone is new and im 21 and it came out of my pocket so i take really good care of it ... in some time ... cm and perhaps ill make him a rom :b
Sent from my GT-I9300 using xda premium
well FYI, there's no point in that. as long as you're using Siyah, CM or Stock don't have any effect on SDS. like, at all
He's right - no point.
There is a fix in the bootloader too, but this only affects your use of download mode. If you have a fixed kernel and recovery, you should be fine.
I keep an ALF6 bootloader installed to keep warranty in any OTHER situation so I have 0 flash counter (and I just avoid writing NAND from download mode).
if I get SDS, either I get FULL SDS (phone completely dead) or I get HALF SDS, when status shows as custom, even if unrooted. Having CM is no more a lose than stock.
I already had my Mobo replaced last November though. Still go 0xf1
rootSU said:
He's right - no point.
There is a fix in the bootloader too, but this only affects your use of download mode. If you have a fixed kernel and recovery, you should be fine.
I keep an ALF6 bootloader installed to keep warranty in any OTHER situation so I have 0 flash counter (and I just avoid writing NAND from download mode).
if I get SDS, either I get FULL SDS (phone completely dead) or I get HALF SDS, when status shows as custom, even if unrooted. Having CM is no more a lose than stock.
I already had my Mobo replaced last November though. Still go 0xf1
Click to expand...
Click to collapse
Im on xella with red triangle can u pm a "resetable" bootloader?
Sent from my GT-I9300 using xda premium
SnowPluralism said:
Im on xella with red triangle can u pm a "resetable" bootloader?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
here you go, have a look at this thread - http://forum.xda-developers.com/showthread.php?t=2083860
mikep99 said:
here you go, have a look at this thread - http://forum.xda-developers.com/showthread.php?t=2083860
Click to expand...
Click to collapse
Thanks mate
Sent from my GT-I9300 using xda premium