Help restoring in TWRP - Nexus 5 Q&A, Help & Troubleshooting

I've wiped everything in TWRP (factory reset; advanced -> dalvik/system/data/internal/cache; format data), then pushed my backup to /sdcard/. When I go into Restore to reload the backup, it just shows a big gray square with no items. I've tried pushing it to several different locations and restarting TWRP. I finally landed on having the backup folder (named something like 8780a9ypwt98h34) inside the folder called 'TWRP' that TWRP creates upon being booted the first time.
But nothing shows up in the Restore. It's just a big blank square box, where you can tell there should be navigation items like folders and files listed.
Why isn't the backup showing? What do I have to do?

EDIT: just realized TWRP has a file manager. Where do I put the backup (it's a folder named something like 9807a9h9f83fh398). Also, is there a reason that instead Restore listing items like a file manager (like what you see in TWRP when you hit install, or when you go through the TWRP file manager), all it shows is a gray box with no text in/around it?

Hi, I've been using PhilZ recovery for a while but before that I used TWRP and might be able to help if you still need it.
If I'm remembering correctly, TWRP looks for backups in one location and doesn't allow you to navigate to a different directory so it's important to get your backup in just the right spot for it to be recognized.
When I was trying to do exactly what you are, what I found that worked for me was to start by doing a backup before trying to copy the files I actually wanted to restore. Doing that backup to start with allows TWRP to create all the directories it needs to for its static backup location. Once that was done it was easy then to just copy my backup to the proper location.
The directories should be something like this: TWRP > BACKUPS > stringoflettersandnumbers > nameofbackup
Hope this helps.
Nexus 5 / Cataclysm / Franco / PhilZ

chef_christoph said:
Hi, I've been using PhilZ recovery for a while but before that I used TWRP and might be able to help if you still need it.
If I'm remembering correctly, TWRP looks for backups in one location and doesn't allow you to navigate to a different directory so it's important to get your backup in just the right spot for it to be recognized.
When I was trying to do exactly what you are, what I found that worked for me was to start by doing a backup before trying to copy the files I actually wanted to restore. Doing that backup to start with allows TWRP to create all the directories it needs to for its static backup location. Once that was done it was easy then to just copy my backup to the proper location.
The directories should be something like this: TWRP > BACKUPS > stringoflettersandnumbers > nameofbackup
Hope this helps.
Nexus 5 / Cataclysm / Franco / PhilZ
Click to expand...
Click to collapse
That's brilliant. I will try that.

Related

Flash a Data.img?

I extracted all my files from my data.img backup and made it into a .zip. Is there anyway
i can cwm flash that data.zip to get all my data back? I tried just flashing the zip and it says,
"(bad) Installation Aborted."
Any help would be greatly appreciated
mafo5000 said:
I extracted all my files from my data.img backup and made it into a .zip. Is there anyway
i can cwm flash that data.zip to get all my data back? I tried just flashing the zip and it says,
"(bad) Installation Aborted."
Any help would be greatly appreciated
Click to expand...
Click to collapse
Here's a few things you could do assuming that what you want is even in this zip file.
1) Get a working cwm format zip file and take a close look at it because you need to use it as a template if this is going to work. In particular, check out updater-script in META-INF\com\google\android\*. Updater-script is what directs the restore operation so it needs to match what you want to do. You can get the idea by looking at one that restores say, some data or system files, like a kernel will always restore some /system/lib/module files.
2) Since you've got some sort of zip file, make sure it matches the general format of a working cwm zip file and then just make sure step 1) is right.
3) I don't know if this is still a search for .android_secure folder on /sdcard, but if it is you're probably not going to get there from here, because the tf101 generallyl doesn't have that file since there's no need for tf101 -> sdcard app storage. For example, mine never had that folder either on internal or external storage.
4) Kernels aren't in the data or system archives from cwm, so that is possibly some sort of show-stopper too. I'm working on the cwm source today a bit to try to create a boot.img (or in the newer cwm lingo, boot.*.tar) archive. That archive will use blob and boot tools to be able (via the direction in updater-script) burn the blob onto block m*4.
I hope that helps.
Oh yeah, another thing you can try: If you wanted just the 'apps' from the cwm archive, you shouldn't even need the zip file. All you need to do is run Titanium Backup (assuming you've got it or can get it), and use the new feature in options called restore from cwm backup (or something like that). I've used it and it works fine on 3.x and 5.x cwm backups.
-- good luck
hachamacha said:
Here's a few things you could do assuming that what yowant is even in this zip file.
1) Get a working cwm format zip file and take a close look at it because you need to use it as a template if this is going to work. In particular, check out updater-script in META-INF\com\google\android\*. Updater-script is what directs the restore operation so it needs to match what you want to do. You can get the idea by looking at one that restores say, some data or system files, like a kernel will always restore some /system/lib/module files.
2) Since you've got some sort of zip file, make sure it matches the general format of a working cwm zip file and then just make sure step 1) is right.
3) I don't know if this is still a search for .android_secure folder on /sdcard, but if it is you're probably not going to get there from here, because the tf101 generallyl doesn't have that file since there's no need for tf101 -> sdcard app storage. For example, mine never had that folder either on internal or external storage.
4) Kernels aren't in the data or system archives from cwm, so that is possibly some sort of show-stopper too. I'm working on the cwm source today a bit to try to create a boot.img (or in the newer cwm lingo, boot.*.tar) archive. That archive will use blob and boot tools to be able (via the direction in updater-script) burn the blob onto block m*4.
I hope that helps.
Oh yeah, another thing you can try: If you wanted just the 'apps' from the cwm archive, you shouldn't even need the zip file. All you need to do is run Titanium Backup (assuming you've got it or can get it), and use the new feature in options called restore from cwm backup (or something like that). I've used it and it works fine on 3.x and 5.x cwm backups.
-- good luck
Click to expand...
Click to collapse
OK Ill see if the titanium backup way works. I'll report back to you if it works. Also if I do get all my apps back is there a way to get the app data?
Hi - If Titanium is bringing up the selections screen then the usual choices for each app are data/app/data+app, so yes.
The titanium back option is called "extract from Android backup" I can't do
It right now because I don't have my tf with me. But I don't think it will work because
The Android backup I made was currupted. I would get the .android_secure error
And couldn't restore. So if titanium takes the data.img from my Android I'm thinking
It won't work but if I can give it the zip it probably will. I won't be home for a couple
Hours.
thank you so much i got all my stuff back using titanium backup!
mafo5000 said:
thank you so much i got all my stuff back using titanium backup!
Click to expand...
Click to collapse
Cool! --
Congrats.

[Q] Go backup restored problem

I hope it is the right forum to ask.
I've just flashed my GS2 to JB 4.1.2 and Rooted.
Before that I made a mistake and backup my files with Go backup pro.
Now I can't restored because it is not find my backup files on the path..
I have searched in your forum vertically and horizontally and I found some thread about this problem but without a solution.
Could someone please advice me how to restore my files back?
Thank you very much.
Tomer.
tomer_inbar said:
I hope it is the right forum to ask.
I've just flashed my GS2 to JB 4.1.2 and Rooted.
Before that I made a mistake and backup my files with Go backup pro.
Now I can't restored because it is not find my backup files on the path..
I have searched in your forum vertically and horizontally and I found some thread about this problem but without a solution.
Could someone please advice me how to restore my files back?
Thank you very much.
Tomer.
Click to expand...
Click to collapse
I also backup my files using Go Backup pro. The backups by default are in external sdcard ( sdcard1). After flashing a rom you reinstall Gobackup Pro from Play Store. Launch the app and you will see the two tabs onscreen : backup tab and restore tab. Just click the restore tab and you see a prompt showing all backup files. Choose the latest files and click restore.
terrynguyen said:
I also backup my files using Go Backup pro. The backups by default are in external sdcard ( sdcard1). After flashing a rom you reinstall Gobackup Pro from Play Store. Launch the app and you will see the two tabs onscreen : backup tab and restore tab. Just click the restore tab and you see a prompt showing all backup files. Choose the latest files and click restore.
Click to expand...
Click to collapse
I tried it and still I don't have any backups on screen.. :crying:
See which storage has been set as default. ( under settings - storage)
If you backed up to SD and now internal memory is made as default, it won't show the files. (as it searches only internal memory)
- - - - - - - - - - - - - - - - - - - - - - - - - -
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Thank you for your answer.
I did backup on the SD card.
I did check and both shows no backup..
GoBackup doesnt recognize old backup files problem solved!
OK...got something for all of u punks like me out there. After installing new ROM i couldn't restore my backuped upfiles with GoBackup coz app couldn't recognize or find old backup files. I really had some important stuff there and wasn't intending to just give up. I have read many forums but everyone said to just give it up and forget it. Said hell no! So after few days of trying (reinstalling rom,gobackup,deleting caches and god knows what else i have tried) i came a cross of this lame idea . I actually opened GoBackup files on my GoogleDrive(so.... i had backup but app couldn't find it or recognize it to be able to restore it) and checked what i had installed. Made a list and installed all apps i had when i was making backup. Then i installed apps and made backup via gobackup. And here it goes... i copyed old backup files in latest backup directory , renamed old backup files using names from new files. So u get your old backup using file names of latest backup. Now app will recognize your old backup coz u renamed them. App thinks your old backup is actually latest backup. U just go into app and restore your things.
So:
1.Check out your GoBackup directory where u have your backup files (which after rooting app doesn't find or recognize) and make a list of apps u wanna restore
2.Install apps from your list
3.Make new backup of all apps u wanna restore later(old ones u had installed)
4.Now open backed up files that u wanna restore and open latest backup directory and rename old files using names from new backup files.
5.After renaming old backup files, move them into latest backup directory replacing latest backup files with renamed ones.
6.Go to GoBackup app and make restore of latest backup which is actually old one .
Found an easy solution
1. Connect your phone via cable.
2. Open SD card, locate GOBackup folder and press copy.
3. Go to local memory and press paste.
Now open GOBackup on your device, and its a miracle, all your backup there

Lost backups

So I have 3 backups saved and I want to delete them to free up space. They are there in TWRP when I go to restore them but I can not find them in file explorer to delete them. I've checked all files and they're not there. How else can I access them and why are they not showing up now?
~~~~~~~~~~~~~~
HTC one m7
TWRP v2.6.3.3
S ON
ARHD 82.0
Hi @bricktm7
This is a protected section of the recovery. Ultimately if you delete the TWRP folder, the backups will be deleted from your device as I have done this before. But in previous times people often had access to the backups via a file manager. TWRP updated with this new mode where backups would be hidden in a file manager for security purposes and maybe to stop you from accidentally deleting them.
If you wish to see the files. You can turn on "Show hidden files and folders", this may show the backups (I am not %100 sure on this but you can try it). But if you wish to delete them. I recommend you go into Recovery Mode, and delete it from the Backup/Restore section.
If you have any other questions, feel free to ask and if you couldn't understand me - Let me know and I'll try to simplify it.

[Q] Clockworkmod file in root of sdcard

I have a clockworkmod file in the root of sdcard. I can see it in ES File Explorer but I cannot see it when I connect the phone to my computer. I use clockworkmod recovery only by booting into it when I need to...not by flashing it.
Although it dissappears when I delete it in ES File Explorer, if I refresh the screen it is still there. Anyone know what this file is exactly and how to get rid of it for good?
I tried another app called File Manager by Gira.me. It shows this file as ...
Path: /storage/emulated/0/clockworkmod
Type: */*
Size: 0 B
Last modified: Unknown
Permissions: ---
MD5: Unknown
When I try to delete it it says "Not enough permissions". There must be some way to delete this file.
Boot cwm, adb shell, rm the file
beekay201 said:
Boot cwm, adb shell, rm the file
Click to expand...
Click to collapse
I get the same message in adb shell "permission denied". I finally got rid of this by flash booting into TWRP. The file manager included allowed me to delete the clockworkmod folder. However, there was now also a TWRP folder so I deleted that one also before rebooting the system.
Thanks for the suggestion.
xda6969 said:
I get the same message in adb shell "permission denied". I finally got rid of this by flash booting into TWRP. The file manager included allowed me to delete the clockworkmod folder. However, there was now also a TWRP folder so I deleted that one also before rebooting the system.
Thanks for the suggestion.
Click to expand...
Click to collapse
Stuff like this happens when recoveries (or anything that stores files on your SD), puts files in the wrong place. CWM is doing it because it's designed for Jellybean systems.
It's time to move on to TWRP.
Aerowinder said:
Stuff like this happens when recoveries (or anything that stores files on your SD), puts files in the wrong place. CWM is doing it because it's designed for Jellybean systems.
It's time to move on to TWRP.
Click to expand...
Click to collapse
I like TWRP better now but it did the same thing. After leaving Recovery, when I looked at the contents of the sdcard in a File Manager, I had a 0 byte folder that I couldn't delete. I was then forced to boot back into TWRP and delete from there. I wish these recoveries would clean up after themselves when you exit them.
xda6969 said:
I like TWRP better now but it did the same thing. After leaving Recovery, when I looked at the contents of the sdcard in a File Manager, I had a 0 byte folder that I couldn't delete. I was then forced to boot back into TWRP and delete from there. I wish these recoveries would clean up after themselves when you exit them.
Click to expand...
Click to collapse
There isn't anything to clean up, TWRP makes that folder because that's where it stores nandroids.
Try this in a terminal emulator:
su
restorecon -FR /data/media/0/*
Reboot into recovery to recreate TWRP folder, then see if you can delete from Android.
Aerowinder said:
There isn't anything to clean up, TWRP makes that folder because that's where it stores nandroids.
Try this in a terminal emulator:
su
restorecon -FR /data/media/0/*
Reboot into recovery to recreate TWRP folder, then see if you can delete from Android.
Click to expand...
Click to collapse
Do you need to be rooted for that? If you don't, the next time it happens I will try it but it's clean now so I will leave it as is. Can a nandroid backup be used just to restore app data? I don't flash custom recoveries, I just boot into them. I would boot into TWRP, do a Nandroid of my app data, then copy the contents of the TWRP folder to my PC. Then I could do a complete wipe of the phone, recreate the TWRP folder, put the Nandroid backup in it, install the apps and restore their data.
xda6969 said:
Do you need to be rooted for that? If you don't, the next time it happens I will try it but it's clean now so I will leave it as is. Can a nandroid backup be used just to restore app data? I don't flash custom recoveries, I just boot into them. I would boot into TWRP, do a Nandroid of my app data, then copy the contents of the TWRP folder to my PC. Then I could do a complete wipe of the phone, recreate the TWRP folder, put the Nandroid backup in it, install the apps and restore their data.
Click to expand...
Click to collapse
Yes, you need to be rooted for restorecon command (su). A lot of people had troubles like yours when they moved to Lollipop (me too). Now that the recoveries have been updated, it's no longer an issue for most. You may still need to run the command, though. I suppose if you did a full wipe in stock recovery, it would fix the problem.
Your question about restoring app data with nandroid is vague and could be answered in a few ways. With your issue, the data partition is actually where the problem is, so I wouldn't recommend restoring the partition.
Instead, you might use Titanium Backup or something similar to back up only app data. But you need root for that.
Easiest solution is to root, fix issue, then, if you really want to, unroot. Don't need to wipe anything.

Titanium backup just creates a "file" instead of a folder.

I have tried changing the location, rebooting my phone, changing the file to a .zip, etc. but nothing is working. When i change it to a zip and try to open it, it says the archive is damaged. When i delete the backup file and then recreate a backup, its still just a "File" type of file. Am i missing a setting or something? No matter where i place the backup it's the same thing. Im trying to turn it into a folder so i can drag in other backup files. I keep breaking the phone due to the locked bootloader, and the other 3 times titanium made a folder with all the backup contents in it.
P.S. I dont want to back it up to something like google drive. Someone always says to do that on every thread i look at

Categories

Resources