Hello,
I am currently running the H918 model with twrp and full root. Root was successful and the phone is running well. Thanks to all those who put in their time and effort and providing such a quick root capability. Makes the phone even more amazing than it already is.
Unfortunately, I am having an issue with be able to modify system files as I am unable to edit them whatsoever. I have tried using adb and using mount and remount commands but nothing has worked. I was hoping if anybody would be able to assist me with my issue. Thank you.
I've tried reflashing super su and I have busy box installed. Adaway is working properly (only through system less root) and I have been able to hibernate apps through tibu. I still cannot edit any files under /system. Does anyone have any suggestions? Thanks.
use root explorer
Thanks for your response. I've tried many root managers (including root explorer), enabled root permissions, had them successfully granted through supersu and still a no go. I just ran recowvery again and flashed twrp (this time without formatting data) and I am still unable to edit any system files.
Related
I have just rooted my 4.4.4 Xt1028 using KingRoot v 4.5.0 it's not permanent and I can't get xposed to install because of the ro system, My main phone is an xt1028 that was unlocked with sunshine on 4.4.3. However sunshine doesn't support the 4.4.4 so Im at a loss on what to do next. Any suggestions?
Indeed, I've stumbled upon the same thing!
Root goes away after a reboot, but enough to run TitaniumBackup, or a few other apps that want root in order to read the file system.
This is identical to the prior PIE exploit that worked up to 4.4.2 I wonder if there is a way to package this stuff from KingRoot in order not to waste time running it so obviously after each reboot ...
http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623
i got a 2013 Moto G Vzw prepaid that i got back when they were $24.95
been waiting to see if it can be rooted or unlocked to get CM installed or something
i turned it on today, tried the activation bypass and i was able to get into the OS
( pressing next, pull down noticication, then multitask and swype away)
(this device is on KK 4.4.4)
i was able to install and run kingroot 4.5.0 and it gave me some error, BUT it worked successfully anyways....
i can confirm root with titanium and terminal etc...
i have yet to restart it, but my purpose of this is to use it as a gopro remote, or playing ingress or some type of home automation
this should get my by until something else is found
The root is temporary whether or not you reboot. After a while, root stops working and sometimes makes your phone unstable. Everything may start to crash and you'd have to reboot your phone.
Teet1 said:
The root is temporary whether or not you reboot. After a while, root stops working and sometimes makes your phone unstable. Everything may start to crash and you'd have to reboot your phone.
Click to expand...
Click to collapse
This is true, I've seen it too.
What is interesting is that root checker claims that there is /system/xbin/su present by Kingroot. But /system is always read only. ES explorer appears to create files in /system, but if you quit and re-launch, there are no files there.
From shell, I tried to quickly replace KingRoot with SuperSu :
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
This did not work since in shell it claims that the file system is read only.
I wonder how Kingroot manages to maintain the illusion of /system/xbin/su for a while.
There could be a way to authorize SuperSu with Kingroot, and keep the temporary root all the way until a reboot.
I would be so happy to have xposed frameworks at least maybe busybox. my main phone is an xt1028 unlocked but my brothers was already on 4.4.4 that's why I'm so excited about this progress
bibikalka said:
This is true, I've seen it too.
What is interesting is that root checker claims that there is /system/xbin/su present by Kingroot. But /system is always read only. ES explorer appears to create files in /system, but if you quit and re-launch, there are no files there.
From shell, I tried to quickly replace KingRoot with SuperSu :
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
This did not work since in shell it claims that the file system is read only.
I wonder how Kingroot manages to maintain the illusion of /system/xbin/su for a while.
There could be a way to authorize SuperSu with Kingroot, and keep the temporary root all the way until a reboot.
Click to expand...
Click to collapse
If it manages to write into /system, perhaps we can exploit KingRoot to do some more in depth stuff?
Teet1 said:
If it manages to write into /system, perhaps we can exploit KingRoot to do some more in depth stuff?
Click to expand...
Click to collapse
It does not write into /system, it just fools the OS for a short while that somehow "su" was placed into /system/xbin . That's the strange thing about it!
bibikalka said:
It does not write into /system, it just fools the OS for a short while that somehow "su" was placed into /system/xbin . That's the strange thing about it!
Click to expand...
Click to collapse
I read it uses an exploit on the system to gain root or temproot. Maybe we can do the same?
I can't delete any system apps with it anymore, does anybody else have the same problem or even a fix for it?
Working fine on 6.01 for me, Did you try uninstalling and reinstalling it?
I just updated to 6.0.1 myself, rooted using superSU 2.61. I too cannot delete system apps using titanium. I tried to uninstalled and reinstall the app (via playstore) but it didn't help.
I also tried to do the same via the root explorer option in ES file explorer and it didn't work. I tried to toggle the root explorer option in ES, but after I turned it off I couldn't turn it on again. Root checker does say that I have root, and other root apps e.g. adaway, xprivacy still work.
Any help and suggestion is most welcome!
case-sensitive said:
I just updated to 6.0.1 myself, rooted using superSU 2.61. I too cannot delete system apps using titanium. I tried to uninstalled and reinstall the app (via playstore) but it didn't help.
I also tried to do the same via the root explorer option in ES file explorer and it didn't work. I tried to toggle the root explorer option in ES, but after I turned it off I couldn't turn it on again. Root checker does say that I have root, and other root apps e.g. adaway, xprivacy still work.
Any help and suggestion is most welcome!
Click to expand...
Click to collapse
hey guys, "system less root"
That would modify system... Just freeze the apps.
geoff5093 said:
That would modify system... Just freeze the apps.
Click to expand...
Click to collapse
Some people still want to recover the space.
With systemless root you will need to modify the system in TWRP to get titanium and ES working correctly.
It's as simple as going into TWRP and mounting the system R/W.
You then need to open the terminal in the following places:
/system/bin and execute "touch su"
/system/xbin and execute "touch su"
This will create zero byte files for SuperSu to come along and swap/link to on boot so that ES and TiBu can ask for root and get it.
They will then operate as you expect.; with the caveat that you are on your own when you start tinkering and may break something.
tech_head said:
Some people still want to recover the space.
With systemless root you will need to modify the system in TWRP to get titanium and ES working correctly.
It's as simple as going into TWRP and mounting the system R/W.
You then need to open the terminal in the following places:
/system/bin and execute "touch su"
/system/xbin and execute "touch su"
This will create zero byte files for SuperSu to come along and swap/link to on boot so that ES and TiBu can ask for root and get it.
They will then operate as you expect.; with the caveat that you are on your own when you start tinkering and may break something.
Click to expand...
Click to collapse
Pretty sure you lose Android Pay with this method though, just FYI if you care about that.
But if you are running Xposed you broke it anyway. There is a way to get it working.
You will need to remove the empty su files you just created to be able to add cards.
You will need to use a Xposed module to hide modifications to the system so that the device check comes back clean.
It's a pain, but if you want Xposed, TiBu, ES and Android Pay, that is the price.
Sent from my Nexus 6P using Tapatalk
I usually use this app:
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
I'm not on 6.0.1 at the moment so I can't test if it works. Anyone wanna test it out and report back?
WizeGuyDezignz said:
I usually use this app:
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
I'm not on 6.0.1 at the moment so I can't test if it works. Anyone wanna test it out and report back?
Click to expand...
Click to collapse
Doesn't work. Apps restore themselves.
Hey people!
I just got a nexus 7 2012 and i am wanting to mount it in my car. So i wanted to do a few things before that.
I updated to official 5.1.1 via OTA. Everything is STOCK
First step was rooting which SEEMED to work (DID it via WUGS). It installed SU and busybox. Next step was to create my own bootanimation
This is where the issues have started. I can not change permissions or move any files to the system directory even with W/R option turned on
I can delete the files but can not copy files to the directories. I can no change permissions in ANY directory.
I have tried in root explorer mounting r/w ES file explorer R/W ... i tried to install a new busy box and it installs then immediately says "you installed but it seems there is an older version on the system" i can not uninstall busybox. I tried mounting in terminal and it says all partitions are EXT 4. I have tried rerooting. Root check says everything is fine. SU seems to be working fine (it elevates permissions for all the root apps).
But for the life of me it will not copy anything into / or /system. :crying:
Should i just forget it and install another rom, WIPE everything and start again? If ROM which one is the best at the moment (nexus 2012)
After 2-3 hours of messing about... I just TWRP and flashed a different SU and it starting working.
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Cacciu said:
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Click to expand...
Click to collapse
It's been awhile since I used SuperSU so I might be fuzzy: SuperSU has two components, 1) the .zip portion installed from TWRP and 2) the APK. The zip is like "the framework/service/su" part and the APK is the app that just tracks and loads the DB with which apps or services have been granted SU access.
My question is "Which of these did you uninstall?" : OR: Did you uninstall both? Maybe only uninstalling one or the other causes an 'out of sync' condition.
Anyway: This version of SuperSU https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 discussed in that thread has the APK in the .zip file. By definition all TWRP recoveries are rooted and can do what they want to like installing SuperSU.
What happens after you boot seems more likely to be about left-over crud from the APK / DB component, (and I'm guessing here), so if the SuperSU APK is still there, I'd clear it's data entirely, perhaps get rid of it entirely if you can and reinstall the .zip that contains all parts of SuperSU (maybe they all do now) from that link ^^. Make sure that link I gave is the one you want (systemless, etc).
TWRP should've done the heavy lifting during SuperSU install since it's already rooted. If it didn't, then keep the log from TWRP and look over it's install steps during the SuperSU install. Post it here maybe.
Thanks for the answer.
I uninstalled the apk.
I already tried to install the apk directly and also installing it from the zip, and there was either a message like "no root detected" or " root is corrupted".
I also deleted the su folder, uninstalled the apk and reinstalled the zip. But it was always the same: the apk did either say it's not rooted or did not install/show in the apps.
Probably i have to unroot and root it, or do you have any other idea?
TWRP Terminal
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Cacciu said:
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Click to expand...
Click to collapse
You might be out of luck if you deleted the su directory or any other related to binary su code. I'm not sure why you couldn't do a reinstall of the original SuperSU .zip file. You've got that whole 'catch-22' thing going right now.
The only thing I'm wondering about is whether a certain amount of cleanup has to take place before you can just roll SuperSU*.zip over an old mangled version and get it to work. Do you get errors in TWRP when trying to reinstall the entire package?
---------- Post added at 02:48 PM ---------- Previous post was at 02:05 PM ----------
I downloaded this version of SuperSU (which may or may not be what you used, but you of course want the one you used): http://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip
Then I unzipped it and the installer script for not only the binary parts but the apk is here .\SR1-SuperSU-v2.82-SR1-20170608224931\META-INF\com\google\android\updater-binary. (updater-script is a dummy). It's kind of old school and is very easy to understand (the shell script that installs it).
All the files that it pushes onto the SD are easy to find and use, although you have to keep SELinux settings in mind.
It's worth taking a look at if you want to try to rebuild the wrecked version or if you want to just reapply the zip and have a better understanding of any errors it spits out.
Good luck.
I've looked all over and I'm unable to find a solution or even what's stopping me from modifying the /system folder in the root directory. I can remove files from that folder and all of it's subfolders but I'm unable to add any files into that directory. I am rooted on the T-mobile OnePlus 6t that has been converted to the international ROM. I know my root works cause I can perform other root functions. I also cannot modify the /system folder from TWRP either which is really strange to me. Also, when TWRP prompts me to install the app, it just reboots recovery since it's trying to install it as a system app which I can't do for this odd reason I have yet to find out. This issue all of a sudden showed up after an OTA update and re-rooting after. I have tried reinstalling TWRP, Magisk and Oxygen OS itself but the issue persists. I have also tried running "reboot disemmcwp" as root in a terminal window AND using adb but I guess that command no longer works. Any suggestions welcome as this is the last place I can find an answer to this issue.
Edit: found out I'm unable to uninstall system apps for some reason. So the issue isn't space related.
Toilet Clauger said:
I've looked all over and I'm unable to find a solution or even what's stopping me from modifying the /system folder in the root directory. I can remove files from that folder and all of it's subfolders but I'm unable to add any files into that directory. I am rooted on the T-mobile OnePlus 6t that has been converted to the international ROM. I know my root works cause I can perform other root functions. I also cannot modify the /system folder from TWRP either which is really strange to me. Also, when TWRP prompts me to install the app, it just reboots recovery since it's trying to install it as a system app which I can't do for this odd reason I have yet to find out. This issue all of a sudden showed up after an OTA update and re-rooting after. I have tried reinstalling TWRP, Magisk and Oxygen OS itself but the issue persists. I have also tried running "reboot disemmcwp" as root in a terminal window AND using adb but I guess that command no longer works. Any suggestions welcome as this is the last place I can find an answer to this issue.
Click to expand...
Click to collapse
Known issue that in the Newer OxygenOS versions there is no free space in /system. I'd download Solid Explorer and check the Free Space in the Root Directory.
Sent from my OnePlus6T using XDA Labs
Mannan Qamar said:
Known issue that in the Newer OxygenOS versions there is no free space in /system. I'd download Solid Explorer and check the Free Space in the Root Directory.
Click to expand...
Click to collapse
I've thought about that before. I use root explorer and can see there's more space than needed for the files I want to insert. Is there some buffer space needed in there and how much?
Toilet Clauger said:
I've thought about that before. I use root explorer and can see there's more space than needed for the files I want to insert. Is there some buffer space needed in there and how much?
Click to expand...
Click to collapse
Well, if you go to magisk and select core only mode then reboot you will be able to modify system
toolhas4degrees said:
Well, if you go to magisk and select core only mode then reboot you will be able to modify system
Click to expand...
Click to collapse
I was actually able to find the issue. Space was the issue. I guess there's a space buffer needed from what a file explorer says is left and what's actually left. I uninstalled a couple system apps I disable anyway and was able to insert files/apps into system again.
I made space easy I have the new OnePlus camera apk 125mb the old one is 67mb