Database Users

Best Guide Online on how to Root your X

I don't feel like reformatting it to make it look good. You can find my post at AllDroid.org or by following this link http://alldroid.org/Default.aspx?tabid=40&g=posts&t=554 let me know if this helped you out. If you follow it to a tee you should have no problems at all.

This is what the link that they OP posted says.
This is a walk-through of how to root your Droid X using the Birdman's method. This walk-though is based off of Rainabba's walk-though but I am going to go into a little bit more detail on some sections to make it more understandable for newer people to rooting.
Before starting this walk-through make sure you do not have any Server Applications running on your computer. This includes stuff like PDAnet's or Some Bluetooth server apps. I noticed that PDAnet will close the adb.exe so you can't do anything. It has also come to my attention that bit-torrent and U-torrent applications may interfere with this process shut those down to.
First you will need to download 3 files, just put these files onto your desktop.
Download the DroidXRoot_v2.zip file from http://alldroid.org/default.aspx?g=posts&t=493
Download the ADBDriver_v3_Google.zip from http://alldroid.org/Defa...40&g=posts&t=495
Download the correct SDK for your OS (Operating System) from http://developer.android.com/sdk/index.html
Now that you have all 3 files downloaded and put onto your desktop its time to do stuff with them.
Extract the DroidXRoot_v2.zip to drive "c:" and just name it "DroidXRoot" so it will look like "c:/DroidXRoot"
Extract the SDK folder into your "DroidXRoot" it doesn't matter what the name of this folder is I used the preset name. This should not look like "c:/DroidXRoot/android-sdk-windows"
Open the "android-sdk-windows" folder and then open the "Tools" folder. From here copy ALL of the files from this folder.
Back out of the "Tools" folder and then out of the "android-sdk-windows" folder. You should now be in "c:/DroidXRoot" Paste those files in here.
Right now Bookmark this page, doing the ADB driver install requires a reboot. This way you can find this post instantly.
Time to install the ADB drivers. For these instructions go to http://alldroid.org/Defa...40&g=posts&t=495 and follow the instructions.
Assuming that the installation went through with no problems, its time to move on.
(Where you see the "Run" at type the command in the quotes ("") but with out the quotes. You should also be able to just copy and past whats inside the quotes if your lazy)
Go to the phone it should still be plugged in from doing the ADB driver install if not plug it in now.
Go to your phone: Home, Menu Button, Settings, Applications, Development: Make sure the "USB debugging" option is enabled/checked.
Hit your Home Button and pull down the Status Bar and click on USB connection: Make sure its set to PC MODE.
Open a command prompt (On Windows 7 and Vista: Start, then type cmd, Right click the cmd and make sure you run as admin. Linix just open the terminal and make sure your running Root through it. If you don't know how to get that good terminal root.)
Ok now that you have your command prompt open Run "cd c:\DroidXRoot"
Run "adb devices" you should see your device listed with a whole bunch of numbers. If you get the message "No devices found" you didn't copy and past the files correct from the tools folder to the "DroidXRoot" folder or you didn't install the driver right from the previous post. If you get the message "adb is not recognized as an internal or external command" you may still have a server file running, make sure there all exited since you rebooted while installing the "adb" drivers. Well if you see your device your doing great keep moving.
Run "adb push Superuser.apk /sdcard/Superuser.apk"
Run "adb push su /sdcard/su"
Run "adb push busybox /sdcard/busybox"
Run "adb push exploid /sqlite_stmt_journals/exploid" If you have any problems with the pushing as in getting the "access denied" response then you did not start in an admin or root and need to restart...
Run "adb shell"
Run "cd sqlite_stmt_journals"
Run "chmod 755 exploid"
Where doing great if you didn't have any problems. From here pick up your phone, and navigate to a screen where you can turn on/off your WiFi with a widget, turn your WiFi on. You will need to turn it off then back on instantly after the following command.
Run "./exploid" turn your Wifi off then turn it back on. Now follow the directions on your command prompt. When that completes you will be back at a shell prompt.
Run "rootshell" You will be prompted for a password enter "secretlol" and press Enter. You are now root but you still have more to do. (You will know that you are in root because your prompt will be a "#" instead of "$")
Run "cp /sdcard/Superuser.apk /system/app/Superuser.apk"
Run "cp /sdcard/su /system/bin/su"
Run "cp /sdcard/busybox /system/bin/busybox"
Run "chmod 4755 /system/bin/su"
Run "chmod 4755 /system/bin/busybox"
Run "rm /system/bin/rootshell"
Run "exit" to drop from root to a non-root user, you will still be logged into the phone.
Run "exit" again to drop back from your phone to your computer command prompt, you should be at "c:\DroidXRoot"
Now you need to confirm that you have established Root:
Run "adb shell"
Run "su" you should now see the "#" sign which indicates you are root)
WATCH YOUR DROID X SCREEN SO YOU CAN ALLOW SUPERUSER ROOT ACCESS!!!
Credits
Sebastian Kramer for this blog post - http://c-skills.blogspot...07/android-trickery.html
Birdman - for editing Sebastians work for the droidx
[mbm] - for answering birdmans many questions while root was tried (and failed xD)
Rainabba - for the original post located at http://alldroid.org/default.aspx?g=posts&t=493
The blog list
Birdman - @mrweeeedbirdman - http://stevenbird.info
Rainabba - @rainabba - http://rainabba.blogspot.com
Videos
Evidence of root: http://tiny.cc/DroidXRootProof
Video tutorial for root: http://tiny.cc/How2RootDroidXVideo
As is always the case with this sort of activity, you do this completely at your own risk. AllDroid, Rainabba, Birdman, and myself take NO responsibility for the outcome.
Edited 7/27/10
Added the section about shutting down the Bit-torrent and U-torrent applications - Thanks sanzy for finding that out.
Fixed a typo in line 21 - Thanks kdkinc fo noticing that.

Alright. Thank you very much.
I'm new to the DroidX. I'm trying to root my friend's phone.
Before updating to the OTA 2. 2 does the DroidX need to be "S-Off" as we Incredible users call it?
Or does this process cover that?
Thank you again.
Sent from my ADR6300 using XDA App

ksidirt said:
Alright. Thank you very much.
I'm new to the DroidX. I'm trying to root my friend's phone.
Before updating to the OTA 2. 2 does the DroidX need to be "S-Off" as we Incredible users call it?
Or does this process cover that?
Thank you again.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Simply put... S-Off does not work for anything other than HTC phones. So your Motorola Droid X will not need S-Off because it's not an option.
As of right now.. the leaked 2.2 is rootable but I don't know if the OTA that Verizon release for the DX will block the root or not.
To be safe, if you really want froyo now... use the leak, I have no problems with it, or you can wait until the OTA is released and confirmed rootable.
Your choice...To each his own

MrDanger said:
Simply put... S-Off does not work for anything other than HTC phones. So your Motorola Droid X will not need S-Off because it's not an option.
As of right now.. the leaked 2.2 is rootable but I don't know if the OTA that Verizon release for the DX will block the root or not.
To be safe, if you really want froyo now... use the leak, I have no problems with it, or you can wait until the OTA is released and confirmed rootable.
Your choice...To each his own
Click to expand...
Click to collapse
Awesome. Thank you.

I ended up using the following:
http://alldroid.org/default.aspx?g=posts&t=553
Worked first try.
If you're going to update to 2.2, you will need to run some additional commands prior to the update via adb or Root Explorer.
I've not had any issues with 2.2 - and I upgraded the day I got my X. No complaints here.
I'm also not really concerned with getting the official OTA -- chances are it (or a version of the update that is compatible with the leaked 2.2) will be found in the wild before long.

[Q] How to flash Rom

Hey, I'm pretty new to the android scene and was needing some help trying to flash froyo or any rom for that matter. I've read over the entire froyo thread and tried the way that ppl had posted but I must be doing something wrong...
Here are the steps that I tried
1)I've gone ahead and rooted the phone using the One-Click root tool provided in another thread
2)Downloaded ODIN and jp2 kernel and kp3 kernel
3)This is where I start getting lost... I opened ODIN and went to boot recovery mode on my vibrant by holding both volume buttons and power... But when I hit start on ODIN, nothing ever happens... All I still see on my phone is
-reboot system now
-reinstall packages
-delete all user data
-delete cache data
I never get a status bar or anything
4)The other thread said don't put anything in PIT and put jp2_kernel.tar as PDA. Do I put anything in phone or csc?
I'm pretty lost after this point... working with SDK/tools? and such...
Could someone please explain in simple terms how to flash this rom? or an easier way for me to flash this or any rom?
Thank you for any and all help

Why boot recovery mode? You should go for Download mode. And what do you exactly want to do? I'd recommend you to read the big FAQ in here http://forum.xda-developers.com/showthread.php?t=723596

Press Volume Down! Not both of them!

I'm trying to flash froyo
Thanks for the link...I see how to get to download mode now.
5. Connect phone in debug mode run SDK/adb and type:
adb push su /system/xbin/
adb push busybox /system/xbin/
adb push Superuser.apk /system/app
adb shell
chmod 4755 /system/xbin/su
chmod 4755 /system/xbin/busybox
chmod 644 /system/app/Superuser.apk
Any idea on how to do this part?
I have SDK downloaded but everytime i run adb.exe it just pulls a command prompt then closes it right away.

captdong3 said:
I'm trying to flash froyo
Thanks for the link...I see how to get to download mode now.
5. Connect phone in debug mode run SDK/adb and type:
adb push su /system/xbin/
adb push busybox /system/xbin/
adb push Superuser.apk /system/app
adb shell
chmod 4755 /system/xbin/su
chmod 4755 /system/xbin/busybox
chmod 644 /system/app/Superuser.apk
Any idea on how to do this part?
I have SDK downloaded but everytime i run adb.exe it just pulls a command prompt then closes it right away.
Click to expand...
Click to collapse
First write "adb shell" and the write everything line by line or make a BAT file containing the first three lines and the write "adb shell" for the chmod commands

You can not simply double click the adb.exe. You'll have to open a command promt first. Change to the directory where the su,busybox,Superuser.apk resides in ("cd C:\folder\where\i\saved\my\files"). From there you can use the commands listed above.

So it seems like Everytime I do
4. Open ODIN and put JP2 kernel as PDA - do not change other settings, flash the phone, do not use any PIT file.
- Reboot.
It bricks my phone... All I get is the phone with the ! point and computer symbol
I have to take it back to download mode and use ODIN again with factory settings...
Any ideas on what I might be doing wrong?

captdong - you should ALWAYS select a PIT file, since this file contains the boot information for your phone. If nothing else is stated, you should use the 513.PIT file for older ROMs. All the new ROMs use 512.PIT
Follow these directions:
1: Download the newest version of Samsung Kies and install that.
2: Download a ROM of your choice from www.samsung-firmwares.com
3: Download the appropiate PIT-file from www.samsung-firmwares.com - it is a little further down the page.
4: Make sure that you have both a MODEM, CSC and CODE (PDA) in the ROM you downloaded - In the future you may only need a CODE file.
5: Reboot your computer (just for safety's sake)
6: Turn your phone in download mode by pressing vol down + home + power but DO NOT connect the phone to your PC yet.
7:Open ODIN and select PIT file, the PDA (CODE), CSC and MODEM from your downloaded ROM
8: Plug in the USB cable to your phone.
9: Press start and DO NOT unplug the phone before the lock screen appears.
If you have any questions feel free to ask .

captdong3 said:
So it seems like Everytime I do
4. Open ODIN and put JP2 kernel as PDA - do not change other settings, flash the phone, do not use any PIT file.
- Reboot.
It bricks my phone... All I get is the phone with the ! point and computer symbol
I have to take it back to download mode and use ODIN again with factory settings...
Any ideas on what I might be doing wrong?
Click to expand...
Click to collapse
it's confusing. Based on what you said, it's look like (the instruction that you got) it deals with flashing modified kernel. Now, if you want to flash modified kernel, MAKE sure that you flash it over the intended firmware. Example, if you want to flash modified JP2 KERNEL, make sure you already got JP2 firmware on the phone.
If you want to flash a complete firmware, then PIT file is A MUST. Just follow Kjeldmis guide.

[GUIDE] Linux Ubuntu: Unlocking Bootloader / Rooting Nexus S

One thing I've noticed is there isn't a lot of documentation for getting set up and unlocking your bootloader on a Linux OS. Setting up your machine to get adb and fastboot to recognize your device takes a tiny bit of extra work on a Linux operating system, but what exactly needs to be done may not be clear to everyone. Whether it's because you're new to the Android SDK/adb, somewhat new to Linux, or can't simply can't seem to find the Vendor Code for the Nexus S. (For those who are looking specifically for this, it's '18d1', and I assume will be the same on all Nexus devices to come; If this means nothing to you right now, read on.)
Disclaimer: I take no responsibility if something goes wrong (if it does, it should be fixable though), Unlocking your bootloader voids your warranty (but you can lock it back), Unlocking the bootloader will wipe your entire phone, including USB Storage; so make a copy of all those family photos and other files you may have put onto the USB storage if you want to keep them.
For the sake of sanity, this guide assumes you are using Ubuntu. If you're using something else (or different applications), there are terminal commands offered, and you probably have an idea on how to adapt the given instructions to your Linux OS.
Preparation: Installing the Android SDK, ADB, Fastboot & Setting Up Your Nexus S to be Recognized
1. Download the Android SDK for Linux: http://dl.google.com/android/android-sdk_r08-linux_86.tgz
2. Save it in a folder of your choice. I chose to keep it in my Downloads folder, myself. If you'd like, you can rename it to the simpler name of 'AndroidSDK.tgz'. The rest of the guide will assume that you did, because I'm lazy, and it makes things simpler; it will also assume you saved it in Downloads. If you feel that you have the intuition to rename and edit the path names based on your own choices, then fine; but if you're utterly lost here, just stick with what I'm doing; download to 'Downloads', rename to 'AndroidSDK.tgz'.
3. Now that you have it, navigate to the folder you downloaded it to, right-click, and click 'Extract' to unzip it. If for some reason you cannot do this, open up a terminal and try this command:
Code:
tar zxvf /home/<your-user-name>/Downloads/AndroidSDK.tgz
You may have to adjust the command if you didn't save it under Downloads or didn't rename the file to AndroidSDK.tgz.
4. Now, we'll install adb and some other software packages by starting up the Android SDK and AVD Manager. Start it either by:
- Navigating to your AndroidSDK folder, going to the 'tools' folder and double-clicking the file called 'android'; if a popup opens asking you what you want to do with it click 'Run'.
- Using this command:
Code:
/home/<your-user-name>/Downloads/AndroidSDK/tools/android
5. In Android SDK and AVD Manager, click on "Available packages". Check the box next to "Android SDK Tools, revision 8" and "Android SDK Platform-tools", and click on "Install Selected" then "Install". When prompted click "Yes" to restart ADB.
6.You should now have a folder in /home/<your-user-name>/Downloads/AndroidSDK/ called "platform-tools".
7. Download fastboot here: http://developer.htc.com/adp.html
- Save it to the aforementioned platform-tools folder.
- Now, navigate to the file, right click it, click 'Properties', go to the 'Permissions' Tab and check 'Allow executing file as program'. Alternatively, run this command:
Code:
chmod +x /home/<your-user-name>/Downloads/AndroidSDK/platform-tools/fastboot
8. Now to set things up so adb and fastboot recognize your Nexus.
- Type this command into a terminal:
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
- Paste this into the blank file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
- Click save and close.
- Then, type the following terminal command:
Code:
sudo restart udev
9. Almost done with preparations! Run this command:
Code:
gedit .bashrc
And add this line to the top of the file:
Code:
#AndroidDev PATH
export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools
Then save the file and close.
10. Download this file and save it to /home/<your-user-name>/Downloads/AndroidSDK/platform-tools: http://www.mediafire.com/?4pe5y906zr67nfh
10.We're ready to go!
Unlocking the Bootloader on your Nexus S and Rooting
Once again, unlocking your bootloader wipes everything on your device, including USB storage. Make a backup of any files you want to keep.
1. On your Nexus S, go to Menu>Settings>Applications. Select "Development" and check the box next to "USB debugging"
2. Power off the phone, and then hold down the Volume Up button and the Power button simultaneously to get into Bootloader/Fastboot mode. Connect your Nexus to the computer via USB.
3. Run this command to unlock your bootloader: (Once again WIPES EVERYTHING!)
Code:
fastboot oem unlock
Hit Enter and on your phone you will be prompted to confirm the action. (Use Volume +/- buttons to choose, power button to confirm choice) Confirm. At this point you will have an unlocked bootloader.
4. Copy/paste the following into the Terminal window:
Code:
fastboot flash recovery /home/<your-user-name>/AndroidSDK/platform-tools/recovery-clockwork-herring.img
5. Use the Volume +/- buttons to choose the Recovery option, then press the power button.
6. In Recovery, go to 'mounts and storage' and choose 'mount USB storage'.
7. Go to this page: http://forum.xda-developers.com/showthread.php?t=682828
About 1/5 of the way down on that page, find the link for "su-2.3.6.1-ef-signed.zip", which is the link for the Froyo version of Superuser. Control-click (right click) on that link and choose "Download Link As..." Save that file to your desktop and then copy it to the main directory of your mounted phone.
8. Click 'Unmount'. Go back to 'mounts and storage' and choose 'mount /system'. Then Go Back and choose 'install zip from sdcard'>'choose zip from sdcard'>su-2.3.6.1-ef-signed.zip
9. When it's finshed installing, reboot. You are now rooted.
Special Thanks
Amin Sabet; I used your Mac guide as a reference and copy/pasted some things for convenience.
Koush; For first posting the unlocking information, developing ClockworkMod Recovery, and ROM Manager. You should probably hook him up with a donation. https://www.paypal.com/us/cgi-bin/w...63663d3faee8d9384d85353843a619606282818e091d0
Michael.B.; for suggesting adding the platform-tools folder to the .bashrc file.
Linus Torvalds; Without which we'd have neither Android nor Ubuntu.
Feel free to leave your comments on the guide below.

Good guide for beginners, I would throw in how to update their path so they can just type adb or fastboot
On Linux, edit your ~/.bash_profile or ~/.bashrc file. Look for a line that sets the PATH environment variable and add the full path to the tools/ and platform-tools directories to it. If you don't see a line setting the path, you can add one:
export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools
Click to expand...
Click to collapse
Be sure to update your username above.

Thanks a lot man, great guide. I didn't get my NS yet but this is gonna be very useful soon
ps: someone please stick this

Michael.B. said:
Good guide for beginners, I would throw in how to update their path so they can just type adb or fastboot
Be sure to update your username above.
Click to expand...
Click to collapse
Thanks for the tip. I added your tip and instructions for marking fastboot as executable.

Stuck due to the thread's usefulness

I forgot to ask: will this work for 64 bit systems?

nicholasbgr said:
I forgot to ask: will this work for 64 bit systems?
Click to expand...
Click to collapse
It should work just fine.

Thanks, got me rooted nice and quickly.

BlackOtaku said:
It should work just fine.
Click to expand...
Click to collapse
Yes but don't forget to install 32 libs.
Thanks for guide
Useful !
I'm waiting for cyanogen ROM so i'll able to install
Cheers

To confirm, yes it works on 64bit. I am running that

Thanks for the confirmation, guys

Good stuff, much appreciated.

I'm working on a simple shell script that should automate some of the more menial tasks while holding the user's hand through the process. I should have it up later today.
UPDATE: It's up! Link on the first page.
Sent from my Nexus S using XDA App

question:
If I use
Code:
fastboot boot recovery.img
instead of
Code:
fastboot flash recovery recovery.img
will i get OTA updates?

confiq said:
question:
If I use
Code:
fastboot boot recovery.img
instead of
Code:
fastboot flash recovery recovery.img
will i get OTA updates?
Click to expand...
Click to collapse
Or, I don't get OTA until i change OS with zip file (ex: su app) ?

confiq said:
Or, I don't get OTA until i change OS with zip file (ex: su app) ?
Click to expand...
Click to collapse
You shouldn't flash the recovery in the boot partition, I think that will cause problems with the phone period. :S
If you flash a custom boot.img (which this guide doesn't cover, though the script will flash Superboot) or kernel like Paul's Superboot, Supercurio's Voodoo Kernel, or Koush's insecure boot.img, OTA updates will fail to install. OTA updates will also reflash your recovery back to stock. One of the devs around here will probably start modifying them so they don't check the boot.img or reflash the recovery though.

Thanks for this! Worked perfectly

Hi all,
I have a strange problem. I can install ClockworkMod recovery but, when I reboot the phone, I don't have superuser installed and su doesn't work. If I reboot the phone, I have to install the recovery every time. It seems it isn't permanent.
Thanks
Matroska

matroska said:
Hi all,
I have a strange problem. I can install ClockworkMod recovery but, when I reboot the phone, I don't have superuser installed and su doesn't work. If I reboot the phone, I have to install the recovery every time. It seems it isn't permanent.
Thanks
Matroska
Click to expand...
Click to collapse
To fix the problem, before selecting zip file, you have to select mount /system. Then go to apply update.zip and proceed as usual.
Thanks

ok im stock
with this part fastboot oem unlock ware i put this code in my terminal of my pc ,,i put the cell in fasboot , i intall everiting if i put that code in my terminal
bash: /home/toshiba/.bashrc: line 2: syntax error near unexpected token `('
bash: /home/toshiba/.bashrc: line 2: `export PATH=${PATH}:/home/<your-user-name>/Downloads/AndroidSDK/tools:/home/<your-user-name>/Downloads/AndroidSDK/platform-tools# ~/.bashrc: executed by bash(1) for non-login shells.'
[email protected]:~$ fastboot oem unlock
fastboot: command not found
[email protected]:~$
what can i do or im doing wrong

UNBRICK ASUS MemoPad 7 ME176C/CX

Enter recovery and sideload CN ROM
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip
To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So you need to give command to recovery to instal zip from location you want.
1. root with rootzenfone.apk
http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
2. turn on usb debuging
3. download ww rom and rename it update.zip
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
4. download es or some other file menager that has root access.
5. go to / (root) and manualy copy update.zip to /data folder
6. Download https://drive.google.com/file/d/0B6...drivesdk&resourcekey=0-W0btfSuQS9kq5iNNsCuWgQ and copy command file to cache/recovery folder
6. open ADB and type line by line:
adb remount
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
after this reboot to recovery and automaticly instal ww rom

This is fantastic, and smart move making a new thread...
Thanks,
sutekh137

And if you're not bricked, but can't update from the old software version. Copy and paste the commands in terminal emulator to force the update. Worked out great. Thanks for the tip.

slayeralive said:
Enter recovery and sideload CN ROM
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip
To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So you need to give command to recovery to instal zip from location you want.
1. root with rootzenfone.apk
http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
2. turn on usb debuging
3. download ww rom and rename it update.zip
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
4. download es or some other file menager that has root access.
5. go to / (root) and manualy copy update.zip to /data folder
6. open ADB and type line by line:
adb remount
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
after this your device will reboot to recovery and automaticly instal ww rom
Click to expand...
Click to collapse
I'm having a lil problem here. Could you elaborate a little more, like in /root. <-- What does this mean? Do i write root or am I to go to root of the tablet's memory? And should I use adb on my PC connecting by usb cable to the tablet? I'm having a little problem understanding some of the steps.
(Remember, it's my sex life that it's in danger here)!

bravesoul said:
I'm having a lil problem here. Could you elaborate a little more, like in /root. <-- What does this mean? Do i write root or am I to go to root of the tablet's memory? And should I use adb on my PC connecting by usb cable to the tablet? I'm having a little problem understanding some of the steps.
(Remember, it's my sex life that it's in danger here)!
Click to expand...
Click to collapse
I would assume root of the device itself as the next step is to put update.zip in /data
(Get me in on the fun. I helped. )

I tried terminal emulator to write adb remount, but just after I wrote it, it gives me an error.
I've put the the update.zip in data folder. but there's like two data folders in my tablet's memory root. Do I put it after mnt or before (I,m using root browser v2.3)? Like in the real root of everything? Another question. Must I use the zip inside another zip of the asus ww rom, or just the unzipped zip file. (LOL, confusing, i know).
(I dunno JerBear, they're very peculiar about what/who they blow)!!

bravesoul said:
I tried terminal emulator to write adb remount, but just after I wrote it, it gives me an error.
I've put the the update.zip in data folder. but there's like two data folders in my tab memory's root. Do I put it after mnt or before?
Click to expand...
Click to collapse
They should be symlinked to the same thing. Let me check...
Well. I only have the data folder that's in the root. Peculiar.
As for the zip file question, go for trial and error. Worst case scenario recovery rejects it.
(We'll work around it )

This is what I get in terminal emulator:

Me176c
bravesoul said:
This is what I get in terminal emulator:
Click to expand...
Click to collapse
You need that command only when you are using ADB over PC

Thanks, but I have other issues.
What zip file should I use? The original we download from ASUS or the zip file inside the original.
JerBear told me to try one or another, but he doesn't know I'm in a place where Internet speed is like 50 Kbps... Which means it takes about two hours to download the original file.
However,(and this will sound strange), if anyone can give me the original names of both the original .182 zip file and the one inside the original, I think I can use a previously (and renamed) downloaded .182 ROM.

Me176c
bravesoul said:
Thanks, but I have other issues.
What zip file should I use? The original we download from ASUS or the zip file inside the original.
JerBear told me to try one or another, but he doesn't know I'm in a place where Internet speed is like 50 Kbps... Which means it takes about two hours to download the original file.
However,(and this will sound strange), if anyone can give me the original names of both the original .182 zip file and the one inside the original, I think I can use a previously (and renamed) downloaded .182 ROM.
Click to expand...
Click to collapse
Use zip inside original.

slayeralive said:
Use zip inside original.
Click to expand...
Click to collapse
So to be clear. I'll use ES File Manager to rename the file (update.zip) and copyit into Root->Data->Turn off the tablet and on again->enter into recovery->in PC I'll use adb->type adb remount and other commands->The tablet will reboot and update into the WW.182 ROM.
Right?

Me176c
bravesoul said:
So to be clear. I'll use ES File Manager to rename the file (update.zip) and copyit into Root->Data->Turn off the tablet and on again->enter into recovery->in PC I'll use adb->type adb remount and other commands->The tablet will reboot and update into the WW.182 ROM.
Right?
Click to expand...
Click to collapse
No man can you read? Do not turn of. Connect to pc and use adb or use terminal. If you are using terminal skip adb commands and start at "su" command. After typing last command it will automaticly reboot to recovery and start instalation than just wait...

slayeralive said:
No man can you read? Do not turn of. Connect to pc and use adb or use terminal. If you are using terminal skip adb commands and start at "su" command. After typing last command it will automaticly reboot to recovery and start instalation than just wait...
Click to expand...
Click to collapse
Ok, ok. Don't get your intelligence in a twist.
Thanks for helping me with my absurd noobiness. :good:

bravesoul said:
Ok, ok. Don't get your intelligence in a twist.
Thanks for helping me with my absurd noobiness. :good:
Click to expand...
Click to collapse
Have fun with your "reward"

Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).

Try again you did somethin wrong

Folow the steps download->extract->rename to update.zip->copy to /data folder->type in terminal

bravesoul said:
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Click to expand...
Click to collapse
If you missd or typed wrong one character in terminal it wont work. Try again.

bravesoul said:
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Click to expand...
Click to collapse
From the top, you must be rooted and you must know what that is.
I used the file from inside the download. I believe it has user in the name.
Rename this file to be update.zip.
Place update.zip into the data folder in the root directory, ie. root/data/update.zip.
Back out of that when it's finished and find the original post with the instructions, touch it and touch the message symbol like you are going to reply.
Copy all of the commands from after su, to the end.
Open terminal emulator, Type su and give root permission at the prompt, touch and paste, you should see what you copied, if you don't, do it again. If you do, touch enter and the process will begin.
Do not do anything until the device reboots COMPLETELY. It will go through several reboots, just wait.
Viola, you will be updated.

[Guide] A noob's guide to Perm Root & TWRP on Verizon Note 4 Retail 5.1.1 (BPA1)

Samsung Galaxy Note 4 – Verizon Wireless – Permanent Root Guide
Disclaimer: I am not 100% sure on what everything here does. These are just a reproduction of the exact steps, files, and programs I used to achieve successful permanent root on my Verizon Note 4 running 5.1.1 (Build Version: BPA1).
I collected all the apps, files, and this guide into one location. You can source these files yourself or you can use the ones I included.
Download Guide & ALL Required Files
Google Drive
Required Files & Programs
Included in download
ADB – minimal_adb_fastboot_v1.3.1_setup.exe
Odin – Odin3 v3.09.exe & Odin3.ini
Samsung Mobile Phone Drivers (Windows Only) – SAMSUNG_USB_Driver_for_Mobile_Phones.exe
TWRP – twrp-3.0.2-0-trltevzw.tar.md5
SuperSU – BETA-SuperSU-v2.71-20160331103524.zip
Bootloader Unlock – samsung_unlock_n4-fix
Kingroot (Temporary Root App) - NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk
Not included in download. These files/programs you must find and download.
Super-Sume Pro – On Google Play Store ($3.99)
https://play.google.com/store/apps/details?id=darkslide.com.supersumepro&hl=en
eMMC Brickbug Check – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en
Root Checker – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Required Tools/Parts/Devices
Samsung Galaxy Note 4 on Verizon updated to 5.1.1 (BPA1)
PC with Windows
Micro USB Cable
MicroSD Card
MicroSD Card Reader/USB Adapter (To Format MicroSD Card)
Step 0: Install Note 4 USB Drivers
If you haven’t done this before at some point it’s as simple as opening the Samsung Mobile Phone Drivers included with this guide.
Step 1: Backup All The Things!
Backup anything that is important to you. You should regularly be doing this anyway.
If you use Two Factor Authentication such as Google Authenticator or Lastpass’ Authenticator I highly suggest you disable this before proceeding as we will be factory resetting your device potentially locking you out of some accounts or making them significantly more difficult to recover access too.
Step 1.5: Disable Encryption
Disable both device and sd card encryption.
Step 2: Factory Reset
Factory Reset your phone and format the sd card.
Step 3: Preparing The Device
Follow the directions below to navigate your device’s settings’ menus to change the required settings.
Settings > Security > Reactivation Lock | Disabled! This is very important!
Settings > Security > Unknown sources | Enabled
Settings > Developer Options > USB debugging | Enabled
Settings > Developer Options > Verify app via USB | Enabled
Move the file NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk included with this guide to your phone’s download folder. When plugged in with a usb cable to your computer it’s usually located at “SAMSUNG-SM-N910V\Phone\Download”.
Step 4: Preparing Your PC
Run minimal_adb_fastboot_v1.3.1_setup.exe included with this guide.
Pay attention to what directory this installs to. It’s usually C:\Program Files (x86)\Minimal ADB and Fastboot.
Step 4.1: Copying Files
samsung_unlock_n4-fix & BETA-SuperSU-v2.71-20160331103524.zip included with this guide need to be copied (the actual files, don’t create shortcuts) to the install folder for ADB (Usually C:\Program Files (x86)\Minimal ADB and Fastboot.). These files must be in the same folder as adb.exe
Step 5: ADB & The Unlocker
Your phone should have been connected already with a usb cable to your computer. We need to verify your phone is found by adb. Open adb.exe located in the folder from Step 4. Once the window (cmd.exe) opens a command line interface saying
Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>
Type in the following command: adb devices
Which should return the following
Code:
List of devices attached
123a12ab device
The 123a12ab is made up. Yours will be specific to your device. If you see something listed like the above adb is working. Now on to the next command to move the unlocker to the phone.
Step 5.1: Send Unlocker to Phone with adb
Type the following command: adb push samsung_unlock_n4-fix /data/local/tmp/
If you get an error it’s because you a) typo b) file isn’t in the folder with adb.exe c) your phone is locked/screen is off d) usb debugging isn’t turned on in settings > developer options.
Step 6: Kingroot For Temp Root
Keep the adb window accessible you will need to be able to switch to it and enter in the commands below quickly as temp root is unstable. Be ready to copy or type them quickly.
On your phone open the app My Files. Click on Device storage > Download > NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk to install Kingroot. After it installs click close, not open. Close all running apps.
Step 6.5: Work Quick With Precision
Open Root Checker so it’s ready to go. Don’t Check yet. Hit the home button and then open Kingroot. In Kingroot scroll down and click the button to start temp root. If you don’t see root successful after a minute or two or four you may need to restart your phone and repeat the process of opening root checker and then Kingroot.
Once you do see successful root click the multi tasking button on the phone to switch over to root checker. Temp root is buggy and may crash. If it does repeat this process again with getting temp root and opening the apps in the correct order.
If you make it into root checker via the multi tasking button it will ask you to grant it root access, click yes, check for root. If it says you have root go to the adb window and type these comamnds in quickly before temp root causes your phone to crash.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
The device will reboot. After reboot, shut the phone down by removing only the battery and usb cable.
Step 7: One More Time
Put the battery and cable back in and turn the phone back on. Now repeat Step 5 & 6.5 but skip Step 5.1 and Step 6. After you send the last adb command and it reboots again pull the battery, sd card, and usb cable. Keep the sd card out! Until you plug it into your computer and format it. It doesn’t matter when you format it if it’s not reporting the correct size. This will be fixed by putting it back into your phone AFTER you format it on your pc and formatting it on the phone.
Step 8: Temp Root A Third Time
If it isn’t already installed go ahead and install Super-Sume Pro.
Close all apps.
Open Super-Sume Pro, click the home button, and open Kingroot.
In Kingroot apply temp root. Click the multi tasking button and switch over to Super-Sume Pro. When it asks for Root grant it. Click the big blue button and follow the instructions. It may take a minute or two. Shut the phone down after it’s done.
Step 9: Odin
Turn the phone on and enter download mode by pressing and holding volume down + power + home. When it’s comes to the screen and says “Downloading” you’re ready to proceed. Open the file included with this guide Odin3 v3.09.exe. In Odin3 where it says Files [Download] click AP and navigate to the folder with this guide and select/open the file twrp-3.0.2-0-trltevzw.tar.md5 and then click Start. Once it finishes it will enter a black screen to reboot. Press and hold these buttons immediately to enter TWRP , volume up + power + home.
Step 10: TWRP & ADB Sideloading
Swipe to allow changes in TWRP. Click Advanced and then ADB Sideload. Swipe to start adb. On your computer open adb.exe from Step 4. On the command line interface in adb.exe
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload BETA-SuperSU-v2.71-20160331103524.zip
The phone will install Super SU, after it is finished we will install the new Kernel before rebooting.
You may need to re-enter ADB Sideload on the phone.
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip
Reboot the phone.
If boots into 5.1.1 open root checker and verify you have root.
Information Sources: felixtaf, ryanbg, kingroot, twrp, emotion, ibowtoandroid, shimp208, & urgodfather
I also posted this on reddit. https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/

It's missing kernel part
Enviado desde mi SM-N910V mediante Tapatalk

Thank you for posting this so clearly! Would Samsung "smart switch" be a viable tool to use for backing up all my apps/app data, home screen setup, etc. before rooting, and still work to import the data after rooting?

EdrickMG said:
It's missing kernel part
Enviado desde mi SM-N910V mediante Tapatalk
Click to expand...
Click to collapse
That kernel flash is optional from what I've seen. That's just what people have been wanting on their phones
Robots_Never_Die said:
Samsung Galaxy Note 4 – Verizon Wireless – Permanent Root Guide
Disclaimer: I am not 100% sure on what everything here does. These are just a reproduction of the exact steps, files, and programs I used to achieve successful permanent root on my Verizon Note 4 running 5.1.1 (Build Version: BPA1).
I collected all the apps, files, and this guide into one location. You can source these files yourself or you can use the ones I included.
Download Guide & ALL Required Files
Google Drive
Torrent File
Torrent Magnet Link
Torrent is hosted on 10gbit/s seedbox.
Required Files & Programs
Included in download
ADB – minimal_adb_fastboot_v1.3.1_setup.exe
Odin – Odin3 v3.09.exe & Odin3.ini
Samsung Mobile Phone Drivers (Windows Only) – SAMSUNG_USB_Driver_for_Mobile_Phones.exe
TWRP – twrp-3.0.2-0-trltevzw.tar.md5
SuperSU – BETA-SuperSU-v2.71-20160331103524.zip
Bootloader Unlock – samsung_unlock_n4-fix
Kingroot (Temporary Root App) - NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk
Not included in download. These files/programs you must find and download.
Super-Sume Pro – On Google Play Store ($3.99)
https://play.google.com/store/apps/details?id=darkslide.com.supersumepro&hl=en
eMMC Brickbug Check – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en
Root Checker – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Required Tools/Parts/Devices
Samsung Galaxy Note 4 on Verizon updated to 5.1.1 (BPA1)
PC with Windows
Micro USB Cable
MicroSD Card
MicroSD Card Reader/USB Adapter (To Format MicroSD Card)
Step 0: Install Note 4 USB Drivers
If you haven’t done this before at some point it’s as simple as opening the Samsung Mobile Phone Drivers included with this guide.
Step 1: Backup All The Things!
Backup anything that is important to you. You should regularly be doing this anyway.
If you use Two Factor Authentication such as Google Authenticator or Lastpass’ Authenticator I highly suggest you disable this before proceeding as we will be factory resetting your device potentially locking you out of some accounts or making them significantly more difficult to recover access too.
Step 1.5: Disable Encryption
Disable both device and sd card encryption.
Step 2: Factory Reset
Factory Reset your phone and format the sd card.
Step 3: Preparing The Device
Follow the directions below to navigate your device’s settings’ menus to change the required settings.
Settings > Security > Reactivation Lock | Disabled! This is very important!
Settings > Security > Unknown sources | Enabled
Settings > Developer Options > USB debugging | Enabled
Settings > Developer Options > Verify app via USB | Enabled
Move the file NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk included with this guide to your phone’s download folder. When plugged in with a usb cable to your computer it’s usually located at “SAMSUNG-SM-N910V\Phone\Download”.
Step 4: Preparing Your PC
Run minimal_adb_fastboot_v1.3.1_setup.exe included with this guide.
Pay attention to what directory this installs to. It’s usually C:\Program Files (x86)\Minimal ADB and Fastboot.
Step 4.1: Copying Files
samsung_unlock_n4-fix & BETA-SuperSU-v2.71-20160331103524.zip included with this guide need to be copied (the actual files, don’t create shortcuts) to the install folder for ADB (Usually C:\Program Files (x86)\Minimal ADB and Fastboot.). These files must be in the same folder as adb.exe
Step 5: ADB & The Unlocker
Your phone should have been connected already with a usb cable to your computer. We need to verify your phone is found by adb. Open adb.exe located in the folder from Step 4. Once the window (cmd.exe) opens a command line interface saying
Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>
Type in the following command: adb devices
Which should return the following
Code:
List of devices attached
123a12ab device
The 123a12ab is made up. Yours will be specific to your device. If you see something listed like the above adb is working. Now on to the next command to move the unlocker to the phone.
Step 5.1: Send Unlocker to Phone with adb
Type the following command: adb push samsung_unlock_n4-fix /data/local/tmp/
If you get an error it’s because you a) typo b) file isn’t in the folder with adb.exe c) your phone is locked/screen is off d) usb debugging isn’t turned on in settings > developer options.
Step 6: Kingroot For Temp Root
Keep the adb window accessible you will need to be able to switch to it and enter in the commands below quickly as temp root is unstable. Be ready to copy or type them quickly.
On your phone open the app My Files. Click on Device storage > Download > NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk to install Kingroot. After it installs click close, not open. Close all running apps.
Step 6.5: Work Quick With Precision
Open Root Checker so it’s ready to go. Don’t Check yet. Hit the home button and then open Kingroot. In Kingroot scroll down and click the button to start temp root. If you don’t see root successful after a minute or two or four you may need to restart your phone and repeat the process of opening root checker and then Kingroot.
Once you do see successful root click the multi tasking button on the phone to switch over to root checker. Temp root is buggy and may crash. If it does repeat this process again with getting temp root and opening the apps in the correct order.
If you make it into root checker via the multi tasking button it will ask you to grant it root access, click yes, check for root. If it says you have root go to the adb window and type these comamnds in quickly before temp root causes your phone to crash.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
The device will reboot. After reboot, shut the phone down by removing only the battery and usb cable.
Step 7: One More Time
Put the battery and cable back in and turn the phone back on. Now repeat Step 5 & 6.5 but skip Step 5.1 and Step 6. After you send the last adb command and it reboots again pull the battery, sd card, and usb cable. Keep the sd card out! Until you plug it into your computer and format it. It doesn’t matter when you format it if it’s not reporting the correct size. This will be fixed by putting it back into your phone AFTER you format it on your pc and formatting it on the phone.
Step 8: Temp Root A Third Time
If it isn’t already installed go ahead and install Super-Sume Pro.
Close all apps.
Open Super-Sume Pro, click the home button, and open Kingroot.
In Kingroot apply temp root. Click the multi tasking button and switch over to Super-Sume Pro. When it asks for Root grant it. Click the big blue button and follow the instructions. It may take a minute or two. Shut the phone down after it’s done.
Step 9: Odin
Turn the phone on and enter download mode by pressing and holding volume down + power + home. When it’s comes to the screen and says “Downloading” you’re ready to proceed. Open the file included with this guide Odin3 v3.09.exe. In Odin3 where it says Files [Download] click AP and navigate to the folder with this guide and select/open the file twrp-3.0.2-0-trltevzw.tar.md5 and then click Start. Once it finishes it will enter a black screen to reboot. Press and hold these buttons immediately to enter TWRP , volume up + power + home.
Step 10: TWRP & ADB Sideloading
Swipe to allow changes in TWRP. Click Advanced and then ADB Sideload. Swipe to start adb. On your computer open adb.exe from Step 4. On the command line interface in adb.exe
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload BETA-SuperSU-v2.71-20160331103524.zip
The phone will install Super SU, after it is finished we will install the new Kernel before rebooting.
You may need to re-enter ADB Sideload on the phone.
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip
Reboot the phone.
If boots into 5.1.1 open root checker and verify you have root.
Information Sources: felixtaf, ryanbg, kingroot, twrp, emotion, ibowtoandroid, shimp208, & urgodfather
I also posted this on reddit. https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/
Click to expand...
Click to collapse
Sent from my SM-N910V using XDA-Developers mobile app

KingVekxin said:
That kernel flash is optional from what I've seen. That's just what people have been wanting on their phones
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
It's optional but have to make like 3 more steps with kernel you just flash it and that's it... 3 less steps

EdrickMG said:
It's missing kernel part
Enviado desde mi SM-N910V mediante Tapatalk
Click to expand...
Click to collapse
It's included in Step 10. I think you may have missed it. It's the very last step. It's also included in the Google Drive folder and torrent.

You shouldn't need to do SuperSuMe. You can use Kingroot for the whole shebang. Also, you will need a kernel for 5.1.x roms otherwise it will bootloop at the Verizon logo.

Robots_Never_Die said:
It's included in Step 10. I think you may have missed it. It's the very last step. It's also included in the Google Drive folder and torrent.
Click to expand...
Click to collapse
Yes you are right I thought u missed it and it's very important... Disregard my previous comment
Enviado desde mi SM-N910V mediante Tapatalk

EdrickMG said:
It's missing kernel part
Enviado desde mi SM-N910V mediante Tapatalk
Click to expand...
Click to collapse
Hyperdimensionalist said:
Thank you for posting this so clearly! Would Samsung "smart switch" be a viable tool to use for backing up all my apps/app data, home screen setup, etc. before rooting, and still work to import the data after rooting?
Click to expand...
Click to collapse
I have not used it. What I did was find every export settings/backup option in apps like nova launcher. I wrote down one time passwords for eligible accounts or disabled 2 factor Auth temporarily. I copied my SD card to my computer, along with all the files in the folders Downloads, Media, DCIM, etc. I exported my contacts and copied the file to my pc. I didn't care about any saved games so I can't help you there. Some people have success with Helium for back ups. Using the pc backup option.

Sizzlechest said:
You shouldn't need to do SuperSuMe. You can use Kingroot for the whole shebang. Also, you will need a kernel for 5.1.x roms otherwise it will bootloop at the Verizon logo.
Click to expand...
Click to collapse
The kernel is included. See comment below from the guy who said I didn't include it.
I heard kingroot sends data to China. So I don't want it on my phone longer than needed.
EdrickMG said:
Yes you are right I thought u missed it and it's very important... Disregard my previous comment
Enviado desde mi SM-N910V mediante Tapatalk
Click to expand...
Click to collapse

isnt kingroot deleted once you do a full wipe before installing a custom rom via twrp?

mta1981 said:
isnt kingroot deleted once you do a full wipe before installing a custom rom via twrp?
Click to expand...
Click to collapse
Correct. Though this is a guide for staying on stock rom with root and the option to change roms at a later point easily.

Robots_Never_Die said:
Samsung Galaxy Note 4 – Verizon Wireless – Permanent Root Guide
Disclaimer: I am not 100% sure on what everything here does. These are just a reproduction of the exact steps, files, and programs I used to achieve successful permanent root on my Verizon Note 4 running 5.1.1 (Build Version: BPA1).
I collected all the apps, files, and this guide into one location. You can source these files yourself or you can use the ones I included.
Download Guide & ALL Required Files
Google Drive
Torrent File
Torrent Magnet Link
Torrent is hosted on 10gbit/s seedbox.
Required Files & Programs
Included in download
ADB – minimal_adb_fastboot_v1.3.1_setup.exe
Odin – Odin3 v3.09.exe & Odin3.ini
Samsung Mobile Phone Drivers (Windows Only) – SAMSUNG_USB_Driver_for_Mobile_Phones.exe
TWRP – twrp-3.0.2-0-trltevzw.tar.md5
SuperSU – BETA-SuperSU-v2.71-20160331103524.zip
Bootloader Unlock – samsung_unlock_n4-fix
Kingroot (Temporary Root App) - NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk
Not included in download. These files/programs you must find and download.
Super-Sume Pro – On Google Play Store ($3.99)
https://play.google.com/store/apps/details?id=darkslide.com.supersumepro&hl=en
eMMC Brickbug Check – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en
Root Checker – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Required Tools/Parts/Devices
Samsung Galaxy Note 4 on Verizon updated to 5.1.1 (BPA1)
PC with Windows
Micro USB Cable
MicroSD Card
MicroSD Card Reader/USB Adapter (To Format MicroSD Card)
Step 0: Install Note 4 USB Drivers
If you haven’t done this before at some point it’s as simple as opening the Samsung Mobile Phone Drivers included with this guide.
Step 1: Backup All The Things!
Backup anything that is important to you. You should regularly be doing this anyway.
If you use Two Factor Authentication such as Google Authenticator or Lastpass’ Authenticator I highly suggest you disable this before proceeding as we will be factory resetting your device potentially locking you out of some accounts or making them significantly more difficult to recover access too.
Step 1.5: Disable Encryption
Disable both device and sd card encryption.
Step 2: Factory Reset
Factory Reset your phone and format the sd card.
Step 3: Preparing The Device
Follow the directions below to navigate your device’s settings’ menus to change the required settings.
Settings > Security > Reactivation Lock | Disabled! This is very important!
Settings > Security > Unknown sources | Enabled
Settings > Developer Options > USB debugging | Enabled
Settings > Developer Options > Verify app via USB | Enabled
Move the file NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk included with this guide to your phone’s download folder. When plugged in with a usb cable to your computer it’s usually located at “SAMSUNG-SM-N910V\Phone\Download”.
Step 4: Preparing Your PC
Run minimal_adb_fastboot_v1.3.1_setup.exe included with this guide.
Pay attention to what directory this installs to. It’s usually C:\Program Files (x86)\Minimal ADB and Fastboot.
Step 4.1: Copying Files
samsung_unlock_n4-fix & BETA-SuperSU-v2.71-20160331103524.zip included with this guide need to be copied (the actual files, don’t create shortcuts) to the install folder for ADB (Usually C:\Program Files (x86)\Minimal ADB and Fastboot.). These files must be in the same folder as adb.exe
Step 5: ADB & The Unlocker
Your phone should have been connected already with a usb cable to your computer. We need to verify your phone is found by adb. Open adb.exe located in the folder from Step 4. Once the window (cmd.exe) opens a command line interface saying
Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>
Type in the following command: adb devices
Which should return the following
Code:
List of devices attached
123a12ab device
The 123a12ab is made up. Yours will be specific to your device. If you see something listed like the above adb is working. Now on to the next command to move the unlocker to the phone.
Step 5.1: Send Unlocker to Phone with adb
Type the following command: adb push samsung_unlock_n4-fix /data/local/tmp/
If you get an error it’s because you a) typo b) file isn’t in the folder with adb.exe c) your phone is locked/screen is off d) usb debugging isn’t turned on in settings > developer options.
Step 6: Kingroot For Temp Root
Keep the adb window accessible you will need to be able to switch to it and enter in the commands below quickly as temp root is unstable. Be ready to copy or type them quickly.
On your phone open the app My Files. Click on Device storage > Download > NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk to install Kingroot. After it installs click close, not open. Close all running apps.
Step 6.5: Work Quick With Precision
Open Root Checker so it’s ready to go. Don’t Check yet. Hit the home button and then open Kingroot. In Kingroot scroll down and click the button to start temp root. If you don’t see root successful after a minute or two or four you may need to restart your phone and repeat the process of opening root checker and then Kingroot.
Once you do see successful root click the multi tasking button on the phone to switch over to root checker. Temp root is buggy and may crash. If it does repeat this process again with getting temp root and opening the apps in the correct order.
If you make it into root checker via the multi tasking button it will ask you to grant it root access, click yes, check for root. If it says you have root go to the adb window and type these comamnds in quickly before temp root causes your phone to crash.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
The device will reboot. After reboot, shut the phone down by removing only the battery and usb cable.
Step 7: One More Time
Put the battery and cable back in and turn the phone back on. Now repeat Step 5 & 6.5 but skip Step 5.1 and Step 6. After you send the last adb command and it reboots again pull the battery, sd card, and usb cable. Keep the sd card out! Until you plug it into your computer and format it. It doesn’t matter when you format it if it’s not reporting the correct size. This will be fixed by putting it back into your phone AFTER you format it on your pc and formatting it on the phone.
Step 8: Temp Root A Third Time
If it isn’t already installed go ahead and install Super-Sume Pro.
Close all apps.
Open Super-Sume Pro, click the home button, and open Kingroot.
In Kingroot apply temp root. Click the multi tasking button and switch over to Super-Sume Pro. When it asks for Root grant it. Click the big blue button and follow the instructions. It may take a minute or two. Shut the phone down after it’s done.
Step 9: Odin
Turn the phone on and enter download mode by pressing and holding volume down + power + home. When it’s comes to the screen and says “Downloading” you’re ready to proceed. Open the file included with this guide Odin3 v3.09.exe. In Odin3 where it says Files [Download] click AP and navigate to the folder with this guide and select/open the file twrp-3.0.2-0-trltevzw.tar.md5 and then click Start. Once it finishes it will enter a black screen to reboot. Press and hold these buttons immediately to enter TWRP , volume up + power + home.
Step 10: TWRP & ADB Sideloading
Swipe to allow changes in TWRP. Click Advanced and then ADB Sideload. Swipe to start adb. On your computer open adb.exe from Step 4. On the command line interface in adb.exe
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload BETA-SuperSU-v2.71-20160331103524.zip
The phone will install Super SU, after it is finished we will install the new Kernel before rebooting.
You may need to re-enter ADB Sideload on the phone.
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip
Reboot the phone.
If boots into 5.1.1 open root checker and verify you have root.
Information Sources: felixtaf, ryanbg, kingroot, twrp, emotion, ibowtoandroid, shimp208, & urgodfather
I also posted this on reddit. https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/
Click to expand...
Click to collapse
Just wanted to say thank you for compiling everything you rock

Thanks to the OP for the effort!
This should be stickied!
Sent from my SM-N910V using Tapatalk

Hey thanks to all devs for all that is being done to make our n4 more lovable. I have everything set up per op. ADB sees my phone and I am able to get root. I enter all the lines of the code and get positive response on all till I get to chmod 777 samsung_unlock_n4-fix. It is in my minimal adb and fastboot folder. It is also unzipped. It all works up to there. Also have drivers installed. Thanks
Sent from my SM-N910V using Tapatalk

having an issue after the command lines, saying this is for some samsung devices only?.....anyone know the fix for this ?

MrMeek said:
having an issue after the command lines, saying this is for some samsung devices only?.....anyone know the fix for this ?
Click to expand...
Click to collapse
What android version are you on? If you are on 4.4.4, update to lollipop and try! Also verify that your emmc starts with 15!

Robots_Never_Die said:
Samsung Galaxy Note 4 – Verizon Wireless – Permanent Root Guide
Disclaimer: I am not 100% sure on what everything here does. These are just a reproduction of the exact steps, files, and programs I used to achieve successful permanent root on my Verizon Note 4 running 5.1.1 (Build Version: BPA1).
I collected all the apps, files, and this guide into one location. You can source these files yourself or you can use the ones I included.
Download Guide & ALL Required Files
Google Drive
Torrent File
Torrent Magnet Link
Torrent is hosted on 10gbit/s seedbox.
Required Files & Programs
Included in download
ADB – minimal_adb_fastboot_v1.3.1_setup.exe
Odin – Odin3 v3.09.exe & Odin3.ini
Samsung Mobile Phone Drivers (Windows Only) – SAMSUNG_USB_Driver_for_Mobile_Phones.exe
TWRP – twrp-3.0.2-0-trltevzw.tar.md5
SuperSU – BETA-SuperSU-v2.71-20160331103524.zip
Bootloader Unlock – samsung_unlock_n4-fix
Kingroot (Temporary Root App) - NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk
Not included in download. These files/programs you must find and download.
Super-Sume Pro – On Google Play Store ($3.99)
https://play.google.com/store/apps/details?id=darkslide.com.supersumepro&hl=en
eMMC Brickbug Check – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en
Root Checker – On Google Play Store (Free)
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Required Tools/Parts/Devices
Samsung Galaxy Note 4 on Verizon updated to 5.1.1 (BPA1)
PC with Windows
Micro USB Cable
MicroSD Card
MicroSD Card Reader/USB Adapter (To Format MicroSD Card)
Step 0: Install Note 4 USB Drivers
If you haven’t done this before at some point it’s as simple as opening the Samsung Mobile Phone Drivers included with this guide.
Step 1: Backup All The Things!
Backup anything that is important to you. You should regularly be doing this anyway.
If you use Two Factor Authentication such as Google Authenticator or Lastpass’ Authenticator I highly suggest you disable this before proceeding as we will be factory resetting your device potentially locking you out of some accounts or making them significantly more difficult to recover access too.
Step 1.5: Disable Encryption
Disable both device and sd card encryption.
Step 2: Factory Reset
Factory Reset your phone and format the sd card.
Step 3: Preparing The Device
Follow the directions below to navigate your device’s settings’ menus to change the required settings.
Settings > Security > Reactivation Lock | Disabled! This is very important!
Settings > Security > Unknown sources | Enabled
Settings > Developer Options > USB debugging | Enabled
Settings > Developer Options > Verify app via USB | Enabled
Move the file NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk included with this guide to your phone’s download folder. When plugged in with a usb cable to your computer it’s usually located at “SAMSUNG-SM-N910V\Phone\Download”.
Step 4: Preparing Your PC
Run minimal_adb_fastboot_v1.3.1_setup.exe included with this guide.
Pay attention to what directory this installs to. It’s usually C:\Program Files (x86)\Minimal ADB and Fastboot.
Step 4.1: Copying Files
samsung_unlock_n4-fix & BETA-SuperSU-v2.71-20160331103524.zip included with this guide need to be copied (the actual files, don’t create shortcuts) to the install folder for ADB (Usually C:\Program Files (x86)\Minimal ADB and Fastboot.). These files must be in the same folder as adb.exe
Step 5: ADB & The Unlocker
Your phone should have been connected already with a usb cable to your computer. We need to verify your phone is found by adb. Open adb.exe located in the folder from Step 4. Once the window (cmd.exe) opens a command line interface saying
Code:
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>
Type in the following command: adb devices
Which should return the following
Code:
List of devices attached
123a12ab device
The 123a12ab is made up. Yours will be specific to your device. If you see something listed like the above adb is working. Now on to the next command to move the unlocker to the phone.
Step 5.1: Send Unlocker to Phone with adb
Type the following command: adb push samsung_unlock_n4-fix /data/local/tmp/
If you get an error it’s because you a) typo b) file isn’t in the folder with adb.exe c) your phone is locked/screen is off d) usb debugging isn’t turned on in settings > developer options.
Step 6: Kingroot For Temp Root
Keep the adb window accessible you will need to be able to switch to it and enter in the commands below quickly as temp root is unstable. Be ready to copy or type them quickly.
On your phone open the app My Files. Click on Device storage > Download > NewKingrootV4.85_C139_B255_en_release_2016_03_29_105203.apk to install Kingroot. After it installs click close, not open. Close all running apps.
Step 6.5: Work Quick With Precision
Open Root Checker so it’s ready to go. Don’t Check yet. Hit the home button and then open Kingroot. In Kingroot scroll down and click the button to start temp root. If you don’t see root successful after a minute or two or four you may need to restart your phone and repeat the process of opening root checker and then Kingroot.
Once you do see successful root click the multi tasking button on the phone to switch over to root checker. Temp root is buggy and may crash. If it does repeat this process again with getting temp root and opening the apps in the correct order.
If you make it into root checker via the multi tasking button it will ask you to grant it root access, click yes, check for root. If it says you have root go to the adb window and type these comamnds in quickly before temp root causes your phone to crash.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
The device will reboot. After reboot, shut the phone down by removing only the battery and usb cable.
Step 7: One More Time
Put the battery and cable back in and turn the phone back on. Now repeat Step 5 & 6.5 but skip Step 5.1 and Step 6. After you send the last adb command and it reboots again pull the battery, sd card, and usb cable. Keep the sd card out! Until you plug it into your computer and format it. It doesn’t matter when you format it if it’s not reporting the correct size. This will be fixed by putting it back into your phone AFTER you format it on your pc and formatting it on the phone.
Step 8: Temp Root A Third Time
If it isn’t already installed go ahead and install Super-Sume Pro.
Close all apps.
Open Super-Sume Pro, click the home button, and open Kingroot.
In Kingroot apply temp root. Click the multi tasking button and switch over to Super-Sume Pro. When it asks for Root grant it. Click the big blue button and follow the instructions. It may take a minute or two. Shut the phone down after it’s done.
Step 9: Odin
Turn the phone on and enter download mode by pressing and holding volume down + power + home. When it’s comes to the screen and says “Downloading” you’re ready to proceed. Open the file included with this guide Odin3 v3.09.exe. In Odin3 where it says Files [Download] click AP and navigate to the folder with this guide and select/open the file twrp-3.0.2-0-trltevzw.tar.md5 and then click Start. Once it finishes it will enter a black screen to reboot. Press and hold these buttons immediately to enter TWRP , volume up + power + home.
Step 10: TWRP & ADB Sideloading
Swipe to allow changes in TWRP. Click Advanced and then ADB Sideload. Swipe to start adb. On your computer open adb.exe from Step 4. On the command line interface in adb.exe
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload BETA-SuperSU-v2.71-20160331103524.zip
The phone will install Super SU, after it is finished we will install the new Kernel before rebooting.
You may need to re-enter ADB Sideload on the phone.
Type the following command: adb devices
Verify your device is there and says sideload.
Type the following command: adb sideload Emotion-TW-5.1.1-nightly-r21-RC1-SM-N910P.zip
Reboot the phone.
If boots into 5.1.1 open root checker and verify you have root.
Information Sources: felixtaf, ryanbg, kingroot, twrp, emotion, ibowtoandroid, shimp208, & urgodfather
I also posted this on reddit. https://www.reddit.com/r/galaxynote4/comments/4f8cgc/guide_a_noobs_guide_to_permanent_rootunlocked/
Click to expand...
Click to collapse
Good one mate...
You can also flash MultiSystem-Kernel_LP-5.1.1 by @hsbadr instead of emotion kernel!
Its SE Permissive and wont show, "Seandroid is not selinux enforcing" error during boot and very snappy!
https://www.androidfilehost.com/?fid=24415232478676428

Yes this is a very good write-up of instructions. But I too, think the flashing the kernel is worth mentioning, considering I went through all this and ended up boot looping because I did not have the kernel, ended up doing it all over again, but a lot smarter the second time around.
?If someone helps you, plz thank them?
Sent from my Tab S SM-T700

Robots_Never_Die said:
Samsung Galaxy Note 4 – Verizon Wireless – Permanent Root Guide
Step 8: Temp Root A Third Time
If it isn’t already installed go ahead and install Super-Sume Pro.
Close all apps.
Open Super-Sume Pro, click the home button, and open Kingroot.
In Kingroot apply temp root. Click the multi tasking button and switch over to Super-Sume Pro. When it asks for Root grant it. Click the big blue button and follow the instructions. It may take a minute or two. Shut the phone down after it’s done.
Click to expand...
Click to collapse
My Super-Sume Pro is stuck on the beginning of Step 2. Is this necessary to run or can I skip out on it.