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 All,
I had obtained root via CF-Autoroot and was using it with xposed for the last few weeks without issues. I took the lunge and tried to install phh super su, magisk systemless root. so the nightmare begins for me and i'm hoping it's an easy fix!
My system is still encrypted (I believe because TWRP can't see the system) SD card is fine. I've wiped my device a few times already and am hoping I don't need to wipe it again(prior to this setup).... So currently it's running fine without root access (How I hate android without root!!!)
- I've tried flashing Supersu zip in TWRP and it's failed - I believe it's not supported yet for encrypted devices.
-I've tried using the original CF-Autoroot method I used initially.
Both methods, it boots up straight away (no optimising apps) and after installing supersu app from playstore, it says no binaries found.
What are some ways I can inject root without wiping my device?
Please help me! Thankyou!
Maybe go back to the start and flash original FW through Odin and start from scratch, so you have a fresh phone to work with.
dwarfer66 said:
Maybe go back to the start and flash original FW through Odin and start from scratch, so you have a fresh phone to work with.
Click to expand...
Click to collapse
That's my plan when I get home tonight. I want to flash the original firmware file my phone started with (I'm assuming it won't delete anything?) and then run through the root steps again.. if it doesn't work, I'll wipe my phone and make sure I get rid of encryption this time..
kevinwu128 said:
That's my plan when I get home tonight. I want to flash the original firmware file my phone started with (I'm assuming it won't delete anything?) and then run through the root steps again.. if it doesn't work, I'll wipe my phone and make sure I get rid of encryption this time..
Click to expand...
Click to collapse
I think you will only lose stuff if you do a system reset after installing the original FW.
I only have had to do that on my tab S not my Edge after coming from a custom rom as I got slow down.
Resolved: flashed original rom and obtained root with cf-autoroot.
If someone has detailed instructions for magisk systemless root and xposed, it'd be much appreciated.. i want to have the option to use android pay or play pokemon go if i wanted. Thankyou
I want to root my phone, and I haven't been doing that kind of stuff since S3 so I'm a bit lost.
I've read the thread about root by Chainfire. From what I understand, this can be used for a phone with Android 6.01, right? On the other hand, I've read about a systemless root. Can this be done with my phone model and this Android version?
My main concern is the warranty. I know the first solution will trip the knox. What about the latter? Would this be better in my situation?
(And a minor question: my phone has found a software update. Should I do it before or after rooting my phone, or does it matter at all?)
for me and it can be different for other users, i have a preference for system root.
if you just want a stable root on your phone, and don't care about passing google security checks (safetynet) you should choose chainfires supersu. just download the latest zip (assuming you already have a custom recovery) and flash it. supersu will "decide" which rooting method (system/systemless) fits to your phone.
The more advanced method is magisk-root which gives you no option for system-root. the whole magisk concept is based on systemless changes to the system partition. it gives you the opportunity to pass safetynet and to add systemless modules. the downside is, that the usability (due to it's complexity) can sometimes be a bit tricky (trial and error )
hope this helped for your decision..
BTW: afaik is knox triggered with both methods
drei.liter.milch said:
if you just want a stable root on your phone, and don't care about passing google security checks (safetynet) you should choose chainfires supersu. just download the latest zip (assuming you already have a custom recovery) and flash it. supersu will "decide" which rooting method (system/systemless) fits to your phone.
The more advanced method is magisk-root which gives you no option for system-root. the whole magisk concept is based on systemless changes to the system partition. it gives you the opportunity to pass safetynet and to add systemless modules. the downside is, that the usability (due to it's complexity) can sometimes be a bit tricky (trial and error )
hope this helped for your decision..
BTW: afaik is knox triggered with both methods
Click to expand...
Click to collapse
To add something: if supersu installs in systemless mode you can bypass it.
Flash the supersu zip
Reboot
Go to supersu and select full root wipe
Click no when asked to restore boot image
Your phone will automatically reboot don't let it go to system, go to recovery
With twrp go to terminal and enter this command without quotes "echo SYSTEMLESS=false>>/data/.supersu
Reinstall supersu zip
Reboot
You yave system root :good:
Sent from my Samsung Galaxy S5 Neo using XDA Labs
Thanks for your replies! I do not care about safetynet. I do care about warranty but from what I see, there is no way around this.
Would you update phone's software first?
Joanka said:
Thanks for your replies! I do not care about safetynet. I do care about warranty but from what I see, there is no way around this.
Would you update phone's software first?
Click to expand...
Click to collapse
Yeah update your system first and if you need warranty just full wipe root and select yes for biit image restore from supersu let us know if it works for you and don't hesitate to ask if you need anything
Sent from my Samsung Galaxy S5 Neo using XDA Labs
Thanks for your help! I'm updating the sofware right now and I will proceed with the root.
"just full wipe root and select yes for biit image restore from supersu" -I think I'm not sure what it means. Would you explain it a little bit more?
Joanka said:
Thanks for your help! I'm updating the sofware right now and I will proceed with the root.
"just full wipe root and select yes for biit image restore from supersu" -I think I'm not sure what it means. Would you explain it a little bit more?
Click to expand...
Click to collapse
Yes, click full unroot and click yes for boot image restore but no for recovery restore
Sent from my Samsung Galaxy S5 Neo using XDA Labs
I have mine (S5 Neo G903W) rooted and as far as I can tell if you want your warranty you can unroot it anytime
The phone provider however doesn't state anything about rooting or whatnot and I am not a type of person who does stupid stuff that needs a warranty anyway lol
For warranty they can check knox status, if is tripped usually is void
Hey all,
After my rooting experience with marshmallow, I used that with 7.1.1 and have had no issues. MODS: This was my approach to rooting 7.1.1. I apologize in advance for creating this thread if it's not necessary yet since XDA has given me so much help, I'm returning the favor.
NOTE: for those that want to roast me on this thread and/or flame me, don't do it. We are all noobs at one point or another. I have provided no links but have supplied the filename to the best in my capacity.
XDA gang,
After numerous attempts to root nougat, I tried this approach. This was the same approach I took w/ marshmallow.
I used Odin3_v3.12.3
selected 7.1.1 – look for filename j700tuvu3bqi5 NOTE: uncheck auto reboot. I do\did because in my experience, I encountered a boot loop.
after odin processes the flash, I disconnected the usb cable and did a battery pull.
Boot up your phone and let your phone build the recovery. After your phone reboots after the recovery, do a battery pull when the samsung splash screen starts to display itself.
Enter stock recovery and perform a cache, dalvik, and factory reset. Reboot from recovery.
Do a battery pull when the samsung splash screen starts to display itself. Boot back into download mode while holding volume down, home button, and power button. Let go of the buttons when the download mode screen comes up.
Use odin again and click on the AP button – select twrp_3.0.3-1_sm-j700t_23217. I found and downloaded this from XDA. Click start on odin and let odin do it thing. Disconnect the usb cable and do a battery pull.
Enter twrp recovery while holding volume up, home button and power button. Release buttons when twrp comes up.
Here, you will need to flash the latest supersu. I used v2.82-SR5. Also download no-verity-no-encrypt-ashyx.zip (big ups to ashyx for creating this)
Install these 2 files and reboot. NOTE: your phone will reboot twice – no cause for alarm.
After your phone boots up into nougat, go through the setup and reboot your phone.
After doing all of this, I've had zero issues. It may seem arduous but I found it necessary for my goal.
Did you have any issues with unlock screen lag on pin;/pattern?
There are reports and my own experience with this on a 7.0.0 version of otherwise identical process as yours to root. conclusion seems to be the no-verity-no-encrypt patch causes this, and that this patch (or something functionally identical) is integrated into supersu 2.82 versions.
edit - what model phone did you do this one? 7.1.1 not available for the j730g yet, unfortunately.
im on a320y , i got my phone suddenly custom binary blocked by frp lock,
then i reflash 7.0 stock firmware, i forgot how i rooted my device at the first time.
now im done with all the things, already rooted, but now im facing the unlock lag (especially when u are on secure lockscreen ex.pattern, password, etc)
this is very annoying, because there is no problem with unlocking screen when using fingerprint.
leo31 said:
im on a320y , i got my phone suddenly custom binary blocked by frp lock,
then i reflash 7.0 stock firmware, i forgot how i rooted my device at the first time.
now im done with all the things, already rooted, but now im facing the unlock lag (especially when u are on secure lockscreen ex.pattern, password, etc)
this is very annoying, because there is no problem with unlocking screen when using fingerprint.
Click to expand...
Click to collapse
caveat emptor, your results may differ drastically from mine, brick device, etc. but I did find a way around this
https://forum.xda-developers.com/apps/supersu/supersu-2-82-nougat-pin-pattern-unlock-t3764305
the issue is removing forced encryption, as far as the pattern unlock lag goes.
i have done this repeatedly on the a520f now and on a j730g/ds as well
DullPeon said:
caveat emptor, your results may differ drastically from mine, brick device, etc. but I did find a way around this
https://forum.xda-developers.com/apps/supersu/supersu-2-82-nougat-pin-pattern-unlock-t3764305
the issue is removing forced encryption, as far as the pattern unlock lag goes.
i have done this repeatedly on the a520f now and on a j730g/ds as well
Click to expand...
Click to collapse
can i flash the newest su while im still rooted? i mean, i dont want to reflash the whole rom again and again via odin.
and my superuser is from magisk manager. will it crash my system?
leo31 said:
can i flash the newest su while im still rooted? i mean, i dont want to reflash the whole rom again and again via odin.
and my superuser is from magisk manager. will it crash my system?
Click to expand...
Click to collapse
U should please educate yourself on what u got going on here..just some advice cuz......
SuperSu is SuperSU, either system wide root or systemless root.
Magisk is magisk, systemless root.
Seems like u rooted your device with SuperSu first, then installed magisk just a heads up SuperSu is obsolete now..and u do not need both. Use one or the other.. No matter, though, I would first make a nandroid backup. Next, I would go into SuperSu and select full system unroot. Next, reboot.go back to your magisk manager,it will say your device is not rooted. download and install through magisk, the magisk16.0 zip. Then it will do it's thing and install magisk and you will be rooted with magisk and have your root manager and magisk module manager. Magisk is like having SuperSu and Xposed all in one. So that's why I say to say goodbye to SuperSu and go all in with magisk. U can learn more that way too.
If u do not want magisk as root, I can't ponder why u wouldn't....just uninstall it. Then download whatever the latest SuperSu zip is. Boot to recovery and flash it. If there is any other updates no that magisk is gone, it will automatically update u with a notification and say yes to update SU binary. That's all.you are prob not getting it cuz magisk is in there too. So, u do not need that mess and remember to always make nandroid backups in twrp before anything where u may screw stuff up. I hope this helps and make sure to find out everything about anything with Android, before u do it.. good luck.
fullofhell said:
U should please educate yourself on what u got going on here..just some advice cuz......
SuperSu is SuperSU, either system wide root or systemless root.
Magisk is magisk, systemless root.
Seems like u rooted your device with SuperSu first, then installed magisk just a heads up SuperSu is obsolete now..and u do not need both. Use one or the other.. No matter, though, I would first make a nandroid backup. Next, I would go into SuperSu and select full system unroot. Next, reboot.go back to your magisk manager,it will say your device is not rooted. download and install through magisk, the magisk16.0 zip. Then it will do it's thing and install magisk and you will be rooted with magisk and have your root manager and magisk module manager. Magisk is like having SuperSu and Xposed all in one. So that's why I say to say goodbye to SuperSu and go all in with magisk. U can learn more that way too.
If u do not want magisk as root, I can't ponder why u wouldn't....just uninstall it. Then download whatever the latest SuperSu zip is. Boot to recovery and flash it. If there is any other updates no that magisk is gone, it will automatically update u with a notification and say yes to update SU binary. That's all.you are prob not getting it cuz magisk is in there too. So, u do not need that mess and remember to always make nandroid backups in twrp before anything where u may screw stuff up. I hope this helps and make sure to find out everything about anything with Android, before u do it.. good luck.
Click to expand...
Click to collapse
this is cool. your answer is helping me a lot. since i forgot how i rooted this device, i think i will remove my magisk manager first.
and i will see if my root is still working or not. if my device still rooted, so i will straightly flash newer SU.
but if it wont work, so i have to flash the newer SU too, right?
leo31 said:
this is cool. your answer is helping me a lot. since i forgot how i rooted this device, i think i will remove my magisk manager first.
and i will see if my root is still working or not. if my device still rooted, so i will straightly flash newer SU.
but if it wont work, so i have to flash the newer SU too, right?
Click to expand...
Click to collapse
Couple things buddy,
If u aren't rooted with magisk, which your magisk manager says rooted with magisk or rooted with SuperSu, uninstall magisk, then flash latest SuperSu zip.make sure to make backups in twrp.that is critical or u will be in bad shape if something goes wrong.and until u are better acquainted with Android , something very well may go wrong. If u are J700T, or J700T1 be sure to always flash the encryption break zip( no verity) which is posted on the ashyx twrp page.after flashing anything.always. there are more instructions under the j700t threads just click on any of our roms.make a nandroid in twrp first, that's a backup.then reboot. if u flashed SuperSu first u are rooted with it . So once uninstall magisk reboot, then u can just see if SuperSu app is functioning properly and shows root access granted on specific apps. Then go to recovery/twrp and flash latest SuperSu then encryption break zip(no verity). If u never did this before, chances are u never formatted after root or installing twrp and have to lose everything. After installing root or twrp u were supposed to go to twrp, wipe, format, "type yes" then flash root and encryption break zip, then reboot and set up phone. U can tell easily if in twrp it doesn't allow u to mount "data" and are unable to make a nandroid. If so don't bother with messing with anything root related till u format your phone, not factory reset, u select format, then type yes. Then flash SuperSu, and the encryption break zip. Once u do that re setup your phone. Then boot back to recovery and make a backup. That will flush magisk manger right out.
Sorry I know that's a lot but please read the j700T T1 threads. First pages of roms explain all this. Figure out if u have made nandroids and can even mount data first. Let me know what that status is. Then I can better help.
If u have done backups and flashed the encryption break zip before then follow above instructions and get rid of magisk or supersu.(this one is easy too, select full unroot) then leave magisk manager alone, go into it and select install magisk, it does it for u. Reboot after each system change. Then u will be rooted with magisk which is the current norm. SuperSu isn't what it once was the Creator retired and it's not anything special. Magisk is the future man. Good luck I hope this helps you.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
U don't have to flash only SuperSu to have root.magisk also roots your device, way better too
fullofhell said:
Couple things buddy,
If u aren't rooted with magisk, which your magisk manager says rooted with magisk or rooted with SuperSu, uninstall magisk, then flash latest SuperSu zip.make sure to make backups in twrp.that is critical or u will be in bad shape if something goes wrong.and until u are better acquainted with Android , something very well may go wrong. If u are J700T, or J700T1 be sure to always flash the encryption break zip( no verity) which is posted on the ashyx twrp page.after flashing anything.always. there are more instructions under the j700t threads just click on any of our roms.make a nandroid in twrp first, that's a backup.then reboot. if u flashed SuperSu first u are rooted with it . So once uninstall magisk reboot, then u can just see if SuperSu app is functioning properly and shows root access granted on specific apps. Then go to recovery/twrp and flash latest SuperSu then encryption break zip(no verity). If u never did this before, chances are u never formatted after root or installing twrp and have to lose everything. After installing root or twrp u were supposed to go to twrp, wipe, format, "type yes" then flash root and encryption break zip, then reboot and set up phone. U can tell easily if in twrp it doesn't allow u to mount "data" and are unable to make a nandroid. If so don't bother with messing with anything root related till u format your phone, not factory reset, u select format, then type yes. Then flash SuperSu, and the encryption break zip. Once u do that re setup your phone. Then boot back to recovery and make a backup. That will flush magisk manger right out.
Sorry I know that's a lot but please read the j700T T1 threads. First pages of roms explain all this. Figure out if u have made nandroids and can even mount data first. Let me know what that status is. Then I can better help.
If u have done backups and flashed the encryption break zip before then follow above instructions and get rid of magisk or supersu.(this one is easy too, select full unroot) then leave magisk manager alone, go into it and select install magisk, it does it for u. Reboot after each system change. Then u will be rooted with magisk which is the current norm. SuperSu isn't what it once was the Creator retired and it's not anything special. Magisk is the future man. Good luck I hope this helps you.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
U don't have to flash only SuperSu to have root.magisk also roots your device, way better too
Click to expand...
Click to collapse
i think the lag while unlocking screen is caused by dm-verity.zip file which i flashed straightly after installing twrp.
leo31 said:
i think the lag while unlocking screen is caused by dm-verity.zip file which i flashed straightly after installing twrp.
Click to expand...
Click to collapse
No, that same dm verity zip has been used since marshmallow and the unlock lag is a nougat bug. All that zip does is disable encryption so u can access data. And thus allow mounting of internal.
fullofhell said:
No, that same dm verity zip has been used since marshmallow and the unlock lag is a nougat bug. All that zip does is disable encryption so u can access data. And thus allow mounting of internal.
Click to expand...
Click to collapse
this is the 2nd time i root my device.
the first time i rooted my a3, i didn't face any lag and never laggy while unlocking screen.
but the problem is i forgot how i rooted it. which files did i flashed. which tutorial did i follow.
but no problem so far , because the fingerprint unlock does not give any lag.
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.