Related
Hey all, first off, please don't flame. I am totally unfamiliar with Samsung. I just got my mom a gnex for mothers day and am going to root it but I keep seeing all these thread posts saying Google wallet is broken scattered through the ROM threads. I don't know if I'm even gonna put a custom rom on her phone, I just want root for maintenance. And I really don't have time to seriously study tons of threads. If anyone could advise about
A( what is breaking wallet
B( if I unlock bootloader and put on custom recovery, do I need to restore to factory recovery to flash radio updates ?
Ç( if there is a ROM that is pretty stock but more importantly stable, it'd be super appreciated to hear about it.
I run AOKP on me Evo 4g, but the random reboots are quite frequent. Is it more stable here?
By the way, it's a sprint galaxy nexus. Thanks much for any pointers.
Looking for good kernel for battery more than performance. Also, it seems to me on Sammy, you can't flash radio updates on custom kernel or custom recovery. Am I reading wrong?
Much thank to any who take time to respond. Thanks.
sent from 2yr old Evo on ICS
Don't root and ROM your mother's Galaxy Nexus.
Jesus people. Leave it stock. Don't need to do maintenance, don't need to do anything. Leave it stock and you'll save yourself and her all kinds of trouble.
Point taken, but the thing is she's been dealing with a Samsung moment for >2yrs . The thing won't even hardly make phone calls anymore, takes about 45sec for SMS to open etc. She's always asking me if it can be fixed (cuz she knows I spend 24-7 on my Evo and xda). I always tell her I'd have to root it to really try to do anything (wipe caches, etc).. but i got her a gnex figuring if there's issues, I can fix for her easily (also got it for her cuz I figured if development on Evo LTE goes south, I'll trade phones with her.
Anyhow, was hoping for clarification about do I have to have stock recovery and ROM to update radios etc. On HTC Evo you don't, but it seems like I've seen talk of that here.
Thanks anyone.
Edit: and martonikaj, I'll keep your info in mind.
Just trying to figure where the partition checks are with Sammy. I thought I read that if your kernel is custom, you can't flash updated radios.
sent from 2yr old Evo on ICS
scottspa74 said:
Edit: and martonikaj, I'll keep your info in mind.
Just trying to figure where the partition checks are with Sammy. I thought I read that if your kernel is custom, you can't flash updated radios.
Click to expand...
Click to collapse
I understand her frustration with her current device and your willingness to help, but you need to keep her device stock. You don't need to flash new radios to the device. Just leave it stock and you'll both be better off in the long run. The cons vastly outweigh the pros when considering rooting/ROMing a device of a completely novice/uninformed user that doesn't need any extra issues.
Just FYI, there is no check on the Nexus. You can be running whatever kernel and ROM you want and flash radios if your bootloader is unlocked. But again, this will never be necessary, the phone will work just fine on stock radios.
I super appreciate your input. You have answered questions I have. I am one of those who deeply feel that if your Android is not rooted, then you should buy a non Android device. It's Only yours if you control its dalvik and can wipe caches
Need recovery for that.
I'm not at all arguing with your point. And I appreciate the responses (but without #, it's only good for throwaway).
Thank you.
sent from 2yr old Evo on ICS
scottspa74 said:
I super appreciate your input. You have answered questions I have. I am one of those who deeply feel that if your Android is not rooted, then you should buy a non Android device. It's Only yours if you control its dalvik and can wipe caches
Need recovery for that.
Click to expand...
Click to collapse
You're welcome.
I'll agree on your point if your mom wants to read up on what root is, follow an XDA guide, learn how to use command prompt and Fastboot, and root her own device.
Until then, leave it stock.
Should have gotten her an IPhone lol.. I agree with you that every android should be rooted, but Moms don't need root they need something that just works . If a person is willing to do the research and learning about root themselves I always recommend android, if not stock or IPhone less headache for me
Sent from my Galaxy Nexus using XDA
twizzler703 said:
Should have gotten her an IPhone lol.. I agree with you that every android should be rooted, but Moms don't need root they need something that just works . If a person is willing to do the research and learning about root themselves I always recommend android, if not stock or IPhone less headache for me
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
The phone its just perfect as is it.. Id root her phone just to put adfree on it
The phone is not Samsung, i mean doesn't have touchwiz on it.. Its pure google
And. Forget about iphone
Galaxy Nexus AOKP m5 Franco kernel m3
msedek said:
The phone its just perfect as is it.. Id root her phone just to put adfree on it
The phone is not Samsung, i mean doesn't have touchwiz on it.. Its pure google
And. Forget about iphone
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
Exactly. Google will only mass release versions that are finished and user friendly. Don't root it, it won't make her experience any better.
I've rooted devices for a few not-quite-as-technically-savvy-as-me friends in the past, and I've always regretted it - as have they. You shouldn't own a rooted device unless you rooted it yourself and know how to operate it. Otherwise, it's just asking for problems and complications. I got so sick of the calls from friends in other countries, "Hey, you rooted my phone and now I can't install an update that my carrier is pushing. Fix it!" Or if it's not a cry for help, I'd catch blame for any little issue that randomly occurred on the device. "My phone just randomly rebooted itself, this is obviously because you broke it when you rooted it."
I can only imagine how much worse it would be with a mother.
If you absolutely need the ability to wipe cache and dalvik (not really an issue unless your flashing ROMs, which your mother won't be, but whatever), you can always do it through fastboot.
Again, what martonikaj said:
martonikaj said:
Don't root and ROM your mother's Galaxy Nexus.
Click to expand...
Click to collapse
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.
Hey everybody. So I've had this device since December and when the 4.0.4 update was released for VZW users, I was not able to update. Upon further research, I found out that there was a mistake in the factory and the recovery image was not flashed, meaning I could not update software or perform factory resets. I brought it into Verizon and got a replacement, but I got a refurb with terrible signal issues. I went back to Verizon and they told me I could get a new phone. I am now eligible to get a new phone for free as a replacement. I purposely kept the Gnex until now so I could swap it out for the SIII that is releasing tomorrow. I actually fixed my Gnex on my own by flashing stock images of the 4.0.4 manually. So the question is, should I revert my phone back to 4.0.2 and leave out the recovery image when flashing in order to get the SIII, or keep my Gnex which is now working perfectly fine?
jttate04 said:
Hey everybody. So I've had this device since December and when the 4.0.4 update was released for VZW users, I was not able to update. Upon further research, I found out that there was a mistake in the factory and the recovery image was not flashed, meaning I could not update software or perform factory resets. I brought it into Verizon and got a replacement, but I got a refurb with terrible signal issues. I went back to Verizon and they told me I could get a new phone. I am now eligible to get a new phone for free as a replacement. I purposely kept the Gnex until now so I could swap it out for the SIII that is releasing tomorrow. I actually fixed my Gnex on my own by flashing stock images of the 4.0.4 manually. So the question is, should I revert my phone back to 4.0.2 and leave out the recovery image when flashing in order to get the SIII, or keep my Gnex which is now working perfectly fine?
Click to expand...
Click to collapse
Keep the gnex and flash jellybean or cm9/aokp
Sent from my Galaxy Nexus using xda premium
If you want the extra RAM and locked bootloader, take it back and get the SIII.
If you want a phone with 4.1.1 today keep the Nexus, go to development section and flash jellybean already
Really wish people would grow a pair and just choose the device that they want, rather than asking a bunch of strangers that know nothing about them.
martonikaj said:
Really wish people would grow a pair and just choose the device that they want, rather than asking a bunch of strangers that know nothing about them.
Click to expand...
Click to collapse
It's perfectly valid for someone to seek the opinions of others to help them in their decision.
Do mods matter to you
If you want to be able to easily load mods to your phone keep the Galaxy Nexus. If you want a painless, but Verizon-controlled environment get the SIII. If I was in your position I'd keep the Gnex, but your priorities may be different.
It really depends on what you're going to do with your phone. If you go the GS3 route, just be aware that given the current situation with the locked bootloader, your ability to customize the phone will be compromised, until devs really find an effective way to bypass the bootloader. There is the Developer Edition of the Verizon Galaxy Nexus, but that seems to be only available through Samsung and not Verizon.
At least by sticking with the Nexus, you have access to all the available custom roms now, as well as JB and so forth.
Sent from my Nook Color using Tapatalk
CKTurbo128 said:
It really depends on what you're going to do with your phone. If you go the GS3 route, just be aware that given the current situation with the locked bootloader, your ability to customize the phone will be compromised, until devs really find an effective way to bypass the bootloader. There is the Developer Edition of the Verizon Galaxy Nexus, but that seems to be only available through Samsung and not Verizon.
At least by sticking with the Nexus, you have access to all the available custom roms now, as well as JB and so forth.
Sent from my Nook Color using Tapatalk
Click to expand...
Click to collapse
Don't forget the wonderful gift of touchwiz
Has Google released the links for JellyBean for LTE Devices yet? I'm not using a GSM
jttate04 said:
Has Google released the links for JellyBean for LTE Devices yet? I'm not using a GSM
Click to expand...
Click to collapse
No. There's no Verizon or Sprint OTAs yet. Source is out for GSM and Verizon though.
I'd get the GS3. If you find out you made the wrong choice you can sell the GS3 and re-buy a Nexus and make $.
You fixed terrible signal issues by flashing the phone? That's weird as signal issues have been reported as hardware related all over this forum.
But as its now fixed and working for you, I'd certainly keep it..There's a reason why you bought it in the first place, since its working why not keep it and save your upgrade.
For me, after having the freedom of a unlocked bootloader I'm not sure I can ever own a non-nexus device again!
The thing is, we weren't even going to root it. I thought that Teamviewer Quicksupport supported all S3's.
I looked and he is running 4.1.1. So...I'm not sure what the big deal is, but no matter what, Quicksupport is not "supported" when we go to the Play Store. If there is a simple fix, I would love this, because he is not tech-savvy and this is why we got this model.
However -
I've only rooted one phone in my life before, when there was only really one way of rooting. It seems I have read that problem abound with these S3 models - more specifically, IMEI may be lost, and choosing exactly which way to root, since there are varying stock kernels.
I see this thread here on the IMEI backup/injection. Am I safe to assume, that is where I start? (I have read that the Bell is just a ATT version, so will the ATT version instructions work here? I will ask in that thread but not sure).
Then - once that is done - I have to pick a way to root it that works for Bell's SIII SGH-1747M. That is where I am running into a bit of a wall. I wonder if I can get someone who has done this with this model to help me out and pick a safe way to mod it? Do I need to post more info to help decide this? I can get on his device and get whatever info is needed.
I also read, that perhaps Bell's stock kernels either do or do not need unsecuring (not quite sure after a lot of reading) before doing anything else. I really am trying to learn - it's just all very daunting and when I'm reading and not understanding, I can still read til the sun explodes and never be able to do this correctly. Well, maybe if I had an unending supply of phones.
Thank you for your help...
I would just ask in the IMEI and other forums but they are not available to me (either post count too low or I'm not sure).
Sincerely,
Foxdev
foxdev said:
The thing is, we weren't even going to root it. I thought that Teamviewer Quicksupport supported all S3's.
I looked and he is running 4.1.1. So...I'm not sure what the big deal is, but no matter what, Quicksupport is not "supported" when we go to the Play Store. If there is a simple fix, I would love this, because he is not tech-savvy and this is why we got this model.
However -
I've only rooted one phone in my life before, when there was only really one way of rooting. It seems I have read that problem abound with these S3 models - more specifically, IMEI may be lost, and choosing exactly which way to root, since there are varying stock kernels.
I see this thread here on the IMEI backup/injection. Am I safe to assume, that is where I start? (I have read that the Bell is just a ATT version, so will the ATT version instructions work here? I will ask in that thread but not sure).
Then - once that is done - I have to pick a way to root it that works for Bell's SIII SGH-1747M. That is where I am running into a bit of a wall. I wonder if I can get someone who has done this with this model to help me out and pick a safe way to mod it? Do I need to post more info to help decide this? I can get on his device and get whatever info is needed.
I would just ask in the IMEI and other forums but they are not available to me (either post count too low or I'm not sure).
Sincerely,
Foxdev
Click to expand...
Click to collapse
You can root without worrying about losing your IMEI.. Give this thread a look over.. Click
BAM1789 said:
You can root without worrying about losing your IMEI.. Give this thread a look over.. Click
Click to expand...
Click to collapse
Thanks, I just added it as a part of the research I did I am not worried so much about that anymore, but the other things are like....making my mind explode. All I've ever done so far is my Thunderbolt 2 years ago and that was so easy.
foxdev said:
Thanks, I just added it as a part of the research I did I am not worried so much about that anymore, but the other things are like....making my mind explode. All I've ever done so far is my Thunderbolt 2 years ago and that was so easy.
Click to expand...
Click to collapse
this is actually a pretty simple device to root too. Just pick a method and read it over and it'll be pretty hard to screw anything up
Sent from my R800i using xda app-developers app
Also make a backup of your imei just in case something goes sideways.
Sent from my SAMSUNG-SGH-I747 using xda premium
d3athsd00r said:
Also make a backup of your imei just in case something goes sideways.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks, going to do that for sure
Also, does anyone know with this model if Teamviewer Quicksupport just doesn't work at all? I cant get answers from Teamviewer. If it did I wouldn't need to root the stupid thing!
i don't understand why you believe you need to root to have this app supported. i attempted to use the app and it told me i needed to download an app from here. try that before you root?
edit: also i am rooted and it still did not allow me to use the app. rooting isn't your solution here
sent from my I747
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