Related
http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/
Maybe someone who is a little more savvy in this field could take a look?
Here is a very good article and discussion about the issue:
http://forum.xda-developers.com/showthread.php?t=1644364
Sent from my SGH-T989 using xda premium
this is kinda scary but so far I never had any problem
We don't even have any kernel source. There is a leaked kernel but that didn't cause any brick in our devices. Also note that the article does not mention sgh t989 or sgh 727 and all its sub variants. If this was the case for us you would see many more "[Q] plz halp I haz brick " threads
Sent from my SGH-T989 using XDA
Hey guys. I just came over from the Sprint version of this phone (Epic 4G touch), and while I know that this article dosen't say that it pertains to our device specifically, one of the devs over there got in touch with samsung about the issues. You can see their progress here:
http://forum.xda-developers.com/showthread.php?t=1644364
For those who don't want to read (and I don't blame you if you don't want to, it's heavy stuff and I needed to have it explained to me), long story short: The memory chips (known as the EMMC) in the phone have their own firmware embedded in them, independent of the ROM, kernel, modem, etc. In that firmware, there's a bug that writes a string of zeros to an area of the firmware itself, kind of a self distrusting thing. It's only for certain revisions of the EMMC firmware, and it's only triggered by a specific low-level wipe function that is commonly used in recoveries (I'm not sure which, one of the partition wipes I think), and it for some reason seems to happen more with an ICS based kernel more than in a GB.
Given the nature of EMMC chips and the fact that multiple devices might share these same physical type of EMMC memory chips, it's hard to say how many different kinds of phones and devices might be affected, but it's safer to assume that we might be, rather than to think that we're safe based on this article alone.
There's no official solution as of yet, as far as I know. Samsung has started to patch their 4.x kernels to work around this specific wipe function, thus avoiding triggering the bug, and I think this is because rewriting the EMMC firmware itself is more risky and perhaps harder to do on a wide scale, but again, I'm not sure of their reasons. But, we do know that they're working to find some way around the bugs, and those who built custom kernels also removed/modified that wipe command to work around this bug with success.
Again, I know this doesn't say that it applies to our phones, but because of what was discovered on the Epic 4G touch, I believe that it *may* apply to many, many Samsung phones and devices, and just to be safe, I figure I should share this with you all.
The solution that we were using for time being was: never, ever do any recovery functions from a ICS based kernel/recovery. Always ODIN a GB based kernel/recovery to do what you need to do, then flash the proper ICS back. Kind of tedious, but it worked and prevented me from ever bricking when a LOT of other people were. Food for thought, everyone
TL;DR: You should probably avoid doing anything in an ICS based recovery/kernel on any Samsung device until we hear from them that they've worked out this bug.
kahm said:
Hey guys. I just came over from the Sprint version of this phone (Epic 4G touch), and while I know that this article dosen't say that it pertains to our device specifically, one of the devs over there got in touch with samsung about the issues. You can see their progress here:
http://forum.xda-developers.com/showthread.php?t=1644364
For those who don't want to read (and I don't blame you if you don't want to, it's heavy stuff and I needed to have it explained to me), long story short: The memory chips (known as the EMMC) in the phone have their own firmware embedded in them, independent of the ROM, kernel, modem, etc. In that firmware, there's a bug that writes a string of zeros to an area of the firmware itself, kind of a self distrusting thing. It's only for certain revisions of the EMMC firmware, and it's only triggered by a specific low-level wipe function that is commonly used in recoveries (I'm not sure which, one of the partition wipes I think), and it for some reason seems to happen more with an ICS based kernel more than in a GB.
Given the nature of EMMC chips and the fact that multiple devices might share these same physical type of EMMC memory chips, it's hard to say how many different kinds of phones and devices might be affected, but it's safer to assume that we might be, rather than to think that we're safe based on this article alone.
There's no official solution as of yet, as far as I know. Samsung has started to patch their 4.x kernels to work around this specific wipe function, thus avoiding triggering the bug, and I think this is because rewriting the EMMC firmware itself is more risky and perhaps harder to do on a wide scale, but again, I'm not sure of their reasons. But, we do know that they're working to find some way around the bugs, and those who built custom kernels also removed/modified that wipe command to work around this bug with success.
Again, I know this doesn't say that it applies to our phones, but because of what was discovered on the Epic 4G touch, I believe that it *may* apply to many, many Samsung phones and devices, and just to be safe, I figure I should share this with you all.
The solution that we were using for time being was: never, ever do any recovery functions from a ICS based kernel/recovery. Always ODIN a GB based kernel/recovery to do what you need to do, then flash the proper ICS back. Kind of tedious, but it worked and prevented me from ever bricking when a LOT of other people were. Food for thought, everyone
TL;DR: You should probably avoid doing anything in an ICS based recovery/kernel on any Samsung device until we hear from them that they've worked out this bug.
Click to expand...
Click to collapse
Finally someone with a brain! Thanks for the post
Sent from my SGH-T989 using xda premium
Scary stuff indeed, has anyone confirmed that our devices (T989) is affected by this bug?
Back on the original Epic we used Odin to get the next version. I think it was 2.1 to 2.2 roms. I've always wondered how safe it was to revert to GB by flashing after installing ICS
Sent from my SGH-T989 using xda premium
[Q] plz halp I haz brick
Disregard. Funny how you figure out your issue just seconds after you post and open yourself up to ridicule.
DOH!
mharmon said:
I seem to have hard-bricked my SGH-T989 phone after flashing task650-aokp-Build-36. I don't know if it's a superbrick, but nothing I can do seems to make any difference. The phone does not seem to respond and does not seem to power off, power on or go into download mode. I have swapped with a known good battery and I know that's not the issue. I've tried using a USB jig and that doesn't help. I've contacted Samsung and I should be shipping it to them Monday.
If anyone has any advice, I'm willing to try anything otherwise I'm going to take my lumps and ship my phone off.
Click to expand...
Click to collapse
Pull your battery sd card and sim card out. leave phone sitting with everything pulled for about an hour. put it back together and try again. make sure your battery is charged for sure. it would suck if it was nothing but a dead battery
Sent from my SAMSUNG-SGH-T989 using xda premium
Micronads said:
Pull your battery sd card and sim card out. leave phone sitting with everything pulled for about an hour. put it back together and try again. make sure your battery is charged for sure. it would suck if it was nothing but a dead battery
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks for the quick response. I've tried pulling the battery, USB jig, etc. and can't get it to power on, off or go into download mode. I know what I did wrong. I made a rookie mistake and flashed a ROM meant for my AT&T I777. I feel stupid for bricking my phone.
mharmon said:
Thanks for the quick response. I've tried pulling the battery, USB jig, etc. and can't get it to power on, off or go into download mode. I know what I did wrong. I made a rookie mistake and flashed a ROM meant for my AT&T I777. I feel stupid for bricking my phone.
Click to expand...
Click to collapse
Sounds like you are fizzucked then. Sorry to hear that. That is what sucks about having different phones and flashing stuff. Got to keep track of what is what.
Sent from my Galaxy SII T-mobile using xda premium
Micronads said:
Sounds like you are fizzucked then. Sorry to hear that. That is what sucks about having different phones and flashing stuff. Got to keep track of what is what.
Sent from my Galaxy SII T-mobile using xda premium
Click to expand...
Click to collapse
Yeah sounds dead to me. Send in for warranty. Oh well, stuff happens. Good luck to you!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Id rather risk bricking than rock without 4.04
Sent from my SGH-T989 using xda premium
Nobody has said it is necessary applicable to this device.
jim93 said:
Nobody has said it is necessary applicable to this device.
Click to expand...
Click to collapse
You're right, it doesn't say it's applicable to our device. But it also doesn't say our device is one of the safe GS2 variants. As you can see in my signature, I'm also using 4.0.4. And if you read my post history, I recommend it to everyone. I'm just saying that it hasn't been proven safe yet, but there's also no proof its dangerous either.
Sent from my SGH-T989 using xda premium
ICS has been flashed to these phones probably a half million times by now. If it was causing bricks we would have heard about it.
Sent from the iPhone graveyard.
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
kahm said:
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
Click to expand...
Click to collapse
Also, people should know that the listed phones in the OP are Exynos based and T989, i727/r and i717 are Qualcomm based. This has been discussed in the skyrocket forums and some devs have explained that.
Just my 2 cents.
kahm said:
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
Click to expand...
Click to collapse
The brick in this thread was due to flashing an i777 rom to a t989. Flashing an i777 rom to t989 regardless of OS will brick your phone.
It seems to be all exynos based, but thanks for the heads up, man.
Hi everybody,
I bought a Note 2 in october 2012. I installed the ROM HD Revolution. Until now there was no problem.
Few days ago, my screen has swiched off and there was lot of reds pixels everywere on the screen.
The phone of course was rooted and the garantly not applicable.
So in the samsung shop, i explain that the phone was rooted... The techniciens has puted a new screen thinking that the problem was coming from a screen hardware. This new screen has well worked during 20 mn, after that, same trouble, the screen was killed....
My phone was sent to another tehcniciens ( more specialists and i think, working directly with samsung) in france, who can works on the motherboard. But just before to sent it, the technical personnal has succefuly replace the rom Revolution by another official ROM by Odin. (In order to keep my garantly.....wonderful techniciens)
Today the phone was return to me, with just a new screen. The third screen after mine who was killed in first.
No motherboard trouble, no graphic chipset trouble was fixed, only the HD Revolution ROM who is apparently , and i 'am sure now, has killed the screen
I'am not able to explain why and how, I am not found on the web or another forum the same trouble.
Somebody know what's happened?
thanks
You might want to contact the developer, but I doubt the rom was the issue.
Sent from my SAMSUNG-SGH-I317 using xda premium
silentecho13 said:
You might want to contact the developer, but I doubt the rom was the issue.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I'am sure, very sure that the problem on the screen is due to the ROM Revolution, otherwise explain me why the third screen has no trouble after changing only the ROM with the lastest samsung ROM?
The official technicians do try to convince you that a custom ROM is the cause of your problem. Not making a judgement on whether this was what happened in your case, but just my personal opinion.
I am in India, where anyway Sammy tries to avoid taking responsibility however possible. One of my friend had sds on his s3, and the guys from Samsung tried to refuse him warranty on the basis that they believed he had a custom firmware. They were adamant on this even on his pointing out that thousands had had this even on the stock ROM, and thus could not be in any way related to flashing a custom firmware. Only when he threatened them with legal action (as they couldn't prove it was flashed anyway) did they finally took it in for repairs.
My advice is, check out the devs thread for the ROM, if its a genuine problem then it is sure to be mentioned by someone there.
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
SacGuru said:
The official technicians do try to convince you that a custom ROM is the cause of your problem. Not making a judgement on whether this was what happened in your case, but just my personal opinion.
I am in India, where anyway Sammy tries to avoid taking responsibility however possible. One of my friend had sds on his s3, and the guys from Samsung tried to refuse him warranty on the basis that they believed he had a custom firmware. They were adamant on this even on his pointing out that thousands had had this even on the stock ROM, and thus could not be in any way related to flashing a custom firmware. Only when he threatened them with legal action (as they couldn't prove it was flashed anyway) did they finally took it in for repairs.
My advice is, check out the devs thread for the ROM, if its a genuine problem then it is sure to be mentioned by someone there.
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
aquasirius said:
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
Click to expand...
Click to collapse
I suggest you verify on the forum thread and contact the dev. I highly doubt its the rom. I imagine for what you say to be possibly its not rom related but kernel and would require some sort of color adjustment hack of sorts, even then I highly doubt it as more users would have experienced the same. As for your proof from samsung means nothing. I've sent devices and computers out to warranty and the document says one thing but when I take it apart I see things where changed that do not reflect what the work order says. Not saying its the case just saying take it with a grain of salt.
I can't seem to find the rom your talking about.
prbassplayer said:
I suggest you verify on the forum thread and contact the dev. I highly doubt its the rom. I imagine for what you say to be possibly its not rom related but kernel and would require some sort of color adjustment hack of sorts, even then I highly doubt it as more users would have experienced the same. As for your proof from samsung means nothing. I've sent devices and computers out to warranty and the document says one thing but when I take it apart I see things where changed that do not reflect what the work order says. Not saying its the case just saying take it with a grain of salt.
I can't seem to find the rom your talking about.
Click to expand...
Click to collapse
It was the REVOLUTION HD Rom.
You think that the Samsung technicians when they changed the screen after the other first technicians has not been honnest?
It's incredible, i don't believe in this idea... I cannot see the interest... But if you are talking about the kernel maybe it yes...
It's a crazy story...
HD Revolution....? wait.. isnt it for a international version of Note 2?
No wonder why your phone is acting up. Flashing almost non compatible ROM on your device doesnt give you rights to discredit Dev.
I believe he is talking about this rom that is not in the att section.
http://forum.xda-developers.com/showthread.php?t=1925402
OP, when flashing did you happen to flash anything else such as that gpu rendering thing they have on that page? Also, any extreme overclocking or anything?
Sent from the Bacon Pope's Galaxy Note 2
Well then if that is the rom there is your problem. Your lucky Note II in general share the same SoC else you would have hard bricked. I suggest you do your research correctly before saying something broke your device. In the end its your responsability to know what you are flashing and even if said rom/kernel/mod does break your device its your fault, you flashed it not the developer. Its a risk we all take when modifying our devices.
cwhitney24 said:
I believe he is talking about this rom that is not in the att section.
http://forum.xda-developers.com/showthread.php?t=1925402
OP, when flashing did you happen to flash anything else such as that gpu rendering thing they have on that page? Also, any extreme overclocking or anything?
Sent from the Bacon Pope's Galaxy Note 2
Click to expand...
Click to collapse
I use the recovery mode after have put the zip's ROM on my SD card.
And i never use the o/c
I 'am sure that the trouble has been caused by the Kernel or the ROM... I don't remember what was the kernel... i thinking...
prbassplayer said:
Well then if that is the rom there is your problem. Your lucky Note II in general share the same SoC else you would have hard bricked. I suggest you do your research correctly before saying something broke your device. In the end its your responsability to know what you are flashing and even if said rom/kernel/mod does break your device its your fault, you flashed it not the developer. Its a risk we all take when modifying our devices.
Click to expand...
Click to collapse
I know that, but on the french forum we are several with this ROM, i'am looking for the same trouble in France: nothing...
I'am wondering what's happened and i 'am not here to cry but to exlpain you this trouble and i 'am trying to have an elaborate conversation in order to find the origin, I find it normal beetween enthusiast....
aquasirius said:
I know that, but on the french forum we are several with this ROM, i'am looking for the same trouble in France: nothing...
I'am wondering what's happened and i 'am not here to cry but to exlpain you this trouble and i 'am trying to have an elaborate conversation in order to find the origin, I find it normal beetween enthusiast....
Click to expand...
Click to collapse
Well you are disproving yourself. If no other LTE variant on that rom has had similar problems then its not the rom/kernel/mod. It was a fluke of bad hardware with lazy techs (don't want to generalize its easier to blame it on an external source than actually debugging). Second your arguments are null in the end becaus:
mike1986. said:
No mate, LTE version is not supported.
Click to expand...
Click to collapse
That includes I7105, I317[M] and T889[V]. It might work, but probably not 100% and the developer simply offers no support for it.
aquasirius said:
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
Click to expand...
Click to collapse
Relax man, I did not think you were lying, neither did I accuse you of it, I merely asked you to, and personally believe,that the developers on this forum (who are people like you and me) are anyday more trustworthy than repair men who are from samsung or freelancers (read people bent on profiting from me screwing up my cellphone). Thus I asked you to visit the developers thread and look for comments about the issues you were facing, that is what I would've done.
Apparently you flashed a ROM which was not meant for your particular model. Whether that is true or not, I am sorry for all the trouble you had to go through with the engineers and all. I hope your note 2 functions great from now on.
Je vous présente mes meilleurs vœux pour l'année 2013
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
prbassplayer said:
Well you are disproving yourself. If no other LTE variant on that rom has had similar problems then its not the rom/kernel/mod. It was a fluke of bad hardware with lazy techs (don't want to generalize its easier to blame it on an external source than actually debugging). Second your arguments are null in the end becaus:
That includes I7105, I317[M] and T889[V]. It might work, but probably not 100% and the developer simply offers no support for it.
Click to expand...
Click to collapse
It was the REVOLUTION HD 4, installed in november, not the 8 or the 9
I used the ROM perfectly adapted for my note 2
Now my note is working without problem with the last samsung rom with 4.1.2 android version.
Nothing has been changed into my phone (hardware etc...) just a new ROM...
And never else was happened on my phone before the trouble.
aquasirius said:
It was the REVOLUTION HD 4, installed in november, not the 8 or the 9
I used the ROM perfectly adapted for my note 2
Now my note is working without problem with the last samsung rom with 4.1.2 android version.
Nothing has been changed into my phone (hardware etc...) just a new ROM...
And never else was happened on my phone before the trouble.
Click to expand...
Click to collapse
Man you said your on a 3rd screen so don't say hardware hasn't changed. This is not counting for anything that changed when you shipped out. In the end it doesn't matter if it was a November rom, or January rom its based on the N7100 firmware not N7105 therefor although it might work probably won't work 100%. You are so caught up that it has to be the rom that you are ignoring key points in your argument. It is more likely to be a hardware problem than software. I'm not saying it wasn't the rom/kernel combination because its possible, who knows, however its a rom based on Sammy firmware that isn't made for your device. Plain and simple.
Cheers
prbassplayer said:
Man you said your on a 3rd screen so don't say hardware hasn't changed. This is not counting for anything that changed when you shipped out. In the end it doesn't matter if it was a November rom, or January rom its based on the N7100 firmware not N7105 therefor although it might work probably won't work 100%. You are so caught up that it has to be the rom that you are ignoring key points in your argument. It is more likely to be a hardware problem than software. I'm not saying it wasn't the rom/kernel combination because its possible, who knows, however its a rom based on Sammy firmware that isn't made for your device. Plain and simple.
Cheers
Click to expand...
Click to collapse
I mean hardware (motherboard, chipset,....etc) of course screens are hardware.
And I have 7100 and the ROM I used was for the 7100.
The ROM has broken something on my phone, i don't know what, maybe my english is too bad and i'am not able to do understand my story with the corrects words
I'am not a noob to choose the wrong ROM for my note 2...
we thought that the problem has came from a voltage problem beetween the screen and the GPU or the chipset...
Without any else action from me (no o/c, no brutality) i cannot see anything else....
I think several people have made good points though who knows, it's also possible some part of your os got corrupted and it killed the screens. I've seen a lot of wierd stuff happen with computers over the years. I repair phones, desktops and laptops myself and I continue to see new problems. Some of it I figure out, some I never do.
Another explanation that occurs to me - a transitory short that fried the screens. Did you drop or jar the phone? Spill fluid? Have high or extremes of temp or humidity ? **** happens. Intermitant problems are the absolute worst to track down. If it is something lurking in the hardware and they didn't fix it completely, it may say hello to you again! Problem devices often stay problem devices even after a number of "final" repairs that work for a while. That's why if something like that happened to me, I'd be happier with a replacement device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Dumbo53 said:
I think several people have made good points though who knows, it's also possible some part of your os got corrupted and it killed the screens. I've seen a lot of wierd stuff happen with computers over the years. I repair phones, desktops and laptops myself and I continue to see new problems. Some of it I figure out, some I never do.
Another explanation that occurs to me - a transitory short that fried the screens. Did you drop or jar the phone? Spill fluid? Have high or extremes of temp or humidity ? **** happens. Intermitant problems are the absolute worst to track down. If it is something lurking in the hardware and they didn't fix it completely, it may say hello to you again! Problem devices often stay problem devices even after a number of "final" repairs that work for a while. That's why if something like that happened to me, I'd be happier with a replacement device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Maybe you right, and the phone has been exposed every time in good condition, and never droped or jared. I will see with the time if it was a another hardware problem.
I think actually the association ROM/kernel has revealed an intrinseq hardware problem on my phone and maybe later even with a samsung rom the problem should be appear again....
aquasirius said:
I mean hardware (motherboard, chipset,....etc) of course screens are hardware.
And I have 7100 and the ROM I used was for the 7100.
The ROM has broken something on my phone, i don't know what, maybe my english is too bad and i'am not able to do understand my story with the corrects words
I'am not a noob to choose the wrong ROM for my note 2...
we thought that the problem has came from a voltage problem beetween the screen and the GPU or the chipset...
Without any else action from me (no o/c, no brutality) i cannot see anything else....
Click to expand...
Click to collapse
Wait.....Your Note 2 is an N7100? Then why did you come to an i317 forum to complain about a ROM somehow breaking your screen?
If you really think you have a legitimate concern that a ROM may have damaged your phone in some way, contact the developer. Maybe it has happened before. Maybe the developer can make changes to prevent it from happening to others. What you probably shouldn't do is to make claims that a ROM damaged your phone on a forum for a different model of phone.
I'm just curious if anyone else here besides me is still on the ATT 4.1.1 or 4.1.2 only because they are still skeptical about updating or just refuse to accept it, and the reasons why. I feel like I'm the bad guy around here because I refuse to rush and play with the latest toy (Ooops, I mean the 4.3 update).
I'm even reading some of the members, and even some devs here wondering why some people are refusing to update, because you can do just about anything on the new bootloader that you can do on the old ones.
Well, I always thought that us rooters who are non-developers are not suppose to accept OTA updates from our carriers, and should only be flashing the Roms from our developers (good devs by the way). OTAs tend to fix previous issues and attempt to make the phones more secure, but at the same time, create new issues and further lock down the phones.
Look at all the posts around here right now that are just filled with 4.3 issues. One of the most common for example: (I'm having issues, have soft bricked, or just don't like the update?) Is there a way to flash back to complete 4.3 stock so that I can start over? No! And without any official firmware released from AT&T, if something goes wrong with your phone, then all you have to flash is a custom ROM, which I was taught that we should be doing any way, while avoiding the OTAs.
I just want to see here if there is anyone else thinking the same way and why, or is this just going to turn into people who OTA-ed becoming defensive.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
shortydoggg said:
I'm just curious if anyone else here besides me is still on the ATT 4.1.1 or 4.1.2 only because they are still skeptical about updating or just refuse to accept it, and the reasons why. I feel like I'm the bad guy around here because I refuse to rush and play with the latest toy (Ooops, I mean the 4.3 update).
I'm even reading some of the members, and even some devs here wondering why some people are refusing to update, because you can do just about anything on the new bootloader that you can do on the old ones.
Well, I always thought that us rooters who are non-developers are not suppose to accept OTA updates from our carriers, and should only be flashing the Roms from our developers (good devs by the way). OTAs tend to fix previous issues and attempt to make the phones more secure, but at the same time, create new issues and further lock down the phones.
Look at all the posts around here right now that are just filled with 4.3 issues. One of the most common for example: (I'm having issues, have soft bricked, or just don't like the update?) Is there a way to flash back to complete 4.3 stock so that I can start over? No! And without any official firmware released from AT&T, if something goes wrong with your phone, then all you have to flash is a custom ROM, which I was taught that we should be doing any way, while avoiding the OTAs.
I just want to see here if there is anyone else thinking the same way and why, or is this just going to turn into people who OTA-ed becoming defensive.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For starters i can't imagine why anyone who is rooted and running a custom ROM would ever dream of installing an official OTA. By the time the carrier's have had time to update their own ROM and distribute the update it will have long been incorporated into most custom ROM's. Point and case is 4.3 (which i have been running thanks to Task650 for many months)...boom all of a sudden you are stuck with a bootloader that you cannot change, or how about the case of the S4's who blindly or unknowing installed an OTA that gives them a locked bootloader that cant be downgraded (in the case of those of us with carriers who are evil bastards). The only case where i would personally find it 'acceptable' to install official OTA's is someone who has no interest in rooting or installing any custom software to their device. Yes the current S3 bootloader is rootable but one day, probably the next (if there is one) update i would imagine it will be locked down like the new devices. Its sad to say but the direction Google seems to be moving all Android devices may end up this way which will be a dark day indeed.
dntesinfrno said:
....Its sad to say but the direction Google seems to be moving all Android devices may end up this way which will be a dark day indeed.
Click to expand...
Click to collapse
I don't think it's Google locking the devices down. It's the manufacturers: Samsung, HTC, Motorola, etc... that are incorporating the locked bootloaders. I may be wrong, but that's the way it seems.
jack man said:
I don't think it's Google locking the devices down. It's the manufacturers: Samsung, HTC, Motorola, etc... that are incorporating the locked bootloaders. I may be wrong, but that's the way it seems.
Click to expand...
Click to collapse
Yes currently its the manufacturers, at the behest of the carriers...hence why att and verizon are locked on the s4 and up samsung devices but not sprint or tmo. I was simply stating that if things continue to go the way they seem to be with googles decisions moving forward with android it could end up that way.
They can lock em down but you know some talented dev will find a way in
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
rumrnr62 said:
They can lock em down but you know some talented dev will find a way in
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
True, but that can take months, and until then, you're stuck.
Can always buy a dev version or a nexus
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
I'll wait until the dev 4.3 rom stable then flash. Not much difference IMO.
ibuddler said:
I'll wait until the dev 4.3 rom stable then flash. Not much difference IMO.
Click to expand...
Click to collapse
Same here.
I wonder if for some reason another toy (Ooops, update) comes to this phone, will the rooters who OTA-ed, and then re-rooted or flashed another ROM (and tripped their new warranty bit counters in the process) be able to receive the new update, or will it be blocked because of the counter increment, and once again, will have to rely on custom ROMs, which they should already be doing?
shortydoggg said:
I'm just curious if anyone else here besides me is still on the ATT 4.1.1 or 4.1.2 only because they are still skeptical about updating or just refuse to accept it, and the reasons why. I feel like I'm the bad guy around here because I refuse to rush and play with the latest toy (Ooops, I mean the 4.3 update).
I'm even reading some of the members, and even some devs here wondering why some people are refusing to update, because you can do just about anything on the new bootloader that you can do on the old ones.
Click to expand...
Click to collapse
...Anything, except flashing back to stock for reflashing purposes or for warranty service or resetting the Knox warranty bit. OTA may also damage resale value, among other downsides.
shortydoggg said:
Well, I always thought that us rooters who are non-developers are not suppose to accept OTA updates from our carriers, and should only be flashing the Roms from our developers (good devs by the way). OTAs tend to fix previous issues and attempt to make the phones more secure, but at the same time, create new issues and further lock down the phones.
Look at all the posts around here right now that are just filled with 4.3 issues. One of the most common for example: (I'm having issues, have soft bricked, or just don't like the update?) Is there a way to flash back to complete 4.3 stock so that I can start over? No! And without any official firmware released from AT&T, if something goes wrong with your phone, then all you have to flash is a custom ROM, which I was taught that we should be doing any way, while avoiding the OTAs.
I just want to see here if there is anyone else thinking the same way and why, or is this just going to turn into people who OTA-ed becoming defensive..
Click to expand...
Click to collapse
There are diverse camps among the rooters & other members here. Through my GS1, GS2 & GS3 I've used mostly debloated stock TW roms; for work, on the road constantly & needing a maximum stable daily driver; like other stock TW enthusiasts.
Apart from user (flashing) errors, the stability, the flexibility & connectivity complaints you cited are what I measured against when deciding to flash a 4.3 rom, kernel & modem from |ROM|Bootloader|Kernel|Modem| AT&T Official 4.3 MJB |24 Nov 2013| .
What designgears, upndwn4par, loserskater & the others have posted on multiple threads I read & reread here before flashing allowed me to attempt the 4.3 upgrade with a solid backout plan & maximum control, reaching my desired result:
Stable, debloated (by me, it's personal) permission edited (using App Ops) battery optimized 4.3 using the same bootloader as on 4.1.2.
The resources exposed in that one thread I linked, plus miles of reading in prep here on XDA showed me how to have the upgrade my way, so even stock a enthusiast can get a first class passage thanks to our devs. Buy them a drink when you can!
Some months ago I made the huge mistake of applying the OTA update to my locked AT&T G S III SGH-i747 which had a stock ROM at the time.
The result could not have been worse. The phone is barely usable now. It's very slow, drains battery faster, cannot tether for free anymore, and can't seem to be able unlock. I tried with SamMobile and lost my money because their software does not work on this phone, and they don't answer to my inquiries
So, does anyone know a method for unlocking it?
Is there a way to go back to stock? Is there a way to reset it before selling it?
My phone is encrypted and I don't know if that makes any difference, but I am afraid it becomes bricked
I have searched the threads first and can't find a definitive answer to my questions
After this terrible experience I am seriously consider never buying a Samsung Android phone ever again. In fact, I am even afraid to install the AT&T OTA KitKat update given the possibility of my phone becoming even less usable
I'm assuming you're referring to Sim unlocking to use on other networks. It doesn't have a locked bootloader if that's what you mean though.
Once updated to 4.3 the only way to Sim unlock it is to get an unlock code from AT&T or buy one online. Unlock codes MUST be entered into the stock dialer.
As for the issues you mentioned, I suspect it has something to do with your encryption, though I could very well be wrong though. I can say your experience is not the norm, so something simply just went wrong along the way. It happens.
This is what I suggest you do. Backup your important data, including what's on your internal SD card.
Flash the 4.3 MJB firmware via Odin. (Firmware is in a thread in the General section.)
Reboot to recovery and factory reset. (This will wipe all apps and data including the internal sdcard)
Reboot, setup and test to see if it's improved.
Alternatively, if you have trouble with Odin, enewman17 has a thread in development for full stock revert. I'll try to find the link in a moment. If either method gives you problems, factory reset and try again.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
---------- Post added at 12:20 AM ---------- Previous post was at 12:20 AM ----------
http://forum.xda-developers.com/showthread.php?t=2658486
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Thanks DocHoliday77. I will try to do what you are saying
This update was a well known fiasco, and had to be pulled by Samsung:
http://www.thefullsignal.com/samsung/samsung-galaxy-s-iii/16037/android-43-update-pulled-samsung
http://www.thefullsignal.com/samsung/galaxy-s3/16050/samsung-galaxy-s3-android-43-update-pushing-att
Multiple complaint threads were created in the AT&T forum, which they conveniently folded into a single one
https://forums.att.com/t5/Android/Galaxy-s3-android-update-to-4-3/m-p/3858373
Some people tried to factory reset the phone after the update with the result being the phone bricked (you can read in the above thread and on this very same website). So, I am a little worried about that. But right now the phone it's very unusable, so I guess I have little to lose by following your directions
Question: why do I need to flash the 4.3 MJB firmware via Odin if the firmware is already in my phone? Sorry if it's too obvious to you
I suggest flashing the full firmware in case something was corrupted in yours. That's all.
The only thing I know for sure about the update issue was that it primarily affected i9300 users. Pretty much any article you find about the update being pulled will be talking about that international model. I'm not aware of any us models having an update pulled after its release. I can't say much about AT&Ts though, I'm a T-Mobile user. But on T-Mobile there were very few problems at all. Even with leaked and ported builds from other carriers. I personally didn't have a single issue, but I do recall a lot of people panicking because they thought the i9300 problems were going to affect them too, which ultimately they didn't.
As for complaints on the carrier forums, you'll find similar threads related to every update for every carrier. Its an extremely small percentage compared to the overall number who took the updates with no issues.
Anyway, I hope flashing that firmware helps to solve some of the problems you've had. Make sure your important data is backed up of course and you may need to factory reset. I do acknowledge some had some unnecessary problems though, so I can't guarantee anything. Hopefully everything goes smoothly for you.
Good luck!
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Well, it affected non-international users as well, like me. Not sure what you mean by "primarily" but if it means you mostly heard about the i9300 and you don't use AT&T so you didn't hear too much about it, that does not really sound less anecdotal than my experience
And yes, I am aware the people who complain in forums does not necessarily represent the whole universe of users. However, the absence of more people complaining in such forums does not prove in any way the problems do not affect most users. One simply can't draw conclusions one way or the other.
Thanks for your help. Based on your reputation I am sure you know what you are talking about with regards to ROMs and technical details.
I am not convinced, though, about how typical or less typical are the problems I am experiencing just based on the information on this thread.
:deleted: (with apologies)
err on the side of kindness
Can anyone make a full guide/explanation on vendor files.
Only information I can find on the subject is jumbled. Multiple people with various issues and problems either caused or fixed by incorrect or correct vendors etc. Camera issuss, youtube issues, booting issues all seem to be caused by this vendor file.
What is the vendor file? Is it bootloader file or more?
Do you flash it with twrp or odin?
Before flashing twrp or after?
Flashing before the rom or after?
How do we get a vendor file?
Thank you to anyone who can do this
NotEvenFinalForm said:
Can anyone make a full guide/explanation on vendor files.
Only information I can find on the subject is jumbled. Multiple people with various issues and problems either caused or fixed by incorrect or correct vendors etc. Camera issuss, youtube issues, booting issues all seem to be caused by this vendor file.
What is the vendor file? Is it bootloader file or more?
Do you flash it with twrp or odin?
Before flashing twrp or after?
Flashing before the rom or after?
How do we get a vendor file?
Thank you to anyone who can do this
Click to expand...
Click to collapse
Damn bub, ..... I got over whelmed reading your post. You got alot learn. What are you trying to do?
Rally517 said:
Damn bub, ..... I got over whelmed reading your post. You got alot learn. What are you trying to do?
Click to expand...
Click to collapse
Lol. Basically i used to know what I was doing back in 2015. But alots changed since I last had a samsung. (S5).
I still havnt put a custom rom on here or broke my knox but I want to be 100% clear what im doing when i inevetably put a rom on this phone
Same....I really don't understand why it is now so complicated....the system looks like it's limited. I remember when you could flash custom ROMs without lose warranty and now everything you do, you lose warranty and Samsung apps. This is so stupid, it's like they want to become like Apple, but this Samsung rom Is heavy and slow your phone, make you drain battery, etc. so it's inevitable to flash a custom ROM. I still got the original firmware but if I change ROM I also can't have Samsung camera working which is good. It's very ****. However how to use vendor and where to find it? I see very little development for this device and don't understand why.
Pierfranc said:
Same....I really don't understand why it is now so complicated....the system looks like it's limited. I remember when you could flash custom ROMs without lose warranty and now everything you do, you lose warranty and Samsung apps. This is so stupid, it's like they want to become like Apple, but this Samsung rom Is heavy and slow your phone, make you drain battery, etc. so it's inevitable to flash a custom ROM. I still got the original firmware but if I change ROM I also can't have Samsung camera working which is good. It's very ****. However how to use vendor and where to find it? I see very little development for this device and don't understand why.
Click to expand...
Click to collapse
Tbh tho samsung is still the best android. Oneplus customer service is garbage and full of broken promises. Not to mention its no longer flagship specs for affordable prices. Huawei are a complete joke and who else is there really...
I dont mind this samsung stock firmware. I want to go to lineage but seeing so many problems with it and apparently doesnt even have anyone maintaining it
NotEvenFinalForm said:
Tbh tho samsung is still the best android. Oneplus customer service is garbage and full of broken promises. Not to mention its no longer flagship specs for affordable prices. Huawei are a complete joke and who else is there really...
I dont mind this samsung stock firmware. I want to go to lineage but seeing so many problems with it and apparently doesnt even have anyone maintaining it
Click to expand...
Click to collapse
OnePlus and Huawei are good brand and they make nice phones, I tried them and they sometimes are faster than Samsung rivals. P20 and OnePlus 6 are faster than Galaxy S9. For example: Smart View to share screen on television via WiFi is very very slow on Galaxy S9, a very stupid and inefficient performance, which not always work, it's very incredible, on a flagship like S9! While on P10 lite (really it, the old Huawei phone) is very fast. Maybe just because they have not garbage pre-installed. But I prefer S9 for many aspects, like size, I don't want a tablet in my pocket. Galaxy S10e will be the best phone I think. Anyway I want change ROM but I am scared to not find a good one, to disable many Samsung apps forever and since I have more than 1 year of warranty, to lose it. So I want know how to proceed to root from the beginning and then get best Rom for it, without lose the good Samsung camera features. Any idea? Any valid camera to replace the stock one?
GuestK00160 said:
Tbh tho samsung is still the best android. Oneplus customer service is garbage and full of broken promises. Not to mention its no longer flagship specs for affordable prices. Huawei are a complete joke and who else is there really...
I dont mind this samsung stock firmware. I want to go to lineage but seeing so many problems with it and apparently doesnt even have anyone maintaining it
Click to expand...
Click to collapse
Remember all Samsung exynos devices have a leak that will let hackers take over your phone , dont use Wifi calling and turn off Volte calling if you are on the official firmware , we have iODE Pixelexperience atm well supported