Related
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)
When I had my S3 and other Samsung devices, I could jump back and forth between updates.
Which was cool and all.
But when I flashed an S4 Mini, KNOX got tripped on it.
I flashed a NEWER firmware to it, and it was from sammobile.
Others also complained about having this issue.
But what about the Note 4?
I have a 910C, and I love the phone. On wifi, battery life is beastly.
But it seems Samsung did not patch the mobile data issue (like LG did), and if I get on mobile internet, my battery is ded.
So... would a downgrade trip KNOX?
h8Aramex said:
When I had my S3 and other Samsung devices, I could jump back and forth between updates.
Which was cool and all.
But when I flashed an S4 Mini, KNOX got tripped on it.
I flashed a NEWER firmware to it, and it was from sammobile.
Others also complained about having this issue.
But what about the Note 4?
I have a 910C, and I love the phone. On wifi, battery life is beastly.
But it seems Samsung did not patch the mobile data issue (like LG did), and if I get on mobile internet, my battery is ded.
So... would a downgrade trip KNOX?
Click to expand...
Click to collapse
KNOX shouldn't get tripped if you flash an official Samsung firmware.
Ashatar said:
KNOX shouldn't get tripped if you flash an official Samsung firmware.
Click to expand...
Click to collapse
That's what I thought too, but after that trip... well, I have my fears.
It is a company phone, which came with 2 years of warranty.
Well, I will cross my fingers and hope for the best.
There is no way I can use the phone like this abroad, on the road, on the field. (With such terrible battery on LP.)
h8Aramex said:
That's what I thought too, but after that trip... well, I have my fears.
It is a company phone, which came with 2 years of warranty.
Well, I will cross my fingers and hope for the best.
There is no way I can use the phone like this abroad, on the road, on the field. (With such terrible battery on LP.)
Click to expand...
Click to collapse
Good luck!
Ashatar said:
Good luck!
Click to expand...
Click to collapse
It works. You can downgrade, upgrade.
BUT, you cannot downgrade permanently.
Because the phone WILL check for updates (no matter what you try, or do) and WILL download the new firmware.
Is there a way to root without tripping KNOX? (the 4.4.4 firmware of course, so I can keep the update away.)
Okay I had an idea.
I will download the older version (one older than 4.4.4 latest), and then do this sim card / wifi trick.
It will notice the update and download it once Wifi is on, but should ignore L after the reboot.
What do you guys think?
(Shame it takes forever to download anything from sammobile.)
Okay, its' really weird.
The old version works. (latest 4.4.4 - 1 version)
You can install it, disable update checks, and you are good.
BUT! Once you update to the latest 4.4.4 from OTA - 4.4.4 will instantly download 5.0 after the boot.
Even if you disabled auto-update from way back.
It's basically in the system to force check an update as soon as there is ANY data connection,
and download it once there is a wifi connection available. (unless you untick wifi only.)
Once it downloads, there is no going back.
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
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.
Sorry if i sound like a noob.
As we all know multi touch bug still exist in Max pro m1 as of now on 311(latest update).
Shivam kumar jha developed a custom rom for our phone AOSP Extended back when Device was just launched and somehow this multi touch bug was solved in it.
So my question is, is it possible for developers to somehow solve the multi touch bug on stock rom in same way it was solved on AEX?
June Security Patch update will, hopefully, fix it. It is expected soon.
If you are impatient, one needs to root their device to be able to take steps that fix multi touch bug on stock rom. Requires Magisk or editing a system file to 'fix' the bug. Rooting your device effectively voids its warranty.
Consider your options.
It will be fix in next update
Also can we expect camera2api in next update?
Baconoid said:
June Security Patch update will, hopefully, fix it. It is expected soon.
If you are impatient, one needs to root their device to be able to take steps that fix multi touch bug on stock rom. Requires Magisk or editing a system file to 'fix' the bug. Rooting your device effectively voids its warranty.
Consider your options.
Click to expand...
Click to collapse
Man, i am waiting for june security update since the day i bought the phone
BTW i am rooted and using Nitrogen OS as of now.
mayank.. said:
It will be fix in next update
Also can we expect camera2api in next update?
Click to expand...
Click to collapse
Not sure about camera2api.
But there are ways to achieve it and it requires root.
DarkLord007 said:
Not sure about camera2api.
But there are ways to achieve it and it requires root.
Click to expand...
Click to collapse
I know just hope for camera2api
DarkLord007 said:
Man, i am waiting for june security update since the day i bought the phone
BTW i am rooted and using Nitrogen OS as of now.
Click to expand...
Click to collapse
Hi bro..I recently bought the device. You said you are on Nitrogen OS right now.
My doubt is, if you wanna get back to official stock ROM, then, will your device get OTA updates released by Asus?? And, are you sure about it??
Please reply to this. Thanks in advance.
AbhinavO said:
Hi bro..I recently bought the device. You said you are on Nitrogen OS right now.
My doubt is, if you wanna get back to official stock ROM, then, will your device get OTA updates released by Asus?? And, are you sure about it??
Please reply to this. Thanks in advance.
Click to expand...
Click to collapse
Yes. But It requires RELOCKING your bootloader even after you revert to stock.(in case you revert using twrp backup.)
After unlocking bootloader *UNOFFICIALLY* if you want, you can relock it and enable OTA again.
Unlocking with *OFFICIAL* tool will BREAK your OTA permanently.
You can Use this guide to revert back to stock with ota enabled.
https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
Note:-This Guide tells you to flash stock rom through fastboot method.
The only version of stock rom that is flasbable through fastboot is 247.
The latest 311 and older 309 & 305 cannot be flashed from fastboot.