Develop Bugs

Updated to 4.3 months ago using international version, how to update to 4.3 knox-free

I updated to 4.3 using the international method months ago because I was tired of waiting for the new tmobile update so I could put apps on my sd card. Now that tmobile officially updated everything, I want to update it so I can use wifi calling. I might follow this guide http://forum.xda-developers.com/showthread.php?t=2546024 so I wont break my warranty in an irreversible way. I just dont know if it will work because the guide states I need to be on 4.2.2. Currently my phone is not working correctly. It will boot but my home screen is blank and all screwed up and then it just restarts a few seconds later. I don't know what I should do. I want to keep my root. Should I do a full restore? I might try to load an old backup from the recovery for now just so its usable. Any help will definitely be appreciated. Thank you!!!!

coolpepp said:
I updated to 4.3 using the international method months ago because I was tired of waiting for the new tmobile update so I could put apps on my sd card. Now that tmobile officially updated everything, I want to update it so I can use wifi calling. I might follow this guide http://forum.xda-developers.com/showthread.php?t=2546024 so I wont break my warranty in an irreversible way. I just dont know if it will work because the guide states I need to be on 4.2.2. Currently my phone is not working correctly. It will boot but my home screen is blank and all screwed up and then it just restarts a few seconds later. I don't know what I should do. I want to keep my root. Should I do a full restore? I might try to load an old backup from the recovery for now just so its usable. Any help will definitely be appreciated. Thank you!!!!
Click to expand...
Click to collapse
IMPORTANT
Follow these steps if you want a fully working 4.3 ROM on your Galaxy S4 (M919) with all the benefits of the 4.3 update, WITHOUT KNOX. These steps should provide you with a 100% KNOX free setup so you can continue to keep root and flash new ROMs to your heart's content! THIS GUIDE WILL ONLY WORK FOR YOU IF YOU HAVE NOT ALREADY UPDATED TO 4.3 USING THE OTA UPDATE AND ARE STILL USING THE 4.2 BOOTLOADER. IF YOU HAVE THE NEW BOOTLOADER THAT READS "KNOX WARRANTY" THEN THIS WILL NOT WORK FOR YOU.​
STANDARD DISCLAIMER APPLIES! YOU KNOW THIS CAN BREAK YOUR PHONE, THERE ARE PLENTY OF PEOPLE WHO HAVE HAD NO ISSUES, THERE ARE SOME WHO HAVE. THIS IS A RISK YOU, AND YOU ALONE TAKE, I HAVE NOT HELD A GUN TO YOUR HEAD AND TOLD YOU TO FOLLOW THESE STEPS.
---------- Post added at 01:52 AM ---------- Previous post was at 01:49 AM ----------
An yes I would recommend you do a full restore first an see if that helps solve whatever issues you are having now.

Lost and new to rooting

Ok, I hope that this post doesn't just instantly get bashed or ignored for its nature, but I feel like I'd waste so much more time just fumbling through the forum trying to find something relevant if I had to do this on my own. So, hopefully someone can point me in the right direction. Basically, while overseas my Sprint s3 had to get rooted to work, but now that I'm back in the states I'd like to properly root my phone for functions like wifi tethering.
At the present this is what is on my phone.
-clockworkmod recovery v6.0.1.2
-android version 4.1.1
My main questions would be the following?
1.Can I have the latest version of android and still have my phone rooted, and can this be done with what presently on my phone?
2.How do I remove the present clockworkmod recovery (or should I), for something better?
3.What is generally considered the best set up for the sprint s3 at the moment?
Thanks in advance.

Since you are rooted, go the this thread
http://forum.xda-developers.com/showthread.php?t=2541900. It has the latest version. You really should use Philz recovery, I'll try to find the link.
---------- Post added at 08:59 PM ---------- Previous post was at 08:53 PM ----------
Here's the thread for Philz recovery.
http://forum.xda-developers.com/showthread.php?t=2446393

-_- I just downloaded a app called root checker, because my assumption was that just because I had Clockworkmod my phone must be rooted, but it turns out that the results were negative, plus I forgot to mention that I've done a factory reset when I first got back if that effects anything. So, my phone isn't actually rooted, sorry about that.

No worries, If you can boot into recovery then just flash a rooted rom. If not, I suggest you root it before you take any OTAs, especially the OTA for 4.3

If you want the latest set up, I suggest not taking the OTA at all and flashing on of the latest stock 4.3 roms that are de-knoxed. I have I've for Boost and VM and @CNexus has one for Sprint.
Sent from my SPH-L710 using Tapatalk

Can't update after root

Hi, i just did root the device and when i went to update the software it says that operating system on my device has been modified are you guys experiencing the same thing?

wisnia99 said:
Hi, i just did root the device and when i went to update the software it says that operating system on my device has been modified are you guys experiencing the same thing?
Click to expand...
Click to collapse
That is part of the KNOX system. Rooting trips it. So Now your phone has been permanently marked in its hardware as tampered. Any system that checks it integrity will now fail it. You will never be able to get OTA updates now. Also if your employer uses KNOX on their servers you will not be able to use this phone to connect to their servers for email now. That is the purpose of KNOX to assure network providers that the phone is stock and not tampered with.
Even if you try to unroot it the KNOX flag will still be tripped. This was an issue on the NOTE 3 as well. Once the KNOX flag is tripped it cannot be reset as it is in the hardware.

Thanks for the explanation i really dont care for tripping Knox as long as i can update trough Keis or wait for new roms

You can use the Wanam Xposed module to fake your system status and still get System Updates. Thats what I did.

TheCrzy1 said:
You can use the Wanam Xposed module to fake your system status and still get System Updates. Thats what I did.
Click to expand...
Click to collapse
So if they do any firmware or radio updates wouldn't it break the root?

I ran into the problem on note 3 if u Odin back to stock u can get updates depending on devs if they have a new root method or not I generally never updated till I found I method to reroot

wisnia99 said:
Thanks for the explanation i really dont care for tripping Knox as long as i can update trough Keis or wait for new roms
Click to expand...
Click to collapse
You can still use Odin to flash roms if needed, or the wanam trick....

I installed wanam and set my status to official but the OTA system update still fails with the message my phone has been modified. I have galaxy tools installed with native tether enabled if that matters. What should i do to enable the update?
---------- Post added at 01:17 PM ---------- Previous post was at 12:30 PM ----------
The OTA Still errored with a "device has been modified" or some such. I ran triangle away and saw my binary status was 'custom'. I checked the triangle away 'auto reset at boot and that fixed my binary status. Now i well retry the update and rpt back.
---------- Post added at 02:05 PM ---------- Previous post was at 01:17 PM ----------
With my sprint note 4 wanam doesnt help nor triangle away although binary, flash and counter all look good in T Away

cknicker said:
I installed wanam and set my status to official but the OTA system update still fails with the message my phone has been modified. I have galaxy tools installed with native tether enabled if that matters. What should i do to enable the update?
---------- Post added at 01:17 PM ---------- Previous post was at 12:30 PM ----------
The OTA Still errored with a "device has been modified" or some such. I ran triangle away and saw my binary status was 'custom'. I checked the triangle away 'auto reset at boot and that fixed my binary status. Now i well retry the update and rpt back.
---------- Post added at 02:05 PM ---------- Previous post was at 01:17 PM ----------
With my sprint note 4 wanam doesnt help nor triangle away although binary, flash and counter all look good in T Away
Click to expand...
Click to collapse
Well, if you are rooted and have custom recovery you can't get updates, "ota's" you will have to wait for a dev to come up with a flashable update. Being on 4.4.4 no reason to worry... You are up to date.
Oh, btw, forget about triangle away... It no longer serves any purpose for us...

On stock unrooted you still get OTA. Even with Knox tripped. If you have a custom recovery and root dont take the ota if you are promoted. It will brick your phone and you will have to Odin back to stock anyway.
---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------
Prompted not promoted lol

Real_JESRadio said:
On stock unrooted you still get OTA. Even with Knox tripped. If you have a custom recovery and root dont take the ota if you are promoted. It will brick your phone and you will have to Odin back to stock anyway.
---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------
Prompted not promoted lol
Click to expand...
Click to collapse
In 'about device it now says my phone is up to date. My version numbers are below. Do they show my phone was really updated?
Baseband version
N910PVPU1ANIE
Kernel version
3.10.0-2774708
[email protected] #1
Wed Sep 17 19:19:02 KST 2014
Build number
KTU84P.N910PVPU1ANIE
SE for Android status
Enforcing
SEPF_SM-N910P_4.4.4_A019
Wed Sep 17 19:19:33 2014

Real_JESRadio said:
On stock unrooted you still get OTA. Even with Knox tripped. If you have a custom recovery and root dont take the ota if you are promoted. It will brick your phone and you will have to Odin back to stock anyway.
---------- Post added at 08:15 PM ---------- Previous post was at 08:14 PM ----------
Prompted not promoted lol
Click to expand...
Click to collapse
Interesting. I came from the S3. Trying to take an ota wouldn't brick the phone but it would stop any future notifications of updates. We were fortunate to have a lot great devs there.
Btw, if you can still Odin the phone is not bricked. Bricked is dead...

jhill110 said:
Interesting. I came from the S3. Trying to take an ota wouldn't brick the phone but it would stop any future notifications of updates. We were fortunate to have a lot great devs there.
Btw, if you can still Odin the phone is not bricked. Bricked is dead...
Click to expand...
Click to collapse
Came from the S3 myself as well. Definitely a lot of active development until after SlimKat 7.0 and then that fell apart just in time for getting the Note 4. The numbers 4 and 3 i am starting to despise.
Slimteam, when i was keeping up with them, stated something about Android 5.0.
Maybe well get a surprise and see SlimPop for the Note 4. Slimpop isnt as euphonious as it looks to the eye...
On Topic: i wasnt able to update after rooting either as the phone is currently already UTD.

jhill110 said:
Interesting. I came from the S3. Trying to take an ota wouldn't brick the phone but it would stop any future notifications of updates. We were fortunate to have a lot great devs there.
Btw, if you can still Odin the phone is not bricked. Bricked is dead...
Click to expand...
Click to collapse
I mean soft bricked. And I should have elaborated, if you have a custom recovery you will soft brick taking an OTA update. Yes, some ROMs eliminate the OTA capability but some stock based ROMs will still get a notification.
---------- Post added at 12:47 AM ---------- Previous post was at 12:45 AM ----------
cknicker said:
In 'about device it now says my phone is up to date. My version numbers are below. Do they show my phone was really updated?
Baseband version
N910PVPU1ANIE
Kernel version
3.10.0-2774708
[email protected] #1
Wed Sep 17 19:19:02 KST 2014
Build number
KTU84P.N910PVPU1ANIE
SE for Android status
Enforcing
SEPF_SM-N910P_4.4.4_A019
Wed Sep 17 19:19:33 2014
Click to expand...
Click to collapse
That is the latest update. A new one is coming soon. But you should be on the latest with that build.

Deleted.

So then i am rooted with TWRP recovery and still can load OTA updates? What happened to Knox?

Simple. Go to the download screen and see what the status says. Google it

Does anyone know what is in this latest update do I need it if so where can I get it in a flashable format that works with a rooted phone

red triangle while trying to update OTA lollipop while on TWRP...

Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376

jfreshh330 said:
Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376
Click to expand...
Click to collapse
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triangle deal.
So try and find one thats a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the T-Mobile files. As mentioned though, just make sure the stock recovery is from Android 4.4.X or 5.X.X and you will be fine.

flexfulton said:
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triange deal.
So try and find one that a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the AT&T files. As mentioned though, just make sure the stock recovery in from Android 4.4.X or 5.X.X and you will be fine.
Click to expand...
Click to collapse
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.

jfreshh330 said:
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.
Click to expand...
Click to collapse
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!

flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
Click to expand...
Click to collapse
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?

flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!
Click to expand...
Click to collapse
Awesome thanks so much!

jfreshh330 said:
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?
Click to expand...
Click to collapse
Sideload the latest recovery as found in the thread I linked to above. Reboot and the OTA should take no problems. It was downloading and everything fine for you before but was unable to flash because of an outdated recovery you installed.
So my recommened method to update OTA, is to follow the first route you were taking but with the newest recovery.img file in place of what you used in step 1.
If you already have the OTA downloaded on your phone, you shouldn't have to download it again either. It should see that it's already downloaded ready to be installed.
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
jfreshh330 said:
Awesome thanks so much!
Click to expand...
Click to collapse
No problem. Let me know how it turns out for you.

If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).

redpoint73 said:
If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).
Click to expand...
Click to collapse
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.

flexfulton said:
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Click to expand...
Click to collapse
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
flexfulton said:
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.
Click to expand...
Click to collapse
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.

redpoint73 said:
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.
Click to expand...
Click to collapse
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.

flexfulton said:
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Click to expand...
Click to collapse
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
flexfulton said:
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.
Click to expand...
Click to collapse
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.

redpoint73 said:
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.
Click to expand...
Click to collapse
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
I was trying to help out as I had the same issue when I went to update. I installed a recovery that was too old, determined that I needed to flash a recovery from either 4.4.X or lollipop and my OTA update was fine after that. Point being, I could go ahead and flash a newer recovery to get the OTA to download.
Anyway I applogize if I was in error in my help. No one else was helping and based on my own experiences it sounded like the same issue.

flexfulton said:
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
Click to expand...
Click to collapse
OTAs will normally only allow you to install from the immediate previous version (you cannot skip a version). Sometimes they are complete packages; but often they are not. Sometimes the OTA just contains what has been changed; basically a "patch". And for that reason, the updates need to be installed sequentially. In fact, I've seen folks brick due to unwittingly installing partial firmware packages from OTAs (with s-off, which bypasses such safety checks).
flexfulton said:
Anyway I applogize if I was in error in my help.
Click to expand...
Click to collapse
There's no need to apologize. As you are well aware, this is a self-supporting community that flourishes due to the contributions of its members. Your answers may not have been 100% correct. But it was well intended; and you answered to the best of your knowledge. At least you learned something and can pass it along now. I'm just a member who passes along what I've learned here also (don't have any specialized developer knowledge or anything); and I'm certainly not right all the time.

So the recovery 3.32.5312 will not work? And i apologize i am on 4.4.4 not 4.4.2

has anyone found latest OTA AT&T I317-UCUCNJ2 flashable by ODIN?

Triangle Away never worked for me to unroot to stock so I am unable to install ATT OTA updates, including the latest Aug 2015 one. Has anyone in the community been able to grab the latest stock OTA file I317UCUCNJ2 and can share for manual ODIN flash? User Zen Kernel did an awesome job with the last one from Nov 2014, but i can't find any updates to his post for the Aug 2015 Thanks!

I'd hold off until the NJ3 update...(not confirmed but likely dropping soon).
The NJ2 update did not fix the stagefright stack overflow exploit...
So it's likely sammy will push a fix soon...g

vklen said:
Triangle Away never worked for me to unroot to stock so I am unable to install ATT OTA updates, including the latest Aug 2015 one. Has anyone in the community been able to grab the latest stock OTA file I317UCUCNJ2 and can share for manual ODIN flash? User Zen Kernel did an awesome job with the last one from Nov 2014, but i can't find any updates to his post for the Aug 2015 Thanks!
Click to expand...
Click to collapse
Been looking for this answer for hours lol Thank you. I was trying to reflash CWM on my phone after last year AT&T took it out.

Prolly not the answer you are looking for but in Zen's same thread a user posted how he did the update in a round about way. Unrooting/upgrade/re-rooting. I can confirm this works without a hitch. If you run into trouble "checking for updates" after the un-rooting, you'll have to set the time to manual and a day ahead cause if you don't catch the update the first go around there is a 24hr block till you can check again.

I317_ATT_I317UCALJ2_I317ATTALJ2_Original
uploading as we speak
---------- Post added at 11:52 AM ---------- Previous post was at 11:52 AM ----------
I317_ATT_I317UCALJ2_I317ATTALJ2_Original
uploading as we speak

THIS THE FILE COPY THIS ADDRESS AND PASTE IT ON UR BROWSER IT SHOULD DOWNLOAD DONT FORGET TO SMASH THAT THANKS BUTTON BUTTY
file:///C:/Users/admin/AppData/Roaming/Microsoft/Windows/Start%20Menu/Programs/note2%20stock+root/I317_ATT_I317UCALJ2_I317ATTALJ2_Original.zip

vtech7634 said:
THIS THE FILE COPY THIS ADDRESS AND PASTE IT ON UR BROWSER IT SHOULD DOWNLOAD DONT FORGET TO SMASH THAT THANKS BUTTON BUTTY
file:///C:/Users/admin/AppData/Roaming/Microsoft/Windows/Start%20Menu/Programs/note2%20stock+root/I317_ATT_I317UCALJ2_I317ATTALJ2_Original.zip
Click to expand...
Click to collapse
Your local hard-drive files aren't accessible to us. That isn't the file the original poster is asking for anyway. That is one of, if not the oldest, releases. CALJ2. The original poster asked for UCUCNJ2.