Long Story Short: On a CM12(Nightly) Moto G(Falcon) that had to be thoroughly reformatted after an unexplained disaster, I'm trying to use a TWRP backup made earlier and ensconced on my computer to restore my phone. After using the backup function once to establish the filepath, I transfer the backup to the backups folder in TWRP and use the restore function. At first, it said that it was a f2fs backup or something, but after reformatting to match it just hangs when trying to restore the data folder(without a specific error), and throws a "Failed" message. Backup doesn't work, phone gets one step closer to being launched out the window. I've thoroughly reformatted everything, reflashed recovery, and double checked all the catches I know of(the backup is under 2.5 gb for instance).
I'm stumped. Should I give up at this point? Is the backup just gone(especially given that it's connected to how this all got started)? Is there nothing I can do with having captured all the folders onto my PC?
(Full story)
While fiddling around with Moto G 2013(falcon/xt1032) running CM12 Nightly this morning I decided I should take a backup with TWRP (which I had also specifically installed this morning because of rumors of it working with encryption). The moment after I rebooted from the (supposedly successful)backup, my phone got stuck in a nasty bootloop, would even reboot from attempting to start recovery half the time. After a lot of cursing and trial and error I successfully formatted everything and reinstalled TWRP, and that stopped.
I had even managed a mass evacuation of my files (simply dragging everything off with windows explorer) to my computer. This included that fateful backup that TWRP made, that didn't seem to be worse the wear. There are some things on here that I'd rather miss (especially since I just cleaned out my PC based backup program yesterday), so I'm trying to restore my phone from there.
Related
Last night, I installed TW 4.5/TW Manager. I did a ClockworkMod backup first. I decided to restore it.
However, after restoration, the phone is in a factory state. Save for my lock pattern, which it remembered, the phone is in first-run setup mode, all my home screen layouts are gone, all my apps are not in the aop drawer except those the G2 ships with. Contents of the virtual SD card like photos are still there.
I tried restoring my only other CWM backup (a November backup that previously *restored ok* to undo a MIUI test, for example), but this, too, now boots in to the same state.
What has gone wrong here?
And is there any way of getting back the system that I assume/d is/was in the CWM backup files?
If I can't guarantee I can restore a CWM backup, it makes the world a very scary place to be.
Hi all, first of all, I apologize if I've posted in the wrong place.
I was never an "expert" with Android but I have used the EVO 4G for the past two years and just upgraded to the Galaxy S3. I rooted it this morning and have been playing with it. I wanted to flash different ROMs and try them out but I ran into some problems when trying to create a nandroid backup.
First I tried the usual method via ROM Manager. When I rebooted into Recovery, instead of backing up it just loaded the main CWM screen and at the bottom a message said it wasn't able to load the ROM Manager script and to make sure I have ROM Manager 4.4.0.0 or above (which I do). Then I tried to make a backup from CWM itself and after it was done, the date was all messed up as it thought it was 1970. Also when I booted back and loaded ROM Manager, it wasn't able to see the backup I made. I did try to make a backup in both my internal and external SD Card but didn't make a difference.
Please advise, thanks!
Don't use ROM Manager, no real need to use it for backups. Boot into recovery and manually backup (like you did). The date issue is a known CWM issue and will be resolved by them sometime soon I'm sure. The backup you did should be fine. I've backed up a few times (with the same date issue), but never tried restoring yet. Net Net, when you ran the backup manually (even with the borked date) you are good.
PS. I only use ROM Manager to rename the backups, as if I tried to manually change the name via a file explorer the file became invalid. If I changed the name via ROM Manager the backup was perfect.
I have also had issues with creating a nandroid. I have the verizon version so it probably has to do with it.
I have v 5.8.4.8 and installed it through ROM Manager.
I tried a nandroid and it errored with
Error while backing up boot image.
I'm guessing that it is known and has to do with the locked bootloader. But was just seeing if I anyone else had the issue.
johnhazelwood said:
Don't use ROM Manager, no real need to use it for backups. Boot into recovery and manually backup (like you did). The date issue is a known CWM issue and will be resolved by them sometime soon I'm sure. The backup you did should be fine. I've backed up a few times (with the same date issue), but never tried restoring yet. Net Net, when you ran the backup manually (even with the borked date) you are good.
PS. I only use ROM Manager to rename the backups, as if I tried to manually change the name via a file explorer the file became invalid. If I changed the name via ROM Manager the backup was perfect.
Click to expand...
Click to collapse
I used to use ROM Manager to backup before mostly because as you have stated I could name the backup
Thanks for letting me know that even though the date is broke it's still good. I get a bit cautious when it comes to backing up
Alright...
I had the Shishir rom on my phone for many months and it worked very well. Tonight I dropped my phone (has happened many times before with no repercussions) while it was plugged in and the rom would no longer load on start up. The boot sequence would run all the way through and get stuck on the four colored X.
So I booted into CWM and made a backup because I had not previously backed up my contacts recently. I transferred this backup to my pc. I restored backup and now my phone works fine. However all of the contacts and messages are gone.
So I ask, I plead, is there any way to manually extract the contact database from the CWM backup image?
-drmorbo
Titanium backup
Sent from my Galaxy Nexus
I tried it. Titanium sees the backup but says there is nothing in it...so was all the data corrupted the moment the phone fell and the backup is worthless or..?
This is by far the most painful flash I have ever had to do. Let me explain...
I have the htc one m8 with the ViperOne software. Recently they released the Android L version so naturally I downloaded the new 4.0.0 Viper rom and upgraded my firmware. Since I have a lot of data I backed it up using HTC sync manager which has been flawless. I also made a TWRP backup. I then cleared my data and flashed the rom flawlessly. Once that was done I went to restore all my data (pictures, music, settings, wallpaper, etc) using Sync manager. However, everytime I plugged it in and went to restore my data, it would freeze at about 1-7% and I would have to close it. It wouldn't work.
Naturally I restored my phone from TWRP and went into Titanium backup and made a backup. It took awhile, but it was done. I flashed the rom again but instead when I went to restore things from Titanium backup, it wouldn't recognize my data. It just said "searching for application data." I even changed the detection settings, but nothing.
Once again, I restored my phone from TWRP and this time decided to back up Titanium backup to Google Drive. It took an hour but it worked. I flashed the rom again and went to download the Drive zip file to my SD card.
Think I'm homefree right?
Nope, God played his cruel trick on me and instead my computer froze everytime I tried to transfer the file to my SD card. Now my computer is constantly freezing, I can't get HTC sync manager to work without freezing, titanium backup won't recognize my backups no matter what I do. This has been painful.
So here I sit, wondering, what in God's name do I do?
Over the course of the last two years I have flashed the *expletive deleted* out of my Nine and gone through the set up countless times, because I wanted to, and mostly with childlike enthusiasm. Sometimes, like today, it's because I have to. I seem to fail more often than not restoring from TWRP, and recently sometimes with flashfire free version. I never seem to have a problem "testing" the backups after creation, without any major changes they restore without issue. My problems seem to arise after flashing a new rom or preview and then trying to revert back to my previous restores. More often than not these fail on me and I find myself , like today, looking at the set up screen.
What ways (free) work best to save/restore roms, and what the hell am I doing wrong with my back ups? I have a basic grasp of ADB/fastboot. But it appears I have just enough info to be dangerous.
I blame the Vendor partition...
I've not had any problems with TWRP and restoring. I will add, however, that I don't backup the vendor partition. I have had problems with that before. I don't seen any real need to back up the vendor partition, though, so I just exclude that. I keep copies of the vendor image for the ROM that I flash. If I need to restore a backup, I restore it and then flash the original vendor image for that ROM version again.
I don't back up at all any more now that Google is able to reinstall all your apps when performing a fresh install. Just install the rom, choose the restore and let Google do its thing whilst I crack on with other things.
I've had several issues with TWRP backups on 6.x and 7.x, so now I use FF over ADB to make a "NORMAL" backup to my PC. I also use TiBu for apps and store a zip file of the complete TiBu folder on my PC.