MobileRead Forums - View Single Post

Renate · 12-10-2022, 07:42 PM

I noticed that the USB interface descriptor for MTP on my Poke3 is weird.
I patch it in my kernel. I have no idea if that will make any difference, I doubt it.

Code:

C:\>kpatch payload rec.sym onyx.kpc MTP
Profile #8: MTP
01fbfd50 mtp_interface_desc
01fbfd50 09 (ok)
01fbfd51 04 (ok)
01fbfd52 00 (ok)
01fbfd53 00 (ok)
01fbfd54 03 (ok)
01fbfd55 ff -> 06
01fbfd56 ff -> 01
01fbfd57 00 -> 01
01fbfd58 00 (ok)

(This is actually showing patching the recovery on a Leaf2.)
It's probably either a communication glitch from a wonky cable or a bad MTP driver in Windows.
In the interim, you might look into my AdbSync.
I use that to synchronize books onto my devices.

12-10-2022, 07:42 PM	#2
Renate Onyx-maniac Posts: 4,004 Karma: 18026955 Join Date: Feb 2012 Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6	I noticed that the USB interface descriptor for MTP on my Poke3 is weird. I patch it in my kernel. I have no idea if that will make any difference, I doubt it. Code: C:\>kpatch payload rec.sym onyx.kpc MTP Profile #8: MTP 01fbfd50 mtp_interface_desc 01fbfd50 09 (ok) 01fbfd51 04 (ok) 01fbfd52 00 (ok) 01fbfd53 00 (ok) 01fbfd54 03 (ok) 01fbfd55 ff -> 06 01fbfd56 ff -> 01 01fbfd57 00 -> 01 01fbfd58 00 (ok) (This is actually showing patching the recovery on a Leaf2.) It's probably either a communication glitch from a wonky cable or a bad MTP driver in Windows. In the interim, you might look into my AdbSync. I use that to synchronize books onto my devices.