Related
I was playing with my TF101 earlier today and went to check Titanium Backup when I was given a surprise, I can't use it anymore. My tablet had been rooted since the day I got it nearly a year ago but somehow my busybox got uninstalled. I have not done anything that would cause it to be uninstalled, and when I try to install it again no program is able to. When trying to update the Su binary Superuser fails to gain root access as well, so something weird happened in the past few days (looking at my most recent Titanium Backups manually it seems it happened after 6/3, but I don't know why).
My first attempt to fix was re-flash the most recent Honeycomb-based Revolver update (3.11.1) and run "Fix Permissions" but that didn't help. I'm thinking the only way to be able to fix this is to do a wipe and re-install of everything, or even a new nvflash, but my most recent backup is months old (I'd been travelling and not messing with ROMs so I didn't have a need for a backup).
Does anyone have suggestions as to what else I can do before I try and do a wipe/install?
Thanks
In terminal, does "which su" and "which busybox" return anything?
How about "ls -l /system/*/su" and "ls -l /system/*/busybox"
You probably have 2 versions and one is not does not have the su id set.
sent while running with scissors
gee one said:
In terminal, does "which su" and "which busybox" return anything?
Click to expand...
Click to collapse
I tried running it in "Android Terminal Emulator" but for some reason it doesn't work anymore, it loads and then auto closes... so I did it in "System Tuner"s terminal emulator.
I ran both and got "Failed to run: Error running exec(). Command: [which, su] Working Dierctory:null Environment: null"
How about "ls -l /system/*/su" and "ls -l /system/*/busybox"
Click to expand...
Click to collapse
for both of these i get "No such file or directory"
I honestly have no idea what is going on because this last week I used it as a netbook while travelling Korea and for the 4 months prior I haven't been able to access the internet regularly so I haven't been playing around with CWM, flashing new roms, etc. I think the newest apps I've installed were mixi (like Facebook, but Japanese), Skype, and Temple Run, none of which require root access.
shadowmonk36 said:
I was playing with my TF101 earlier today and went to check Titanium Backup when I was given a surprise, I can't use it anymore. My tablet had been rooted since the day I got it nearly a year ago but somehow my busybox got uninstalled. I have not done anything that would cause it to be uninstalled, and when I try to install it again no program is able to. When trying to update the Su binary Superuser fails to gain root access as well, so something weird happened in the past few days (looking at my most recent Titanium Backups manually it seems it happened after 6/3, but I don't know why).
My first attempt to fix was re-flash the most recent Honeycomb-based Revolver update (3.11.1) and run "Fix Permissions" but that didn't help. I'm thinking the only way to be able to fix this is to do a wipe and re-install of everything, or even a new nvflash, but my most recent backup is months old (I'd been travelling and not messing with ROMs so I didn't have a need for a backup).
Does anyone have suggestions as to what else I can do before I try and do a wipe/install?
Thanks
Click to expand...
Click to collapse
Don't do the wipe yet, just use Recovery to reinstall the same ROM and it may help. It maybe related to kernel or /system/bin or /system/xbin (or even etc).
I tried reflashing the most recent Revolver Honeycomb update (3. 11.1) but it didn't help, still have the problem.
Re-manually install busybox and SU using the superuser.zip that's flashable in cwm, then Install SuperSU and update binary with that. Should fix all issues, I prefer SuperSU to superuser since it doesn't glitch as much. xD
Thing O Doom said:
Re-manually install busybox and SU using the superuser.zip that's flashable in cwm, then Install SuperSU and update binary with that. Should fix all issues, I prefer SuperSU to superuser since it doesn't glitch as much. xD
Click to expand...
Click to collapse
I will give that a try, as soon as I can find the superuser.zip file in question. I googled for it, and looked on XDA but I can't seem to locate it. Could you help point me in the right direction?
I re-thought about what tingtan said and I realized that just an update wouldn't necessarily have everything needed so I found the most recent full ROM and flashed it followed by the update and it looks like things are fixed.
I'd still like a link to that superuser.zip file for the future, but now I can backup and I might try playing with ICS now.
Superuser.zip link: http://androidsu.com/superuser/
I prefer SuperSU though, all preference.
Thing O Doom said:
Superuser.zip link: http://androidsu.com/superuser/
I prefer SuperSU though, all preference.
Click to expand...
Click to collapse
Thanks, that is the one I found but since you were talking about SuperSU I wasn't sure if it was correct. I will also give SuperSU a try, but after I reflash everything (it broke again shortly after I got my titanium backup done).
I recently flashed a new rom (the last time I did this was almost 2 years ago so I forgot what to do). Titanium backup has been doing weekly updates for a long time. So when I started up the phone titanium backup is gone, I read that I must redownload from the play store, but when I run it, it says I failed to acquire root privileges. It tells me to get busy box, so I download that too, but that won't install properly.
What should I do now? Have I lost root? The bootloader is available...that means it's still rooted right? The internal sd card still shows my folder of titanium backup and all the other root folders I used to have on my phone, I just can't get titanium backup to run so i can't restore.
Thanks!
stryder1587 said:
I recently flashed a new rom (the last time I did this was almost 2 years ago so I forgot what to do). Titanium backup has been doing weekly updates for a long time. So when I started up the phone titanium backup is gone, I read that I must redownload from the play store, but when I run it, it says I failed to acquire root privileges. It tells me to get busy box, so I download that too, but that won't install properly.
What should I do now? Have I lost root? The bootloader is available...that means it's still rooted right? The internal sd card still shows my folder of titanium backup and all the other root folders I used to have on my phone, I just can't get titanium backup to run so i can't restore.
Thanks!
Click to expand...
Click to collapse
If you flash a new rom root is lost.
You have to root again.
S.R.
A few of the JB ROMS were causing issues with root. The fix was to re-flash the SU (superuser) apk and that would fix things right up. You should be able to find it doing a search.
Good luck and hope this helps!
stryder1587 said:
I recently flashed a new rom (the last time I did this was almost 2 years ago so I forgot what to do). Titanium backup has been doing weekly updates for a long time. So when I started up the phone titanium backup is gone, I read that I must redownload from the play store, but when I run it, it says I failed to acquire root privileges. It tells me to get busy box, so I download that too, but that won't install properly.
What should I do now? Have I lost root? The bootloader is available...that means it's still rooted right? The internal sd card still shows my folder of titanium backup and all the other root folders I used to have on my phone, I just can't get titanium backup to run so i can't restore.
Thanks!
Click to expand...
Click to collapse
Lets start with a few basic questions... dont mean to offend you, just wanna make sure its not something you may have overlooked.
What rom did you flash?
What, if anything, did you wioe in recovery?
Did you get a superuser or supersu prompt when titanium started?
shivasrage said:
If you flash a new rom root is lost.
You have to root again.
S.R.
Click to expand...
Click to collapse
Not necessarily so. Most custom roms are pre-rooted by the dev. Ive flashed countless roms and until recently w/ jb not had any issues w/ root access.
Sent from my Nexus S 4G using Tapatalk 2
seems you've just lost root privileges,
just flash supeuser again and you will be fine...
I think this is the right thread to ask queation relevant to titanium backup so,
Here's my question -- how to backup messages by using titanium backup.
atishey23 said:
I think this is the right thread to ask queation relevant to titanium backup so,
Here's my question -- how to backup messages by using titanium backup.
Click to expand...
Click to collapse
it pretty much looks like this in TitBack, give or take a few letters: "[SMS/MMS/APN] Phone/Messaging...". when you tap on it, the pop-up recognizes it as "Phone/Messaging Storage". this is where your text messages are.
some 3rd-party MMS apps like GoSMS Pro can back up your messages too, and I believe there's also an app or two solely for backing up your messages to your sdcard/internal storage.
Titanium Batch restore fail
Hi all
Having a few problems, I'm new to flashing roms and the use of Titanium Backup and I've just flashed my second ROM. I've gone from CM9 to CM10. Before doing so I created a backup of apps + data.
I flashed the ROM fine, and ran the batch restore function in Titanium. I have all the icons on my homescreen from the previously installed apps but after clicking on them my phone tells me that app isn't installed. I then notice that my notification from Titanium's batch restore shows the apps I had downloaded from the play store failed to restore (the notification said that the elements failed after batch restore was complete).
I noticed that these apps have a line through them when the list of apps I want to restore appears.
Titanium then advised me that the apps did not restore as the Android ID had changed, So I then reverted to the previous android ID thinking this to be the solution. However, after running the restore function again, the same amount of elements failed to restore.
Due to my lack of knowledge in Titanium and my need for these apps, I turned to the play store and decided to manually redownload all the apps again. This does not work either! The error message I get is the apps cannot be downloaded due to an error (491). I guess this is to do with the android ID changing?
Please help, how can I get these apps to restore? and also how can I be able to download apps from the play store again? :crying:
EDIT: So I was able to reinstall the apps from the play store by wiping the dalvik + cache.
This still leaves me baffled as to why Titanium wasn't able to do this
jessel56 said:
Hi all
Having a few problems, I'm new to flashing roms and the use of Titanium Backup and I've just flashed my second ROM. I've gone from CM9 to CM10. Before doing so I created a backup of apps + data.
I flashed the ROM fine, and ran the batch restore function in Titanium. I have all the icons on my homescreen from the previously installed apps but after clicking on them my phone tells me that app isn't installed. I then notice that my notification from Titanium's batch restore shows the apps I had downloaded from the play store failed to restore (the notification said that the elements failed after batch restore was complete).
I noticed that these apps have a line through them when the list of apps I want to restore appears.
Titanium then advised me that the apps did not restore as the Android ID had changed, So I then reverted to the previous android ID thinking this to be the solution. However, after running the restore function again, the same amount of elements failed to restore.
Due to my lack of knowledge in Titanium and my need for these apps, I turned to the play store and decided to manually redownload all the apps again. This does not work either! The error message I get is the apps cannot be downloaded due to an error (491). I guess this is to do with the android ID changing?
Please help, how can I get these apps to restore? and also how can I be able to download apps from the play store again? :crying:
EDIT: So I was able to reinstall the apps from the play store by wiping the dalvik + cache.
This still leaves me baffled as to why Titanium wasn't able to do this
Click to expand...
Click to collapse
Did you try to restore system apps? I always use tb w/ the pro key to restore user apps + data, and have been getting the changed android id lately, but whether I keep the new id or revert to the old one, my restore works. Depending on what ROM I'm going to or from, sometimes I have to change my home screen shortcuts for system apps.
Sent from my Nexus S 4G using xda premium
p1gp3n said:
Did you try to restore system apps? I always use tb w/ the pro key to restore user apps + data, and have been getting the changed android id lately, but whether I keep the new id or revert to the old one, my restore works. Depending on what ROM I'm going to or from, sometimes I have to change my home screen shortcuts for system apps.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I didn't select restore system apps, instead I selected restore all apps with data, failing that I tried restore missing apps + all system data.
What option should I normally be selecting to do a straight restore after flashing a ROM? Does the fact that there is a line through the apps that I'm trying to restore mean anything?
I always select "restore missing apps + data" it's the 1st option under restore in the batch menu. The apps with a line through them are the ones that tb recognizes as being backed up but not installed.
Sent from my Nexus S 4G using xda premium
I rooted my TF700, installed superuser, is able to use Root Browser. But i still can't use Titanium Backup. I installed Titanium Backup, but I couldn't acquire root privilege. Anybody know why?
Also, when I use Root Browser, sometimes i can see the files, sometimes the thing is just empty. Anybody know whY? i'm lost!
I did try googling, but can't find anything i need.
Thanks!
I would try these:
Use SuperSU instead of superuser
Install and update to latest version of busybox
Install ROM Manager and use it to fix permissions (don't use it for anything else)
I'm tired of search. Write a post is my last resort always.
The thing is I've tried with both Android L builds and got the same. I install Titanium Backup and SuperSU (have tried 2.01 and 2.02 newest versions) prompt for super user privilegies, however Titanium Backup clearly states it don't have root access... and inside SuperSU app you can see Titanium Backup as rooted.
The strange thing is that I've been searching about this since the morning and see no one with this issue, that's why I'm writing this post.
How can I get Titanium Backup to work properly with root?
Thanks in advance.
PS: My phone is rooted since Root Explorer works like a charm.
alainalemany said:
I'm tired of search. Write a post is my last resort always.
The thing is I've tried with both Android L builds and got the same. I install Titanium Backup and SuperSU (have tried 2.01 and 2.02 newest versions) prompt for super user privilegies, however Titanium Backup clearly states it don't have root access... and inside SuperSU app you can see Titanium Backup as rooted.
The strange thing is that I've been searching about this since the morning and see no one with this issue, that's why I'm writing this post.
How can I get Titanium Backup to work properly with root?
Thanks in advance.
PS: My phone is rooted since Root Explorer works like a charm.
Click to expand...
Click to collapse
Is that version the test versions from their twitter site?
http://forum.xda-developers.com/goo...droid-l-developer-preview-discussion-t2795890
http://forum.xda-developers.com/google-nexus-5/help/android-l-developer-preview-help-t2796217
Thanks @Shinyhead and @Lethargy, the problem was I was installing Titanium Backup from Google Play.
Dear community,
honestly I considered myself not a noob anymore when it comes to flashing, rooting and installing devices. But obviously I was wrong: Cyanogenmod, Titanium Backup and SuperSU are fooling me to madness. :silly: So I hope to find help here because all I want to do is to restore all apps' data. But I will start at the beginning:
I updated my rooted Nexus 7 LTE to CM 13.0-20151226-NIGHTLY-deb and it turned out that Google Play Services continue to crash, no PlayStore could be loaded and so on. I've searched for this issue and don't want to discuss this here as there are many threads for this already.
However, I deciced to switch to OpenGapps and downloaded the pico package for Android 6 on ARM.
By the way I also switched from CWM recovery to TWRP 2.8.7.1.
Finally, CM was running as expected and I danced my pants off!
During all this I formatted the device completely, but made a backup of all apps using Titanium Backup.
So, I re-installed Titanium Backup, copied the backup files to the device and started to "restore missing apps and data" from the bulk operations menu.
All selected apps were installed perfectly (danced again) but then I noticed that the apps' data was not restored.
I searched for this issue and found instructions saying that SuperSU is needed for Titanium Backup to restore data. That was new to me as TB worked fine without SuperSU on my device all the time.
However, I flashed the latest stable Version of SuperSU from chainfire.
After rebooting, the SuperSU app was installed and when it starts, an error popup appears saying that no su file is installed and this has to be done manually.
When I now start Titanium Backup, it prompts missing root access and consequently does not start up.
Furthermore CM is really unstable and freezes from time to time.
So, I lost root by flashing SuperSU? What irony!
Anyway, I am willing to format and re-install my device another time and I would gladly set SuperSU aside as I never needed it in the past. But I really need to get Titanium Backup working to restore the apps' data.
Can anyone of you help me on this, please? Is SuperSU really necessary or do you know a way to manage Titanium Backup without SuperSU on CM13?
cocororo said:
Dear community,
honestly I considered myself not a noob anymore when it comes to flashing, rooting and installing devices. But obviously I was wrong: Cyanogenmod, Titanium Backup and SuperSU are fooling me to madness. :silly: So I hope to find help here because all I want to do is to restore all apps' data. But I will start at the beginning:
I updated my rooted Nexus 7 LTE to CM 13.0-20151226-NIGHTLY-deb and it turned out that Google Play Services continue to crash, no PlayStore could be loaded and so on. I've searched for this issue and don't want to discuss this here as there are many threads for this already.
However, I deciced to switch to OpenGapps and downloaded the pico package for Android 6 on ARM.
By the way I also switched from CWM recovery to TWRP 2.8.7.1.
Finally, CM was running as expected and I danced my pants off!
During all this I formatted the device completely, but made a backup of all apps using Titanium Backup.
So, I re-installed Titanium Backup, copied the backup files to the device and started to "restore missing apps and data" from the bulk operations menu.
All selected apps were installed perfectly (danced again) but then I noticed that the apps' data was not restored.
I searched for this issue and found instructions saying that SuperSU is needed for Titanium Backup to restore data. That was new to me as TB worked fine without SuperSU on my device all the time.
However, I flashed the latest stable Version of SuperSU from chainfire.
After rebooting, the SuperSU app was installed and when it starts, an error popup appears saying that no su file is installed and this has to be done manually.
When I now start Titanium Backup, it prompts missing root access and consequently does not start up.
Furthermore CM is really unstable and freezes from time to time.
So, I lost root by flashing SuperSU? What irony!
Anyway, I am willing to format and re-install my device another time and I would gladly set SuperSU aside as I never needed it in the past. But I really need to get Titanium Backup working to restore the apps' data.
Can anyone of you help me on this, please? Is SuperSU really necessary or do you know a way to manage Titanium Backup without SuperSU on CM13?
Click to expand...
Click to collapse
lmao, your title is nice!
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken. .52 is stable even though its not listed as, i have been using it for some time, and its whats needed for M. you may even find some .6 versions, dont use those, they are systemless, well you can if you want lol. i havent tried them yet, so i dont know what pitfalls may lurk.
Thank you for your help and I am happy to entertain
bweN diorD said:
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken.
Click to expand...
Click to collapse
I will try to update SuperSU as soon as possible.
But sadly TWRP now freezes a few moments after I start the device in recovery mode. When the device starts normally, it freezes as well while showing the CM launcher screen. It stays animated but nothing happens. I will try to re-install TWRP via fastboot flash and then install SuperSU .52 and post my experiences here. :fingers-crossed:
Hi again bweN diorD,
bweN diorD said:
i believe your problem is you used the wrong su zip, you need the latest beta, not stable. should be .52 if im not mistaken.
Click to expand...
Click to collapse
Sorry to say so but SuperSU .52 does not solve the problem. In fact, after flashing the BETA-SuperSU-v2.52.zip using TWRP, CM does not start up anymore. The loading screen with the hypnotizing smiley appears and stays animated but even after 15 minutes CM does not start up. Even TWRP was freezing from time to time.
So I re-installed TWRP, CM and Gapps like in my first post again.
So, is the problem that my device is not rooted indeed? Could this be fixed with CF-autoroot or any tool like this?
I found this thread http://forum.xda-developers.com/showthread.php?t=2448352 although it is for the device deb-razor and my device's bootloader says it is a deb-zoo. By the way, the bootloader displays "LOCK STATE - unlocked".
cocororo said:
Hi again bweN diorD,
Sorry to say so but SuperSU .52 does not solve the problem. In fact, after flashing the BETA-SuperSU-v2.52.zip using TWRP, CM does not start up anymore. The loading screen with the hypnotizing smiley appears and stays animated but even after 15 minutes CM does not start up. Even TWRP was freezing from time to time.
So I re-installed TWRP, CM and Gapps like in my first post again.
So, is the problem that my device is not rooted indeed? Could this be fixed with CF-autoroot or any tool like this?
I found this thread http://forum.xda-developers.com/showthread.php?t=2448352 although it is for the device deb-razor and my device's bootloader says it is a deb-zoo. By the way, the bootloader displays "LOCK STATE - unlocked".
Click to expand...
Click to collapse
hmmm,
i havent used 2.52 on a cm rom, but i have used it on plenty aosp 6.0.* roms without issue.
clean things up so its booting again, then look in developer options and make sure root is turned on. i have seen a few times devs default it to off, but i have never seen a custom rom come not rooted at all.
bweN diorD said:
clean things up so its booting again, then look in developer options and make sure root is turned on.
Click to expand...
Click to collapse
Thanks for your support!
I cleaned everything up -- meaning re-installed everything -- so the device boots up. I checked the developer options and root is set to "apps only". That worked up to now.
Speaking of root: As I wrote I used to have CWM and switched to TWRP. Anyhow, CWM always asked to "fix root" when exiting. I think that's why things worked then and now with TWRP this "fix root" option is gone. But why is SuperSU not working for my Nexus 7 deb? I also tried to install older versions like advised in the Nexus 7 thread here but there was not even a SuperSU app.
So, I recap: CWM used to fix root, TWRP does not. That's why installing SuperSU seems to be a good idea. SuperSU's latest version freezes CM at start-up. Without SuperSU Titanium Backup does not restore app data while other apps do not have problems to get root access. I'm confused
cocororo said:
Thanks for your support!
I cleaned everything up -- meaning re-installed everything -- so the device boots up. I checked the developer options and root is set to "apps only". turn it on apps and adb and see if that helps, thats the preferred setting anywaysThat worked up to now.
Speaking of root: As I wrote I used to have CWM and switched to TWRP. Anyhow, CWM always asked to "fix root" when exiting. I think that's why things worked then and now with TWRP this "fix root" option is gone. its not gone in twrp, it sees that you have root and doesnt ask. really its unadvised to use the twrp generated root anyways But why is SuperSU not working for my Nexus 7 deb? I also tried to install older versions like advised in the Nexus 7 thread here but there was not even a SuperSU app.hmm, maybe thats the problem, maybe you need to install supersu to get things working properly. its on the play store, give it a shot
So, I recap: CWM used to fix root, TWRP does not. That's why installing SuperSU seems to be a good idea. SuperSU's latest version freezes CM at start-up. Without SuperSU Titanium Backup does not restore app data while other apps do not have problems to get root access. I'm confused
Click to expand...
Click to collapse
^^^^
so to clarify your last paragraph, when you say that installing supersu breaks things, were talking about the zip right?
i just want you to get the app from the play store, if you havent tried that alone yet. but change the root setting too.
bweN diorD said:
so to clarify your last paragraph, when you say that installing supersu breaks things, were talking about the zip right?
i just want you to get the app from the play store, if you havent tried that alone yet. but change the root setting too.
Click to expand...
Click to collapse
Correct, I was talking about the zip which is meant to be installed through TWRP.
So, I downloaded the SuperSU app after double-checking that root is set to "Apps & ADB" in the developer settings. Btw. debugging and installation from unknown sources (I hope this is the right translation for this feature) is enabled as well.
When I started the SuperSU app, it first says the binary SU needs an update and I could choose the installation method: When choosing "normal", the app tried to install but failed saying "Installation failed! Restart device and try again!" but even after restarting this was what the app gave me. When I chose "TWRP" the app rebooted the device to recovery but I assume this would end up in installing the zip file which crashed my CM.
Finally, I installed CF-autoroot for deb via the .bat file included in the CF-autoroot package. Now, SuperSU and Titanium Backup are not complaining anymore, so I think this root issue is fixed! :highfive: (couldn't find a dancing smiley).
However, Titanium Backup is not bringing back my app data The restore process seems good as Titanium Backup installs missing apps but even if I install an app the official way via PlayStore and then restore the app's data from my backup using Titanium Backup, there is no effect and the app acts like being installed freshly.
TB claims "restore successful" but the app's data is still missing. I will now check if the backup files are really sound and if I can get them to work on another device. The worst thing I could imagine is that TB did not backup data of apps which had been installed on sdcard. In that case, the data is lost, I'm afraid...
Do you have an idea how this could be or what I could try?
cocororo said:
Correct, I was talking about the zip which is meant to be installed through TWRP.
So, I downloaded the SuperSU app after double-checking that root is set to "Apps & ADB" in the developer settings. Btw. debugging and installation from unknown sources (I hope this is the right translation for this feature) is enabled as well.
When I started the SuperSU app, it first says the binary SU needs an update and I could choose the installation method: When choosing "normal", the app tried to install but failed saying "Installation failed! Restart device and try again!" but even after restarting this was what the app gave me. When I chose "TWRP" the app rebooted the device to recovery but I assume this would end up in installing the zip file which crashed my CM.
Finally, I installed CF-autoroot for deb via the .bat file included in the CF-autoroot package. Now, SuperSU and Titanium Backup are not complaining anymore, so I think this root issue is fixed! :highfive: (couldn't find a dancing smiley).
However, Titanium Backup is not bringing back my app data The restore process seems good as Titanium Backup installs missing apps but even if I install an app the official way via PlayStore and then restore the app's data from my backup using Titanium Backup, there is no effect and the app acts like being installed freshly.
TB claims "restore successful" but the app's data is still missing. I will now check if the backup files are really sound and if I can get them to work on another device. The worst thing I could imagine is that TB did not backup data of apps which had been installed on sdcard. In that case, the data is lost, I'm afraid...
Do you have an idea how this could be or what I could try?
Click to expand...
Click to collapse
sorry, i really dont know what happens as far as titanium when you put an app on the sd.
glad you got root working though, although i still dont understand why it wouldnt work the right way.
if you run into any more specific road blocks, ill try and help if i can, but this general problem with the data, i havent a clue the problem or solution, short of the data isnt there completely.
Hi again,
sorry for my late reply! I tried a couple of things but here's the most obvious one:
Apparently the backup files are kind of corrupt. I don't know what went wrong there but TB did not create a full backup. Indeed there is a .tar.gz file for every app but in fact none of these has more than 2 KB. So I strongly assume that this might be the mistake - which also means that all my app's data is lost.
bweN diorD said:
glad you got root working though
Click to expand...
Click to collapse
At least this is a success and I am happy to have TWRP, OpenGapps and Titanium Backup running on a fully rooted device :good:
Thank you for all your time and help! I really appreciate how supportive we "techies" are :highfive:
Have a great day and - a bit late but anyway - a happy new year!