Timestamps Lost, connection errors (used MTP)

Posts: 24 · lijsfgfdgdf 13 Oct 2017, 07:41

Today I upgraded FFS and backed up my mobile phones.

For one Phone, FFS reports
Error calling "IPortableDeviceProperties::GetValues".
HRESULT: 0x80042009, Facility: COM/OLE Interface Management

I can browse & Copy files in Windows Explorer without any problem

For the other Phone I noticed that timestamps were lost. All change timestamps are set to 1970 (0 in Unix time)

EDIT: It seems like the problem for the time stamps is recovery mode MTP. Can I update just the timestamps of the backup folders?

Posts: 24 · lijsfgfdgdf 23 Dec 2017, 07:15

Again, I updated FFS and again I cannot backup one of my phones because of the same error

Error calling "IPortableDeviceProperties::GetValues".
HRESULT: 0x80042009, Facility: COM/OLE Interface Management

I would appreciate If someone would reply....

Posts: 7211 · Zenju 23 Dec 2017, 10:25

Can you post the full error message for the "0x80042009" error code? This might indicate a problem that should be ignored.

Posts: 24 · lijsfgfdgdf 18 Mar 2018, 13:40

That IS the full error message that is shown to me by FFS. Version 9.8 still the same problem. If there is a Logfile with additional Information please tell me where to find it.

Posts: 7211 · Zenju 18 Mar 2018, 13:55

There must be some text prior to "Error calling..."

Posts: 24 · lijsfgfdgdf 23 Mar 2018, 07:10

Well, there is prior text, but no concrete error message. Its just "cannot read". As this is translated based on FFS language setting, it is not part of the Drivers/OSes error message I guess:

"Cannot read directory "mtp:\HUAWEI GRA-L09\Interner Speicher".

Error calling "IPortableDeviceProperties::GetValues".
HRESULT: 0x80042009, Facility: COM/OLE Interface Management"

Posts: 7211 · Zenju 23 Mar 2018, 09:43

I'm suspecting that there is a non-file, non-folder item that FFS could and should ignore.
Here is the WPD tool that gives a low-level view on the MTP device:
https://www.mediafire.com/file/esuors6i88u1ahf/WPD_Tools_32-bit.rar
Can you browse to the "Interner Speicher" node via "wpdinfo.exe" and report which items it shows there?

Posts: 24 · lijsfgfdgdf 23 Mar 2018, 10:21

I dont see any export functionality, so I uploaded a screenshot for you.

Posts: 7211 · Zenju 23 Mar 2018, 10:47

These are the device properties, what about the child items of WPD_OBJECT_ORIGINAL_FILE_NAME=="Interner Speicher"?

Posts: 24 · lijsfgfdgdf 23 Mar 2018, 11:32

Well, there are no Names in the tree, just DEVICE then one level deeper item s10001 and one more level deeper several oXXXX subitems with XXXX being hexadecimal chars. Some items wpd info is not able to get properties for:

Failed to get ALL property values for object 'o1671', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o1673', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o37AE', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o37B0', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o3EFC', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o42D9', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o45FC', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o466A', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o5A2F', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o8322', HRESULT = 0x80042009 (0x80042009)

probably those cause the issues?!

the other oXXXX have an WPD_Object_NAME property corresponding to folders on my phone.

Posts: 7211 · Zenju 23 Mar 2018, 14:48

The WPD_Object_NAME property is also okay if WPD_OBJECT_ORIGINAL_FILE_NAME does not exist. Assuming the errors above are for the child items of "Interner Speicher", is there any info shown in the WPDinfo tool, except for the object id?

Posts: 24 · lijsfgfdgdf 23 Mar 2018, 16:59

Yes, s10001 has WPD_Object_NAME "Interner Speicher", so all the oXXXX I talked about are child items of "Interner Speicher"
Also the error code in WPD matches the error code that is presented by FFS.

Posts: 7211 · Zenju 23 Mar 2018, 18:26

Is there any info shown in the WPDinfo tool for the child items, except for the object id?

Posts: 24 · lijsfgfdgdf 25 Mar 2018, 18:54

like this?

Posts: 7211 · Zenju 26 Mar 2018, 08:11

I'd like to see the tree of child items, with all their properties and potential error messages.

Posts: 24 · lijsfgfdgdf 26 Mar 2018, 19:10

I'd like to see the tree of child items, with all their properties and potential error messages. Zenju, 26 Mar 2018, 08:11

well, I described the tree of child items:

There are no [natural] names in the tree, just DEVICE then one level deeper [child] item s10001 and one more level deeper[children of s10001] several oXXXX subitems with XXXX being hexadecimal chars. lijsfgfdgdf, 23 Mar 2018, 11:32

I described their properties in my last post (besides UID and DATE_MODIFIED and the two NAME properties the functional entries are identical)

And I posted the error messages

Failed to get ALL property values for object 'o1671', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o1673', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o37AE', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o37B0', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o3EFC', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o42D9', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o45FC', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o466A', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o5A2F', HRESULT = 0x80042009 (0x80042009)
Failed to get ALL property values for object 'o8322', HRESULT = 0x80042009 (0x80042009) lijsfgfdgdf, 23 Mar 2018, 11:32

I'm pretty sure FFS could handle this if it would ignore (or allow the user to ignore) the items with

HRESULT = 0x80042009 (0x80042009)

Posts: 7211 · Zenju 27 Mar 2018, 08:58

well, I described the tree of child items: lijsfgfdgdf, 26 Mar 2018, 19:10

Can you post complete, unabridged screenshots of what you see in the WPD tool (including the tree view on the left)?

Posts: 24 · lijsfgfdgdf 28 Mar 2018, 20:46

well, I don't have the device here right now and the forum software breaks ASCII ART descriptions.

Using a different Android Device I see the same kind of items; A DEVICE with child s10001 for the storage and in the subtree starting at node s10001 a lot of oXXXX items for the objects (folders) - so I guess this structures looks like this for every android device supporting MTP.

Why not allow to ignore HRESULT = 0x80042009 (0x80042009) and give me a test build to verify?

I can make a screenshot of the tree tomorrow, but I will not do screenshots of each of the hundreds of oXXXX items in order to show their properties.

Posts: 24 · lijsfgfdgdf 11 Apr 2018, 18:16

: FFS_P8_Full.png (484.87 KiB) Viewed 7366 times

Posts: 24 · lijsfgfdgdf 11 Apr 2018, 18:17

I'm sorry, I was quite busy during the last days.

Posts: 7211 · Zenju 12 Apr 2018, 13:34

Can you post a screenshot for one of the failed items, e.g. "o1673"? You don't need to remove the date or persistent unique id fields, as they are not sensitive information.

Also try to enlarge the properties window a bit, so that all of them are visible.

Posts: 24 · lijsfgfdgdf 29 Jun 2018, 05:57

Sorry for not answering. I had to reset that phone, did a backup using a tool that ignored the error (named GoodSync) and after resetting the phone the buggy items are gone. So I do not have the problem anymore and I cannot be of any help solving it. However I still think it is easily solvable by ignoring items that have error 0x80042009 or at least giving the user the ability to decide to ignore that error.