Database Info

Canadian Note 3 (N900W8) Knox Thread (0x0 can be maintained)

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.

[Q] root for 4.4.2

hey rooters and devs is there a stable 4.4.2 root out right now for verzion without tripping knox?
i took the update to 4.4.2 and i cant even touch mu phone since it sucks makes random noises like a dot when clicking something.
Also, when will be able to start flashing custom roms or 4.4.2. i bricked my phone like 3 times since i didnt unlock the boot loader but now i can actually flash the roms.
TL,DR root for 4.4.2 without tripping know
when will we be able to flash cyanogenmod

broazny said:
hey rooters and devs is there a stable 4.4.2 root out right now for verzion without tripping knox?
i took the update to 4.4.2 and i cant even touch mu phone since it sucks makes random noises like a dot when clicking something.
Also, when will be able to start flashing custom roms or 4.4.2. i bricked my phone like 3 times since i didnt unlock the boot loader but now i can actually flash the roms.
TL,DR root for 4.4.2 without tripping know
when will we be able to flash cyanogenmod
Click to expand...
Click to collapse
The only root exploit for VRUDNE1 4.4.2 that works on our phone is "Towelroot" by Geohot which is in the S5 section.
Once rooted, these things apply to everyone on VRUDNE1 4.4.2 as well as anyone on 4.3 VRUCML1 or VRUCNC1 OTAs:
a) You can NOT install a custom recovery (No CWM, No TWRP, nothing)
b) You can NOT install any AOSP rom
c) You can NOT install a custom kernel
d) Only an unofficial version of Safestrap can be used on VRUDNE1. This is not a custom recovery, Safestrap is NOT a custom recovery.
e) As of 8:50 EST, there is no custom VRUDNE1 TouchWiz rom to install. Safestrap hijacks the bootprocess and only uses the stock kernel, in your case stock VRUDNE1 4.4.2 kernel, in order to boot other custom TouchWiz roms. Only VRUDNE1 roms would be able to successfully flash on your phone. But none exist yet.
Literally all that you can do as of this post is root, debloat, install Safestrap, and hope that you will be able to use custom VRUDNE1 based TouchWiz roms.

back to 4.3
will i be able to odin back to 4.3 without tripping knox and locking the bootloader?
SlimSnoopOS said:
The only root exploit for VRUDNE1 4.4.2 that works on our phone is "Towelroot" by Geohot which is in the S5 section.
Once rooted, these things apply to everyone on VRUDNE1 4.4.2 as well as anyone on 4.3 VRUCML1 or VRUCNC1 OTAs:
a) You can NOT install a custom recovery (No CWM, No TWRP, nothing)
b) You can NOT install any AOSP rom
c) You can NOT install a custom kernel
d) Only an unofficial version of Safestrap can be used on VRUDNE1. This is not a custom recovery, Safestrap is NOT a custom recovery.
e) As of 8:50 EST, there is no custom VRUDNE1 TouchWiz rom to install. Safestrap hijacks the bootprocess and only uses the stock kernel, in your case stock VRUDNE1 4.4.2 kernel, in order to boot other custom TouchWiz roms. Only VRUDNE1 roms would be able to successfully flash on your phone. But none exist yet.
Literally all that you can do as of this post is root, debloat, install Safestrap, and hope that you will be able to use custom VRUDNE1 based TouchWiz roms.
Click to expand...
Click to collapse

broazny said:
will i be able to odin back to 4.3 without tripping knox and locking the bootloader?
Click to expand...
Click to collapse
No, you can not downgrade once on 4.4.2 VRUDNE1.

thank you very much, do you know when the devs will be able to find a way to downgrade or unlock the bootloader
SlimSnoopOS said:
No, you can not downgrade once on 4.4.2 VRUDNE1.
Click to expand...
Click to collapse

broazny said:
thank you very much, do you know when the devs will be able to find a way to downgrade or unlock the bootloader
Click to expand...
Click to collapse
I'll be blunt with you, I sincerely doubt that's being actively worked on for our 2 year old device. The bootloader has yet to be unlocked on the S4 which has had an active bounty with numerous devs so its not happening here. If AOSP means that much to you, sell your S3 for a bootloader unlocked S3 or get another device which has less hurdles to get AOSP.
Edit: Or you can email these guys at MobileTechVideos and see if their S3 bootloader downgrade process works on 4.4.2. It is a paid service either way, but some people have considered this when on 4.3.

SlimSnoopOS said:
I'll be blunt with you, I sincerely doubt that's being actively worked on for our 2 year old device. The bootloader has yet to be unlocked on the S4 which has had an active bounty with numerous devs so its not happening here. If AOSP means that much to you, sell your S3 for a bootloader unlocked S3 or get another device which has less hurdles to get AOSP.
Edit: Or you can email these guys at MobileTechVideos and see if their S3 bootloader downgrade process works on 4.4.2. It is a paid service either way, but some people have considered this when on 4.3.
Click to expand...
Click to collapse
Is there any successes to this downgrade of the bootloader of the link that you sent? I'm not on a s4 I'm on a SCH-I535 sgs3 same as s4 if I'm correct.. Correct me if I'm wrong s4 and s3 have a lot of the same stuff

jcbjoe said:
Is there any successes to this downgrade of the bootloader of the link that you sent? I'm not on a s4 I'm on a SCH-I535 sgs3 same as s4 if I'm correct.. Correct me if I'm wrong s4 and s3 have a lot of the same stuff
Click to expand...
Click to collapse
I haven't seen anyone report back on having used this. I figured someone would have done so and posted on xda but, nothing. That link is for the Verizon S3 btw. The S4 was mentioned just for comparison purposes only.
Sent from my SCH-I535 using Tapatalk 4

SlimSnoopOS said:
I haven't seen anyone report back on having used this. I figured someone would have done so and posted on xda but, nothing. That link is for the Verizon S3 btw. The S4 was mentioned just for comparison purposes only.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I originally saw it on XDA. Josh inadvertently reverted one while doing a JTag service. He was able to reproduce it several times in testing. Most don't even know about it till they brick their device and need JTag service.

Galaxy S6 5.1.1 root

Hi,my galaxy s6 is on version 5.1.1 with the G920FXXU2BOGG firmware and I want to root it but don't know the right method.I know that there is already a method on how to root galaxy s6 on 5.1.1 but does it support my firmware?because it is made to root the first 5.1.1 firmware or it supports all galaxy s6 5.1.1 firmwares?

hlm19 said:
Hi,my galaxy s6 is on version 5.1.1 with the G920FXXU2BOGG firmware and I want to root it but don't know the right method.I know that there is already a method on how to root galaxy s6 on 5.1.1 but does it support my firmware?because it is made to root the first 5.1.1 firmware or it supports all galaxy s6 5.1.1 firmwares?
Click to expand...
Click to collapse
Only way to get root on 5.1.1 thus far is by flashing TWRP recovery.
If you are an amateur to this sort of thing I would highly suggest not to do that.
It will void your warranty permanently by tripping KNOX which can't be "un-tripped"
May I ask why you think you need/want root?

I want to root my galaxy s6 as I see some good custom roms and want to try them.I've had some android phones before like the galaxy note 4,galaxy note 3,htc one m8 and galaxy nexus and rooted them.Just curious on how to root my gs6 with the XXU2BOGG firmware.Does the 5.1.1 root method supports my firmware?

hlm19 said:
I wan't to root my galaxy s6 as I see some good custom roms and want to try them.I've had some android phones before like the galaxy note 4,galaxy note 3,htc one m8 and galaxy nexus and rooted them.Just curious on how to root my gs6 with the XXU2BOGG firmware.Does the 5.1.1 root method supports my firmware?
Click to expand...
Click to collapse
Okay then, as long as you aware of the risks..
Rooting isn't device dependent, it's just software. It's supported on any firmware as long as you have TWRP installed. It just installs SuperSU for you into the system files.
http://forum.xda-developers.com/galaxy-s6/orig-development/twrp-t3080940
Pretty sure TWRP is supported on all models of S6/Edge, they all share the same hardware as each other.
Just flash it with Odin version 3.10.6.
Grab it here ZeroFLTE represents all S6 models except Sprint model which require their own special one (no idea why)
You then follow the Odin install method, making sure you're using 3.10.6. Otherwise more than likely will not work.
After installation of TWRP and then booting into TWRP you will be faced with the "SuperSU is not installed, would you like to install it?"
.. And done.
Er, actually I think that appears when when you go to restart via TWRP menu
But yeah.. best of luck, don't blame me if your phone explodes into a fire ball that goes nuclear and destroys the world.. Or simply bricks it
Edit: Wait are you talking about the Chainfire root method? If you are you may as well not even consider that if you're planning on custom firmware installs.. TWRP is your best bet because it isn't device/firmware specific like CF. And you need TWRP for firmware installs anyway..

Stevles said:
Okay then, as long as you aware of the risks..
Rooting isn't device dependent, it's just software. It's supported on any firmware as long as you have TWRP installed. It just installs SuperSU for you into the system files.
http://forum.xda-developers.com/galaxy-s6/orig-development/twrp-t3080940
Pretty sure TWRP is supported on all models of S6/Edge, they all share the same hardware as each other.
Just flash it with Odin version 3.10.6.
Grab it here ZeroFLTE represents all S6 models except Sprint model which require their own special one (no idea why)
You then follow the Odin install method, making sure you're using 3.10.6. Otherwise more than likely will not work.
After installation of TWRP and then booting into TWRP you will be faced with the "SuperSU is not installed, would you like to install it?"
.. And done.
Er, actually I think that appears when when you go to restart via TWRP menu
But yeah.. best of luck, don't blame me if your phone explodes into a fire ball that goes nuclear and destroys the world.. Or simply bricks it
Edit: Wait are you talking about the Chainfire root method? If you are you may as well not even consider that if you're planning on custom firmware installs.. TWRP is your best bet because it isn't device/firmware specific like CF. And you need TWRP for firmware installs anyway..
Click to expand...
Click to collapse
Thanks mate!So twrp now supports 5.1.1?

Welcome! TWRP has supported 5.1.1 since the latest version: 2.8.7.1. Change log is in the second post here. Take care and have fun

Stevles said:
Welcome! TWRP has supported 5.1.1 since the latest version: 2.8.7.1. Change log is in the second post here. Take care and have fun
Click to expand...
Click to collapse
Thanks again!But I thought the only way to root the gs6 with 5.1.1 is by using the unikernel something?as 5.1.1 is different than 5.0.2.

hlm19 said:
Thanks again!But I thought the only way to root the gs6 with 5.1.1 is by using the unikernel something?as 5.1.1 is different than 5.0.2.
Click to expand...
Click to collapse
Not sure about that.. Perhaps install unikernal first just to be sure
Okay so go to the last page or two of the TWRP thread and start reading

Stevles said:
Not sure about that.. Perhaps install unikernal first just to be sure
Click to expand...
Click to collapse
Yeah,just checked and have to flash unikernel first and then the twrp via odin.If I root using this twrp method,it supports my 5.1.1 firmware right?Sorry for lots of asking.

hlm19 said:
Yeah,just checked and have to flash unikernel first and then the twrp via odin.If I root using this twrp method,it supports my 5.1.1 firmware right?Sorry for lots of asking.
Click to expand...
Click to collapse
Assuming it doesn't boot loop with unikernel (all reports say it's fine) then yeah you won't have any dramas with root via TWRP.. Like I said it's just software, the boot loop comes from Samsung being slippery Gypsies and modifying their kernels to basically stop people from modifying system partitions. Hence the need for a custom kernel to bypass that crap. You'll be fine

Stevles said:
Assuming it doesn't boot loop with unikernel (all reports say it's fine) then yeah you won't have any dramas with root via TWRP.. Like I said it's just software, the boot loop comes from Samsung being slippery Gypsies and modifying their kernels to basically stop people from modifying system partitions. Hence the need for a custom kernel to bypass that crap. You'll be fine
Click to expand...
Click to collapse
Yeah,and if I need to unroot it,I do just flash the official firmware via odin?

hlm19 said:
Yeah,and if I need to unroot it,I do just flash the official firmware via odin?
Click to expand...
Click to collapse
Sorry for delayed response.. Yes flashing a firmware tar. md5 will reset the system partition back to full stock and replace the recovery, kernel, modem etc.
Just download one corresponding to your device ie.. SM-G92XX where the first X is either a 5 or 0 and the second is the country or region the phone was intended for. I keep the latest firmware for my device and country (not carrier because it has too much bloatware) around at all times to undo any screw ups and start again

Stevles said:
Sorry for delayed response.. Yes flashing a firmware tar. md5 will reset the system partition back to full stock and replace the recovery, kernel, modem etc.
Just download one corresponding to your device ie.. SM-G92XX where the first X is either a 5 or 0 and the second is the country or region the phone was intended for. I keep the latest firmware for my device and country (not carrier because it has too much bloatware) around at all times to undo any screw ups and start again
Click to expand...
Click to collapse
Thanks for the help!Will try it

Try this:
http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395

roydok said:
Try this:
http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Click to expand...
Click to collapse
I think he may have already actually, thanks for your input. It was certainly mentioned earlier but now there's a link which is always nice

What does tripping KNOX do? I like and would like to continue using the Tap & Pay feature from my bank. Is KNOX separate from the secure element the bank uses?
Other than providing a separate environment for work, what else does KNOX provide?

Galaxy S3 Verizon ROOT ROM ETC worth it or NAH

Model #: SCH-I535
Android Version: 4.4.2
Baseband version: I535OYUDNE1
Kernel version: 3.4.0 (May 20, 2014 KST)
Build number: KOT49H.I535VRUDNE1
SE for Android status: Enforcing SEPF_SCH-I535_4.4.2_0016
Hardware version: I535.10
So i just got this S3 for really darn cheap in great shape. I figured i wanted to root and use custom recovery and then maybe try some new roms. But it comes to my attention through like all the helpful tutorials that the bootloader is locked and there is almost zero guarentee that even the one that have done this will work without many issuses. so im just seeing if anyone thinks its worth it to try with this phone or look else where and deal with 4.4.2

Of course its always worth getting rid of all the bloatware ! I have a galaxy S3 rooted with the liquid smooth ROM and love it .
The bootloader is not locked I had to root it and remove the battery on reboot in order to pass it or it will try to reload back to default also took a few times .

I would say it is worth it to root. From there your choices are limited since you are on 4.4.2 with the NE1 bootloader.
I bought such a device in May, proceeded to root, install SafeStrap, and then flashed the SuperLiteROM.
NOTE, there are only three ROMs safe to use on an i535 with the NE1 bootloader.
DO NOT try to flash a custom recover such as CWM or TWRP.
to quote myself from another thread:
I picked up a used i535 a few months ago as a device to mod and learn. I had no intentions of using it as my daily phone - I'm on AT&T with an i747. I found it was already on the NE1 bootloader and modem, I hadn't read enough before purchasing.
I was able to root it with TowelRoot. Following that I installed BusyBox and then installed SafeStrap Recovery for devices with the NE1 bootloader, see here.
From what I have seen there are three ROMs available to this device on NE1; stock NE1, SuperLiteROM, and Paul Pizz. This thread is a good resource for all but Paul Pizz, which is here. I after installing SafeStrap I flashed SuperLiteROM to the stock slot, it seems to avoid some issues when flashed here instead of a secondary slot. Since then I have installed XPosed framework and have several mods working with no issues.
Click to expand...
Click to collapse
The XPosed module I spent the most time tinkering with was XPrivacy.

SM-G930T with G930TUVS9CSC1 Firmware, are there custom roms? Have any rom sugestions?

So I just got T-Mobile Galaxy S7 from ebay. Unfortunately the owner kept it up to date or updated it before sending it out. I'm coming across conflicting information on custom roms. I've found instructions on rooting, and have had success. Before i go in to detail on what ive learned so far, is it even possible to flash custom roms with the v9 bootloader? Can I use roms intended for the exynos variants of the SM-G930? Like lineage-herolte. Am I stuck with the T-Mobile rom?

I'm in the same boat; bought it from eBay with the most recent firmware and I'm looking for a root/flash method.

here is a root method that worked for me.
https://forum.xda-developers.com/tm...ow-to-root-samsung-galaxy-s7-flat-sm-t3930328
Im waiting on a SM-G930U from verizon to come in the mail before I start blindly flashing to the SM-G930T. I don't want to brick my only phone. I'll updated once ive tried.

Thanks! Have you noticed any issues after rooting? I've heard heat is one of them.

I didnt leave it rooted. I didn't see the point without a rom to put on it, so I reflashed stock T-Moble G930TUVS9CSC1 with odin.

Any update with flashing that custom ROM?

Flashing boot files
Hi just letting you know Be careful I flashed ENG-boot files going around and bricked a my 1st g930vl because it had a U9 boot loader.
I see one or two actuall post but no twrp, so once it gets wiped than it's time to get a new phone.