I recently got a Mini, took the system update fresh out of the box since I knew there was a root method for it, and then rooted it.
None of the ad blocking apps work on this phone. I'm thinking that /system is read only, so they can't change whatever file they need to. I've tried rebooting into recovery- just seems to boot normally, but from what I've read, with the previous root method this would set /system to RW. No difference though. Any suggestions? Am I missing something basic?
jjlangen said:
I recently got a Mini, took the system update fresh out of the box since I knew there was a root method for it, and then rooted it.
None of the ad blocking apps work on this phone. I'm thinking that /system is read only, so they can't change whatever file they need to. I've tried rebooting into recovery- just seems to boot normally, but from what I've read, with the previous root method this would set /system to RW. No difference though. Any suggestions? Am I missing something basic?
Click to expand...
Click to collapse
I use adaway and droid mini. It works well. Maybe you didn't root a phone or reboot into recovery
Just ran the tool to disable the /system write protect, reinstalled, and it's working fine now.
Related
Ever since I upgraded to 2.2 I've been having issues with superuser. I always receive the notification when an app requests SU, and SU does list those items as having SU permissions, however - I'm having varying results;
Titanium backup - Can remove non system apps fine, can freeze system apps fine, but if I try to uninstall one (for example, stock MMS) it just hangs, and does nothing (I'm able to press home to get out but the process continues to run until I end it.) The rest of the app appears to function as normal.
Quickboot- works just fine (yet requires superuser)
Root Explorer- I'm able to delete system files but as soon as I refresh the folder where I deleted the app, it's still there. (And yes I'm mounted as R/W)
Flashing through recovery - works just fine, no issues.
So far this is what I've done that I thought would correct the issue;
(Firstly, I tried using superoneclick before PNP came out) Tried attempting with both ways and superoneclick advised that root was a success. After doing so, I still had the issues above.
Lastly, I decided to do a clean start when PNP came out so I went back and re-did the 2.2 leak (with odin) re-did CWM, re-flashed PNP (and a theme) yet I'm still in the same situation.
My question is, is anyone else having this issue?
If i'm the only one I will just try to start over again (this time using the updated leak that includes recovery)
I know Ti Backup had issues with removing system apps. As for root explorer I haven't tried to remove any system apps with it.
___________________________________
Just when you think you have it idiot proof, they come out with a better idiot.
bdemartino said:
Ever since I upgraded to 2.2 I've been having issues with superuser. I always receive the notification when an app requests SU, and SU does list those items as having SU permissions, however - I'm having varying results;
Titanium backup - Can remove non system apps fine, can freeze system apps fine, but if I try to uninstall one (for example, stock MMS) it just hangs, and does nothing (I'm able to press home to get out but the process continues to run until I end it.) The rest of the app appears to function as normal.
Quickboot- works just fine (yet requires superuser)
Root Explorer- I'm able to delete system files but as soon as I refresh the folder where I deleted the app, it's still there. (And yes I'm mounted as R/W)
Flashing through recovery - works just fine, no issues.
So far this is what I've done that I thought would correct the issue;
(Firstly, I tried using superoneclick before PNP came out) Tried attempting with both ways and superoneclick advised that root was a success. After doing so, I still had the issues above.
Lastly, I decided to do a clean start when PNP came out so I went back and re-did the 2.2 leak (with odin) re-did CWM, re-flashed PNP (and a theme) yet I'm still in the same situation.
My question is, is anyone else having this issue?
If i'm the only one I will just try to start over again (this time using the updated leak that includes recovery)
Click to expand...
Click to collapse
Has anyone figured out the deal woth TB? Ive been having the same issues.
nickrl said:
Has anyone figured out the deal woth TB? Ive been having the same issues.
Click to expand...
Click to collapse
Still doesn't work for me to uninstall apps. I just downloaded Uninstaller for Root from the market and it works fine. Do my backups in TB and uninstall from UfR.
akellar said:
Still doesn't work for me to uninstall apps. I just downloaded Uninstaller for Root from the market and it works fine. Do my backups in TB and uninstall from UfR.
Click to expand...
Click to collapse
I updated my root explorer and did a fresh install and it corrected the problem also.
Had same issue with TI, used Uninstaller for root but using pick'n'pack was pretty much the same experience
Dually noted on the uninstallation and reinstall of root explorer...
Okay, so I know i'll probably get chewed out b/c this has probably been asked before but here goes
I am using Huawei Ascend through metro pcs. I updated last night from 2.1 to 2.2. I've rooted using gingerbreak. However NOTHING I do allows me to remove the pre loaded metro crap. I loaded root explorer per someone on heres advice, and mounted it to r/w however when I click the folder to get to the apps it says it is in r/o. It doesn't matter how many times I click it, it will not change to r/w.
I also tried deleting them with titanium back up...but it wont let me.
Those are temporary mounts of RO to RW. I use SUFBS like RE but does more and you can quickly change your system from RO to RW, but when you close the app it goes back to RO.
I was literally just coming back to update this. I figured it out. You have to use Root Explorer 2.16. Once I loaded that it worked fine with 0 problems! Thanks for the response though
Hi,
I rotted my phone on 2.3.5 and followed manual upgrade process to get 2.3.6 and indeed it worked fine with keeping root.
Of late, when ever I run TitaniumBackup it give me warning as
"Your ROM is rooted but SU binary has non-optimal access rights, which may cause problems
Titanium Backup Pro can fix this problem automatically in many cases. Do you want to proceed? "
When I say "Yes. do it", it gives me message as
"Access rights on "SU" binary was succesfully corrected from "0:0:[4755]" to "0:0:6755" " and asks to restart for apply changes.
Once it restarted it didn't seems to apply changes and asks me same question when I re-open TB.
I understand it has something with access rights files but not sure how to fix this. [we moved SU to diff path to keep root, is that causing issues?] Can someone help me.
Thank you.
Did you upgrade to root using adding 'chmod 4755' to mount_ext3.sh ?
Shaliuno said:
Did you upgrade to root using adding 'chmod 4755' to mount_ext3.sh ?
Click to expand...
Click to collapse
I think so, used below method.
go to /system/bin/
open in text editor – mount_ext3.sh
add the 3 following lines to the very bottom
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 4755 /system/app/Superuser.apk
I did used ES File explorer to perform this. I also read posts mentioning the problem because of ES, how ever I performed this earlier even before complaints and never had problem as it stayed Rooted, so left as it is.
I also installed SU updated from market as I had problems with updating SU binaries.
Not sure but that is the problem I guess.
On every start this script is executed and besides its normal function, it also changes permissions to maintain root. Titanium changes these permissions but upon restarting all reverts back.
Strange thing is I also got Titanium and it doesn't say anything.
Or maybe ES Explorer really messed something up, so the root stays but something ese like Titanium doesnt like it
Shaliuno said:
Not sure but that is the problem I guess.
On every start this script is executed and besides its normal function, it also changes permissions to maintain root. Titanium changes these permissions but upon restarting all reverts back.
Strange thing is I also got Titanium and it doesn't say anything.
Or maybe ES Explorer really messed something up, so the root stays but something ese like Titanium doesnt like it
Click to expand...
Click to collapse
That is correct, I still see Superuser and TB says as Root Access OK in first screen. So Root seems fine with all restarts but not the access settings.
As far as ES File explorer, I used that for editing but once I knew its rooted in 2.3.6 I removed root access from ES File explorer.
not sure as this needs to be fixed. TB does have option, so we could mute the notification about access permanently but I kind of like to make sure this isn't causing some other issue.
sazhagianambi said:
That is correct, I still see Superuser and TB says as Root Access OK in first screen. So Root seems fine with all restarts but not the access settings.
As far as ES File explorer, I used that for editing but once I knew its rooted in 2.3.6 I removed root access from ES File explorer.
not sure as this needs to be fixed. TB does have option, so we could mute the notification about access permanently but I kind of like to make sure this isn't causing some other issue.
Click to expand...
Click to collapse
Don't worry about what TB says.... 6755 is a security hole that you do not want to leave open.... I would use something else.... I am a UNIX/Linux guy by trade, so I am telling you that 4755 is what it should be... Use root explorer and ROM manager instead of TB, I have had way to many issues with TB in the past.
Could you tell please what kind of issues you had?
Im using TB for backing up apps+data and freezing stock/old ones I dont use. Dont want to get by suprise if it goes mad
Thank you!
jimbridgman said:
Don't worry about what TB says.... 6755 is a security hole that you do not want to leave open.... I would use something else.... I am a UNIX/Linux guy by trade, so I am telling you that 4755 is what it should be... Use root explorer and ROM manager instead of TB, I have had way to many issues with TB in the past.
Click to expand...
Click to collapse
Thank you Jim for clearing up, may be I should setup ignore warning then.
Shaliuno said:
Could you tell please what kind of issues you had?
Im using TB for backing up apps+data and freezing stock/old ones I dont use. Dont want to get by suprise if it goes mad
Click to expand...
Click to collapse
TB can and has messed up backups, frozen apps come unfrozen at the worst times, it has a minimal busybox, it has broken root before, it is just more of a headache than anything else... there are several apps that will give much better results.
For freezing apps, try modaco's eazy freezy
For backups, use ROM manager, way more successfull, and VERY stable and tested, and the backups it uses are the same that most manufactures deliver in the fxz and updates, since they are saved in img files, and they can be restored from a default recovery if you really are stuck, and can not even get into it on boot...
For busybox, there are two really good ones, I personally use busybox installer from JRummy16, also the one from Stephen (stericson) is really good too, and I have used it, but had an issue with a version several versions ago, and switched.
I am not bashing TB in any way, so no flames, if you like it.... This is just my experience and I have been using android since 1.4-1.5 version, and I have seen a lot of things....
I bought this phone yesterday, Rooted this morning before work, Voodoo backed it up, and updated to the newest update,
Now when I try to Restore root everything looks grand except Superuser says the su binary is not found.
The su binary is located in /system/bin I believe or xbin but none the less its there. some apps can access root while other cannot..
Any Ideas anyone can give me besides rooting once again, Not an option at work.
Thanks in advanced,
If not let me know and Ill Root again once I'm home, Just looking to play on the slow day.
It's been my experience that on this particular phone Voodoo OTA Root Keeper isn't effective. Simply save the SuperSU.zip on your external SD card and reflash via custom recovery after updating..
The only thing simple is the belief in simplicity.
Haven't Bootloader unlocked yet, used the moto2failgo, or how ever it was to root this morning, so this is what it will be once again once I get home, Thanks for the response, Makes my wonder, the only App that continues to function with root access (aside from Voodoo its self) is Titanium Backup, I am wondering if this is because it has its own busybox and i had not install busybox prior to the update, and cannot now due to lost root.
Hi all,
I recently moved from Windows Phone to Android and have been enjoying fiddling with my phone. I rooted the phone using ODIN and CF Auto Root (CF-Auto-Root-herolte-heroltexx-smg930f.tar.md5). I used Titanium Backup to remove a lot of bloatware from my device, but ended up making a mess of things. I then flashed the stock firmware for my Telstra device from Sammobile (G930FXXU1APF2_G930FTEL1APF2_TEL).
Everything seemed fine, but I now cannot use Titanium Backup to integrate updates or move apps to the system partition. I have tried using ES File Explorer and an adb shell to do this also, but with no luck. The apps either do not work, or are installed back into /data/app. It seems to move the apk to /system/app (I can see it there), then removes the app from /data/app and then hangs. If I reboot the phone, the app is uninstalled (but the apk is still in /system/app). I have noticed via /proc/mounts that the /system partition is often mounted RO. Even when I remount RW after TB starts processing it immediately becomes RO.
I have set the TB to use indirect app loading, enabled USB debugging and unknown sources for apps.
Before I reflashed with the stock firmware I was able to move apps to the system partition (I did Gmail and Google Keyboard and they worked well). Could I have stuffed up my firmware flashing? I only used the AP file, not BL/CP/CSC/UMS that were included in the download.
I apologise in advance if I am all over the shop here with my description. I know enough to get myself into trouble but not enough to get out! And yes, first thing I did after flashing was to back everything up so I don't make the mistake again...