New Update Message - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Today I received the new update message, last time it tried to install it itself after 3 times postponed. But for for reason it failed. Is it because the phone is rooted ?
What if AT&T release the Jelly bean update in the future and I want to install it. How do I fix the update error message? Do I need to un-root the phone first ?

benzso63 said:
Today I received the new update message, last time it tried to install it itself after 3 times postponed. But for for reason it failed. Is it because the phone is rooted ?
What if AT&T release the Jelly bean update in the future and I want to install it. How do I fix the update error message? Do I need to un-root the phone first ?
Click to expand...
Click to collapse
+1. I also have stock LEM firmware and I am rooted(everything is stock though). When I try to update to LG1 via OTA, it downloads the update and reboots in CWM and fails to update. When I plugin via Kies to update, it times out.
Is there any way to update to LG1 when you are rooted?

AlwaysNoob said:
+1. I also have stock LEM firmware and I am rooted(everything is stock though). When I try to update to LG1 via OTA, it downloads the update and reboots in CWM and fails to update. When I plugin via Kies to update, it times out.
Is there any way to update to LG1 when you are rooted?
Click to expand...
Click to collapse
Correct me if I'm wrong but it should work if you have the stock recovery - which in your case you don't but not necessarily in the OP's case. Unless the OP wasn't perfectly clear.
Maybe you need to go back to stock first?

saj222 said:
Correct me if I'm wrong but it should work if you have the stock recovery - which in your case you don't but not necessarily in the OP's case. Unless the OP wasn't perfectly clear.
Maybe you need to go back to stock first?
Click to expand...
Click to collapse
Is there any way I can remove CWM and go back to stock recovery? I rooted my phone using this easy guide http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/

I am not worry about the minor update from AT&T, we all expect to get Jell Bean soon. Just want to make sure we can download the update and install it properly without any errors. So should we go stock? What will be the steps? Download the stock firmware and use Odin flash it back?

I wouldn't worry about the official update. Usually in a day or two of official release, there will be an official firmware in package in the development section.

Did you mean we can just download the custom jelly bean firmware and install it as custom rom instead of the official one from AT&T? I think that make sense.
mrhaley30705 said:
I wouldn't worry about the official update. Usually in a day or two of official release, there will be an official firmware in package in the development section.
Click to expand...
Click to collapse

When its released, yes. That's one reason there are threads just for stock firmware.

Related

Un-Flashing Clockworkmod

So I rooted mine S III and flashed the clockworkmod recovery in preparation to install Cyanogen mod 10 ROM for it, bute after reading more I decided to not do it, afraid of bricking, unstable ROM etc. After a while I used super user option to ''Un-root'' it, after reboot it was gone and I though it was back to normal state. Now just last week I received Update from T-mobile which is bugging me every few days, but when I try to install it the phone boots with Android icon and it's belly open like shelf with tesseract moving around and progress bar for few seconds, then recovery shows up and says something failed. Can I throw it out somehow and install the update? I'm worried because I won't be able to install the 4.1 which is coming sometime soon.
I have yet to come across a stock recovery file on its own. You probably need to ODIN back to stock. Make sure you back up.
Also, (assuming you have a T Mobile phone)I believe the OTA you are receiving is the UVALH2 update, in which case you can already find that ODIN package in this thread if not, there are other stock images in this thread also.
Infamous_Cheez said:
I have yet to come across a stock recovery file on its own. You probably need to ODIN back to stock. Make sure you back up.
Also, (assuming you have a T Mobile phone)I believe the OTA you are receiving is the UVALH2 update, in which case you can already find that ODIN package in this thread if not, there are other stock images in this thread also.
Click to expand...
Click to collapse
Screw the update I want Jelly Bean, what if it shows up and phone just boots up into recovery and just stands there like an idiot?
Only two ways to get jb right now is to update to UVALH2 then apply the ota patch from samsung. Alternatively wildchld has the jb rom ready to go in the dev thread.
Note that with these updates if you flash a rom with cwm or twrp you will not get the full update. Only odin or kies can update all partitions available in the ota.
Sent from my SGH-T999 using xda app-developers app

Question about root and roms

If I root my S3 will I still be able to get the OTA updates? I rooted my Atrix and after that I couldn't get the OTA updates. Also what is the best ROM?
anaylor01 said:
If I root my S3 will I still be able to get the OTA updates? I rooted my Atrix and after that I couldn't get the OTA updates. Also what is the best ROM?
Click to expand...
Click to collapse
If you don't need a specific feature from the stock firmware (gestures, wifi calling, etc), just get CM or AOKP and save yourself a headache.
Best? As far as stock? I've read LI6 is decent.
Well with my Atrix when Android 3.0 came out I wasn't able to update it because I was rooted. So my question is when Jelly Bean comes out will I be able to update it to Jelly bean if I am rooted or have a custom rom installed?
anaylor01 said:
Well with my Atrix when Android 3.0 came out I wasn't able to update it because I was rooted. So my question is when Jelly Bean comes out will I be able to update it to Jelly bean if I am rooted or have a custom rom installed?
Click to expand...
Click to collapse
3.0 wasn't even for phones. If you install custom recovery you will not be able to receive an OTA until you flash the stock recovery. Just use a jellybean ROM.
Sent from my SGH-T999
joshnichols189 said:
If you install custom recovery you will not be able to receive an OTA until you flash the stock recovery.
Click to expand...
Click to collapse
How can this be true? This is what I did.
Restored a UVALEM nandroid (via CWM). It was the original firmware on the phone when I bought it (no custom install, but I rooted with the Sprint method a couple weeks prior), I just happened to keep this backup.
Reset factory defaults.
Nandroid again for clean UVALEM backup.
Use Software > About phone > Software update to get the UVALH2 update. It was ~90mb.
Phone rebooted after it was done.
Dropped into CWM to make another backup (CWM still here, was never removed).
Downloaded LI6 JB OTA from SamMobile. Installed that from CWM.
I have LI6, never removed CWM. And it is still there. Root should be, although I did not test to confirm.
If you can't receive OTAs with custom recovery/root, how did this work? Is it a feature that was not active in the UVALH2 build? What about the LI6 build I flashed from CWM?
Aerowinder said:
How can this be true? This is what I did.
Restored a UVALEM nandroid (via CWM). It was the original firmware on the phone when I bought it (no custom install, but I rooted with the Sprint method a couple weeks prior), I just happened to keep this backup.
Reset factory defaults.
Nandroid again for clean UVALEM backup.
Use Software > About phone > Software update to get the UVALH2 update. It was ~90mb.
Phone rebooted after it was done.
Dropped into CWM to make another backup (CWM still here, was never removed).
Downloaded LI6 JB OTA from SamMobile. Installed that from CWM.
I have LI6, never removed CWM. And it is still there. Root should be, although I did not test to confirm.
If you can't receive OTAs with custom recovery/root, how did this work? Is it a feature that was not active in the UVALH2 build? What about the LI6 build I flashed from CWM?
Click to expand...
Click to collapse
I don't know, clockworkmod is supposed to block the installation of OTA updates.
Sent from my SGH-T999
Hmm, I'm using 6.0.1.2, and it does ask me if I want to disable /system/etc/install-recovery.sh, when I try to exit.

How can i go back to ICS

how do i go from the official sprint jelly bean update back to the last official ICS update from sprint.
ariel123 said:
how do i go from the official sprint jelly bean update back to the last official ICS update from sprint.
Click to expand...
Click to collapse
ODIN is you best friend in these circumstances:
Click Here
Then the stock LI3 update:
Click Here
And Drivers if you dont have them:
Click Here
and just follow this tut:
http://theunlockr.com/2012/07/28/how-to-unroot-sprint-samsung-galaxy-s3/
and you should be back to square one.
Oh, and there is apparently an issue with ODIN fashing modem higher than LEN.
EDIT: You can install a custom recovery to flash the LI3 modem.
I can help you with that also. Let me know if you have any problems.
EDIT #2: (I keep remebering stuff) If you have a custom recovery you can skip all that jazz and just flash LI3 this way:
http://forum.xda-developers.com/showthread.php?t=1743923
GRock84 said:
ODIN is you best friend in these circumstances:
Click Here
Then the stock LI3 update:
Click Here
And Drivers if you dont have them:
Click Here
and just follow this tut:
http://theunlockr.com/2012/07/28/how-to-unroot-sprint-samsung-galaxy-s3/
and you should be back to square one.
Oh, and there is apparently an issue with ODIN fashing modem higher than LEN.
EDIT: You can install a custom recovery to flash the LI3 modem.
I can help you with that also. Let me know if you have any problems.
EDIT #2: (I keep remebering stuff) If you have a custom recovery you can skip all that jazz and just flash LI3 this way:
http://forum.xda-developers.com/showthread.php?t=1743923
Click to expand...
Click to collapse
hey thanks i just want to go back to ics and unroot inorder to do the jb update ota. which method do you think is easiest
ariel123 said:
hey thanks i just want to go back to ics and unroot inorder to do the jb update ota. which method do you think is easiest
Click to expand...
Click to collapse
Oh well in that case just follow the steps in the tut i recommended. Itll take you back to stock. You'll need the stock recovery installed to update also, so if you have a custom installed just flash the stock recovery with ODIN from this thread along with the stock rom. (recovery is at the bottom of the OP)
after the install and your phone boots you should get the prompt to update
GRock84 said:
Oh well in that case just follow the steps in the tut i recommended. Itll take you back to stock. You'll need the stock recovery installed to update also, so if you have a custom installed just flash the stock recovery with ODIN from this thread along with the stock rom. (recovery is at the bottom of the OP)
after the install and your phone boots you should get the prompt to update
Click to expand...
Click to collapse
I second that with one thing changed. Forget the ota from sprint. Too many reasons to fail. Go back to ics like suggested but keep cwm/twrp. And flash this instead
http://www.androidfilehost.com/?fid=9390135922294523494 update with system checks removed. Flash in twrp/cwm
Just my $.02

[Solved] official JB 4.3 for Maguro ?

Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
niaoRen said:
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
Click to expand...
Click to collapse
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
True, I've experienced this before, I would recommend go with Official Factory image if not sure your device is running completely stock before apply OTA...
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
fux0r99 said:
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
Click to expand...
Click to collapse
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Zepius said:
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Click to expand...
Click to collapse
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
niaoRen said:
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
Click to expand...
Click to collapse
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
cupfulloflol said:
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
Click to expand...
Click to collapse
alright. Will try to revert to stock kernel and try the official OTA. Will revert back here after i've attempted it. Thanks a bunch you all
I just found a easier way to do things.
Just flash this 4.3 stock ROM over my current 4.2 rom. Works like a charm and hassle free.

Unroot to accept update

Hi,
I have a rooted Sprint GS3, running the stock ROM with just one or two root based apps. Do I need to unroot to accept the OTA update? If so, how do I go about doing that?
TheSapient said:
Hi,
I have a rooted Sprint GS3, running the stock ROM with just one or two root based apps. Do I need to unroot to accept the OTA update? If so, how do I go about doing that?
Click to expand...
Click to collapse
if you would like to run a 4.3 stock ROM, there are a couple in the development section that you can choose from without having to run the 4.3 boot loader that contains KNOX. That way you don't have to go through the unroot process to accept the OTA.
jdelano said:
if you would like to run a 4.3 stock ROM, there are a couple in the development section that you can choose from without having to run the 4.3 boot loader that contains KNOX. That way you don't have to go through the unroot process to accept the OTA.
Click to expand...
Click to collapse
Thanks. I think the preference is to accept the OTA. If we need to unroot, we'll do that if we can figure out how. Sorry for being a little vague. I'm trying to help someone else out.
ok, you can go here Restore to unrooted MD4 follow that and you're good to go
I was stock rooted with clockwork recovery.
Took the OTA without unrooting with no problems at all, just had to re-root when it was done.
dotNETProgrammer said:
I was stock rooted with clockwork recovery.
Took the OTA without unrooting with no problems at all, just had to re-root when it was done.
Click to expand...
Click to collapse
Really? I thought it was always a bad idea with a custom recovery. Maybe we will try it rooted as well. Thanks.
Every other time I've tried it would download, but just wouldn't flash the OTA.
This time, it did. Surprised me.
Re
I got the update notification today when i woke up and when i clicked the restart and install it went to recovery mode, i panicked and clicked reboot (honestly still dont know what to do),
and restarted the phone without updating
I'm running stock 4.1.2 with just 2 root apps (superuser) and tatanium backup, how can i update ?
thanks
mjkubba said:
I got the update notification today when i woke up and when i clicked the restart and install it went to recovery mode, i panicked and clicked reboot (honestly still dont know what to do),
and restarted the phone without updating
I'm running stock 4.1.2 with just 2 root apps (superuser) and tatanium backup, how can i update ?
thanks
Click to expand...
Click to collapse
Relax . You do not have to update. You do not have to lose Root. Check out THIS thread. It will explain a few things to you in detail about Updates, and how to stop the update nag. If you want to update to the latest TW 4.3 Stock Rooted, check out the thread HERE. Just make sure you read, and read again before doing anything. Also make sure to download the correct Rom. There are several versions on the thread.
prboy1969 said:
Relax . You do not have to update. You do not have to lose Root. Check out THIS thread. It will explain a few things to you in detail about Updates, and how to stop the update nag. If you want to update to the latest TW 4.3 Stock Rooted, check out the thread HERE. Just make sure you read, and read again before doing anything. Also make sure to download the correct Rom. There are several versions on the thread.
Click to expand...
Click to collapse
Thanks for the answer.
I actually want to update to stock 4.3, and I was trying to achieve that by getting the OTA update.
And i was wondering if i can still do that?
If I simply can't then I'll just go to CM instead of getting other rooms since I used to have them with my old HTC.
Thanks again
If you want completely Stock Rooted 4.3, it's the second link I posted for you. It's the Stock, Rooted, Factory Rom, with Knox removed. All done by CNexus . Just be sure to read before doing anything. As there are several versions posted. I would highly suggest going this route instead of taking the OTA update. Once you take the OTA you will have Knox, and a different bootloader.
TEAM MiK MikROMs Since 3/13/11
Thanks a lot man, I'm having a problem installing the ROM, I'm getting assert error (status 7) error when trying to install the odexed rom,
I have just updated my CWM to 6.0.4.5
Sorry I cant reply to the thread directly, need 10 posts to be able to do so.
MJ
edit: now it's stuck on boot loop
edit: I downloaded the original recovery rom and installed it from ordin, then updated phone through kies. it's all good now.

Categories

Resources