Don't think anyone else has posted this yet so here goes:
A Google employee called Rich Hyndman posted this on his Google+:
https://plus.google.com/115995639636688350464/posts/b9ejZegfw8p
With Android 4.0 you can backup and restore app data to a computer using adb with no root required. I just did this on my stock device because I wanted to unlock it and install the 4.0.2 update manually as no OTA notification had come my way. Unfortunately the backup part doesn't work on Windows yet but it does on Ubuntu and Mac OS.
Here are the steps I performed:
1.) Connected my Galaxy Nexus to my Ubuntu machine with the Android SDK already setup
2.) I ran "sudo adb backup -f 20111219.bak -all" (adb only works as root on my machine)
3.) This pops up a screen on the phone asking for an encryption password to use for the backup (this will be asked for when you restore). It might work with no password
4.) Once the backup has completed the adb command will exit. Keep the .bak file somewhere safe
5.) Backup everything on USB storage (I used my Windows machine for this as I have no idea how to get MTP working on Linux)
6.) Wipe your phone with a factory reset or fastboot oem unlock
7.) Once wiped boot normally and you will have to perform initial setup again (do this on Wifi as it takes a while to re-download all apps)
8.) Wait for all your apps to download (download notifications will stop)
9.) With your phone connected to your PC again run "adb restore 20111219.bak" (this works on Windows oddly)
10.) If you used a password in step 3 enter it on your phone here and tap the restore button.
11.) Wait for it to finish restoring.. done
I restored BEFORE applying the update manually as detailed here because I didn't know if backing up on Android version 4.0.1 could be restored to Android version 4.0.2.
This restored all my app and game data and even setup the folders and shortcuts on my home screen (but not widgets). However, it did not restore my SMS message and call history so it looks like at least some apps won't be included in backups - YMMV.
OK so when I type in adb backup -f C\Backups\gnexbackup.ab -all -nosystem
it looks like it does it's thing and backs up everything, but then when I go to the folder (Backups) I don't see that .ab file... what's up?
I am using takju 4.1.1 unlocked bootloader, but no root
same problem
works, but does not fix broken system apps
start cmd with admin
go to location of adb.exe
C:\>cd C:\adb
check adb
C:\adb>adb devices
List of devices attached
0123456789ABCDEF device
connect only one device!
if "adb devices" returns anything else, something is wrong, try '>adb kill-server' and retry and/or redownload newest adb at thanks Snoop05
C:\adb>adb backup -all
confirm at phone with password, no password leads to failure during restoring process, its a known bug (adb v1.0.32 and below)
file C:\backup.ab will be created
restore with
C:\adb>adb restore backup.ab
confirm at phone with password
wait till done
works for me, all user apps and data are restored, but it did not fix my broken google services and deleted calendar storage (accidents happen )
This function is not reliable. Some apps work, others dont. Only use this if you dont have any other options, e.g. broken phone or some malfunction.
I put CM7 on my daughter's Wildfire S a year ago, and everything has been fine until now - and it just bootloops on the CM7 animation.
I have tried wiping dalvik & cache, fixing permissions in CWM, reflashing CM7 (the version from last year - cm-7-20120717-UNOFFICIAL-marvel.zip) and gapps. Nothing helps. Any ideas please, before I try a full wipe? I am trying to avoid that since she has no backups...
fjuniper said:
I put CM7 on my daughter's Wildfire S a year ago, and everything has been fine until now - and it just bootloops on the CM7 animation.
I have tried wiping dalvik & cache, fixing permissions in CWM, reflashing CM7 (the version from last year - cm-7-20120717-UNOFFICIAL-marvel.zip) and gapps. Nothing helps. Any ideas please, before I try a full wipe? I am trying to avoid that since she has no backups...
Click to expand...
Click to collapse
Try flashing the latest version, it'll have less bugs anyway. I don't think you absolutely need to wipe when updating a ROM but it would probably be advisable.You can try this however.
-Download the Android Debug Bridge (adb) from Google's site onto your computer.
-Plug your phone into the computer and open the Terminal Emulator.
-Type cmd in the little window that appears and press enter.
-Navigate to the folder that you downloaded ADB to. (Example: cd C:\Users\Guest\Downloads\platform-tools )
-Type "adb backup" without the quotes to take a copy of your phone's data onto the computer.
-Now you can safely do whatever you want.
99Aaron99 said:
Try flashing the latest version, it'll have less bugs anyway. I don't think you absolutely need to wipe when updating a ROM but it would probably be advisable.You can try this however.
-Download the Android Debug Bridge (adb) from Google's site onto your computer.
-Plug your phone into the computer and open the Terminal Emulator.
-Type cmd in the little window that appears and press enter.
-Navigate to the folder that you downloaded ADB to. (Example: cd C:\Users\Guest\Downloads\platform-tools )
-Type "adb backup" without the quotes to take a copy of your phone's data onto the computer.
-Now you can safely do whatever you want.
Click to expand...
Click to collapse
Thanks. That is the latest version of the ROM unfortunately - old ROM on an old phone now.... If I go to e.g. CM10, I will have to do a full wipe anyway.
I have ADB already installed. It does respond to ADB commands like adb reboot, but using adb backup just results in the full set of commands being listed i.e. it doesn't know what to do. Are there other parameters to use? backup isn't in the list presented.
...
I found a suggestion to use
adb backup –apk –shared –all –f /backup/mybackup.ab
But I just get the response
adb: unable to connect for backup
fjuniper said:
Thanks. That is the latest version of the ROM unfortunately - old ROM on an old phone now.... If I go to e.g. CM10, I will have to do a full wipe anyway.
I have ADB already installed. It does respond to ADB commands like adb reboot, but using adb backup just results in the full set of commands being listed i.e. it doesn't know what to do. Are there other parameters to use? backup isn't in the list presented.
...
I found a suggestion to use
adb backup –apk –shared –all –f /backup/mybackup.ab
But I just get the response
adb: unable to connect for backup
Click to expand...
Click to collapse
I'll be honest, I've never used that command before. I just know how it works, I took a Nandroid backup when I first rooted my phone so have never needed it. I can't really help from this point on.. However if your phone will boot into recovery, assuming you have ClockWorkMod installed you can do a backup through that.
99Aaron99 said:
I'll be honest, I've never used that command before. I just know how it works, I took a Nandroid backup when I first rooted my phone so have never needed it. I can't really help from this point on.. However if your phone will boot into recovery, assuming you have ClockWorkMod installed you can do a backup through that.
Click to expand...
Click to collapse
Hi, I was hoping to do an app+data kind of backup like Titanium. I did take a nandroid in CMW and then restored it, but it perfectly reproduced the bootloop behaviour haha. In the end I did a full wipe and told my daughter that she needed to start from scratch. 14 year olds are more pragmatic that I would be - she was just grateful she had her phone back and could get on FB. Google restored her contacts, which is the main thing. So all sorted, but the bootloop cause remains a mystery...
How to enable ADB on ALLWINNER A13 9" - 4.2.2 - Windows 7 - error:device not found
Hi folks, my target is to do a full backup of my android tablet device without rooting nor installing app's on the device. It can be done just by the ADB tool and the simple command
Code:
adb backup -apk -shared -all
.
Basic information
PC: Windows 7, pro. USB 2.0 port. ADB Driver "Drivers-AllwinnerA10-32bits\32Bit_Win_7_Vista_XP" from 2011. ADB Platform-Tool, Android Debug Bridge version 1.0.31. Logged in as normal User, not Admin. The development kit is not installed, I just downloaded the Platform-Tool, unzipped it and started "adb" - I just want to make a f***ing backup :crying:
Tablet:
ALLWINNER A13 9". Android Version 4.2.2. USB Debugging enabled. Detail Info's:
Model number: JL902
Kernel Version: 3.4.0+ [email protected] #1 Mon 25.11.2013
Build-Number: full_gs702c-userdebug 4.2.2 JDQ39 eng.root.20131207
NOT ROOTED.
Problem:
I do not get a connection from the PC to the tablet. Also no RSA Key question comes up at the tablet. The adb tool just throws an error :"device not found". I tried several things, log in as Admin, "adb wait-for-device", plugging and unplugging ... nothing helped. The adb tool works fine, I tested it with a Samsung Galaxy S2. I'm not quite sure about the adb USB driver on windows, but there is no exclamation mark nor other problems reported. So this should be fine.
Anyone any hint, tip or solution? Would be great - gathering for hours with this problem - searching forum 'n stuff....
Thanks in advance
Juha
Try with uberizer or MTKDroid tools. Just connect and select adb terminal.
kramkumar said:
Try with uberizer or MTKDroid tools. Just connect and select adb terminal.
Click to expand...
Click to collapse
Thx 4 the hint, tried uberizer:
Code:
ERROR No useable device has been found
I think since in Android 4.2.2 the RSA Key authentication was introduced, something is wrong with the connection. Because I would expect the RSA Key question on the tablet, but the tablet does not show this dialog.
By the way, I recognized that the USB driver for the ADB interface is titled "Drivers-AllwinnerA10" but the tablet has a A13 core. But I do not find another driver at the moment and the vendor ID -VID_10D6&PID_0C02&REV_0202&MI_01- fits (otherwise, windows wouldn't install it anyway). Does it make sense to search for another driver?
hi from messing with various drivers and android devices i have found that installing PDA net for windows (theirs and android version too but not needed) once pdanet installs let the drivers for your phone be installed, if by any chance you have drivers already installed what you can do is go to device manager, click on your device uninstall the drivers, unplug your phone and then open pdaNET a window will come up waiting for you to connect your phone and the driver installation process will begin.
The program downloads the correct driver for mostly any model phone you have and works flawlessly with ADB, if by any chance this helped just give me a thanks !
abstractVoid said:
The program downloads the correct driver for mostly any model phone you have and works flawlessly with ADB, if by any chance this helped just give me a thanks !
Click to expand...
Click to collapse
Thanks for the tip. It really installed an USB driver as you said (I've deinstalled the other driver before). But sadly the result is the same. I can't access the ADB interface - same error "Device not found".
At this point I want to say thanks to all viewers of this thread, it seems really to be not an easy task. I'm still open minded in any direction and would be happy for any suggestion what I might try.
Even a hint, how I could reduce the possibilities for the root of my problem. I'm still not quite sure, if the driver is the problem or even if the tablet itself has some kind of software defect on this kernel version - By the way, does anyone have the same kernel version (posted at the beginning - 3.4.0+ [email protected] --- repeated for your convenience) of Jelly Bean (4.2.2)? Do you have experience with the ADB interface then?
How may I isolate the real problem? Any idea wellcome :cyclops:
I have nearly an identical tablet except mine has the PnP code of Vendor 10D6/Device 0C01 and it shows as P706 on the USB description.
I installed PDAnet, that actually was able to upload the Android version of PDAnet to the tablet, so I think that's a definite for the driver working. But I'm also having trouble getting ADB to list the device and I'm using the latest ADB from the SDK. Since ADB tries to setup a network server, I'm wondering if the ADB driver on windows has to be tethered as a NIC somehow?, just a theory.
I'm using a fresh install of XP and can do a complete rollback, so I'm certain it's not the OS.
There's also another quirk about this tablet. I wanted to do a backup of the firmware from this device. Techknow's utilities use ADB to issue several shell commands to copy "partitions" to the SD card, I thought I might as well try to do that manually only to find what would've been copied as /dev/block/nanda, nandb, etc. is named /dev/block/acta, actb, etc. instead. But lack of "root" means I can't read any of those partitions or even copy su into /sbin.
Uberizer isn't any good since as far as I can see that also uses ADB. Any known issues with versions of ADB? or even any other tools which do similar to ADB?, or even a way to "root" these devices just by Terminal and SD?
Regards
Ah, okey, soz I got the USB thing a bit mixed up. My tablet does have the same code, I assume the 0C01 is when it's in recovery mode (power on with volume + pressed)
I also realised the driver that was working wasn't one from PDAnet.
I've updated the working 32-bit driver with the version of ADB I'm using and included it in the attachment. Maybe you can try that and see if you have any progress.
I'll keep posted on this thread.
SOLVED!
Copy .android from the attachment into your %USERPROFILE% directory (i.e. C:\Document and Settings\<user> on XP or C:\Users\<user> on Windows 7)
You can check what the user directory is by DIR %USERPROFILE% in the "DOS" command line (%USERPROFILE% is case sensitive).
ADB should list your device when you do adb devices in the "DOS" command line.
Basically, adb_usb.ini with a custom identifier was missing.
Regards,
qUE
Right, I've made up a pack to automate putting SU on the device and setting up permissions on SU and BUSYBOX.
!!! This is only for the VID_10D6&PID_0C02 device, your mileage may very with other devices. !!!
DRIVER directory should contain the USB driver you need, otherwise try installing PDAnet and tell it to replace the driver.
Install USB driver, run SUME.BAT
to hopefully backup all the needed stock firmware to SD;
adb shell
su
cat /dev/block/acta > /mnt/sd-ext/acta.img
cat /dev/block/actb > /mnt/sd-ext/misc.img
cat /dev/block/actc > /mnt/sd-ext/system.img
exit
exit
adb kill-server
qUE
Confirmed solved
qUE-ARM said:
SOLVED!
Copy .android from the attachment into your %USERPROFILE% directory (i.e. C:\Document and Settings\<user> on XP or C:\Users\<user> on Windows 7)
<SNIP>
Basically, adb_usb.ini with a custom identifier was missing.
Click to expand...
Click to collapse
CONFIRMED SOLVED
Yes, that was it! I copied the adb_usb.ini file into the .android user directory (which only contains these ascii chars "0x10D6" - no CR no LF or anything else) and it worked out !!!
Thank you (Thanks meter will follow ) Some interesting things I discovered now:
There was no RSA-Key question at all on the tablet!!!
as I did the full backup with "adb backup -apk -shared -all" I was asked on the tablet to confirm this
So obviously something strange is going on here. Since it is claimed everywhere the with Android 4.2.2 the ADB interface should be generally RSA-Key protected. Okay, might be that I misunderstood something here :silly:
At least this problem is solved and I appreciated every comment in this thread. One question would be final to answer:
Who should have brought the adb_usb.ini to my PC. The ADB driver ? The ADB Platform-Tool package? So, whom to blame here - NO - just kidding :laugh:
I did briefly try the platform-tools (since I didn't mind the OS being trashed), they didn't add any adb_usb.ini and there isn't any real indication the file was needed/didn't exist, they could've simply put a note on the ADB utility when it didn't find any devices.
I'm not sure what ADB backup does. As far as I know the mounted partition images are differently named to various backup tutorials, so I get the feeling ADB backup just simply copies the user data and not much else. I recommend doing the backup I mentioned as well, it'll at least capture a copy of the boot partition, which if the device doesn't have that you'll probably need to revert to using live suite or some other firmware utility to restore it. Getting the firmware for that is another story, read a fair amount of posts here and other places on the net that don't sound fun.
I personally still can't get superuser to behave for using su on the terminal/term.apk (I want to remove useless "system" apps and make sure the device isn't talking back to anyone, i.e. google), but I'll keep tinkering.
My main aim for getting one of these tablets was to boot other firmware from the SD slot, but it looks as if the u-boot process is locked to internal NAND. So might have to modify it by adding "fatload mmc" to the script.
qUE
Quick Update;
Right the permissions thing turned out to be an issue with Superuser, dunno why. So replace the su binary from SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053) into my SUME pack and install the Superuser.apk by;
adb root
adb shell mount -o rw,remount /system
adb push Superuser.apk /system/app
as for stripping back the Applications, I've got it down to this as bare bones
adb pull /system/app backup\system\app
to backup system applications before you do anything
I found if you do delete any applications and then android gets stuck at the logo, just adb push them back and it'll boot without reboot when you've got the chain right.
minimum applications needed for boot are;
DefaultContainerService.apk
DefaultContainerService.odex
SystemUI.apk
SystemUI.odex
Launcher2.apk
Launcher2.odex
Settings.apk
Settings.odex
SettingsProvider.apk
SettingsProvider.odex
ActSensorCalib.apk
InputDevices.apk
InputDevices.odex
FusedLocation.apk
FusedLocation.odex
LatinIME.apk
LatinIME.odex
PackageInstaller.apk
PackageInstaller.odex
ApplicationsProvider.apk
ApplicationsProvider.odex
A few odds and sods missing will make settings close, but it's trivial stuff. Personally don't like the sound of Fused Location, but it won't boot without it and I haven't seen any dodgey traffic from it (yet).
I recommend installing Droidwall with adb push /system/app, before installing games.
And modifying /etc/hosts with 127.0.0.1 to certain you know whos and advertisers.
Some of my personal choice replacement applications (so far);
Total Commander over ES file explorer.
Opera Classic over the inbuilt browser (although I'm still trying to remove the default search engine).
qUE
More update;
Discovered some new things;
BACKUP FILES WITH "ADB PULL" BEFORE MODIFYING ANY FILES!!!
I think performancepolicy.apk needs to be added to the bare bones application list, afaics from looking inside the package it sets system performance stuff, so likely throttling to preserve battery power.
bin_cfg.xml in /misc which can be modified by
adb shell mount -o rw,remount /misc
then adb pull, edit and push the file back
the line in there for "backlight_brightness" 780;1020;780 can be changed to 240;1020;240 which dims the backlight substantially saving battery power. not sure if 240 is the absolute minimum, but 120 seems to be too low afaics. interestingly information on the settings is in the files named _userview.xml
build.prop in /system which can be modified by
adb shell mount -o rw,remount /system
then adb pull, edit and push the file back
and then chmod 644 /system/build.prop
the lines in there for ro.wifi.signal.level.# can all be set to 0, this theoretically cuts the wifi power usage to less than 1mW, again saving battery. if android doesn't boot fully on reboot it's because chmod hasn't been set, you should be able to adb back in and correct.
please be careful modifying either file as both seem to have safety limits imposed on certain device components (i.e. battery temprature), messing with those can make the tablet stop working.
qUE
Hello, I just made a TWRP backup and it backed up to /data/media/0/TWRP/Backups/SERIAL_NUMBER/date. This obviously takes up a lot of room on my phone and I want to move it to my PC. Problem is, my PC isn't seeing the files. Neither is the Root Browser app after given the proper permissions. My phone is running a CM13 nightly, specifically the 9/10 nightly (yeah i know i am outdated). I am making a mistake here but I can't for the life of me figure it out. Please help.
The reason I'm making this backup is because I want to try out RROS.
v1n0dhn said:
Hello, I just made a TWRP backup and it backed up to /data/media/0/TWRP/Backups/SERIAL_NUMBER/date. This obviously takes up a lot of room on my phone and I want to move it to my PC. Problem is, my PC isn't seeing the files. Neither is the Root Browser app after given the proper permissions. My phone is running a CM13 nightly, specifically the 9/10 nightly (yeah i know i am outdated). I am making a mistake here but I can't for the life of me figure it out. Please help.
The reason I'm making this backup is because I want to try out RROS.
Click to expand...
Click to collapse
What twrp version are you using?
Simply moving the TWRP folder where there is the backup on the PC.
Inviato dal mio m8 utilizzando Tapatalk
connect your phone to your pc
boot into TWRP
while in twrp, run adb on your pc
execute 'adb devices' to confirm your phone is connected and adb recognizes it
on adb in your pc, execute the command 'adb pull /data/media/0/TWRP/Backups/SERIAL_NUMBER/date'
adb will dump the backup to the folder where adb is
hope that helps!
Thanks for the help everyone and I finally got it. For some reason, Windows Explorer didn't update itself fully so I didn't see the file.