Backup / Restore WiFi Passwords - Verizon Samsung Galaxy S 4

Hi Everyone,
I recently got a new refurbished S4 (via insurance) running 4.4. My old phone was running 4.2; still works (cracked screen but is still usable). Both are rooted.
On the old phone I backed up wpa_suplicant. New phone transferd. After saving any network that wasn't open would be deleted after a reboot (odd). I manually edited the filed and copy and pasted the info for all the saved networks. Reboot. Same.
I deleted the wp_suplicant file and rebooted to get a new file.
I tried backing up all wifi passwords using Titanumim Backup Pro (xml file) and restoring. Wifi manager now knows which networks I have saved and tries to authenticate but fails.
I deleted then got a new wpa_suplicant file. Manually entered the passwords and everything works. I compared the pass keys in the manually entered and backed up files and they are different. Was there an encryption change or some other change in wifi connection between 4.2 and 4.4?
Google backup is turned on but that didn't restore anything either.
Anyone have any ideas how to backup/restore the passwords? I have so many saved I'd really like to not have to re-enter them all.
Thanks!

Try using bmgr, te restore wifi passwords from your old phone. See this link for the description: http://jftr.de/2014/01/fairphone-and-android-backups-to-the-google-cloud/
I just used it to transport all my wifi passwords from my old phone to my new. This uses googles backup service and your devices does not need to be rooted. You do have to run it through adb shell from your pc:

Related

[Q] Back up just wifi settings?

Every time I flash a new Rom or update from fresh a new build I have to enter in multiple wifi passwords. I know it's suggested to not back up system data Rom to rom but is there a way to back up JUST my wifi accounts that are stored?
It's not a huge deal but some of these passwords are not 'password' but rather '8d4f856334' lol and not easy to remember so I have to log into the router each time.
Id like to know as well. Getting pissed bcz of this.
use titanium backup back up system and your apps flash your rom run titanium as normal user apps only then go to restore system data uncheck everything except the wifi access points that will restore those passwords
The green system apps should be fine to restore, if you move to GB it saves augomzgically
The noob guide already notes this about system apps

[Q] android sync manager wifi restore HELP!

Hi all,
My phone, an evo shift 4g running 2.3.3, started acting up so i decided i would restore it to factory settings to start fresh. Before i restored, i backed up my contacts, messages, and calendar with android sync manager wifi, which resulted in an .mbk file. Since the phone has been restored, i have been trying to restore my data but android sync manager keeps freezing everytime i start the restore. Can anyone help me figure out how to restore my data? I've seen people get everything back from their google accounts, but apparently i didn't sync my phone correctly so i basically have an empty phone and I didn't backup to my sd (all i have is the .mbk file). I know how to temp root and have a basic knowledge of ADB... if that helps... thanks.

Couple of questions on Resurrection Remix JB 3.06

Hello.
I just replaced my old Gingerbread by GT-I9100 Resurrection Remix JB v3.0.6[04-09][AOKP JB](AROMA+OTA) using the suggested 'extended steps' and selecting its default settings.
I did this after taking full app+system data backups with Titanium 5.5 and EFS backup with EFS Pro.
The system restarted just fine and looks pretty spiffy.
I tried to restore back my data and that's where I got stuck.
USB debugging shows as checked but Titanium keeps asking for it. EFS Pro is also having problems with it.
If I disable it, EFS Pro complains. If I enable it, EFS Pro runs at full processor load trying to initialize without ever managing to do so.
Titanium on the other hand, refuses to find the data it had saved earlier. They are both on the phone itself and in a laptop. It only shows the new 4.1.1 applications and I see no way to point it to anything else.
Is it a matter of version incompatibility or something else?
Do I have to install some extra mod before these two work?
Thanks in advance.
kanenas_0 said:
Hello.
I just replaced my old Gingerbread by GT-I9100 Resurrection Remix JB v3.0.6[04-09][AOKP JB](AROMA+OTA) using the suggested 'extended steps' and selecting its default settings.
I did this after taking full app+system data backups with Titanium 5.5 and EFS backup with EFS Pro.
The system restarted just fine and looks pretty spiffy.
I tried to restore back my data and that's where I got stuck.
USB debugging shows as checked but Titanium keeps asking for it. EFS Pro is also having problems with it.
If I disable it, EFS Pro complains. If I enable it, EFS Pro runs at full processor load trying to initialize without ever managing to do so.
Titanium on the other hand, refuses to find the data it had saved earlier. They are both on the phone itself and in a laptop. It only shows the new 4.1.1 applications and I see no way to point it to anything else.
Is it a matter of version incompatibility or something else?
Do I have to install some extra mod before these two work?
Thanks in advance.
Click to expand...
Click to collapse
1. After enabling USB debugging, just reboot once. Although in JB, titanium backup doesn't require USB debugging, in order to function properly.
2. Goto Settings - Apps - All - superuser - force stop and clear data. this ensures next time you run those apps, they ask for Su permissions again.
3. Manually tell Titanium backup the location of your old backups.
How?
- Run Titanium backup
- Press menu button, Select Preferences
- Select Backup folder Location (under Backup Settings)
- Browse to the location of your old backups and select use current folder, when you are done.
Notes:
A). Ensure your old titanium backup folder is still present on your phone's Internal/External SD.
-Use a file manager to confirm this.
-If your old folder is missing or empty, copy it back from your Pc and try the third step above again.
B.) Your internal SD is the location always shown by default. Your external SD is located in
/storage/sdcard1 Or in /mnt/emmc
C.) Please only restore your apps only with titanium, don't restore their data. This is to only ensure maximum performance and stability of your new ROM.
Problem solved!
Swyped from my Samsung Galaxy SII
Thank you much Jokesy.
I tried to follow your instructions and came up with some completely different problem right after the reboot in step 1.
My unlock popup doesn't come up.
Instead I get a message on the bottom of the screen:
"SIM card is locked. Emergency calls only"
The battery is full, the signal level is at zero, and I find myself inaccessible when I try to call my cellphone.
I can still run CWM but don't see any relevant options.
Removing/reinserting the battery didn't make a difference. I haven't tried installing some other SIM card yet.
Update: I tried another SIM card and it gets into the phone. My standard card still doesn't.
How did that come up out of the blue? And how do I get around it? Do I have to redo the ROM installation?
Thanks.
kanenas_0 said:
Thank you much Jokesy.
I tried to follow your instructions and came up with some completely different problem right after the reboot in step 1.
My unlock popup doesn't come up.
Instead I get a message on the bottom of the screen:
"SIM card is locked. Emergency calls only"
The battery is full, the signal level is at zero, and I find myself inaccessible when I try to call my cellphone.
I can still run CWM but don't see any relevant options.
Removing/reinserting the battery didn't make a difference. I haven't tried installing some other SIM card yet.
Update: I tried another SIM card and it gets into the phone. My standard card still doesn't.
How did that come up out of the blue? And how do I get around it? Do I have to redo the ROM installation?
Thanks.
Click to expand...
Click to collapse
that another SIM you used, does it belong to the same network as yours?
Swyped from my Samsung Galaxy SII
Jokesy said:
that another SIM you used, does it belong to the same network as yours?
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
It's the same SIM I was using before.
Situation has improved in the meantime.
I left the phone without the SIM card and the battery for a few minutes and then tried with a dead SIM I had around.
It got in with no problems and I managed to restore the apps as per your instructions (but see below).
I also set it to ask for a pin code instead of swipe.
At this point I rerun EFS Pro. It gave some sort of error during intialization but it started up and I restored the saved EFS settings (that seems to have done the trick with the signal).
I powered off, replaced the dead SIM with my working one and restarted.
Back to the 'SIM card is locked' and a dial pad on the screen. Entering my code, didn't remove it. But I now had a full signal.
By hitting the buttons randomly, I eventually got an overlaid message about the Nova launcher not starting up or something and should I wait (it was a bit unreadable). I told it to wait and the system started up right away.
It looks like the 'SIM card locked' message is triggered by some delay in starting up the lancher. Maybe some timer fires up.
The final problem with the Titanium restore, is the contacts list.
It refuses to restore my contacts.
I pointed it to the proper folder where the contacts backup is along with the apps (I can see the file and a hex editor shows my contacts in it) but it never shows them as a restore option in the list (they are dated 9/9/2012 and I only see the default contacts file created by the new ROM (which has only me and a couple of others from my Google account).
Is it a bug/conflict in Titanium or some esoteric trick is needed?
Thanks so much again.
kanenas_0 said:
It's the same SIM I was using before.
Situation has improved in the meantime.
I left the phone without the SIM card and the battery for a few minutes and then tried with a dead SIM I had around.
It got in with no problems and I managed to restore the apps as per your instructions (but see below).
I also set it to ask for a pin code instead of swipe.
At this point I rerun EFS Pro. It gave some sort of error during intialization but it started up and I restored the saved EFS settings (that seems to have done the trick with the signal).
I powered off, replaced the dead SIM with my working one and restarted.
Back to the 'SIM card is locked' and a dial pad on the screen. Entering my code, didn't remove it. But I now had a full signal.
By hitting the buttons randomly, I eventually got an overlaid message about the Nova launcher not starting up or something and should I wait (it was a bit unreadable). I told it to wait and the system started up right away.
It looks like the 'SIM card locked' message is triggered by some delay in starting up the lancher. Maybe some timer fires up.
The final problem with the Titanium restore, is the contacts list.
It refuses to restore my contacts.
I pointed it to the proper folder where the contacts backup is along with the apps (I can see the file and a hex editor shows my contacts in it) but it never shows them as a restore option in the list (they are dated 9/9/2012 and I only see the default contacts file created by the new ROM (which has only me and a couple of others from my Google account).
Is it a bug/conflict in Titanium or some esoteric trick is needed?
Thanks so much again.
Click to expand...
Click to collapse
1. Some people have reported entered enter pin issue, after flashing JB ROMs.
2. You must be kidding me if you think Titanium will restore your contacts from Gingerbread to an AOSP based Jellybean ROM.
They had some better options than titanium in backing up your contacts.
1. Exporting your contacts to SD.this one is simple and doesn't require you to download anything.
2. Using free apps like contacts backup & restore.
3. Merging & syncing your contacts, with your Google account.
My advise:
- backup your present ROM,
- flash a stock based 4.0.3 custom ROM
- Restore your contacts
- backup your contacts with the options i listed above.
- Restore your ROM via CWM recovery
- Restore your contacts.
Done
It will only take few hrs, but you will get your problem solved.
Swyped from my Samsung Galaxy SII
OK, I'll try this and report back.
This (2) is annoying though.
It's just a SQLite database. If they can backup JB (therefore they know the contacts format) they should be able to restore anything back to it.
Otherwise it defeats the purpose of using a database for backup.
Oh well. I have some restoration to do
I must say I never expected such a mixup with the upgrade but at last, it seems to be on the right track.
I followed your last instructions, reinstalled my old XXKI3 ROM, restored and made a couple of backups of my contacts.
I restored the backed up JB 3.0.6, rebooted and imported the contacts, but in the process I lost the signal again (wi-fi was OK).
So EFS Pro back to the rescue, or so I thought.
I tried importing the saved EFS folder from the old XXKI3 but EFS Pro had a problem now mounting the /efs so nothing happened.
I even installed KTool at this point, renamed the EFS Pro image to efs.img, and tried loading it. I can't remember if it also gave me a mount /efs error but I still had no signal.
Trying to go back to the old XXKI3 with Odin, it gave me the same /efs problem so I didn't have a signal even in the old version.
Then I found out about GSII_Repair.
I got it from the market, run option 1 (save existing efs), then option 2 (make /efs writable) and rebooted.
Back with the signal again (but with some different IMEI). But it worked just fine. It seems option 2 doesn't just make it writable but it also loads up some default working files.
I did the whole cycle again, upgraded to JB and all's fine.
EFS Pro can restore /efs now but it loses the signal, so it's back to GSII_Repair to restore it along with the wrong IMEI.
All in all a good exercise.
Hopefully I'll be able to reset the IMEI back to what it was (or find a way to convert the saved img to the actual files and maybe do the IMEI fix manually -- I found this thread that might help: http://forum.xda-developers.com/showthread.php?t=1264021 )
The problem can be considered as successfully completed and I have no words to thank you enough Jokesy.
Much appreciated for your help.

Unable to restore Helium backup!

I used the Helium backup app to backup all my apps before flashing my S3 with the stock ROM. I copied my entire internal memory as it is, and pasted it after flashing. This of course included the crucial 'Carbon' folder with all my backups made my Helium.
BUT now I installed helium and it refuses to detect those backups. In 'Restore and Sync' it simply says "No backups were found on your internal storage".
I know this is probably best asked to the Helium developer but I reckon it's a very famous app so someone might be able to suggest a solution here. I've already tried rebooting.
Thanks!
cyanide911 said:
I used the Helium backup app to backup all my apps before flashing my S3 with the stock ROM. I copied my entire internal memory as it is, and pasted it after flashing. This of course included the crucial 'Carbon' folder with all my backups made my Helium.
BUT now I installed helium and it refuses to detect those backups. In 'Restore and Sync' it simply says "No backups were found on your internal storage".
I know this is probably best asked to the Helium developer but I reckon it's a very famous app so someone might be able to suggest a solution here. I've already tried rebooting.
Thanks!
Click to expand...
Click to collapse
Had the same problem, wanted to root my phone, but unlocking the bootloader wipes everything, so used Helium to backup all my apps. Backed up to both internal storage and dropbox, copied "carbon" folder from internal storage to computer, unlocked bootloader, copied back, and helium wouldn't see backups from "carbon" folder. Will, however, find backups from dropbox, but without premium version, cannot restore them.
I did find a workaround, but it is not the most pleasant way of doing things. If you open the menu options and tap PC Download, it will display a local ip address and port (i.e. http://192.168.1.xxx:5000 or 10.1.10.xxx:5000). This is your phones ip address on your network and may appear different depending on your router and/or network setup, and the 5000 is the port to access helium web server on phone. Navigate to that ip address through your web browser, including http:// and it will open a web interface for backing up and restoring. See attached screenshot. Click on the browse button under Restore and navigate to the carbon folder that you backed up. In each folder will be 3 files, xxx.png, xxx.ab, and .nomedia (xxx is the name of the file i.e. com.adobe.reader). Choose the file with .ab and click open. The web interface will ask if you want to restore, click yes. Repeat for all items to be restored. If the web interface says file invalid, make sure the server is still running on your phone. Should show a cloud in the notification bar and say Helium server is running. If the server stops, just restart it from menu->pc download in the helium app.
This is not the most elegant or efficient way of doing this, but if all your data is in those backups and you really want them, this is the only solution I have found so far. I hope this helps.
Edit: Was able to restore first two apps before posting, but after continuing, remaining apps would not restore. May still work, but even though I get restore complete, the apps don't show up. Will require further investigation.
kind of solution
i have the same problem i tried to unlock nexus 10 and made a backup and (manualy) copied the carbon folder to my PC and restored after unlocking
and as you know it wont detect the backups..
i think it has to do with a .json file that is either not created when the backup is done or not carried over the copy.
(i know about this .json file, as i had a previous backup from whatsapp which had this txt file which has info about the backup)
so when i tried to restore all my apps i only got that whatsapp detected (as an old version)
i mailed Koush( the developer) and he said that manual moving is not supported and the way to go is using the IP server to extract the backups to PC.. (ie doing the backups with the Web tool and not in the app itself)
one thing i can think of (cheating the app. installing the app, doing a backup of the app and replacing the .ab file for the one in the lost backup.. ) i will try that and post back
---------- Post added at 03:28 PM ---------- Previous post was at 03:13 PM ----------
ok i had an old PLUME (twitter client) backup with data,
what i did and seemed to work (for this test )
is to delete data on installed PLUME
backup plume without data. (a plume folder gets created on the carbon folder)
replaced the .ab from this backup with the old backup's .ab
now helium restored the old file with the previous backup data restored as well
i hope this works for other apps. i will try with my nimble quest game which i have a backup and is the only thing no recoverable i had in helium everything else is account based on the cloud
so the way to go here could (until koush changes this)
install the affected apps
backup them
navigate to the carbon folder and replace the .ab's with the old counterparts (which have data)
enjoy
I also had same problem, and i try use the solution below, but it can NOT work for me.
My device is ASUS Padfone 2, without root.
After try many method, I success finally!!
Here is my step, hope can help other people like me:
1. check the backup folder name. i.e jp.co.johospace.jorte, copy it to your PC.
2. use google search this key word "jp.co.johospace.jorte", you can find out what is this app, download and install it from play store.
3. After install finished, open your Helium and backup this app, i.e. "jorte"
4. After backup finished, check Helium restore, you can see "jorte" was backuped.
5. close Heilum from setting/apps, then open file explorer, find a folder named "jp.co.johospace.jorte" in the ../sdcard/carbon/
6. open the folder, you can see 3 files: 1.._jp.co.johospace.jorte.png 2..nomedia 3..jp.co.johospace.jorte.ab
copy jp.co.johospace.jorte.ab from your PC to android /sdcard/carbon/jp.co.johospace.jorte and replace it
7. open Helium again, and restore jorte, you can see data was restored!
it's probably possible to generate a set of manifests for it. the json ones don't seem to have any special data (as in no binary or signature type things)
e.g. for Lux the app
{"enabled":true,"system":false,"flags":545832516,"packageName":"com.vito.lux","versionCode":158,"label":"Lux","versionName":"1.58","locked":false,"date":1375397585745,"apk":true,"backup":true}
cut down to
{"enabled":true,"packageName":"com.vito.lux","label":"Lux","locked":false,"date":1375398819080,"apk":true,"backup":true}
still restores ok
I'm not sure how much metadata is necessary for it to work but that still restores (and the date is moot anyway).
It's possible if you mess up the enabled or system attributes or if the flags attributes are useful hints to the restore command to set package properties - it may make you have to wipe your device (or replace a newer version of the app or install data for an older version, etc). but for your everyday apps for a recent backup - you could probably make a quick powershell or whatever script to iterate over a set of subfolders and generate some dummy manifests.
Code:
$subfolders = Get-Item -Path 'E:\carbon\*'
foreach ($f in $subfolders){
if($f.Attributes.ToString() -eq "Directory")
{
$filecont="{`"enabled`":true,`"packageName`":`""+$f.name+"`",`"label`":`"" + $f.Name + "`",`"locked`":false,`"date`":1375398819080,`"apk`":true,`"backup`":true}"
$fname= $f.FullName + "\" + $f.Name + ".json"
[System.IO.File]::WriteAllText($fname, $filecont)
}
}
(I'd probably suggest using the manifests from backup restores for google system apps and contacts/sms/launcher, etc instead of these though)
anyway, wish the dev added clear non skippable instructions to the app (first run), and the desktop dl page
Maybe they're there and im stupid.
gierso said:
kind of solution
so the way to go here could (until koush changes this)
install the affected apps
backup them
navigate to the carbon folder and replace the .ab's with the old counterparts (which have data)
enjoy
Click to expand...
Click to collapse
thanks for this workaround. this feels like a huge gap in the functionality of a backup app. if there is a forced need to use the cloud, the user should at least be made aware of it.
not sure how much I can legitimately complain about a free app, but definitely not interested in the premium version based on this.
It's simple !
I found out a way. What you do is, 1st backup all your apps using Carbon to your Internal or External storage. Copy all the files in the carbon folder where you have backed up your data. Once you finish wiping your data, install all the apps again and backup using carbon. Now,replace these backup files with the actual backups ! Since you have backed up after re-installing your ROM , carbon won't say it couldn't find any backups.
Cheers
- Sent from Galaxy S3
chinnu189 said:
I found out a way. What you do is, 1st backup all your apps using Carbon to your Internal or External storage. Copy all the files in the carbon folder where you have backed up your data. Once you finish wiping your data, install all the apps again and backup using carbon. Now,replace these backup files with the actual backups ! Since you have backed up after re-installing your ROM , carbon won't say it couldn't find any backups.
Cheers
- Sent from Galaxy S3
Click to expand...
Click to collapse
it's not simple. it's annoying and longwinded. and defeats about half the point of automated backup apps.
the Carbon/Helium app is horrible.
While this went ok I had to reset my device today for another reason.
So before doing that, I backed up using Carbon, and transferred the data via the the web interface as the dev suggested
but was unable to restore the packages as uploading the zip back fails.
(the server on the n4 just stops after the upload. Moreover - there's no logs of any kind for the user as to why it fails. and no upload progress.).
Dunno if the dev will reply what the problem with the android web server component is but for now since i needed the backup urgently
I ended up having to extract the zip and convert the backup into individual manifests/copy the zip contents into app packages folders
Here's the powershell code to do this if anyone else has a similar problem (use at your own risk, I only tested it once on my device)
Code:
$backuppath='E:\_MediaServerE\backup\' #extract your backup.zip contents here (those are the .ab, png files in the zip you downloaded + a backup.json maniest the app generated for all the packages)
$jsonFile=$backuppath+"backup.json"
$jsonText=[System.IO.File]::ReadAllText($jsonFile)
$files = Get-Item -Path ($backuppath + "*")
[System.Reflection.Assembly]::LoadWithPartialName("System.Web.Extensions")
$ser = New-Object System.Web.Script.Serialization.JavaScriptSerializer
$jsonPackageDefs = $ser.DeserializeObject($jsonText)
function getPackageDef([string]$pname, [Object]$packagesIn){
$ret = ""
foreach($p in $packagesIn.packages){
if($p.packageName -eq $pname){
$ret = $ser.Serialize($p)
break;
}
}
return $ret
}
#for each file copy it to a subfolder with the package name, and find the json manifest in the manifest collection
#and write it to the app folder
foreach ($f in $files){
if($f.Attributes.ToString() -eq "Directory"){
#skip
}
elseif($f.basename[0] -eq "." -or ($f.basename+$f.Extension) -eq "backup.json"){
#skip
}
else{
$bn=$f.BaseName
$bn
if([System.IO.Directory]::Exists(($backuppath+$f.BaseName))-eq $false){
[System.IO.Directory]::CreateDirectory(($backuppath+$f.BaseName));
}
if([System.IO.File]::Exists($backuppath+$f.BaseName+"\"+$f.BaseName+$f.Extension)){
[System.IO.File]::Delete($backuppath+$f.BaseName+"\"+$f.BaseName+$f.Extension)
}
if([System.IO.File]::Exists($backuppath+$f.BaseName+"\"+$f.BaseName +".json")){
[System.IO.File]::Delete($backuppath+$f.BaseName+"\"+$f.BaseName +".json")
}
$f.CopyTo(($backuppath+$f.BaseName+"\"+ $f.BaseName + $f.Extension))
$packageDetailsText=getPackageDef $f.BaseName $jsonPackageDefs;
$jsonFileNameOut=$backuppath+$f.BaseName + "\" + $f.BaseName + ".json"
[System.IO.File]::WriteAllText($jsonFileNameOut, $packageDetailsText)
}
}
I then copied the results to internal storage\carbon and was able to restore.
I hate the carbon app it's probably the worst experience I had backing up my device. It's cost me hours of worrying and coding to restore my data and i paid for that crap... There is hardly any documentation to follow and the dev doesn't even warn to not copy files on the app page (that's for the previous issue just above, this one is more about the 'proper' way breaking) Moreover it failed to backup the com.ea.games.nfs13_row game correctly due to its size so I lost the save data for it.
This is not an experience people should have with a backup app.
He should just provide a secondary way to transfer things using the files in the carbon folder (and/or a zip of the backup) instead of the web server bit that breaks, and takes forever. (and yes, I realize the web server generates the zip from the carbon folder and adds the manifest for the download, but if you can't upload it back for restoring properly - what's the point)
oh and keep in mind - you're storing unencrypted tar equivalents of your phone app data - so take care about where you keep the zip or the ab files. (the ab files are tars with a slight header change) (not that Carbon asks you to provide any means of protecting them, so more of an unrelated aside)
No idea, what I posted worked for me !
SMS not returning?
chinnu189 said:
No idea, what I posted worked for me !
Click to expand...
Click to collapse
Everything else seemed to work (thanks for this solution, definitely helpful to at least confirm data). Anyways - the one thing I can't seem to figure out is how to restore text messages (com.android.providers.telephony.ab) - I've tried to do it as a whole app using the PC interface, tried copying the folder as a replacement via Android File Transfer to the 'carbon' folder, etc.
When I try to restore via helium server, it quickly shows me everything as restored but I don't see the messages. When I try to do it manually (e.g. force copy), I don't see an option under "Restore and Sync" to actually select messaging.
Am I missing something stupid / obvious? The raw data seems to be there (for example, call logs were uploaded just fine, text messages seem to have an issue).
--Dan
So I came up with a solution based on what works for others. Why this works when it didn't previously is beyond me, but hopefully someone else can use it if individual parts of their Helium backup don't work properly (in theory it should work for any app / SQL dataset). The whole point of Helium is that we're running non-rooted phones and so Titanium Backup or the like aren't applicable. For reference, I'm running an N4 to OSX 10.7.x
1. Use the Helium Server to create a full backup.
2. Wipe phone or whatever you need to do (I had to do a factory reset for Google since it's an N4 and my proximity sensor is dead).
3. Install the apps you had previously via Play Store (pain in the a**).
4. Run Helium server and upload the backup data.
5. Update apps as needed (should be auto but who knows for individual stuff).
6. Check app data in apps. Texts are obviously easy to see for me. Hopefully everything restored nicely for you here.
***Now for the bit for people who got corrupted restores.
7. Unzip the backup file on your computer, select the .ab files that correspond to the missing / corrupted restores and then zip those into a new file on your computer (for step 9). Keep these files handy in unzipped form as well for step 10.
8. Perform a new Helium backup of those sections onto the internal SD card (yes it will be blank, worry not).
9. (Optional step): Run Helium server and upload that new zip file (with the stuff that didn't make it) alone. Try restore. Unlikely to work but worth a shot.
10. Running Android File Transfer, find the SD card, find the folder 'carbon' and then find the corresponding sub-folders that have the modules that were corrupted. Replace the SD card backups of the broken modules with the good ones from your computer.
11. Run Helium restore again, but only for the sections you want (I swear, for me Messaging didn't show up the first few times but after step 10 it did).
12. Wait, hoepfully it works well. I would reboot after running the restore to a) kill Helium and b) confirm functionality.
FWIW, my telephony.ab was 1.8MB and took SIX hours to restore. Seriously. Yeah yeah, that's a lot of texts but six hours? I've since added "SMS Backup & Restore" to my phone and will probably just use that, map out my phone layout and functionality and just manually replace apps from now on since most data is in the cloud. You lose some stuff, but prima facie it's boat tons easier.
Hopefully that helps someone else who had the same issues.
Best,
--Dan
app is just crap
i lose the most important data.some apps restored,but not the precious i wanted.
thanks helium
Garbage app, just installed it, backed up then when i tried to restore i get the same errors all because i copied the carbon folder to my pc. Stupid
digitallysick said:
Garbage app, just installed it, backed up then when i tried to restore i get the same errors all because i copied the carbon folder to my pc. Stupid
Click to expand...
Click to collapse
Yeah.. I wanted to give a try.. but its real garbage.
thanks chinnu189
your solution worked great for me and only took 2 minutes. messages were restored too. now i can finish Final Fantasy :victory:
It worked for me - JUST BUY THE GOD DAMNED APP
Yes its $5.00 but you know what, I bet you've spent that on a burger, fries and drink in the past month.
I spent an hour trying to do it the free way, made a backup to internal, made a backup to pc using the server, yadda yadda yadda, then ended up on here looking for help because it wasn't working properly.
Finally went fck it here's my five bucks and I backed up to the cloud and restored from the cloud. It just works as advertised and perfectly at that.
Even in high school my time was worth $5 an hour. I just wasn't ready to acknowledge it then. Trust me, it's worth every cent. Buy Helium Premium.
</Advertisement>
No seriously I am a long time Titanium Pro user and Helium allowed me to move my nexus 4 data to my nexus 5 without having to go through the hassles of root. Well worth it for that alone.
Ok, hope this helps somebody. Just did the whole copy the folder instead of use the webserver business. I tried the replace methods above to no avail.
What did work is backing up ONE app to internal and replacing the *.ab file with the backup data into the 'carbon' folder, overwriting the one that has basically a blank app.
If I tried to restore multiple apps at the same time, it didn't work.
This is on a nexus 5, by the way. Now on to the rest of my apps...
the webserver method is a) slow b) keeps dropping out. the app is nothing but a headache.
as for the cloud backup one - depends on the service and whether you can specify the file to be encrypted prior to the transfer.
when doing backups using PC download mode (thru the URL port 5000), the device must be in standby, ie. Screen ON and UNLOCKED. its the only way the backups gets created good and can be restored.
Extracting Helium ab files
I backup up using Helium, and was unable to restore, so I had a small adventure recovering my files (eventually successful). These are some brief notes.
I had used the PC option to get the backup.zip file on my PC (I was going to reflash my Nexus 7 "grouper", 8GB). However, Helium refused to re-install the 2.5GB file back to the tablet. (Wait for upload via WiFi, then "failed".)
I could extract the particular 1.8GB ab file I wanted from the backup-zip that Helium made. However, "adb restore ..." would not work either.
After searching on "adb extractor" I found that the perl scripts (http://forum.xda-developers.com/showthread.php?t=1730309) were able to get me an extracted file in nominal "tar" format. I say nominal, because none of the tar programs I have would touch it---bad blocks etc. (I tried the Java adb extractor first, but did not pursue it further because of the tar issues.)
It turns out that the Helium "ab-tar" file was ordered like this:
2 bytes of something.
5 bytes of something.
Tar header block.
Tar data/header blocks...
5 bytes of something (starting at location 0x10007).
Tar data/header blocks...
5 bytes of something (at location 0x1800C).
Etc.
I.e., every 0x8000-byte chunk was prefixed by 5 bytes of stuff. Except for the second chunk. And the whole file was prefixed by 2 bytes of stuff.
Not only that, but the tar header checksums had been divided by 8 (i.e., last octal digit replaced with '\0').
After converting to a regular tar file, I was able to restore the files to their place. I now have a tar-reconstructing program that I will send to anyone who requests it.
Sigh. Backup should not be this hard.

[Q] Can't backup with adb/helium/google/recovery

G'day/Good Morning/Hello/Hi,
I own a Sony Ericsson Xperia Pro (MK16i) and I am running CyanogenMod9 (20130721), rooted and bootloader unlocked. I have been trying to back up the apps and app data so that I can transfer them to my new phone (Motorola Moto G with Android 4.4.2, unrooted and bootloader locked), but whatever I try doesn't work.
With adb backup, it prompts me to confirm the backup operation on my phone, but nothing appears and I end up with a 0 byte backup file. Tried it on a few computers. Works with my new phone.
With Carbon/Helium, it complains that I have a desktop backup password, but I've never set one, and I can't seem to set one. No matter what I type, I get "failure setting backup password".
With google's servers, I can't find a place to check that it is backed up, nor figure out how to restore to my new phone. It may be backed up, but I can't find out where. In google's dashboard, I only see three apps' data backed up, and they're all system apps (wallpaper, settings, market).
With CWM-based recovery, it took a while and seemed to backup to my SD card, but I can't find where it put anything.
I would prefer to use Carbon/Helium, so if someone could tell me what file or db I can access to clear/reset the desktop backup password, that will hopefully push me in the right direction.
Hope you'll help me.
Thank You
http://forum.xda-developers.com/showpost.php?p=38583034&postcount=3 looks like i should just give up now

Categories

Resources