Today i ended up installing a new rom on kindle fire, everything worked very well, but i have a little issue now.
Just to be safe i decided to do a backup with TWRP after the installation of CyanogenMod. Previously i did a backup of the stock rom.
Now if i TWRP -> Restore I'm able to see only the last backup done, and if i use a file browser i'm only able to see the old stock backup.
What is happening? I wish i could delete the old backup to get back the 2.1 GB it occupies
Edit:The issue is not related to the device, but to the different android version of the rom. Previously my backups were in /TWRP/BACKUP, now in mnt/shell/emulated/TWRP/BACKUP
That path should be a symlink to the exact same place. If you updated twrp recently then its possible it might be part of the fact that twrp reads serial numbers now and started only showing backups in the same folder as the serial numbered folder rather than the 0000000000 folder.
Code:
you need to use root browser for this to work
Related
I am new to this whole rooting thing and have some questions about rom manager and nandroid backup. I have the ROM manager app but have not done the backup yet. My question is if i make a backup with ROM manager is that essentially the same thing as a nandroid backup???
I also have titanium backup and have backed up all my apps and stuff. So if i do load another rom do i use titanium backup to reload the apps that i have after i load the new rom?
my phone was rooted with z4root, i have superuser, have ran titanium backup, and have ROM manager.
EDIT: phone is a moto droid 1
EDIT2:i tried to follow this guide ( im unable to post the link but its on androidpolice forum )
I was able to create an image and then went to make my nandroid backup. i followed the steps and it just booted my phone like normal and didnt create the folder. Do i have to have my phone mounted while doing this? Do i have to do anything to the img files that were created?
EDIT:3 I finally was able to make my nandroid backup. I guess i will look into ROMs now.....
thanks
Hi,
I'm running Android 4.2.2. on my HTC One with Clockwork 6.0.3.1.
When I'm doing nandroid backups, they are finished without any problems. I can find them in CWM and restore if I want to. My problem is that I cannot find them on my OS browser. I can neither find them when browsing my phone on my PC. The folders appear to be empty and so I cannot backup them on my pc...
Anyone having this issue?
Thanks in advance,
Ben
had same issue yesterday while flashing ARHD 10.2
i'm still searching. it must be somewhere
See in data/media or in sdcard/0 and the cwm folder...
I found it, got help in another topic!
You need to use a root explorer on your phone.
/data/media/clockworkmod/backup seems to be the location
you made my day
I switched from twrp to cwm two days ago... Using a root explorer (actually i tried more than one), hidden files are shown but all i see in the cwm folder is a file called '.recovery version'
The recovery itself can see and restore my two nandroids... :what:
It seems my TWRP has changed the backup location after flashing. After installing 4.2.2 (ARHD) I wiped everything because I was coming from stock. But I got no idea were my backups are stored, I created a Nandroid today when flashing ARHD 12.0 and noticed it did not show my previous backups.
The backups are not being saved to sdcard\TWRP but another location and I cannot find it, anyone know where the new location is? using TWRP 2.5.0.0
I checked
legacy\twp
emulated\0\twrp
TWRP shows today's backup I just can't figure out were that is
jebise101 said:
It seems my TWRP has changed the backup location after flashing. After installing 4.2.2 (ARHD) I wiped everything because I was coming from stock. But I got no idea were my backups are stored, I created a Nandroid today when flashing ARHD 12.0 and noticed it did not show my previous backups.
The backups are not being saved to sdcard\TWRP but another location and I cannot find it, anyone know where the new location is? using TWRP 2.5.0.0
I checked
legacy\twp
emulated\0\twrp
TWRP shows today's backup I just can't figure out were that is
Click to expand...
Click to collapse
Not sure if you ever got an answer to this question, but for me they were not on the sdcard but in root/data/TWRP/BACKUPS/...
and for anyone else with this problem: simply delete the TWRP folder on the sdcard and then go back into recovery and TWRP should now find the right place to save backups.
In TWRP - advanced -file manager to check the folder /data/media/twrp
Hi Guys!
I've just flashed my HTC One to the ViperOne ROM. And since i backed up all my apps beforehand with ADB i was wondering if i could use the backup file that i have on my PC taken with the stock ROM, on my new rom?
Cheers!
What do you mean by 'backed up using adb'? Did you copy files from your phone to your computer?
deeevan said:
What do you mean by 'backed up using adb'? Did you copy files from your phone to your computer?
Click to expand...
Click to collapse
Thanks for the fast reply!
I've followed this vid through the root process where it was suggested to do a backup as seen here: http://youtu.be/qpj6dEMn9dw?t=2m45s
So i basically used ADB to backup apps settings etc and it saved a file on my comp. And i was wondering if i could use that even if made on a different ROM.
I'm out and on my phone, don't really want to watch a video to find out what command you ran. I assume it was a whole system backup like a nandroid.
Because you've now installed a different ROM, you only want to restore certain parts of your backup ie. You just want your user apps and data restored. If you restored your whole backup, you'd wipe Viper ROM and be back where you started.
Have a look at TitaniumBackup and Helium which will allow you to just backup and restore apps. I use Titanium and it has options to extract from a nandroid or adb backup.
I ran it and it seems to have worked. Still on the Viper rom atleast!
But thanks for the help!
Just read up about adb backup. Thanks, learnt something new today.
You should look at Titanium as it will give you finer grain control over restoring.
So it happened i faced this challenge and i found a way to go about so i decided to share.
JUST flash a ROM for your phone.
Create a nandroid backup.
Now place the backup folder you originally wanted to restore in the TWRP Folder the backup just created.
Boot into recovery, then restore and flash your nandroid backup as its suppose to be.
The ROM may not be showing up in the backup folder if the folder serial # doesn't match the phone's serial #?
audit13 said:
The ROM may not be showing up in the backup folder if the folder serial # doesn't match the phone's serial #?
Click to expand...
Click to collapse
Yes
Wouldn't it be easier to rename the TWRP backup folder with the corresponding serial # and then restore?
audit13 said:
Wouldn't it be easier to rename the TWRP backup folder with the corresponding serial # and then restore?
Click to expand...
Click to collapse
In my case, the serial number was the same because it was still the same phone but anytime i place the backup folder in the serial folder , TWRP couldn't find it and restore , so i backed up a rom and placed it in that backup folder and i was able it find and restore. But with what you said yes that would be easier if your the serial numbers were different or you changed your phone but that wasn't my case.
Weird because I have used TWRP many times before and, when I create a backup, I move the backup to my computer. When I want to restore it, I mount the backup folder in twrp, copy the backup to my N5, and TWRP always finds the backup and restores it. I have used the same procedure with my LG G2, Samsung S4, Samsung S3, and Samsung Note 3.
audit13 said:
Weird because I have used TWRP many times before and, when I create a backup, I move the backup to my computer. When I want to restore it, I mount the backup folder in twrp, copy the backup to my N5, and TWRP always finds the backup and restores it. I have used the same procedure with my LG G2, Samsung S4, Samsung S3, and Samsung Note 3.
Click to expand...
Click to collapse
Exactly , thats how its suppose to be
Not sure why it doesn't always work for your phone.
it happened when i flashed a rom update and decided to go back