Hello,
I recently got a new phone OnePlus3 and trying to move my old messages from viber to the new one. The application doesn't support this process so I'm using a backup of the two applications along with the help from Android Backup Extractor. The process is described in the web so a google search would provide some more information.
The problem lies on the adb backup command as the package which is extracted from the device is kinda empty.
The old phone is a Nexus 4 with stock Android (rooted) version 5.1.1. The commands I'm using are:
Code:
adb backup com.viber.voip -f ./viber-old.ab
The resulting file is 54 bytes in size and when I unpack it with Android Backup Extractor it's an empty tar file.
I've tried with adb version matching the one on the phone (version 32) and with latest (36) downloaded from the android SDK. I've also tried setting a password for backups and not use empty one.
Since I've been trying with no success I tried on OnePlus3 and on Nexus 5X with no results either. The final size might be different but it's the same issue either 0 bytes or 54 bytes. (which includes just the manifest file). Previously around X-mas I have done the process successfully and moved my messages from Nexus 4 to my Nexus 5X so it's either a new permission policy in Android or Viber application doesn't allow backups?
Happy to debug further if one has some suggestion.
Thanks
The backup to Google Drive option doesn't work to restore on another device? Seems silly...
https://www.youtube.com/watch?v=anMx7W2-gLk
Truth to be told I didn't try that. I'll give it a go when at home - thanks
Sent from my Nexus 5X using Tapatalk
Related
Hi,
the android filesystem gives me headaches. since the last update of Titanium Backup the app doesn't work any more on two of mine devices (nexus 4 and nexus 10), it allways fails with insulficient storage. on my nexus 7 (2013) however it works perfect, so i started to investiage, what's the difference and came uppon the storage folder path. on the nexus 7 its storage/sdcard0/TitaniumBackup and on the nexus 4 & nexus 10 its storgae/emulated/legacy/TitaniumBackup. whit the version of TB before the last update it was possible to select storage/emulated/0/TitaniumBackup, which worked for those devices but since the last update this path gets allways converted to legacy and the developer doesn't react to this issue. so i started to play arount in the file explorer and noticed, that on both nexus 4 and 10 when i navigate to storage/emulated/0/ the sdcard content appears, while when navigating to storage/emulated/legacy/ or storage/sdcard0 nothin appears. on the nexus 7 on the other hand the content appears in storage/emulated/legacy and storage/sdcard0 while storage/emulated/0 doesn't even exist.
I know, that most of this folders are simlinks but how to tell which one is a link an where the real data is stored - and how to adapt the filestruktur of the nexus 7 to the other devices so that backup will work again? don't think copying from emulated/0 to storage will work, or?
Thanks for any help!
Anyone?
Please, I need to get TB back up working since I can't use Helium/Carbon, because it absolutely sucks (not possible to backup all apps, automation not possible when using a pin like everyone should, not as reliable as TB was).
Hi All,
I'm in a critical situation. I was using Catch notes for few of my personal data until today, unaware of the fact that it is no longer supported. I mistyped my passcode, and ever since it wont allow me inside and access my notes. i tried searching through individual folders, just in case the notes are in plain text. No Luck!!! As per other xda user, i checked in the folder Android/data/com.threebananas, still found nothing.
I terribly need the information. So I'm thinking of breaking the app and try by passing the passcode/password check. i know this puts a moral question. But based on my situation I'm convincing myself saying its ok, as it is no longer supported!!! and nobody will be impacted, expect myself and of course I need the data.
I have little experience in trying to look through software/apps and tweak them for my necessity, with little success. Now I'm not even sure if this break-in is possible. I'm totally out of date with respect to these kind of stuff. So any help ANY HELP will be very much appreciated.
Note: I use Samsung Galaxy S3 (GT-I9300), rooted, ver 4.1.2.
Regards,
Mathi
I'm in the same bad situation and i don't know what can i do and i need my data
i am doomed as well
The same issue. Dozens of ideas lost. My 4 digit catch password simply is not recognized. Gratefull for any help.
Found a solution.
Are there anyone still having this problem?
Here is how I got the data back.
(1) back up the data
% adb backup com.threebanana.notes
(2) unpack the backup file
% java -jar abe.jar unpack backup.ab backup.tar
(3) untar the backup.tar & locate notes_pad.db
(4) uninstall & reinstall the "Catch" app
(5) back up the data from the newly installed app
(6) unpack the backup file
(7) open the backup.tar (do not untar; just open it), and replace the notes_pad.db with the original one (should be in backup folder)
(8) pack the backup file
% java -jar abe.jar pack backup.tar backup.ab
(9) restore the data
% adb restore backup.ab
We are a large urban school district located in southern California that will be soon be distributing approximately 11,000 android tablets to our first grade classrooms. The biggest challenge we’ve had with this project so far is coming up with a way to quickly and reliably clone the devices with all the apps and settings. The approach we’ve been attempting to take is the same as how we would handle PC’s by creating a master image that then gets copied to all the other devices.
Our first attempt at doing this was by using adb backup/restore. This process was less than ideal as it didn’t copy all the settings/preferences that we wanted and still required a lot of manual configuration to get the devices in to our ideal state. The bigger problem we had here was that sometimes it would just hang during the restore. Most of the time it did work but we’ve run in to this restore problem enough that we need something more reliable.
So our current cloning method is using Clockworkmod Recovery. Basically we flash CWM on to the device, make our backup, copy that backup to the destination devices and restore it with CWM. Seems to work great. And it copies everything on the devices so there’s virtually no manual configuration that needs to be done.
However there’s a few caveats with this process. At first we found that it was also cloning the MAC address which of course caused havoc on our wireless network. Through a whole lot of trial and error I found that if I delete /data/nvram/RestoreFlag from the data backup tar the MAC address no longer gets cloned. Thought we were good, but…
The next problem we found when attempting to enroll the devices in to our MDM system. They end up replacing each other because they all show the same UDID and GUID. The MDM app is installed in the backup image but we are waiting until after it is restored to complete the enrollment. I’m not sure if the UDID and GUID is something specific to the MDM or if that’s a global Android thing.
So does anyone know if there something else I can delete from the backup to prevent this? This also raises the question, are there any other items in a CWM backup that should not be copied between devices? Or is there a better method we could use to clones the devices?
The device we are currently using is a Lenovo A1000 (MTK MT8317). After creating the backup I’ve been removing the system and cache tars entirely and only the file mentioned above from within the data tar. So the only parts that get restored are data and boot. Any suggestions are welcome.
ttttttttttttttttt said:
We are a large urban school district located in southern California that will be soon be distributing approximately 11,000 android tablets to our first grade classrooms. The biggest challenge we’ve had with this project so far is coming up with a way to quickly and reliably clone the devices with all the apps and settings. The approach we’ve been attempting to take is the same as how we would handle PC’s by creating a master image that then gets copied to all the other devices.
Our first attempt at doing this was by using adb backup/restore. This process was less than ideal as it didn’t copy all the settings/preferences that we wanted and still required a lot of manual configuration to get the devices in to our ideal state. The bigger problem we had here was that sometimes it would just hang during the restore. Most of the time it did work but we’ve run in to this restore problem enough that we need something more reliable.
So our current cloning method is using Clockworkmod Recovery. Basically we flash CWM on to the device, make our backup, copy that backup to the destination devices and restore it with CWM. Seems to work great. And it copies everything on the devices so there’s virtually no manual configuration that needs to be done.
However there’s a few caveats with this process. At first we found that it was also cloning the MAC address which of course caused havoc on our wireless network. Through a whole lot of trial and error I found that if I delete /data/nvram/RestoreFlag from the data backup tar the MAC address no longer gets cloned. Thought we were good, but…
The next problem we found when attempting to enroll the devices in to our MDM system. They end up replacing each other because they all show the same UDID and GUID. The MDM app is installed in the backup image but we are waiting until after it is restored to complete the enrollment. I’m not sure if the UDID and GUID is something specific to the MDM or if that’s a global Android thing.
So does anyone know if there something else I can delete from the backup to prevent this? This also raises the question, are there any other items in a CWM backup that should not be copied between devices? Or is there a better method we could use to clones the devices?
The device we are currently using is a Lenovo A1000 (MTK MT8317). After creating the backup I’ve been removing the system and cache tars entirely and only the file mentioned above from within the data tar. So the only parts that get restored are data and boot. Any suggestions are welcome.
Click to expand...
Click to collapse
You can try use adb from Android SDK but this method needs root
We did initially try adb but it was inconsistent during the restore phase. Sometimes it would just stop in the middle and never complete. Didn’t try it on a rooted device. So maybe that would have helped…
Anyhow I found the solution to my immediate problem. Figured out what our MDM vendor refers to as the UDID is really the Android_ID. So by deleting that row from the settings database in our master backup image it’ll generate a new one the first time the OS starts after restoring with CWM.
I’m still a little concerned we’re going to find other issues cause by this cloning method later on but I guess we’ll just have to roll with the punches as they come.
In case someone else ever needs to clone devices like this and in the interest of sharing here’s the basic steps we’re following.
1.) Setup the master device as you like with all the apps and settings.
2.) Install Clockworkmod Recovery on to the master device
3.) Boot into CWM Recovery
4.) Mount /data and connect to adb
5.) Delete /data/nvram/RestoreFlag (this step prevents duplication of MAC address)
6.) Using sqlite open the database (this prevents duplication of Android_ID): \data\data\com.android.providers.settings\databases\settings.db
execute: delete from secure where name='android_id';
7.) unmount /data
8.) Create a backup
9.) Boot the device back in to normal mode and copy the clockworkmod folder to your computer. This the backup image you’ll restore on the other devices.
10.) [OPTIONAL] I deleted the system and cache backup files from this folder and also removed them from the nandroid file. There didn’t seem to be anything in these we cared about so removing those speeds up the restore process.
Once you have the backup image here’s how to restore it on the other devices:
1.) Install CWM Recovery
2.) Copy the clockworkmod folder from your computer on to the device
3.) Boot in to CWM Recovery
4.) Restore the backup
5.) Reboot the device back in to normal mode
6.) [OPTIONAL] Complete MDM enrollment
Sorry for the thread grave dig, but thanks for posting info on how to do this. I have attempted cloning in the past and ran into similar issues. My question - is this process the same for Android Lollipop 5.0/5.1? I have some Lenovo K3 Notes I'd like to deploy and cloning would save a lot of time.
Haven’t had the need to do any devices running 5.x versions so can’t say for sure. I would imagine a similar process would work.
But I will provide a bit of an update. Our initial deployment of 11,000 Lenovo A1000 devices have been out in the field since February/March of 2014 and no trouble has come to light using this cloning method. These devices run 4.1.2
Sometime around May 2014 we did another round that was about 300 Lenovo A3000 devices. Don’t have one of these handy and I don’t remember the exact Android version but it was 4.x something.
Then starting in October 2014 we put out another 9000 or so Lenovo A3500 devices. These run 4.4.2
All around so far so good.
For the A3000 and A3500 there were two changes to the process. For step 5 in creating the backup I had to clear the entire nvram directory instead of just the one file. I don’t remember what exactly but there was something undesirable getting copied over. The result of clearing this directory is the first boot after the restore takes a little longer as each app runs through the “update” process at startup. The second change was I could not get CWM to backup and restore to/from the internal memory so instead did it from a micro-sd card. This ended up speeding up the restore process since we didn’t have to copy the backup to each device and instead just moved the sd card with the files already there.
this should be pinned in android dev
also sorry for grave digging? except this should be a maintained topic. why isnt this an ongoing thread?
Looking to setup a new phone I encountered the issue that there is no way from LINE itself to transfer chat, except the very tedious mechanism to ex- and import every single contact chat manually. What's worse, this doesn't work with group chats. The other documented alternative is using Titanium Backup, but this requires root. After some further investigation I finally discovered that the Android Debug Bridge (adb) - which is part of the official Android SDK - offers everything that is needed to backup and transfer LINE to second smartphone. That means it works root-free and without any paid tools. You can use this process either to transfer the data to a new device or to restore it to the same device, for this description I assume you're going to copy it to a new phone.
The short version is, you can use adb to:
Read out android_id
Install an old LINE version that allows adb backups (in LINE < 5.3 android:allowBackup is not set, thus by default true)
Backup LINE app data & LINE sdcard data
Set android_id (on new device), which LINE is checking to validate it's data
Restore LINE app data & LINE sdcard data (to new device)
The long version
Prerequisites
Enable the Email verification for your LINE account. If something goes wrong , you will at least have access to all of your contacts and messages of the last weeks.
You must have ADB working. I'm not going to explain how to install it in detail, you should be able to find Android Developer guides who cover that (e.g. http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/) The rough outline is:
- install Android SDK
- install USB phone drivers from you phone manufacture
- enable (hidden) Developer Mode/USB debug mode on your phones
Furthermore you must have an old line APK, I used LINE 5.1 You should have no issue to find it online in one of the APK archives. As mentioned earlier, the current versions of LINE does not allow ADB backups, like old versions do. Luckily you can install an old version, while keeping the data. Ideally the old LINE versions never runs, so that it has no chance to corrupt your chat-data. However even accidentally running it, didn't have any visible impact on my data, the app closed itself after starting.
For the next steps I assume you have a folder called c:\backup\line to store the backup inside and already containing a file called 'line-old.apk' which - as the name suggests - is your copy of an old line apk.
Backup old phone
) Close/Kill LINE app if it's running, disconnect from WLAN and put into flight mode (to ensure that nothing wants to interact with the LINE app) and connect your old phone via USB cable
------
) Start ADB service:
Code:
adb start-server
Accept access/fingerprint from ADB on your old phone, if you haven't done so already
------
) Create a file called android_id.txt that contains your android_id:
Code:
adb shell settings get secure android_id > c:\backup\line\android_id.txt
You can also use "adb shell settings get secure android_id" to simply show the current android_id value.
------
) Install old LINE Version:
Code:
adb install -r -d c:\backup\line\line-old.apk
-r = reinstall, keep data; -d = allow to install older version
------
) Backup LINE app data (chats) to your PC:
Code:
adb backup -f c:\backup\line\line.ab jp.naver.line.android
You need to click 'allow backup' on your old phone
------
) Backup LINE sdcard data (images, sticker) to your PC:
Code:
adb pull /sdcard/Android/data/jp.naver.line.android c:\backup\line\sdcard
------
) (optional) restore current LINE APK, either by using an APK like in step 4.) or via updating through Google Play store
------
) End ADB service
Code:
adb kill-server
------
) Finished, disconnect your old phone from your PC
Restore to (new) phone:
) Connect your new phone via USB cable
------
) Start ADB service:
Code:
adb start-server
Accept access/fingerprint from ADB on your new phone, if you haven't done so already
------
) Change your new phone android_id to that of your old phone. Replace XXXXXXXX with the value inside c:\backup\line\android_id.txt
Code:
adb shell settings put secure android_id XXXXXXXX
You can use "adb shell settings get secure android_id" to show the current android_id value.
------
) Install old LINE Version:
Code:
adb install -r -d c:\backup\line\line-old.apk
-r = reinstall, keep data; -d = allow to install older version
------
) Upload LINE app data (chats) to your new phone:
Code:
adb restore c:\backup\line\line.ab
Click on your phone to "restore my data"
------
) Upload LINE sdcard data (images, sticker) to your new phone:
Code:
adb push c:\backup\line\sdcard /sdcard/Android/data/jp.naver.line.android
------
) Install current LINE APK, either by using an APK like in step 4.) or via updating through Google Play store
------
) End ADB service
Code:
adb kill-server
------
) Finished, disconnect your new phone from your PC
Final notes
Alternatively to changing the the android_id it used to be - and maybe still is? - possible to erase the settings. I haven't tried this and I can't see any real downsides to reusing the android_id. Considering how easy it is to change, I wouldn't consider it a specially protected property.
Thank you for the very good description!
However, when I try to downgrade current Line 7.3.0 I get an error message:
"c:\backup\line\line-old.apk: 1 file pushed. 5.0 MB/s (23629798 bytes in 4.516s)
pkg: /data/local/tmp/line-old.apk
Failure [INSTALL_FAILED_PERMISSION_MODEL_DOWNGRADE]
c:\tools>adb backup -f c:\backup\line\line.ab jp.naver.line.android
Now unlock your device and confirm the backup operation...
c:\tools>adb pull /sdcard/Android/data/jp.naver.line.android c:\backup\line\sdcard
/sdcard/Android/data/jp.naver.line.android/: 435 files pulled. 0.7 MB/s (1825753 bytes in 2.469s)!"
So the backup file: line.ab only become 42 bytes.
The Failure message semmes to be something new from Android 6 ?
Is there a way to get around this?
kamoj1 said:
Thank you for the very good description!
However, when I try to downgrade current Line 7.3.0 I get an error message:
"c:\backup\line\line-old.apk: 1 file pushed. 5.0 MB/s (23629798 bytes in 4.516s)
pkg: /data/local/tmp/line-old.apk
Failure [INSTALL_FAILED_PERMISSION_MODEL_DOWNGRADE]
c:\tools>adb backup -f c:\backup\line\line.ab jp.naver.line.android
Now unlock your device and confirm the backup operation...
c:\tools>adb pull /sdcard/Android/data/jp.naver.line.android c:\backup\line\sdcard
/sdcard/Android/data/jp.naver.line.android/: 435 files pulled. 0.7 MB/s (1825753 bytes in 2.469s)!"
So the backup file: line.ab only become 42 bytes.
The Failure message semmes to be something new from Android 6 ?
Is there a way to get around this?
Click to expand...
Click to collapse
If u have root the easiest way is
Get old android_id
Backup line with titanium backuo
Put old android_id on new device
Restore line backup
kamoj1 said:
So the backup file: line.ab only become 42 bytes.
The Failure message semmes to be something new from Android 6 ?
Is there a way to get around this?
Click to expand...
Click to collapse
I've looked around and the only way around that message is to uninstall the App. You can uninstall an app and keep it's data with adb, so in theory this should work:
Backup old phone
4) Install old LINE Version:
Code:
adb shell pm uninstall -k jp.naver.line.android
adb install -r -d c:\backup\line\line-old.apk
But fair warning, I haven't tried it myself.
Amazing! Working for me.
Thank you very much for your effort.
Very appreciated.
Hey there, hoping I can get a reply from you in regards to this tutorial.
I had followed everything to the T, made backups and made sure to be careful along the way... upon logging in on my new device, I had to log in via Facebook, wasn't a problem at all, and I was back into my account, however it seems like my chats didn't get moved over at all. On the otherhand, it seems like my stickers were able to be transferred over due to them popping up in my store (unless that's simply due to them being associated with my account).
I'm lucky enough to have root somewhat working (it's slightly broken atm) on my old device, so at least I was able to nandroid backup before attempting to backup/uninstall any data... and am currently attempting to restore back into the backup with hopes that all of my chat data is available as it was before I attempted to transfer.
Currently my root is broken, and cause any backups from TB to show an "insufficient space" error message (unless this is because I am using a PRO apk I found somewhere... maybe I should try another TB apk.
Anyhow, I also ran into the "Failure INSTALL_FAILED_PERMISSION_MODEL_DOWNGRADE" which the above member ran into and used your suggested steps which seemed to work for him.
Waiting on your reply! Thanks ahead of time!
Sounds to me like your data wasn't transferred at all. Stickers are indeed bound to your account and remain with it even if you switch from Android to iOS. Unless you had your old phone connected to the internet and used LINE again, the data should be still on that phone. (LINE is deleting it, if it detects you moved to a second phone (or probably changed the android_id?)).
Anyways, trying to pin down your issue: As part of the first steps, you should have created backup files of your chats (line.ab) and your sd card. Did they end up on your PC? line.ab for me was around 40MB and there are plenty of files in the sdcard folder.
Can this method be used for line lite? what modification in the command should I use?
I want full version of it
Any new and easy way to move all line chat logs/chats along with images from a previous device to a new device?
https://help.line.me/line/android/pc?lang=en
desiregeek said:
Any new and easy way to move all line chat logs/chats along with images from a previous device to a new device?
https://help.line.me/line/android/pc?lang=en
Click to expand...
Click to collapse
I am afraid the solution in the link you provided doesn't allow the back-up of media that are older than a few weeks old (The rest of the chats will be backuped though
It looks like that the push command doesn't have the permissions to write anything on last Android versions like 12
Code:
adb push c:\backup\line\sdcard /sdcard/Android/data/
adb: error: failed to copy 'c:\backup\line\sdcard\jp.naver.line.android\.nomedia' to '/sdcard/Android/data/jp.naver.line.android/.nomedia': remote secure_mkdirs failed: Operation not permitted
adb: error: failed to read copy response
This is the main limit on an unrooted phone, I am trying to see if I can do anything repacking those together into the line.ab file which is possible to be restored but missing the other data.
Hello xda members,
I have a 6.0.1 GALAXY S5 with a broken screen, and used adb to make a TWRP backup.
Next, I tried using adb to retrieve Android ID in TWRP, and I get sh/bin/ not found error.
Nandroid manager successfully decompressed the backup, but it crashes when looking for the Android id.
Is there any method to find out the id of my broken phone, I only have access to the backup.