search

zacharee / SamloaderKotlin

MIT License
981 stars 109 forks source link

"Bad return status: 400" for SM-S908B region EUX #111

Closed divinity76 closed 1 year ago

divinity76 commented 1 year ago

trying to download SM-S908B with EUX results in

Bad return status: 400

SM-S908B with EUX definitely exist, here is a screenshot as proof:

and here is a screenshot of trying to download it with Bifrost: image

interestingly, same happens with EUY but /not/ with BTE (BTE works fine).

Xpl0itR commented 1 year ago

same

divinity76 commented 1 year ago

@Xpl0itR until this is resolved, i wrote a region scanner to find alternative regions at https://github.com/jesec/SamFirm.NET/issues/3

$ time php test2.php SM-F916N
total urls to check per model string: 509
total urls to check: 2545
Checking model string 1/5: SM-F916N
http://fota-cloud-dn.ospserver.net/firmware/KTC/SM-F916N/version.xml   : 200
http://fota-cloud-dn.ospserver.net/firmware/LUC/SM-F916N/version.xml   : 200
http://fota-cloud-dn.ospserver.net/firmware/SKC/SM-F916N/version.xml   : 200
http://fota-cloud-dn.ospserver.net/firmware/KOO/SM-F916N/version.xml   : 200
(...)
MichaelDavidGK commented 1 year ago

@Xpl0itR until this is resolved, i wrote a region scanner to find alternative regions at jesec/SamFirm.NET#3

@divinity76 why do you check for models by removing last sign from model string? (SM-S916N exists; SM-S916, SM-S91, SM-S9, SM-S don't exist) it's not like device like this will exist in most cases also even if it exists it's a different model, so there is no point to it

divinity76 commented 1 year ago

@MichaelDavidGK because my phone's model code is SM-S908BZWGEUB , but the update server did not use my full model code, and I wasn't sure exactly what model code the update servers used, so after an exhaustive search,

hans@cac3:~$ time php test2.php SM-S908BZWGEUB
total urls to check per model string: 509
total urls to check: 5599
Checking model string 1/11: SM-S908BZWGEUB
Checking model string 2/11: SM-S908BZWGEU
Checking model string 3/11: SM-S908BZWGE
Checking model string 4/11: SM-S908BZWG
Checking model string 5/11: SM-S908BZW
Checking model string 6/11: SM-S908BZ
Checking model string 7/11: SM-S908B
http://fota-cloud-dn.ospserver.net/firmware/AFG/SM-S908B/version.xml   : 200
http://fota-cloud-dn.ospserver.net/firmware/MOB/SM-S908B/version.xml   : 200
http://fota-cloud-dn.ospserver.net/firmware/VIP/SM-S908B/version.xml   : 200
http://fota-cloud-dn.ospserver.net/firmware/O2C/SM-S908B/version.xml   : 200
(...)

also even if it exists it's a different model, so there is no point to it

I certainly hope not (and the SM-S908B firmware was fully compatible with my SM-S908BZWGEUB model.)

MichaelDavidGK commented 1 year ago

This is model code.

It's different from model which is on main section of "About phone" in settings (sometimes they have /DS which you can ignore as it only informs that this model has dual SIM support).

You can also find it everywhere on the Internet (also Samsung site and forums)

It is also mentioned in separate tab "Software information" in "About phone" under "SE for Android status" and "Service provider software version".

As well as in Version Menu called by *#1234# (may also contain /DS).

On Thu, 2 Nov 2023, 09:59 divinity76, @.***> wrote:

@MichaelDavidGK https://github.com/MichaelDavidGK because my phone's model code is SM-S908BZWGEUB , but the update server did not use my full model code, and I wasn't sure exactly what model code the update servers used, so after an exhaustive search,

@.***:~$ time php test2.php SM-S908BZWGEUB total urls to check per model string: 509 total urls to check: 5599 Checking model string 1/11: SM-S908BZWGEUB Checking model string 2/11: SM-S908BZWGEU Checking model string 3/11: SM-S908BZWGE Checking model string 4/11: SM-S908BZWG Checking model string 5/11: SM-S908BZW Checking model string 6/11: SM-S908BZ Checking model string 7/11: SM-S908Bhttp://fota-cloud-dn.ospserver.net/firmware/AFG/SM-S908B/version.xml : 200http://fota-cloud-dn.ospserver.net/firmware/MOB/SM-S908B/version.xml : 200http://fota-cloud-dn.ospserver.net/firmware/VIP/SM-S908B/version.xml : 200http://fota-cloud-dn.ospserver.net/firmware/O2C/SM-S908B/version.xml : 200 (...)

also even if it exists it's a different model, so there is no point to it

I certainly hope not (and the SM-S908B firmware was fully compatible with my SM-S908BZWGEUB model.)

— Reply to this email directly, view it on GitHub https://github.com/zacharee/SamloaderKotlin/issues/111#issuecomment-1790414839, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJJT3E5XLPG7QBJO6BBYB3TYCNVGXAVCNFSM6AAAAAA6LGRJGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJQGQYTIOBTHE . You are receiving this because you were mentioned.Message ID: @.***>

zacharee commented 1 year ago

There isn't really much I can do if Samsung isn't serving the firmware for a certain CSC directly. As suggested above, you'll have to try a different CSC that contains yours.

divinity76 commented 1 year ago

@zacharee problem is, the Samsung phone itself can download SM-S908B region EUX, but not Bifrost - The phone is doing /something/ differently, and the server is reacting to it

zacharee commented 1 year ago

OTA packages use a different server and require a pretty complex registration process that's unique per-device.

divinity76 commented 1 year ago

@zacharee oh ok. close this issue then?

Btw would be nice if Bifrost itself could get a region scanner (I don't do Kotlin myself, but I wrote one in PHP to get around the SM-S908B+EUX issue - would have saved me the trouble if Bifrost had one, and not everyone has the motivation and know-how to get around it)

zacharee commented 1 year ago

Can you request that in a new issue so I can track it better?

MK73DS commented 2 months ago

I experience the same problem with Bifrost 1.19.3 when trying to download S928BXXS3AXI1/S928BOXM3AXI1/S928BXXS3AXI1/S928BXXS3AXI1 for SM-S928B and EUX CSC. The update definitely exists, I got an OTA notification for it and it is present in samfw https://samfw.com/firmware/SM-S928B/EUX/S928BXXS3AXI1 image