Develop Bugs

[Q] Can I apply the 4.1 OTA update after root?

Sorry if this has been asked before and I missed it when searching, but on this sprint galaxy s3, can the OTA update be applied successfully after being rooted?
I ask because I just got one for my girlfriend and she wanted me to root it so that she can use the wifi tether program. And out of the box it was still on 4.0.4. I successfully rooted it with out any problem using the tool kit. And now it's prompting for the update every day, which is getting annoying to her. I told her to hold off till I can find a clear answer.
I know I can get a 4.1 rom and flash that now that it has cwm recovery on it if the update is a no go. Its just a manner of getting her to decide on which one she likes.

You can update but you can not use the normal OTA that she is getting the notification for if she has a custom recovery installed. The good thing is that, if you receive the notification and tell the phone to update it will fail and then stop nagging you for a while.
There are a few ways to go about updating if you want to. You can replace the stock recovery and then update. You can also manually apply the update (the update in in a ZIP in the cache folder). Move the update from cache to your sdcard and then flash it from CWM. This will only work if you are strictly stock (i.e. no modified or removed system files).

http://androidfilehost.com/?fid=9390135922294523494 flash in cwm/twrp. No wipe. This is a modified version of sprints update without the system checks

Cant say it enough. I have updated the normal ota way with root. Mine and my wifes as well

Thanks folks. Went ahead and had her run the ota and it was successful and she still has root.
Sent from my SPH-L900 using xda app-developers app

billard412 said:
http://androidfilehost.com/?fid=9390135922294523494 flash in cwm/twrp. No wipe. This is a modified version of sprints update without the system checks
Click to expand...
Click to collapse
Muchas garcias Billiard. This will be so much easier than trying to restore all the bloatware apps!

I'm on 4.3 but I just got an update saying "Android 4.3 update now available"?

I'm on 4.3 but I just got an update saying "Android 4.3 update now available"?
So I'm on stock 4.3 rooted build JSS15Q but I just got an OTA message.
Naturally this wont work since I'm rooted, but does anyone know what gives? And if there's some sort of update is there a way I can do it while keeping root?

Check About tablet in settings. If you are not on build JSS15R then it is an update.

stevemw said:
Check About tablet in settings. If you are not on build JSS15R then it is an update.
Click to expand...
Click to collapse
Yes, although I'm rooted with a custom recovery so the OTA fails.

Macmee said:
So I'm on stock 4.3 rooted build JSS15Q but I just got an OTA message.
Naturally this wont work since I'm rooted, but does anyone know what gives? And if there's some sort of update is there a way I can do it while keeping root?
Click to expand...
Click to collapse
I think it will always say there's an android 4.3 update for now since these are only updates of 4.3. I'm sure when we get kit-kat (android 4.4) it'll change to "android 4.4 update now available" and will stay like that for future updates until the next android version (5.0?).
As for keeping root, installing supersu 1.65 is supposed to prevent losing root after the OTA update but I don't believe it's guaranteed to work but it's always a very quick process to gain root again. You should check out sfhub's discussion thread for this update.

bolo808 said:
I think it will always say there's an android 4.3 update for now since these are only updates of 4.3. I'm sure when we get kit-kat (android 4.4) it'll change to "android 4.4 update now available" and will stay like that for future updates until the next android version (5.0?).
As for keeping root, installing supersu 1.65 is supposed to prevent losing root after the OTA update but I don't believe it's guaranteed to work but it's always a very quick process to gain root again. You should check out sfhub's discussion thread for this update.
Click to expand...
Click to collapse
Thanks for the info, in the end I went with this:
http://forum.xda-developers.com/showthread.php?t=2447876
I'm trying it now so hopefully it goes smoothly. The only problem I foresee is that in the future I wont be aware of when further updates are available (this method disables OTA notifications).

Macmee said:
Thanks for the info, in the end I went with this:
http://forum.xda-developers.com/showthread.php?t=2447876
I'm trying it now so hopefully it goes smoothly. The only problem I foresee is that in the future I wont be aware of when further updates are available (this method disables OTA notifications).
Click to expand...
Click to collapse
Best of luck to you :fingers-crossed: On the bright side even though it disables OTA notifications, I guarantee you any sign of a new update in the future, you'll see it here on xda and at least from there you'll know there's an OTA on the way.

My JSS15R just installed OTA. I was running TWRP and SuperSU, and had no problems. Still rooted.
Sent from my Nexus 7 using xda app-developers app

Does anybody know what the changelog for this update is? 8mb seems to make it a minor fix for something I'm guessing
Sent from my Nexus 7 using XDA Premium 4 mobile app

rmm200 said:
My JSS15R just installed OTA. I was running TWRP and SuperSU, and had no problems. Still rooted.
Click to expand...
Click to collapse
I DID have problems. I had TWRP 2.6.3.0 and SuperSU 1.65. Update bombed while in TWRP. Rebooted so fast that I couldn't read any error messages.
I was a minor problem as I just downloaded the odex version of the update from the same thread that Macmee linked above. No biggie, but would have been nice it if it happened automatically.
BTW, I WAS automatically notified of the OTA update even though I was running the Odex version of 15Q (due to problems with OTA update while rooted on the previous version -- been to this rodeo before). If I can ask, what leads you to believe that this odex/deodex version will break OTA notifications?

PJ Clifford said:
I DID have problems. I had TWRP 2.6.3.0 and SuperSU 1.65. Update bombed while in TWRP. Rebooted so fast that I couldn't read any error messages.
I was a minor problem as I just downloaded the odex version of the update from the same thread that Macmee linked above. No biggie, but would have been nice it if it happened automatically.
BTW, I WAS automatically notified of the OTA update even though I was running the Odex version of 15Q (due to problems with OTA update while rooted on the previous version -- been to this rodeo before). If I can ask, what leads you to believe that this odex/deodex version will break OTA notifications?
Click to expand...
Click to collapse
If you are running the odex version from development, OTA notification will still be there, but the OTA update will fail. At the minimum, the kernel-rootfs included in that build, while only having very minimal functionality changes, will fail the SHA1 check in the OTA update because even a 1-byte change will fail.

I started looking to see why I had no problems with the OTA. Turns out I did lose the superSU binary and TWRP after the update. I am back to stock recovery. So I have a bit of fixing to do.
Sent from my Nexus 7 using xda app-developers app

sfhub said:
If you are running the odex version from development, OTA notification will still be there, but the OTA update will fail. At the minimum, the kernel-rootfs included in that build, while only having very minimal functionality changes, will fail the SHA1 check in the OTA update because even a 1-byte change will fail.
Click to expand...
Click to collapse
Ahhh.... That explains everything! After I got the N7, the first thing I did was root it. Of course that was with the older versions of TWRP and SuperSU. I got the notice for the 15q update and, of course, it failed due to the old SuperSU (didn't know that at the time, just that it failed). I ended up downloading the rooted odex version from here and flashed that through TWRP. Worked perfectly. In the mean time, I upgraded TWRP and SuperSU to their latest versions when I discovered that the reason the original OTA failed was due to older versions of those utilities. So, having no clue that the odex version would kill the update, when I got the notification for 15r, I tried the OTA update and, of course in retrospect, THAT failed too. I immediately did the odex version again -- again with no problem. BUT, I have been scratching my head trying to figure out why it didn't work when I had the latest TWRP/SuperSU. Now I know! Next OTA, I will either just reflash to stock or just wait a day or two for the odex/deodex versions to come out.
Whew. That is a load off. Thanks for filling me in on what is going on. I don't mind problems, but I hate a mystery!

[Q] Rooted at Jellybean, no KitKat update from AT&T. How to get KitKat

My galaxy siii was rooted before kitkat was out, and I have been using it until now and have not yet update to KitKat yet because AT&T is not part of it any more.
How do I get KitKat on my phone? Do I have to unroot the phone and put it back into AT&T mode to download or what should I do?

this might help.
remember:READREADREAD
BACKUPBACKUPBACKUP
http://forum.xda-developers.com/showthread.php?t=1802160
good luck
err on the side of kindness

You will need to unroot your phone and have the stock recovery.

Thank you for both replies gentleman

audit13 said:
You will need to unroot your phone and have the stock recovery.
Click to expand...
Click to collapse
I might add to this...if you removed any stock carrier or vendor apps from 4.3 while being rooted...you'll have to restore them via a Titamium Backup or some other way or the OTA update will not install properly. (I realized that the OTA update from 4.3 to 4.4.2 will patch these apps to update them to 4.4.2 compatibility)
If you can't do that or if its unreasonable to do that based on the way the phone was modified while rooted...I suggest flashing the stock 4.3 rom via Odin and then take the OTA.

Id recommend flashing the 4.3 firmware via Odin to begin with. Its starting to seem like a lot of people who even just have to unroot are having problems with the ota. I think Odin flashing stock 4.3 will give the best chance of a successful update.

mwrobe1 said:
I might add to this...if you removed any stock carrier or vendor apps from 4.3 while being rooted...you'll have to restore them via a Titamium Backup or some other way or the OTA update will not install properly. (I realized that the OTA update from 4.3 to 4.4.2 will patch these apps to update them to 4.4.2 compatibility)
If you can't do that or if its unreasonable to do that based on the way the phone was modified while rooted...I suggest flashing the stock 4.3 rom via Odin and then take the OTA.
Click to expand...
Click to collapse
I am having this issue. I rooted on 4.3 and removed Google books and newsstand. I then uprooted and did a factory reset , so everything in download mode says "official" but the apps were still missing so I downloaded them from the play store. My question is will this let me get the OTA now or do I have to push the apps to the /system directory somehow? Also if I flash the 4.3 ODIN tar file, will it trip my warranty bit? It's at 0 right now and want to keep it that way until my warranty is up.

The firmware shouldn't trip the bit, but I can't promise that. Im sure its confirmed one way or the other in its thread though.
As for those apps, they'd have to be system apps, so just installing normally won't help. More importantly though, they would also need to be the same version that was originally built into the firmware. The apps you mentioned have seen many updates and using the current versions will not work.

I got the phone 2 weeks ago and it came with 4.3 installed on it. Would I be able to use the current version and just push them to /system/app with titanium backup? I am trying to get the OTA without tripping any warranty or security measures.

So I was rooted and had a custom recovery...

I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?

Curtai said:
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Click to expand...
Click to collapse
You got some OTA updates to go to get to PJ1 but there's a better way. You could get the PJ1 stock tar from the stock tar thread in general forum and upgrade through Odin again.
OTA is sequential patch updates. Stock tar is full updates. I'd recommend factory reset before flashing the marshmallow update to save time on initial boot optimization.
To answer your question about stopping the updates, turn off auto update feature in Settings when you get to PJ1. Follow the ROM OP to install once you get to PJ1- however you choose.
Note: Since your bootloader is now updated beyond OB7, keep in mind you cannot use Odin to flash full tars OB7 or lower. You cannot downgrade the bootloader but it's still possible to run older ROMs. I only recommend full stock tars no older than OG5.
Sent from my SM-N920P using Tapatalk

samep said:
You got some OTA updates to go to get to PJ1 but there's a better way. You could get the PJ1 stock tar from the stock tar thread in general forum and upgrade through Odin again.
OTA is sequential patch updates. Stock tar is full updates. I'd recommend factory reset before flashing the marshmallow update to save time on initial boot optimization.
To answer your question about stopping the updates, turn off auto update feature in Settings when you get to PJ1. Follow the ROM OP to install once you get to PJ1- however you choose.
Note: Since your bootloader is now updated beyond OB7, keep in mind you cannot use Odin to flash full tars OB7 or lower. You cannot downgrade the bootloader but it's still possible to run older ROMs. I only recommend full stock tars no older than OG5.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
So, now I am on PJ1 and I don't know how to put TWRP on my phone, I want to put tx_dbs_tx's UN7 hybrid on my phone and I am having issues both finding and putting TWRP on my phone... and I can't find a download or anything for it...
I've downloaded 2 different versions of twrp and used odin to put them on but I think I am doing something wrong because it isn't booting into twrp

Curtai said:
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Click to expand...
Click to collapse
and of course I was missing a step... nobody said uncheck auto reboot and it kept keeping the bootloader locked
got it done now and I managed to get the custom rom installed... or at least I think it's working

Curtai said:
and of course I was missing a step... nobody said uncheck auto reboot and it kept keeping the bootloader locked
got it done now and I managed to get the custom rom installed... or at least I think it's working
Click to expand...
Click to collapse
Oh your talking about installing twrp? Yeah you have to not let it reboot. And when is done pull battery and boot into recovery to get it to stick. Obviously you figured it out. But just saying. I think earlier versions you didn't need to do that but now you do.
Glad you got it going. How you like the Rom? Running smooth for me.

ROM is good
Well I obviously got it going and didn't read the first couple posts after the install and didn't notice the SMS issue so I had that problem and I can't find a lot of the menu options that I had with the OB7 original I've been running for about 18 months... It's pretty smooth now and I'm wondering how fast it will fill up my internal memory I like that it's almost 20 gigs free.. for a while I was running on less than 6 I need to find an efficient way to use my external SD card... Other than that the options are neat but it seems really bloated all the extra Google apps make me sick even though I never use them... I've got titanium backup and am freezing them and will probably uninstall them soon... I want a small ROM that I can customize myself or apps that are easily removed or whatever half the apps I don't want are in ROM which is a pain to remove or I just don't know how to unless I use TB
Wow that's a novel sorry but yeah that's my ramblings for the next week I guess... Now I'm gonna hit the rack...

Upgrade Help Please

I am rooted from chainfire, with twrp, on this n910pvpu1ank2 version kitkat 4.4.4
I want to update to the latest, if possible, and retain root. if that's not possible, then I think just update it. all help appreciated.
what steps do I need to take to accomplish this? do I need to odin back to stock and then update? I haven't been able to find the kitkat stock firmware for n910pvpu1ank2.
do you have links to trusted files for the update? I found the most recent update on sammobile here and downloading now. is this the correct file and can I odin this one directly or do I need to go through all the updates first?
https://www.sammobile.com/firmwares/galaxy-note4/SM-N910P/SPR/download/N910PVPS4DQG1/184468/
thank you.

toenail_flicker said:
I am rooted from chainfire, with twrp, on this n910pvpu1ank2 version kitkat 4.4.4
I want to update to the latest, if possible, and retain root. if that's not possible, then I think just update it. all help appreciated.
what steps do I need to take to accomplish this? do I need to odin back to stock and then update? I haven't been able to find the kitkat stock firmware for n910pvpu1ank2.
do you have links to trusted files for the update? I found the most recent update on sammobile here and downloading now. is this the correct file and can I odin this one directly or do I need to go through all the updates first?
https://www.sammobile.com/firmwares/galaxy-note4/SM-N910P/SPR/download/N910PVPS4DQG1/184468/
thank you.
Click to expand...
Click to collapse
You lose root updating.
Fyi: recent updates do not have developer support but maybe latest security update is your goal?
If you're not interested in rooting again and flashing custom ROM and prefer latest stock ROM, I'd recommend:
decrypt any data encrypted
backup any keepsakes to ext SD Card
remove fingerprints
make a TWRP backup (backups should be on external SD Card)
factory reset
wipe internal memory
Power down and remove battery prior to download mode
Flash latest stock tar with Odin from this thread (it may download faster- QB3 would be OK unless you want to download latest, if available. Updates usually aren't available for some time). Use Odin defaults and go through setup wizard.
https://forum.xda-developers.com/showthread.php?p=63868221
Quickest way to latest update is to install Smart Switch (unless you found latest to download for Odin).
https://www.sammobile.com/samsung-smart-switch/
Note: If you do decide to run a custom ROM, security updates are not up to date but it's recommended to install the update recommended in OP for those custom ROMs. You may lose some compatibility by not flashing the recommended update.
Stock tar updates for Odin are full updates so they're not required to be flashed in sequential order. Same for Smart Switch updates. Smart Switch likely only works for non rooted phones which is why I recommended to start with Odin stock tar.
OTA updates patch the previous update sequentially. So OTA update would only be ideal to update after getting to latest with Smart Switch. Odin updates are slower to become available as I recall.
Make your battery is charged to 80% or more. I wouldn't recommend a battery that's over a year old. Start with a fresher battery and replace batteries that have over 500 recharge cycles on them. This could save you trouble in the long run.
Also, keep your phone cool during these initial boots after flash. Forced air from a small fan or air purifier should do fine.
Sent from my SM-N920P using Tapatalk

"Fyi: recent updates do not have developer support but maybe latest security update is your goal?"
this mostly. though I will read through your response carefully. I like kitkat and everything is the way I like it, but I feel as if I should also update the firmware. rather torn honestly. all thoughts and advice on the trade-offs, etc. and I don't play with roms.
thank you for your help. was hoping you'd pop by. you were so much help before.

wow. so much valuable information in your reply. this is amazing. thank you.

toenail_flicker said:
"Fyi: recent updates do not have developer support but maybe latest security update is your goal?"
this mostly. though I will read through your response carefully. I like kitkat and everything is the way I like it, but I feel as if I should also update the firmware. rather torn honestly. all thoughts and advice on the trade-offs, etc. and I don't play with roms.
thank you for your help. was hoping you'd pop by. you were so much help before.
Click to expand...
Click to collapse
You do recall that once you upgrade past OB7 that you lose the ability to return to KitKat via Odin stock tar?
The TWRP backup I recommended is still useful but likely you'd need to downgrade bootloader firmware to 5.1 (OG5 to OK1 is recommended once you've upgraded beyond OB7), factory reset, wipe internal, restore backup and flash Beastmode 1.0 kernel prior to booting.
I think you also need to flash SuperSU zip after kernel to get a boot but I'm not sure on that.
Have you already been through this with lollipop 5.1 and went back to KitKat? If so, you know the drill, just make sure you have the right bootloader.
If you're looking for developer support on stock like ROM, check out dtux or UN7 ROMs with aroma flash modset mods. There's also a few modified stock ROMs that are newer.
I discovered this morning that older updates for Note 4 are vulnerable to BlueBorne exploit through Bluetooth. I keep mine off mostly and disable the options in improve location and nearby devices so it shouldn't be a issue for me. There's a BlueBorne vulnerability scanner in Google Play to check later updates if you like. Search for it in Play.
Sent from my SM-N920P using Tapatalk