I am running cm 9 mini.
I tried to backup few packages.
But I was not able take such a backup.
The packages are in /data/data
adb backup package_name
Unable to connect for backup.
I tried emulator. I got the same error message
Related
I was looking through the adb options the other day and noticed the "adb backup" option. This seems to grab all the files you need for a full app backup (from the console! yay!). I can use adb shell just fine but adb backup doesn't work. It tells me it can't connect. Anyone know why that is?
I have a locked, rooted (before JB/OTA ROM) restored
with Root Keeper, TF300T on JB 4.1.1.
I have ADB working properly when on Stock OTA ROM.
I am able to adb shell & su for a root shell.
I installed the APX mode driver, booted the tablet
ibn APX mode, and windows device manager
reports an APX Transformer.
I'm hoping that means the APX driver is correctly
installed?
When I unlock the bootloader, I should be
able to boot the tablet into fastboot mode
to run 'fastboot flash recovery recovery.img'
(which ever it is, and for the JB boot loader),
right?
Once I reboot into recovery, adb devices
should see the tablet as a recovery mode
device?
I'm interested in CROMI 3 3+ ROM.
I did an adb backup of the tablet,
and a TiBu of the apps & data
and system data. I also backed up
my calender to an iCal file and
my contacts to a vCard file.
I also did a TiBu to an update.zip
of my user apps and their data.
Did I forget anything? I'm hoping
to figure out how to copy the
contents of /sdcard to a directory
on the docks sdcard, (would
ES FE or Root Explorer do that?).
Thanks
I want to use adb logcat from my device via the terminal. Because it seems to be the only way to access all logs without root. I think Clockworkmod found a way in the Helium Backup app
Nexus 6P, stock ROM, not rooted, locked bootloader
I backed up my easteregg cats by using "adb backup -f cats.ab com.android.egg -system". Worked without a problem, so I assume that drivers (I think I used 15 seconds ADB) and settings (USB debugging, PTP) on both Windows 10 and Android are set up properly.
Now I tried to restore that backup by using "adb restore cats.ab". This results in the following message:
"Now unlock your device and confirm the restore operation."
But nothing happens on my phone. I tried to backup and restore some other packages, same result.
I already tried restarting both devices and that's pretty much all ideas I had.
tacc said:
Nexus 6P, stock ROM, not rooted, locked bootloader
I backed up my easteregg cats by using "adb backup -f cats.ab com.android.egg -system". Worked without a problem, so I assume that drivers (I think I used 15 seconds ADB) and settings (USB debugging, PTP) on both Windows 10 and Android are set up properly.
Now I tried to restore that backup by using "adb restore cats.ab". This results in the following message:
"Now unlock your device and confirm the restore operation."
But nothing happens on my phone. I tried to backup and restore some other packages, same result.
I already tried restarting both devices and that's pretty much all ideas I had.
Click to expand...
Click to collapse
Did you have a resolution to this? I am trying the same thing on a Oneplus 3T and having the same exact results. Restoring on an emulated device work fine.
[UPDATE] Issue for myself was with a conflicting version of ADB on my laptop which was old and not compliant with Android 7.1.1 . For the record, a restore using ADB 1.0.32 on Android 7.1.1 does not work; upgraded to ADB 1.0.39 and everything worked fine.
Hello
So here is my problem :
I made a backup of my xt1032 (motoG) with CM13 with TWRP. I pulled the TWRP file in /sdcard on my PC to not accidentaly delete it.
Before restoring my save, I wiped my internal storage, data, system, dalvikcache and cache. Then i wanted to push my backup from my PC to my sdcard (or anywhere on my phone), so i entered this :
Code:
adb push TWRP /sdcard/TWRP
Nothing happended, CMD.exe was stuck after jumping a line, I waited for 1 or 2 hours... nothing. So i tried to push in an other place my backup by entering this in CMD :
Code:
adb push TWRP /TWRP
But it is the same :/. Do you know what can I do? My phone is blank and I can only access to fastboot and recovery. I tried to adb sideload a stock ROM and CM13, but it does not work...
Thanks a lot ! :fingers-crossed:
Ok it works, I reinstalled SDK android !
I don't know if it could have worked if i just uninstalled/reinstalled the platform tools with SDK Manager, I didn't try.
I think I had some trouble with it because I remember I installed the last adb version manually on internet...
So this thread can be closed