When running MTP responder it shows ```Waiting interface to be ready: [FAILED]```

[Luis01Felipe]

[dioandtweety]

The first time it is executed, it can be used normally, but after exiting DBI, it will not work again, and the config needs to be copied again.

[Luis01Felipe]

The first time it is executed, it can be used normally, but after exiting DBI, it will not work again, and the config needs to be copied again.

So If I copy and replace the config archive it will work temporarily again? If so, its not awesome but as I rarely install anything it could work well

[dioandtweety]

It won't work.

[dioandtweety]

https://www.youtube.com/watch?v=weq6sB-738g This video was of help to you

[Luis01Felipe]

https://www.youtube.com/watch?v=weq6sB-738g This video was of help to you

Thanks, but I tryed and it still doesn't work, same error in Waiting interface to be ready: [FAILED]

[GRCastro19]

https://www.youtube.com/watch?v=weq6sB-738g This video was of help to you

Thanks, but I tryed and it still doesn't work, same error in Waiting interface to be ready: [FAILED]

you found the solution

[Luis01Felipe]

https://www.youtube.com/watch?v=weq6sB-738g This video was of help to you

Thanks, but I tryed and it still doesn't work, same error in Waiting interface to be ready: [FAILED]

you found the solution

Unfortunately no

[johnkelvinliu]

Setting usb3force=1 in only one of the booting options inside microSDcard/bootloader/hekate_ipl.ini may cause DBI fails to connect. usb3force=1 need to be set in all booting options so as to use usb connection normally+enable USB3.0 again with fss0 package3.

microSDcard/bootloader/hekate_ipl.ini: [CFW-sysMMC] usb3force=1

[CFW-emuMMC] usb3force=1

[stock] usb3force=1

---

you may also try replacing the usb cable, try different usb sockets, restarting the console.