Database Users

Encryption Stuck at 0%

Old:
So I searched, but no luck. My phone requires a 6 character unlock password to encrypt the device. This is not a power on password, but an unlock password. How do I change that to a pattern or pin? TIA!
Update:
So I went ahead with the 6-ch password, and now encryption is stuck at 0% forever. Is it Jeboo? I unrooted the device and removed SU apk. Thanks.

I'm running Shostock 2.1 BTW.

Anyone out there have any clues where to find an answer? Is it because of Jeboo custom recovery?

I had this exact problem. Yes, it's the recovery. On stock TW and any stock-based roms (and most other roms), the encryption will not start (stuck at 0%) if you don't have the stock recovery. Cyanogenmod is the only rom I've found where encryption actually works. Unfortunately, TWRP 2.6 still doesn't seem to recognize the correct password for me. Additionally, CM doesn't have an option to encrypt the (external) SD card. (Quick note, encrypting the external SD card works everywhere no matter what, it's just device encryption I've been talking about.) I still haven't solved this problem. All I want is to be able to have a decent custom rom with both device and external encryption and have TWRP be able to read them. Apparently that is too much to ask currently. Too bad, oh well. I'm sitting reasonably happy at the moment on unencrypted Goldeneye with OUDHS, but I really wish I had device encryption. If we could somehow find a flashable stock recovery, that might solve the problem, but I don't know for sure, because I can't find one, and I don't know enough to do anything more.

:angel:
kL7GtEd said:
I had this exact problem. Yes, it's the recovery. On stock TW and any stock-based roms (and most other roms), the encryption will not start (stuck at 0%) if you don't have the stock recovery. Cyanogenmod is the only rom I've found where encryption actually works. Unfortunately, TWRP 2.6 still doesn't seem to recognize the correct password for me. Additionally, CM doesn't have an option to encrypt the (external) SD card. (Quick note, encrypting the external SD card works everywhere no matter what, it's just device encryption I've been talking about.) I still haven't solved this problem. All I want is to be able to have a decent custom rom with both device and external encryption and have TWRP be able to read them. Apparently that is too much to ask currently. Too bad, oh well. I'm sitting reasonably happy at the moment on unencrypted Goldeneye with OUDHS, but I really wish I had device encryption. If we could somehow find a flashable stock recovery, that might solve the problem, but I don't know for sure, because I can't find one, and I don't know enough to do anything more.
Click to expand...
Click to collapse
Alright, I thought it was the recovery. I had the same problem with a custom rom on my gs3, but my office disable encryption for me. They can no longer do that under their policy.
Can you install a custom rom and then flash the stock recovery with odin, or will that interfere with the ROM? I really hate the stock bloat, but I need email on my phone so that maybe my only option.

Has anyone tried this with vanilla 4.3 and twrp?

I guess I'll have to go to stock, root, debloat, and unroot.

hashish16 said:
I guess I'll have to go to stock, root, debloat, and unroot.
Click to expand...
Click to collapse
How are you going to unroot?

jd1639 said:
How are you going to unroot?
Click to expand...
Click to collapse
The super user app lets you unroot.

Google assistant

Has anyone received Google Assistant on their phones yet? Just curious.

Yep. You can force it with a build.prop edit. It worked for me, but I think there are mixed reports. Root required.
https://forum.xda-developers.com/showpost.php?p=71272192&postcount=1520

I'm surprised to hear some people still don't have GA natively. I'm a long time HTC user, but I just bought my 10 last Fri. it's pretty sweet. although, I must say, I still REALLY like my One M8.

SilverZero said:
Yep. You can force it with a build.prop edit. It worked for me, but I think there are mixed reports. Root required.
https://forum.xda-developers.com/showpost.php?p=71272192&postcount=1520
Click to expand...
Click to collapse
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.

misfiremind said:
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
Click to expand...
Click to collapse
I'm S-ON, unlocked bootloader, newest N firmware and latest Bad Boyz ROM (full version with MagiskSU, not SuperSU) and I have Android Pay working just fine. No reboot necessary, just use Magisk Manager to hide Magisk from Android Pay.

SilverZero said:
I'm S-ON, unlocked bootloader, newest N firmware and latest Bad Boyz ROM (full version with MagiskSU, not SuperSU) and I have Android Pay working just fine. No reboot necessary, just use Magisk Manager to hide Magisk from Android Pay.
Click to expand...
Click to collapse
I know, but I've rooted and messed with custom ROMs on every phone I've had and I'm kind of tired of messing with that stuff. Really I think the best thing I could do is buy a Pixel. I'm tired of the different phone manufacturers and their bloated ROMs and the constant problems that custom ROMs have. At least for right now. Thanks though. I'll keep it in mind if I ever feel like jacking with that stuff again.

"OK Google" Always on!!??
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?

misfiremind said:
I unlocked my bootloader Saturday but I'm reluctant to root because I don't want to lose Android Pay. If I can modify some the build.prop for Google Assistant and get wi-fi hotspot then reboot so I can use Android pay then I might.
Click to expand...
Click to collapse
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
misfiremind said:
I know, but I've rooted and messed with custom ROMs on every phone I've had and I'm kind of tired of messing with that stuff. Really I think the best thing I could do is buy a Pixel. I'm tired of the different phone manufacturers and their bloated ROMs and the constant problems that custom ROMs have. At least for right now. Thanks though. I'll keep it in mind if I ever feel like jacking with that stuff again.
Click to expand...
Click to collapse
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...

deakelem said:
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
Click to expand...
Click to collapse
this is from my Bolt, so it may be different, but I can disable just fine...

OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
I didn't even try after unlocking because I'm still waiting for my bank to support Android Pay, but I just checked and your right. I'm blocked from Android Pay. Might as well figure out how to root and install a ROM this weekend. ? And no, I have no idea what Magisk is, but I guess I'll have to figure it out.

deakelem said:
So has anyone else noticed this?
The attached screenshot shows the settings for the "ok google" always listening feature. I know this feature is useful to launch google from any screen or even when the screen is off but I do not want this on for privacy reasons. I was always able to disable it on Marshmallow but now with N even when i turn it off it turns back on.
How to try to reproduce:
Turn off the feature
Exit the settings menu
Go back to the Ok google settings and see if its enabled again.
Is this happening to anyone else!?
Click to expand...
Click to collapse
Mine seems to work fine. Have you tried clearing the Google App data? I had an issue with a couple of apps after the Nougat update and had to clear the data and uninstall then reinstall the apps to get them working correctly.

misfiremind said:
Mine seems to work fine. Have you tried clearing the Google App data? I had an issue with a couple of apps after the Nougat update and had to clear the data and uninstall then reinstall the apps to get them working correctly.
Click to expand...
Click to collapse
Ill try that but I flashed N using the RUU and then clean installed OMJ's badboys rom so no app data would have been there during M to N
---------- Post added at 02:16 PM ---------- Previous post was at 02:14 PM ----------
OMJ said:
this is from my Bolt, so it may be different, but I can disable just fine...
Click to expand...
Click to collapse
Thats strange, i dont have all those menu entries... could be cause I have work email on my phone via activesync which restricts certain security and lockscreen options.

OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
Click to expand...
Click to collapse
I'm confused . . . My bootloader is unlocked, has been since I got my 10 last summer, and I just used Android Pay this weekend, and Magisk Manager says I'm currently passing SafetyNet. Android Pay is checked in Magisk Hide.
Are you saying that unlocking the bootloader alone will cause SafetyNet to fail, but Magisk Hide will then allow it again?

SilverZero said:
I'm confused . . . My bootloader is unlocked, has been since I got my 10 last summer, and I just used Android Pay this weekend, and Magisk Manager says I'm currently passing SafetyNet. Android Pay is checked in Magisk Hide.
Are you saying that unlocking the bootloader alone will cause SafetyNet to fail, but Magisk Hide will then allow it again?
Click to expand...
Click to collapse
yes, merely having the bootloader unlocked even w/ 100% stock ROM, safetynet will fail....the beauty of magisk is that it hides it

I think at this point I'd rather relock my bootloader and go back to using my Galaxy S4 while I try to sell my HTC 10 and then put that money towards a Pixel. Anybody wanna buy a phone? ?

It's here! I literally just this minute got Google Assistant!

OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
I think I am going to give this a shot. I am running your stock rooted with TWRP while S-on. Can I just install your Magisk Full Rom and go from there or is that too easy to believe? Thanks OMJ!

OMJ said:
hate to be the bearer of bad news but SafetyNet will fail w/ a unlocked bootloader
you must not be familar w/ Magisk....the "magic" of magisk can modify the phone w/o actually modifying /system, so technically u have a stock device but custom at the same time...plus magisk hide allows AP to work & pass SafetyNet
my Magisk ROM has all the mods & bloatware removed just like my custom ROM...
Click to expand...
Click to collapse
Is magisk a ROM or more of a mod? And what is magisk su? I'm going to try and get my phone rooted this weekend but I can't find a tutorial thread, it seems to be scattered everywhere. It seems like I fastboot TWRP, flash SuperSU, flash magisk then install magisk manager from Google Play?

misfiremind said:
I didn't even try after unlocking because I'm still waiting for my bank to support Android Pay, but I just checked and your right. I'm blocked from Android Pay. Might as well figure out how to root and install a ROM this weekend. ? And no, I have no idea what Magisk is, but I guess I'll have to figure it out.
Click to expand...
Click to collapse
im running viper due to lack of cm/aosp st the moment.. so i have magisk but i have no idea what it is or how to use it. very little instruction out there.

Has anyone been successful in editing their build.prop file to activate (or deactivate) Google Assistant? I actually want to deactivate Google Assistant but I can't seem save changes to my build.prop file.
I have root on stock ROM.
Set SE Linux to permissive.
Tried using Root Explorer and build.prop Editor. Both give me an error message stating it can't save the build.prop file.
Suggestions?

What im going to lose after root.

As title said, what features im going to lose besides the OTA and knox?
Sent from my SM-G950F using Tapatalk

iiD4x said:
As title said, what features im going to lose besides the OTA and knox?
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
Caution: This phone has dm-verity enabled. This means that if you root your phone, it will no longer boot as it can't pass the "Integrity check". I lost a bunch of stuff when I rooted, because I didn't knew that. Recovering it after with something like TWRP is not possible, because the data partition is encrypted.
Backup everything before!!!

gunner007dc said:
Samsung Pay if you use it (any Knox dependant apps), Android Pay can work with Magisk but it's a cat-mouse game of passing SafetyNet. Some financial apps will refuse to work on rooted phones (some can be avoided with Magisk Hide) but if they mean anything to you it's best to check the apps to see if anyone reports problems with a rooted device. I know Netflix and other content providers sometimes block rooted phones.
Click to expand...
Click to collapse
:good: Thanks.
Fusseldieb said:
Caution: This phone has dm-verity enabled. This means that if you root your phone, it will no longer boot as it can't pass the "Integrity check". I lost a bunch of stuff when I rooted, because I didn't knew that. Recovering it after with something like TWRP is not possible, because the data partition is encrypted.
Backup everything before!!!
Click to expand...
Click to collapse
Yeah, i did backup before rooting, Thanks.

Warrenty

Pokemon go

Warranty (tripping knox), Android & Samsung Pay and over-the-air updates.
Generally you have to unroot for the OTA updates to work, but sometimes that is not enough, you have to factory restore the device as well. There is the app "FlashFire" which help you keep root as you upgrade OTA, but I find this won't work on all phones.
These three reasons are why I simply do not root anymore. Now if you have a Google Pixel or OnePlus, they generally don't take away your warranty even if you unlock bootloader or root. Some manufacturer like HTC and Moto, generally you have to request a bootloader unlocking code in order to install custom recovery to root, and in requesting the unlock code you forfeit your warranty.

Is there a way to patch s Health to get it working?

Fusseldieb said:
Caution: This phone has dm-verityenabled. This means that if you root your phone, it will no longer boot as it can't pass the "Integrity check". I lost a bunch of stuff when I rooted, because I didn't knew that. Recovering it after with something like TWRP is not possible, because the data partition is encrypted.
Backup everything before!!!
Click to expand...
Click to collapse
The only thing you said that is correct is that the phones have dm-verity. But given that is implemented by the boot. Img, you can either remove it with 1, an engineering boot, because you can disable dm verity with selinux in permissive. 2, flash a rom that doesn't contain the dmverity flag, seeing as the boot only checks dm verity against the partitions that contain the flag(which isn't many. And is none on a full custom rom) or 3, pull apart the boot image and remove the dmverity file.
And general root has no bearing on dmverity anyways unless an app attempts to obtain root during boot up.
But anyways. It really depends on the root method as to what you lose. If we can achieve root with a locked bootloader, you will still be able to use Samsung pay and other Knox apps with standard root hider

Hi all is there a saver root yet every one I see there was problems
cheers

Install TWRP

I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!

Great job keep us posted

zamzenos said:
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Click to expand...
Click to collapse
I think you would need a boot.img that disables it. Or you can disable encryption manually and erase all data to keep it disabled.

zamzenos said:
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Click to expand...
Click to collapse
@jcadduono can help you to have a perfect job about TWRP ...
Ask him on irc ...

Backup failed because /data cannot be mounted, which suggests a mismatch twixt TWRP and device. Decided to push on and try to root. This failed, so that stock firmware had to be installed. I've hacked a number of phones and tabs here, so I was itching to see what could be done with existing N7 mods. Now I know.
It looks as though we need recovery etc specific to FE. Not sure we will have the numbers for it, though. If anyone has any ideas...

zamzenos said:
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Click to expand...
Click to collapse
Your a brave man for trying this and the first to do so on here so thank you!.
As for the encryption on all the last few sammy devices ive had/have including the original Note 7 once you flash twrp you have to format data in twrp (not wipe mind you...format) to remove encryption.
We also had to then flash a zip to deal with dm verity but now SU does that anyway and also keeps the device decrypted when you reboot.
Id hazard a guess and say if you formatted and flashed SU this might actually work.
Now that we know flashing twrp (which was my main worry) and then odin stock without any issues this just got alot less risky.
sent from my Note FE, S8 plus, S7 edge or S6

Well I'm traveling now and will give this a go when I return home. Question: does DM Verity and Magic's or SU root require a a Note FR boot image to work or can they simply patch the boot image?

force70 said:
Your a brave man for trying this and the first to do so on here so thank you!.
As for the encryption on all the last few sammy devices ive had/have including the original Note 7 once you flash twrp you have to format data in twrp (not wipe mind you...format) to remove encryption.
We also had to then flash a zip to deal with dm verity but now SU does that anyway and also keeps the device decrypted when you reboot.
Id hazard a guess and say if you formatted and flashed SU this might actually work.
Now that we know flashing twrp (which was my main worry) and then odin stock without any issues this just got alot less risky.
sent from my Note FE, S8 plus, S7 edge or S6
Click to expand...
Click to collapse
Ah, I followed directions I found on the N7 forum, from which I assumed that SU would do the encryption. This is the first time I have come up against this barrier. I was resigned to possibly not having root, but from what you say I now think we might well manage it.
I've had a number of narrow shaves with various devices, so I felt that I could find my way out of any difficulty I encountered hacking the FE (maybe just fool's luck) . While cortez.i will try it at some stage, I am tempted to dive back in and see what happens.
Incidentally, sammobile didn't have the K variant firmware (may have now). I found it through google on a vietnamese site.
Just found this comprehensive guide to removing dm-verity:
http://www.theandroidsoul.com/disable-dm-verity-forced-encryption-galaxy-note-7/

Posting this separately.
FE WILL ROOT!
Factory reset is automatic (with less KT bloat, for some reason).
Titanuim can uninstall apps. But Adaway cannot copy edited hosts file. Sdfix cannot release the card: says there are no groups in WRITE_EXTERNAL_STORAGE. Keep getting a security warning with each reboot from security log agent, but no action on reboot. Hopefully, all this can be sorted.
Finally, TWRP backup successful. Assume for now that it would restore, if needed.

zamzenos said:
Posting this separately.
FE WILL ROOT!
Factory reset is automatic (with less KT bloat, for some reason).
Titanuim can uninstall apps. But Adaway cannot copy edited hosts file. Sdfix cannot release the card: says there are no groups in WRITE_EXTERNAL_STORAGE. Keep getting a security warning with each reboot from security log agent, but no action on reboot. Hopefully, all this can be sorted.
Finally, TWRP backup successful. Assume for now that it would restore, if needed.
Click to expand...
Click to collapse
You are THE MAN !!!!
WOOOOOOOOOO

wolfgart said:
You are THE MAN !!!!
WOOOOOOOOOO
Click to expand...
Click to collapse
I second that!
You shoukd be able to freeze security log agent with TIBU or package disabler pro to get rid of that message

force70 said:
I second that!
You shoukd be able to freeze security log agent with TIBU or package disabler pro to get rid of that message
Click to expand...
Click to collapse
I uninstalled the log agent with Titanium, ripped out all the Knox, still getting that message. I think I'll backup progress so far and restart FE from within the warning message and see what happens...**
Thank you both for the kudos. But some work still to be done. I'm finding some apps won't start - unfortunately some of them important. It's OK for now - I'm not using the FE yet - but need to get some real benefits from root, otherwise it's back to stock with Adhell (tho' I'd say sammy will spike that soon). Maybe folk with more tech xp than I have can work out what's wrong here.
**Restart from within Security boots into Recovery - in this case TWRP. Looks like a response to the decrypted state, and is set off by any root level action. Can we get rid of this?

zamzenos said:
Posting this separately.
FE WILL ROOT!
Factory reset is automatic (with less KT bloat, for some reason).
Titanuim can uninstall apps. But Adaway cannot copy edited hosts file. Sdfix cannot release the card: says there are no groups in WRITE_EXTERNAL_STORAGE. Keep getting a security warning with each reboot from security log agent, but no action on reboot. Hopefully, all this can be sorted.
Finally, TWRP backup successful. Assume for now that it would restore, if needed.
Click to expand...
Click to collapse
which root package did you use, Magix or SU and did you have to use no verity disable zip?
EDIT: Nevermind, i'm rooted with SuperSU. have a 4 hour plane ride home so i'll have plenty time to checkout root before i get home..

cortez.i said:
which root package did you use, Magix or SU and did you have to use no verity disable zip?
EDIT: Nevermind, i'm rooted with SuperSU. have a 4 hour plane ride home so i'll have plenty time to checkout root before i get home..
Click to expand...
Click to collapse
Just curious if Knox is now tripped,by using SU ?
For myself,I'm not too worried about it either way,but,those interested in root may want to know,for future Samsung Pay use/possible resale value loss due to Knox 0x1/etc....

KOLIOSIS said:
Just curious if Knox is now tripped,by using SU ?
For myself,I'm not too worried about it either way,but,those interested in root may want to know,for future Samsung Pay use/possible resale value loss due to Knox 0x1/etc....
Click to expand...
Click to collapse
Yes sir as soon as you flash twrp its tripped.
And we need twrp for SU so no way around it.
sent from my Note FE, S8 plus, S7 edge or S6

force70 said:
Yes sir as soon as you flash twrp its tripped.
And we need twrp for SU so no way around it.
sent from my Note FE, S8 plus, S7 edge or S6
Click to expand...
Click to collapse
I figured that much hadn't changed since I last rooted/ROM'd a Samsung device,thanks for confirming. :good:
Again,for myself,it's not much of an issue,I plan on keeping this phone for the long haul (at least 1-2 yrs) & loss of Samsung Pay/Android Pay is of no consequence to me.

KOLIOSIS said:
I figured that much hadn't changed since I last rooted/ROM'd a Samsung device,thanks for confirming. :good:
Again,for myself,it's not much of an issue,I plan on keeping this phone for the long haul (at least 1-2 yrs) & loss of Samsung Pay/Android Pay is of no consequence to me.
Click to expand...
Click to collapse
Ive never cared about knox either....and this phone I will keep until it dies or I do lol

force70 said:
Ive never cared about knox either....and this phone I will keep until it dies or I do lol
Click to expand...
Click to collapse
+1
LMFAO,let's hope for the former................... :highfive:

so... after renaming SecurityLogAgent.apk from TWRP, i've had no problems running root apps, modifying build.prop, etc. google Adaway Vesion 3.2 and install this version and it will configure hosts files without issue (at least on my device). will continue testing and report findings should things changes. thanks @zamzenos for risking your device to confirm that the Note 7 version of TWRP is working.

cortez.i said:
so... after renaming SecurityLogAgent.apk from TWRP, i've had no problems running root apps, modifying build.prop, etc. google Adaway Vesion 3.2 and install this version and it will configure hosts files without issue (at least on my device). will continue testing and report findings should things changes. thanks @zamzenos for risking your device to confirm that the Note 7 version of TWRP is working.
Click to expand...
Click to collapse
The Adaway update worked. Thanks for that. I followed the N7 forum guide, except that I formatted data using TWRP, and used SU as advised. I uninstalled the log agent with Titanium (and as much of Knox as I could find). I no longer get security notifications, but something is still being tripped by any root activity. The apps that won't start don't require root, for instance, Adobe Reader, and sms and call log restore apps. I cannot see any common cause here. SDfix (latest version) says it can't find any groups, so can't do its work.
I'll nose around the S7 & 8 forums and see if any of these problems are turning up there (dev on the N7 was seriously interrupted by the problems caused by sammy's battery restrictions).

Shortcut to being rooted on N910VVRU2CQI2

Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE

I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks

My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839

RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.

Thanks doc. Is that a folder that gets overwritten when you flash a new room?

This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?

lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works

RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.

does this require the developer version? btw how do i backup

I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.

RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.

kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.

Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.

In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.

Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.

Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.

Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?

lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.

kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.

Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.