• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Note 4 Root Help (Verizon, Marshmallow 6.0.1)

E

eben48

Lurker
Hello, I am trying to root my Verizon note 4 but am running into trouble. I have followed multiple tutorials each basically saying the same thing and to no avail. I have the Samsung USB drivers installed, i have the most recent instance of SuperSU and im using TWRP-2.8.7.0 as included below. The problem i keep running into is a failure when trying to use odin. Here is what i get in the log.

<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!

I have a brand new data transfer cable just in case that was my problem.
I accessed developer mode and have USB Debugging on. I also have reactivation lock off.
Any help would be greatly appreciated. Thanks.
 

Attachments

From what ive read in other areas i have to have root access to unlock the boot loader.I would only need temp root access so i tried king root and its failed every time.I followed the steps in the link and it went through its process , booted up and started trying to automatically update. It doesn't look like that made much of a change.
 
This is the first thread I found on the subject at XDA after checking a link to a different site.
One of the things I noticed was that your device CID had to start with 15
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913

Seems that they found a way around it here.
http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144

I have been begging a co worker who has a Verizon Note 4 to let me have it for the weekend but sofar a nogo.
 
If you are in the phoenix area you can play with mine lol. Im still running into issues where i need temp root to get root. In the forum where i would change my version to lollipop i have to modify the cid with adb before i can flash the different version but i cant use the adb to take advantage of the unlocker tool because i don't have root. If im misinterpreting this please let me know but this is what i have tried so far.
 
After lots of trying i was able to successfully flash lollipop, unlock the bootloader using adb and adb minimal. For some reason adb minimal wouldn't push the file to my phone only adb would but after that adb didn't like to do any of the shell commands so i had to use minimal. its worked but i still haven't figured out why i had to add the extra step.and put su on my phone only to find out that i need a different kernel otherwise i get into a boot loop. So i did the whole process over again just to get a corrupted zip for my new kernel and get the boot loop again. Today now that i know what i'm doing i should be able to get it right lol. I'm just going to find a new kernel that is compatible and i should be good to go. I really appreciate the help.
 
Last edited:
I've been learning adb and Fastboot as I go. Did a few fastboot devices and pulled info with adb but haven't tried to push anything.
Stuff pretty interesting though.
Good luck.
 
Glad you got it the way you want it. Hope the links were useful. Maybe one day I'll get a Note 4 to play with. Itching to try it.
 
eben48 said:
Hello, I am trying to root my Verizon note 4 but am running into trouble. I have followed multiple tutorials each basically saying the same thing and to no avail. I have the Samsung USB drivers installed, i have the most recent instance of SuperSU and im using TWRP-2.8.7.0 as included below. The problem i keep running into is a failure when trying to use odin. Here is what i get in the log.

<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!

I have a brand new data transfer cable just in case that was my problem.
I accessed developer mode and have USB Debugging on. I also have reactivation lock off.
Any help would be greatly appreciated. Thanks.
Click to expand...

Don't use USB 3
 
You must log in or register to reply here.
Back
Top Bottom