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.
I can confirm that Magisk v11.6 installs and appears to function perfectly on my stock, unrooted, bootloader unlocked MCG24.251-5-5 device. Also, MagiskHide is not enabled by default, so keep this in mind if you're using a work device or any other situation where you might get in trouble for failing safetynet. That's all I know so far.
Go forth and Magisk!!!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Pics or it didn't happen
And last, but certainly not least...
So I can root without unlocking the bootloader using sunshine?
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No. Sunshine unlocks your bootloader, so you can then root.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
There will never be a free root for this device unless you develop it, so you can save yourself the time asking in so many different threads.
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Tokogon said:
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Click to expand...
Click to collapse
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
TheSt33v said:
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
Click to expand...
Click to collapse
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Tokogon said:
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Click to expand...
Click to collapse
Sorry, I was wrong about being able to disable it. There doesn't seem to be an option for that. But as long as Magisk Hide is enabled, Pokémon Go works fine for me.
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
y8s said:
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
Click to expand...
Click to collapse
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
TheSt33v said:
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
Click to expand...
Click to collapse
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
y8s said:
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
Click to expand...
Click to collapse
I installed it on stock MCG24.251-5-5 and Superuser is an option that appears in Magisk Manager. Yes, you should probably have the stock boot image before installing Magisk. I think the Magisk installer is designed to detect existing installations of SuperSU and not install its own superuser if it's detected, so if the full unroot didn't clean itself up properly for whatever reason, that might be why it didn't install with superuser.
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Is that correct or should I use another kernel version? I don't want another bootloop or damaged wifi^^
Einheit-101 said:
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Click to expand...
Click to collapse
I don't see any problems with that plan, but you should know that xposed will insta-fail safetynet. If you want to hide modifications from anything that uses safetynet, xposed in any form is not an option. The only thing that works for me is Magisk 11.6's built in root, no xposed, no other modifications. With that, I can use Android Pay, Pokemon Go and my banking apps just fine as long as Magisk Hide is turned on. Android Pay and PoGo are blocked by default, but you need to make sure to go in and manually check the box next to every other app that you want to hide stuff from.
Also, if you insist on using SuperSU instead of the built in Magisk root (why???), you will also have to install the latest version of suhide (and I'm not positive that works anymore).
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
I just haven't had time to dig up another boot.img and flash it. I might revert back to SuperSU and come back to this later.
Einheit-101 said:
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
Click to expand...
Click to collapse
Try clearing the data for your banking app. Maybe it's set up so that once it fails, it never checks again. Also, clear cache/dalvik cache in TWRP if you haven't already. Also also, did you remember to block the banking app in magisk hide?
Good afternoon,
After MUCH research, I have arrived at the conclusion rooting the D6616 with T-Mobile's likely final Z3 build for 5.0.2 (Build 23.1.C.0.399 and, really anything past KK) is no longer possible without involving Kingroot.
Why does this matter? Because there may not be a feasible way to remove the most recent builds of Kingroot from the D6616 ROM. Using Kingroot's own uninstaller in the App settings fails and factory resetting using the ROM/stock recovery threw my phone into a bootloop. Other users report it successfully factory reset their ROM with kingroot installed as a system app and their device no longer rooted. I attribute the variety of outcomes to different software builds and Kingroot versions.
It seems as though the only working root method also uses ZXDualRecovery. Though I have not tried it, all procedures that show the ZXDualRecovery method of pushing recovery and superSU involved rooting the device with Kingroot first and removing it after SuperSU is installed. This appears to be the only still-working method of acquiring temporary root long enough to install recovery. The only way to remove Kingroot is to use flashtool and a new Sony TFT, which also removes root and recovery.
Has anyone successfully been able to pull off rooting a D6616 lately? I want to keep this phone but it is unfortunately useless to me without working root so I'll likely be returning it if nobody still has one that's running the last software with a locked bootloader.
I would really appreciate any help anyone can give.
I believe I have done it! I think SuperSU is ever so slightly ahead of Kingroot.
What I did:
1) Rooted via Kingroot app on Google Play. Run rootchecker after it's done its business to make sure. DO NOTHING ELSE IN THE APP. Doing so may prevent SuperSU from kicking its ass later.
2) Downloaded and upacked to desktop the file for Xperia Z3 from here:
http://nut.xperia-files.com/path/XZD...ecovery_2.8.26
Z3-lockeddualrecovery2.8.26.-RELEASE.combined.zip
3) Disabled antivirus
4) Installed USB drivers via Windows 7 plug-n-play. Unplug phone.
5) Downloaded SuperSU recovery flashable zip from here:
http://www.supersu.com/download#zip
6) Ran install.bat from extracted ZXDualRecovery zip
7) Enabled developer options in phone, enabled USB debugging, revoked USB devices, rebooted phone, plug in phone.
8) Connect Phone, wait for device to register in windows.
9) Okayed communication from PC.
10) Place in USB Install Mode on phone.
11) Choose option 2 to install to device rooted by SuperUser. Kingroot has blocked option 1 (old method)
12) Enter TWRP (Automatic) and go to Backup, check all boxes, create Nandroid by sliding the slider
13) Reboot, ensure phone boots. Put SuperSU.zip on the external flash drive. Go to your new App: NDR Utils. Choose TWRP as Primary Recovery. Choose Reboot to Primary recovery
14) Flash zip for SuperSU. DO NOTHING ELSE. Do not wipe cache, do not fix permissions. Click REBOOT.
15) Launch SuperSU App. Attempt to update Binaries. It will not, but it will detect Kingroot, and somehow can get rid of it itself using onboard capabilities. It will do so and update binaries.
16) Reboot (Automatic via SuperSU)
17) Check to make sure SuperSU binaries installed by launching the app.
18) Reboot to recovery using the steps from step 13) above.
19) Create another backup using step 12) above
20) Reboot and DONE.
To the best of my knowledge, nobody has indicated how to do this in a clear Step-By-Step for the final build of this ROM. So because I've troubled you all for small chunks of the process I figured I would.
This applies to T-Mobile's likely-final software release for the Xperia Z3 android 5.0.2 on build 23.1.C.0.399.
DISCLAIMER TO ANYONE ATTEMPTING THIS: It appears Kingroot is "onto" what it is being used for. Given the behavior of this application, there is no reason for anyone to believe it is not a malicious program, but it is a necessary evil for this purpose. Newer versions of SuperSU are capable of removing Kingroot on their own, but alternative methods may be necessary. I attempted an earlier version of SuperSU and it was incapable of removing Kingroot.
It might remove via debloater. This is the only way to remove the system apps on this phone reliably, so you WILL need it if you intend to keep the bootloader locked. I couldn't get any root-enabled appstore app to do it including ES File explorer and Titanium Backup. It looks like you need a computer to remove system apps on this phone. Fantastic. Debloater works great though so don't be afraid to use it. Use the filter to search for Apps. You can remove them, but they will not be gone until you reboot your device. Hooray no more filecommander and lookout! Debloater can be found here:
https://forum.xda-developers.com/and...bloat-t2998294
Plug in your phone. Give it root access. Easy peezy.
Then Xposed current framework and installer:
https://forum.xda-developers.com/sho....php?t=3034811
Version 3.1.1 fixed the bootloop problem, so you shouldn't need the fix zip, or at least I didn't. But if you do, you can find it here:
https://dottech.org/187028/how-to-fi...-z5-z4-z3-tip/
Flash the framework for your device in recovery (arm) and then the installer APK from the ROM using a file browser.
FINALLY Youtube Adblock and minimized playback. SCORE!
I think that's about it. That's literally the best we can currently hope for from this device. I think there is an Xposed module to heavily alter the look of the ROM here but I have not tried it. Plus it only claims to work w/ 4.4, and we have 5.0.1.
https://forum.xda-developers.com/z3/...6#post71601966
For devicewide adblocking I use DNS66 since there are no proxy settings for adblocking on this device, unless I'm missing something. I really hope I am. This means there's no native adblocking.
Xposed modules worth using you can find by searching in the Xposed store: Blurred System UI (LP), Gravity Box [LP], RootCloak, Xperia/AOSP NavBar Buttons, Xperia Super Radio, YouTube AdAway, YouTube Background Playback. And of course DNS66 (PlayStore).
I have tinkered with the rest and find them of no value.
I followed the steps but SU didn't ask to update anything. It just opens up and everything is fine?
Then all I did was unistall kingroot(purify) and it looks like it's gone, but is it?
Just leaving this here, this is how I rooted on Android 5.0.2 with the D6616
http://nut.xperia-files.com/
Read the documentation that comes with the latest XZDualRecovery and flash SuperSU or whatever you want.
stef-nix said:
Just leaving this here, this is how I rooted on Android 5.0.2 with the D6616
http://nut.xperia-files.com/
Read the documentation that comes with the latest XZDualRecovery and flash SuperSU or whatever you want.
Click to expand...
Click to collapse
Were you able to install twrp without rooting first on your PC? It doesn't work for me. I did option 3, install on unrooted device.
Are you able to systemless root?
When I run the installation it fails at step 3 on the install bat.
Hi, a bit of an old thread, but has anyone had any success rooting the D6616 without using Kingoroot or Kingroot? Both are malware which are designed to not be fully removed and be as resilient as possible, and uninstall does not actually uninstall them...
Yes, the old method still works. Use the search feature. I'd just link you, but I"m busy at the moment.
i followed these steps, and have gotten to the point where you flash supersu and reboot, but i'm stuck in a reboot loop now. wanted to use this old z3 as a dedicated audio player, and needed to root for some audio enhancements...
edit: i did have TWRP for a minute, but now when i go into recovery it's the stock recovery again, with options only to continue booting, boot to safe mode, factory recovery or power down. the first two options return to a boot loop. can/should i attempt to use flashtool, or factory recovery? i don't want to accidentally wipe something i might need in the backup.\
UPDATE 10/19: I was able to get back to ground zero using Sony's xperia companion software repair. Flashtool 9.25 and 9.26 would never successfully install flashmode drivers, nor would it display the stock .ftf file.
fierogt42 said:
Yes, the old method still works. Use the search feature. I'd just link you, but I"m busy at the moment.
Click to expand...
Click to collapse
this new method seems to fail for me on both of my old z3's. does the method you're referring to involve downgrading to 4.4.4? i've done some extensive searching of this forum (and the android development ones as well) but don't seem to be able to find any other info.
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
.
back when engineermode exploit backdoor 'thing' whatever you want to call it, was still a thing i seized to opportunity to gain root access, however since then magisk hide has begun failing me and i would like to either find a way to update magisk from v14.0 safely, or to unroot completely (preferably without wiping) as this has started being problematic. I am on the latest oxygenOS update and i used this guide to root (i originaly linked it here but apparently i cant do that, it was on github, called OneplusRoot by a fella named aldur.)
If anyone can help id really appreciate it.
Thanks in advance
Since One Plus removed engineering mode I'm surprised you were able to update OOS and maintain the exploit. Why don't you just unlock your bootloader and root the proper way? Your phone won't melt if you do.
I would like to avoid wiping if possible. I too am surprised at the persistence of root after at least 3 OTAs. At this point I no longer really need root and would rather my phone run smoothly without some applications crashing or not running due to root.
bump?
gbesh said:
bump?
Click to expand...
Click to collapse
As long as your system boots, and you have root, install the latest magisk manager from the magisk thread, and it will prompt you to update. As long as you give magisk manager root access you should be able to do a "direct install" and reboot and should be up to date. Back up your data first though, I'm not responsible for your data loss (but this worked for me)
Same to unroot. Magisk has an uninstall option that should fully unroot you
manor7777 said:
As long as your system boots, and you have root, install the latest magisk manager from the magisk thread, and it will prompt you to update. As long as you give magisk manager root access you should be able to do a "direct install" and reboot and should be up to date. Back up your data first though, I'm not responsible for your data loss (but this worked for me)
Same to unroot. Magisk has an uninstall option that should fully unroot you
Click to expand...
Click to collapse
Well my system doesn't boot with root. I have to manually mount something and start the magisk service.
Which is why I'm not sure how to update as I've been told the updated version has a different file structure that the one I'm on.
were you able to unroot? i think i am in the same boot right now, on 4.5.13 with magisk root by engineermode, if you were successful please tell me how
yohouse2 said:
were you able to unroot? i think i am in the same boot right now, on 4.5.13 with magisk root by engineermode, if you were successful please tell me how
Click to expand...
Click to collapse
no unfortunately i am still waiting for a solution.
gbesh said:
no unfortunately i am still waiting for a solution.
Click to expand...
Click to collapse
When I ran out of options,I unlocked the bootloader (wiped the device), and the new system was unrooted, i then installed Nolimits rom based on OOS 5.1.2
I asked on another thread and another user told me that if you accepted the complete zip update of the OTA prompt the updated system would lose the root, but you wouldn't lose your data or apps, which is nice, but keep in mind you are more probable to have worse performance or battery than clean install
yohouse2 said:
When I ran out of options,I unlocked the bootloader (wiped the device), and the new system was unrooted, i then installed Nolimits rom based on OOS 5.1.2
I asked on another thread and another user told me that if you accepted the complete zip update of the OTA prompt the updated system would lose the root, but you wouldn't lose your data or apps, which is nice, but keep in mind you are more probable to have worse performance or battery than clean install
Click to expand...
Click to collapse
I can confirm this is not the case, i have been updating as the updates roll out and i am now on 5.1.2 and still able to get root access through adb with a locked bootloader.
gbesh said:
I can confirm this is not the case, i have been updating as the updates roll out and i am now on 5.1.2 and still able to get root access through adb with a locked bootloader.
Click to expand...
Click to collapse
Well the alternative is another thing i read but can't find, and honestly can't recommend unless you find in too, is that you can delete the apk and the magisk image(don't know which one, this is how bad i remember this), then rebooting would remove the root.
yohouse2 said:
Well the alternative is another thing i read but can't find, and honestly can't recommend unless you find in too, is that you can delete the apk and the magisk image(don't know which one, this is how bad i remember this), then rebooting would remove the root.
Click to expand...
Click to collapse
After one of the recent updates, magisk hide started working again and my apps are no longer crashing. It is strange but i guess this situation has turned out favourably after all.