Database Users

[Q] Atrix Won't Root? *HELP*

Hey guys,
So my brother recently purchased a Bell Motorola Atrix. I have been trying to root it for him in order to install the hack where you can access the WebTop environment via a normal HDMI cable.
I tried SuperOneClick, and it says rooting successful (even after it does the test to determine if the device is rooted) and SuperUser does appear in the applications list. I also tried UniversalAndroot, also to no avail.
However, any applications that require root claim that the device is not rooted.
Are there any other ways of rooting this device? Or am I just doing something wrong? (keep in mind I have rooted several other devices with SuperOneClick, and those have all been successful)
Please help,
Thanks,
DS1495

look for "adeo" in the dev forum. try that

Try rebooting? That's what happened with mine.

franciscojavierleon said:
look for "adeo" in the dev forum. try that
Click to expand...
Click to collapse
DONT DO THIS.
He has a Bell Atrix.

I had to toggle debug on and off a few times before it would move past waiting for device.
Make sure you have the mkro drivers installed. Also the phone should be in phone portal mode, I believe.
Good luck
Sent from my MB860 using XDA App

joelszs said:
I had to toggle debug on and off a few times before it would move past waiting for device.
Make sure you have the mkro drivers installed. Also the phone should be in phone portal mode, I believe.
Good luck
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I don't think it matters what it's set as, but I believe most devs recommend none.

DS1495 said:
Hey guys,
So my brother recently purchased a Bell Motorola Atrix. I have been trying to root it for him in order to install the hack where you can access the WebTop environment via a normal HDMI cable.
I tried SuperOneClick, and it says rooting successful (even after it does the test to determine if the device is rooted) and SuperUser does appear in the applications list. I also tried UniversalAndroot, also to no avail.
However, any applications that require root claim that the device is not rooted.
Are there any other ways of rooting this device? Or am I just doing something wrong? (keep in mind I have rooted several other devices with SuperOneClick, and those have all been successful)
Please help,
Thanks,
DS1495
Click to expand...
Click to collapse
Use aroot (dev section) worked great on 1st try on my Bell Atrix

Whatever works I guess
PixoNova said:
I don't think it matters what it's set as, but I believe most devs recommend none.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

Thanks guys, aRoot worked wonderfully! First try!

I have tried the aRoot on the Atrix I just bought yesterday from Bell (I am now a bell customer :-( ) but it doesn't work. I must be missing something. I double click the script, it runs through all the steps, even says, rebooting at the bottom, but it does nothing. I press any key to continue, and nothing.
any thoughts would be appreciated.
Thanks,
AZ

Figured it out, turns out it wasn't recognizing the adb driver.
nick78ru said:
Had this problem. While connected (as USB storage) uncheck USB debugging and and enable it again. Check in Control Panel=>Device manager for ADB Services (should be at the top with sublisting for Motorola usb device or smthing like that).
Then open command promt:
cd\
cd\AndroidSDK(or whatever you called the SDK folder)\tools\
adb devices
Let me know if it helps
Click to expand...
Click to collapse

Warranty Process

I have a RAZR M running on T-Mobile. All was good, but I guess I accidentally took the update last night, because I woke up my phone to be greeted with the "your device has been updated" screen. I was trying to avoid it because I was rooted and wanted to keep the possibility of unlocking the bootloader, but oh well...it's not a big deal. However, now my phone keeps rebooting itself. I haven't narrowed it down to whether it's a consistent time between boots or what, but I've had at least 4 or 5 times since last night where I either glance over and see the boot animation playing, or I've been greeted by the "SIM is from an unknown source" screen when I wake the phone.
There's no chance Verizon will just swap it out for me, is there? Since I'm not their customer, I'm assuming I'd have to go through Motorola, which probably takes forever.

Motos turn around rate is rather fast... 10 days total maybe... 2 shipping to get to them they have to have it done in 5 business days... 2-3 days shipping to get it back to you... but with root they may not fix it... either way its worth a shot if you can go without a phone that long...
Sent from my XT907 using xda app-developers app

Oh, cool, that's not too bad. I'll try going into Verizon tomorrow just to see if I get lucky, but otherwise, I'll get in touch with Motorola.
I had root before, but the update removed it, so it shouldn't be an issue. It's too bad we can't RSD back to 4.1.1. The phone was perfect until the update was installed.

Just redo the NV edit and you don't have to return the phone, you can keep using it on GSM carriers.
The same NV edit works fine under the new build and you don't need root to use RadioComm.
There is also a way to revert to the prior rootable version and then protect root and update again keeping root.

cellzealot said:
Just redo the NV edit and you don't have to return the phone, you can keep using it on GSM carriers.
The same NV edit works fine under the new build and you don't need root to use RadioComm.
There is also a way to revert to the prior rootable version and then protect root and update again keeping root.
Click to expand...
Click to collapse
Sorry, I don't think I was clear. I did redo the NV edit, and that works as expected. It's just that the phone keeps freezing and rebooting. It's done it another 2 times (make that 3...it just did it again) since I posted this thread. The only thing that has changed from yesterday to now is that it now has the update (and a factory reset, since I hoped that would solve the issues).
How do I go back to a rootable version? That would be easiest if possible, but I read that RSD doesn't allow you to downgrade unless you have an unlocked bootloader.

Ok I misunderstood then. Check this link for the reversion method. It is for the HD but the same principle applies to the M as well.
I posted an edited XML file for the XT907 in that thread but there has been more work done since then and a fully scripted tool was made up which may not have been released yet.
This was all worked out over the last couple of days, so check that thread for the most recent info.
Basically you flash back in RSD Lite with the previous full XML.zip but using an edited XML file that skips the tz.mbn and gpt_main0.bin along with the getvar lines.
The boot up and root under that version with Motochopper and use Voodoo root keeper and protect and temp unroot and update again to the current build.
http://www.droidrzr.com/index.php/t...18799201-ota-locked-bootload-razr-hd-test-it/

cellzealot said:
Ok I misunderstood then. Check this link for the reversion method. It is for the HD but the same principle applies to the M as well.
I posted an edited XML file for the XT907 in that thread but there has been more work done since then and a fully scripted tool was made up which may not have been released yet.
This was all worked out over the last couple of days, so check that thread for the most recent info.
Basically you flash back in RSD Lite with the previous full XML.zip but using an edited XML file that skips the tz.mbn and gpt_main0.bin along with the getvar lines.
The boot up and root under that version with Motochopper and use Voodoo root keeper and protect and temp unroot and update again to the current build.
http://www.droidrzr.com/index.php/t...18799201-ota-locked-bootload-razr-hd-test-it/
Click to expand...
Click to collapse
Awesome, thanks! It looks like Kaos is working on a tool for the M, so I'll probably just wait for that. I'm way to tired to read and follow instructions tonight anyway. Thanks for the great work you guys do!

freak4dell said:
I had root before, but the update removed it, so it shouldn't be an issue. It's too bad we can't RSD back to 4.1.1. The phone was perfect until the update was installed.
Click to expand...
Click to collapse
I was just thinking about the root checker in the recovery menu... the "qe0/0 ,1/1 if your rooted and 0/1 if you have rooted"...
Sent from my XT907 using xda app-developers app

Is your phone still freezing and rebooting. If your phone stopped doing that, do you know what you did to stop this because I'm now facing the same problem.
Sent from my XT907 using xda app-developers app

ccdsatt said:
Is your phone still freezing and rebooting. If your phone stopped doing that, do you know what you did to stop this because I'm now facing the same problem.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Mine is still doing it. It's either just a random coincidence that it happened the same time that I took the update, or it's caused by a part of the update that was skipped by the roll-back procedure. Either way, I've contacted Motorola and will be sending the phone to them this week. I just don't feel like dealing with trying to fix it myself, and if the X turns out to be decent, I'm going to end up selling the M so I want it to be in good condition for a good resale value.
Now I need to see if the files to RSD to a completely stock version of the newest build are available anywhere.

[Q] Going in circles

I promise that I have been reading threads for 2 weeks trying to figure out how to solve my problem without posting any questions, because I know no one likes to repeat themselves! I made a little bit of progress, but now I don't know what to do.
I bought my RAZR M in February. I took it out of the box and activated it. I never rooted it - had no intention of rooting it. Everything was great until the April update (98.15.66). All sorts of apps started crashing, background, Chrome, text messaging... phone kept deleting Contacts...it was a mess. I posted in the Moto Support forum and was advised to reset, which I did. It helped a little, sometimes apps still crashed, but I was dealing with it. I know the phone took at least one more update after that, but I don't know which. Then November 8, I did the OTA to 98.30.1. Phone got stuck on the red eye during boot. Tried clearing cache, reset, no luck. Called Moto support and they said they couldn't do anything unless I paid them $120 to flash the phone, because according to their info, my phone was rooted!! I never rooted it, I didn't know anything about rooting (still don't, really). I wonder if something failed during one of these updates and triggered their root checker. After reading threads here on XDA, I was able to use RDS lite to 98.16.3. So at least the phone boots, but now it keeps wanting to do the OTA to 98-30.1.
I assume I should avoid taking the OTA, but I don't know how to do that without hitting "Later" every 12 hours. If I'm understanding correctly, since I have 98.16.3 my bootloader is locked and there is nothing I can do about that. I thought maybe Titanium Backup would help so I could at least freeze the updater, but I don't have SU/root access to be able to do that. Where do I go from here? Thank you very much for any help!

So you've never been rooted and moto said it had been... Did you buy it from Verizon? Lets check and see if that device has ever been rooted... Power of the device... Power on while holding volume up + volume down... Select recovery...when you see Android Andy hold volume down tap volume up... Now you should see QE process does it say 0/0 or 0/1... If it says 0/0 your phone has never been rooted... If it said that I would either call them back.. After taking pix of that... And inform them of that.. Or take it to a Verizon store and request a new device... Post the pic in your topic on Motorola's forum and say how they refused service because your device was rooted when it wasn't... Matt the forums manager should reply and assist then
Sent from my XT907 using xda app-developers app

@sasperson
Where did you "clear cache" during your bootloop? I dont believe stock recovery has that option. Also how did you use RSDLite if you have a locked bootloader, wouldn't it just fail. Not trying to be a ****, i'm just pointing out the inconsistencies.

ATTACK said:
@sasperson
Where did you "clear cache" during your bootloop? I dont believe stock recovery has that option. Also how did you use RSDLite if you have a locked bootloader, wouldn't it just fail. Not trying to be a ****, i'm just pointing out the inconsistencies.
Click to expand...
Click to collapse
Stock recovery does have the option to clear the cache partition...you can RSD I up or to the current version...
Sent from my XT907 using xda app-developers app

ezknives said:
Stock recovery does have the option to clear the cache partition...you can RSD I up or to the current version...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Ok. I didnt know stock recovery had any options, never used it. Didn't he RSD Lite from 98.30.1 to 98.16.3. I thought you couldn't downgrade with a locked bootloader.

I apologize my brain saw .16 the first time I read it from where I'm not used to seeing .30
Sent from my XT907 using xda app-developers app

It does say 1/1. I don't believe it said that when I did the FDR back in April/May when I first starting having issues after the update to 98.15, but I can't say 100% for sure since I didn't even know what it meant up until a couple of weeks ago when I started reading up.
How it got like that, I don't know. I bought the phone from Amazon. Sold by Amazon, marked as Brand New. I didn't buy it from a Joe Schmo marketplace seller.
I have no idea for sure if my bootloader is unlocked or not. From what I've read, it seems that if you have 98.16.3, then it has to be. When I go into the AP fastboot screen, it says Device Status: Locked.
I did post on the Motorola forum and someone there told me how to check in the recovery menu for the root status, but since it says 1/1, someone recommended that I come over here to XDA, which is how I ended up doing the RSD lite thing to at least get my phone functional again.
All of this stuff is so far over my head...I'm not really interested in customization or removing the bloatware - I just disable or ignore it. I am only looking to get my phone back running like normal without telling it "Later" every 12 hours to avoid the update. And if I'm understanding correctly regarding the bootloader, there aren't many customization options anyway. Do I just wait to see if the 98.30 update gets added on the droid-developers.org site?

I
sasperson said:
It does say 1/1. I don't believe it said that when I did the FDR back in April/May when I first starting having issues after the update to 98.15, but I can't say 100% for sure since I didn't even know what it meant up until a couple of weeks ago when I started reading up.
How it got like that, I don't know. I bought the phone from Amazon. Sold by Amazon, marked as Brand New. I didn't buy it from a Joe Schmo marketplace seller.
I have no idea for sure if my bootloader is unlocked or not. From what I've read, it seems that if you have 98.16.3, then it has to be. When I go into the AP fastboot screen, it says Device Status: Locked.
I did post on the Motorola forum and someone there told me how to check in the recovery menu for the root status, but since it says 1/1, someone recommended that I come over here to XDA, which is how I ended up doing the RSD lite thing to at least get my phone functional again.
All of this stuff is so far over my head...I'm not really interested in customization or removing the bloatware - I just disable or ignore it. I am only looking to get my phone back running like normal without telling it "Later" every 12 hours to avoid the update. And if I'm understanding correctly regarding the bootloader, there aren't many customization options anyway. Do I just wait to see if the 98.30 update gets added on the droid-developers.org site?
Click to expand...
Click to collapse
If it says 1/1 that means your currently rooted (0/1 it has at some point been rooted) download a root checker from google play... If it is rooted I'm sure you could install a super user then freeze the updater...
Sent from my XT907 using xda app-developers app

ATTACK said:
Ok. I didnt know stock recovery had any options, never used it. Didn't he RSD Lite from 98.30.1 to 98.16.3. I thought you couldn't downgrade with a locked bootloader.
Click to expand...
Click to collapse
No, the phone tried to install 98.30.1 through OTA, but failed and got stuck on the red eye during boot. Moto said the update failed because I was rooted, which I never rooted the phone. How the phone came to say 1/1 on the recovery screen root check, I'll never know, but it's water under the bridge now.
Once I came here and read how to use RSD lite, I flashed it to 98.16. I don't know what version I was running before the 98.30.1 OTA attempt on Nov. 8.
I downloaded Root Checker. For SU it says, "Not found."
Root Access: "no access"
Is this because I only flashed the VRZ_XT907_9.8.1Q-78-1_1FF.xml, which from what I understand is straight stock? Is the phone technically not really "rooted" then? Is it possible to get the Super Access at this point, or am I stuck?
Again, thank you for your help and patience!

sasperson said:
No, the phone tried to install 98.30.1 through OTA, but failed and got stuck on the red eye during boot. Moto said the update failed because I was rooted, which I never rooted the phone. How the phone came to say 1/1 on the recovery screen root check, I'll never know, but it's water under the bridge now.
Once I came here and read how to use RSD lite, I flashed it to 98.16. I don't know what version I was running before the 98.30.1 OTA attempt on Nov. 8.
I downloaded Root Checker. For SU it says, "Not found."
Root Access: "no access"
Is this because I only flashed the VRZ_XT907_9.8.1Q-78-1_1FF.xml, which from what I understand is straight stock? Is the phone technically not really "rooted" then? Is it possible to get the Super Access at this point, or am I stuck?
Again, thank you for your help and patience!
Click to expand...
Click to collapse
if your on version listed in screenshot yes you can root it ... Use motochopper 1.3
Sent from my XT907 using xda app-developers app

ezknives said:
if your on version listed in screenshot yes you can root it ... Use motochopper 1.3
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Ok, I will give that a try. I have read about motochopper, but was confused as to whether it was the right thing for the version I'm running, I think I was reading "Build version," mixing that with "System version," and getting scared when it said it will brick the phone if not used on the right version. Since my Build Number is 9.8.1Q.78-1, the directions and links on droidrazr.com posted by livinginkaos and SamuriHL should work for me, right? (assuming I can follow the directions, that is)
I wonder if this will fix the strange random app crashes I've been getting ever since the April update. It's very inconvenient to have my text message history wiped.
Thank you for the advice, ezknives!

*Update*
I used motochopper! I used Titanium backup and froze the updater.apk! \o/
I have one more question - now that I have this super user access, is it still best to just disable/freeze the bloatware instead of removing it altogether? I read that some people have used Titanium backup to delete it, I also recall reading that some people had issues with updates if they deleted them and ended up having to reinstall them...?

sasperson said:
*Update*
I used motochopper! I used Titanium backup and froze the updater.apk! \o/
I have one more question - now that I have this super user access, is it still best to just disable/freeze the bloatware instead of removing it altogether? I read that some people have used Titanium backup to delete it, I also recall reading that some people had issues with updates if they deleted them and ended up having to reinstall them...?
Click to expand...
Click to collapse
Yes it's best to freeze it all rather then delete it.... So you don't have to do as much when the next OTA comes out...
Sent from my XT907 using xda app-developers app

ezknives said:
Yes it's best to freeze it all rather then delete it.... So you don't have to do as much when the next OTA comes out...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Everything seems to be back to normal - at least back to how it was a few weeks ago. It still has the random background app crash, but whatever. I've been living with that since the April update. I'm just happy my phone is functional again.
Thanks again for the help!
:victory:

[Question] Kingo Root 1.4.2

So, I periodically try different Root methods on this sm-n900v and tonight I tried Kingo Root (PC), and one time when it rebooted it showed the custom unlocked icon. Is this normal? I figure I'm going to try and repeat what I did until it shows that to me again...
Feedback is always appreciated!

When you say custom unlocked icon do you mean when the Galaxy screen comes on? I see that, but I used Towelroot instead of Kingo

I'm on 5.0 OB6.

Interesting. I don't think it's supposed to work like that

AlexanderJohn said:
I'm on 5.0 OB6.
Click to expand...
Click to collapse
You can try forever...but so far...there is NO way to root OB6
Sent from my Note 3 via Tapatalk

I know, but the custom unlock screen came up and I'm curious as to why. Sorry I didn't clarify that.
Sent from my SM-N900V using Tapatalk

AlexanderJohn said:
I know, but the custom unlock screen came up and I'm curious as to why. Sorry I didn't clarify that.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
All that means is you attempted to load a non standard system.....it obviously didn't mean it worked. It's your time, your effort, your phone...have at it.
But people who know a whole lot more about rooting and the issues involved than you or I have been trying for quite a while and have come up empty handed.
Sent from my Note 3 via Tapatalk

Useful and helpful
donc113 said:
All that means is you attempted to load a non standard system.....
Click to expand...
Click to collapse
neither useful or helpful
donc113 said:
it obviously didn't mean it worked. It's your time, your effort, your phone...have at it.
But people who know a whole lot more about rooting and the issues involved than you or I have been trying for quite a while and have come up empty handed.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Sent from my HTC6435LVW using Tapatalk

hey guys, i dont know much about root script but i got an idea. Cant we somehow brick out bootloiader partition so we can flash the old firmware and than root? tell me what you think.

kstoianov said:
hey guys, i dont know much about root script but i got an idea. Cant we somehow brick out bootloiader partition so we can flash the old firmware and than root? tell me what you think.
Click to expand...
Click to collapse
I've actually thought this same thing, maybe wipe the phone out 100% so it would be as if nothing was there then find a write program to put the older bootloader on their or maybe in that case could get into the bootloader and unlock it and flash the phone as new...hmm, I've had that thought many time but I think it would just completely mess the phone up beyond Bootable or working
Sent from my SM-N900V using Tapatalk

thunderblaster88 said:
I've actually thought this same thing, maybe wipe the phone out 100% so it would be as if nothing was there then find a write program to put the older bootloader on their or maybe in that case could get into the bootloader and unlock it and flash the phone as new...hmm, I've had that thought many time but I think it would just completely mess the phone up beyond Bootable or working
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I am ready to try but i need tool to wipe my aboot.img and a software to flash via qualcomm mode and old aboot.img

I'd be willing to do this stuff to if we can find the right tools

The thing about doing a full 100% wipe to reload say the inital factory firmware is what is called a jtag is needed it is a serial connection to the flash chips that is used in the factory to do the inital programming. The problem is this connection is cut off or more often not made accessible to assembled units.
there was with previous samsung phones a usb jtag kicking dongle that could kick a hard bricked phone into a sorta download mode.
this is not present on the note 3 and the note 3 has e fuses that permanently blow preventing some of these things. Additionally there is a built in check to prevent the loading of bootloaders that are unsigned or older than the current bootloader.
so in the end the only thing messing with wiping the boot loader is going to acomplish is hard or soft bricks...

it could be off topic but how they sign their updates? cant we fool the factory recovery?

mirrin said:
The thing about doing a full 100% wipe to reload say the inital factory firmware is what is called a jtag is needed it is a serial connection to the flash chips that is used in the factory to do the inital programming. The problem is this connection is cut off or more often not made accessible to assembled units.
there was with previous samsung phones a usb jtag kicking dongle that could kick a hard bricked phone into a sorta download mode.
this is not present on the note 3 and the note 3 has e fuses that permanently blow preventing some of these things. Additionally there is a built in check to prevent the loading of bootloaders that are unsigned or older than the current bootloader.
so in the end the only thing messing with wiping the boot loader is going to acomplish is hard or soft bricks...
Click to expand...
Click to collapse
That's kinda what I figured

kstoianov said:
it could be off topic but how they sign their updates? cant we fool the factory recovery?
Click to expand...
Click to collapse
Encrypted I know you guys are grasping as straws in desperate hope of the phone not being as locked down as previously thought. But if it were such a simple task of getting the dev device boot loader and fooling the system into thinking it is a legit update we would have an open phone.
the things with the nc2 and nc4 bootloaders was they for some reason did not use the check correctly and left it open for us.

OneClickRoot Sprint, anyone?

Curious as to whether anyone has tried this. Suspicious as I haven't seen it here lol. Thoughts?

Good luck lol

yeah i saw that site this morning.. anyone have luck?

Jaws4God said:
yeah i saw that site this morning.. anyone have luck?
Click to expand...
Click to collapse
OCR is non attainable on this device.
Too much stuff to do manually.

elijah420 said:
OCR is non attainable on this device.
Too much stuff to do manually.
Click to expand...
Click to collapse
has anyone tried and it fail?

Jaws4God said:
has anyone tried and it fail?
Click to expand...
Click to collapse
OCR is not attainable on this device.
Too much to do manually.

I always recommend manual methods over one click methods you never know what kind of crap these programs will put on your phone.
Its not the first situation where spyware has ended up on phones from these sites. King Root is a good example.
Sent from my LG-H918 using XDA-Developers Legacy app

evo4g63t said:
I always recommend manual methods over one click methods you never know what kind of crap these programs will put on your phone.
Its not the first situation where spyware has ended up on phones from these sites. King Root is a good example.
Sent from my LG-H918 using XDA-Developers Legacy app
Click to expand...
Click to collapse
oh thank you for the heads up.. I was just hoping to find a way to just get simple root on my phone to have access to Gravity Box ... but i do not want to unlock my bootloader and have a custom recovery..
Thanks!

Jaws4God said:
oh thank you for the heads up.. I was just hoping to find a way to just get simple root on my phone to have access to Gravity Box ... but i do not want to unlock my bootloader and have a custom recovery..
Thanks!
Click to expand...
Click to collapse
It's a scam. My dad (without consulting me) tried it on a moto g4. Not only did it not work, he ended up with spyware and spam that I had to get rid of.
There is no simple root. Any phone going forward that is rootable will have to be connected to a pc and adb or odin used to exploit a vulnerability manually.

One click Root Worked For Me (H91810J) T-MO
sjr19 said:
Curious as to whether anyone has tried this. Suspicious as I haven't seen it here lol. Thoughts?
Click to expand...
Click to collapse
OneClickRoot worked on my T-Mobile H91810J. I've rooted a lot of phones and tried the recowvery and numerous other methods. I couldn't get TWRP to flash because I was missing a few commands not listed. They connect through the program (Oneclickroot) and use a program called Vysor. It has to be manually done by one of their techs. I was able to see and copy their commands and files but again I have a T-mobile not Sprint. To be sure, open a chat session and they will 100 percent verify if they can do it. They ask for everything from the model number, to the build number, security patch info...etc . It has to be done manually by the tech not by the program which will tell you after trying to root that you need to have it done manually by them.
They are legit but not cheap. The up side is they can do it right from your pc or most any pc . It's a 24/7 operation also. Pay the extra for the protection. It isn't cheap but it sure is easy and now I am 99 percent sure I can follow their steps if needed. I see where I messed up in the shell commands. I hate my bootloader locked When I boot though. I still have to access it through ADB unless I am missing something. I also still have the annoying orange oem warning screen. Otherwise full root access. I just don't know what I am going to do if something happens and it has to be reset...etc. I love lux and color changer pro. Completely transforms the device in my opinion. Hopefully we have a solution by then to bypass the entire thing. If I could get a hold of chainfire I'd send the code and files right to him or anyone capable of making this easier on everyone.
I plan on posting the code in the near future I just haven't had time. More to follow. OneClickRoot is legit but not cheap. You also have to have some trust to allow a remote connection. If they say they can do it they can. I tried doing the recowvery step by step and it kept locking up on me do to FRP. I messed up some additional shell commands which I didn't know I needed to actually flash twrp.
I am almost positive they can do the sprint version. Just check with them first via chat which is free.

Unless they have found another exploitable security hole, or your phone has NOT taken the zv6 update, your phone is NOT rootable.
The exploit that allowed dirty cow/Santa/elf, copy on write, has been plugged.
Legitimacy of their operation aside, the exploit was plugged with the zv6 update.