Database Users

[How-to] root, the more easy way

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.

PHH's Root Disappeared

Hi Guys.
As the title suggests root access suddenly disappeared from my nexus 6p yesterday.
DigitalHigh rom 7.0 was flashed through the latest twrp (3.0.2-2) and everything was running fine. I got the notification that the SU binary is out of date from PHH's SuperUser. Opened it but nothing really happened. So I downloaded superSU and suddenly it prompted me that the device isn't rooted. Being unfamiliar with PHH's SU I decided to flash the latest SuperSu through TWRP but the phone wouldn't boot.
Right now it has been restored to a backup taken just before flashing SuperSU which means everything is running fine and even android pay works however there's no root access. Is there something specific that might have caused this?
Are there any ways to re-gain root?
Haven't gone through the process of a clean flash yet as the phone is needed for work however even if all of that is done the SU binary will still need to be updated. Is there a different method for updating PHH's root?
So far I have tried clearing cache etc. but noting worked.

apostol96t said:
Are there any ways to re-gain root?
Click to expand...
Click to collapse
Phhusson's superuser and SuperSU don't mix. If you're back to booted, but not rooted with Phh, you'll need to either flash one of the Nougat boot images from the nexus/angler folder or the latest superuser.zip (I think the latest is r229) from http://superuser.phh.me

super su

Anyone know why it wont stay

Ssys no batty

Says no binary installed

pbedard said:
Says no binary installed
Click to expand...
Click to collapse
1st, did you flash the SU file? 2nd, what rom are you on?

Yes 5 times 2 im using dev digitals rom im on sprint

pbedard said:
Yes 5 times 2 im using dev digitals rom im on sprint
Click to expand...
Click to collapse
The latest SU File? which is SR3 2.79? if it didnt work try the Unsu.zip file to remove SU and then flash the SU file again. see if that works.

Devdigital help me thanks

pbedard said:
Devdigital help me thanks
Click to expand...
Click to collapse
did you flashed the unsu file then flashed the Su file?

Devdigital tols me replash the rom cause ite not using super su its using majiskSU

pbedard said:
Devdigital tols me replash the rom cause ite not using super su its using majiskSU
Click to expand...
Click to collapse
AAhh i see. Now i know where you are standing at. you are using magisk. But do you have magisksu ? or keep having supersu as main root but magisk installed? . What i mean to say is, when you go into the magisk app, in the 2nd box of the main screen, does it shows supersu as root method? or magisksu? if it is magisksu then you dont need supersu, now, if it does says supersu, then you do have to fix the issue of supersu to unroot by using supersu function and then go directly into recovery mode and flash magisksu once again.

It says majisksu

pbedard said:
It says majisksu
Click to expand...
Click to collapse
then you dont need su (unless you want it). It is because you already have magisksu (which is pretty much doing the same as su). one overrides the other and then one gets thrown out. Usually to install magisk manually, one does as follows:
1) install magisk app from playstore
2) give supersu access (granted to magisk su)
3) use unroot function in supersu
4) flash magisk zip in recovery mode.
Now, there are other methods to achieve magisksu but the point is that maisksu has changed the binary (which is what SuperSU is telling you that you dont have).But that doesnt mean you are not rooted. you are already rooted with magisk and can achieve pretty much anything that you could achieve with supersu. (it will ask you for prompts asking you whether you want to give su access to "x" or "y" app. etc... Now, if you want SuperSU, you could try to flash the magisk uninstaller. Then do the process of rooting that has been specified for your phone. That should return the SU binary to normality . (this assuming you try to unroot and then flash SU back but didnt work)

hey guys bought my ls997 used. has root because i get the flash screen (untrusted)and twrp is installed and working. how do i find out which to flash ? any advantages to use supersu over magisk ?
i installed magisk manager and it states no root found.

Majisk u have to turn root access on majisk works alot better

@pbedard
Did the help @jinkerz9430 gave work for you?

Yws

Lineage * SuperSU * can't update binaries

This is my installation process [last post is OK]
https://forum.xda-developers.com/galaxy-s5/help/wifi-problem-flashed-lineageos-t3576865
Below are screens from CATLOG [not full tho]
If I try to update binaries in TWRP it stops [nothing in TWRP logs about SU], restarts and stops during Lineage loading screen forever.
So I flash ROM again, and SuperSU from TWRP to fix it.
I was reading that after flashing SuperSU - during first restart it should ask me something like "DO you want to keep root" - it doesn't happen.
SuperSU has no apps listed with root access, but root is OK. TitaniumBackup works, but I'm afraid some of the apps doesn't work properly
Now I'm using
lineage-14.1-20170329-nightly-klte-signed.zip
addonsu-ARM-signed_14.1
SM-G900F
Is there a way to have it done?
I remember like trough a fod that once I was setting permissions in Terminal for some files before updating SU? AM I correct?
Thanks for reding

Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.

Saber said:
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Click to expand...
Click to collapse
I have tried to flash everything and indeed only addonsu-ARM-signed_14.1 is working from TWRP level. Although SuperSU from APK is working OK [latest SR4].
So root seems to be fine for browsing into root or TB! is not complaining about root, but I can not update SU binary - I have also updated Lineage to today's nightly - same thing.

I've used an S4 with lineage and flashing supersu doesn't work. ONE app in particular will not work because the su part of lineage (and old cyanogenmod) doesn't cooperate; it needs supersu for some reason. I was originally on Cyanogenmod from about a year ago, and tried flashing supersu and had this very problem, which is why I tried lineage, but lineage doesn't work and I cannot flash supersu either. I can install from the play store, but it won't update the binary; flashing in recovery fails (in both older cyanogenmod and lineage os) at the boot image patcher step.
supersu 2.79 said:
Finding boot image
Boot image: /dev/block/mmcblk0p20
Extracting ramdisk
Decompressing ramdisk
Failure, aborting
Click to expand...
Click to collapse
The only reason I'm having to resort to this is because Samsung has a problem with their s7 screens failing and won't do a recall...so I'm having to use an older phone and trying to setup my rooted apps, all of which work with the standard Cyanogenmod root or lineage+su addon, except for one app.
EDIT:
Ah-ha, system mode may be the solution, but I'm still trying to get it to boot without getting stuck! I haven't tinkered with supersu in well over a year, and I didn't even know there were two methods for it now.
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120

[Q] Successful rooted, but /system is read only?

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