Develop Bugs

I want to leave my phone rooted, but I want ICS when it comes out...

So I recently found out I'm unable to install OTA Android updates to my phone if it's rooted.
So what can I do once ICS is released for the GS2? Will there be a download online that I can just flash with ODIN? Or are people going to be forced to unroot if they want the official ICS stock?

Most likely samfirmware aka sammobile will release an odin .tar, so you'll be good to go with odin.
Sent from my SPH-D710 using Tapatalk

saj1jr said:
So I recently found out I'm unable to install OTA Android updates to my phone if it's rooted.
Click to expand...
Click to collapse
That's not true. You will be unable to install OTA patch-style updates if you have modified one of the files being patched. If you rooted with Auto Root and that's all you did, you will be able to install OTA patch-style updates even without unrooting (though the update will disable root)
saj1jr said:
So what can I do once ICS is released for the GS2? Will there be a download online that I can just flash with ODIN? Or are people going to be forced to unroot if they want the official ICS stock?
Click to expand...
Click to collapse
I'm sure there will be an ODIN update within a few days or maybe even the same day. You can also flash EK02 and let the OTA update upgrade you (or if you've just rooted with Auto Root, just let the OTA update run), though you are probably better off waiting for an update from XDA, because the updates from here will attempt to keep your rooting and upgrade options as open as possible.
I'll also probably have an OTA compliance check for the next official update so you can tell immediately which files are not in compliance with what the update expects. I have one for EG30 to EK02 as part of the Auto Root package, so it would be similar in functionality.

First rule: Never take an OTA update if you care about rooting.
Any file made available from sprint or samsung will have a rooted/safe version posted in the dev section within a few hours of release.
I know samsung is pretty nice to us rooters but you never know when that might change.

lafester said:
First rule: Never take an OTA update if you care about rooting.
Any file made available from sprint or samsung will have a rooted/safe version posted in the dev section within a few hours of release.
I know samsung is pretty nice to us rooters but you never know when that might change.
Click to expand...
Click to collapse
Is there a way to block OTAs? I'm running Calkulin's 2.8 if that matters.

Relax427 said:
Is there a way to block OTAs? I'm running Calkulin's 2.8 if that matters.
Click to expand...
Click to collapse
There is a thread on blocking them in the wiki, provided here for your ease.
http://forum.xda-developers.com/showthread.php?t=1388778
If you are worried about the OTA messing something up, it'll download and ask to install, but if you've made any changes to your ROM, including installing CWM, then it will fail the integrity check and won't install, so nothing will change.

I don't understand the OP's dilemma. Just wait a couple of hours after the OTA update and get a rooted version of the update... no problem!

It won't be out for a few more months anyways. It isn't even being tested yet. I doubt an initial build is even at Samsung. They are working on the the Galaxy S2 right now(the GSM overseas version). And, I am sure Sprint will sell some other phone with ICS stock before they update ours.

[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

OTA Update Today for AT&T S3

68.86Mb Download. Version stays the same 4.4.2 Also Note 2 got OTA also today from AT&T if someone can post on Note 2 page. Thanks
You will loose Root. After Update Baseband Ver. I747UCFUFNJ1, Kernel 3.4.0-1514807 Wed Oct 1, Build Number KOT49H.I747UCUFNJ1 Still 4.4.2 Android

weird. I wonder what they changed. 69MB is pretty small. security patches? POODLE fix perhaps?

How odd as I'm not getting an update notification, but then again I don't want it. All it is is some more bloat and a new kernel. Probably a kernel that has been patched for towelroot. The update may also lock the bootloader, I wouldn't put it past at&t if it did.

Restore to NE4
Can you restore or downgrade to the NE4? When I got my S3 it came with the new update and towelroot doesn't support it.
I also don't want to take a risk of getting knox tripped if I do try to go to NE4.

tailgunner9 said:
68.86Mb Download. Version stays the same 4.4.2 Also Note 2 got OTA also today from AT&T if someone can post on Note 2 page. Thanks
You will loose Root. After Update Baseband Ver. I747UCFUFNJ1, Kernel 3.4.0-1514807 Wed Oct 1, Build Number KOT49H.I747UCUFNJ1 Still 4.4.2 Android
Click to expand...
Click to collapse
Don't install it. I installed on my S3 which is rooted and now it won't boot past the Samsung logo screen. Just goes to a black screen.

RayEdmondson said:
Don't install it. I installed on my S3 which is rooted and now it won't boot past the Samsung logo screen. Just goes to a black screen.
Click to expand...
Click to collapse
Mine fails to install and gets stuck in an update loop. I haven't figured out how to break out of it yet.
EDIT: Managed to get it all sorted out. I was still on i747UCALEM when I got an OTA prompt today. Something happened and it got stuck in an update loop. It was probably failing to install, then failing to rollback. I couldn't get it to flash any of the older roms anymore, when I finally realized I might have partially updated to 4.3+. I was able to install the MJB rom and it booted, but it said "Baseband Unknown". Using adb, I managed to figure out that the OTA had partially installed an I747UCUFNE4 modem. I say partially because I had tried an NE4 rom after the MJB rom and it also failed to identify the baseband. However, getprop ro.bootloader was returning "I747UCUFNE4".
I flashed TWRP back on my device, flashed an NE4 modem properly, and flashed an NE4 rom. This time it found the baseband and everything seems to be working for me. I have no clue if my bootloader is correct, but I'm done for now.

So it's not safe to update with root? I used towelroot and have a clockwork recovery.

CrossBones3129 said:
So it's not safe to update with root? I used towelroot and have a clockwork recovery.
Click to expand...
Click to collapse
No it will put your phone back to Stock, No Root and Stock Recovery.

I updated and my phone is fine, but I don't have root anymore. I used CF-AutoRoot originally, and then I used TowelRoot after the last update. Neither work anymore on the 4.4.2 NJ1 version, so I'm not sure if there is any "easy" way to get root back. I don't really know what the pitfalls involved with TWRP and all the more-involved things.

tailgunner9 said:
No it will put your phone back to Stock, No Root and Stock Recovery.
Click to expand...
Click to collapse
Dang. Guess I'll have to wait till a new root becomes available

I had 2 that were completely stock, both failed and got stuck
in the att boot logo updating then fail loop. No recovery menu
no options. These has stock bootloaders and were not rooted.
So be warned

nightsbird said:
I had 2 that were completely stock, both failed and got stuck
in the att boot logo updating then fail loop. No recovery menu
no options. These has stock bootloaders and were not rooted.
So be warned
Click to expand...
Click to collapse
Same here. No Root. Was on 4.4.2 from this summer. All I did was accept the update, watched it download the 69MB and then let it do its thing. Reboots, says installing, moves to updating then then fails at 95%. Will do this over and over again until I pull battery. Cannot get to recovery, too. I am pissed, since all I did was respond to AT&T's request to update. Otherwise, the phone was perfectly fine. Now I have no use of my phone.
Please post back with solutions.

media_ninja said:
Can you restore or downgrade to the NE4? When I got my S3 it came with the new update and towelroot doesn't support it.
I also don't want to take a risk of getting knox tripped if I do try to go to NE4.
Click to expand...
Click to collapse
Once updated, all attempts to revert back to NE4 result in a brick.
---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------
Have any of you tried this to update?
http://forum.xda-developers.com/galaxy-s3-att/general/ucufne4-to-ucufnj1-update-t2941792

RSI Repair (Samsung authorized service center) Couldnt repair it.
Samsung blamed AT&T and AT&T blamed Samsung. Turned them in as claims to mobile insurance. Galaxy S3 no longer stocked so Mobile insurance gave me 2 Galaxy Alpha's

nightsbird said:
RSI Repair (Samsung authorized service center) Couldnt repair it.
Samsung blamed AT&T and AT&T blamed Samsung. Turned them in as claims to mobile insurance. Galaxy S3 no longer stocked so Mobile insurance gave me 2 Galaxy Alpha's
Click to expand...
Click to collapse
LOL...typical. Neither one takes responsibility. From my understanding of the way the process works with these updates, it would be AT&T at fault since they have to "test and approve" any updates given by Samsung. Of course they will never admit to being at fault.

How can I disable OTA Update? Also anyone else have play store download a ota security policy?

CrossBones3129 said:
How can I disable OTA Update? Also anyone else have play store download a ota security policy?
Click to expand...
Click to collapse
I have used TiBu in the past to stop updates by freezing the software update function in stock based ROM.
Sent from my SAMSUNG-SGH-I747

CrossBones3129 said:
How can I disable OTA Update? Also anyone else have play store download a ota security policy?
Click to expand...
Click to collapse
I used an app from the Play Store called "My Backup Root" to freeze the update. You can also freeze the security policy updates which is a part of KNOX and/or SELinux I gander.

StoneyJSG said:
I used an app from the Play Store called "My Backup Root" to freeze the update. You can also freeze the security policy updates which is a part of KNOX and/or SELinux I gander.
Click to expand...
Click to collapse
Dang i had to use titanium backup pro. Wish I could have found a free one before paying $6 to stop the notification. Idk what Titanum Backup even does

CrossBones3129 said:
Dang i had to use titanium backup pro. Wish I could have found a free one before paying $6 to stop the notification. Idk what Titanum Backup even does
Click to expand...
Click to collapse
My Backup Root is a free app on Google Play Store. Always good to have Titanium Backup Pro though, as it lets you backup all your apps and pretty much anything on the software side of your phone.

Safe to take software update on rooted stock 6.0.1?

I have a Sprint S6 with rooted stock G920PVPS3CPD2. I have been getting a notification for a software update, and I was wondering if it's safe to take it or if I should just ignore it.

its safe.
however, are you rooted? how can you upgrade being rooted?

Yes, I'm rooted with a custom recovery. That's what I was wondering, if the update would mess things up or brick the phone.

If it fails to download, does that mean the update won't be installed? I'd like to update to the latest version but don't want to mess anything up.

imekul said:
I have a Sprint S6 with rooted stock G920PVPS3CPD2. I have been getting a notification for a software update, and I was wondering if it's safe to take it or if I should just ignore it.
Click to expand...
Click to collapse
If your not in United states then dont update if outside US its shows no service (no signals) ...but there still way to get it which is complicated
Sent from my LG-H815 using XDA-Developers mobile app

Is there a way to disable updates without root? [ANSWERED]

I'd like to have the flexibility of choice - I want to be able to prevent my carrier, US Cellular, or Samsung from disabling our crippling the Note should I choose not to return it.
UPDATE: Answered here.
http://forum.xda-developers.com/showpost.php?p=69377632&postcount=42

Package disabler pro
Sent from my SM-N930F using Tapatalk

And then what?

how do you know it's gonna work? I would think OS updates would have been taken care outside of standard packages.

You can go to settings and set to manual updates. It won't "disable but it won't update unless you tell it to
Sent from my SM-G935T using Tapatalk

Well on my first note mine was set to manual and it pushed the update through regardless a few hours after the notification arrived. IMO anybody able to root has nothing to lose by rooting if they're intending to keep it at this point.

Package disabler. Disable System update SDM's. Don't touch anything to do with Knox though.
Disable these:
Security policy updates
Software update
System update 1
System update 2
I've had those frozen on both my original Note 7 and my replacement Note 7 and get no OTA's at all. Don't think they can push them to you with these disabled.

Just bought the Package Disable Pro+ Premium.
Strange.
Have disabled the "Security Policy updates" and "Software update", BUT my replaced Note7 does not have the 2 System Updates. processes.
Anyone knows what should I do?
Also I have the GearVR, and have not connected it to my handset after they push down the patch to disable the use with Note7.
Anyone knows which process to disable too, so that I can continue using the GearVR?
Pls help... Thanks!

flanky79 said:
Just bought the Package Disable Pro+ Premium.
Strange.
Have disabled the "Security Policy updates" and "Software update", BUT my replaced Note7 does not have the 2 System Updates. processes.
Anyone knows what should I do?
Also I have the GearVR, and have not connected it to my handset after they push down the patch to disable the use with Note7.
Anyone knows which process to disable too, so that I can continue using the GearVR?
Pls help... Thanks!
Click to expand...
Click to collapse
I think you have to edit the build-prop (which means you need to be rooted) to get the Gear VR to work.
As far as the 2 system sdm updates - they are on both my Note 7's, but then I haven't ever taken an OTA or any update as I disabled all of that first thing I got the phones (one was my OG N7, the other the replacement N7). So I can't help you if you have already taken an update, but those system SDMs should be there unless they removed them in an update somehow, which I doubt.

teegunn said:
I think you have to edit the build-prop (which means you need to be rooted) to get the Gear VR to work.
As far as the 2 system sdm updates - they are on both my Note 7's, but then I haven't ever taken an OTA or any update as I disabled all of that first thing I got the phones (one was my OG N7, the other the replacement N7). So I can't help you if you have already taken an update, but those system SDMs should be there unless they removed them in an update somehow, which I doubt.
Click to expand...
Click to collapse
Ya, after I received the replacement on 16/9/16 (Singapore), I received an OTA update within the next couple of days that give the green battery.
That is the only update I received.
If it helps, my version is 6.0.1,
Baseband: N960FXXU2BPI5
Build number: MMB29K.N930FXXU2BPI9
So strange...
Does that mean the only choice I have is to root the phone?
(I haven't rooted before)
What is the best "stock" rooted package now?
I'm fine with the default Samsung apps generally, and does not need to have much default functions disabled.

flanky79 said:
Ya, after I received the replacement on 16/9/16 (Singapore), I received an OTA update within the next couple of days that give the green battery.
That is the only update I received.
If it helps, my version is 6.0.1,
Baseband: N960FXXU2BPI5
Build number: MMB29K.N930FXXU2BPI9
So strange...
Does that mean the only choice I have is to root the phone?
(I haven't rooted before)
What is the best "stock" rooted package now?
I'm fine with the default Samsung apps generally, and does not need to have much default functions disabled.
Click to expand...
Click to collapse
This is the first Android phone I have not rooted. Ever. So honestly, I cannot guide you on the root process, as I never did it on either of my Note 7's. I was eventually going to root, but then the recalls hit and I figured there was no point since I will be giving it up soon. But if you took the green battery update, my understanding is that you cannot root and cannot go back to the previous firmware. I do not know if the update you took got rid of the two system update SDM's, someone else will have to help you with that. I would bet that you can still prevent further OTA's with package disabler pro - however, I do not know that for sure. Hopefully others will see this thread and these posts and chime in with info that clears this up for you.

I rooted my replacement note 7 (with green battery update) a few days ago with no problem in anticipation of a crippling update pushed by Samsung: http://forum.xda-developers.com/note-7/development/recovery-official-twrp-galaxy-note-7-t3446047. But by doing so you trigger knox and lose access to secure folder and shealth. I solved the shealth problem by disabling encryption on my device with Hydra Kernel http://forum.xda-developers.com/note-7/development/kernel-hydrakernel-v1-1-t3452433 while keeping stock ROM. I am considering changing to HydraRom http://forum.xda-developers.com/note-7/development/rom-hydra-rom-v1-0-t3447611 just in case.
Hope this helped!

Considering the fact that the phone automatically runs an update at its first boot is there a way to easily shield the device from the mobile network (so that it won't update)?

Cr4z33 said:
Considering the fact that the phone automatically runs an update at its first boot is there a way to easily shield the device from the mobile network (so that it won't update)?
Click to expand...
Click to collapse
Not sure... but you could try removing the sim card

LightningJay said:
Not sure... but you could try removing the sim card
Click to expand...
Click to collapse
OK then it needs a mobile data subscription?
I thought OTAs would be running 'for free' if they are from the same carrier you are connected to?
Sent from my Samsung Galaxy S7 edge with stock Samsung Marshmallow firmware

LightningJay said:
I rooted my replacement note 7 (with green battery update) a few days ago with no problem in anticipation of a crippling update pushed by Samsung: http://forum.xda-developers.com/note-7/development/recovery-official-twrp-galaxy-note-7-t3446047. But by doing so you trigger knox and lose access to secure folder and shealth. I solved the shealth problem by disabling encryption on my device with Hydra Kernel http://forum.xda-developers.com/note-7/development/kernel-hydrakernel-v1-1-t3452433 while keeping stock ROM. I am considering changing to HydraRom http://forum.xda-developers.com/note-7/development/rom-hydra-rom-v1-0-t3447611 just in case.
Hope this helped!
Click to expand...
Click to collapse
What is your replacement baseband Version that you rooted? By any chance was it PI4?

shellie03 said:
What is your replacement baseband Version that you rooted? By any chance was it PI4?
Click to expand...
Click to collapse
My baseband version is PI5

Nice! Can you paste a link of the root method you did, please?
Sent from my SM-N930T using XDA Premium HD app

shellie03 said:
Nice! Can you paste a link of the root method you did, please?
Sent from my SM-N930T using XDA Premium HD app
Click to expand...
Click to collapse
I followed this method http://forum.xda-developers.com/note-7/development/recovery-official-twrp-galaxy-note-7-t3446047

Cr4z33 said:
OK then it needs a mobile data subscription?
I thought OTAs would be running 'for free' if they are from the same carrier you are connected to?
Sent from my Samsung Galaxy S7 edge with stock Samsung Marshmallow firmware
Click to expand...
Click to collapse
My replacement N7 DL'd the update first thing. I did remove the sim and also shut off WIFI, but it had already DL'd the update. But I did not let it install the update. I rebooted and skipped activating the phone. I didn't do any of the first boot setup stuff - skipped all of that, then went to the play store, logged in with my gmail and first thing I installed as package disabler pro. I immediately disabled all the System updates (4 packages). After that I quit getting the notice to install the already DL'd update. Once you disable the System update SDM's, you can't even get into the phone update OTA selection in settings, it kicks you right out. So even though it had DL'd the update, I was able to prevent it from installing.
I do think the phone is trying to look for an update constantly now though. When I look at my GSM battery monitor, system updates is right near the top of what android system is using all the time. I still have excellent battery life, but I think disabling OTA system updates will make the phone constantly try to look for updates that it simply can't run because the SDM's are disabled. I can live with that as gimping the phone with a crappy OTA that limits the battery or might add other possible things I didn't want was the main goal. Phone runs great and battery life is great. That's all I need.