Ringtones deleted - MY-X55 borked

[lordtoran]

Got my new MY-X55 (identical to MYX5-2) last wednesday and bought a data cable (not an original Sagem one) the same day. Using the PL2303 drivers, I got the cable running at the USB port, everything fine.

After uploading some ringtones to the mobile yesterday, I decided it would be better to rename the ringtones on my hard disk for them to be distinguishable from the built-in ringtones. And to free some space on the phone, I used the "Delete all" command in the sound menu to get rid of the already uploaded and also the built-in ringtones, because these weren't my taste at all.

This action seems to have messed up the phone's internal configuration, because uploading files was instantly broken. First thing I noticed was that My Pictures and Sounds wouldn't upload most .wav files anymore, but everything went fine with My Discover. AMR still worked with MPAS. I also tried TelMemPlus and it also worked, although the connection was lost more frequently.

After coming from work, things got more complicated. Both MPAS and My Discover wouldn't upload any files at all, and MPAS would permantly state a "cable not connected message" after a failed connection attempt - but it would still notice when I just powered on the phone and input the PIN .

Now, when I want to upload a AMR ringtone, I do the following:

- Launch My Discover, point it to COM4, let it detect the phone, try to upload the ringtone
- After about 20% of transfer my phone issues a "Rejected" message.
- Try to upload the file again, now the "Rejected" message does appear directly after the upload is finished, or sometimes not at all.
- Try to upload one more time, with the same result. It is worth noticing that My Discover does not show the "Upload finished" message anytime.
- Close My Discover's I/O window, launch MPAS, and now it detects the phone correctly and may allow me to upload 2 or 3 ringtones before losing connection permanently or stating that the phone doesn't answer after upload.

I would like to reset the mobile to factory settings or hack the section of the config that has been messed with to get rid of this random behavior. Anyone have an idea?