Project

General

Profile

MigrateContactsDatabase » History » Revision 4

Revision 3 (Denis 'GNUtoo' Carikli, 05/05/2021 02:34 PM) → Revision 4/43 (Denis 'GNUtoo' Carikli, 05/08/2021 07:16 PM)

h1. MigrateContactsDatabase 

 h2. Warning 

 * This article is a work in progress 
 * It hasn't been tested yet and might contain mistakes 
 * It needs to be more clear for less technical users 

 h2. Migration 

 {{toc}} 

 h2. Backuping your contacts 

 You'll first need # First backup your contacts somewhere safe 

 h2. Setup ADB 

 Follow the instructions for [[ADB|setting up ADB on your computer]] so that you can access a 
 # Then as root shell on your device. 

 *NOTE*: when prompted on your Replicant device, make sure that you check the box that says *Always allow from this computer* when you grant your computer USB debugging permissions. Otherwise, you will be unable you'll need to obtain root shell access on your Replicant device when you reboot it into the recovery OS to actually perform the backup. 

 *NOTE*: for security reasons, you may want to [[ADB#Revoking-all-computers-USB-debugging-permissions|revoke these non-expiring permissions]] once the backup is complete. 

 h2. Reboot into the recovery 

 To reboot in the recovery, you can follow the instructions in the [[RebootIntoTheRecovery]] wiki page. 

 h2. Erase your contact database 

 Once in the recovery, you will then be able to erase your contact database: 

 <pre> 
 rm -rf /data/data/com.android.providers.contacts/databases/ 
 </pre> 

 h2. Install the new Replicant images 

 Once the backup is done, you can proceed to install the Replicant images that have the contact database format to migrate to. 

 h2. Revoke USB debugging permissions 

 If you don't need @USB debugging permissions@ anymore, it might be a good idea to remove them. The [[ADB#Revoking-all-computers-USB-debugging-permissions|Revoking all computer's USB debugging permissions]] section in the ADB wiki page explains how to do that. 

 That's it! Your device's EFS partition is now backed up. Your device should be running Replicant normally again.