search

KunoichiZ / lumaupdate

Updater for Luma3DS
https://gbatemp.net/threads/release-luma-updater.471739/
Do What The F*ck You Want To Public License
431 stars 47 forks source link

Continuous MD5 check error #97

Closed kyoukq closed 2 years ago

kyoukq commented 2 years ago

What model of system are you using?

What is your current Luma3DS version?

If you are running an hourly version of Luma3DS, please manually update to a stable version as I will no longer deal with people who are using hourlies.

What version of Luma Updater are you using?

How are you running Luma Updater?

What problems are you experiencing?

Whenever I try to update luma I get an MD5 mismatch on the 2nd check consistently. The download also happens instantly on subsequent attempts, so it would seem it doesn't delete the corrupted files when the check fails and just checks it again without redownloading. I tried restarting the 3ds and the application multiple times. I could not find where the downloads are stored to try manually deleting it.

EDIT: It seems others are having the same issue, so I'm assuming the issue has something to do with the server check itself rather than a corrupted download.

What is the exact error code you are receiving?

No error code.

Steps to reproduce

  1. Try to update with a corrupted file already in the directory
ToastyKip commented 2 years ago

I'm also having this issue. The device I'm using is an Old 3DS XL, and the updater menu says my Luma installation is on 10.2. I'm lacking an SD card reader, so I thought to update to 10.2.1 this way, but I'm stuck for now because of this unfortunately.

futurelucas4502 commented 2 years ago

Hi there same issue here I've included a few screenshots below to hopefully show the issue I'm having as well as other information which may or may not be relevant: 20211224_024644630.jpg 20211224_025220492.jpg 20211224_024704108.jpg

RoXYTheNeko commented 2 years ago

Same problem with 3DS XL on Sys 11.14.0-46E and Luma Updater 2.4

futurelucas4502 commented 2 years ago

@RoXYTheNeko your on version 2.4 so you have a different problem you have to manually update lumaupdater to version 2.6 see #53

If it still doesn't work then u have the same problem as us

dylanr2003 commented 2 years ago

im having the same issue. made a github for this, even. Would love to know if anyone finds the fix

jasonridesabike commented 2 years ago

Same issue on a new 3ds.

image

image

dinckelman commented 2 years ago

Can replicate this issue with the exact same environment as the original poster

TehH4rRy commented 2 years ago

Can confirm exact same issue for me too.

ToastedEggplant commented 2 years ago

Same here

dehydratedkidney commented 2 years ago

having this same issue, please lmk if anything changes or fixes thank you :)

b000rg commented 2 years ago

Issue is present for me as well. I'm wanting to update my system version but I'm hesitant to until I'm sure I'm running the latest version of Luma.

update: I was able to get Luma3DS updated to v10.2.1 using Universal Updater, just FYI for those looking to get your CFW updated.

project-shasta commented 2 years ago

Updating Luma3DS via Universal Updater worked fine, am on Version 10.2.1 now. The Updater is also happy now.

speed47 commented 2 years ago

FWIW, FBI's update system also fails the MD5 check, so something changed somewhere (github ? location of the MD5 reference file that we're trying to check the downloaded payload against ?)

EDIT: The Integrity check #2 is a check against the ETag of the HTTP response:

$ curl -sLI --http1.1 https://github.com/LumaTeam/Luma3DS/releases/download/v10.2.1/Luma3DSv10.2.1.zip  |& grep ETag
ETag: "0x8D9BA0160D81308"
$

My guess would be that the ETag format has changed.

EDIT2: Oh, well, got it, we had one chance out of 16 to have this bug: the ETag format doesn't print the leftmost zeroes, i.e. if it was 0x08D9BA0160D81308 then the algorithm would have parsed it correctly. @KunoichiZ if I proposed a patch, would you merge it?

EDIT3: Okay, it's uglier than this, the ETag format does have changed, and the MD5 can no longer be inferred from it. The bad news it that it makes LumaUpdater actually read uninitialized memory, because the ETag is now shorted than what is expected. The good news is that the MD5 is now available through another HTTP header (Content-MD5) that is bas64 encoded. In any case, my PR proposition still stands.

LemonzDEV commented 2 years ago

Hi, same problem. How can i solve it ? Do you have a .cia file with this fix?

Thanks

KunoichiZ commented 2 years ago

Why are people still using this? 3ds.hacks.guide has a better method to updating Luma now. LumaUpdater isn't even a part of the guide anymore. Closing this as all developement has stopped on this, in case it wasn't obvious.