Whenever I try to make a backup with CMW, it gives me an error that says "An error occurred while attempting to run privileged commands"
How do I fix it?
You have S-Off?
estallings15 said:
You have S-Off?
Click to expand...
Click to collapse
Yep fully rooted and everything. It worked before but not sure why it's not working now.
HTC~TwikiE said:
Yep fully rooted and everything. It worked before but not sure why it's not working now.
Click to expand...
Click to collapse
Try reflashing your recovery. Sounds like it's borked.
estallings15 said:
Try reflashing your recovery. Sounds like it's borked.
Click to expand...
Click to collapse
I just tried that and it gives me "An error occurred while downloading your recovery."
How do I do it manually?
HTC~TwikiE said:
I just tried that and it gives me "An error occurred while downloading your recovery."
How do I do it manually?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1242901
estallings15 said:
http://forum.xda-developers.com/showthread.php?t=1242901
Click to expand...
Click to collapse
Just tried that, back to square one. Same error
HTC~TwikiE said:
Just tried that, back to square one. Same error
Click to expand...
Click to collapse
Hmm, I'm getting worried that this may be a hardware problem. Does anybody have any ideas?
estallings15 said:
Hmm, I'm getting worried that this may be a hardware problem. Does anybody have any ideas?
Click to expand...
Click to collapse
The error isn't necessarily hardware; that message could be occurring because of a software problem with the su application that is being used.
- Have you been flashing/nandroiding successfully with CWM in the past?
- Were your su binaries updated recently?
- Did the ROM get an OTA recently that might have updated the su binaries?
- Was this failed backup being done after/before flashing a ROM that wasn't full-wiped?
- EDIT: Why of course you have S-off and anyone who asked after you said so would be a silly fellow.
If all else were to fail, I'd suggest going back to a stock ROM and re-rerooting, and I imagine that your problems would 'go away'. I'm not sure what intermediate methods you could try, though, unless you wanted to try to run your backup commands over adb or re-push your su binaries or .apk.
tuxkamen said:
The error isn't necessarily hardware; that message could be occurring because of a software problem with the su application that is being used.
- Have you been flashing/nandroiding successfully with CWM in the past?
- Were your su binaries updated recently?
- Did the ROM get an OTA recently that might have updated the su binaries?
- Was this failed backup being done after/before flashing a ROM that wasn't full-wiped?
- Do you have S-off?
If all else were to fail, I'd suggest going back to a stock ROM and re-rerooting, and I imagine that your problems would 'go away'. I'm not sure what intermediate methods you could try, though, unless you wanted to try to run your backup commands over adb or re-push your su binaries or .apk.
Click to expand...
Click to collapse
I was under the impression that your recovery didn't need the SU binary to do it's job. The SU binary is used within Android, right?
Edit: Also, he already said that he has S-Off. If you're going to offer help, please pay attention.
I had the same error show up recently. I just went around it and did a backup while in boot recovery.
... now... what to do if that starts to fail... Hmm
Sent from my myTouch 4g using xda app
estallings15 said:
I was under the impression that your recovery didn't need the SU binary to do it's job. The SU binary is used within Android, right?
Click to expand...
Click to collapse
I'm referring to both the Superuser.apk and the general su/busybox binaries (that got installed as part of his rooting process) which I think get used when doing the calls to make backups to your SD card. He's most likely getting the message because either his rooting method has gone awry or whatever his phone thinks is the appropriate way to get elevated privileges is no longer able to do that. The possible causes for that pretty much boil down to either permissions needing fixing or needing to redo the installation of the su "stuff".
I'm not sure how that would _happen_. This goes back to knowing what happened recently to the phone from a software perspective (any new ROM flash lately, potentially to something that doesn't have root perms?). He was able to reinstall CWM, but he may need to re-push the su/busybox stuff in order to get back to full functionality (and maybe do it a few times, just like in the initial rooting process, to make sure it 'sticks').
Edit: Also, he already said that he has S-Off. If you're going to offer help, please pay attention.
Click to expand...
Click to collapse
I'm not sure why I wrote that. I did notice he said it, said 'meh' and wrote it down anyway. -_-
tuxkamen said:
I'm referring to both the Superuser.apk and the general su/busybox binaries (that got installed as part of his rooting process) which I think get used when doing the calls to make backups to your SD card. He's most likely getting the message because either his rooting method has gone awry or whatever his phone thinks is the appropriate way to get elevated privileges is no longer able to do that. The possible causes for that pretty much boil down to either permissions needing fixing or needing to redo the installation of the su "stuff".
I'm not sure how that would _happen_. This goes back to knowing what happened recently to the phone from a software perspective (any new ROM flash lately, potentially to something that doesn't have root perms?). He was able to reinstall CWM, but he may need to re-push the su/busybox stuff in order to get back to full functionality (and maybe do it a few times, just like in the initial rooting process, to make sure it 'sticks').
I'm not sure why I wrote that. I did notice he said it, said 'meh' and wrote it down anyway. -_-
Click to expand...
Click to collapse
No offense, but I'm fairly positive you can perform all the functions in recovery with a completely wiped system partition. If that is the case, then that theory is debunked. S-Off should give you all access/permissions you need. This is why I said that I'm worried about his hardware. If his bootloader was HTC dev unlocked, then I would say he needed S-Off.
estallings15 said:
No offense, but I'm fairly positive you can perform all the functions in recovery with a completely wiped system partition. If that is the case, then that theory is debunked. S-Off should give you all access/permissions you need. This is why I said that I'm worried about his hardware. If his bootloader was HTC dev unlocked, then I would say he needed S-Off.
Click to expand...
Click to collapse
The error message he's getting is from trying to start his backup out of ROM Manager, not recovery--that error usually pops up before going into the backup process. You can verify this yourself by temp unrooting in Superuser, launching ROM Manager, and trying to do something like make a backup or fix permissions. I have a feeling TwikiE could do backups by _booting_ into recovery.
That's why I'm suggesting the need to check the Superuser implementation. ROM Manager doesn't think it has either root permission or privileges. If TwikiE isn't seeing the 'you must be rooted' popup when starting ROM Manager, then the phone is rooted but the app doesn't think it's privileged to send the phone into the backup process. If this the first time TwikiE's tried a backup since his last ROM flash, the ROM might have a bad or incompatible set of root tools, or some other app may have been installed that has bad tools. Or maybe it's as simple as having accidentally hit Deny on a Superuser prompt.
Some things TwikiE could do to try and resolve the problem without rerooting could be:
- Try Fix Permissions out of ROM Manager and see if the same error message appears. If it succeeds, try backing up again. If not...
- Check the Superuser app settings to see if ROM Manager is on the list as allowed or denied. If it's on deny, clear it out. If it's allowed or not there, move on.
- Clear out the application data and cache for both the Superuser app and ROM Manager from the apps menu. Try to backup again and see if the superuser prompt appears.
- If that doesn't work, try uninstalling and reinstalling Superuser and ROM Manager from the Play Store, reinstalling both, then try to backup.
Beyond that comes more drastic steps.
tuxkamen said:
The error message he's getting is from trying to start his backup out of ROM Manager, not recovery--that error usually pops up before going into the backup process. You can verify this yourself by temp unrooting in Superuser, launching ROM Manager, and trying to do something like make a backup or fix permissions. I have a feeling TwikiE could do backups by _booting_ into recovery.
That's why I'm suggesting the need to check the Superuser implementation. ROM Manager doesn't think it has either root permission or privileges. If TwikiE isn't seeing the 'you must be rooted' popup when starting ROM Manager, then the phone is rooted but the app doesn't think it's privileged to send the phone into the backup process. If this the first time TwikiE's tried a backup since his last ROM flash, the ROM might have a bad or incompatible set of root tools, or some other app may have been installed that has bad tools. Or maybe it's as simple as having accidentally hit Deny on a Superuser prompt.
Some things TwikiE could do to try and resolve the problem without rerooting could be:
- Try Fix Permissions out of ROM Manager and see if the same error message appears. If it succeeds, try backing up again. If not...
- Check the Superuser app settings to see if ROM Manager is on the list as allowed or denied. If it's on deny, clear it out. If it's allowed or not there, move on.
- Clear out the application data and cache for both the Superuser app and ROM Manager from the apps menu. Try to backup again and see if the superuser prompt appears.
- If that doesn't work, try uninstalling and reinstalling Superuser and ROM Manager from the Play Store, reinstalling both, then try to backup.
Beyond that comes more drastic steps.
Click to expand...
Click to collapse
Who does anything in ROM Manager? Damn it, OP, reboot into recovery and do it right.
Heh. I didn't want to put it *exactly* that way...
Sent from my HTC myTouch 4g using xda app-developers app
Related
ok something crashed on my modaco rom. super user wont work when it goes to it it just shows black screen. tried deleting cache on it and data. no fix. cant use tether or anything root.
I'd reapply the ROM or restore from backup.
i cant do that. everytime i do a nandroid backup it messes up cause of apps2sd.
I had a similar problem. I installed the Su app from the marketplace over it then i uninstalled it and it fixed the app. Worked for me.
ok i tried reloading rom and same thing. i cant find the app you are talking about. is it the super user whitelist. i cant install anything root now when it goes to su and you have to allow it all i get is black screen and it force closes
pitmanr2003 said:
ok i tried reloading rom and same thing. i cant find the app you are talking about. is it the super user whitelist. i cant install anything root now when it goes to su and you have to allow it all i get is black screen and it force closes
Click to expand...
Click to collapse
Yes its the Super whitelist app.
try reformatting the ext partition first. Wipe the system than do a system restore or nandroid restore. If you did a nandroid backup of the faulty system than I hope you have the stock nandroid backup as well.
ok tried the super whitelist and it downloads but never installs just sends me back to the sprint flash and restarts. i dont really want to restore back cause then i have to download all my apps again. im seriously thinking that apps2sd are more trouble than they are worth. maybe some one can do a walkthrough on how to back them up in the event of a crash like this.
Same here
pitmanr2003 said:
ok tried the super whitelist and it downloads but never installs just sends me back to the sprint flash and restarts. i dont really want to restore back cause then i have to download all my apps again. im seriously thinking that apps2sd are more trouble than they are worth. maybe some one can do a walkthrough on how to back them up in the event of a crash like this.
Click to expand...
Click to collapse
I can confirm this behavior. I just reinstalled from a backup, installing whitelist from the Market gave me the unending HTC screen of death.
adb push Superuser.apk /system/app/
Superuser.apk can be found in any one of the available ROMs, fresh, gutted, MoDaCo, etc.
pitmanr2003 said:
ok something crashed on my modaco rom. super user wont work when it goes to it it just shows black screen.
Click to expand...
Click to collapse
Turn USB Debugging back on.
posguy99 said:
Turn USB Debugging back on.
Click to expand...
Click to collapse
Oh Snap! TY!
I'm having the same issue. Just in case, I ruu'd back and started over.
Everything works fine up to installing the rom.
Debugging is on.
Tried wiping the ext partion from flash screen, says "error" run wipe_ext via consle"
I tried installing the superuser whitelist app from market, and it won't install, says "incompatible update".
Tried pushing the superuser.apk, it says "failed to copy, read only file system.
Any ideas, i'm lost. I can run my nandroid back to before I installed the 1.2c modaco and it works fine, as soon as I install the rom nothing works in root.
I used SU File Manager & Terminal 3.0.6 to cut/copy/paste Superuser.apk back into the app folder. I then ran it and it installed with no problems and works great for me.
I made sure that I used the built in feature to make the system and data folders RW before I cut/copy/pasted anything. Hope this helps.
hi, and thanks for reading this. If the newest sprint update, DI18?, ever gets released, I am afraid I will not get it. I removed some system apps and I guess the update needs to see those. Thinking I knew what I was doing, here is what I did.
Rooted my Epic.
with titanium i backed up media hub, sprint nav, and nascar. I then removed them.
I saw I needed them so I thought I would restore.
I guess titanium can't restore system apk's?
I start looking for those apk's and only find media hub.
I install media hub, epic says i already have it which i sort of don't really.
media hub is back, and thats where I am at.
I hope that makes sense? I will never use media hub, but I want the epic to be like it was right after root, so I can easily get the next, and future, updates.
thanks
I know someone has posted a link to download all of the stock apps... unfortunately I can't find it! Anyone know where that is?
I personally hate Titanium Backup because I can never figure out what it's doing. The backup function has done the same thing to me - you backup an app, then you think you're deleting the system app and can restore from a backup, but you can't. It's so weird. I would recommend either buying Root Explorer (~$3) or trying out the SDX Stock App Removal (free). You can also use adb push to put the system apps in your /system/app directory. But you still need the apps.
Did you try remounting as rw first?
Sent from my SPH-D700 using XDA App
EDIT: see Firon's post below (#8) it will take care of any modifications you've made as long as you have a stock (odexed) ROM, it won't even mess up recovery or kernel!
thank you all. I will play around with it.
according to titanium everything that was gone is back, except "com.sdgtl.stamhubb" no idea what that is. a google search came back with only a couple hits. Others have removed it, not noticing anything. I do not recall removing that myself.
That's a program name not the APK name... try updating if you're ready and see if it will get past verification... if not see if you can find the APK name and follow the same procedure you did with others.
Here's a signed update that will not trash your recovery, kernel, or root. You do not need a stock kernel for this update.
It will restore only the required stock files/apps and update your modem, so as long as you're on DI07, it should successfully update.
I tested it already on my own phone, worked great.
http://firon.net/xda/SPH-D700-DI07toDI18.signed.zip
This way you don't need to restore a bunch of random files to update.
I appear to be all good. thanks everyone.
Firon said:
Here's a signed update that will not trash your recovery, kernel, or root. You do not need a stock kernel for this update.
It will restore only the required stock files/apps and update your modem, so as long as you're on DI07, it should successfully update.
I tested it already on my own phone, worked great.
snip /SPH-D700-DI07toDI18.signed.zip
This way you don't need to restore a bunch of random files to update.
Click to expand...
Click to collapse
Hello,
The procedure for using this is to copy this to the SD card, rename update.zip, boot into recovery mode, select "apply sdcard:update.zip", correct? Or am I missing a step?
When I attempt this, I get a "E:signature verification failed Installation aborted." error.
Would appreciate any suggestions before I resort to flashing to stock. Thank you!
I am getting a
ben.fg said:
Hello,
The procedure for using this is to copy this to the SD card, rename update.zip, boot into recovery mode, select "apply sdcard:update.zip", correct? Or am I missing a step?
When I attempt this, I get a "E:signature verification failed Installation aborted." error.
Would appreciate any suggestions before I resort to flashing to stock. Thank you!
I am getting a
Click to expand...
Click to collapse
I am also wanting to know how to do this. I got the OTA update yesterday and it failed because I deleted Mail. I would like top know how to manually update to d118 w/out turning my epic into a brick. Any advice would be appreciated.
I believe this requires clockwork recovery not the stock recovery.
Ok so I am really ready to just give up when it comes to Android phones lol. I picked up a MyTouch 4g. I did not receive the update so I decided to do the force update here.
http://forum.xda-developers.com/showthread.php?t=843428
The instructions said to also use the guide to permaroot for s=off...
http://forum.xda-developers.com/showthread.php?t=834225
In settings>about> it still shows 2.2 not 2.2.1 but I have s off, I am using titanium backup and rom manager, with superuser. I deleted stock apps and everything. But for some reason this does not seem right. Shouldnt I be on 2.2.1.
Am I fully rooted or is something else going on. Can someone explain please. I only wanted to root to delete all the bloatware on the phone.
rllong1 said:
Ok so I am really ready to just give up when it comes to Android phones lol. I picked up a MyTouch 4g. I did not receive the update so I decided to do the force update here.
http://forum.xda-developers.com/showthread.php?t=843428
The instructions said to also use the guide to permaroot for s=off...
http://forum.xda-developers.com/showthread.php?t=834225
In settings>about> it still shows 2.2 not 2.2.1 but I have s off, I am using titanium backup and rom manager, with superuser. I deleted stock apps and everything. But for some reason this does not seem right. Shouldnt I be on 2.2.1.
Am I fully rooted or is something else going on. Can someone explain please. I only wanted to root to delete all the bloatware on the phone.
Click to expand...
Click to collapse
Before anyone flames you, this is supposed to be in Q&A section. I hope someone answers this for you. I have no experience forcing an update or I would gladly give you advice. Sorry
21productionz said:
Before anyone flames you, this is supposed to be in Q&A section. I hope someone answers this for you. I have no experience forcing an update or I would gladly give you advice. Sorry
Click to expand...
Click to collapse
Sorry about the placing. I thought since I was combining two topics about rooting, it should have been here. Sorry guys. I dont know who moves these things but feel free to. Sorry again.
rllong1 said:
Ok so I am really ready to just give up when it comes to Android phones lol. I picked up a MyTouch 4g. I did not receive the update so I decided to do the force update here.
http://forum.xda-developers.com/showthread.php?t=843428
The instructions said to also use the guide to permaroot for s=off...
http://forum.xda-developers.com/showthread.php?t=834225
In settings>about> it still shows 2.2 not 2.2.1 but I have s off, I am using titanium backup and rom manager, with superuser. I deleted stock apps and everything. But for some reason this does not seem right. Shouldnt I be on 2.2.1.
Am I fully rooted or is something else going on. Can someone explain please. I only wanted to root to delete all the bloatware on the phone.
Click to expand...
Click to collapse
if you've already removed apps you will have to start over with the downgrading section most likely, but it seems to me like you missed a step somewhere
Ok, I dont know where I am in the process. Like I said, I have apps deleted, superuser, tianium, rom manager. All that. So you suggest starting the downgrade process. Can you send a link please. I am on 2.2 not 2.2.1 and I have s off.
Your best bet is to go back to the force 2.2.1 thread and force the upgrade.
You can check root access in android terminal emulator.
Open it up and type "su" without the quotes. If it come up with the # symbol you have root. If not you don't.
Here is the upgrade thread. http://forum.xda-developers.com/showthread.php?t=843428
jjlean said:
Your best bet is to go back to the force 2.2.1 thread and force the upgrade.
You can check root access in android terminal emulator.
Open it up and type "su" without the quotes. If it come up with the # symbol you have root. If not you don't.
Here is the upgrade thread. http://forum.xda-developers.com/showthread.php?t=843428
Click to expand...
Click to collapse
only problem is he removed apps and the update won't flash if certain apps are missing... but since he used titanium he can try to restore them then flash...
slhpss said:
only problem is he removed apps and the update won't flash if certain apps are missing... but since he used titanium he can try to restore them then flash...
Click to expand...
Click to collapse
Yea, you have to restore all the stock apps from what I heard too.
Typed "su" in terminal. I got the pound sign. So im rooted. But to clarify. In order to force that 2.2.1 update I will need to install all apps again then use the guide to force the update.
There is a stock ota backup on here somewhere, use it to get 2.2.1 if you really are rooted.
Sent from my HTC Glacier using XDA App
rllong1 said:
Typed "su" in terminal. I got the pound sign. So im rooted. But to clarify. In order to force that 2.2.1 update I will need to install all apps again then use the guide to force the update.
Click to expand...
Click to collapse
if you have clockwork recovery installed all you need to flash is the update.zip... BUT if you can't get those apps reinstalled it probably won't work... but that depends on which apps you removed and I don't know for sure which ones matter
What apps are removed? You should be able to adb push them back to your phone then just boot into clockwork and flash the update.zip
EDIT:
Dont give up on Android just yet, this phone is a bit harder to get updated and rooted than most..just takes a bit of patience is all...you'll get it.
couple questions
Ok, I can not use adbs so anything with adb I can not do but thanks. Also How do I get into clockwork recovery? I deleted asphalt 5 game, the demo videos, the tmobile app pack.
Why cant you use adb?
To get into clockwork, you can try using rom manager and selecting boot into recovery or you can power off your phone, pop out your battery for a sec to kill the quick boot then reboot it by holding down the volume down and pushing the power button for a few seconds, release the power while still holding the volume down.
reason for no adb
I use a school pc and thus have no administrator rights to run adb commands. I have rom manager installed but everytime I do the thing that says boot into recovery, it just takes me to a screen with an exclamation point.
Sounds like you dont have clockwork installed.
Go into your rom manager app and select install clockwork recovery
Please post all questions in Q&A section.
Sorry guys.I gave up. I just turned s back on and did a hard reset. Hope I dont get charged. Thanks for everything.
Cheers all, I posted this in the big question thread, but it's just getting buried, so I though it's own thread might bring out a response. Anyway, here's the problem:
Unlocked phone no problemo. But rooting is not going so good. Had to fight to get the latest TWRP loaded (openrecovery-twrp-2.6.0.0-mako). Needed to use this string.
fastboot -c "lge.kcal=0|0|0|x" boot openrecovery-twrp-2.6.0.0-mako.img
Which worked fine and got me into the menu where I flashed the superuser.zip file. That proceeded ok (although the first attempt, when I clicked the box to verify the signature, it failed), and I rebooted. Yet this phone is still not rooted - apps requiring root fail, such as Titanium. But superuser is flashed onto the phone, it's in the app list.
Any ideas? I'll take anything at this point. I don't even care if it's about cellphones. Just tell me something, lol.
saison said:
Cheers all, I posted this in the big question thread, but it's just getting buried, so I though it's own thread might bring out a response. Anyway, here's the problem:
Unlocked phone no problemo. But rooting is not going so good. Had to fight to get the latest TWRP loaded (openrecovery-twrp-2.6.0.0-mako). Needed to use this string.
fastboot -c "lge.kcal=0|0|0|x" boot openrecovery-twrp-2.6.0.0-mako.img
Which worked fine and got me into the menu where I flashed the superuser.zip file. That proceeded ok (although the first attempt, when I clicked the box to verify the signature, it failed), and I rebooted. Yet this phone is still not rooted - apps requiring root fail, such as Titanium. But superuser is flashed onto the phone, it's in the app list.
Any ideas? I'll take anything at this point. I don't even care if it's about cellphones. Just tell me something, lol.
Click to expand...
Click to collapse
I'm not ENTIRELY sure, but from what I've heard 4.3 causes a lot of problems with root and only one superuser app even works. I'm not sure which one, but it's possible you're using a superuser apk that doesn't work on 4.3.
Try going to Developer Mode > Root Access and change it to Apps and ADB.
IDK about the rest but SuperSU works fine on stock 4.3
thanks, will try this stuff out
moffa~ said:
Try going to Developer Mode > Root Access and change it to Apps and ADB.
Click to expand...
Click to collapse
Does not appear to be a Root Access option.
3rdstring said:
IDK about the rest but SuperSU works fine on stock 4.3
Click to expand...
Click to collapse
OK, I've got that copied into the 'sdcard', but should I remove the old superuser app before installing this one? Not sure how to do it, as it won't delete from the apps menu, it will only give me the option to disable.
saison said:
Cheers all, I posted this in the big question thread, but it's just getting buried, so I though it's own thread might bring out a response. Anyway, here's the problem:
Unlocked phone no problemo. But rooting is not going so good. Had to fight to get the latest TWRP loaded (openrecovery-twrp-2.6.0.0-mako). Needed to use this string.
fastboot -c "lge.kcal=0|0|0|x" boot openrecovery-twrp-2.6.0.0-mako.img
Which worked fine and got me into the menu where I flashed the superuser.zip file. That proceeded ok (although the first attempt, when I clicked the box to verify the signature, it failed), and I rebooted. Yet this phone is still not rooted - apps requiring root fail, such as Titanium. But superuser is flashed onto the phone, it's in the app list.
Any ideas? I'll take anything at this point. I don't even care if it's about cellphones. Just tell me something, lol.
Click to expand...
Click to collapse
If you're on a JWR (Stock) ROM, flash this: http://d-h.st/sDt
If you're on a JSS (AOSP) one, flash this: http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
Good luck!
Tanmaynarang said:
If you're on a JWR (Stock) ROM, flash this: http://d-h.st/sDt
If you're on a JSS (AOSP) one, flash this: http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
Good luck!
Click to expand...
Click to collapse
Managed to get it with SuperSU 1.51 as mentioned above. Although I had to do it twice, lol. After flashing and rebooting, I started Titanium, and SU asked if i should grant permission. While thinking about this, the window timed out, and Titanium would not work, nor did the sytem appear rooted, until I reflashed SuperSU and started again. This time, I granted permission for Titanium, and all's well. For now. I guess.:silly:
Yeah for some reason Superuser and 4.3 don't mix very well. SuperSU works fine though, I had to flash it too to get PA 3.92 to work properly. I was really worried that I'd lost all my data since Titanium wasn't working and my CWM backup had failed but ultimately it all worked out.
Hi guys,
I've been trying to get Lollipop running properly on my G900F, but there's a problem with my root access - when I start an app that needs root, it takes too long for the system to answer the reques which again makes the app time out. Obviously, this makes it hard to restore my backup from Titanium, but after I manage to run it after lots of swearing, more than a reasonable number of reboots and a little bit of swearing it will still be too slow to give root when running automatic backups. I've tried autoroot, I tried applying the update zip and I've even managed to lock myself out by causing system ui to hang on boot. I'm on my third wipe now and I figured this won't get better by itself and it's not because of a bad ROM update...
So...could someone please help me with how to fix this?
Cheers!
Titanium still not work with lollipop..
For your su problem, you can go into su app and click on the # (right near the apps) and give them su access
kromic1204 said:
Titanium still not work with lollipop..
For your su problem, you can go into su app and click on the # (right near the apps) and give them su access
Click to expand...
Click to collapse
Thanks for replying I actually went with a pre-rooted ROM which seems to work fine. Giving access manually probably wouldn't have worked as it didn't work after I got titanium into the list and even set the timeout to five minutes :S
tiwas said:
Hi guys,
I've been trying to get Lollipop running properly on my G900F, but there's a problem with my root access - when I start an app that needs root, it takes too long for the system to answer the reques which again makes the app time out. Obviously, this makes it hard to restore my backup from Titanium, but after I manage to run it after lots of swearing, more than a reasonable number of reboots and a little bit of swearing it will still be too slow to give root when running automatic backups. I've tried autoroot, I tried applying the update zip and I've even managed to lock myself out by causing system ui to hang on boot. I'm on my third wipe now and I figured this won't get better by itself and it's not because of a bad ROM update...
So...could someone please help me with how to fix this?
Cheers!
Click to expand...
Click to collapse
Latest version of titanium backup works properly with lollipop. What superuser app do you have? I recommend latest SuperSu zip.
I used the latest SuperSU update file and flashed it through both CWM and TWRP. Must have been something with the image - the one I got now works perfectly both with supersu bundled and if I use the update file.