Related
Does anyone in here know if I can safeley reload my Sprite Back-Up after a ROM Upgrade without screwing-up details of the ROM-Upgrade ?
I mean: If I understand this right, after Booting parts of the ROM ar loaded into the RAM, which could be overwritten.
Or am I totally off here ?
After a rom upgrade, you should never restore a complete backup, regardless of the backup program you use. With sprite, it is easy to do a restore of individual databases (appointments, contacts, email, sms etc), as well as the document folder. The other option is to use the "device upgarde" functionality of Sprite Backup, but for that to work, you will need to make an image of the machine with the new rom I believe, and without anything installed. (but for that you need to check the manual).
You should never restore a full backup, since you will be restoring parts of the old ROM in the process.
I only use Sprite backup as a fall-back in case of a problem with a Rom update.
Even if you select the "allow upgrades" option, it can overwrite some of the data that you have just changed in the upgrade.
I have loaded all of my apps and data that I must retain on a memory card and I just reload them from it.
Hope this helps........Later
quote="jofeuerstein" ]Does anyone in here know if I can safeley reload my Sprite Back-Up after a ROM Upgrade without screwing-up details of the ROM-Upgrade ?
I mean: If I understand this right, after Booting parts of the ROM ar loaded into the RAM, which could be overwritten.
Or am I totally off here ?[/quote]
Here is how I see it: Any file that is not ROM-based will be pulled by Sprite Backup.
Even though a hard-reset will reload all the Extended ROM CAB files, they are still in the Storage/Program Memory and can still be replaced, deleted, etc. They are supplemental to the ROM files from the CE ROM core.
A good experience is when I upgraded to Build 3900 on my Extended ROM and restored a Sprite Backup file afterwards and noticed it went back to 3500. The BT*.* files in the Windows directory were backed up, and thus restored, overwriting the work done by the Extended ROM load.
The best thing to do is "move along" your backup file with your upgrades.
If you decide to recook your Extended ROM, upgrade CAB files or builds, then keep that upgrade CAB file handy to run again. I would highly recommend using a program such as OCP Software's WinCE CAB Manager to look into the CAB files you are replacing to see what files and registry entries get directly affected.
Bottom line method for me is 1. backup your PPC, 2. update the Extended ROM, 3. hard-reset, 4. restore the PPC, 5. reapply any new CABs from the Extended ROM, 5. rebackup the PPC.
By the way, the Upgrade works especially well when you have a new CE ROM that has new ROM files, such as Windows Media Player 10 (if and when it comes out). According to the instructions on Sprite's site, you run the Upgrade utility on the clean (hard-reset) image with the OLD ROM, perform the upgrade, then restore your backup WITH the Upgrade Data.
Thank you. Sounds very logical. A complicated process, but it beats reconfiguring the MDA after an Update by several hours ...
Good that all the people who envy us for our "MDAIII" don't know how much time we waste getting these machines to work ....
hdbueller said:
I have loaded all of my apps and data that I must retain on a memory card and I just reload them from it.
Hope this helps......
Click to expand...
Click to collapse
you mean copy the "program files" folder to SD-card and the load it back ? or how :?:
You can copy all the CAB files from the C:\Program Files\Microsoft ActiveSync folder onto the SD card for safekeeping, or look for a program called CabBackup, which has been proven useful in many a situation.
Hey all,
Are nandroid restores specific to one particular device or can they be interchanged between two G1's? I have a spare G1 that I play around with that has root while my other G1 doesn't have root. I am thinking about rooting the other one and wanted to know if I could just go through the rooting process, (radio, spl, cyanogen recovery etc) throw on a cyanogenmod or JF, then do a nandroid restore from the spare device with all my settings on it. I know that nandroid creates a unique numerical folder that has your latest backup in it so I wasn't sure if this folder would be seen by nandroid on a different phone.
Any thoughts?
EDIT:
Just wanted to update this thread in case anyone else wanted/needed to do this. As I suspected, I ran into folder name problems when trying to copy one nandroid restore to my spare phone and trying a restore. There is a simple fix however....
1) Perform a nandroid backup on the phone you WANT to backup.
2) Copy that nandroid folder from the phone to your PC.
3) Perform a nandroid backup on the phone you DON'T WANT to backup.
4) Copy that nandroid folder from the phone to your PC.
5) Compare the nandroid subfolder name (should be alpha-numeric starting with HT) of the backup you want to the name of the one you don't.
6) Change the name of the nandroid subfolder on the backup you want to restore to the same name of the folder you don't want. This way you fool nandroid into thinking that the backup was originally done on that phone.
7) Copy the entire nandroid folder (with the newly changed subfolder name) to the sdcard of the phone you want to restore.
8) Boot into recovery (power+home) and perform the nandroid restore. If the restore fails, you probably don't have the correct subfolder name. Return to step 5 and 6.
9) If the restore is successful, reboot and you should be all set!
Good question. I wouldn't have thought there would be issues with it bar of course your settings etc but then a wipe before would resolve that. Just make sure to do what you've said though (upgrade radio, SPL, recovery etc) first.
DirectMatrix said:
Hey all,
Are nandroid restores specific to one particular device or can they be interchanged between two G1's? I have a spare G1 that I play around with that has root while my other G1 doesn't have root. I am thinking about rooting the other one and wanted to know if I could just go through the rooting process, (radio, spl, cyanogen recovery etc) throw on a cyanogenmod or JF, then do a nandroid restore from the spare device with all my settings on it. I know that nandroid creates a unique numerical folder that has your latest backup in it so I wasn't sure if this folder would be seen by nandroid on a different phone.
Any thoughts?
Click to expand...
Click to collapse
It won't upgrade your SPL, radio, and recovery. If you look in the nandroid folder, you'll see exactly what is backed up. I think its the /system folder and the /data folder as well as something else. But if you have another phone that is already rooted and has the correct SPL, radio, and recovery, this will work.
Should be fine then as he's planning on doing the usual steps up until flashing the desired ROM of choice. Tell us how it goes DirectMatrix and if it works, please change your thread title to include [SOLVED] so we all know ^_^
NeoBlade said:
Should be fine then as he's planning on doing the usual steps up until flashing the desired ROM of choice. Tell us how it goes DirectMatrix and if it works, please change your thread title to include [SOLVED] so we all know ^_^
Click to expand...
Click to collapse
Gonna start rooting the other phone now so I'll keep this thread updated with whether nandroid backups are swappable between phones. I hope so as that will save me quite a bit of settings/data calibrations.
@h.nocturna... LOL, you have been dealing with n00bs too long in the Q&A section....of course nandroid won't upgrade my radio, SPL, and recovery, but I had a good laugh anyways. Thanks all for the advice
Hello,
I recently decided to update my ROM, radio, etc. I had previously had an Eclair rom. I updated the radio, and all other assorted stuff and flashed to a EZgingerbread rom.
In my zeal, I neglected to export a copy of my contacts. I did, however, remember to make a Nandroid backup of my old eclair rom.
So, I attempted to follow some tutorials in copying the file
/data/data/com.android.providers.contacts/databases/contacts2.db
using the adb command
cat /sdcard/contacts2.db > /data/data/com.android.providers.contacts/databases/contacts2.db
from my old backup to the corresponding folder on my phone. However, the phone does not show my contacts, as it seems to reformat the contacts2.db when I reboot the phone, as evidenced when I take a look at the db file on the phone.
Help is appreciated, thanks!
Small edit: I tried restoring the backup, but it gets stuck at the G1 boot screen, reboots, and shows the g1 screen again. So I can't extract my contacts that way. Probably because I loaded a new radio/hboot?
One Question! You have GMail Account Tied to G1, right? All your contacts should be saved in that GMail Account.
You might try performing this same copy while in recovery mode,
so that the overwrite of the file with the 'live' database doesn't happen on reboot.
GiantCrab said:
Hello,
I recently decided to update my ROM, radio, etc. I had previously had an Eclair rom. I updated the radio, and all other assorted stuff and flashed to a EZgingerbread rom.
In my zeal, I neglected to export a copy of my contacts. I did, however, remember to make a Nandroid backup of my old eclair rom.
So, I attempted to follow some tutorials in copying the file
/data/data/com.android.providers.contacts/databases/contacts2.db
using the adb command
cat /sdcard/contacts2.db > /data/data/com.android.providers.contacts/databases/contacts2.db
from my old backup to the corresponding folder on my phone. However, the phone does not show my contacts, as it seems to reformat the contacts2.db when I reboot the phone, as evidenced when I take a look at the db file on the phone.
Help is appreciated, thanks!
Small edit: I tried restoring the backup, but it gets stuck at the G1 boot screen, reboots, and shows the g1 screen again. So I can't extract my contacts that way. Probably because I loaded a new radio/hboot?
Click to expand...
Click to collapse
IANADBA, but you're probably running into an incompatibility in the data structures between the .db files. I'll bet the db versions between Eclair (I don't even remember what Android version that is) and GB are quite different. You might be able to get away with dumping the data from one and loading it into the other using an appropriate sqlite app.
Of course, there may be an very easy way I'm not aware of, in which case I am prepared for maximum flamage.
Jeff
I'm about to flash stock 4.4.2 prior to flashing 4.4.4 soak ... and I can't figure out how to do a complete backup of phone, in case things get screwy.
I can't do nandroid; not enough space.
I tried rsync, but couldn't get rsync running on phone as server.
I'm trying to just copy everything over with SFTP, but there are so many duplicate folders...
/storage/emulated/0 =
/storage/emulated/legacy =
/data/media/0 =
/mnt/shell/emulated/0,
etc etc.
and they don't appear as symlinks.
I tried 'adb backup ' etc ... but I don't want an ".ab" file that I cannot look into.
Is there an easier way?
thanks
d0g said:
I'm about to flash stock 4.4.2 prior to flashing 4.4.4 soak ... and I can't figure out how to do a complete backup of phone, in case things get screwy.
I can't do nandroid; not enough space.
I tried rsync, but couldn't get rsync running on phone as server.
I'm trying to just copy everything over with SFTP, but there are so many duplicate folders...
/storage/emulated/0 =
/storage/emulated/legacy =
/data/media/0 =
/mnt/shell/emulated/0,
etc etc.
and they don't appear as symlinks.
I tried 'adb backup ' etc ... but I don't want an ".ab" file that I cannot look into.
Is there an easier way?
thanks
Click to expand...
Click to collapse
Copy enough stuff off the internal memory to do your backup. Then copy the backup to your PC....then put everything back.
A full backup should only take a couple gigabytes. Moving your pictures, or music or whatever is taking up all that space should suffice.
If you are returning to stock, everything will be erased anyways....unless you modify the XML or manually flash and skip the erase userdata command.
Regardless, your backup won't be fully usable once you are on 4.4.4. If you restore it, your partition table and/or bootloader will be mismatched and you will likely get FCs if you restore back to it.
Are you on a custom ROM or something?
Additionally, if you PROPERLY flash back to stock 4.4.2 (erasing userdata - which is advisable), there's nothing that will go 'screwy'...
What variant are you on? If you are using an XT1060, there is a better way.
samwathegreat said:
Copy enough stuff off the internal memory to do your backup. Then copy the backup to your PC....then put everything back...
Are you on a custom ROM or something?...
What variant are you on? If you are using an XT1060, there is a better way.
Click to expand...
Click to collapse
Ah, so you're saying, remove photos/videos/etc so there's room for a full nandroid, yes?
No custom ROM; I'm on XT1056.
d0g said:
Ah, so you're saying, remove photos/videos/etc so there's room for a full nandroid, yes?
No custom ROM; I'm on XT1056.
Click to expand...
Click to collapse
Yes, it will erase it - unless you modify the XML or manually flash and skip the erase userdata command. I suggested that you take a nandroid backup, then reboot. Connect to your PC, and copy the entire nandroid backup to your PC.
Regardless, you should connect the phone to your PC and save everything on the SDCARD.
Use Philz cwmr & you can do a backup right to your computer (USB mount or OTG). Or use online backup apk (play) & do a nandroid right from your home screen to your OTG card.
As indicated.... Kind of a waste of time. If you go to 4.4.4 then try to nandroid restore to 4.4.2...assuming it even works... You'll be on the wrong bootloader. Then you risk many issues, the worst being a possible brick if you take an OTA down the road... Or for another reason.
Just backup apps and data if you wish... With titanium backup for example... Then if you want to be safe, transfer all your pics and what not, and the titanium backup file to your pc. Then upgrade.
You're pretty much stuck with 4. 4.4.... So a nandroid is pretty much not needed.
Use 'adb pull' to get whatever you want off the phone onto your computer.
Hey Everyone,
I am new to XDA forums,(have used it for troubleshooting in the past but just registered today)
I am also new to android and linux, personally i don't use my phone for anything other than calls or games(i mostly do pc's), however my wife does a lot, she has written her own code, does mods, etc...., and we are both stumped. I am asking this on her behalf, due to a terminal illness she has lost the ability to do several things. On April 30th the lollipop update was pushed to her Note 4 (T-mobile US branded) and it wiped out all of her app data as well as her entire SD card. My question is in 2 parts one regarding the TWRP backup for this phone, and another regarding recovering the SD data from this phone(please let me know if i need to break this out into multiple sections of the site).
We have a TWRP backup that was compressed and loaded onto her cloud storage on 4/27/15, and we are unable to figure out how to get TWRP to recognize it without giving an error about the binary code or just not working period. Here is what we have tried(On advice not just from other XDA posts but various android forums as well)
Using TWRP(7zip for unpacking and repacking)
1. Downloaded the TWRP back up into windows
2. Renamed all files of the back up to be .tar, with the exception of boot which was converted to .img
3. Added Meta-Inf file from what was suppose to be stock ROM( she was not running a custom on this phone)
4. Re-archived everything back into Zip and sideloaded.
result : Error in binary code
Using Odin
1. Converted recovery (file only from backup) to md5 using Cygwin
2. Flashed using Odin
Result: Gained back a few programs but no app data or text histories
We have also tried varying versions of this, i.e. converting extra files or renaming extra files and receive the same issue. I am wondering if it is just an issue with the cloud stored compressed backup(or more likely i dont know what im doing)?
Second question comes from above, I was able to recovery all of the data from the SD card(everything was stored here, app data, recovery files, imgs, everything). When recovering the data it split everything up so all the sub peices of each recovery file are spread out is there a way to combine the individual file parts that were recovered from the SD card into functional android files again?
As i mentioned before i have never really dealt with this type of thing before but i want to try and fix this for her as between the 2 issues she has lost 5 years of data.
Thank you so much for your responses.
Hi, what you need to do is put the backup back into the exact same form it was before, an uncompressed, unzipped folder, then put it into the exact directory where TWRP puts backups when it makes them, and then in TWRP choose the option to restore. If you put the backup in the correct directory, TWRP will see it and allow you to choose it to restore it. Basically you just wanna put the backup back where it was before and then restore it in TWRP.
I wasn't sure if you had done this or not. If you have the backup folder with all the contents in their original form, it should work. I've even moved a backup from one phone onto another phone, exact same model of course, and then restored that backup onto the new phone!
I've never converted a backup into another form to be flashed another way, like Odin or as a zip in TWRP. Although I guess it could be possible it seems like it could be pretty messy.
Also if the TWRP backup was for a kit at build it will not restore on the lollipop baseband. You will need to Odin back to the kitkat NK4 build them you should be able to take the data.
Sent from my SM-N910T using XDA Free mobile app
ShrekOpher said:
Also if the TWRP backup was for a kit at build it will not restore on the lollipop baseband. You will need to Odin back to the kitkat NK4 build them you should be able to take the data.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
YrrchSebor said:
Hi, what you need to do is put the backup back into the exact same form it was before, an uncompressed, unzipped folder, then put it into the exact directory where TWRP puts backups when it makes them, and then in TWRP choose the option to restore. If you put the backup in the correct directory, TWRP will see it and allow you to choose it to restore it. Basically you just wanna put the backup back where it was before and then restore it in TWRP.
I wasn't sure if you had done this or not. If you have the backup folder with all the contents in their original form, it should work. I've even moved a backup from one phone onto another phone, exact same model of course, and then restored that backup onto the new phone!
I've never converted a backup into another form to be flashed another way, like Odin or as a zip in TWRP. Although I guess it could be possible it seems like it could be pretty messy.
Click to expand...
Click to collapse
Thank you both for the suggestions i will give them a try shortly and i will provide an update on how things go.
Yeah, if you put the backup folder in the right directory, which is either internal or external sdxard/TWRP/BACKUPS/serial #/, you could restore just the data at least and it ought to be mostly ok. You ,might need to clear data in an app here or there if they force close.... or if it's too much then yeah, Odin back to KitKat and restore the desired components of the backup.
YrrchSebor said:
Yeah, if you put the backup folder in the right directory, which is either internal or external sdxard/TWRP/BACKUPS/serial #/, you could restore just the data at least and it ought to be mostly ok. You ,might need to clear data in an app here or there if they force close.... or if it's too much then yeah, Odin back to KitKat and restore the desired components of the backup.
Click to expand...
Click to collapse
Thank you for this, i double checked we had it in the right directory, but it still failed. At first it said something about a missing md5, but i tried again and i was able to get the log for the failure though. (attached below)
Hmm, I looked at the logs trying to make sure you chose to Restore in TWRP and not Install. If so it's possible the backup could have gotten altered or corrupted in the transferring back and forth. If you get it intact as it was, it SHOULD work, but I'm but sure what else to do at the moment. I hope you get it working
Sorry for the delay
Hey Everyone,
Sorry for the delay its been a long week, bad thing after bad thing kept happening. I was able to try your suggestions and i put together some additional information in hope this might help us try and figure it out.
*I must figure out how to recover, texts, contacts, call locks. My default texting app was google messenger.
So I figured I would start with the phone
I am using a Samsung SM-910T on 4.4.4 (build *ANK4) It was pretty Vanilla -> rooted, but running the stock ROM
1. The phone was set to do a full internal backup nightly using the online nandroid backup (by H3r3T1L)
2. Backups were set to be in TWRP backup format and to save to an external SD card, then to compress before being uploaded to google drive
3. Backups were set to delete from SD card after the upload was finished.
What happened
1. When stock 5.0.1 firmware OTA came out i was trying to dismiss the notification but apparently hit "accept" by mistake, causing the system to crash.
2. While restoring the phone, i attempted to download the most recent backup from the google drive and flash the zip to restore my data.
3. This Zip would not install, and i noticed all of the backups uploaded had the same anomally-a few of the files were 0 bytes
4. I downgraded the phone to ANK4 based on the above recommendation but it has made no difference.
5. I still get updated binary error and each time i flash the zip, my OS gets wiped.
6. I have tried instructions to just unzip and flash , to put zips in twrp backup folder, to build new file with meta-inf, etc. and nothing seems to work.
When the SD card got deleted I was able to retrieve some data from the deleted SD card, but don't know where the text messages are located or how to combine them back into a usable format. Or at the very least be able to extract the SMS/MMS history.
I hope this extra information helps. In any way im am desperate to try and fix this for my wife.
I believe you can use Titanium Backup to extract files from a TWRP image. If you can't extract anything from the backup it's either corrupted, in the wrong place, or in the wrong form - that is due to the compression decompression not being compatible (all zip programs are not equal). Best of luck.
BTW, you must restore TWRP files not install them.
Sent from my SM-N910T using XDA Free mobile app