[Tool] Frija - Samsung firmware downloader/checker

[Conan179]

Does anyone happen to know why I haven't been able to download FW for my Fold4 EUX for months?

2023-08-31 16:58:28.2218 | INFO | ---------Info Provided--------- |
2023-08-31 16:58:28.2387 | INFO | Device Model: SM-F936B |
2023-08-31 16:58:28.2387 | INFO | Device CSC: EUX |
2023-08-31 16:58:28.2387 | INFO | Sending provided info to FOTA server to retried latest available firmware |
2023-08-31 16:58:28.4688 | INFO | ---------Retrieved info from FOTA server--------- |
2023-08-31 16:58:28.4688 | INFO | PDA: F936BXXU4DWH5 |
2023-08-31 16:58:28.4688 | INFO | CSC: F936BOXM4DWH7 |
2023-08-31 16:58:28.4688 | INFO | Phone: F936BXXU4DWH7 |
2023-08-31 16:58:28.4688 | INFO | Retrieving firmware from FUS server |
2023-08-31 16:58:35.7103 | ERROR | ---------FUS ERROR--------- |
2023-08-31 16:58:35.7119 | ERROR | FUS response status code: 400 |

 

[iBowToAndroid]

However, I have seen some comments about people soft-bricking their S908B with EUX bit 6 firmware and being stuck in Download mode (due to some errors in their magisk install).

Well then that's a Magisk problem, not Samsung firmware problem. Or, it's an error caused by the user who doesn't know what they're doing

 

[nguyenlucky]

Well then that's a Magisk problem, not Samsung firmware problem. Or, it's an error caused by the user who doesn't know what they're doing

Well I mean in some cases, not being able to download latest EUX firmware sucks...

 

[iBowToAndroid]

Well I mean in some cases, not being able to download latest EUX firmware sucks...

There's really no reason why anyone would need that specific firmware and none other

 

[nguyenlucky]

There's really no reason why anyone would need that specific firmware and none other

because other CSCs for S908B haven't caught up with bootloader bit at that time yet?

 

[iBowToAndroid]

because other CSCs for S908B haven't caught up with bootloader bit at that time yet?

You make no sense. EUX is *behind* all the other standard firmwares, not ahead. EUX is on bit 4, and the rest are on 6. So it's not possible for someone to be stuck and need to flash EUX

 

[ataman76]

Is SamFirm no longer working? What should I enter in CSC in Frija to find the software for me? E.g. for the full CSC number: S901BOXM6CWH5?

 

[adfree]

Oh. Nice.

New Version.

Thank you.

Releases · SlackingVeteran/frija

Contribute to SlackingVeteran/frija development by creating an account on GitHub.

github.com

Best Regards

 

[invmini]

So Frija 2.0 has launched, so please everyone update frija to the latest version as there improvements added including a new UI, performance updates and more

 

[SlackingVeteran]

Hey all,
So looks like Samsung decommissioned their old auth system that Frija v1.x was using which made the app almost useless. I had Frija v2 around as beta for the longest time which was using new auth system and can download firmware just like before. Came out of woodwork today to fix some major issues with v2 and pushed the update.
@invmini has updated OP with latest version info but I will add it here as well for ease:

2.0.23262.4
• New UI
• Improved performance, better error/exception logging
• Independent of Samsung dll libraries
• Improved CRC check
• UI includes more details on Download, CRC validation and Decrypt processes
• New Fluent UI with Light/Dark and System theme support
• New Auto mode to retrieve firmware from FUS server for device connected to PC
• Frija now uses Samsung drivers instead of ADB to pull device info needed to find the firmware in Auto mode.
• Added a dialog box notifying users that firmware has been successfully downloaded.
• Mica effect on Windows 11 for both dark and light theme.
• Added many small UI improvements
• Fixes issue where Frija v1.4.4 can no longer download any firmware

I do not expect this to be as stable as v1.4.4. If you run into any issues please feel free to let me know.

 

[adfree]

First attempt I have unpacked and taken name from Zip for path...

2023-09-19 07:02:22.7572 | ERROR | Exception occured while connecting to Frija database | Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
   at Newtonsoft.Json.JsonTextReader.ParseValue()
   at Newtonsoft.Json.JsonTextReader.Read()
   at Newtonsoft.Json.JsonReader.ReadAndMoveToContent()
   at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
   at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
   at Newtonsoft.Json.JsonSerializer.Deserialize(JsonReader reader, Type objectType)
   at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
   at Frija.Backend.Helper.FrijaAPI.DBGet(String path)
2023-09-19 07:02:22.8522 | ERROR | Unhandled Exception Occured | System.NullReferenceException: Object reference not set to an instance of an object.
   at Frija.App.‬‌‍‪‏‫‫‏‎‬‎‭‏‎‌‏‭‎‍‮‮‮‫‏‮()
   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__139_0(Object state)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

For second attempt i have renamed into easier folder name... then Frija runs

Best Regards

 

[SlackingVeteran]

First attempt I have unpacked and taken name from Zip for path...

2023-09-19 07:02:22.7572 | ERROR | Exception occured while connecting to Frija database | Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
   at Newtonsoft.Json.JsonTextReader.ParseValue()
   at Newtonsoft.Json.JsonTextReader.Read()
   at Newtonsoft.Json.JsonReader.ReadAndMoveToContent()
   at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
   at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
   at Newtonsoft.Json.JsonSerializer.Deserialize(JsonReader reader, Type objectType)
   at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
   at Frija.Backend.Helper.FrijaAPI.DBGet(String path)
2023-09-19 07:02:22.8522 | ERROR | Unhandled Exception Occured | System.NullReferenceException: Object reference not set to an instance of an object.
   at Frija.App.‬‌‍‪‏‫‫‏‎‬‎‭‏‎‌‏‭‎‍‮‮‮‫‏‮()
   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__139_0(Object state)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

For second attempt i have renamed into easier folder name... then Frija runs

Best Regards

That error looks like db server returned a html response instead of json, thanks for the call stack!

 

[yoseth]

Any reason for using that particular net core 3.1 (3.1.21)? 3.1.32 works for me, which is the last supported version with security updates.
And why net core 3.1? Microsoft says the LTS net core 6 is backwards compatible with 3.1, but I tried net core 6, frija didn't work.
As 3.1 is out of support, isn't it better to go more modern version for bugs/security?

 

[SlackingVeteran]

Any reason for using that particular net core 3.1 (3.1.21)? 3.1.32 works for me, which is the last supported version with security updates.
And why net core 3.1? Microsoft says the LTS net core 6 is backwards compatible with 3.1, but I tried net core 6, frija didn't work.
As 3.1 is out of support, isn't it better to go more modern version for bugs/security?

3.1 because thats what was latest at the time I started working on it, January 2020. I want to update it to latest but there are couple things I use that does not support anything newer than 3.1. Will have to find a way to remove those pieces and upgrading isn't as easy as just switching the framework. I haven't done any major fixes or updates to 2.0 since 2021, hence the reason of using 3.1. I only came out of woodwork yesterday to push 2.0 to public release after fixing couple things because 1.4.4 was completely useless to download anything

 

[Tenent Jason]

For some reason the .NET core download popup doesn't bring me to any browser or download files in my environment, maybe due to calling non-existent .NET core element for it to work?

 

[SlackingVeteran]

For some reason the .NET core download popup doesn't bring me to any browser or download files in my environment, maybe due to calling non-existent .NET core element for it to work?

Its been broken for very long time.. Which is why there exist a README.txt file. Ever considered reading it?

 

[Normusmaxamus]

Hey all,
So looks like Samsung decommissioned their old auth system that Frija v1.x was using which made the app almost useless. I had Frija v2 around as beta for the longest time which was using new auth system and can download firmware just like before. Came out of woodwork today to fix some major issues with v2 and pushed the update.
@invmini has updated OP with latest version info but I will add it here as well for ease:

2.0.23262.4
• New UI
• Improved performance, better error/exception logging
• Independent of Samsung dll libraries
• Improved CRC check
• UI includes more details on Download, CRC validation and Decrypt processes
• New Fluent UI with Light/Dark and System theme support
• New Auto mode to retrieve firmware from FUS server for device connected to PC
• Frija now uses Samsung drivers instead of ADB to pull device info needed to find the firmware in Auto mode.
• Added a dialog box notifying users that firmware has been successfully downloaded.
• Mica effect on Windows 11 for both dark and light theme.
• Added many small UI improvements
• Fixes issue where Frija v1.4.4 can no longer download any firmware

I do not expect this to be as stable as v1.4.4. If you run into any issues please feel free to let me know.

Great update, works flawless. Many thanks. S23 Ultra user.

 

[serg9911]

@SlackingVeteran

How does the new authorization system differ from the old one? Where can I read or view the sources? Can you send examples in a private message if this is not public information? Thank you for your answers.

 

[Tenent Jason]

Its been broken for very long time.. Which is why there exist a README.txt file. Ever considered reading it?

I read it after my 3rd attempt to launch frija failed Since I was performing direct upgrade from frija 1.4 , wasn't expecting I'll need to install another runtime for it

 

[Tenent Jason]

Is it still not possible to download Watch firmware using Frija? like SM-R8xxx

@SlackingVeteran

How does the new authorization system differ from the old one? Where can I read or view the sources? Can you send examples in a private message if this is not public information? Thank you for your answers.

I would like to know more about this as well