and the need of enabling usb 3Benchmarks <> real world. You also have to consider the overhead of the MTP protocol and HOS drivers.
and the need of enabling usb 3Benchmarks <> real world. You also have to consider the overhead of the MTP protocol and HOS drivers.
That's correct, but sometimes the MTP Devices drivers can get messed UP, you need to recreate them.Correct me if i'm wrong. But why do you need drivers for dbi? Just connect your console with your pc, open dbi and press x. Don't go into any of the options. Just x.
Pressing X launches MTP Responder.Correct me if i'm wrong. But why do you need drivers for dbi? Just connect your console with your pc, open dbi and press x. Don't go into any of the options. Just x.
By the way may be you was on a status like my main console.I FIXED IT
My fucking OFW was on 4.1.0!!!!
I have no idea how this could have happened. Did I manage to downgrade it at some point?
Everything was working fine before using Haze to transfer cheat files.
Before I realised my OFW was (only now?) on 4.1.0, I had decided to wipe the SD card
(Deleted all partitions on the SD card using Windows Disk Manager > Formatted and overwrote using SD Card Formatter)
Partitioned with Hekate > Created emuMMC > Installed DeepSea
Still no joy
Noticed other issues: Tesla Overlay would not stay enabled, DBI couldn't see USB keys etc.
Tried to install an .nsp from the SD card using DBI and got the error "Cannot parse nca. Old firmware"
Added SigPatches > edited hekate_ipl.ini (kip1patch=nosigchk)
Still nothing
Then I noticed it said FW 4.1.0 at the top of the DBI screen. WHAT?
Updated OFW with Daybreak and everything works again
Thanks to everyone who tried to help
DBI just works. I've tried other title installers and they have all given me issues. DBI has always worked and has all the features I need + more.For me, tinfoil is ugly one as hell and so clumsy, but DBI is a truly *nix way masterpiece with it's clean, lightweight and very useful text GUI, just like an old Adubbz installer was long time ago, in a far galaxy.
Don't Worry, that are some basic concepts:So if you boot into the sysNAND, then that old FW version now affects the updated emuNAND/MMC, CFW?
But if you don't, then it's fine?
Still, I'm pretty sure I have updated the OFW many times over the years.
Very confused.
I should probably stop messing with shit when I'm drunk
With the new v616? I just installed a couple games with it, and didn't have any problems. I used the backend, though. Maybe the MTP responder would be a different story?After updating I now get
Write: USB connection failed
Are you on the new firmware 16.1.0? I'm still on 16.0.3 here. Maybe some incompatibility with the latest firmware. In the meantime, you can still try other installers.Yeah with backend. Even trying an older version has the same result now, no idea
Or try the MTP mode is neat and needs no other application on PCAre you on the new firmware 16.1.0? I'm still on 16.0.3 here. Maybe some incompatibility with the latest firmware. In the meantime, you can still try other installers.