Thunderbolt: after rooting, I can run root manager, flash thunderbolt cwm, boot into cwm and backup/etc. However, when I try to run TiBackup or Screen Resolution, or even terminal/su - access denied, device not rooted.
Anyone else experiencing this?
EDIT: read in another thread (search was not working when I posted this originally) to go to problems in TiBackup, then update busybox...
Go into rom manager. Download SU and flash it in clockwork. Should fix ya.
Sent from my ADR6400L using XDA Premium App
ethanwinkley said:
Thunderbolt: after rooting, I can run root manager, flash thunderbolt cwm, boot into cwm and backup/etc. However, when I try to run TiBackup or Screen Resolution, or even terminal/su - access denied, device not rooted.
Anyone else experiencing this?
EDIT: read in another thread (search was not working when I posted this originally) to go to problems in TiBackup, then update busybox...
Click to expand...
Click to collapse
You could search market for busybox and install busybox and install busybox 1.18.3 then try
Just click Problems? in the bottom right of Titanium and let it install busybox for you. I was able to do that and restore all my apps.
Seems like you solved it for you, but for future reference for others, if you're having issues with Titanium only, it could be a the busybox problem, but if other root apps give issues (like Root Explorer can't mount /system as r/w), then the issue is with su or SuperUser not being installed properly.
I had to reboot twice after rooting before SuperUser apk got the notification requests to allow Titanium and RE to get su rights. After that, no problems.
In a nutshell, if you're not getting the SuperUser pop-up request on apps the first time you run them, your su isn't working right yet.
Delete please.
Related
I rooted my Zoom wifi long ago. Flashed all the various Tiamat kernels and followed bigrushdog's 3.1 update with no problems. I recently flashed the CWR RC 4 over the updated 4.0.1 version in Rom Manager. I now see that all my apps requiring root don't work. I have Super user app but don't get the request to grant su anymore. I tried upgrading Super user within the app but it fails and writes a zip update to SD card which is supposed to be flashed through Recovery but doesn't (I suspect because the file is a 0 byte file!).
Any suggestions on how to get root back?
[Solved]: Seems it was a result of trying to upgrade Superuser that I lost root. See the last post below and the solution Almighty1 offers. It worked and I have root back......
Sent from my Xoom using XDA Premium App
tangiers said:
I rooted my Zoom wifi long ago. Flashed all the various Tiamat kernels and followed bigrushdog's 3.1 update with no problems. I recently flashed the CWR RC 4 over the updated 4.0.1 version in Rom Manager. I now see that all my apps requiring root don't work. I have Super user app but don't get the request to grant su anymore. I tried upgrading Super user within the app but it fails and writes a zip update to SD card which is supposed to be flashed through Recovery but doesn't (I suspect because the file is a 0 byte file!).
Any suggestions on how to get root back?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
There is a problem with the latest recovery version in Rom Manager. The recovery from solarnz is probably not at fault, but maybe the interaction of the two. You wil lneed someone with more knowledge than me to help you get root back, but this issue really needs attention. There are several updates to apps that seem to be breaking our Xooms, and there should be pinned warnings or the developers should be making everyone aware of these conflicts as soon as they find out. I had problems and I'm sure a lot of other folks have have problems with these incompatible app updates as well.
Thanks for that. It almost seems like Superuser is "degrading" in the sense that I had a number of apps reflected in the Superuser app as having been granted root (but not Rom Manager). However, I couldn't add new apps to it. And when I cleared Superuser data and reinstalled it, none of the apps that required root (and which had worked before) would work.
I also think that the writing of a 0 byte zip update file by the Superuser app indicates a problem.
I suspect the solution may lie with fastboot and re-pushing Superuser and CHMOD(?) file permissions but like you, I am nervous to play with these sort of things. My Xoom is working and until I have the need to change the ROM, root doesn't matter to me....
after reading this I checked and also had lost root. I had not checked after after flashing 4.0 in rom manger. Superuser was still there but my apps did not have access. I tried flash a new recovery, reflashing Tiamat nether worked. Anyway from adb
adb remount
adb push su /system/bin/
adb shell
chmod 4755 /system/bin/su
exit
adb push Superuser.apk /system/app/
I then rebooted and had root... updated Superuser as I had an older one in my platform-tools and all is well I then flashed the lastest recovery in rom manger and still have root.
Hope this helps
Thanks. I will give it a try this evening when I get back from work.
Also found this: http://forum.xda-developers.com/showpost.php?p=14643716&postcount=340 which seems similar to your solution.
This is why I hate CWR. I wish we had Amon RA recovery.
Please excuse me if this has been covered elsewhere but I have done a search and can't find anything that applies to my Transformer or the problem I have.
I used Razorclaw to root my Transformer when it was on Honeycomb, and Voodoo OTA rootkeeper to retain it when I upgraded to a later version of HC. And then again when the first ICS update came out. However when the .17 OTA came out, in my haste to try and fix the problems that came with the first ICS update, I hit 'install' without thinking. I should have made sure voodoo had a fresh backup and temporarily unrooted the TF (as I had done on previous updates).
So after the update I checked with both Titanium Backup and Voodoo which indicated I did not have root. I selected the 'restore root' option in Voodoo and it then indicated I had regained root access.
So now the three apps that I had granted root access prior to the upgrade (Titanium Backup, ES File Explorer and Voodoo) still have root access, but whenever I try a new app that requires root it says I don't have root. And checking in Superuser the 3 apps above are listed as allowed, but no other requests are even logged.
So my question is how can I have some apps that require root working, yet new requests are denied? And is there a simple way to fix it? I don't want to uninstall Superuser in case that loses me root completely (and permanently) and when I try to update Superuser it fails to gain su and stops.
Edit:TF is running Stock firmware, just rooted.
Look to see if you SU in system/xbin if not look in system/bin and copy SU from there to system/xbin
baseballfanz said:
Look to see if you SU in system/xbin if not look in system/bin and copy SU from there to system/xbin
Click to expand...
Click to collapse
This did not fix it I'm afraid, but thank you for your suggestion. It's almost like Superuser is frozen and won't allow anything else root access. I see there is a 'Superuser Update Fixer' App on the Market (oops I mean Google Play Store) but I'm not sure if that will solve the problem I have as it seems to require root access to work...
dingbatt said:
This did not fix it I'm afraid, but thank you for your suggestion. It's almost like Superuser is frozen and won't allow anything else root access. I see there is a 'Superuser Update Fixer' App on the Market (oops I mean Google Play Store) but I'm not sure if that will solve the problem I have as it seems to require root access to work...
Click to expand...
Click to collapse
Try running ViperMod (option 1) again to get full root.
dingbatt said:
This did not fix it I'm afraid, but thank you for your suggestion. It's almost like Superuser is frozen and won't allow anything else root access. I see there is a 'Superuser Update Fixer' App on the Market (oops I mean Google Play Store) but I'm not sure if that will solve the problem I have as it seems to require root access to work...
Click to expand...
Click to collapse
I don't think you have root. I had same thing happen, literally almost exactly and its because I did not have proper root. Use vipermod to get root back and you'll see everything will work like normal
Sent from my Transformer TF101 using xda premium
Thank you both baseballfanz and eminembdg (I pushed the thanks button) Vipermod Option 1 did the trick. I now have full root access restored. The biggest problem I had was I couldn't find any Win7-64 ADB drivers so had to go and pull the old Win7-32 laptop out to get everything to work properly.
Still can't see why I had partial root permissions though. I thought it was all or nothing. Kind of like being a bit pregnant.
DISCLAIMER: I am NOT RESPONSIBLE on anything that will happen on your device such as getting bricked or malfunctioning. I only posted this little trick I found out to help others who are also in the same boat. This method MAY or MAY NOT WORK on your device, so proceed at your own risk.
=====================================
Maybe some of you have not seen any Superuser prompt that appears whenever you run apps that needs root (example are Link2SD, Titanium Backup) and etc. Out of frustration last night, I tried to find a way to fix this and I have indeed found it.
But before that here are some of the prerequisites needed:
-Phone/Tablet must be ROOTED
-Has access to system using File Explorers such as Mi(UI) File Explorer, Root Explorer and other explorer that DO NOT prompts Superuser. What I mean here is that you can see /data, /mnt, /etc folders and the like.
..and here are the little steps in fixing it:
1. Download and install BusyBox from Google Play Store.
2. Open BusyBox, select 1.20.2.
3. Click install, and wait for it and it's done.
4. After BusyBox has been installed, download SuperSU from Play Store.
5. Install and let it load.
6. After loading, press YES when asked to update SU Binary.
7. When it's done, press back and try apps that needs root like Titanium Backup.
And there, notification prompt would appear again!
NOTE: UNINSTALL, take note UNINSTALL previous Superuser app through Root Uninstaller. Main reason why that should be uninstalled so that there would be no conflicts with the SU app.
OPTIONAL: you MAY UNINSTALL BusyBox app but I recommend not so to avoid any problems.
I have also applied this method to my tablet that's already rooted but doesn't have Superuser app yet. A simple press of thanks is highly appreciated. :3
hey, I've been trying and trying again but still can't... what should I do? root explorer cant fix my problem.. superSU, superuser fixer, it can't fix my problem too.
ellynepain said:
hey, I've been trying and trying again but still can't... what should I do? root explorer cant fix my problem.. superSU, superuser fixer, it can't fix my problem too.
Click to expand...
Click to collapse
It's not working for me neither, i can't fix this superuse thing
Hey,
A few days ago, my Superuser app stopped granting root access, and now it crashes ranodmly.
I know I'm not the first one and I read many things about it but everything I tried was unsuccessful.
I tried to update the Superuser app but it needs root access at the end of the process.
I checked if my phone was still rooted with a "Check Root" app and it's still rooted.
I tried to install BusyBox, but it needs root access.
I tried to uninstall the Superuser app and the re-install it but since it's a default app included with my ROM I can't uninstall it.
I have a Galaxy Appolo running with Kyrillos 9.7.
Does anyone know how I can fix this ?
Superuser app is being reported to have issues at some point. Try Chainfire's SuperSU app, and see if that works.
If that too didn't work, maybe your root permissions have been messed up, not sure though.
coolsandie said:
Superuser app is being reported to have issues at some point. Try Chainfire's SuperSU app, and see if that works.
If that too didn't work, maybe your root permissions have been messed up, not sure though.
Click to expand...
Click to collapse
I installed it, but when I launch it it tells me to update the SU binaries. I tried to do it but the process just seems to take forever, so I suppose it's not working.
Gangstalin said:
I installed it, but when I launch it it tells me to update the SU binaries. I tried to do it but the process just seems to take forever, so I suppose it's not working.
Click to expand...
Click to collapse
Then I guess there are problems with your root permissions maybe. Try other Superuser app just to confirm it, and if needed re-install your ROM as a last resort.
Gangstalin said:
I installed it, but when I launch it it tells me to update the SU binaries. I tried to do it but the process just seems to take forever, so I suppose it's not working.
Click to expand...
Click to collapse
Try a custom rom with pre rooted busybox and suprer su
If it doesnot work unroot ur phone and root again
This should fix ur problem:thumbup:
HIT THANKS IF I HELPED
Sent from my GT-S7500
I'll start out by saying I'm a total noob at this whole android rooting process, hence why I'm posting a thread here rather than posting a reply in the appropriate thread. I rooted and unlocked my phone using this guide: http://forum.xda-developers.com/showthread.php?t=1762709&nocache=1
I opted for the "flashing rooted stock ROM" option.
As the title of my post states, after installing CM10.1, I open superuser to update binary and everything appears to work fine until the very end, it reads "making sure new su works...fail!". Now when I restore back to rooted TW, I have no problem updating the su binary. I've tried Superuser update fixer, I've installed busybox; i cant find any other solution on Google. Any ideas?
The CM file I downloaded is: cm-10.1-20130714-NIGHTLY-d2vzw.zip
Gapps file is: gapps-jb-20130301-signed.zip
Liam1987 said:
I'll start out by saying I'm a total noob at this whole android rooting process, hence why I'm posting a thread here rather than posting a reply in the appropriate thread. I rooted and unlocked my phone using this guide: http://forum.xda-developers.com/showthread.php?t=1762709&nocache=1
I opted for the "flashing rooted stock ROM" option.
As the title of my post states, after installing CM10.1, I open superuser to update binary and everything appears to work fine until the very end, it reads "making sure new su works...fail!". Now when I restore back to rooted TW, I have no problem updating the su binary. I've tried Superuser update fixer, I've installed busybox; i cant find any other solution on Google. Any ideas?
The CM file I downloaded is: cm-10.1-20130714-NIGHTLY-d2vzw.zip
Gapps file is: gapps-jb-20130301-signed.zip
Click to expand...
Click to collapse
Make sure your using the latest version of the Superuser app, another option would be to try using SuperSU as an alternative to the Superuser app. Also is root access functioning normally for you?
Sent from my SCH-I535 using xda premium
Hi and thanks for the reply.
Yes superuser is up to date and I've tried supersu. Root seems to be functioning as I can open apps that require root access.
But when I try to restore missing apps via titanium backup, I get a msg saying "restore finished, 'x' elements failed". X being the number of apps I try to restore
Sent from my SCH-I535 using xda app-developers app
Check to see if the root apps are granted root access.
chevyowner said:
Check to see if the root apps are granted root access.
Click to expand...
Click to collapse
When I open SuperSU, it has a list of apps with superuser status. Is that what you mean? I can run root apps and as far as I can tell they're functioning, with the exception of when I try restoring apps with Titanium Backup
Also, right after I flashed CM10.1, I made a backup right away. Not sure if it means anything, but If I wipe/reset and restore the CM10.1 backup, and the first thing I do is try updating the binary in Superuser, it reads "checking installed version: 9 com.Android.Settings", until I open SuperSU and "update binary". Then if I go to Superuser, it'll say "checking installed version: 1.41:Superuser" as I imagine it should. But at this point I still run into "making sure new su works..fail!"
Superuser has no problem updating when I'm on my rooted stock. I'm sure I messed up somewhere along the way while flashing CM10.1, I just don't know where