Develop Bugs

SM-N900T won't encrypt after rooting...

Escalating to it's own thread after a lot of trial/error in others:
I can't get native Android device-level encryption to work on an SM-N900T after rooting:
Tried CF-Auto-Root - root successful (KNOX Warranty tripped), but won't encrypt
Tried Root de la Vega - root successful (KNOX Warranty remained tripped), but won't encrypt
Tried Xposed Framework + Wanam Xposed to reset "System" to 'Official', successful, but won't encrypt
Tried TriangleAway just to verify that Counter, Binary, and System reported as intended (0, official, official respectively), but won't encrypt
Multiple attempts at device-level encryption, thorough and 'fast' cause immediate reboot. I'm using password, not PIN, as required, and also testing via manually initiating encryption as well as letting ExchangeSecurityPolicy enforce it. The only way I can get device-level encryption seems to be by restoring to stock (tested multiple times).
Perhaps there's some other env bit encryption requires/checks in order to run?
Any ideas welcome.
Thanks.

I can absolutely confirm this issue. Same thing happened here. Unroot and you are set. The issue is if you root again, it will stop booting - I found out the hard way. Sucks but hey.
As encryption for me is important, I will have to wait with re-rooting the device to remove bloatware.. too bad!
Also, TWRP which usually supports encryption also does not work with this version of Samsungs encryption.

Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

digittante said:
Escalating to it's own thread after a lot of trial/error in others:
I can't get native Android device-level encryption to work on an SM-N900T after rooting:
Tried CF-Auto-Root - root successful (KNOX Warranty tripped), but won't encrypt
Tried Root de la Vega - root successful (KNOX Warranty remained tripped), but won't encrypt
Tried Xposed Framework + Wanam Xposed to reset "System" to 'Official', successful, but won't encrypt
Tried TriangleAway just to verify that Counter, Binary, and System reported as intended (0, official, official respectively), but won't encrypt
Multiple attempts at device-level encryption, thorough and 'fast' cause immediate reboot. I'm using password, not PIN, as required, and also testing via manually initiating encryption as well as letting ExchangeSecurityPolicy enforce it. The only way I can get device-level encryption seems to be by restoring to stock (tested multiple times).
Perhaps there's some other env bit encryption requires/checks in order to run?
Any ideas welcome.
Thanks.
Click to expand...
Click to collapse
How did you reset knox to 0 using Wanam Xposed? I see no option to reset "System" to "Official"...

Esteef said:
How did you reset knox to 0 using Wanam Xposed? I see no option to reset "System" to "Official"...
Click to expand...
Click to collapse
That's two separate things:
KNOX Warranty Void - cannot be reset to 0x0 once it's tripped to 0x1
Report "System" as "Official" - Look in the Security Hacks section of Wanam Xposed for "report fake status"

Can confirm this too, not possible to root and then Encrypt. Really would like this to work.
My phone is a SM-N9005

Having the same issue...

webdave said:
Having the same issue...
Click to expand...
Click to collapse
After weeks of trying different things.I Finally figured it out!! (Verizon Variant, but should work with T-Mobile Galaxy Note 3 just fine, see website)
First- Encrypt your device, before rooting
Second- Use the Kingoapp Root method, not Root De La Vega. When i used Root De La Vega, it would not work, and I would get the same error as everyone else. http://www.kingoapp.com/# is the link to the kingo root method. Its a One-Click method that took 10 minutes from start to finish. I just downloaded Multi-Window Manager to test the root, and it worked like a charm.

yousefarman89 said:
After weeks of trying different things.I Finally figured it out!! (Verizon Variant, but should work with T-Mobile Galaxy Note 3 just fine, see website)
First- Encrypt your device, before rooting
Second- Use the Kingoapp Root method, not Root De La Vega. When i used Root De La Vega, it would not work, and I would get the same error as everyone else. http://www.kingoapp.com/# is the link to the kingo root method. Its a One-Click method that took 10 minutes from start to finish. I just downloaded Multi-Window Manager to test the root, and it worked like a charm.
Click to expand...
Click to collapse
That won't work for some of us because it will trip Knox. That is the advantage of Root De La Vega right now.

webdave said:
That won't work for some of us because it will trip Knox. That is the advantage of Root De La Vega right now.
Click to expand...
Click to collapse
Kingoapp is supposed to not trip the Knox flag as well.

krelvinaz said:
Kingoapp is supposed to not trip the Knox flag as well.
Click to expand...
Click to collapse
Really? I'll have to look into this.

designgears in his Dev post when he closed the Root de la Vega [KNOX 0x0 Root | SM-N900T thread pointed to it.
http://forum.xda-developers.com/showpost.php?p=47067300&postcount=105
I asked him via PM and he confirmed it.

krelvinaz said:
Kingoapp is supposed to not trip the Knox flag as well.
Click to expand...
Click to collapse
how can i checked if its tripped or not? I have Kingo/and im encrpyted

yousefarman89 said:
how can i checked if its tripped or not? I have Kingo/and im encrpyted
Click to expand...
Click to collapse
Boot into download mode and see if the Knox flag is 0x0 or 0x1(tripped).

webdave said:
Boot into download mode and see if the Knox flag is 0x0 or 0x1(tripped).
Click to expand...
Click to collapse
Knox remains 0x0 it worked
Sent from my SM-N900V using Tapatalk

greffel said:
Can confirm this too, not possible to root and then Encrypt. Really would like this to work.
My phone is a SM-N9005
Click to expand...
Click to collapse
Can also confirm not limited to the Note 3. Same thing for the Note 2 updated to 4.3 as well, SGH-I317m variant. Rooted with an odin flashed root injected stock rom.
---------- Post added at 08:36 PM ---------- Previous post was at 08:26 PM ----------
yousefarman89 said:
After weeks of trying different things.I Finally figured it out!! (Verizon Variant, but should work with T-Mobile Galaxy Note 3 just fine, see website)
First- Encrypt your device, before rooting
Second- Use the Kingoapp Root method, not Root De La Vega. When i used Root De La Vega, it would not work, and I would get the same error as everyone else. http://www.kingoapp.com/# is the link to the kingo root method. Its a One-Click method that took 10 minutes from start to finish. I just downloaded Multi-Window Manager to test the root, and it worked like a charm.
Click to expand...
Click to collapse
Regarding the kingoapp root method - did anyone else read this thread? Written in the xperia forums but some telling info regarding the dev. http://forum.xda-developers.com/showthread.php?t=2460745&page=8 Might work but could be a heavy cost.

Just got a note 3 and this is an old thread. So wanted to update this question.
To encrypt device after root all that is needed to do is run the following command from terminal or adb shell as root. You must have the latest busybox installed.
pkill -KILL daemonsu
After running this command you should be back at the "$" prompt and out of root. Do not run su again.
Then encrypt your device. Encryption should work fine. Once rebooted you will have root again.
I had to repeat the above steps because I ran su again. Running su restarts daemonsu.
Good luck

alphahere said:
Just got a note 3 and this is an old thread. So wanted to update this question.
To encrypt device after root all that is needed to do is run the following command from terminal or adb shell as root. You must have the latest busybox installed.
pkill -KILL daemonsu
After running this command you should be back at the "$" prompt and out of root. Do not run su again.
Then encrypt your device. Encryption should work fine. Once rebooted you will have root again.
I had to repeat the above steps because I ran su again. Running su restarts daemonsu.
Good luck
Click to expand...
Click to collapse
does this apply to all samsung rooted but bootlocked devices like say verizon galaxy s5?

spyngamerman said:
does this apply to all samsung rooted but bootlocked devices like say verizon galaxy s5?
Click to expand...
Click to collapse
Just tried with a Verizon Note 3 with locked bootloader after running
pkill -KILL daemonsu
No problem encrypting data partition at all. So should work with S5.
Rebooting restores root function. The above command only temporarily disables root.
Good luck.

It worked!
OMG alphahere. Thanks so much, this finally worked on my Note 3 (N9005) with X-Note Rom 4.4.2 after hours and days of searching and failing...
Well, as a newbie I had to try several times. Turns out that I didn't read your post that carefully. It seems that the term "running adb shell as ROOT", so typing "su" that you have # instead of $ in cmd, is a small but important detail to disable SuperSU-Root temporarily in order to let encryption run without getting stuck in malfunctioning Enter-Password-Screen and ergo factory reset with Stock-ODIN from the start
THANK YOU, You're the best!!! <3

[Q] Root for SM-T215?

Forgive me for asking this question but I can't find a way to root this. Yes, I tried searching but it can't seem to find anything about this particular model.
It's the LTE version of the Tab 3 7.0 if anyone is wondering.
Thanks in advance.

I tried using http://www.kingoapp.com/ to root my SM-T215 and for some reason it did not work for me. Others have tried and had success.
Have you tried that yet? http://forum.xda-developers.com/showthread.php?t=2473747

SM-T215 Rooting
Am a noob and still learning but if u would like to try my method,i be happy that i could help u.No flashing of roms as my only intention of rooting is to get rid of those unwanted apps and boosting the speed/battery life.
SM-T215 Tab 3 7.0 LTE (8GB)
Rooting: Only Kingoapp works. (Provide root with supersu but no custom recovery)
Custom Recovery for backup/restore: Only TWRP (SM-T217S) flash through ODIN works.CWM gets bootloops.
No custom roms are found compatible/stable for the T215 so far but xPosed framework is an option.

amie2109 said:
Am a noob and still learning but if u would like to try my method,i be happy that i could help u.No flashing of roms as my only intention of rooting is to get rid of those unwanted apps and boosting the speed/battery life.
SM-T215 Tab 3 7.0 LTE (8GB)
Rooting: Only Kingoapp works. (Provide root with supersu but no custom recovery)
Custom Recovery for backup/restore: Only TWRP (SM-T217S) flash through ODIN works.CWM gets bootloops.
No custom roms are found compatible/stable for the T215 so far but xPosed framework is an option.
Click to expand...
Click to collapse
tried kingoapp, framaroot, zroot, and afew more but still cant get my tab to be rooted.
just bought this tab 3 7.0 SM T215 to replace my outdated modded galaxy apollo cm7 alpha 9 with the hope that i can explore more on modded roms on a better handset.
if only there is ROOTING for sm-t215 at the least..
8GB filled with bloatware is making my device suffocating and annoying.
sigh ~

crazyVato said:
tried kingoapp, framaroot, zroot, and afew more but still cant get my tab to be rooted.
just bought this tab 3 7.0 SM T215 to replace my outdated modded galaxy apollo cm7 alpha 9 with the hope that i can explore more on modded roms on a better handset.
if only there is ROOTING for sm-t215 at the least..
8GB filled with bloatware is making my device suffocating and annoying.
sigh ~
Click to expand...
Click to collapse
I have a Tab 3 7.0 LTE (SM T215) edition too, and i every rooting method doesnt work.. HELPP someone

Zetomono said:
I have a Tab 3 7.0 LTE (SM T215) edition too, and i every rooting method doesnt work.. HELPP someone
Click to expand...
Click to collapse
Flash or install universal root. If that does not work install vroot sure that this will have rooted your phone. You can then uninstall remplasarla by SuperSU smoothly and the other

Andromeda 90 said:
Flash or install universal root. If that does not work install vroot sure that this will have rooted your phone. You can then uninstall remplasarla by SuperSU smoothly and the other
Click to expand...
Click to collapse
Do you have the links to the methods that you've just suggested?

crazyVato said:
Do you have the links to the methods that you've just suggested?
Click to expand...
Click to collapse
All right.
1. Install this apk. https://mega.co.nz/#!bQwAlJiT!H04MbX-_Hp0o2sYo7RCaFG904_x_2sxLW0rTTsZlLSM
2. Before running the application, you must tick the boxes, usb debugging, allow mock locations, all in development options, and be connected to the internet.
3.-That done, you open the application, and click where it says open das, root, now there waiting to do their work, if all goes well, your phone will reboot.
4.-If you ever leave a message with Chinese letters before or after you restart your phone, give right click option. Always be on that, that is to give super user permissions.
5. as either root, replace the Chinese application SuperSU, qui this. https://mega.co.nz/#!CVx1BLSQ!g1lLufWuy7GzqxuEgYK2MSHFrqS6UGvelfvD24V_aFs

still not working
i tried that and doesn't work. installed the apk click root but still

How I root my SM-T215 (Singapore) at 4.2.2
Excuse me for being a Noob...
To enable USB Debugging is the same as Note 3. Tap on About Phone and the Baseband 7 times (I Think) as almost weeks ago when I tried.
Enable USB Debugging (tick) and all in this paragraph first before trying this website (namely Allow Mock Locations, etc) :
www . mgyun. com / vfroot
Download (立即下载) and Install the software into Desktop.
Need not turn off Tab 3, just connect and wait for the software to detect.
Then it will do its work to root it.
Tab 3 will reboot at least once, and when asked for ADB access, authorize it.
I managed to root my SM-T215 via this method without any knowledge of any programming knowledge.
I hope this helps. Have not checked on Knox yet but glad that I can remove some apps which slows down the Tab 3 LTE

does not work on my SM-T215.

Any other option for rooting SM T215.
Tried various root versions - none works.

www.mgyun.com download the root application and install it in ur pc, once u've launch the app and connect ur device, the app will automatically detect the model of ur device. just click on root.. once rooted, uninstall the chinese version of superuser but TAKE NOTE you need to keep the kinguser tool in your device or else no rooted is being done. once everything is installed, user rootchecker to double confirm that ur device has been rooted. it is not a full root, but it'll do for now. good luck
Sent from my SM-T215 using XDA Premium 4 mobile app

jaspore said:
Excuse me for being a Noob...
To enable USB Debugging is the same as Note 3. Tap on About Phone and the Baseband 7 times (I Think) as almost weeks ago when I tried.
Enable USB Debugging (tick) and all in this paragraph first before trying this website (namely Allow Mock Locations, etc) :
www . mgyun. com / vfroot
Download (立即下载) and Install the software into Desktop.
Need not turn off Tab 3, just connect and wait for the software to detect.
Then it will do its work to root it.
Tab 3 will reboot at least once, and when asked for ADB access, authorize it.
I managed to root my SM-T215 via this method without any knowledge of any programming knowledge.
I hope this helps. Have not checked on Knox yet but glad that I can remove some apps which slows down the Tab 3 LTE
Click to expand...
Click to collapse
samsung has finally released kitkat firmware for SM-T215, the update had factory resetted my device to stock. before i proceed with your www .mgyun. com / vfroot method, will your method still work? (just to be safe)

crazyVato said:
samsung has finally released kitkat firmware for SM-T215, the update had factory resetted my device to stock. before i proceed with your www .mgyun. com / vfroot method, will your method still work? (just to be safe)
Click to expand...
Click to collapse
Sorry for this late reply.
When I had rooted T215, my priority is remove bloatware which includes Software updates. Knowing that Tab 3 hardware will be stretched, I don't want any updates as it will make Tab 3 sluggish.
Thus I am still at 4.2.2. and staying it this way for now.
I am not at 4.4.2+ , so it is still strong with the root.

jaspore said:
Sorry for this late reply.
When I had rooted T215, my priority is remove bloatware which includes Software updates. Knowing that Tab 3 hardware will be stretched, I don't want any updates as it will make Tab 3 sluggish.
Thus I am still at 4.2.2. and staying it this way for now.
I am not at 4.4.2+ , so it is still strong with the root.
Click to expand...
Click to collapse
i've forgotten how i rooted my sm-t215 kitkat. If i'm not wrong, you only need to install/flash only the CWM recovery into your phone, and once you've successfully install/flash CWM recovery, go into recovery and choose reboot now. there will be an option for you to install superuser. choose that and your phone will be auto rooted.
here is the link.
http://forum.xda-developers.com/show....php?t=2674649
do it at your own risk, i won't be responsible for anything in case something goes wrong as this only based on my memory.
GOOD LUCK

how could i enable lte option
even it is 4glte .this particular option is missing in network mode

Help with rooting g3 v20i

Hello everybody ..i updated my phone D855 to lollipop v20i but im not able to root it ..i tried all methods but nothing worked ..it keeps giving me DONE but it doesnt install SuperSU ..and when i install it manually it says my phone not rooted ..is there any way to make it work?

LG One Click Root works!
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
dont forget to enable developer mode by acess into about phone > software information on settings and tap 4/5 times the compilation number until unlock developer settings, go back and enter in menu developer settings and check the debug usb option and then root it!

copy2050 said:
LG One Click Root works!
http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
dont forget to enable developer mode by acess into about phone > software information on settings and tap 4/5 times the compilation number until unlock developer settings, go back and enter in menu developer settings and check the debug usb option and then root it!
Click to expand...
Click to collapse
Thank you ..but i tried this one too ..everyone who updated their phones to v20i facing problems with root ..no one could root it

Akhayev said:
Thank you ..but i tried this one too ..everyone who updated their phones to v20i facing problems with root ..no one could root it
Click to expand...
Click to collapse
you are wrong, i flash the v20i GLOBAL and root with that tool and works fine for me!

Akhayev said:
Hello everybody ..i updated my phone D855 to lollipop v20i but im not able to root it ..i tried all methods but nothing worked ..it keeps giving me DONE but it doesnt install SuperSU ..and when i install it manually it says my phone not rooted ..is there any way to make it work?
Click to expand...
Click to collapse
Sounds like you have the 'New' v20iEUR....
Try this :- http://forum.xda-developers.com/showthread.php?t=3072767
Post #216 - jac10000 Old 23rd May 2015, 09:14 PM (Last edited by jac10000; 23rd May 2015 at 10:28 PM.) #216
New ----> 20P
20P --> If you are not root having applied this tool, copy UPDATE-SuperSU-v2.46.zip on your SDCARD , restart on recovery mode and flash UPDATE-SuperSU-v2.46.zip
This :- http://forum.xda-developers.com/showthread.php?t=3048845 by @topet2k12001
Has also been said to work on New v20i...............

I have the same problem, can someone make a guide to root the 20i ?

The same for me, i had used all the rooting tools and procedures without any result.

got the same issue, need root to replace the lteconfig file but cant
no LTE for ME

Not working on D855 V20i TWN Stock Rom. I just reflashed my old V20h to stock V20h because I had root and OTA V20i update was annoying. No root methods work, script/manual or GUI.

[Q] AT&T Note Edge Root, Kingroot + SafeStrap?

for a Samsung Galaxy Note Edge (AT&T SM-N915A) Has anyone used ODIN to flash 4.4.4 from Lollipop (which I read doesn't trip knox) and then used Kingroot to get temporary root and then install Safestrap? I didn't really find any custom roms, but when booting from Safestrap, wouldn't root still be available even if you installed the stock Lollipop rom as the SS rom? Or would it be too difficult to remove the recovery if that's present in the stock LP rom so it doesn't mess with SS if you boot from it?

Slimicus said:
for a Samsung Galaxy Note Edge (AT&T SM-N915A) Has anyone used ODIN to flash 4.4.4 from Lollipop (which I read doesn't trip knox) and then used Kingroot to get temporary root and then install Safestrap? I didn't really find any custom roms, but when booting from Safestrap, wouldn't root still be available even if you installed the stock Lollipop rom as the SS rom? Or would it be too difficult to remove the recovery if that's present in the stock LP rom so it doesn't mess with SS if you boot from it?
Click to expand...
Click to collapse
I did use ODIN to go back to KitKat and then used Kingoroot, but the safestrap part your talking about I have no clue. Was unaware of any safestrap for the Notre 4 or Edge.
Back on Lollipop unrooted though. Found the temp root annoying and with FF browser and AdBlock plugin I'm getting by

help
rquinn19 said:
I did use ODIN to go back to KitKat and then used Kingoroot, but the safestrap part your talking about I have no clue. Was unaware of any safestrap for the Notre 4 or Edge.
Back on Lollipop unrooted though. Found the temp root annoying and with FF browser and AdBlock plugin I'm getting by
Click to expand...
Click to collapse
Can you plz send me a link for the kitkat firmware?

shylude said:
Can you plz send me a link for the kitkat firmware?
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-edge/general/att-note-4-edge-kitkat-odin-tar-files-t3108344

What's up guys? I need some help rooting my N-915A, can you guys show me the path. I'm running lolllipop 5.0.1

Is there ever going to be a root for this phone? Its almost a year and nothing is out yet? I have never had to wait this long for any android phone before. so frustrating

Anything yet

xxswagga1xx said:
What's up guys? I need some help rooting my N-915A, can you guys show me the path. I'm running lolllipop 5.0.1
Click to expand...
Click to collapse
Sorry, no permanent root yet... But the 5.1.1 upgrade is available, just remember to clear the cache before attempting to upgrade.
djwasel said:
Is there ever going to be a root for this phone? Its almost a year and nothing is out yet? I have never had to wait this long for any android phone before. so frustrating
Click to expand...
Click to collapse
Probably not, but that is my opinion and not based on fact.
sandog12 said:
Anything yet
Click to expand...
Click to collapse
Sorry, no permanent root yet...

So it is possible now to get temporary root access using kingroot on 5.1.1 but I am hoping someone get this information to chainfire so that chainfire can use it to come up with a permanent root using odin.

How could i upgrade to 5.1.1 im using 915a in pakistan? Can any on help me ?

hey guys,
I am from Vietnam and i just 've bought the SM-N910A (said that from ATT) in Vietnam. I used RootChecker and Phone INFO to get to check my phone.
The result is my phone was ROOTED!!!. I restarted some times but the ROOT is still accessed.
I tried to use Root Explorer to copy/paste from/into system folder, it's ok like other rooted devices.
I'm following xda-note edge and see everyone's saying that NO way to permanent root ATT note egde.
I also dont know what method the seller used to root my edge, but i think it's permanently rooted.
I've NOT try to unlock bootloader neither install recovery. There seem to be no official method for ATT edge. I am afraid bricking my device.
I upload some screen to show you my note. Thanks and need your advice, guys

datbi_201 said:
hey guys,
I am from Vietnam and i just 've bought the SM-N910A (said that from ATT) in Vietnam. I used RootChecker and Phone INFO to get to check my phone.
The result is my phone was ROOTED!!!. I restarted some times but the ROOT is still accessed.
I tried to use Root Explorer to copy/paste from/into system folder, it's ok like other rooted devices.
I'm following xda-note edge and see everyone's saying that NO way to permanent root ATT note egde.
I also don't know what method the seller used to root my edge, but i think it's permanently rooted.
I've NOT try to unlock bootloader neither install recovery. There seem to be no official method for ATT edge. I am afraid bricking my device.
I upload some screen to show you my note. Thanks and need your advice, guys
Click to expand...
Click to collapse
When you moved data into /system did you remove it before rebooting, or did you leave it in /system and were still able to boot?
If you could enable USB Debugging and open a shell with ADB and type "ps", then post the output, that may be a place to start.

Recently, kingroot has been able to get root on my note, but after 5-10 minutes I get ANRs and the phone crashes, then I have to re flash with Odin to go back to stock. I have logcat logs up to where it crashes as well.
I'm on 5.1.1
Edit
5 minutes after I posted this AT&T tried pushing a security update. Probably to fix this.
Sent from my SAMSUNG-SM-N915A using XDA-Developers mobile app

cabewse said:
Recently, kingroot has been able to get root on my note, but after 5-10 minutes I get ANRs and the phone crashes, then I have to re flash with Odin to go back to stock. I have logcat logs up to where it crashes as well.
I'm on 5.1.1
Edit
5 minutes after I posted this AT&T tried pushing a security update. Probably to fix this.
Sent from my SAMSUNG-SM-N915A using []
Click to expand...
Click to collapse
Hi, i have a n915a too but the baseband ends in BOC8 and the last firmware is 5.0.1, if i use the stock firmware 5.1.1 from other baseband? it will brick the phone?.
is there a way to install different firmware from another model?, like change n915a to n915f or something like that
sorry, my english is not good.

kashaki said:
Hi, i have a n915a too but the baseband ends in BOC8 and the last firmware is 5.0.1, if i use the stock firmware 5.1.1 from other baseband? it will brick the phone?.
is there a way to install different firmware from another model?, like change n915a to n915f or something like that
sorry, my english is not good.
Click to expand...
Click to collapse
Bringing this back to life, we are now September of 2016. Any way of permanent root on Note Edge?

Lethal Ludacy said:
So it is possible now to get temporary root access using kingroot on 5.1.1 but I am hoping someone get this information to chainfire so that chainfire can use it to come up with a permanent root using odin.
Click to expand...
Click to collapse
I root my phone using kingroot at&t SM-N915A 5.1.1

stunomatic0 said:
I root my phone using kingroot at&t SM-N915A 5.1.1
Click to expand...
Click to collapse
I did temp root with KingRoot too. I went and disable the bothering Carrier IQ which was taking all my zerolemon battery. And also I disable most most of the bloatware of at&t.
Let's hope Chainfire or someone co.e with the permanent one.
Sent from my SAMSUNG-SM-N910A using Tapatalk

Customs boot icon
I rooted my at&t note edge using king root. Then I installed SuperSU and used the option to install binaries in "normal" mode. Then the phone rebooted and in the booting screen i got an icon with an unlocked lock that said "Custom" then the phone booted normally no problem.
I dont know if this information is useful but i thought it was important to share.

juanfe1a said:
I rooted my at&t note edge using king root. Then I installed SuperSU and used the option to install binaries in "normal" mode. Then the phone rebooted and in the booting screen i got an icon with an unlocked lock that said "Custom" then the phone booted normally no problem.
I dont know if this information is useful but i thought it was important to share.
Click to expand...
Click to collapse
What android do you have?
SAMSUNG SM-N910A With Tapatalk

gremy1987 said:
What android do you have?
SAMSUNG SM-N910A With Tapatalk
Click to expand...
Click to collapse
I have 5.1.1. After rooting the phone repeatly bacause after 30 seconds of being rooted the phone rebooted. I went into download mode (home + dwVol) the status showed that was official and that it was locked. I don't know if this information is relevant but sharing is important.

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