After updating to I897UCJH7, I can't replace TW_Touch.ogg because it keeps telling me I don't have enough space or some nonsense.
According to SuperUser, my SU Binary is 2.3.1-ef and Superuser is 2.3.6.1.
Anyone else have this problem?I can't alter anything in system.
EDIT: I fixed it by reconstructing the data folder from an clockwork backup.
Related
Here is a Dump from the System Apps for those who accidentally deleted some of them and can't update to OTA2. I deleted some apps, you won't need for OTA2 to make the package smaller.
Remember before updating to OTA2 to protect your superuser by downloading and applying OTA root keeper.
After the update you have to download Superuser then just reactivate root by using ota root keeper.
PW for the archive is:
tptsystemappsdump
When I rooted ,I backup and delete some some flexT9 input file, then I find out I can not recive SMS after root .
So I unroot ,now I get OTA update but it's says error about I miss some flexT9 file.I can not restore file without root.
Now I can never root again ,and I can not even UPDATE OTA because system fille ar change.
What can I do NOW ?
My TPT is rooted (Titanium Backup shows it as rooted and RomManager also) but when I try to reinstall the Browser App it says could not install the app. Also Insallation via adb didn't work.
Can I somehow copy the files manually and what files need to be copied?
Thank you for this, one of our tablets unistalled the lenovo app market while trying to update itself, only want this for the notesmobile update but your dump helped greatly and meant i didn't have to faf about pulling it from my tpt
@Atom2007:
you will have to put the Browser.apk and Browser.odex into /system/apps with i.e. Root Explorer.
delete post
Hey all,
I have rooted my HTC One. SuperSU works, as well as Titanium Backup, etc.
Some issues...
BusyBox will not install, and AdAware properly alters the hosts file, but after a reboot, AdAware is disabled and the hosts file seems unmodified.
I've also noticed that trying to make some applications "system apps" (sys/app) via Titanium Backup, it seems to work, and applications detect as having system permissions, but after a reboot the apps and permissions are gone.
Any ideas?
Thanks!
The system partition is shadowed, writing to it is temporary. For AdAware the fix is to flash a ROM with a symlinked hosts file, perhaps busybox is similar.
BenPope said:
The system partition is shadowed, writing to it is temporary. For AdAware the fix is to flash a ROM with a symlinked hosts file, perhaps busybox is similar.
Click to expand...
Click to collapse
Hmm...
I also noticed this...
I am using a Notification widget called Power Toggles, and one of the buttons is a Shutdown/Restart button. When I click it, and select Shutdown, Restart, Recovery, etc. it fails "because it doesn't have root access." I have given the application root permissions.
What is going on?
I originally wanted to use Lucky Patcher, main reason why I rooted my phone, howeve, it popped out an error message about BusyBox missing from the system (it still kinda sorta worked, but not really). I've tried installing BusyBox with 5 different installers, some say tahat they can't be installed and I should change a direction (even a non-system partition scares them). One app has installed the busybox, but another one can't see it, neither can Lucky Patcher. Also, no means of making /system/ writeable work (special apps, ES File Explorer, Total Commander, File Commander).
Wat the hell should I do to make my BusyBox installation existent, solid and visible? (and also get an actual ability to make that /system/ writeable).
I'm using Sony Xperia Z1 C6903 on Android 4.4.4, build number 14.4.A.0.157
Is ur phone rooted? Cuz busybox installers need root access to write to /system
Tehmask said:
I originally wanted to use Lucky Patcher, main reason why I rooted my phone, howeve, it popped out an error message about BusyBox missing from the system (it still kinda sorta worked, but not really). I've tried installing BusyBox with 5 different installers, some say tahat they can't be installed and I should change a direction (even a non-system partition scares them). One app has installed the busybox, but another one can't see it, neither can Lucky Patcher. Also, no means of making /system/ writeable work (special apps, ES File Explorer, Total Commander, File Commander).
Wat the hell should I do to make my BusyBox installation existent, solid and visible? (and also get an actual ability to make that /system/ writeable).
I'm using Sony Xperia Z1 C6903 on Android 4.4.4, build number 14.4.A.0.157
Click to expand...
Click to collapse
Root is making your device able to write to /system/ ... Probably your device wasn't rooted correctly..Try to download-install an app that checks if your device is rooted...
If it's not try to root again using the latest guides
So I have a rooted stock zv6 android 5.1 sprint lg g4. Root is working fine and so is xposed version 79 sdk 22. I get all su prompts and can grant of deny them. In titanium backup latest version from Google play I also get the root prompt and I grant it, but it still says it doesn't have root access even though I even see the toast message that it has been granted superuser. It says something about not obtaining root using system/bin/su. But using root explorer the su binaries are there I even copied the su from the xbin folder and pasted it into the bin folder tried changing install paths in busy box still didn't solve it. What has me stumped that the prompt to grant superuser permissions comes up with titanium backup, but even granting it does not see it/achieve superuser permissions for whatever reason. Do you guys have any idea on what to try?
Bump
Sent from my VS985 4G using XDA Free mobile app
I had my phone rooted and all working fine on Nougat. I then tried installing secure settings for Tasker and since around this time, i've lost root and if i try flashing super su in TWRP, each time i boot and check i'm not rooted. If i open Super Su app it tells me that the framework needs to be updated and to reboot, i do this and it just keeps telling me the same.
The only thing i am thinking may have broken this is i found a guide to get Secure Settings working on nougat where someone suggested creating a folder with root file explorer called 'su' in system/bin. Now when i open up Titanium Backup it tells me it could not acquire root and say the attempt was made using the "/system/bin/su" command which im thinking means it's looking somewhere there is an empty folder?
I cant now of course delete the system/bin/su folder i created as i cant enable root in File Explorer so i'm pretty stuck and not sure what i can do. I've tried the cleanup and full unroot in the supersu app and then flashing supersu in twrp again but still says no root when i check
Any suggestions?
farquea said:
I had my phone rooted and all working fine on Nougat. I then tried installing secure settings for Tasker and since around this time, i've lost root and if i try flashing super su in TWRP, each time i boot and check i'm not rooted. If i open Super Su app it tells me that the framework needs to be updated and to reboot, i do this and it just keeps telling me the same.
The only thing i am thinking may have broken this is i found a guide to get Secure Settings working on nougat where someone suggested creating a folder with root file explorer called 'su' in system/bin. Now when i open up Titanium Backup it tells me it could not acquire root and say the attempt was made using the "/system/bin/su" command which im thinking means it's looking somewhere there is an empty folder?
I cant now of course delete the system/bin/su folder i created as i cant enable root in File Explorer so i'm pretty stuck and not sure what i can do. I've tried the cleanup and full unroot in the supersu app and then flashing supersu in twrp again but still says no root when i check
Any suggestions?
Click to expand...
Click to collapse
This post was a bit more informative than your "my device unrooted itself" post in the stable thread.
Dirty flash your system or use the file manager in TWRP to remove the offending folder.
I was thinking of trying that but fixed it a different way as I just posted in the SuperSU thread. But in case anyone else ever has this problem...
I fixed my issue. By disabling SuperSU and enabling again from the app settings and it gave me root. I then deleted a created su folder in system/bin that I manually created earlier when trying to get secure settings working.