How to Unlock Bootloader and Root Verizon Galaxy Note 2 on VRAMC3!

Download this video for viewing in HD on your smartphone or computer.
Click Here to Download High-Quality HD video to your Smartphone or Computer.

This video was brought to you by Click Here to See at

For those of you who want to install custom ROMs on your Verizon Note 2, you will need to unlock bootloader and install a custom recovery.

Today, we will be unlocking the bootloader using Adam Outler’s “No You Verizon” program and also root it.  This will install TWRP recovery so you can backup, restore, and install custom ROMs.

This is ONLY for Android 4.1.2 with VRAMC3 Build, please do not use on newer Android 4.3 or 4.4.2!

If you don’t need to install custom ROMs, just want “root”, see How to Root Verizon Note 2 instead.

Step 1. Under Settings->About Phone, make sure your build number is “VRAMC3” as shown below.


Step 2. Go to Settings->Developer options.


Step 3. Make sure “Developer options” and “USB debugging” are both checked ON.


Step 4. Connect a micro-USB cable from your Note 2 to your computer.


Step 5. Download the latest version of No You Verizon CASUAL program here.


Step 6. Make sure you have Java installed on your computer.  If you don’t, simply go to and download & install.


Step 7. Open up Device Manager and make sure you have “Samsung Android ADB Interface”.  If you don’t see this, download and install Samsung USB drivers from here.


Step 8. Next, run the No You Verizon CASUAL program by double-clicking on it.


Step 9. If you see “Device Connected”, you are ready to go, click on “Do it”.


Step 10. Your phone should reboot couple times and if done successfully, you will get “Congratulations: Your device is unlocked” message.  If you get any errors, you can reboot your phone and try running the program again.  (Sometimes, it takes me 2 or 3 tries so don’t panic if it doesn’t work the first time, just try it again!)


Step 11. Your Note 2 should have rebooted itself to TWRP recovery.  Choose “Reboot”.


Step 12. Choose “System”.


Step 13. Once rebooted, you should find a new app called “SuperSU” and your Verizon Note 2 is fully rooted now with TWRP recovery installed, congrats!



Q: I am getting Heimdall.exe has stopped working error!
A: This happened to me on my desktop computer.  There’s no way to fix it, just grab another computer with Windows 7 and try it.

Q: Does this work on Windows XP or Windows 8?
A: No, this program only works on Windows 7 or Linux/Ubuntu OS.

Credits – Adam Outler donate to the developer of this tool or hit Thanks on XDA!

You may also like...

42 Responses

  1. Mike says:

    Obviously I’m not sure what happened otherwise I wouldn’t be looking for help but I tried the steps listed on this site to root and unlock bootloader for my Samsung Galaxy Note 2 SCH-I605. I ensured I had the latest and greatest drivers. I used the same cable I had been using already to connect my phone to my laptop and the laptop would see my SCH-I605. I verified that I had Samsung ADB Interface in Device Manager, etc. etc. Everything was perfect for the leap to root the phone. So I started it, my phone showed the Download screen and not to remove target. But then all of a sudden the app came up and said cannot detect device and tried loading the Casual Automated Driver Installer. That’s when everything went awry. The CADI simply ran in an eternal loop and I could not get it to stop. I couldn’t do ANYTHING. I ended up simply having to hit the big red “X” and stop all actions. However my phone still showed the Download screen. I yanked the battery, put it back in and thankfully the phone seems to still work perfectly. HOWEVER!!! My laptop won’t even SEE my phone anymore. I also tried my desktop at work. It won’t see my phone either. It shows the driver installed successfully on Windows but it still doesn’t show the phone ANYWHERE. Hence, I can’t do anything now. Any ideas on what I lost in my phone that is now causing any computer I plug it into not to show that its there in File Explorer OR Device Manager?

  2. Nikki says:

    Worked beautifully, I think people just get confused with the directions a bit. I read your disclaimer on … well in my own terms “stupid people” and you had me cracking up!

    However, just wanted to say thank you very much. Also, if you’d like, I can whip up a more “non-technical” version of your instructions if you like, that’s what I do all day long — things like, telling very smart people with a BS in Nursing, hell, half of them have a masters! My favorite was…. Them: My computer is really slow!!!! Me: I’ll be over to look… Them: I have no clue why it’s doing this!!! Me: “No, see, you can’t run netflix, hulu+, your very important memory hogging database program, your other database, and play solitaire while listening to Pandora and oh look, yahoo message from Potential_Date.01 and …. is that a PoF pop up… yes yes it is… from Potential_Date.02 …. ok for real lady? You seriously want to know why your databases are slow… omg did Microsoft Access just pop up……” Them: “Yes, see how long it took!!” …

    • dodgeabel says:

      Not sure that a disclaimer necessarily implies “stupid people”. There are those that do have the sense to read the directions, which were NOT difficult at all too follow, to the letter and yet still have issues. Whether it be because of their PC/Laptop, their phone itself or even the USB cable as Adam Outler states is the problem 70% of the time. However, when everything is followed to the letter, and a part of the program gets caught in an eternal loop, there is nothing else one can do except to ask the question where the instructions where posted and hope for assistance from either the publisher of that article or possibly someone who may have experienced the same issue and has since found a solution. That said, I am only a Systems Operations Manager so I guess I can easily get confused on directions.

      As for the publisher of the article, Max, I still want to thank you for publishing the article. The instructions were concise and succinct. Even though I am still not able to get my phone to root and unlock the bootloader, your article alone has pointed me in the right direction for a great deal of helpful topics and insight.

  3. Jesé Rodríguez says:


    I had 3 problems which I had to solve:
    1) Antivirus (Avast) was blocking communication between the app (No You Verizon) and the device. I disabled the antivirus permanently until I finished the process. And re-launched the app.

    2) The USB clable. I have 2. The stock large usb cable from the SGNote. And a shorter one from SGS2. When It worked with the shorter one, Idk why…

    3) Be careful. Whe you’re running the app, it sometimes overwrites the Samsung stock ADB drivers to the libUsb drivers needed by heimdall. So, before running the app, open device manager with the device in Download Mode, look for libUsb, right-click and “disable”, and then right-click and “delete” or “remove”. Don’t worry, the app is going to reinstall this later automatically. I should show your Samsung drivers instead.

    After doing this it worked for me. I hope this help someone. Now im running custom ROMs (Jelly Beans ROM Build 18). I really dont like stock ROMs.

    • Jeff says:

      I had problems as well. Had to disable the antivirus and use a shorter, generic data transfer cord from walmart. Just wanted to comment and let others know.

      • Izz Abdullah says:

        Same here. Number 3 fixed my issue – “Unexpected Handshake error” and by disabling and deleting from dev mgr, I was finally able to root.

        • julian says:

          How exactly did you do this? I am getting the same “handshake” error and I can’t understand how you deleted the stuff in step 3.

          • Carl says:

            Thanks so much!! #3 worked for me as well. I was getting the handshake error… for other noobs like me, here’s what I did:

            -Turn off device
            -Put device in download mode (hold vol down, home button, and power button until you reach download mode)
            -Make sure your device is plugged in, in Windows, go to Start, right click Computer, click Properties, click Device Manager. Look for libusb, click its drop down, right click on the entry, disable, then right click again and uninstall
            -Unplug device and pull battery, put battery back in, turn device back on and plug back in
            -Make sure the samsung drivers are installed, should show up in Device manager
            -NOW you are ready to run CASUAL
            -Everything went good from here until I went to reboot > system, it told me it appeared my root permissions were messed up. I just slid the slider at the bottom to fix and all was well.

            Thanks again!

  4. Mike B says:

    I am just getting started, here. The first thing I did was download the NoYouVerizon-GalaxyNote2-CASUAL R515.jar file. Windows anti virus program indicates there is a virus.

    Has anyone else had this issue?

  5. Craig Gins says:

    As i sat these pages, i thought we are only reading similar to the article written in most blogs however when I am now in the heart of the article, I cannot help myself to understand the message that coded in there. It’s surprising that the blogger may make this blog amazing with the quality content that others do not have. I will enjoy this page for much more reading valuable content down the road.

  6. Joe says:

    Sorry for this long post but I wanted to share my unlocking and rooting experience:
    This method DID work for my Verizon Galaxy Note 2. Up until two days ago I thought it would be impossible to root a verizon phone. The version of “No You Verizon Casual Program” does support Windows 8. This was the OS version I used.

    Besides following the instructions listed above, there were few things that I did which may or may not matter. Before I started anything, I installed helium (formerly known as carbon) and backed my phone up. I used helium because it works with unrooted phones. I then restarted my phone. Shut off my (Nova) launcher and used the default touchwiz launcher. It didn’t take me 2 or 3 times…It took me 5 or 6 times to run the “No You Verizon” program and try to unlock the bootloader. I had to turn off my antivirus program. I then checked to make sure that my phone was on debugging mode. Once plugged, I made sure the driver was correct (Samsung ADB).
    I closed up the pop-ups that appeared on the computer (when you first plug in the phone). I don’t have or desire any of the verizon malware…I mean software crap on my computer.

    I then proceeded to follow all of the instructions above listed above by Max…

    The first 4 times, the program indicated errors and it would stop and/or say device disconnected. Every time this happened, I would physically disconnect the phone and restart the phone AND the computer. At least two times I had to pull the battery from the phone to restart.

    The fifth time, the progression bar on the “No You Casual” was at about ¼ to complete and it indicated that the program was “injected.” To me it didn’t look like it did anything so I gave up. I thought maybe it was because of the fact that I was on Windows 8 (Windows answer to a computer virus…wrong place to gripe about that) I entertained the idea of trying it on Linux. After downloading the program on Linux, I thought why run the risk of F^%@ing up my computer by adding a foreign program or worse yet bricking my phone? So I gave up completely and thought another day another time.

    The following day I get a notification saying there was an update for “SUPER USER” and I’m saying to myself “WTF that’s impossible!”

    I never checked my app draw. Super user was installed. So I restart my phone on “safe mode “ but I didn’t see the TWRP program go on . I did everything I mentioned above & followed the instructions on this page. Then I ran the “No You” program (for the 6th time) on my win 8 computer. This time it worked! The bootloader was unlocked, my phone was rooted, and the TWRP was installed as was the Superuser program.

    One thing to note is that when I ran the “no you” program on my windows 8 laptop for the very first time, it asked to install some other program which I did. As mentioned before I shut off my antivirus because it initially detected the “No You” program as malware.

    At the end of the day if you plan on doing this always remember to follow the instructions, use your common sense, if you’re not sure ask questions and research, research, research on forums, youtube, etc. It’s all risky business!

    • Joe says:

      Also lots of thanks to Max Lee and this website…I’ve been enjoying and learning a thing or two from your YT video posts since I got my Galaxy Note 2!!!

  7. larry says:

    Hey I have tried and tried but I can’t get it to work. I keep getting Error: failed to access device. libusb error:-12. Can anyone help. I have followed the instructions to the t. I don’t know what else to do.

  8. Deshawn says:

    I’m getting this error message

    push “$ZIPFILEexynos-abuse” /data/local/tmp/


    • Max Lee says:

      Try on another computer if having trouble I had to do that as my main desktop didnt work well no matter what i tried.

      • Deshawn says:

        No I actually had to disable disable the Microsoft Security Essentials. It actually says “Real-time protection” and I just had to turn that off and then it worked. I think you should edit that in the instructions. It would really help others.

  9. Deshawn says:

    No I actually had to disable disable the Microsoft Security Essentials. It actually says “Real-time protection” and I just had to turn that off and then it worked. I think you should edit that in the instructions. It would really help others.

  10. jmac says:

    How do you unlock bootloader if your already rooted. I have i605VRALJB installed. I had to install through ODIN using pit and a root66 recovery file because thats the only one that would work and anything else I try leads me to the yellow triangle when I reboot . I cant even enter recovery through volume up/home/power

  11. ryan says:

    how long should it be “initialising protocol…”?

  12. irving says:

    im having a bit of a problem. casual does its thing but it doesnt boot into recovery “Your device should be rebooting into Android now.
    Waiting for ADB device connection. When Windows 7 recognizes the device, we will continue. Don’t touch anything.” thats all it does. the phone turns on but it doesnt let me flash roms and if i try to go to recovery manually it doesnt take me to twrp, it takes me to android system recovery under manual mode with a red triangle. and if i try to flash a rom it says “filesystem check failed”.. help please

  13. Izz Abdullah says:

    @Jesé Rodríguez said:

    This drove me nuts getting hung up on “Unexpected Handshake Error and this approach fixed that problem for me.

    Thanks all!

  14. Jae says:

    what if I’m already rooted by using the method you posted on this website? How would I unlock bootloader then?

  15. tyler says:

    im stuck on initialising protocol…..

  16. Brandon says:


    Is there any way to root with Windows Vista?

  17. Dan Savercool says:

    Verizon sent a network update the other night when my phone was on. When it was done and the phone automatically rebooted, the TWRP recovery screen came up. I could not get it to move off that screen, although some of the icons on the recovery screen did work, such as Wipe and Restore. Everything on my phone was removed when I started pressing icons. I went into Play Store, downloaded my copy of Titanium Backup Pro, and ran the restore function (my restore file was safe on the SD card) to get everything back onto my Note 2. In doing all this, did I lose the bootloader unlock and rooting? How can I check to see if this went back to Verizon’s control?

  18. Mauro Arias says:

    Hello, i have a Samsung Galaxy Note II SCH-I605 Verizon runing on JB 4.3 but i just can’t get the bootloader unlock, i can’t install CWM or TWCP, is there any software that can be used to unlock my bootloader?

  19. steve says:

    I have a note 2 with a baseband of “VRUEMJ9” is there a boot loader unlock for this ?? or will this one work ?

    • rock says:

      I’m having the same problem…it says safe root is the only way with our firmware. How do we flash into recovery or twrp.

  20. Velda says:

    I almost never leave remarks, however i did a few searching and wound up here How to Unlock Bootloader and Root Verizon Galaxy Note 2 on VRAMC3!
    | Galaxy Note 2 Root!. And I do have a few questions for you if you do not
    mind. Is it just me or does it look as if like a few of the
    comments look like written by brain dead individuals? 😛 And, if you are writing
    on additional sites, I would like to keep up with anything new
    you have to post. Would you make a list of all of all your shared pages like your linkedin profile, Facebook page or twitter feed?

  21. Claudia says:

    I am currently on MC3, but STOCK Rooted.
    Do I need to remove root before unlocking bootloader?

  22. saw thein says:

    Ihave little and poorenglish

  23. Mario says:

    Do have an unlock bootloader solution for i605 VRUEMJ9? Thanks

  24. mdenoss says:

    I tried different micro usb cables, my laptop and desktop. None will let me get past:
    ERROR: Failed to access device. libusb error. -12

    But it reboots the phone into downloading mode and just sits.

  25. Hiroshi Irizarry says:

    This will unlock the bootloader on VRAMC3 and root it at the same time with adams no you Verizon program? Correct. So it will do both jobs at the same time?

  26. Hiroshi Irizarry says:

    Is there an unlock bootloader solution for 4.4.2 build ND7?

Leave a Reply

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