TRANSFERRING to degoogled phone
Transferring Data from iPhone to GrapheneOS
Here are two practical methods for transferring your contacts, messages (SMS/RCS), call history, and photos from an iPhone to a GrapheneOS device (Pixel phone). These methods prioritize privacy and work well with de-Googled setups.
Important Notes Before Starting
- Perform transfers after installing GrapheneOS (flashing wipes the Pixel).
- Contacts transfer easily via standard .vcf files.
- Photos transfer reliably as files (HEIC format works on GrapheneOS, but you can convert to JPG if needed).
- Messages and call history are the trickiest due to Apple's closed ecosystem. Full iMessage history often doesn't transfer cleanly; SMS works better. Call logs are rarely fully transferable without paid tools.
- Disable iMessage on your iPhone (Settings > Messages > iMessage off) and deregister your number at appleid.apple.com to avoid issues with future texts.
- Use a computer (Mac, Windows, or Linux) as an intermediary for easier file handling, or peer-to-peer apps like LocalSend (available on both platforms).
1. File-Based Export + Manual Transfer (Most Privacy-Friendly, No Cloud Required)
This method uses built-in iOS tools and direct file sharing. It's excellent for privacy-conscious users.
Contacts:On iPhone: Open Contacts app → Go to Lists view → Long-press "All iPhone" or "All iCloud" → Export → Select All Fields → Save to Files app as a .vcf file.
Transfer the .vcf file to GrapheneOS (via USB cable, LocalSend, or USB drive).
On GrapheneOS: Open the default Contacts app → Import the .vcf file.
Photos:
On iPhone: Open Photos app → Select albums or all photos → Share/Save to Files (or use Shortcuts app for bulk export).
Transfer files via LocalSend (peer-to-peer over Wi-Fi, no cloud) or USB cable to a computer then to GrapheneOS.
On GrapheneOS: Use a gallery app (e.g., Simple Gallery from F-Droid) to view/import. Photos land in the DCIM or Pictures folder.
Messages & Call History:
Limited success. Export SMS via a third-party iOS app or use iTunes/Finder backup on a computer, then extract with tools like iMazing or iExplorer (paid).
For GrapheneOS: Install an SMS import app like SMS Backup & Restore (via Aurora Store or F-Droid alternatives). Full call history is often incomplete or requires advanced SQLite extraction (not beginner-friendly).
Many users report partial SMS success but recommend starting fresh or only importing recent important threads.
Pros: High privacy, no third-party accounts.
Cons: Manual; messages/call history are partial at best.
2. Computer as Intermediary (Reliable for Bulk Photos & Contacts)
Use your computer to pull data from iPhone and push to GrapheneOS.
Contacts:On computer: Connect iPhone via USB → Use Finder (Mac) or iTunes/Windows Photos → Export contacts as .vcf (or sync via iCloud web if you temporarily use it, then export).
Import .vcf into GrapheneOS Contacts app (same as Method 1).
Photos:
Connect iPhone to computer → Use Photos app (Mac/Windows) or Image Capture to download all photos/videos to a folder.
Connect GrapheneOS Pixel via USB (enable File Transfer mode) → Copy the folder over.
Alternative: Use Syncthing after transfer for ongoing sync (install on computer + GrapheneOS).
Messages & Call History:
On computer: Create an iTunes/Finder backup of iPhone → Use third-party software like iMazing or AnyTrans to extract SMS and call logs into readable formats (XML/CSV).
Convert and import SMS into GrapheneOS using SMS Backup & Restore app. Call history transfer is spotty—some tools export it, but native Android dialer import is limited.
Pros: Handles large photo libraries well; works offline.
Cons: Requires a computer; some tools for messages are paid.
Additional Tips
- Use Syncthing, DAVx⁵, or EteSync for ongoing sync after the initial transfer.
- If you have thousands of photos, tools like Ente (E2EE photo app with iOS client) can upload from iPhone and sync to GrapheneOS.
- iMessage limitation: True iMessage history (blue bubbles, effects) doesn't transfer well to Android. You'll see them as green SMS going forward.
- Test small batches first to avoid data loss.
- Avoid full "phone transfer" apps that require Google services or cloud accounts if privacy is your priority.
Visual Voicemail on GrapheneOS
Visual voicemail (VVM) on GrapheneOS is tricky because the OS is fully de-Googled and uses AOSP (Android Open Source Project) components. Many carriers rely on proprietary protocols, Google services, or specific carrier configs that don't fully work out of the box on GrapheneOS, even if basic voicemail (dial-in) functions. You've already contacted your carrier, so the issue is likely compatibility with GrapheneOS rather than an account problem.
Most Effective Solutions (Least to Most Invasive)
▼ 1. Basic Troubleshooting (Try These First)
Toggle VVM off/on:
Open the Phone app (GrapheneOS default dialer or Google Phone if installed).
Go to Settings > Voicemail.
Turn Visual Voicemail off, then back on.
Restart your phone afterward.
Disable Wi-Fi temporarily, enable mobile data, and try activating VVM again (some carriers need pure cellular for initial setup).
Check voicemail setup via dial-in:
In Phone app > Settings > Voicemail > Advanced settings > Setup.
Note the voicemail number, dial it, set a PIN/password, and record/select a greeting if not already done.
Then re-enable VVM.
Clear cache for the Phone app (Settings > Apps > Phone > Storage > Clear cache).
Restart phone and test with a new test voicemail left for yourself.
▼ 2. Carrier-Specific Workarounds
VVM support varies heavily by carrier:
T-Mobile (and MVNOs like Mint, Tello, Metro): Often problematic on Pixel 7+. Many users report it fails to activate in both GrapheneOS and Google dialers. A common fix is installing the official T-Mobile Visual Voicemail app (via Aurora Store if avoiding Play Store). Some users say this works when the built-in dialer doesn't.
AT&T (and MVNOs like Cricket, Consumer Cellular): Frequently does not work on GrapheneOS/AOSP due to lack of support in the open-source dialer. Users often need Google Dialer + sandboxed Play services as a workaround.
Verizon (and MVNOs like Visible, TracFone): Mixed results; some work with Google Dialer, others need tweaks or third-party apps.
If you're on an MVNO, try the parent carrier's VVM app or check their specific setup instructions.
If your carrier has its own dedicated VVM app (e.g., T-Mobile's), install and test that first—it bypasses the dialer entirely for many people.
▼ 3. Use Google Phone App with Sandboxed Google Play (Recommended for Many Users)
GrapheneOS officially suggests this for tricky carrier features:
Install sandboxed Google Play (via the Apps app in GrapheneOS — no full Google account login required for many features).
Install the Google Phone (Phone by Google) app.
Set it as your default phone app.
Try enabling VVM in its settings.
Grant necessary permissions (phone, SMS, etc.) and test with mobile data.
This has resolved activation issues for Verizon, some T-Mobile setups, and others without fully compromising de-Googling.
▼ 4. Alternative Voicemail Solutions (No VVM Needed)
If native VVM remains unreliable:
Google Voice: Port your number or set it up for voicemail (transcription included). Works well with sandboxed Play.
YouMail or similar third-party voicemail apps (available via Aurora Store).
Stick with traditional dial-in voicemail (it's reliable on GrapheneOS).
Some users forward calls to a service that provides visual/transcribed voicemail.
Additional Tips
- Ensure your carrier settings and APN are correct (GrapheneOS pulls these from stock Pixel configs, but you can reset them in Settings > Network & internet > SIMs > Advanced).
- Test on Wi-Fi vs. mobile data—some activation steps fail over certain connections or VPNs.
- Update GrapheneOS and the Phone app to the latest version.
- If nothing works, post details on the GrapheneOS discussion forum (discuss.grapheneos.org) with your exact carrier, phone model, and error message—community members often share carrier-specific tweaks (e.g., secret codes like ##886266344## for advanced VVM config on some networks).
