[FIXED] MPE creates duplicated device / IMEI

For user who dont speak german please use this part of my forum
gautxori
Beiträge: 48
Registriert: Fr 3. Apr 2015, 12:09

[FIXED] MPE creates duplicated device / IMEI

Beitrag von gautxori »

When connecting my phone to my PC, MPE creates a new ("unknown") phone, with the same IMEI I already had configured.

So I get this in MPE on PC:
Bild

And I get this in windows explorer:
Bild

You see there are two devices for the same IMEI: [355748091167135]

I have compared the files "settings.dat", for I guess these are the ones storing information to identify the devices. Apparently there are only two meaningful lines which could link the devices to these files. The older device configuration, "samsung SM-J530F", has

Code: Alles auswählen

ProfileData=3E31282C2617144B36341F7A05057D166504604C465C5141020901077B67746C66248C9436185F4345582A700F6A73290104454B0201071665030872194C405B2350
SIM0=0,,CARD 1,simyo,VS
and the "unknown" device configuration has

Code: Alles auswählen

ProfileData=383E2E313C0E1D4B3E4A0705070275607C6E624F445A564C6FCFCF
SIM0=0,,CARD 1,unknown,VS
(Note: both the device name and the SIM information are wrong in the new, "unknown" device, for the phone network name is still "simyo", and the device is "samsung SM-J530F").

I synced the device yesterday, after reinstalling a nandroid backup, and yesterday MPE recognized the device properly. I'm not sure what could have happened since then, for I did several updates after reinstallation. I think I even updated MPE Client.

In an attempt to make the device recognized with the above profile, I have changed in "settings.dat" the ProfileData, to the value of the new device. When trying to connect the device, a new profile continues to be created.

Questions: Is there any way to make MPE recognize the device as the previous "samsung SM-J530F", instead of creating a new "unknown" device? Can it be done by changing some file, or file content?
Otherwise, in case i should create a new device, which would be the steps to recover as much as possible from the previously configured device, "samsung SM-J530F", to the new one? Which files should I copy from one explorer folder, to the new one? Should I modify the content of any file to avoid further errors?
Zuletzt geändert von gautxori am Mo 4. Mär 2024, 17:51, insgesamt 1-mal geändert.
gautxori
Beiträge: 48
Registriert: Fr 3. Apr 2015, 12:09

Beitrag von gautxori »

I checked the debug.txt file, I cannot understand why MPE on PC does not recognize the device properly...:
...
15:04:49.87 Connect via USB
15:04:49.87 RunADBCommand: start-server
15:04:49.92 ADB CommandResponse:
15:04:49.92 RunADBCommand: devices
15:04:49.97 ADB CommandResponse: List of devices attached
5200627cb86bc4cb device
15:04:49.97 RunADBCommand: -s "5200627cb86bc4cb" forward tcp:5210 tcp:5210
15:04:50.10 ADB CommandResponse:
15:04:50.10 Try connecting to 127.0.0.1...
15:04:50.11 AndroidSocket_Connect...
15:04:50.22 Connect to Android OK (127.0.0.1)
15:04:50.22 Settimeout: RT=2000 WT=500
15:04:50.23 [TX]: AT+CGSN
15:04:50.27 [RX]: AT+CGSN
15:04:50.27 [RX]: 355748091167135
15:04:50.27 [RX]: OK
15:04:50.27 IMEI=355748091167135
15:04:50.27 G_Userfolder=C:\MPE\MyPhoneExplorer\samsung SM-J530F [355748091167135] G_IMEI=samsung SM-J530F [355748091167135]
15:04:50.27 Settimeout: RT=15000 WT=1000
15:04:50.27 [TX]: AT*PIN?
15:04:50.29 [RX]: AT*PIN?
15:04:50.29 [RX]: *PIN: ACCESS OK,10
15:04:50.29 [RX]: OK
15:04:50.29 [TX]: ATI
15:04:50.31 [RX]: ATI
15:04:50.31 [RX]: unknown
15:04:50.31 [RX]: OK
15:04:50.31 [TX]: AT*APPVERSION=2.1.0
15:04:50.33 [RX]: AT*APPVERSION=2.1.0
15:04:50.33 [RX]: 24,3.9
15:04:50.33 [RX]: OK
15:04:50.33 [TX]: AT*ECAM=1
15:04:50.35 [RX]: AT*ECAM=1
15:04:50.35 [RX]: OK
15:04:50.35 [TX]: AT+CBC
15:04:50.37 [RX]: AT+CBC
15:04:50.37 [RX]: +CBC: 1,100
15:04:50.37 [RX]: OK
15:04:50.37 [TX]: AT+CSQ
15:04:50.39 [RX]: AT+CSQ
15:04:50.39 [RX]: +CSQ: 1,99
15:04:50.39 [RX]: OK
15:04:50.39 Alle Verbindungsaktionen beendet
15:04:50.39 New IMEI=unknown [355748091167135], checking for Password
15:04:50.40 No password set, sucess...
15:04:50.53 SaveDatafile: Phonebook.dat (233974 Bytes) False
15:04:50.58 SaveDatafile: Notes.dat (244090 Bytes) False
15:04:50.76 SaveDatafile: Organizer.dat (591616 Bytes) False
15:04:50.80 DoItemUpdate fertig
15:04:50.83 CheckUserDirectory for: unknown [355748091167135]
15:04:50.83 Userfolder=C:\MPE\MyPhoneExplorer\unknown [355748091167135]
15:04:58.31 Lade Userdatenbank: unknown [355748091167135]
15:04:58.53 pb_metadata.xml does not exist!
15:04:58.53 Phonebook.dat does not exist!
15:04:58.53 SimPhoneBook.dat does not exist!
15:04:58.55 Kontakte geladen
15:04:58.56 Calls.dat does not exist!
...
I also downgraded MPE Client version 3.9:
- to 3.4. I get "OBEX Errorcode: D0 - Internal server error" messages with the older version.
- to 3.3. MPE creates a new Unknown profile, whose IMEI is [000000000000000]
FJ
Site Admin
Beiträge: 32106
Registriert: Mi 15. Feb 2006, 01:16
Wohnort: Tirol
Kontaktdaten:

Beitrag von FJ »

The "unknown" is the Manufacturer Name and Model of the phone. Probably you have a app on the phone which prevents MyPhoneExplorer Client from reading the real Manufacturer name and model. I never saw this before so i don't think its a official system setting.
Ich bitte um Verständnis daß ich aufgrund des hohen Aufkommens im Forum und meines zeitlichen Rahmens nichtmehr jeden Thread im Forum persönlich lesen bzw. beantworten kann.

Bitte benutzt auch die Forum-Suche bzw. die FAQ
gautxori
Beiträge: 48
Registriert: Fr 3. Apr 2015, 12:09

Beitrag von gautxori »

FJ hat geschrieben:The "unknown" is the Manufacturer Name and Model of the phone. Probably you have a app on the phone which prevents MyPhoneExplorer Client from reading the real Manufacturer name and model. I never saw this before so i don't think its a official system setting.
You're right, the strange thing was that even after disabling that app - XprivacyLua -, I could not make MPE Client work. Fortunately now it's working.

BTW, there is some bug in MPE Client 3.9, it does not close properly when there is no connection from PC, the countdown reaches -59 min...:

Bild
Antworten