Related
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
So, I have an i317 At&t note 2. It was originally on 4.3, but I wanted to unlock it. I followed some forum posts and reverted back to 4.1 and was able to unlock it. It worked with a tmobile sim on 4.1.1, but now when I try to update it (either through Kies or through update on phone), it updates but then gets stuck at the samsung galaxy note 2 display. I found another forum post (thanks, but cant find thread atm ) which had a file to download. I installed that using Odin, but that only got it to work on 4.1.1.
I guess my question is I have the note 2 running on 4.1.1 that I factory unlocked, but now it wont let me update. How do I get 4.3 on it? Thanks
Ok there's plenty of 4.3 Rom's in the development section...
Just have to search for them!
Q: »»»»
Is it rooted?
Do you have a custom recovery installed?
Are you sure your familiar flashing Rom's?
Etc etc etc......
SENT FROM MY SAMMY i317 USING TAPATALK4
Bajanman said:
Ok there's plenty of 4.3 Rom's in the development section...
Just have to search for them!
Q: »»»»
Is it rooted?
Do you have a custom recovery installed?
Are you sure your familiar flashing Rom's?
Etc etc etc......
SENT FROM MY SAMMY i317 USING TAPATALK4
Click to expand...
Click to collapse
It is not rooted. All I have done to it is downgrade it to 4.1.1, then unlocked it. Is there a stock ROM. I want to be able to go into settings -> about phone -> and update it that way whenever a new version comes out and not have to install custom ROMS. Is that possible?
No, I don't have a custom recovery installed and I am not familiar with flashing Rom's.
I thought I could downgrade to 4.1.1, unlock, then update to the newest stock version through updates in the phone, but thats not the way it works when you unlock the note 2??
thanks
Pardon me if I sound ignorant. I am new to android (switched over from apple a month ago). The note 2 had 4.3 on it. I followed thread
http://forum.xda-developers.com/showthread.php?t=2014982
to unlock my phone, but had to revert back to 4.1.1 in order to do so. I followed posting
http://wccftech.com/guide-to-downgrade-firmware-on-samsung-galaxy-devices/
to downgrade to 4.1.1. That went successfully and I successfully unlocked the note and all was good. It was running 4.1.1 and I was using a tmobile sim. I went to updates through settings on the phone and tried to update. After that point, it just boots up to "samsung galaxy note 2" screen. I used Odin3 v3.07 to reinstall 4.1.1 and its working again.
I would ideally like to be able to go through software updates on the phone to update it and not need to use custom roms. Is the problem I am trying to update from 4.1.1 to 4.3 and I need to manually update to 4.2.x first, then go to 4.3?
I don't understand why unlocking it prevents me from updating from 4.1.1. I have tried through the phone and through Kies, which keeps getting an error. Does this make sense? Am i doing something wrong? The phone is originally At&t. Do I need an At&t sim inserted to update through the phone?
thanks for all the help and once again, sorry if these questions seems elementary. I am reading through forum posts and trying to understand what all this means. I'm not sure what rooting or flashing means and how flashing is different then unlocking.
Thanks for the help
scottrf8 said:
Pardon me if I sound ignorant. I am new to android (switched over from apple a month ago). The note 2 had 4.3 on it. I followed thread
http://forum.xda-developers.com/showthread.php?t=2014982
to unlock my phone, but had to revert back to 4.1.1 in order to do so. I followed posting
http://wccftech.com/guide-to-downgrade-firmware-on-samsung-galaxy-devices/
to downgrade to 4.1.1. That went successfully and I successfully unlocked the note and all was good. It was running 4.1.1 and I was using a tmobile sim. I went to updates through settings on the phone and tried to update. After that point, it just boots up to "samsung galaxy note 2" screen. I used Odin3 v3.07 to reinstall 4.1.1 and its working again.
I would ideally like to be able to go through software updates on the phone to update it and not need to use custom roms. Is the problem I am trying to update from 4.1.1 to 4.3 and I need to manually update to 4.2.x first, then go to 4.3?
I don't understand why unlocking it prevents me from updating from 4.1.1. I have tried through the phone and through Kies, which keeps getting an error. Does this make sense? Am i doing something wrong? The phone is originally At&t. Do I need an At&t sim inserted to update through the phone?
thanks for all the help and once again, sorry if these questions seems elementary. I am reading through forum posts and trying to understand what all this means. I'm not sure what rooting or flashing means and how flashing is different then unlocking.
Thanks for the help
Click to expand...
Click to collapse
What is unclear is why ware you trying unlock it, what carrier it was on and what carrier you are changing to,
You're asking if it needs an ATT SIM to update, so I'm lost on what carrier it was on.
The original carrier is at&t. I unlocked it and now am using a tmobile sim. However, when I got to settings and check for updates, it says "checking at&t servers for updates". So it is working for tmobile now, but only on 4.1.1. I don't mind downloading custom roms (and definitely appreciate the work), but I would like the option to not have to.
And when I boot up the phone, even though the network says tmobile, it shows at&t start up screen when it boots up into 4.1.1. Which is why u was thinking maybe the reason it won't do updates through the phone is cause there is no at&t sim inserted when it is "checking at&t server for updates"
scottrf8 said:
And when I boot up the phone, even though the network says tmobile, it shows at&t start up screen when it boots up into 4.1.1. Which is why u was thinking maybe the reason it won't do updates through the phone is cause there is no at&t sim inserted when it is "checking at&t server for updates"
Click to expand...
Click to collapse
Well, over my head here. I think you have figured out technically why it's not working.
You are operating on a T-mobile network and you will not see ATT servers.
Even though it's says you are on T-mobile is anything working? Like texting, surfing or cell calls?
I would imagine texting is not since the config should be pointing at ATT servers.
I would think you should be running one of these factory images
http://forum.xda-developers.com/showthread.php?t=1969551
I personally do not know if the T-889 is close to the ATT Note 2 model.
You may want to bounce over to this forum
http://forum.xda-developers.com/note-2-tmobile
See if anyone has attempted what you are doing.
In my mind you need to flash a T-mobile image to do what you want.
I am not suggesting you do this, I am merely giving you an opinion.
You may want to investigate this custom ROM
http://forum.xda-developers.com/showthread.php?t=2568537
||ROM|| Jedi MasterX2 ||4.3||MULTICARRIER
Yeah, I dunno. It's an i317 on at&t. And it was definitely on tmobile cause it let me send text messages and it showed "tmobile" across the top as well as their 4g icon.
All I was trying to do was unlock my at&t note 2. Now its unlocked but stuck to 4.1.1. Lol
scottrf8 said:
Yeah, I dunno. It's an i317 on at&t. And it was definitely on tmobile cause it let me send text messages and it showed "tmobile" across the top as well as their 4g icon.
All I was trying to do was unlock my at&t note 2. Now its unlocked but stuck to 4.1.1. Lol
Click to expand...
Click to collapse
You may want to investigate this custom ROM
http://forum.xda-developers.com/show....php?t=2568537
||ROM|| Jedi MasterX2 ||4.3||MULTICARRIER
It is customized to install for multiple carriers. It's a user configurable install. You can pick which carrier you are, which apps to install etc.
It is 4.3
hey dicksteele, the page isnt found....
scottrf8 said:
hey dicksteele, the page isnt found....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2568537
Main page
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Hi All,
My wife's old AT&T Galaxy Note 2 - never been rooted - is still on 4.3.
So I went to Software update and it is saying that the update has been interrupted and I have to wait 24 hours. So I keep on restoring to factory defaults / changing the time trick -- and It still fails. I have clue why it can't pick up the updates from the AT&T Servers.
Is there a way to update it forcefully - Like using ODIN or something? The last time I tried this (even with the official AT&T ROM - it tripped the counter of my Galaxy Note 1). -- is it the same case with ODIN and Note 2?
Also, the more important question is - will I lose my SIM unlock if I update to 4.4.2 via ODIN or other methods?
Long time ago, I have used the trick *#197328640# and it worked wonders. Will I lose it in 4.4.2 ?
As much as possible, I don't want to root it because I will sell it and he doesn't want rooted phones.
Thank you.
keplenk said:
Hi All,
My wife's old AT&T Galaxy Note 2 - never been rooted - is still on 4.3.
So I went to Software update and it is saying that the update has been interrupted and I have to wait 24 hours. So I keep on restoring to factory defaults / changing the time trick -- and It still fails. I have clue why it can't pick up the updates from the AT&T Servers.
Is there a way to update it forcefully - Like using ODIN or something? The last time I tried this (even with the official AT&T ROM - it tripped the counter of my Galaxy Note 1). -- is it the same case with ODIN and Note 2?
Also, the more important question is - will I lose my SIM unlock if I update to 4.4.2 via ODIN or other methods?
Long time ago, I have used the trick *#197328640# and it worked wonders. Will I lose it in 4.4.2 ?
As much as possible, I don't want to root it because I will sell it and he doesn't want rooted phones.
Thank you.
Click to expand...
Click to collapse
Here if you haven't figured it out yet try this
http://forum.xda-developers.com/showthread.php?t=2618447
This will downgrade to 4.1.1 then ota to 4.3 but it wont root it and thats what your problem
Check for OTA Update in your settings.
Is it Lollipop?
I don't think so. I think it is a security update.
I'm rooted on stock rom so i just froze it using Titanium backup. Heard people installed the update and it froze there rooted phone.
Update the Software for the Samsung Galaxy Note II (i317)
Update summary
AT&T released a new software update for the Samsung Galaxy Note 2 (SGH-i317) via Firmware Over the Air (FOTA) over Wi-Fi on November 11, 2014.
Software Update Includes
Android OS Enhancements
User-Initiated Software Update
From the Home screen, press the Menu key.
Tap Settings.
Tap the More tab.
Tap About Device.
Tap Software update.
Tap Check for updates, and then follow the subsequent prompts.
Verifying the Update
From the Home screen, press the Menu key.
Tap Settings.
Tap the More tab.
Tap About Device.
The following information displays:
Android version: 4.4.2
Baseband version: I317UCUCNJ1
Kernel version: 3.0.31-1728680 [email protected] #1 Wed Oct 1 22:38:36 KST 2014
Build number: KOT49H.I317UCUCNJ1
File size: 93.2MB
I already have TWRP installed (stock rooted - last build) and I'm just wondering if it is worth it go back to stock recovery and update - then reinstall TWRP all over again.
What do you think guys?
keplenk said:
I already have TWRP installed (stock rooted - last build) and I'm just wondering if it is worth it go back to stock recovery and update - then reinstall TWRP all over again.
What do you think guys?
Click to expand...
Click to collapse
I wouldn't. I just posted this in the other thread about the OTA:
a042349 said:
Same thing happened to me. Rooted but otherwise stock GN2. Got the update, rebooted and it got stuck at the boot logo. I tried everything. Flashed CWM, then tried a couple different ROM's. Then went to TWRP recovery, and tried the Team Elektron ROM, that got a little farther, boot logo with sound, but it still hung. Tried a modem update, and even the bootloader - nothing worked.
Luckily I had just bought mine ($300 on Amazon right now) so I just sent it back as defective and ordered a new one. Gonna be real careful of the ATT update and maybe even skip it and go right to a custom ROM.
Click to expand...
Click to collapse
same thing just happened to me. Got stuck on the "Launching Apps" screen. tried everything to recover. still have black tie protection on my phone from BB and decided to have them swap it under my plan.
New phone, up to date on 4.4.2 NJ1 but i would like to root now. Anyone successful yet?
kabinoff said:
same thing just happened to me. Got stuck on the "Launching Apps" screen. tried everything to recover. still have black tie protection on my phone from BB and decided to have them swap it under my plan.
New phone, up to date on 4.4.2 NJ1 but i would like to root now. Anyone successful yet?
Click to expand...
Click to collapse
Best way is to download a custom recovery and flash it in Odin. Then when boot hold on the home and up key to enter recovery. If the phone boot complete withou enter recovery, the recovery would be replaced with the factory recovery. When in recovery flash supersu zip and restart. The recovery will be replaced with the factory recovery, but you had root installed, enter supersu and reboot.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
melvinaury said:
Best way is to download a custom recovery and flash it in Odin. Then when boot hold on the home and up key to enter recovery. If the phone boot complete withou enter recovery, the recovery would be replaced with the factory recovery. When in recovery flash supersu zip and restart. The recovery will be replaced with the factory recovery, but you had root installed, enter supersu and reboot.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
actually flashed CF with Odin and it worked.
kabinoff said:
actually flashed CF with Odin and it worked.
Click to expand...
Click to collapse
Did it really work?
I don't understand one thing - official 4.4.2 OTA was released over a month ago, correct?
I have two Note 2 SGH-I317s AT&T branded with OEM 4.3 (no rooting or other non-OEM additions).
If I stick working AT&T SIM card and check for updates it says the device is up to date.
Moreover if I'd connect it to Kies it would also say that firmware is up to date!
Same thing on both phones - what am I missing?
I purchased them used - maybe the previous owners rooted them and this prevents them from updating?
One had a Knox at "1" since I for some stupid reason downgraded it to 4.1 via Odin (and then took it to AT&T service center where they flashed 4.3 back), another one has Knox at "0"...
toshik1 said:
I don't understand one thing - official 4.4.2 OTA was released over a month ago, correct?
I have two Note 2 SGH-I317s AT&T branded with OEM 4.3 (no rooting or other non-OEM additions).
If I stick working AT&T SIM card and check for updates it says the device is up to date.
Moreover if I'd connect it to Kies it would also say that firmware is up to date!
Same thing on both phones - what am I missing?
I purchased them used - maybe the previous owners rooted them and this prevents them from updating?
One had a Knox at "1" since I for some stupid reason downgraded it to 4.1 via Odin (and then took it to AT&T service center where they flashed 4.3 back), another one has Knox at "0"...
Click to expand...
Click to collapse
Is service activated on the AT&T SIM? That might be a factor.
Regardless, there are two 4.4.2 official releases for the I317 - NE5 and NJ1. If OTA won't work for you, check my sig for links to packages that provide another way to get the complete stock firmare on your phone - rooted or unrooted.
Zen Arcade said:
Is service activated on the AT&T SIM? That might be a factor.
Regardless, there are two 4.4.2 official releases for the I317 - NE5 and NJ1. If OTA won't work for you, check my sig for links to packages that provide another way to get the complete stock firmare on your phone - rooted or unrooted.
Click to expand...
Click to collapse
Yes the SIM card has normal active service on it.
Other reasons OTA won't work:
1 - Location (if you are not in an area where OTA updates are provided, then...
)
2 - AT&T Update apk disabled on phones (seems unlikely that this would be the case on two phones but a factory reset might clear this as it is set on the data side)
3 - Identity issues (could be any number of things related to IMEI, efs partition scrambling, etc - just spitballing)
As far as suggestions go, I'd say try a factory reset and clear cache from recovery. If that doesn't work, maybe go back to AT&T and see if they can figure it out - the phones are stock and it's their OTA process. If that doesn't work, you can pursue the path I suggested previously - same firmware update, minus the script that pushes stock recovery every time you boot. You will trip the knox flag though...only an issue for warranty repair really. Others here have intentially or unitentionally received the NJ1 OTA with the knox flag tripped on their phones.
DroidTuner said:
I don't think so. I think it is a security update.
I'm rooted on stock rom so i just froze it using Titanium backup. Heard people installed the update and it froze there rooted phone.
Click to expand...
Click to collapse
Which process did you freeze?
I did a hard reset and finally took 423.13(!!!) Mb upgrade! Be careful what you wish for
Got 4.4.2 I317UCUCNE5
toshik1 said:
I did a hard reset and finally took 423.13(!!!) Mb upgrade! Be careful what you wish for
Got 4.4.2 I317UCUCNE5
Click to expand...
Click to collapse
Glad to hear it. Wait a day (or disable network time and the set the time on the phone forward at least a day) and try again - you should get NJ1. (If that's what you want). Approx. 93MB security and minor enhancement update.
Just to follow-up - it took the second update with T-Mobile SIM card even without waiting for 24 hours.
I guess in order to take the updates the phone's IMEI MUST re-register on AT&T network with the valid AT&T SIM card first.
It's now I317UCUCNJ1
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.