I'm on the latest miui and when I go to my titanium backup it says it can't get root acces. I can use all my other apps that require root but not titanium backup. Is anyone else having this problem? I sure could use some help. I love the latest miui. but I can't restore any of my apps that I backed up. I did download busybox as well. Then it tells me to enable SU in SU setting but I don't see anything that I can enable
I got it fellas, I did a complete wipe and flashed the latest miui. I then went in and turned on SU and it's all gravy now.
Sorry guys may I ask a question relative to restoring apps via TiBU?
Before flashing stock 4.3 I had updated TiBU and backed up my apk's+data
Wiped everything to have a clean slate for TRIM to work perfectly and I've started to restore my apps.
TIBU takes forever to install a single apk, actually never ends.
Reboot.....
If I try to install apk from the market and then restore only the data from TiBU the app crashes.
After that I cannot reinstall the app anymore even from the play store.
Is there a way to overcome this?
Thanks
PS: I have already tried the solution Menu/Preferences/backup folder location
PS2: Nexus 4 - built JWR66Y - FRANCO r178
vagos696 said:
Sorry guys may I ask a question relative to restoring apps via TiBU?
Before flashing stock 4.3 I had updated TiBU and backed up my apk's+data
Wiped everything to have a clean slate for TRIM to work perfectly and I've started to restore my apps.
TIBU takes forever to install a single apk, actually never ends.
Reboot.....
If I try to install apk from the market and then restore only the data from TiBU the app crashes.
After that I cannot reinstall the app anymore even from the play store.
Is there a way to overcome this?
Thanks
PS: I have already tried the solution Menu/Preferences/backup folder location
PS2: Nexus 4 - built JWR66Y - FRANCO r178
Click to expand...
Click to collapse
I don't trust TiBU. its a real mess for me. I for one backup my ANDROID folder, and flash all apps through recovery. and then copy back the Android folder on SDCARD.
How did you root your 4.3 image? Many custom kernels break root on 4.3. Try re-flashing SuperSU or re-flash ROM and stick to the stock kernel.
via Nexus Toolkit. I'm still rooted even after applied Franco, but I'll revert back to stock kernel just to check your possibility.
Even the saved TiBU apk's are not getting installed.
How can I re-install the broken apps which were affected from TiBU? As I mentioned even fresh installation from the play store is not processed.
I was hoping to avoid re-flashing and re-rooting from scratch.
Nope even with stock kernel I face the same problems. Any suggestions?
I guess there's something wrong with your /data partition. I'd either start over with flashing the factory image or at least format /data (not wipe, really format). Don't forget to backup your internal sdcard content first, it will be deleted with both methods.
Also I'd recommend not using a toolkit for flashing the factory image and rooting. It's easy enough using fastboot and a custom recovery. This way you'll be on the safe side, not missing any errors etc.
Make sure your TiBU directory is set to storage/emulated/legacy/TitaniumBackup, not storage/emulated/0/TitaniumBackup.
It worked for me, anyway. Well, after having to perform a factory reset, as it screwed up the UUIDs, that is
Thanks for the suggestion. You were right my path was storage/emulated/0/TitaniumBackup.
I revert it to the suggested one but I have the same issue.
Factory reset, start from scratch, initial path storage/emulated/legacy/TitaniumBackup
The same problem which also end up destroying the fresh apk as well.
Hopeless
Tell us exactly what you're doing. Which ROM / image, software, versions, procedure, all the details. Maybe something other well ring a bell.
As already quoted
1. Before updating to 4.3, I updated TiBU to the latest version and kept backup of the apps+data
2. Clean flash of stock 4.3 ROM (JWR66Y) via Nexus Toolkit
3. Root (Busybox, SU etc)
4. Flashing Franco Kernel r178
5. Installation of TiBU
6. Try to restore - PROBLEM
Plan B:
1. Factory Data Reset
2. BusyBox gone but still have root access
3. Stock ROM - Stock Kernel - Rooted
4. Install TiBU
5. Restoring - PROBLEM
Description of the PROBLEM:
I cannot restore apk's is getting into a loop and never ends.
I can restore data to an installed apk, but then the app crashes
I cannot re-install the (restored) app via playstore, I get "unknown error code during installation -24-"
Current situation
1. Factory Data Reset again
2. Franco r178
3. No restores via TiBU
Don't shoot me, but it still sounds like the TiBu 4.3 ROM backup folder path problem. Here's what I do and what works for me:
1. Open TiBu
2. Click on "Menu"
3. Click on "Preferences"
4. Click on "Backup folder location"
5. Click on "DETECT!"
6. Click on "Whole device"
7. Choose "/storage/emulated/legacy/TitaniumBackup"
8. Click on "Use the current folder"
9. TiBu will now ask if it should move the other backups to the new folder, say no.
10. Exit the preferences with the back key
11. TiBu will now reload with the new preferences
Now restoring should work if the path is the problem.
About loosing root with a custom kernel on 4.3 ROMs:
If you lose root by flashing a custom kernel it may still seem like root is active, i.e. the root frontend app will still be there and ask for root permissions etc. Try the following to ensure that TiBu is running with full root privileges: Uninstall some unimportant system application (some Gapp for example, like Google Currents - backup first if you need it). If uninstalling gets cancelled with a message like "Can't find the apk file", it's likely that root doesn't work properly.
Come on man, I hate to give up
Thanks for the inspiration but unfortunately:
1. I can unistall, backup and restore properly Google Currents (hence proper root)
2. Back up folder was set properly also by verifying your steps (2-10)
And again if I try to restore an old app (not the data) it gets to the familiar loop.
Ok. I'd now flash the full factory image, thus resetting every partition (backup internal sdcard first). Please try without a toolkit to be safe. You need the drivers installed (your toolkit should already have taken care of that) and have adb and fastboot ready. There are batch/shell scripts included in the factory image which invoke the fastboot commands in one step.
Next flash a custom recovery with fastboot and use it to flash SuperSU for root access.
Refrain from flashing a custom kernel now and try if you can successfully restore with TiBu at this point.
If you can, the problem was either one of your partitions/filesystems f_cked up or the toolkit doing something wrong.
rooted and rommed a friend's note 3 to jasmine, and before we did it we upgraded titanium backup to the pro edition via marketplace, without realizing that it had deleted all three backups that were all in separate locations, one in the default location, one on the SD card and one in the phone's internal storage.
before I did anything to the phone rom wise I made a nandroid backup via twrp and I cannot boot it into an emulator successfully AND get the texts from it through installing titanium backup, creating a backup and copying it off, didn't work out.
so now what I need is a way to load up a nandroid backup without corrupting the backup. every time I try to restore the backup into the phone it bootloops, only thing I can think of that would interfere with it is the kernals, NC2/4. jasmine is currently running on NC2 and the stock firmware with the texts on it uses NC4, when I tried reflashing NC4 to the device after reintalling the backup it bootlooped, and vice versa with NC2.
thoughts/suggestions? sol on the texts?
thanks.
Never tried this but worth a shot. https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore
Sent from my SM-N900V using Tapatalk
I'll give it a go.
followed the steps found at: http://forum.xda-developers.com/nexus-s/general/extract-restore-sms-mms-contacts-call-t1370349
and had no success, doing the same via root explorer and nandroid manager to get the original files from the backup, nothing was restored.
I'm assuming that they're just gone after that?
rom manager text restore found nothing, quite a few were backed up though so who knows. not a good thing to lose them all.
I have backed up my device using FlashFire, but to restore it I would need to be in a rooted ROM with Flashfire installed.
It should be easier to make a backup with adb, which can be restored to an unrooted device.
I set it up and tried to make a backup. However, when using the backup command, it says to unlock your device and confirm the backup. At this point, a screen is supposed to open on the 935T that allows this to be done (have done it on other devices some time ago), but it does not open it.
Has anyone else tried adb back-up and been successful - or have an idea of why the device does not respond ?
I set up Developer options as instructed with respect to adb. Also believe I am on latest SDK - ADB.
Note - the root threads are full of posts on being stuck on boot screen, etc., and rather then having to reinstall and wipe firmware, this might offer a good alternative
Update - it looks like ADB is not fully compatible with 6.0 with regard to backups and restores. The failure to bring up the confirmation screen on the device is pretty common and even when it does, the results are usually no good.
ADB will back up the data of the apps but not the apks, what I do back up apks es file explorer and do ADB to backup the app data. It is pain but it works without root.
newuser1984 said:
ADB will back up the data of the apps but not the apks, what I do back up apks es file explorer and do ADB to backup the app data. It is pain but it works without root.
Click to expand...
Click to collapse
Backing apps and data can be done a number of ways - I want to back up system also and you need boot to do that, but supposed to be able to restore with adb without root, so if the backup was of a rooted system, it should restore it that way. It just doesn't work on 6.0 devices yet.
Hi All,
I'm running the latest AICP 13.1 nightly on my Moto G4, rooted with SuperSU. My issue is that Titanium Backup throws an error when launching showing: "Sorry I could not acquire root privileges... This attempt was made using the "/system/bin/.ext/.su" command""
Starting a terminal and switching to root prompts SuperSU to ask to grant permissions and is successful. Same with busybox or the official TWRP app.
I've done a lot of digging and I'm at a bit of a loss. The only thing that seems somewhat odd is that busybox, SuperSU, and the Official TWRP App are all installed on the internal storage while Titanium Backup installed to the SD card. Moving Titanium Backup to the internal storage doesn't change the results though. The choice of where to install the apps wasn't made by me so I'm not sure what decides that.
TIA!
Seems like the next nightly of AICP fixed this, so I don't really know what the core issue was.
bra1niac said:
Hi All,
I'm running the latest AICP 13.1 nightly on my Moto G4, rooted with SuperSU. My issue is that Titanium Backup throws an error when launching showing: "Sorry I could not acquire root privileges... This attempt was made using the "/system/bin/.ext/.su" command""
Starting a terminal and switching to root prompts SuperSU to ask to grant permissions and is successful. Same with busybox or the official TWRP app.
I've done a lot of digging and I'm at a bit of a loss. The only thing that seems somewhat odd is that busybox, SuperSU, and the Official TWRP App are all installed on the internal storage while Titanium Backup installed to the SD card. Moving Titanium Backup to the internal storage doesn't change the results though. The choice of where to install the apps wasn't made by me so I'm not sure what decides that.
TIA!
Click to expand...
Click to collapse