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

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

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

Related

FULL Disk ENCRYPTION + ROOT Easy steps >>> HOW TO root & encrypt entire device

FULL Disk ENCRYPTION + ROOT Easy steps >>> HOW TO root & encrypt entire device
How to encrypt your rooted device. I wrote these instructions based on my Note 4 (T-Mobile branded N910T3 ) BUT they will work for ANY device!
THE SHORT OF IT:
YOU SIMPLY NEED TO ECRYPT YOUR DEVICE FIRST PRIOR TO ROOTING. YOU CAN ROOT IT AFTER IT IS ENCRYPTED, NOT BEFORE.
tested on Android 4, 5, & 6.
Once you root or install various roms you lose the ability to encrypt your device. This issue manifests itself in the form of either hanging, rebooting, or the animation just sitting there but not actually doing anything when you try to use the full disk encryption feature built into all modern versions of android. Below are the steps on how to get this native encryption feature working while still maintaining your root & favorite rom.
Credit goes to chatty kathy, i mean bruzzy who graciously and verbosely provided instructions on how to encrypt my rooted 12.2" Samsung Galaxy Note Pro (AT&T branded SM-P907A) here: http://forum.xda-developers.com/showthread.php?t=2791587
McFood on androidforums.com also reiterated much of the same here: http://androidforums.com/threads/how-to-encrypt-a-rooted-device.866968/
As usual: Use this guide at your own risk!
Quick Overview:
Unroot if rooted. Encrypt. Reroot. The only thing special is that you have to manually kick start SuperSU when rooting after the encryption is in affect. See steps 12 & 13.
INSTRUCTIONS:
-------------------
0. Make a backup to your external SD card of your entire system FIRST such as a nandroid backup via a custom recovery (Philz Touch, TWRP, etc). I even do modem, etc. just in case you ever need.
1. Ensure your device is not rooted and also not encrypted (if already rooted, skip to step 3; if already encrypted, decrypt or do a factory-reset - don't try CF-Auto-Root on an encrypted device, it'll soft-brick)
2. Root the device (I used this sticky: http://forum.xda-developers.com/not...y-steps-n910t3-dofc-dog1-how-to-root-t3177225 )
3. Temporarily un-root the device (when using SuperSU: go to Settings and remove the tick at the option "Activate Superuser")
4. Reboot
5. Activate the device encryption (the battery must be at least at 80% and the device must be plugged in the wall charger)
6. The device will restart after a short period of time and start the encryption (this will take some time, but you should see a progress bar indicating how far it is)
7. After the encryption is finished the device will reboot and ask for the password, just log in
8. If not yet done, flash a custom recovery where you have console access or can use ADB as root (I used TWRP)
9. Boot into recovery. (POWER + VOLUME UP + HOME button together at the same time)
10. Mount /system (it's not mounted automatically, at least not in the version I used - TWRP 2.7.1.0).
11. Open a console or ADB shell to run the basic linux commands in red in the next two steps on the phone ((In TWRP it is under Advanced & then Terminal Command and start the console in any directory, it doesn't matter, i would choose the root directory / ))
11-continued: Laymans terms: go to Advanced in TWRP and then Terminal Command. Just press select to start shell in the root directory "/ ".
once you are at the prompt you simply type in the commands in red in steps 12 & 13.
12. Copy the su binary (if you use SuperSU you run this command: cp /system/xbin/daemonsu /system/xbin/su )
13. Execute the installation (if you use SuperSU run this command: /system/xbin/su --install )
14. Reboot
15. Send the NSA a message and tell them to lick your balls. Oh wait nevermind they have a backdoor in AES... FTP = Fukt The Police :cyclops:

OP space
The real trick here is disabling (step 3) and then manually re-enabling (steps 12 and 13) root which you manually re-enable after the encryption is complete. The order is key. You cannot encrypt the device while rooted.
go to Advanced in TWRP and then Terminal Command. Just press select to start shell in the root directory "/ ".
once you are at the prompt you simply type in those commands:
cp /system/xbin/daemonsu /system/xbin/su
::THEN PRESS ENTER TO EXECUTE THE COPY COMMAND::
Then type:
/system/xbin/su --install
:RESS ENTER TO EXECUTE THE su COMMAND running the installation.::
Now reboot and you are done!
If you don't have TWRP installed there are other options to be able to run the command. Most custom recoveries either allow you to bring up a console window like that or they allow you to run commands on your device through your PC using ADB, either way it will work, you are just copying files with the first command and executing one of them to install on the second.

? on steps 12 + 13
"12. Copy the su binary (if you use SuperSU you run this command: cp /system/xbin/daemonsu /system/xbin/su )
13. Execute the installation (if you use SuperSU run this command: /system/xbin/su --install )"
Where in TWRP do I do this?
Also, do I need to be in the rom I am choosing as my daily driver when i start this process? What do i do if I change roms?

?
Bueller?

V3racious said:
6. The device will restart after a short period of time and start the encryption (this will take some time, but you should see a progress bar indicating how far it is)
Click to expand...
Click to collapse
This part never happens for me, it just gets stuck on the boot animation. I've disabled superuser. What else can I do? This is really frustrating.

livejamie said:
This part never happens for me, it just gets stuck on the boot animation. I've disabled superuser. What else can I do? This is really frustrating.
Click to expand...
Click to collapse
Exactly. I tried this before and got the same results.

jrkart99 said:
Exactly. I tried this before and got the same results.
Click to expand...
Click to collapse
I just gave up on root for now.

Breakdown of steps 12 & 13
jrkart99 said:
"12. Copy the su binary (if you use SuperSU you run this command: cp /system/xbin/daemonsu /system/xbin/su )
13. Execute the installation (if you use SuperSU run this command: /system/xbin/su --install )"
Where in TWRP do I do this?
Also, do I need to be in the rom I am choosing as my daily driver when i start this process? What do i do if I change roms?
Click to expand...
Click to collapse
For steps 12 and 13 you go to Advanced in TWRP and then Terminal Command. Just press select to start shell in the root directory "/ ".
once you are at the prompt you simply type in those commands:
cp /system/xbin/daemonsu /system/xbin/su
::THEN PRESS ENTER TO EXECUTE THE COPY COMMAND::
Then type:
/system/xbin/su --install
:RESS ENTER TO EXECUTE THE su COMMAND running the installation.::
Now reboot and you are done!
If you don't have TWRP installed there are other options to be able to run the command. Most custom recoveries either allow you to bring up a console window like that or they allow you to run commands on your device through your PC using ADB, either way it will work, you are just copying files with the first command and executing one of them to install on the second.
To answer your other question: YES you need to choose your ROM first, otherwise you have to do this all over again. Install your ROM first, root it next if your rom doesn't come pre-rooted, manually disable root, and lastly encrypt the device.

livejamie said:
This part never happens for me, it just gets stuck on the boot animation. I've disabled superuser. What else can I do? This is really frustrating.
Click to expand...
Click to collapse
Can you verify that you have in fact disabled root first? You cannot encrypt a rooted device. Also what is the model number of your device? What version of Android are you using?

Try this method after SuperSU is installed.
http://forum.xda-developers.com/showthread.php?p=56037508
Good luck
Sent from my Nexus 7 using Tapatalk

Hello,
I have sprint note 4.. I have installed HybridX Android 5.1.1 on it.. which have root and everything ready.
I go to system apps, from there disable SuperSu and then reboot in safe mode and start encryption.. These are the steps I read on another page..
However, my phone gets stuck on the sprint spark yellow screen as soon as I say ok to encrypt.. it will restart and gets stuck on there.
I have tried without restarting in safe mode.. but the same result.
What can I do to encrypt my Sprint Note 4.
Thanks

Hello,
I am on Galaxy Note 3 with N7 Darklord ROM and both methods don't work.
Root is disabled, but when I run encryption, the phone restarts in 2-3 minutes
and nothing is encrypted
Please advise how to encrypt the device! Thanks!

5.0.1 Should be fine to root + encrypt
Hi all,
Just to confirm that the only version I managed to root and encrypt is 5.0.1.
I have a Note 4 910F and this worked;
- Flash stock via odin
- Root (chainfire via odin)
- Install Busybox
- Install Terminal Emulator, then run su -> pkill -KILL daemonsu (same as other instructions on this forum)
- Encrypt the phone
Again, this only worked on 5.0.1 (N910FXXU1BOC5_N910FBTU1BOB2_N910FXXU1BOC4_HOME.tar)
All other versions got stuck on encryption screen.

In short, all you have to do is ENCRYPT the device FIRST then ROOT it AFTERWARDS. It will not work once the device is rooted. I have not had a chance to try unrooting through SuperSU or disabling the daemonsu through a terminal emulator as mentioned so I am not sure if this works but it definitely works if you encrypt PRIOR to rooting. I can confirm it works on Marshmallow as I just did so on a Note 4.

Now has anyone had any luck making backup images of their encrypted devices? If so what custom recovery software and version are you running on your device?

[GUIDE]How to Root and Custom Recovery with a broken USB Port!

A Comprehensive guide to Rooting And Custom Recovery with a Non-Functioning USB Port
This is for those of us who have a broken USB port on our Xperia devices and still want to flash! If it is too difficult/expensive to get your device repaired, this method may still get you root and custom recovery.
Requirements:
As we always say with suggestions from XDA, DO THIS AT YOUR OWN RISK. I take no responsibility for you or your device.
This procedure was carried out on a Z3 Compact with stock firmware 23.4.A.1.264.
1. Xperia device with stock firmware - what I had: 23.4.A.1.264
2. KingRoot - what I had: 4.8.1
3. [NUT]'s XZDualRecovery - what I had: Z3C-lockeddualrecovery2.8.26-RELEASE.combined.zip
4. Android file exporer with root capcibility - what I had: ES File Explorer File Manager
5. Android terminal with root capability - what I had: Terminal Emulator for Android
6. Root Checker - what I had: Root Checker
STEP 1:
Use Kingroot to root the device. The version I had at the time said that there was no root method specifically available but there was a generic method which worked. If this doesnt work - try rebooting and try it. It worked for me on my second attempt.
STEP 2:
Use Root Checker to make sure the device is rooted - a dialog box should open from Kingroot asking if you want to grant it root access, press yes!
STEP 3:
Download XZDualRecovery twice - one for flashing and one for extracting (I found this easier on a PC).
STEP 4:
In the extracted version, open the install.bat in a text editor so you can read the code
STEP 5:
Search for the bit where the bat file makes the directory and transfers the necessary files
Code:
echo =============================================
echo Step2 : Sending the recovery files.
echo =============================================
adb shell "mkdir /data/local/tmp/recovery"
adb push ..\tmp\dr.prop /data/local/tmp/recovery/dr.prop
adb push ..\system\bin\chargemon /data/local/tmp/recovery/chargemon
adb push ..\system\bin\mr /data/local/tmp/recovery/mr
adb push ..\system\.XZDualRecovery\xbin\dualrecovery.sh /data/local/tmp/recovery/dualrecovery.sh
adb push ..\tmp\NDRUtils.apk /data/local/tmp/recovery/NDRUtils.apk
adb push ..\system\.XZDualRecovery\xbin\rickiller.sh /data/local/tmp/recovery/rickiller.sh
adb push ..\tmp\byeselinux.ko /data/local/tmp/recovery/byeselinux.ko
adb push byeselinux\byeselinux.sh /data/local/tmp/recovery/byeselinux.sh
adb push ..\tmp\wp_mod.ko /data/local/tmp/recovery/wp_mod.ko
adb push byeselinux\sysrw.sh /data/local/tmp/recovery/sysrw.sh
adb push ..\tmp\modulecrcpatch /data/local/tmp/recovery/modulecrcpatch
adb push ..\system\.XZDualRecovery\xbin\busybox /data/local/tmp/recovery/busybox
adb push ..\system\.XZDualRecovery\xbin\recovery.twrp.cpio.lzma /data/local/tmp/recovery/recovery.twrp.cpio.lzma
adb push ..\system\.XZDualRecovery\xbin\recovery.philz.cpio.lzma /data/local/tmp/recovery/recovery.philz.cpio.lzma
if exist {..\system\.XZDualRecovery\xbin\ramdisk.stock.cpio.lzma} (
adb push ..\system\.XZDualRecovery\xbin\ramdisk.stock.cpio.lzma /data/local/tmp/recovery/ramdisk.stock.cpio.lzma
)
adb push ..\tmp\installrecovery.sh /data/local/tmp/recovery/install.sh
STEP 6:
Make the corresponding directory /data/local/tmp/recovery with your file explorer
STEP 7:
Copy the files mentioned in the bat from the extracted version to the folder location. All the files go into one folder with the same file name apart from the last one which is renamed installrecovery.sh to install.sh.
STEP 8:
Double check everything that it mentioned in the bat file is in the correct directory on the device.
STEP 9:
Open terminal emulator and type "su" - a dialog box should open from Kingroot asking if you want to grant it root access, press yes!
STEP 10:
Use "pwd" and "cd" to see where you are and to change directory. You are trying to get to /data/local/tmp/recovery.
STEP 11:
Once your there type in "./install.sh" to start [NUT]'s recovery installer. A whole bunch of stuff should come up in the window explaining the status of the installer.
STEP 12:
If all went well - your device should reboot and go straight into TWRP. MAKE A BACKUP!!!
STEP 13:
From here I directly wiped the device and installed a new ROM. Click the thanks button if this worked for you - Happy Flashing!
Credits
@[NUT] for his custom recovery and support.
@istux for his research, suggestions and perseverance.

Finally you get it
Great work!

istux said:
Finally you get it
Great work!
Click to expand...
Click to collapse
thanks - lets hope it is useful for someone

Awsome! Very useful guide

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

[GUIDE][ROOT]How to install TWRP and ROOT your X507, X509 (PC Guide)

Okay, I have seen many people using the unofficial TWRP on their device, and that's a little dangerous because it may be malicious, and you might not even know that.
I am not saying it is, but it can be.
Now, back to the topic here,
HOW TO INSTALL TWRP[2] AND GET ROOT ACCESS[3] and moreHere goes..
Before anything, you need to get ADB and FASTBOOT programs on your PC and get your drivers installed so you can communicate with the device through your computer.
To Download ADB and fastboot program, you can download this file (not my upload)
Extract it anywhere you want(and remember that location).
(lets say "C:\workspace\ADB" and I will use this path for this guide).Typically, the driver for ADB will install the first time you connect your device to your computer and:
Internet is available
USB Debugging is enabled on your phone
But the FASTBOOT driver would probably not be available yet. to get fastboot drivers, follow these steps:
Turn on and Unlock your device and connect it to PC via the USB cable.
Open CMD and execute "cd C:\workspace\ADB".(or you can open C:\workspace\ADB in file explorer and type CMD in the address bar to open CMD directly there.
Type "adb devices".
Now, your phone will ask something(permission to allow ADB access on the connected PC)allow it. After you allow it, the CMD will show a list of attached devices and the mode they are attached in, your device should show "device" for now.
If it does not, there is some problem, search on internet or ask for help here
Now type "adb reboot bootloader".
now your Phone will shutdown and open in a different state. It will say Fastboot on the screen.
Now the driver is installing or is already installed, to check, type this:
"adb devices" and it should show a list and your device's mode should change to "fastboot".
That's it for the ADB and FASTBOOT. You have the necessary things to continue.
Continue to next post for TWRP and the post next to it for ROOT ACCESS.

Now, we will talk about how to install TWRP
@DroidThug has been kind enough to get Official support of TWRP for this device.
Head over to this thread to download the official image file of the TWRP Recovery and keep it on your computer, this is the very first step you need to take.
Here is the thread: https://forum.xda-developers.com/leeco-le-1s/development/official-twrp-t3527566
If you are lazy enough to go through the thread, which i suggest you to visit, here is the direct link to the download page: https://dl.twrp.me/x3/
And here is the direct download link of the v3.0.3(latest as of 31st Jan, 2017): https://dl.twrp.me/x3/twrp-3.0.3-0-x3.img
Once you have the recovery image, you need to flash it through fastboot.
If you are following this guide from start, you should already be in fastboot and have CMD open on your PC in adb folder.
Now, a few things you might want to follow strictly if you are unsure how to do it:
Copy the recovery image file to "C:\workspace\ADB" (adb folder).
Rename that file to "twrp.img"
Now you need to execute this command from CMD to flash the file:
"fastboot flash recovery twrp.img" and press enter.
This will take a few seconds and will will be over soon.
Now you need to reboot directly into RECOVERY, because if you will boot to the system first, the Device will replace your newly flashed recovery with the stock recovery and all this will be wasted. But if you reboot to recovery first, it will patch those things up and will stay.
So, to reboot to recovery, you need to use the key combo to get into the recovery,
Press and hold "Volume UP" and "Power" Buttons till the screen goes off(from fastboot mode) and is lit up again and then leave the power key and 2-3 seconds later, leave the Volume key too.
You will enter into recovery mode and it will ask you "if you want to keep the System partition to read only or not?"
I'd recommend keeping it to read only unless you know what you are doing.
There you have it!
You have successfully installed TWRP on your device!

GET ROOT ACCESS
Okay, So you have the RECOVERY installed already
Now go to this page and download the latest "Recovery Flashable ZIP" from there. (Here is the latest one as on 31st Jan, 2017).
You can do this in two ways through Phone(with TWRP already present) and through PC.
Through PhoneAll you need to do is flash it through the recovery and thats it, you will have root access!
Here are the steps to flash ZIPs from Recovery:
Get the zip file you want to flash(the one downloaded above) and place it somewhere in the Phone's internal storage.
Reboot to recovery(Power off and then hold "Vol UP" and "Power" keys till the screen is lit up.).
Tap on "Install".
Navigate to the ZIP file you placed in your phone's internal storage.
Select it and swipe to flash it.
The last step might take a few seconds and will be done then.
After its done, that't it!
Reboot to system and you have ROOT ACCESS!
Through PCOkay, you would still need to reboot to recovery, but you can follow this guide if you don't want to copy the zip file on your phone for whatever reason you may have.
Here are the steps:
Enter recovery.
Select "Advanced->ADB Sideload" and swipe to start sideload.
Now connect your phone to PC.
Now open CMD in ADB folder.
Check if your device is detected by typing "adb devices". It should show a device with sideload state.
Now type "adb sideload " and drag the zip file into the cmd window.
OR
you can copy the zip to the adb folder and rename it to supersu.zip and write "adb sideload supersu.zip" in the CMD.
Now Press enter.
After this, in a few seconds, it will be over and you can reboot to system(it might automatically reboot to system too).
And that's it! There you have it!
You have ROOT ACCESS on your device!

5. Now the driver is installing or is already installed, to check, type this:
"adb devices" and it should show a list and your device's mode should change to "fastboot".
Click to expand...
Click to collapse
If the phone is on fastboot mode, "adb devices" supposed to not give any output. "fastboot devices" will show the device and mode as fastboot.
You will enter into recovery mode and it will ask you "if you want to keep the System partition to read only or not?"
I'd recommend keeping it to read only unless you know what you are doing.
Click to expand...
Click to collapse
My screen is broken (that's only white light and no digitiser). I dont have any other Le 1S to get idea.
1. Are you sure Vol Up + Power will enter into Recovery? Mine is 5.5.014S.
2. I want to make my system partition as writable. Can you tell how to achieve with hardware keys like Vol Up or down & power.
3. After step 2. Can I flash SuperSu from PC without enabling sideload. While on custom recovery , "adb devices" will show mode as recovery. So flashing supersu from here. Not sure if this is correct. On my Moto G falcon. whenever I go into TWRP, adb recovery and MTP works.
Also can you check whats the combination Vol Up+Vol Dn+Power. When it starts I can connect to adb but all partitions are read only and not allowing to make any change to device. Not sure if its due to encryption.
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell
[email protected]_HK:/ $ cat /data/misc/adb/adb_keys
/system/bin/sh: cat: /data/misc/adb/adb_keys: Permission denied
1|[email protected]_HK:/ $ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
[email protected]_HK:/ $ su
/system/bin/sh: su: not found
[email protected]_HK:/ $ cd
[email protected]_HK:/data $ pwd
/data
[email protected]_HK:/ $ exit
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb reboot bootloader
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>fastboot devices
0123456789ABCDEF fastboot
**
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb install mirror.apk
[100%] /data/local/tmp/mirror.apk
Error: java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder android.os.IServiceManager.getService(java.lang.String)' on a null object reference
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell am start -n com.android.settings/.wifi.WifiSettings
java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder android.os.IServiceManager.getService(java.lang.String)' on a null object reference
at android.os.ServiceManager.getService(ServiceManager.java:55)
at android.app.ActivityManagerNative$1.create(ActivityManagerNative.java:2494)
at android.app.ActivityManagerNative$1.create(ActivityManagerNative.java:2492)
at android.util.Singleton.get(Singleton.java:34)
at android.app.ActivityManagerNative.getDefault(ActivityManagerNative.java:88)
at com.android.commands.am.Am.onRun(Am.java:295)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:99)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:250)
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell dumpsys wifi
adb shell dumpsys wifi^C
C:\Users\Mkn\Downloads\Le1s drivers\minimal_adb_fastboot_1.4.1_portable>adb shell
[email protected]_HK:/ $ ls -ld sdcard
lrwxrwxrwx root root 2017-03-21 11:12 sdcard -> /storage/sdcard0
[email protected]_HK:/ $ cd /storage/sdcard0
/system/bin/sh: cd: /storage/sdcard0: Permission denied
2|[email protected]_HK:/ $ ls -ld
drwxr-xr-x root root 2017-03-21 11:12 .
[email protected]_HK:/ $ ls -ld /storage/sdcard0
d--------- system system 2017-03-21 11:12 sdcard0
[email protected]_HK:/ $
Update:
I some how managed to side load. My Phone got bootlop after installing twrp. Then flashed userdata by following http://forum.le.com/in/index.php?th...op-restart-solution-letv-le1s-x507-x509.1155/ . Now its factory reset as I can see the screenshot from PC.
Still interested in knowing what's that Vol Up+Vol Down + Power.

If any one have le 1s related problem and solution or any one want to try new rom or kernal asap then all of u are welcome in our group on telegram so plz join with us
Requriemt
1. Download telegram from play store
2. Just click below link
https://telegram.me/LeSuperGroup
Thanks all of u

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!

Database Users

welcome