Database Users

miui titanium backups

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.

Restoring after wipe clean from 4.2.2 to 4.3 via Titanium BU

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.

[Q] TWRP Restore didn't restore apps - can I get them back? [solved]

What it says on the tin. I backed up using ROM Manager to launch the backup. I was upgrading to the CM11m6 from CM10.2 but that led to a failed boot followed by boot into recovery so I decided to restore. Restoring has left just CM`s built-in apps, a few gapps and one paid app. I thought nandroid backups were like imaging a computer and you got everything back? I stupidly didn't make backups with TitaniumBackup thinking it was unnecessary.
So, any ways for me to get all my apps back?

Update for googlers: I used Nandroid Manager to restore the missing apps from the backup. Hope that helps someone else with this situation!
I discovered a new issue while I continued to use CM 10.2.1--some apps updated and then it went into a bootloop again. Luckily I had am so I restored it and restored the missing apps again. I suspect it's either Gmail, Google Text-to-Speech, Google+ or Android Terminal Emulator. Google didn't reveal anybody else having this problem yet with the latest updates, so I must have some very unique issue.
As for updating to CM11, I'm gonna try creating another image (which'll hopefully restore all apps!) after it gets stable and trying updating to CM M5 instead of M6 which seems to have caused a bootloop for at least one person, too. I can't post outside links yet, so that person's report can be found by googling this phrase including quotation marks: "Update From 10.2.1 Stable To 11 M6 Causes Boot Loop".

Another update for googlers: The problem of apps-not-restoring seems to have been caused by version 2.6.0.0 of TWRP. I tried updating to 2.6.3.1 using both GooManager and TWRP Manager but it didn't stick. Used Nexus Root Toolkit to upgrade TWRP to 2.7.0.0, though. Restoring the image with that restored all the apps as far as I can figure out. Yay! Now I don't have to wait 3-4 hours for the app restore process to finish on top of the nandroid restore.

Accidentally formatted /system partition. Busybox not working

I was facing an issue with a custom rom and tried to do data wipe with twrp.
But accidentally I selected /system partition also and wiped that. Not sure if this is the problem or not, but since then few apps are not working. Titanium backup is showing phone is not rooted (I tried the workaround of force sys/bin and it worked for a while). Busybox showing that phone is not rooted.
I am fed up with all these errors.
Please help me solve this. I am using SM-N900 (Exynos) Galaxy Note 3.

If you want root, flash supersu from twrp.

Akhyll said:
I was facing an issue with a custom rom and tried to do data wipe with twrp.
But accidentally I selected /system partition also and wiped that. Not sure if this is the problem or not, but since then few apps are not working. Titanium backup is showing phone is not rooted (I tried the workaround of force sys/bin and it worked for a while). Busybox showing that phone is not rooted.
I am fed up with all these errors.
Please help me solve this. I am using SM-N900 (Exynos) Galaxy Note 3.
Click to expand...
Click to collapse
Re-install "Root" and install "CWM Recovery" then flash busybox or download from Google Play

audit13 said:
If you want root, flash supersu from twrp.
Click to expand...
Click to collapse
dalisoft said:
Re-install "Root" and install "CWM Recovery" then flash busybox or download from Google Play
Click to expand...
Click to collapse
still didn't work

Can't mount system as writable in TWRP (device or resource busy)

Hi everyone,
Just got my new G6, after much pain I managed to unlock the bootloader, install TWRP (v3.2.1.0) and to root it with SuperSU (stable release 2.82).
For now I'll keep the stock rom but I wanted to make a backup in case something went wrong with other tweaking I might do and I couldn't because TWRP couldn't "mount /system (device or resource busy)".
So I went into the mount menu and tried checking system but it just won't. I can mount it as read only but I can't mount it as writable.
If it's of any importance, I couldn't get magisk to install to root the phone and had to use SuperSU instead.
I could do the backup while mounting system as read only but I feel like it might be an issue in the future (for custom roms or even restoring the backup maybe ?) if I can't fix this issue.
So does anyone how to get TWRP to mount system as writable ? Thank you

Elvenstar said:
Hi everyone,
Just got my new G6, after much pain I managed to unlock the bootloader, install TWRP (v3.2.1.0) and to root it with SuperSU (stable release 2.82).
For now I'll keep the stock rom but I wanted to make a backup in case something went wrong with other tweaking I might do and I couldn't because TWRP couldn't "mount /system (device or resource busy)".
So I went into the mount menu and tried checking system but it just won't. I can mount it as read only but I can't mount it as writable.
If it's of any importance, I couldn't get magisk to install to root the phone and had to use SuperSU instead.
I could do the backup while mounting system as read only but I feel like it might be an issue in the future (for custom roms or even restoring the backup maybe ?) if I can't fix this issue.
So does anyone how to get TWRP to mount system as writable ? Thank you
Click to expand...
Click to collapse
Have you formatted data trough the dedicated option in TWRP? Format, not wipe, where you have to put "yes".
Anyway you can try with Melina's TWRP which solves many problems of the official one: https://forum.xda-developers.com/lg-g6/development/recovery-twrp-3-2-1-unofficial-fixes-t3722199

Killua96 said:
Have you formatted data trough the dedicated option in TWRP? Format, not wipe, where you have to put "yes".
Anyway you can try with Melina's TWRP which solves many problems of the official one: https://forum.xda-developers.com/lg-g6/development/recovery-twrp-3-2-1-unofficial-fixes-t3722199
Click to expand...
Click to collapse
I did try it once after the magisk install failed and I assumed it was because of that issue but I haven't tried yet with superSU correctly installed. Should I immediately try the backup after formatting or boot the phone once before ?
The issue I have with Melina's TWRP is that it's not compatible with fulmics and if I were to install any custom rom I think it would be that one (to keep stock camera mostly)

Elvenstar said:
I did try it once after the magisk install failed and I assumed it was because of that issue but I haven't tried yet with superSU correctly installed. Should I immediately try the backup after formatting or boot the phone once before ?
The issue I have with Melina's TWRP is that it's not compatible with fulmics and if I were to install any custom rom I think it would be that one (to keep stock camera mostly)
Click to expand...
Click to collapse
Format data, reboot recovery, and try to install magisk or mount system.
For Melina's TWRP it has NO problems with Fulmics, Zefie said that "officially" is not compatible because two users said that they have problems with that TWRP only with fulmics, i can assure you that with last version of both Melina's TWRP and Fulmics i never had problems like those two users, anyway you can try to use Melina's TWRP and if you have any problems just flash back the official twrp.

Killua96 said:
Format data, reboot recovery, and try to install magisk or mount system.
For Melina's TWRP it has NO problems with Fulmics, Zefie said that "officially" is not compatible because two users said that they have problems with that TWRP only with fulmics, i can assure you that with last version of both Melina's TWRP and Fulmics i never had problems like those two users, anyway you can try to use Melina's TWRP and if you have any problems just flash back the official twrp.
Click to expand...
Click to collapse
Alright so it's been a rough ride.
I formatted data, reboot TWRP and then indeed I was able to mount system as writable.
I then did my backup, which said it was successful and the only error it showed then was "unable to unmount /system"
I flashed magisk and rebooted into the normal system and the phone of course was back to factory settings and asked me my google account. Except that when I tried logging in it always showed me an error along the lines of "google play services keeps crashing". (making it impossible to get through the installation part of the system)
I'm not sure why that happened. I had frozen some apps but that shouldn't have been saved since I formatted data right ? and the phone was working perfectly fine before that.
But anyway I didn't really know what to do at that point so I just jumped the gun and downloaded and flashed fulmics.
It worked fine but only with supersu. For some reason magisk just doesn't want to get installed at all.
The rom itself worked fine but I had no root access by choosing magisk in the aroma installer so I wiped again and installed it again with supersu which works.
I also flashed xposed which is also working as intended.
So I'm all set for now I think.
Maybe when I need to wipe again I'll figure out why magisk doesn't work but for now I'm satisfied.
In any case, thank you for your help