Database Develop

[Q] Restore original firmware (DDJG4)

Can any one please help me as to how to restore original version JG4 from froyo XXJP2?

any 1 can help me...

Let me know what you need, there already exist the firmware[DDJG4) on samfirmware.com to download, use the old odin and 512 pit and flash the the firmware, I have tried it and it works.
-Pramod

sog-1986 said:
Can any one please help me as to how to restore original version JG4 from froyo XXJP2?
Click to expand...
Click to collapse
You will need the firmware file to flash with Odin. Use this link to grab the firmware file: https://www.wuala.com/Samsung Galax...riginal Firmwares/Asia/July/?key=AfzUZSU4SpKU
NOTE: This link is provided by "darkstriker" the author of this brilliant post: http://forum.xda-developers.com/showthread.php?t=723596
You can also use that as a reference in case you get stuck somewhere.
Coming back to the point, download Odin v1.3 and the PIT file (512 specifically) from this link: https://www.wuala.com/Samsung Galax...din/Odin & Bootloader(.PIT)/?key=AfzUZSU4SpKU
Follow these simple steps: (DO NOT CONNECT YOUR PHONE JUST YET. IF IT IS ALREADY CONNECTED, REMOVE THE USB CABLE FIRST)
1. Make sure Kies is not running. Ensure it is also not running in the notification area.
2. Start Odin v1.3 and make sure these options are TICKED / CHECKED
a. Re-Partition
b. Auto Reboot
c. F. Reset Time
3. Click on the PIT button and select the PIT file downloaded earlier (512 specifically)
4. Click the PDA button and select the file "ADD_ODD"
NOTE: This firmware archive does not contain any other files needed by Odin.
5. Switch off your phone and start into "DOWNLOAD MODE" using the key combination: VOLUME DOWN + HOME + POWER BUTTON.
6. Now connect the phone to the computer and wait for Odin to pick up a COM port and show "available" status.
7. Click on the "Start" button and wait for the process to complete and the phone to subsequently reboot. DO NOT INTERRUPT THIS PROCESS BY ANY MEANS.
If all done well, you will be back to JG4 in no time.....
Cheers.....

Hey there,
Any luck getting it running properly??
Cheers....

The easiest way would be to update via kies, I tried to get the update notification in the Kies, not updated though, follow these steps to get the update notification in kies.
Connect the phone to kies, and then run regedit.exe , change the regedit keys
[HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB\X]
"SoftwareRevision"="I9000DDJF3/I9000ODDJF3/I9000DDJF3/I9000DDJF3"
"ProductCode"="GT-I9000HKAINU"
"HIDSWVER"="I9000DDJF3/I9000ODDJF3/I9000DDJF3/I9000DDJF3"
"DEVCONINFO"=""
X = Device Number
and run the upgrade frimware in kies and you will see JG4 to be available to be updated through kies!!
-Pramod

pramods said:
The easiest way would be to update via kies, I tried to get the update notification in the Kies, not updated though, follow these steps to get the update notification in kies.
Connect the phone to kies, and then run regedit.exe , change the regedit keys
[HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB\X]
"SoftwareRevision"="I9000DDJF3/I9000ODDJF3/I9000DDJF3/I9000DDJF3"
"ProductCode"="GT-I9000HKAINU"
"HIDSWVER"="I9000DDJF3/I9000ODDJF3/I9000DDJF3/I9000DDJF3"
"DEVCONINFO"=""
X = Device Number
and run the upgrade frimware in kies and you will see JG4 to be available to be updated through kies!!
-Pramod
Click to expand...
Click to collapse
+1
I managed to do this for myself. =)

pramods said:
The easiest way would be to update via kies, I tried to get the update notification in the Kies, not updated though, follow these steps to get the update notification in kies.
Connect the phone to kies, and then run regedit.exe , change the regedit keys
[HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB\X]
"SoftwareRevision"="I9000DDJF3/I9000ODDJF3/I9000DDJF3/I9000DDJF3"
"ProductCode"="GT-I9000HKAINU"
"HIDSWVER"="I9000DDJF3/I9000ODDJF3/I9000DDJF3/I9000DDJF3"
"DEVCONINFO"=""
X = Device Number
and run the upgrade frimware in kies and you will see JG4 to be available to be updated through kies!!
-Pramod
Click to expand...
Click to collapse
What were the modifications in the registry. I know modifying the productcode can make a difference with respect to the available firmwares but does changing the SoftwareRevision and HIDSWVER enables us to downgrade the firmware?
On a side not I wanted to revert from JPC to JM1 (through kies with XUE productcode hack). So I first flashed JF3 trhough odin. Now it seems that there is some swisscom stuff left. For instance the start page of my internet browser is now in a german language swisscom site. Any1 can give me directions how to get back to my original stock configuration? Which is dutch OS language and dutch swype JM1.

Orcie said:
What were the modifications in the registry. I know modifying the productcode can make a difference with respect to the available firmwares but does changing the SoftwareRevision and HIDSWVER enables us to downgrade the firmware?
On a side not I wanted to revert from JPC to JM1 (through kies with XUE productcode hack). So I first flashed JF3 trhough odin. Now it seems that there is some swisscom stuff left. For instance the start page of my internet browser is now in a german language swisscom site. Any1 can give me directions how to get back to my original stock configuration? Which is dutch OS language and dutch swype JM1.
Click to expand...
Click to collapse
That i suspect is because the upgrade was done through Kies. Odin on the other hand gives you the option to re-partition. At least that is what I think is causing this. Have you tried the "Factory data reset" option under Settings - Privacy? Or perhaps getting into recovery mode and then doing a factory reset? That might do the trick for you.
Cheers....

Thanks a lot, it worked quite smoothly

sog-1986 said:
Thanks a lot, it worked quite smoothly
Click to expand...
Click to collapse
The market works properly for you? You can download apps?

I have this same problem.
Was uprading firmware to JG4 via kies then boom Kies went error - send report to MS crap.
Now when I try to odin flash i get
error cache/sec_csc.zip
tried to go back to JF4 tried lots of JG4 firmwares but i still get the same error on reboot.

Yes the market works properly for me, i can download stuff

Devconinfo
what exactly do i type in the DEVCONINFO section ?
many thanks

Hi,
I didn't want to open a new topic so I'll just reply here.
I'm about to flash a custom ROM on my GalaxyS, but I'd like to have an option to revert to original ROM if needed.
I understand that I need that original ROM in order to revert/reflash it, but I'm having trouble finding it.
This is my current, original ROM:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you tell me where do I find it ?
Thank you

Update nougat EVA-L09C25B136

Hello, I have an EVA-L09C25B136 that's on EMUI 4.1 and Android 6.0. When I check for updates there are not any updates.
The phone is from a latin american carrier "Claro DR" and I haven't done anything to the phone, so it is pure stock. Is there any way I can update this phone to the latest available version for this model?
I have searched the forums but the guides are not directly related to my exact build so I want to be sure before I go and damage it.
Thank you.

FirmwareFinder. It can download every available build from Huaweis server..
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder&hl=en

How do I know which firmware is compatible with my device?
When I get the list and check every one of the options available, none of those say that they are for my build number.

Don't know what you did.
Open FirmwareFinder, normally it'll recognize your build. In your case EVA-L09C25. If not set the model manually.
Then tap the refresh button and the app will show all builds.
Tap on the first one (EVA-L09C25B320) and ckeck firmware access.
A pop-up will appear with following text: "Firmware approved for installation Models ... . So, there's your latest build (with Nougat, EMUI 5).
For further information about FirmwareFinder and how to use it please check the forum or ask google.

Here is what I did:
In firmware finder indeed it recognized my phone as EVA-L09C25.
1) Click the refresh button.
2) First two firmwares said not approved for installation.
3) 3rd on the list: Firmware aproved for installation Models for Installation: VIE-L09C25B320. Shouldn't be EVA-L09?
4) Tried downloading with firmware finder proxy, download stops at 74%, and closes updater.
5) Tried downloading the zip file and extracting the UPDATE.APP and copied it to the root of the SD Card in the dload folder.
6) Started the update on reboot it says that the firmware is not compatible.
What else should I try?

Well, I've seen what you mean. Very strange. I can only assume that it's caused by C25. It's not even listed in the cust list here https://www.huaweiblog.de/firmware-update-was-bedeutet-cust-emui-und-co/ (german).
Sorry, that I don't know more.

How to flash Mi 5X with "fake" ROM?

Hi, I'm new in here..
wanna ask some question.
last year, my friend bought Mi 5X from Online shop (obviously, not an official store from that online shop)
when he receive the phone and trying to check for miui updates, the pop-up message window keep showing when we tried to check the update, its said "connect to WLAN", even we already connected to the wifi network.
if i really correct, the miui version still miui 8 but with 5 digit number of the version.
Then, we already tried to unlock the phone in the same day. And the result we cannot unlock the phone.
is this possible change to another ROM (probably using from xiaomi.eu site) ?
Thanks!

So..R U Chinese?
Your English is bad..
According to your question, your Mi 5X cannot update to the latest MIUI version..And cannot unlock bootloader.
And there is another way to update MIUI, you can first download the latest MIUI full-size zip which fits your phone on miui.com (DO NIT EXTRACT),and launch 'System Update' app, press the three points at the edge, then choose 'choose zip from SD card
' and then choose the downloaded MIUI full-size zip ,then you can update offline.
如果

I need "emmc_appsboot.mbn" file from a working MD E2 devices.
Any body can help me pls. My mi5x device is now on black secreen. Not openning..
it became after load orijinal rom onto oxygen boot.
Any body can help me pls
I need "emmc_appsboot.mbn" file from a working MD E2 devices.

Samsung Galaxy SM-N950F/DS stucked in boot loop, possibly wrong firmware installed

Hello dears,
One of my clients called me related to a problem with their Note 8 device. At first it sounded like a typically bricked device problem but after taking a closer look on some of the screenshots they've sent me with the device it really got me confused as to what had happened to the device. I don't have the device with me at the moment so the screenshots is all I have until the client arrives but I'm posting this thread in hopes to find out if there is any possibility of fixing the device so that I put the client on the road for nothing.
From what I understood the client tried rooting the phone and it got into a boot loop afterwards (I don't know the exact process of rooting that they've tried, that's all they said to me), they also said that they've been with the device to someone else afterwards and they've tried a few times to resoft the device with some ROM variants on the phone but they've "failed"to fix the device in the end and my client got bored of waiting for them to keep trying.
I thought the phone may be soft bricked and I asked them for some screenshots with the device so that I can see what firmware they were running and also a screenshot with the phone model details on the back and so they sent the screenshots to me and a few extra more.
Now, the first thing that I see is that the phone strangely runs or has ran a DIFFERENT firmware version for a DIFFERENT MODEL. If you look at the screenshots posted bellow, you will see that the phone is a SM-N950F/DS but runs an N9500 Firmware/ROM (Chinese I guess). I am confused, I haven't see that before. Is it possible that the guys working at the phone before managed to install a wrong firmware and hard brick the phone even more?
I see that the ROM that is currently shown on the phone is indeed an official/stock one from Samsung so I also wonder if that's how the phone actually came out on the shelf since the client told me that they've bought it from around that region. But still, the rom is clearly made for another model from the one written on the back of the phone so I don't really know what to say I haven't met with this issue before.
Also, judging by the screenshots offered what would be the steps you guys would make to fix the phone (if possible) and what exact rom version should I flash via Odin if anyone has an idea.
Should I flash the stock N950F/DS firmware or the N9500 CHC/TWN stock firmware? What would be the steps to bring this device back to life ? I appreciate your patience and I hope that the phone can still be revived.
Here are the screenshots (I apologise for the quality but this is what the client has sent at the moment).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

He has flashed the wrong filmware/rom.
The fact it can boot into recovery means it is not hard bricked. You should be able to just flash the N950F DS filmware to fix it, which you can get from Sammobile or Updato.

stonedpsycho said:
He has flashed the wrong filmware/rom.
The fact it can boot into recovery means it is not hard bricked. You should be able to just flash the N950F DS filmware to fix it, which you can get from Sammobile or Updato.
Click to expand...
Click to collapse
Excuse for asking this but I have two questions:
Could you tell me wich exact version of the firmware should I go for (as there are many versions) and also will the bootloader accept the firmware by flashing it via Odin or are there any chances it may give some dm-verifcation failed error ?
Thank you very much.

BrainwashedUser said:
Excuse for asking this but I have two questions:
Could you tell me wich exact version of the firmware should I go for (as there are many versions) and also will the bootloader accept the firmware by flashing it via Odin or are there any chances it may give some dm-verifcation failed error ?
Thank you very much.
Click to expand...
Click to collapse
Just use the latest version of filmware. It is still rootable if the guy wants to try again.
Just find out what country and network he is on and you can use the advanced search to find the filmware.
I am no expert, so I am unable to answer that question but it should be fine...

stonedpsycho said:
Just use the latest version of filmware. It is still rootable if the guy wants to try again.
Just find out what country and network he is on and you can use the advanced search to find the filmware.
I am no expert, so I am unable to answer that question but it should be fine...
Click to expand...
Click to collapse
Thank you, when my client arrives I will try to flash the N950FXXS5DSB4 (since we're in Romania here).
I take it the DS = Dual Sim and the B4 means that the ROM was created for the version 4 of the bootloader on wich the phone currently runs on. The rom is carrier free and the version is Android 9 (Pie), March 11, 2019).
I hope the bootloader won't reject it. I will come back with an update afterwards.

BrainwashedUser said:
Thank you, when my client arrives I will try to flash the N950FXXS5DSB4 (since we're in Romania here).
I take it the DS = Dual Sim and the B4 means that the ROM was created for the version 4 of the bootloader on wich the phone currently runs on. The rom is carrier free and the version is Android 9 (Pie), March 11, 2019).
I hope the bootloader won't reject it. I will come back with an update afterwards.
Click to expand...
Click to collapse
The DS doesn't refer to Dual Sim, it's just part of Samsung's versioning scheme. The single and dual SIM variants of the Note 8 use the same firmware.
As you said the device is carrier free, then the "ROM" CSC is the one you want to go for, and the latest version of that (DSE5) is available via SamFirm for the "INS" CSC - although you would be getting the "INS" version, it's a standard one that contains multiple CSCs within it, including "ROM".

StevePritchard said:
The DS doesn't refer to Dual Sim, it's just part of Samsung's versioning scheme. The single and dual SIM variants of the Note 8 use the same firmware.
As you said the device is carrier free, then the "ROM" CSC is the one you want to go for, and the latest version of that (DSE5) is available via SamFirm for the "INS" CSC - although you would be getting the "INS" version, it's a standard one that contains multiple CSCs within it, including "ROM".
Click to expand...
Click to collapse
I have the device, downloaded the DSE5 ROM, connected the phone and it when I click start it instantly fails.
On the phone I get a while line instead of an error on why it failed.
Anyone has any idea why is that ?

BrainwashedUser said:
I have the device, downloaded the DSE5 ROM, connected the phone and it when I click start it instantly fails.
On the phone I get a while line instead of an error on why it failed.
Anyone has any idea why is that ?
Click to expand...
Click to collapse
I Get Re-Partition Error now. I even tried with the PIT and RE-PARTITION checked as well and it gives the same error.

BrainwashedUser said:
I Get Re-Partition Error now. I even tried with the PIT and RE-PARTITION checked as well and it gives the same error.
Click to expand...
Click to collapse
I managed to flash the same ROM that it's written on the recovery menu via Odin but after passing (takes 5 minutes) and gives no error it boots into recovery. Same thing if I extract the PIT file from CSC and check the re-partition. It passes but it boots me into the recovery menu after restart. If I restart normally afterwards it still loops to the logo and restarts. It shows the logo, vibrates twice, reboots and keeps doing the same thing. Flashing with the latest ROM for SM-N950F/DS (N950FXXU6DSE5) will give the error Re-partition failed in Odin.
Any ideas ?

BrainwashedUser said:
I managed to flash the same ROM that it's written on the recovery menu via Odin but after passing (takes 5 minutes) and gives no error it boots into recovery. Same thing if I extract the PIT file from CSC and check the re-partition. It passes but it boots me into the recovery menu after restart. If I restart normally afterwards it still loops to the logo and restarts. It shows the logo, vibrates twice, reboots and keeps doing the same thing. Flashing with the latest ROM for SM-N950F/DS (N950FXXU6DSE5) will give the error Re-partition failed in Odin.
Any ideas ?
Click to expand...
Click to collapse
I am unsure with all the errors but try using Odin 13.3.1.

Similar Issue
Hi, almost similar issue here.
I just bought a second-hand Note 8, but there are discrepancy between the variants. The seller said that he got the phone in Singapore, and the back sticker and etching said it is SM-N950FD. On the Settings > About Phone, it said the model number is SM-N950F/DS/DS. However, the Recovery said that this phone is greatlteks, running N950NKSU3BRA1 and the download mode is in Korean and the Product Name is SM-N950N running custom binary, with FRP Lock and OEM Lock = OFF. Carrier ID is LUC.
I need to return this values to stock so that I can upgrade to Pie. Please advise on which stock ROM should I install in this phone.

awetsm said:
Hi, almost similar issue here.
I just bought a second-hand Note 8, but there are discrepancy between the variants. The seller said that he got the phone in Singapore, and the back sticker and etching said it is SM-N950FD. On the Settings > About Phone, it said the model number is SM-N950F/DS/DS. However, the Recovery said that this phone is greatlteks, running N950NKSU3BRA1 and the download mode is in Korean and the Product Name is SM-N950N running custom binary, with FRP Lock and OEM Lock = OFF. Carrier ID is LUC.
I need to return this values to stock so that I can upgrade to Pie. Please advise on which stock ROM should I install in this phone.
Click to expand...
Click to collapse
Looks like you have a refurbished note 8 korean model N950N with replaced body and faked software N950F .
The motherboard is Korean so don't try flash N950F software on it will fail in odin it won't work.
Only N950N firmware will work only on your phone and you can flash android 9 pie but be careful if you flash N950N firmware you will lose N950F software and also dual sim will no longer will work too because possibly your dual sim also converted by software not Hardware. Because there's no N950N Exists with dual sim model.

Samsung Galaxy S10 Software update

I can't update my Android OS to 11 it's still on Android 10. When I tried going to Phone Settings > Software updates> Download and install> Your software is up to date. Is there a way to get this Android 11 or 12 update to my device Baseband Version. G973USQS4ETK2

Looks like you have a USA phone, I assume on a USA network? Looks like USCellular?
What carrier and country are you in? I see there are updates for your firmware as recent as this month... that would be Android 11. 12 is not on US phones yet.

Its under T-mobile US I guess I was able to look the information up and I saw the baseband version is under T-mobile. Is there a way to patch Android 11 or even 12 to this cause I also tried rooting this but I'm having a hard time downloading stuffs.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It stopped Updating since this last patch.

First off, if you want to root, I think you will be able to - your BL version is 4 (5th from end number in the build version or the baseband version). It's not free to root this way, but I believe you can. However, if you do that, then I don't think you can update to any newer version of stock ROM, because you cannot update the bootloader (which is part of the other releases). Also not, rooting may wipe your phone too.
As for the other question, show me your full software info page, so I can see the CSC codes and other things. I want to make sure they make sense.
My guess is that because you have a U phone (as opposed to U1 with a multi-CSC setup) that you would not be able to patch/update the phone. This is because the U is typically locked to the carrier updates, and if it's looking for USCellular, that would explain why your TMo carrier can't update it. You could reflash to a U1 ROM using ODIN, and this should allow updating in the future, but it will likely require a wipe (you could try an upgrade flash, but I don't recall if this is possible from U to U1). This will also update the bootloader which means you can't root today, but you would be up to date.
So, decide how you want to go first... because you can't have both (root + updated... unless you do custom roms, which I am not versed in, but you are liklely going to give up some things with custom roms, from the superficial reading I've done there)

I think it would be best to move from U to U1 to still have updates.

Dharhil said:
I think it would be best to move from U to U1 to still have updates. View attachment 5519565
Click to expand...
Click to collapse
So my phone looked much like yours does, xaa/xaa/tmb. Couldn't get updates either. I used patched Odin and flashed latest xaa version, and used 'home' csc, resulting in keeping user data.
I wanted to keep everything much as it was because using Mint Siim, I'm able to get voip / vowifi, but it also does 'carrier aggregation', so I get a little LTE+ icon indicating such, signal is very good also. Doing the update kept everything working as it was.
I don't plan on rooting so the bump in BL version didn't care about.
cheers

I agree with @AsItLies - your phone looks like it's already on a multi-CSC ROM (XAA). Not sure why it's not updating, but since you're already there, you should be able to do the Odin update as an upgrade, using the "home" CSC and it should update the ROM at the very least. Ideally, your phone should show TMB/TMB/TMB, because the first one is the current SIM, the second is the carrier, and the third is the original CSC (which you can't change anyway)... for example, mine shows TFN/TFN/SPR (Tracfone aka Total Wireless, in my case). My ROM is a U1, though... maybe that's why both of yours is not changing the XAA properly?
I'd say, give the U1 a shot, with the HOME CSC and upgrade mode in ODIN and see if that works. But before you do that, BACKUP EVERYTHING YOU NEED, just in case.
I would recommend using Frija to download the ROM (much faster than web downloads)... but the rest of the info is available on various threads here on XDA. I would recommend reading through the guide posts here THOROUGHLY before doing anything: https://forum.xda-developers.com/t/g973u-and-g973u1-firmware-links-here.3905852/
If you still have questions, you can ask there or here...
@AsItLies are you on a U or U1 ROM? Just curious...

@schwinn8 it's funny you should ask that, because when I first got my phone it said 973U. Now, after the update I described above, it says 973U1.
I'm guessing that indication isn't used to determine if an update is available, could be wrong, but I *think* an update just depends on if it was originally U or U1, and you're running the original firmware. So anything that is multi csc but was originally a U, I don't think that will OTA update (only manually with patched Odin).
Anyway, there are very few updates left, so not too worried about it, doing it manually is quite easy. Pretty sure A12 will be the last we'll see.
cheers

Agreed, not a big deal regarding updates now... but was just curious... I'm surprised to see you're still showing XAA/XAA... I figured those would change.
I had issues with one of my wife's phones (we bought two S10+ phones at the same time)... hers refused to switch to TFN for some reason. Sadly, she NEEDED it because she used the old-fashioned voicemail and app. I could see the app on my phone (where the CSC change worked fine) so I knew what I needed, but couldn't get it to happen. I ended up returning that phone (Ebay) and getting one that was already setup for TFN... and that one is fine. Funny thing, I think it was an XAA as well, but I don't remember now).
I've also seen a thread here that says CSC won't change anymore for users. But even that post has very mixed info... as my experience confirmed. So weird.
/rant

I don't know what am I doing hahah. I tried flashing in ODIN but it failed and trying to click start again saying SetupConnection... and nothing happens... I think it has to to with this?.

I don't know what "this" you're referring to? Did you read up about how to use ODIN? Did you watch any videos on it via Youtube (if that's your preference)? Did you install drivers?

schwinn8 said:
I don't know what "this" you're referring to? Did you read up about how to use ODIN? Did you watch any videos on it via Youtube (if that's your preference)? Did you install drivers?
Click to expand...
Click to collapse
I did two thing but I dont know which is which fixed it I downloaded an Update manually via Frija for SM-G973U (that I don't know it even exist bcxz sammobile doesn't have a record of it) and the 2nd one is I downloaded Odin3 v3.13.3 to flash the downloaded software. (previously i was using Odin3 v3.14.1)

I'm not sure, but it sounds like you figured it out? Congrats... yes Frija will sometimes get you a newer version than is normally seen. Or a version specific to your phone. Not a bad thing.
One thing I will warn you, I have read that many people are having issues with apps and features in Android 12... I'd recommend NOT getting that if you can prevent it. I prefer to let other people deal with the bugs before I have to get into them... but that's just me.