Database Info

[Q] Anyone ever completely unrooted Note 3 with Kingo yet?

I have tried to UNROOT my Verizon Note 3 (SM-N900V) 4.3/MJE using Kingo, but Kingo shows that I am NOT rooted and doesn’t provide the “Unroot” option as it should. I used Kingo to root my phone, and I haven’t installed any custom ROMs or recoveries other than upgrading to SuperSU Pro and installing Xposed Installer.
I’ve watched dozens of videos on unrooting, but little without Kingo. Unfortunately at the end of these videos, they all show that the Knox warranty being voided (0 x 1) and some can’t remove the Custom Padlock screen. Just wondering if anyone has successfully unrooted and not having the Custom Padlock screen or Knox tripped.
Any help would be greatly appreciated!
Also, sorry if I didn’t post this right as this is my very first post or thread.

Easy Solution to Kingo Unrooting Found
I contacted Kingo about a week ago and gave them a decent donation along with my question. Unfortunately I never got any response back whatsoever. I’m thinking that they are really busy. So, I went ahead and took the leap and did the work successfully myself.
1. I uninstalled Xposed Installer through its own uninstaller. Then I removed it along with Titanium Backup, and the Pro version through CleanMaster with no problems.
2. I was able to uninstall SuperSU through it’s own “Uninstall” feature, then rebooted.
3. The first thing I noticed was the “Custom” and Padlock logo still on my screen at bootup, but the great thing was that I booted up without any problems.
4. I had discovered that the SuperSu Pro apk was still present through the phone’s Application Manager and was able to uninstall it from there.
5. Finally and fearfully, I rebooted one more time.
Everything booted normally again, and this time, the “Custom” logo and padlock were finally gone! I checked the Knox counter and both flags showed 0 x 0. Kingo had a problem with their servers in early February and I tried to root about 15 times over a period of about ten days or so. Suddenly one evening, I was able to successfully root within 3 or 4 minutes, and it really was a one click ordeal. Just be aware that you may not be able to unroot with their program. Don’t fear. Unrooting manually the way I did reveals absolutely no traces of a previous root or that the phone had been tampered with. I’m not sure that anyone who has flashed a custom ROM or recovery would have the same results though, so proceed with caution.

Is superuser v2.25 compatible on lollipop?

So I can successfully install superuser v2.40, but it's not working with one of my apps (puzzle and dragons). I have been told me to downgrade to 2.25, but I have been having issues.
The problem is no matter what, when I flash 2.25 it gets stuck in a bootloop. Flashing it on stock, and even flashing it over 2.40, and flashing it over 2.40 when clicking the replace button in the superuser app. What am I doing wrong? Is 2.25 not compatible with my phone?

Hi First of all, if you have any compatibility issues with apps try upgrading them rather than downgrading. In this case SuperSU v2.46 would be the current version. Anyways, I just googled a bit and that's not the problem at all.
The developers of the game implemented a function which doesn't let the app start on a rooted device. It will check if you have Superuser-rights and automatically close the game at the splash screen if so.
So actually what you need is something that "hides" your root. There are several methods. I heard about Xposed modules like RootCloak for example. I even read on the xda News page that it's Lollipop compatible

experience7 said:
Hi First of all, if you have any compatibility issues with apps try upgrading them rather than downgrading. In this case SuperSU v2.46 would be the current version. Anyways, I just googled a bit and that's not the problem at all.
The developers of the game implemented a function which doesn't let the app start on a rooted device. It will check if you have Superuser-rights and automatically close the game at the splash screen if so.
So actually what you need is something that "hides" your root. There are several methods. I heard about Xposed modules like RootCloak for example. I even read on the xda News page that it's Lollipop compatible
Click to expand...
Click to collapse
Thanks for the reply. On the game's forums, I have been told that masking does not work (if you look at xposed rootcloak it says it's not compatible). And some users have been able to get the game to work with certain versions. I am on the latest binaries and it still doesn't work. The only way to get it to work is to unsinstall SuperSU and reflash it every time I want to play.

On some forums I've read that SuperSU has got a function to "hide" or "temporarily disable" it... Take a look at the app. Hopefully this feature hasn't been removed and maybe that's enough for you to get the game working. It's not a perfect solution but at least you don't have to uninstall / reflash every time. Let me know if it worked

Stuck in bootloop after flashing to CM13 / SuperSU

I was trying to root my OPO by flashing SuperSU Beta_V2.52 but after each flash my OPO goes into a boot loop, flashed several builds of SuperSU (inc; beta's) and all of them result in a bootloop. To be on the safe side i did fresh installs of CM13 via bootloader, no result.
Pulling my hair what the solution will be. Dev's from "Cyanogenmod-team" are aware of this problem but find its not there problem to solve...:
It needs to be said that this issue with SU is something that is outside the scope of official support. We neither recommend or support SuperSU installs, as it opens the device up security wise in ways that most users (not all, some do the homework to understand what's going on) either ignore or are ignorant of. So if there's a bootloop happening, you are going to need to diagnose it on your own, or with others help here. You can also check XDA as well.

sandeman11 said:
I was trying to root my OPO by flashing SuperSU Beta_V2.52 but after each flash my OPO goes into a boot loop, flashed several builds of SuperSU (inc; beta's) and all of them result in a bootloop. To be on the safe side i did fresh installs of CM13 via bootloader, no result.
Pulling my hair what the solution will be. Dev's from "Cyanogenmod-team" are aware of this problem but find its not there problem to solve...:
It needs to be said that this issue with SU is something that is outside the scope of official support. We neither recommend or support SuperSU installs, as it opens the device up security wise in ways that most users (not all, some do the homework to understand what's going on) either ignore or are ignorant of. So if there's a bootloop happening, you are going to need to diagnose it on your own, or with others help here. You can also check XDA as well.
Click to expand...
Click to collapse
Did you try SuperSU V2.76?

[CENTER​​[/CENTER]
sandeman11 said:
I was trying to root my OPO by flashing SuperSU Beta_V2.52 but after each flash my OPO goes into a boot loop, flashed several builds of SuperSU (inc; beta's) and all of them result in a bootloop. To be on the safe side i did fresh installs of CM13 via bootloader, no result.
Pulling my hair what the solution will be. Dev's from "Cyanogenmod-team" are aware of this problem but find its not there problem to solve...:
It needs to be said that this issue with SU is something that is outside the scope of official support. We neither recommend or support SuperSU installs, as it opens the device up security wise in ways that most users (not all, some do the homework to understand what's going on) either ignore or are ignorant of. So if there's a bootloop happening, you are going to need to diagnose it on your own, or with others help here. You can also check XDA as well.
Click to expand...
Click to collapse
Happened to me couple of times while switching from cm12.1 to cm13. Turns out marshmallow doesn't really support superSU v2.52. Try v2.76 instead. Worked like a charm for me
P.S.:update your TWRP to version 3.0.

[Q] Huawei Y6 and its many issues

I possess a Huawei Y6 SCL-L01C55B130, and I encountered a lot of problems in rooting it.
First, I unlocked the bootloader, then flashed TWRP 2.8.7.0 with Minimal ADB and Fastboot. Result: the recovery is messily responsive with touch! Is there any NORMALLY FUNCTIONING recovery for this device (as in, not requiring me to use a hammer and nail to get the touch to work)?
Then, I tried to flash SU: another disaster. It asked apps for "superuser permissions", but rootchecker told me the phone WASN'T rooted. I had to uninstall SuperSU, because I couldn't ask it to unroot nor use the flashable "UnSu" package (I had flashed SU multiple times trying to make it work). Is there any way to remove any and all traces of its passage?
Then, again, I tried King Root: after some attempts, it worked, but then I discovered how much of a nuisance that tool is, because of all the "spyware" stuff it brings with it. I eventually decided to unroot and uninstall the tool, but, again, can I remove the traces it left in my system (if there are any)?
Eventually, I used magisk 12.0, and it works like a charm for rooting.
Other issues emerged though: I had finally rooted and debloated my phone, but I can't apparently play "nintendo games" because of Safetynet. Is there a way to circumvent it (as in, hiding the open bootloader and root)? Are the SU and KingRoot traces going to be an issue?
If I need to flash a new custom rom (the stock and/or nobrand apparently DON'T EXIST on the internet)to obtain the safetynet workaround and have a clean system, so be it, but which bugs do they have with my specific device? The situation is very confusing because of the existence of SO MANY variations of Huawei Y6.
Thanks for reading all this mess, and for the help!

Was stock, rooted on 8.0, restarted phone, now unrooted on 10...WTH?

Need some answers/help...
I was stock, rooted on 8.0....saw a pop-up box yesterday about OTA, didn't think much about since I thought being rooted wouldn't allow the OTA. Have seen the occasional pop-up over maybe the last couple weeks, but I don't normally restart my phone unless it starts to lag or freeze up/run slow. A restart usually fixed that. Was perfectly happy staying on 8.0. I did a shutdown on my phone this evening, and when I restarted it, bam, I'm unrooted on 10 now, specifically, QP1A.190711.020
The phone was bought from Google, unlocked in Oct 2017. I immediately unlocked bootloader and rooted at that time and have been running stock 8.0 since. TWRP and Magisk were used following instructions from the thread here on the forum.
No data was lost after the restart today and 10 seems to be running ok. I did download some data and pictures through my USB-c onto a flashdrive and it did seem to drain my battery FAST while doing it.
What I'd like to know now is how to get root back. I wouldn't mind staying on 10, but if I re-root, will another OTA break my root again? I haven't tried to do a shutdown and a restart again to see what would happen because I'm afraid my phone will brick.
I'm kind of a noob at this, and I don't always understand when you all get technical, but I can follow step-by-step instructions.
First off, how did an OTA actually get through, update and unroot my phone?
And second, can someone point me to step-by-step instructions to re-root my phone on 10, and how do I keep it from happening again?
Thanks for looking and I'd be very appreciative if someone could help me out.
Thank you.
Jim

same here

Same here.
I've got a retail (NON-Verizon) rooted, stock OG Pixel with 8.1 and I've been ignoring the nag to update to 10.
My wife has a retail (NON-Verizon) Pixel 2 that was also stock, rooted 8.1 except she just took the update and asked me about it later.
Both were done with TWRP and Magisk, albeit differing versions.
She's now unrooted at QP1A.191005.007.A1
TWRP v3.2.1-0-walleye is installed.
EDIT: TWRP seems to have been nuked by the OTA upgrade.
I just tried to reboot into TWRP recovery and it's gone.
Magisk Manager app version 5.4.0 (57) + "Latest Magisk Version: v16.0" (I'm pretty sure I rooted via v14.5(1456) though) are present.
"Update Magisk Manager" is nagging about updating /installing MagiskManager-v5.8.2
Root Checker Basic v6.4.6 is also installed.
I'm scared to death to update Magisk or attempt root without some guidance from you fine folks here.
Until then, I'll start having her backup everything she wants to keep in case things go sideways.

I didn't think I was the only one this happened to.
Ok...noticed another issue.
I had Titanium Backup Pro installed. I had several apps frozen before the forced upgrade to 10. Guess what? Those apps are listed as disabled in the app list with no button for re-enabling them. Titanium Backup Pro no longer works because I lost root with the forced update to 10, so I can't unfreeze with Titanium Backup.
Is there any way to unfreeze those apps without re-rooting? Not too sure I even want to attempt to root again.
Also, I haven't shutdown or restarted since the forced update. S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?

fjm568 said:
S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?
Click to expand...
Click to collapse
Correct.
As for "other issues", none that I, or she, have noticed.
Still breathlessly waiting to hear about how I go about re-rooting without data loss.