Related
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
Okay, so I have this phone and the info attached to the imei DCNO Prod Test phone. It has the following build listed N900VVREBMJ5 test-keys. I checked for root access with a app and it didn't have root access. I tried to root with odin3 root_de_la etc and it came up with an error and was basically soft bricked. Was able to reload the pit file and eventually get it working again. I clearly don't know what I'm doing and bought this phone online and have learned very little since last night. It loads up with the custom logo etc etc. I'm looking load a regular stock rom onto or just a custom one, but no matter what I do I get an error.. Can anybody help.. thanks
Use kingo root.... Google it. It works on all of the builds for n900v.
Sent from my SM-N900V using Tapatalk
shiftr182 said:
Use kingo root.... Google it. It works on all of the builds for n900v.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
as stated on the general tab, the most important thing is to check if secureboot is enabled first!!! Turn phone off, turn on holding power, home, volume down and check to see if it say secureboot enabled. If it says disabled you might be famous
2swizzle said:
as stated on the general tab, the most important thing is to check if secureboot is enabled first!!! Turn phone off, turn on holding power, home, volume down and check to see if it say secureboot enabled. If it says disabled you might be famous
Click to expand...
Click to collapse
It's enabled. Btw, it says rooted already, but it fails to remove root or reroot. I also can't load anything on it...
topurdue said:
It's enabled. Btw, it says rooted already, but it fails to remove root or reroot. I also can't load anything on it...
Click to expand...
Click to collapse
Anyways, my problem is this. It says I'm rooted. I installed SuperSU it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!" Safestrap reads, "not rooted not active". Kingo states root "yes". I don't know what to do any help whould be great
topurdue said:
Anyways, my problem is this. It says I'm rooted. I installed SuperSU it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!" Safestrap reads, "not rooted not active". Kingo states root "yes". I don't know what to do any help whould be great
Click to expand...
Click to collapse
Anyways, i wiped deleted restarted and now i have root access.. blah blah ill be back im sure.
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
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
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.