I could be mistaken, but it seems as though my G100 has returned to a non-rooted state.
Yesterday morning I was finally able to move the slider for OEM-unlock under Developer Settings.
So I installed Magisk on my device, downloaded a stock firmware using the RSA tool from Lenovo, patched the boot.img using Magisk on my phone, and was able to write that to my phone using the [fastboot flash boot boot.img] command.
And all seemed to be well. I even had my carrier and everything working on it last night and had begun restoring my apps and data with Titanium Backup.
And then suddenly Titanium Backup is reporting it is unable to gain root access. Magisk seems to still believe that the phone is rooted, and Titanium Backup still shows up in it's list. I still see the notification pop up when Titanium Backup launches, saying that it was granted Superuser access. But Titanium Backup has it's own internal popup that says it couldn't acquire root using /system/bin/su
I've tried re-writing my boot.img via fastboot as before, and there is no change in the symptom.
Anyone have any ideas?
I've performed a factory reset on my device, and the command [fastboot flash boot boot.img] again, and it seems to be working.
Titanium Backup is working, but seems to be unable to restore some things. I've reached out to them to see if anything can be done.
After further investigation, it seems the "root" I have obtained so far with the stock ROM is not really root at all. It does allow some root operations, but many are simply blocked on Android 11 by default.
I suspect my only path forward is to install a custom ROM.
Looked into this a bit more and found that disabling the option:
Verify apps over usb
Under developer settings allows Titanium Backup to proceed for most of my restores.
Also, it seems Titanium Backup is deprecated, so that's fun. Edit: Titanium Backup was able to restore most of my applications after the above change, but many of the restored applications simply don't work.
Going to try out Swift Backup.
Related
My device:
I have a 7" iDeaUSA YG A777 Android Tablet that is rooted. The version of Android it is running is 4.0.3. The kernel on the device is 3.0.8-tcc [email protected] #97.
My problem:
When I try to back up my device using the MyBackup app, the device reboots in the middle of the backup. When I attempt another back up after the reboot, I get the same results. I've tried uninstalling and re-installing the app, but that doesn't work. Clearing the app's cache doesn't work, either. I also tried doing a factory reset and restoring everything manually, but that also didn't work. I read a few posts that suggested that the SD card or USB flash drive might be the cause, but that isn't the case (at least in regards to my situation) because the same thing happens when I try to back up online to MyBackup's database with no SD card or USB flash drive attached.
I also tried using Titanium Backup ★ root, but I got the exact same results as I did with MyBackup, so the problem isn't app specific. One thing that did work was not allowing root access to MyBackup. When that is denied, I can back up my device as many times as I want. However, since MyBackup has been denied root access, it can only back up the apps on my device, not the data that accompanies those apps. That's a problem because the main reason that I'm backing up my device is to back up the apps on my device AND its data.
I've been at this for three days. During that time, going through all of the steps that I've listed here has made the backup go through completely without rebooting once or twice, but the reboot problem persists more often than not. I’m out of ideas to try. Any suggestions would be helpful.
I finally figured out what the problem was. I mentioned in my first post that I used Titanium Backup and got the same results as I did with MyBackup Pro. However, when I used Titanium Backup, MyBackup Pro was still granted root privileges. I think when Titanium Backup got to the MyBackup Pro app to back it up, it activated something with the app that was causing it to reboot my tablet. In other words, what I did to fix my problem was I denied root privileges to MyBackup Pro and Titanium Backup now works fine and produces a successful backup everytime. So, MyBackup Pro was the problem.
Can You help, do use the 4.0.3?
How do you Root?
I would like change firmware to 4.1 to ....
emersonvier said:
Can You help, do use the 4.0.3?
How do you Root?
I would like change firmware to 4.1 to ....
Click to expand...
Click to collapse
I do use 4.0.3. However, rooting a device depends on the brand of the device. For example, the process to root a Google Nexus tablet might be different than the process to root a Samsung Galaxy tablet. What you should do is put your phone or tablet's brand into a Google search engine and then add "root" to the search query (Ex: "Google Nexus 7 root").
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
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!
I'm setting up a new Pixel 3 (Android 9), and moving from a Note 4 (Android 6.0.1).
When setting up, Google installs some, but not all, apps from the store. The missing apps I expected to restore from redundant Titanium Backup and My Backup Pro backups.
I have successfully installed Magisk 18.1 using the Boot Image Patch method (no TWRP)
Titanium Backup Pro reports it has superuser rights. When I try to restore an app created with the Note 4, Titanium Backup hangs forever on the "Restoring App+Data AppName n.n.nn.n" overlay with the spinning circle. TiBk is unresponsive, although Android is still running and I can see home screen or notifications. Restart is required to clear the pending action. I have run TiBk with USB debugging enabled (if that is still required), but get the same failure.
I also have MyBackup Pro. When I try to restore an apk (or apk+data), it appears to run normally. MBP reports it has superuser rights. At the end of the process the status summary says: Appname: failed: cp: can't create '/data/app/appnamestring-1/appnamestring.apk': Path does not exist.
I tried using MBP to back up an app already installed on the Pixel 3 from the store, and then restore it. It gives the same error, except the place where there is "appnamestring-1" in the Android 6 backup, there is now something like "appnamestring-2fjdk56akjfkdye7dkfja9=="
Also, I observe that the app that was installed prior to this backup restore experiment is no longer present afterward. I re-installed from the store.
Can anyone suggest next steps for solving this issue?
timg11 said:
I'm setting up a new Pixel 3 (Android 9), and moving from a Note 4 (Android 6.0.1).
When setting up, Google installs some, but not all, apps from the store. The missing apps I expected to restore from redundant Titanium Backup and My Backup Pro backups.
I have successfully installed Magisk 18.1 using the Boot Image Patch method (no TWRP)
Titanium Backup Pro reports it has superuser rights. When I try to restore an app created with the Note 4, Titanium Backup hangs forever on the "Restoring App+Data AppName n.n.nn.n" overlay with the spinning circle. TiBk is unresponsive, although Android is still running and I can see home screen or notifications. Restart is required to clear the pending action. I have run TiBk with USB debugging enabled (if that is still required), but get the same failure.
I also have MyBackup Pro. When I try to restore an apk (or apk+data), it appears to run normally. MBP reports it has superuser rights. At the end of the process the status summary says: Appname: failed: cp: can't create '/data/app/appnamestring-1/appnamestring.apk': Path does not exist.
I tried using MBP to back up an app already installed on the Pixel 3 from the store, and then restore it. It gives the same error, except the place where there is "appnamestring-1" in the Android 6 backup, there is now something like "appnamestring-2fjdk56akjfkdye7dkfja9=="
Also, I observe that the app that was installed prior to this backup restore experiment is no longer present afterward. I re-installed from the store.
Can anyone suggest next steps for solving this issue?
Click to expand...
Click to collapse
The only way that worked for me is getting my apps installed from GDrive backup (the from settings - > security - > backup or so). Actually this only restores apps from the play store.
Restore via ADB also didn't work for me...
TGHH said:
The only way that worked for me is getting my apps installed from GDrive backup (the from settings - > security - > backup or so). Actually this only restores apps from the play store.
Restore via ADB also didn't work for me...
Click to expand...
Click to collapse
Thank you for the reply! It was rather quiet around here...
But seriously, you can't restore apps? Why?? What is the issue? Why can't an app designed to backup and restore, running with superuser permissions, restore an app?
timg11 said:
Thank you for the reply! It was rather quiet around here...
But seriously, you can't restore apps? Why?? What is the issue? Why can't an app designed to backup and restore, running with superuser permissions, restore an app?
Click to expand...
Click to collapse
I found it also quite annoying! Trying to copy apps via cable seems to be only fetching a list of apps from the old phone and then re-installing them. No settings, no data. Also - obviously - only apps from play store! So unusable.
My advise - export, backup etc. all you can from your old phone for import or so.
In regards to Titanium - there's a wayto make it work. I had this once that it got stuck: in the settings there's an option to change the processing mode - see https://www.titaniumtrack.com/kb/titanium-backup-kb/titanium-backup-troubleshooting.html , number 29.
You will have to ACK every app to be stored but it should work.
Not sure what I did different to you but it worked for me (titanium). Maybe try restoring app only, then data only. I think I might have done a batch restore from a nandroid originally.
Ok, I've tried different things, but it seems I'm stuck when trying to restore my app data for certain apps (mostly games) on crDroid 6.11 (Android 10). I'm restoring from an older Android 6 ROM. I would prefer not to root at this point.
I've tried:
ADB backup: I can create backup, but adb is stuck on the 7 Pro at the password prompt when trying to restore
Helium backup: Again, I can create backup on my old phone, and transfer to new phone. But Helium throws an error when trying to restore.
It seems I'm running out of options. I can simply not understand it should be so difficult to back up your app data for a few simple apps (games) and restore them on a new device without root.
I know there are options with root, and maybe I will end up rooting with Magisk just to be able to do this. But I still find it very strange that there is no easy tool to do this - or maybe there is and I don't know it.
Any suggestions are very welcome. Thanks!