Database Info

Kingo Android Root [KNOX 0x0 Root] - The easy way!

Hi,
I just got my Note 3 and was annoyed by the hole knox issue so i started to read back & forward after a few hours i found this program called kingo which i liked cause i only had to install it and start the program and the rest was done for me by the program.
Here are the easy steps to rooting.
1. Install the Note 3 drivers on the PC "all i did was plug-in the phone and it was installed for me".
2. Install Kingo (LINKS REMOVED)
3. Open the program and follow the simple instructions on you monitor.
When it's done you are rooted and your knox will still be 0x0.
After this i used Odin to flash the TWRP 2.6.3.7 and the knox was still 0x0.
I then shut off the phone to reboot into TWRP and did a backup of the stock rom rooted. Once done backing up the rom i rebooted into download mode and noticed that it knox was changed to 0x1.
So if you want root on stock rom then this is the easiest solution but you wont get custom recovery nor custom roms without tripping the knox counter for now.

Great does it work with latest stock firmware mj7
Sent from my SM-N9005 using Tapatalk

Doesn't work with MJ7, as posted on their Facebook page.

I did this with MJ2

Zionator said:
I did this with MJ2
Click to expand...
Click to collapse
If you did not absolutely need a custom recovery/kernel you should have gone with URDLV and you could have kept knox 0x0

xclub_101 said:
If you did not absolutely need a custom recovery/kernel you should have gone with URDLV and you could have kept knox 0x0
Click to expand...
Click to collapse
I have no idea what you are talking about.

Zionator said:
Hi,
I just got my Note 3 and was annoyed by the hole knox issue so i started to read back & forward after a few hours i found this program called kingo which i liked cause i only had to install it and start the program and the rest was done for me by the program.
Here are the easy steps to rooting.
1. Install the Note 3 drivers on the PC "all i did was plug-in the phone and it was installed for me".
2. Install Kingo from here.
3. Open the program and follow the simple instructions on you monitor.
When it's done you are rooted and your knox will still be 0x0.
After this i used Odin to flash the TWRP 2.6.3.7 and the knox was still 0x0.
I then shut off the phone to reboot into TWRP and did a backup of the stock rom rooted. Once done backing up the rom i rebooted into download mode and noticed that it knox was changed to 0x1.
So if you want root on stock rom then this is the easiest solution but you wont get custom recovery nor custom roms without tripping the knox counter for now.
Click to expand...
Click to collapse
As far as I know Kingo is banned on XDA forums until further notice, unless they finally got approved? Not to get you paranoid or anything, but suspicious communications with a chinese server were part of the rooting method you just used.

blumsen said:
As far as I know Kingo is banned on XDA forums until further notice, unless they finally got approved? Not to get you paranoid or anything, but suspicious communications with a chinese server were part of the rooting method you just used.
Click to expand...
Click to collapse
Why is it suspicious ? I mean it's most likely downloading what's needed for rooting and bypassing the knox system.
If it was banned then there should be a post so others know about it.
I am using Zonealarm firewall and i wasn't made aware of any suspicious behaviour.

Zionator said:
Why is it suspicious ? I mean it's most likely downloading what's needed for rooting and bypassing the knox system.
If it was banned then there should be a post so others know about it.
I am using Zonealarm firewall and i wasn't made aware of any suspicious behaviour.
Click to expand...
Click to collapse
It was suspected of sending your IMEI #. Don't know the details.....

Zionator said:
Why is it suspicious ? I mean it's most likely downloading what's needed for rooting and bypassing the knox system.
If it was banned then there should be a post so others know about it.
I am using Zonealarm firewall and i wasn't made aware of any suspicious behaviour.
Click to expand...
Click to collapse
1. It is suspicious because nobody knows who Kingo are. It is suspicious because the process is not transparent and it was not known what kind of information is collected from your device (or why) and what information is received (and possibly installed on your PC/ device). The exploit that they use for rooting is also kept secret. The server's IP they use is chinese. Some of the information they collect is arguably not necessary (for example your device's IMEI). The communication with Kingo is over a facebook page. Hmm.. can't think of more suspicious things right now, but that is plenty I think
2. "It is most likely just.." yes that is true. and for 99% of users that is good enough. Myself, I will lose my job if my clients/ employers find such a huge security hole which I am aware of and ignore. But then again they also expect me to never get near the WWW with my work phone or computer, I am not allowed to have a wifi module in my work laptop! You can see why a "probably just a harmless connection to China" is just not good enough in some situations.
3. If you do a search on XDA for Kingo, you will see that all threads were closed by admins.
4. Time for you to get a new firewall, or tinker with the settings!

Zionator said:
I have no idea what you are talking about.
Click to expand...
Click to collapse
With firmware before MJ3 there is a separate method called Universal Root De La Vega (URDLV) which is a lot more transparent and which (as long as you keep updating with Mobile Odin Pro and you do not change stock kernel and stock recovery) is giving you full root while keeping your Knox 0x0 (if you had it 0x0 before URDLV).

xclub_101 said:
With firmware before MJ3 there is a separate method called Universal Root De La Vega (URDLV) which is a lot more transparent and which (as long as you keep updating with Mobile Odin Pro and you do not change stock kernel and stock recovery) is giving you full root while keeping your Knox 0x0 (if you had it 0x0 before URDLV).
Click to expand...
Click to collapse
Oh ok but i have already flashed a custom recovery and rom. To hell with the warranty. I have never liked any stock roms and i like my freedom so my knox will most likely look like 0x2 now.
Kingo : Well if it's that bad then i am sure the moderators will close this and had i known this was the issue then i wouldn't have made this thread. However i would still have used this method if i knew this before as i never stay on stock rom and after finding out about the stupid chip that cant be recoded i didn't wanna wait for someone to come with a solution in one years time so i flashed the rom and recovery and now enjoying the phone
So if the Kingo really is that bad it has been wiped from my phone when i flashed a new rom.

Does not belong in Original Development, you did not create Kingo.
Moved to General
Use at your own risk. Rooting process has been known to collect and transmit IMEI and Serial numbers to China
FNSM

Before I even read the posts and start asking questions, I would like to know one thing. That is what does that United Arab Emirates mean in the pic below, its my screen after entering "About"
and can I root my device without any sort of issues?

iTTi said:
Before I even read the posts and start asking questions, I would like to know one thing. That is what does that United Arab Emirates mean in the pic below, its my screen after entering "About"
and can I root my device without any sort of issues?
Click to expand...
Click to collapse
http://www.tra.gov.ae/mynumber.php
Regardless of TRA ID - at this point you can not root MJ7 and keep knox 0x0.

kennyglass123 said:
Does not belong in Original Development, you did not create Kingo.
Moved to General
Use at your own risk. Rooting process has been known to collect and transmit IMEI and Serial numbers to China
FNSM
Click to expand...
Click to collapse
Just FYI - but Kingo stopped collecting the IMEI numbers a few versions ago.

mvansomeren said:
Just FYI - but Kingo stopped collecting the IMEI numbers a few versions ago.
Click to expand...
Click to collapse
That is great news! Our security expert has not been available to confirm this and Kingo has not sent us any correspondence to notify us of that. Has anyone confirmed this by recording data traffic while rooting?

Ok i have been reading around the net and all the reported security issues comes back to XDA.
wmshua.com is the site the connection is sent out to but is it possible that the app connects to their servers only in order to download the appropriate phone/device drivers.
On there web site under F.A.Q's
Q. Why don't you publish your source code?
A1. We kind of hope, in the future, Kingo Android Root could generate revenue to support our staff (STILL FREE FOR USERS). We all know that, in the long run, interest alone cannot make a living. To develop better software, we need to be financially motivated aside from being driven by passion.
A2. We manage to obtain root privilege of Android by exploiting certain undisclosed vulnerabilities, which we believe would be patched in no time once made public. And that would dysfunction this software that we've worked so hard for.
Click to expand...
Click to collapse
However it pushes Chainfires SuperSU to the device's and apparently they didn't ask him for his permission to use his work.
All in all i don't think isn't a matter of security issue anymore but more likely a matter of hard fellings that they stole Chainfires SuperSU to use in there app without asking him.
Correct me if i am wrong ?

xclub_101 said:
http://www.tra.gov.ae/mynumber.php
Regardless of TRA ID - at this point you can not root MJ7 and keep knox 0x0.
Click to expand...
Click to collapse
Knox 0x0 is the warranty thingy right? I have no warranty. So whats next?

xclub_101 said:
http://www.tra.gov.ae/mynumber.php
Regardless of TRA ID - at this point you can not root MJ7 and keep knox 0x0.
Click to expand...
Click to collapse
Is it not possible to root MJ7 using knigo! or rooting MJ7 using kingo will trigger knox ?

Help with Rooting

I'm looking to root my phone, but I have a few questions. I just want to make sure I'm using a method that will work for my phone as I seem to have an uncommon version. I'm on a small carrier, and I'm questioning how I can root without tripping KNOX. Every guide I've found seems to indicate there are questions about rooting my phone. My build version also never shows up on any of the guides as a supported build.
Relevant information:
Galaxy S6
Model: SM-G920R6
Android Version: 5.0.2
Baseband Version: G920R6WWU2AOF2
KNOX version: 2.4
Anyone able to point me to a root that will work, and not trigger KNOX? Any guides are welcome as well!

As far as I know there isnt a way to root without triggering knox , and if you want to root you could probly find a guide quite eaisly , if its that you want to still be able to use knox secured apps etc use magisk

BluePanther7 said:
I'm looking to root my phone, but I have a few questions. I just want to make sure I'm using a method that will work for my phone as I seem to have an uncommon version. I'm on a small carrier, and I'm questioning how I can root without tripping KNOX. Every guide I've found seems to indicate there are questions about rooting my phone. My build version also never shows up on any of the guides as a supported build.
Relevant information:
Galaxy S6
Model: SM-G920R6
Android Version: 5.0.2
Baseband Version: G920R6WWU2AOF2
KNOX version: 2.4
Anyone able to point me to a root that will work, and not trigger KNOX? Any guides are welcome as well!
Click to expand...
Click to collapse
If You still on 5.0.2 then try PingPong root... its not triggering method

vteccorp said:
If You still on 5.0.2 then try PingPong root... its not triggering method
Click to expand...
Click to collapse
I tried PingPong. It notified me that it could not complete (I assume because I have an unsupported version).

hairyfred said:
As far as I know there isnt a way to root without triggering knox , and if you want to root you could probly find a guide quite eaisly , if its that you want to still be able to use knox secured apps etc use magisk
Click to expand...
Click to collapse
Will Android Pay still work with magisk? I'm not familiar with it. I was under the impression that I would be permanently unable to use mobile payment applications if Knox was triggered. Is that wrong?

BluePanther7 said:
Will Android Pay still work with magisk? I'm not familiar with it. I was under the impression that I would be permanently unable to use mobile payment applications if Knox was triggered. Is that wrong?
Click to expand...
Click to collapse
Yes it will , enable magisk hide and it should work , android pay dosnt use knox , i think samsung pay does but android pay is not effected by knox
Install magisk and it will all be fine
Also for rooting , just flash twrp with odin then flash magisk for root etc

Pixel 2 Safety Net issue

Hi everyone,
Firstly, I'd like to state that I have researched before asking here!
So recently I had issues with my phone and thought the system was modified somehow, thus invalidating safety net. I reflashed today with a fresh download of the July update from google to try to fix it, but to my amazement with magisk uninstalled the phone still could not pass safety net and samsung pay for my gear s3 wouldn't operate and the play store was still not certified.
I noticed that there was a recent issue that topjohnwu fixed so I tried magisk beta to see if that helped but I'm stuck on the same issue. Is there an ongoing issue that I'm missing here and it is a matter of patience and updating?
Thanks kindly in advance for any input as my research has led me nowhere too useful.

need a bit more information... is your bootloader unlocked? If your bootloader is unlocked, and you do not have magisk installed to workaround safety net, you will not pass safety net without magisk installed unless you relock your bootloader...

building off what djer34 said, if your bootloader is unlocked, in addition to magisk, i believe you also need a patched kernel that can hide the check for if your bootloader is unlocked. my safetey net passes with root + flash kernel + bootloader unlock + magisk

About rooting S7

I am sorry for being dumb by post this questions, I want to root my S7 so i can install costume rooms.
My question is; does rooting can affect my device and make problems?
What is this whole thing about the Samsung Knox?
What is the simple way to flash rom white/out root?
If i want to restore my phone to the stock, it is possible to do it?
And what about the warranty is the warranty will become void?
Thanks in advanced.

rheh104 said:
I am sorry for being dumb by post this questions, I want to root my S7 so i can install costume rooms.
My question is; does rooting can affect my device and make problems?
What is this whole thing about the Samsung Knox?
What is the simple way to flash rom white/out root?
If i want to restore my phone to the stock, it is possible to do it?
And what about the warranty is the warranty will become void?
Thanks in advanced.
Click to expand...
Click to collapse
I think about root
U will get a lot of articale on google about
advantage of root and disadvantages of root
About knox
If you root your device, you trip the Knox Warranty bit. Knox services do not run on devices that have tripped the Warranty bit, because this indicates a device is rooted and flashed with an unofficial Android build
But u can flash custom rom without root but when u will flash any custom recovery your will warranty not be valid
And i don't about
Is there any way to revert your warranty of u have triggered knox
But u can easily come to your stock rom
With root or without root

shabbir143 said:
I think about root
U will get a lot of articale on google about
advantage of root and disadvantages of root
About knox
If you root your device, you trip the Knox Warranty bit. Knox services do not run on devices that have tripped the Warranty bit, because this indicates a device is rooted and flashed with an unofficial Android build
But u can flash custom rom without root but when u will flash any custom recovery your will warranty not be valid
And i don't about
Is there any way to revert your warranty of u have triggered knox
But u can easily come to your stock rom
With root or without root
Click to expand...
Click to collapse
And if i install rom how to install TWRP whiteout root?
And is it possible to delete TWRP?

rheh104 said:
And if i install rom how to install TWRP whiteout root?
And is it possible to delete TWRP?
Click to expand...
Click to collapse
You must use Odin to flash twrp recovery, just watch on YouTube there are many useful videos about it. This is how you root your phone.
Yes it is possible to go back on stock Samsung rom by flashing stock rom from sammobile or updato site. Everything will be as it was before root except your Knox is void 0x1 and u cant use Samsung Pay ect.

Scorpionea said:
You must use Odin to flash twrp recovery, just watch on YouTube there are many useful videos about it. This is how you root your phone.
Yes it is possible to go back on stock Samsung rom by flashing stock rom from sammobile or updato site. Everything will be as it was before root except your Knox is void 0x1 and u cant use Samsung Pay ect.
Click to expand...
Click to collapse
Samsung pay is not available in my country so...

rheh104 said:
Samsung pay is not available in my country so...
Click to expand...
Click to collapse
So then it's no problem, but be sure to know what u doing . Watch few videos , watch again if u never done this before and you will get there.

Scorpionea said:
So then it's no problem, but be sure to know what u doing . Watch few videos , watch again if u never done this before and you will get there.
Click to expand...
Click to collapse
Thanks for helping me out, one last thing; i have all my images on the samsung cloud and i found this thing: The following Knox services are affected if a Warranty bit is tripped.
Knox Platform for Enterprise
Existing Workspace's are permanently locked and the data is no longer accessible.
New Workspace's can't be created.
Knox Cloud Services
All Knox Cloud services stop working because they rely on a Knox license key to operate – For example, Knox Mobile Enrollment, Knox Configure, and Knox Manage.
Other Secure Samsung services
Samsung E-FOTA stops working.
Unique Knox security features stop working, such as Real Time Kernel Protection (RKP) , or Device Attestation.
Other Samsung Services that require Knox stop working – for example, Samsung Pay and Secure Folder.
If i will root my S7 all photos will be locked or removed?

rheh104 said:
Thanks for helping me out, one last thing; i have all my images on the samsung cloud and i found this thing: The following Knox services are affected if a Warranty bit is tripped.
Knox Platform for Enterprise
Existing Workspace's are permanently locked and the data is no longer accessible.
New Workspace's can't be created.
Knox Cloud Services
All Knox Cloud services stop working because they rely on a Knox license key to operate – For example, Knox Mobile Enrollment, Knox Configure, and Knox Manage.
Other Secure Samsung services
Samsung E-FOTA stops working.
Unique Knox security features stop working, such as Real Time Kernel Protection (RKP) , or Device Attestation.
Other Samsung Services that require Knox stop working – for example, Samsung Pay and Secure Folder.
If i will root my S7 all photos will be locked or removed?
Click to expand...
Click to collapse
Hm I really dont know, just tried to search a bit and couldn't find much info . It seems Samsung cloud isn't affected by root.
Personally I dont use Samsung cloud .

Scorpionea said:
Hm I really dont know, just tried to search a bit and couldn't find much info . It seems Samsung cloud isn't affected by root.
Personally I dont use Samsung cloud .
Click to expand...
Click to collapse
Just raed about this knox **** and some people said that they root their devices and the root ruined thiers devices oh **** man it is a big dilemma

rheh104 said:
Just raed about this knox **** and some people said that they root their devices and the root ruined thiers devices oh **** man it is a big dilemma
Click to expand...
Click to collapse
Nope ,root will not ruined your device at all. Dunno what u have read but people can make mistakes trying to root it or whatever they trying to do.
Can't help you much then this, it's your call to root it or not

CVE-2019-2215 for root.

Can we use CVE-2019-2215 exploit to gain root?
Here is a list of Phones affected by the hack.
A “non-exhaustive list” of vulnerable phones include:
Pixel 1
Pixel 1 XL
Pixel 2
Pixel 2 XL
Huawei P20
Xiaomi Redmi 5A
Xiaomi Redmi Note 5
Xiaomi A1
Oppo A3
Moto Z3
Oreo LG phones
Samsung S7
Samsung S8
Samsung S9
See the ars article for more details. I wonder if we have a dev willing to turn this into a root app? And what's the eta for that!
https://arstechnica.com/information...ty-that-gives-full-control-of-android-phones/

looks promising from what im reading about it, i have yet to find an application using it to look at though, also, i hardly know how to make a root so dont expect anything from me

There's a POC on the google thread...just need someone to provide the means to root...and/or just write a bit to the correct partition or whatever to enable OEM unlocking:
https://bugs.chromium.org/p/project-zero/issues/detail?id=1942
POC: https://bugs.chromium.org/p/project-zero/issues/attachmentText?aid=414885

Looks promising, sounds like we still need a dev to pick this up. It's all there just needs a properly setup root app and we can gain root.

Here is the poc compiled:
https://drive.google.com/file/d/10kJ9LvWq1AH1wdourLszXDMPSPbMMNXp/view?usp=drivesdk
You have to use an untrusted app i.e android terminal, termux, connectbot etc.. from the app copy it over to the apps home directory.. chmod +x poc3... then ./poc3.. itll tell you kernel was exploited if ur device is vulnerable..
i can confirm p2xl isvulnerable on latest firmware (will be patched in october updates on the pixels)

Dont know if it's possible or not, but I find kinda nonsense to root a device without unlocking bootloader. If you modify something inside the /system partition you need to disable dm-verity as well, for which you also need to flash non-samsung-signed kernel (thats the reason to unlock the bootloader), otherwise the device wont boot.
Also, forget about flashing twrp without UB

bamsbamx said:
Dont know if it's possible or not, but I find kinda nonsense to root a device without unlocking bootloader. If you modify something inside the /system partition you need to disable dm-verity as well, for which you also need to flash non-samsung-signed kernel (thats the reason to unlock the bootloader), otherwise the device wont boot.
Also, forget about flashing twrp without UB
Click to expand...
Click to collapse
I hear you, but if I can just get apps like adaway, titanium backup, etc I'll be happy. There are a lot of apps that need root that I don't also need a custom kernel and don't as far as I know alter the system partition. This limited root was available for many generations of galaxy and note phones.
Front page xda now...
https://www.xda-developers.com/zero...it-google-pixel-huawei-xiaomi-samsung-others/

Confirmed. My kernel is clear and root is planted. I am Verizon Pixel 2 android 10, different device but same. will post the process when i have a moment.

can't wait bought pixel 2 just because posted this

i think the POC is specific to Pixel 2. I tried it on a Pixel and Samsung S8 Active and no go. That said, this looks promising. I'm working on a version that will work with Samsung S8 Active. Wrt to root being useless without an unlocked bootloader - not so. There are ways to persist as root without an unlocked bootloader and writing to /system. Will post more if I get anywhere.

Does anyone know or can help with step by step process of using poc zip.I have pixel 2 and don't know how about using poc zip or process of flashing it,thank you Sean.

petiolarissean said:
Does anyone know or can help with step by step process of using poc zip.I have pixel 2 and don't know how about using poc zip or process of flashing it,thank you Sean.
Click to expand...
Click to collapse
push it to your phone using adb and run it in the shell. if you're vulnerable you should see "Exploited" if you run uname. this is an exploit that can be used to develop a root, but it needs development.

Yup, I was thinking of the same to use this as a root vulnerability..

I tried to use Qu1ckr00t to root the 955u on pie and it didn't work. The POC needs to be modified to support the s8 and its samsung kernel.

The PoC of Hernandez manipulates kernel data structures, the user process credentials, that are protected by Samsung real time kernel protection (RKP). Normally, the PoC should therefore not work on Samsung devices, or am I wrong with that?
The original PoC was reported to work on S8 and S9. But i fear this was only due to the PoC did not trigger RKP. Will have a look at the original PoC, to assess that ...

So mine ends on writev() returns 0x1000 which means I'm not vulnerable correct? Is that just because the poc isn't made to work with my device or am I not vulnerable in general.

We have https://github.com/grant-h/qu1ckr00t
AFAIK It needs to be modified for S8, currently only working for Pixel 2.
@elliwigy can you help here..

updesh94 said:
We have https://github.com/grant-h/qu1ckr00t
AFAIK It needs to be modified for S8, currently only working for Pixel 2.
@elliwigy can you help here..
Click to expand...
Click to collapse
many ppl have already made and posted the poc used there.. u just gotta look around.. but chances r it wont work unless ur device is vulnerable and the poc is tailored to ur kernel/device
i dont own any vulnerable devices so im not working on it personally..

This seems to only be exploitable on Oreo bootloaders.
"ANDROID: binder: remove waitqueue when thread exits." patched the exploit and was added to the G950U kernel when Pie was released.
Therefore, Pie is not exploitable and it seems that anyone running a V6 bootloader will not be able to use this exploit either.
The good news is, if you're running a V5 bootloader, it is theoretically possible to use this exploit. The bad news is I'm using a V6 bootloader. :/

pixlone said:
This seems to only be exploitable on Oreo bootloaders.
"ANDROID: binder: remove waitqueue when thread exits." patched the exploit and was added to the G950U kernel when Pie was released.
Therefore, Pie is not exploitable and it seems that anyone running a V6 bootloader will not be able to use this exploit either.
The good news is, if you're running a V5 bootloader, it is theoretically possible to use this exploit. The bad news is I'm using a V6 bootloader. :/
Click to expand...
Click to collapse
Wow, Thanks for clearing this up, I am on Pie but not sure If I am on the new bootloader or older one as I Never updated when the update mentioned you wont be able to downgrade. ?