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
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.
Migrating to a new phone and discovered an issue with the backups on my old phone. This is tested and happening on both btw.
If I backup and restore a working app it then will force close on opening. Clearing cache and data and still force closes.
I tried uninstalling titanium, deleting titanium folder and reinstalling.
Same issue after a backup and restore of an application.
Running Oneplus 6 and Oneplus 7 pro
Unlocked and unrooted with magisk
Titanium at latest version from market.
logcat
https://pastebin.com/6R8Wv12D
Thanks for any help available
tabooki said:
Migrating to a new phone and discovered an issue with the backups on my old phone. This is tested and happening on both btw.
If I backup and restore a working app it then will force close on opening. Clearing cache and data and still force closes.
I tried uninstalling titanium, deleting titanium folder and reinstalling.
Same issue after a backup and restore of an application.
Running Oneplus 6 and Oneplus 7 pro
Unlocked and unrooted with magisk
Titanium at latest version from market.
logcat
https://pastebin.com/6R8Wv12D
Thanks for any help available
Click to expand...
Click to collapse
App restore with titanium doesn't work for switching to a new phone, only restoring to the same phone and same os. When it does work the apps tend to be super glitchy. I'll drop a link to the xda thread where you can get more info/ help. Good luck.
https://forum.xda-developers.com/showthread.php?t=2717159
Sent from my GM1917 using XDA Labs
swiftbones74 said:
App restore with titanium doesn't work for switching to a new phone, only restoring to the same phone and same os.
Click to expand...
Click to collapse
Agreed. I've only migrated app data to a new phone using TB import/export (.TiBkp) feature. AFAIK, you can only do that one app at a time. So I've only done it with a few apps that I really wanted to save the user data.
More folks on this forum are recommending Swift Backup these days. It seems more reliable for this phone. I've use TB for years, but now I've just started trying out Swift Backup.
It appears TB is not compatible with the newer "split apks" format for newer apps in the appstore.
Basically TB will only backup the "base.apk" for an app when it does a backup. But with split apks, there are other APK files besides base.apk, like one for the app's language (split_config.en.apk) or the cpu type (split_config_arm64_v8a.apk) and the screen resolution (split_config.xxhdpi.apk).
So, since TB does NOT backup these extra apk files, these files will be missing when you do a restore with TB and thus the restored app will crash when you try to run it.
Luckily there is a new open-source backup app that works well with Slit-apks on Android 8+:
GitHub - NeoApplications/Neo-Backup: backup manager for android
backup manager for android. Contribute to NeoApplications/Neo-Backup development by creating an account on GitHub.
github.com
And I think it's better then Swift backup because:
1) Swift backup requires your google account login
2) Swift backup throws errors if you block internet access to it for security reasons
3) Swift backup is not open-source, so it could go the way of TB in the future.
4) And OandBackupX is FREE
JohnC said:
It appears TB is not compatible with the newer "split apks" format for newer apps in the appstore.
Basically TB will only backup the "base.apk" for an app when it does a backup. But with split apks, there are other APK files besides base.apk, like one for the app's language (split_config.en.apk) or the cpu type (split_config_arm64_v8a.apk) and the screen resolution (split_config.xxhdpi.apk).
So, since TB does NOT backup these extra apk files, these files will be missing when you do a restore with TB and thus the restored app will crash when you try to run it.
Luckily there is a new open-source backup app that works well with Slit-apks on Android 8+:
GitHub - NeoApplications/Neo-Backup: backup manager for android
backup manager for android. Contribute to NeoApplications/Neo-Backup development by creating an account on GitHub.
github.com
And I think it's better then Swift backup because:
1) Swift backup requires your google account login
2) Swift backup throws errors if you block internet access to it for security reasons
3) Swift backup is not open-source, so it could go the way of TB in the future.
4) And OandBackupX is FREE
Click to expand...
Click to collapse
So I tried this app and maybe you can help me out and tell me why after trying a restore I ended up with all of these errors , any advice or hints would be great,,,also prior to attempted install I was rooted and about 40 plus apps installed fine,
Swift does not give me these errors
Thanks
[email protected] said:
So I tried this app and maybe you can help me out and tell me why after trying a restore I ended up with all of these errors , any advice or hints would be great,,,also prior to attempted install I was rooted and about 40 plus apps installed fine,
Swift does not give me these errors
Thanks
Click to expand...
Click to collapse
Those errors seem like there is a problem with xandbackupx not being able to gain root access.
When you first started OABX, it has a bunch of cards where each card requires a different permission on your device - did you go through each card/step and give all those permissions, including root?
Are you using android 8+?
JohnC said:
Those errors seem like there is a problem with xandbackupx not being able to gain root access.
When you first started OABX, it has a bunch of cards where each card requires a different permission on your device - did you go through each card/step and give all those permissions, including root?
Are you using android 8+?
Click to expand...
Click to collapse
Thanks for the reply,,, yes I checked all and granted all permissions, Iam on a11 firmware running a a12 rom Bliss, ,, I will mess with it some more with it , it looks really robust with alot of options so maybe one of the settings need to be ticked or maybe it's just this rom, it's not a big deal as I have the other one to fall back on until I do some more testing
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.