Develop Bugs

Question about rooting LG G2 (Sprint) and OTA Updates.

Good afternoon guys,
I have a few set of questions and I will be glad if someone is able to kindly help me out. Please keep in mind that I am not an android expert as far as rooting, custom roms, etc... So I ask for patience from you guys!
Now... into the questions. I got my LG G2 2 weeks ago from Sprint. Great solid phone with killer specs. I previously had a Galaxy Epic 4G Touch. I was looking into rooting my LG G2 phone. However, somewhere in an article online, I read that, if I were to root my LG, I would no longer receive OTA software updates... Like an updated android version for example.. Is that true? I dont care about loosing root after updating. I just dont want to root my phone, receive an OTA update and then mess up my phone.. So thats my first question.
Next... I've done quite a few research online on how to root the G2 from sprint. What i am currently having issues with is finding the drivers. I know I must install them prior to attempting anything else. I read that I could use the Tmobile version drivers even though I am on sprint. But no luck finding those either. Could someone provide me with a link to download the drivers? Thanks! (Windows 8)
And last... I've seen many methods on rooting this device, that at the end, was confused on which one to use. Soo.. could someone share a link of a working method to root the LG G2 from Sprint (Android 4.4.2)
Thank you guys and I will be very grateful for any help. :good:

Any change of the android operating system with ota can fail. They are looking it seems note for any excuse to break the phone if you do anything. Best idea is to make sure you can unroot, then take ota.
Best way to root is go with ioroot25. I believe it is in lg g2 general.
Sent from my Nexus 7 using Tapatalk

Thank you for your reply.
How would I unroot my G2? Would I use ioroot25? Or is there some type of app that I would have to download? Correct me if I'm wrong, but... Is it possible to unroot with SuperSU ones is installed on your phone after a sucessful root?
Thanks.! :good:

SuperSU can unroot (and temp unroot, though anybodies guess if it'll survive an OTA). There's several other temp unrooters, I often use Hide My Root (try to get some perspective on what the device *actually* works like). Otherwise, removing su, supersu, busybox (if installed) and whatever else until /system looks unmodified works. If there's custom recovery, you (as well as I) probably need to flash that back to stock as well. Or.. quite likely there will be a version around to flash without taking the actual OTA update if there isn't already (haven't checked the other thread). That'll likely be the easiest rather than bother with redoing the work to fix it up again.
Nothing is risk-free of course, but unrooted and flashed back to stock recovery it should be at least fairly unlikely to hurt anything. Of course that's often the stuff I mess up.

Robles23 said:
Good afternoon guys,
I have a few set of questions and I will be glad if someone is able to kindly help me out. Please keep in mind that I am not an android expert as far as rooting, custom roms, etc... So I ask for patience from you guys!
Now... into the questions. I got my LG G2 2 weeks ago from Sprint. Great solid phone with killer specs. I previously had a Galaxy Epic 4G Touch. I was looking into rooting my LG G2 phone. However, somewhere in an article online, I read that, if I were to root my LG, I would no longer receive OTA software updates... Like an updated android version for example.. Is that true? I dont care about loosing root after updating. I just dont want to root my phone, receive an OTA update and then mess up my phone.. So thats my first question.
Next... I've done quite a few research online on how to root the G2 from sprint. What i am currently having issues with is finding the drivers. I know I must install them prior to attempting anything else. I read that I could use the Tmobile version drivers even though I am on sprint. But no luck finding those either. Could someone provide me with a link to download the drivers? Thanks! (Windows 8)
And last... I've seen many methods on rooting this device, that at the end, was confused on which one to use. Soo.. could someone share a link of a working method to root the LG G2 from Sprint (Android 4.4.2)
Thank you guys and I will be very grateful for any help. :good:
Click to expand...
Click to collapse
Well I took a OTA update this morning not thinking.....rooted but stock rom and now my phone wont come out of recovery.....Trying to fix this now...ugg! Not fun

[Q] No root with ANK1 - is it safe to rollback to previous firmware?

I'm just wondering if it's safe to rollback the firmware on my Galaxy Tab S 10.5" to the previous one or if it causes some sort of conflict.
I want to do so because I've just installed the most recent one (T800ODD1ANK1 - India) and I can't root it using Cf-Autoroot posted here.
Thanks!

What happens when you try to root it?

DUHAsianSKILLZ said:
What happens when you try to root it?
Click to expand...
Click to collapse
Nothing. I did it with Odin and it just reboots to the same old unrooted tablet. All is working fine as usual, but no root.

What botters me the most is that I had Xposed framework installed but now it has no functionality and all the modules I had installed don't work. I would install the previous firmware but I'm afraid of breaking something, with installing older software on top of newer one.

I was able to root the US version of that ROM (T800XXU1ANK1) using CF Auto Root from Chainfire:
http://download.chainfire.eu/473/CF...uto-Root-chagallwifi-chagallwifixx-smt800.zip
Perhaps give that a shot???

I will but the India version has a more recent changelist (which was the reason why I chose to install it).
Thanks in advance.

As I predicted, since the changelist is different (your version has the same as the older one I had, with functioning root, but not with this one), no root.
Does anyone know if it is safe to install a previous version of the software? Like, for example, Cellular South ANK1 (with an older changelist).
Thanks.

Itchiee said:
I was able to root the US version of that ROM (T800XXU1ANK1) using CF Auto Root from Chainfire:
http://download.chainfire.eu/473/CF...uto-Root-chagallwifi-chagallwifixx-smt800.zip
Perhaps give that a shot???
Click to expand...
Click to collapse
I'm having the same issue as the original poster. It says I am rooted, but I'm not because root checker just keeps spinning and there isn't a SU# icon in my apps. I've done this with Odin about a million times before, for some reason on my new T800 (after I updated the software), it doesn't work.
Am I missing a step because I have the same version you have? Extract the file. Load the md5 file into AP. Hit Start. Wait for it to reboot. Right?
Yea root isn't working for me with T800XXU1ANK1. =(

Im assuming you ran Super SU and updated the binaries or whatever it asks, or updated the app in playstore?
Ive done nothing different and root works fine.

I was thinking about another root alternative. I was thinking about downloading the supersu zip and save it to the device or sd card. Then flash twrp recovery with odin, then boot into recovery and flash the supersu zip to get root? Could that work as an alternative since it flashes root in the process?

I just rolled back to T800XXU1ANJ6 and I am rooted.

I just bought a Tab S, and I can't seem to find an answer to a question that relates to this thread. Is there any advantage to updating before rooting?
I can't decide if I should root it now or update the software, and then root. After searching some, it appears that it doesn't matter whether I upgrade or not, but I can't seem to find if there is any advantage to updating it then rooting. Like, is it easier to get the latest firmware that way?

PeterGunz said:
I just bought a Tab S, and I can't seem to find an answer to a question that relates to this thread. Is there any advantage to updating before rooting?
I can't decide if I should root it now or update the software, and then root. After searching some, it appears that it doesn't matter whether I upgrade or not, but I can't seem to find if there is any advantage to updating it then rooting. Like, is it easier to get the latest firmware that way?
Click to expand...
Click to collapse
If i am correct, There should be stock custom roms available that are prerooted so you can flash over. As for an ota update, that is faster than being rooted then flashing lollipop rom.
Anyway we have a lollipop rom already built. Its smooth and most things are working. Its really cool and id rather use this than waiting for samsung to get the latest update out. Do you have the 10.5 in or 8.4 inch?

DUHAsianSKILLZ said:
If i am correct, There should be stock custom roms available that are prerooted so you can flash over. As for an ota update, that is faster than being rooted then flashing lollipop rom.
Anyway we have a lollipop rom already built. Its smooth and most things are working. Its really cool and id rather use this than waiting for samsung to get the latest update out. Do you have the 10.5 in or 8.4 inch?
Click to expand...
Click to collapse
I have the wifi 10.5 inch.
So, you are saying update OTA then root, unless I want to jump to Lollipop (which I do), which in that case it doesn't matter so I should just root and flash a lollipop rom?
Thanks for helping me out.

PeterGunz said:
I have the wifi 10.5 inch.
So, you are saying update OTA then root, unless I want to jump to Lollipop (which I do), which in that case it doesn't matter so I should just root and flash a lollipop rom?
Thanks for helping me out.
Click to expand...
Click to collapse
Up to you If you want to jump to lollipop/CM12, just run flash Cfautoroot( with odin to root) then install twrp and flash the lollipop rom. There is a thread for cm12/lollipop in the development tab s section.
But wait! Rooting trips knox with voids your warranty. Same users has reported getting service from samsung for free of charge from defective units and some had to pay to get defective parts replaced by samsung. 50/50 chance. I took the risk and havent got a hardbrick or anything yet.
Regards

DUHAsianSKILLZ said:
Up to you If you want to jump to lollipop/CM12, just run flash Cfautoroot( with odin to root) then install twrp and flash the lollipop rom. There is a thread for cm12/lollipop in the development tab s section.
But wait! Rooting trips knox with voids your warranty. Same users has reported getting service from samsung for free of charge from defective units and some had to pay to get defective parts replaced by samsung. 50/50 chance. I took the risk and havent got a hardbrick or anything yet.
Regards
Click to expand...
Click to collapse
Thank you for the heads-up. I've rooted all 6 of my android phones that I've had, so I'm not too worried about voiding the watrranty. Judging by your reply it sounds like there are a lot of lemons out there for this device. Mine seems to be running okay, but I just can't take all the lag that I assume comes from TW and bloatware. My HTC One M8 with Lollipop seems faster and smoother than my Tab S at stock. Although after typing the last sentence, I put Nova on there and sped up all the animations and it is definitely light years faster than my One M8 now.

I think the answer to the original post is that the Su binary was installed, but the op didn't download then update Super su after rooting. You wont get full root until you do as there is no app to handle root requests.

Can't get root twice for bootloader unlock. Got it once, can't do it again.

I had 5.1.1 installed. Couldn't get KingRoot to give temp root (lots of people say you can only do it on 4.4.4, lots of other people say they got it to work on 5.1.1 if you read around).
So I tried downgrading to 4.4.4. Odin failed every time.
So I tried downgrading to 5.0.1. That worked. But kingroot still was unable to get root.
I then found King O Root. Tried that once, no luck. Tried it a 2nd time, and success. I then ran the samsund_fix file. And it changed my CID.
But then you have to restart the phone and run the fix file again.
I have run king o root (and tried kingroot) each at least 30 times now. And I can't get either to give me root access again. I've even tried the desktop version of king o root. Nothing.
I'm SOOO close I feel. But I can't get that last step. Its killing me.
Can anyone help with where to go next?
I figure either 1) I have to find a way to get temporary root one more time. OR 2) find a way to get down to kitkat 4.4.4 to get temporary root.
One other quick question, is the reason I can't get to 4.4.4 because I upgraded all the way to 5.1.1? EVERYTHING I read says 'yeah you can downgrade' but mine won't downgrade. Odin fails with an error So how do I get to 4.4.4? Am I just screwed?
NAND Write Start!
boot.img
FAIL! (Auth)

Are you sure you have to push the file again?
Sometimes it doesn't take and you need to push it again. The last couple of times I unlocked it went on the first try. Go into download mode and see if it says "developer mode."
I was able to unlock on 5.1.1. Kingroot and Kingoroot are extremely unstable besides being Chinese software with all of the risks that entails. There is supposedly a PC version of one of them (shudder) that is allegedly a bit more stable.
Where are you getting the firmware you're trying to use to downgrade?

douger1957 said:
Are you sure you have to push the file again?
Sometimes it doesn't take and you need to push it again. The last couple of times I unlocked it went on the first try. Go into download mode and see if it says "developer mode."
Click to expand...
Click to collapse
So I'm not 100% sure I have to push the file again. I know when I ran the fix file in adb shell the first time, it said I have to run the fix script again. And then when I boot into download mode, I see nothing that says "developer mode".
But, on the other hand. When I check with the eMMC Brickbug checker thing. That says the CID did change according to what the samsung_fix script said it changed it to.
So I *think* the CID changed? But I don't have developer mode. So I think I need to run the fix script again to finish the job.
douger1957 said:
I was able to unlock on 5.1.1. Kingroot and Kingoroot are extremely unstable besides being Chinese software with all of the risks that entails. There is supposedly a PC version of one of them (shudder) that is allegedly a bit more stable.
Click to expand...
Click to collapse
I actually tried a PC version of kingoroot. It also failed numerous times.
douger1957 said:
Where are you getting the firmware you're trying to use to downgrade?
Click to expand...
Click to collapse
I'm getting it from androidfilehost.
https://www.androidfilehost.com/?w=search&s=n910v
That's where I got the 5.0.1 version that worked when I went from 5.1.1 to 5.0.1. But I guess I could try finding a 4.4.4 version from somewhere else. I don't know where though.
It passes md5 check in odin. Though I'm not sure that means much.

nertskull said:
So I'm not 100% sure I have to push the file again. I know when I ran the fix file in adb shell the first time, it said I have to run the fix script again. And then when I boot into download mode, I see nothing that says "developer mode".
But, on the other hand. When I check with the eMMC Brickbug checker thing. That says the CID did change according to what the samsung_fix script said it changed it to.
So I *think* the CID changed? But I don't have developer mode. So I think I need to run the fix script again to finish the job.
I actually tried a PC version of kingoroot. It also failed numerous times.
I'm getting it from androidfilehost.
https://www.androidfilehost.com/?w=search&s=n910v
That's where I got the 5.0.1 version that worked when I went from 5.1.1 to 5.0.1. But I guess I could try finding a 4.4.4 version from somewhere else. I don't know where though.
It passes md5 check in odin. Though I'm not sure that means much.
Click to expand...
Click to collapse
This may be your problem. I don't think you can flash a rooted ROM with a locked bootloader with success. Try this one. (Thanks, @hsbadr!) It's the OEM firmware. This will mean that you'll need to start from scratch. I should note that another poster has had trouble flashing this firmware although other posters including myself have used it successfully.
@hsbadr has a repository of firmwares. What you're looking for is the full firmware. Sammobile is another source of firmware, but they're terribly slow to download from.

douger1957 said:
This may be your problem. I don't think you can flash a rooted ROM with a locked bootloader with success. Try this one. (Thanks, @hsbadr!) It's the OEM firmware. This will mean that you'll need to start from scratch. I should note that another poster has had trouble flashing this firmware although other posters including myself have used it successfully.
@hsbadr has a repository of firmwares. What you're looking for is the full firmware. Sammobile is another source of firmware, but they're terribly slow to download from.
Click to expand...
Click to collapse
I tried that firmware you linked to. That took me back to 5.1.1. I tried kingroot and kingoroot, and still no luck. After 8 or 9 tries each, I still can't get temproot.
I thought it would be better to go back to 4.4.4, and looked through hsbadr's list of roms you linked me to. I tried both of the 4.4.4 full firmwares (NJ5 and NI1) and both fail on odin.
It would seem to me I'm never getting back to 4.4.4/kitkat am I?
Should I just keep running kingroot/kingoroot until I can get temp root? I ran kingoroot at least 30 times last night on 5.0.1 and never got root again. I really don't understand why I could get it once but never again.
Should I try running it a million times on 5.1.1 where I now am again? Or should I go back to 5.0.1? Is there any other way to get temporary root?

nertskull said:
I tried that firmware you linked to. That took me back to 5.1.1. I tried kingroot and kingoroot, and still no luck. After 8 or 9 tries each, I still can't get temproot.
I thought it would be better to go back to 4.4.4, and looked through hsbadr's list of roms you linked me to. I tried both of the 4.4.4 full firmwares (NJ5 and NI1) and both fail on odin.
It would seem to me I'm never getting back to 4.4.4/kitkat am I?
Should I just keep running kingroot/kingoroot until I can get temp root? I ran kingoroot at least 30 times last night on 5.0.1 and never got root again. I really don't understand why I could get it once but never again.
Should I try running it a million times on 5.1.1 where I now am again? Or should I go back to 5.0.1? Is there any other way to get temporary root?
Click to expand...
Click to collapse
I was able to unlock my bootloader twice on 5.1.1. I used Kingroot to unlock Lollipop and Kingoroot to unlock Marshmallow. See if you can find an older version of either root methods. I think I remember reading somewhere that the newer version is flakier than the older stuff. I'm fairly convinced that the rooted ROM you flashed is part of the problem.
As I said, Kingroot and Kingoroot are highly unstable. You may need to spend quite a bit of time in multiple attempts. It comes down to how badly do you want root?

douger1957 said:
I was able to unlock my bootloader twice on 5.1.1. I used Kingroot to unlock Lollipop and Kingoroot to unlock Marshmallow. See if you can find an older version of either root methods. I think I remember reading somewhere that the newer version is flakier than the older stuff. I'm fairly convinced that the rooted ROM you flashed is part of the problem.
As I said, Kingroot and Kingoroot are highly unstable. You may need to spend quite a bit of time in multiple attempts. It comes down to how badly do you want root?
Click to expand...
Click to collapse
Holy success. I have no idea why. But after rebooting the phone for the umpteenth time and running kingoroot another 20 times. It finally gave me another successful temp root, this time while on 5.1.1.
I ran the script again, and now when I got into download mode, I have Mode: Developer showing. Hooray.
BUT....then bootloops. I couldn't get it started.
I then accidentally wiped everything, completely wiped. No operating system according to twrp.
So I looked around, and it appears JasmineRom and CM13 by hsbadr are mentioned as good custom ROMs. So I grabbed CM13, used twrp to install it. And success. I have a working phone. At least, for the past couple minutes.
So a tremendous thank you for giving me some guidance.
I have two more questions for the moment though.
1) How easy/hard would it be to lose developer mode? Do I need to be careful about what roms I flash? Could I lose that? Or now that it is in developer mode, should I be pretty safe in that sticking around?
2) Can I try any Rom on it right now. There don't appear to be a lot of verizon note 4 specific roms around for this phone, because it hasn't had root for long. Will any of the other note 4 roms work? Or should I make sure to stick to only 'proven verizon' roms.
Thanks again for the help.
....
Oh, and how bad do I want root? Badly. Super badly. If I had the money I would have ditched this phone forever ago. I will never buy another phone again on the hope/promise that it will get root soon.

nertskull said:
Holy success. I have no idea why. But after rebooting the phone for the umpteenth time and running kingoroot another 20 times. It finally gave me another successful temp root, this time while on 5.1.1.
I ran the script again, and now when I got into download mode, I have Mode: Developer showing. Hooray.
BUT....then bootloops. I couldn't get it started.
I then accidentally wiped everything, completely wiped. No operating system according to twrp.
So I looked around, and it appears JasmineRom and CM13 by hsbadr are mentioned as good custom ROMs. So I grabbed CM13, used twrp to install it. And success. I have a working phone. At least, for the past couple minutes.
So a tremendous thank you for giving me some guidance.
I have two more questions for the moment though.
1) How easy/hard would it be to lose developer mode? Do I need to be careful about what roms I flash? Could I lose that? Or now that it is in developer mode, should I be pretty safe in that sticking around?
2) Can I try any Rom on it right now. There don't appear to be a lot of verizon note 4 specific roms around for this phone, because it hasn't had root for long. Will any of the other note 4 roms work? Or should I make sure to stick to only 'proven verizon' roms.
Thanks again for the help.
....
Oh, and how bad do I want root? Badly. Super badly. If I had the money I would have ditched this phone forever ago. I will never buy another phone again on the hope/promise that it will get root soon.
Click to expand...
Click to collapse
The only way I know to lock your bootloader is to flash an OEM firmware, take an OTA or mess with flashing bootloader without knowing what you're doing..
What you can flash depends upon which bootloader you have unlocked. Lollipop? You can flash a ROM based on a Lollipop bootloader. Jasmine 4.3 and CM 13 before 6/20 are Marshmallow ROMs based on Lollipop bootloaders. You can also run ROMs made for the N910F/G (also based on Lollipop bootloaders) if you use the proper data fix.
If you want to run a pure Marshmallow ROM, you need to do the unlock dance again. If you're interested in wifi calling, you'll need to stick with a fairly stock OEM ROM like Jasmine 6.0 or 7.0 (both versions are buried pretty deep in the thread) or PaulPizz which I haven't tried but hear good things about.

douger1957 said:
The only way I know to lock your bootloader is to flash an OEM firmware, take an OTA or mess with flashing bootloader without knowing what you're doing..
What you can flash depends upon which bootloader you have unlocked. Lollipop? You can flash a ROM based on a Lollipop bootloader. Jasmine 4.3 and CM 13 before 6/20 are Marshmallow ROMs based on Lollipop bootloaders. You can also run ROMs made for the N910F/G (also based on Lollipop bootloaders) if you use the proper data fix.
If you want to run a pure Marshmallow ROM, you need to do the unlock dance again. If you're interested in wifi calling, you'll need to stick with a fairly stock OEM ROM like Jasmine 6.0 or 7.0 (both versions are buried pretty deep in the thread) or PaulPizz which I haven't tried but hear good things about.
Click to expand...
Click to collapse
Awesome. I downloaded CM13 from before the 20th and it seems to work great. I had to flash the CM13 rom and open GApps at the same time, otherwise the GApps kept crashing. But flashing them at the same time before turning on CM13 for the first time seemed to work.
Thanks for the help. Don't follow things closely enough to have known that I needed a pre 20th build.
Perhaps one more question.
Would you recommend taking the time to unlock the marshmallow bootloader? I don't need wifi calling. And I seem to be getting most of the benefits of 6.0.1 now even though using a lollipop bootloader.
I'm hesitant to try to unlock the marshmallow bootloader, because according to the instructions, it looks like I have to deal with kingroot/kingoroot again to do it. And I had such a hard time getting those to work this first time (easily 80+ tries running kingoroot) before I got temproot, that I'm not sure I want to take the risk of doing it again.
In your opinion, is it worth the risk to unlock the marshmallow bootloader? Or is running marshmallow on the lollipop bootloader reasonable enough?
Thanks

nertskull said:
Awesome. I downloaded CM13 from before the 20th and it seems to work great. I had to flash the CM13 rom and open GApps at the same time, otherwise the GApps kept crashing. But flashing them at the same time before turning on CM13 for the first time seemed to work.
Thanks for the help. Don't follow things closely enough to have known that I needed a pre 20th build.
Perhaps one more question.
Would you recommend taking the time to unlock the marshmallow bootloader? I don't need wifi calling. And I seem to be getting most of the benefits of 6.0.1 now even though using a lollipop bootloader.
I'm hesitant to try to unlock the marshmallow bootloader, because according to the instructions, it looks like I have to deal with kingroot/kingoroot again to do it. And I had such a hard time getting those to work this first time (easily 80+ tries running kingoroot) before I got temproot, that I'm not sure I want to take the risk of doing it again.
In your opinion, is it worth the risk to unlock the marshmallow bootloader? Or is running marshmallow on the lollipop bootloader reasonable enough?
Thanks
Click to expand...
Click to collapse
That's a difficult question to answer and for me would boil down to whether I wanted features available in Marshmallow based ROMs or not.
Wifi calling is a nice to have feature for me but it's not really a dealbreaker. There's a bit more security baked into Marshmallow which is always nice to have.
The development atmosphere is more active over at the generic Note 4 forum. You can now get one of the super ROMs (Note/S7 combo ports) in either flavor. You'll want to stick with ROMs developed for the N910F or G models. They're international phones with fewer integration headaches for our N910V phones. To use those ROMs on our phone, you'll need a data fix most kindly provided by @louforgiveno.
My suggestion in picking a ROM is to zero in on one that seems to have the features you'd like to have and read the entire thread. Look for threads in either the General or Q&A subforums that are dedicated to answering questions about the ROM and read those, too. Some of those threads are upwards to 1,000 posts or more, you say? You'll discover what problems people have had with the ROM and the solutions or workarounds needed to overcome them. You'll also discover just how lazy many posters are either not reading thoroughly or failing to use the search function.
Final suggestions? Do a full nandroid backup before you flash anything. In TWRP, check off all of the boxes. In many of today's ROMs, you'll have a 8 to 10 gig backup file. If you can't keep that on the phone, move it to your PC. There will be far fewer tears if something goes wrong. When you flash a ROM, do a full wipe. I check off Dalvik/ART cache, system, data, and cache. For your first ROM, I would move anything that you have on internal storage off the phone and wipe internal storage too. If you have any Kingroot/Kingoroot cooties, that should clear them off the phone. When you're done flashing a ROM there's an option to wipe the cache. Do it. If you've installed a bunch or apps or deleted them, wipe the Dalvik and cache. It'll help bring the Android stars into alignment as that forces the system to optimize.
Good luck and happy flashing.

You need to go to 5.1.1 use kingOroot and then do it again. Cid will remain that's what I did. Its different for everyone these root methods are pulled from the internet and it will usually take a few time and it will try dufrrent methods of rooting
nertskull said:
I had 5.1.1 installed. Couldn't get KingRoot to give temp root (lots of people say you can only do it on 4.4.4, lots of other people say they got it to work on 5.1.1 if you read around).
So I tried downgrading to 4.4.4. Odin failed every time.
So I tried downgrading to 5.0.1. That worked. But kingroot still was unable to get root.
I then found King O Root. Tried that once, no luck. Tried it a 2nd time, and success. I then ran the samsund_fix file. And it changed my CID.
But then you have to restart the phone and run the fix file again.
I have run king o root (and tried kingroot) each at least 30 times now. And I can't get either to give me root access again. I've even tried the desktop version of king o root. Nothing.
I'm SOOO close I feel. But I can't get that last step. Its killing me.
Can anyone help with where to go next?
I figure either 1) I have to find a way to get temporary root one more time. OR 2) find a way to get down to kitkat 4.4.4 to get temporary root.
One other quick question, is the reason I can't get to 4.4.4 because I upgraded all the way to 5.1.1? EVERYTHING I read says 'yeah you can downgrade' but mine won't downgrade. Odin fails with an error So how do I get to 4.4.4? Am I just screwed?
NAND Write Start!
boot.img
FAIL! (Auth)
Click to expand...
Click to collapse

For me, I had to run Kingoroot from my laptop, and Kingroot never worked.

Question about how to root 6.0.1 on Verizon Note 4 N910V

I'm a little confused about the conflicting answers I'm reading in the threads here and was hoping someone could give me a simple answer. As of now I am rooted on 5.1.1 running oscar_kernelv2.0. No special rom just regular touch wiz. I would like to upgrade to a ROOTED 6.0.1. My question is in order to do this do I factory wipe my phone, make sure I'm rooted on 5.1.1 and then I can just flash a rooted 6.0.1? I have no problem rooting into 5.1.1 I'm just confused about what the next steps are suppose to be after that in order to upgrade to MM. If anyone could help I'd appreciate it because the MM guides here are too vague.

First do this
http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144

I'm a little confused about the conflicting answers I'm reading in the threads here and was hoping someone could give me a simple answer. As of now I am rooted on 5.1.1 running oscar_kernelv2.0. No special rom just regular touch wiz. I would like to upgrade to a ROOTED 6.0.1. My question is in order to do this do I factory wipe my phone, make sure I'm rooted on 5.1.1 and then I can just flash a rooted 6.0.1? I have no problem rooting into 5.1.1 I'm just confused about what the next steps are suppose to be after that in order to upgrade to MM. If anyone could help I'd appreciate it because the MM guides here are too vague.
Click to expand...
Click to collapse
I would go to this post specifically by @civichater . When i would go back and forth awhile back this is always where i turned to.

Questions belong in the Help section, not Development. Please read the sticky called "Rules for Posting in Development" before posting in there again :good:
THREAD MOVED

Tripper511 said:
I'm a little confused about the conflicting answers I'm reading in the threads here and was hoping someone could give me a simple answer. As of now I am rooted on 5.1.1 running oscar_kernelv2.0. No special rom just regular touch wiz. I would like to upgrade to a ROOTED 6.0.1. My question is in order to do this do I factory wipe my phone, make sure I'm rooted on 5.1.1 and then I can just flash a rooted 6.0.1? I have no problem rooting into 5.1.1 I'm just confused about what the next steps are suppose to be after that in order to upgrade to MM. If anyone could help I'd appreciate it because the MM guides here are too vague.
Click to expand...
Click to collapse
Flash the safe upgrade by hsbrad which is rootable. The upgrade guide is in verizon note 4 general forum. It invoves relocking your phone temporarily . You will need mobile data to run kingroot the upgrade will leave Your wifi unusable at this point but unlock is almost the same as the process u used if u unlocked 5.1.1

I had to get a "new" phone sent due to the screen on my previous one starting to push out from a swollen battery. It came with Marshmallow already installed. Will this unlock and root method work? The version number is 6.0.1.

will4958 said:
I had to get a "new" phone sent due to the screen on my previous one starting to push out from a swollen battery. It came with Marshmallow already installed. Will this unlock and root method work? The version number is 6.0.1.
Click to expand...
Click to collapse
you have to downgrade to 5.1.1 first.

mojoswagger1980 said:
Flash the safe upgrade by hsbrad which is rootable. The upgrade guide is in verizon note 4 general forum. It invoves relocking your phone temporarily . You will need mobile data to run kingroot the upgrade will leave Your wifi unusable at this point but unlock is almost the same as the process u used if u unlocked 5.1.1
Click to expand...
Click to collapse
Is the no wifi issue just a temporary problem UNTIL the rooted 6.0.1 is installed? Or will wifi never work as long as I'm running hsbrad MM?

The wifi problem is only temporary. It's because the bootloader is incorrect, but you'll fix that in one of the following steps. Just follow the instructions to the letter and it will work. Be patient and don't skip anything. I just rooted two note 4's in less than a week. Never thought it to be possible, but I'm extremely happy now. I don't even miss the Note 7 I had for a few weeks.

5.1.1 to 6.0.1

I am having some trouble locating the info I need for this update. I am currently on 5.1.1 running Paul pizz rom and I want to update to his 6.0.1 rom. I know I need to get to 6.0.1 first and go through the whole unlock and root again, but I can't find out how to go about this. Links would be great or just a brief summary of what needs to be done. Thanks.

droidx2.3.3 said:
I am having some trouble locating the info I need for this update. I am currently on 5.1.1 running Paul pizz rom and I want to update to his 6.0.1 rom. I know I need to get to 6.0.1 first and go through the whole unlock and root again, but I can't find out how to go about this. Links would be great or just a brief summary of what needs to be done. Thanks.
Click to expand...
Click to collapse
Just a little bit of searching will turn up what you desire.
http://forum.xda-developers.com/showthread.php?p=67305192
Sent from my SM-N910V using Tapatalk

This is the ONLY method that worked for me and I tried them all--kudos doctor-cool--http://forum.xda-developers.com/note-4-verizon/general/stabilized-process-to-unlock-bootloader-t3375527
The emotion kernel is optional--I went with xceed kernel with grace4note rom and its like i have a new phone...amazing

Well I tried to get it done the other day but I had to give up for the time being. I was able to get to 6.0.1 but couldn't get that rooted. As soon as I was able to achieve temp root the phone would lock up and eventually reboot and go in to a boot loop.
So I tried several times with king root and kingo root with no luck and having to Odin back to stock almost each time. So now I'm even further back than I started since now I'm on stock Un rooted 5.1.1.
Sent from my SM-N910V using XDA-Developers mobile app

It's easy, just time consuming. I haven't read the link(s) above, so therefore I didn't use them to begin with. They might just contain more complete information. I love the work that some of these guys do for us, but their instructions are sometimes awful for noobies.
Basically, see this thread. Once you do it, you're back to a locked phone, but you're now on MM. Then, you must re-unlock it. Before you start the process, I'd run a backup, particularly on Snapchat if you use it. It doesn't let you login if your phone is rooted.
[HOWTO] Bootloader Unlock and Upgrade to Marshmallow [N910V]
My advice is to look at both threads before you begin and stick to the instructions that seem easiest for you to understand.

Yeah I've gone through the root process successfully before but I just couldn't get the phone to stay working long enough to complete the process.
It would either lock up and I'd have to pull the battery or it would reboot into a boot loop. I was able to get to the point if being in 6.0.1 like the thread says but then it went into a boot loop when king root made it reboot. So I had to Odin back to stock 5.1.1 and that's when nothing would work.
Sent from my SM-N910V using XDA-Developers mobile app