How to remove bloat ware from kingo super user

[20GT]

particular apps that are 'root' capable.

at the moment am I leaving my phone open to exploitation by not having a SU

 

[svim]

Ahhh, there may be an issue in that your Mega apparently has a hardware locked bootloader and that may be why replacing SuperSU is a problem. Read through this thread on XDA and there's some pertinent references you should find interesting.
https://forum.xda-developers.com/showthread.php?t=2558602

 

[20GT]

Ahhh, there may be an issue in that your Mega apparently has a hardware locked bootloader and that may be why replacing SuperSU is a problem. Read through this thread on XDA and there's some pertinent references you should find interesting.
https://forum.xda-developers.com/showthread.php?t=2558602

Thanks I heard mention of that but I'm not technically knowledgeable to understand what they are saying.
If the bootloader is locked how did it get rooted in the first place, or what does the bootloader have to do with this?

I'd like to try Replace KingoRoot with SuperSU manually without Terminal (2017) later today.
1. If the bootloader is locked will this work?

QUOTE
You can't root using odin. Only known root method I have heard of is kingo app. We are stuck with are roms until someone figures out away around the locked bootloader. You will always get a bootloop or bricked phone if you try flashing anything else besides stock.... For now.

2. Does this mean that I can or can't do the the replacement process?
It doesn't seem to be flashing. just un-installing and replacing.

6.1. Install SuperSU as system app
Android 4.4.x and below: Copy: /common/Superuser.apk => /system/app
Android 4.4.x and below: Change permission to 644 (-rw-rw-r--)

Android 5.0.x and above: Create a folder named "Superuser" or whatever
Android 5.0.x and above: Change permission to 755 (drwxrwxr-x)
Android 5.0.x and above: Copy: /common/Superuser.apk => /system/app/Superuser
Android 5.0.x and above: Change permission to 644 (-rw-rw-r--)

6.2. Replace: /common/install-recovery.sh => /system/etc
6.3. Delete: /system/etc/install_recovery.sh

6.4. Replace: /<Your architecture>/libsupol.so => /system/lib

6.5. Rename "su" to "daemonsu"

6.6. Replace: /<Your architecture>/daemonsu => /system/xbin
6.7. Replace: /<Your architecture>/supolicy => /system/xbin

6.8. Delete: /system/app/kingouser.apk and uninstall it from Settings -> App (if it was installed as user app)

After you replace any files, make sure the new file still has the same permissions as the old file. X-plore does this automatically, that's why X-plore is the best file manager. Root Browser doesn't, and you will lost root or get bootloop after reboot. But, you can re-root with KingoRoot and do it again.

There is no need to replace "su" binaries since they are write protected, but SuperSU can replace them once you update it in STEP 8

7. That's all. Reboot your device

8. SuperSU will appear on app drawer. Open it and it will ask you to update the binary. Press "continue" and "normal". The update should be successful.
[/B]

3. crap i just read the first part over again 1. Delete/Uninstall Kingouser, but keep Kingoroot.

Mine is just called SuperUser

 

[20GT]

Double crap

I just had my firmware wiped and replaced (so I was told)
To remove something that was installing TextNow in the middle of the night and now I see this in my installed apps.

 

[svim]

Maybe give some thought into just re-flashing the stock ROM for your Mega. This will return it back to its original, non-rooted, 4.2.2 status. Then apply any OTA updates or use the Kies utility to update it to 4.4.2 again. Then if you still want to root your phone just approach the whole task with a lot of caution. Most older Samsung phones are rootable using the Odin utility, and then replacing the stock Recovery with a custom one along with adding in the proper SuperSU, but apparently the Mega isn't one of them. Not all phones can be be rooted, in general the manufacturers, the carriers, and even Google (Android) frown on rooting so it's become more problematic with each wave of new phones coming out. As for older phones developers may or may not care to put any effort into coming up with rooting procedures so that's another issue. One-click rooting apps like Kingo are popular because they are one of the few ways to root a lot of phone models, but those who rely on them do have to pay an indirect price (as you've already seen).
Anyway, getting back to a stock ROM, you can download one from here:
http://updato.com/firmware-archive-select-model?record=0133A4AD53D711E6B055FA163EE8F90B
or from that previous XDA article.
As for the Odin utility, you could try the most recent version but I'd just use an older one in this instance. Odin isn't very backwards-compatible with older hardware.
http://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/


As for the locked bootloader on your Mega, you might be able to go to your carrier and have them unlock it for you. Legally the carriers are obliged to do so (as long as you don't have any outstanding bills to pay up) but it's still a grey area as a lot of service centers ignore the rules. (Also, that ruling was under Tom Wheeler's more consumer-friendly FCC, as opposed to the current, consumer hostile Ajit Pai's FCC.)
https://arstechnica.com/information...-wireless-carriers-have-to-unlock-your-phone/
Also, some bootloader basics:
https://www.androidcentral.com/what-is-android-bootloader

 

[20GT]

This will return it back to its original, non-rooted, 4.2.2 status.

I thought that going backwards would trigger knox and ruin the phone?

As for the locked bootloader on your Mega, you might be able to go to your carrier and have them unlock it for you. Legally the carriers are obliged to do so (as long as you don't have any outstanding bills to pay up) but it's still a grey area as a lot of service centers ignore the rules.

It seems like you are referring to unlocking the phone as if I wanted to take it to another carrier.

 

[svim]

Yeah good catch, after re-reading your latest points that might brick your Mega.

Getting back to your current situation, you mentioned 'the firmware was wiped and replaced'. That's a pretty significant process so what indicators are telling you this occurred? Is your phone still running a stock ROM? Is it still KitKat? ROM files are typically 1GB+ in size so once expanded and in place in the storage memory it's quite sizable, not something that can done without manual interaction.

 

[20GT]

When TextNow reinstalled itself I took my phone to a phone repair shop. I told them that whatever it was, was deeper than a factory reset and that I think I needed a complete wipe and fresh start. They charged me 30 to reinstall the firmware and 25 for a root. But they didn't say they were going to use a one click root app like kingo. When I got it back I went back to them and said how dissatisfied with the fact that they changed me 25 and not the app that did the work wants 5$ they refunded me 6$.

Anyway I suppose I'm stuck with it. I'll just unfreeze it when I need give an app permission.