problem with mounting /system as rw - Xperia Z2 Q&A, Help & Troubleshooting

hi
I have successfully rooted my z2 but I can't mount the system folder as rw
I tried different methods to mount it by myself, including trying to remount it with es file manager, downloading different apps from google store, trying the script manager
any help

How did you root it?

@egynono I had trouble with root r/w after updating to 314 and rooting with Easy Root. I did a full unroot from the SuperSU app, rebooted, ran Easy Root again and made sure it finished completely, including the "cleaning up" part, rebooted, installed SuperSU from the play store, rebooted, and r/w worked (tested in root explorer). Adaway was also fixed and able to write the host file.
Not sure if all reboots are needed or if it was a fluke but it worked for me. Haven't unlocked the bootloader yet.

daniels7 said:
How did you root it?
Click to expand...
Click to collapse
there is tool called Easy Tool Google It And You Will Know

Try Rootkit Xperia:
http://forum.xda-developers.com/showthread.php?t=2559009&nocache=1
This fixed it for me and works perfectly and quick

irishrally said:
@egynono I had trouble with root r/w after updating to 314 and rooting with Easy Root. I did a full unroot from the SuperSU app, rebooted, ran Easy Root again and made sure it finished completely, including the "cleaning up" part, rebooted, installed SuperSU from the play store, rebooted, and r/w worked (tested in root explorer). Adaway was also fixed and able to write the host file.
Not sure if all reboots are needed or if it was a fluke but it worked for me. Haven't unlocked the bootloader yet.
Click to expand...
Click to collapse
WTH My Phone Got Damage And Does Not Want To Work Its Restarting Non stop

Install the app 'Root Validator' and check whether your phone is perfectly rooted.
Kj

Related

Problem with Root and SU

So, when I rooted I installed SuperSU and uninstalled Superuser.
Went through the steps to from the mod to get all apps into the multi view window. During the move odex services I got stuck in bootloop and had to re-odin the root image file.
Now that everything is set superuser is obviously the file back in charge of handling SU prompts from apps but for some reason it's not accepting/hearing them so anything I install that requires root is crashing.
Attempted clearing the SU data but it didn't help.
Is there anyway to fix this short of flashing back to stock then back to root?
Would mounting the system as writable, deleting SU and then re-flashing the root image fix the problem?
Basically I'm trying to avoid resetting my phone up to get this done.
Hitman3984 said:
So, when I rooted I installed SuperSU and uninstalled Superuser.
Went through the steps to from the mod to get all apps into the multi view window. During the move odex services I got stuck in bootloop and had to re-odin the root image file.
Now that everything is set superuser is obviously the file back in charge of handling SU prompts from apps but for some reason it's not accepting/hearing them so anything I install that requires root is crashing.
Attempted clearing the SU data but it didn't help.
Is there anyway to fix this short of flashing back to stock then back to root?
Would mounting the system as writable, deleting SU and then re-flashing the root image fix the problem?
Basically I'm trying to avoid resetting my phone up to get this done.
Click to expand...
Click to collapse
I thought for sure that SuperSU is what was used in that file but I guess there must be a couple out there? The method I used never installed Superuser...?
EDIT: Nevermind I see that there are 2 different root methods and one uses SuperSU. Sorry
shojus said:
I thought for sure that SuperSU is what was used in that file but I guess there must be a couple out there? The method I used never installed Superuser...?
Click to expand...
Click to collapse
I used the file from imnuts, which used superuser and not supersu.
I went ahead and deleted superuser, xbin/su and am reflashing. hope this fixes the problem.
which worked until the phone randomly rebooted and got stuck in loop..
and it was either sdpeed increase or lbe privacy guard causing it.
jellybean works better with supersu...try the file mrRobinson created...ie the original root image.
droidstyle said:
jellybean works better with supersu...try the file mrRobinson created...ie the original root image.
Click to expand...
Click to collapse
Ive even removed superuser and installed supersu and doing the all apps mod was causing this issue.
I have a feeling it could be because I was renaming the services.odex file before replacing it.
Trying a direct overwrite was causing a non stop bootloop I couldn't get out of 4 seperate occassions.
droidstyle said:
jellybean works better with supersu...try the file mrRobinson created...ie the original root image.
Click to expand...
Click to collapse
100% agree! I have not used Superuser for ages... Far superior imo...
shojus said:
100% agree! I have not used Superuser for ages... Far superior imo...
Click to expand...
Click to collapse
after rooting I feel like the touch screen has lost some sensitivity. not sure if it's just me and the day or I'm just loco.
and what I mean specifically is when flipping through my home screens they like to snap back now and then.

[Q] CleanMaster Root Access Failed

I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
I have been having this same issue on rooted stock gs4. It's temperamental when it comes to root I've noticed. One day I was able to turn it app off of auto start and when I installed a new app it wouldn't let me do it and su says I'm granted
I'm experiencing the same issues. Auto Start Manager is the only feature that has this issue.
Sent from my SPH-L710 using XDA Free mobile app
yoongkc said:
I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
Click to expand...
Click to collapse
I always face this issue also, what I do as a temporary fix is, go to the SuperSU app, then "Forget" Clean Master, open Clean Master and try to disable an app from Auto starting, grant root and the app will be disabled I hope it works for you too
I am glad I am not the only one having this issue. I recently updated an app via the play store and clean master told me it was auto starting. I tried to block it, but it keeps telling me root access failed and to grant it. Well I've granted it root 18 times now and it still says root failed. I have tried everything to get it to work...clear logs, tell superSU to forget clean master, give it global default, etc. Nothing seems to work and it's pissing me off.
Unfortunately this does not work for me.
I have granted root access according to SuperSU Pro however when trying to stop autostarting apps in Clean Master it reminds me to allow access.
I even get a popup massage from SU stating that the app got granted root access.
Whats happening here? Does anyone have a work around?
Deleting Cleanmaster in SuperSU doesnt help. It is always the same unfortunately.
Best Regards
J
I too also have problems with the autostart function in Clean Master on my Optimus Zone II
First of all, if you've root then you shouldn't use clean master. That's so naive.
About the permissions. Even after root your system partition stays in read only mode. I'm guessing this okay. You should check that out first.
Re:Re: [Q] CleanMaster Root Access Failed
Vtrendzzy said:
First of all, if you've root then you shouldn't use clean master. That's so naive.
About the permissions. Even after root your system partition stays in read only mode. I'm guessing this okay. You should check that out first.
Click to expand...
Click to collapse
Ok, (I know Im gunna reget this), but why?, in your option, should Clean Master NOT be used, since it need so many "root" functions in order to work? Ive used it for years. Rooted or no, (mostly rooted), and why do all the "autostart" apks, (ROM Toolbox, Autostarts, Autostart Manager,etc) work just fine. I've tryied it with r-w on system on, sooooo....next...?
DerDoktorEsq said:
Ok, (I know Im gunna reget this), but why?, in your option, should Clean Master NOT be used, since it need so many "root" functions in order to work? Ive used it for years. Rooted or no, (mostly rooted), and why do all the "autostart" apks, (ROM Toolbox, Autostarts, Autostart Manager,etc) work just fine. I've tryied it with r-w on system on, sooooo....next...?
Click to expand...
Click to collapse
I can't argue over this. Best options for you 1. Root Cleaner (high priority) 2. SD Maid Pro (medium priority)
See the difference yourself.
fix?
Has anyone figured out what the issue is here? It worked just fine on cm12 but stock Lilli nope. Root issues for sure it must have something to do with system partition. Has anyone fixed this issue?
dillweedinc said:
Has anyone figured out what the issue is here? It worked just fine on cm12 but stock Lilli nope. Root issues for sure it must have something to do with system partition. Has anyone fixed this issue?
Click to expand...
Click to collapse
Has anyone figured out what the issue is here?²
hey..the main culprit is supersu app
yoongkc said:
I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
Click to expand...
Click to collapse
Clean master is not working on 2.46(I mean the autostart manager) I noticed this yesterday..i flashed a new Rom first it was having Supersu 2.46 version in which CM was not working but after flashing Supersu 2.49 CM is working plus in Google store supersu 2.46 beta is there which won't work...my clean master started working again normally like before after installing SuperSU 2.49...so try flashing or installing supersu 2.49
Link for supersu zip (Flashable zip)
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Clean master root access
wow. cool...,ill try that,
thanx
it's supersu problem
StoneyJSG said:
I am glad I am not the only one having this issue. I recently updated an app via the play store and clean master told me it was auto starting. I tried to block it, but it keeps telling me root access failed and to grant it. Well I've granted it root 18 times now and it still says root failed. I have tried everything to get it to work...clear logs, tell superSU to forget clean master, give it global default, etc. Nothing seems to work and it's pissing me off.
Click to expand...
Click to collapse
Just go thru my above post..it will definitely work..so give it a try... flashing new supersu 2.49 resolved the problem for me.?
Yep its working again. I tried 2.48 cuz somebody said it worked for them, but i had no luck there. 2.49 did the trick, thx for letting us know in the thread.
tycoon78[stoner] said:
Clean master is not working on 2.46(I mean the autostart manager) I noticed this yesterday..i flashed a new Rom first it was having Supersu 2.46 version in which CM was not working but after flashing Supersu 2.49 CM is working plus in Google store supersu 2.46 beta is there which won't work...my clean master started working again normally like before after installing SuperSU 2.49...so try flashing or installing supersu 2.49
Link for supersu zip (Flashable zip)
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Its working for me too.
Thanks tycoon78 for the tip
RE:RE:RE: [Q] CleanMaster Root Access Failed/SuperUser
The new Super SuperUser Apk 2.49 from chainfire, did not work for my CleanMaster blocking apks from autostarting on my little optimus 2....:crying: any other suggestions?
Ahhh! Thank you so much tycoon! It works for me after updating super user!
QUOTE=Alison.Souza;60674697]Its working for me too.
Thanks tycoon78 for the tip [/QUOTE]
DerDoktorEsq said:
The new Super SuperUser Apk 2.49 from chainfire, did not work for my CleanMaster blocking apks from autostarting on my little optimus 2....:crying: any other suggestions?
Click to expand...
Click to collapse
I just rooted my s6 edge and was having the same issue with 2.46. Luckily when I updated to 2.49, I was unable to block the autostartup apps.

SuperSU prompt not appearing for BD and ES File explorer?

I recently updated my Galaxy S5 Sm-G900T to 5.1.1 and rooted it. Using "CF-Auto-Root-kltetmo-kltetmo-smg900t.tar" straight from the website with Odin v10. At first, the prompt appeared for both Battery Doctor and ES Explorer, but then root randomly got removed and so i rerooted it again and now the prompt isn't appearing. It is appearing for all other apps asking for root besides those 2. I used Root Checker to make sure root is working properly, and it seems to be verified and passed. Is there anything i can do? I have tried re-rooting, reinstalling apps, wiping delvic and cache. But no use.
Frankie_Xenon said:
I recently updated my Galaxy S5 Sm-G900T to 5.1.1 and rooted it. Using "CF-Auto-Root-kltetmo-kltetmo-smg900t.tar" straight from the website with Odin v10. At first, the prompt appeared for both Battery Doctor and ES Explorer, but then root randomly got removed and so i rerooted it again and now the prompt isn't appearing. It is appearing for all other apps asking for root besides those 2. I used Root Checker to make sure root is working properly, and it seems to be verified and passed. Is there anything i can do? I have tried re-rooting, reinstalling apps, wiping delvic and cache. But no use.
Click to expand...
Click to collapse
Same problem es explorer is not asking for supersu rights.Use root explorer if u want
dhruvdave said:
Same problem es explorer is not asking for supersu rights.Use root explorer if u want
Click to expand...
Click to collapse
Solved. Flashed 2.65 SuperSu.
SuperSu 2.7.1 is not stable with S5 5.1.1

several apps having issues now on rooted Marshmallow

I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
njaustin123 said:
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
Click to expand...
Click to collapse
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
dimm0k said:
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
Click to expand...
Click to collapse
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
Whenever you do a clean fresh flash Rom at the setup most rooms let you restore all your previous apps from google, no need to go to the play store it does it automatic. If you made a backup just restore the data.
Sent from my LG-H901 using XDA-Developers mobile app
dimm0k said:
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
Click to expand...
Click to collapse
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
I have witnessed this, mainly with Google apps. after restoring the app with data the app would randomly crash... removing the app and installing it from Google fixes it, but I have not experienced this with non-Google apps. I'll keep this in mind the next go around when restoring my stuff.
njaustin123 said:
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
Click to expand...
Click to collapse
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
after doing some research and from my understanding, the bad news is that it looks like it's up to devs to add the feature of writing to the external SD via the Storage Access Framework (SAF). unfortunately it doesn't look like an easy task, as the developer of Tasker mentioned that he won't be implementing this since the number of external SD users are far and few =( and would revisit it if that number changes.
the good news for those of us smart and brave enough to root our devices, this is solvable via editing packages.xml and adding in one line for each app you want to "fix". this is documented here
justice26 said:
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
works fine for me here... are you using stock ROM?
dimm0k said:
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
Click to expand...
Click to collapse
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
njaustin123 said:
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
Click to expand...
Click to collapse
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
dimm0k said:
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
Click to expand...
Click to collapse
OK, so here is it: I was able to mount /system as rw with the terminal emulator in ROM toolbox and then create a dummy file named su. Rebooted the phone, both the apps still fail. I will write to the developers. For the time being, I am OK turning data on/off manually along with using MyProfiles for other things. And for the One Power Guard, I believe freezing many of the T-Mobile and LG junk using Titanium and having SetCPU with a little bit under-clocking have already made the battery better. So I can wait. Am also evaluating Craig's Root Battery App instead of OPG. Thank you anyways.

Asus Zenfone 4: Oreo released

To whom it may concern: Asus software engineers were busy and they released Oreo: https://www.asus.com/de/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
For me I'll wait for some answers about compatibility of TWRP and the possibility to root. At present I run rooted Nougat Version WW_14.1064.1711.96 (TWRP 3.1.1 with Magisk V15.2, XPosed V89 and Gravity Box [N.] V 7.0.6). Never change a running system if you don't feel the urgent need
AP756 said:
To whom it may concern: Asus software engineers were busy and they released Oreo: https://www.asus.com/de/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
For me I'll wait for some answers about compatibility of TWRP and the possibility to root. At present I run rooted Nougat Version WW_14.1064.1711.96 (TWRP 3.1.1 with Magisk V15.2, XPosed V89 and Gravity Box [N.] V 7.0.6). Never change a running system if you don't feel the urgent need
Click to expand...
Click to collapse
Excellent. You use XDA guide to Root and install TWRP? You don't have brick?
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3.
The main problem: ROOT doesn't work. Root check says phone's rooted, and apps request and get root permissions, but in fact there's no one. For example, root uninstaller can't remove any system app. Tried lesser TWRP (3.1.1), tried SuperSU instead of Magisk. SuperSU doesn't even work, says "SU binnary occupied".
Also one problem: WW-15.0405.1712.83 doesn't want install through TWRP, says "no file contexts". But you can install it through stock recovery, it just bypasses this check.
To get stock recovery, you can do the trick: install SuperSU, boot system, open the app and pick "Unroot" option (it will offer you to clear recovery and boot). Now you get stock recovery and can install firmware.
UPD: Was wrong. Root works, but neither Magisk nor SuperSU gives RW permission on system folder. That's the main problem now. Tried updating permissions on system folders manually through file managers (Root Explorer, etc.). Tried updating through terminal: from adb shell and from recovery. Nothing works. Folders are marked RW now, permissions are right, but apps like Root Uninstaller still can't do anything.
Vikindor said:
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3.
The main problem: ROOT doesn't work. Root check says phone's rooted, and apps request and get root permissions, but in fact there's no one. For example, root uninstaller can't remove any system app. Tried lesser TWRP (3.1.1), tried SuperSU instead of Magisk. SuperSU doesn't even work, says "SU binnary occupied".
Also one problem: WW-15.0405.1712.83 doesn't want install through TWRP, says "no file contexts". But you can install it through stock recovery, it just bypasses this check.
To get stock recovery, you can do the trick: install SuperSU, boot system, open the app and pick "Unroot" option (it will offer you to clear recovery and boot). Now you get stock recovery and can install firmware.
UPD: Was wrong. Root works, but neither Magisk nor SuperSU gives RW permission on system folder. That's the main problem now. Tried updating permissions on system folders manually through file managers (Root Explorer, etc.). Tried updating through terminal: from adb shell and from recovery. Nothing works. Folders are marked RW now, permissions are right, but apps like Root Uninstaller still can't do anything.
Click to expand...
Click to collapse
Thanks to shared. You have sucess to make root?
PedroArmindo said:
Thanks to shared. You have sucess to make root?
Click to expand...
Click to collapse
Well, yes. As said at the end of the last message, phone in fact appears to be rooted. I have access to /root folder and apps now ask for super-user permissions.
But some apps, like Root Uninstaller, doesn't work... However you can manually delete unwanted .apk from /system folder, it's possible.
Vikindor said:
Well, yes. As said at the end of the last message, phone in fact appears to be rooted. I have access to /root folder and apps now ask for super-user permissions.
But some apps, like Root Uninstaller, doesn't work... However you can manually delete unwanted .apk from /system folder, it's possible.
Click to expand...
Click to collapse
Could you test if the Titanium Backup app works?
grinna said:
Could you test if the Titanium Backup app works?
Click to expand...
Click to collapse
Checked. Yep, it works.
I'm sorry if this is a noob question, but where can I get TWRP 3.2.1-0?
Vikindor said:
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3. ...
Click to expand...
Click to collapse
lunger said:
I'm sorry if this is a noob question, but where can I get TWRP 3.2.1-0?
Click to expand...
Click to collapse
Hi. Sorry, haven't seen this message.
TWRP: https://twrp.me/
Magisk can be found here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (or in app stores).
Hi,
Can anyone help me with my phone ZE554kL on how to root this or link me to a guide? Thanks in advance.
"Continue reading only if interested what happen."
I've never done this before and I just want to do root because my internal storage was wiped out when I was backing up all my files to PC. Windows explorer stops responding while transferring files then after the not responding issue, my internal storage is empty and when I checked my phone all the files is gone (photos, videos, PDFs).
I tried different android recovery software in windows and everytime i do a scan, i always ending up being asked by the software to root my phone so it can scan through to my internal storage.
Since my files was lost, i never touch my phone since then so nothing will be written on internal storage that could take away the chance of recovering my files.

Categories

Resources