Develop Bugs

New Update Message

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

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

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

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

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

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

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

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

[Solved] official JB 4.3 for Maguro ?

Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35

niaoRen said:
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
Click to expand...
Click to collapse
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.

lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
True, I've experienced this before, I would recommend go with Official Factory image if not sure your device is running completely stock before apply OTA...

First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.

lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
fux0r99 said:
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
Click to expand...
Click to collapse
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.

Zepius said:
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Click to expand...
Click to collapse
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?

niaoRen said:
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
Click to expand...
Click to collapse
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).

cupfulloflol said:
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
Click to expand...
Click to collapse
alright. Will try to revert to stock kernel and try the official OTA. Will revert back here after i've attempted it. Thanks a bunch you all

I just found a easier way to do things.
Just flash this 4.3 stock ROM over my current 4.2 rom. Works like a charm and hassle free.

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!

Samsung Software update for L710t (spark)

I'm on stock rooted 4.4.2 on my Sprint L710t (spark version). I got a notification for an OTA update yesterday coming in at 70.5MB and states that they're security updates and bug fixes. Did anyone else get this and do they know what these changes are? Will I lose root if I update?
I'm currently on OA3 baseband. Thanks.

I have the same baseband but have not received that message. Did you except the update or at least let it download the update then copy it from your system files to your internal or external sdcard? If you download it and save it could you upload it so I can get it from you and look through the update?

PleaseDontBrick said:
I'm on stock rooted 4.4.2 on my Sprint L710t (spark version). I got a notification for an OTA update yesterday coming in at 70.5MB and states that they're security updates and bug fixes. Did anyone else get this and do they know what these changes are? Will I lose root if I update?
I'm currently on OA3 baseband. Thanks.
Click to expand...
Click to collapse
Idk if you will loose root access or if it will even allow you update since you are rooted cause you have modified the system file a little! I got the update this morning finally but I couldn't take it cause I have TWRP recovery and not stock recovery and I have deleted quiet a system apps. But you pull the update file from your cahce folder and open the zip file up and look at what all gest updated! The bootloader, kernel, modem and a bunch of system apps and CSC codes are all updated so far that I can see.

I haven't been able to update either since I'm using TWRP. Do you think it's worth going back to stock recovery in order to update? How would I even do that on OA3? I've seen a lot of tutorials on getting stock back on NF4 baseband, but nothing on OA3.

PleaseDontBrick said:
I haven't been able to update either since I'm using TWRP. Do you think it's worth going back to stock recovery in order to update? How would I even do that on OA3? I've seen a lot of tutorials on getting stock back on NF4 baseband, but nothing on OA3.
Click to expand...
Click to collapse
I'm sure it would help at least with our service cause they did update our modem! I'm not sure either about what is the best way to try to update. I'm running a custom kernel and TWRP so I would have to flash the NF4 package and see see it would give me ota-update for OA3 then allow me to update to the new L710TVPU0AOF2. Thats the new baseband. I'm not really sure I haven't ever had the problem of worrying about stock ota-updates. I've always normally had devices that developers post the update firmware packages online for us! I've asked Chainfire if he thinks we could flash the update using Flashfire but he hasn't replied yet. I don't think we will be able to but it's worth a shot to ask.

I just received the same update. Is there a way to disable it

How can I upload it?? Where is the update downloaded into??

Root & OTA Update??

I have Lollipop, Root & Xposed.
The last days i have seen that Samsung starts to release new versions of the Note 3 Neo Lollipop, as informed from SamMobile, and normally it'll be available and as OTA Updates.
But for us that we are rooted is there any way to install this OTA Update? (e.g. via Chainfire's FlashFire)

Hi
Just asking....
Do u got stock ota update file
Or got any link to ota rom?
Much appreciate
Ty

biskutcotek said:
Hi
Just asking....
Do u got stock ota update file
Or got any link to ota rom?
Much appreciate
Ty
Click to expand...
Click to collapse
Ota update file or ota rom no!
I have only the stock rom file for use with Odin via SamMobile