So I did the "temp un-root" in Voodoo OTA Rootkeeper before updating to the new OTA build. The update was successful. I then went back to Voodoo and restored root access. It confirmed that I had root. I then went to SuperSU and it seemed to be working fine as well. TiBu also seemed to be working fine.
I then went to ES File Explorer, which I confirmed had been granted root access, and tried to rename the PowerOn.ogg file in order to stop the AT&T bootup sound. The rename did not work, but no error message. Out of curiosity I then tried to cut and paste that file up one directory and it told me it failed due to insufficient privileges. Does this mean something is wrong with my root?
It reminds me of a time on my Galaxy S3 when I did the exact same process with Voodoo and an OTA update...and everything seemed to be working fine...but when I was testing out the then newly released Carbon backup app, it failed to get proper root access every time until I finally just re-rooted the device.
I can't understand why I am having issues, but everything is reporting that I have proper root access. I even downloaded Root Checker and it confirmed my root access.
Any thoughts? Thanks!
The new es is a pain...you have to go to menu then tools then root explorer then mount r/w then check the rw side next to /system in order to write to anything in /system
Have to do it every time you start es
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Related
Hoping for some help because I've ran into some really odd issues with SuperUser/root on my TF101.
I used the guide in the Dev Forum and flashed to Prime 1.4, everything was great and working well. I made a Nandroid of my base to fall back on.
ChainsDD updated SuperUser on 6/10 or 6/11 and I accepted the update from the market. When I launched SU, I was prompted to update the Binary, I granted SU root access and it said it completed. However, since then, no app that requires root has requested SU according to the log and Kernel Manager is telling me I don't have root.
If I open Terminal Emulator, it is automatically at a # rather than a $
In Root Explorer, tapping the Mount R/W button changes to R/O and I was able to successfully create and delete a test folder in /system
I need to get SuperUser functioning again, any thoughts or ideas?
What's a TF104 model device?
Um. you do know that # in terminal emulator indicates that the app currently has root access?
Open superuser, its being recognized as permanent root because you allowed it to have root access.
And its TF101 not TF104.
Sorry, misread the model...
I know the # means root that's why the title is kinda lost root...
I'm not getting any of the notifications that SuperUser granted access, like I used to. Also, Kernel Manager isn't being granted Root access when I launch it
I think the SuperUser binary update failed, I got the binary from goo-inside.me and flashed it from CWM. Then I cleared the SuperUser app data and launched it. I was again prompted to update the binary version. It failed and prompted me to to flash a zip that it downloaded to my SD card. That zip is a 0kb file.
Try downloading superuser from the market.
david279 said:
Try downloading superuser from the market.
Click to expand...
Click to collapse
Same results
Also, Superuser is now randomly Force Closing on launch.
Talked with ChainsDD, it's a problem with how he compiled Super User for honeycomb. Fix will be released tomorrow.
Sent from my gginggerfied EVO
Fixed binary has been posted to goo-inside.me
Sent from my gginggerfied EVO
My girlfriend has an S4 that I rooted and bootloader unlocked when she got it. This is her first Android phone - finally got her off the iPhone!! I want to block the OTA so I can still have my own fun with it. I know I could use an app, e.g., titanium backup or some other app, to freeze the OTA. But she just switched banks and doesn't have a card yet in order to purchase apps through the play store and I havent found an app that will do it for free.
Wondering if I can just rename the apks responsible for pushing the OTA with a root level access file manager without screwing anything up??
Saw somewhere to freezeI, I think: AT&Tupdate, FWupdate, and LocalFOTA.apk's.
Also saw on ScottsROMS site to rename: wssyncmldm.apk
Can I just rename all of these to '.......apk.bak' without any problem? What ones do I actually need to do something to??
Just run a custom ROM. I'm sure they all have the OTA update disabled.
How to Block OTA
Prerequisites
Must be rooted!
Must have a root level file manager. I prefer ES File Explorer
Instuctions
Start root explorer app
Mount /system as read/write
Navigate to /system/app/
Rename wssyncmldm.apk -> wssyncmldm.apk.bak
Reboot
[CREDIT: http://forum.xda-developers.com/showthread.php?t=2268946 and scrosler]
Normally this would be fixed by editing platform.xml in /etc/permissions, but if I try to edit that file I get an error that says the entire filesystem is read-only. The app has already been granted root access, so I'm not sure if this is an issue with root, or perhaps there's something else I'm missing.
I followed the instructions in this thread to upgrade to 5.1.1, then I installed WanamLite from this thread.
Any pointers?
Have your re-root your device?
5.1.1 is a bit problematic to ROOT.
5.1.1 Stock ROM uses secure kernel that causing bootloop when you root it.
Use a permissive kernel to successfully root your device.
Edit:
Your first step (Stock ROM) is not rooted.
I suspected there could be an issue with the root, yeah.
I downloaded a root checker and it says it is rooted fine. For every other purpose it seems to work as expected (editing /etc/hosts to prevent ads works fine, for instance), just not for editing platform.xml.
I had a problem like this problem last week when I moved on to 5.1.1. I was getting a pop-up that said this folder is not writable, when trying to set my folder from the sd card.
Try sdfix by nextapp
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.
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.