How to Root & Unlock Bootloader on Galaxy Note 4!

howto-root-and-unlock-bootloader-verizongalaxynote4-40

After struggling to root my recently bought Verizon Note 4, I’ve finally been able to root and unlock the bootloader after about 10 tries.  It is pretty easy to do once you know how to do it but it took me about a week to get this working correctly, mostly due to the fact that temp root was hard to do with KingRoot and KingORoot.

Anyways, I have been working on this tutorial so anyone can repeat it easily, if you follow step-by-step, you should be able to easily unlock the bootloader and root your Verizon Galaxy Note 4 SM-N910V!

Before we begin, BACKUP EVERYTHING as you may LOSE EVERYTHING if something goes wrong.  Also, make sure Reactivation Lock is OFF if you turned it on before.

Also, you will need a microSD card inserted, make sure you BACKUP EVERYTHING on that microSD card as we will format it later.

Step 1. Install and run “eMMC Brickbug Check” app on Play Store.

howto-root-and-unlock-bootloader-verizongalaxynote4-1

Make sure your CID starts with “15” otherwise this root method will NOT WORK!

howto-root-and-unlock-bootloader-verizongalaxynote4-2

Step 2. Go into Settings->About phone and check that your Android version is 5.1.1 or less.  (It may work on 6.0.1, I have not tried it yet but if you are brave enough, please try it and let me know!)

You may also like...

81 Responses

  1. KSP says:

    Will it work on AT&T note 4 SM-N910A?

  2. Doug says:

    dang killed my note 4 oh well will be without a phone for a while

  3. Nitesh says:

    Max, do you think this will work on Att galaxy s4 on 5.1.1?

  4. Nord says:

    Hello Max, after entering adb devices I do not get connected. I get offline. What do you think I am doing wrong? thanks, Nord

  5. Rodean lindsay says:

    C:\Users\admin\Downloads\fastboot>adb shell
    shell@trltevzw:/ $ su
    CANNOT LINK EXECUTABLE: empty/missing DT_HASH in “su” (built with –hash-style=gnu?)
    i keep getting that error

  6. Joe says:

    We need an att note 4 sm-n910a bootloader work around

  7. kirby johnson says:

    should the command adb push samsung _unlock_n4-fix be n4-2 now?

    • jared daniels says:

      hey kirby, i saw your post and assumed that you were having the same issues i was while running cmd/adb. i changed the commands to, “samsung_unlock_n4-2” and it worked. i’m still in the process of rooting (should be flashing the system only 5.1.1 as soon as it finishes downloading). did you ever have any luck with your root?

      • Ricardo says:

        I tried both “samsung_unlock_n4-fix” and “samsung_unlock_n4-2” but it keeps telling me there is no such file in directory.

        • Michael says:

          You might have missed the part where he said copy the n4-2 file into your fastboot folder. If you don’t move it there, the computer will tell you no such directory.

        • Michael says:

          Also, this version of root is very unstable. After unlocking the bootloader, you might consider skipping the supersu and Oscar kernel and just flashing Cyanogenmod 13 with Gapps (Google Apps package). CM13 includes root access and lots of customization. Plus it won’t overheat your cpu which is what the method in this tutorial is bound to do. I did this on two note 4s and they were both so hot you could barely hold the. The cm13 runs 15 degrees cooler (Celsius) and is literally twice as fast with roughly 25% longer battery life.

        • Michael says:

          If it keeps saying no such file then somehow the files aren’t located in the correct folder. I would delete the fastboot folder and the n4-2 folder and redownload them. Then, verify they are located in your downloads folder (don’t move them) and copy the n4-2 file into the fastboot folder. If those are located as specified, then the directory should take and the file can be applied to the phone via adb.

  8. kirby johnson says:

    when I finally get into the phone shell and type su it says not found?
    But when I run Kingoroot the phone reboots. I DO have a Verizocrap SM-N910V.
    Are there different versions of the same phone/ Android 5.1.1 BTW.

  9. marcvs says:

    Hey very nice your site! But try to make a tutorial for not only a certain version! I have the C version. Thanks.

  10. ashil says:

    Brother i am ashil my phone note 4 n910p i am update marshmallows now my phone no notification panl no data icon and hand free activities problem come and my my zm contact not show what the problem plzz bro i need to help

  11. Jerry says:

    I did this a few months ago and flashed CM13 build 04262016, but cannot go past that version.

    XDA guy told me it’s probably because I’m still using the 5.11 BL and not MM.

    Now I cannot find any MM BL files anywhere after searching for hours! 🙁

    Anyone know where to find the MM BL file for a SM-N910V Note 4?

  12. Mac says:

    The Download for (Android 5.1.1 Stock Firmware for Verizon Note 4 SYSTEM ONLY) is stoping in 60%
    I repeated it no way .. It stops in 60%.
    Please send new download link.

  13. Tyron says:

    I’ve tried downloading the Androi 5.1.1 Stock Firmware SSYSTEM ONLY, but the download page doesnt load after entering the captcha. All it says is”Could not open socket”. Can you please fix this

  14. Jeff says:

    Boot loop right before Step 20. It shows Custom image loading, then keeps rebooting itself.

    • Salazar says:

      I had the same issue. You need to remove your SD card and battery, then reinsert your battery only, not the SD card. It’ll boot normally now. Your SD card likely wasn’t formatted correctly.

      • Jeff says:

        Awesome. I’ll try that when I get home. Thanks for the quick reply!

      • Mr. X says:

        I had dr ketan’s cm13 rom on my 5.1.1 and it all loaded fine. However, the security option in settings where you turn on “Unknown Sources” would not open, it gave an error and exited and also the Verizon signal would not fully activate on it. Other than that, I loved it. I am using Verizon note 4 n910v on the 5.1.1 with unlocked bootloader.

    • Jeff says:

      The fix for me was to use ADB to move SuperSu.zip and Oscar_Kernel.zip, then install in TWRP. That stopped the boot loop and finished the install.

  15. Salazar says:

    @Jeff

    I had the same issue. You need to remove your SD card and battery, then reinsert your battery only, not the SD card. It’ll boot normally now. Your SD card likely wasn’t formatted correctly.

  16. Ralph says:

    I’m about ready to try this method for my Note 4…will this work for Sprint Note 4 running 6.0.1? My CID starts with “15”.

    • Jerry says:

      VERIZON ONLY. (but you can always try it and report your results. 😉 )
      Your Sprint Note 4 should already have an Unlocked Bootloader, so you can already load TWRP and many custom ROMs.

  17. Dan says:

    Im trying to get kingo root working with stock 6.0.1. It wont work, but im thinking its because the file downloaded provided is a “samsung unlock n4-2″. However, your command listing and video shows”samsung unlock n4-2 fix” The added fix is a different script? Could this be why its not working for me? I followed other users commands and got it to upload using the n4-2 version with adb, but it still doesnt work. I’m hoping that the “fix” file would do the trick. Thanks.

    • jared aiono says:

      hey dan, i tried it with 6.0.1 and couldnt get it to work either. i tried changing the, “n4-fix” to, “n4-2″ with no luck. i decided just to flash back to 5.1.1 and it worked fine once the scripts/commands were changed from,” …n4-fix” to, “…n4-2.”

      • Dan says:

        Ok thanks. Ill try doing it that way. Thanks for the help.

      • jared aiono says:

        no problem. im not sure if you were experiencing problems with 6.0.1 but i had tons of issues after the update. with 5.1.1, rooted, stock ROM and the kernal included in this tutorial my SM-910V is running flawlessly. Exposed framework has a stable version for our phones now, so everything is jiving well.

  18. Dan says:

    Yeah 6.0.1 has not been good. Issues and battery drain. Glad to hear the rooted option is good. Im going to give it a shot.

  19. M says:

    Is there anyway to print this all out without all the ads?
    and it only printing one page a time?
    thanks I have tried a few different browser extensions that did not give good results.
    Thanks in advance and thanks for the guide!!

  20. Norbert says:

    After step 22 I get in a boot loop. When booting it says “kernel is no seandroid enforcing” and “bit set warranty bit: enforced.”

    • Jared Aiono says:

      Norbert, are you using the .zip files from this tutorial? Make sure you dont extract the files, just copy the entire .zip to your external micro sd.

    • Norbert says:

      I loaded the factory image 5.1.1 again and started over. Everything was fine until I rebooted after step 22. Max didn’t make it clear if Oscar and BetaSuperSU were supposed to be installed at the same time or not. I installed BetaSuperSU first, rebooted and then installed Oscar. I hope someone out there can help.

      • Demetrius says:

        I know this was a year ago but I’m experiencing the same thing, boot loop after I flash the oscar kernel v0.2 and BETA SuperSU v2.74. Did you ever resolve this issue? I’ve tried and tried. Or anyone else found a solution to this problem? I’m on Verizon with a CID 15, successful TWRP boot loader. Successful 5.1.1 system only. But boot loop on kernel and SU flash.

  21. Norbert says:

    I did a factor reset as suggested by someone at XDA. It is no longer in a constant boot loop, but it will still reboot when I manually start it or reboot it. When it starts it says “unfortunately KNOX has stopped running.” It was doing that before, too.

  22. Norbert says:

    Congratulations to all of you who were able to get this working. However, I’m not one of you. I’ve redone this four times and it always is fine until I install Oscar and BetaSuperSU. Fortunately, the Note 4 is not my daily driver.

  23. Jerry says:

    Who’s Oscar?
    I’ve done 20+ of these Verizon Note 4’s successfully without the help of Oscar…

  24. Jerry says:

    At what step are you stuck on?
    Were you able to unlock the BL?
    Install TWRP?

  25. Norbert says:

    Jerry, yes I was able to unlock the bootloader and install TWRP. Once I’ve loaded the system image, I can reboot several times and everything is stable. As soon as I obtain root by installing the Oscar kernel and BetaSU, the phone becomes unstable. It might boot properly at first, but I still get “XXX has failed to start” where XXX can be any of a number of apps. If I let that go on without first shutting it down, it will go into a boot loop. However, if I do shut it down and restart it will also eventually go into a boot loop. Do you install the Oscar kernel or a different one? Obviously this phone can’t be my daily driver until I get it stable.

    Before I install the rom each time, I wipe data, cache, dalvic cache and system.

  26. Brandon says:

    Has anyone tried this on 6.0.1 before I go and buy the note 7?

    • Jerry says:

      Yes it works on 6.0.1, BUT you MUST downgrade to 5.1.1 THEN upgrade your bootloader and baseband to 6.0.1. (NOT THE ENTIRE ROM)
      Then unlock and load ONLY custom ROMs built for the Marshmallow (6.0.1) bootloader/baseband.

  27. فلاح says:

    pls. i need other link to 5.1.1 Stock Firmware for Verizon Note 4 SYSTEM ONLY

    Because it stops every moment

  28. Francisco says:

    This work’s in the N910A note 4?? Pleas contact me!!!

  29. Francisco says:

    One person coment that he try with this proces and result’s sacefull!!

  30. Gordon says:

    when i put cd fastboot i get (The system cannot find the path specified) any ideas had note3 with jasmine it went swimming now have note 4 with 6.0.1 cant stand it any ideas???

  31. Michael says:

    Hey guys! I did this method to the tee, and everything worked except for two things! My phone wouldn’t attempt to search for cell signal and it would say “kernel is not seandroid enforcing” on the boot screen. I’m not sure if the kernel part is really an issue, but the cell signal certainly is. Can someone please help? :-/ I’ve been trying to root this phone for a couple weeks now and its frustrating to have gotten to that point only to have to reflash it back to stock 5.1.1.

  32. danni says:

    please max answer!!! will this work with the att model? my cid starts with 15 too… if it wont please explain because i heard the att model had the same bootloader lock

    • Jerry says:

      It ONLY works with the Verizon Note 4.

      There was NO Developer Edition released for the ATT Note 4, so it will NOT WORK ON ATT.

  33. Chris says:

    Need some help… So I follow everything and everything work for a week. Then my phone started restarted all the time .at first I thought it was a certain app .only app I have downloaded was root checker pokemon go snapchat and mobile strike .. But the phone would restart everytime I open snap chat . So I delete the app and it continue to restart on its own . I have no clue what the problem could be .. I re-rooted my phone again to see if anything was damage from my first root but the problem continues .. Oh the funny thing now is that my phone wont restart if I have it charging .. I have checked the battery on another note 4 and it works with no issue and the battery from that note 4 I added into mines and the problem continue .problem stops when I have it charging … Has anyone had this problem ?

  34. Guy says:

    10|root@trltevzw:/data/local/tmp # chmod 777 samsung_unlock_n4-fix
    Unable to open samsung_unlock_n4-fix: No such file or directory

    that is the error i get now

    Help

  35. Norbert says:

    My Bluetooth is not working that well on this. It is distorted and has a very short range. Anyone have a fix?

  36. Aaron West says:

    I get stuck at the adb push samsung_unlock_n4-fix /data/local/tmp/ and says there is no such file I have everything downloaded into download folder & extracted can you please help me

  37. Pis sedoff says:

    POS instructions. Followed to an absolute and precise T with a brick as the result. We all know that the “bricking is common” disclaimer is merely a disclaimer but the lack of detailed instructions (i.e., change name to “samsung_unlock_n4-2” rather than “samsung_unlock_n4-fix” or the fact that files SHOULD NOT BE UNZIPPED is not acceptable.

  38. hydrofarmer says:

    when I go to do the first command in the command prompt (adb push samsung_unlock_n4-fix /data/local/tmp/) and hit enter it says “cannot stat ‘samsung_unlock_n4-fix’ no such file or directory” I have copied and pasted the unlock file into the fastboot folder and it doesnt work. I have re downloaded everything to make sure I didnt have corruption as well. My CMD window just keeps saying it cannot find the file or directory. I havent moved these files anywhere from the download folder. I am stuck please help!

  39. Ken says:

    the file has been renamed instead of “fix” at the end it is “2”.
    I’m having problems with all of these the purport to root the n910v, kinroot, kingoroot and anything else I’ve tried cannot root this device!!!!

Leave a Reply

Your email address will not be published. Required fields are marked *