yashsingh1/xdaforums huggingface dataset:
[T-Mobile Galaxy Note 4 General] chodaboy19:
Yes, you need to reflash DOK2 via ODIN. Then via ODIN flash CF-Root. Then flash TWRP via ODIN. :(

Some more info:

http://xdaforums.com/showpost.php?p=63816659&postcount=2769
[T-Mobile Galaxy Note 4 General] mickeycobra04:
thanks man, one more question, if we are dok2, we can skip the first 3 steps, right? following the link below, sorry man such a noob right now just got home from being active duty. was so used to just rooting getting installing new roms! lol

http://xdaforums.com/note-4-tmobile/general/dok2-5-1-1-setup-t3272388
[T-Mobile Galaxy Note 4 General] chodaboy19:
Did you already flash "systemless root"? If so, then you need to start from step #3 and reflash DOK2 again to overwrite the boot.img.

Once you have re-flashed DOK2, then follow this guide and you will have CF-Rooted DOK2:

http://xdaforums.com/note-4-tmobile/general/easy-steps-stock-odin-n910tuvu1anih-cf-t2903733

:good:
[T-Mobile Galaxy Note 4 General] mickeycobra04:
Well no, I'm already on DOK2, I'm just trying to get any sort of root unless there is a method to obtain a full root. From what I've read, there is no such thing as full root after the new update?
[T-Mobile Galaxy Note 4 General] chodaboy19:
If you haven't rooted DOK2 at all then follow the original guide, the recently released CF-Root should give you full root.

http://xdaforums.com/note-4-tmobile/general/easy-steps-stock-odin-n910tuvu1anih-cf-t2903733

most recent CF-Root: https://download.chainfire.eu/571/CF-Root/CF-Auto-Root/CF-Auto-Root-trltetmo-trltetmo-smn910t.zip

You no longer need to use the experimental "systemless root".
[T-Mobile Galaxy Note 4 General] mickeycobra04:
im on original ota 5.1.1 update but that post doesnt say much about DOK2. Should i still follow through the steps and follow with the updated version?
[T-Mobile Galaxy Note 4 General] rmdeathwish:
I am also interested in this, same situation.

Can someone please help?
[T-Mobile Galaxy Note 4 General] ShrekOpher:
If your on DOK2 and it's running well just ODIN flash TWRP and flash the SuperSu.Zip in twrp. No need for auto root.
[T-Mobile Galaxy Note 4 General] mickeycobra04:
Can we Odin flash TWRP if we have no sort of root, just off a stock firmware?
[T-Mobile Galaxy Note 4 General] mrhaley30705:
You can flash it without root, as Odin will just overwrite what's there. It will trip the Knox counter, so be warned if you use any of the Knox features.
[T-Mobile Galaxy Note 4 General] ShrekOpher:
If you have never rooted your phone, using the updated CF Auto root for DOK2 might be the easiest way to get stock 5.1.1 with root.
[T-Mobile Galaxy Note 4 General] sling:
Yep that's the easiest way to get it done thanks for heads up just rooted
[T-Mobile Galaxy Note 4 General] LoopDoGG79:
Ive tried using rooting my phone using this. I wiped all data, Odined the stock 5.1.1. Ive followed all the steps. It has several times resulted in my phone having random freeze ups and reboots. On occasion it reboots into download mode, and says "Could not boot normally" and a MMC read error happened. I removed my SD card, but this still occurs. I used Chainfires 2.65 SU beta. Anybody get this level of instability after flashing it?
[T-Mobile Galaxy Note 4 General] chodaboy19:
http://xdaforums.com/note-4-tmobile/help/fix-mmcfailed-internal-memory-yes-t3277144

Might help you.
[T-Mobile Galaxy Note 4 General] mikemoney:
:confused:will root app delete be able to fully remove junk apps and any app I dont want if I use CF auto root. Thx
[T-Mobile Galaxy Note 4 General] ShrekOpher:
No systemless root does not allow for system app removal, you will have run a debloater script to remove system apps.
[T-Mobile Galaxy Note 4 General] mikemoney:
thanks:(
[T-Mobile Galaxy Note 4 General] sling:
I'm 24 hours into using Chainfire auto root having no issue.

My device was 5.1.1 OTA stock
[T-Mobile Galaxy Note 4 General] LoopDoGG79:
I didn't use auto root. I was told it might break Android pay. I only flashed the SU 2.65 beta

I have to add, it looks like the act of Odin flashing the latest 5.1.1 ROM on the note 4, (Mine is the SM - N910T) possibly corrupted my internal partition. At times it boots to download mode, indicating it cant boot and I have a bad mmc. Now, I've been running pure stock DOK2. (No root, stock recovery) while I'm still getting freeze ups and reboots, it's less then when I was systemless root.
[T-Mobile Galaxy Note 4 General] rajil.s:
Does android pay work with systemless root?
[T-Mobile Galaxy Note 4 General] LoopDoGG79:
Yes. I did not use auto root, just the latest SU Beta
[T-Mobile Galaxy Note 4 General] ShrekOpher:
Version 2.66 updated in the chainfire thread DO NOT FLASH IT. It looks like its got a bug that for some reason is killing the cell signal on our Device. I will report it back to the thread and keep you updated when a new safe version is available.

FOR NOW ONLY FLASH 2.65
[T-Mobile Galaxy Note 4 General] ShrekOpher:
Just as a quick update.

ChainFire reached out to get some feedback on why SuperSu 2.66 beta was causing the list IMEI bug. I provided him with a log today. I'll let everyone know when the issue is resolved in future updates. For now just stick with 2.65.

Thanks
[T-Mobile Galaxy Note 4 General] _kevn_:
[MENTION=5264497]ShrekOpher[/MENTION] , which version of android pay do you have? I just went through odin flashing stock 5.1.1 > twrp > supersu 2.65 and android pay is telling me i'm not compatible... just curious if it's been patched already with the latest version from the play store.
[T-Mobile Galaxy Note 4 General] ShrekOpher:
Android Pay got an update at the end of last week. I have not had the opportunity to test using tap and pay on the new version of the app. From what I can see so far the cards I already had setup are not being deactivated. Once I have a chance to see if Android Pay will still work I will report back.

Has anyone else been able to use Android Pay since the update to the app last week?

Thanks!
[T-Mobile Galaxy Note 4 General] _kevn_:
I just checked my old backup of it from dec 15 and it's 1.1... newest play store version is 1.2... hopefully you've got an older backup if they've patched it. :(

I'm attempting to restore my 1.1 backup but titanium backup doesn't seem to be cooperating with me atm. Trying to see if the older version will give me different results.
[T-Mobile Galaxy Note 4 General] ShrekOpher:
Apk mirror will have the older versions of both Android Pay and Google Play Services.
[T-Mobile Galaxy Note 4 General] ShrekOpher:
Its official Google is patching Android pay to no longer work with systemless root. Just as an update Google fixed the systemless root work around in Android Pay. It will no longer work on systemless root phones. http://www.androidpolice.com/2016/0...temless-root-android-pay-no-longer-compatible
[T-Mobile Galaxy Note 4 General] prican25:
Android Pay workaround for 2.67 Beta

Hey,

Thought I'd share this as I found it in Nexus 5X forum and tested it to be working enough for me to add a card but cannot test purchasing at the moment. Credit goes to jgummeson and nathanchance:

1. Navigate to TWRP > Advanced > Terminal Command.

2. Select the current folder (should be root or /) using the button in the righthand corner.

3. Type these two commands, one at a time:

echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu

4. Install systemless SuperSU 2.67 beta zip

5. Reboot system and choose not to install supersu

Be sure to have USB Debugging enabled and ADB drivers installed for the following or you can try Terminal Emulator:

1. Open terminal/command prompt and type "adb shell" and hit enter

2. From adb shell type "su" and hit enter (supersu should come up on the phone)

3. Type "chmod 751 /su/bin" and hit enter.

Please type without the quotes and I did this on a clean install of DOK2.

Good luck
[T-Mobile Galaxy Note 4 General] icugotit2:
Confirmed working on clean Dok2 following the steps from above. Thnaks pri ! for sharing
[T-Mobile Galaxy Note 4 General] yogieajuz:
So just ODIN CF Auto root without flash TWRP?
[T-Mobile Galaxy Note 4 General] ubigred:
Yes
[T-Mobile Galaxy Note 4 General] yogieajuz:
Thanks. But this not full root is that right?
[T-Mobile Galaxy Note 4 General] timg11:
I'm running Android: 5.1.1 N910TUVU2DOK stock with 3.10.40-BeastMode kernel installed in December. (this thread)

I'm looking for a way to remove the red and yellow warning text "kernel is not seandroid enforcing" and "set warranty bit : kernel" that appears with every boot.

Would this new root method remove those messages?

From my current state, how could I switch to this new method in a way that would

1) remove the warning message

2) be data compatible (so I can back up and restore everything with TiBk without issues - that should be possible if I stick with stock DOK, right?)
[T-Mobile Galaxy Note 4 General] ShrekOpher:
Flash stock dok2 firmware via Odin, then use the systemless root SuperSu.Zip and you will be good to go
[T-Mobile Galaxy Note 4 General] timg11:
Thanks ShrekOpher, I'm unfamiliar with the pros and cons of systemless root. I looked at http://www.supersuroot.com/, and it appears to be for Marshmallow. But Stock DOK2 firmware is 5.1.1 right?

Is it really as simple as this:

1) Flash stock DOK2 firmware N910TUVU2DOK2_N910TTMB2DOK2.zip (is factory reset and full wipe required first?)

2) download SuperSUApk-v2.46.zip and sideload the APK, install, and reboot

3) Done?
[T-Mobile Galaxy Note 4 General] ShrekOpher:
System less root will work on 5.1.1. The Benefit is that it allows for root access for MOST apps without modifying the system. Which mean to your device and a few application it will look like your phone has not been modified which will allow for the two items on the boot screen to look normal, and allow you to use SE LINUX enforcing with a stock kernel.
[T-Mobile Galaxy Note 4 General] jlarson5488:
Help i have no clue what im doing....

Hey guys. Ive roots motos and nexus devices which were super easy to root and flash. however i now have a note4 and i cant stand this slow stock rom. i want to root but every method looks complicated and im not 100% sure which method is safest. I also need to confirm which rom is fastest and how to maintain use of the samsung apps for the s-pen. I need to know how to root, unlock my bootloader, and the best recovery to use for flashing. Can anyone point me in the right direction. I listed my specs below.

Thanks,

Model: SM-N910T3

5.1.1

Baseband:N910T3UVU1DOK2

Build:LMY47X.N910T3UVU1DOK2

KNOX: 2.4.1

Bootloader: Locked
[T-Mobile Galaxy Note 4 General] squiglybob13:
So right now I'm rooted in the stock rom but a custom kernel. If I want to use this new method, would I just have to flash the stock kernel and reroot? Or would I have to flash the entire stock rom first?
[T-Mobile Galaxy Note 4 General] timg11:
This thread <http://xdaforums.com/showpost.php?p=64161125&postcount=3> has a link to Beta Super-SU v2.67

https://www.chainfire.eu/ has a posting "SuperSU v2.72 BETA released"

I read earlier in this thread that "SuperSu 2.66 beta was causing the list IMEI bug". Has it been fixed? Which version is currently recommended for systemless root?
[T-Mobile Galaxy Note 4 General] timg11:
Now SuperSU is up to 2.74 beta.

Has anyone tried it? Does it work with the Note4?

---------- Post added at 03:22 PM ---------- Previous post was at 02:59 PM ----------

I have read this thread from this message to the end. I do not see any report or update that the IMEI bug has been fixed. So the problem has not been fixed? Is 2.65 still the only safe version to use?

---------- Post added at 04:15 PM ---------- Previous post was at 03:22 PM ----------

[MENTION=3074575]yogieajuz[/MENTION], I have a factory-fresh refurb SM-N910T. I'd like to try the CF Auto Root without flashing TWRP. Did this work for you?

The reason I was attracted to the systemless root with SuperSU is because I want to avoid the red and yellow messages at boot about the kernel. Does the CF Auto Root method work with an unmodified kernel and prevent the messages at boot time?
[T-Mobile Galaxy Note 4 General] yogieajuz:
That work perfect on mine but make sure you get the right CF auto root for your model. But i still got yellow massage on boot.
[T-Mobile Galaxy Note 4 General] timg11:
Thanks for clarifying that the CF-Auto-Root method still modifies the kernel and causes the message. I'll go with the systemless room from SuperSU. Can anyone confirm which versions for SuperSU work for the N910T?

---------- Post added at 07:34 PM ---------- Previous post was at 07:06 PM ----------

[MENTION=5264497]ShrekOpher[/MENTION], I was re-reading the whole thread and noticed this message. So this systemless root method still causes the yellow and red text warnings to appear at the top of the screen when booting?

I thought you said that this systemless root prevented that message in my first question back in April. Did I misunderstand? Is there any way to have root without the yellow and red text warnings at boot time?
[T-Mobile Galaxy Note 4 General] ShrekOpher:
when I posted the OP it did not cause that text to appear. If you are seeing it then you need to Odi the stock FIRMWARE and TWRP then flash the systemless root supersu. It may have changed though with newer version of the SuperSU and any software updates to the Note 4. I do not use my note 4 anymore. I may have to pull it out and take a look though.
[T-Mobile Galaxy Note 4 General] timg11:
[MENTION=5264497]ShrekOpher[/MENTION], I found this in the changelog for SuperSU:

21.01.2016 - v2.67 - BETA
- (systemless) Improved deep sleep fix for Samsung 5.1+

Is that the issue that was the root cause of the "IMEI bug"? Does this "improvement" fully fix the problem with the SM-N910T?

---------- Post added at 08:13 PM ---------- Previous post was at 07:56 PM ----------

Thanks for the reply! I have a SM-N910T fresh from the factory refurb with stock Android 5.1.1 and build number LMY47X.N910TUVU2DOK2. I have not done anything to it yet. I'm trying to decide between CF-Auto-root and SuperSU root, and which version (2.65 vs 2.74) to use if I use SuperSU.

I was reacting to this message from you, where chodaboy said " I'm getting the message: "Kernel is not SEAndroid Enforcing"?", and then you said "Yeah I get that as well,"

So maybe it changed along the way as you said? I don't know of any other rooting method to avoid the warnings, so I guess I'll try the SuperSU systemless root:

I will install TWRP 3.0.2 for trltetmo (Samsung Galaxy Note 4 Qualcomm (trlte)) using Odin 3.10.7

I will use TWRP to install SuperSU 2.74 (pending your confirmation that it is fixed)

The result I am looking for is a rooted Note 4 with otherwise stock FW, without red and yellow warning messages when booting. All correct?
[T-Mobile Galaxy Note 4 General] S5Sickness:
I don't see a difference in the old and the new one.... i do see the red and yellow message has changed at boot... i don't get the red but i do still get the yellow about the kernel...
[T-Mobile Galaxy Note 4 General] timg11:
So I'm concluding that nobody knows whether Chainfire has fixed the bug in SuperSU 2.74. I'm assuming it is fixed, because it's been several months, and it seemed like a pretty serious issue. Just to be sure, I will modify the install procedure as follows:

I will install TWRP 3.0.2 for trltetmo (Samsung Galaxy Note 4 Qualcomm (trlte)) using Odin 3.10.7

I will use TWRP to make a Nandroid backup of the stock ROM to extSdcard in case SuperSU 2.74 is still broken.

I will use TWRP to install SuperSU 2.74

I will test connectivity, and if none, Nandroid restore back to original stock. (then evaluate whether to use SuperSU 2.65 or just go with CF-AutoRoot)

---------- Post added at 11:28 PM ---------- Previous post was at 11:23 PM ----------

@ S5Sickness, is is possible find the code that displays that warning and patch it out? Is it part of the bootloader? Am I the only one that wants a "clean" boot appearance?
[T-Mobile Galaxy Note 4 General] slnit:
Works fine with the stock kernel and supersu v2.74, good job thanks.
[T-Mobile Galaxy Note 4 General] Pinan:
I believe you meant to say "SuperSU 2.65"
[T-Mobile Galaxy Note 4 General] timg11:
Correct - post has been edited.
[T-Mobile Galaxy Note 4 General] timg11:
Lost root after thee weeks - why?

I completed this root method a few weeks ago and reported on the details above. Everything has been fine for three weeks. Today, I run Titanium Backup and it can't get root.

I then run SuperSU, and it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"

Yes it is a problem! How could that happen? Automatic updates are disabled the Kernel and build number are the same. What could cause this loss of root?

I assume I have to go back to recovery and flash the SuperSU ZIP again?

Then how do I prevent a repeat of this problem?
[T-Mobile Galaxy Note 4 General] timg11:
I was able to restore root by reflashing SuperSU from Recovery.

I'm still looking for answers on why this occurred.
[T-Mobile Galaxy Note 4 General] ShrekOpher:
Titanium Backup does not have full features with systemless root. You can disable app but some you will not be able to uninstall.
[T-Mobile Galaxy Note 4 General] timg11:
That is good to know, but I still don't understand why I lost root. Are you saying that the loss of root has something to do with Titanium Backup? I have not tried to uninstall apps, only freeze them.
[T-Mobile Galaxy Note 4 General] ShrekOpher:
If you think you lost root you can always just flash the super user zip again. I doubt you lost root, my guess is that the app you are trying to use is saying you don't have root, because it is not compatible with systemless root. some root apps just will not work on systemless root. The only way to have full root on any device passed Android 5.1.1 is the flash a custom kernel.
[T-Mobile Galaxy Note 4 General] timg11:
I lost root again after only 1 week. I first notice that Titanium Backup says it can't get root (it is able to work with systemless root before this). Next, Run SuperSU. As in this post, SuperSU says ""There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 5.0 [***ANY ANDROID VERSION***] , you need to manually re-root. [OK]""

I reboot to recovery, re-flash SuperSU, and then I have root again. SuperSU and Titanium Backup work normally again.

So this is not a compatibility issue with systemless root - something is removing root by disabling SuperSU.

Do you have any suggestions on how the root could be lost? How can I prevent it? Is this not happening to others? Maybe I need to freeze some apps?

---------- Post added at 02:25 PM ---------- Previous post was at 01:51 PM ----------

Another question - with systemless root, do I need busybox? Are they related? Is busybox compatible with systemless? Will it interfere or cause problems with systemless root?

I ask because I ran MyBackup Pro, and it said "Your busybox is not installed or out of date".

I ran Busybox Pro, and it says "Busybox is not installed. Busybox 1.24.2 will be installed to /su/bin". I backed out and did not do anything yet.
[T-Mobile Galaxy Note 4 General] Daymeand:
Systemless root

I tried it on my galaxy note edge lollipop 5.1.1. And I was rooted but my internet 4g was completely unusable. Even after trying to root force it on.

I tried it on the same phone after I updated to marshmallows 6.0.1. And got the same thing.

The beta supersu 2.6.1 doesn't work correctly.

Fyi please try and help with this issue.
[Galaxy S III Mini Q&A, Help & Troubleshooting] nuschpl:
Aim of this thread is collect knowledge about SDcard mode, which may help when phone is bricked and download mode doesn't work. Big Galaxy S series on Exynos support it by entering download mode(by buttons/download jig) and short some resistor, Galaxy S3 min is ST-Ericsson NovaThor U8420 based. I'm wonder if it's Exynos specific. I've prepared Sdcard by cloning /dev/mmcblk0 from functional phone, and using download JIG, doesn't work. Does anybody has more info on this topic?
[Moto G Q&A, Help & Troubleshooting] adamo145:
phone just boots up and then goes to a blank/black screen and is unsuable.

bootloader is unlocked and twrp is installed.

wtf did I do.

crap.

help!!
[Moto G Q&A, Help & Troubleshooting] adamo145:
not sure what you mean.

If I hold down the power/volume down buttons I can get to that menu but that doesnt seem to help.
[Moto G Q&A, Help & Troubleshooting] DPX:
U mentioned that u installed twrp. Can u go there?
[Moto G Q&A, Help & Troubleshooting] adamo145:
yes i can
[Moto G Q&A, Help & Troubleshooting] adamo145:
can someone link the 5.0.2 stock rom? maybe I can download and install that?
[Moto G Q&A, Help & Troubleshooting] lost101:
Stock Motorola Lollipop ROM Collection​
[Moto G Q&A, Help & Troubleshooting] adamo145:
thanks so much.

how do I go about loading this onto my moto g?

I dont really know how and I dont want to screw my phone up anymore than it is.
[Moto G Q&A, Help & Troubleshooting] lost101:
First post of that thread contains detailed flashing instructions.
[OnePlus 2 Q&A, Help & Troubleshooting] ethanscooter:
I was VERY stupid. I went back to stock Oxygen OS using a fastboot image and now if I dial #*06# the IMEI box shows up but no IMEI number is actually in the box it is just blank. I did post about this before but last time I didn't really know what happened I was asking if anyone could tell me what they thought happened. I am pretty sure I screwed up the EFS partition and I am just wondering what I need to do now. Is there some way I can repair it I mean I don't have a backup. Can I contact OnePlus support? I really need help.
[OnePlus 2 Q&A, Help & Troubleshooting] v7:
Where did you find the fastboot file?

________

v7

XDA Assist
[OnePlus 2 Q&A, Help & Troubleshooting] ethanscooter:
I forgot where I found it from... do you know where he correct one is?
[OnePlus 2 Q&A, Help & Troubleshooting] v7:
There's no official fastboot zip from the Oneplus.That's why I asked you.Did you find it from XDA?

__

v7

XDA Assist
[OnePlus 2 Q&A, Help & Troubleshooting] ethanscooter:
I forgot, honestly this happened a few weeks ago I tried looking through my history but I couldn't find it. How can I fix it?

EDIT: It wasn't from XDA for sure.
[OnePlus 2 Q&A, Help & Troubleshooting] _MetalHead_:
This happened to me a few times in the past, all I had to do was wipe dalvik and cache again and it came back. Not sure if it's the same issue but I would give it a shot. Just boot into recovery and wipe them again and see if it gets you back up and running.
[OnePlus 2 Q&A, Help & Troubleshooting] ethanscooter:
I tried it and still nothing...
[OnePlus 2 Q&A, Help & Troubleshooting] krishna442:
http://xdaforums.com/showpost.php?p=62440352&postcount=21

first try this.

then, flash H2OS. (Oxygen Os won't work from that recovery so, H2OS. Later you can re-flash though)

(Try this first!!!)

EDIT: if that doesn't reset, try this.

http://xdaforums.com/oneplus-2/gene...over-oneplus-2-to-t3269543/page2#post64303240

Official O2OS files.
[OnePlus 2 Q&A, Help & Troubleshooting] ethanscooter:
I cannot use that because my device is not hard bricked and it will not install the driver since I can enter the bootloader normally.
[OnePlus 2 Q&A, Help & Troubleshooting] khaos64:
Not sure if you've seen this post its based on the post above but I think it just uses fastboot. Don't know if it will work for you, but figured it would be worth a shot.

http://xdaforums.com/showpost.php?p=62973446&postcount=2
[OnePlus 2 Q&A, Help & Troubleshooting] ethanscooter:
I tried using the tool and it did not work, I purposely hard bricked the device to try it and still no signal or imei. Another problem is WiFi takes about 4 minutes just to turn on but I can live with that I just want service.
[OnePlus 2 Q&A, Help & Troubleshooting] krishna442:
Basically flashing back the stock should bring back the efs. Let's see if someone has a solution. Sorry!
[OnePlus 2 Q&A, Help & Troubleshooting] kuban_kevin:
EFS files are unique to each phone. If the EFS is corrupt or damaged, and there is no backup, I don't know of any way to fix it ;_; You can try OnePlus support but they aren't as dumb as carrier warranty or other phone manufacturers. They'll be more likely to know what you did.