Database Users

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.

[HELP] Screwd up nandroid

Hello guys!
I was updating from 4.4.4 to lollypop via OTA, then I realized that even if I run the stock ROM, I am still unlocked + root, meaning that the OTA won't run.
I did a complete nandroid backup via Wugs Nexus Toolkit, including data.
Then I wiped and flashed the new 5.0 via Nexus Toolkit, but when I tried to restore only the data it didn't work.
I decided to go back to 4.4.4. and do things properly, but now I'm not able to restore anything.
I am not bothered with the apps and stuff, but I had plenty of pictures which I forgot to backup, and I want to restore them. I even tried to access the nandroid backup files, but no success!
I was accustomed with the old CMW, where you had the .img files, but I got no clue on what to do here!
I add the picture of the nandroid backup folder on my PC ( I think the data files are splitted, but I cannot open them in any case, not even with 7zip).
The nandroid was executed via Nexus Toolkit, but I guess it has been done through TRWP.
Long story short:
1) how can I access the pictures inside the nandroid backup?
2) how can I restore a nandroid backup that keeps failing?

theraizen said:
1) how can I access the pictures inside the nandroid backup?
Click to expand...
Click to collapse
Maybe CWM does things differently, I don't know, but with TWRP, a Nandoid backup doesn't back up your SD card partition, so if you wiped everything, all your pics are gone. Sorry.

Yeah, I guess so.. Managed to recover something with DISK DIGGER (its an app, free on the store). Just wanted to write it here, so if anyone has the same issue can recover this way!

Can't restore my phone from Backup of TWRP

dHi friends.
I installed a TWRP and did a BackUp normally, but then I flash a new Rom, the 19s, and now when I get into the TWRP i can not see any file, but when i go to the file explorer in my phone all the files are there, The problem is in the TWRP, no files can be seen.
What could be a possible solution??
Thanks!!

I assume that clean flash of recovery should resolve your problem.
Maybe the screenshot can help us.

I've had an issue with TWRP as well. I was on stock 21s when I backed up all and installed CM13. After that I restored 21s and the big surprise was that my password was not the same. I mean the one that you have to enter instead of fingerprint to unlock the phone.
Strange though... I've wiped all and restored again, the same thing. Luckily my fingerprint was detected. Also there was some thing with bluetooth. Eventually I had to do a fresh install and everything came back to normal, but it looks like I couldn't rely on the backup at all. This is happening with TWRP 5.8 TeamSpaiN. I'm not saying that the recovery is to be blamed, but its behavior is weird at times...

valy_cta said:
I've had an issue with TWRP as well. I was on stock 21s when I backed up all and installed CM13. After that I restored 21s and the big surprise was that my password was not the same. I mean the one that you have to enter instead of fingerprint to unlock the phone.
Strange though... I've wiped all and restored again, the same thing. Luckily my fingerprint was detected. Also there was some thing with bluetooth. Eventually I had to do a fresh install and everything came back to normal, but it looks like I couldn't rely on the backup at all. This is happening with TWRP 5.8 TeamSpaiN. I'm not saying that the recovery is to be blamed, but its behavior is weird at times...
Click to expand...
Click to collapse
Yes, I had something like that, I don't remember what TWRP I installed. But, my fingerprint was detected normally, however my pattern has been changed I dont know to what, i couldn't unlock my phone by the pattern, just with the fingerprint, i solved by the forgotten pattern and with the leeco account.
The other problem that I had afetr flashing 19s, was that in TWRP I couldn't see any files even not able to restore, because there wasn't any file, but in the explorer, I saw the files normally. I had to format the userdata, and of course did a backup on my pc of my backup, for pasting it after. And then it worked normally. That is very strange!!
But i could solve it.

Soft-Bricked Nova / No system

Hello,
Today I tried to root my Nova and somehow I managed to delete the system while doing that. I don't know how or when, I did wipe the phone at some point, but left system unchecked. So now it is stuck in an endless boot, I just see the orange "Your phone is unlocked and not safe etc" message, nothing more. I can access TWRP and fastboot, and tried to use the LineageOS 13. But it failed, it told me I need a CAN-model, and mine is "generic_a53". So I figured I'll just put EMUI back on it, but I can't seem to find a working version for my phone. The huawei-website is pretty useless in that regard, they don't offer it. And the HiSuite-recovery just said that my model is not supported anymore.
So.. help? I know I screwed up and should have made a full backup, but I never figured I'd screw this up so spectacularly.
EDIT: Okay, I just clicked on "Backup" in TWRP, out of curiosity, and it said that "System" is 2516mb, but "Data" is 0mb, so maybe that's what's lacking?

Seems you are using the wrong TWRP. Use the one made for lineage. Also, what is your exact model number, you should be able to recover that way. My guess is you wiped data, factory reset, or formatted data. You could try using the backup made by bluesmoothie to restore data. You will have to search around this forum as I can't remember exactly which thread it is in.

fragee said:
Hello,
Today I tried to root my Nova and somehow I managed to delete the system while doing that. I don't know how or when, I did wipe the phone at some point, but left system unchecked. So now it is stuck in an endless boot, I just see the orange "Your phone is unlocked and not safe etc" message, nothing more. I can access TWRP and fastboot, and tried to use the LineageOS 13. But it failed, it told me I need a CAN-model, and mine is "generic_a53". So I figured I'll just put EMUI back on it, but I can't seem to find a working version for my phone. The huawei-website is pretty useless in that regard, they don't offer it. And the HiSuite-recovery just said that my model is not supported anymore.
So.. help? I know I screwed up and should have made a full backup, but I never figured I'd screw this up so spectacularly.
EDIT: Okay, I just clicked on "Backup" in TWRP, out of curiosity, and it said that "System" is 2516mb, but "Data" is 0mb, so maybe that's what's lacking?
Click to expand...
Click to collapse
Just like @wangdaning said, you're using wrong TWRP.
If you wanna flash LOS13, you gotta flash the TWRP mentioned at requirements.
It told you that your model is "generic_a53" because you're using "twrp_huawei_generic_a53.img".
To restore your phone, try to restore the backup made by bluesmoothie.
1) Download the TWRP backup (emui 4.1) made by @bluesmoothie from here: https://www.dropbox.com/sh/qrk0fbpn...ffYdia7raa/TWRP/BACKUPS/FPFDU16930014596?dl=0 . I had to download the files one by one, as I couldn't download the whole folder because dropbox was telling me that it's too big. After you've downloaded all the files from backup, put them in a folder named 1970-03-18--16-40-58_CANC432B100.
2) Download this recovery: https://www.androidfilehost.com/?fid=745425885120713827 , which is made by @Grarak.
3) Make a backup of boot.img so a folder will be created at TWRP > BACKUPS (e.g. FPFDU16A20001907).
4) Place the TWRP backup folder into the folder created at step 3). So, it'll be like this: TWRP > BACKUPS > FPFDU16A20001907 > 1970-03-18--16-40-58_CANC432B100.
5) Restore the backup.

Okay, it was the wrong TWRP, now that I flashed the recommended one, I was able to install LOS13, and now everything is working again. Thank you very much guys!

Proper TWRP backup and restore procedures?

For the life of me I cant restore a backup of my current rom. What am I missing?
Ive tried backup on both slots and attempted to restore Individually.

enigma2446 said:
For the life of me I cant restore a backup of my current rom. What am I missing?
Ive tried backup on both slots and attempted to restore Individually.
Click to expand...
Click to collapse
Backing up with encryption is messy...
If you disable all security with the OS booted... And are on F2FS... You probably stand the best chance...
Otherwise... Might I recommend Migrate or Titanium Backup and forget about the backup feature in TWRP altogether...
Or use adb backup with your PC... But I don't know if that is restorable either

I'm not sure what goes wrong for people with TWRP backup's? I often see people talking here and on telegram about this. I didn't get my ph-1 till late September of last year so I missed the unofficial TWRP builds and I'm sure there were lots of improvement's made along the way. This being said, backup's work flawlessly for me and I use them almost daily since December when I started flashing lots of different ROMs. The only time I've run into a problem restoring a backup is from custom to stock or vice versa.
When I run into a backup not restoring I flash that ROM plus TWRP zip and then try again I don't even boot into the system just reboot and try again and it works for me. I hope this helps you.
I am encrypted on all my setups these days and always flash the exact same way from TWRP : select install , choose rom zip, select add more zips, select TWRP zip, flash/ select home button, select reboot, select recovery. Again from TWRP: select install, choose gapps (if needed), choose add more zips, select Magisk, flash and reboot into the system.
I stated the obvious above because I assume there must be either a subtle nuance btwn the way that people flash or something btwn the phone and twrp changed at some point before December (when I began using regularly)
@rignfool isn't alone in his belief that TWRP backup's don't work well. He is also one of many people that know more about Android development and the ph-1 then myself. However I disagree with anyone who would say TWRP backup's don't work well because I depend on them and they do work, precisely as they are supposed to.