Just Solve the File Format Problem - User contributions [en]

How to move from Chromebook to Windows or MacBook

2023-10-26T01:43:31Z

Kayvon2008:

If you're currently using a Chromebook with ChromeOS and are looking to switch (or graduate) to a Windows computer, there are a few steps you can follow to make the transition as smooth as possible. While the two operating systems have some similarities, there are also some key differences that you'll need to be aware of. In this guide, we'll take you through the steps you need to follow to transfer your files, apps, and settings from ChromeOS to Windows, so you can get up and running on your new machine in no time. This tutorial can also work with macOS if you change some stuff. Unlike other transfers, including Windows <-> macOS or iOS <-> Android, moving away from ChromeOS does not come with compromise. Everything that can happen on a Chromebook can happen on a Windows sevice.

== Steps ==
=== Transfer browsing data ===
Note: your mileage may vary if the device is school or organization owned.

# Enable "sync everything" on the old Chromebook. Choose which information you want to sync. By default, all of the settings, apps, saved passwords, bookmarks, themes, payment info, history, and virtually everything else on your Chromebook (except your downloads, files, Android apps, and Linux data) is automatically synced to the cloud.[1] Just in case anything changed, double-check your sync settings to make sure you have everything you need:
#* Click the time at the bottom-right corner of your old Chromebook.
#* Click Settings (the gear icon).
#* Click Sync and Google services.
#* Click Manage what you sync.
#* Choose Sync everything to ensure that all of your data from this Chromebook will be available on your new Chromebook.
#* Alternatively, you can select Customize sync and choose to leave some things out.
# Unbox and complete the initial setup of the new Windows device.
# Download Google Chrome on Windows
# Sign in to your Google account previously used on the Chromebook on your Windows desktop.
# Turn on Sync and wait for all ChromeOS data to download onto your new Windows device.
# If this is not possible, go to the browser settings of both the source and target device and export and import all passwords (Autofill), bookmarks via chrome://bookmarks , and history via [https://chrome.google.com/webstore/detail/export-chrome-history/dihloblpkeiddiaojbagoecedbfpifdj this chrome extension].

=== Move files from ChromeOS to Windows ===
# Open the files app on your Chromebook, and click more, then click show hidden files.
# Go to “Trash” and recover all files you’ll think you might need in the future.
# Prepare a USB drive or cloud storage, and either move all of your files in “My Files” to the USB stick, or upload every item to the Cloud service of your choice
# Move or Download all files to the computer to the User folder (C:/Users/yourname), than if applicable delete all files from the USB storage device or cloud service

=== Move Cookies and LocalStorage from ChromeOS to Windows ===
# Install the chrome extension for [https://chrome.google.com/webstore/detail/editthiscookie/fngmhnnpilhplaeedifhccceomclgfbg cookies] and/or [https://chrome.google.com/webstore/detail/localstorage-manager/fkhoimdhngkiicbjobkinobjkoefhkap local storage] when necessary on both devices.
# Use each extension to transfer the login data, settings, and other data from one browser to another. This does include Windows93 and MicroBit MakeCode data, the configuration data for some sites, notes that store in a browser, and other stuff. If you just use this for login data, you will not need to use this part.

=== Transfer Android data from ChromeOS to Windows ===
Note: This process is only available on Chromebooks launched after 2020. Please check the chromebook model's release date before doing the process. If your Chromebook is older, skip to the step with "file manager plus". Additionally, macOS is not supported for the transfer of Android apps, due to no Android container or emulator software outside app testing purposes exists as of June, 28, 2023. macOS only supports iOS app emulation, so if you are using macOS, copy the entire "Play Files" folder with the "show all" options checked.
# Install the Linux container on your Chromebook if you haven’t already. Note that it will take 10 gigabytes of storage.
# Open the terminal app and paste: sudo apt-get install android-sdk-platform-tools and click enter, and wait for adb to install, and type “adb” to test.
# On the Chromebook, Select Settings Advanced, Developers, In the left panel, select Linux, Develop Android apps. Turn on Enable ADB debugging. Select Restart. … Select Confirm and sign in. Important: Once you turn on ADB, it’s available to all accounts on your Chromebook. To turn it off, you must factory reset (Powerwash) your Chromebook, and the chromebook will permanently display a warning on the lock screen. If you would like to not do this, skip a few steps.
# Type “adb backup -all -apk -system -obb -shared -keyvalue” on the Linux terminal and hit enter. Confirm the backup operation on the Chromebook.
# Wait for the ADB backup to complete.
# After the backup is complete, get “backup.ab” and move it to the place you transferred your files, camera, and downloads.
# Launch Windows Subsystem for Android.
# Here, enable Developer mode then tap on Manage developer settings.
# Use your left mouse button to scroll down until you find Wireless debugging. Tap to open it and enable it.
# Tap on Pair device with pairing code.
# Take note of Wi-Fi pairing code, and IP address and port.
# Launch Windows Terminal and make sure ADB is installed ([https://web.archive.org/web/20221203173623/https://www.xda-developers.com/install-adb-windows-macos-linux/#adbsetupwindows install ADB first]).
# Use command adb pair <IP:port> to pair ADB with WSA.
# In Wireless debugging window, see Device name and under it IP address and port.
# Use command adb connect <IP:port> to connect WSA with ADB.
# Once this is done, use command adb devices to make sure that WSA is connected.
# When you have confirmed that you have been connected to the Subsystem, type the following command, “adb restore (path to backup.ab)”
# Wait until the process restores all ChromeOS data to the PC
# Check if every application is installed
# If an application is missing, or you believe the ADB method is too complicated, download the “File Manager +” app on the Play Store, go to apps, and extract every APK that you would like to transfer.
# Go to the Files app, go to the “Play Files” and click more, and check both hidden file checkmarks.
# Move the “backups” to the moving system of your choice, and if you did NOT use the adb method, copy/move all folders to the moving system (usb, cloud)
# Install WSATools on the PC, and manually install each APK.
# Some apps do not support ADB backup for data, so try manually backuping apps, by checking the settings of the app, and clicking the back up option, moving the data, then using the restore option on the windows computer.

=== Transfer Linux container from ChromeOS to Windows ===
# If you do not use Linux containers, or just installed it for ADB, skip this part.
# On your Chromebook, at the bottom right, select the time.
# Select Settings and then Advanced and then Developers.
# Select Linux and then Back up and restore.
# To manually back up your Linux apps and files, select Back up.
# At the left, under "My files," choose where to save your files.
# Write your file name and select Save.
# At the bottom right, a backup progress notification will appear.
# Move the Linux backup to your PC
# In the PC’s File Explorer, rename your backup from .tini to .tar.gz.
# Use your method of choice to restore the backup onto the PC, or move all the files from the Home directory.
# An alternate method to export the Linux container, especially in incidents it will not boot is via "vmc export penguin "The name of a USB device connected" " which will generate a .tar.gz file on the usb drive.
# If you have used hacks via the vmc command before, or use the Parallels VM, use vmc via vmc list and export each additional vmc container first.

=== Extension Data ===
# Check every extension for data, and if so, export or backup the data of the application, and than move to the PC, than restore or import the data using the extension.

=== Other users ===
# If you have multiple users of the Chromebook, and want to transfer multiple users from ChromeOS to Windows, create an account for each user you would like to transfer.
# Repeat the transfer process for each user you would like to move.

=== Untransferable Data ===
# The following data cannot be transferred as of now:
#* Terminal app settings (backed up in the cloud but not restorable)
#* Crosh history (local, unexportable)
#* Extension data that cannot be backed up or exported
#* Android apps that do not support any form of Backup
#* Some chromebook settings are stored in the cloud, including WiFi networks, and not restorable to a non-ChromeOS device
#* Some chromebook settings are stored on-device and non-transferable, like Flags and Bluetooth configuration.
#* Cached webpage data

__PARTS__

[[Category:ChromeOS]]
[[Category:Windows]]
[[Category:Information]]
[[Category:Articles in Quality Review]]

Google Takeout

2023-06-30T01:15:56Z

Kayvon2008: /* Services NOT included in takeout */

{{FormatInfo
|formattype=electronic
|subcat=Backup
}}
[[Google Takeout]] is a [[Google]] service that provides an archived copy of data associated with a Google account (an account on all Google services like Gmail, [[Google Drive]], [[YouTube]], and more).

== Discussion==
ArchiveTeam HIGHLY recommends taking out your primary school (Elementary, middle, high) when you complete it.
# Nostalgia - checking your old work
# '''Future use - Colleges and businesses might need old work.'''
# Personal data - Sometimes you store non-school files on school services, or you do non-school things during school.

==Takeout==
Google Takeout offers a near complete backup of your data straight from the cloud. Please send feedback to google if you realize something’s missing.

https://takeout.google.com/

Note: please enable: Access log activity and click the gear icon in google drive and tick the 2 boxes for the maximum amount of data.

==Services NOT included in takeout==
*[[Android Google Drive Backup]]s
*Feedburner data (go to the feedburner website to export it yourself)
*[[Google drive WhatsApp backup]]s, pretty much the same deal as [[iCloud WhatsApp Backup]]s
*Chrome canvas data
*Chrome cursive data
*[https://www.google.com/tools/feedback/reports?hl=en Feedback made by the icon]
*Google custom search engine data
*Google Alerts data
*Google 9-square launcher icon configuration
*Google drive "private app data"
*Google Scholar data
*Teachable Machine Data
*Management-related data (cpu usage, etc)
*Find my mobile location data
* Google drive and workplace settings
*(unconfirmed) Some Google Chrome sync data other than those listed.
*Recently permanently deleted data
*Possibly more…

[[Category:Archiving]]
[[Category:Google]]

Google Takeout

2023-06-30T01:09:56Z

Kayvon2008:

{{FormatInfo
|formattype=electronic
|subcat=Backup
}}
[[Google Takeout]] is a [[Google]] service that provides an archived copy of data associated with a Google account (an account on all Google services like Gmail, [[Google Drive]], [[YouTube]], and more).

== Discussion==
ArchiveTeam HIGHLY recommends taking out your primary school (Elementary, middle, high) when you complete it.
# Nostalgia - checking your old work
# '''Future use - Colleges and businesses might need old work.'''
# Personal data - Sometimes you store non-school files on school services, or you do non-school things during school.

==Takeout==
Google Takeout offers a near complete backup of your data straight from the cloud. Please send feedback to google if you realize something’s missing.

https://takeout.google.com/

Note: please enable: Access log activity and click the gear icon in google drive and tick the 2 boxes for the maximum amount of data.

==Services NOT included in takeout==
*[[Android Google Drive Backup]]s
*Feedburner data (go to the feedburner website to export it yourself)
*[[Google drive WhatsApp backup]]s, pretty much the same deal as [[iCloud WhatsApp Backup]]s
*Chrome canvas data
*[https://www.google.com/tools/feedback/reports?hl=en Feedback made by the icon]
*Google custom search engine data
*Google Alerts data
*Google 9-square launcher icon configuration
*Google drive "private app data"
*Google Scholar data
*Teachable Machine Data
*Management-related data (cpu usage, etc)
*Find my mobile location data
* Google drive and workplace settings
*(unconfirmed) Some Google Chrome sync data other than those listed.
*Recently permanently deleted data
*Possibly more…

[[Category:Archiving]]
[[Category:Google]]

How to move from Chromebook to Windows or MacBook

2023-06-29T22:42:57Z

Kayvon2008:

If you're currently using a Chromebook with ChromeOS and are looking to switch (or graduate) to a Windows computer, there are a few steps you can follow to make the transition as smooth as possible. While the two operating systems have some similarities, there are also some key differences that you'll need to be aware of. In this guide, we'll take you through the steps you need to follow to transfer your files, apps, and settings from ChromeOS to Windows, so you can get up and running on your new machine in no time. This tutorial can also work with macOS if you change some stuff. Unlike other transfers, including Windows <-> macOS or iOS <-> Android, moving away from ChromeOS does not come with compromise. Everything that can happen on a Chromebook can happen on a Windows sevice.
[[Category:Windows]]
[[Category:Articles in Quality Review]]

== Steps ==
=== Transfer browsing data ===
# Enable "sync everything" on the old Chromebook. Choose which information you want to sync. By default, all of the settings, apps, saved passwords, bookmarks, themes, payment info, history, and virtually everything else on your Chromebook (except your downloads, files, Android apps, and Linux data) is automatically synced to the cloud.[1] Just in case anything changed, double-check your sync settings to make sure you have everything you need:
#* Click the time at the bottom-right corner of your old Chromebook.
#* Click Settings (the gear icon).
#* Click Sync and Google services.
#* Click Manage what you sync.
#* Choose Sync everything to ensure that all of your data from this Chromebook will be available on your new Chromebook.
#* Alternatively, you can select Customize sync and choose to leave some things out.
# Unbox and complete the initial setup of the new Windows device.
# Download Google Chrome on Windows
# Sign in to your Google account previously used on the Chromebook on your Windows desktop.
# Turn on Sync and wait for all ChromeOS data to download onto your new Windows device.
# If this is not possible, go to the browser settings of both the source and target device and export and import all passwords (Autofill), bookmarks via chrome://bookmarks , and history via [https://chrome.google.com/webstore/detail/export-chrome-history/dihloblpkeiddiaojbagoecedbfpifdj this chrome extension].

=== Move files from ChromeOS to Windows ===
# Open the files app on your Chromebook, and click more, then click show hidden files.
# Go to “Trash” and recover all files you’ll think you might need in the future.
# Prepare a USB drive or cloud storage, and either move all of your files in “My Files” to the USB stick, or upload every item to the Cloud service of your choice
# Move or Download all files to the computer to the User folder (C:/Users/yourname), than if applicable delete all files from the USB storage device or cloud service

=== Move Cookies and LocalStorage from ChromeOS to Windows ===
# Install the chrome extension for [https://chrome.google.com/webstore/detail/editthiscookie/fngmhnnpilhplaeedifhccceomclgfbg cookies] and/or [https://chrome.google.com/webstore/detail/localstorage-manager/fkhoimdhngkiicbjobkinobjkoefhkap local storage] when necessary on both devices.
# Use each extension to transfer the login data, settings, and other data from one browser to another. This does include Windows93 and MicroBit MakeCode data, the configuration data for some sites, notes that store in a browser, and other stuff. If you just use this for login data, you will not need to use this part.

=== Transfer Android data from ChromeOS to Windows ===
Note: This process is only available on Chromebooks launched after 2020. Please check the chromebook model's release date before doing the process. If your Chromebook is older, skip to the step with "file manager plus". Additionally, macOS is not supported for the transfer of Android apps, due to no Android container or emulator software outside app testing purposes exists as of June, 28, 2023. macOS only supports iOS app emulation, so if you are using macOS, copy the entire "Play Files" folder with the "show all" options checked.
# Install the Linux container on your Chromebook if you haven’t already. Note that it will take 10 gigabytes of storage.
# Open the terminal app and paste: sudo apt-get install android-sdk-platform-tools and click enter, and wait for adb to install, and type “adb” to test.
# On the Chromebook, Select Settings Advanced, Developers, In the left panel, select Linux, Develop Android apps. Turn on Enable ADB debugging. Select Restart. … Select Confirm and sign in. Important: Once you turn on ADB, it’s available to all accounts on your Chromebook. To turn it off, you must factory reset (Powerwash) your Chromebook, and the chromebook will permanently display a warning on the lock screen. If you would like to not do this, skip a few steps.
# Type “adb backup -all -apk -system -obb -shared -keyvalue” on the Linux terminal and hit enter. Confirm the backup operation on the Chromebook.
# Wait for the ADB backup to complete.
# After the backup is complete, get “backup.ab” and move it to the place you transferred your files, camera, and downloads.
# Launch Windows Subsystem for Android.
# Here, enable Developer mode then tap on Manage developer settings.
# Use your left mouse button to scroll down until you find Wireless debugging. Tap to open it and enable it.
# Tap on Pair device with pairing code.
# Take note of Wi-Fi pairing code, and IP address and port.
# Launch Windows Terminal and make sure ADB is installed ([https://web.archive.org/web/20221203173623/https://www.xda-developers.com/install-adb-windows-macos-linux/#adbsetupwindows install ADB first]).
# Use command adb pair <IP:port> to pair ADB with WSA.
# In Wireless debugging window, see Device name and under it IP address and port.
# Use command adb connect <IP:port> to connect WSA with ADB.
# Once this is done, use command adb devices to make sure that WSA is connected.
# When you have confirmed that you have been connected to the Subsystem, type the following command, “adb restore (path to backup.ab)”
# Wait until the process restores all ChromeOS data to the PC
# Check if every application is installed
# If an application is missing, or you believe the ADB method is too complicated, download the “File Manager +” app on the Play Store, go to apps, and extract every APK that you would like to transfer.
# Go to the Files app, go to the “Play Files” and click more, and check both hidden file checkmarks.
# Move the “backups” to the moving system of your choice, and if you did NOT use the adb method, copy/move all folders to the moving system (usb, cloud)
# Install WSATools on the PC, and manually install each APK.
# Some apps do not support ADB backup for data, so try manually backuping apps, by checking the settings of the app, and clicking the back up option, moving the data, then using the restore option on the windows computer.

=== Transfer Linux container from ChromeOS to Windows ===
# If you do not use Linux containers, or just installed it for ADB, skip this part.
# On your Chromebook, at the bottom right, select the time.
# Select Settings and then Advanced and then Developers.
# Select Linux and then Back up and restore.
# To manually back up your Linux apps and files, select Back up.
# At the left, under "My files," choose where to save your files.
# Write your file name and select Save.
# At the bottom right, a backup progress notification will appear.
# Move the Linux backup to your PC
# In the PC’s File Explorer, rename your backup from .tini to .tar.gz.
# Use your method of choice to restore the backup onto the PC, or move all the files from the Home directory.
# An alternate method to export the Linux container, especially in incidents it will not boot is via "vmc export penguin "The name of a USB device connected" " which will generate a .tar.gz file on the usb drive.
# If you have used hacks via the vmc command before, or use the Parallels VM, use vmc via vmc list and export each additional vmc container first.

=== Extension Data ===
# Check every extension for data, and if so, export or backup the data of the application, and than move to the PC, than restore or import the data using the extension.

=== Other users ===
# If you have multiple users of the Chromebook, and want to transfer multiple users from ChromeOS to Windows, create an account for each user you would like to transfer.
# Repeat the transfer process for each user you would like to move.

=== Untransferable Data ===
# The following data cannot be transferred as of now:
#* Terminal app settings (backed up in the cloud but not restorable)
#* Crosh history (local, unexportable)
#* Extension data that cannot be backed up or exported
#* Android apps that do not support any form of Backup
#* Some chromebook settings are stored in the cloud, including WiFi networks, and not restorable to a non-ChromeOS device
#* Some chromebook settings are stored on-device and non-transferable, like Flags and Bluetooth configuration.
#* Cached webpage data

__PARTS__

How to move from Chromebook to Windows or MacBook

2023-06-29T03:41:20Z

Kayvon2008: /* Transfer Android data from ChromeOS to Windows */

If you're currently using a Chromebook with ChromeOS and are looking to switch (or graduate) to a Windows computer, there are a few steps you can follow to make the transition as smooth as possible. While the two operating systems have some similarities, there are also some key differences that you'll need to be aware of. In this guide, we'll take you through the steps you need to follow to transfer your files, apps, and settings from ChromeOS to Windows, so you can get up and running on your new machine in no time. This tutorial can also work with macOS if you change some stuff. Unlike other transfers, including Windows <-> macOS or iOS <-> Android, moving away from ChromeOS does not come with compromise. Everything that can happen on a Chromebook can happen on a Windows sevice.
[[Category:Windows]]
[[Category:Articles in Quality Review]]

== Steps ==
=== Transfer browsing data ===
# Enable "sync everything" on the old Chromebook. Choose which information you want to sync. By default, all of the settings, apps, saved passwords, bookmarks, themes, payment info, history, and virtually everything else on your Chromebook (except your downloads, files, Android apps, and Linux data) is automatically synced to the cloud.[1] Just in case anything changed, double-check your sync settings to make sure you have everything you need:
#* Click the time at the bottom-right corner of your old Chromebook.
#* Click Settings (the gear icon).
#* Click Sync and Google services.
#* Click Manage what you sync.
#* Choose Sync everything to ensure that all of your data from this Chromebook will be available on your new Chromebook.
#* Alternatively, you can select Customize sync and choose to leave some things out.
# Unbox and complete the initial setup of the new Windows device.
# Download Google Chrome on Windows
# Sign in to your Google account previously used on the Chromebook on your Windows desktop.
# Turn on Sync and wait for all ChromeOS data to download onto your new Windows device.
# If this is not possible, go to the browser settings of both the source and target device and export and import all passwords (Autofill), bookmarks via chrome://bookmarks , and history via [https://chrome.google.com/webstore/detail/export-chrome-history/dihloblpkeiddiaojbagoecedbfpifdj this chrome extension].

=== Move files from ChromeOS to Windows ===
# Open the files app on your Chromebook, and click more, then click show hidden files.
# Go to “Trash” and recover all files you’ll think you might need in the future.
# Prepare a USB drive or cloud storage, and either move all of your files in “My Files” to the USB stick, or upload every item to the Cloud service of your choice
# Move or Download all files to the computer to the User folder (C:/Users/yourname), than if applicable delete all files from the USB storage device or cloud service

=== Move Cookies and LocalStorage from ChromeOS to Windows ===
# Install the chrome extension for [https://chrome.google.com/webstore/detail/cookies-transfer/gglghmchcghfjeclmdjdhpigdcemleej cookies] and/or [https://chrome.google.com/webstore/detail/localstorage-manager/fkhoimdhngkiicbjobkinobjkoefhkap local storage] when necessary on both devices.
# Use each extension to transfer the login data, settings, and other data from one browser to another. This does include Windows93 and MicroBit MakeCode data, the configuration data for some sites, notes that store in a browser, and other stuff. If you just use this for login data, you will not need to use this part.

=== Transfer Android data from ChromeOS to Windows ===
Note: This process is only available on Chromebooks launched after 2020. Please check the chromebook model's release date before doing the process. If your Chromebook is older, skip to the step with "file manager plus". Additionally, macOS is not supported for the transfer of Android apps, due to no Android container or emulator software outside app testing purposes exists as of June, 28, 2023. macOS only supports iOS app emulation, so if you are using macOS, copy the entire "Play Files" folder with the "show all" options checked.
# Install the Linux container on your Chromebook if you haven’t already. Note that it will take 10 gigabytes of storage.
# Open the terminal app and paste: sudo apt-get install android-sdk-platform-tools and click enter, and wait for adb to install, and type “adb” to test.
# On the Chromebook, Select Settings Advanced, Developers, In the left panel, select Linux, Develop Android apps. Turn on Enable ADB debugging. Select Restart. … Select Confirm and sign in. Important: Once you turn on ADB, it’s available to all accounts on your Chromebook. To turn it off, you must factory reset (Powerwash) your Chromebook, and the chromebook will permanently display a warning on the lock screen. If you would like to not do this, skip a few steps.
# Type “adb backup -all -apk -system -obb -shared -keyvalue” on the Linux terminal and hit enter. Confirm the backup operation on the Chromebook.
# Wait for the ADB backup to complete.
# After the backup is complete, get “backup.ab” and move it to the place you transferred your files, camera, and downloads.
# Launch Windows Subsystem for Android.
# Here, enable Developer mode then tap on Manage developer settings.
# Use your left mouse button to scroll down until you find Wireless debugging. Tap to open it and enable it.
# Tap on Pair device with pairing code.
# Take note of Wi-Fi pairing code, and IP address and port.
# Launch Windows Terminal and make sure ADB is installed ([https://web.archive.org/web/20221203173623/https://www.xda-developers.com/install-adb-windows-macos-linux/#adbsetupwindows install ADB first]).
# Use command adb pair <IP:port> to pair ADB with WSA.
# In Wireless debugging window, see Device name and under it IP address and port.
# Use command adb connect <IP:port> to connect WSA with ADB.
# Once this is done, use command adb devices to make sure that WSA is connected.
# When you have confirmed that you have been connected to the Subsystem, type the following command, “adb restore (path to backup.ab)”
# Wait until the process restores all ChromeOS data to the PC
# Check if every application is installed
# If an application is missing, or you believe the ADB method is too complicated, download the “File Manager +” app on the Play Store, go to apps, and extract every APK that you would like to transfer.
# Go to the Files app, go to the “Play Files” and click more, and check both hidden file checkmarks.
# Move the “backups” to the moving system of your choice, and if you did NOT use the adb method, copy/move all folders to the moving system (usb, cloud)
# Install WSATools on the PC, and manually install each APK.
# Some apps do not support ADB backup for data, so try manually backuping apps, by checking the settings of the app, and clicking the back up option, moving the data, then using the restore option on the windows computer.

=== Transfer Linux container from ChromeOS to Windows ===
# If you do not use Linux containers, or just installed it for ADB, skip this part.
# On your Chromebook, at the bottom right, select the time.
# Select Settings and then Advanced and then Developers.
# Select Linux and then Back up and restore.
# To manually back up your Linux apps and files, select Back up.
# At the left, under "My files," choose where to save your files.
# Write your file name and select Save.
# At the bottom right, a backup progress notification will appear.
# Move the Linux backup to your PC
# In the PC’s File Explorer, rename your backup from .tini to .tar.gz.
# Use your method of choice to restore the backup onto the PC, or move all the files from the Home directory.
# An alternate method to export the Linux container, especially in incidents it will not boot is via "vmc export penguin "The name of a USB device connected" " which will generate a .tar.gz file on the usb drive.
# If you have used hacks via the vmc command before, or use the Parallels VM, use vmc via vmc list and export each additional vmc container first.

=== Extension Data ===
# Check every extension for data, and if so, export or backup the data of the application, and than move to the PC, than restore or import the data using the extension.

=== Other users ===
# If you have multiple users of the Chromebook, and want to transfer multiple users from ChromeOS to Windows, create an account for each user you would like to transfer.
# Repeat the transfer process for each user you would like to move.

=== Untransferable Data ===
# The following data cannot be transferred as of now:
#* Terminal app settings (backed up in the cloud but not restorable)
#* Crosh history (local, unexportable)
#* Extension data that cannot be backed up or exported
#* Android apps that do not support any form of Backup
#* Some chromebook settings are stored in the cloud, including WiFi networks, and not restorable to a non-ChromeOS device
#* Some chromebook settings are stored on-device and non-transferable, like Flags and Bluetooth configuration.
#* Cached webpage data

__PARTS__

How to move from Chromebook to Windows or MacBook

2023-06-29T03:38:32Z

Kayvon2008: /* Transfer Android data from ChromeOS to Windows */

If you're currently using a Chromebook with ChromeOS and are looking to switch (or graduate) to a Windows computer, there are a few steps you can follow to make the transition as smooth as possible. While the two operating systems have some similarities, there are also some key differences that you'll need to be aware of. In this guide, we'll take you through the steps you need to follow to transfer your files, apps, and settings from ChromeOS to Windows, so you can get up and running on your new machine in no time. This tutorial can also work with macOS if you change some stuff. Unlike other transfers, including Windows <-> macOS or iOS <-> Android, moving away from ChromeOS does not come with compromise. Everything that can happen on a Chromebook can happen on a Windows sevice.
[[Category:Windows]]
[[Category:Articles in Quality Review]]

== Steps ==
=== Transfer browsing data ===
# Enable "sync everything" on the old Chromebook. Choose which information you want to sync. By default, all of the settings, apps, saved passwords, bookmarks, themes, payment info, history, and virtually everything else on your Chromebook (except your downloads, files, Android apps, and Linux data) is automatically synced to the cloud.[1] Just in case anything changed, double-check your sync settings to make sure you have everything you need:
#* Click the time at the bottom-right corner of your old Chromebook.
#* Click Settings (the gear icon).
#* Click Sync and Google services.
#* Click Manage what you sync.
#* Choose Sync everything to ensure that all of your data from this Chromebook will be available on your new Chromebook.
#* Alternatively, you can select Customize sync and choose to leave some things out.
# Unbox and complete the initial setup of the new Windows device.
# Download Google Chrome on Windows
# Sign in to your Google account previously used on the Chromebook on your Windows desktop.
# Turn on Sync and wait for all ChromeOS data to download onto your new Windows device.
# If this is not possible, go to the browser settings of both the source and target device and export and import all passwords (Autofill), bookmarks via chrome://bookmarks , and history via [https://chrome.google.com/webstore/detail/export-chrome-history/dihloblpkeiddiaojbagoecedbfpifdj this chrome extension].

=== Move files from ChromeOS to Windows ===
# Open the files app on your Chromebook, and click more, then click show hidden files.
# Go to “Trash” and recover all files you’ll think you might need in the future.
# Prepare a USB drive or cloud storage, and either move all of your files in “My Files” to the USB stick, or upload every item to the Cloud service of your choice
# Move or Download all files to the computer to the User folder (C:/Users/yourname), than if applicable delete all files from the USB storage device or cloud service

=== Move Cookies and LocalStorage from ChromeOS to Windows ===
# Install the chrome extension for [https://chrome.google.com/webstore/detail/cookies-transfer/gglghmchcghfjeclmdjdhpigdcemleej cookies] and/or [https://chrome.google.com/webstore/detail/localstorage-manager/fkhoimdhngkiicbjobkinobjkoefhkap local storage] when necessary on both devices.
# Use each extension to transfer the login data, settings, and other data from one browser to another. This does include Windows93 and MicroBit MakeCode data, the configuration data for some sites, notes that store in a browser, and other stuff. If you just use this for login data, you will not need to use this part.

=== Transfer Android data from ChromeOS to Windows ===
Note: This process is only available on Chromebooks launched after 2020. Please check the chromebook model's release date before doing the process. If your Chromebook is older, skip to the step with "file manager plus"
# Install the Linux container on your Chromebook if you haven’t already. Note that it will take 10 gigabytes of storage.
# Open the terminal app and paste: sudo apt-get install android-sdk-platform-tools and click enter, and wait for adb to install, and type “adb” to test.
# On the Chromebook, Select Settings Advanced, Developers, In the left panel, select Linux, Develop Android apps. Turn on Enable ADB debugging. Select Restart. … Select Confirm and sign in. Important: Once you turn on ADB, it’s available to all accounts on your Chromebook. To turn it off, you must factory reset (Powerwash) your Chromebook, and the chromebook will permanently display a warning on the lock screen. If you would like to not do this, skip a few steps.
# Type “adb backup -all -apk -system -obb -shared -keyvalue” on the Linux terminal and hit enter. Confirm the backup operation on the Chromebook.
# Wait for the ADB backup to complete.
# After the backup is complete, get “backup.ab” and move it to the place you transferred your files, camera, and downloads.
# Launch Windows Subsystem for Android.
# Here, enable Developer mode then tap on Manage developer settings.
# Use your left mouse button to scroll down until you find Wireless debugging. Tap to open it and enable it.
# Tap on Pair device with pairing code.
# Take note of Wi-Fi pairing code, and IP address and port.
# Launch Windows Terminal and make sure ADB is installed ([https://web.archive.org/web/20221203173623/https://www.xda-developers.com/install-adb-windows-macos-linux/#adbsetupwindows install ADB first]).
# Use command adb pair <IP:port> to pair ADB with WSA.
# In Wireless debugging window, see Device name and under it IP address and port.
# Use command adb connect <IP:port> to connect WSA with ADB.
# Once this is done, use command adb devices to make sure that WSA is connected.
# When you have confirmed that you have been connected to the Subsystem, type the following command, “adb restore (path to backup.ab)”
# Wait until the process restores all ChromeOS data to the PC
# Check if every application is installed
# If an application is missing, or you believe the ADB method is too complicated, download the “File Manager +” app on the Play Store, go to apps, and extract every APK that you would like to transfer.
# Go to the Files app, go to the “Play Files” and click more, and check both hidden file checkmarks.
# Move the “backups” to the moving system of your choice, and if you did NOT use the adb method, copy/move all folders to the moving system (usb, cloud)
# Install WSATools on the PC, and manually install each APK.
# Some apps do not support ADB backup for data, so try manually backuping apps, by checking the settings of the app, and clicking the back up option, moving the data, then using the restore option on the windows computer.

=== Transfer Linux container from ChromeOS to Windows ===
# If you do not use Linux containers, or just installed it for ADB, skip this part.
# On your Chromebook, at the bottom right, select the time.
# Select Settings and then Advanced and then Developers.
# Select Linux and then Back up and restore.
# To manually back up your Linux apps and files, select Back up.
# At the left, under "My files," choose where to save your files.
# Write your file name and select Save.
# At the bottom right, a backup progress notification will appear.
# Move the Linux backup to your PC
# In the PC’s File Explorer, rename your backup from .tini to .tar.gz.
# Use your method of choice to restore the backup onto the PC, or move all the files from the Home directory.
# An alternate method to export the Linux container, especially in incidents it will not boot is via "vmc export penguin "The name of a USB device connected" " which will generate a .tar.gz file on the usb drive.
# If you have used hacks via the vmc command before, or use the Parallels VM, use vmc via vmc list and export each additional vmc container first.

=== Extension Data ===
# Check every extension for data, and if so, export or backup the data of the application, and than move to the PC, than restore or import the data using the extension.

=== Other users ===
# If you have multiple users of the Chromebook, and want to transfer multiple users from ChromeOS to Windows, create an account for each user you would like to transfer.
# Repeat the transfer process for each user you would like to move.

=== Untransferable Data ===
# The following data cannot be transferred as of now:
#* Terminal app settings (backed up in the cloud but not restorable)
#* Crosh history (local, unexportable)
#* Extension data that cannot be backed up or exported
#* Android apps that do not support any form of Backup
#* Some chromebook settings are stored in the cloud, including WiFi networks, and not restorable to a non-ChromeOS device
#* Some chromebook settings are stored on-device and non-transferable, like Flags and Bluetooth configuration.
#* Cached webpage data

__PARTS__

How to transfer all data from Chromebook to Windows or MacBook

2023-06-29T03:34:42Z

Kayvon2008: Kayvon2008 moved page How to transfer all data from Chromebook to Windows or MacBook to How to move from Chromebook to Windows or MacBook

#REDIRECT [[How to move from Chromebook to Windows or MacBook]]

How to move from Chromebook to Windows or MacBook

2023-06-29T03:34:41Z

Kayvon2008: Kayvon2008 moved page How to transfer all data from Chromebook to Windows or MacBook to How to move from Chromebook to Windows or MacBook

If you're currently using a Chromebook with ChromeOS and are looking to switch (or graduate) to a Windows computer, there are a few steps you can follow to make the transition as smooth as possible. While the two operating systems have some similarities, there are also some key differences that you'll need to be aware of. In this guide, we'll take you through the steps you need to follow to transfer your files, apps, and settings from ChromeOS to Windows, so you can get up and running on your new machine in no time. This tutorial can also work with macOS if you change some stuff. Unlike other transfers, including Windows <-> macOS or iOS <-> Android, moving away from ChromeOS does not come with compromise. Everything that can happen on a Chromebook can happen on a Windows sevice.
[[Category:Windows]]
[[Category:Articles in Quality Review]]

== Steps ==
=== Transfer browsing data ===
# Enable "sync everything" on the old Chromebook. Choose which information you want to sync. By default, all of the settings, apps, saved passwords, bookmarks, themes, payment info, history, and virtually everything else on your Chromebook (except your downloads, files, Android apps, and Linux data) is automatically synced to the cloud.[1] Just in case anything changed, double-check your sync settings to make sure you have everything you need:
#* Click the time at the bottom-right corner of your old Chromebook.
#* Click Settings (the gear icon).
#* Click Sync and Google services.
#* Click Manage what you sync.
#* Choose Sync everything to ensure that all of your data from this Chromebook will be available on your new Chromebook.
#* Alternatively, you can select Customize sync and choose to leave some things out.
# Unbox and complete the initial setup of the new Windows device.
# Download Google Chrome on Windows
# Sign in to your Google account previously used on the Chromebook on your Windows desktop.
# Turn on Sync and wait for all ChromeOS data to download onto your new Windows device.
# If this is not possible, go to the browser settings of both the source and target device and export and import all passwords (Autofill), bookmarks via chrome://bookmarks , and history via [https://chrome.google.com/webstore/detail/export-chrome-history/dihloblpkeiddiaojbagoecedbfpifdj this chrome extension].

=== Move files from ChromeOS to Windows ===
# Open the files app on your Chromebook, and click more, then click show hidden files.
# Go to “Trash” and recover all files you’ll think you might need in the future.
# Prepare a USB drive or cloud storage, and either move all of your files in “My Files” to the USB stick, or upload every item to the Cloud service of your choice
# Move or Download all files to the computer to the User folder (C:/Users/yourname), than if applicable delete all files from the USB storage device or cloud service

=== Move Cookies and LocalStorage from ChromeOS to Windows ===
# Install the chrome extension for [https://chrome.google.com/webstore/detail/cookies-transfer/gglghmchcghfjeclmdjdhpigdcemleej cookies] and/or [https://chrome.google.com/webstore/detail/localstorage-manager/fkhoimdhngkiicbjobkinobjkoefhkap local storage] when necessary on both devices.
# Use each extension to transfer the login data, settings, and other data from one browser to another. This does include Windows93 and MicroBit MakeCode data, the configuration data for some sites, notes that store in a browser, and other stuff. If you just use this for login data, you will not need to use this part.

=== Transfer Android data from ChromeOS to Windows ===
# Install the Linux container on your Chromebook if you haven’t already. Note that it will take 10 gigabytes of storage.
# Open the terminal app and paste: sudo apt-get install android-sdk-platform-tools and click enter, and wait for adb to install, and type “adb” to test.
# On the Chromebook, Select Settings Advanced, Developers, In the left panel, select Linux, Develop Android apps. Turn on Enable ADB debugging. Select Restart. … Select Confirm and sign in. Important: Once you turn on ADB, it’s available to all accounts on your Chromebook. To turn it off, you must factory reset (Powerwash) your Chromebook, and the chromebook will permanently display a warning on the lock screen. If you would like to not do this, skip a few steps.
# Type “adb backup -all -apk -system -obb -shared -keyvalue” on the Linux terminal and hit enter. Confirm the backup operation on the Chromebook.
# Wait for the ADB backup to complete.
# After the backup is complete, get “backup.ab” and move it to the place you transferred your files, camera, and downloads.
# Launch Windows Subsystem for Android.
# Here, enable Developer mode then tap on Manage developer settings.
# Use your left mouse button to scroll down until you find Wireless debugging. Tap to open it and enable it.
# Tap on Pair device with pairing code.
# Take note of Wi-Fi pairing code, and IP address and port.
# Launch Windows Terminal and make sure ADB is installed ([https://web.archive.org/web/20221203173623/https://www.xda-developers.com/install-adb-windows-macos-linux/#adbsetupwindows install ADB first]).
# Use command adb pair <IP:port> to pair ADB with WSA.
# In Wireless debugging window, see Device name and under it IP address and port.
# Use command adb connect <IP:port> to connect WSA with ADB.
# Once this is done, use command adb devices to make sure that WSA is connected.
# When you have confirmed that you have been connected to the Subsystem, type the following command, “adb restore (path to backup.ab)”
# Wait until the process restores all ChromeOS data to the PC
# Check if every application is installed
# If an application is missing, or you believe the ADB method is too complicated, download the “File Manager +” app on the Play Store, go to apps, and extract every APK that you would like to transfer.
# Go to the Files app, go to the “Play Files” and click more, and check both hidden file checkmarks.
# Move the “backups” to the moving system of your choice, and if you did NOT use the adb method, copy/move all folders to the moving system (usb, cloud)
# Install WSATools on the PC, and manually install each APK.
# Some apps do not support ADB backup for data, so try manually backuping apps, by checking the settings of the app, and clicking the back up option, moving the data, then using the restore option on the windows computer.

=== Transfer Linux container from ChromeOS to Windows ===
# If you do not use Linux containers, or just installed it for ADB, skip this part.
# On your Chromebook, at the bottom right, select the time.
# Select Settings and then Advanced and then Developers.
# Select Linux and then Back up and restore.
# To manually back up your Linux apps and files, select Back up.
# At the left, under "My files," choose where to save your files.
# Write your file name and select Save.
# At the bottom right, a backup progress notification will appear.
# Move the Linux backup to your PC
# In the PC’s File Explorer, rename your backup from .tini to .tar.gz.
# Use your method of choice to restore the backup onto the PC, or move all the files from the Home directory.
# An alternate method to export the Linux container, especially in incidents it will not boot is via "vmc export penguin "The name of a USB device connected" " which will generate a .tar.gz file on the usb drive.
# If you have used hacks via the vmc command before, or use the Parallels VM, use vmc via vmc list and export each additional vmc container first.

=== Extension Data ===
# Check every extension for data, and if so, export or backup the data of the application, and than move to the PC, than restore or import the data using the extension.

=== Other users ===
# If you have multiple users of the Chromebook, and want to transfer multiple users from ChromeOS to Windows, create an account for each user you would like to transfer.
# Repeat the transfer process for each user you would like to move.

=== Untransferable Data ===
# The following data cannot be transferred as of now:
#* Terminal app settings (backed up in the cloud but not restorable)
#* Crosh history (local, unexportable)
#* Extension data that cannot be backed up or exported
#* Android apps that do not support any form of Backup
#* Some chromebook settings are stored in the cloud, including WiFi networks, and not restorable to a non-ChromeOS device
#* Some chromebook settings are stored on-device and non-transferable, like Flags and Bluetooth configuration.
#* Cached webpage data

__PARTS__

How to transfer all data from Chromebook to Windows

2023-06-29T03:34:11Z

Kayvon2008: Kayvon2008 moved page How to transfer all data from Chromebook to Windows to How to transfer all data from Chromebook to Windows or MacBook

#REDIRECT [[How to transfer all data from Chromebook to Windows or MacBook]]

How to move from Chromebook to Windows or MacBook

2023-06-29T03:34:11Z

Kayvon2008: Kayvon2008 moved page How to transfer all data from Chromebook to Windows to How to transfer all data from Chromebook to Windows or MacBook

If you're currently using a Chromebook with ChromeOS and are looking to switch (or graduate) to a Windows computer, there are a few steps you can follow to make the transition as smooth as possible. While the two operating systems have some similarities, there are also some key differences that you'll need to be aware of. In this guide, we'll take you through the steps you need to follow to transfer your files, apps, and settings from ChromeOS to Windows, so you can get up and running on your new machine in no time. This tutorial can also work with macOS if you change some stuff. Unlike other transfers, including Windows <-> macOS or iOS <-> Android, moving away from ChromeOS does not come with compromise. Everything that can happen on a Chromebook can happen on a Windows sevice.
[[Category:Windows]]
[[Category:Articles in Quality Review]]

== Steps ==
=== Transfer browsing data ===
# Enable "sync everything" on the old Chromebook. Choose which information you want to sync. By default, all of the settings, apps, saved passwords, bookmarks, themes, payment info, history, and virtually everything else on your Chromebook (except your downloads, files, Android apps, and Linux data) is automatically synced to the cloud.[1] Just in case anything changed, double-check your sync settings to make sure you have everything you need:
#* Click the time at the bottom-right corner of your old Chromebook.
#* Click Settings (the gear icon).
#* Click Sync and Google services.
#* Click Manage what you sync.
#* Choose Sync everything to ensure that all of your data from this Chromebook will be available on your new Chromebook.
#* Alternatively, you can select Customize sync and choose to leave some things out.
# Unbox and complete the initial setup of the new Windows device.
# Download Google Chrome on Windows
# Sign in to your Google account previously used on the Chromebook on your Windows desktop.
# Turn on Sync and wait for all ChromeOS data to download onto your new Windows device.
# If this is not possible, go to the browser settings of both the source and target device and export and import all passwords (Autofill), bookmarks via chrome://bookmarks , and history via [https://chrome.google.com/webstore/detail/export-chrome-history/dihloblpkeiddiaojbagoecedbfpifdj this chrome extension].

=== Move files from ChromeOS to Windows ===
# Open the files app on your Chromebook, and click more, then click show hidden files.
# Go to “Trash” and recover all files you’ll think you might need in the future.
# Prepare a USB drive or cloud storage, and either move all of your files in “My Files” to the USB stick, or upload every item to the Cloud service of your choice
# Move or Download all files to the computer to the User folder (C:/Users/yourname), than if applicable delete all files from the USB storage device or cloud service

=== Move Cookies and LocalStorage from ChromeOS to Windows ===
# Install the chrome extension for [https://chrome.google.com/webstore/detail/cookies-transfer/gglghmchcghfjeclmdjdhpigdcemleej cookies] and/or [https://chrome.google.com/webstore/detail/localstorage-manager/fkhoimdhngkiicbjobkinobjkoefhkap local storage] when necessary on both devices.
# Use each extension to transfer the login data, settings, and other data from one browser to another. This does include Windows93 and MicroBit MakeCode data, the configuration data for some sites, notes that store in a browser, and other stuff. If you just use this for login data, you will not need to use this part.

=== Transfer Android data from ChromeOS to Windows ===
# Install the Linux container on your Chromebook if you haven’t already. Note that it will take 10 gigabytes of storage.
# Open the terminal app and paste: sudo apt-get install android-sdk-platform-tools and click enter, and wait for adb to install, and type “adb” to test.
# On the Chromebook, Select Settings Advanced, Developers, In the left panel, select Linux, Develop Android apps. Turn on Enable ADB debugging. Select Restart. … Select Confirm and sign in. Important: Once you turn on ADB, it’s available to all accounts on your Chromebook. To turn it off, you must factory reset (Powerwash) your Chromebook, and the chromebook will permanently display a warning on the lock screen. If you would like to not do this, skip a few steps.
# Type “adb backup -all -apk -system -obb -shared -keyvalue” on the Linux terminal and hit enter. Confirm the backup operation on the Chromebook.
# Wait for the ADB backup to complete.
# After the backup is complete, get “backup.ab” and move it to the place you transferred your files, camera, and downloads.
# Launch Windows Subsystem for Android.
# Here, enable Developer mode then tap on Manage developer settings.
# Use your left mouse button to scroll down until you find Wireless debugging. Tap to open it and enable it.
# Tap on Pair device with pairing code.
# Take note of Wi-Fi pairing code, and IP address and port.
# Launch Windows Terminal and make sure ADB is installed ([https://web.archive.org/web/20221203173623/https://www.xda-developers.com/install-adb-windows-macos-linux/#adbsetupwindows install ADB first]).
# Use command adb pair <IP:port> to pair ADB with WSA.
# In Wireless debugging window, see Device name and under it IP address and port.
# Use command adb connect <IP:port> to connect WSA with ADB.
# Once this is done, use command adb devices to make sure that WSA is connected.
# When you have confirmed that you have been connected to the Subsystem, type the following command, “adb restore (path to backup.ab)”
# Wait until the process restores all ChromeOS data to the PC
# Check if every application is installed
# If an application is missing, or you believe the ADB method is too complicated, download the “File Manager +” app on the Play Store, go to apps, and extract every APK that you would like to transfer.
# Go to the Files app, go to the “Play Files” and click more, and check both hidden file checkmarks.
# Move the “backups” to the moving system of your choice, and if you did NOT use the adb method, copy/move all folders to the moving system (usb, cloud)
# Install WSATools on the PC, and manually install each APK.
# Some apps do not support ADB backup for data, so try manually backuping apps, by checking the settings of the app, and clicking the back up option, moving the data, then using the restore option on the windows computer.

=== Transfer Linux container from ChromeOS to Windows ===
# If you do not use Linux containers, or just installed it for ADB, skip this part.
# On your Chromebook, at the bottom right, select the time.
# Select Settings and then Advanced and then Developers.
# Select Linux and then Back up and restore.
# To manually back up your Linux apps and files, select Back up.
# At the left, under "My files," choose where to save your files.
# Write your file name and select Save.
# At the bottom right, a backup progress notification will appear.
# Move the Linux backup to your PC
# In the PC’s File Explorer, rename your backup from .tini to .tar.gz.
# Use your method of choice to restore the backup onto the PC, or move all the files from the Home directory.
# An alternate method to export the Linux container, especially in incidents it will not boot is via "vmc export penguin "The name of a USB device connected" " which will generate a .tar.gz file on the usb drive.
# If you have used hacks via the vmc command before, or use the Parallels VM, use vmc via vmc list and export each additional vmc container first.

=== Extension Data ===
# Check every extension for data, and if so, export or backup the data of the application, and than move to the PC, than restore or import the data using the extension.

=== Other users ===
# If you have multiple users of the Chromebook, and want to transfer multiple users from ChromeOS to Windows, create an account for each user you would like to transfer.
# Repeat the transfer process for each user you would like to move.

=== Untransferable Data ===
# The following data cannot be transferred as of now:
#* Terminal app settings (backed up in the cloud but not restorable)
#* Crosh history (local, unexportable)
#* Extension data that cannot be backed up or exported
#* Android apps that do not support any form of Backup
#* Some chromebook settings are stored in the cloud, including WiFi networks, and not restorable to a non-ChromeOS device
#* Some chromebook settings are stored on-device and non-transferable, like Flags and Bluetooth configuration.
#* Cached webpage data

__PARTS__

How to move from Chromebook to Windows or MacBook

2023-06-21T02:07:24Z

Kayvon2008: confirmed to be bougus

If you're currently using a Chromebook with ChromeOS and are looking to switch (or graduate) to a Windows computer, there are a few steps you can follow to make the transition as smooth as possible. While the two operating systems have some similarities, there are also some key differences that you'll need to be aware of. In this guide, we'll take you through the steps you need to follow to transfer your files, apps, and settings from ChromeOS to Windows, so you can get up and running on your new machine in no time. This tutorial can also work with macOS if you change some stuff. Unlike other transfers, including Windows <-> macOS or iOS <-> Android, moving away from ChromeOS does not come with compromise. Everything that can happen on a Chromebook can happen on a Windows sevice.
[[Category:Windows]]
[[Category:Articles in Quality Review]]

== Steps ==
=== Transfer browsing data ===
# Enable "sync everything" on the old Chromebook. Choose which information you want to sync. By default, all of the settings, apps, saved passwords, bookmarks, themes, payment info, history, and virtually everything else on your Chromebook (except your downloads, files, Android apps, and Linux data) is automatically synced to the cloud.[1] Just in case anything changed, double-check your sync settings to make sure you have everything you need:
#* Click the time at the bottom-right corner of your old Chromebook.
#* Click Settings (the gear icon).
#* Click Sync and Google services.
#* Click Manage what you sync.
#* Choose Sync everything to ensure that all of your data from this Chromebook will be available on your new Chromebook.
#* Alternatively, you can select Customize sync and choose to leave some things out.
# Unbox and complete the initial setup of the new Windows device.
# Download Google Chrome on Windows
# Sign in to your Google account previously used on the Chromebook on your Windows desktop.
# Turn on Sync and wait for all ChromeOS data to download onto your new Windows device.
# If this is not possible, go to the browser settings of both the source and target device and export and import all passwords (Autofill), bookmarks via chrome://bookmarks , and history via [https://chrome.google.com/webstore/detail/export-chrome-history/dihloblpkeiddiaojbagoecedbfpifdj this chrome extension].

=== Move files from ChromeOS to Windows ===
# Open the files app on your Chromebook, and click more, then click show hidden files.
# Go to “Trash” and recover all files you’ll think you might need in the future.
# Prepare a USB drive or cloud storage, and either move all of your files in “My Files” to the USB stick, or upload every item to the Cloud service of your choice
# Move or Download all files to the computer to the User folder (C:/Users/yourname), than if applicable delete all files from the USB storage device or cloud service

=== Move Cookies and LocalStorage from ChromeOS to Windows ===
# Install the chrome extension for [https://chrome.google.com/webstore/detail/cookies-transfer/gglghmchcghfjeclmdjdhpigdcemleej cookies] and/or [https://chrome.google.com/webstore/detail/localstorage-manager/fkhoimdhngkiicbjobkinobjkoefhkap local storage] when necessary on both devices.
# Use each extension to transfer the login data, settings, and other data from one browser to another. This does include Windows93 and MicroBit MakeCode data, the configuration data for some sites, notes that store in a browser, and other stuff. If you just use this for login data, you will not need to use this part.

=== Transfer Android data from ChromeOS to Windows ===
# Install the Linux container on your Chromebook if you haven’t already. Note that it will take 10 gigabytes of storage.
# Open the terminal app and paste: sudo apt-get install android-sdk-platform-tools and click enter, and wait for adb to install, and type “adb” to test.
# On the Chromebook, Select Settings Advanced, Developers, In the left panel, select Linux, Develop Android apps. Turn on Enable ADB debugging. Select Restart. … Select Confirm and sign in. Important: Once you turn on ADB, it’s available to all accounts on your Chromebook. To turn it off, you must factory reset (Powerwash) your Chromebook, and the chromebook will permanently display a warning on the lock screen. If you would like to not do this, skip a few steps.
# Type “adb backup -all -apk -system -obb -shared -keyvalue” on the Linux terminal and hit enter. Confirm the backup operation on the Chromebook.
# Wait for the ADB backup to complete.
# After the backup is complete, get “backup.ab” and move it to the place you transferred your files, camera, and downloads.
# Launch Windows Subsystem for Android.
# Here, enable Developer mode then tap on Manage developer settings.
# Use your left mouse button to scroll down until you find Wireless debugging. Tap to open it and enable it.
# Tap on Pair device with pairing code.
# Take note of Wi-Fi pairing code, and IP address and port.
# Launch Windows Terminal and make sure ADB is installed ([https://web.archive.org/web/20221203173623/https://www.xda-developers.com/install-adb-windows-macos-linux/#adbsetupwindows install ADB first]).
# Use command adb pair <IP:port> to pair ADB with WSA.
# In Wireless debugging window, see Device name and under it IP address and port.
# Use command adb connect <IP:port> to connect WSA with ADB.
# Once this is done, use command adb devices to make sure that WSA is connected.
# When you have confirmed that you have been connected to the Subsystem, type the following command, “adb restore (path to backup.ab)”
# Wait until the process restores all ChromeOS data to the PC
# Check if every application is installed
# If an application is missing, or you believe the ADB method is too complicated, download the “File Manager +” app on the Play Store, go to apps, and extract every APK that you would like to transfer.
# Go to the Files app, go to the “Play Files” and click more, and check both hidden file checkmarks.
# Move the “backups” to the moving system of your choice, and if you did NOT use the adb method, copy/move all folders to the moving system (usb, cloud)
# Install WSATools on the PC, and manually install each APK.
# Some apps do not support ADB backup for data, so try manually backuping apps, by checking the settings of the app, and clicking the back up option, moving the data, then using the restore option on the windows computer.

=== Transfer Linux container from ChromeOS to Windows ===
# If you do not use Linux containers, or just installed it for ADB, skip this part.
# On your Chromebook, at the bottom right, select the time.
# Select Settings and then Advanced and then Developers.
# Select Linux and then Back up and restore.
# To manually back up your Linux apps and files, select Back up.
# At the left, under "My files," choose where to save your files.
# Write your file name and select Save.
# At the bottom right, a backup progress notification will appear.
# Move the Linux backup to your PC
# In the PC’s File Explorer, rename your backup from .tini to .tar.gz.
# Use your method of choice to restore the backup onto the PC, or move all the files from the Home directory.
# An alternate method to export the Linux container, especially in incidents it will not boot is via "vmc export penguin "The name of a USB device connected" " which will generate a .tar.gz file on the usb drive.
# If you have used hacks via the vmc command before, or use the Parallels VM, use vmc via vmc list and export each additional vmc container first.

=== Extension Data ===
# Check every extension for data, and if so, export or backup the data of the application, and than move to the PC, than restore or import the data using the extension.

=== Other users ===
# If you have multiple users of the Chromebook, and want to transfer multiple users from ChromeOS to Windows, create an account for each user you would like to transfer.
# Repeat the transfer process for each user you would like to move.

=== Untransferable Data ===
# The following data cannot be transferred as of now:
#* Terminal app settings (backed up in the cloud but not restorable)
#* Crosh history (local, unexportable)
#* Extension data that cannot be backed up or exported
#* Android apps that do not support any form of Backup
#* Some chromebook settings are stored in the cloud, including WiFi networks, and not restorable to a non-ChromeOS device
#* Some chromebook settings are stored on-device and non-transferable, like Flags and Bluetooth configuration.
#* Cached webpage data

__PARTS__

How to move from Chromebook to Windows or MacBook

2023-06-18T23:33:17Z

Kayvon2008:

If you're currently using a Chromebook with ChromeOS and are looking to switch (or graduate) to a Windows computer, there are a few steps you can follow to make the transition as smooth as possible. While the two operating systems have some similarities, there are also some key differences that you'll need to be aware of. In this guide, we'll take you through the steps you need to follow to transfer your files, apps, and settings from ChromeOS to Windows, so you can get up and running on your new machine in no time. This tutorial can also work with macOS if you change some stuff. Unlike other transfers, including Windows <-> macOS or iOS <-> Android, moving away from ChromeOS does not come with compromise. Everything that can happen on a Chromebook can happen on a Windows sevice.
[[Category:Windows]]
[[Category:Articles in Quality Review]]

== Steps ==
=== Transfer browsing data ===
# Enable "sync everything" on the old Chromebook. Choose which information you want to sync. By default, all of the settings, apps, saved passwords, bookmarks, themes, payment info, history, and virtually everything else on your Chromebook (except your downloads, files, Android apps, and Linux data) is automatically synced to the cloud.[1] Just in case anything changed, double-check your sync settings to make sure you have everything you need:
#* Click the time at the bottom-right corner of your old Chromebook.
#* Click Settings (the gear icon).
#* Click Sync and Google services.
#* Click Manage what you sync.
#* Choose Sync everything to ensure that all of your data from this Chromebook will be available on your new Chromebook.
#* Alternatively, you can select Customize sync and choose to leave some things out.
# Unbox and complete the initial setup of the new Windows device.
# Download Google Chrome on Windows
# Sign in to your Google account previously used on the Chromebook on your Windows desktop.
# Turn on Sync and wait for all ChromeOS data to download onto your new Windows device.
# If this is not possible, go to the browser settings of both the source and target device and export and import all passwords (Autofill), bookmarks via chrome://bookmarks , and history via [https://chrome.google.com/webstore/detail/export-chrome-history/dihloblpkeiddiaojbagoecedbfpifdj this chrome extension].

=== Move files from ChromeOS to Windows ===
# Open the files app on your Chromebook, and click more, then click show hidden files.
# Go to “Trash” and recover all files you’ll think you might need in the future.
# Prepare a USB drive or cloud storage, and either move all of your files in “My Files” to the USB stick, or upload every item to the Cloud service of your choice
# Move or Download all files to the computer to the User folder (C:/Users/yourname), than if applicable delete all files from the USB storage device or cloud service

=== Move Cookies and LocalStorage from ChromeOS to Windows ===
# Install the chrome extension for [https://chrome.google.com/webstore/detail/cookies-transfer/gglghmchcghfjeclmdjdhpigdcemleej cookies] and/or [https://chrome.google.com/webstore/detail/localstorage-manager/fkhoimdhngkiicbjobkinobjkoefhkap local storage] when necessary on both devices.
# Use each extension to transfer the login data, settings, and other data from one browser to another. This does include Windows93 and MicroBit MakeCode data, the configuration data for some sites, notes that store in a browser, and other stuff. If you just use this for login data, you will not need to use this part.

=== Transfer Android data from ChromeOS to Windows ===
# Install the Linux container on your Chromebook if you haven’t already. Note that it will take 10 gigabytes of storage.
# Open the terminal app and paste: sudo apt-get install android-sdk-platform-tools and click enter, and wait for adb to install, and type “adb” to test.
# On the Chromebook, Select Settings Advanced, Developers, In the left panel, select Linux, Develop Android apps. Turn on Enable ADB debugging. Select Restart. … Select Confirm and sign in. Important: Once you turn on ADB, it’s available to all accounts on your Chromebook. To turn it off, you must factory reset (Powerwash) your Chromebook, and the chromebook will permanently display a warning on the lock screen. If you would like to not do this, skip a few steps.
# Type “adb backup -all -apk -system -obb -shared -keyvalue” on the Linux terminal and hit enter. Confirm the backup operation on the Chromebook.
# Wait for the ADB backup to complete.
# After the backup is complete, get “backup.ab” and move it to the place you transferred your files, camera, and downloads.
# Launch Windows Subsystem for Android.
# Here, enable Developer mode then tap on Manage developer settings.
# Use your left mouse button to scroll down until you find Wireless debugging. Tap to open it and enable it.
# Tap on Pair device with pairing code.
# Take note of Wi-Fi pairing code, and IP address and port.
# Launch Windows Terminal and make sure ADB is installed ([https://web.archive.org/web/20221203173623/https://www.xda-developers.com/install-adb-windows-macos-linux/#adbsetupwindows install ADB first]).
# Use command adb pair <IP:port> to pair ADB with WSA.
# In Wireless debugging window, see Device name and under it IP address and port.
# Use command adb connect <IP:port> to connect WSA with ADB.
# Once this is done, use command adb devices to make sure that WSA is connected.
# When you have confirmed that you have been connected to the Subsystem, type the following command, “adb restore (path to backup.ab)”
# Wait until the process restores all ChromeOS data to the PC
# Check if every application is installed
# If an application is missing, or you believe the ADB method is too complicated, download the “File Manager +” app on the Play Store, go to apps, and extract every APK that you would like to transfer.
# Go to the Files app, go to the “Play Files” and click more, and check both hidden file checkmarks.
# Move the “backups” to the moving system of your choice, and if you did NOT use the adb method, copy/move all folders to the moving system (usb, cloud)
# Install WSATools on the PC, and manually install each APK.
# Some apps do not support ADB backup for data, so try manually backuping apps, by checking the settings of the app, and clicking the back up option, moving the data, then using the restore option on the windows computer.
# An untested alternate method to export the Android container, which exports absolutely everything, and works in incidents it will not boot is via "vmc export arcvm "The name of a USB device connected" " . Note that it cannot be restored, only manually imported. Which will generate a .tar.gz file on the usb drive

=== Transfer Linux container from ChromeOS to Windows ===
# If you do not use Linux containers, or just installed it for ADB, skip this part.
# On your Chromebook, at the bottom right, select the time.
# Select Settings and then Advanced and then Developers.
# Select Linux and then Back up and restore.
# To manually back up your Linux apps and files, select Back up.
# At the left, under "My files," choose where to save your files.
# Write your file name and select Save.
# At the bottom right, a backup progress notification will appear.
# Move the Linux backup to your PC
# In the PC’s File Explorer, rename your backup from .tini to .tar.gz.
# Use your method of choice to restore the backup onto the PC, or move all the files from the Home directory.
# An alternate method to export the Linux container, especially in incidents it will not boot is via "vmc export penguin "The name of a USB device connected" " which will generate a .tar.gz file on the usb drive.
# If you have used hacks via the vmc command before, or use the Parallels VM, use vmc via vmc list and export each additional vmc container first.

=== Extension Data ===
# Check every extension for data, and if so, export or backup the data of the application, and than move to the PC, than restore or import the data using the extension.

=== Other users ===
# If you have multiple users of the Chromebook, and want to transfer multiple users from ChromeOS to Windows, create an account for each user you would like to transfer.
# Repeat the transfer process for each user you would like to move.

=== Untransferable Data ===
# The following data cannot be transferred as of now:
#* Terminal app settings (backed up in the cloud but not restorable)
#* Crosh history (local, unexportable)
#* Extension data that cannot be backed up or exported
#* Android apps that do not support any form of Backup
#* Some chromebook settings are stored in the cloud, including WiFi networks, and not restorable to a non-ChromeOS device
#* Some chromebook settings are stored on-device and non-transferable, like Flags and Bluetooth configuration.
#* Cached webpage data

__PARTS__

How to move from Chromebook to Windows or MacBook

2023-06-18T23:30:48Z

Kayvon2008: Created page with "If you're currently using a Chromebook with ChromeOS and are looking to switch (or graduate) to a Windows computer, there are a few steps you can follow to make the transition..."

If you're currently using a Chromebook with ChromeOS and are looking to switch (or graduate) to a Windows computer, there are a few steps you can follow to make the transition as smooth as possible. While the two operating systems have some similarities, there are also some key differences that you'll need to be aware of. In this guide, we'll take you through the steps you need to follow to transfer your files, apps, and settings from ChromeOS to Windows, so you can get up and running on your new machine in no time. This tutorial can also work with macOS if you change some stuff.
[[Category:Windows]]
[[Category:Articles in Quality Review]]

== Steps ==
=== Transfer browsing data ===
# Enable "sync everything" on the old Chromebook. Choose which information you want to sync. By default, all of the settings, apps, saved passwords, bookmarks, themes, payment info, history, and virtually everything else on your Chromebook (except your downloads, files, Android apps, and Linux data) is automatically synced to the cloud.[1] Just in case anything changed, double-check your sync settings to make sure you have everything you need:
#* Click the time at the bottom-right corner of your old Chromebook.
#* Click Settings (the gear icon).
#* Click Sync and Google services.
#* Click Manage what you sync.
#* Choose Sync everything to ensure that all of your data from this Chromebook will be available on your new Chromebook.
#* Alternatively, you can select Customize sync and choose to leave some things out.
# Unbox and complete the initial setup of the new Windows device.
# Download Google Chrome on Windows
# Sign in to your Google account previously used on the Chromebook on your Windows desktop.
# Turn on Sync and wait for all ChromeOS data to download onto your new Windows device.
# If this is not possible, go to the browser settings of both the source and target device and export and import all passwords (Autofill), bookmarks via chrome://bookmarks , and history via [https://chrome.google.com/webstore/detail/export-chrome-history/dihloblpkeiddiaojbagoecedbfpifdj this chrome extension].

=== Move files from ChromeOS to Windows ===
# Open the files app on your Chromebook, and click more, then click show hidden files.
# Go to “Trash” and recover all files you’ll think you might need in the future.
# Prepare a USB drive or cloud storage, and either move all of your files in “My Files” to the USB stick, or upload every item to the Cloud service of your choice
# Move or Download all files to the computer to the User folder (C:/Users/yourname), than if applicable delete all files from the USB storage device or cloud service

=== Move Cookies and LocalStorage from ChromeOS to Windows ===
# Install the chrome extension for [https://chrome.google.com/webstore/detail/cookies-transfer/gglghmchcghfjeclmdjdhpigdcemleej cookies] and/or [https://chrome.google.com/webstore/detail/localstorage-manager/fkhoimdhngkiicbjobkinobjkoefhkap local storage] when necessary on both devices.
# Use each extension to transfer the login data, settings, and other data from one browser to another. This does include Windows93 and MicroBit MakeCode data, the configuration data for some sites, notes that store in a browser, and other stuff. If you just use this for login data, you will not need to use this part.

=== Transfer Android data from ChromeOS to Windows ===
# Install the Linux container on your Chromebook if you haven’t already. Note that it will take 10 gigabytes of storage.
# Open the terminal app and paste: sudo apt-get install android-sdk-platform-tools and click enter, and wait for adb to install, and type “adb” to test.
# On the Chromebook, Select Settings Advanced, Developers, In the left panel, select Linux, Develop Android apps. Turn on Enable ADB debugging. Select Restart. … Select Confirm and sign in. Important: Once you turn on ADB, it’s available to all accounts on your Chromebook. To turn it off, you must factory reset (Powerwash) your Chromebook, and the chromebook will permanently display a warning on the lock screen. If you would like to not do this, skip a few steps.
# Type “adb backup -all -apk -system -obb -shared -keyvalue” on the Linux terminal and hit enter. Confirm the backup operation on the Chromebook.
# Wait for the ADB backup to complete.
# After the backup is complete, get “backup.ab” and move it to the place you transferred your files, camera, and downloads.
# Launch Windows Subsystem for Android.
# Here, enable Developer mode then tap on Manage developer settings.
# Use your left mouse button to scroll down until you find Wireless debugging. Tap to open it and enable it.
# Tap on Pair device with pairing code.
# Take note of Wi-Fi pairing code, and IP address and port.
# Launch Windows Terminal and make sure ADB is installed ([https://web.archive.org/web/20221203173623/https://www.xda-developers.com/install-adb-windows-macos-linux/#adbsetupwindows install ADB first]).
# Use command adb pair <IP:port> to pair ADB with WSA.
# In Wireless debugging window, see Device name and under it IP address and port.
# Use command adb connect <IP:port> to connect WSA with ADB.
# Once this is done, use command adb devices to make sure that WSA is connected.
# When you have confirmed that you have been connected to the Subsystem, type the following command, “adb restore (path to backup.ab)”
# Wait until the process restores all ChromeOS data to the PC
# Check if every application is installed
# If an application is missing, or you believe the ADB method is too complicated, download the “File Manager +” app on the Play Store, go to apps, and extract every APK that you would like to transfer.
# Go to the Files app, go to the “Play Files” and click more, and check both hidden file checkmarks.
# Move the “backups” to the moving system of your choice, and if you did NOT use the adb method, copy/move all folders to the moving system (usb, cloud)
# Install WSATools on the PC, and manually install each APK.
# Some apps do not support ADB backup for data, so try manually backuping apps, by checking the settings of the app, and clicking the back up option, moving the data, then using the restore option on the windows computer.
# An untested alternate method to export the Android container, which exports absolutely everything, and works in incidents it will not boot is via "vmc export arcvm "The name of a USB device connected" " . Note that it cannot be restored, only manually imported. Which will generate a .tar.gz file on the usb drive

=== Transfer Linux container from ChromeOS to Windows ===
# If you do not use Linux containers, or just installed it for ADB, skip this part.
# On your Chromebook, at the bottom right, select the time.
# Select Settings and then Advanced and then Developers.
# Select Linux and then Back up and restore.
# To manually back up your Linux apps and files, select Back up.
# At the left, under "My files," choose where to save your files.
# Write your file name and select Save.
# At the bottom right, a backup progress notification will appear.
# Move the Linux backup to your PC
# In the PC’s File Explorer, rename your backup from .tini to .tar.gz.
# Use your method of choice to restore the backup onto the PC, or move all the files from the Home directory.
# An alternate method to export the Linux container, especially in incidents it will not boot is via "vmc export penguin "The name of a USB device connected" " which will generate a .tar.gz file on the usb drive.
# If you have used hacks via the vmc command before, or use the Parallels VM, use vmc via vmc list and export each additional vmc container first.

=== Extension Data ===
# Check every extension for data, and if so, export or backup the data of the application, and than move to the PC, than restore or import the data using the extension.

=== Other users ===
# If you have multiple users of the Chromebook, and want to transfer multiple users from ChromeOS to Windows, create an account for each user you would like to transfer.
# Repeat the transfer process for each user you would like to move.

=== Untransferable Data ===
# The following data cannot be transferred as of now:
#* Terminal app settings (backed up in the cloud but not restorable)
#* Crosh history (local, unexportable)
#* Extension data that cannot be backed up or exported
#* Android apps that do not support any form of Backup
#* Some chromebook settings are stored in the cloud, including WiFi networks, and not restorable to a non-ChromeOS device
#* Some chromebook settings are stored on-device and non-transferable, like Flags and Bluetooth configuration.
#* Cached webpage data

__PARTS__

Android ADB Backup

2022-11-15T05:18:08Z

Kayvon2008: /* Structucture */

{{FormatInfo
|formattype=electronic
|subcat=Backup
|subcat2=Android Backup
|extensions={{ext|ab}}
}}
Android backups (.ab) are backups made by Android Debug Bridge (ADB). They are the preferred way of backing up an unrooted stock android device. (Manufacturers and/or carriers may provide their own backup tools). They can be encrypted (with AES) or unencrypted. They can be created via ADB backup and restored via ADB restore. Android backups themselves are [[Tape Archive|.TAR]] files with a different header and no footer. Unfortunately, there are no graphical tools yet (other than mobile forensic tools like Cellebrite Physical Analyzer, Oxygen Detective, Magnet AXIOM, and [https://www.mobiledit.com/forensic-express/details MobilEDIT Forensics], which are all payed) that can extract them, and they require the command line. It is compressed via the DEFLATE method.
===Header===
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
ANDROID BACKUP
1
1
none
</pre>

==Extraction==
It is extremely hard to extract them, and for the [https://sourceforge.net/projects/android-backup-processor/ best available tool] you need the command line (and knowledge how to use it) and Java installed. [https://www.softpedia.com/get/Mobile-Phone-Tools/Droid-Explorer.shtml Droid Explorer] claims to be able to extract ADB backups, but there is no prompt of extraction and is a pain to install. [https://stackoverflow.com/questions/18533567/how-to-extract-or-unpack-an-ab-file-android-backup-file Other command line tricks] may also convert it to an easily extractable TAR.
==Structucture==
<code> /app </code> Contains all app data 
<code> /app/(package id) </code> Contains app data 
<code> /app/(package id)/a </code> Contains app APK (app file) (if requested) (/data/app/) 
<code> /app/(package id)/f </code> Contains app files (/data/data/(package id)/files) 
<code> /app/(package id)/db </code> Contains app SQLite databases (open them [http://inloop.github.io/sqlite-viewer/ here]) (/data/data/(package id)/databases) 
<code> /app/(package id)/ef </code> Contains app shared data (storage/emulated/0/Android/data/(package id) ) 
<code> /app/(package id)/sp </code> Contains app shared prefrences (app settings), usually [[xml]] files (/data/data/(package id)/shared_preferences) 
<code> /app/(package id)/r </code> Contains app resources like webview data (like cookies) and texture cache (/data/data/(package id)/ 
<code> /app/(package id)/obb </code> Contains .obb files if specified in the backup (/storage/emulated/0/Android/obb/(package id) 
<code> /app/(package id)/_manifest </code> AndroidManifest.xml of the app 
<code> /shared </code> Contains shared files (/storage/emulated/0/) 

==Flags==
<code> -all </code> Backups all compatible apps 
<code> -f </code> Chooses the path and name for the file 
<code>(package id) </code> Backs up the stated package(s) if compatible. 
<code>-system </code> backups system apps if -all or a system package Id is stated. 
<code>-nosystem </code> does not back up system data. 
<code>-apk </code> Backs up the [[.apk]] of the app(s) 
<code>-noapk </code> does not back up apk files 
<code>-obb </code> Backs up [[.obb]] (app extention) files 
<code>-noobb </code> Does not back up .obb files 
<code>-shared </code> Backs up all shared storage (/storage/emulated/0/), including SD cards and USB OTGs, so it is recommended to eject and disconnect any external storage unless you want to back up that. 
<code>-noshared </code> does not back up shared storage. 
<code>-includekeyvalue </code> or <code>-keyvalue</code> Backs up apps that support Key Value backups. Key value backups were added in Android 2.2 “Froyo”, and this flag was added in Android 8.0 “Oreo” (Even since Developer Preview 1) 
<code>-nokeyvalue</code> Does not back up key value apps.

==Discontinuation==
Android backups are being discontinued and fully replaced by [[Android Google Drive Backup|Google Drive backups]]. Google drive backups cannot be downloaded, and there is a 25 MB per-app limit. You need a network sniffer to log upload traffic to capture these. The warning was there since the SDK of Android 10 “Queen Cake”, however, backups themselves weren’t changed. In Android 12 “Snow Cone”, apps with Snow Cone’s API level with backup flag set to true and a Snow Cone device will back up to (dumb) Google Drive instead.
[[Category:Android]]
[[Category:File formats with extension .ab]]

==Example==
[https://archive.org/download/cats_20211030/cats.ab cats.ab]: Extracted on a Galaxy Tab A with Android Nougat, Contains Android easter egg (com.android.egg) cats and render data.
==See also==
*[[iTunes backup]]

Just Solve the File Format Problem:Privacy policy

2022-07-29T04:55:47Z

Kayvon2008:

We do not collect any data for money because we are a nonprofit. We only collect the data you put in the wiki.

Just Solve the File Format Problem:General disclaimer

2022-07-29T04:53:15Z

Kayvon2008:

* Nobody who contributes here can ensure beyond a reasonable doubt that you will be able to use or convert to/from a given format.
* We just document the mess, [https://www.youtube.com/watch?v=eFTLKWw542g we didn't make it] (except those of us who did; you know who you are).
* Documentation is always incomplete and the real world changes quickly, and that goes double for file formats.
* If your favourite piece of knowledge about an obscure format is missing, it is because you didn't add it yet.
* Keep backups!
==ArchiveTeam disclaimer==

# We are NOT the internet archive.
# We aren’t responsible for your SSD or eMMC getting damaged during a warrior run due to using all the limited RW cycles. We also aren’t responsible for dither damaged media due to overuse or cycles. Please learn chemistry about your drive.
# We aren’t responsible for the data you pick up when running warrior. Not our fault, not your fault.
## We aren’t responsible for you picking up a virus during a warrior run and it ruining your life due to that.
## We aren’t responsible for you getting arrested by accidentally downloading child pornography or any other illegal materials in your country, as currently, there are no laws concerning unintentional archival or crawling of the data. Luckily methods to detect this locally prove unethical due to the code of human rights. To prevent a possible possibility of an arrest, disable the cloud backup of ArchiveTeam Warrior data and avoid giving access to your computer to other people unless absolutely necessary. All data will get deleted and overwritten by new data after the warrior uploads this data. If you find out that CP was accidentally archived, let it be. Navigate away and forget about it. Reporting it might ruin a Warrior user’s life and possibly cause them to take their own life due to prison.
## We aren’t responsible for getting horrified or any other negative feeling due to shock media, gore, rule 34 and 28 art, or anything else by peeking in a warrior capture.
## We aren’t responsible for damages caused by any cognitohazards or infohazards (if they exist online) like SCP-096 images if he was real.
# Please keep thermal stuff in mind. You will be responsible if your house burns down due to a drive or CPU or RAM catching on fire.

[[Category:Meta]]

ITunes backup

2022-04-12T20:25:08Z

Kayvon2008:

{{DISPLAYTITLE:iTunes backup}} {{FormatInfo
|formattype=electronic
|subcat=Backup
}}''iTunes backups'' are backups made by Apple iTunes and contain most of the data of any iOS-based device. Mac users use [[Time Machine]]. They can be encrypted. On newer iOS versions, some data can only be backed up with
encrypted backups. The backups themselves are files with a random string and can be opened individually with FilExt. Backups can be browsed with iMazing or iExplorer. Backups of an iPhone connected to an Apple Watch contain the Apple watch's backup. These backups can be compressed.
==Stuff '''ONLY''' included in encrypted backups==
*Safari History
*Keychain data (passwords)
*Health data
*Activity data
*WiFi passwords/settings
*Call logs

==Stuff '''NOT''' Included in iTunes backups==
*Your device passcode/password
*App packages (IPA)
*App Cache and Temporary files
*Stuff downloaded from iTunes
*PDFs downloaded to Apple Books
*Content synced from iTunes
*Data stored in iCloud, which need to be downloaded separately.
*Face ID data (faces)
*Touch ID data (fingerprint files)
*Apple Pay settings and data
*Apple Mail downloaded mails
*Logs (if you use iTunes they are there when synced)
===Apple Watch===
*Bluetooth pairings
*Credit or debit cards that are used for Apple Pay on your Apple Watch
*Passcode for your Apple Watch
*Messages (backed up to iCloud, download separately)
*Logs
*App packages

==See Also==
*[[iMazing Backup]]

Google Takeout

2022-04-04T23:21:36Z

Kayvon2008: /* Services NOT included in takeout */

{{FormatInfo
|formattype=electronic
|subcat=Backup
}}
[[Google Takeout]] is a [[Google]] service that provides an archived copy of data associated with a Google account (an account on all Google services like Gmail, [[Google Drive]], [[YouTube]], and more).

== Discussion==
ArchiveTeam HIGHLY recommends taking out your primary school (Elementary, middle, high) when you complete it.
# Nostalgia - checking your old work
# '''Future use - Colleges and businesses might need old work.'''
# Personal data - Sometimes you store non-school files on school services, or you do non-school things during school.

==Takeout==
Google Takeout offers a near complete backup of your data straight from the cloud. Please send feedback to google if you realize something’s missing.

https://takeout.google.com/

Note: please enable: Access log activity and click the gear icon in google drive and tick the 2 boxes for the maximum amount of data.

==Services NOT included in takeout==
*[[Android Google Drive Backup]]s
*Feedburner data (go to the feedburner website to export it yourself)
*[[Google drive WhatsApp backup]]s, pretty much the same deal as [[iCloud WhatsApp Backup]]s
*Chrome canvas data
*[https://www.google.com/tools/feedback/reports?hl=en Feedback made by the icon]
*Google custom search engine data
*Google Alerts data
*Google 9-square launcher icon configuration
*Google drive "private app data"
*Google Scholar data
*Teachable Machine Data
*Management-related data (cpu usage, etc)
*Find my mobile location data
* Google drive and workplace settings
*Recently permanently deleted data
*Possibly more…

[[Category:Archiving]]
[[Category:Google]]

Android ADB Backup

2022-03-21T08:13:18Z

Kayvon2008: /* Structucture */

{{FormatInfo
|formattype=electronic
|subcat=Backup
|subcat2=Android Backup
|extensions={{ext|ab}}
}}
Android backups (.ab) are backups made by Android Debug Bridge (ADB). They are the preferred way of backing up an unrooted stock android device. (Manufacturers and/or carriers may provide their own backup tools). They can be encrypted (with AES) or unencrypted. They can be created via ADB backup and restored via ADB restore. Android backups themselves are [[Tape Archive|.TAR]] files with a different header and no footer. Unfortunately, there are no graphical tools yet (other than mobile forensic tools like Cellebrite Physical Analyzer, Oxygen Detective, Magnet AXIOM, and [https://www.mobiledit.com/forensic-express/details MobilEDIT Forensics], which are all payed) that can extract them, and they require the command line. It is compressed via the DEFLATE method.
===Header===
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
ANDROID BACKUP
1
1
none
</pre>

==Extraction==
It is extremely hard to extract them, and for the [https://sourceforge.net/projects/android-backup-processor/ best available tool] you need the command line (and knowledge how to use it) and Java installed. [https://www.softpedia.com/get/Mobile-Phone-Tools/Droid-Explorer.shtml Droid Explorer] claims to be able to extract ADB backups, but there is no prompt of extraction and is a pain to install. [https://stackoverflow.com/questions/18533567/how-to-extract-or-unpack-an-ab-file-android-backup-file Other command line tricks] may also convert it to an easily extractable TAR.
==Structucture==
<code> /app </code> Contains all app data 
<code> /app/(package id) </code> Contains app data 
<code> /app/(package id)/a </code> Contains app APK (app file) (if requested) 
<code> /app/(package id)/f </code> Contains app files 
<code> /app/(package id)/db </code> Contains app SQLite databases (open them [http://inloop.github.io/sqlite-viewer/ here]) 
<code> /app/(package id)/ef </code> Contains app shared data (storage/emulated/0/Android/data/(package id) ) 
<code> /app/(package id)/sp </code> Contains app shared prefrences (app settings), usually [[xml]] files 
<code> /app/(package id)/r </code> Contains app resources like webview data (like cookies) and texture cache 
<code> /app/(package id)/obb </code> Contains .obb files if specified in the backup 
<code> /app/(package id)/_manifest </code> AndroidManifest.xml of the app 
<code> /shared </code> Contains shared files (/storage/emulated/0/) 

==Flags==
<code> -all </code> Backups all compatible apps 
<code> -f </code> Chooses the path and name for the file 
<code>(package id) </code> Backs up the stated package(s) if compatible. 
<code>-system </code> backups system apps if -all or a system package Id is stated. 
<code>-nosystem </code> does not back up system data. 
<code>-apk </code> Backs up the [[.apk]] of the app(s) 
<code>-noapk </code> does not back up apk files 
<code>-obb </code> Backs up [[.obb]] (app extention) files 
<code>-noobb </code> Does not back up .obb files 
<code>-shared </code> Backs up all shared storage (/storage/emulated/0/), including SD cards and USB OTGs, so it is recommended to eject and disconnect any external storage unless you want to back up that. 
<code>-noshared </code> does not back up shared storage. 
<code>-includekeyvalue </code> or <code>-keyvalue</code> Backs up apps that support Key Value backups. Key value backups were added in Android 2.2 “Froyo”, and this flag was added in Android 8.0 “Oreo” (Even since Developer Preview 1) 
<code>-nokeyvalue</code> Does not back up key value apps.

==Discontinuation==
Android backups are being discontinued and fully replaced by [[Android Google Drive Backup|Google Drive backups]]. Google drive backups cannot be downloaded, and there is a 25 MB per-app limit. You need a network sniffer to log upload traffic to capture these. The warning was there since the SDK of Android 10 “Queen Cake”, however, backups themselves weren’t changed. In Android 12 “Snow Cone”, apps with Snow Cone’s API level with backup flag set to true and a Snow Cone device will back up to (dumb) Google Drive instead.
[[Category:Android]]
[[Category:File formats with extension .ab]]

==Example==
[https://archive.org/download/cats_20211030/cats.ab cats.ab]: Extracted on a Galaxy Tab A with Android Nougat, Contains Android easter egg (com.android.egg) cats and render data.
==See also==
*[[iTunes backup]]

Android ADB Backup

2022-03-01T19:06:35Z

Kayvon2008: /* Structucture */

{{FormatInfo
|formattype=electronic
|subcat=Backup
|subcat2=Android Backup
|extensions={{ext|ab}}
}}
Android backups (.ab) are backups made by Android Debug Bridge (ADB). They are the preferred way of backing up an unrooted stock android device. (Manufacturers and/or carriers may provide their own backup tools). They can be encrypted (with AES) or unencrypted. They can be created via ADB backup and restored via ADB restore. Android backups themselves are [[Tape Archive|.TAR]] files with a different header and no footer. Unfortunately, there are no graphical tools yet (other than mobile forensic tools like Cellebrite Physical Analyzer, Oxygen Detective, Magnet AXIOM, and [https://www.mobiledit.com/forensic-express/details MobilEDIT Forensics], which are all payed) that can extract them, and they require the command line. It is compressed via the DEFLATE method.
===Header===
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
ANDROID BACKUP
1
1
none
</pre>

==Extraction==
It is extremely hard to extract them, and for the [https://sourceforge.net/projects/android-backup-processor/ best available tool] you need the command line (and knowledge how to use it) and Java installed. [https://www.softpedia.com/get/Mobile-Phone-Tools/Droid-Explorer.shtml Droid Explorer] claims to be able to extract ADB backups, but there is no prompt of extraction and is a pain to install. [https://stackoverflow.com/questions/18533567/how-to-extract-or-unpack-an-ab-file-android-backup-file Other command line tricks] may also convert it to an easily extractable TAR.
==Structucture==
<code> /app </code> Contains all app data 
<code> /app/(package id) </code> Contains app data 
<code> /app/(package id)/a </code> Contains app APK (app file) (if requested) 
<code> /app/(package id)/f </code> Contains app files 
<code> /app/(package id)/db </code> Contains app SQLite databases (open them [http://inloop.github.io/sqlite-viewer/ here]) 
<code> /app/(package id)/ef </code> Contains app shared data (storage/emulated/0/Android/data/(package id) ) 
<code> /app/(package id)/sp </code> Contains app shared prefrences (app settings), usually [[xml]] files 
<code> /app/(package id)/r </code> Contains app resources like webview data (like cookies) and texture cache 
<code> /app/(package id)/_manifest </code> AndroidManifest.xml of the app 
<code> /shared </code> Contains shared files (/storage/emulated/0/) 

==Flags==
<code> -all </code> Backups all compatible apps 
<code> -f </code> Chooses the path and name for the file 
<code>(package id) </code> Backs up the stated package(s) if compatible. 
<code>-system </code> backups system apps if -all or a system package Id is stated. 
<code>-nosystem </code> does not back up system data. 
<code>-apk </code> Backs up the [[.apk]] of the app(s) 
<code>-noapk </code> does not back up apk files 
<code>-obb </code> Backs up [[.obb]] (app extention) files 
<code>-noobb </code> Does not back up .obb files 
<code>-shared </code> Backs up all shared storage (/storage/emulated/0/), including SD cards and USB OTGs, so it is recommended to eject and disconnect any external storage unless you want to back up that. 
<code>-noshared </code> does not back up shared storage. 
<code>-includekeyvalue </code> or <code>-keyvalue</code> Backs up apps that support Key Value backups. Key value backups were added in Android 2.2 “Froyo”, and this flag was added in Android 8.0 “Oreo” (Even since Developer Preview 1) 
<code>-nokeyvalue</code> Does not back up key value apps.

==Discontinuation==
Android backups are being discontinued and fully replaced by [[Android Google Drive Backup|Google Drive backups]]. Google drive backups cannot be downloaded, and there is a 25 MB per-app limit. You need a network sniffer to log upload traffic to capture these. The warning was there since the SDK of Android 10 “Queen Cake”, however, backups themselves weren’t changed. In Android 12 “Snow Cone”, apps with Snow Cone’s API level with backup flag set to true and a Snow Cone device will back up to (dumb) Google Drive instead.
[[Category:Android]]
[[Category:File formats with extension .ab]]

==Example==
[https://archive.org/download/cats_20211030/cats.ab cats.ab]: Extracted on a Galaxy Tab A with Android Nougat, Contains Android easter egg (com.android.egg) cats and render data.
==See also==
*[[iTunes backup]]

Android ADB Backup

2022-03-01T18:57:05Z

Kayvon2008: /* Structucture */

{{FormatInfo
|formattype=electronic
|subcat=Backup
|subcat2=Android Backup
|extensions={{ext|ab}}
}}
Android backups (.ab) are backups made by Android Debug Bridge (ADB). They are the preferred way of backing up an unrooted stock android device. (Manufacturers and/or carriers may provide their own backup tools). They can be encrypted (with AES) or unencrypted. They can be created via ADB backup and restored via ADB restore. Android backups themselves are [[Tape Archive|.TAR]] files with a different header and no footer. Unfortunately, there are no graphical tools yet (other than mobile forensic tools like Cellebrite Physical Analyzer, Oxygen Detective, Magnet AXIOM, and [https://www.mobiledit.com/forensic-express/details MobilEDIT Forensics], which are all payed) that can extract them, and they require the command line. It is compressed via the DEFLATE method.
===Header===
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
ANDROID BACKUP
1
1
none
</pre>

==Extraction==
It is extremely hard to extract them, and for the [https://sourceforge.net/projects/android-backup-processor/ best available tool] you need the command line (and knowledge how to use it) and Java installed. [https://www.softpedia.com/get/Mobile-Phone-Tools/Droid-Explorer.shtml Droid Explorer] claims to be able to extract ADB backups, but there is no prompt of extraction and is a pain to install. [https://stackoverflow.com/questions/18533567/how-to-extract-or-unpack-an-ab-file-android-backup-file Other command line tricks] may also convert it to an easily extractable TAR.
==Structucture==
<code> /app </code> Contains all app data 
<code> /app/(package id) </code> Contains app data 
<code> /app/(package id)/a </code> Contains app APK (app file) (if requested) 
<code> /app/(package id)/f </code> Contains app files 
<code> /app/(package id)/db </code> Contains app SQLite databases (open them [http://inloop.github.io/sqlite-viewer/ here]) 
<code> /app/(package id)/ef </code> Contains app shared data (storage/emulated/0/Android/data/(package id) ) 
<code> /app/(package id)/sp </code> Contains app shared prefrences (app settings), usually [[xml]] files 
<code> /app/(package id)/r </code> Contains app resources like webview data (like cookies) and texture cache 
<code> /app/(package id)/_manifest/ </code> AndroidManifest.xml of the app 
<code> /shared </code> Contains shared files (/storage/emulated/0/) 

==Flags==
<code> -all </code> Backups all compatible apps 
<code> -f </code> Chooses the path and name for the file 
<code>(package id) </code> Backs up the stated package(s) if compatible. 
<code>-system </code> backups system apps if -all or a system package Id is stated. 
<code>-nosystem </code> does not back up system data. 
<code>-apk </code> Backs up the [[.apk]] of the app(s) 
<code>-noapk </code> does not back up apk files 
<code>-obb </code> Backs up [[.obb]] (app extention) files 
<code>-noobb </code> Does not back up .obb files 
<code>-shared </code> Backs up all shared storage (/storage/emulated/0/), including SD cards and USB OTGs, so it is recommended to eject and disconnect any external storage unless you want to back up that. 
<code>-noshared </code> does not back up shared storage. 
<code>-includekeyvalue </code> or <code>-keyvalue</code> Backs up apps that support Key Value backups. Key value backups were added in Android 2.2 “Froyo”, and this flag was added in Android 8.0 “Oreo” (Even since Developer Preview 1) 
<code>-nokeyvalue</code> Does not back up key value apps.

==Discontinuation==
Android backups are being discontinued and fully replaced by [[Android Google Drive Backup|Google Drive backups]]. Google drive backups cannot be downloaded, and there is a 25 MB per-app limit. You need a network sniffer to log upload traffic to capture these. The warning was there since the SDK of Android 10 “Queen Cake”, however, backups themselves weren’t changed. In Android 12 “Snow Cone”, apps with Snow Cone’s API level with backup flag set to true and a Snow Cone device will back up to (dumb) Google Drive instead.
[[Category:Android]]
[[Category:File formats with extension .ab]]

==Example==
[https://archive.org/download/cats_20211030/cats.ab cats.ab]: Extracted on a Galaxy Tab A with Android Nougat, Contains Android easter egg (com.android.egg) cats and render data.
==See also==
*[[iTunes backup]]

Android ADB Backup

2022-03-01T18:56:25Z

Kayvon2008: /* Structucture */

{{FormatInfo
|formattype=electronic
|subcat=Backup
|subcat2=Android Backup
|extensions={{ext|ab}}
}}
Android backups (.ab) are backups made by Android Debug Bridge (ADB). They are the preferred way of backing up an unrooted stock android device. (Manufacturers and/or carriers may provide their own backup tools). They can be encrypted (with AES) or unencrypted. They can be created via ADB backup and restored via ADB restore. Android backups themselves are [[Tape Archive|.TAR]] files with a different header and no footer. Unfortunately, there are no graphical tools yet (other than mobile forensic tools like Cellebrite Physical Analyzer, Oxygen Detective, Magnet AXIOM, and [https://www.mobiledit.com/forensic-express/details MobilEDIT Forensics], which are all payed) that can extract them, and they require the command line. It is compressed via the DEFLATE method.
===Header===
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">
ANDROID BACKUP
1
1
none
</pre>

==Extraction==
It is extremely hard to extract them, and for the [https://sourceforge.net/projects/android-backup-processor/ best available tool] you need the command line (and knowledge how to use it) and Java installed. [https://www.softpedia.com/get/Mobile-Phone-Tools/Droid-Explorer.shtml Droid Explorer] claims to be able to extract ADB backups, but there is no prompt of extraction and is a pain to install. [https://stackoverflow.com/questions/18533567/how-to-extract-or-unpack-an-ab-file-android-backup-file Other command line tricks] may also convert it to an easily extractable TAR.
==Structucture==
<code> /app </code> Contains all app data 
<code> /app/(package id) </code> Contains app data 
<code> /app/(package id)/a </code> Contains app APK (app file) (if requested) 
<code> /app/(package id)/f </code> Contains app files 
<code> /app/(package id)/db </code> Contains app SQLite databases (open them [http://inloop.github.io/sqlite-viewer/ here]) 
<code> /app/(package id)/ef </code> Contains app shared data (storage/emulated/0/Android/data/(package id) ) 
<code> /app/(package id)/sp </code> Contains app shared prefrences (app settings), usually [[xml]] files 
<code> /app/(package id)/r </code> Contains app resources like webview data (like cookies) and texture cache 
<code> /app/(package id)/_manifest/ </code> AndroidManifest.xml of the app
<code> /shared </code> Contains shared files (/storage/emulated/0/) 

==Flags==
<code> -all </code> Backups all compatible apps 
<code> -f </code> Chooses the path and name for the file 
<code>(package id) </code> Backs up the stated package(s) if compatible. 
<code>-system </code> backups system apps if -all or a system package Id is stated. 
<code>-nosystem </code> does not back up system data. 
<code>-apk </code> Backs up the [[.apk]] of the app(s) 
<code>-noapk </code> does not back up apk files 
<code>-obb </code> Backs up [[.obb]] (app extention) files 
<code>-noobb </code> Does not back up .obb files 
<code>-shared </code> Backs up all shared storage (/storage/emulated/0/), including SD cards and USB OTGs, so it is recommended to eject and disconnect any external storage unless you want to back up that. 
<code>-noshared </code> does not back up shared storage. 
<code>-includekeyvalue </code> or <code>-keyvalue</code> Backs up apps that support Key Value backups. Key value backups were added in Android 2.2 “Froyo”, and this flag was added in Android 8.0 “Oreo” (Even since Developer Preview 1) 
<code>-nokeyvalue</code> Does not back up key value apps.

==Discontinuation==
Android backups are being discontinued and fully replaced by [[Android Google Drive Backup|Google Drive backups]]. Google drive backups cannot be downloaded, and there is a 25 MB per-app limit. You need a network sniffer to log upload traffic to capture these. The warning was there since the SDK of Android 10 “Queen Cake”, however, backups themselves weren’t changed. In Android 12 “Snow Cone”, apps with Snow Cone’s API level with backup flag set to true and a Snow Cone device will back up to (dumb) Google Drive instead.
[[Category:Android]]
[[Category:File formats with extension .ab]]

==Example==
[https://archive.org/download/cats_20211030/cats.ab cats.ab]: Extracted on a Galaxy Tab A with Android Nougat, Contains Android easter egg (com.android.egg) cats and render data.
==See also==
*[[iTunes backup]]

Android Backup

2022-02-27T02:50:04Z

Kayvon2008: /* Third-party backups */

{{FormatInfo
|formattype=electronic
| subcat = Backup
|thiscat=Android Backup
}}
“Android Backup” may refer to the following:
==Google and AOSP backups==
*[[Android ADB Backup]] (.ab) - Backups created via ADB. (Android 4.0 Ice Cream Sandwich - Android 13 Tiramisu)
*[[Android Recovery Mode Backup]] (.backup) - Backup created via the “Backup User Data” option on Android Recovery Mode (Removed)
*[[Android Google Drive Backup]] - Backups stored at Google Drive, requires network sniffer/network capturer to access

==Manufacturer Backups==
*[[Samsung Smart Switch backup]] (.bk)
*[[Huawei backup folder]]
*[[Xiaomi backup folder]]

==Carrier Backups==
*[[Verizon Cloud backup]]
*[[Sprint Backup]]

==Third-party backups==
*[[Helium Backup]]
*[[Enhanced Android Backup]] (.abex)
*[[Backup Your Mobile Backup]] (.bkp)
*[[Seedvault Backup]]
=== Emulator Backups ===
*[[Bluestacks transfer file]] ([https://support.bluestacks.com/hc/en-us/articles/360061342631-How-to-transfer-your-apps-from-BlueStacks-4-to-BlueStacks-5#%E2%80%9C1%E2%80%9D Resource])
===Custom recovery backups===
*[[TeamWin Recovery Project Backup]]
*[[ClockworkMod Recovery Backup]]

==Forensics-related==
*See [[Forensics and Law Enforcement]]
{{disambiguation}}

Forensics vs. Data Recovery vs. Data Preservation

2022-02-15T02:24:42Z

Kayvon2008: Created page with "1. Digital forensics is a feild where police get data out of an electronic device to solve a case (ex. Murder, terrorism). Basically think of it as detectives. 2. Data Recover..."

1. Digital forensics is a feild where police get data out of an electronic device to solve a case (ex. Murder, terrorism). Basically think of it as detectives.
2. Data Recovery is the recovery of personal data from deletion, encryption, or frogotton passwords/passcodes. Think of it as getting priceless photos undeleted.
3. Data Preservation/Archival is archiving or preserving data so that you can access it in the future or for heritage.

OneDrive

2022-02-15T02:20:37Z

Kayvon2008:

{{FormatInfo
|formattype=electronic
|subcat=Filesystem
|released=2007
}}
'''OneDrive''' (previously '''SkyDrive''' and '''Windows Live Folders''') is a cloud file service run by Microsoft, in both consumer and business versions, with various manners of accessing, modifying, and syncing the files supported, including Microsoft Office integration. It's been reported that Microsoft does all sorts of monitoring of user content (including by automated processes) to enforce various terms of service (it's apparently against their terms of service to have among your private files anything with partial nudity or discussion of purchasing firearms, or copyright and confidential files of course), banning people's accounts (even paid ones) and deleting people's files for alleged violations. It's also reported that the content of files gets modified automatically without notice, such as to insert odd Microsoftisms into HTML documents and added metadata to Microsoft-format documents (Word, Publisher, etc.), some of which might permit tracing which users created or accessed a file.

== Logs ==
OneDrive produces many log files. See [https://github.com/ydkhatri/OneDrive A parser for OneDrive .odl files].

== Links ==
* [https://onedrive.live.com/about/en-us/ Official site]
* [https://blog.onedrive.com/ Official blog]
* [[Wikipedia:OneDrive|Wikipedia article]]
* [http://www.myce.com/news/microsoft-onedrive-for-business-modifies-files-as-it-syncs-71168/ Microsoft OneDrive for Business modifies files as it syncs]
* [https://twitter.com/koenrh/status/466199731275071488/photo/1/large Microsoft works with government to help them spy on users' data]

[[Category:Microsoft]]

Android Google Drive Backup

2022-02-13T07:52:28Z

Kayvon2008:

{{FormatInfo
|formattype=electronic
|subcat=Backup
|subcat2=Android Backup
}}
Android Google Drive backups. Unfortunately, there is nearly no way to download them, except getting an Android device emulator and downloading it there. https://www.elcomsoft.com/ecx.html this tool can help download google drive backup data partially minus the apps, and https://www.imobie.com/backup-restore/android-backup-extractor.htm this app can download the same data but is made for consumer data recovery. Cellebrite UFED cloud may be able to download, but it is unreliable. The backups are encrypted with your lock code. You may need a network sniffer to access these. But, https encryption exists and you need to remove the encryption. The most effective way is with Oxygen forensics to download your data. If you want to get a copy of this, contact your local law enforcement agency that you know has Oxygen Forensics your account credentials and your device passcode. However, if you value your privacy, we don’t recommend this.

The easiest way to get these backups is via requesting a copy of the backup(s) with a passcode: https://support.google.com/policies/contact/sar
[[File:GDB1.png]]
[[File:GDB2.png]]
[[File:GDB3.png]]

Google Takeout

2022-02-10T23:12:41Z

Kayvon2008: /* Services NOT included in takeout */

{{FormatInfo
|formattype=electronic
|subcat=Backup
}}
[[Google Takeout]] is a [[Google]] service that provides an archived copy of data associated with a Google account (an account on all Google services like Gmail, [[Google Drive]], [[YouTube]], and more).

== Discussion==
ArchiveTeam HIGHLY recommends taking out your primary school (Elementary, middle, high) when you complete it.
# Nostalgia - checking your old work
# '''Future use - Colleges and businesses might need old work.'''
# Personal data - Sometimes you store non-school files on school services, or you do non-school things during school.

==Takeout==
Google Takeout offers a near complete backup of your data straight from the cloud. Please send feedback to google if you realize something’s missing.

https://takeout.google.com/

Note: please enable: Access log activity and click the gear icon in google drive and tick the 2 boxes for the maximum amount of data.

==Services NOT included in takeout==
*[[Android Google Drive Backup]]s
*Feedburner data (go to the feedburner website to export it yourself)
*[[Google drive WhatsApp backup]]s, pretty much the same deal as [[iCloud WhatsApp Backup]]s
*Chrome canvas data
*[https://www.google.com/tools/feedback/reports?hl=en Feedback made by the icon]
*Google custom search engine data
*Google Alerts data
*Google 9-square launcher icon configuration
*Google drive "private app data"
*Google Scholar data
*Teachable Machine Data
*Management-related data (cpu usage, etc)
*Recently permanently deleted data
*Possibly more…

[[Category:Archiving]]
[[Category:Google]]

Google Takeout

2022-02-08T04:54:25Z

Kayvon2008: /* Services NOT included in takeout */

{{FormatInfo
|formattype=electronic
|subcat=Backup
}}
[[Google Takeout]] is a [[Google]] service that provides an archived copy of data associated with a Google account (an account on all Google services like Gmail, [[Google Drive]], [[YouTube]], and more).

== Discussion==
ArchiveTeam HIGHLY recommends taking out your primary school (Elementary, middle, high) when you complete it.
# Nostalgia - checking your old work
# '''Future use - Colleges and businesses might need old work.'''
# Personal data - Sometimes you store non-school files on school services, or you do non-school things during school.

==Takeout==
Google Takeout offers a near complete backup of your data straight from the cloud. Please send feedback to google if you realize something’s missing.

https://takeout.google.com/

Note: please enable: Access log activity and click the gear icon in google drive and tick the 2 boxes for the maximum amount of data.

==Services NOT included in takeout==
*[[Android Google Drive Backup]]s
*Feedburner data (go to the feedburner website to export it yourself)
*[[Google drive WhatsApp backup]]s, pretty much the same deal as [[iCloud WhatsApp Backup]]s
*Chrome canvas data
*[https://www.google.com/tools/feedback/reports?hl=en Feedback made by the icon]
*Google custom search engine data
*Google Alerts data
*Google 9-square launcher icon configuration
*Google drive "private app data"
*Teachable Machine Data
*Management-related data (cpu usage, etc)
*Recently permanently deleted data
*Possibly more…

[[Category:Archiving]]
[[Category:Google]]

Google Takeout

2022-02-06T08:29:29Z

Kayvon2008: /* Services NOT included in takeout */

{{FormatInfo
|formattype=electronic
|subcat=Backup
}}
[[Google Takeout]] is a [[Google]] service that provides an archived copy of data associated with a Google account (an account on all Google services like Gmail, [[Google Drive]], [[YouTube]], and more).

== Discussion==
ArchiveTeam HIGHLY recommends taking out your primary school (Elementary, middle, high) when you complete it.
# Nostalgia - checking your old work
# '''Future use - Colleges and businesses might need old work.'''
# Personal data - Sometimes you store non-school files on school services, or you do non-school things during school.

==Takeout==
Google Takeout offers a near complete backup of your data straight from the cloud. Please send feedback to google if you realize something’s missing.

https://takeout.google.com/

Note: please enable: Access log activity and click the gear icon in google drive and tick the 2 boxes for the maximum amount of data.

==Services NOT included in takeout==
*[[Android Google Drive Backup]]s
*Feedburner data (go to the feedburner website to export it yourself)
*[[Google drive WhatsApp backup]]s, pretty much the same deal as [[iCloud WhatsApp Backup]]s
*Chrome canvas data
*[https://www.google.com/tools/feedback/reports?hl=en Feedback made by the icon]
*Google custom search engine data
*Google Alerts data
*Google 9-square launcher icon configuration
*Google drive "private app data"
*Ad personalization data
*Recently permanently deleted data
*Possibly more…

[[Category:Archiving]]
[[Category:Google]]

Android Google Drive Backup

2022-01-28T02:17:26Z

Kayvon2008:

{{FormatInfo
|formattype=electronic
|subcat=Backup
|subcat2=Android Backup
}}
Android Google Drive backups. Unfortunately, there is nearly no way to download them, except getting an Android device emulator and downloading it there. https://www.elcomsoft.com/ecx.html this tool can help download google drive backup data partially minus the apps, and https://www.imobie.com/backup-restore/android-backup-extractor.htm this app can download the same data but is made for consumer data recovery. Cellebrite UFED cloud may be able to download, but it is unreliable. The backups are encrypted with your lock code. You may need a network sniffer to access these. But, https encryption.

The easiest way to get these backups is via requesting a copy of the backup(s): https://support.google.com/policies/contact/sar
[[File:GDB1.png]]
[[File:GDB2.png]]
[[File:GDB3.png]]

Forensics and Law Enforcement

2022-01-22T07:59:55Z

Kayvon2008: /* Cloud Warrant Return */

{{FormatInfo
|formattype=electronic
|thiscat=Forensics and Law Enforcement
|image=All Detective Magazine February 1934.jpg
}}

See also [[Law]]

== Forensic images of disks and computer network data ==

In the course of investigations, detectives sometimes need to preserve digital information. These are formats used in this process. See also [[Disk Image Formats]]. In contrast to those raw disk images, forensic formats also store various metadata as well as hash tables to track the origin of data and ensure it is not altered after the fact.

* [[Advanced Forensics Format]] (AFF)
* [[Advanced Forensics Metadata]] (AFM)
* [[Digital Evidence Bag]] (DEB)
* [[EnCase hash map]] (Expert Witness)
* [[Expert Witness]]

== Biometrics ==
See also [[Fingerprints]]

* [[ANSI 378]] (used to store minutae of fingerprints)
* [[ANSI 379]] (used to store images of irises)
* [[ANSI 381]] (used to store images of fingerprints)
* [[ANSI 385]] (used to store face recognition data)
* [[CBEFF]]
* [[ISO 19794-2]] (used to store minutae of fingerprints)
* [[NIST IHead]] (one of its uses is storing fingerprint images)
* [[WSQ]] (used to store images of fingerprints)

==Mobile-related==
*[[Cellebrite UFED Report]] (.ufdr)
*[[Oxygen Backup XML]]
*[[MOBILedit Backup XML]]
*[[MOBILedit Backup Package]]
== Oxygen ==
* [[Oxygen Cloud Backup]]
* [[Oxygen Forensic Backup]]
* [[Oxygen Desktop Backup]]
* [[Oxygen UICC Image]]
* [[Oxygen Agent Extraction]]

== Cloud Warrant Return ==
*[[Apple iCloud Warrant Return]]
*[[Google Warrant Return]]
*[[Facebook Warrent Return]]
*[[Skype Warrant Return]]
*[[Snapchat Warrent Return]]
*[[Discord Warrent Return]]
*[[Instagram Warrent Return]]

== Links ==
* [https://archive.org/details/ShmooCon2014_You_Dont_Have_the_Evidence ShmooCon 2014 - You Don't Have the Evidence (January 2014) (video)]
* [[The Sleuth Kit and Autopsy]] can read raw, Expert Witness, and AFF formats
* [http://qanda.digipres.org/132/best-choice-for-digital-preservationists-who-create-images?show=157 Is AFF the best choice for digital preservationists who create images?]

Auto-created directories

2022-01-21T07:11:39Z

Kayvon2008:

{{FormatInfo
|formattype=electronic
|subcat=Filesystem
}} This page demonstrates all of the usually hidden directories and files that are automatically created by the OS when you plug in a storage device.
{| class="wikitable" style="width: 60%;"
|-
! Path
! Description
! OS that makes it
|-
|/System Volume Information
|Usually inaccessible to Windows users without proper command line stuff, to access this, plug this into a Mac, Chromebook, or Linux computer.
|Microsoft Windows
|-
|/$RECYCLE.BIN
|Stores files currently in the recycle bin in Windows
|Microsoft Windows
|-
|/.Trashes
|Ditto as above, but for Apple macOS, iOS, and iPadOS
|Apple macOS, iOS, and iPadOS
|-
|/LOST.DIR
|Stores data when Android has a problem
|Google/AOSP Android
|-
|/.LOST.DIR
|Stores data when Android has a problem
|Google/AOSP Android
|-
|/Android
|Stores data and cache created by Android apps, and this may appear if you use Windows Subsystem for Android.
|Google/AOSP Android
|-
|/.android_secure
|Stores apps that have been moved to the SD card or USB OTG
|Google/AOSP Android
|-
|/.Spotlight-V100
|Stores spotlight index data
|Apple macOS, iOS, and iPadOS
|-
|/.fseventsd
|.fseventsd is part of the File System Events notification mechanism - when a file changes, the operating system sends a message to any programs which care, such as the Spotlight indexing system. <ref> https://www.quora.com/What-do-folders-named-fseventsd-Spotlight-V100-and-Trashes-mean-on-OS-X-10-6-Snow-Leopard/answer/James-Sutherland-5?ch=15&oid=7300798&share=e0b22fc8&srid=tyMQ3&target_type=answer </ref>
|Apple macOS, iOS, and iPadOS
|-
|/LG Smart TV
|Stores cache for LG smart TVs with webOS in the form of .tn3 files.
|LG webOS (Only TVs)
|}

Auto-created directories

2022-01-21T07:08:55Z

Kayvon2008:

{{FormatInfo
|formattype=electronic
|subcat=Filesystem
}} This page demonstrates all of the usually hidden directories and files that are automatically created by the OS when you plug in a storage device.
{| class="wikitable" style="width: 60%;"
|-
! Path
! Description
! OS that makes it
|-
|/System Volume Information
|Usually inaccessible to Windows users without proper command line stuff, to access this, plug this into a Mac, Chromebook, or Linux computer.
|Microsoft Windows
|-
|/$RECYCLE.BIN
|Stores files currently in the recycle bin in Windows
|Microsoft Windows
|-
|/.Trashes
|Ditto as above, but for Apple macOS, iOS, and iPadOS
|Apple macOS, iOS, and iPadOS
|-
|/LOST.DIR
|Stores data when Android has a problem
|Google/AOSP Android
|-
|/.LOST.DIR
|Stores data when Android has a problem
|Google/AOSP Android
|-
|/Android
|Stores data and cache created by Android apps, and this may appear if you use Windows Subsystem for Android.
|Google/AOSP Android
|-
|/.android_secure
|Stores apps that have been moved to the SD card or USB OTG
|Google/AOSP Android
|-
|/.Spotlight-V100
|Stores spotlight index data
|Apple macOS, iOS, and iPadOS
|-
|/.fseventsd
|???
|Apple macOS, iOS, and iPadOS
|-
|/LG Smart TV
|Stores cache for LG smart TVs with webOS in the form of .tn3 files.
|LG webOS (Only TVs)
|}

Google Takeout

2022-01-17T07:01:16Z

Kayvon2008: /* Services NOT included in takeout */

A google account is an account on all google services like Gmail, Google Drive, YouTube, and more.

ArchiveTeam HIGHLY recommends taking out your primary school (Elementary, middle, high) when you complete it.
# Nonstalga - checking your old work
# '''Future use - Collages and businesses might need old work.'''
# Personal data - Sometimes you store non-school files on school services, or you do non-school things during school.

==Takeout==
Google Takeout offers a near complete backup of your data straight from the cloud. Please send feedback to google if you realize something’s missing.

https://takeout.google.com/

Note: please enable: Access log activity and click the gear icon in google drive and tick the 2 boxes for the maximum amount of data.

==Services NOT included in takeout==
*[[Android Google Drive Backup]]s
*Feedburner data (go to the feedburner website to export it yourself)
*[[Google drive WhatsApp backup]]s, pretty much the same deal as [[iCloud WhatsApp Backup]]s
*Chrome canvas data
*[https://www.google.com/tools/feedback/reports?hl=en Feedback made by the icon]
*Google custom search engine data
*Google 9-square launcher icon configuration
*Google drive "private app data"
*Ad personalization data
*Recently permanently deleted data
*Possibly more…

Google Takeout

2022-01-17T04:02:44Z

Kayvon2008: /* Services NOT included in takeout */

A google account is an account on all google services like Gmail, Google Drive, YouTube, and more.

ArchiveTeam HIGHLY recommends taking out your primary school (Elementary, middle, high) when you complete it.
# Nonstalga - checking your old work
# '''Future use - Collages and businesses might need old work.'''
# Personal data - Sometimes you store non-school files on school services, or you do non-school things during school.

==Takeout==
Google Takeout offers a near complete backup of your data straight from the cloud. Please send feedback to google if you realize something’s missing.

https://takeout.google.com/

Note: please enable: Access log activity and click the gear icon in google drive and tick the 2 boxes for the maximum amount of data.

==Services NOT included in takeout==
*[[Android Google Drive Backup]]s
*<s>[[Google Play Games save data]]</s> Already included I forgot
*Feedburner data (go to the feedburner website to export it yourself)
*[[Google drive WhatsApp backup]]s, pretty much the same deal as [[iCloud WhatsApp Backup]]s
*Chrome canvas data
*[https://www.google.com/tools/feedback/reports?hl=en Feedback made by the icon]
*Google custom search engine data
*Google 9-square launcher icon configuration
*Google drive "private app data"
*Ad personalization data
*Recently permanently deleted data
*Possibly more…

Google Takeout

2022-01-17T01:14:15Z

Kayvon2008: /* Services NOT included in takeout */

A google account is an account on all google services like Gmail, Google Drive, YouTube, and more.

ArchiveTeam HIGHLY recommends taking out your primary school (Elementary, middle, high) when you complete it.
# Nonstalga - checking your old work
# '''Future use - Collages and businesses might need old work.'''
# Personal data - Sometimes you store non-school files on school services, or you do non-school things during school.

==Takeout==
Google Takeout offers a near complete backup of your data straight from the cloud. Please send feedback to google if you realize something’s missing.

https://takeout.google.com/

Note: please enable: Access log activity and click the gear icon in google drive and tick the 2 boxes for the maximum amount of data.

==Services NOT included in takeout==
*[[Android Google Drive Backup]]s
*[[Google Play Games save data]]
*Feedburner data (go to the feedburner website to export it yourself)
*[[Google drive WhatsApp backup]]s, pretty much the same deal as [[iCloud WhatsApp Backup]]s
*Chrome canvas data
*[https://www.google.com/tools/feedback/reports?hl=en Feedback made by the icon]
*Google custom search engine data
*Google 9-square launcher icon configuration
*Google drive "private app data"
*Ad personalization data
*Recently permanently deleted data
*Possibly more…

Android Backup

2022-01-17T01:02:01Z

Kayvon2008: /* Emulator Backups */

{{FormatInfo
|formattype=electronic
| subcat = Backup
|thiscat=Android Backup
}}
“Android Backup” may refer to the following:
==Google and AOSP backups==
*[[Android ADB Backup]] (.ab) - Backups created via ADB. (Android 4.0 Ice Cream Sandwich - Android 13 Tiramisu)
*[[Android Recovery Mode Backup]] (.backup) - Backup created via the “Backup User Data” option on Android Recovery Mode (Removed)
*[[Android Google Drive Backup]] - Backups stored at Google Drive, requires network sniffer/network capturer to access

==Manufacturer Backups==
*[[Samsung Smart Switch backup]] (.bk)
*[[Huawei backup folder]]
*[[Xiaomi backup folder]]

==Carrier Backups==
*[[Verizon Cloud backup]]
*[[Sprint Backup]]

==Third-party backups==
*[[Helium Backup]]
*[[Enhanced Android Backup]] (.abex)
*[[Backup Your Mobile Backup]] (.bkp)
=== Emulator Backups ===
*[[Bluestacks transfer file]] ([https://support.bluestacks.com/hc/en-us/articles/360061342631-How-to-transfer-your-apps-from-BlueStacks-4-to-BlueStacks-5#%E2%80%9C1%E2%80%9D Resource])
===Custom recovery backups===
*[[TeamWin Recovery Project Backup]]
*[[ClockworkMod Recovery Backup]]

==Forensics-related==
*See [[Forensics and Law Enforcement]]
{{disambiguation}}

Android Backup

2022-01-16T04:22:57Z

Kayvon2008:

{{FormatInfo
|formattype=electronic
| subcat = Backup
|thiscat=Android Backup
}}
“Android Backup” may refer to the following:
==Google and AOSP backups==
*[[Android ADB Backup]] (.ab) - Backups created via ADB. (Android 4.0 Ice Cream Sandwich - Android 13 Tiramisu)
*[[Android Recovery Mode Backup]] (.backup) - Backup created via the “Backup User Data” option on Android Recovery Mode (Removed)
*[[Android Google Drive Backup]] - Backups stored at Google Drive, requires network sniffer/network capturer to access

==Manufacturer Backups==
*[[Samsung Smart Switch backup]] (.bk)
*[[Huawei backup folder]]
*[[Xiaomi backup folder]]

==Carrier Backups==
*[[Verizon Cloud backup]]
*[[Sprint Backup]]

==Third-party backups==
*[[Helium Backup]]
*[[Enhanced Android Backup]] (.abex)
*[[Backup Your Mobile Backup]] (.bkp)
== Emulator Backups ==
*[[Bluestacks transfer file]] ([https://support.bluestacks.com/hc/en-us/articles/360061342631-How-to-transfer-your-apps-from-BlueStacks-4-to-BlueStacks-5#%E2%80%9C1%E2%80%9D Resource])
===Custom recovery backups===
*[[TeamWin Recovery Project Backup]]
*[[ClockworkMod Recovery Backup]]

==Forensics-related==
*See [[Forensics and Law Enforcement]]
{{disambiguation}}

Android Backup

2022-01-16T04:11:12Z

Kayvon2008: /* Carrier Backups */

{{FormatInfo
|formattype=electronic
| subcat = Backup
|thiscat=Android Backup
}}
“Android Backup” may refer to the following:
==Google and AOSP backups==
*[[Android ADB Backup]] (.ab) - Backups created via ADB. (Android 4.0 Ice Cream Sandwich - Android 13 Tiramisu)
*[[Android Recovery Mode Backup]] (.backup) - Backup created via the “Backup User Data” option on Android Recovery Mode (Removed)
*[[Android Google Drive Backup]] - Backups stored at Google Drive, requires network sniffer/network capturer to access

==Manufacturer Backups==
*[[Samsung Smart Switch backup]] (.bk)
*[[Huawei backup folder]]
*[[Xiaomi backup folder]]

==Carrier Backups==
*[[Verizon Cloud backup]]
*[[Sprint Backup]]

==Third-party backups==
*[[Helium Backup]]
*[[Enhanced Android Backup]] (.abex)
*[[Backup Your Mobile Backup]] (.bkp)
===Custom recovery backups===
*[[TeamWin Recovery Project Backup]]
*[[ClockworkMod Recovery Backup]]

==Forensics-related==
*See [[Forensics and Law Enforcement]]
{{disambiguation}}

Android Backup

2022-01-16T04:09:49Z

Kayvon2008: /* Carrier Backups */

{{FormatInfo
|formattype=electronic
| subcat = Backup
|thiscat=Android Backup
}}
“Android Backup” may refer to the following:
==Google and AOSP backups==
*[[Android ADB Backup]] (.ab) - Backups created via ADB. (Android 4.0 Ice Cream Sandwich - Android 13 Tiramisu)
*[[Android Recovery Mode Backup]] (.backup) - Backup created via the “Backup User Data” option on Android Recovery Mode (Removed)
*[[Android Google Drive Backup]] - Backups stored at Google Drive, requires network sniffer/network capturer to access

==Manufacturer Backups==
*[[Samsung Smart Switch backup]] (.bk)
*[[Huawei backup folder]]
*[[Xiaomi backup folder]]

==Carrier Backups==
*[[Verizon Cloud backup]]

==Third-party backups==
*[[Helium Backup]]
*[[Enhanced Android Backup]] (.abex)
*[[Backup Your Mobile Backup]] (.bkp)
===Custom recovery backups===
*[[TeamWin Recovery Project Backup]]
*[[ClockworkMod Recovery Backup]]

==Forensics-related==
*See [[Forensics and Law Enforcement]]
{{disambiguation}}

Forensics and Law Enforcement

2022-01-15T22:57:15Z

Kayvon2008: /* Mobile-related */

{{FormatInfo
|formattype=electronic
|thiscat=Forensics and Law Enforcement
|image=All Detective Magazine February 1934.jpg
}}

See also [[Law]]

== Forensic images of disks and computer network data ==

In the course of investigations, detectives sometimes need to preserve digital information. These are formats used in this process. See also [[Disk Image Formats]]. In contrast to those raw disk images, forensic formats also store various metadata as well as hash tables to track the origin of data and ensure it is not altered after the fact.

* [[Advanced Forensics Format]] (AFF)
* [[Advanced Forensics Metadata]] (AFM)
* [[Digital Evidence Bag]] (DEB)
* [[EnCase hash map]] (Expert Witness)
* [[Expert Witness]]

== Biometrics ==
See also [[Fingerprints]]

* [[ANSI 378]] (used to store minutae of fingerprints)
* [[ANSI 379]] (used to store images of irises)
* [[ANSI 381]] (used to store images of fingerprints)
* [[ANSI 385]] (used to store face recognition data)
* [[CBEFF]]
* [[ISO 19794-2]] (used to store minutae of fingerprints)
* [[NIST IHead]] (one of its uses is storing fingerprint images)
* [[WSQ]] (used to store images of fingerprints)

==Mobile-related==
*[[Cellebrite UFED Report]] (.ufdr)
*[[Oxygen Backup XML]]
*[[MOBILedit Backup XML]]
*[[MOBILedit Backup Package]]
== Oxygen ==
* [[Oxygen Cloud Backup]]
* [[Oxygen Forensic Backup]]
* [[Oxygen Desktop Backup]]
* [[Oxygen UICC Image]]
* [[Oxygen Agent Extraction]]

== Cloud Warrant Return ==
*[[Apple iCloud Warrant Return]]
*[[Google Warrant Return]]
*[[Facebook Warrent Return]]
*[[Snapchat Warrent Return]]
*[[Discord Warrent Return]]
*[[Instagram Warrent Return]]

== Links ==
* [https://archive.org/details/ShmooCon2014_You_Dont_Have_the_Evidence ShmooCon 2014 - You Don't Have the Evidence (January 2014) (video)]
* [[The Sleuth Kit and Autopsy]] can read raw, Expert Witness, and AFF formats
* [http://qanda.digipres.org/132/best-choice-for-digital-preservationists-who-create-images?show=157 Is AFF the best choice for digital preservationists who create images?]

Android Backup

2022-01-15T22:54:15Z

Kayvon2008: /* Forensics-related */

{{FormatInfo
|formattype=electronic
| subcat = Backup
|thiscat=Android Backup
}}
“Android Backup” may refer to the following:
==Google and AOSP backups==
*[[Android ADB Backup]] (.ab) - Backups created via ADB. (Android 4.0 Ice Cream Sandwich - Android 13 Tiramisu)
*[[Android Recovery Mode Backup]] (.backup) - Backup created via the “Backup User Data” option on Android Recovery Mode (Removed)
*[[Android Google Drive Backup]] - Backups stored at Google Drive, requires network sniffer/network capturer to access

==Manufacturer Backups==
*[[Samsung Smart Switch backup]] (.bk)
*[[Huawei backup folder]]
*[[Xiaomi backup folder]]

==Carrier Backups==
==Third-party backups==
*[[Helium Backup]]
*[[Enhanced Android Backup]] (.abex)
*[[Backup Your Mobile Backup]] (.bkp)
===Custom recovery backups===
*[[TeamWin Recovery Project Backup]]
*[[ClockworkMod Recovery Backup]]

==Forensics-related==
*See [[Forensics and Law Enforcement]]
{{disambiguation}}

Android Backup

2022-01-15T22:53:41Z

Kayvon2008: /* Forensics-related */

{{FormatInfo
|formattype=electronic
| subcat = Backup
|thiscat=Android Backup
}}
“Android Backup” may refer to the following:
==Google and AOSP backups==
*[[Android ADB Backup]] (.ab) - Backups created via ADB. (Android 4.0 Ice Cream Sandwich - Android 13 Tiramisu)
*[[Android Recovery Mode Backup]] (.backup) - Backup created via the “Backup User Data” option on Android Recovery Mode (Removed)
*[[Android Google Drive Backup]] - Backups stored at Google Drive, requires network sniffer/network capturer to access

==Manufacturer Backups==
*[[Samsung Smart Switch backup]] (.bk)
*[[Huawei backup folder]]
*[[Xiaomi backup folder]]

==Carrier Backups==
==Third-party backups==
*[[Helium Backup]]
*[[Enhanced Android Backup]] (.abex)
*[[Backup Your Mobile Backup]] (.bkp)
===Custom recovery backups===
*[[TeamWin Recovery Project Backup]]
*[[ClockworkMod Recovery Backup]]

==Forensics-related==
*See [[Forensics and law enforcement]]
{{disambiguation}}

Health and Medicine

2022-01-15T22:43:47Z

Kayvon2008: /* Optical */

{{FormatInfo
|formattype=electronic
|thiscat=Health and Medicine
|image=Colorful-pills.jpg
}}

== Biomedical signals (time series) ==

* [[ACQ]] (AcqKnowledge)
* [[BCI2000]] (The BCI2000 project)
* [[BioSemi]] (BDF) data format
* [[BKR]] (EEG data format)
* [[CFWB]] (Chart Data File Format)
* [[DICOM-Waveform]] (An extension of Dicom for storing waveform data)
* [[ecgML]] (A markup language for electrocardiogram data acquisition and analysis)
* [[EDF/EDF+]] (European Data Format)
* [[FEF]] (File Exchange Format for Vital signs, CEN TS 14271)
* [[General Data Format for Biosignals]]
** [[GDF v1.x]] (General Data Format for biomedical signals - Version 1.x)
** [[GDF v2.x]] (The General Data Format for biomedical signals - Version 2.x)
* [[HL7aECG]] (Health Level 7 v3 annotated ECG)
* [[MEF (Multiscale Electrophysiology File Format)]]
* [[OpenXDF]] (Open Exchange Data Format)
* [[SCP-ECG]] (Standard Communication Protocol for Computer assisted electrocardiography)
* [[SIGIF]] (A digital SIGnal Interchange Format)
* [[WFDB]] (Format of Physiobank)

== CPAP and oximeters (sleep apnea treatment) ==

These devices generally use proprietary data formats. The [[SleepyHead]] open-source software can read some of them.

* [[ChoiceMMed MD300W1]]
* [[Contec CMS50D]]
* [[DeVilbiss Intellipap]]
* [[Fisher & Paykel Icon]]
* [[Philips Respironics System One]]
* [[ResMed S9]]
* [[Weinmann SOMNOsoft2]]

== Genetic data ==
* [[23andMe]]
* [[Complete Genomics]]

See [[Scientific Data formats#Biological]] for more formats

== Medical Imaging ==
* [[Analyze AVW]]
* [[Aperio SVS]]
* [[BioRad confocal image]]
* [[BRIK/HEAD]] (Voxel data from AFNI programs, dual-file (data and metadata, repectively))
* [[DeltaVision]]
* [[DICOM]] (Digital Imaging and Communications in Medicine (.dcm))
* [[gii]] (NIfTI offspring for brain surface data, single-file (combined data and meta-data) style)
* [[IMG/HDR]] (ANALYZE or NIfTI voxel data, dual-file (separate data and metadata, respectively))
* [[MGH]] (uncompressed)
* [[MGZ]] (zip-compressed)
* [[MINC]] (Medical Imaging NetCDF format; since version 2.0, based on HDF5 (.mnc))
* [[MRC]] (Medical Research Council)
* [[NII]] (Neuroimaging Informatics Technology Initiative (NIfTI) voxel data, single-file (combined data and metadata))
* [[OME-TIFF]] (Open Microscopy Imaging format)
* [[OME-XML]] (Open Microscopy Imaging format)
* [[OST (Open Spatio-Temporal)]] (extensible, open alternative for microscope images)
* [[SDM]] (Signed Differential Mapping- brain maps(.sdm))
* [[TRK]] (Vector data describing tracts of neurons, used by TrackVis)

== Medical Record Keeping and Transaction Processing ==

* [[Prescription Drug Event]] (PDE)
* [[TIBCO Foresight HIPAA Validator Validation Profile File]] (APF)

== Optical ==
* [[Eyeglass file format (Ross Spencer)]] - file format invented by digital preservation researcher to demonstrate how to create file formats
== Uncategorized ==
* [[Apple Health]]
** [[Apple Health Export]]
* [[Google Fit]]
* [[Microsoft Health and Fitness]]

== Links ==
* [http://medconfidential.org/how-to-opt-out/ NHS England patients: how to opt-out from having your health data disclosed]
* [http://www.wired.co.uk/news/archive/2014-02/26/demand-transparency-from-nhs NHS data blunders mean you can't trust Care.data]

Culinary arts

2022-01-15T22:41:27Z

Kayvon2008:

{{FormatInfo
|formattype=electronic
|thiscat=Culinary arts
|image=Outdoor-cooking.jpg
}}

What's cookin'? These file formats relate to the preparation of food.

* [[Foodini]] (3D printer for food)
* [[h-recipe]] (Microformats; cooking/baking recipes)
* [[Microsoft Food and Drink]]

Android Backup

2022-01-15T22:38:02Z

Kayvon2008: /* Forensics-related */

{{FormatInfo
|formattype=electronic
| subcat = Backup
|thiscat=Android Backup
}}
“Android Backup” may refer to the following:
==Google and AOSP backups==
*[[Android ADB Backup]] (.ab) - Backups created via ADB. (Android 4.0 Ice Cream Sandwich - Android 13 Tiramisu)
*[[Android Recovery Mode Backup]] (.backup) - Backup created via the “Backup User Data” option on Android Recovery Mode (Removed)
*[[Android Google Drive Backup]] - Backups stored at Google Drive, requires network sniffer/network capturer to access

==Manufacturer Backups==
*[[Samsung Smart Switch backup]] (.bk)
*[[Huawei backup folder]]
*[[Xiaomi backup folder]]

==Carrier Backups==
==Third-party backups==
*[[Helium Backup]]
*[[Enhanced Android Backup]] (.abex)
*[[Backup Your Mobile Backup]] (.bkp)
===Custom recovery backups===
*[[TeamWin Recovery Project Backup]]
*[[ClockworkMod Recovery Backup]]

==Forensics-related==
*See [[Forensics and Law enforcement]]
{{disambiguation}}

LG webOS Smart TV

2022-01-15T07:54:17Z

Kayvon2008:

{{FormatInfo
|formattype=physical
|subcat=Networked devices
}}'''LG Smart TVs''' usually run the webOS operating system. If it is from 2014 or older, they may run Android (Google TV) (only used in 2 kinda luxury models), or NetCast. ZENA forensics has made an analysis on a 55SK8000PUA tv.
==Partition structure==
Four EXT4 partitions can be found.

7-zip revealed a SquashFS at the beginning of the image.

The Squashfs has a Linux-style folder schema and seems to contain the WebOS files.

I decided then to run "binwalk" on the image: the tool found 6 SquashFS file systems.

Overall I found six SquashFS, extracted by binwalk and four EXT4 partitions, extracted by MobileRevelator and TestDisk: Partition 0 (/mnt/lg/uhdcp), Partition 1 (/var/db), Partition 2 (/mnt/lg/cmn_data) and Partition 3(/media).

==SquashFS files==

The six SquashFS files contain the stock LG WebOS. The "/etc/issue" file contains the operating system version. In the dataset it contains "webOS TV 3.5.0".

===Partition 0 (/mnt/lg/uhdcp) and Partition 1 (/var/db)===

Partition 0 (/mnt/lg/uhdcp) and Partition 1 (/var/db) don't seem containing useful data from a forensics perspective.

===Partition 2 (/mnt/lg/cmn_data)===

Partition 2 (/mnt/lg/cmn_data) seems containing the most interesting files from a forensics perspective.

The "/.iot/accountInfoFile" file contains a username, apparently related to the Amazon Echo service. In the provided dataset three values seem interesting: userID, userNo and aliasName.

The "/.iot/networkInfoFile" file contains the device name (in the provided dataset "[LG] webOS TV SK8000PUA")

*The "/btsvc/mtk.conf" file contains:
*the TV Bluetooth name (in the provided dataset "[LG] webOS TV SK8000PUA")
*the TV Bluetooth MAC Address (in the provided dataset "00:51:ed:2b:db:27", manufactured by LG Innotek)
*the paired LG MR18 remote controller Bluetooth MAC Address (in the provided dataset "98:f5:a9:da:aa:f5")

The "/btsvc/mrcu1.info" file contains additional details about the remote controller, including the firmware version.

The "/btsvc/pairing_history" file contains information about remote controller pairing, including timestamps.

The "/btsvc/bluedroid-mtk/rec/bluedroid/bt_config.conf" file contains additional information about paired devices.

The "/channel_logo/major_logo_img" folder contains TV channels images an related JSON files.

The "/irdbmanager/setting/oss_setting_info_stb.txt" file contains information about the connected Set Top Box. In the provided dataset the Set Top Box is manufactured by "Direct TV" and connected on HDMI_1 port. The service name is "DirectTV(Denver)".

The "/var/lib/connman/" file contains information about connected Wi-Fi.

The "/var/luna/data/downloadhistory.db" file contains information about installed applications. An embedded JSON file for each installation is available. It contains information about the specific app, including timestamps. In the specific dataset various apps are installed like Netflix, Amazon Prime Video, Vudu, ChannelPlus, Sling and YouTube.

The "/var/lib/wam/" folder contains information about the "Web Application Manager", a component responsible for web application management in webOS platform. The Default subfolder is a Chrome-style profile folder, that can be parsed with Hindsight.

Various Chrome-style Localstorage databases are stored in the profile. Among the others, the "lgappstv.com" contains last use date for each installed app.

The "/var/luna/preferences/" folder contains various TV settings and preferences.

The "/var/luna/preferences/localtime" file contains the local timezone. In the provided dataset "/usr/share/zoneinfo/America/Denver".

The "/var/luna/preferences/option" file contains various TV settings, including the ZIP code. In the provided dataset "80020", that corresponds to "Broomfield, Colorado" where VTO Labs is located.

The "/var/luna/preferences/locl" file contains the SHA-256 value of the System PIN. In the provided dataset the value is "9af15b336e6a9619928537df30b2e6a2376569fcf9d7e773eccede65606529a0" that corresponds to the PIN "0000".

The "/var/luna/preferences/systemprefs.db" file contains various system preferences, including the local timezone.

Some other interesting files in the "/var/luna/preferences/" folder are:
*time
*twinTV
*channel
*environmentCondition
*localeinfo

The "/var/spool/" folder contains various log files.

For example, the "analytics_log_NNN.tgz" files, contain information about app launch, and other user actions. More research is definitely needed on these logs, but they are for sure useful to build a usage timeline.

The "/webbrowser/chrome/Default" folder contains the internal web browser data. The WebOS Web Browser is based on Chromium, so the content of the folder can be easily parsed with Hindsight.

In the provided dataset I found three Google searches ("calendar", "aol mail", "sprout"), a login on AOL.com with a specific email address and a login on Facebook.com.

===Partition 3 (/media)===

Partition 3 (/media) contains user data and third-party applications binary files, libraries and configuration.

The "cryptofs/apps/usr/palm" folder contains third-party application binary files, libraries and configuration.

The "cryptofs/apps/var/lib/status" file contains third-party application details, including installation date.

*"captureTV" folder should contain captured images
*"internal" folder should contain user files (wallpapers, downloads, ringtones)
*"myphoto" folder should contain user photos

==Links==
* https://blog.digital-forensics.it/2020/12/a-journey-into-iot-forensics-episode-2.html

Executable compression

2022-01-15T07:52:11Z

Kayvon2008: /* List of formats */

{{FormatInfo
|formattype=electronic
|subcat=Compression
|thiscat=Executable compression
}}
'''Executable compression''' takes an [[Executables|executable]] file, and makes it smaller, without changing its functionality. One way to do that is to compress the file and bundle it with a small decompression routine, which decompresses the file, in memory, every time it is executed.

It is usually possible to identify a particular kind of compressed executable as such, and decompress it to its original form. Another possibility is to let the program decompress itself, then try to capture it in memory. However, some developers have used various tricks to try to make these things difficult.

== Security information ==
Executable compression frequently involves techniques, such as self-modifying code, that are also used by '''viruses''' and other malware. Compounding the problem, a compressed executable can't be properly scanned by anti-malware software unless it knows how to decompress it.

Don't be surprised if your anti-malware software thinks some compressed executable files look suspicious. Research into this topic should be considered '''NSFW'''.

== List of formats ==

* [[624]]
* AINEXE - See [[AIN#AINEXE]]
* [[aPACK]]
* [[APK]]
* [[ASPack]]
* [[AVPACK]] (Andrei Volkov)
* [[AXE (executable compression)|AXE]]
* [[COMPACK]]
* [[DIET (compression)|DIET]]
* [[EXEPACK]]
* [[ICE (executable compression)|ICE]]
* [[JAM (executable compression)|JAM]]
* [[The JAM Packer|JAM Packer, The]]
* [[LZEXE]]
* [[PECompact]]
* [[Petite]]
* [[PGMPak]] (Todor Todorov)
* [[PKLITE]]
* [[PKLITE32]]
* [[Pro-Pack|PRO-PACK]]
* [[SCRNCH]]
* [[SHRINK (executable compression)|SHRINK]]
* [[TINYPROG]]
* UCEXE - See [[UltraCompressor II#UCEXE]]
* [[UPX]]
* [[WWPACK]]
* [[XPACK]]
* [[X-pack for Executable‎]]

== Software ==
* [https://www.sac.sk/ SAC FTP collection] → [https://www.sac.sk/files.php?d=7 PACK] (also at [ftp://ftp.elf.stuba.sk/pub/pc/pack/], [http://info.elf.stuba.sk/packages/pub/pc/pack/], [http://ebook.pldworld.com/%5Bmirroring%5D/ftp.elf.stuba.sk/pub/pc/pack/])
* {{OldskoolDOSEXE}} → Executable Tools Pack → packers/, unpackers/
* [{{CdTextfilesURL|pdos9606/ARCHIVER/EXECOMP/}}] - A collection of some compression and decompression utilities for DOS

== See also ==
* [[Archiving#Self-extracting archives]]

== Links ==
* [[Wikipedia: Executable compression]]

[[Category:Executables]]
[[Category:Executable envelopes]]

Application

2022-01-15T07:50:53Z

Kayvon2008: Redirected page to Executables

#REDIRECT [[Executables]]

Application

2022-01-15T07:50:30Z

Kayvon2008: Redirected page to Excecutible

#REDIRECT [[Excecutible]]

Application

2022-01-15T07:49:27Z

Kayvon2008:

An application is different from a regular executable because it consists of a folder instead of a single file and has no registry tweaks.
==Types==
*[[iOS app]]
*[[APK]]
*[[Smart TV app]]

----
https://github.com/openlgtv/epk2extract