Related
hi there,
finally i found a more easy way to root my z3tc.
it works with out flashing an other firmware and it keeps the drm keys and your bootloader locked.
its not even necessary to wipe the device, so you can keep all our apps an settings.
so here are the steps i did to get root on my z3tc running the latest kitkat stock firmware.
1.) download and install kingroot 4.1 its an oneclick root, similar to towelroot.
take care that it is v4.1+ and not below !!!
2.) install superuser from playstore (just because you well be asked for it in the next step. i use kinguser for granting permissions later)
3.) download an install XZDualRecovery
(choose option 2, install for superuser.)
4.) download and flash (via recovery) SonyRICDefeat
enjoy full root on your device
nvm
stavro said:
hi there,
finally i found a more easy way to root my z3tc.
it works with out flashing an other firmware and it keeps the drm keys and your bootloader locked.
its not even necessary to wipe the device, so you can keep all our apps an settings.
so here are the steps i did to get root on my z3tc running the latest kitkat stock firmware.
1.) download and install kingroot 4.1 its an oneclick root, similar to towelroot.
take care that it is v4.1+ and not below !!!
2.) install superuser from playstore (just because you well be asked for it in the next step. i use kinguser for granting permissions later)
3.) download an install XZDualRecovery
(choose option 2, install for superuser.)
4.) download and flash (via recovery) SonyRICDefeat
enjoy full root on your device
Click to expand...
Click to collapse
i concur with TS.
But be warned that kingroot's SU binary sometimes have issues with granting access to ADB even though you have allowed it by default.
I spent the entire day troubleshooting my friend's tablet trying to root via kingroot,flashing dual recovery and giving it proper root via supersu. needless to say, it was very educational as it was frustrating.
once you ran the bat file for ric defeat, you still need to dl the app called SDfix (by nextapp) to fully write to sdcard. and yes, the sdcard write bug is still there from kitkat!
Hi There,
Does this Method work with Lollipop?
Is it possible to use Supersuser instead of Kinguser to mangage permissions?
Greets nutz
nutsymtom said:
Hi There,
Does this Method work with Lollipop?
Is it possible to use Supersuser instead of Kinguser to mangage permissions?
Greets nutz
Click to expand...
Click to collapse
Yes works with Lollipop. After running the latest Kingroot (KingRoot-4.1.0.249.apk ), before rebooting I installed dual recovery for locked bootloader. Then rebooted to TWRP and flashed BETA-SuperSU-v2.49.zip, which will uninstall KingUser on first run.
However I got the XignCode3 error from com2us and gamevil games. So I booted back into TWRP and flashed UPDATE-SuperSU-v2.46.zip and everything was peachy.
Teella said:
Yes works with Lollipop. After running the latest Kingroot (KingRoot-4.1.0.249.apk ), before rebooting I installed dual recovery for locked bootloader. Then rebooted to TWRP and flashed BETA-SuperSU-v2.49.zip, which will uninstall KingUser on first run.
However I got the XignCode3 error from com2us and gamevil games. So I booted back into TWRP and flashed UPDATE-SuperSU-v2.46.zip and everything was peachy.
Click to expand...
Click to collapse
is there a special reason why you flashed supersu v2.49 first and v2.46 afterwards? i mean flashing just v2.46 would work as well right ?
@frostmore did you use 4.1 ? as far as i understood ric defeat gives you write access to the system on the internal storage on sony devices (for what normally root would be sufficient) and has nothing to do with the kitkat writing limitation on external cards. so you have to use one of the many apps in the store which will fix this. (or do the trick yourself in an xml file) since i installed xposed as well (this was btw the only reason why i wanted root to be able to use app settings again) i did it there.
It works !!!
Finally. Thx a lot.
Worked great on my SGP611. I didn't bother unlocking the bootloader. I performed this on 23.1.A.0.690. I first replaced with SuperSU 2.46, but it seemed to have issues removing KingRoot. I then flashed 2.49 beta, and it removed KingRoot, then I switched back to SuperSU 2.46.
Cheers!
I tried rooting my SGP611 with Android version 4.4.4 and failed. That is when I decided to manually update (flash) it to 5.0.2 with the build number 23.1.A.1.28 (currently the latest version Sony had released). And suddenly the magic happend thanks to KingRoot. On the first try I have successfully rooted my device.
Then, without rebooting, I immediately installed NUT's XDualRecovery via the second method (install on stock modded ROM with superuser).
Next thing I rebooted into TWRP recovery and flashed the latest available BETA version of SuperSU by Chainfire (2.49-BETA).
I rebooted back into system and opened the SuperSU app and removed all the KingRoot apps, updated the 'su' binary with 'Normal' mode in SuperSU and finally rebooted my device again.
The result was satisfying.
At last I have root access on my Xperia Z3 Tablet Compact 16GB Wifi model running Android 5.0.2 with Chainfire's SuperSU, XDualRecovery, Bootloader locked!
I tried RIC defeating my device and wasn't successful. But apperently that's not a big deal because XDualRecovery may have already killed RIC. (Maybe I am wrong(!), so please correct me...)
My favourite apps like AdAway, Titanium Backup, SD Maid and Busybox work flawlessly. And rebooting my device didn't remove my root for now. Well, I have to test it for some days to see if root is permanent.
A big THANK YOU to the KingRoot team.
I tried Rooting my SGP 612 with stock 5.0.2 but got stuck at the first step. Kingroot couldnt root the device succesfully.
Edit: Dont mind the commenct, worked fine on the second try.
ChiDi9901 said:
I tried RIC defeating my device and wasn't successful. But apperently that's not a big deal because XDualRecovery may have already killed RIC. (Maybe I am wrong(!), so please correct me...).
Click to expand...
Click to collapse
I forgot about that part. That didn't work for me either. According to XZDualRecovery thread it does. I can confirm have r/w access to /system, haven't checked anywhere else..
arcane613 said:
I forgot about that part. That didn't work for me either. According to XZDualRecovery thread it does. I can confirm have r/w access to /system, haven't checked anywhere else..
Click to expand...
Click to collapse
I wasn't able to write to my external SDCard until I ran SDFix by nextapp, now I can RW everywhere
hey guys rooted Z3 Tab with Kingoroot..
on the last step i install Supersu 2.49 and install the binaries...
but on the last step install Supersu 2.46 but after reboot
can't install the Supersu Binaries?
Anyone have s a idea for me?
Regards
This method still works on 23.1.A.28
i can't root my SGP621 with kingroot 4.1 :crying:
it says "root access is unavailable"
it's on Lollipop 5.0.2
thanks guys
sir, can i root the sameway ?
@stavro this is my device info...thx
i am not the developer of the root method nor do i have experience with rooting (via kingroot) of other devices then mine (sgp611).
its just a list of things i did to get root in a more simpler way then it was already possible before.
i would expect that it works for the sgp621 too since you have same firmware version then i have.
but if you are not sure you better go to the general kingroot thread and see if other people can confirm that root is working for your device.
Do I have to flash XZDualRecovery and SonyRIC Defeat when I only need root?
stavro said:
i am not the developer of the root method nor do i have experience with rooting (via kingroot) of other devices then mine (sgp611).
its just a list of things i did to get root in a more simpler way then it was already possible before.
i would expect that it works for the sgp621 too since you have same firmware version then i have.
but if you are not sure you better go to the general kingroot thread and see if other people can confirm that root is working for your device.
Click to expand...
Click to collapse
I can confirm that this method works on sgp621!
No issues at all even starting from Lollipop 5.0.2 v23.1.A.0.690 firmware, thank you!
The only thing I can't do is flash RICDefeat patch from recovery (it fails with an error I can't remember), but even without that patch I can read and write \system folder.
Bruce666 said:
Do I have to flash XZDualRecovery and SonyRIC Defeat when I only need root?
Click to expand...
Click to collapse
It's highly recommended to install
XZDualRecovery to automatically gain the RIC patch. You don't need to flash SonyRIC Defeat if you install the recovery because it's already included.
The question is, what do you want to do with root? Having system R/W access is quite important to actually have a complete root experience.
Hi Everyone, l have a question about this Magisk Mod and its directed to s7 & s7 edge users. If anyone is using this Mod, may you please tell us how you got it to work, coz l have tried and failed many times. Your help would be kindly appreciated..
King Addies
Root and install xposed.
I have used a stock rom, as it says on the magisk thread and followed all the instuctions and still failed.. lm not really botherd about using the mod anymore, but l made this thread so all the other people who are in my situation can get help or a tutorial on how to install it on s7 & s7 edge. Coz l could not really get much help from the official thread.
King Addies
I'm using sac23's custom Note 7 port ROM. After installing his ROM, I went to SuperSU, clicked the option for cleanup to install different Super User app. Reboot phone. Then I booted into TWRP, flashed Magisk, then flashed Phh's Super User. Reboot system. Then install Magisk Manager or Auto Magisk app. Activate Auto Magisk under accessibility settings. Works like a dream.
Mr. Orange 645 said:
I'm using sac23's custom Note 7 port ROM. After installing his ROM, I went to SuperSU, clicked the option for cleanup to install different Super User app. Reboot phone. Then I booted into TWRP, flashed Magisk, then flashed Phh's Super User. Reboot system. Then install Magisk Manager or Auto Magisk app. Activate Auto Magisk under accessibility settings. Works like a dream.
Click to expand...
Click to collapse
Thanx for your input on this issue mate, hope the info you have provided helps all those that want to use this Mod on their s7 or s7 edge phones..
King Addies
One more step, sorry. You have to also install Phh's SU app from the Google Play store.
Besides Sac23's Note 7 Port Rom, has anyone else tested or used this Mod on any other s7 or s7 edge Rom..
King Addies
Magisk works fine with any ROM. You just need to use a custom kernel or:
Obtain root using CF - Auto Root
Remove root via SuperSU app
Click No when asked about restoring stock boot.img
Go through the normal Magisk/Phh Superuser steps to install
Only thing I've noticed is that banking apps can still detect that I am rooted. Not sure if this is because I did SuperSU/modified boot.img method. I may try flashing back to stock via ODIN then flashing a custom kernel and install Magisk that way and see.
I've already tried all this. Do you think it's because i've got encrypted device?!
I've tried so many combinations as well... In the end, i have to always restore the stock firmware, run CF-autoroot and xposed normally.
Any ideas why? anyone?!
Galactus said:
Magisk works fine with any ROM. You just need to use a custom kernel or:
Obtain root using CF - Auto Root
Remove root via SuperSU app
Click No when asked about restoring stock boot.img
Go through the normal Magisk/Phh Superuser steps to install
Only thing I've noticed is that banking apps can still detect that I am rooted. Not sure if this is because I did SuperSU/modified boot.img method. I may try flashing back to stock via ODIN then flashing a custom kernel and install Magisk that way and see.
Click to expand...
Click to collapse
kevinwu128 said:
I've already tried all this. Do you think it's because i've got encrypted device?!
I've tried so many combinations as well... In the end, i have to always restore the stock firmware, run CF-autoroot and xposed normally.
Any ideas why? anyone?!
Click to expand...
Click to collapse
Encryption isn't the reason, I'm encrypted too.. There isn't really a benefit to it right now anyways. SafetyNet has been updated, you can't pass it with Xposed PERIOD until another bypass is done by the dev.
The key like someone said on a different thread, is to run CF Auto Root, then unroot with SuperSU. Follow the steps from there and you should be good to go but as I've already said, a lot has changed since then. Su-hide isn't working half of the time etc. Better off waiting for them to sort out all the issues first.
Galactus said:
Encryption isn't the reason, I'm encrypted too.. There isn't really a benefit to it right now anyways. SafetyNet has been updated, you can't pass it with Xposed PERIOD until another bypass is done by the dev.
The key like someone said on a different thread, is to run CF Auto Root, then unroot with SuperSU. Follow the steps from there and you should be good to go but as I've already said, a lot has changed since then. Su-hide isn't working half of the time etc. Better off waiting for them to sort out all the issues first.
Click to expand...
Click to collapse
Maybe I did have it working then, the only thing I tested it with Pokemon go and it didn't work.. so I just assumed it wasn't working, so I reverted all changes. I spent way too much time than I had hoped
Cheers Buddy
Hi there, I install superman rom with magisk already installed but cant find the cheekbox to unroot on Magisk Manager.
Still cant use Snapchat & pokemon go on my s7.
Anyone can help ?
Regards.
Devilover said:
Hi there, I install superman rom with magisk already installed but cant find the cheekbox to unroot on Magisk Manager.
Still cant use Snapchat & pokemon go on my s7.
Anyone can help ?
Regards.
Click to expand...
Click to collapse
Magisk is pointless right now. Simply having an unlocked bootloader causes SafetyNet to fail. The latest version of magisk also removed the checkbox to turn root on and off. To use Snapchat YOU MUST login before any modifications. Make a titanium backup of Snapchat logged in, then you can restore it whenever you want.
silverrum said:
Besides Sac23's Note 7 Port Rom, has anyone else tested or used this Mod on any other s7 or s7 edge Rom..
King Addies
Click to expand...
Click to collapse
Im using Darklord S7e PeK port Latest Kernel and successful MagiskSU install on my Galaxy Note 3 N9005
I flashed it on TWRP 2.0.8.0
When rebooting Do Not Check Install SU (Chainfire SU) if you want Magisk
In Regards to Snapchat i used SC staright after Magisk install from twrp and it logged on also SC allows rooted Lineage OS 7.1.1 :/
PoTBrain• said:
Im using Darklord S7e PeK port Latest Kernel and successful MagiskSU install on my Galaxy Note 3 N9005
I flashed it on TWRP 2.0.8.0
When rebooting Do Not Check Install SU (Chainfire SU) if you want Magisk
In Regards to Snapchat i used SC staright after Magisk install from twrp and it logged on also SC allows rooted Lineage OS 7.1.1 :/
Click to expand...
Click to collapse
What part of S7/S7Edge do you fail to understand?
Or, boot into TWRP, format data to unencrypt then flash latest magisk and reboot. Once booted, open magisk manager hit menu button and open settings, check magisk hide. Exit settings, open menu and open magisk hide, there you can check any app you want to hide from root. done.
So, i tried to Root my GF's I9506 with CF-Autoroot.
Safteynet fails and PokemonGo doesn't work, login problems.
I Unrooted trough SuperSU, restarted the phone a couple of times but PoGo still wont login.
She's on Stock Samsung Rom with Stock Recovery.
What can i do?
I was able to Re-Root with SuperSU for some reason. Had to update the binary tho. That's strange...
Shouldnt work if SuperSU unrooted in the first place?
Maybe it leaves files behind. If you're interested, there are ways to hide root from the game.
Anyway, the only sure way to remove root would probably be the flashing of a stock ROM.
Pwnycorn said:
Maybe it leaves files behind. If you're interested, there are ways to hide root from the game.
Anyway, the only sure way to remove root would probably be the flashing of a stock ROM.
Click to expand...
Click to collapse
Hmm. She really dosen't want to do a factory reset. so i guess i have to hide it then..
I think there are a few options i think all of them needs another recovery though:
Magisk + Magiskhide + phh
SuperSu, Suhide
Something called iSu.
Might it help to root again, remove anu "Su" files and folders trough ES Filexplorer? Then unroot from SuperSu?
If the phone is running a stock ROM, flashing a stock ROM usually leaves all of the data intact.
Dallebull85 said:
Hmm. She really dosen't want to do a factory reset. so i guess i have to hide it then..
I think there are a few options i think all of them needs another recovery though:
Magisk + Magiskhide + phh
SuperSu, Suhide
Something called iSu.
Might it help to root again, remove anu "Su" files and folders trough ES Filexplorer? Then unroot from SuperSu?
Click to expand...
Click to collapse
Removing any root file live might break root, which in turn won't let you remove any of the other files left.
Besides, you don't even know what files to look for.
Having a custom recovery won't affect her usage of the phone, nor the game. Besides, it gives you the benefit of making a Nandroid backup.
Ty for all the answers. So a custom Recovery doesn't trigger Saftynet?
Might as well install TWRP, backup and try to reflash stock rom from there.
Samsung Galaxy S4 International Qualcomm (jfltexx)
Samsung Galaxy S4 LTE Advanced i9506 (ks01lte)
Which one? i suppose its the 9506, flashhing my old CF-autoroot for my 9505(jfltexx) didn't work.
To flash a stock ROM, you need Odin, Samsung phone drivers, and the stock ROM from sammobile.com.
OK. But i'll do a backup on twrp first. Ty ty
Fixed it! Reflashed stock Rom with Odin and now Pogo works again!
Ty a lot for all the help. you guys are the best!
Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Cool:good:
Xposed isn't working with magisk? I was planning to install it
amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk
Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )
how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?
We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...
We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?
We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2
Hi, so I was trying to get full root not only system less root on j730gm and what i followed here to rooted mobile witj twrp first(boot.img patched), then after that full unroot (keep boot.img patched) and in twrp gave command and install super su zip again and this time logs clearly showed system method while rooting, after all that I am getting bootloop. Mobile is hang on samsung logo, tried reset with twrp and official recovery both. Can some one tell me where i did mistake or where is the problem. My only requirement is to root this mobile and make super user app as system app. Even after hard reset mobile should stay rooted. Any help would be much appreciated.
Br
Zish
zishhaider said:
Hi, so I was trying to get full root not only system less root on j730gm and what i followed here to rooted mobile witj twrp first(boot.img patched), then after that full unroot (keep boot.img patched) and in twrp gave command and install super su zip again and this time logs clearly showed system method while rooting, after all that I am getting bootloop. Mobile is hang on samsung logo, tried reset with twrp and official recovery both. Can some one tell me where i did mistake or where is the problem. My only requirement is to root this mobile and make super user app as system app. Even after hard reset mobile should stay rooted. Any help would be much appreciated.
Br
Zish
Click to expand...
Click to collapse
I don't understand your goal?
Systemless root IS full root. Your terminology is incorrect.
SuperSU doesn't really support system root on Android 7.
I also dont see the point of making SuperSU a system app. Even though its rather pointless if that is all you require for whatever strange reason then you can just move the Supersu app to the system partition.
There is a better way to stay rooted after a hard reset and it's called FRP.
First there is nothing strange in stay rooted after hard reset, trust me. My friend use this mobile. He needs root for lucky patcher. When first he came to me I rooted it via twrp and after couple of days he came back with custom binary block option and plus he doesn't remember newly created gmail id pass. For me it was hell of a job. So i decided to root it permanently. I am not an expert though but my point was to take full root instead of systemless root. Thanks for clearing that 7.0 isn't supported for full system root. I saw here a rom stock dexoded and pre rooted. Is it better option to install it rather than stock rom?
See this link, i was trying to do the same
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
zishhaider said:
See this link, i was trying to do the same
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
Click to expand...
Click to collapse
Like I already stated Factory Reset Protection (FRP) is already built in to SuperSU.
Just do the following in a terminal then re-install SuperSU:
echo "FRP=true">>/data/. supersu
.