If you have any issues, please first have a look at the FAQ , and if that doesn't help with you, get in touch with me 1. Backup your iPhone You should switch your iPhone to Flight Mode or take out the SIM card before creating the backup, otherwise you may receive messages after you created the backup, and those won't be included in the backup file then.
Connect your iPhone to your computer, start iTunes and make an unencrypted backup by selecting your iPhone and clicking the Back Up Now button. Detailed instructions can be found on Apple's support pages. Find your iTunes backup folder Go to the folder that contains your iTunes backups.
Depending on the operating system you are using, this folder will be located at the following paths: This is the folder of the backup you just created. Copy the files to your phone Locate the file 3d0d7e5fb2cee4dea3d28 in the folder 3d for your messages, and the file 5ac78afad79cd in the folder 5a for your call logs. Copy the file s you want to import to your Android phone. The app works with any filename, so you may want to rename the message database file to something like sms.
The renaming is completely optional, though. If you use the original filename s or one of the ones suggested above, the app will find the files automatically and not prompt you to select the manually. Better safe and charged than sorry and having to start over.
I would also recommend just letting your phone do its thing while the import is running. The import should continue in the background if you absolutely have use your phone for something, but the general rule of thumb is: Textra , you can skip to step 5.
If you are not using the default Messaging app, theoretically everything should work just fine - but i can't promise anything. If it does not, and you are getting any errors or weird behaviour other than those cases covered in the FAQ , you may want to switch back to the stock Messaging app, or even completely remove any 3rd party messaging apps.
Install the app Please continue with installing the app on your phone. You probably won't need the instructions below, but they will give you an idea of what to expect. No need to read this, but here's what will happen next: After opening the app, tap on the Select File Button.
If this is the first time you use the app, Android will ask you to grant iSMS2droid certain permissions and also to switch your default messaging application to iSMS2droid. This is required to be able to write to Android's messaging database. After the import has finished you will be asked to switch back to your previous messaging application, so there's nothing you have to change by yourself.
Now navigate to the location of the message database file that you copied onto your phone in step 3. When you select the message database file, the app will ask you to either import all messages or select conversations by contact. If you select the later, it will show you the names of the contacts if you have already added them to your phone's addressbook, otherwise it will show you only the contacts' phone numbers.
If you chose to import all messages, the app will now start the import process, otherwise it will load a list of conversations and allow you to pick the conversations you'd like to import. You can continue using your phone while your messages are being imported, but please be aware that using other apps may decrease the performance of iSMS2droid, resulting in a longer import time. Once the import has finished, you'll be asked to switch your messaging application back to the one that was previously the default, and then you're done!
If you want just your messages, you only need to copy one single file, which can be found in your iTunes backup folder see above , and that is the file 3d0d7e5fb2cee4dea3d28 in the folder 3d If you want your call log, you need to copy the file 5ac78afad79cd from the folder 5a. For older iOS versions it's called 2b2ba1bc3a5ac8c27afdf14afb42c61a19ca. If your backup folder does not contain the backup file of the message database, you haven't received or sent any messages since the last time you created a backup.
Please check the older backup folders, starting with the one that has the most recent timestamp at the end, and search for the file in those. If you don't have any other backup folders, and are absolutely sure that the file you are looking for is nowhere to be found e. If you are using an older version of iOS, the call logs file is called 2b2ba1bc3a5ac8c27afdf14afb42c61a19ca. This prevents the app from finding the file automatically, so it will then ask you to select it manually - after which everything should work as expected.
In over 5 years of supporting this app, there hasn't been a single support request for this error message where the reason wasn't either a encrypted backup, or a completely wrong file. For a detailed explanation, please have a look at the next question. If you receive a SMS message or plain-text iMessage, your iPhone takes the text body and saves it together with some metadata into its message database.
This also happens when you receive a MMS message or iMessage with attachments , but when saving the text body and metadata into the message database, it also downloads the attachments and saves them into a specific folder on your iPhones filesystem, and then puts the path to those attachments into a separate table in the message database.
This means we now have the text body and the information about its attachments in the database - but we don't have the attachment files themselves. When you create a backup of your iPhone, those attachments get also backed up to your computer, but each one as a separate files with a cryptic filename that is based on the path of the file on your phone.
It would theoretically be possible to also import the attachments, but that would require you to copy your whole iTunes backup folder to your Android phone, as it is impossible to predict which files from your backup are message attachments until iSMS2droid actually opens the message database and starts importing.
I am thinking about making it a two-step process: Unfortunately i'm not in possesion of an iPhone anymore, so i can't really fully develop this feature, as it would require extensive testing with real backups. This means you should be able to import Please keep in mind that any other activity during the import will greatly affect this number, especially any apps that use lots of memory or access the storage.
Any security apps or anti-virus scanners should also be disabled during the import, as they will most likely try to inspect every single message, which will slow down the process considerably. If you are using a Samsung device: Samsung has fiddled with their version of Android, causing it to crash when just reading the count of messages.
Newer Samsung devices seem to be working fine again, so if it's working for you, just ignore the warning. If you are either using Samsung device with a not-so-recent Android version, or don't use a Samsung device but the app crashes anyways, please use the Online Converter below.
Your messages are most likely not really missing, you just don't see them - yet. The import process writes those messages to a database, and the Android messaging app then reads them from this database to display them. The bigger the database, the longer it takes for the messaging app to load them, and that's why Android does something called "indexing the database". You don't need to know the technical details, but it's a process that is ran for each new message, and it takes a while.
Once the messages are indexed, the messaging app can show them with nearly no delay. If you are receiving or sending messages, this indexing happens in the fraction of a second, you shouldn't notice it at all. But as we are writing hundreds, thousands, or for some users even hundredths of thousand messages to the database, this indexing takes substantially longer, and the messaging app will only show those messages that have already been indexed - and that looks like there are messages missing, even if they are in the database.
If it's been more than a couple of minutes or an hour, if you imported a lot of messages since the import, and you still don't see all messages, you can try to reboot your phone and then check the messaging app once it has started up again. If you see at least some new messages then, give it some more time to do the indexing, don't just reboot it again right away.
Let your phone work through the database, the less you use your phone do during this process, the faster they will show up. Please see the above question, "The app crashes when i select the database file! If you are using a FairPhone: If your device is running an Android version older than that, iSMS2droid will simply not work, and there's nothing that can be done about it, except updating your device to Android "Lollipop" 5.
You shouldn't be buying a device with such an old Android version anyways, as the incompatibility of iSMS2droid will be the least of your worries.
If for whatever reason you absolutely must import your messages on such an old device, please use the Online Converter below. The app's name is a concatenation of the phrase iPhone SMS to Android Converter, formerly Support I will try to provide support for this app as much as i can, but there are a couple of things you should know: If you first give the app a bad rating on Google Play because something didn't work, and then ask me for help, i will ignore you.
If you contact me with a question that was already answered in the FAQ or instructions, i will ignore you. If you contact me through any other means than the support address provided below, i will ignore you. If you come across as if i'd owe you anything or you would be entitled to something, i will ignore you.
This is a free app, after all. If you have a very exotic problem, i may ask you to provide me with your message database file. Everybody is a snowflake, and some problems can't be reproduced without having the data that causes them. If you are sure that your issues is really something that wasn't explained in the FAQ or solved by following the instructions, send an email to support isms2droid. Please include the app version shown on the main screen , the device name and the Android version you are using, otherwise it will be more difficult to provide any support.
The converter is nowhere near as capable as the iSMS2droid Android app, but i'm providing it for those who can't use the app. If you haven't tried using the iSMS2droid app, please do so first.