There are users here in Canada with Note 3's that have "Custom" in "Current Bianary" and "System Status".
This information has not been posted, I have NO idea why. I am guessing these people could care less about us (the people still in the dark).
I have only just obtained a Note 3 (Week ago) and I am trying to figure this stuff out.
We have a special Note 3 in our N900W8's. Apparently we can:
- Downgrade from 4.4.2 to 4.3 via Odin 3.09 without tripping Knox (not sure if this requires the Mexican bootloader first or if we can do it with our Canadian bootloaders)
- Keep Knox at 0x0 with Custom Everything else. From what I see, our bootloaders are unlocked allowing us to flash our phones in Odin with multiple files (not 1 file mode as this contains a bootloader) as long as we dont include the bootloader (theory from what I have seen, and read a few times, no confirmation).
However I can not get an answer out of anyone who knows anything. I cannot just blindly flash and see if Knox is tripped, I'll only get one shot. Not worth it IMO.
Can anyone chime in on this? Is it acceptable to call members out? I know exactly who the 2 people are that have Custom everything and Knox at 0x0. 2 Torontonians, younger guys, doesn't seem like they want to talk though. Can I call them in here, is that acceptable behavior? Never done that before. Hehe.
I can confirm. I used this method:
http://forum.xda-developers.com/showthread.php?t=2614772
I have a Rogers Note 3 with CWM installed and rooted with Knox at 0x0. My friend just updated his Note 3 to kit Kat (through kies) and rooted using cf-autoroot and his knox is 0x0. I haven't tried downgrading so I cannot comment on that.
I am planning to flash the official Rogers rom shortly and then root (not sure about installing a custom recovery yet) I will report back when completed.
I PM'd you but yeah, I'm Knox 0x0 on X-Note 12 right now. Sorry about that, wasn't home.
kiru said:
I can confirm. I used this method:
http://forum.xda-developers.com/showthread.php?t=2614772
I have a Rogers Note 3 with CWM installed and rooted with Knox at 0x0. My friend just updated his Note 3 to kit Kat (through kies) and rooted using cf-autoroot and his knox is 0x0. I haven't tried downgrading so I cannot comment on that.
I am planning to flash the official Rogers rom shortly and then root (not sure about installing a custom recovery yet) I will report back when completed.
Click to expand...
Click to collapse
That link notes that installing a custom recovery will trip knox. Could you please verify what you did to install custom recovery and still maintain knox 0x0? Will be very interested in your follow-up.
kiru said:
I can confirm. I used this method:
http://forum.xda-developers.com/showthread.php?t=2614772
I have a Rogers Note 3 with CWM installed and rooted with Knox at 0x0. My friend just updated his Note 3 to kit Kat (through kies) and rooted using cf-autoroot and his knox is 0x0. I haven't tried downgrading so I cannot comment on that.
I am planning to flash the official Rogers rom shortly and then root (not sure about installing a custom recovery yet) I will report back when completed.
Click to expand...
Click to collapse
Could you also PM me the procedure? Knox is really bugging me and TW is bloated with too many craps. X-Note looks awesome! Thanks !
bingbinghaha said:
Could you also PM me the procedure? Knox is really bugging me and TW is bloated with too many craps. X-Note looks awesome! Thanks !
Click to expand...
Click to collapse
Actually, I would be interested too. Any chance of posting the procedue instead of PM to multiple users? If not, please PM me as well
I followed the guide in the link I posted as it is pretty detailed already. I have root and cwm recovery installed with Knox at 0x0.
kiru said:
I followed the guide in the link I posted as it is pretty detailed already. I have root and cwm recovery installed with Knox at 0x0.
Click to expand...
Click to collapse
Second that.
---------- Post added at 12:55 AM ---------- Previous post was at 12:38 AM ----------
Okay here. https://www.youtube.com/watch?v=Tks73wZH3qg&list=UU2FLZg9YNAr4YAd0VEDDKGQ
You have to pause to see it at the beginning, and in hindsight, I probably have should of started in CWM, then booted into recovery, but whatever.
Set it to HD and pause it at the beginning, you can see my Knox 0x0. Then watch the video and I boot into the ROM, then back into CWM, all in one cut.
Cheers.
Same here
Knox 0x0 here, after a few good reasons to trip it
Android newcomer here.
I have a Bell Canada SM-N900W8, and it came with 4.3. Rooted 4.3 with Kingo (noob style) and that was just perfect to start out. Then the OTA came out. I unrooted the device, reseted with Kies 3 update to 4.4.2 and then Kingo wasn't working anymore of course.
At that point I decided I didn't care about tripping knox and installed TWRP to start trying roms... Tried like 2-3 1+gb complete packed roms (bootloops, probably cauz im a noob) then I wiped from TWRP, restored my OTA backup, flashed with CF-Auto-Root international version (canadian is another bootloop) and then flashed a CivZ kernel +stock-modification rom that I now simply keep clean with Titanium Backup and some apps y'all know about.
Some more info :
My version is VLUCNB7
My current kernel [email protected]
My current SE state is Permissive
Again, Knox is 0x0. Even after bootloops of custom crap that was crashing and I'm custom-rom, custom-kernel.
Two facts to finish that off
1) That's weird
2) I'm a lucky *****
Have a great day
What if I want to use a custom 4.3 ROM (just to get BT Tethering) without tripping KNOX?
The guides seems to push you to install the 4.4 ROMs.
I have the Bell version of N900W8.
Started at MI5, rooted de la vega, then wanted to upgrade to 4.4.2.
Used polishpats way of upgrading with the leaked 4.4.2, flashed all the AP,CSC,CP,PIT, then installed TWRP and autorooted, both with Odin 3.09 - no knox trip
Wanted to try X-note, installed it using TWRP, and no knox trip
Upgraded the kernel using TWRP, no knox trip
Did not like X-note, wanted to go back to 4.4.2, and reflashed it - no knox trip
Downgraded back to 4.3, no knox trip
upgraded to offical 4.4.2, no knox trip
rooted via chainfire and odin - no knox trip
now sitting at rooted 4.4.2 with 0x0 still
Are you basically saying Bell's N900W8 is KNOX untripable?
I'm on MJ4 (UDLV Rooted) with remaining with MJ1 Bootloader
Since I don't want a KITKAT rom, can I just install a custom recovery (TWRP) without doing all that Mexican instruction stuff?
I really just want a 4.3 ROM with BT Tethering.
klau1 said:
Are you basically saying Bell's N900W8 is KNOX untripable?
I'm on MJ4 (UDLV Rooted) with remaining with MJ1 Bootloader
Since I don't want a KITKAT rom, can I just install a custom recovery (TWRP) without doing all that Mexican instruction stuff?
I really just want a 4.3 ROM with BT Tethering.
Click to expand...
Click to collapse
Hello,
My friend has just the same phone as me, he bought it a few weeks before me, and he used his own techniques and got 0x1 knox tripped, so I just can't warn you enough : not all N900W8 are "untrippable"
...but...I didn't trip mine and I'm not alone.
Without more information you can't just say canadian w8's are untrippable, cauz they are.
Well, are older the better?
I got mine the first week it came out.
klau1 said:
Well, are older the better?
I got mine the first week it came out.
Click to expand...
Click to collapse
I doubt it.
Will look into this. I am positive all N900W8's are the same.
Surely your friend missed something or did something improperly to trip Knox.
Taking this all in. Thanks for the posts guys!
@nexxusty
in your opinion, do you have to go thru installing KITKAT rom from Mexico if you just want to install another 4.3 ROM that has BT Tethering without tripping KNOX?
klau1 said:
@nexxusty
in your opinion, do you have to go thru installing KITKAT rom from Mexico if you just want to install another 4.3 ROM that has BT Tethering without tripping KNOX?
Click to expand...
Click to collapse
Klau you took the question right out of my head brother. LOL.
I am not sure... this also pains me as I want to try CF-auto Root right now on 4.4.2 Rogers.
From my knowledge of technology, I dont think it will. Not positive though. I am hoping you do not need to flash this.
I will test for us. Here is hoping I wont lose my warranty. Will report back.
nexxusty said:
Klau you took the question right out of my head brother. LOL.
I am not sure... this also pains me as I want to try CF-auto Root right now on 4.4.2 Rogers.
From my knowledge of technology, I dont think it will. Not positive though. I am hoping you do not need to flash this.
I will test for us. Here is hoping I wont lose my warranty. Will report back.
Click to expand...
Click to collapse
Flashed CF-Auto-Root, flashed TWRP 2.6.3.0, 0x0 still!
Now for the info on my phone.
I have done as follows.
Phone came with 4.3 stock --> Root De La Vega --> Flashed 4.4.2 Stock (Rogers) with Odin 3.09 --> CF Auto-Root --> TWRP 2.6.3.0 = Rooted 4.4.2 with TWRP 2.6.3.0 Recovery and Knox @ 0x0.
I'm not stopping here. Will flash everything DrawntoLife has.
Appreciated my man. Thanks again! Easy to Follow Step By Step Tutorial **WILL** be written tonight after I am done at a LAN I am already late for figuring this out.
Talk soon everyone! Happy flashing!
did you consider extracting the ODIN package and leave out the Bootloader?
Remember we had to do that upgrading from MJ1 to MJ4. Reportedly, it was the newer bootloaders that trip KNOX.
klau1 said:
did you consider extracting the ODIN package and leave out the Bootloader?
Remember we had to do that upgrading from MJ1 to MJ4. Reportedly, it was the newer bootloaders that trip KNOX.
Click to expand...
Click to collapse
When I updated to 4.4.2? I did, but I was not sure if that would trip Knox so I left it in the package.
It's irrelevant now anyway, the bootloader in 4.4.2 Rogers is the one I am on now and allowing me to do all this still.
I suggest you update to it. Use the package labeled "N900W8VLUCNB7_N900W8OYACNB7_RWC". That is 4.4.2 for a Rogers Note 3.
I can safely assume you can flash this at any point and be fine. Even if you are already on a hacked 4.4.2 or something. There would be no issue updating the bootloader to the same version, would just overwrite it.
Hi,
I am really tempted to root my work phone and I am totally digging these Temporary Root methods like TowelRoot and KingRoot where the root is lost upon reboot. I haven't been able to find a clear answer and I figured i'd ask here.
Can someone tell me if these methods trips the KNOX warranty counter? I have a Note 4 and like I said, it's a work phone and I wouldn't want any issues down the road if I left the company or whatever.
I would be open to hearing if there are permanent root methods that don't trip KNOX as well for the Note 4.
Thx in advance.
I found this older thread:
http://forum.xda-developers.com/showthread.php?t=2499546&page=2
Where they are saying it doesn't trip knox, but I'm not sure about now in 2015.
rizz2pro said:
I found this older thread:
http://forum.xda-developers.com/showthread.php?t=2499546&page=2
Where they are saying it doesn't trip knox, but I'm not sure about now in 2015.
Click to expand...
Click to collapse
That thread is for Note 3.
By the way, Latest Kingroot doesn't trip the Knox.
Anyway, you could ask it in the Note 4 Forum here.
I'm new to Samsung devices and apparently that Knox efuse is a real SOB to deal with. I don't need custom recoveries/kernels or anything fancy, just want to be able to use superuser.
I know there's at least *a* root exploit for the S7, but I'm sure it also blows the efuse. Is there a "systemless root" or anything like what the S5/S6 had that doesn't trip knox?
your question can be answered with a 5 minute search but no. bootloader is locked, system is verified on boot
I thought that's what the point of non-system root was though? So that you aren't modifying system
There is no way to root without tripping Knox (the 0x1 Warranty Void flag). This has been the case since the eFuse was introduced (at least back on the Note 3).
Sent from my SM-G930W8 using Tapatalk
---------- Post added at 10:49 PM ---------- Previous post was at 10:46 PM ----------
123421342 said:
your question can be answered with a 5 minute search but no. bootloader is locked, system is verified on boot
Click to expand...
Click to collapse
That's for Snapdragon 820 units. We don't know if the OP has Snapdragon or Exynos
Sent from my SM-G930W8 using Tapatalk
I don't have my S7 yet, but I was going to get one soon. How would I find out if it's Snapdragon or Exynos once I get one?
I swear I saw some threads about S6 rooting without tripping Knox...
drfsupercenter said:
I don't have my S7 yet, but I was going to get one soon. How would I find out if it's Snapdragon or Exynos once I get one?
I swear I saw some threads about S6 rooting without tripping Knox...
Click to expand...
Click to collapse
If you buy a US version, it should be snapdragon. The international/non-US version is the Exynos.
Ah, OK. Well I'm in the US so that answers that.
I would not risk it for the biscuit
http://pingpongroot.co/PingPongRoot-tutorial.html
This is the thing I was talking about. It works for the S6/S6 Edge, so why can't we do this on S7?
Something I was thinking about... Knox basically verifies the checksum of the system partition upon booting, right? Well, there are system updates (I had two of them after turning the phone on the first time) and those obviously modify the system partition. Which means the checksum has to be updated during that process or it would trip Knox just for doing an OTA update! So the million-dollar question is, couldn't we just spoof that ourselves?
And more importantly, why wouldn't "systemless root" do the trick? I can understand tripping Knox if you start deleting things from /system using your new root powers, but what about just using it to modify data? That's one of the main things I use root for, backing up and restoring data, which is a totally separate partition from /system.
Rooting Without Voiding Warranty [Samsung Galaxy s7] DEFINITELY POSSIBLE
drfsupercenter said:
I'm new to Samsung devices and apparently that Knox efuse is a real SOB to deal with. I don't need custom recoveries/kernels or anything fancy, just want to be able to use superuser.
I know there's at least *a* root exploit for the S7, but I'm sure it also blows the efuse. Is there a "systemless root" or anything like what the S5/S6 had that doesn't trip knox?
Click to expand...
Click to collapse
There most certainly is a very easy way to root the Samsung galaxy s7 snapdragon to use superSU.
I did it on my sprint Samsung galaxy s7 very easily and sprint is supposed to make it the
hardest.
http://forum.xda-developers.com/galaxy-s7/how-to/samsung-galaxy-s7-sm-g930p-root-xposed-t3502829
I did this like a month ago, but ended up undoing it thanks to Pokémon Go and SafetyNet. If you know a solution let me know...
drfsupercenter said:
I'm new to Samsung devices and apparently that Knox efuse is a real SOB to deal with. I don't need custom recoveries/kernels or anything fancy, just want to be able to use superuser.
I know there's at least *a* root exploit for the S7, but I'm sure it also blows the efuse. Is there a "systemless root" or anything like what the S5/S6 had that doesn't trip knox?
Click to expand...
Click to collapse
Complete guide to root without voiding warranty!
http://forum.xda-developers.com/galaxy-s7/how-to/samsung-galaxy-s7-sm-g930p-root-xposed-t3502829
Hey guys
I recently acquired my S6 . I was wondering if someone could instruct me on how to root it? I don't mind tripping Knox or voiding warranty. I found rooting instructions but I'm not sure they work on my build and I don't want to mess up my phone. Please assist me in rooting. Build details are in screens hot below
I have the same problem. The current how-to is so outdated that i don't dare to root my phone using that.
And yes those builds complicate things.
same here I wanna root my S6 marshmallow without tripping KNOX
If you don't mind tripping KNOX the root is pretty simple. Just flash this file by Chainfire with Odin and you are done. However you can't root without tripping KNOX.
http://www.mediafire.com/download/2wy5hj88ua9a8fz/CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar.md5