Develop Bugs

[Q] OTA failed - how do I check my status?

I've been receiving [incessant!] prompts that an OTA update was ready to install on my phone.
So - I unrooted my phone and replaced the stock recovery using this process.
Following that, I checked that I no longer had root, and booted to recovery to confirm it was the stock recovery... and then back into the phone to finally tap the "install" button when prompted.
The phone rebooted into the stock recovery, started to install the update... then, in red text - an ERROR message (that I failed to capture because after a few minutes the phone just went to an android with a red ! triangle over it).
I had to pull the battery since the buttons didn't do anything and there were no other options. The phone booted back into recovery, and then I got some sort of confirmation message in yellow text that sounded like "success", and I was still in the stock recovery.
So, I selected the "reboot" option and booted back into the phone.
All seems well (I'm still 100% stock, not rooted), but I am completely unclear if the update worked or failed.
If I go to "system update", I get messages in all four categories:
( i ) Error
The PRL update could not be
completed. Please try again later.
If the problem persists, you may
need to contact Customer Service.
Error: (Code:4)Client Authentication
Error
Click to expand...
Click to collapse
The Update Profile, Update Samsung Software, and Update Firmware all return the same error message.
How can I check the status of my device?
Any ideas what these errors indicate?

Looking for an answer on this- either:
1) What does "Error: (Code:4)Client Authentication Error" indicate when checking for updates in the System Update category?
and/or
2) How do I check to confirm if the OTA update completed successfully?
On a side note - I'm also interested in learning what is/was in that update. The answer to 2) might help me find a thread specific to that OTA update.
Help is appreciated, thanks.

Are you using a custom recovery like CWM or TWRP?

The Root said:
Are you using a custom recovery like CWM or TWRP?
Click to expand...
Click to collapse
No. As described in the first post -
I had previously rooted my phone and installed CWM recovery (to flash a 'root from recovery' update).
Since I was receiving this update notification, I followed the process in the link I posted to unroot and restore the stock recovery. I booted into recovery to confirm the stock recovery was back. Then I accepted the OTA update, and the process went as described.
Also, Hardware Version (in 'About Device' in settings) no longer shows "modified" status. I'm still un-rooted / stock recovery.
Should the update have changed my version? I'm showing PLG8 for baseband version.
As mentioned, the appearance is that I can't force the phone to check for a new version due to the error message I get in the System Update categories, so I'm unclear whether the OTA applied, didn't apply, if it caused an issue, or if this is all normal?
What would indicate that the OTA update applied? Baseband version number? What should it be?
If you check for a System Update on your device, do you get this same message that I'm seeing?
Thanks!

geolemon said:
Since I was receiving this update notification, I followed the process in the link I posted to unroot and restore the stock recovery. I booted into recovery to confirm the stock recovery was back. Then I accepted the OTA update, and the process went as described.
Also, Hardware Version (in 'About Device' in settings) no longer shows "modified" status. I'm still un-rooted / stock recovery.
Should the update have changed my version? I'm showing PLG8 for baseband version.
Click to expand...
Click to collapse
When you went through this step what version of ICS were you on? Also, did you erase any system apps? Sometimes this can stop the update from processing. The newest version is LI3 and should be reflected in your baseband. There were like 2 updates that got you to LG8 originally so if you had restored to an earlier version you might have been getting the update to LG8, but then again if it failed obviously you wouldn't be on LG8 now... Hard to say. Would need to know more about your setup.

The Root said:
When you went through this step what version of ICS were you on? Also, did you erase any system apps? Sometimes this can stop the update from processing. The newest version is LI3 and should be reflected in your baseband. There were like 2 updates that got you to LG8 originally so if you had restored to an earlier version you might have been getting the update to LG8, but then again if it failed obviously you wouldn't be on LG8 now... Hard to say. Would need to know more about your setup.
Click to expand...
Click to collapse
Thanks.
No - All stock. LG8 I believe.
All I did was root my phone using the first two links on this thread (install CWM recovery, then root from recovery):
http://forum.xda-developers.com/showthread.php?t=1743780
And unrooted it using the last link on that original post in that thread (unroot and stock restore).
Nothing was changed, all stock.
Only rooted it to provide an emergency means of tethering if necessary on a work trip.
Superuser app was added (and was removed on stock restore), and Wifi Tether app was installed.
Is the update to LG8, or LI3?

geolemon said:
Thanks.
No - All stock. LG8 I believe.
All I did was root my phone using the first two links on this thread (install CWM recovery, then root from recovery):
http://forum.xda-developers.com/showthread.php?t=1743780
And unrooted it using the last link on that original post in that thread (unroot and stock restore).
Nothing was changed, all stock.
Only rooted it to provide an emergency means of tethering if necessary on a work trip.
Superuser app was added (and was removed on stock restore), and Wifi Tether app was installed.
Is the update to LG8, or LI3?
Click to expand...
Click to collapse
If you're on LG8 it should be the update to LI3. Have you Odined to stock, stock?
Sent from my SPH-L710 using xda app-developers app

I may be misunderstanding the question... clicking that link may help.
I was 100% stock prior to a client visit two weeks back. I rooted following the process in that link.
In brief (using files in that link)
1) installed CWM via Odin
2) use CWM to flash "root from recovery" file
This week I started getting prompted there was an OTA.
Knowing I at least needed stock recovery or it would fail,I restored back to stock following the restore process in that link.
In brief (using restore files in that link):
1) flash unroot file via CWM
2) use Odin to flash stock recovery.
I used root checker to confirm root was gone, rebooted to recovery to confirm CWM was gone, booted back to phone and accepted the OTA.
The phone then booted into recovery and events occurred as described in post 1.
Anything unusual spotted with the process?
Sent from my Nexus 7 using xda app-developers app

Here's a screen capture of the update error message:
Sent from my SPH-L710 using xda app-developers app

Why not re-root, flash CWM or TWRP, then flash the rooted LI3 ROM here: http://forum.xda-developers.com/showthread.php?p=28116723
Wish I could help with the actual error you're receiving in stock recovery, but at least this way you will have LI3, which seems to be what you're wanting to accomplish.
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!

DrgnRebrn said:
Why not re-root, flash CWM or TWRP, then flash the rooted LI3 ROM here: http://forum.xda-developers.com/showthread.php?p=28116723
Wish I could help with the actual error you're receiving in stock recovery, but at least this way you will have LI3, which seems to be what you're wanting to accomplish.
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!
Click to expand...
Click to collapse
Not a bad suggestion, at least fundamentally. However - I wasn't pleased after rooting previously that my device status showed as "modified", which then caused my Google Wallet app to constantly display a warning and have transactions appearing in an "unknown" status because of 'compromised security due to modified device status', and all that. Ugly.
I also wasn't able to consistently tether, in fact more often than not could not. I can't prove this ties somehow to a 'modified' status, but since that was my primary reason for rooting (and since the tethering was for an "if needed" to VPN in on a business trip (think 'spare tire') I only want to root again if I can:
1) tether consistently and reliably (I'm traveling again on the 20th)
2) do so without the device status showing as "modified".
Otherwise, I'd prefer to leave my device stock, where at least stock apps work as supplied.
Does that method impact the device status?

geolemon said:
Not a bad suggestion, at least fundamentally. However - I wasn't pleased after rooting previously that my device status showed as "modified", which then caused my Google Wallet app to constantly display a warning and have transactions appearing in an "unknown" status because of 'compromised security due to modified device status', and all that. Ugly.
I also wasn't able to consistently tether, in fact more often than not could not. I can't prove this ties somehow to a 'modified' status, but since that was my primary reason for rooting (and since the tethering was for an "if needed" to VPN in on a business trip (think 'spare tire') I only want to root again if I can:
1) tether consistently and reliably (I'm traveling again on the 20th)
2) do so without the device status showing as "modified".
Otherwise, I'd prefer to leave my device stock, where at least stock apps work as supplied.
Does that method impact the device status?
Click to expand...
Click to collapse
I searched XDA for "Change modified status" and this was the third result: http://forum.xda-developers.com/showthread.php?p=22462960
1) I've had great success using the wifi tether app. I connect through VPN to my company all the time with it. Also, there is a plethora of support posts related to troubleshooting wifi tethering. Search "wifi tether" and start reading. If you cannot get it done though, then go back to stock & pay to use the tether service through Sprint.
2) I searched on XDA for "Google Wallet" & this was the very first result: http://forum.xda-developers.com/showthread.php?p=28679456
Rooting is not for everyone. There's no shame in being stock.
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!

DrgnRebrn said:
I searched XDA for "Change modified status" and this was the third result: http://forum.xda-developers.com/showthread.php?p=22462960
1) I've had great success using the wifi tether app. I connect through VPN to my company all the time with it. Also, there is a plethora of support posts related to troubleshooting wifi tethering. Search "wifi tether" and start reading. If you cannot get it done though, then go back to stock & pay to use the tether service through Sprint.
2) I searched on XDA for "Google Wallet" & this was the very first result: http://forum.xda-developers.com/showthread.php?p=28679456
Rooting is not for everyone. There's no shame in being stock.
Samsung Galaxy S3
OdexedBlue ROM
LI3 Stock Kernel
LIF Baseband
XDA Premium - Support our developers, modders, & themers!
Click to expand...
Click to collapse
I'm over the novelty of rooting, that's all, years ago. Going back to my G1 (the first Android phone ever!), I rooted that one even.
In the case of my Magic (basically a G1 without a keyboard), it was really to extend it's life, I was running custom ROMs on both the G1 and Magic (CM6), was a great option. Kept it a long time, loved that phone actually. Still miss a trackball.
Here, I rooted for a specific purpose - and actually the Wifi Tether app was the one I used, since I've had experience with it on my other phones. Always worked flawlessly, going back to the Magic days even.
But on the GS3 - I don't know if you've tried it or not - it's not reliable. You'll find threads for it (I worked through several of them in the airport trying to get it working, using different profiles, different settings, even sideloading an older APK that predated the GS3 profile, as some users mentioned that as the path. Bottom line regardless - it's just not 100% on the GS3. I spent somewhere close to 2 hours, 1 of that in the airport, reading through threads and troubleshooting suggstions, none were 100%.
And I wouldn't pay for it, we travel with MiFi devices that the company pays for. This was just a backup plan, me being a nice guy. Thought it would be easy, as it always has been in the past. There's something unique to this phone that's very different than others, not sure if this is your first, but other phones are usually simple... root, use Wifi tether. No hassle.
So, that being the case (or until an option exists for tethering that is reliable), I don't have much need for root. Even Titanium Backup. Would be nice to do nandroid backups, but if it's all stock... should be no real need.
I didn't read that thread (yet), but there's an "everything about Wallet" thread here. That one may be linked... Wallet works, I haven't had a problem with it not working, but with the device in a Modified status, it gives you some eyebrow raising warnings.
I believe that thread is actually for people who didn't read that "everything about Wallet thread", have flashed a custom ROM without clearing Wallet, and as a result now find themselves in tears with a locked/bricked Wallet. That'll make some people happy.
If my device is going to show a "modified" status, with the (hopefully few) risks inherent in that (ie. Sprint support), I'll at least go to a JB leak ROM or CM10 or similar and get some bang for my commitment, as opposed to the "least modified possible" route yet showing modified status. I just had no need to yet, not looking forward to wiping my phone, reinstalling, reconfiguring.
Triangle Away has been around a long time too - I didn't bother with it when I rooted because of this disclaimer:
- On the SGS3/Note2/etc, System->Settings->About device->Status still shows "Modified"
This is outside the scope of Triangle Away. The "system" status is not even always resettable in the bootloader. If you are going for warrenty, you need to also reflash a full stock firmware and wipe your device. If they boot up your device and find root apps, you're not going to get any warranty anyway. If you do such a full stock reflash and wipe, the "Modified" value will go away.
Click to expand...
Click to collapse
The Modified status did go away when I flashed the stock recovery back. Wallet is my only concern with that status btw, it's slick how it gives you transaction statuses, however it apparently leaves many of them as "unknown" in this state, which I'd like to fix (or stay stock for now).

workaround to the OTA 4.1.2 with red triangle signal

My phone prompted me to update to 4.1.2. Everytime I press install, it would boot and then stops half way with a red triangle icon. A few minutes later it will boot to 4.1.1. Someone suggested that it may be due to build.prop file. I mucked around with the build.prop trying to get google wallet to work. I don't care about the wallet anymore. All I want is to upgrade to 4.1.2 with no data loss.
Someone on this forum suggested using the GNex TOOLKIT V9.1 to flash Google Stock Image to phone and then the OTA update would work. If I do that, will I lost any data on the phone?
Sorry, NB to android. Thanks.

you messed with system files, the OTA will not install because of that.
you need to replace the files you modified with the original build.prop and any other files that you modified
if you want to go to stock: http://forum.xda-developers.com/showthread.php?t=1626895

Ahh ... it took me a while to get my gnex configured to the way I want. That method sounds like a clean method but at the same time will wipes everything I have configured so far.
I should probably create a second thread to ask a different question, is there a way to disable the 4.1.2 OTA notification nag? I will keep this phone for another month or so before I pass it to someone else.

If you don't care about any changes you've made to the system partition, you can just flash the boot and system images. This will keep your data.
I upgraded this way before the official OTA was out. It will, of course, blow any changes you've made to /system away, but it will keep your user data and all your settings, etc. You normally don't upgrade by "dirty flashing" over top of another system, but nobody I've seen has reported any issues with going from stock 4.1 to stock 4.1.2 this way. I did it, and have had zero issues. Always take a nandroid backup if possible, just in case.
Follow efrant's guide, just only flash boot and system (and NOT userdata)

How to update from stock root 4.1.1 to current?

I'm sure this has been addressed but I can't seem to find a definitive answer. I am bone stock (stock recovery and no custom rom) with just root on AT&T.
There are no missing deleted apps, as I replaced them previously but I still have never been able to do any of the OTA updates. It's starts and then fails.
Is there a way to unroot and the do an OTA update? I am trying to avoid Odin so I dont have to wipe everything and then have to start all over and adjust settings to my liking an also reinstall all of my apps.
I seen there is an option in the Super User app to "completely unroot and uninstall". Will choosing this option allow me to finally do OTA?
I've never installed a custom recovery or a custom rom so I don't know why OTA's always fail. At this point, I dont really care about having root since the only reason I previously wanted it was to remove at&t bloatware but I'd rather have OTA's at this point.
Any advice or direction would be greatly appreciated! Please speak slowly and in layman's terms as I am an old fart that is still a bit of a n00b, lol.
Thanks!!
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

n01un0 said:
I'm sure this has been addressed but I can't seem to find a definitive answer. I am bone stock (stock recovery and no custom rom) with just root on AT&T.
There are no missing deleted apps, as I replaced them previously but I still have never been able to do any of the OTA updates. It's starts and then fails.
Is there a way to unroot and the do an OTA update? I am trying to avoid Odin so I dont have to wipe everything and then have to start all over and adjust settings to my liking an also reinstall all of my apps.
I seen there is an option in the Super User app to "completely unroot and uninstall". Will choosing this option allow me to finally do OTA?
I've never installed a custom recovery or a custom rom so I don't know why OTA's always fail. At this point, I dont really care about having root since the only reason I previously wanted it was to remove at&t bloatware but I'd rather have OTA's at this point.
Any advice or direction would be greatly appreciated! Please speak slowly and in layman's terms as I am an old fart that is still a bit of a n00b, lol.
Thanks!!
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
If you are on stock and have a valid AT&T SIM card in the device with full access to Wi-Fi and the AT&T network, you should be able to get an OTA update. Root could, however, indeed prevent an OTA update so your best bet may be to unroot. You could unroot and uninstall SuperSU from the SuperSU app just as you suggested. This should do it. However, if it doesn't and you would really want to avoid Odin and custom recovery, then you could do a 2-step manual update to 4.3 via stock recovery - first to 4.1.2 and then to 4.3. This will naturally update your phone to (full) stock 4.3 and we can then see if the phone will take the Kit-Kat OTA update from there.
You can see the instructions for the 2-step update via stock recovery in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2387423
1) Download the 2 zip files under update412.zip and update43.zip respectively to your computer
2) Copy the zip files to a good quality (micro) SD card
3) Place the card in your phone and boot to recovery mode by simultaneously holding down the Volume Up, Home and Power buttons
4) Hold the buttons until you see a blue message flash across the screen. Then release the Power button but continue to hold the Volume Up and Home button until you see the Android image appear. Then release the buttons
5) Use the volume up/down key to scroll to <mount from external storage> and the power button to select
6) Navigate to the first zip file (update412.zip) and install. Wait for installation to finish and your phone to reboot.
7) Complete set up. Check your phone settings. Then power off and reboot to recovery again.
8) Repeat the process for the second update file.

Well I tried the unroot feature in SuperSU and then uninstalled it.
I then tried the OTA update again and as usual, it failed about 30-40% in.
Ive never installed a custom recovery or a ROM so I don't get it. All I did was use Mr.Robinsons thread/directions on "how to root without tripping...." just for root only in the sticky.
I give up.:banghead:
Thank you though for responding. I may try the alternative way you suggested when I get time tomorrow and see what happens. Either that or screw it, im stuck with 4.1.1 and now I don't even have root. :banghead:
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app

n01un0 said:
Well I tried the unroot feature in SuperSU and then uninstalled it.
I then tried the OTA update again and as usual, it failed about 30-40% in.
Ive never installed a custom recovery or a ROM so I don't get it. All I did was use Mr.Robinsons thread/directions on "how to root without tripping...." just for root only in the sticky.
I give up.:banghead:
Thank you though for responding. I may try the alternative way you suggested when I get time tomorrow and see what happens. Either that or screw it, im stuck with 4.1.1 and now I don't even have root. :banghead:
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
There have been several reports of failed OTA update so you may not be alone here. The process I advised is sure to take you to 4.3 JB without hassle. There is, of course, a manual update process from 4.3JB to 4.4.2 Kit-Kat (the latest OS). You will, however, require custom recovery for this ...
http://forum.xda-developers.com/showthread.php?t=2788357

Larry2999 said:
There have been several reports of failed OTA update so you may not be alone here. The process I advised is sure to take you to 4.3 JB without hassle. There is, of course, a manual update process from 4.3JB to 4.4.2 Kit-Kat (the latest OS). You will, however, require custom recovery for this ...
http://forum.xda-developers.com/showthread.php?t=2788357
Click to expand...
Click to collapse
Well I finally was able to update via OTA. I had to actually use Kies and reinstall firmware and then go through all the updates, starting from scratch and took forever. What an absolute pain in the ass. Plus, after all this work to go from 4.1 to 4.4..........I can't see where it was worth it. I am now going through the tedious task of setting up all the settings and widgets and everything else the way it was or the way I like. So much for Kies actually backing up and "restoring" anything.
I have a couple of questions though....
1. Now that I am on 4.4..........how do I root this version (that works). I was reading the thread saying to use towelroot but it's not confirmed if this is still working after I guess you do the OTA after a certain date and it's now patched. I DO NOT want to install custom roms or anything else. All I want is root so that I can remove the AT&T crapware that is now even worse with this phone on 4.4.
2. I have a battery percentage that is in the LEFT upper corner that I can not figure out what program or app it is associated with and I can not get rid of it. This is not the % indicator that is part of Android and next to the battery icon on the right which is on and is okay, this is one the left.
3. I hate the new PIN lockscreen because the keypad/numbers are so small compared to old version. Any way to fix this?

n01un0 said:
Well I finally was able to update via OTA. I had to actually use Kies and reinstall firmware and then go through all the updates, starting from scratch and took forever. What an absolute pain in the ass. Plus, after all this work to go from 4.1 to 4.4..........I can't see where it was worth it. I am now going through the tedious task of setting up all the settings and widgets and everything else the way it was or the way I like. So much for Kies actually backing up and "restoring" anything.
I have a couple of questions though....
1. Now that I am on 4.4..........how do I root this version (that works). I was reading the thread saying to use towelroot but it's not confirmed if this is still working after I guess you do the OTA after a certain date and it's now patched. I DO NOT want to install custom roms or anything else. All I want is root so that I can remove the AT&T crapware that is now even worse with this phone on 4.4.
2. I have a battery percentage that is in the LEFT upper corner that I can not figure out what program or app it is associated with and I can not get rid of it. This is not the % indicator that is part of Android and next to the battery icon on the right which is on and is okay, this is one the left.
3. I hate the new PIN lockscreen because the keypad/numbers are so small compared to old version. Any way to fix this?
Click to expand...
Click to collapse
Glad to know you were finally able to update. To try to answer your questions ....
1. Towelroot indeed comes well recommended for rooting on Kit Kat. You could, however, first try CF Auto Root which is one of the simplest approaches to rooting. If this doesn't work, you could try Option 2 in the thread below ... The thread also contains instructions to CF Auto Root.
http://forum.xda-developers.com/showthread.php?t=2538991
2. I'm not sure what that battery indicator is. I run 4.4.2 also on my S3 but I cant see this. Can you try a reset to see if it would go away?
3. You can try removing this from settings.

Im glad you asked this...
I too noticed Im on 4.1.1 stock but rooted. I wondered if you could go to 4.4.2 as my phone tried to OTA update on its own last week and failed. I did not know if it was worth it to try or not another way. About the only thing I see that would want me to try is Google Wallet now working with S3 on 4.4.2 without having to jump through all kinds of hoops, mine used to work fine, but now GW will not open up all the way. Im not sure its worth doing if I have to re setup all my crap as I will be upgrading my phone whenever I want, just holding out to see if the Nexus 6 will be out end of the year and on AT&T..Im not liking that all the new phones are getting so freakin big, the S3 is just right and I dont want to have to end up with a damn Note sized phone but that is a whole other discussion

If you're still on 4.1.1, BEFORE ANYTHING ELSE, UNLOCK YOUR PHONE IF HASN'T ALREADY
otherwise you'll regret it
then the rest, tbh, you don't need to unroot at all to upgrade, just flash the firmware in ODIN or recovery..
edit: nvm it seems like you've already upgrade yours to KitKat

[Q] 4.1.2 to 4.4.2

Hi everyone.
I’m currently on rooted SGH-i747M(Rogers) 4.1.2, and I'm trying to find out how to upgrade to 4.4.2 and keep it rooted.
Since my device is already rooted it won’t let me update to the latest firmware.
What would be the proper procedure to move to 4.4.2 rooted?
and does it worth it to upgrade to 4.2.2? I'm asking because I've seen posts on how to downgrade to 4.1.2 from 4.4.2.
Thanks so much in advance.

Once you upgrade to 4.3 or 4.4.2, you cannot downgrade to anything before 4.3.
Is your phone carrier unlocked? If not, I suggest downgrading to 4.1.1, unlock it, then start upgrading the stock ROM.
The easiest way would be to flash back to stock non-rooted 4.1.1, unlock it, and start updating via OTA or use desktop Odin to flash a stock Rogers ROM from sammobile.com.

stssific sarah
audit13 said:
Once you upgrade to 4.3 or 4.4.2, you cannot downgrade to anything before 4.3.
Is your phone carrier unlocked? If not, I suggest downgrading to 4.1.1, unlock it, then start upgrading the stock ROM.
The easiest way would be to flash back to stock non-rooted 4.1.1, unlock it, and start updating via OTA or use desktop Odin to flash a stock Rogers ROM from sammobile.com.
Click to expand...
Click to collapse
Thanks alot for the tips!
I'm on Rogers and I don't remember doing any unlocking.
So do I download the stock 4.1.1 also from sammobile.com and use Odin to downgrade to it?
And after I unlock it on 4.1.1, do OTA update to 4.4.2., and then root it?

newbie386 said:
Thanks alot for the tips!
I'm on Rogers and I don't remember doing any unlocking.
So do I download the stock 4.1.1 also from sammobile.com and use Odin to downgrade to it?
And after I unlock it on 4.1.1, do OTA update to 4.4.2., and then root it?
Click to expand...
Click to collapse
Exactly. That's what I did with my Bell s3. Make sure you are not rooted and running stock recovery before running OTA updates.

audit13 said:
Exactly. That's what I did with my Bell s3. Make sure you are not rooted and running stock recovery before running OTA updates.
Click to expand...
Click to collapse
On 4.1.1 what unlocking method did you use?

http://forum.xda-developers.com/showthread.php?t=2176719

This is my experience with the T999 model but it should be the same here. Personally I hate otas, so I avoid them if at all possible.
You shouldnt need to flash the full 4.1.1 firmware to do the unlock. Just the modem. Then flash the 4.4.2 firmware via odin after unlocking. Reroot and youre done.
Nothing wrong with how audit13 suggested btw. Itll work that way too. Just offering an alternative.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Thanks to you all, I'm now on rooted 4.4.2 with CWM.
One thing I missed is to backup the rom using CWM. I've already restored all my previous apps and data using Titanium Backup, and I had to go through a lot of troubleshooting with errors like *Unfortunately ***** has stopped." I think everything's working well now though. Should I still do backup in CWM or is backing up with TB enough?
My second question is that it seems to drain battery more. When I wake up this morning the battery was only at 85% or so. I have it plugged in now but it's charging very slow. Is this a known issue with a fix?

Did you restore data and settings for system apps? If so, this can cause issues if done from one build to another, such as battery drain, force closes and degraded performance.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Did you restore data and settings for system apps? If so, this can cause issues if done from one build to another, such as battery drain, force closes and degraded performance.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I did TB-> Batch Actions -> Restore all apps with data. Right below there is 'Restore all system data' which I didn't do, but I'm not sure if that 'all' includes system data as well?
The selections under Restore section in Titanium Backup were the following:
RUN: Restore missing apps with data
RUN: Restore all apps with data <<=== this is what I did
RUN: Restore all system data
RUN: Restore missing apps + all system data
RUN: Restore newer versions of user apps
I recharged to 100% then performed a Battery Calibration using an app, but 20% just got drained in an hour and half of pretty much all standby time(screen off).

I would factory reset, reboot and let it sit for a few minutes. Then using titanium, restore only essential apps and data first. You should be able to use the batch restore and then select from a list what you want to include. Test for a bit to see if anything you restored causes problems. If not restore a few more and test. Do this until you narrow down what is causing your problems.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

You're right. I should just do that.
I was following the root method at galaxys3root.com, and the files I was told to use were UPDATE-SuperSU-v2.01, Odin3 v1.85 and CWMS3ATTrecovery.tar in which there was image.img without any version number.
I did some digging and found Odin3 v3.09 which seems to be the latest version. Then I went to http://www.clockworkmod.com/rommanager to download the CWM from the original source, but they're all img files and odin wants a tar file. How do I put this into a tar file, and do I need to rename any? I just want to do everything right this time. Would DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V2.1 be a good idea as well?
edit: oh never mind I went into the CWM and saw the version was 6.0.4.7 which is the latest. So I'll just use the same files again for root.

I just did a factory reset, and the CWM and the root as well as superSU are not lost. Is this normal? I thought factory reset takes away the root... Also I just checked in download mode that the Warranty Bit is now 1. It was 0 when I first rooted, so I'm guess the resetting might have done that. Oh well...

Custom recoveries and kernels are what usually trip the warranty bit, so if you installed cwm, thats what tripped it. I wouldn't worry too much over it. Warranty claims are pretty rare, and a lot of people have reported their warranty was honored even though the bit was tripped.
Root will remain after resetting because it is on the system partition. Factory reset only wipes /data.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

After factory reset I only restored some of the apps this time, and for many of them I restored only the data. But this battery drain issue is still there. It not only drains battery but in the morning when I woke up the lock screen didn't want to come on. I pressed the power button, and the three physical buttons' LED lights were lit but the screen remained blank. It took a long time until the lock screen comes on but it didn't respond to touch, acting very very laggy until I reboot. I tried wiping dalvik cache(although I wasn't quite sure what it was) in restore mode but it didn't help.
I learned about battery drain monitor apps and downloaded Wakelock Detector. It was showing that my AVG Antivirus Pro is awake all the time taking a lot of battery, and I'm not quite sure if it's supposed to be that way since it should be running in the background all the time. But this seem to be still too much. Can I just assume at this point that the Antivirus is what's causing the issue?

I've seen others recommend wakelock detector, but I'm not familiar with it myself. But I doubt your AV should be using that much, nor should Android System. But a dead giveaway that there's a problem lurking is it only spent 1 second in deep sleep. And 7.5 hours awake with the screen off.
Looking at the wld screen, it certainly seems like AVG is the problem, or at least a big part of it! I'm not sure it's the only one though with your system use being so high in the first screen shot.
I'd suggest uninstalling AVG and test it at least for one full cycle. Also, look to see if wld is able to log kernel wakelocks. In better battery stats you have to set it to do so in settings if I remember right.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Lollipop Update issue

I have a Note 4 on Sprint, still running KitKat. Here's my problem:
I really don't want the Lollipop update. I don't want it because I love KitKat so much and I tried Lollipop out on my friend's phone and hated the look and feel of it. I don't want it to finish downloading because I hardly have any space on my phone as it is.
I don't want to
-root my phone
-factory reset my phone
-trip Knox
Right now, I'm pretty angry because I'd like to use WiFi, but can't because every time I turn it on the update starts to download. I tried going into settings and turning off auto update, but that didn't stop it. I also tried filling my device storage so that there were less than 800 megabytes left, but that had no effect on the update either, it just continues downloading. I realize that there are similar posts on this issue, but none of them really apply to me. Thank you in advance for any help.

Just update it then use a kk theam the update will help i dont think you can stop the ota update

chad.420.419 said:
Just update it then use a kk theam the update will help i dont think you can stop the ota update
Click to expand...
Click to collapse
Thank you for replying, but that really doesn't help me at all. As I said several times over in my original post, I don't want the update at all. I'm constantly hearing about people choosing to keep KitKat, so there must be some way. And even if I could apply a theme to my whole phone without being rooted, it wouldn't fix all the other problems that I have with lollipop.

But the 3 things to consider or note before you begin:
1) if you update beyond OB7, the bootloader gets upgraded to one with a reactivation lockable bootloader. That will prevent you from being able to Odin back to KitKat. You need to disable auto update and stop the update notices before they start; otherwise the nags persist and you may accidentally update.
2) the lollipop file system is different than KitKat do better off formatting your data and wiping cache and dalvik-cache and powering down and pulling battery prior to Odin OB7 stock tar. Let it boot and setup wizard prior to Odin of TWRP (uncheck auto reboot for recovery flash only), boot into TWRP recovery and flash the ROM.
3) dalvik gets built on initial boot of lollipop ROMs; the stock tar still not much quicker. You'll likely see the phone hang at the second boot splash screen with blue LED slowly blinking before you see the app optimization and app start pop-ups. You can expect that with lollipop. Give it 30 minutes to boot before you panic. To avoid CPU heating and slowing the process, remove your phone from its case and ventilate if it gets too warm. You need to start with battery charged to about 80% to full to be safe. It's best to not try and update apps or restore apps until you've flashed and booted the custom ROM. More apps means the process takes longer. You can format the data again prior to flashing the custom ROM to speed things along. If possible, backup your media, and downloads that you want to keep and wipe internal sdcard to get a cleaner start with lollipop. That's optional but don't lose your keepsakes. What you flash should be on extSdCard to avoid the wipe-loss if it.
BTW, the post you're referring to may have been an attempt to recover phone after attempting to downgrade to OB7 or KitKat. It's since been discovered that although Odin wouldn't downgrade, there's a possibility to flash older ROMs in recovery and immediately flash a 5.1.1 rooted kernel to get it to boot without looping. That doesn't have to apply to you; the general rule is to Odin flash the tar that matches the ROM you want to flash in recovery. But again, if you upgrade beyond OB7, you cannot go backwards with Odin. Only few exceptions apply; generally it is forward, not backwards. OB7 is the divide that separates the simple from more complex conditions. So these last 3 paragraphs shouldn't apply to you as long as you're wanting to stay with OB7 or KitKat.
Just for an idea of what to consider in other lollipop updates. The ram optimization got a bit crazy after OB7 and continued until it improved in OJ6. Personally, I think OJ6 and OK1 updates are the best lollipop updates yet. You'll certainly find more security updates in those updates. But lollipop 5.1.1 also introduced the need to root the kernel but Chainfire has recently brought us a patch to use stock kernel again; it's married from experimental to beta. I've mostly ran with stock kernel on my phone, especially before lollipop 5.1.1
Things were once simpler but got a tad more complex as time and updates followed OB7.
Sent from my SM-N910P using Tapatalk

7H3N3RD said:
I have a Note 4 on Sprint, still running KitKat...
I don't want to
-root my phone
-factory reset my phone
-trip Knox
Right now, I'm pretty angry...
Click to expand...
Click to collapse
That's a tough ask for a definitive answer, IMO. IDK if it can be done but I'll offer an idea for discussion. Consider pros and cons and alternatives and even constructive differing because l don't know if it's been tried and proven to stop the persistent update on stock KitKat. There are root alternatives but your request is taken into some consideration below.
Odin stock tar will not trip Knox or require root. There are 2 stock tars for KitKat (those end with NIE and NK2, last 3 letters only, NIE being the original, NK2 the last KitKat update).
My theory is that you could...
1) Odin the first tar, NIE stock tar is linked below, let it download the OTA for NK2 but postpone the update long enough to go into Settings/System update/Auto update and uncheck the option.
2) Turn phone off and boot into recovery. It should find the NK2 update and prompt to apply it. If not there's an option to apply from cache, I think.
3) Once booted, make sure the auto update is still unchecked.
https://www.androidfilehost.com/?fid=95784891001612590
The instructions for Odin stock tar are found here but early posts in that thread may be relative to Odin if stock KitKat tar. The stock tar above is actually linked in post #2
http://forum.xda-developers.com/showpost.php?p=56853325&postcount=1
If auto update resets during the process, it most likely promptly starts the OTA download, negating the effort. No guarantees but reason the risks before you proceed. That's the whole theory, if someone knows the system update gets reset to auto or if that's not enough to prevent it, please advise. On a rooted Lollipop phone, uncheck auto update seemed to be enough to prevent the OK1 update from downloading and being persistent to update... I may have overlooked something in my simple theory. Did I?
Don't be angry with me if it doesn't work. Your data may not be lost but backup what you can on PC via USB, particularly photos, media and downloads on internal memory before you start. KIES may actually work to backup a lot on a stock un-rooted phone but be careful about what you restore; don't want to start the persistent update again if you succeed in preventing it.
Sent from my SM-N910P using Tapatalk

You definitely can stop it from nagging you to update by turning off notifications (I think you turn it off for Google services framework, and if not that, it's Google play services). This worked for me when I stayed on kitkat.
But deleting the downloaded update file is an issue without root. It lies in /cache or /cache/FOTA directory I believe, which you can't access without root. You may be able to wipe cache with stock recovery, but I'm not sure if it has that option (I'm not on stock recovery so can't check) or if it even works for what you want. Perhaps you can try deleting the cache for Google services framework or Google play services, not sure if the works either. Just some thoughts which may help you