So I ended up smoking my old phone the other day when using it as a signal generator to test some amps on the bench. The battery was getting low so i plugged the charger into the laptop that I also had the osilliscope plugged into. - bad idea. ground loop fry.
Anyways i have my new phone here, rooted with TWRP installed. Stock kit kat via .kdz.
The problem I am having is the phone will not allow me to choose the backup I have of my old phone.
Just for curiosity I made a fresh backup of the other halfs phone, loaded it to the SD card and I get the same results.
It seems TWRP will not restore any backups unless it was a backup of that particular phone. Iv never had this issue before, I have to be doing something wrong.
I made a backup of the stock OS, then flashed a MM rom to it, got everything working and backed that up also.
Both the backups I made I can choose to restore. I notice each phone will make a new folder on the sd. So i moved the other backups to the folder that was made for this phone, but no luck there.
Any ideas WTF is going on anybody?
No idea. The only thing I was going to say - moving the old backups to where the new ones are, is the only thing I've ever had to do.
larski156 said:
So I ended up smoking my old phone the other day when using it as a signal generator to test some amps on the bench. The battery was getting low so i plugged the charger into the laptop that I also had the osilliscope plugged into. - bad idea. ground loop fry.
Anyways i have my new phone here, rooted with TWRP installed. Stock kit kat via .kdz.
The problem I am having is the phone will not allow me to choose the backup I have of my old phone.
Just for curiosity I made a fresh backup of the other halfs phone, loaded it to the SD card and I get the same results.
It seems TWRP will not restore any backups unless it was a backup of that particular phone. Iv never had this issue before, I have to be doing something wrong.
I made a backup of the stock OS, then flashed a MM rom to it, got everything working and backed that up also.
Both the backups I made I can choose to restore. I notice each phone will make a new folder on the sd. So i moved the other backups to the folder that was made for this phone, but no luck there.
Any ideas WTF is going on anybody?
Click to expand...
Click to collapse
Look in the TWRP/Backups folder for your new backup. It should say VS985 then some numbers. Copy this folder name to the backup that you're trying to restore then TWRP should find it.
Related
Just put my old SD into a new Eris and I'm trying to nandroid (I've rooted)
error: run 'nandroid-mobile.sh restore' via adb !
is the error I get.
Can someone help? I've tried a lot of things. The phone's fully charged and plugged in.
EDIT: I fixed this by deleting my nandroid folder after backing up my backups, doing a nandroid backup, deleting that backup, putting my old backup there and then restoring.
Thanks anyway.
I just tried to do this as well. Same thing happened to me. I'm guessing the backups are only good for the specific phone they were backed up on. If anyone knows a way around this, could you share? I have a few backups from my old phone and would hate to have to start over.
read the Edit: portion of the OP above
I've had this happen a couple times. Usually, I get it when the battery is low. Perhaps an internal protection? The other times, for some reason it won't create an MD5 file. The only way around that is to manually create one. I'm not sure what caused the initial problem here, but it's nice to see you got it fixed.
To clear this up, this can happen when the battery is low or possibly when trying to nand on a new phone/ newly flashed recovery.
I solved it by
-- saving everything inside the nand folder I wanted to restore.
-- Deleting the nandroid folder from my sd card
-- Booting into recovery and doing a nandroid backup
-- Deleting the contents of that nandroid backup and replacing them with my nandroid from the first step
So last night, I copied a nandroid I had previously made from my computer onto my phone. When I tried to restore it, it aborted b/c the md5 sum didn't match. Strange. So I copied a different nandroid onto the phone, tried to restore that one, same thing- md5 mismatch.
What's going on there? Is the file being corrupted during the move to/from the phone? That seems like it'll make storing your old backups on your computer kind of useless.
STaria said:
So last night, I copied a nandroid I had previously made from my computer onto my phone. When I tried to restore it, it aborted b/c the md5 sum didn't match. Strange. So I copied a different nandroid onto the phone, tried to restore that one, same thing- md5 mismatch.
What's going on there? Is the file being corrupted during the move to/from the phone? That seems like it'll make storing your old backups on your computer kind of useless.
Click to expand...
Click to collapse
Make a new nandroid and immediately restore it. If it works move it to your computer and then back to your sd and attempt another restore to see if you get the same problem with a nandroid you KNOW was good before you moved it.
EDIT: you didn't still have your phone plugged to the computer when you tried to do the restore did you? If so try restoring it again unplugged. Its known to cause issues.
Sent from my cm7 Aria.
Yea I did end up doing that, I immediately restored the backup, it worked, so I went ahead and flashed a new ROM. When it came time to restore, it said something along the lines of "error writing boot image" and failed.
I ended up just using Titanium to restore everything, but it's worrying that my stored backups might not work.
EDIT: Oh, having it plugged in may have been the issue... I'll keep that in mind.
Did you rename the folder that the backup img files are in? They aren't supposed to be changed (i.e., "2010-11-27.21.30.28").
drumist said:
Did you rename the folder that the backup img files are in? They aren't supposed to be changed (i.e., "2010-11-27.21.30.28").
Click to expand...
Click to collapse
Nope, didn't touch them. Just copied to and from the computer.
Today is a very sad day for me. Getting out of the car, my note slipped from my hands and fell perhaps 18 inches and landed face down on the parking lot. When I went to pick it up, the glass was a complete mess.
I still have functionality on my screen, although I have to be extremely careful to avoid slicing my finger on the exposed sharp edges of the glass.
I just rooted my phone and am (obviously) new to Android from years of being with the iPhone. I had replaced a couple of those due to theft and a single drop incident, and he backups and restore were very simple.
I have Titanium backup installed, and the phone is rooted using the stock ROM. Can someone please be so kind as to give instruction on performing a complete backup including all SMS/Call Logs/Apps/Data/Pictures, etc?
I will have to send the phone back to Squaretrade and will lose all information, so this is vital for me before sending it back.
Thanks in advance for the help.
You have clockwork recovery installed yet? if so go to recovery mode then hit backup..it will make a nandroid backup in your external sd card.
sailador said:
You have clockwork recovery installed yet? if so go to recovery mode then hit backup..it will make a nandroid backup in your external sd card.
Click to expand...
Click to collapse
Just like he said, get CWM installed. Flash it you the Note and then make a nandroid backup to an external sd card, or copy the file to your computer. Then restore it when you get the new note.
Sent from the best phone in the world Galaxy Note!!!
The first two posts are your best bet. You can use Titanium Backup and do a batch backup. I don't think Titanium will back up everything though, for example I don't think it does SMS or call logs. Not 100% sure of that though.
Nandroid
Nandroid is probably your best bet. If Titanium Backup does not back up SMS logs there is a program called SMS Backup and restore that will backup all your sms messages to your external SD which is compatible with most messaging clients, I know it works with stock messaging, chomp, and gosms, not sure about handcent.
I haven't installed CWM yet. I will get that done and report back ASAP.
center19 said:
I haven't installed CWM yet. I will get that done and report back ASAP.
Click to expand...
Click to collapse
Also, copy any folder in sdcard folders out to computer just in case the methods above go wrong (not likely) But better safe than sorry.
Sorry to hear that
For those of you who flash roms regularly like myself, is there a way to not have to download these large game files every new rom flash? When i installed Bard's Tale i downloaded the HD version (around 3gb) and chose the option to install to SD Card thinking ok obviously this will download to SD card so when i flash a new rom i won't have to download all this again? Well wrong, flashed a new rom, restored via TWRP Data backup, still have to download Bard's Tale from scratch again. Obviously also doesn't save my game data!
Anyway to get around this and actually SAVE these games to SD Card so when i flash a new rom i don't have to download the game from scratch again?
I thought doing a data backup via TWRP and restore would also restore this type of stuff? Does it only restore the game saved data such as my progress in the game for mobile games with this kind of backup?
Might, maybe, you better off doing back-up for that while being booted into OS, with something like TitaniumBackup or MBP???
Sent from my HTC One X+ using Tapatalk 2
I had the same issue you mentioned when doing a rom flash with TWRP backup that I restored via Titanium Backup.
The games in question were "pinball arcade" and "Zen Pinball", so thankfully the data was only 500mb or so.
One way to get around this issue is to backup the data on your computer, however, that is not very convenient or fast.
The other way you *might* be able to get around this is by changing the names of the folders that the game data is in. I think the TWRP backup overwrites it for some reason because other data on my SDcard is still there after a rom flash & wipe.
So my theory is that by just changing the folder name or even moving the folder to a different area, you might be able to just copy it back to its proper location after you have flashed and restored your TWRP backup.
Sadly, I've not gotten around to actually testing this theory out myself, but, when I do I'll make sure to update everyone. Probably won't be until a new version of the Elegancia Rom comes out and I have to update, lol.
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.