Database Users

[Q] Safe Build for Root on SM-N900V

I'm looking to root my Note 3, and I'm curious what the safe guidelines are, I can't seem to find a definitive answer on this.
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
My current details are as follows:
Model: SM-N900V
Build: JSS15J.N900VVRUBMJ7
Am I SoL?
Thanks for the help.
NOTE: I tried searching , but it seems the search function is temporarily unavailable :crying:

crizznaig said:
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
Click to expand...
Click to collapse
Yes, you can either use the Kingo root tool or wait until "Root de la Vega" gets a fix.
Personally, I would wait instead of using Kingo: there is some privacy concerns with using Kingo since we don't actually know how/what it does.
DroidModderX said:
The verdict is still out as to whether Kingo App is anything other than a malicious virus ridden software, or an innocent one click root method for many devices. If you do decide to use this app you should do so at your own risk. This root method is completely close sourced so we aren't sure of everything contained with in it. If this bothers you then steer clear. If you don't mind your data potentially being at risk this method is a one click method that works for a long list of devices. It has been confirmed via an XDA thread that this method will work with the Verizon Galaxy Note 3 after the latest OTA update.
Click to expand...
Click to collapse

Yeah I've read the recent situations with Kingo and Vroot as well. I'm cool with waiting, I'd prefer to not have my IMEI data mined for root
I've waited thus far.
So basically I should be following developments on the Root de la Vega stuff.
Appreciate the response

Yeah I've read the recent situations with Kingo and Vroot as well. I'm cool with waiting, I'd prefer to not have my IMEI data mined for root
I've waited thus far.
So basically I should be following developments on the Root de la Vega stuff.
Appreciate the response

Bricked
bummer, i didnt see this yesterday, and i am now bricked and looking to restore somehow back to factory via odin or whatever

crizznaig said:
I'm looking to root my Note 3, and I'm curious what the safe guidelines are, I can't seem to find a definitive answer on this.
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
My current details are as follows:
Model: SM-N900V
Build: JSS15J.N900VVRUBMJ7
Am I SoL?
Thanks for the help.
NOTE: I tried searching , but it seems the search function is temporarily unavailable :crying:
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=2498850

I also just received my Note3 with that build number. Any update yet on root?

lieutenantglorp said:
I also just received my Note3 with that build number. Any update yet on root?
Click to expand...
Click to collapse
I have MJ7 and used Kingo
http://forum.xda-developers.com/showthread.php?t=2521581

Kingo Can't Connect
I have just tested Kingo with a Note 3 Verizon (N900V Firmware MJ7) and can't connect.
Thing is, I can see it find in ADB and I can issue commands via ADB. Of course USB debugging is enabled and working fine through ADB.
I'm running the latest version of Kingo 1.1.2.1770, and it just reads "Connecting service" in the bottom-right and the big "Not Connected" in the middle.
I've also attempted to connect my G-III phone which I access via ADB with no problem, and Kingo doesn't see that either.
This is my first test with a one-click root solution. I haven't found any instructions for rooting the N900V any other way (eg directly via command line) .. Anyone have any idea what I could be doing wrong, or how to root the N900V running MJ7 without Kingo?
Thank you in advance
RKM

I would assume you can use odin with stock original firmware and pit file to downgrade your phone from MJ7, use de la vega, use supersu+ "preserve superuser" functionality, then OTA update. Using supersu+/preserve option/OTA/re-enable is how I updated and kept root.

I'd be willing to bet it's your anti-virus or firewall software and that you are doing this on either Win 7 or Win 8.
Sent from my SM-N900V using Tapatalk

Also, having just read up on the latest Kingo stuff, just use it. It's fine. The latest versions don't send your IMEI. I'd still use it if they did, personally. IMEI+serials are sent around all the time when you buy/sell phones online since you need to confirm clean IMEI before paying to be sure the phone hasn't been reported stolen. Nothing bad to worry about. It's your phone, if someone could possibly do anything weird, Verizon would swap you a new one.

bigillz said:
I would assume you can use odin with stock original firmware and pit file to downgrade your phone from MJ7, use de la vega, use supersu+ "preserve superuser" functionality, then OTA update. Using supersu+/preserve option/OTA/re-enable is how I updated and kept root.
Click to expand...
Click to collapse
Doing this will soft brick your device. You cannot go back to MI9 if you are already on MJ7. Do not try to flash back to stock MI9 if you are already on MJ7.
HAZA12D_HYPERDRIVE_NOTE3

haza12d said:
Doing this will soft brick your device. You cannot go back to MI9 if you are already on MJ7. Do not try to flash back to stock MI9 if you are already on MJ7.
HAZA12D_HYPERDRIVE_NOTE3
Click to expand...
Click to collapse
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.

bigillz said:
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.
Click to expand...
Click to collapse
Not positive, but I think they were having to use the pit file with MJ7 after they had tried MI9. Just flashing MJ7 wouldn't work. I've been wrong before though.

G8orDroid said:
Not positive, but I think they were having to use the pit file with MJ7 after they had tried MI9. Just flashing MJ7 wouldn't work. I've been wrong before though.
Click to expand...
Click to collapse
Yes, that's what I've read too.
I'd be willing to bet it's your anti-virus or firewall software and that you are doing this on either Win 7 or Win 8.
Click to expand...
Click to collapse
Unfortunately I don't run any AV software other than the intrinsic Win7, and I had already setup exceptions for the app, disabled, it -- and I've been running Kingo "As Administrator" explicitly in each case.
It just seems so weird that ADB works flawless, and Kingo does not. They're basically the same thing (I believe Kingo is just running everything through ADB, right?)
Ugh .. so I can't downgrade to root, and I can't get Kingo to connect despite it not being related to AV apps and ADB working fine. Leave it to tech to turn a thirty minute project into days!!
Thanks again for any ideas

bigillz said:
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.
Click to expand...
Click to collapse
Yes, even with the pit. You cannot go back to MI9 once you update.
HAZA12D_HYPERDRIVE_NOTE3
---------- Post added at 01:50 PM ---------- Previous post was at 01:46 PM ----------
rkmFL said:
Yes, that's what I've read too.
Unfortunately I don't run any AV software other than the intrinsic Win7, and I had already setup exceptions for the app, disabled, it -- and I've been running Kingo "As Administrator" explicitly in each case.
It just seems so weird that ADB works flawless, and Kingo does not. They're basically the same thing (I believe Kingo is just running everything through ADB, right?)
Ugh .. so I can't downgrade to root, and I can't get Kingo to connect despite it not being related to AV apps and ADB working fine. Leave it to tech to turn a thirty minute project into days!!
Thanks again for any ideas
Click to expand...
Click to collapse
Do you have developer options enabled and have USB debugging enabled?
HAZA12D_HYPERDRIVE_NOTE3

haza12d said:
Do you have developer options enabled and have USB debugging enabled?
Click to expand...
Click to collapse
Absolutely, yes.
I mentioned back in the original thread, I have USB debugging enabled and successfully using ADB, which requires this along with the cert approval (required as of Android 4.2 or 4.3, can't remember now).
As a developer, I use ADB on a daily basis and have never had any issue connecting to the phones.
I've re-installed Kingo, etc -- nothing. I can even fire up a command prompt while Kingo is running and send an ADB devices to see my phone successfully connected with the (with the latest Samsung drivers, right from Kingo's site stating the requirement).
Thanks again for the ideas

rkmFL said:
Absolutely, yes.
I mentioned back in the original thread, I have USB debugging enabled and successfully using ADB, which requires this along with the cert approval (required as of Android 4.2 or 4.3, can't remember now).
As a developer, I use ADB on a daily basis and have never had any issue connecting to the phones.
I've re-installed Kingo, etc -- nothing. I can even fire up a command prompt while Kingo is running and send an ADB devices to see my phone successfully connected with the (with the latest Samsung drivers, right from Kingo's site stating the requirement).
Thanks again for the ideas
Click to expand...
Click to collapse
I agree, it doesn't make a lot of sense that Kingo wouldn't connect if you can connect manually thru ADB. I believe it does use ADB to communicate. The software will take a while to run especially on a slow connection, but I am assuming from what you've said that it never gives you a "Device Connected" status, correct?
I mentioned firewall and AV earlier because some of them will block either the app or the communication. I had Trend Micro running on one of the computers I used and it wouldn't connect until I uninstalled it.

I installed update and Kingo wont Root my device...Help!

Is there another root method I could use to root my device. Kingo goes through the whole process then fails.
Thanks!

stu5797 said:
Is there another root method I could use to root my device. Kingo goes through the whole process then fails.
Thanks!
Click to expand...
Click to collapse
Suggestions:
Make sure you have USB debugging enabled. Shut down and do a battery pull and re-try.
I haven't tried Kingo with the new update, but the battery pull seemed to help on MJ7 and I have seen where others successfully used Kingo after the update.

I did have USB debug enabled. Kingo goes through the whole process then says root failed

It worked. Forgot to turn off anti virus on computer

stu5797 said:
Is there another root method I could use to root my device. Kingo goes through the whole process then fails.
Thanks!
Click to expand...
Click to collapse
already answered

az_biker said:
already answered
Click to expand...
Click to collapse
so is kingo safe???

jrocc24 said:
so is kingo safe???
Click to expand...
Click to collapse
If you are ALREADY on MJE, root with Kingo, then install safestrap
If you are still on MI9 or MJ7, boot into odin and install MJ7 tar, accept MJE OTA, root with Kingo, install SS, profit.
With the exception of the above info, check out my SIG and see the detailed step by step!

but i mean with that whole stealing IMEI and all that... just a worry and not a reality?

jrocc24 said:
but i mean with that whole stealing IMEI and all that... just a worry and not a reality?
Click to expand...
Click to collapse
After gaining root with Kingo, there are steps in my SIG instructions how to install Chainfire's SuperSU which overwrites Kingo's superuser. Also, once rooted, I would uninstall Kingo app from pc, run quick anti-virus scan... I know dozens of users who have done this with ZERO issues, including myself.
As with ANYTHING when rooting your phone, it is YOUR call and your responsibility to change, add or remove anything related to your phone. But I can tell you, I have not heard of ONE verifiable incident of erroneous data collection or anything similar related to the use of Kingo.
Follow my steps, and enjoy! Don't forget to hit THANKS if this helped you and pass the word to others who would benefit from the step by step...

thanks man!! i hit thanks twice ill keep it in mind when i need it for tethering once they totally block it... once again thank you

Kingo is SAFE.
You also need to set your screen timeout to be 10 minutes and swipe to unlock your device to get to your home screen and leave it there while it installs.
You don't need to remove any PIN's or passwords you have, just get into the phone because Kingo will ask you to install a few programs on your device to get it to root.

RypeDub said:
Kingo is SAFE.
.
Click to expand...
Click to collapse
I don't think ANYBODY can state that 100% although it does seem relatively low risk at this point.

jmorton10 said:
I don't think ANYBODY can state that 100% although it does seem relatively low risk at this point.
Click to expand...
Click to collapse
Technically nobody can say ANY program that uses an exploit is 100% safe. Uninstall kingo from pc immediately (anti virus scan) install Chainfire's superSU immediately after root (overwrites kingo superuser)...
Notorious 3

got my new Note 3 today, i let it install the newest MJE update right away. Followed the directions with latest Kingo 1.1.5, it just sits there and says it can't connect over and over and does this little flashing between the orange and red icon on the Kingo client. Running on Windows XP, going to try again on a different pc with Windows 7 this evening. Yes USB debugging enabled and screen timeout set to max (10 minutes). Tried two different cables too. Tried different USB ports, tried rebooting phone and pc.

neyenlives said:
got my new Note 3 today, i let it install the newest MJE update right away. Followed the directions with latest Kingo 1.1.5, it just sits there and says it can't connect over and over and does this little flashing between the orange and red icon on the Kingo client. Running on Windows XP, going to try again on a different pc with Windows 7 this evening. Yes USB debugging enabled and screen timeout set to max (10 minutes). Tried two different cables too. Tried different USB ports, tried rebooting phone and pc.
Click to expand...
Click to collapse
Turn off you anti virus

Can't, I'm on a work pc right now. Will try later on my laptop at home.
Sent from my SM-N900V using Tapatalk

neyenlives said:
Can't, I'm on a work pc right now. Will try later on my laptop at home.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Make sure display timeout
is over 10 min, disable pc anti-virus. Retry even if kingo fails..took me 3 attempts
Check link in my sig for step by step
Notorious 3

It was the anti-virus I guess, worked fine first time at home on my laptop after disabling MSE real time protection.
Sent from my SM-N900V using Tapatalk

Glad you're up and running
Notorious 3

Just to confirm a few things:
Was running MJ7 rooted w/ Beans build 4
installed stock MJ7 tar through Odin
rebooted
Took MJE OTA
rebooted
rooted via Kingo
installed Chainfire's SuperSU
Installed Safestrap
restored MJ7 rom (Beans Build 4)
NOT a single issue after re-rooting with Kingo
MJE running MJ7 Rom
VERIFIED KNOX 0x0 and 0x0

Rooting Verizon Note3 Help

I've been reading the forum for few hours Friday night and yesterday and found lots of help but and videos but not on how to run this Universal De La Vega script which is where I think I'mscewing it up. I downloaded the N900VVRUBMJE_N900VVZWMJE_N900VVRUBMJE_HOME.tar.md5 from SamMobile. I ran the Universal De La Vega script using Cygwin. After a couple of attempts I figured out to move everything to the c:/ root to reduce typing errors. It produced a file with a Vega in the name as the instructions say, but I not sure I ran the script correctly. More on that in a second. I flashed the NOTE3 with the file using ODin and got a soft brick. I then flashed it with the HOME_tar.md5 I got from SamMobile and the phone rebooted and worked ok, but I'm back to stock and not yet rooted. Happy I downloaded the correct stock file and flashing it save my xss, but I still need to root.
Can I please get a little help on how the De La Vega script is executed.
These are the instructions:
Usage: ./URDLV.sh [full|csc] [stock firmware file path]
Example: ./URDLV.sh csc F:\N900PVPUBMI3_N900PSPTBMI3_SPR.tar.md5
Example: ./URDLV.sh full F:\OneClick_I537UCUBMI2.exe
full = AP and CSC (Creates a single file with both AP and CSC, no bootloaders, modems, etc.)
csc = CSC only
[stock firmware file path] - needs to be the full file path!
Drag and drop the file into the terminal window to get the full path.
I'm having trouble undertanding the second line entry. the ./URDLV.sh full ... where is the OneClick_I537?UCBM12.exe file? When I ran it I just ran the URDLV..sh csc and the URDLV.sh full both on the same N900VVRUBMJE_N900VVZWMJE_N900VVRUBMJE_HOME.tar.md5 from SamMobile. Do I only run one of the two lines on the script? And then set up Odin depending on one or two files?
I trust that this makes sense to someone, I am not Lenix command line savvy...
Thanks in advance!

I rooted my note 3 verizon via Kingo.
Was easy and quick.
Look in the Root via Kingo forum if you want to go a different route~

OneClick_I537?UCBM12.exe ="equal to" grab and drop your N900VVRUBMJE_N900VVZWMJE_N900VVRUBMJE_HOME.tar.md5
but i try it 10+ time not working for me neither....i have the OEM MJE not OTA

tigersfa8 said:
I rooted my note 3 verizon via Kingo.
Was easy and quick.
Look in the Root via Kingo forum if you want to go a different route~
Click to expand...
Click to collapse
Just looked at Kingo looks easy but I'd rather stay with sda if there's a solution. These guys are very trust worthy!

I think I figured it out. Am going to try running the script with [full] only and it generates a tar.md5 and I'll try it. But that's tomorrow, now it's SuperBowl. Thanks all.

Is Kingo chinese spyware?

I too need root help
I just got the Verizon Note 3 today and it came out of the box with build MJE on it. I tried Kingo's app to root it and it said unsupported after it tried to root it. I cannot find a method of rooting the device with this build number. I am hesitant about moving everything to the new phone just to have to wipe it again.

wizard62777 said:
I just got the Verizon Note 3 today and it came out of the box with build MJE on it. I tried Kingo's app to root it and it said unsupported after it tried to root it. I cannot find a method of rooting the device with this build number. I am hesitant about moving everything to the new phone just to have to wipe it again.
Click to expand...
Click to collapse
use "vroot"
remember disable all firewall and anti virus.
i was rooting my phone for 5 days now. finally got it rooted.

I follow all the instructions for vroot, but when I install SuperSU it tries to disable KNOX but it says failed, and root checker says I still don't have root access.

wizard62777 said:
I follow all the instructions for vroot, but when I install SuperSU it tries to disable KNOX but it says failed, and root checker says I still don't have root access.
Click to expand...
Click to collapse
try run vroot as administrator. i happened to me yesterday.

I finally got vroot to give me root access on my phone, but now I cant get SuperSU to install and update and get rid of the chinese root.

WOW
I posted the original post asking for help rooting using dela vega and still no help. Everyone says use kingo and that's apparently not working now either. So I'm going to go read up on vroot as many have suggested.
This is not the type of help that I got the last time I posted for help on my S2.
ADMIN you can close this thread it went no where.

ansel1 said:
I posted the original post asking for help rooting using dela vega and still no help. Everyone says use kingo and that's apparently not working now either. So I'm going to go read up on vroot as many have suggested.
This is not the type of help that I got the last time I posted for help on my S2.
ADMIN you can close this thread it went no where.
Click to expand...
Click to collapse
de la vega won't work with mje - there are a slew of posts stating such.
Sent from my SM-N900V using XDA Premium 4 mobile app

Reilly1812 said:
de la vega won't work with mje - there are a slew of posts stating such.
Click to expand...
Click to collapse
Correct. De la vega no longer works on the latest Verizon builds. Samsung patched the exploit up. Kingo has been having very slow website and server problems, so people have not been able to root using that either. The only one that's working correctly at the moment is vRoot.
Once you root with vRoot, do a search for chainfire's SU 1.00 apk and flash that in SafeStrap. That will get rid of the Chinese SU app. Then you can also uninstall the other Chinese app that gets installed.

-BoneZ- said:
Correct. De la vega no longer works on the latest Verizon builds. Samsung patched the exploit up. Kingo has been having very slow website and server problems, so people have not been able to root using that either. The only one that's working correctly at the moment is vRoot.
Once you root with vRoot, do a search for chainfire's SU 1.00 apk and flash that in SafeStrap. That will get rid of the Chinese SU app. Then you can also uninstall the other Chinese app that gets installed.
Click to expand...
Click to collapse
Just bought a VZW Note 3 (N 9000V UD) and I could swear it came with MJE but I still got an OTA and since I was reading that Kingo worked with MJE, I took it. Kingo didn't work before as far as I could tell, but I had only tried a few times. After, I can say definitively that Kingo is useless.
Tried De La Vega next and can also confirm that it's useless on OTA MJE. Got an error during ODIN upload and was soft-bricked at that point. ODIN'd back to OEM MJE, tried De la Vega again and got the same result; soft-brick.
As of 20140209, I cannot find a way to root a new VZW Note 3 but I'm still looking because as nice as this hardware is, I couldn't care less if I can't even restore my apps/data (backed up with TB).
I have looked at vroot, but since it's not in English, I'm not sure how far I'd get and I'm nervous as hell relying on something that's such a clear security risk.

rainabba said:
I have looked at vroot, but since it's not in English, I'm not sure how far I'd get and I'm nervous as hell relying on something that's such a clear security risk.
Click to expand...
Click to collapse
The vRoot software for your PC is in English. Only the SU app is in Chinese, but you need to overwrite that SU app with a secure one like chainefire's anyway.
The security risk is minimal if you have good security software on your PC and if you replace the Chinese SU with a more secure one. And the security risk is virtually eliminated if you install Safestrap and then use a different ROM.

-BoneZ- said:
The vRoot software for your PC is in English. Only the SU app is in Chinese, but you need to overwrite that SU app with a secure one like chainefire's anyway.
The security risk is minimal if you have good security software on your PC and if you replace the Chinese SU with a more secure one. And the security risk is virtually eliminated if you install Safestrap and then use a different ROM.
Click to expand...
Click to collapse
I did get rooted after some 3 hours of sifting through old posts and figuring out how to get through the Chinese interface of vroot but I saw some warnings while installing that I don't like (mtkcamera) and so far, I've had to re-root at least 6 times while trying to get SuperSU in place.
All the directions indicate that I need to launch SuperSU, grant it permissions, then continue but when I open it, I immediately get the "outdate binary" prompt and no superuser prompt so I can't move forward with this one. I'm going to try an older version of SuperSU in the hopes that it will be less agressive with the binary update and perhaps give me a shot at authorizing it.
UPDATE:
Thanks to cubarican84, I used the following SIMPLE solution to clean up the chinese superuser mess: http://www.w0lfdroid.com/2013/11/How-to-Remove-Replace-VRoot-Chinese-superuser-with-SuperSU.html?m=1

Reilly1812 said:
de la vega won't work with mje - there are a slew of posts stating such.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I thought it worked but tripped knox.
Sent from my SM-N900V using Tapatalk 2

recDNA said:
I thought it worked but tripped knox.
Sent from my SM-N900V using Tapatalk 2
Click to expand...
Click to collapse
With MJE just soft bricks. Unless there's a trick like repartitioning or something. But nobody has chimed in on that thread despite numerous help requests.
Just got Kingo working again tonight. May have to try a few times. I succeeded using USB 3 cable in MTP USB 3.0 mode.
Sent from my SM-N900V using Tapatalk

Were you able to update supersu in the playstore?
Sent from my SM-N900V using Tapatalk 2

[Q] Note 3 Manual Re-Root - no SU binary installed

I rooted my device with Kingo Android root. I am currently running android OS 4.3.
Everything was going just fine until just today when opened SuperSU and it told me that there is no SU binary installed. SuperSU cannot install it.
Pretty much I need to manually re-root my device.
I am not aware of any recovery files that I may have. To clarify, I have never backed up my device in any way. I have only had it for a month, and there is hardly anything on it. I figured, why bother? Well now I know.
I have done quite a few google searches about this, and I can not find any help.
What is my best course of action?
Thank you very much.

Try reflash and re-root with cf-auto root through Odin. A a small question: u still have root right to install some app such root explorer and titanium backup?
Sent from my SM-N9005 using XDA Premium 4 mobile app

hhai2pth said:
Try reflash and re-root with cf-auto root through Odin. A a small question: u still have root right to install some app such root explorer and titanium backup?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunatly, I no longer have root. None of my root apps can get root permissions because the SU binary is missing.
I tried flashing my firmware, but now my phone is stuck in an unusable state. The official firmware leaves me unable to boot with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I flash a different ROM on top of that one, all my spen stuff is messed up.
This is way different from jailbreaking. There are so many rom files I have a hard time finding the one I need.
SM-900A in case anyone wants my number.

DrShenanigan said:
Unfortunatly, I no longer have root. None of my root apps can get root permissions because the SU binary is missing.
I tried flashing my firmware, but now my phone is stuck in an unusable state. The official firmware leaves me unable to boot with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I flash a different ROM on top of that one, all my spen stuff is messed up.
This is way different from jailbreaking. There are so many rom files I have a hard time finding the one I need.
SM-900A in case anyone wants my number.
Click to expand...
Click to collapse
You need to go on sammobile and download your stock firmware (you probably want to stay on 4.3 unless your particular phone and carrier have root capabilities on 4.4.2 which verizon and att do not yet have) then flash it through odin... just search your model # through sammobile and it will show all the available stock firmwares. That will at least get you running again then u will have to root it again from there
Posted from my beast of a VZW Note 3!!

I downloaded the firmware from that site and have tried to flash it.
I get an Error Meassage:
SW REV CHECK FAIL : [sb1]Fused 2 > Binary 1

DrShenanigan said:
I rooted my device with Kingo Android root. I am currently running android OS 4.3.
Everything was going just fine until just today when opened SuperSU and it told me that there is no SU binary installed. SuperSU cannot install it.
Pretty much I need to manually re-root my device.
I am not aware of any recovery files that I may have. To clarify, I have never backed up my device in any way. I have only had it for a month, and there is hardly anything on it. I figured, why bother? Well now I know.
I have done quite a few google searches about this, and I can not find any help.
What is my best course of action?
Thank you very much.
Click to expand...
Click to collapse
1st : I dunno ur device which version of note 3.
2nd : kingo sometimes for some device not working well. Try avoid to use this method. Try cf-autoroot instead. Easy nd simple, but knox will trip.
3rd : have u tried update to latest supersu?
3rd :
Sent from somewhere under the sky, at the vorner of this rounded earth.

antique_sonic said:
1st : I dunno ur device which version of note 3.
2nd : kingo sometimes for some device not working well. Try avoid to use this method. Try cf-autoroot instead. Easy nd simple, but knox will trip.
3rd : have u tried update to latest supersu?
3rd :
Sent from somewhere under the sky, at the vorner of this rounded earth.
Click to expand...
Click to collapse
Updating SuperSU is what cause this mess, I believe. It's too late for that now anyhow, because my phone does not boot.
I have the SM-900A. There is no cf-autoroot for it. Not that I canfind at least.

DrShenanigan said:
Updating SuperSU is what cause this mess, I believe. It's too late for that now anyhow, because my phone does not boot.
I have the SM-900A. There is no cf-autoroot for it. Not that I canfind at least.
Click to expand...
Click to collapse
Try this, mate
http://forum.xda-developers.com/showthread.php?t=2466423

[Q] NC-4 can't get it rooted?....Help please

Ok I did take that darn update and so am on: NC-4
I used the " towelroot " when it was first introduced.
I have the " Unlocked padlock " with the word "custom" under it when I reboot.
I have used " Root checker basic " by Joeykrim. " this device does not have proper root access".
I have been reading loads of thread's but can't find anyone else who is having the same issue.
I then tried towelroot 2 and 3 when they came out, but I still can't get my phone rooted.
I don't know what to try now.

Did You update the su binaries? As per op
Sent from my SM-N900V using XDA Premium 4 mobile app

Have you just tried a different root checker?

I did and have
Sorry for my slow response, RL got crazy for a few days there.
I did update the SU, via the link to chain fire
I have tried multiple root checkers.
I am about to go through the steps again.

j_axxy said:
Sorry for my slow response, RL got crazy for a few days there.
I did update the SU, via the link to chain fire
I have tried multiple root checkers.
I am about to go through the steps again.
Click to expand...
Click to collapse
If it doesn't work again try reflashing the NC4 stock tar via odin and trying the towelroot process again. The SU binaries not being up to date should have no effect on whether you are actually rooted or not.

FIXED
kinstre11 said:
Try reflashing the NC4 stock tar via odin and trying the towelroot process again.
Click to expand...
Click to collapse
That got it done, thank you kindly kinstre11.

My pleasure.