Develop Bugs

[Q] Kingo root help

So i have a Galaxy s4 mini with sprint as my carrier. I'm currently trying to root it via Kingo root app but the problem is that everytime i try, the end result is NeedRoot. I checked my phone and apparently the problem is that everytime I try to root, i get a little shield on my phone saying "Security notice" once it's clicked it states " An attempt to access a secure area on your phone without authorization has been blocked. Make sure your phone is protected by updating the security policy to the latest version from samsung". So how do I remove this policy problem? I just want to root my S4 Mini. Any help/advice is great help, thank you!

No one has an answer?

irvinavitia said:
No one has an answer?
Click to expand...
Click to collapse
If you took all the updates and are on NA7, no. As far as I know we need ODIN/Kies to root now. Ideally, we wouldn't have have taken the update that made Knox an issue. Someone would have dumped update, broken it apart and gave us a zip to flash everything but the bootloader so we wouldn't have these issues.

I believe you will find the answer to your question here ...
Rooting SPH-L520 Under KNOX?
http://forum.xda-developers.com/showthread.php?t=2676255

mdawdy said:
I believe you will find the answer to your question here ...
Rooting SPH-L520 Under KNOX?
http://forum.xda-developers.com/showthread.php?t=2676255
Click to expand...
Click to collapse
Did you notice who posted last on there?

Hi i have a s4 mini gti9195i with knox rooted by kingo root apk
how can i change from kingo's superuser to supersu from chainfire? The update of the binary fails.

Not fast but 100% good way:
1. Flash stock firmware with odin (remove kingoroot and all it's trash).
2. Use CF-Auto-root or (if you plan to use custom roms) flash custom recovery.
Notice:
CF-Auto-root probably will trip knox flag when trying to disable knox security.

Unroot my Samsung Tab S

I have a rooted Samsung Tab S wifi with this firmware installed T800XXU1ANFB. In order to unroot do i need to flash it with the same stock firmware it has on it. Or can i flash it with an updated stock firmware?

Metamorph22 said:
I have a rooted Samsung Tab S wifi with this firmware installed T800XXU1ANFB. In order to unroot do i need to flash it with the same stock firmware it has on it. Or can i flash it with an updated stock firmware?
Click to expand...
Click to collapse
Just select full unroot from settings in the supersu app.

I am a newbie... so here goes.
I did root it but when I go to verify it it doesn't verify. SuperSU was put on my device, but it wants to update the binary and I did that, but it keeps failing.
What I want to do is unroot it entirely and set it back to factory settings so I went to the settings in SuperSU like said above. If it is unrooted, how would I know? SuperSU is still on my table And only able to.bto.be disabled instead of e tirely removed.
I also think it didn't work because maybe I was trying to root it with a auto file for kitkat instead of lollipop. And links to the version for this lollipop are in a few places but each time I try to extract what I've downloaded the file is corrupt and it never unzips.
I've got the galaxy tab s 10.5; 16gb; wifi only (sm-t800) running lollipop 5.0.2
I'd really like to root so I can get the bloatware off, but if it isn't possible at the moment then I'd might as well go back to an unrooted device.
I'll take all the help I can get or be directed to. I've been pulling my hair out for two days on how to figure it out.

After you have unrooted reboot and you will be unrooted. Root can be verified with Root validator.
For root you can use my build here:
http://forum.xda-developers.com/showthread.php?t=3079488

ashyx said:
After you have unrooted reboot and you will be unrooted. Root can be verified with Root validator.
For root you can use my build here:
http://forum.xda-developers.com/showthread.php?t=3079488
Click to expand...
Click to collapse
On a second reboot I noticed I wasn't rooted. Thanks. I finally am rooted now.

ashyx said:
After you have unrooted reboot and you will be unrooted. Root can be verified with Root validator.
For root you can use my build here:
http://forum.xda-developers.com/showthread.php?t=3079488
Click to expand...
Click to collapse
I'm having a different problem but I am sure it is related to this topic.
I ended up being properly rooted after I got the correct one for lollpop 5.0.2. Then I realized that The Sims Freeplay would not work. I tried to use root cloak and I had no luck. I thend tried to use xposed, but it hasn't been upgraded to Lollipop yet.... so I thought about if rooting my device was really worth it since the only game I religiously play is The Sims Freeplay (apparently they are cracking down on people who hack their game.... which is all good and well because because it has nothing to do with my game... I have a rooted device to get rid of bloatware, not to hack the game that I play in a legit way -- but whatever)...
So I chose to unroot from SuperSU like I did once before (when I wasn't properly rooted, but SU was still on my device) just to see what would happen.
I've used Odin two more times to put back the original root file I got to work for Lollipop and now on the second reboot, SuperSU still hasn't been put on my device (like it originally had did long before I even rooted properly).
So now TWRP boots up every time I want to just go straight to my download screen and from there I click on download to get to my screen. That's when I use odin and the cf-auto.
I hope I don't sound confusing. I just want to know where can I go from here?
Apparently the Sims Freeplay is being a real PITA about people trying to play their game on a root device (doesn't surprise me with EA), but I want to play it on my device rooted or not... but now my tablet feels like it's both. It's not straight out of the store box and it's not fully rooted...
What the heck am I doing wrong now?

If you have twrp installed you don't need to flash cfautoroot again. Just reboot from within twrp and it will offer to root.
If you are still having problems see the link below.
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-twrp-t800-t3079488
If you are having problems getting into download mode you are not doing it properly.
Hold POWER + VOL DOWN + HOME.

Under which category will it offer to root and will there be a way to get the sims freeplay working? If not I'd like to get back to straight out of the box for the tablet... but something tells me after reading for a few hours last night that thats impossible.

geekery15 said:
Under which category will it offer to root and will there be a way to get the sims freeplay working? If not I'd like to get back to straight out of the box for the tablet... but something tells me after reading for a few hours last night that thats impossible.
Click to expand...
Click to collapse
If you unroot with the supersu app you will be fully unrooted.
To reroot boot into twrp then reboot.

[Q] Bootloader locked. Screwed?

I've got a new t807a from AT&T. According to the "about device" settings page, SE is "enforcing." My understanding is that this conclusively indicates that my bootloader is locked. It's currently running Android version 4.4.2, build number kot49h.T807aucu1ank1
I don't need a custom ROM and I don't care about tripping my knox counter (per se). I just want root. I've asked this in several relevant threads this week and gotten contradictory responses. Is there or is there not currently a method to root my tablet?
If not: is there hope? This is a great tablet but I can't live with the bloat for 18 months until I can afford a replacement. I CAN still return it and eat the 70-dollar "restocking" fee.
Thanks in advance.

Just because it is enforcing, does not mean it is locked.
The s6 shows enforcing and for the T-Mobile version can be rooted with autoroot and trip Knox.

TheArtiszan said:
Just because it is enforcing, does not mean it is locked.
The s6 shows enforcing and for the T-Mobile version can be rooted with autoroot and trip Knox.
Click to expand...
Click to collapse
So what does that mean for my t807a?

thorvindr said:
So what does that mean for my t807a?
Click to expand...
Click to collapse
Locked bootloader aside, root can be achieved. Check the Dev pages for specifics/updates but this is the auto page link. You'll see the 807 is being tested but check back there often to monitor progress.

skeeterpro said:
Locked bootloader aside, root can be achieved. Check the Dev pages for specifics/updates but this is the auto page link. You'll see the 807 is being tested but check back there often to monitor progress.
Click to expand...
Click to collapse
Thanks. I have been following that. Just hoping someone knows something I don't I suppose.

ATT=Locked Bootloader which there's not going to be root or anything. Same goes for Verizon. SE enforcing is Selinux. Most devices have that including my Tab S 10.5 WiFi with unlocked bootloader. SE is an protections or somesort (google it).
Since you have a locked bootloader, it will fail to flash modfied stuff to get root. It will only flash stock images. So you may have to return it. Just remember, don't buy from att or Verizon. Buy an unlocked model or Tmobile. Hope this helps!

DUHAsianSKILLZ said:
ATT=Locked Bootloader which there's not going to be root or anything. Same goes for Verizon. SE enforcing is Selinux. Most devices have that including my Tab S 10.5 WiFi with unlocked bootloader. SE is an protections or somesort (google it).
Since you have a locked bootloader, it will fail to flash modfied stuff to get root. It will only flash stock images. So you may have to return it. Just remember, don't buy from att or Verizon. Buy an unlocked model or Tmobile. Hope this helps!
Click to expand...
Click to collapse
I think you're telling me there's no way to unlock the bootloader and root is therefore completely unattainable. Is that right? If it's just a matter of "we haven't cracked it yet," I can be patient. But if you're saying there's really no hope, I'm going to be far less patient.
Is there no software solution (ie towelroot) that might help me get root without having to get past the bootloader?

thorvindr said:
I think you're telling me there's no way to unlock the bootloader and root is therefore completely unattainable. Is that right? If it's just a matter of "we haven't cracked it yet," I can be patient. But if you're saying there's really no hope, I'm going to be far less patient.
Is there no software solution (ie towelroot) that might help me get root without having to get past the bootloader?
Click to expand...
Click to collapse
Its a matter "we haven't cracked it" and no one is working on it. So basically almost to no hope and the odds of getting root or unlocking the Bootloader is really really low. There's no software solution like towel root that will get root or anything that doesn't mess with bootloader.
So there's no hope (unless some breakthrough happens).

DUHAsianSKILLZ said:
Its a matter "we haven't cracked it" and no one is working on it. So basically almost to no hope and the odds of getting root or unlocking the Bootloader is really really low. There's no software solution like towel root that will get root or anything that doesn't mess with bootloader.
So there's no hope (unless some breakthrough happens).
Click to expand...
Click to collapse
Well that blows. I guess that's what I get for buying off-the-rack.

Is this info outdated?
info outdated?
I've got an easy working root on my t807A with kingroot. And yet there seems to be no custom roms available for it.
Slightly out of topic, does anyone have a install to SDcard solution? Nothing I find seems to work

JMVPSlash said:
info outdated?
I've got an easy working root on my t807A with kingroot. And yet there seems to be no custom roms available for it.
Slightly out of topic, does anyone have a install to SDcard solution? Nothing I find seems to work
Click to expand...
Click to collapse
The built-in app manager lets you move apps to SD but I also have not found a solution to install directly to SD (without repartitioning the card). After several months of despair, I'm just now checking back to see if there's been any development on the bootloader front. It appears not. You can get root with Kingroot (also check out supersume, if that's still around, to replace kingroot's su app with supersu) but apparently the bootloader being locked prevents any non-official ROM from booting.

G920P Rooting

Can build G920PVPU3CPD3 be rooted?
Which root method should I use?

Maverick923 said:
Can build G920PVPU3CPD3 be rooted?
Which root method should I use?
Click to expand...
Click to collapse
Just install TWRP and flash SuperSU.

So there is noway to do this without tripping knox?

bump!

No.
Let me add on a bit to my initial response. Rooting the phone will trip Knox. Has been this way for quite some time. Discussed across many thread here and elsewhere.
Now the question comes up as to what do you lose by tripping Knox? Samsung Pay will never work for you. Android Pay may or may not work. Many people have been able to get it working at least in part, but disable Root (via SuperSu) when using Android Pay. I don't use either of those, so I don't care.
Then the question comes up if this voids warranty. The answer is only if you say "Hey, I rooted my phone and then broke something!" If you need warranty for a physical defect, go back to stock via Odin and you shouldn't have a problem. If you root your phone and then install a ROM not meant for your phone or local (like a Note ROM or an international ROM) you are probably going to mess something up that will be immediately obvious. The solution is not to do that.
Realistically, there aren't a ton of great ROMs available for this phone and most are based on stock anyway. No CM13 as yet. If you can live with your phone un-Rooted, that might be the wisest choice.
That said, I rooted my phone as soon as I got it. I went the full route, didn't care about tripping Knox and still don't. I have run both Renegade and TeamSPR ROMs and have been happy with them.
Now you can decide what to do.

Or u could root ur phone n install xposed on it ... Rooted S6 stock rom is now compatible with xposed its better than any custom roms out there
Sent from my LG-H815 using XDA-Developers mobile app

In my case, I only need temporary root. After that it maybe removed. So it would be nice to be able keep knox from being tripped if possible. Installing twrp is an additional step too that I would like to avoid again because it would serve no purpose since root would only be temporary. I also wanted to be sure that build G920PVPU3CPD3 could be rooted. Thanks for your input guys.

Komplikationen bei CF-Auto-Root mit Firmware?

Hello,
I have the Samsung Galaxy A50 (model number: SM-A505FN) and I wanted to root it with CF-Auto-Root, because I previously rooted an S5 in this way and it worked out without problems.
Now I have two questions:
1. Does the bootloader have to be unlocked because I read in other forums that you only have to unlock it if you want to get custom recoveries or OS.
As the description of CF-Auto-Root says, I want to stay as close as possible to the stock and only give apps root rights. I also want to keep getting OTA-updates and I don't want my phone to be wiped because I've already set everything up.
2. On the Firmware.Mobi page, to which you will be redirected if you go to ChainFires homepage, there are 3 Galaxy A50's listed, but with the model numbers SM-A505F, SM-A505U1 and SM-A505W (all without "fn" at the end unlike my modell number). Now to my question: Can I use one of these or do complications arise? If so, which one should I take?
Thank you in advance for future answers!
Kind regards,
Shademaster639

It's an English forum

I hope i am right but translated from german to english using google translate.
I have the Samsung Galaxy A50 (model number: SM-A505FN) and I wanted to root it with CF-Auto-Root, because I previously rooted an S5 in this way and it worked without problems.
Now I have two questions:
1. Must the bootloader be deactivated because I read in other forums that you only have to deactivate the bootloader if you want to get custom recoveries or OS.
As the description of CF-Auto-Root says, I want to stay as close as possible to the floor and only give apps root rights. I also want to keep getting OTA updates and I don't want my phone to be wiped because I've already set everything up.
2. On the Firmware.Mobi page, to which you will be redirected if you go to ChainFires homepage, there are 3 Galaxy A50's listed, but with the model numbers SM-A505F, SM-A505U1 and SM-A505W (all without "fn" on End, as with my model number). Now to my question: Can I use it or do complications arise? If so, which one should I take?
Thank you in advance for future answers!
Kind regards
Shademaster639

Lol, just recognized that the forum is english. I didn't think about this as I wrote the entry. The translation @spawnlives gave fits my question. Sorry for my mistake!
EDIT: I've edited my entry now to english.

Shademaster639 said:
Hello,
I have the Samsung Galaxy A50 (model number: SM-A505FN) and I wanted to root it with CF-Auto-Root, because I previously rooted an S5 in this way and it worked out without problems.
Now I have two questions:
1. Does the bootloader have to be deactivated because I read in other forums that you only have to deactivate the bootloader if you want to get custom recoveries or OS.
As the description of CF-Auto-Root says, I want to stay as close as possible to the stock and only give apps root rights. I also want to keep getting OTA-updates and I don't want my phone to be wiped because I've already set everything up.
2. On the Firmware.Mobi page, to which you will be redirected if you go to ChainFires homepage, there are 3 Galaxy A50's listed, but with the model numbers SM-A505F, SM-A505U1 and SM-A505W (all without "fn" at the end unlike my modell number). Now to my question: Can I use one of these or do complications arise? If so, which one should I take?
Thank you in advance for future answers!
Kind regards,
Shademaster639
Click to expand...
Click to collapse
I have not used cf auto root.
On earlier version of Android I used a different root method, now am using magisk on android version 9
Since cf auto root ( now SuperSu ) has not been updated for a while use of it on current Android version may not work.
Generally bootloader needs to be unlocked as rooting phones is a modification to the original firmware. Generally with Samsung, modifications to the phone OTA updates won't be possible. To update phone you will have to flash with odin then root again.
For point 2 I am not sure. If you are going to try it maybe use F model number. I think the U1 and W are for snapdragon variants not Eyxnos variants.
If you haven't read them yet these threads maybe of some help.
https://forum.xda-developers.com/showthread.php?t=1980683
https://forum.xda-developers.com/android/development/firmware-mobi-t3675896/page43
Note: Before trying anything always backup up your phone first.
As I have said I have not used cf auto root so maybe not able to help to much.

spawnlives said:
I have not used cf auto root.
On earlier version of Android I used a different root method, now am using magisk on android version 9
Since cf auto root ( now SuperSu ) has not been updated for a while use of it on current Android version may not work.
Generally bootloader needs to be unlocked as rooting phones is a modification to the original firmware. Generally with Samsung, modifications to the phone OTA updates won't be possible. To update phone you will have to flash with odin then root again.
For point 2 I am not sure. If you are going to try it maybe use F model number. I think the U1 and W are for snapdragon variants not Eyxnos variants.
If you haven't read them yet these threads maybe of some help.
https://forum.xda-developers.com/showthread.php?t=1980683
https://forum.xda-developers.com/android/development/firmware-mobi-t3675896/page43
Note: Before trying anything always backup up your phone first.
As I have said I have not used cf auto root so maybe not able to help to much.
Click to expand...
Click to collapse
Thank you for your quick answer.
I am a newbie regarding rooting as I rooted my phone years ago and I just followed some instructions by chainfire.
1. It would be kind if you could explain a bit more detailed what you mean with "flashing with odin then root again".
2. How do I backup my phone optimally?
Kind regards
Shademaster639

Shademaster639 said:
Thank you for your quick answer.
I am a newbie regarding rooting as I rooted my phone years ago and I just followed some instructions by chainfire.
1. It would be kind if you could explain a bit more detailed what you mean with "flashing with odin then root again".
2. How do I backup my phone optimally?
Kind regards
Shademaster639
Click to expand...
Click to collapse
Samsung firmware can be downloaded from the internet or using PC apps. Generally if needed to flash firmware with Odin it will revert back to stock rom.So generally any modifications done to the phone ( ie: custom recovery,root,customs Rom's etc ) will be reverted back to stock firmware.
So if the phone is modifiied and you want upgrade to lastest firmware you would flash with Odin and then you would have to modify you phone again.
From a backup point of view I don't really have any non root method that I use. I mainly use custom recovery ( TWRP ) to backup when making changes to the phone ( except for firmware upgrades ). You could try something like a cloud backup service or try Samsung Smart Switch. There are also apps ( like on play store ) that will do backups up as well ( keep/copy backup's on SD card or PC ).

spawnlives said:
Samsung firmware can be downloaded from the internet or using PC apps. Generally if needed to flash firmware with Odin it will revert back to stock rom.So generally any modifications done to the phone ( ie: custom recovery,root,customs Rom's etc ) will be reverted back to stock firmware.
So if the phone is modifiied and you want upgrade to lastest firmware you would flash with Odin and then you would have to modify you phone again.
From a backup point of view I don't really have any non root method that I use. I mainly use custom recovery ( TWRP ) to backup when making changes to the phone ( except for firmware upgrades ). You could try something like a cloud backup service or try Samsung Smart Switch. There are also apps ( like on play store ) that will do backups up as well ( keep/copy backup's on SD card or PC ).
Click to expand...
Click to collapse
If I got it right, you root your phone by flashing a modified AP-file with Odin, so if I want stock firmware back, I have to flash the original firmware?

Shademaster639 said:
If I got it right, you root your phone by flashing a modified AP-file with Odin, so if I want stock firmware back, I have to flash the original firmware?
Click to expand...
Click to collapse
Basically yes. Stock firmware will generally replace any modifications done to the phone.

spawnlives said:
I have not used cf auto root.
On earlier version of Android I used a different root method, now am using magisk on android version 9
Since cf auto root ( now SuperSu ) has not been updated for a while use of it on current Android version may not work.
Generally bootloader needs to be unlocked as rooting phones is a modification to the original firmware. Generally with Samsung, modifications to the phone OTA updates won't be possible. To update phone you will have to flash with odin then root again.
For point 2 I am not sure. If you are going to try it maybe use F model number. I think the U1 and W are for snapdragon variants not Eyxnos variants.
If you haven't read them yet these threads maybe of some help.
https://forum.xda-developers.com/showthread.php?t=1980683
https://forum.xda-developers.com/android/development/firmware-mobi-t3675896/page43
Note: Before trying anything always backup up your phone first.
As I have said I have not used cf auto root so maybe not able to help to much.
Click to expand...
Click to collapse
CF auto root uses modified firmware and requires an unlocked bl if it even works.. if he wants root he will have to unlock the BL. Also to add, CF auto root uses SuperSU, it hasn't become SuperSU.. in fact, CF stands for ChainFire if I'm not mistaken who made SuperSU.. the auto root basically pre-rooted/patched firmware similar (but different of course) as magisk patching firmware with root. You are correct though that it might not work on newer devices/OS with system as root and ram disk in recovery or on system etc etc.
Also, the A505U A505U1 A505W A505FN or w.e models are all Exynos, not snapdragon. He will be taking a risk though flashing firmware from a different model so he better be prepared to fix it if it doesnt work. His best bet is to stick to his variant. I am sure if he looks around a bit he'll find all he needs. Last comment, the U and U1 models in USA are not BL unlockable. They are exynos but still locked in the USA.

elliwigy said:
CF auto root uses modified firmware and requires an unlocked bl if it even works.. if he wants root he will have to unlock the BL. Also to add, CF auto root uses SuperSU, it hasn't become SuperSU.. in fact, CF stands for ChainFire if I'm not mistaken who made SuperSU.. the auto root basically pre-rooted/patched firmware similar (but different of course) as magisk patching firmware with root. You are correct though that it might not work on newer devices/OS with system as root and ram disk in recovery or on system etc etc.
Also, the A505U A505U1 A505W A505FN or w.e models are all Exynos, not snapdragon. He will be taking a risk though flashing firmware from a different model so he better be prepared to fix it if it doesnt work. His best bet is to stick to his variant. I am sure if he looks around a bit he'll find all he needs. Last comment, the U and U1 models in USA are not BL unlockable. They are exynos but still locked in the USA.
Click to expand...
Click to collapse
Thanks.
Appreciate the insight and the clarification.
Hopefully @Shademaster639 will pay attention to your post.
O/T: should say thanks also to the exploits made even though I don't have a ( US ) snapdragon variant on other devices.

elliwigy said:
CF auto root uses modified firmware and requires an unlocked bl if it even works.. if he wants root he will have to unlock the BL. Also to add, CF auto root uses SuperSU, it hasn't become SuperSU.. in fact, CF stands for ChainFire if I'm not mistaken who made SuperSU.. the auto root basically pre-rooted/patched firmware similar (but different of course) as magisk patching firmware with root. You are correct though that it might not work on newer devices/OS with system as root and ram disk in recovery or on system etc etc.
Also, the A505U A505U1 A505W A505FN or w.e models are all Exynos, not snapdragon. He will be taking a risk though flashing firmware from a different model so he better be prepared to fix it if it doesnt work. His best bet is to stick to his variant. I am sure if he looks around a bit he'll find all he needs. Last comment, the U and U1 models in USA are not BL unlockable. They are exynos but still locked in the USA.
Click to expand...
Click to collapse
I have unlocked my bootloader now since I had to do it nevertheless. I couldn't use cf-auto-root since there was no modified firmware for my device (sm-a505fn) listed on firmware.mobi. I tried rooting my phone using the latest version of magisk (v20.x) now, got random bootloops though. So I flashed my device back to stock with the original samsung firmware.

@spawnlives
1. Could you suggest me a video/forum entry/method that worked for rooting the a50 (SM-A505FN)? Is it recommended to install TWRP or just root with Magisk?
2. Are the newer devices protected with something like a "hidden OEM unlock" as I saw some videos about it how to deactive it? You are supposed to see this if this appears in your download mode: "KG STATE: Prenormal"?
Thank you in advance for future answers!
Kind regards
Shademaster639
EDIT: I have tried to root my phone now with latest Magisk version v20.x, but I got random bootloops. Same with version v19.3, which should work stable on a50 referring to this post: https://forum.xda-developers.com/galaxy-a50s/how-to/guide-root-galaxy-a50s-magisk-v19-3-t4001271
Kind regards
Shademaster639

Shademaster639 said:
@spawnlives
1. Could you suggest me a video/forum entry/method that worked for rooting the a50 (SM-A505FN)? Is it recommended to install TWRP or just root with Magisk?
2. Are the newer devices protected with something like a "hidden OEM unlock" as I saw some videos about it how to deactive it? You are supposed to see this if this appears in your download mode: "KG STATE: Prenormal"?
Thank you in advance for future answers!
Kind regards
Shademaster639
EDIT: I have tried to root my phone now with latest Magisk version v20.x, but I got random bootloops. Same with version v19.3, which should work stable on a50 referring to this post: https://forum.xda-developers.com/galaxy-a50s/how-to/guide-root-galaxy-a50s-magisk-v19-3-t4001271
Kind regards
Shademaster639
Click to expand...
Click to collapse
From you private message
Magisk has 2 parts to it.
Magisk- root method
Magisk Manager - control panel for magisk.
Magisk Manager is an apk app so it will show up regardless whether you phone is rooted or not ( except safe mode ).
Not having your device I not sure about you reboot issues. While doing a quick search there are issues posted here on xda and on Google about it. If i see anything useful I let you know.
KG and RMM states ( checked in download mode ) is a extra lock to prevent modifying your phone. I don't know if it effects every Samsung device though. So basically if KG and/or RMM state is showing Prenormal it will prevent modifying your phone.
Some more info from here
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535

spawnlives said:
From you private message
Magisk has 2 parts to it.
Magisk- root method
Magisk Manager - control panel for magisk.
Magisk Manager is an apk app so it will show up regardless whether you phone is rooted or not ( except safe mode ).
Not having your device I not sure about you reboot issues. While doing a quick search there are issues posted here on xda and on Google about it. If i see anything useful I let you know.
KG and RMM states ( checked in download mode ) is a extra lock to prevent modifying your phone. I don't know if it effects every Samsung device though. So basically if KG and/or RMM state is showing Prenormal it will prevent modifying your phone.
Click to expand...
Click to collapse
I know that Magisk Manager will show up regardless whether my phone is rooted as I just installed it on my phone (like any other apk/app). I was asking if there was a way to fix the bootloop with the manager.
I checked if the bootloader is unlocked by going into the odin/download mode [VOLUME UP] + [VOLUME DOWN] and it showed: KG STATE: checking.
(Comment under a video of @AndroidHowTo: https://www.youtube.com/watch?v=zqbu7jCmeMY
 @AndroidHowTo OK But Now I Have Another Problem
your video ( KG STATE:Checking) but its Must be (KG STATE:NORMAL)
Until it is solved
AndroidHowTo:
If your device KG State = Checking it means the status is normal / unlocked bootloader. it different with RMM State)

Shademaster639 said:
I know that Magisk Manager will show up regardless whether my phone is rooted as I just installed it on my phone (like any other apk/app). I was asking if there was a way to fix the bootloop with the manager.
I checked if the bootloader is unlocked by going into the odin/download mode [VOLUME UP] + [VOLUME DOWN] and it showed: KG STATE: checking.
(Comment under a video of @AndroidHowTo:
@AndroidHowTo OK But Now I Have Another Problem
your video ( KG STATE:Checking) but its Must be (KG STATE:NORMAL)
Until it is solved
AndroidHowTo:
If your device KG State = Checking it means the status is normal / unlocked bootloader. it different with RMM State)
Click to expand...
Click to collapse
KG state - prenormal
and / or
RMM state - prenornal
Problems with modifying phone.
KG state - checking
RMM state - normal or disappeared
Allows modifying phone.
For want of better terminology they are separate keys to the same lock.
There are plenty of sites regarding this:
https://chimeratool.com/fr/docs/sam...onitoring-and-management-rmm-unlock-functions