toffer / iphone-sms-backup Goto Github PK

Now sure how these particular flags should work but I noticed they don't appear in the convert_address_imessage() which causes the script to break.

102405
77825

Hope that helps :)

In case the database has any iMessage messages, they are skipped

Steps to reproduce:

1. Send an iMessage from the iphone
2. Backup the phone to the computer
3. execute ./sms-backup.py

Actual Result:

INFO:root:Skipping msg (13925) not sent. Address: None. Text: Doesn't play :(.

Expected Result:

2011-12-23 22:48:20 |          FROM_NAME | (999) 999-9999 |  Doesn't play :(.

Around the line 401 in the function responsible for getting the addresses for the iMessage a check is failed if the madrid_flags is different from the tested values, making the return of the function faulty as the variables are not initialized.
The code for this type of iMessage is 102405, I will submit a patch once it works for me. I have to probably look into how the recipients are retrieved from the item, so that the multiple recipients are correctly handled.

Newbie here, hoping you can point me in the right direction. I know where the DB file is but am unsure how to follow your suggestion of "pass the db name with --input". I don't know python but I do know basic sql and come from an IT background. Is it a command or do I edit the python file? Any direction would be greatly appreciated.

FYI for anyone else reading, the file is %UserProfile%\AppData\Roaming\Apple Computer\MobileSync\Backup<some long folder name>\3d and the file name is 3d0d7e5fb2ce288813306e4d4636395e047a3d28

Hi. I have some international messages, which are not exported correctly.

For example, a simple UK number should be +44 1234 123456, but your code just convert it into 1234123456, losing all the information about country code. For another example, a simple China number should be +86 123-1234-1234, and your code just convert it into 2312341234, which is even a invalid number, since even though you are allowed to omit the leading country code, the remaining leading 1 is necessary.

My suggestion is just removing strip(), trunc(), and format_phone() functions below. Or at least add a parameter like --keep-phone-number-as-is.

Original Line 129 - 158 in the code:

def strip(phone):
    #...
def trunc(phone):
    #...
def format_phone(phone):
    #...

My experience suggests that sms-backup.py can't support an encrypted backup{

C:\Pittman\SMS-Backup>python sms-backup.py -i Manifest.db
ERROR:root:Unable to access c:\users\ibm_ad~1\appdata\local\temp\tmpwmv22l: file is encrypted or is not a database

C:\Pittman\SMS-Backup>

I am sure that supporting encrypted backups would be quite a challenge.

Before attempting to use sms-backup.py, check to see if backups are encrypted (see https://support.apple.com/en-us/HT205220) and please note that if Encrypt iPhone backup is grayed out, it might be because your company has mandated encryption (see https://discussions.apple.com/thread/8077165). Sigh.

Has anyone modified this script to handle attachments (MMS and iMessage photos, videos, audio files etc)? These are stored in the Attachments directory. I need to parse an iPhone SMS DB, to name these files after the sender and date. Any ideas? Thanks!