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.

[Q] Rooting w/Kingo App Question

Please forgive me if this has been discussed elsewhere. I could not locate it. Anyways, I have the Verizon Samsung Galaxy Note 3 with the latest software...Android 4.3, build MJE. My goal is to hopefully root the device and then install SS to add a ROM. Previously I have the Galaxy S3, which was running a custom ROM. I had no problems with my S3. Since the boot loader of the Note 3 is locked, it's not as easy to do. I keep reading about using Kingo but I'm not sure if it will actually will work with this phone. Has anybody out there successfully rooted their phone with Kingo? Please respond if you have. I have a free day and would love to spend it customizing my phone.
Thanks!

tss01 said:
Has anybody out there successfully rooted their phone with Kingo? Please respond if you have. I have a free day and would love to spend it customizing my phone.
Click to expand...
Click to collapse
Yes. It was really not difficult although it took me a few tries to successfully get SS working. Although Kingo kept saying I was rooted, SS said I was not rooted and it did not have SU access. I just removed SS and SU and un-rooted and tried again. The 3rd time it just worked. In hindsight I think I was having a problem with the cable, that came with the phone, maintaining a USB connection.

Rooting w/Kingo
Hi,
I went ahead to gave it a shot. First I made sure my anti-virus was disabled then I started Kingo and following the onscreen prompts. I automatically downloaded needed drivers. It then told me to re-connect my phone. I did and within a couple of minutes I get "ROOT Failed Not Support". I tried it two more times with the same result.
Any suggestions on my next step cuz I'm out of ideas.
Thanks!

I used it successfully last night, but on MJ7, not MJE.
I didn't read very carefully and had my phone in download/Odin mode.
Kingo recognizes that and attempted exploits against the bootloader - which failed.
So I booted the phone (with ADB / USB debugging on), and Kingo automatically recognized that and succeeded.
Just mentioning in case that's what is going on.

I've used it twice now, most recently about 12 hours ago. Haven't had a problem doing it. Worked first try both times. Normally booted with USB debugging enabled, connected and ran the program. Windows 8.1 laptop. Verizon GN3 fresh odin of MJE and am now rooted with SS installed and running Beans B6 on the stock slot.
Did you get this situated OP? We would love to help get you up and running so you can customize away.

Rooting w/Kingo
There must be some special trick to get Kingo to work properly. I did disable my anti-virus on my computer. I forgot that I have an anti-virus program on my phone as well. Should I disable that also? Is there some special way that I need to install my drivers? I'm really lost right now.
Thanks, for any help.

tss01 said:
There must be some special trick to get Kingo to work properly. I did disable my anti-virus on my computer. I forgot that I have an anti-virus program on my phone as well. Should I disable that also? Is there some special way that I need to install my drivers? I'm really lost right now.
Thanks, for any help.
Click to expand...
Click to collapse
Kingo should install the drivers for you. As far as the anti virus on your phone that could be a problem. I've never tried when I wasn't bare bones stock before I installed anything. Are you adverse to doing a factory reset and trying from scratch, I mean thats what you are doing after you root anyways right?, or are you wanting root to use titanium or whatever to backup everything before you use SafeStrap?
I would reboot everything, disable both Anti-Virus, make sure USB debugging is enabled and run Kingo again. You may have to run as administrator. Keep watching during the process and your phone will prompt you to allow USB debugging for your computer and then it will prompt you again to allow unknown source installs and then after the reboot the phone will prompt one more time for root right to finalize the process.

I was able to root with Kingo on the latest built MJE. It worked for me on the first try. Try another computer if you can.
Does anyone know if there is a way to remove the Custom text with the padlock from the splash screen?
Sent from my SM-N900V using Tapatalk

mexiking713 said:
I was able to root with Kingo on the latest built MJE. It worked for me on the first try. Try another computer if you can.
Does anyone know if there is a way to remove the Custom text with the padlock from the splash screen?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Use Wanam and check "fake system status" reboot a couple times and it will be gone.

GrandMasterB said:
Use Wanam and check "fake system status" reboot a couple times and it will be gone.
Click to expand...
Click to collapse
I tried that but it didn't work. I rooted while on the official MJE with Kingo. I installed SafeStrap recovery and I'm running CleanRom. It's no big deal but it would be nice to be able to get rid of it.
Sent from my SM-N900V using Tapatalk

Just as a note for people using this method. I tried it it told me it failed but it actually worked. I don't understand the reasoning behind it but all I know is that it worked. Way easier than de LA Vega. Which used to be easy. Lol. I still prefer Odin and CF auto root. But kingo works
Sent from my SM-N900P using xda app-developers app

mexiking713 said:
I tried that but it didn't work. I rooted while on the official MJE with Kingo. I installed SafeStrap recovery and I'm running CleanRom. It's no big deal but it would be nice to be able to get rid of it.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
You made sure to install/activate Xposed framework, then reboot, then activate the Wanam Module and reboot again? Just asking because I've never had it not work for me and I've done it a dozen times or more between the AT&T Galaxy Note 3 and now the Verizon Galaxy Note 3.

GrandMasterB said:
You made sure to install/activate Xposed framework, then reboot, then activate the Wanam Module and reboot again? Just asking because I've never had it not work for me and I've done it a dozen times or more between the AT&T Galaxy Note 3 and now the Verizon Galaxy Note 3.
Click to expand...
Click to collapse
I have other mods running from Wanam right now but that particular one doesn't work. Bummer
Sent from my SM-N900V using Tapatalk

tss01 said:
Hi,
I went ahead to gave it a shot. First I made sure my anti-virus was disabled then I started Kingo and following the onscreen prompts. I automatically downloaded needed drivers. It then told me to re-connect my phone. I did and within a couple of minutes I get "ROOT Failed Not Support". I tried it two more times with the same result.
Any suggestions on my next step cuz I'm out of ideas.
Thanks!
Click to expand...
Click to collapse
If you're still having issues, check the link in my sig. Step by step instructions to get you up and running. Basically fool-proof

MJE TAR File - Question
Hello again:
I'm alittle confused about the need to Oden the MJE Tar file. I am already at MJE (from Verizon) and wonder why I would need to install this? I am Jelly Beans Build 6 installed and it appears to be working just fine. I also have HyperDrive installed and it appears to be working "ok" so far but time will tell. I did have a problem getting my phone to connect to my car via bluetooth but will try this again when I go out this morning.
Thanks!

tss01 said:
Hello again:
I'm alittle confused about the need to Oden the MJE Tar file. I am already at MJE (from Verizon) and wonder why I would need to install this? I am Jelly Beans Build 6 installed and it appears to be working just fine. I also have HyperDrive installed and it appears to be working "ok" so far but time will tell. I did have a problem getting my phone to connect to my car via bluetooth but will try this again when I go out this morning.
Thanks!
Click to expand...
Click to collapse
If you're already running MJE no need to reflash it in Odin. The Odin step isvfor those still on Mi9 or Mj7.
Notorious 3

[Q] kingo

I had y n3 rooted with kingo awhile back then I had to reimaged my phone with this file ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5
and now I can not get kingo to work. does anyone have any suggestions. thanks

in what way? how/ when does it fail.

kingo
Stryker1297 said:
in what way? how/ when does it fail.
Click to expand...
Click to collapse
the last thing I see before it fails is downloading requisite then it goes straight to fail notsupport

kingo
can anyone help with this. thanks

Mine failed the first time so had to run it twice. I would recommend enabling unknown sources and disabling verify apps so it can just do it's thing without any prompts.
Sent from my SM-N900V using Tapatalk

Whenever you wanna root via Kingo...make sure that the screen display time is set to 10 min...because while kingo is rooting the device we need to grant some permissions which pop-ups on the screen...
Also if Kingo fails for the first time run it again...2-3 times

Can't Root Note 3 (on MJE) with Kingo Root- HELP!

I just recently did a manual update of my Note 3 with Odin and am now on MJE. Every time I plug the Note in and run Kingo Root it never recognizes the phone but the computer does!
I have tried using a different USB port, re-installed Kingo, I'm sure my drivers are correct because again, I can connect to the PC with no problem.
Anyone have any idea how to get Kingo going? I am familiar with it since I used it to root my Note 3 when on MJ7 previously.
PLEASE HELP! I have a lot of apps that depend on root access that now I can't run any more.
Thanks.
P.S. - Sorry if this has already been covered somewhere here on the forum. I did several searches but came up with nothing.

What worked for me was turning on automatic updates in windows. I always have it disabled so I can control the windows update process.
Sent from my SM-N900V using XDA Premium 4 mobile app

Reilly1812 said:
What worked for me was turning on automatic updates in windows. I always have it disabled so I can control the windows update process.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the info. I'm currently at work, and it appears that Windows automatic updates are already on and set to update once every week. However, all of these settings are actually greyed out so I assume that only my administrator can make any changes to these settings.
When I used Kingo before I was at home, so maybe I'll have more luck when I get there but surely welcome yours and anyone else's ideas on this.

See if vroot will do the job for you.

I'm having a Similar issue, I have the MJE update, however no matter what I do, I'm getting a "Not Support" error when trying to root, and I've tried multiple cables, ports, and two PCs now, getting the exact same error. I googled around but wasn't able to see ANYONE with this error, and all Kingo says to do is keep trying when the root fails.
Edit: i've even tried wiping my phone and resetting to defaults, but still, i get this error, my PC at home was windows 8 enterprise, and the PC i tried at work was XP, i'm going to try a win7 PC next, but this is really frustrating.

In the same boat, for the most part.
Got the phone three days ago. Shipped with MI9. Odined to MJE.
Tried every combination of Kingo 1.1.6, 1.1.7 and 1.1.8, along with several cords, all available USB2 and USB3 ports, along with setting the phone up as MTP, PTP and Media device USB3 mode. USB debugging is ON, every PC given authority on the phone popups. Unknown sources CHECKED. Antivirus off on PC. Display on phone set to 10 minutes. Rebooted phone and PC between installations of Kingo, between attempts at rooting, between driver installations and uninstallations. Let Kingo install drivers, pre-installed through XDA links to drivers on Sam's site. You name it, I've tried it. In all, I've spent about 4 hours trying over 100 permutations of variables I could think of. Goose eggs.

ZachPA said:
In the same boat, for the most part.
Got the phone three days ago. Shipped with MI9. Odined to MJE.
Tried every combination of Kingo 1.1.6, 1.1.7 and 1.1.8, along with several cords, all available USB2 and USB3 ports, along with setting the phone up as MTP, PTP and Media device USB3 mode. USB debugging is ON, every PC given authority on the phone popups. Unknown sources CHECKED. Antivirus off on PC. Display on phone set to 10 minutes. Rebooted phone and PC between installations of Kingo, between attempts at rooting, between driver installations and uninstallations. Let Kingo install drivers, pre-installed through XDA links to drivers on Sam's site. You name it, I've tried it. In all, I've spent about 4 hours trying over 100 permutations of variables I could think of. Goose eggs.
Click to expand...
Click to collapse
I'm wondering if where it pulls files it needs is having issues or something and isn't pulling the dependencies we need to properly root?

So it's not just me. Bummer

int3gr4l said:
I'm wondering if where it pulls files it needs is having issues or something and isn't pulling the dependencies we need to properly root?
Click to expand...
Click to collapse
And yet, there are plenty of reports here and elsewhere of folks with Verizon Note 3's on MJE having no troubles at all rooting using Kingo. FMITGA.

ZachPA said:
And yet, there are plenty of reports here and elsewhere of folks with Verizon Note 3's on MJE having no troubles at all rooting using Kingo. FMITGA.
Click to expand...
Click to collapse
That's why I'm curious if their site is having issues with us downloading the files using the root. It fails for me with the not support error immediately after saying downloading the dependencies.

Just some added confusion... I did the same method... Odin to MJE... Root with kingo... Get same fail message... Try again but this time noticed that it actually rebooted the phone... Same fail message again... Check with root checker and I'm rooted... Install safestrap and update superSU... Good to go... Kingo says fail but I'm rooted and all root access apps working and rom slots flashed.

Lucky SOB.
Sent from my SM-N900V using xda app-developers app

having the same issue here. just got my note yesterday and been trying but no luck. getting NotSupport right after the 2nd "downloading requisite dependency files". would love some insight on this.

privy said:
having the same issue here. just got my note yesterday and been trying but no luck. getting NotSupport right after the 2nd "downloading requisite dependency files". would love some insight on this.
Click to expand...
Click to collapse
I really am wondering if it's the Kingo site. Whenever I try to navigate to the site it's taking quite a long time to load, as if they're having some issues with hosting, and when it goes to download the second set of files, it's unable to get through to the site to pull them.

Same here Privy
Sent from my SM-N900V using xda app-developers app

I had this issue when using a USB 3.0 port. Once I switched to USB 2.0, my device was recognized by the software.
Sent from my SM-N900V using Tapatalk

Same issue here, was having some issues with play store so back to stock with odin. Tried everything just like everyone else here. It has to be an issue with the kingo site. Redownloaded kingo and it tool an hour. Thats way too long and i bet root is timing out. Has to be it, at least i hope so.

Just an FYI I was on the stock OTA MJE with my note 3 and I rooted with Kingo and it literally worked the very first time I did it. Click, click boom rooted. Couldn't of been easier.
Point being it's doable on the rom, and easily. So keep it up
Sent from my SM-N900V using Tapatalk

The first time I rooted with no problem but after I went back to stock with odin I can no longer root with Kingo.

Just got my Note 3 yesterday, and have spent easily an hour installing and reinstalling drivers trying to get Kingo to work, but no luck.
As privy said: "having the same issue here. just got my note yesterday and been trying but no luck. getting NotSupport right after the 2nd "downloading requisite dependency files". would love some insight on this."
That's exactly the issue I'm having too.

Root SM-N900V MJE

Hi everyone, I'm having some issues trying to root my Note 3 SM-N900V on MJE. Here are the methods I have tried thus far:
-Installed/Ran Kingo
*Result: Device not supported (Multiple attempts, tried USB 2.0/3.0, uninstall/reinstall drivers and applications, flashed stock MJE rom then ran - same result)
-URDLV
*Result: Odin FAILED (used MJE from provided link to create .tar in terminal window, made second .tar in terminal using MJE from sammobile - same result, had to flash stock rom with Odin to get phone working again)
Is there a way to root this phone?

Same problem.....can't root this phone
I have tried everything.... anyone have a solution????
jimmayg said:
Hi everyone, I'm having some issues trying to root my Note 3 SM-N900V on MJE. Here are the methods I have tried thus far:
-Installed/Ran Kingo
*Result: Device not supported (Multiple attempts, tried USB 2.0/3.0, uninstall/reinstall drivers and applications, flashed stock MJE rom then ran - same result)
-URDLV
*Result: Odin FAILED (used MJE from provided link to create .tar in terminal window, made second .tar in terminal using MJE from sammobile - same result, had to flash stock rom with Odin to get phone working again)
Is there a way to root this phone?
Click to expand...
Click to collapse

Use vroot. It will and it will not trip Knox. I soft bricked mine this morning after screwing around. I used Odin to get back to stock MJE then I rooted with vroot. It a simple one click root but you have to search for the method of removing the Chinese superuser
sent from tapatalk....probably while pooping.

For this device you need Kingo 1.1.8. (Found on there Facebook page) If you downloaded Kingo from there site, it is the newest version witch may not work properly. Uninstall the version you have, reboot your PC and install 1.1.8. You may need to run Kingo more than one time before it takes. I had to run it 3 time before it took.
Good luck

phillymade said:
For this device you need Kingo 1.1.8. (Found on there Facebook page) If you downloaded Kingo from there site, it is the newest version witch may not work properly. Uninstall the version you have, reboot your PC and install 1.1.8. You may need to run Kingo more than one time before it takes. I had to run it 3 time before it took.
Good luck
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2630466&page=12 post #115

chriscw81 said:
Use vroot. It will and it will not trip Knox. I soft bricked mine this morning after screwing around. I used Odin to get back to stock MJE then I rooted with vroot. It a simple one click root but you have to search for the method of removing the Chinese superuser
Click to expand...
Click to collapse
Thank you for the reply, this is what I ended up using and it worked flawlessly. Installed app, clicked root, and I was rooted.
For those who don't know: Only drawback to Vroot is that it installs Chinese SU. For fix, type 'Replace Chinese Superuser' into google and follow first, or second link (first is video). (can't provide link because I haven't posted 10 times :/ ) The fix is easy and works instantaneously.
phillymade said:
For this device you need Kingo 1.1.8. (Found on there Facebook page) If you downloaded Kingo from there site, it is the newest version witch may not work properly. Uninstall the version you have, reboot your PC and install 1.1.8. You may need to run Kingo more than one time before it takes. I had to run it 3 time before it took.
Good luck
Click to expand...
Click to collapse
As far as Kingo 1.1.8 goes I was never able to find it... I read that people had success with that version but every time I followed links to obtain it I just got the same ole 1.2.0. (went to FB page and installed version was 1.2)
Thanks again for all the help everyone, Vroot did it for me

Cool, glad it worked out for ya.
sent from tapatalk....probably while pooping.