2021_VZW_NOTE4_Tool Too Root+Unlock Bootloaders+Upgrade Or Downgrade_Bootloaders_Works On KK/LL/MM Plus Roms For All 3 Firmwares

[mrjoshjohnsmith]

you cant hide google play services or phone wont boot so it unhides them if you hide them is that what you are talking about
magisk modules work on eftsu

No actually I was talking just about Gpay. EFTSU actually unhides Gpay each time I boot up (maybe its just a bug or something). O ok I was not aware that you can use Magisk Modules in EFTSU. could you kindly stear me into the right direction on exactly which module I would need for a Verizon Note 4? I have never actually installed a module before as I am very new to rooting and modifying.

 

[jrkruse]

No actually I was talking just about Gpay. EFTSU actually unhides Gpay each time I boot up (maybe its just a bug or something). O ok I was not aware that you can use Magisk Modules in EFTSU. could you kindly stear me into the right direction on exactly which module I would need for a Verizon Note 4? I have never actually installed a module before as I am very new to rooting and modifying.

Flash in etfsu manager if it hangs during flash or if successful reboot too twrp and flash in twrp as well just too make sure it is installed properly

 

[mrjoshjohnsmith]

Flash in etfsu manager if it hangs during flash or if successful reboot too twrp and flash in twrp as well just too make sure it is installed properly

Sweet thats, awesome man, I will try it tomorrow morning and I will def let you guys know how it goes! Thanks brother!

 

[jrkruse]

Sweet thats, awesome man, I will try it tomorrow morning and I will def let you guys know how it goes! Thanks brother!

that is for stock rooted samsung rom if you are using lineage you will have to use kdragons aosp safetynet fix below

Releases · kdrag0n/safetynet-fix

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com

 

[mrjoshjohnsmith]

that is for stock rooted samsung rom if you are using lineage you will have to use kdragons aosp safetynet fix below

Releases · kdrag0n/safetynet-fix

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com

that is for stock rooted samsung rom if you are using lineage you will have to use kdragons aosp safetynet fix below

Releases · kdrag0n/safetynet-fix

Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix

github.com

Thanks JK, so I already tried the Safety net fix for the Stock but rooted OS in the beginning of this thread (the one with latest FW) and although it does install, and it even shows up in my EFTSU Manager (and for some reason it fixed the issue with having to reselect hide upon startup, now it stays hid) but sadly as soon as g-pay goes to contact my credit card institution, it says the same thing I noted previously in the thread about the phone either running unofficial software or that it is rooted. So, I am at a loss as to what it is picking up on? Do you have any other suggestions or know what else may be happening? Also, I have not tried the lineage safety net yet but I wanted to make sure, do I use the latest version in the Github link you provided (2.4.0)? Thanks for everything man!

 

[jrkruse]

Thanks JK, so I already tried the Safety net fix for the Stock but rooted OS in the beginning of this thread (the one with latest FW) and although it does install, and it even shows up in my EFTSU Manager (and for some reason it fixed the issue with having to reselect hide upon startup, now it stays hid) but sadly as soon as g-pay goes to contact my credit card institution, it says the same thing I noted previously in the thread about the phone either running unofficial software or that it is rooted. So, I am at a loss as to what it is picking up on? Do you have any other suggestions or know what else may be happening? Also, I have not tried the lineage safety net yet but I wanted to make sure, do I use the latest version in the Github link you provided (2.4.0)? Thanks for everything man!

you have too add gpay to hide root and then you need too clear data on the gpay app and reboot

 

[mrjoshjohnsmith]

you have too add gpay to hide root and then you need too clear data on the gpay app and reboot

Ok, so I actually started back over and deleted Gpay, then reinstalled the safetynet module in both TWRP and EFTSU Manager, then I installed gpay without starting it up yet, and then made sure it was hidden in EFTSU Manager and that Safetynet was active in the module. Then I restarted, and again made sure the settings were active in EFTSU, and then finally opened the app, and once again it lets me open and log into Gpay but not use tap and pay! So since I could not get it to work on that phone, I turned my attention to the other file you provided me (the Lineage safetynet file) and to my absolute amazement, once I installed the latest magisk, and a majisk canery file (which I cant figure out where I got that one from or what version it is) and then installed the lineage safetynet module, google pay then worked absolutely flawlessly on lineage!! I was excited as heck for this, but why in the heck wont it work on my stock (but rooted) note 4??




Edit, I forgot to mention that before I started over with the stock rooted one, I did try to do as you said and hide root and then clear data in the Gpay app and then reboot....

 

[jrkruse]

Ok, so I actually started back over and deleted Gpay, then reinstalled the safetynet module in both TWRP and EFTSU Manager, then I installed gpay without starting it up yet, and then made sure it was hidden in EFTSU Manager and that Safetynet was active in the module. Then I restarted, and again made sure the settings were active in EFTSU, and then finally opened the app, and once again it lets me open and log into Gpay but not use tap and pay! So since I could not get it to work on that phone, I turned my attention to the other file you provided me (the Lineage safetynet file) and to my absolute amazement, once I installed the latest magisk, and a majisk canery file (which I cant figure out where I got that one from or what version it is) and then installed the lineage safetynet module, google pay then worked absolutely flawlessly on lineage!! I was excited as heck for this, but why in the heck wont it work on my stock (but rooted) note 4??




Edit, I forgot to mention that before I started over with the stock rooted one, I did try to do as you said and hide root and then clear data in the Gpay app and then reboot....

kdragons safetynet fix will most likely work on stock rom as well

 

[mrjoshjohnsmith]

kdragons safetynet fix will most likely work on stock rom as well

What I am confused about is that the safetynet fix works in lineage but not in the stock rooted version? The only difference is that I am using Magisk in Lineage rather than EFTSU which is the one installed in your stock Rom, could this be why?

Just to be sure, I tried the steps this morning (in the stock rom) with several different versions (some as old as 2020) of Gpay just to make sure that it wasn't being affected by app compatibility.

Is there something I may be doing wrong?

 

[jrkruse]

What I am confused about is that the safetynet fix works in lineage but not in the stock rooted version? The only difference is that I am using Magisk in Lineage rather than EFTSU which is the one installed in your stock Rom, could this be why?

Just to be sure, I tried the steps this morning (in the stock rom) with several different versions (some as old as 2020) of Gpay just to make sure that it wasn't being affected by app compatibility.

Is there something I may be doing wrong?

Flash magisk and try it on stock rom. Gpay is probably detecting the eftsu manager. Magisk manager has the ability too rename its manager but the other doesn’t

 

[mrjoshjohnsmith]

Flash magisk and try it on stock rom. Gpay is probably detecting the eftsu manager. Magisk manager has the ability too rename its manager but the other doesn’t

This is going to come off as a pretty dumb question but how do I flash Magisk when EFTSU is already installed in the rooted stock version that you have provided above? I have read over the Magisk instructions but I still do not understand what it means exactly (or how it is saying to do it) when it says talks about patching Magisk into the official firmware when dealing with a "Samsung (System-as-root)" device. Any help you can give would be greatly appreciated for sure.

 

[jrkruse]

This is going to come off as a pretty dumb question but how do I flash Magisk when EFTSU is already installed in the rooted stock version that you have provided above? I have read over the Magisk instructions but I still do not understand what it means exactly (or how it is saying to do it) when it says talks about patching Magisk into the official firmware when dealing with a "Samsung (System-as-root)" device. Any help you can give would be greatly appreciated for sure.

Its best to flash the stock boot.img first then flash magisk zip in Twrp

 

[mrjoshjohnsmith]

Its best to flash the stock boot.img first then flash magisk zip in Twrp

Unless I am misunderstanding what you mean when you say flash the stock boot.img, whenever I have tried to flash the stock boot image I immediately lose TWRP and my unlocked bootloader and then I have to go back through the whole process all over again (which you have made easy but still takes time) and then I end up with the rooted version you have provided but with EFTSU? Am I understanding you correctly?

 

[jrkruse]

Unless I am misunderstanding what you mean when you say flash the stock boot.img, whenever I have tried to flash the stock boot image I immediately lose TWRP and my unlocked bootloader and then I have to go back through the whole process all over again (which you have made easy but still takes time) and then I end up with the rooted version you have provided but with EFTSU? Am I understanding you correctly?

you flash the stock boot img in twrp and then magisk zip and you wont loose anything

 

[mrjoshjohnsmith]

you flash the stock boot img in twrp and then magisk zip and you wont loose anything

Agh of I think I understand what you are saying, I forgot that the Stock firmware from Samsung has different sections in it (including a boot image), sadly I have never tried to demarcate one part of the firmware from another so I have to ask, how do I do that exactly? So I need any particular programs on my PC to be able to do that? Thanks JK

 

[jrkruse]

Agh of I think I understand what you are saying, I forgot that the Stock firmware from Samsung has different sections in it (including a boot image), sadly I have never tried to demarcate one part of the firmware from another so I have to ask, how do I do that exactly? So I need any particular programs on my PC to be able to do that? Thanks JK

just use 7zip and open AP***tar.md5 and highlight boot.img and click extract here

 

[mrjoshjohnsmith]

Thanks JK.

Ok so I did what you suggested with the stock Boot.img from the latest Stock build for the Verizon note 4, which appeared to work. Then I (in the same TWRP Session) installed Magisk 25.2 (latest build of magisk) and cleared delvik/cache and then rebooted to install the Magisk 25.2apk from file manager and although it installed it would just forever hang up on the magisk startup screen (where it shows the magisk mask). So I tried rebooting and a few other things suck as reisntall from both twrp and from booted state, nothing worked. So I tried an older version of magisk (version 21.4 paired with magisk manager version 8.0.7) and then magisk would open, but sadly it was such an old version that there was no option to run the safetynet module (or any modules that I could find) and the Hide option was also missing. So I tried to update to a newer version within the Magisk app and alas as soon as I would it would then start hanging up at start screen again

Any suggestions?

 

[chappatti]

DOWNGRADING FROM ANDROID 9 N910VVRS2CQE1 ROOTED and UNLOCKED BL (HAVOC ROM) -- TO KITKAT 4.4.4

A different question here. It's been ages since I worked on my Note 4. (VZW).

So I have the need to go back down to Stock KitKat 4.4.4 BUT STILL ROOTED AND UNLOCKED BL from what I currently have, which is N910VVRS2CQE1 Android 9 (HAVOC ROM).

1. Do I have to worry about downgrading the BL, even though it is unlocked? That is, can I go straight down to 4.4.4.
2. Does the firmware files you provide contain such an option? I have not downloaded the files yet until I know what I am doing.
3. IS there a TWRP flashable file to get me down to KitKat?
4. Please can you privide some tips how I should proceed?

Many thanks for any assistance! And thanks for the work put in on this comprehensive post!!