Database Users

[HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)

This how-to originally started out as a part of the Kindle Fire For Beginners (KFFB) guide, but evolved into this supplemental guide. Because of its origin, this guide assumes the reader is already familiar with KFFB, so reading it is a mandatory prerequisite. Users who post questions in this thread already covered in KFFB will be directed to go back and read it again.
My motives for writing this guide are very much in line with the reasons why I wrote KFFB. I'm hoping users will take the time to learn what they are doing and why they are doing it instead of crossing their fingers and hitting a button on an automated program. While I understand this is the more tedious route to their destination, the knowledge gained here can be used to get back on track when things go wrong or methods inevitably change over time.
The first post in this series details the process of rooting and installing a ROM on a stock device. The two share many of the same preliminary steps, so it makes sense to go over both at the same time.
Preparations
Again, please read Kindle Fire For Beginners before continuing. The conventions introduced in KFFB (e.g. having KFU installed in "C:\kfu") will continue to be used here. Make sure the battery is fully charged. A drained battery is not something you'll ever want to encounter and especially not while in the middle of this process. Create a new folder "C:\kfu\software" on your hard drive. Downloaded software to be installed on the Kindle Fire will be moved there.
Download and install WinMD5Free to some place on your Computer. The developers for most of the software you'll download for the Kindle Fire will provide an MD5 checksum. The checksum is used to verify the integrity of downloaded file, so you can be sure that you haven't gotten a bad download or a corrupted file. Tell WinMD5Free what file you want to check and compare the calculated checksum with the one provided by the developer. If the two match, you can be confident about installing it on your Kindle Fire.
For all required software listed in this document...
Extract (unzip) the files from the compressed archive (unless otherwise noted)
Verify the MD5 checksums if they have been provided
Move them to the C:\kfu\software folder
As with any other how-to guide, it's always a good idea to just read through the document first to get a basic idea of the process involved. Once you are comfortable with the concepts, then go back through and actually perform the steps required.
Getting to fastboot mode
The first step to modifying the Kindle Fire is to get the device into fastboot mode. The easiest and safest way to do this on a stock device is to use a factory cable. The factory cable is safe because it does not require the bootmode to be changed on the device. If something unexpected happens, you'll be able to disconnect the factory cable and reboot straight back into the stock software.
If you choose not to use a factory cable and change the bootmode to get into fastboot mode, you'll be taking a small gamble that you'll be able to issue fastboot commands to the device and change the bootmode back to normal. If you cannot change the bootmode back for some reason (e.g. your device drivers for fastboot mode fail to recognize the device), the device will be stuck in fastboot mode until you find a way to do so. In nearly every case, if you are able to issue the adb commands to get into fastboot mode, you should be able to send the fastboot commands necessary to get out of it. This is just a fair warning out of an abundance of caution... make sure you've done everything to ensure the ADB device drivers have been installed properly.
If you have a factory cable, you can turn the Kindle Fire off and connect the cable to the device, then the computer. The Kindle Fire will power up and put you directly into fastboot mode. You can then skip the rest of this section and go directly to flashing a recovery and bootloader. Otherwise...
Required software:
pokey9000's fbmode​
1) Boot up the Kindle Fire normally and connect a USB cable to the device and computer.
2) Copy pokey9000's fbmode program into a user writeable location on the Kindle Fire...
Code:
adb push C:\kfu\software\fbmode /data/local/tmp/
3) Change the permissions on the fbmode program so it can be executed (run) on the device...
Code:
adb shell chmod 755 /data/local/tmp/fbmode
4) Execute (run) the fbmode program to change the bootmode to fastboot...
Code:
adb shell /data/local/tmp/fbmode
5) Reboot the device...
Code:
adb reboot
Note: In case you are wondering why the "adb shell idme bootmode 4002" command previously discussed in KFFB was not used here, that command requires root privileges not available in the stock configuration. Without root privileges, the above workaround is required.
Installing a recovery and custom bootloader
Required software:
FIREFIREFIRE bootloader
TeamWin Recovery Project (TWRP) recovery
Note: Do not extract the contents of the FIREFIREFIRE bootloader zip file. It will be flashed as-is with TWRP recovery.​
1) Install the TWRP recovery...
Code:
fastboot -i 0x1949 flash recovery C:\kfu\software\openrecovery-twrp-2.2.2.1-blaze.img
2) Set the bootmode to recovery (5001)...
Code:
fastboot -i 0x1949 oem idme bootmode 5001
3) Reboot the device into TWRP recovery. If you used a factory cable to get into fastboot mode, turn off the device by holding down the power button for about 20 seconds. Replace the factory cable with a generic USB cable and the device will start up again automatically. Otherwise...
Code:
fastboot -i 0x1949 reboot
4) Copy the FIREFIREFIRE bootloader zip file to the /sdcard directory on the Kindle Fire...
Code:
adb push C:\kfu\software\fff-u-boot_v1.4a.zip /sdcard/
5) From the main menu of TWRP, press the "Install" button to flash the FFF bootloader onto the bootloader partition. Navigate to the /sdcard directory on the left (should be the default the first time you use TWRP) and select the file from the list on the right. Then simply "Swipe to Confirm Flash" to install.
6) Optional: Make a nandroid backup of the stock software. From the main menu of TWRP, press the "Backup" button and then "Swipe to Back Up" to create a snapshot of the stock system. If you change your mind later about rooting or have second thoughts about the ROM, just "Restore" the backup and return to the stock configuration.
Rooting the stock software
Users interested in flashing a custom ROM may elect to skip this section. Rooting the stock software is not a requirement to flash a custom ROM because the custom ROM will completely overwrite the stock software. However, if you are undecided on the question of rooted stock vs. custom ROM, root the stock software first and try that out for a while. The option to flash a custom ROM will still be available at a later time.
The following method of rooting the Kindle Fire stock software has been tested on 6.3.x and 6.2.x systems. Skip step #5 when rooting 6.2.x systems because the root checker does not exist in those versions.
Required software:
Superuser by ChainsDD
Note: Two separate files will be needed from the contents of this zip file: the su binary from the system\bin folder and the Superuser.apk file from system\app folder.​
This section assumes the device is already booted into TWRP recovery.
1) Remount the /system partition in read/write mode...
Code:
adb shell mount system
2) Copy the su binary onto the device...
Code:
adb push C:\kfu\software\su /system/xbin/
3) Change the owner of the su binary to root...
Code:
adb shell chown root:root /system/xbin/su
4) Set permissions for the su binary to run as root...
Code:
adb shell chmod 6755 /system/xbin/su
5) Disable the root checker by renaming the check_rooted executable...
Code:
adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
6) Change the bootmode back to normal...
Code:
adb shell idme bootmode 4000
7) Reboot the system...
Code:
adb reboot
8) Once the Kindle Fire has rebooted into the system, install the Superuser app...
Code:
adb install C:\kfu\software\Superuser.apk
Congratulations! You have gained root privileges on the stock Kindle Fire software!
Installing a custom ROM
It should go without saying, but users who intend on staying with a rooted stock device need to skip this section. Flashing a custom ROM will overwrite the stock software and leave no trace of the original Kindle Fire interface.
Required software:
Any ROM you choose to install. Check the KF Development List as a starting point.
Note: Do not extract the contents of the ROM archive. The recovery program will need the actual zip file to install.​
This section assumes the device is already booted into TWRP recovery.
1) Carefully read the ROM thread for specific directions and warnings provided by the developer when flashing any new ROM.
2) Copy the custom ROM zip file to the /sdcard directory on the Kindle Fire...
Code:
adb push C:\kfu\software\ROM.zip /sdcard/
You must replace the "ROM.zip" part of the above command to the actual name ROM's zip file you've downloaded.
3) From the main menu of TWRP, "Wipe -> Factory Reset" to remove the existing files in the data and cache partitions that could interfere with the operation of the new system software. A "Factory Reset" will delete any installed apps, software/network settings, etc. It will not touch the /sdcard directory that contains music, eBooks, and files of that nature.
4) From the main menu of TWRP, "Install" to flash the ROM onto your device. Navigate to the /sdcard directory on the left (should be the default the first time you use TWRP) and select the file from the list on the right. Then simply "Swipe to Confirm Flash" to install.
5) From the main menu of TWRP, "Reboot -> System" to boot into the newly flash ROM.
Congratulations! You have completely replaced the stock Kindle Fire software with a custom ROM!
Cleaning up
The zip files pushed onto the /sdcard during installation are only necessary during the installation process and do not need to take up space on the device after completing the install. Use a file manager or mount the storage device on the host computer to delete the files and reclaim the used space.
Coming soon...?
I've got some other topics in mind, but like I did with the KFFB, I'll see how users respond to this post before I continue. Please feel free to comment and make suggestions. I may not respond to everything, but I will keep the helpful comments in mind if/when I decide to expand this how-to guide. Thanks for reading.
Credits
jcase - For providing the basis for this guide and lending his expertise in rooting devices
pokey9000 - For his work on FFF and providing the fbmode exploit
TeamWin and Dees_Troy - For providing the TWRP recovery and continuing its development
ChainsDD - For the Superuser package​

Unroot or Revert to Stock Software
This second post in the series details the procedures required to undo the steps taken in the first. Use it to unroot or revert back to the stock software like it just came from the factory. If you tried out the rooted stock software or a custom ROM for a while, but just prefer the no-frills stock software, you've come to the right place.
Unrooting the stock software
Required software:
None​
This section assumes the device is already booted into the system software.
1) Uninstall the Superuser app
Code:
adb uninstall com.noshufou.android.su
2) Optional: Set the bootmode to recovery. Alternatively, use the recovery selection feature in FFF to boot into recovery during startup without manipulating the bootmode setting here. If you are more comfortable setting the bootmode directly...
Code:
adb shell su -c 'idme bootmode 5001'
3) Reboot the device into recovery...
Code:
adb reboot
4) Mount the data partition...
Code:
adb shell mount data
5) Optional: Delete the files that the Superuser app left behind...
Code:
adb shell rm -rf /data/data/com.noshufou.android.su
6) Mount the system partition...
Code:
adb shell mount system
7) Re-enable the root checker by renaming the check_rooted executable...
Code:
adb shell mv /system/bin/check_rooted.bak /system/bin/check_rooted
8) Delete the su binary from the device...
Code:
adb shell rm /system/xbin/su
9) From the main menu of TWRP, "Reboot -> System" to restart the device into the system software.
Congratulations! You have unrooted the stock Kindle Fire software!
Reverting to stock software
Required software:
Amazon Kindle Fire Software Update​
Warning: Installing the Amazon Kindle Fire Software Update will not only replace the system software, but also overwrite the bootloader and recovery with the stock versions. Any custom bootloader and recovery like FFF and TWRP will be overwritten in the process.
This section assumes the device is already booted into TWRP recovery.
1) Copy the update bin file to the /sdcard as update.zip
Code:
adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip
2) From the main menu of TWRP, "Wipe -> Factory Reset" to remove the existing files in the data and cache partitions that could interfere with the operation of the new system software. A "Factory Reset" will delete any installed apps, software/network settings, etc. It will not touch the /sdcard directory that contains music, eBooks, and files of that nature.
3) From the main menu of TWRP, press the "Install" button to flash the stock software onto your device. Navigate to the /sdcard directory on the left and select the "update.zip" file from the list on the right. Then simply "Swipe to Confirm Flash" to install.
4) Optional: From the main menu of TWRP, "Wipe -> SD Card" to remove all files on the USB mountable storage space. This step will permanently delete all of the files that appear on a computer when the device is connected as a USB storage device.
5) From the main menu of TWRP, "Reboot -> System" to restart the device into the system software.
Congratulations! You have reverted the device to a completely stock Kindle Fire!

KFFB Supplement Post #3
Reserved...

Great explanations!
I wanted to thank you for explaining everything clearly so that people can understand what they are doing when installing their bootloader, recovery and new ROMs.
Thanks again... plee3

Thanks so much!
This worked flawlessly. I had gotten stuck trying to root with KFU (I think the driver is slightly funky in fastboot - so KFU failed to flash either recovery or bootloader and left me in fastboot mode) but using the '-i 0x1949' option with fastboot made everything work perfectly.

Once again you have done a beautiful guide. You are very good at this, and always look forward to more guides from you.
Keep um coming !!
Cheers

Thibor69 said:
Once again you have done a beautiful guide. You are very good at this, and always look forward to more guides from you.
Keep um coming !!
Cheers
Click to expand...
Click to collapse
I know, right?

can i follow this to root 6.3.1?

xXezmacXx said:
can i follow this to root 6.3.1?
Click to expand...
Click to collapse
Yes, it's been tested to work from 6.2.0 and up.

Needs Sticky
Great Work. Gets my vote (and really needs) to be sticky'd.
Thanks for listening
Sincerely,
William
[Kindle Fire: gedeROM v1.25 [KeyClicks Added] {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.

Thanks to all. I'm glad some of the readers got some use out of it.
Docs009 said:
Great Work. Gets my vote (and really needs) to be sticky'd.
Thanks for listening
Sincerely,
William
[Kindle Fire: gedeROM v1.25 [KeyClicks Added] {3.0 Kernel, CM9, Android 4.0.4} - Stock Kernel]
[HTC Evo 4G Supersonic: MikG 3.11 ROM - Chop Suey Custom Kernel]
[Retired: HTC CDMA Hero: Gingerbread Hero Deck ROM - Stock Kernel]
end.
Click to expand...
Click to collapse
If you think this guide will be useful to other users here, you can ask the moderators to review the thread and possibly make it a sticky. I would ask, but it seems a bit... uncouth to nominate my own post for sticky status.
Thanks for reading!

Gotta tell you, there should be some warnings/things to look out for in this guide. If you install all the latest Android SDKs (I pretend to develop in my spare time) it loads the wrong drivers. It will show up as "Android Device" or something like that. The correct drivers have it show up as "Android Composite Device". If you have the SDK in your path (which you need for Eclipse) after the first reboot it might load the wrong drivers again as it did with me which are the wrong ones and basically you won't be able to communicate with the Kindle again.
Took me almost an hour to get this thing off the "Kindle Fire" loading screen because of this problem/unawareness.

ExploreMN said:
Well, I followed the instructions. Got as far as "adb shell reboot" after the fbmode command. Now it just sits at "kindle fire" and shows up as an unknown device in device manager.
Is there anyway to recover from this or did I just junk my fire?
Click to expand...
Click to collapse
Your Kindle Fire is fine... it's in fastboot mode. The computer is most likely the problem. You'll have to make sure your device drivers are working properly, so the computer can send fastboot commands to the device.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

kinfauns said:
Your Kindle Fire is fine... it's in fastboot mode. The computer is most likely the problem. You'll have to make sure your device drivers are working properly, so the computer can send fastboot commands to the device.
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
Thanks Kinfauns. I actually got it fixed without even reading about it...I get a little medieval on things that frustrate me and eventually got it figured out...I edited my post to warn people about what tripped me up!

ExploreMN said:
Gotta tell you, there should be some warnings/things to look out for in this guide. If you install all the latest Android SDKs (I pretend to develop in my spare time) it loads the wrong drivers. It will show up as "Android Device" or something like that. The correct drivers have it show up as "Android Composite Device". If you have the SDK in your path (which you need for Eclipse) after the first reboot it might load the wrong drivers again as it did with me which are the wrong ones and basically you won't be able to communicate with the Kindle again.
Took me almost an hour to get this thing off the "Kindle Fire" loading screen because of this problem/unawareness.
Click to expand...
Click to collapse
Well, I actually tell you at the beginning of this guide to read my guide for beginners. In that guide, I tell you to use the driver installer included in KFU. Any how-to guide has to make some set of assumptions and I made the assumption that you'd actually follow the previous set of instructions before proceeding onto the next. I think you'd agree that I cannot possibly account for every possible deviation a user might take away from my actual directions. If I even attempted such a thing, this guide would turn into Encyclopedia Britannica.
In addition, I also gave you ample warning about putting your device into fastboot mode by manipulating the bootmode. I made a clear suggestion for you to get a factory cable and use it to get into fastboot mode the "safe" way. I've never seen any other rooting guide/utility even make mention of this possibility, so I've gone above and beyond what you'd get anywhere else.
With those things together, I believe I've done the very best I can to minimize the possibility that you might get stuck and have to "get a little medieval" on your device. Regardless, I'm glad you got it figured out. Good luck with the rest of it.

kinfauns said:
Well, I actually tell you at the beginning of this guide to read my guide for beginners. In that guide, I tell you to use the driver installer included in KFU.
Click to expand...
Click to collapse
True enough. Just didn't think it would keep reloading the drivers from the SDK if the SDK was in the path for Eclipse. I'm guessing anyone who set up Eclipse would not think this is an issue and might get stuck like I did...so it's still worth mentioning. (to me at least)

The second installment of this how-to guide has been posted. Included are instructions on unrooting and reverting back to the stock software. Suggestions and comments are always appreciated. Thanks!

Thank you for the excellent guide.
For what it's worth, this guide is very helpful for the admitted "noob" who has somehow failed with a utility like KFU and needs to go back and work through the pieces step by step. Thank you for laying out an instruction manual with enough detail to not only do the steps needed - but also to begin to understand what I'm doing.
I've rooted my KF (thanks to your assistance) so that I could install Swype. I then was able to use OTA-Rootkeeper to "hide" my SU file so that I can use Amazon media on my Fire as I want to, but still get the benefits I wanted from a rooted device (primarily the use of the Android Market, "Google Play", and the use of Swype).
For those that don't *really* want to unroot but do want to still use the Amazon content tools, I HIGHLY recommend the OTA-Rootkeeper utility.
Thanks again!

Kinfauns,
My Kinde Fire was bricked, with power problems. So I did the short trick to repair the bootloaders, using the linux stick and this script here, provided by firekit: usb_fix_parts_and_install_fff_twrp
When I look into device manager i have "Android Phone - Android Composite ADB Interface", at printers and devices the name shows as Kindle.
Can I go direct to these instructions here?
Rooting the stock software
Users interested in flashing a custom ROM may elect to skip this section. Rooting the stock software is not a requirement to flash a custom ROM because the custom ROM will completely overwrite the stock software. However, if you are undecided on the question of rooted stock vs. custom ROM, root the stock software first and try that out for a while. The option to flash a custom ROM will still be available at a later time.
The following method of rooting the Kindle Fire stock software has been tested on 6.3.x and 6.2.x systems. Skip step #5 when rooting 6.2.x systems because the root checker does not exist in those versions.
Required software:
Superuser by ChainsDD
Note: Download the latest zip for Gingerbread/ICS (the filename should end in "efghi-signed.zip"). Two separate files will be needed from the contents of this zip file: the su binary from the system\bin folder and the Superuser.apk file from system\app folder.
This section assumes the device is already booted into TWRP recovery.
1) Remount the /system partition in read/write mode...
Code:
adb shell mount system
2) Copy the su binary onto the device...
Code:
adb push C:\kfu\software\su /system/xbin/
3) Change the owner of the su binary to root...
Code:
adb shell chown root:root /system/xbin/su
4) Set permissions for the su binary to run as root...
Code:
adb shell chmod 6755 /system/xbin/su
5) Disable the root checker by renaming the check_rooted executable...
Code:
adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
6) Change the bootmode back to normal...
Code:
adb shell idme bootmode 4000
7) Reboot the system...
Code:
adb reboot
8) Once the Kindle Fire has rebooted into the system, install the Superuser app...
Code:
adb install C:\kfu\software\Superuser.apk
Congratulations! You have gained root privileges on the stock Kindle Fire software!
Click to expand...
Click to collapse

DuendePaladino said:
Kinfauns,
My Kinde Fire was bricked, with power problems. So I did the short trick to repair the bootloaders, using the linux stick and this script here, provided by firekit: usb_fix_parts_and_install_fff_twrp
When I look into device manager i have "Android Phone - Android Composite ADB Interface", at printers and devices the name shows as Kindle.
Can I go direct to these instructions here?
Click to expand...
Click to collapse
If you used that script in Firekit, you should have FFF 1.2 and TWRP 2.0.0 installed, so technically, yes.... you can boot into TWRP and start following those directions. However, I would recommend that you upgrade your bootloader and recovery to the versions I have in the previous section... FFF 1.4a and TWRP 2.1.1. I won't go into all the reasons why, but they are "better" and likely to keep you out of trouble in the future. Since you already have FFF installed, it will be easy for you to get into fastboot mode. Once you are in fastboot mode, start with flashing TWRP and continue on from there.

[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.

Is there a way to stop H91810p schedule update?

As title says... Just found out about H91810p will make the phone unrootable which is something im planning later on. Sadly the update is scheduled for next restart.
Anything i can do to prevent that?

TempezT said:
As title says... Just found out about H91810p will make the phone unrootable which is something im planning later on. Sadly the update is scheduled for next restart.
Anything i can do to prevent that?
Click to expand...
Click to collapse
if you're rooted, go to /cache and rename update.zip to something else. then create a zero length file using the name update.zip. lastly set the permissions on that file to read only

Here since your on TMO, I compiled this for a buddy of mine through various sources (links provided) on the whole procedure start to finish. Might as well paste it for ya. Props to all original authors, etc...
I just did this on mine, same model, on firmware 10j. If your not on that or i step one will be to flash to the appropriate version. I didnt include that in my notes as myself and my buddy were both on 10j. But theres plenty of threads for that. if your on that, continue on:
Also if you are already flashed and rooted, jump to step #8 for the info regarding OTAs...
====================================================
Specifically for T-Mobile LG V20 H918
Firmware(s) 10I & 10J
====================================================
BOOTLOADER
SOURCES:
*** https://forum.xda-developers.com/v20/how-to/guide-unlock-bootloader-t3488878
*** https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594/page2
*** https://forum.xda-developers.com/showpost.php?p=69897433&postcount=1060
*** https://forum.xda-developers.com/pi...e-pixel-xl-t3466185/post69239012#post69239012
====================================================
Warning: This will delete all your data. You'll also see a large warning every time you turn on the device (attached), this disappears in less than a second.
*Turn on developer mode:
Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
*Turn on OEM unlock and USB debugging:
Settings -> Developer options -> OEM unlock & USB Debugging. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
*Install LG drivers
WIN:
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
MAC:
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
You may need to get an additional .dll for adb to work, if so you can pull it from the pixel add compilation here:
https://xenserver.underpants-gnomes.biz/~romracer/fastboot_adb_pixel.zip
*In Terminal navigate to ADB root:
Type
Code:
adb devices
and authorize your computer on the phone
Type
Code:
adb reboot bootloader
Type
Code:
fastboot devices
and make sure your phone shows up
Type
Code:
fastboot oem unlock
Type
Code:
fastboot getvar all
Should say (bootloader) unlocked:yes
Type
Code:
fastboot reboot
====================================================
TWRP & ROOT:
SOURCES:
http://www.droidviews.com/install-twrp-root-t-mobile-lg-v20/
https://forum.xda-developers.com/v20/how-to/instruction-to-root-h918-10i-t3536472
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
https://build.nethunter.com/android-tools/dirtycow/arm64/
https://github.com/jcadduono/android_external_dirtycow#running
https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
https://download.chainfire.eu/supersu
====================================================
*Prerequisites:
Your LG driver must be up to date. You can have problems with USB 3.1 if so grab latest drivers.
ADB installed, put all 4 recowvery files into the folder:
https://build.nethunter.com/android-tools/dirtycow/arm64/
Download the TWRP “twrp-3.0.2-1-h918” image:
https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
Rename TWRP file to twrp.img and put it into internal storage (sdcard)
Download SuperSU:
https://download.chainfire.eu/supersu
Copy SuperSU onto external memory card (or keep in root of adb, and you could push it back, after formating).
You must be on a 100% stock ROM. Rooted or not.
USB Debugging & OEM unlock allowed in Developer Settings
Bootloader unlocked
Make sure all security/locks are off. No pins, fingerprint, etc…
Steps:
1. Plug your phone to your host computer. Make sure it's in MTP mode.
2. Open your command prompt:
Code:
cd\
cd (right click your mouse and paste the ADB platform-tools address, if using portable pack, where you put the adb folder)
Code:
adb devices
This will show your connected phone
3. Enter the following prompt: (you can simply highlight, copy, right click on command prompt and choose paste):
Code:
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb shell
cd /data/local/tmp
chmod 0777 *
./dirtycow /system/bin/applypatch recowvery-applypatch
* On ADB shell mode, you should see $ on the front. Wait for few…
Code:
./dirtycow /system/bin/app_process64 recowvery-app_process64
* Your phone screen may look weird. Wait for another few minutes. Once finished exit.
Code:
exit
4. Type:
Code:
adb logcat -s recowvery
You should see a lot of lines comes across your screen.
Once you see the ASCII box with the message about giving jcadduomo a hug you can press CTRL+C to exit logcat.
Reboot to the stock recovery:
Code:
adb shell reboot recovery
Restart a session:
Code:
adb shell
You will see a $ sign. Now to check…
Code:
getenforce
It should show Permissive. Thanks Dirty COW!!!
5. Temp Root. Lets patch the boot image:
Code:
cd /data/local/tmp
./dirtycow /system/bin/run-as recowvery-run-as
run-as exec ./recowvery-applypatch boot
Lets run as root
Code:
run-as su
You should have a #, indicating you have root. Ahh my little nix…
6. Flash TWRP
Code:
dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
exit
reboot recovery
The phone should have flashed TWRP and rebooted into recovery.
7. TWRP:
In TWRP swipe to allow modifications. Or TWRP will be replaced next boot!
To disable any encryption perform the factory reset, and the Format Data options.
Install SuperSU from the external SD location.
If you didn’t do a full wipe and reset, you probably want to wipe cache and dalvik.
Reboot to system.
8. Stop them OTA updates!!!
====================================================
https://forum.xda-developers.com/showpost.php?p=72463487&postcount=4237
https://forum.xda-developers.com/showpost.php?p=70795926&postcount=5
====================================================
Open up your dialer interface and type in 277634#*#
This will bring up a hidden menu and then select Wi-Fi test and then select OTA then select disable.
After that you will have to kill the hidden menu and you shouldn't be seeing the annoying OTA icon in your status bar anymore.
In file manager (root browser):
Rename otacerts.zip in /system/etc/security to otacerts.bak.
The full update is found in the cache partition called update.zip.
Move (or delete) the update.zip file from /cache directory (I put it on the sd card).
** dimm0k's method there seems to achieve a similar result, cant hurt to add the step of creating a zero length file after deleting/moving update.zip. I hadnt seen it, thus never did that but I havent had any OTA activity in a few days on mine.
Also in titanium backup (buy it already if you haven’t lol), freeze:
FOTA Update 7.0
Update Center 5.30.12
(I also disabled the com.lge.updatecenter.xxx overlay and themes, cuz whatever... lol)
Reboot and swipe away the notification if its still there. Should have stopped by this point.
======================
There ya go, good luck!

Damn I dont have a computer in hand. Guess i have to wait until im back home in October. Cross fingers this thing don't restart cause that freaking patch is already scheduled.

MDMAchine said:
Here since your on TMO, I compiled this for a buddy of mine through various sources (links provided) on the whole procedure start to finish. Might as well paste it for ya. Props to all original authors, etc...
I just did this on mine, same model, on firmware 10j. If your not on that or i step one will be to flash to the appropriate version. I didnt include that in my notes as myself and my buddy were both on 10j. But theres plenty of threads for that. if your on that, continue on:
Also if you are already flashed and rooted, jump to step #8 for the info regarding OTAs...
====================================================
Specifically for T-Mobile LG V20 H918
Firmware(s) 10I & 10J
====================================================
BOOTLOADER
SOURCES:
*** https://forum.xda-developers.com/v20/how-to/guide-unlock-bootloader-t3488878
*** https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594/page2
*** https://forum.xda-developers.com/showpost.php?p=69897433&postcount=1060
*** https://forum.xda-developers.com/pi...e-pixel-xl-t3466185/post69239012#post69239012
====================================================
Warning: This will delete all your data. You'll also see a large warning every time you turn on the device (attached), this disappears in less than a second.
*Turn on developer mode:
Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
*Turn on OEM unlock and USB debugging:
Settings -> Developer options -> OEM unlock & USB Debugging. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
*Install LG drivers
WIN:
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
MAC:
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
You may need to get an additional .dll for adb to work, if so you can pull it from the pixel add compilation here:
https://xenserver.underpants-gnomes.biz/~romracer/fastboot_adb_pixel.zip
*In Terminal navigate to ADB root:
Type
Code:
adb devices
and authorize your computer on the phone
Type
Code:
adb reboot bootloader
Type
Code:
fastboot devices
and make sure your phone shows up
Type
Code:
fastboot oem unlock
Type
Code:
fastboot getvar all
Should say (bootloader) unlocked:yes
Type
Code:
fastboot reboot
====================================================
TWRP & ROOT:
SOURCES:
http://www.droidviews.com/install-twrp-root-t-mobile-lg-v20/
https://forum.xda-developers.com/v20/how-to/instruction-to-root-h918-10i-t3536472
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
https://build.nethunter.com/android-tools/dirtycow/arm64/
https://github.com/jcadduono/android_external_dirtycow#running
https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
https://download.chainfire.eu/supersu
====================================================
*Prerequisites:
Your LG driver must be up to date. You can have problems with USB 3.1 if so grab latest drivers.
ADB installed, put all 4 recowvery files into the folder:
https://build.nethunter.com/android-tools/dirtycow/arm64/
Download the TWRP “twrp-3.0.2-1-h918” image:
https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
Rename TWRP file to twrp.img and put it into internal storage (sdcard)
Download SuperSU:
https://download.chainfire.eu/supersu
Copy SuperSU onto external memory card (or keep in root of adb, and you could push it back, after formating).
You must be on a 100% stock ROM. Rooted or not.
USB Debugging & OEM unlock allowed in Developer Settings
Bootloader unlocked
Make sure all security/locks are off. No pins, fingerprint, etc…
Steps:
1. Plug your phone to your host computer. Make sure it's in MTP mode.
2. Open your command prompt:
Code:
cd\
cd (right click your mouse and paste the ADB platform-tools address, if using portable pack, where you put the adb folder)
Code:
adb devices
This will show your connected phone
3. Enter the following prompt: (you can simply highlight, copy, right click on command prompt and choose paste):
Code:
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb shell
cd /data/local/tmp
chmod 0777 *
./dirtycow /system/bin/applypatch recowvery-applypatch
* On ADB shell mode, you should see $ on the front. Wait for few…
Code:
./dirtycow /system/bin/app_process64 recowvery-app_process64
* Your phone screen may look weird. Wait for another few minutes. Once finished exit.
Code:
exit
4. Type:
Code:
adb logcat -s recowvery
You should see a lot of lines comes across your screen.
Once you see the ASCII box with the message about giving jcadduomo a hug you can press CTRL+C to exit logcat.
Reboot to the stock recovery:
Code:
adb shell reboot recovery
Restart a session:
Code:
adb shell
You will see a $ sign. Now to check…
Code:
getenforce
It should show Permissive. Thanks Dirty COW!!!
5. Temp Root. Lets patch the boot image:
Code:
cd /data/local/tmp
./dirtycow /system/bin/run-as recowvery-run-as
run-as exec ./recowvery-applypatch boot
Lets run as root
Code:
run-as su
You should have a #, indicating you have root. Ahh my little nix…
6. Flash TWRP
Code:
dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
exit
reboot recovery
The phone should have flashed TWRP and rebooted into recovery.
7. TWRP:
In TWRP swipe to allow modifications. Or TWRP will be replaced next boot!
To disable any encryption perform the factory reset, and the Format Data options.
Install SuperSU from the external SD location.
If you didn’t do a full wipe and reset, you probably want to wipe cache and dalvik.
Reboot to system.
8. Stop them OTA updates!!!
====================================================
https://forum.xda-developers.com/showpost.php?p=72463487&postcount=4237
https://forum.xda-developers.com/showpost.php?p=70795926&postcount=5
====================================================
Open up your dialer interface and type in 277634#*#
This will bring up a hidden menu and then select Wi-Fi test and then select OTA then select disable.
After that you will have to kill the hidden menu and you shouldn't be seeing the annoying OTA icon in your status bar anymore.
In file manager (root browser):
Rename otacerts.zip in /system/etc/security to otacerts.bak.
The full update is found in the cache partition called update.zip.
Move (or delete) the update.zip file from /cache directory (I put it on the sd card).
** dimm0k's method there seems to achieve a similar result, cant hurt to add the step of creating a zero length file after deleting/moving update.zip. I hadnt seen it, thus never did that but I havent had any OTA activity in a few days on mine.
Also in titanium backup (buy it already if you haven’t lol), freeze:
FOTA Update 7.0
Update Center 5.30.12
(I also disabled the com.lge.updatecenter.xxx overlay and themes, cuz whatever... lol)
Reboot and swipe away the notification if its still there. Should have stopped by this point.
======================
There ya go, good luck!
Click to expand...
Click to collapse
Okay someone in my base lend his laptop but its low end(sony viao core2 duo) dunno how well this work for flashing purposes, also I wanted to point before doing the process that my phone was unlocked permanently by tmobile unlock app and wanted to know if this can affect the unlocking or any other function of my v20.

Following those instructions to root will not gid rid of your carrier unlock.

You might be able to go to Settings>>Storage and delete Cached data.

Zacharee1 said:
You might be able to go to Settings>>Storage and delete Cached data.
Click to expand...
Click to collapse
Thank you! Now my other concern is that Im paying Jump! and root would void the warranty so I dont know if I should go ahead and do it regardless cause that silly update is already scheduled.

TempezT said:
Thank you! Now my other concern is that Im paying Jump! and root would void the warranty so I dont know if I should go ahead and do it regardless cause that silly update is already scheduled.
Click to expand...
Click to collapse
You can always restore to stock with the H918. Backup and root.

Zacharee1 said:
You can always restore to stock with the H918. Backup and root.
Click to expand...
Click to collapse
Thanks!
The issue Im having now is that I cant find how to root H91810k which is the current version my phone has besides the schedule update. Any info on that?

You have to find the KDZ for 10d and flash it with LGUP. Then you can use EasyRecowvery to root.
Flashing KDZs will wipe your data, so use LG Bridge to make a backup.

MDMAchine said:
Here since your on TMO, I compiled this for a buddy of mine through various sources (links provided) on the whole procedure start to finish. Might as well paste it for ya. Props to all original authors, etc...
I just did this on mine, same model, on firmware 10j. If your not on that or i step one will be to flash to the appropriate version. I didnt include that in my notes as myself and my buddy were both on 10j. But theres plenty of threads for that. if your on that, continue on.......
Click to expand...
Click to collapse
This is awesome! Thank you!!! You may want to make this its own post it's so helpful. Thanks again!!!!!!!!!

wewantutopia said:
This is awesome! Thank you!!! You may want to make this its own post it's so helpful. Thanks again!!!!!!!!!
Click to expand...
Click to collapse
No problem! Glad it helped, I will probably update the post a bit, and then I'll re-post it to its own thread in a few days. As I noticed this section is a bit disorganized...

MDMAchine said:
8. Stop them OTA updates!!!
====================================================
https://forum.xda-developers.com/showpost.php?p=72463487&postcount=4237
https://forum.xda-developers.com/showpost.php?p=70795926&postcount=5
====================================================
Open up your dialer interface and type in 277634#*#
This will bring up a hidden menu and then select Wi-Fi test and then select OTA then select disable.
After that you will have to kill the hidden menu and you shouldn't be seeing the annoying OTA icon in your status bar anymore.
In file manager (root browser):
Rename otacerts.zip in /system/etc/security to otacerts.bak.
The full update is found in the cache partition called update.zip.
Move (or delete) the update.zip file from /cache directory (I put it on the sd card).
** dimm0k's method there seems to achieve a similar result, cant hurt to add the step of creating a zero length file after deleting/moving update.zip. I hadnt seen it, thus never did that but I havent had any OTA activity in a few days on mine.
Click to expand...
Click to collapse
just wanted to add that SOMETIMES the update.zip is not in /cache. had this happen to me when I had the LGV10 and it just happened to me now. I had recently wiped my device to start from scratch and after initially setting up my device I got the update icon and indeed /cache/update.zip existed. a few reboots later for various reasons the update icon/notification disappeared, as did /cache/update.zip. I thought I was in the clear until last night when I got the update icon/notification again, but this time it was not in /cache. it somehow changed to /data/data/com.google.android.gms/app_download. so if you can't find it in /cache, look there!

[GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and Magisk installation OLD guide

The guide below is depreceatred and should NOT be used.
Please use the guide in this thread instead. - https://forum.xda-developers.com/g6-play/how-to/guide-t3929928
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* thermonuclear war, or you getting fired because the alarms failed and you could not call in.
Please
* Ensure you have an advanced understanding of this device before flashing it! YOU are choosing to make these modifications or your own free will.
*/
This has been confirmed to work on:
XT1922-3 Model
XT1922-4 Model
XT1922-5 Brazilian Model
XT1922-7 Boost Mobile variant of this device with the code name JETER with Android 8.0.0 Build OCP27.91-23
XT1922-9 Model
Links to all boot images have been removed at the request of Motorola.
If you have done an OTA for your Device these boot.img's may not work for your device. We will need a newer boot.img to patch.
Please make backups using TWRP. Right now there is no ROM from moto for these devices that I've found. So proceed with caution.
Just make sure to download the correct boot.img for your device.
If you have another model please follow the first few steps to grab the stock boot.img and post it here and I can patch it.
The steps listed in this process WILL wipe your userdata. If you have anything you need to save back it up first.
Prerequisites:
Unlocked bootloader.
ADB/Fastboot installed on your machine ( https://developer.android.com/studio/releases/platform-tools ) If you have issues with commands make sure you have a current build of ADB and fastboot.
Step 1.) Download _ this TWRP image to the ADB/Fastboot folder on your computer.
Step 2.) Reboot to your bootloader. You can do this by turning on your device and holding power and both volume buttons at the same time.
Step 3.) Once the device reboots to the bootloader type the following from your computer with your phone connected via USB.
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Step 4.) Once TWRP boots from your computer type (it may take a bit to boot because it is trying to decrypt your userdata, but it will fail and prompt for a password. Just click cancel):
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
This will backup your stock boot and recovery images if you to revert to stock later.
Step 5.) Now type:
Code:
adb reboot bootloader
Step 6.) Download either XT1922-9_no_dm-verity_boot.img or XT1922-7_no_dm-verity_boot.img or XT1922-5_no_dm-verity_boot.img or XT1922-4_no_dm-verity_boot.img or XT1922-3_no_dm-verity_boot.img patched dm-verity boot image depending on which device you have and download it into the ADB/Fastboot folder on your computer.
Step 7.) Run the following command from your computer to install the relevant boot image to your device.
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
OR
Code:
fastboot flash boot XT1922-7_no_dm-verity_boot.img
OR
Code:
fastboot flash boot XT1922-5_no_dm-verity_boot.img
OR
Code:
fastboot flash boot XT1922-4_no_dm-verity_boot.img
OR
Code:
fastboot flash boot XT1922-3_no_dm-verity_boot.img
Step 8.) Run the following command from your computer to install the TWRP image to your device.
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
Step 9.) Use the volume keys on the device to select boot to recovery and TWRP will boot up again. When it prompts for a decryption password select cancel again.
Step 10.) From your computer type the following into your command prompt/terminal from your adb/fastboot folder:
Code:
adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor
Step 11.) Download this patched fstab.qcom boot image into the ADB/Fastboot folder on your PC.
Step 12.) Run the following command from command prompt/terminal on your computer:
Code:
adb push fstab.qcom /vendor/etc/fstab.qcom
Step 13.) Next click the "Wipe" button in TWRP and slide "Swipe to Factory Reset" THIS WILL WIPE YOUR DATA ON YOUR PHONE. Ensure you have backup.
Step 14.) Download the Magisk zip file https://github.com/topjohnwu/Magisk/releases/ to your ADB/Fastboot folder.
Step 15.) Run the following command to push the boot image to your device
Code:
adb push Magisk-vXXX.zip /tmp
This will push the Magisk-vXXX.zip to your /tmp folder
Step 16.) Flash Magisk-v16.4.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 17.) Reboot your device
Step 18.) It will say N/A in the top corner of your device for a few seconds. Then it will boot the the Motorola boot screen and you can setup your device as a new phone.
Step 19.) Verify Magisk Manager is installed and the root functionality works.
Step 20.) ???
Step 21.) Profit
Credits:
CodyF86 and his Moto E5 thread for clues as to what it would take to turn off DM-Verity

Reserved

1st....
Thanks for your guide!

i can confirm this works perfectly on my boost model if you do everything exactly as the tutorial say. will be posting screenshots once i re download xda labs on phone. using computer as i type this
---------- Post added at 01:40 AM ---------- Previous post was at 01:00 AM ----------
alright so until this thread is able to work on the app i cant post screenshots but magisk safety net protection works. my kernel adiutor settings stuck on boot. the only things thats not working is being able to uninstall some bloatware and useless system apps. o theres no device encryption on boot anymore which is nice.

Hi @kwiksi1ver,
Thank you for your guide! :highfive:
However, I recomend to do one of these two things:
- Option 1: Add to your guide a link for download the original "boot.img" and "recovery.img". This is required for restoring the original state of the device in case of some error.
- Option 2: Instead of directly "flash" the "recovery.img" in the step 3, you can recommend to use a simple "boot". This doesn't replace the recovery and it's more safe. Then you can instruct to the user to make a backup of his stock boot & recovery partitions. See my guide about G6+: https://forum.xda-developers.com/moto-g6/how-to/moto-g6-root-guide-start-pro-users-t3795197
If you do it, then some users can rollback when some trouble appear. For example, someone here: https://forum.xda-developers.com/showpost.php?p=76789160&postcount=27 needs your help (I have a G6+, so I can't help him).
Regards. :angel:

Sweat
So here is confirming. This works 100% alas i can only confirm the boost version as well.
THANK YOU

I Can confirm this works on the boost mobile variant of the jeter if you follow every step exactly. Magisk works, and safety net is good, and magisk hide works tried Pokemon go and it was successful. Modules I used on my Moto g4 play work on my g6 play. Only thing I've noticed is the bloatware and certain system apps ( like Facebook) refuse to be uninstalled. Screenshots provided. Kernel aduitor settings also stayed when I used the apply on boot option

manos78 said:
Hi @kwiksi1ver,
Thank you for your guide! :highfive:
However, I recomend to do one of these two things:
- Option 1: Add to your guide a link for download the original "boot.img" and "recovery.img". This is required for restoring the original state of the device in case of some error.
- Option 2: Instead of directly "flash" the "recovery.img" in the step 3, you can recommend to use a simple "boot". This doesn't replace the recovery and it's more safe. Then you can instruct to the user to make a backup of his stock boot & recovery partitions. See my guide about G6+: https://forum.xda-developers.com/moto-g6/how-to/moto-g6-root-guide-start-pro-users-t3795197
If you do it, then some users can rollback when some trouble appear. For example, someone here: https://forum.xda-developers.com/showpost.php?p=76789160&postcount=27 needs your help (I have a G6+, so I can't help him).
Regards. :angel:
Click to expand...
Click to collapse
Cheers. I've added the stock files to the second post in the thread and I'll see what I can do about updating with the fastboot boot twrp.img steps and have the user backup their stuff first.
I wish I could help the user your referenced too, but they have different device. They have a G6, I have a G6 Play, and you have a G6+.
ninjakira said:
Only thing I've noticed is the bloatware and certain system apps ( like Facebook) refuse to be uninstalled.
Click to expand...
Click to collapse
You can run "adb shell" then "su" then type "pm disable com.facebook.system", "pm disable com.facebook.katana", "pm disable com.facebook.appmanager", "pm disable com.ironsource.appcloud.oobe", "pm disable com.lookout" etc which will disable the apps.
Alternatively you could use a file manager with root access and delete the various files and reboot. Make sure to keep a backup just in case you need them:
/oem/app/FcbkAppManagerSprint/FcbkAppManagerSprint.apk
/oem/app/FacebookStubSprint/FacebookStubSprint.apk
/oem/priv-app/FcbkInstallerSprint/FcbkInstallerSprint.apk
/oem/priv-app/LookoutSprint/LookoutSprint.apk
/data/app/com.ironsource.appcloud.oobe-mMdx9tUtxjFcQlRhjRmqrQ==/base.apk

kwiksi1ver said:
Cheers. I've added the stock files to the second post in the thread and I'll see what I can do about updating with the fastboot boot twrp.img steps and have the user backup their stuff first.
I wish I could help the user your referenced too, but they have different device. They have a G6, I have a G6 Play, and you have a G6+.
You can run "adb shell" then "su" then type "pm disable com.facebook.system", "pm disable com.facebook.katana", "pm disable com.facebook.appmanager", "pm disable com.ironsource.appcloud.oobe", "pm disable com.lookout" etc which will disable the apps.
Alternatively you could use a file manager with root access and delete the various files and reboot. Make sure to keep a backup just in case you need them:
/oem/app/FcbkAppManagerSprint/FcbkAppManagerSprint.apk
/oem/app/FacebookStubSprint/FacebookStubSprint.apk
/oem/priv-app/FcbkInstallerSprint/FcbkInstallerSprint.apk
/oem/priv-app/LookoutSprint/LookoutSprint.apk
/data/app/com.ironsource.appcloud.oobe-mMdx9tUtxjFcQlRhjRmqrQ==/base.apk
Click to expand...
Click to collapse
I just mainly want to remove Facebook as a system app and remove it's automatic updates and just reinstall it on play store as a regular app lol. I did try a couple root uninstallers and the failed to remove anything from the system. Also used a file manager with root and the results were the samr. The phone automatically resets when there's an attempt at removing system apps. I'll try to get a logcat for ya

I removed it all without any tools except for adb and it doesn't come back. Here is the code I used.
Code:
adb shell
su
cp -r /oem/app/FcbkAppManagerSprint /sdcard
cp -r /oem/app/FacebookStubSprint /sdcard
cp -r /oem/priv-app/FcbkInstallerSprint /sdcard
cp -r /oem/priv-app/LookoutSprint /sdcard
cp -r /data/app/com.ironsource.appcloud.oobe-mMdx9tUtxjFcQlRhjRmqrQ==/base.apk /sdcard
mount -o rw,remount /oem
mount -o rw,remount /data
mount -o rw,remount /system
rm -rf /oem/app/FcbkAppManagerSprint
rm -rf /oem/app/FacebookStubSprint
rm -rf /oem/priv-app/FcbkInstallerSprint
rm -rf /oem/priv-app/LookoutSprint
rm -rf /data/app/com.ironsource.appcloud.oobe-mMdx9tUtxjFcQlRhjRmqrQ==
reboot
If you run all of those command it will backup your annoying APK's to the /sdcard folder if you need them later and then delete the originals and then it reboots your device.
The ironsource appcloud apk is the thing that reinstalls the Sprint bloatware apps over and over again, so removing or disabling that is key to keeping the crap gone.

Will rooting Boost mobile variant unlock the phone ?

piesladowy said:
Will rooting Boost mobile variant unlock the phone ?
Click to expand...
Click to collapse
No it does not sim unlock the phone. Sprint/boost will unlock your sim provided you are with them for a year with the same device

XT1922-5
Hi Guys. I've tried use this procedure on XT1922-5 (Brazilian varianty) however, how I imaginated, it did not work. After the Step 18 my phone stay freez on Motorola boot screen (freezed in M). After that I did a full restore to stock and now phone is ok.
Some one her that have this same Moto g 6 Play variant (XT1922-5) could help me to create a recovery + root process too?
Best regards, GESATEC

Stock Firmware file?
Does any one have a stock frimware file for the
JETER??
I have a 100% stock JETER
If some one can help me I'll post the frimware file ones I get it

FizzyAps said:
Does any one have a stock frimware file for the
JETER??
I have a 100% stock JETER
If some one can help me I'll post the frimware file ones I get it
Click to expand...
Click to collapse
Hi,I believe that there is another Topic with JETER rom:
https://forum.xda-developers.com/moto-g6/development/firmware-stock-moto-g6-play-aljeter-t3792868
Please, check If your stock file os different before post

GESATEC said:
Hi,I believe that there is another Topic with JETER rom:
https://forum.xda-developers.com/moto-g6/development/firmware-stock-moto-g6-play-aljeter-t3792868
Please, check If your stock file os different before post
Click to expand...
Click to collapse
that's got the unlocked model not sprint/boost

JETER
FizzyAps said:
that's got the unlocked model not sprint/boost
Click to expand...
Click to collapse
Ok, I understood . I would lik JETER rom too.
Can u put files on Google Drive?

GESATEC said:
Hi Guys. I've tried use this procedure on XT1922-5 (Brazilian varianty) however, how I imaginated, it did not work. After the Step 18 my phone stay freez on Motorola boot screen (freezed in M). After that I did a full restore to stock and now phone is ok.
Some one her that have this same Moto g 6 Play variant (XT1922-5) could help me to create a recovery + root process too?
Best regards, GESATEC
Click to expand...
Click to collapse
Hi, can you post your stockboot.img file that you backed up during step 4? I can modify that and then I see if we can make it work for the XT1922-5 as well.

kwiksi1ver said:
Hi, can you post your stockboot.img file that you backed up during step 4? I can modify that and then I see if we can make it work for the XT1922-5 as well.
Click to expand...
Click to collapse
Manu thanks. Let me arrive at my home and I'll post it

ninjakira said:
No it does not sim unlock the phone. Sprint/boost will unlock your sim provided you are with them for a year with the same device
Click to expand...
Click to collapse
If you managed to get the boost version onto sprint, in theory it should be eligible for a sim unlock w/50 days of service.

A Noobs Guide ! Verizon Galaxy Note 4 Hardware Repair, Root, install Twrp and ROM's

Hello,
In the process of flashing my note 4, several dozen times, it seems I overheated it while flashing and burned up my memory and got the dreaded memory error,
which requires you to either
1, buy a machine to remove the memory chip, solder in a new one, and reprogram it with a special flashing tool, ( probably several thousand dollars, with acccess to the correct flash file
or
2, buy a new motherboard
So,
I ordered a new motherboard from China, 29.00 on Alibaba.
When i received it it was already setup booted to a running 5.0.1 oem rom, with no user or other programs setup. I could not root it..
I tried several guides and found this one by @hsbadr
Code:
https://forum.xda-developers.com/note-4-verizon/development/howto-bootloader-unlock-upgrade-to-t3398144
In the forum found this link to files needed
Code:
https://forum.xda-developers.com/devdb/project/?id=15720#downloads
with this file
Code:
https://forum.xda-developers.com/devdb/project/dl/?id=18880
and installed it via odin.
Both this guide
Code:
https://forum.xda-developers.com/showthread.php?t=3360883
and @hsbadr guide shows to install kingroot, others show kingoroot, and others show to install a perm root after temp root.
In way with either my oem 5.0.1 or 5.1.1 could I root with kingroot, with any flavor of file! kingoroot would not install on either rom.
HOWEVER i was successful at using the PC kingoroot version with the above file mentioned.
CAUTION #1. make sure you have an antivirus installed to block some spyware. I used AVG with windows 7
CAUTION #2. dont click on any popups except to close them except for the main root screen
Root took about 30 sec with no reboots,
Caution : its a temp root that wont last on reboot
so continue onto
ADB & The Unlocker
install ADB to c:/ADB folder
copy the unlocker file to this folder or add c:/ADB to your path
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 search by your home button in windows
search command or cmd
right click, open as administrator
change directory to your adb folder and
Type in the following command:
Code:
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.
++++ modified, you should have temp root with kingoroot pc version
Step 6: SKIP -----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.
Step 6.5: Work Quick With Precision
++++ modified
Open Root Checker so it’s ready to go. Check .
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 command adb window and type these commands in quickly to verify root
you are now going to enter the linux shell on your device
Code:
adb shell
su
if you see the # prompt you are ready. copy and paste the following
Code:
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 and flash the developer code, shut the phone down by removing only the battery and usb cable.
+++++ edited
Step 7: One More Time to unlock the bootloader !!
Put the battery and cable back in and turn the phone back on.
Now repeat the kingoroot PC to gain temp root
Repeat step 6.5
After you send the last adb command and it will reboot and enter a bootloop . THIS IS NORMAL.
again pull the usb cable.
Pull the Battery
PULL THE SD Card and Keep the sd card out!
The sd card is unusable and needs a reformat, or you can keep it because it has a backup of your locked bootloader
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.
Your bootloader is NOW UNLOCKED
reboot your phone,
and install TWRP via ODIN !!
++++ ignore this it wont work i tried . you need the androind kingroot or kingoroot to work. if u use kingoroot PC to root again, SUPERSUme will not find it .. waste of time
Step 8: Temp Root A Third Time
+++ Modified
Step 8: copy over a rom that you have already downloaded that you want to try
I reccomend this one
Code:
https://forum.xda-developers.com/note-4/snapdragon-dev/oreo-8-1-0-unofficial-lineage-15-1-rom-t3760969
download the rom, and the gapps to your computer and transfer them to a clean SD card.
power off the phone and install the SD card with your rom files
++++ Now were going to do it !!!
Step 9: Odin the newest twrp
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.
Browse to your ODIN folder on your computer , right click, open as administrator the odin.exe file
In Odin3 where it says Files [Download] click AP and navigate to the folder you have the twrp file . select/open the file twrp-3.x.x.x-trltevzw.tar.md5
Turn off the automatic rebooting in the custom tab, DO NOT select the PIT tab
Press start
Once it finishes it will say Success or FAILED
IF it says FAILED start the process over, you didn't unlock the bootloader
Power off the phone with the pull battery method
Press and hold these buttons immediately to enter TWRP ,
volume up + power + home.
++++ this step 10 is outdated. see mine below
++++ There are other methods to root unless you want to root your stock 5.1.1 kernel and stay there
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: ab devices
Verify your device is there and sys 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.
++++++
Step 11: TWRP rom setup the first time by @tripLr
power on phone to recovery by holding down <up> <home> then <power>
boot into TWRP, allow changes.
select backup , change to SD card
BACKUP your rootable device with the bootloader and modem and everything. Name the backup rooted-backup-everything-5.1.1
go to install but DONT install yet
Select your sd card.
You should see the files for the ROM you transferred from your computer
If You dont, you can boot back up, transfer the files appropriately . Then come back here.
Now go to Wipe, Custom, and select everything except external SD card.
THIS IS TO guarantee, no Kingoroot or kingroot stuff is in the phone !!!
WIPE IT TWICE !!!
Now install you ROM, and after your inital setup, come back to TWRP and do a full backup
every time you try a new rom, and get it set up, do a backup. that way you can switch and test to your hearts desire till you run out of SD memory.
The cool thing is you can backup to an external memory device ! more room !
Enjoy
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/[/QUOTE]

tripLr said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: http://xda.tv/post77375464
Click to expand...
Click to collapse
Admin can you delete this I accidentally posted the wrong type