I'm trying to backup my unrooted Moto G7 phone (android 9) to my windows 10 laptop before I unlock its bootloader and root it. I need the ability to restore either everything or at least the installed apps. For privacy reasons I do not sync with Google.
So, using the command, either
adb backup -all
or
adb backup -apk
I get a popup on the phone to allow the backup, which I do, but the produced file
'Backup.ab' either has 0 bytes or a small number. Certainly not a full backup.
Please help so I can root the phone.
Thank you.
P.S. is there another way to backup an unrooted phone?
Nobody offered to help. So in case someone else is frustrated like me here is what worked for me. Quotations and -f.
Example:
adb backup "-apk -shared -all -f"
works. Note the 2 " and the -f
This also works
adb backup "-apk -shared -all -f E:\path\backup.ab"
I hope this helps someone else.
Backup doesn't start.
Phone: Nexus 5x Android 7.1.2. Phone has not been rooted.
I bought this second hand about eighteen months ago. I know all about the bootloop problem, but this one is OK. I unlocked it and flashed 7.1.2 and it's been as right as rain ever since. However, at the time I didn't relock the boot loader.
I want to lock now, but that will cause it to do a factory reset.
I've downloaded installed the platform tools. (Version: 29.0.1 - June 2019) When I run the command:
Code:
adb backup -apk -shared -all -f D:\Android\20190629.backup
on my Windoze 7 box, the dialog to start the backup pops up on the phone.
The Backup Now button is disabled until I enter a password. This enables the button, but there is no response when I tap it.
Fairly quickly, the command quits, and I am left with a zero sized file on the PC.
One thing that turned up is that it might be necessary to have a desktop backup set in developer options.
I am sure that I have never set one up before. However, I tried this, and it appears to be found by the dialog. However, still no go.
Update: adb backup runs immediately after a reboot.
I have determined that if I follow these steps the backup runs.
Connect through adb
Run
Code:
adb reboot
After the phone comes up, set the correct USB mode (File transfer)
Start adb
Run
Code:
adb devices
Run
Code:
adb backup [I]options[/I] ...
The Backup dialog will pop up on the phone. If necessary, enter your backup password. Tap
Code:
Back up my Data
The backup now runs.
The only thing that I've done differently is the reboot. I've tried this successfully three times now.
I discovered this accidently after installing TWRP. I had to eliminate the possibility that somehow TWRP had shuffled some critical bits, or that the reboot fixed the problem.
- oops wrong post
unixwolf said:
I have determined that if I follow these steps the backup runs.
The backup now runs.
Click to expand...
Click to collapse
That part runs.
Have you tried the restore?
Adb backup has given many users trouble.
Related
Let me first say that I have read every post I could find on this subject and tried them all with no success. I rooted my Aria using the Ubuntu Live CD so I could use Titanium backup and eventually try different roms. My phone is still using the stock rom. I then installed Titanium backup which reports "your system settings will prevent you from restoring applications. to correct this go to your phone's settings, then in "applications" and tick the "unknown sources" check box."
The unknown sources check box is of course not there because I have not been able to successfully run the code for allowing non-market apps.
From terminal in the Ubuntu Live CD with USB cable connected and set to charge only. I tried and got "remount failed: operation not permitted." at the adb remount step.
Linux Code:
sudo su
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo "update secure set value = 1 where name = 'install_non_market_apps';"|sqlite3 ./settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb reboot
I downloaded the android-sdk_r07 and extracted it to my C drive. From a Windows command prompt, I changed to the sdk\tools folder. Adb devices sees the phone but adb remount fails with "remount failed: operation not permitted."
Windows Code:
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
I found a post from attn1 that I have not tried that said:
"Put your phone in recovery mode. Go to advanced>mount system and mount data. Follow steps in post #13 (using the windows or linux code above) in cmd screen and you'll be fine." I am not comfortable in trying this approach as there are not enough specific step details and I don't want brick my phone.
I would really appreciate the correct detailed steps to enable non-market apps using the supplied code either from Windows or the Ubuntu Live CD. Thank you in advance.
You are rooted, so boot into recovery and create a nandroid backup; if something goes wrong when pushing settings.db and you cannot boot, restore your nandroid backup. Then, as attn1 stated, perform the same steps you mention above, but while the phone is in recovery and you have mounted the system and data folders.
winsettr said:
You are rooted, so boot into recovery and create a nandroid backup; if something goes wrong when pushing settings.db and you cannot boot, restore your nandroid backup. Then, as attn1 stated, perform the same steps you mention above, but while the phone is in recovery and you have mounted the system and data folders.
Click to expand...
Click to collapse
Thank you winsettr for your post. It looks like running the commands from recovery did indeed work. Titanium backup no longer reports the "your system settings will prevent you from restoring applications. To correct this go to your phone's settings, then in "applications" error.
However, I expected to see the settings\applications unknown sources check box check box and it is not there. I guess I will have to try side-loading an app to confirm that it will work.
I think that gui option would be part of the rom, a part that AT&T has removed... So yeah, see if side- loading works now.
Sent from my Liberty using XDA App
FYI, I am indeed able to side load now from an .apk copied to the sd card. However, I am not able to install from an internet link. Trying to do so generates a "your phone is not authorized" error message.
Until you get a custom rom running, I wouldn't worry too much. Sounds like you can get any app you want (just download internet apps to sd then install). There may be an additional setting in settings.db but that's beyond my knowledge...
Sent from my Liberty using XDA App
Hi all.
I've just installed some app that broke down my S3 stock OS.
The OS was rooted, and I gave the crappy app superuser access...
It was supposed to change the DPI setting, but now it's boot-looping over the Samsung logo.
Now I'd like to recover my data, photos and stuff...
CWM Recovery 5.5.0.4 is installed.
I can start a backup, but it won't complete since I don't have a large enough SD card at hand (it's a 32 GB SGS3 with a bunch of large videos...).
I don't care about the movies, just the photos, but there's no option for a selective backup...
I also tried updating CWM to a more recent release with Odin (downloaded .img and tar'ed it...), but it won't go further than SetupConnection.
I've not tried a factory reset of anything else yet...
Is there a way I can still recover my data, or should I just get over it and try to flash the whole thing back with Odin?
Thanks for your help.
Adb backup?
maybe reinstalling the ROM can fix it ?
The other thing you can try is adb pull /build prop, edit LCD density back to 320 and adb push it back
Thanks for your answers.
adb looks like the way to go, but I never managed to get it working on my computers.
"adb devices" won't list any, "adb shell" returns "error: device not found".
USB debugging was enabled in the OS.
Is the phone supposed to be in recovery mode or download mode? None works... (Also tried with the OS running before it started crashing)
Is there a setup guide somewhere?
Actually, working with Android on Windows (XP x64) has been a total nightmare so far.
On my main computer, Device Manager loops forever on device detection / driver installation, and successive driver installation/uninstallation/reinstallation mangled WMP10 completely (and since it's tied to Windows, I can't reinstall it).
On other computers, driver installation went fine, I hardly managed to copy movies to the phone through MTP / WMP, and never managed to copy anything back.
I only ever managed to move files over wifi, but that's at wifi speed, not USB2 speed...
And now that I gave Kies a try (stayed away from it so far), it keeps eating 100% CPU whenever I run it.
I had that adb problem then I installed android command centre, and bam, it worked! Will try and find link for you....brb
Finally managed to run adb on the computer with Kies installed.
I'll look into this.
Here go
http://forum.xda-developers.com/showthread.php?p=36671130
Can't use adb pull/push anymore: in a previous attempt to reduce the nandroid backup size, I formated the system and cache partitions.
Then I managed to run a full backup with CWM Recovery, but can't find my files in there.
The backup files only contains application data, but the sdcard folder is totally missing.
Well, it appears the problem indeed was in build.prop.
My backup has 2 files: build.prop.bak and buid.prop.temp.
.bak has the old density, .temp has the new value.
Somehow the app failed to rename build.prop.temp to build.prop, and made the system unbootable.
adb backup won't work either: it's waiting for a confirmation on the phone, and doesn't seem to work in recovery mode.
Now browsing /data/media with adb shell !
I had to mount /data manually (in recovery), I guess the same is true for a recovery backup, and that's why I couldn't find my files.
Think I'll manage to get it all back now.
Thanks a lot slaphead20.
I was just about to wipe away all these family pictures!
Nico57m said:
Now browsing /data/media with adb shell !
I had to mount /data manually (in recovery), I guess the same is true for a recovery backup, and that's why I couldn't find my files.
Think I'll manage to get it all back now.
Thanks a lot slaphead20.
I was just about to wipe away all these family pictures!
Click to expand...
Click to collapse
FYI TWRP will not wipe ur sd when u do factory reset
but ur problem not with data its with system and u can fix it simply by reflashing the u r using without any wipe
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I have been experimenting with flashing, etc. and somehow the lockscreen were corrupted and the pattern I was using was not longer valid. I had the fingerprint already setup so I could enter using the rear sensor, but having a corrupted lockscreen is annoying. THis method requires TWRP custom recovery. It is compatible with locked bootloaders and doesn't modify the stock boot or system. It is also compatible with all the AAXON 7 models.
If you have the stock ROM and need TWRP and ADB interface:
A. Setup ADB interface in your PC and device drivers. and connect your terminal to the PC.
B. Setup axon7tool in your computer. Enter into EDL mode by running the command "adb reboot edl" in the command prompt. The terminal will seen to be off.
C. Disable the antivirus and then backup your recovery image using axon7tool running "axon7tool -r recovery". Save the created file in a safe place.
D. Flash tenfar's signed TWRP as a new recovery using axon7tool. It will reboot to system again.
E. Open the command prompt and run:
Code:
adb devices
adb reboot recovery
1. In TWRP , and with the ADB interface properly installed run these the commands from your computer:
Code:
adb devices
adb shell mv /data/system/locksettings.db locksettings.db.old
adb reboot
Now the system will allow you to pass lockscreen without security. In that case you do not need to apply the rest of the steps. Should you continue experimenting issues with the lockscreen, then you should apply the full procedure. Just add the following 2 steps:
2. Open the command prompt and run:
Code:
adb devices
adb reboot recovery
3. When TWRP had fully loaded, run in the command prompt the following commands:
Code:
adb devices
adb shell mv /data/system/gatekeeper.pattern.key gatekeeper.pattern.key.old
adb shell mv /data/system/locksettings.db locksettings.db.old
adb shell mv /data/system/gatekeeper.password.key gatekeeper.password.key.old
adb shell mv /data/system/locksettings.db-shm locksettings.db-shm.old
adb shell mv /data/system/locksettings.db-wal locksettings.db-wal.old
adb reboot
If you want to restore the stock recovery, you just need to rename the recovery-backup.bin file created in step C back to recovery.bin and run the command "axon7tool -w recovery". after that you can enable your antivirus software again. axon7tool can't connect with some antivirus software. I will be editing this OP with links to the procedures required for each step. All of them are in this forums.
Enjoy
@Oki
To fix either " Wrong Pattern " , " Wrong Pin " users only need to delete " /data/system/locksettings.db " from either Terminal/File Explorer with root or TWRP File explorer then Reboot and you'll be good to go .
DrakenFX said:
@Oki
To fix either " Wrong Pattern " , " Wrong Pin " users only need to delete " /data/system/locksettings.db " from either Terminal/File Explorer with root or TWRP File explorer then Reboot and you'll be good to go .
Click to expand...
Click to collapse
Sure! but this guide is intended for people with the stock, unrooted, blocked bootloader who want to remain with a pure stock experience. Usually people without experience rooting devices. This is why I will edit the guide to add all the details to every step.
Could I do this with a pin as well? I restored a backup and it corrupted my password and I have to use the fingerprint on the back to get in.
twilighttony said:
Could I do this with a pin as well? I restored a backup and it corrupted my password and I have to use the fingerprint on the back to get in.
Click to expand...
Click to collapse
Yes, the procedure deletes everything. If you have problems just do the same also with:
gatekeeper.password.key
locksettings.db-shm
locksettings.db-wal
I have updated the OP just to describe the full procedure.
I had this problem earlier today of having the PIN corrupted, but I have it set to require the pin on the first boot.
I fixed it by removing all files ending in ".key" in /system. Not really sure how this compares to removing locksettings.db. Afterward, I put my password back using Google's device manager.
Of course, I am rooted with twrp, so this comes after setting that up.
Masterjuggler said:
I had this problem earlier today of having the PIN corrupted, but I have it set to require the pin on the first boot.
I fixed it by removing all files ending in ".key" in /system. Not really sure how this compares to removing locksettings.db. Afterward, I put my password back using Google's device manager.
Of course, I am rooted with twrp, so this comes after setting that up.
Click to expand...
Click to collapse
The problem of this method is that it only works if the bootloader is unlocked and the phone has the No-verify patch installed.
When you say "No-verify patch," are you talking about removing Google license verification from apps (via an app such as lucky-patcher for instance)? AFAIK that is on a per-app basis and wouldn't affect something like the lockscreen password.
So if the phone has those prerequisites (unlocked, No-verify, TWRP), is there a difference between removing the ".key" files and the locksettings.db? I am not entirely sure what the different files contain, and don't seem to be able to find this information through Google, though I may just not be searching the right set of keywords.
Masterjuggler said:
When you say "No-verify patch," are you talking about removing Google license verification from apps (via an app such as lucky-patcher for instance)? AFAIK that is on a per-app basis and wouldn't affect something like the lockscreen password.
So if the phone has those prerequisites (unlocked, No-verify, TWRP), is there a difference between removing the ".key" files and the locksettings.db? I am not entirely sure what the different files contain, and don't seem to be able to find this information through Google, though I may just not be searching the right set of keywords.
Click to expand...
Click to collapse
No-Verify is an additional security system implementend in the kernel. When No-Verify is active, it checks for the signature of the system partition. If the system was modified, then the system won't boot. This is why after unlocking the bootloader you have to apply No-Verify Patch or any package with the integrated patch such as SuperSU. As you can see, it has nothing to do with the app signature or the lockscreen at all.
The method presented in the OP is valid for most Android phones, and the only prerequisite is to have TWRP installed. It is safe and a lot more recommended than patching the system partition. Patching system or kernel should always be your last resort. usually deleting locksettings.db is enough, and it is a general method that works for almost any locking method.
On B25 and have followed all instructions. Seems this method no longer works :/
I got a new phone and there is an app on my old phone that I've lost the login info to. I'd like to try backing up the app and it's data from the old phone and moving it to the new phone but at least in the app I was trying (Swift Backup) this feature requires root. Is there any way to accomplish this without root?
I'm on a Verizon Pixel 5 so I don't think it will be possible for me to root for quite some time.
skytbest said:
I got a new phone and there is an app on my old phone that I've lost the login info to. I'd like to try backing up the app and it's data from the old phone and moving it to the new phone but at least in the app I was trying (Swift Backup) this feature requires root. Is there any way to accomplish this without root?
I'm on a Verizon Pixel 5 so I don't think it will be possible for me to root for quite some time.
Click to expand...
Click to collapse
Have you tried this
https://play.google.com/store/apps/details?id=com.google.android.apps.pixelmigrate
Good idea, I skipped this step when initially setting up my phone because I wanted to start fresh. I only realized my problem with this one app a while later.
Looking at that Data Transfer Tool it appears there is no actual way to open the app after you've set up the phone. Do you know if there might be some way? It does appear that this might fix my issue, but I cannot open this app. I can't see it in my app drawer but when I search on my settings I can find the app info for it, however there is no option to open the app. Very frustrating.
YES.
You might use HELIUM app. It requires a desktop companian app got installed, too.
How-to:
Install Helium on Android
Install Helium on your PC
Windows Users must also install Android drivers and restart.
Open Helium Desktop on PC
Open Helium on Android (and follow any instructions there)
Helium should now be enabled!
If adb is enabled...
adb backup still works although it isn't mentioned in the adb's help anymore...
At least still in Q that is...
basically: adb backup -f package.name.ab package.name
or with more stuff included: adb backup -apk -obb -f cxz.johnnysquirrel.riddleofthebox.ab cxz.johnnysquirrel.riddleofthebox
list the packages: adb shell pm list packages
or: adb shell cmd package list packages
find particular package, add grep: adb shell "pm list packages | grep cxz"
output is like : package:cxz.johnnysquirrel.riddleofthebox
The package used as an example doesn't have any extra data to be saved really...
CXZa said:
adb backup still works although it isn't mentioned in the adb's help anymore...
At least still in Q that is...
basically: adb backup -f package.name.ab package.name
or with more stuff included: adb backup -apk -obb -f cxz.johnnysquirrel.riddleofthebox.ab cxz.johnnysquirrel.riddleofthebox
list the packages: adb shell pm list packages
or: adb shell cmd package list packages
find particular package, add grep: adb shell "pm list packages | grep cxz"
output is like : package:cxz.johnnysquirrel.riddleofthebox
The package used as an example doesn't have any extra data to be saved really...
Click to expand...
Click to collapse
Nice, I think I'll give this a try. Once I back it up where do those files go? How do I then restore it on my new device?
skytbest said:
Nice, I think I'll give this a try. Once I back it up where do those files go? How do I then restore it on my new device?
Click to expand...
Click to collapse
To the same folder from which you are running that adb. There is adb restore command too.
adb restore <file> - restore device contents from the <file> backup archive
It "should" work when you go upwards. Restoring to an older android version is less certain...
CXZa said:
To the same folder from which you are running that adb. There is adb restore command too.
adb restore <file> - restore device contents from the <file> backup archive
It "should" work when you go upwards. Restoring to an older android version is less certain...
Click to expand...
Click to collapse
Ok, I think I see. In your original response for the adb backup command you included two params cxz.johnnysquirrel.riddleofthebox.ab and cxz.johnnysquirrel.riddleofthebox. Is one of those the apk and the other the app data?
I see here there are two different restore command, one for the actual app "adb install application.apk" and one to restore the data "adb restore application.backup"
skytbest said:
Ok, I think I see. In your original response for the adb backup command you included two params cxz.johnnysquirrel.riddleofthebox.ab and cxz.johnnysquirrel.riddleofthebox. Is one of those the apk and the other the app data?
Click to expand...
Click to collapse
after -f is the file name where to backup. The last is the package name.
skytbest said:
I see here there are two different restore command, one for the actual app "adb install application.apk" and one to restore the data "adb restore application.backup"
Click to expand...
Click to collapse
First one installs the apk, next one restores... so you should do like:
adb restore cxz.johnnysquirrel.riddleofthebox.ab
No idea how it works like if you have that app as an newer system app in that new phone....
These things can be tricky so other exceptions are also possible...
CXZa said:
adb backup still works although it isn't mentioned in the adb's help anymore...
At least still in Q that is...
basically: adb backup -f package.name.ab package.name
or with more stuff included: adb backup -apk -obb -f cxz.johnnysquirrel.riddleofthebox.ab cxz.johnnysquirrel.riddleofthebox
list the packages: adb shell pm list packages
or: adb shell cmd package list packages
find particular package, add grep: adb shell "pm list packages | grep cxz"
output is like : package:cxz.johnnysquirrel.riddleofthebox
The package used as an example doesn't have any extra data to be saved really...
Click to expand...
Click to collapse
ADB backup / restore doesn't allow you to backup things on the one phone and then restore them on the other phone.
jwoegerbauer said:
ADB backup / restore doesn't allow you to backup things on the one phone and then restore them on the other phone.
Click to expand...
Click to collapse
If you say so...
Switching phones like a pro: How our reviewers do it. (September 25, 2020)
https://www.androidauthority.com/how-to-switch-phones-901221/
skytbest said:
I got a new phone and there is an app on my old phone that I've lost the login info to.
Click to expand...
Click to collapse
The login info is lost to the phone or the app?
If to the phone then confirming the backup might be quite challenging...
CXZa said:
If you say so...
Switching phones like a pro: How our reviewers do it. (September 25, 2020)
Click to expand...
Click to collapse
The article linked to is absolutely useless.
OK, the backups created from ADB have no "checks" to see if the device you are restoring to is the same device.
But you'll run into big troubles if devices aren't of same version: by same version I mean the same actual Android version as well as the same manufacturer.
skytbest said:
I got a new phone and there is an app on my old phone that I've lost the login info to. I'd like to try backing up the app and it's data from the old phone and moving it to the new phone but at least in the app I was trying (Swift Backup) this feature requires root. Is there any way to accomplish this without root?
I'm on a Verizon Pixel 5 so I don't think it will be possible for me to root for quite some time.
Click to expand...
Click to collapse
While answering to another question I came to think that it might work to this situation too.
So, the adb works? No use to write anything more if it doesn't...
Also that app must be signed with testkeys or some other known keys...
CXZa said:
While answering to another question I came to think that it might work to this situation too.
So, the adb works? No use to write anything more if it doesn't...
Also that app must be signed with testkeys or some other known keys...
Click to expand...
Click to collapse
I tried the ADB backup and restore (without root) but it did not work. I was still prompted to log in on my new phone. Unfortunately it seems like I'll need to transfer the whole app's state from my old phone to new, which I'm not sure is possible.
skytbest said:
I tried the ADB backup and restore (without root) but it did not work. I was still prompted to log in on my new phone. Unfortunately it seems like I'll need to transfer the whole app's state from my old phone to new, which I'm not sure is possible.
Click to expand...
Click to collapse
Remember that you were told ADB Backup / Restore doesn't work as expected.
skytbest said:
I tried the ADB backup and restore (without root) but it did not work. I was still prompted to log in on my new phone. Unfortunately it seems like I'll need to transfer the whole app's state from my old phone to new, which I'm not sure is possible.
Click to expand...
Click to collapse
Okay, so adb works. It gives some possibilities...
So, you have a locked with what, pin or pattern. It's basically just like 10 000 of those that you have to test...
(Bad idea really , if the phone is the locked one...)
Better written apps allow for backup.
I put those files on my SD card as well as a complete copy of all loaded user apps and system apk updates. My SD card is my data drive as well. I can do a full reload from it alone.
Without a data drive life is a lot more painful...
CXZa said:
Okay, so adb works. It gives some possibilities...
So, you have a locked with what, pin or pattern. It's basically just like 10 000 of those that you have to test...
Click to expand...
Click to collapse
Not really sure what you're getting at here. It's locked because I no longer have access to the phone number I signed up for the app with. So when I install the app on my new phone it sends a verification pin to a number that I do not have, and I am not able to change the number associated with the account.
That's why I 'd need to transfer the whole app state over so I can open the app on my new phone and be exactly where I was on my old phone, with no need to log in.
skytbest said:
Not really sure what you're getting at here. It's locked because I no longer have access to the phone number I signed up for the app with. So when I install the app on my new phone it sends a verification pin to a number that I do not have, and I am not able to change the number associated with the account.
That's why I 'd need to transfer the whole app state over so I can open the app on my new phone and be exactly where I was on my old phone, with no need to log in.
Click to expand...
Click to collapse
You still have the same email address? Just reset the password.
Or are things a bit more complicated?
What app are you referring too?
skytbest said:
Not really sure what you're getting at here. It's locked because I no longer have access to the phone number I signed up for the app with. So when I install the app on my new phone it sends a verification pin to a number that I do not have, and I am not able to change the number associated with the account.
That's why I 'd need to transfer the whole app state over so I can open the app on my new phone and be exactly where I was on my old phone, with no need to log in.
Click to expand...
Click to collapse
So the old phone isn't locked, but the app is...
CXZa said:
So the old phone isn't locked, but the app is...
Click to expand...
Click to collapse
All my registered apps are by email.
Hi,
I was recording a screen capture video using ScreenCam for Android (non rooted) but my tablet (Samsung Galaxy S3) shut down running out of battery. When I restarted the tablet, the video was NOT saved in the usual video folder. I was wondering if I could find somewhere on the tablet a temporary file from which I could recover (even part) of the 30 min recording ? I have looked a bit everywhere and even tried recovery app which mined old deleted video but I never saw this one. In other hand, when I go under Setting>Apps>ScreenCam>Storage, I see 1.49 GB of Cache, which could correspond the 30 minutes record I did, but not sure it is recoverable. Thanks in advance if somebody has a idea, I really like tp recover this record if possible.
Liz
Good
brhp said:
Good
Click to expand...
Click to collapse
?
1) get the package name of app, for example from Google Play link (id) https://play.google.com/store/apps/details?id=<pkgname>
2) enable developer options and usb-debugging
3) on PC install platform tools and usb drivers
4) in cmd.exe try to get backup of that app (leave password blank)
Code:
adb backup -f screencam.ab -apk -shared <pkgname>
5) inspect screencam.ab with ABE extractor (java required)
you can also check Internal Storage for files
Code:
adb pull -a /sdcard
more invasive method if you're willing to risk. (can't remember) bootloader is
already unlocked and device is not encrypted by default? just install TWRP from Odin3 and get full access to /data
[RECOVERY][OFFICIAL] TWRP 3.6.0_9-0 [I9300 I9305]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Thanks aIecxs for taking time to reply. It seems I have a problem with ADB to solve first. Always get the message "adb server version( <31> doesn't match this client <41>; killing..." I actually have no idea how to uninstall ADB to reinstall it properly but I guess this is what I should do...
no need to reinstall, just restart
Code:
adb kill-server