Develop Bugs

Is firmware update worth it?

To the Community:
I just today received a note from T-Mobile Update Service that there's an update available. Of course being rooted it's not available to me OTA.
I plugged in my phone to Kies and the update that's available is from
Current firmware version: PDA:LK8 / PHONE:LK8 / CSC:LK8 (TMB)
to
Latest firmware version: PDA:LL4 / PHONE:LL4 / CSC:LL4 (TMB)
When I clicked on UPGRADE FIRMWARE I got a caution that read, "Devices that have been rooted or modified with customized software may experience a failure during the upgrade process."
So I have a couple of questions:
1. is this upgrade worth it?
2. should I unroot / Triangle Away / etc. and go through that rigamarole or should I risk proceeding with Kies? (As long as I don't brick my phone I have no problem recovering / restoring / etc.)
4. if I don't do anything, how can I get rid of the reminder-to-update icon in the notification bar?
Thanks in advance.

actually its not worth upgrading so consider carefully before you want to do so

Latest OTA update patches the exynous exploit. I would say yes it is worth updating.
Sent from my SGH-T889 using xda app-developers app

ciphercodes said:
Latest OTA update patches the exynous exploit. I would say yes it is worth updating.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Yeah I think I agree. I thought about the upgrade, then let it go ahead. That being said, have you seen what Verizon have been up to? Really screwing with rooted users IMHO. That's why I am not too quick to update, just in case it can be a negative upgrade.

If you are already rooted and are using SuperSu, then there is a setting called "survivor mode" which will attempt to retain root even after an update. I checked this box, updated and still have root. Yet another option is ti use an app from the android market called OTA Rootkeeper which essentially does the same thing.

I don't think the update is worth it. ExynosAbuse also fixes the security flaw. So I have root and a secure phone. Also I don't care much for multi window. I will however updated whenever LTE is enabled. Well, I might wait till LTE is rolled into Cyanogen first then upgrade to that.

Supermighty said:
I don't think the update is worth it. ExynosAbuse also fixes the security flaw. So I have root and a secure phone. Also I don't care much for multi window. I will however updated whenever LTE is enabled. Well, I might wait till LTE is rolled into Cyanogen first then upgrade to that.
Click to expand...
Click to collapse
But doesn't the ExynosAbuse mess up the camera when it is disabled in the app? And if you don't disable it then you only have root without the protection. I was in this situation and just did the update with OTA rootkeeper. I maintained root and my device status is still normal. See this thread http://forum.xda-developers.com/showthread.php?t=2111188

GMAN1722 said:
But doesn't the ExynosAbuse mess up the camera when it is disabled in the app? And if you don't disable it then you only have root without the protection. I was in this situation and just did the update with OTA rootkeeper. I maintained root and my device status is still normal. See this thread http://forum.xda-developers.com/showthread.php?t=2111188
Click to expand...
Click to collapse
messing up the camera as far as I know is only on the Galaxy SIII. the note II's camera has no problems with the fix- there's no reason at all not to use it.

theoilman said:
messing up the camera as far as I know is only on the Galaxy SIII. the note II's camera has no problems with the fix- there's no reason at all not to use it.
Click to expand...
Click to collapse
From reading this thread http://forum.xda-developers.com/showthread.php?t=2052656 there were a few reports of the camera not working correctly when the exploit was disabled

Supermighty said:
I don't think the update is worth it. ExynosAbuse also fixes the security flaw.
Click to expand...
Click to collapse
Chainfire did a really good job providing a temporary solution to take care of this exploit via exynos abuse application but this vulnerability was within the kernel and this had to be fixed via kernel update. The new update patches this vulnerability at kernel level making sure no other functions are affected by it.
Sent from my SGH-T889 using xda app-developers app

[Qwaswas windingwasUOTE=whatllitbenext;37061997]To the Community:
I just today received a note from T-Mobile Update Service that there's an update available. Of course being rooted it's not available to me OTA.
I plugged in my phone to Kies and the update that's available is from
Current firmware version: PDA:LK8 / PHONE:LK8 / CSC:LK8 (TMB)
to
Latest firmware version: PDA:LL4 / PHONE:LL4 / CSC:LL4 (TMB)
When I clicked on UPGRADE FIRMWARE I got a caution that read, "Devices that have been rooted or modified with customized software may experience a failure during the upgrade process."
So I have a couple of questions:
1. is this upgrade worth it?
2. should I unroot / Triangle Away / etc. and go through that rigamarole or should I risk proceeding with Kies? (As long as I don't brick my phone I have no problem recovering / restoring / etc.)
4. if I don't do anything, how can I get rid of the reminder-to-update icon in the notification bar?
Thanks in advance.[/QUOTE]
I was wondering the same thing. I am stock/rooted. I wanted to keep root but be up to date. I found over on the q&a forum to use Voodoo OTA Root Keeper. And do the update OTA instead of using KIES. This worked like charm and made me extremely happy. Quick and easy.

ExynosAbuse messed up my camera at any rate. YMMV. The update worked fine for me. OTA Rootkeeper and restored root just fine after.
Hastily spouted for your befuddlement

[PSA] New Firmware update for Canadian Galaxy S4 SGH-M919V

There's a new OTA update available for the Galaxy S4 SGH-M919V variant from Wind Mobile, Eastlink, Videotron in Canada.
This is the update that finally brings the much awaited Apps2SD feature to our phones. It also includes the following enhancements:
- Some new icons in the settings
- Additional 'Smart Pause' button in quick settings
- Stability improvements
- Upgrades the camera firmware.
- Storage shown as 16GB now, but 6.38 GB is occupied by System memory under 'Misc'.
Firmware version: M919VVLUAMG1

So its official. TMo is the last carrier on Earth to get this update.

stevessvt said:
So its official. TMo is the last carrier on Earth to get this update.
Click to expand...
Click to collapse
Unfortunately, it appears to be the case as of now. I really can't imagine it being that far off now. Since, these versions are identical!

Will the update kill ROOT?

macaumen said:
Will the update kill ROOT?
Click to expand...
Click to collapse
The OTA will fail to update if you're rooted.
I had to Odin back to stock and then apply the OTA update.
So yes, the update will break root.
I haven't tried to root it since, so I can't report any progress there.
Sent from my SGH-M919V using Tapatalk 4 Beta

dj_aj said:
The OTA will fail to update if you're rooted.
I had to Odin back to stock and then apply the OTA update.
So yes, the update will break root.
I haven't tried to root it since, so I can't report any progress there.
Sent from my SGH-M919V using Tapatalk 4 Beta
Click to expand...
Click to collapse
It failed because it said your device is modified and prevent you from updating or it failed in the middle of updating?

tmobile needs to speed up this apps to sd update.....

I love how they are trying to hide the space the system uses under miscellaneous. This might trick people into not complaining about having more available disk space. I've heard good things about this update... Just want it already.
Still lovin' Tmo more than Sprint!!! 15-26mb beats 100k all day long. And I enjoy being able turn the camera sound off without rooting.
Sent from my SGH-M919 using xda premium

man, i got excited for a minute when i read new firmware update.

T-Mobile is usually quick to send out updates, I wonder why it's taking them long to release this one? The S3 got the JB update pretty quick if I'm not mistaken.

Burner2K0 said:
T-Mobile is usually quick to send out updates, I wonder why it's taking them long to release this one? The S3 got the JB update pretty quick if I'm not mistaken.
Click to expand...
Click to collapse
you can blame me for the update not being released and it wont be released for months, according to my sources. I talked to t mobile about all the bugs they have, so they said fine, we will do everything never to give bugs again, hence a long update period...It was probably my phone calls that lead to this wait

Luthien1 said:
you can blame me for the update not being released and it wont be released for months, according to my sources. I talked to t mobile about all the bugs they have, so they said fine, we will do everything never to give bugs again, hence a long update period...It was probably my phone calls that lead to this wait
Click to expand...
Click to collapse
You son of a ..... ;__; :crying:

I realize it's always an agonizing wait to get your hands on the newest firmware. However, there's a bright side to it. You all are still able to root and tinker with your devices.
I haven't been able to root the newest firmware using motochopper and am hesitant to try CF-Autoroot because in the case it does trip the flash counter and I loose root, I won't be able to reset it.
So, by the time tmobile sends out the update, there hopefully is a way to root.

dj_aj said:
I realize it's always an agonizing wait to get your hands on the newest firmware. However, there's a bright side to it. You all are still able to root and tinker with your devices.
I haven't been able to root the newest firmware using motochopper and am hesitant to try CF-Autoroot because in the case it does trip the flash counter and I loose root, I won't be able to reset it.
So, by the time tmobile sends out the update, there hopefully is a way to root.
Click to expand...
Click to collapse
Next time if your already rooted you can grab the app voodoo OTA Rootkeeper, which should be able to protect and reapply root after an update.

stevessvt said:
Next time if your already rooted you can grab the app voodoo OTA Rootkeeper, which should be able to protect and reapply root after an update.
Click to expand...
Click to collapse
Thanks for that tip. However, I doubt it would've worked because since I was rooted, the update failed to complete installing around 25%. So, I had to odin back to stock and then apply the OTA. Probably something to do with a locked bootloader.

Under About Phone/Status, where you 'Official'?

stevessvt said:
Under About Phone/Status, where you 'Official'?
Click to expand...
Click to collapse
Yeah, the phone status was 'Official'. You'd have to be in order to get OTA updates/notifications.
Initially upon rooting, the status changed to 'Custom', But I followed the guide below to revert it to 'Official' while retaining root.
http://forum.xda-developers.com/showthread.php?t=2296014

Nothing against Canada but can't believe they got an update before the U.S. model.
Sent from my SGH-M919 using Tapatalk 2

Can someone make a flashable rom with these update fir T-Mobile?
Sent from my SGH-M919 using Tapatalk 4 Beta

epsix said:
Can someone make a flashable rom with these update fir T-Mobile?
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
you already can get this update, but you will loose wifi calling and other tmobile features

Nexus 7 4.3 JWR66N OTA update error

My NEXUS 7 (2013) is running on Android 4.3 with the build version JWR66N
The Problem is that i get an OTA update notification for Android 4,3 System Update which is of appx (56 MB).
When i try to install it the Tab reboots and the update fails and it restarts again with the same build version ie. JWR66N.
Again after 2-3 days i get the same notification for that 4.3 System update and again it fails. PLEASE HELP !!!
How will i update to android 4.4 ???
I dont want to sideload or root.... Please suggest a normal fix !!!

Have you done any modifications to your n7 usually that borks any ota update

church said:
Have you done any modifications to your n7 usually that borks any ota update
Click to expand...
Click to collapse
No... I have not done any change.... After booting for the very first time i got an update which worked fine.... Then this OTA update message keeps coming but it never gets installed as it gives an error

red_ferrari007 said:
My NEXUS 7 (2013) is running on Android 4.3 with the build version JWR66N
The Problem is that i get an OTA update notification for Android 4,3 System Update which is of appx (56 MB).
When i try to install it the Tab reboots and the update fails and it restarts again with the same build version ie. JWR66N.
Again after 2-3 days i get the same notification for that 4.3 System update and again it fails. PLEASE HELP !!!
How will i update to android 4.4 ???
I dont want to sideload or root.... Please suggest a normal fix !!!
Click to expand...
Click to collapse
You likely have the problem that some system files got corrupted because of bad EMMC.
When the update fails and you have the fallen android, press/hold Power, then press/release VolUp, then release Power.
This will show you the error and can confirm or refute this diagnosis.
If you want to get past it in the more efficient manner, you'll probably need to unlock the bootloader, then flash one of the factory images.

I will see that when the OTA notification comes again..... But how can I solve the problem.... is anyone else facing it ?
Will I get an Android 4.4 update ?
Sent from my Nexus 7 using xda app-developers app

red_ferrari007 said:
I will see that when the OTA notification comes again..... But how can I solve the problem.... is anyone else facing it ?
Will I get an Android 4.4 update ?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
As I mentioned you'll probably need to flash a factory image to get around it, or you'll have to identify each file that is corrupted and replace it.
If you don't resolve the problem you won't get the 4.4 update automatically, but you can manually install the 4.4 factory image.

sfhub said:
As I mentioned you'll probably need to flash a factory image to get around it, or you'll have to identify each file that is corrupted and replace it.
If you don't resolve the problem you won't get the 4.4 update automatically, but you can manually install the 4.4 factory image.
Click to expand...
Click to collapse
see i found this link which apparently is talking about the same problem and a fix
http://forum.xda-developers.com/showthread.php?t=2380258
but i dont know anything about rooting and flashing.... Thats why i am afraid to do anything

red_ferrari007 said:
see i found this link which apparently is talking about the same problem and a fix
http://forum.xda-developers.com/showthread.php?t=2380258
but i dont know anything about rooting and flashing.... Thats why i am afraid to do anything
Click to expand...
Click to collapse
I and the op posted extensively in that thread. All the solutions there require unlocking your bootloader. If you are going to do that you might as well just flash the factory image.

Ya see that's what the problem is I don't know what's unlocking boot loader and flashing stock ram etc
Sent from my Nexus 7 using xda app-developers app

sfhub said:
I and the op posted extensively in that thread. All the solutions there require unlocking your bootloader. If you are going to do that you might as well just flash the factory image.
Click to expand...
Click to collapse
So if i flash STOCK ROM of a next version would everything be fine ???
I found this video which shows the tutorial
Is it correct ?
http://www.youtube.com/watch?v=bsss9e71bKo&feature=youtube_gdata

red_ferrari007 said:
So if i flash STOCK ROM of a next version would everything be fine ???
I found this video which shows the tutorial
Is it correct ?
http://www.youtube.com/watch?v=bsss9e71bKo&feature=youtube_gdata
Click to expand...
Click to collapse
Person on the other thread mentioned they got a JWR66N->KRT16S OTA update.
Previously we had only seen JSS15R->KRT16S updates, which would mean you would need to get from JWR66N->JSS15R first. The JWR66N->JSS15R update would fail for you, but there is a chance a JWR66N->KRT16S update would work because more files are shipped whole and not as patches.
Regarding the youtube video, it should get your where you need to be. I would skip the relocking of your device though to keep future flexibility in case something like this happens again.
If you want to be on KRT16S(4.4), then just flash the KRT16S factory image. If you want to be on the latest 4.3 then flash JSS15R.
Keep in mind unlocking the bootloader will erase your use data (including your virtual sdcard) so backup anything important and move it off the tablet to your PC or the cloud.

GOT 4.4 UPDATE...Facing Problems
Today Morning I Finally Got Android 4.4 Update OTA. I installed it..... Installation went smooth...
The Tablet Workded fine for 5-6 Hours.... Now I am getting all types of touch screen issues...
1)Non Responsive
2)Ghost Touch
3)Lagging
Please Help

sfhub said:
Person on the other thread mentioned they got a JWR66N->KRT16S OTA update.
Previously we had only seen JSS15R->KRT16S updates, which would mean you would need to get from JWR66N->JSS15R first. The JWR66N->JSS15R update would fail for you, but there is a chance a JWR66N->KRT16S update would work because more files are shipped whole and not as patches.
Regarding the youtube video, it should get your where you need to be. I would skip the relocking of your device though to keep future flexibility in case something like this happens again.
If you want to be on KRT16S(4.4), then just flash the KRT16S factory image. If you want to be on the latest 4.3 then flash JSS15R.
Keep in mind unlocking the bootloader will erase your use data (including your virtual sdcard) so backup anything important and move it off the tablet to your PC or the cloud.
Click to expand...
Click to collapse
Hi, i was that guy on the other thread,i was wondering why i receive different size of ota of kit kat 253.1mb...others almost receiving 242.5 here on our forum of nexus 7.2 philippines wifi version,just wondring why different file size?
Sent from my Nexus 7 using xda premium

Touchsreen Dead
and2nckiko said:
Hi, i was that guy on the other thread,i was wondering why i receive different size of ota of kit kat 253.1mb...others almost receiving 242.5 here on our forum of nexus 7.2 philippines wifi version,just wondring why different file size?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
SOMETHING HAS GONE HORRIBLY WRONG MAN !!!!
My Entire Screen is dead !!! I mean the TAB is Working but My screen is Not Responding !!!! I am Screwed !!!!!
How Can I chat with u contact u ?

Help... Please

I've done rooting before and stuff like that, it was pretty easy. This is my first Samsung device and I wanted to root it so I did but I didn't know it was going to be stuck into "Custom" mode. So now I can't update when it is available. I'm freaking out now I want everything to be stock from now on and I don't know HOW??? I think I have to flash the stock rom in Odin but I don't know how PLEASE HELP!!!
DEVICE: galaxy tab pro 8.4 WiFi 16gb SM-T320
BUILD NUMBER: KOT49H T320UEU1ANG1

Can anyone please help?????

Download your country's firmware. The writer must be how to flash firmware in him website.

fbli_41 said:
Download your country's firmware. The writer must be how to flash firmware in him website.
Click to expand...
Click to collapse
I heard that I won't be able to change it back to official anymore? Is that true? And I know how to flash it now thanks to sammobile

You can still update even on custom, mine received two updates so far but only automatically. You can't manually check for the OTA update when in custom. I know this because I've experienced it.
Or you can install xposed frameworks from the web and get wanam from play store, spoof software status to official and check for OTA updates no problem. Root requires for this method. All these steps are in XDA somewhere, just have to search a little. (Not necessarily on this forum but all Samsung device forums)
Please forgive me I'm too lazy to post a link for you and its hard for me to find it right now because I'm on mobile.
Sent from my Nexus 5 using XDA Free mobile app

sharpehenry said:
You can still update even on custom, mine received two updates so far but only automatically. You can't manually check for the OTA update when in custom. I know this because I've experienced it.
Or you can install xposed frameworks from the web and get wanam from play store, spoof software status to official and check for OTA updates no problem. Root requires for this method. All these steps are in XDA somewhere, just have to search a little. (Not necessarily on this forum but all Samsung device forums)
Please forgive me I'm too lazy to post a link for you and its hard for me to find it right now because I'm on mobile.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That's absolutely fine. Thanks for your help though, greatly appreciated. You see this is my first Samsung device that's why I'm so concerned and confused.. I'm concerned because if I sell this tablet to anyone they would probably be mad about being it on custom status and can't manually check for software updates. But thanks for giving great info. One question though, will my Knox trip again if I reroot? Knox 0x2?
Tab Pro 8.4

I've rooted many times but stayed on 0x1. Not sure what else can tick more. I've rooted and installed custom ROM on many occasions but stayed on 1.
Sent from my Nexus 5 using XDA Free mobile app

geeshiet said:
I heard that I won't be able to change it back to official anymore? Is that true? And I know how to flash it now thanks to sammobile
Click to expand...
Click to collapse
It will official. That is true. I flashed firmware before on my Trend Lite and it is official still

Latest OTA Changelog

I received an update this morning, and was wondering what the differences are?
http://imgur.com/a/oGoIN

I'm wondering too. I hope we got a stagefright patch.
EDIT: I downloaded the Stagefright detector from Google Play after installing the OTA and my phone no longer shows as vulnerable. So I'd wager that was the primary purpose of the patch.
Sent from my HTC6500LVW using XDA Free mobile app

Does anyone know if this OTA will break root?

wbmsp said:
Does anyone know if this OTA will break root?
Click to expand...
Click to collapse
2nd this question and expand it a little bit. If my bootloader is unlocked and I have S-Off (is that the same thing? I forget), will this update mess anything up? I have S-Off and am rooted but am still on the stock ROM.

Any updates on if this Breaks root/roms or anything? I'm Currently running Santods NusenseSix and have to keep going into airplane mode to stop the download.

Oil and water don't mix never take updates if your rooted. Someone slot smarter then me will come up with an alternative
Sent from my HTC6500LVW using Tapatalk