search

CTCaer / hekate

hekate - A GUI based Nintendo Switch Bootloader
GNU General Public License v2.0
6.53k stars 563 forks source link

Cannot mount BOOT0/BOOT1 via the Hekate USB Tools #960

Closed sthetix closed 4 months ago

sthetix commented 4 months ago

I am using the Hekate version 6.1.1 and when trying to mount the BOOT0 and BOOT1 via the USB Tools , this error comes up.

image

How to fix this issue?

CTCaer commented 4 months ago

Your OS is trying to access more than it should. It's not a fatal error from hekate side (reason why I have the text as warm), so it falls on the OS. If that happens the moment you mount it, just use a proper OS. (Win 7, win 10, Linux and whatever random mac os I use to test UMS do not do that.) If you wrote some random MBR or GPT in boot0/1 for whatever reason then remove it or fix it to the proper size.

I'll leave it open, in case you have more info to add about what eMMC you are trying to mount and OS.

sthetix commented 4 months ago

You were right.I tested it on Windows 10, and it did not display the error message.

On Fri, 10 May 2024 at 18:25, CTCaer @.***> wrote:

Your OS is trying to access more than it should. It's not a fatal error from hekate side (reason why I have the text as warm), so it falls on the OS. If that happens the moment you mount it, just use a proper OS. (Win 7, win 10, Linux and whatever random mac os I use to test UMS do not do that.) If you wrote some random MBR or GPT in boot0/1 for whatever reason then remove it or fix it to the proper size.

I'll leave it open, in case you have more info to add about what eMMC you are trying to mount and OS.

— Reply to this email directly, view it on GitHub https://github.com/CTCaer/hekate/issues/960#issuecomment-2104440313, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFJ23D3FCBC4KC7SQQ3EMD3ZBSVC5AVCNFSM6AAAAABHMY6HBCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBUGQ2DAMZRGM . You are receiving this because you authored the thread.Message ID: @.***>

CTCaer commented 4 months ago

Since that's not normal to happen, you should check if you have any mass storage or usb driver that replaced official ones. Or any hidden app that parses drivers. Because it can be the automounter's problem.

If not then that OS is garbage because when it is actually informed about storage size, it must never try to read more. That info is sent during the inquiry command. You can't mount a driver without it's size populated or not sent or requested. So, there's no point to try and read/write out of bounds and also it can hang/halt hw that does not check if it's above. For example if storage on a ums device is eMMC or SD and you try to read out of bounds, it tears down the whole thing. You need to power cycle it after that. It's not a hot recoverable error