EDIT: SOLUTION in in post #19.
________
I'm on stock rooted US998 Oreo firmware with recently re-rooted V30. Before I was using SuperSu with no issues, but this time I'm using Magisk and Titanium Backup says I don't have root. Of course I do and I've given root authority to Titanium Backup in Magisk Manager.
When opening Titanium Backup, I'm getting an error message that my phone is not rooted -- even though I've given Magisk permission to allow Titanium Backup root privileges.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've uninstalled and reinstalled Titanium Backup (one suggestion)
Someone also suggested installing different version of BusyBox. I like Stericson's Busybox, so I installed that (whereas before I was just running pure stock busybox).
Neither action fixed the problem. I can always go back to SuperSu, but anyone else having the same problem?
I am a reluctant Magisk user, I do like SuperSu -- but surely you can use Magisk with Titanium Backup...
It must be the combo of SuperSU and magisk. I just have Magisk 16.4 beta and no issue with Titanium Backup on stock US998 rom. Try a fresh install.
ChazzMatt said:
I'm on stock rooted US998 Oreoo firmware with recently re-rooted V30. Before I was using SuperSu with no issues, but this time I'm using Magisk.
When opening Titanium Backup, I'm getting an error message that my phone is not rooted -- even though I've given Magisk permission to allow Titanium Backup root privileges. I've uninstalled and reinstalled Titanium Backup (one suggestion) Someone also suggested installing different version of BusyBox. I like Stericson's Busybox, so I installed that (whereas before I was just running pure stock busybox).
Neither action fixed the problem. I can always go back to SuperSu, but anyone else having the same problem?
I am a reluctant Magisk user, I do like SuperSu -- but surely you can use Magisk with Titanium Backup...
Click to expand...
Click to collapse
I was the same way..but super su isn't supported anymore . Switched over to magisk recently and titanium backup still works. There is a few steps I had to do first to get it working properly on Oreo. In magisk manager settings select "global" for mount namespace mode. I also had to change preferences in titanium to get it working. Change app processing mode to interactive, restore 1 app, a window will popup, check allow from this source
After you can change back to "auto,direct" app processing mode in titanium and everything should function like usual.
I have had issues with root explorer initially. For some reason it denied permissions for root without asking. Had to go into magisk, select on the upper left corner, superuser, and enable permissions for that app.
Even for me magisk and titanium combo working just fine.
guapinoy said:
It must be the combo of SuperSU and magisk. I just have Magisk 16.4 beta and no issue with Titanium Backup on stock US998 rom. Try a fresh install.
Click to expand...
Click to collapse
For me it was SuperSu that worked fine since January on Nougat on open market LG US998 V30. But now on Oreo, it's Magisk that's not playing nice with Titanium Backup. Magisk 16.4 beta? I'll try that. I was just on Magisk16.
Maybe try restoring unmodified boot.img? Might be super su clashing with magisk. I'm on magisk 16.0 and it's working fine
JWnSC said:
Maybe try restoring unmodified boot.img? Might be super su clashing with magisk. I'm on magisk 16.0 and it's working fine
Click to expand...
Click to collapse
I flashed the full Oreo KDZ so that should have restored the boot image. I of course lost TWRP and root, so now reinstalled TWRP and this time chose Magisk -- which is where I'm running into issues with Titanium Backup.
Nope. 16.4 magisk doesn't work either with my Titanium Backup. Real puzzler.
That is definitely strange. I flashed the full KDZ for Oreo and then rooted with Magisk 16.4 from TWRP and Titanium Backup works fine for me. (It complained briefly about the type of SU I was using but worked fine otherwise).
Did you flash Stericson's BusyBox to system/xbin or use that installs every boot method? I know from experience with my S8+ that TB seemed to prefer it in /xbin for sure. Also are you using TB Pro?
This is the first decide that I have ever used Magisk with and I have to say that I absolutely hate it and systemless root as a whole. I can't get a damn module to install in magisk and have only been able to successfully flash a couple zips in TWRP....it's nuts.
I also could not run Titanium Backup initially...
What worked for me was:
1. Open Termux,
2. type "su" and enter
3. Select once only and Grant permission when the su request popped up
4. Exit Termux
5. Now try running Titanium Backup again, and the su permission popped up. Granted.
(running Magisk 16.0 on H930DS V30+)
YMMV
Working good for me also.
clean install to (unlock bootloader)
install titanium backup
from Backup settings/Backup folder location select "Storage Provider"
make sure it says "Filesystem storage" for using with internal memory.
I initially used an SD card from my old HTC M8 so needed to select "DocumentProvider storage"
both locations worked fine.
petepc said:
I also could not run Titanium Backup initially...
What worked for me was:
1. Open Termux,
2. type "su" and enter
3. Select once only and Grant permission when the su request popped up
4. Exit Termux
5. Now try running Titanium Backup again, and the su permission popped up. Granted.
(running Magisk 16.0 on H930DS V30+)
YMMV
Click to expand...
Click to collapse
Thank you. This will probably be my solution when I have time to mess with it this weekend.
To the others asking, yes I am using Pro. I have used Titanium Backup for years over many devices with -- on both mine and my wife's phones -- and also install it for friends on their phones.
What it's complaining about it is the SU being used. It's not recognizing Magisk's permission for some reason, and this post sounds like the solution. I'll try it this weekend.
The other issue is it's not exactly a clean install -- it's a clone from LG Bridge of my daily V30+ which is not rooted. This other phone I'm installing it on IS rooted, and I'm trying to get all my daily phone apps/settings, etc onto this OTHER V30. I even uninstalled and reinstalled Titanium Backup, but something is still wrong.
Still this solution sounds keen. I'll try it.
Hi, keep checking, it must be something simple.
I can only say its working fine on mine. I have 8.1.0 pro version if that helps.
Hi, what does it show when you click root access on the overview page?
gazzacbr said:
Hi, what does it show when you click root access on the overview page?
Click to expand...
Click to collapse
It says no root detected, yet in Magisk Manager that app specifically has root. I'll mess with it this weekend.
Other people have the same problem so it's not just me with Magisk.
I may have to go back to SuperSu like I had with Nougat.
Working fine on mine also
Sent from my LG-US998 using Tapatalk
TiBu 8.1.0 working just fine with Magisk 16, although I've only tried freezing and uninstalling apps with it. I'm using LS998 firmware and boot.
JWnSC said:
I was the same way..but super su isn't supported anymore . Switched over to magisk recently and titanium backup still works. There is a few steps I had to do first to get it working properly on Oreo.
In magisk manager settings select "global" for mount namespace mode. I also had to change preferences in titanium to get it working. Change app processing mode to interactive, restore 1 app, a window will popup, check allow from this source
After you can change back to "auto,direct" app processing mode in titanium and everything should function like usual.
I have had issues with root explorer initially. For some reason it denied permissions for root without asking. Had to go into magisk, select on the upper left corner, superuser, and enable permissions for that app.
Click to expand...
Click to collapse
Thanks. I also changed to global just now to make sure everything works, but I actually got Titanium Backup to accept root through this suggestion:
Enemyxofxjesus said:
So about the Titanium Backup not recognizing root thing.....not sure if this will work for anyone else, but I uninstalled TB, then also erased its folder in data/data, rebooted and then reinstalled TB and now it works
Click to expand...
Click to collapse
DroidForLife33 said:
That did the trick. Thanks for your post.
Click to expand...
Click to collapse
I just did this too (deleted the data/data folder for Titanium Backup), and now it's working. When I tried root again, I got this notice below -- but I said don't show again. Seems to be working now. I just backed up all my apps.
ChazzMatt said:
Thanks. I also changed to global just now to make sure everything works, but I actually got Titanium Backup to accept root through this suggestion:
I just did this too (deleted the data/data folder for Titanium Backup), and now it's working. When I tried root again, I got this notice below -- but I said don't show again. Seems to be working now. I just backed up all my apps.
Click to expand...
Click to collapse
If this is not working for me what are my options to freeze the update notifications?
I believe I deleted the right things, would you mind sharing the folder locations for both titanium backup folders?
EDIT: messed around in settings of TB, suddenly works, If I can figure out what exactly I did I will share.
Related
Alright, I'm having some issues with root.
Let's backup and give a little context incase it might help in the diagnosis.
I picked up my TB on launch day then I upgraded to the leaked .09 two or three days ago. Last night I decided to root. So I followed the steps in the root thread without any problem. When I rebooted at the end of it all I installed SetCPU and configured the profiles without any problem. I then installed titanium backup and adfree. I ran adfree and cleared the ads without any issues so then I loaded titanium backup and granted it su access however the app said 'failed' to achieve root when it loaded.
I then rebooted the phone. SetCPU failed to get su access, titanium backup failed to get su access. I then downloaded WiFi tether and drocap2 and they failed to get access. So I rebooted again. This time WiFi tehther and drocap2 got acceess and I even took a screenshot with dropcap2 and turned on WiFi tether. Ok, so I'm happy.
Loaded up Titanium backup again, again it failed to achieve root. So I go back to SetCPU and it fails to achieve root as well.
It's almost like there is a time limit on launching apps with root access once the phone boots before it reverts to non-root access.
The phone itself is working fine, I verified S-OFF by booting into recovery. It just doesn't seem root wants to "stick" when the phone is booted.
So I rebooted again just testing a wild theory I had in my head... and everything is working. Apparently, if I load Titanium Backup is blows root up. No idea why... but all other root apps work as long as I don't load Titantium Backup.
Thoughts?
try flashing a new version of busybox via titanium backup worked like a charm for me
Check out Working Superuser for TB Sense
http://forum.xda-developers.com/showthread.php?t=1003088
I don't think setcpu is gonna work without a custom kernel....
Sent from my ADR6400L using XDA App
feedhead said:
Check out Working Superuser for TB Sense
http://forum.xda-developers.com/showthread.php?t=1003088
Click to expand...
Click to collapse
This fixed the issue I was having.
I was having the same issue as the OP but ROM Manager was the app blowing out SU.
Crimton said:
I don't think setcpu is gonna work without a custom kernel....
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
It works ... the stock kernel (and the few variants that are here - which basically just address adb root) have 4 steps from 245 -> 1000, and just a few governors.
I created profiles to ramp it up while charging, and to slow it down when the screen's off.
Works fine...
can't want for HTC to release source and see what the kernel gods make of it
feedhead said:
Check out Working Superuser for TB Sense
http://forum.xda-developers.com/showthread.php?t=1003088
Click to expand...
Click to collapse
I had to download this and install appinstaller... delete my superuser and install this apk just to get rooted but works like a charm
Ok, I updated my su apk with the one attached above and now it prevents Titantium Backup from borking root but Titantium still doesn't work.
I tried uninstalling Titanium and reinstalling and no go... wierd.
I can't use titanium backup anymore, everytime i run the app i get this:
Code:
Error
Sorry, I could not acquire root privileges. This application will *NOT* work!
Please verify that your ROM is rooted and includes Busybox, and try again
This attempt was made using the "/system/xbin/su" command
I'im running HWMOD's rooted firmware, with superuser "installed and updated", and also busybox "installed and updated". there's nothing wrong, but somehow i can't run titanium backup anymore somehow.
what can be the problem be please, i've googled it and i got no solutions whatsoever!
run the app root checker.
Also from someone who has been there, i dont think titanium works with our unit. Our unit has sd1 and sd2 and sd3. Titanium will backup to sd1, which is internal memory, you can see where this is going. I did a titanium backup, then full wipe, and lost everything because it was not backed up onto sd2...
nightanole said:
run the app root checker.
Also from someone who has been there, i dont think titanium works with our unit. Our unit has sd1 and sd2 and sd3. Titanium will backup to sd1, which is internal memory, you can see where this is going. I did a titanium backup, then full wipe, and lost everything because it was not backed up onto sd2...
Click to expand...
Click to collapse
I don't have to run ROOT CHECKER because i have already other root apps and they function flawlessly (SD maid, quick boot, Busybox installer...) but i run the ROOT CHECKER anyway and it says i do have root privileges.
i forgot to mention that i already used Titanium B to backup apps and data, everything was stored on the external sd card. i could also restore. after all this app is for all android devices.
hamdimo said:
I can't use titanium backup anymore, everytime i run the app i get this:
Code:
Error
Sorry, I could not acquire root privileges. This application will *NOT* work!
Please verify that your ROM is rooted and includes Busybox, and try again
This attempt was made using the "/system/xbin/su" command
I'im running HWMOD's rooted firmware, with superuser "installed and updated", and also busybox "installed and updated". there's nothing wrong, but somehow i can't run titanium backup anymore somehow.
what can be the problem be please, i've googled it and i got no solutions whatsoever!
Click to expand...
Click to collapse
Hi
Also running HWMOD's rooted firmware and Titanium Backup works perfectly well or me. I also have an
Advent Vega and I was able to transfer my SD card from it to the Media pad and restore apps from my Titanium
Backup on it to the Media pad.
Stransky
Sent from my VegaCream RC2 using xda premium
Stransky said:
Hi
Also running HWMOD's rooted firmware and Titanium Backup works perfectly well or me. I also have an
Advent Vega and I was able to transfer my SD card from it to the Media pad and restore apps from my Titanium
Backup on it to the Media pad.
Stransky
Sent from my VegaCream RC2 using xda premium
Click to expand...
Click to collapse
that's what makes the app perfect, BACKUP and RESTORE between different android devices.
have you updated superuser? this seems to have been the cause. Titanium Backup was working fine before I updated superuser and error message is the same as yours. currently i'm using MyBackups.
you can check HWMOD's thread for details as somone also has him about this already.
{SOLVED}
ferdz33 said:
have you updated superuser? this seems to have been the cause. Titanium Backup was working fine before I updated superuser and error message is the same as yours. currently i'm using MyBackups.
you can check HWMOD's thread for details as somone also has him about this already.
Click to expand...
Click to collapse
I solved it, the problem is that titaniumbackup is using the "/system/bin/su" command but the SU binaries are actualy installed in "/system/xbin/"
what i did is going to BUSYBOX and from there switching the install location to "/system/xbin/"
i tried "mybackups" but i prefer TB
hamdimo said:
I solved it, the problem is that titaniumbackup is using the "/system/bin/su" command but the SU binaried are actualy installed in "/system/xbin/"
what i did is going to BUSYBOX and from there switching the install location to "/system/xbin/"
i tried "mybackups" but i prefer TB
Click to expand...
Click to collapse
thanks hamdimo! will try your solution when I get home later.
btw, HWMOD just released HWMOD kernel 3.0.42 + custom updates and this issue was also addressed.
ferdz33 said:
thanks hamdimo! will try your solution when I get home later.
btw, HWMOD just released HWMOD kernel 3.0.42 + custom updates and this issue was also addressed.
Click to expand...
Click to collapse
I fear that my hack could led to believe that searching for the "su" binary only in predefined positions is a good thing ...
I still believe applications should gather the correct informations from the PATH environment variable, as good ol' *NIX does.
But as you said it's kind of addressed, let's hope the hack will have a story
These problems arise only if one updates the "Superuser" application past the 3.0.7 (with "su" binary 3.0.3.2).
That one version is the latest one working as expected.
And yes I am a bit sceptical about my own choice of including 3.1.3 instead of the 3.0.7 in my latest update.
The "su" binary executable alone has grown from a mere 22Kb to 380Kb and "apk" has doubled it's size too (1.5Mb).
Related to these changes in "Superuser" several applications does not work any more for many users and upgrades are needed.
The process of getting "root" privileges for any application has turned tremendously slow. From almost immediate to 2/3 secs. each time.
this solution worked for me
Since superuser is working and granting root permissions to other apps (except TB). Using root explorer, I tried renaming the original su file from /system/bin/su and replacing it (copy-paste) with the su file from /system/xbin
Reloaded TB and it worked =)
Actually i have no problem in my 1st install for titanium backup. but soe how i uninstall accidentally. when i reinstall, it prompt memory not enough but i hve abt 3.5 gb left. my fone is rooted S3. can anybody help. tks in advanced...
So I have the HTC Evo 4G LTE and i upgraded to the 3.16 update. Ran QBKING77's root and unlock method and everything worked great, my question is, i was using the phone and ran my backup of titanium and after i did that it said that i lost root access, so i did the twrp recovery (2.4.1) and reset the phone to right after the unlock, i deleted the titanium backup i had and downloaded all my apps and settings again manually, If i use Root checker basic (one with a white background and hashtag with a green checkmark) it says i have root access, if i use Root Checker (with blue android) it says i do not, if i try to use titanium backup it says i do not have root, but every other root program i have works fine and says i have root access, ROM Toolbox Pro works just fine...how do i get Titanium Backup to work???
edit- this is the error i get with titanium backup: sorry, i could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again. This attempt was made using the "/system/xbin/su" command
What rom are you on?? Also you can try to update your su app from within the app or flash the su zip found here
http://forum.xda-developers.com/showthread.php?t=1538053
to see if it will resolve the issue. Also what version of titanium backup are you using? You should have the option to hit the problems button and download a reliable version of busy box from within the titanium backup app. If not and your running a stock rom then download busybox from the play store, install latest ver and see if it helps.
#Root-Hack_Mod*Always=LTE
laie1472 said:
What rom are you on?? Also you can try to update your su app from within the app or flash the su zip found here
http://forum.xda-developers.com/showthread.php?t=1538053
to see if it will resolve the issue. Also what version of titanium backup are you using?
#Root-Hack_Mod*Always=LTE
Click to expand...
Click to collapse
Using the stock ROM, didn't flash anything, Using TB Version 6.01, and SuperuserSU Pro.
tonyevo52 said:
Using the stock ROM, didn't flash anything, Using TB Version 6.01, and SuperuserSU Pro.
Click to expand...
Click to collapse
Have you checked if Super SU is granting titanium backup root access?
Sent from my EVO using xda premium
Download busybox from the play store, run the app and get latest ver of busy box, clear data on tb, reboot, and see if you still get the error. If so try flashing the su zip from the link. If that's a no go I'd recommend backing up your data via other apps, making a nand & flashing a stock rooted rom.
#Root-Hack_Mod*Always=LTE
alpha_mau5 said:
Have you checked if Super SU is granting titanium backup root access?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
It says it has access, says grant, but now the root checker basic i was using says i do not have access, restarting to see if i can change it, when i start SuperuserSU, it say i need to update the binaries and when i hit ok, it says installing and then operation failed and starts the program. As well, anything that has been granted access, a little black popup shell shows at the bottom of the screen real quick saying that super setcpu has been granted root access for the interactive shell?
I have tried two versions of busybox, busybox free which tells me there was a problem opening a shell with root access and then closes and i tried busybox installer which says device is rooted but when i hit install it says that instillation failed.
Im on the stock rom from the 3.16 update, everything i have read is that i would not be able to flash a rom because of compatibility issues and i the 3.16RUU is not available for download anywhere..and just FYI, still fairly new to rooting, but learning!
Thanks
Thanks 72, I flashed the SU Update 1.04 from your link and its working perfect now, good to go...take care. Hopefully it stays rooted!
tonyevo52 said:
Thanks 72, I flashed the SU Update 1.04 from your link and its working perfect now, good to go...take care. Hopefully it stays rooted!
Click to expand...
Click to collapse
No prob glad it worked out for you. Also have you read cap's post here
http://forum.xda-developers.com/showthread.php?t=2126626&page=4
Relating to flashing roms for those in your situation?? Check it out, definitely worth it.
#Root-Hack_Mod*Always=LTE
Has anyone been able to backup using Titanium. Titanium Pro tells me "Backup interrupted...not enough space." I have lots of space. I have tried all the google search solutions and none work.
I have the same problem. Initially, I thought that the sdcards were not mounted (for su root) but that wasn't the issue.
TB will currently backup VIRTUAL items (e.g. Accounts, WiFi access points) which have the TB logo next to it. It seems to fail for all other items.
gale2000 said:
Has anyone been able to backup using Titanium. Titanium Pro tells me "Backup interrupted...not enough space." I have lots of space. I have tried all the google search solutions and none work.
Click to expand...
Click to collapse
Same problem here. According to this post:
http://forum.xda-developers.com/showthread.php?t=2391363&page=7
the small app called sdfix could solve the problem. I haven't tried yet.
cr2069 said:
Same problem here. According to this post: http://forum.xda-developers.com/showthread.php?t=2391363&page=7 the small app called sdfix could solve the problem. I haven't tried yet.
Click to expand...
Click to collapse
Sorry, I've already tried sdFix along with other possible fixes.
(see rooting thread http://forum.xda-developers.com/showpost.php?p=55286180&postcount=55 and http://forum.xda-developers.com/showpost.php?p=55339398&postcount=85)
sdFix fixes the issue with not having write permission to the EXTERNAL SD card. TB is able to write to both INTERNAL and EXTERNAL sd cards -- for VIRTUAL items but it may not have sufficient permission for backing up apps, etc. I sent a log to TB support a few days ago without reply.
Anybody have luck with Helium?
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
iammudd said:
Sorry, I've already tried sdFix along with other possible fixes.
(see rooting thread http://forum.xda-developers.com/showpost.php?p=55286180&postcount=55 and http://forum.xda-developers.com/showpost.php?p=55339398&postcount=85)
sdFix fixes the issue with not having write permission to the EXTERNAL SD card. TB is able to write to both INTERNAL and EXTERNAL sd cards -- for VIRTUAL items but it may not have sufficient permission for backing up apps, etc. I sent a log to TB support a few days ago without reply.
Click to expand...
Click to collapse
Too bad, seems to be TB's problem. Waiting for any progress...The main reason I want rooting is to use TB, but it's not working...
TB will now work if you RE-root your device:
Use SuperSU (settings option) to fully un-root.
Use Modding.MyMind's TWRP custom recovery from http://forum.xda-developers.com/ascend-mate2/orig-development/2014-09-22-teamwin-recovery-project-t2885144
Code:
adb reboot bootloader
fastboot boot TWRP_MT2-L03_RECOVERY.img
Backup your stock recovery.
Backup your stock bootloader.
Backup your system.
When you reboot, TWRP will notice that you're NOT rooted and ask if you wish to be rooted. Choose YES.
Reboot to System.
Start SuperSU and follow the prompts to update SuperSU binaries.
Good luck but you assume all risks. If there are errors in the above instructions, please reply in this thread.
Thanks again to all those involved in bringing TWRP to this device.
iammudd said:
TB will now work if you RE-root your device:
Use SuperSU (settings option) to fully un-root.
Use Modding.MyMind's TWRP custom recovery from http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t2885144
Code:
adb reboot bootloader
fastboot boot TWRP_MT2-L03_RECOVERY.img
Backup your stock recovery.
Backup your stock bootloader.
Backup your system.
When you reboot, TWRP will notice that you're NOT rooted and ask if you wish to be rooted. Choose YES.
Reboot to System.
Start SuperSU and follow the prompts to update SuperSU binaries.
Good luck but you assume all risks. If there are errors in the above instructions, please reply in this thread.
Thanks again to all those involved in bringing TWRP to this device.
Click to expand...
Click to collapse
Shouldn't it be "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img"?
I like the above method though because you get to back up the original recovery first. Just reboot to bootlloader and do "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img" after the backup.
On another note, Titanium Backup still fails for me.
foltz61 said:
Shouldn't it be "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img"?
I like the above method though because you get to back up the original recovery first. Just reboot to bootlloader and do "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img" after the backup.
On another note, Titanium Backup still fails for me.
Click to expand...
Click to collapse
Yes, fastboot boot TWRP_MT2-L03_RECOVERY.img allowed me to try it out first. If it had failed, then hopefully I would still have had the stock recovery. (After playing around with TWRP a bit, I DID eventually flash it.)
foltz61 said:
On another note, Titanium Backup still fails for me.
Click to expand...
Click to collapse
Just now, TB failed again (insufficient storage error).
Had to rerun SdFix to check the platform.xml modifications, FULLY UNROOT and then RE-rooting with TWRP and reinstalling SuperSU again.
Now TB is working again. Very strange. (Will report back if I find out what triggered the problem.)
iammudd said:
Just now, TB failed again (insufficient storage error).
Had to rerun SdFix to check the platform.xml modifications, FULLY UNROOT and then RE-rooting with TWRP and reinstalling SuperSU again.
Now TB is working again. Very strange. (Will report back if I find out what triggered the problem.)
Click to expand...
Click to collapse
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
I don't know if all of this was necessary, but it it working now.
I tried the same thing for the sdcard1, and Titanium said backup successful, but I couldn't find the backup on sdcard 1???
gale2000 said:
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
I don't know if all of this was necessary, but it it working now.
I tried the same thing for the sdcard1, and Titanium said backup successful, but I couldn't find the backup on sdcard 1???
Click to expand...
Click to collapse
Same problem and this also fixed it for me thanks
gale2000 said:
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
Click to expand...
Click to collapse
This workaround has been made obsolete. See next post:
I didn't know what the drawbacks are to using this folder so I was initially reluctant but I've given up and went down this path as well. However, I've reduced some permissions and here's what appears to be working for me:
Use ES Explorer to create the new folder and change its permissions to rwx for group and others. (I didn't need to change owners for any of the folders.)
Use ES Explorer to TEMPORARILY add read-only permission to /data for OTHERS.
Change TiBu backup folder location by manually navigating to the new folder.
Once the new folder has been selected, I restore /data to its original permissions. (The read permission was only needed temporarily for TiBu to find the new folder.)
Copying the files back to my PC, I can see that the zip files for the apks appear to have "reasonable" apk sizes (i.e. not zero-length as before).
I ran across this thread while digging into a Titanium Backup "Insufficient Storage" error and digging into an error thrown by Helium backup. In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Still trying to figure out what's going on with Helium. I have a hunch it may be due to use of a password without encryption, not sure yet.
kemonine96 said:
In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Click to expand...
Click to collapse
Thanks, this appears to have done the trick. It was very baffling when TiBu would work for some tasks but not others. Glad you stumbled onto this thread.
And another follow up for those using Helium or looking for an "adb backup" based solution
This device does not appear to include the full adb backup stack. From some limited testing tonight the pop-up prompt when running "adb backup' or using Helium Backup does not produce prompt on the device so it just fails. This is a known problem on some devices and it's too bad Huawei decided this wasn't a necessary inclusion.
kemonine96 said:
I ran across this thread while digging into a Titanium Backup "Insufficient Storage" error and digging into an error thrown by Helium backup. In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Still trying to figure out what's going on with Helium. I have a hunch it may be due to use of a password without encryption, not sure yet.
Click to expand...
Click to collapse
helium has never worked right for me. I bought it sight unseen since he's such a great dev, but just could not get it to work either rooted or unrooted. I did learn how to do adb backup though because if that.
nrfitchett4 said:
helium has never worked right for me. I bought it sight unseen since he's such a great dev, but just could not get it to work either rooted or unrooted. I did learn how to do adb backup though because if that.
Click to expand...
Click to collapse
Were you able to get adb backup to work at all? I never was able to get it to work.
I solved my titanium backup issues by going into SuperSU, then settings for SuperSU, and unchecked the mount namespace seperation box, then reboot
kemonine96 said:
Were you able to get adb backup to work at all? I never was able to get it to work.
Click to expand...
Click to collapse
It worked just fine for me. Used it to backup kids unrooted phones. That's been a couple years though.
Do you know if there's a way to get Xposed working? I tried the Xposed Framework SDK 26 from inside Magisk, but it put me in a boot loop.
I think we now have Xposed - check the end of this discussion:
https://github.com/rovo89/Xposed/issues/310
I might give this a go when I'm feeling less lazy.
Well actually yes xposed is available. But I left this solution for a long time in favour of Magisk and it's modules to be honest
Sent from my HTC U11 using XDA Labs
thref23 said:
I think we now have Xposed - check the end of this discussion:
https://github.com/rovo89/Xposed/issues/310
I might give this a go when I'm feeling less lazy.
Click to expand...
Click to collapse
Thanks a lot for the link! Thanks a lot to rovo89 for the beta4!!!
xposed-v90-sdk26-arm64-beta4-test1.zip works fine on SHT-AL09 after flashing it via TWRP
What we need:
ROOT
TWRP
Flash with TWRP View attachment xposed-v90-sdk26-arm64-beta4-test1.zip
Install View attachment XposedInstaller_3.1.5.apk
PROFIT!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ZeuseZ said:
Thanks a lot for the link! Thanks a lot to rovo89 for the beta4!!!
xposed-v90-sdk26-arm64-beta4-test1.zip works fine on SHT-AL09 after flashing it via TWRP
What we need:
ROOT
TWRP
Flash with TWRP View attachment 4525802
Install View attachment 4525805
PROFIT!
View attachment 4525804
Click to expand...
Click to collapse
A lot of Xposed modules do not work. GravityBox, which is my favorite, completely f*ked up the rom - had to reflash. Tried a couple of others - didnt break things, but didnt work either. It's dangerous to try these modules, because TWRP restore doesn't really work.
If I'm not mistaken, in the event of a bad module, Xposed can be disabled at boot by pressing a hardware key over and over again. Not that I want to find out.
Anyways, Edge and Edge Pro work. They don't remap the fingerprint sensor functionality. But they have other useful features.
thref23 said:
If I'm not mistaken, in the event of a bad module, Xposed can be disabled at boot by pressing a hardware key over and over again. Not that I want to find out.
Click to expand...
Click to collapse
Which hardware key would that be? And what exactly does "over and over again" mean - how many times or for how long?
Apo11on said:
Which hardware key would that be? And what exactly does "over and over again" mean - how many times or for how long?
Click to expand...
Click to collapse
Any key. This must be where I read it:
https://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
Lukest85 said:
While the device boots you can activate the xposed safemode to disable the framework & modules, without flashing any files and without entering recovery or ROM.
Background:
People are posting when stuck at boot screens or bootloops with xposed installed and there have been lots of great solutions/advice from the community but I have not seen much info posted about the xposed safemode so thought I would share what I believe to be the easiest & first thing to try in order to boot & troubleshoot your setup.
To disable xposed:
1. Repeatedly press any single hardware button during early startup (as soon as device powers on)
2. Wait for device to finish booting into recovery/ROM
3. Fix your setup
Details:
1. The first recognised key press generates two vibrations
2. Then continue to press the same hardware button four more times within 5 seconds
*Each key press generates a short vibration*
3. Success is confirmed with a long vibration
NB
• Activating safemode adds the file 'disabled' (no quotes) to data/data/de.robv.android.xposed.installer/conf/
• The 'disabled' file can be created manually from recovery or rom to disable xposed & modules
• If problems with hardware buttons try pressing the touchscreen to activate safemode
To re-enable xposed:
1. Remove the file 'disabled' using file manager or terminal
2. Reboot
3. Enjoy
***common reasons for xposed related bootloops are due to xposed module/s conflicting with system or each other, and user installing the incorrect framework for the device/sdk. Please investigate these options first and read/search the xposed Q&A OP/thread if you're unsure before posting or contacting devs***
xposed Q&A thread:
http://forum.xda-developers.com/showthread.php?t=3030118
Disclaimer:
**I cannot guarantee safemode works with every version of xposed or every device but it has always worked for me on differing setups, roms & devices.**
I hope this is helpful and will be updating the post again so stay tuned for more detailed/technical info.
Give thanks to talented & amazing devs: @Tungstwenty - xposed safemode @romracer - xposed @rovo89 - official xposed
Fantastic work & great dedication !!!
Click to expand...
Click to collapse
thref23 said:
Any key. This must be where I read it:
https://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
Click to expand...
Click to collapse
That's not really helpful in our case. It says to keep pressing and then it will boot into recovery. Step 3 says "Fix your setup" . If TWRP is not working properly (and that's exactly point - it does not, so there is no fixing) there is no benefit in booting into the recovery. Doing stuff like clearing cache does nothing when Xposed module screws up the rom. Not to mention you dont really need this Xposed "feature" in order to boot into recovery or download mode. You can just shut down your device and then use the regular, designated hw key combination in order to boot into either.
Apo11on said:
A lot of Xposed modules do not work. GravityBox, which is my favorite, completely f*ked up the rom - had to reflash. Tried a couple of others - didnt break things, but didnt work either. It's dangerous to try these modules, because TWRP restore doesn't really work.
Click to expand...
Click to collapse
TWRP restore works fine for me.
magnumlove said:
TWRP restore works fine for me.
Click to expand...
Click to collapse
You have different M5 model than mine - the 10" if I recall correctly. Partition table and a bunch of other things are not the same. You have the same or very similar model as the OP from that twrp thread, so it's not surprising the recovery works for you. If someone with SHT-AL09 says the restore works for them - that's a different story, and I'd have to start troubleshooting my own device. As of this moment, I think this recovery build is not fully compatible with 8.4" LTE version. It's failing to mount /system and /vendor partitions, and after some troubleshooting I've done I can see there are 4 versions of mount binary on my device. For example, when I manually invoke the one in /sbin folder - I can do "mount -o remount,rw /system" just fine, but when I try the same with mount version from /system/bin folder - it fails. And there is 2 more of them. It's not clear which one twrp is using when it's trying to mount partitions for restore, but it's obviously the wrong one. The only way I see to fix this is to recompile twrp.
I have the SHT-AL09. When I was bootlooped (I was actually more bricked than bootlooped), I installed TWRP, and I could not mount anything (except my SD card) as read/writeable.
After the equivalent of a factory reset, I installed TWRP, and it seems to work perfectly.
I have not tried to restore a backup. But I wonder if doing so would work after the equivalent of a factory reset, if not while bootlooped.
thref23 said:
I have the SHT-AL09. When I was bootlooped (I was actually more bricked than bootlooped), I installed TWRP, and I could not mount anything (except my SD card) as read/writeable.
After the equivalent of a factory reset, I installed TWRP, and it seems to work perfectly.
I have not tried to restore a backup. But I wonder if doing so would work after the equivalent of a factory reset, if not while bootlooped.
Click to expand...
Click to collapse
"seems to work perfectly" and "I have not tried to restore a backup" are contradicting statements in this context. "seems" sounds like a guess. If you want to be about 95% sure it will work -boot into twrp, goto Advanced->Terminal and type "mount". Examine if your /system and /vendor partitions are mounted as "ro" or "rw" - if it's ro then your restore is likely to fail. Needless to say, to be 100% sure you have to actually attempt a restore. Make certain to decrypt your /Data using PIN/password when twrp prompts you, otherwise you will get screwed. TWRP doesn't need to decrypt in order to wipe, and it wipes the /Data partition before every restore. If you don't decrypt and attempt restore - /Data will get wiped, but then the /Data restore will fail, because it's encrypted. In that case, theoretically you should be able to boot into twrp again, and it should prompt you for PIN /password to restore /Data again. Once you provide it and successfully decrypt - you should be run the restore again and restore the missing /Data partition from nandroid backup.
Apo11on said:
"seems to work perfectly" and "I have not tried to restore a backup" are contradicting statements in this context. "seems" sounds like a guess. If you want to be about 95% sure it will work -boot into twrp, goto Advanced->Terminal and type "mount". Examine if your /system and /vendor partitions are mounted as "ro" or "rw" - if it's ro then your restore is likely to fail. Needless to say, to be 100% sure you have to actually attempt a restore. Make certain to decrypt your /Data using PIN/password when twrp prompts you, otherwise you will get screwed. TWRP doesn't need to decrypt in order to wipe, and it wipes the /Data partition before every restore. If you don't decrypt and attempt restore - /Data will get wiped, but then the /Data restore will fail, because it's encrypted. In that case, theoretically you should be able to boot into twrp again, and it should prompt you for PIN /password to restore /Data again. Once you provide it and successfully decrypt - you should be run the restore again and restore the missing /Data partition from nandroid backup.
Click to expand...
Click to collapse
Without rebooting back into TWRP, I think all partitions are mounted r/w. Previously, if I unchecked 'mount system partition read only,' it would stay checked - not anymore. And I was able to successfully flash Xposed. That's what I mean by "seems to work perfectly."
I have TWRP backups now, that I hope I never have to try and restore. For now I'd much rather leave well enough alone than to be 100% certain. Plus I kind of hate rebooting.
thref23 said:
I have the SHT-AL09. When I was bootlooped (I was actually more bricked than bootlooped), I installed TWRP, and I could not mount anything (except my SD card) as read/writeable.
After the equivalent of a factory reset, I installed TWRP, and it seems to work perfectly.
I have not tried to restore a backup. But I wonder if doing so would work after the equivalent of a factory reset, if not while bootlooped.
Click to expand...
Click to collapse
Restore works fine from EMUI to EMUI. I had issues when trying to restore back to EMUI from a GSI-TWRP hung on the splash screen. Managed to restore in the end after flashing stock system img. All my back ups were made with PIN screenlock removed.
Apo11on said:
A lot of Xposed modules do not work. didnt break things, but didnt work either
Click to expand...
Click to collapse
same here, most modules don't work, has anyone found a solution?
Si73 said:
Restore works fine from EMUI to EMUI. I had issues when trying to restore back to EMUI from a GSI-TWRP hung on the splash screen. Managed to restore in the end after flashing stock system img. All my back ups were made with PIN screenlock removed.
Click to expand...
Click to collapse
I don't have screenlock but I haven't managed to create any backup, because of the famous 255 error
I've got huawei mediapad m5 lite (bah2-w19)