Develop Bugs

Before Rooting Question

I just got this phone. Android 4.2.2. I was wondering if rooting is still possible. I know that there are issues with unlocking the bootloader like, we can't. So can I still root and have the rooting goodies? If so, can you direct me to the correct method of rooting? All the methods I can find include unlocking the bootloader first and I don't know if I can just skip that step or not.
Thank you for your time.

Time To Shine said:
I just got this phone. Android 4.2.2. I was wondering if rooting is still possible. I know that there are issues with unlocking the bootloader like, we can't. So can I still root and have the rooting goodies? If so, can you direct me to the correct method of rooting? All the methods I can find include unlocking the bootloader first and I don't know if I can just skip that step or not.
Thank you for your time.
Click to expand...
Click to collapse
To answer your question you need to unlock/s-off your phone to root it, I would recommend running the rumrunner tool, installing a customer recovery and then install a custom rom. The reason I say install a custom rom even if you want to remain stock is because you can get a stock rom without any bloat. Most of the bloat apps on the HTC One and pretty much any phone, run in the background as soon as your phone starts, this eats battery life and performance. For a stock rom check out Santod040, he has a good stock rom released, personally I like NuSense and ViperOne they are both very solid roms.
Read this thread - http://forum.xda-developers.com/showthread.php?t=2473644 it is the Rumrunner tool. I believe as long as you DO NOT UPGRADE to 4.3 you can still root/unlock/s-off, after you unlock/s-off you can install whichever rom you like without worrying about losing the ability to have root access.
You will want to get into the bootloader to check which OS version you have and then download the corresponding version of Rumrunner.
Edit:
Be sure to backup your whole phone as soon as you install a customer recovery. After the backup is complete, save a copy on your computer. There will be times when you are tinkering with your phone that you will need to get your phone back to a factory state, you can use a RUU but in my opinion that is more complicated process and you have a higher risk of something going wrong compared to simply restoring a backup.

Okay. Thank you. I will look into this.

[Q] Newbie With Questions Rooting T-Mobile Samsung Note 3

Hello,
I'm new to this whole rooting thing (I need to root my device for a couple of apps from the Google Play store) and I've been reading all the forums and I'm scratching my head going over all the information and I want to make sure I get it right so I don't brick my phone. Here is my situation:
- I have a Samsung Galaxy Note 3 (SM-N900T) on T-Mobile USA which was purchased October 2013
- This phone is stock from T-Mobile and has never had any type of mods, etc done to it
- 2 days ago, I upgraded the software OTA to KitKat 4.4.2
- I do NOT have the 'multitouch' issue as described in some of the forums
All I want to do at the end of the day is root my phone, without damaging it - preferably without tripping KNOX either (if possible).
It is confusing to me which thread to follow. I see links / instructions for CF-Root, CF-Auto-Root, Root De La Vega, etc are from October 2013 (not sure if this latest OTA update changes the steps) and I don't know which one to use without damaging my phone. I have the AP, CP, CSC information if this helps. Any help is greatly appreciated.
Thanks in advance!

Follow this exactly from step 4 (since you already have 4.4.2), and you will have no issues. All root methods as of now trip KNOX, so if you really don't want to do that, don't root.
http://forum.xda-developers.com/showthread.php?t=2672393
Enjoy!

bobbyphoenix said:
Follow this exactly from step 4 (since you already have 4.4.2), and you will have no issues. All root methods as of now trip KNOX, so if you really don't want to do that, don't root.
http://forum.xda-developers.com/showthread.php?t=2672393
Enjoy!
Click to expand...
Click to collapse
Thanks for this! Will this erase my phone back to defaults? Do I need to backup my phone prior to rooting it?

Everything will stay as is. None of the steps does a factory reset. All that will happen is you gain root, and will be able to use the SD card like you did on 4.3. As far as a back up goes I don't think you can on stock. You need the custom recovery which this will give you. Then you can do that if you want.
Sent from a Galaxy Note 3 far, far away....

bobbyphoenix said:
Everything will stay as is. None of the steps does a factory reset. All that will happen is you gain root, and will be able to use the SD card like you did on 4.3. As far as a back up goes I don't think you can on stock. You need the custom recovery which this will give you. Then you can do that if you want.
Sent from a Galaxy Note 3 far, far away....
Click to expand...
Click to collapse
Great, thanks again. I will try this tomorrow.

Just some tips if you haven't used ODIN before, or used custom recoveries. When it does its thing, and reboots, make sure ODIN says PASS before disconnecting or shutting off. It's not in the instructions since those doing this know this, but just giving a heads up. Also on the last step after flashing the SD card fix it says to back out until you see REBOOT. When you do that you have two options. You want to press the option 1. NO, and not 2. Reset/stop custom recovery. Again it's not in the post, but you want to keep the custom recovery active, so always select NO.
Sent from a Galaxy Note 3 far, far away....

Thanks so much BobbyPhoenix! Looks like everything is working and my phone is not bricked
Now that I have rooted my phone, I need to read up on what else I can do besides use apps from the Google Play that require root access, e.g. removing bloatware and using my phone as an Access Point.
Thanks again!

Good to hear. One of my first apps I install is AdAway. It's not in the Play Store because Google bans all ad-blockers. If you hate ads (like me) this is a must have. If you want to try it here is the link. After you install it, and open it for the first time to install the hosts, you may be prompted to do a symlink. This is normal. Just press yes. Enjoy your root!
You don't have to download the F-Droid app. Just look for "download apk" under the latest version which right now is 2.8.1.
https://f-droid.org/repository/browse/?fdfilter=adaway&fdid=org.adaway
changelog site
https://raw.github.com/dschuermann/ad-away/master/CHANGELOG

Good morning all, since my post above back in March, my rooted Note 3 has worked great. Today, when I connected my phone to Kies3, I see that there is an available firmware update from:
PDA:NB4 / PHONE:NB4 / CSC:NB4 (TMB)
to
PDA:NE6 / PHONE:NE6 / CSC:NE6 (TMB)
Are there any precautions I need to take if I want to upgrade to the latest firmware using Kies3 if my phone is rooted using the above procedure?
Thanks in advance!

Not sure if Kies will let you update firmware as you are rooted.
You can update to the NE6 Firmware by using Odin.
Find firmware either in this forum or elsewhere and flash away.
There was a good thread here on the Tmobile GN3 Forum with dl links, and steps.
Be well.

Thanks... I'll see what I can find.

gil_happy said:
Thanks... I'll see what I can find.
Click to expand...
Click to collapse
Yes there is, when you Odin, make sure you are on stock kernel, and then before you go into Odin go ahead and run triangle away, then boot into download mode. Just seems some people have had issues getting modem to flash, and getting boot loader to flash. Other than that you will have no issues. Thanks man.

Best Temporary Root APK for 4.4...KingRo or KingRoot/SuperSuMe?

Hey,
Been experimenting over the past few days now that I have a 4.4 phone for Verizon...What is the best temporary root program? after a while it seems my phone either loses root, or it isn't fully rooted (features not optional or working) with KingRo.
KingRo is the easiest, with KingRoot the phone shuts down or restarts itself, if i try to install supersume it also reboots or freezes.
Any other ideas? I have done the install via SP Tools and that is no better. after a few hours i lose root acccess and have to reboot. Even if i do a soft reboot i still loose root.

I think that is why they call it temporary. I too use kingroot. When my phone boots it is gone. It doesn't take Long for my phone to reboot when trying to use root functions.
Sent from my SM-N910V using Tapatalk

Someone posted something in the 'New Note 4 owner' thread about a possible permanent root. I checked it out earlier today, and from what I read, for our phone (those with a Verizon retail Note 4) it's meant for Lollipop 5.0.1. It provides a link to the Odin and root file downloads you'd need. I haven't tried it myself yet, but I'm remaining skeptically optimistic. Sadly, there haven't been new posts to that thread since my last one at 2:10pm today. Hopefully, someone will give it a shot this weekend, and if not I may try it on Monday. I'd just have to update to the 5.0.1 version of Lollipop first. I need my phone for work, so that's mainly why I haven't delved into it yet.

No way that root for lollipop works permanently when we cant root 4..4
I'm just looking to see if everryobe is having the same trouble as me with kingroot or KingO, perhaps one program iss better than the other,
Of the newer android phones, which one is the best that is rootable> if i decide to switch to a permnanent rooted phone

anyone>

Any phone Not from Verizon almost. Verizon locks down the boot loader.
Sent from my SM-N910V using Tapatalk

no suggestions?

???

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.

Root help - Is it even possible?

Hi folks.
Been lurking for a while, but this is my first post.
I've been looking into rooting my SM-G870W (Galaxy S5 Active, Canadian, Telus) for a while now. It's currently updated to Android 6.0.1.
I've read a lot of different information and I've held off on actually trying it because of several posters saying they've bricked their phone or had no luck.
To the best of my knowledge and research, there is no "plug and play" app or program that will root automatically. Is this accurate?
I have read of manual recommendations or guides that say they work.
This site, being the foremost authority as far as I'm concerned, is my last step in research.
Can anyone please advise if this is possible for this phone and version?
If so, is there an existing guide that is reputable that I could follow?
I thank you in advance.

A little late to post. But I am having no luck rooting my SM-870W on Telus. I used Odin and the CF-Auto-Root-kltecanactive-kltevlactive-smg870w for Marshmallow 6.0.1
I just end up with "Recovery is SeAndroid enforcing"
I then have to flash back the stock rom
Tomorrow when I have time, I am going to downgrade back to Lollipop to root it. If successful, then I will use Flashfire to update to Marshmallow 6.0.1 and see how that goes.

Well so far I successfully downgraded my phone back to Lollipop and rerooted it. . Tomorrow or next week will try updating with flashfire

I tried again to root marshmallow using flashfire, and it boot looped. So just going to stay on Lollipop and keep rooted. Will probably upgrade phone soon anyway. I don't know how others on youtube etc say they have done it, but it's not working for me.

Thanks for posting
I too have the same model phone and I'm running into the exact same issue you are. Thanks for posting which lets me know I'm not the only one facing this problem
windrider42 said:
I tried again to root marshmallow using flashfire, and it boot looped. So just going to stay on Lollipop and keep rooted. Will probably upgrade phone soon anyway. I don't know how others on youtube etc say they have done it, but it's not working for me.
Click to expand...
Click to collapse