Related
My device is D6503. I had stock .314 rooted rom with locked bootloader. I updated via OTA to .167 and root remained except system partition write.
For this SuperSu was moved to system partition before update and also Survival mode was swithced on!
Another useful information is that if you do the SD Card fix on .314 it will remain after the update, so still all apps will be able to write on SD.
I was on Hungarian T-mobil .314 fw, unbranded phone.
UPDATE:
If you run the RIC killer from below, you will be able to mount system rw:
RIC killer
You lose no data during the update, even Xposed moduls works like before.
I thought this can be an useful information for everyone, if not moderators can delete the thread.
Which stock 314 firmware did you have before? Canada / USA stock 314 doesn't let you do ota, it forces you to use pcc for the update and you lose root.
bdithug said:
Which stock 314 firmware did you have before? Canada / USA stock 314 doesn't let you do ota, it forces you to use pcc for the update and you lose root.
Click to expand...
Click to collapse
Hungarian T-mobil, but the phone is unbranded. Also it is important to not have custom recovery installed, because then OTA won't install. You can only root if you want to be able to update via OTA in the future.
bojan1986819 said:
Hungarian T-mobil, but the phone is unbranded. Also it is important to not have custom recovery installed, because then OTA won't install. You can only root if you want to be able to update via OTA in the future.
Click to expand...
Click to collapse
Hmm.. So flash a stock 314 fw (Hungarian tmobile confirmed) , root but don't install custom recovery, then do ota and it will preserve root? Can you install a custom recovery afterwards?
bdithug said:
Hmm.. So flash a stock 314 fw (Hungarian tmobile confirmed) , root but don't install custom recovery, then do ota and it will preserve root? Can you install a custom recovery afterwards?
Click to expand...
Click to collapse
I'm not fully sure because you lose system partition write access after the OTA, so this have to be checked by someone. I don't install custom recovery because SD card fix and Xposed is all I need and I want to keep the possibility to use OTA updates in the future. I don't like when I have to reinstall everything and set my preferences again if I want to have a new fw with root, without exploit.
If someone checks this I will add the result to the first post.
Did anyone else duplicate this method?
bojan1986819 said:
I'm not fully sure because you lose system partition write access after the OTA, so this have to be checked by someone. I don't install custom recovery because SD card fix and Xposed is all I need and I want to keep the possibility to use OTA updates in the future. I don't like when I have to reinstall everything and set my preferences again if I want to have a new fw with root, without exploit.
If someone checks this I will add the result to the first post.
Click to expand...
Click to collapse
I did another similar way: created my own personal rooted zip file and flashed. I loosed access to mount system..
Hope someone can fix it.
MichaelWT said:
Did anyone else duplicate this method?
Click to expand...
Click to collapse
Yes someone in the thinktank thread did the same. So it seems like if you can do OTA and switch on Survival mode it works.
Yes you can, but you won't be able to mount r/w system untill devs find a kernel xploit to make it adbd insecure.
hi mates
more information would be of much more help, please :good:
ota marashmellow
I have rooted android 5.1.1, now I got 6.0 ota, can I update, is root preserved or I will lost my root after updating.
do not. two things can do, wait out root 6 and continue with 5.1.1 (root) or OTA update and lose root
I have root all verified and supersu installed correctly & twrp custom recovery. However I tried installing a sound mod but just reboots & nothing. Same with dpi changer.
Is there some file that is somehow protecting any changes to be made even though I have root access?
Many Thanks In advance.
Duncan1982 said:
I have root all verified and supersu installed correctly & twrp custom recovery. However I tried installing a sound mod but just reboots & nothing. Same with dpi changer.
Is there some file that is somehow protecting any changes to be made even though I have root access?
Many Thanks In advance.
Click to expand...
Click to collapse
Maybe install busybox from Ericsson
Thanks I have busy box installed, this is very odd it is like there is a security file blocking everything despite root.
Xblast works as I have the clock centred and circle battery.
I am Experienced in root, and haven't stumbled upon this before.
Was thinking it was 4.4.4 but others are having success.
Hmmmm baffled.
Maybe has something to do with the security settings?
Install if you like the Wanam module and check if Disable Secure storage is disabled.
Thats all i can think about for now.
Nope nothing, even tried changing secure storage value to false and upon hitting save it reboots and nowt.
I give up can't think of anything oh it could be AEA Kernel that perhaps is causing the problem?
The only way to find out if its the kernel you flashed. Re-flash the stock-kernel
Thanks for getting back, Yeh back to stock and same problem. Maybe for some reason only have partial root, can't see that as supersu is there and functional and I have twrp custom recovery. Hmmmmm the mind boggles lol.
Reasonably experienced root user and for the life of me I can't sus what's up.
Tried refreshing the AEA Kernel and it won't even do that now.
Not that it's important, was just after a sound mod & changing the Dpi down to 560. Tried both it won't change.
Some security thing is preventing this but what could it be?
With some 4.4.4 ROMs on the note 2, there were problems with getting "full" root using twrp. I don't know if this is relatedn but the symptoms sound similar. Solution there was to use philz recovery (which isn't an option here), or for some Roms to flash an older version of supersu in twrp and then update after starting. Could be worth a shot.
Did you make sure to open the SuperSU app after rooting and update the binary? Are you SELinux permissive?
If you are having issues, download the recovery version of SuperSU, install it, then make sure to open the app so it updates.
You could also disable SELinux through the build.prop. Having a kernel that is SELinux permissive doesn't matter if you still have everything enabled in the build.prop
Code:
(SELinux disable)
ro.build.selinux=0
(KNOX disable)
ro.config.tima=0
ro.config.knox=0
If none of that has helped, it is recommended you restore to stock and root again, making sure that reactivation lock is disabled before attempting to perform the root portion.
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 am unboxing a new XT1644 - I am going to run the Nougat OTA, after that is done, what is the best root method so that I can get still future OTA's and security patches as they are released? (while remaining rooted)
I plan to keep the phone stock ROM, although I may delete or freeze some bloatware using Link2SD (unless you have a better method to suggest). So I imagine whatever root method will need to be systemless. For flashing software, I will probably just stick with stock recovery or TWRP running via attached Windows 7 computer or else Flashfire.
I am planning to install these apps requiring root:
● AdAway
● Link2SD
● Root Explorer
● SignalCheck Pro
● Trimmer
WTF? said:
I am unboxing a new XT1644 - I am going to run the Nougat OTA, after that is done, what is the best root method so that I can get still future OTA's and security patches as they are released? (while remaining rooted)
I plan to keep the phone stock ROM, although I may delete or freeze some bloatware using Link2SD (unless you have a better method to suggest). So I imagine whatever root method will need to be systemless. For flashing software, I will probably just stick with stock recovery or TWRP running via attached Windows 7 computer or else Flashfire.
I am planning to install these apps requiring root:
● AdAway
● Link2SD
● Root Explorer
● SignalCheck Pro
● Trimmer
Click to expand...
Click to collapse
Unlock your bootloader, which will void warranty.
Flash TWRP to your recovery partition via fastboot
Make sure you boot into TWRP first, then back into system
Install Magisk Manager, then download the latest version of Magisk through the app
Reboot to recovery the BACK UP EVERYTHING
Install the Magisk zip located under /MagiskManager
Reboot to bootloader
Flash stock recovery
Reboot to system
NOTE: If you cannot boot after Magisk is installed, you will need to restore your boot partition from within TWRP.
Personally, I don't think you should root and keep up with OTA, it may brick your system with root. (Never happened to me, I've only seen it happen)
Hit thanks if I helped.
I've got a H870 from Israel with locked bootloader that isn't going to be unlocked (thanks for nothing, LG).
Now I've downgraded it from Pie to Oreo, as the Oreo kernel is vulnerable to CVE-2019-2215; thanks to https://repo.or.cz/cve2019-2215-3.18.git I've got a working su binary that sets SElinux to permissive and gives me a root shell.
I'm looking for a way to integrate this with one of the usual root apps (ideally Magisk), but I'm somewhat at a loss as to how these do their magic, especially in a way that doesn't involve messing with /system (which cannot be mounted r/w and comes from a ramdisk anyway (as far as I understand it).
Does anybody have experience with this? Can Magisk do a systemless install, and can its su be substituted by my own su?
Thanks for any input