Develop Bugs

|Guide|How-To| Root & Install Custom Recovery for 4.3 / 4.4 Update |16 July 2014 |

|Guide|How-To| Root & Install Custom Recovery for 4.3 / 4.4 Update |16 July 2014 |
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here.
If you have not updated to 4.4, go here.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Edit:
Here is some potentially useful info for root method #1 from ansonantonym.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery then flash SuperSu and the Knox Remover
4) Reboot
5) Download SuperSu from the Play Store
6) Open SuperSu and update the binary when prompted
7) Reboot
8) Enjoy rooted 4.3/4/4
Downloads:
Odin
TWRP (Odin flashable tar)
SuperSu (v1.65)
SuperSu (v2.01)
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
Please be sure to thank Chainfire, Dees_Troy, and Kaito95.
*****

Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

jeremyds45 said:
Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.

upndwn4par said:
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.
Click to expand...
Click to collapse
Ah it is so nice to have root again... Thank you so much for putting up with a noob.
Crazy events of a noob that lead me to root
Installed ota 4.3
Tried to root and install superuser by odin and then custom recovery to flash
Root didn't happen because of knox
Could only get to CWM custom recovery if it was right after odin and battery pull?...
Flashed the script to remove knox, which did remove knox
Tried the same root method as above and no root access
Tried supersu and then updating in play with no success
Changed security update settings etc nothing
Reset delvik, cache, permissions, etc nothing
Different root method and files for odin, and custom recovery stuck
Used files from this thread, went into custom recovery and flashed supersu
Installed supersu from play store...
Updated the binary using custom recovery
Rebooted...
ROOT access, all root applications work fine and root sticks even after reboots
I never messed with cf auto root method
THANK you guys for your time effort and sharing, helps noobs out like me a lot!

Sweet! I've missed root since I upgraded using the OTA file you provided. Looking forward to much other great things coming from you

Thank You
upndwn4par said:
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here. Make sure you understand the risks and uncertainties described in the OP.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery and flash SuperSu.
4) Flash the Knox Remover
5) Reboot
6) Download SuperSu from the Play Store
7) Update the binary when prompted
8) Reboot
8) Enjoy 4.3
Downloads:
Odin
TWRP (Odin flashable tar)
UpdateSuperSu
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
*****
Click to expand...
Click to collapse
Method two absolutely worked. Thank you so much. I was scared to flash TWRP but knowing you did it gave me the courage. Have full root and happy

questions about this root
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.

THANKS!!!! your a lifesaver didn't know how much longer i could take without root

Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??

bkong said:
Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??
Click to expand...
Click to collapse
use the TWRP method worked perfected for me

Thanks

PimpMyPC said:
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.
Click to expand...
Click to collapse
The second method worked great. I believe (and the way that worked for me) that you use your custom recovery to flash the knox script, not using Odin and pda. I don't think it removed anything other than knox, there is a different script for removing knox and att bloatware. Should still be able to factory reset... But can't guarantee that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Root & Knox
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????

tailgunner9 said:
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????
Click to expand...
Click to collapse
Those settings are just for granting device administrator privileges. If unchecked, Knox is still doing it's thing, just not at an administrative level.
Yes, it is safe to try and root.
I have Android Device Manager as admin. That way if I ever lose my device I can just log in to the Play Store and locate and / or wipe the device.

To do this just flash the recovery.img file using odin and clicking the pda button correct?

Is there a way to freeze Knox instead of deleting it in the event I would want to go back to full stock?

After you are rooted, use an app like Titanium Backup(pro) or My Backup pro. Both will freeze it.

Root
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks

tailgunner9 said:
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks
Click to expand...
Click to collapse
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.

indymx said:
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.
Click to expand...
Click to collapse
Thanks indymx, may get the nerve up to try it on my AT&T S3. Let me know if you run into any problems. Guess Rom Manager and other programs that require Root are working Ok and you have rebooted few times to be sure it keeps Root?? Have Happy Thanksgiving.

Kingroot on E500H lollipop

Now kingroot method can root Galaxy E500H running lollipop 5.1.1 , even if u reboot ur device, it'll be rooted...
Sent from my SM-E500H

Thanks man
---------- Post added at 08:44 PM ---------- Previous post was at 08:28 PM ----------
Not work with me
Kingroot v 4.6.2

I works fine with me without any problem.
Sent from my SM-E500H

i loose root if i restart.

Stuck on Reactivation Lock screen on boot
I recently rooted my Samsung E500H using Kingroot. It completed successfully. But as I restarted my phone. It stuck on Reactivation Lock on first screen before boot.
Please Help

talent.anand said:
I recently rooted my Samsung E500H using Kingroot. It completed successfully. But as I restarted my phone. It stuck on Reactivation Lock on first screen before boot.
Please Help
Click to expand...
Click to collapse
Dude chainfire released a root for E5 E500H why you use kingoroot?
here is the link https://autoroot.chainfire.eu/ search for your model and download it then flash it via Odin

What is the difference between the two? Am using kingroot with no issues on E500H or is there something I didnt know?

mtadao said:
What is the difference between the two? Am using kingroot with no issues on E500H or is there something I didnt know?
Click to expand...
Click to collapse
1.Kingroot doesnt trigger knox while cfroot does.
2.kingroot installs its own superuser management app.Cf autoroot uses supersu.
3.kingroot is network based while cfautoroot requires flashing by odin
Users have reported that kingroot root disappered after reboot

Root doesn't disappear after boot for me, it's permanent

but it's not stable as CF

Will try it and see

Is it ok to use cf autoroot. I already rooted with kingroot but root dissappear after reboot. Any special requirement for cfautoroot? Simply i should glash via odin right.

your knox will be tripped donot follow this kingoroot if yiu have updated ypur device to latest version you will loose the my knox feature of your device which is best feature of samsung so far and exclusive also...

can the root be reversed? if so,how??

Systemless Root: SuperSU v2.64... No (custom) Kernel needed

**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.

Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.

balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.

balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
Fixed!

koop1955 said:
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.
Click to expand...
Click to collapse
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).

JoeFCaputo113 said:
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).
Click to expand...
Click to collapse
I wasn't sure if CM13 is already working on International phones.
I only know what I read....
From Chainfire's post:
Rooting procedure:
- flash/upgrade to Marshmellow
- flash modified boot.img
- flash/boot TWRP and sideload latest...
Joe, be careful if you try this. Looks like you need to Odin back to stock.

Does this still void knox?

1619415 said:
Does this still void knox?
Click to expand...
Click to collapse
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.

koop1955 said:
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.
Click to expand...
Click to collapse
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox

1619415 said:
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox
Click to expand...
Click to collapse
Well Merry Christmas!

JoeFCaputo113 said:
Well Merry Christmas!
Click to expand...
Click to collapse
You to
---------- Post added at 01:52 PM ---------- Previous post was at 01:01 PM ----------
Has anyone tried rooting with this method and trying samsumg pay?

Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.

todivefor said:
Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.
Click to expand...
Click to collapse
Try Number 15

1619415 said:
Try Number 15
Click to expand...
Click to collapse
Thanks. Been there done that.
Sent from my SM-T710 using Tapatalk

For those asking about whether this root method trips knox or not. Yes this will trip knox. Anytime you use odin to flash non official Samsung firmware/software then it forever trips knox. Therefore flashing any custom recovery will absolutely trip knox... forever.
Samsung and Android pay apps will not work on rooted devices. Period. The pay apps are intended for official factory software for obvious reasons. Security is the main focus with these types of apps that deal with your personal banking/credit card information. Hence a rooted device is not considered "secure".

using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.

yaibakt said:
using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.
Click to expand...
Click to collapse
Try installing/updating busybox and try removing titanium backups root access them regrant it

JoeFCaputo113 said:
**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.
Click to expand...
Click to collapse
Nice work will give this a go soon.

1619415 said:
Try installing/updating busybox and try removing titanium backups root access them regrant it
Click to expand...
Click to collapse
thank you. ill give it a try. :good:

This may be a weird question, but we don't have a stock kernel to flash. Would there be a way to make a zip of a stock kernel and then use this to get root? I'd like to have a custom ROM but with the stability of a stock Kernel. This is the first phone I can think of that I've owned that didn't have a stock kernel with root.

Want to get rid of KingRoot

I updated my Z1 Compact from 4.4.4 to 5.1.1 using FlashTool and a Stock ROM
I then searched for the easiest root available and it seemed to be KingRoot and it went fine... the device was rooted quite fast.
But then i read from other people that KingRoot installs all kinds of crap - and i noticed that too
I couldn't install SuperSU or make it work so i just wanted to get completely rid of KingRoot again..
I found a SuperSU KingRoot remover using a Terminal - but that didn't work
So now i've Flashed the device again and factory reset it + updated to latest 5.1.1 ...
So now is the question :
Is my device clean of KingRoot ??
how to tell ??
Thanks

Montago said:
I updated my Z1 Compact from 4.4.4 to 5.1.1 using FlashTool and a Stock ROM
I then searched for the easiest root available and it seemed to be KingRoot and it went fine... the device was rooted quite fast.
But then i read from other people that KingRoot installs all kinds of crap - and i noticed that too
I couldn't install SuperSU or make it work so i just wanted to get completely rid of KingRoot again..
I found a SuperSU KingRoot remover using a Terminal - but that didn't work
So now i've Flashed the device again and factory reset it + updated to latest 5.1.1 ...
So now is the question :
Is my device clean of KingRoot ??
how to tell ??
Thanks
Click to expand...
Click to collapse
Maybe too late, but the best thing would have been to install recovery once you were rooted, then you can use recovery to flash a whole new system with su instead of KingRoot. If you want to root again with KingRoot, you can try that. Once you've rooted, install recovery, and download a prf or other stock based rom zip file that has su included, then boot to recovery, wipe everything, and flash new rom.
---------- Post added at 02:52 PM ---------- Previous post was at 02:47 PM ----------
Montago said:
I updated my Z1 Compact from 4.4.4 to 5.1.1 using FlashTool and a Stock ROM
I then searched for the easiest root available and it seemed to be KingRoot and it went fine... the device was rooted quite fast.
But then i read from other people that KingRoot installs all kinds of crap - and i noticed that too
I couldn't install SuperSU or make it work so i just wanted to get completely rid of KingRoot again..
I found a SuperSU KingRoot remover using a Terminal - but that didn't work
So now i've Flashed the device again and factory reset it + updated to latest 5.1.1 ...
So now is the question :
Is my device clean of KingRoot ??
how to tell ??
Thanks
Click to expand...
Click to collapse
Also check this - http://forum.xda-developers.com/showpost.php?p=65004634&postcount=2

this is exactly what i tried... but some of the files couldn't be deleted and i got like 30 warning messages that KingRoot couldn't start...
I wasn't confident that everything had been removed - especially not when i could find KingRoot files and folders all over the system afterwords ??
http://zidroid.com/how-to-get-ride-and-replace-kinguser-with-supersu-app/

Verizon Note 4 on 6.0.1 Help Rooting

Hey so i have done my job and spent the past week figuring out how to do this. Unfortunately i am on 6.0.1 and every time i flash TWRP 2.8.7.0 VSW with odin my phone blocks it and says SECURE CHECK FAIL (RECOVERY). yes my reactivation lock is off and nothing is encoded. as of right now my phone is working but i would really like to get it rooted soon and any help is appreciated.

joe1996 said:
Hey so i have done my job and spent the past week figuring out how to do this. Unfortunately i am on 6.0.1 and every time i flash TWRP 2.8.7.0 VSW with odin my phone blocks it and says SECURE CHECK FAIL (RECOVERY). yes my reactivation lock is off and nothing is encoded. as of right now my phone is working but i would really like to get it rooted soon and any help is appreciated.
Click to expand...
Click to collapse
You need to be rooted before you flash TWRP. Have you already gone through the steps to root your phone?

quinciebee said:
You need to be rooted before you flash TWRP. Have you already gone through the steps to root your phone?
Click to expand...
Click to collapse
No I am not rooted every guide I find says you need to flash a custom recovery then install the root from that recovery?

Hi i have Samsung note 4(SM-N910F). When i check root status with( phono info apk) it says root existence (/system/xbin/su) and check with Root checker apk it shows congratulations you are rooted. but super su apk not working after download this apk when i update binary it takes too long time and some times mobile restart itself. Total problem is super su apk not working Now what should i do? Please help me

joe1996 said:
No I am not rooted every guide I find says you need to flash a custom recovery then install the root from that recovery?
Click to expand...
Click to collapse
You may be confusing flashing supersu in a custom recovery, with rooting your phone. There are a number of steps you have to go through before you can gain root on the Verizon Note 4. Flashing a custom recovery will not root your phone. You have to first follow the steps here, before you can flash a custom recovery, then flash supersu, in order to gain access to your root.
---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------
Banty448 said:
Hi i have Samsung note 4(SM-N910F). When i check root status with( phono info apk) it says root existence (/system/xbin/su) and check with Root checker apk it shows congratulations you are rooted. but super su apk not working after download this apk when i update binary it takes too long time and some times mobile restart itself. Total problem is super su apk not working Now what should i do? Please help me
Click to expand...
Click to collapse
Try flashing the supersu zip in your custom recovery, instead of installing it through the app store. You also have an N910F, this thread is for N910V. You'd probably get a more accurate response if you posted to the N910F thread.

quinciebee said:
You may be confusing flashing supersu in a custom recovery, with rooting your phone. There are a number of steps you have to go through before you can gain root on the Verizon Note 4. Flashing a custom recovery will not root your phone. You have to first follow the steps here, before you can flash a custom recovery, then flash supersu, in order to gain access to your root.
So I have successfully restored my note 4 to 5.1.1 not im going for root and a custom rom. ill keep you updated.:good:
Click to expand...
Click to collapse

Banty448 said:
Hi i have Samsung note 4(SM-N910F). When i check root status with( phono info apk) it says root existence (/system/xbin/su) and check with Root checker apk it shows congratulations you are rooted. but super su apk not working after download this apk when i update binary it takes too long time and some times mobile restart itself. Total problem is super su apk not working Now what should i do? Please help me
Click to expand...
Click to collapse
Manually flash SuperSU 2.79 (or later) if you are prior to 7.0.1 at this point systemless root becomes necessary .....and I don't know man . I have it working on 7.1.1 but it came loaded I didn't have to install ....hmmmm I'd start at chain fires web site see what he says . ignore anything involving cfauto root unless u achieved root by this means in which case u r in the wrong forum
---------- Post added at 11:14 PM ---------- Previous post was at 11:13 PM ----------
joe1996 said:
quinciebee said:
You may be confusing flashing supersu in a custom recovery, with rooting your phone. There are a number of steps you have to go through before you can gain root on the Verizon Note 4. Flashing a custom recovery will not root your phone. You have to first follow the steps here, before you can flash a custom recovery, then flash supersu, in order to gain access to your root.
So I have successfully restored my note 4 to 5.1.1 not im going for root and a custom rom. ill keep you updated.:good:
Click to expand...
Click to collapse
When you flash supersu it does install app and binary :laugh: see if u got to the point u could flash from twrp it would signify you are on unlocked boot loader. Without unlocking root will only persist til reboot then process would need to be repeated. The only way to fix this is to be able to mod the boot IMG which requires developer mode to be enabled . this is notable by the presence of an unlocked lock on the first splash screen (secondary program loader splash)
Click to expand...
Click to collapse