All,
When I got my Verizon Pixel XL I did the sync with my Samsung S6 it was replacing and was surprised on how quickly it pulled almost everything over. The only parts that were missing were phone history and text messages which I then pulled over using the SMS Backup & Restore App.
I got everything setup and of course now realize I can root my Pixel using pixel8 but I have to unlock the bootloader which will wipe the device.
I have never had the best luck actually doing a full backup/restore without root on other devices like the S6 I had and the S5 before that. I usually loose something in the process.
I tried to do an ADB full backup with all data, system files and shared data: adb backup -f backups\backup-all-system-apk-shared-201611081225.ab -all -system -apk -shared it only came out to be 2.7GB. When I did the backup without shared data or system: adb backup -f backups\backup-all-nosystem-apk-noshared-201611081223.ab
-all -nosystem -apk -noshared it only came out to be about 720MB.
According to my storage, I have 35.15 GB used of 119GB. So even the full 2.7GB seems Quite low.
Does anyone have a method of Getting ALL Data from a non-rooted device, in my case all 35GB so I can restore the entire device and not loose anything once I unlock the bootloader?
I got it working after passing the -obb option too. Also, that size looks right; mine was 3.7GB. Most of your used storage is your read-only redundant OSes, recoveries, boot paraphernalia, etc., so most of that doesn't need to be backed up.
hth
Related
Hi,
I'm just trying to backup my HOX to do a post-JB factory reset. I'm a bit concerned about the size of backup files I'm getting from adb - they seem very small!
adb backup -apk -all -nosystem -f backup.ab
for example, gives a backup.ab file of 253Mb. Can that be right? I understood those flags would include all non-system apps (not on the phone storage), not just their settings, and I'd have expected a lot more than that. Storage in Settings tells me I'm using 6.xxGb of "app storage" and about 4Gb of the 25Gb phone storage.
I know actual figures depend on personal usage, I just wanted to know whether people thought those seemed like correct ballpark figures.
adb would seem to be my only option real option since I don't want to root until I'm out of warranty.
Thanks,
Allan
That's only the system partition and it sounds about right.
To fully backup your phone you would want system, data, boot, and sdcard (not usually done as it's not erased for most things).
(Easiest way I know is to a backup like that using CWM or TWRP recoveries)
Thanks, that's reassuring that it doesn't seem anything's wrong with the backup.
I'd really rather not root to use any of the more powerful backup solutions but I recognise that means I'm more limited with what I can do.
I think I'll rebackup with adv to cover the last few days and then just go for it.
Thanks again!
Hey,
I've created a backup with this command:
Code:
./adb backup -f fullbackup_2013-03-28.ab -apk -shared -all -system
The resulting file was 11 GB which was expected. After this I unlocked my bootloader. Restoring the backup hung two times. FIrst at com.android.chrome then at com.google.android.googlequicksearchbox. These two were also mentioned in Android issue report #34311 (sorry can't post link, I'm under 10 posts). Both times I rebooted my phone and restarted the restore. The third restore went through.
Now my problem is I'm missing a lot of data. My storage is only at 6 GB, that's at least 5 GB missing. My music folder for example was only partially restored. How can this be? Is there anything I can do?
I'm running 4.2.2 stock. My adb version is 1.0.31.
Update: I've now extracted the backup and I can say for sure that there are files in there that don't get restored.
Has nobody else experienced such a behavior?
AW: [Q] adb restore doesn't restore everything
yes i have done that with my nexus 7.. it seemed to restored my file structure but when i tried to open files nothing would happen... u really cant rely on that thing
Sent from my Galaxy Nexus using xda app-developers app
It's safer to use adb pull and adb push to backup and restore the sdcard, and only use adb backup for user apps and data. Also, it's not generally a good idea to backup and restore system apps and data. So -noshared and -nosystem for adb backup, and pull and push for the sdcard might work better. As for the data you already backed up, maybe Titanium Backup would help. I understand it can access adb .ab files, though I haven't used it for that myself.
I dont know what I did but I know it was my fault.
Whenever I try to create a full backup of all partitions I get "createTarFork() process ended with ERROR=255"
But when I exclude the System partition it works fine.
So if I restore everything else later on will everything work fine? I'm not exactly sure whats getting left out in the partition.
Btw, my bootloader is unlocked, I'm currently on FreedomOS 2.1, I have Magisk, Xposed, all the good stuff...
ALSO! I did an ADB backup on my computer with "adb backup -apk -shared -all -system -f"
I'd be fine with the ADB backup but "backup.ab is only 1.5 GB and my nandroid backups are usually around 11GB...
lit_lee said:
I dont know what I did but I know it was my fault.
Whenever I try to create a full backup of all partitions I get "createTarFork() process ended with ERROR=255"
But when I exclude the System partition it works fine.
So if I restore everything else later on will everything work fine? I'm not exactly sure whats getting left out in the partition.
Btw, my bootloader is unlocked, I'm currently on FreedomOS 2.1, I have Magisk, Xposed, all the good stuff...
ALSO! I did an ADB backup on my computer with "adb backup -apk -shared -all -system -f"
I'd be fine with the ADB backup but "backup.ab is only 1.5 GB and my nandroid backups are usually around 11GB...
Click to expand...
Click to collapse
Team Win recommends using the system image backup instead of just system for dm-verity devices, but I still get the same problem as you when trying to perform a backup. What you could try is clean flashing the ROM and then just restore data from ur backup. That should work.
Airwolf79 said:
Team Win recommends using the system image backup instead of just system for dm-verity devices, but I still get the same problem as you when trying to perform a backup. What you could try is clean flashing the ROM and then just restore data from ur backup. That should work.
Click to expand...
Click to collapse
Yeah I read in other places a fresh flash would work but I wanted to weight my options.
How does one go about doing the image backup? That sounds a lot better.
lit_lee said:
Yeah I read in other places a fresh flash would work but I wanted to weight my options.
How does one go about doing the image backup? That sounds a lot better.
Click to expand...
Click to collapse
When you select backup in TWRP, it's one of the available boxes to check. Uncheck system, check system image. This hasn't solved my problem of backups not completing though. I always remove my fingerprints and pin before a backup, and I've been able to complete backups before, but usually the problem lies in encrypting the backup itself. However, I've still had backups hang at 95% even without encryption. Maybe someone else can shed some light on to why this is happening.
the createTarFork() process ended with ERROR=255 is not from system its from data and issues with parallel apps on ur OP5T
download Android Terminal and type
Code:
su
pm remove-user 999
then u can backup with twrp, never tried to do a restore yet though
I'm trying to back up my phone with adb because rooting will have to involve wiping. I've tried backing up with
Code:
adb backup -apk -shared -all -f backup.ab
and similar commands (noapk, noshared...), but whatever I do I can't get a backup bigger than about 1.5GB. This is a problem as my whole 32GB internal memory is almost full, and it's not just files, one of my apps alone shows up as using 2.5GB storage. How do I backup the whole phone?
I'm using adb.exe from platform tools from developer.android.com, my phone is Android 7.0, software 2.41.401.41
Edit: I've managed to open up the ab file and it's almost all just system stuff (com.htc.china.location.service, why the hell would I want to back that up??), and about a dozen of my apps (only 40MB of them), and for at least one the storage is missing.
Hi,
Few months ago I bought a ROG Phone 6D, a few weeks ago it fell and it managed to hit a pointy pebble right on the "aeroactive portal" (the valve that opens when you attach the cooler), damaging it. Now whenever I use the cooler the valve will open but won't close, and on the phone itself will show a notification saying "abnormal aeroactive portal detection". I wrote to ASUS asking where I could get it fixed and they told me there's no in store assistance for my country and I must compile a form and have it sent to their centre.
I was also told my phone will be factory reset (even for such an issue) to ensure my privacy, so I wanted to find a way to have a full backup (apps, settings, data, life universe and everything) but when looking for ways to backup a phone it seems all the methods I used to use years ago are not working (or partially working now), even adb backup can miss some stuff apparently now, and is considered deprecated.
I would like to find a way to backup my phone so that when it comes back I could just restore it and act like it hasn't lost a single day without having to root my phone (which, as far as I've understood, will void my warranty), is there such a thing in 2023? The command adb backup -apk -obb -shared -all -system -f fullbackup.ab seems to be the best at the moment, with the exception it might miss some apps if they opted out of backups. Is there something better than this?
Thanks!
there is maybe a way to backup with D2D transfer apps as it is the only backup method that still get all permissions. unfortunately I don't know if such apps can be used on single phone.
Android 11 forces apps to support local backups but not cloud backups
It's no secret that backing up and restoring apps and data sucks on Android, especially when switching devices. Android 11 is slightly making things better.
www.xda-developers.com
But you can at least backup your files of Internal Storage from adb.
Code:
adb pull -a /sdcard
cloud backup may also work for some apps, you can use Swift Backup without root or Google One (untested)