WARNING iPhone Ringtonemaker Don't use

Discussion in 'iPhone' started by Flyingstar, Dec 3, 2007.

  1. Flyingstar macrumors newbie

    Joined:
    Sep 13, 2007
    #1
    Iphone ringtonemaker (Efko software)

    Will NOT refund your purchase price when their product fails to work as advertised!!

    It stopped working, I reported the issue to their support department, they could not "fix" it and I lost all my Itunes ringtones as well.

    I had to do a restore to get my iPhone to have ANY after sale ringtones.

    Efko just said "sorry no refunds" Beware!
     
  2. chr1s60 macrumors 68000

    chr1s60

    Joined:
    Jul 24, 2007
    Location:
    California
    #2
    That is just bad business. This kind of thing happens and then software companies wonder why some people steal their products instead of paying for a license.
     
  3. chadrob30 macrumors 6502

    chadrob30

    Joined:
    Nov 13, 2007
    Location:
    In front of my Mac.
    #3
    With the latest firmware update this shouldn't be an issue at all. Apparently Apple is relaxing the chokehold on custom ringtones. Just make your own!
     
  4. megfilmworks macrumors 68020

    megfilmworks

    Joined:
    Jul 1, 2007
    Location:
    Sherman Oaks
    #4
    Why use iphoneringtonemaker when you can simply add the ringtones by dragging them to the ringtone folder?? This works on locked unhacked iPhones and it's free.
     
  5. chadrob30 macrumors 6502

    chadrob30

    Joined:
    Nov 13, 2007
    Location:
    In front of my Mac.
    #5
    That's pretty much what I was getting at, but I worded it all wrong, lol.
     
  6. Eddiestein macrumors member

    Joined:
    Jul 30, 2007
    #6
    If you bought it on a credit card couldn't you do a chargeback?
     
  7. dacreativeguy macrumors 68020

    Joined:
    Jan 27, 2007
    #7
    This is why I won't pay for any 3rd party iphone software until Apple officially sanctions it. No way I'm going to give someone $20 for something that Apple can nullify in the next firmware update. Read the fineprint on these developers' sites and see how they address this issue.
     

Share This Page