Need some help applying OTA update - Sprint Samsung Galaxy S III

Hello, first of all, I'm sorry for the noob question. I tried to search for the answer but I got more confused than when I started. I have rooted my SGS3 just to be able to use the Wifi hotspot, I'm not into other modifications or anything, I just wanted the hotspot. Now the phone wants me to update through OTA, but of course it's not working. My questions are:
-Should I go back to stock (following the videos from qbking77) and then apply the OTA? Is it safe?
-Should I go back to stock and MANUALLY update the phone?
-Is LF9 the latest OFFICIAL update?
-Is there anything else I should consider?
I don't care about custom roms or any other modifications, I like the phone vanilla BUT with the hotspot enabled. I was looking through a lot of videos and threads but I could't find a good answer.
Thanks in advance!

The latest official release is LJ7. You have a couple of options to get the update.
- You could go back to stock to accept the update. The key is that you need the stock recovery installed for the update to work normally. You could then reflash the custom recovery if you like.
- You could manually apply the update from the recovery. If you phone is bugging you to apply the update it then you probably already have the update ZIP in your \cache\ folder. You could also download it. The normal OTA update will only work in the CWM recovery (not TWRP) but there are modified versions posted here that remove the check to allow it to work from TWRP.
Other considerations: If you are using the WiFi Tether for Root users it will no longer work one you update to Jelly Bean (LJ7). You will need to unisntall that and get version that was modified by TrevE.

m20120 said:
The latest official release is LJ7. You have a couple of options to get the update.
- You could go back to stock to accept the update. The key is that you need the stock recovery installed for the update to work normally. You could then reflash the custom recovery if you like.
- You could manually apply the update from the recovery. If you phone is bugging you to apply the update it then you probably already have the update ZIP in your \cache\ folder. You could also download it. The normal OTA update will only work in the CWM recovery (not TWRP) but there are modified versions posted here that remove the check to allow it to work from TWRP.
Other considerations: If you are using the WiFi Tether for Root users it will no longer work one you update to Jelly Bean (LJ7). You will need to unisntall that and get version that was modified by TrevE.
Click to expand...
Click to collapse
Thanks for the help! Yes I think I have CWM on. I followed a video from qbking77 (I think) and installed it. Or at least it was something like custom recovery or something the like. Do you think I can apply the update directly from CWM? Or it would be easier (and cleaner) to go back to stock recovery and do it "officially". Also, are all stock recovery the same? I ask because there are some different files in qbking77's website. I don't know if the version of stock recovery matters at all. Also, thanks for the tip on the modified app.

You probably have CWM recovery. You only need the stock recovery if you want to let the phone apply the OTA (i.e. it prompts you to accept the update). You also have to have the phone in a completely stock state (root is ok). You can not have any modified system files.
If you want to apply the update manually you can also do that with CWM. You can copy the file (something like eec955eb4a5b.update_SPH-L710_LI3_to_LJ7.zip) from the \cache folder to the internal sdcard of your phone. You can then boot into CWM recovery and apply flash the ZIP update. You must have stock system files in order for this update to work also.
If you have modified any system files (I removed the system version of Swype) you have to get back to stock in either case.

m20120 said:
You probably have CWM recovery. You only need the stock recovery if you want to let the phone apply the OTA (i.e. it prompts you to accept the update). You also have to have the phone in a completely stock state (root is ok). You can not have any modified system files.
If you want to apply the update manually you can also do that with CWM. You can copy the file (something like eec955eb4a5b.update_SPH-L710_LI3_to_LJ7.zip) from the \cache folder to the internal sdcard of your phone. You can then boot into CWM recovery and apply flash the ZIP update. You must have stock system files in order for this update to work also.
If you have modified any system files (I removed the system version of Swype) you have to get back to stock in either case.
Click to expand...
Click to collapse
Ok, so the only thing I did is install the wfi hotspot app after rooting, I didn't touch anything else. So I shouldn't worry about system files, right?
You mentioned that since my phone is bothering me with updates notifications, it is because it already downloaded the update into the "cache," right? So I should just find that file, put it in the sdcard and flash from CWM? It's really that easy?

nahuelarg86 said:
Ok, so the only thing I did is install the wfi hotspot app after rooting, I didn't touch anything else. So I shouldn't worry about system files, right?
You mentioned that since my phone is bothering me with updates notifications, it is because it already downloaded the update into the "cache," right? So I should just find that file, put it in the sdcard and flash from CWM? It's really that easy?
Click to expand...
Click to collapse
It is probably there if it is prompting you to update.
One step that I almost forgot about. When you do the update you will reinstall the script that detects a custom recovery and it will install the stock recovery.
There is a good procedure here that gives you the step by step process, including flashing the Team Epic file to prevent the updated ROM from restoring the stock recovery. If you do not flash the Team Epic file the update will still be successful and you will still have root, you will just end up with the stock recovery.
The process is really easy and it is the one that I used to update from LI3 to LJ7.

Related

[Q]If i root, will i be avalible to revieve OTA updates?

Maybe a noobish question, but im sorry
As the title says : if i root the phone, will i be able to recieve updates OTA ?
edit : and same question : if i get cwr (for nandroid backups) will i be able to recieve OTA updates?
Thanks guys
So long as you're running the stock rom, you should still get OTA updates. They may or may not break root, but you'll have to risk that. If you're running a custom ROM, then you probably will not get OTA updates, but you can of course update your ROM as per the developer builds.
You will remove root if you install an OTA, and I have heard of people actually bricking their phones installing an OTA with root.
installing CWM will break OTA even if you're on the stock ROM because it flashes in stock recovery, not CWM.
...and from the mixed responses you can tell that it wasn't really a noob question. (all answers were partially correct, btw).
The update will still get pushed to your phone, based on the build version of your phone. The custom recovery will fail to install, at which point you can simply install it yourself by performing a manual flash via recovery.
Depending on the extent of the update, you may or may not lose root, and possibly even your custom recovery. Your best option is to manually flash an update, then the su.zip, and I've also put together flashable a script to prevent your custom recovery from reverting to stock at your next boot (I'll post it when I get chance). Flash all the files while in CWM, and you're golden!
I have reached maximum thanks-per-day, otherwise i would give a thanks to all of you..
So, i still have few questions :
1) If i root, get custom CWM, but stock rom, will i still be able to SEE ota update, and to DL it over the OTA (not flash it)?
2) Can i brick my device with flashing ota , while rooted and with custom CWM ?
Thanks in advance
-yes it will still show up.
-it won't brick your device, but the update will fail, and you'll have to pull battery to gay back into the os.
Sent from my Galaxy Nexus using XDA App

will this setup work?

I have a noob question:
I unlocked my bootloader and rooted my gsm nexus. However I would like to be able to receive and install any updates OTA- basically stay as stock as possible with root. My plan was to leave the stock recovery in place. If I need to do a backup or reflash su.zip (after an update to regain root) I was planning on running rom manager and using it to flash CWM. I realize that this CWM would not survive a reboot as the startup script will reflash the stock recovery.
Will this work and does it make sense?
thanks
quick bump- basically I want to know what will prevent an OTA update from installing
Edit I realized there was a flaw in my logic. After an OTA update I will lose root and then be unable to flash the recovery via rom manager. I guess will have to resort to fastboot after OTA

[GUIDE] AT&T CWM-flashable UCALG1 update | no wipe, leaves root and universal search

[GUIDE] AT&T CWM-flashable UCALG1 update | no wipe, leaves root and universal search
I've put together a zip file with the I747UCLG1 AT&T OTA update that can be flashed using CWM. This file
does not trip the flash counter
preserves root
does not include the Google search update to remove universal search
does not wipe /data
does require removing all themes and modifications
Standard disclaimer: I am not responsible if this bricks your phone, destroys your IMEI or kills your kids.
Prerequisites: You have to be on stock I747UCALEM for this to work. It may be rooted, but all the standard AT&T and Samsung bloatware must be there with no modifications. It's okay if some of the apps are frozen with Titanium Backup. You must not have any other mods or themes applied. The updater will check this stuff and abort if anything is wrong. I personally restored a nandroid backup I made right after rooting. If you didn't make one, you can use Odin and the instructions here to go back to stock.
To apply it:
Boot into recovery and make a nandroid backup.
Go back to AT&T UCALEM rooted stock if necessary (see above). If you're already on stock UCALEM but have framework-res.apk modications applied, you can flash this zip to restore framework-res.apk to UCALEM stock.
Make sure CWM recovery from clockworkmod.com is installed. The recovery from Team Epic will not work. You can get a zip file to flash in your current recovery to install v5.8.4.5 from here. Use one of the first two files; the ones that start with "recovery-clockwork". After you flash the zip, restart recovery through the "advanced" menu. Your recovery should say "ClockworkMod Recovery" at the top and not "CWM-based Recovery".
Put one of the zip files from below on your internal or external SD card.
Boot into recovery
Wipe cache and dalvik cache (optional?)
Flash the attached zip
(Optional) Go to Backup and Restore, Advanced Restore and restore the /data from the nandroid backup you made in step 1. If you used a nadroid backup in step 2, this should restore your data and apps. If you used Odin to flash the rooted UCALEM image, this step isn't necessary.
Reboot
Open Settings / Application Manager. Choose All tab. Click on AT&T Software update. Clear "Clear data". If you were getting OTA notifications before, this will prevent them from recurring. After doing this, your phone will know it's up-to-date.
This worked for me. I checked that my flash counter is still at 0 and Google search is still finding local stuff like apps. I still have root.
DOWNLOADS:
I747UCALG1_OTA.zip: This is the full OTA, with kernel and bootloader. You must be using the stock UCALEM kernel for this to work.
I747UCALG1_OTA_No_Bootloader.zip: This is the full OTA without the bootloader.
I747UCALG1_OTA_No_Bootloader_No_Kernel.zip: This is the OTA without the bootloader or the kernel. You can use this if you're already running a non-stock kernel.
I747UCALG1_OTA_Bootloader.zip: This is just the bootloader. You can apply this along with the "no kernel no bootloader" zip above in case you want everything but the kernel.
MODS:
This process requires the stock framework-res.apk, so at this point you'll need to reapply any mods you already applied. Here are some mods that I've rebuilt against LG1. Both are zip files you can apply through recovery.
Tether and Cell Standby Fix: This includes the mod to enable native Bluetooth and WiFi tethering from here and the fix for the incorrect reporting of Cell Standby time from here.
Tether, Cell Standby Fix, Increase Autobrightness: The same as above, but also with a mod to bump up autobrightness levels from here.
No Increasing Ring: This removes the increasing ringtone volume. The mod is from here.
OTHER PIECES:
Kernel: The UCALG1 kernel and kernel modules.
UCLG1 Modem: Just the modem from the OTA.
UCLEM Modem: The modem from the stock UCALEM firmware.
UCALG1 Bootloader
UCALG1 Bootloader (no checks): This is the LG1 bootloader will all the checks for AT&T ROMs removed from the flashing script. This can be flashed even if you're running a non AT&T ROM, but only flash it on AT&T phones!
UCALEM Bootloader
UCALEM Bootloader (no checks): This is the LEM bootloader will all the checks for AT&T ROMs removed from the flashing script. This can be flashed even if you're running a non AT&T ROM, but only flash it on AT&T phones!
LIST OF CHANGES IN OTA:
A full list of the files and partitions changed by the OTA is attached to this post.
Only 10MB? Wonder what they updated... not much need for it for me, Im on AOKP, but downloading anyways, and thanx button hit TWICE LOL
Let us know if it's a lockdown flash...
B-Naughty said:
Let us know if it's a lockdown flash...
Click to expand...
Click to collapse
Doesn't seem to be. I still have my CWM recovery and I was able to flash the KT747 Sammy kernel. The OTA did flash aboot (the bootloader?) though. It tried to flash a new recovery, but I removed that part.
drothenberger said:
Doesn't seem to be. I still have my CWM recovery and I was able to flash the KT747 Sammy kernel. The OTA did flash aboot (the bootloader?) though. It tried to flash a new recovery, but I removed that part.
Click to expand...
Click to collapse
Hmmm... guess we'll just to see what users report, but for the wise, to all, use the zip provided just in case... AND FOLLOW THE OP
when i try to do this I'm getting an error assert failed: apply_patch_check("/system/app/Flipboard.apk" E: error in sdcard/I747UCLG1_OTA.zip
dave1977nj said:
when i try to do this I'm getting an error assert failed: apply_patch_check("/system/app/Flipboard.apk" E: error in sdcard/I747UCLG1_OTA.zip
Click to expand...
Click to collapse
Did you remove Flipboard or install an update?
You have to be on stock UCALEM. The OTA applies binary patches to a bunch of apps (including Flipboard.apk), so they have to be in a specific starting state for the OTA to apply correctly.
drothenberger said:
Did you remove Flipboard or install an update?
You have to be on stock UCALEM. The OTA applies binary patches to a bunch of apps (including Flipboard.apk), so they have to be in a specific starting state for the OTA to apply correctly.
Click to expand...
Click to collapse
yes backed up from day 1 it may have auto updated can someone tell me the stock version # of flipboard or an apk would be great! so i can install it?
Thanks
dave1977nj said:
yes backed up from day 1 it may have auto updated can someone tell me the stock version # of flipboard or an apk would be great! so i can install it?
Thanks
Click to expand...
Click to collapse
Here you go.
drothenberger said:
Here you go.
Click to expand...
Click to collapse
tried that still the same error message need some help please....
Hmm, may want to consider removing the bootloader parts from the CWM until it's verified what exactly our friends at ATT had Samsung add to this. Updating bootloaders never is a good thing when it comes to ATT
dave1977nj said:
tried that still the same error message need some help please....
Click to expand...
Click to collapse
What recovery are you using? Maybe give the CWM 5.8.4.5 a try (in the OP) if you're not already using it.
pinoymutt said:
Hmm, may want to consider removing the bootloader parts from the CWM until it's verified what exactly our friends at ATT had Samsung add to this. Updating bootloaders never is a good thing when it comes to ATT
Click to expand...
Click to collapse
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
drothenberger said:
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
Click to expand...
Click to collapse
So if I'm on stock LG1 I flash rooted LEM and then flash your zip? Does your update include the baseband update ?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
mobilehavoc said:
So if I'm on stock LG1 I flash rooted LEM and then flash your zip?
Click to expand...
Click to collapse
I don't think I understand. You're already on UCALG1, but you want to apply the OTA to go from LEM to LG1? Why?
If you do want to do that, you do need to flash the rooted LEM tar through Odin. Then follow the rest of the instructions in the OP.
Does your update include the baseband update ?
Click to expand...
Click to collapse
Yup. It includes everything except the Google search update, recovery, and (optionally) the bootloader.
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Odin back to pure stock working fine.. some of my apps fore close though
drothenberger said:
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
Click to expand...
Click to collapse
Many thanks! You never know what kind of goodies they like to through in new bootloaders, so better safe than sorry!
ewingr said:
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Click to expand...
Click to collapse
I think there are only two ways to get rooted LG1: Start with rooted LEM and use OTA Rootkeeper to keep root when you apply the OTA or use the method in the OP. In your case, you'd have to Odin back to the rooted LEM to get root, then if you want to go back to LG1, follow the OP steps.
ewingr said:
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Click to expand...
Click to collapse
Depends which method of rooting you want to use. If you are interested in the method that does not trip the counter, then yes you would flash that through ODIN (which will technically revert you back to UCLEM with root injected) and then apply the update in the OP here and in the end you should be on a a rooted UCALG1 w/o a tripped counter.
Anyone wanna pull just the baseband for cwm zip?

Flashing Stock Recovery?

Okay, so I installed Clockword Recovery and ROM Manager so that I could get Jellybean early. And it was awesome. But now I'm getting bugged about the OTA update, and I kinda want that. Ofcourse, Clockwork Mod Recovery won't let me install OTA, so how can I go back to stock recovery? Because I dislike the idea of not having OTA updates anymore...
Hopefully before you get hundreds of rude entitled responses you should check out some of the stickies on the various forums. I believe there is one with a title that matches exactly what you are looking for
If not having stock recovery is the only problem (and there are a number of other reasons an OTA update could fail to install), you can definitely use ClockworkMod to install it.
If the update has already been downloaded to the phone, the zip file will be stored in /cache. Just boot into CWM and flash it. If the update hasn't been downloaded, grab zip file yourself (take a look at the OTA update URLs thread) and flash it using CWM.
If you're rooted, don't forget to also flash SuperSU before you reboot, or use some other method to maintain root. OTA updates will remove root regardless of how they are installed unless you take care.

OTA Update

I have rooted my Nexus 7 wifi 2012 tablet with TWRP
I don't want to keep un-rooting, applying ota updates then re-rooting my tablet. Is there an easy way. Maybe modified images i can use on a rooted tablet which i can install via the install option in twrp recovery loader.
I also notice that Nexus root tool kit has a ota sideload update option in the advanced menue.
So my question is where are the modifies ota update files if they exist as I don't want to keep un-rooting, rerooting each time to apply official ota updates. I have searched the net and can't find modifies ota updates?
My OTA failed due to root and modifications so I extracted system.img and boot.img from the 5.1 tarball and flashed them using Nexus Root Toolkit. Works well.
I'm going through the same issue - I want to keep running stock, but every time an OTA update comes in, it bugs me for an update until I go through the whole process of finding the files elsewhere, using the Toolkit to flash them etc etc.
Is there a better way to do this automatically? Can I find the downloaded OTA package on the Nexus and just flash it from there?
Since Lollipop, you can't take an OTA in any way (official or sideload) if you've modified your system. Rooting, custom recovery or kernel. Unrooting does not help since the system already has been modified.
Easiest way to upgrade and still keep your data is to flash the factory image but leave out userdata.img. This can be easily done through NRT (No wipe mode) if command prompt is scary. Yes you'll have to reroot... But hey, this is a Nexus, it's easy.
I assume that means waiting for someone to post the update?
If you want to wait for someone to make a prerooted image, then yes. Otherwise just download the official factory image (Google it) and go for it.
Google doesn't always release OTAs and factory images at the same time, so some waiting will probably always be involved...
Drives me crazy. TWRP used to be able to intercept a OTA flash, flash the needed images, detect you lost root and ask to restore root.
Somewhere that disappeared.
I just flashed a very old stock and took every OTA to 5.0.2, rooted, setup... now getting bombarded with 5.1.1 update notification. Ugh
Didgeridoohan said:
Since Lollipop, you can't take an OTA in any way (official or sideload) if you've modified your system. Rooting, custom recovery or kernel. Unrooting does not help since the system already has been modified.
Easiest way to upgrade and still keep your data is to flash the factory image but leave out userdata.img. This can be easily done through NRT (No wipe mode) if command prompt is scary. Yes you'll have to reroot... But hey, this is a Nexus, it's easy.
Click to expand...
Click to collapse
I need to flash the latest lollipop image to my rooted nexus with TWRP. I know where to find the images but don't remember how to flash it. What exactly are the steps and how do I leave out userdata.img ?
And what are the steps to reroot lollipop?
Thanks
i keep getting the offer to download the 5.1 update but when i do it dloads it then tries to reboot into recovery to flash it but it obviously boots into TWRP recovery which is no good.
So the question is when it dloads the update where does it dload to?
and could i flash it from TWRP if i find it?

Categories

Resources