-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] /api/binary
endpoint returns the same response body regardless of request params
#6
Comments
I just tried to display raw data from Kies's servers, and looks like it got the device firmware code correctly as expected. And when I look at the https://doc.samsungmobile.com/SM-G986U1/XAA/doc.html I can clearly see the release date. But I don't know the exact reason why it returns that response to you. I will research more about this problem and let you know if it is related to Kies / Samsung's servers itself or SamFetch. |
Hmm that is strange. I just tried again with some different firmwares and got the same response. I even tried using Postman to send the request since I was using the openapi web interface before but that didn't change anything. Let me know if there's anything I need to try or test. Thanks for your help! |
Probably this is the reason: |
Yes, I think you're right. I just tested another tool on Windows 10 (SamFirm_Reborn) and it did the same thing so it seems like it's a change on Samsung's end. |
@ysfchn if you find any way around this, let me know. |
Are you affiliated with the site SamFirm ? |
Not sure if I'm missing something but it seems like the
/api/binary
endpoint returns the same response body regardless of the params sent with the request.Request:
/api/binary?region=XAA&model=SM-G986U1&firmware=G986U1UEU1DUB7%2FG986U1OYM1DUB7%2FG986U1UEU1DUB7%2FG986U1UEU1DUB7
Response:
The
20210416
date of the firmware is what tipped me off because I'm trying to download a firmware from 2-28. So I also tried a couple of other firmwares (all pulled from the/api/list
endpoint) and they all returned the same response as above. I'm guessing it's just returning info for the latest firmware every time but I'm not sure.The text was updated successfully, but these errors were encountered: