Related
Anyone knows what is this?
Will it affect the rooting on my note 3 if I update?
Sent from N9005 4.4.2 NB7 rooted device
antique_sonic said:
Anyone knows what is this?
Will it affect the rooting on my note 3 if I update?
Sent from N9005 4.4.2 NB7 rooted device
Click to expand...
Click to collapse
You should turn off Automatic Security Policy Updates in Settings -> General -> Security.
Uncheck Auto update Security and depending on your usage, disable or enable Via Wifi Only so that it doesn't constantly ask.
They could patch some KNOX stuff and certificates in these updates, so you wouldn't want it if you're rooted.
Grabbed photo from AC:
nicholaschum said:
You should turn off Automatic Security Policy Updates in Settings -> General -> Security.
Uncheck Auto update Security and depending on your usage, disable or enable Via Wifi Only so that it doesn't constantly ask.
They could patch some KNOX stuff and certificates in these updates, so you wouldn't want it if you're rooted.
Grabbed photo from AC:
Click to expand...
Click to collapse
Thanks man.
Unchecked alrd. I just curious whether it will affect the rooting or not. Coz I googling, but can't find anything so far till you answer me.
I am considering rooting my Canadian (Rogers) Note 3 (SM-N900W8) in order to defeat the ludicrous SD-Card crippling brought by the latest Kitkat 4.4.2 software update. I'm aware that by doing so the Knox 0x1 counter will void the warranty. What I'd like to know is whether there are any additional negative results besides this well-known one.
For example I've seen inconsistent reports of the Screen Mirroring function being disabled as soon as the device is rooted. Some claim it is more related to the presence of a custom kernel, recovery or ROM, while others insist that merely rooting with everything stock was enough to disable screen mirroring.
If I do nothing more than use CF-Autoroot as described here:
http://forum.xda-developers.com/showthread.php?t=2466423
...no custom recovery, kernel or ROM, do I risk any undesirable repercussions other than the warranty and Knox issue? Will screen mirroring or any other functions work worse than they did before?
Thanks for any help...
Rooting won't break any functionality of the phone except the security it was meant for i.e the secure container ( and of course, depending on who you ask, warranty ). Problems you mentioned are probably related to custom roms themselves.
Sent from my SM-N900W8 using xda app-developers app
hey_joe said:
Rooting won't break any functionality of the phone except the security it was meant for i.e the secure container ( and of course, depending on who you ask, warranty ). Problems you mentioned are probably related to custom roms themselves.
Click to expand...
Click to collapse
Thanks for your reply... and will it also not interfere with any potential future over-the-air updates that might come along, be it a 4.4.3 update or a more trivial software patch to fix an issue that gets released? I realize that a major enough OTA update might un-root the phone which is fine.. I just wouldn't want to brick or lose access to updates because of root. Would they continue to be accessible, or would I likely have to first un-root manually to enable them?
Thanks again...
Yes you can not OTA update on the rooted phone.
You can unroot and apply the OTA update.
Or use the fake system status option in the Wanam.
vndnguyen said:
Yes you can not OTA update on the rooted phone.
You can unroot and apply the OTA update.
Or use the fake system status option in the Wanam.
Click to expand...
Click to collapse
Thanks... if memory serves (been a while for me since last rooted device) all that is necessary to unroot is to run the administrative option from within the Superuser app itself, to remove the SU binary completely.. correct? And then to re-root just repeat the previous CF-Autoroot steps and regain SU?
paleozord said:
Thanks for your reply... and will it also not interfere with any potential future over-the-air updates that might come along, be it a 4.4.3 update or a more trivial software patch to fix an issue that gets released? I realize that a major enough OTA update might un-root the phone which is fine.. I just wouldn't want to brick or lose access to updates because of root. Would they continue to be accessible, or would I likely have to first un-root manually to enable them?
Thanks again...
Click to expand...
Click to collapse
You don`t need OTA`s mate, just download the new updated rom from Sammobile and flash it with Mobile Odin Pro and you`ll even keep root
gee2012 said:
You don`t need OTA`s mate, just download the new updated rom from Sammobile and flash it with Mobile Odin Pro and you`ll even keep root
Click to expand...
Click to collapse
So all ROM and software updates are always made available directly from Samsung as flashable downloads, on the same day they're released to devices over-the-air? As a general rule?
paleozord said:
So all ROM and software updates are always made available directly from Samsung as flashable downloads, on the same day they're released to devices over-the-air? As a general rule?
Click to expand...
Click to collapse
Within a day usualy you can download the full rom from here www.sammobile.com/firmwares/2/ and flash it with Odin or better yet Mobile Odin.
paleozord said:
So all ROM and software updates are always made available directly from Samsung as flashable downloads, on the same day they're released to devices over-the-air? As a general rule?
Click to expand...
Click to collapse
Or you can open the app Phone INFO ★Samsung★, select menu 'Firmware Browser...' to see a list of available stock firmwares for your phone.
Tap to view firmware's details, there is also a download link. You can download it and then flash by Kies or Odin.
(screenshots are attached)
I'm not rooted but I can't launch s health on the final version of Nougat that my phone updated to today. (Xxu1dplt)
It says about a Knox warning and device compromised?
It's running stock though! Anyone else with the same issue?
Have you ever rooted before and then unrooted? Sorry if stupid question
Sent from my SM-G935F using XDA-Developers Legacy app
Once knox is tripped, game over even if you unroot.
jadaress1 said:
Have you ever rooted before and then unrooted? Sorry if stupid question
Sent from my SM-G935F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Nope. I assumed s health didn't work in earlier beta due to being beta.
I've never rooted this phone. Only thing I did was install beta by applying in the beta app.
Try uninstall and re-install again s-health
Go to download mode by switching off the device then hold Power + Volume Down + Home
Does it say Warranty void: 1?
CuBz90 said:
Go to download mode by switching off the device then hold Power + Volume Down + Home
Does it say Warranty void: 1?
Click to expand...
Click to collapse
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.
f1ux said:
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.
Click to expand...
Click to collapse
Ye if Knox has tripped, Samsung will have nothing to do with it, even if it's their fault, they just don't want to hear about it.
f1ux said:
It wasn't but it is now. Seems somehow during the beta it has tripped it. I contacted samsung and they're not interested.
It doesn't matter now as i've bit the bullet and installed twrp+renovate edge rom. Ironically renovate edge is running better than the official rom did with better doze despite having all the same apps installed. And s-health works fine on it.
Not sure what samsung are trying to prove by crippling people running the official ROM.
Click to expand...
Click to collapse
If what you want is to use SHealth on stock nougat with a knox tripped phone, I can give you a working solution with one caveat.
If you were already a beta tester you need to Odin back to BTU mm (or whatever CSC version you used to join the beta) and setup your phone normally. Make sure you also open SHealth. After, if you have not received a notification to update, go to settings and manually search for updates. Depending on which version of marshmallow you went back to, you might receive one update to the latest 6.0.1 available and after that, you will again be prompted to update, this time to 7.0. If you follow these steps, SHealth will work, even with knox tripped, but, if you manually reset the phone. SHealth will be blocked once again.
I know it seems a little complicated, but it's really not that hard.
Hope this helps.
f1ux said:
Nope. I assumed s health didn't work in earlier beta due to being beta.
I've never rooted this phone. Only thing I did was install beta by applying in the beta app.
Click to expand...
Click to collapse
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.
joejoe23 said:
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.
Click to expand...
Click to collapse
people lie. the dindu nuffins
joejoe23 said:
This is weird . There's no way Knox is tripped without you doing anything like flashing TWRP.
Click to expand...
Click to collapse
yes, i've been flashing my phone for around 10times with official binaries and never tripped knox. I flashed BTU(from INS) and updated to N, s health working fine here
Ive had the same problem, after flashing the official UK Rom. Knox is not triggered but shealth refused to work.
I reflashed the rom using every file incl. CSC and now everything works like it should.
1stlynx said:
Ive had the same problem, after flashing the official UK Rom. Knox is not triggered but shealth refused to work.
I reflashed the rom using every file incl. CSC and now everything works like it should.
Click to expand...
Click to collapse
I am quite new at this, so you basically did this in Odin?
.... can't post link to picture
You add in Odin: BL, AP, CP and CSC ?
I have the same problem in Shealth, and i would really like to stick with warrenty (Currently in the dawnload mode is still 0). And with Shealth compromised, My Knox app doesn't works as well.
Punisher159 said:
I am quite new at this, so you basically did this in Odin?
.... can't post link to picture
You add in Odin: BL, AP, CP and CSC ?
I have the same problem in Shealth, and i would really like to stick with warrenty (Currently in the dawnload mode is still 0). And with Shealth compromised, My Knox app doesn't works as well.
Click to expand...
Click to collapse
Hi,
i used this guide :
https://www.sammobile.com/forum/showthread.php?t=30800
dont know if i am allowed to post the link.
i did step 3.
Way to make shealth working on tripped but stock devices:
Install marshmallow with odin
Run shealth for it to start collecting user data
Update to nougat without wiping device
profit
kartonick said:
Way to make shealth working on tripped but stock devices:
Install marshmallow with odin
Run shealth for it to start collecting user data
Update to nougat without wiping device
profit
Click to expand...
Click to collapse
i have tried that but i wont count steps. so its of no use. when updated it... stopped working completely
poncespr said:
If what you want is to use SHealth on stock nougat with a knox tripped phone, I can give you a working solution with one caveat.
If you were already a beta tester you need to Odin back to BTU mm (or whatever CSC version you used to join the beta) and setup your phone normally. Make sure you also open SHealth. After, if you have not received a notification to update, go to settings and manually search for updates. Depending on which version of marshmallow you went back to, you might receive one update to the latest 6.0.1 available and after that, you will again be prompted to update, this time to 7.0. If you follow these steps, SHealth will work, even with knox tripped, but, if you manually reset the phone. SHealth will be blocked once again.
I know it seems a little complicated, but it's really not that hard.
Hope this helps.
Click to expand...
Click to collapse
Hello,
I am interested with the first solution. Can you please give me more detail how to proced ? Thank you in advance
does samsung pay works with u? i bought a second hand uk handset without having any knowledge of knox which was tripped. though i got it to work following a post here, samsung pay doesnot work evenon stock firmware.
elkhalifi said:
Hello,
I am interested with the first solution. Can you please give me more detail how to proced ? Thank you in advance
Click to expand...
Click to collapse
Thank you poncespr, your solution woked for me.
I am able to launch SHealth again
Hey there, everybody. I'm currently running a manually odexed version of the stock N900VVRUEOF1 firmware, with bootloader unlock, TWRP 2.8.7.0, and am both rooted and running Xposed framework...
Out of nowhere, I see a long-forgotten icon, in my notification tray. It's saying there's a software update available! I wanted to make sure this wasn't some fluke (or to make sure I wasn't dreaming), so I checked out Verizon's update list.
https://www.verizonwireless.com/support/software-updates/
Lo, and behold! There's an actual, honest-to-goddess update! (Listed as: LRX21V.N900VVRSEPL1)
However, there is little to no information on what it is or does, apart from the ever-vague "latest security updates"...
Fearing a potential planned obsolescence (like the Note 7) or it wrecking my custom root/recovery/bootloader status, I haven't installed it.
I could try to unpack it all and go digging through it, but that takes way more time or energy than I can currently devote to this sort of thing...
Does anybody know what is involved with this update or have any other information as-to what it includes?
Sent from my SM-N900V using Tapatalk
Would love to know as well. However I am not rooted nor do I want to.
I was honestly shocked when I saw the notification.
I'm tempted to go through with the update but since I like how I have my phone setup at the moment, im really hesitant to install it.
Would love to hear from anyone that has!
Update...
New update is just a security update for Lollipop.... http://www.galaxynote3update.com/verizon-galaxy-note-3-updates-lrx21v-n900vvrsepl1/
Kancerstick said:
Would love to know as well. However I am not rooted nor do I want to.
I was honestly shocked when I saw the notification.
I'm tempted to go through with the update but since I like how I have my phone setup at the moment, im really hesitant to install it.
Would love to hear from anyone that has!
Click to expand...
Click to collapse
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
New update is just a security update for Lollipop.... http://www.galaxynote3update.com/verizon-galaxy-note-3-updates-lrx21v-n900vvrsepl1/
NeoHiPPy1980 said:
Hey there, everybody. I'm currently running a manually odexed version of the stock N900VVRUEOF1 firmware, with bootloader unlock, TWRP 2.8.7.0, and am both rooted and running Xposed framework...
Out of nowhere, I see a long-forgotten icon, in my notification tray. It's saying there's a software update available! I wanted to make sure this wasn't some fluke (or to make sure I wasn't dreaming), so I checked out Verizon's update list.
https://www.verizonwireless.com/support/software-updates/
Lo, and behold! There's an actual, honest-to-goddess update! (Listed as: LRX21V.N900VVRSEPL1)
However, there is little to no information on what it is or does, apart from the ever-vague "latest security updates"...
Fearing a potential planned obsolescence (like the Note 7) or it wrecking my custom root/recovery/bootloader status, I haven't installed it.
I could try to unpack it all and go digging through it, but that takes way more time or energy than I can currently devote to this sort of thing...
Does anybody know what is involved with this update or have any other information as-to what it includes?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
GoNavyMike said:
New update is just a security update for Lollipop.... http://www.galaxynote3update.com/verizon-galaxy-note-3-updates-lrx21v-n900vvrsepl1/
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
New update is just a security update for Lollipop.... http://www.galaxynote3update.com/verizon-galaxy-note-3-updates-lrx21v-n900vvrsepl1/
Click to expand...
Click to collapse
Thanks for the update, GoNavyMike.
That's about all I could find as well. :-/
In an effort to get a better idea of what has changed, would you have happened to have installed this? If so, would you say that there's any noticeable difference in performance or features, apart from the obvious potential app updates?
I'm all for the performance fixes and whatnot, but I really don't wanna lose root. Does this patch over current root methods, bump the Lollipop build up to 5.1 (sdk21), or anything like that? These are the kinds of things that a number of folks (myself included) are curious about. If you have updated, any insight you might provide would be very valuable!
Thanks for your time!
Sent from my SM-N900V using Tapatalk
Was shocked to see myself.
I'm having trouble to disable the notification.
Tried using disable services from the playstore and unticking system update from Google framework also tried the Disable system updates app for rooted devices. Also the tick mark to hide notifications is grayed out on System Update in applications.
Im running Stock VRUEOF1 with TWRP and rooted.
Any suggestions?
My GF and I both have the Note 3. Mine is rooted and her's is stock, so I told her to go ahead and install it. Yeah, it's just a security update. I decided to update mine and it fails with the 402 error. Likely because I'm rooted. I need to look into deleting the update and blocking OTA.
BEWARE
Hey so I've got the 900v and it was rooted stock deodexed with a few rom toolbox tweaks. After the updated I was soft bricked - had to revert back to factory with Odin - no fun.
OffTheChainz said:
Was shocked to see myself.
I'm having trouble to disable the notification.
Tried using disable services from the playstore and unticking system update from Google framework also tried the Disable system updates app for rooted devices. Also the tick mark to hide notifications is grayed out on System Update in applications.
Im running Stock VRUEOF1 with TWRP and rooted.
Any suggestions?
Click to expand...
Click to collapse
I used titanium backup pro and I froze the software update and it removed the annoying update pop up and stoped the updating from happening.
xm41907 said:
My GF and I both have the Note 3. Mine is rooted and her's is stock, so I told her to go ahead and install it. Yeah, it's just a security update. I decided to update mine and it fails with the 402 error. Likely because I'm rooted. I need to look into deleting the update and blocking OTA.
Click to expand...
Click to collapse
Thanks for the heads-up. This is the sort of thing I was worried about. Firstly, whether being rooted would mess with the update (perhaps it's just a partial update...?) and secondly, that I'd be able to keep root.
Assuming that your GF is okay with you borrowing her phone (which IS a rather large assumption, for nearly anybody), would you mind trying to see if current rooting methods still work for the new update?
bprintz44 said:
Hey so I've got the 900v and it was rooted stock deodexed with a few rom toolbox tweaks. After the updated I was soft bricked - had to revert back to factory with Odin - no fun.
Click to expand...
Click to collapse
I'm sorry to hear about having to do the full backup and restore... According to what yourself and xm41907 have posted, it apparently checks for full stock. Not sure how you managed to get as far as you did, but at least we know that this update doesn't play nice with rooted phones.
Performance/security improvements are great and all, but there are plenty of Xposed mods and manual tweaks to take care of that-- as long as there's still root.
If there's anybody who doesn't care whether they have root or not, I'd love to hear if current rooting methods still work after the new update, or if this update patches over or current for exploits.
Disclaimer: If you update, you do so at your own risk. However, we'd love to hear more about the details and any root-related insight.
Thanks, everybody!
Sent from my SM-N900V using Tapatalk
NeoHiPPy1980 said:
Assuming that your GF is okay with you borrowing her phone (which IS a rather large assumption, for nearly anybody), would you mind trying to see if current rooting methods still work for the new update?"
Click to expand...
Click to collapse
I can ask if she is ok attempting root. I've been out of it since the Verizon Note 3 first got root capability. This brought me back to it seeing the bootloader can be unlocked and roms put on. I'm jazzed to try AryaMod !
I'm worried about what specifically it means by "Security Updates". I'm still on the OLD unlimited data plan. Because of this, I have to use FoxFi to tether as Verizon doesn't allow it. I'm worried this update may block it.
Can anyone confirm FoxFi still bypasses Verizon's tethering check post update? My Note 3 is totally stock, not rooted, and updated to the last patch(before this one).
Thanks!
Gaylo said:
I'm worried about what specifically it means by "Security Updates". I'm still on the OLD unlimited data plan. Because of this, I have to use FoxFi to tether as Verizon doesn't allow it. I'm worried this update may block it.
Can anyone confirm FoxFi still bypasses Verizon's tethering check post update? My Note 3 is totally stock, not rooted, and updated to the last patch(before this one).
Thanks!
Click to expand...
Click to collapse
I ran the update over a day ago and FoxFi still works.
RITMan said:
I ran the update over a day ago and FoxFi still works.
Click to expand...
Click to collapse
Im in the same boat but I'll wait a while before playing with FoxFi
Gaylo said:
I'm worried about what specifically it means by "Security Updates". I'm still on the OLD unlimited data plan. Because of this, I have to use FoxFi to tether as Verizon doesn't allow it. I'm worried this update may block it.
Can anyone confirm FoxFi still bypasses Verizon's tethering check post update? My Note 3 is totally stock, not rooted, and updated to the last patch(before this one).
Thanks!
Click to expand...
Click to collapse
For those wondering...
I went ahead and did the update. Foxfi is still working post update
Thanks everyone for your continued feedback about this update. I am still clinging on to my Note 3. This is most certainly my last subsidized phone on VZW with my UDP.
In any event, I was just as shocked as you guys to see the system update notification. I went straight to Tibackup and froze the "System updates" app, which has tamed the notifications.
I did the update 2 days ago on my non-rooted note 3.
Everything is pretty much the same I dont notice any difference really.
Only thing is it seems my battery life has become worse.
Kancerstick said:
I did the update 2 days ago on my non-rooted note 3.
Everything is pretty much the same I dont notice any difference really.
Only thing is it seems my battery life has become worse.
Click to expand...
Click to collapse
That's what I've noticed too maybe we just need to factory reset our phone somebody should test that and give us feedback I haven't noticed anything changed with this update maybe possibly a better signal will update in a couple days and battery light seems to be an affected slightly
teckynerd6249 said:
That's what I've noticed too maybe we just need to factory reset our phone somebody should test that and give us feedback I haven't noticed anything changed with this update maybe possibly a better signal will update in a couple days and battery light seems to be an affected slightly
Click to expand...
Click to collapse
Update for everybody with the Note 3 I don't know if it's coincidence or not after updating but when I'm in the YouTube app and have my charger connected to my phone it will say dock is connected really quick and then disappear it will probably do this two or three times a day just wanted to throw this out there and let people know that there might be a bug in the update I will check my USB port and see if it's clean and not damaged
speed_phreak said:
Thanks everyone for your continued feedback about this update. I am still clinging on to my Note 3. This is most certainly my last subsidized phone on VZW with my UDP.
In any event, I was just as shocked as you guys to see the system update notification. I went straight to Tibackup and froze the "System updates" app, which has tamed the notifications.
Click to expand...
Click to collapse
Hey Speed_Phreak - thanks for your post, I think I'm on the right track but still having some trouble. After freezing "Security Policy Updates.apk," "Samsung Updates.apk," and performing a restart, the OTA "security update" notification persists. How did you access "system update.apk?"
bprintz44 said:
Hey Speed_Phreak - thanks for your post, I think I'm on the right track but still having some trouble. After freezing "Security Policy Updates.apk," "Samsung Updates.apk," and performing a restart, the OTA "security update" notification persists. How did you access "system update.apk?"
Click to expand...
Click to collapse
Freeze "System update".. in titanium backup.
I have upgraded my A310F to Nougat but decided I don't like some things (mostly related to Dream UX or whatever the thing is called) and some minor flaws like inability to use keyboard other than Samsung one (other ones crash the Samsung Keyboard process when trying to use emoticons), also the battery management is quite poor (there is no longer a list of apps I want to be killed once I just stop using them).
Anyway - I got back to Marshmallow by simply flashing firmware via Odin (all works fine again).
But the question is... how can I stay on Marshmallow forever?
Currently I've disabled the autoupdate over wi-fi but AFAIK the update popups will keep appearing once only Nougat will be officially available in XEO region.
How can I make this permanent? Any ideas?
If you have any - be it without or with rooting - please let me know. I don't want to loose the ability to use Samsung Store.
wolfensg said:
I have upgraded my A310F to Nougat but decided I don't like some things (mostly related to Dream UX or whatever the thing is called) and some minor flaws like inability to use keyboard other than Samsung one (other ones crash the Samsung Keyboard process when trying to use emoticons), also the battery management is quite poor (there is no longer a list of apps I want to be killed once I just stop using them).
Anyway - I got back to Marshmallow by simply flashing firmware via Odin (all works fine again).
But the question is... how can I stay on Marshmallow forever?
Currently I've disabled the autoupdate over wi-fi but AFAIK the update popups will keep appearing once only Nougat will be officially available in XEO region.
How can I make this permanent? Any ideas?
If you have any - be it without or with rooting - please let me know. I don't want to loose the ability to use Samsung Store.
Click to expand...
Click to collapse
If you are root it will never update
sakat49 said:
If you are root it will never update
Click to expand...
Click to collapse
Thanks!
sakat49 said:
If you are root it will never update
Click to expand...
Click to collapse
BTW: Do you know by any chance if the content bought previously in the Themes Store will be available after rooting?
wolfensg said:
BTW: Do you know by any chance if the content bought previously in the Themes Store will be available after rooting?
Click to expand...
Click to collapse
why not?
MoshPuiu said:
why not?
Click to expand...
Click to collapse
Yup. It is there I thought that this may be related with not working Samsung Pay with rooted phone but fortunately it's not.