Database Info

GUIDE: How to downgrade from Lollipop to KitKat 4.4.2

I had a problem where my Samsung Galaxy S4 (SGH-I337M) was stuck in a boot loop because of the Lollipop 5.0.1 update. I tried everything from going into recovery mode and factory resetting it to doing the smack method on it. Then I found this way by flashing the Android Kitkat 4.4.2 ROM back into my phone via Odin. Here are the steps to downgrade to KitKat 4.4.2:
NOTE: I am not responsible for anything that happens to your phone. please proceed if you know what you are doing.
Before you start:
Turn on USB debugging by going to Settings>More>Developer Options. (If you don't have developer options, go to Settings>More>About device and press the build number 5-10 times and developer mode will be enabled)
Make sure battery is charged at least 50%
Backup everything if you can or make sure you have a backup already done.
Have your phone plugged into the computer
After you done those things, you ready to begin. Here is what to do:
1. Download Odin v3.09. You can download it by copy and pasting the link. odindownload.com/
2. Download the firmware for your phone. Go to sammobile.com (You will have to create a free account first) and look up your model. (For Example: you will search SGH-I337M if you have a Canadian Galaxy S4). The Model info should be behind the battery. If you don’t know or can’t find it, comment below and I will find it for you. Make sure you have the right carrier as well if it says so.
NOTE: Downloading the firmware may take a while if you have a slow internet connection. If you have a slow internet connection, make sure your computer doesn't sleep overnight while its downloading.
3. Extract both files to your computer.
4. Open Odin v3.09
5. On your Galaxy S4, Turn off your device. When its shut off, press the Power>Hone, and VOLUME DOWN key at the same time. You will see this pop up. (Image called 5-custom-os-warning.jpg. Click file for picture if you don't understand)
You will press volume up. Then you will see this. (Image called 4-downloading.jpg . Click file for picture if you don't understand)
DO NOT TOUCH YOUR PHONE WHEN THIS SHOWS UP!
5. Open Odin v3.09. Click the AP Button.
(Image called Odin-3.09.jpg . Click file for picture if you don't understand)
6. Look for the firmware you downloaded and click open. You will have to wait a bit until the firmware is in Odin. You will know when its finished when you see the file name in the AP box.
7. Click START. You will have to wait as the process takes 5-10 minutes. The phone will reboot once or twice. then the welcome screen should pop up. and you are DONE. You have successful downloaded Android KitKat 4.4.2.
Enjoy!
LukeTheTechGuy

Another guide http://forum.xda-developers.com/galaxy-s4/general/i9505-downgrade-5-0-lollipop-to-4-4-2-t3052472

Thank you! i works

LukeTheTechGuy said:
I had a problem where my Samsung Galaxy S4 (SGH-I337M) was stuck in a boot loop because of the Lollipop 5.0.1 update. I tried everything from going into recovery mode and factory resetting it to doing the smack method on it. Then I found this way by flashing the Android Kitkat 4.4.2 ROM back into my phone via Odin. Here are the steps to downgrade to KitKat 4.4.2:
NOTE: I am not responsible for anything that happens to your phone. please proceed if you know what you are doing.
Before you start:
Turn on USB debugging by going to Settings>More>Developer Options. (If you don't have developer options, go to Settings>More>About device and press the build number 5-10 times and developer mode will be enabled)
Make sure battery is charged at least 50%
Backup everything if you can or make sure you have a backup already done.
Have your phone plugged into the computer
After you done those things, you ready to begin. Here is what to do:
1. Download Odin v3.09. You can download it by copy and pasting the link. odindownload.com/
2. Download the firmware for your phone. Go to sammobile.com (You will have to create a free account first) and look up your model. (For Example: you will search SGH-I337M if you have a Canadian Galaxy S4). The Model info should be behind the battery. If you don’t know or can’t find it, comment below and I will find it for you. Make sure you have the right carrier as well if it says so.
NOTE: Downloading the firmware may take a while if you have a slow internet connection. If you have a slow internet connection, make sure your computer doesn't sleep overnight while its downloading.
3. Extract both files to your computer.
4. Open Odin v3.09
5. On your Galaxy S4, Turn off your device. When its shut off, press the Power>Hone, and VOLUME DOWN key at the same time. You will see this pop up. (Image called 5-custom-os-warning.jpg. Click file for picture if you don't understand)
You will press volume up. Then you will see this. (Image called 4-downloading.jpg . Click file for picture if you don't understand)
DO NOT TOUCH YOUR PHONE WHEN THIS SHOWS UP!
5. Open Odin v3.09. Click the AP Button.
(Image called Odin-3.09.jpg . Click file for picture if you don't understand)
6. Look for the firmware you downloaded and click open. You will have to wait a bit until the firmware is in Odin. You will know when its finished when you see the file name in the AP box.
7. Click START. You will have to wait as the process takes 5-10 minutes. The phone will reboot once or twice. then the welcome screen should pop up. and you are DONE. You have successful downloaded Android KitKat 4.4.2.
Enjoy!
LukeTheTechGuy
Click to expand...
Click to collapse
Does this same procedure work for downgrading to JellyBean MDJ firmware? Or can Lollipop only be downgraded to Kitkat?
Thanks.

Brother my 9505 have custom lollipop now.can I this process for back to kk?or its for only stock lollipop to kk?

yes, it can also be downgraded to MDJ firmware... I just tried yesterday. However, WiFi and phone call are not working. I then flashed to 4.4.2 and works perfectly since then.

HI, is not neccesary to install BL and PDA? Only AP? Thanks !!!

Is this working on SHV-E330L?

[Resolved] [HELP] I need help, my phone doesn't start.

First of all, I have a Galaxy S8+ (Model: SM-G955FD). I was trying to install the stock firmware through Odin, there were a bunch of file when I downloaded them (AP, BL, CP, CSC and HOME_CSC) but the guide I was following said to select only the AP and put start. And I did that but now I cannot do anything with it. It is stuck at "SAMSUNG Galaxy S8+ POWERED BY android", I've tried entering the recovery mode but it doesn't work so I can't access fastboot or anything. Adb not working because it doesn't connect to the computer. The only thing I can enter is the download mode, but I guess it deactivated usb debugging and oem unlock because I can't do anything on Odin, it fails. My phone became useless. It doesn't even shut down, if I try to force shut down it turns on again.
Almost forgot to say, the phone was rooted, I have no warranty anymore.
Is there anything I can do? I can't afford another phone, there's gotta be something.

IMOplus said:
First of all, I have a Galaxy S8+ (Model: SM-G955FD). I was trying to install the stock firmware through Odin, there were a bunch of file when I downloaded them (AP, BL, CP, CSC and HOME_CSC) but the guide I was following said to select only the AP and put start. And I did that but now I cannot do anything with it. It is stuck at "SAMSUNG Galaxy S8+ POWERED BY android", I've tried entering the recovery mode but it doesn't work so I can't access fastboot or anything. Adb not working because it doesn't connect to the computer. The only thing I can enter is the download mode, but I guess it deactivated usb debugging and oem unlock because I can't do anything on Odin, it fails. My phone became useless. It doesn't even shut down, if I try to force shut down it turns on again.
Almost forgot to say, the phone was rooted, I have no warranty anymore.
Is there anything I can do? I can't afford another phone, there's gotta be something.
Click to expand...
Click to collapse
You should have flashed all 4 parts. Most stock firmwares come as an all-in-one .tar.md5 file that is all 4 parts in one file, these all-in-one firmwares are flashed in the AP slot. The guide you followed probably assumed that you would have an all-in-one firmware file, that's why it says to flash in the AP slot.
BL goes on BL slot
AP goes in AP slot
CP goes in CP slot
CSC goes in CSC slot
Then click start.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
You should have flashed all 4 parts. Most stock firmwares come as an all-in-one .tar.md5 file that is all 4 parts in one file, these all-in-one firmwares are flashed in the AP slot. The guide you followed probably assumed that you would have an all-in-one firmware file, that's why it says to flash in the AP slot.
BL goes on BL slot
AP goes in AP slot
CP goes in CP slot
CSC goes in CSC slot
Then click start.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Ok, I tried that, but it failed. Odin is not working with anything. I've also tried installing twrp again but it failed too. When I flashed only the AP, I think the part of the system that was installed has the usb debugging and oem unlock turned off, is that possible? Well, Odin doesn't work.
Edit: I tried again after you replied to me and it worked! I mean, what's your magic? Well, thanks. My problem is solved.

IMOplus said:
Ok, I tried that, but it failed. Odin is not working with anything. I've also tried installing twrp again but it failed too. When I flashed only the AP, I think the part of the system that was installed has the usb debugging and oem unlock turned off, is that possible? Well, Odin doesn't work.
Edit: I tried again after you replied to me and it worked! I mean, what's your magic? Well, thanks. My problem is solved.
Click to expand...
Click to collapse
Sometimes, it just takes flashing a few times, it doesn't always work on the first try.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

OTA updates not working post OREO BETA

Hello,
This is just a quick post for anyone who may still be stuck on the OREO BETA firmware even though it finished a few months ago.
I was getting so frustrated, everyone was getting updates apart from me, apparently if you want to be helpful and join the beta, Samsung then penalise you for it.
Anyway I tried contacting them and received a vague, "You'll get it some time". I was frustrated to say the least.
So after weeks of waiting I thought I'd bite the bullet and put the newest firmware on my S8 using ODIN.
So although a lot of people probably know what they're doing when it comes to ODIN, and I may be going over the same ground as others have, I thought I'd just put here what I did in case anyone else is in the same boat as me and feels nervous of applying the Firmware themselves.
Top tip would be to try and backup any non restorable information you have on your phone as it will be wiped by ODIN via my steps.
So firstly I have an SM-G950F which is BTU. I also used a Windows 10 laptop for ODIN.
1. I downloaded the latest BTU firmware for my SM-G950F from sammobile.com (URL I used https://www.sammobile.com/firmwares/galaxy-s8/SM-G950F/BTU/)
2. Downloaded ODIN v3.13.1 from sammobile.com too (https://dl.sammobile.com/Odin3-v3.13.1.zip)
3. Then on my laptop I extracted the firmware file to a folder, it contained 5 or 6 files.
4. I extracted ODIN from the xip file to it's own folder and started it up running it as Administrator in Windows (Right click Run as Administrator).
5. In Odin I clicked on each of the options BL, AP, CP, CSC selecting each corresponding file from the extracted firmware folder. Under CSC I used the file with HOME in the name.
6. I shutdown my phone and started it in update mode by holding the Volume down and Bixby buttons and the power button.
7. Once that started I had to press Volume Up on the first screen and then connected the phone to the laptop using an appropriate lead (the Samsung one).
8. It detected my phone on COM 4 and the box was blue.
9. I then clicked Start and left it for a long time.
10. Eventually the phone restarted and ODIN said PASS in green.
11. I found that I did then need to do a Factory Reset and a Cache clear before it was properly happy.
12. So to do the reset and clear I restarted the phone into recovery mode which involved shutting it down then holding Volume Up and Bixby buttons and pressing Power.
13. Once that had started it took a little while and eventually showed me a menu. I scrolled using the volume keys to Wipe data/Factory reset and selected it using the Power button.
14. I then scrolled to Wipe cache partition and selected that.
15. Then I restarted the phone and went through the wizards etc. to set my phone up and got it to restore my apps and settings from my google account.
All looking good, it still thinks the phone is official etc. and OTA updates seems fine now. No major problems so far.
Obviously that was just my experience but perhaps it will help someone who was hesitant to do it.

Stock-S7 freezes on startup after Oreo-update (full wipe, different stock ROMs)

Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp

philipp-h said:
Hi there,
I am trying to repair a stock S7 (G930F) which freezes after an OTA-update. About a year ago there was a similar problem, which I solved by flashing an older firmware and telling the owner not to do the update again. Now the update was done again and this time Odin does not let me downgrade due to "KERNEL REV. CHECK FAIL".
The freeze appears 10 to 20 seconds after reboot. The phone freezes completely and after 20 seconds it restarts. That's not enough time to complete the initial setup or anything else.
I tried many different stock ROMs, full-wipe by stock-recovery, re-partitioning with Odin, safe mode, all with and without SD-card, SIM-card and cable plugged in.
I can't try custom ROMs or TWRP due to the FRP (force reset protection). To disable this a have to login with the previous Google-account... this is not possible within time before the phone freezes. My last idea would be to search for a method to remove the FRP in the darker pages on the web and then using TWRP and custom ROMs. Or the dangerous NAND-Erase in Odin (I have no EFS-backup)?
Any ideas except buying a new one?
Thanks,
Philipp
Click to expand...
Click to collapse
Philip, it helps if you let us know what country your in.
Anyway the solution to your problem is pretty straight forward, you just need to flash the latest firmware for your region with Odin. No need to mess about with TWRP at this point.
Official firmware will contain a copy of the stock kernal which will also be installed when you flash with Odin 99% of the time. If for some reason the kernal is not flashed (it happens) and you continue to get the reboot issue then you will need to flash the kernal seperately first with Odin then the firmware afterwards.
The issue with the FRP lock will remain after this but should allow you to unlock with google email and password.
So we're talking, downlaod mode, flash official fimrware and go from there.

Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...

philipp-h said:
Hi cooltt,
thanks for your reply. Unfortunately I already tried many stock ROMs. I am from Germany, so of course DBT first (G930FDBT7ESL9), then VIA (Telefonica) and VD2 (Vodafone) since they had higher build numbers. Desperately I also tried other versions to get it running somehow (for example the Polish G930FPRT7ETA9). The kernel was successfully installed with all ROMs.
I was very confused, that this does not work. In my understanding this can not be explained. After full wipe/repartition and flashing stock it should be as "stock" as it can be (and everyone should have these problems). Either all these ROMs I tried are broken, some hidden things like EFS are heavily broken or there is a hardware issue with this phone which made absolutely no problems with Nougat but now with Oreo.
Bootloops after OTA (which are dirty) are usual, but this is driving me crazy. I can not believe in a hardware issue since a very similar problem appeared one year ago with Oreo and there were never any issues with Nougat. But if it is a software problem, more users should have this...
Click to expand...
Click to collapse
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.

cooltt said:
Hello Philip this might be a long post
What firmware was on the device before the problem started? Was it branded or unbranded?
Are you sure the phone is a genuine G930F or a phone that has been turned into a G930F by flashing that firmware in the past? You can check by looking at what the phone model is at the top left corner of "Download mode"
Where are you getting the other firmwares from?
I've attched Samfirm tool which will get the latest firmware direct from Samsung servers.
1. Unzip file
2. Right click on SamFirm application and run as admin.
3. Check "Auto" & "check crc32" & "decrypt auto"
4. Model is "SM-G930F" type it exactly as shown without quotes
5. Region is "BTU" . Offically UK with all EU language options but also additional files which will fix firmware install problems.
6. Press "check update" then "download". It will decrypt automatically and you will have a zip file with 5 files inside(BL,CSC,AP,CP,CSC_HOME) choose CSC not CSC_Home when placing into Odin. Place all other files in right place.
Odin attached is version 3.13b patched. This version of Odin will ignore lots of miss-match device errors and just install the above BTU firmware.
Click to expand...
Click to collapse
Hi cooltt and thanks for your help!
Unfortunately the BTU-ROM did not solve the freeze-reboot-problem but led to another: After flashing the phone gets stuck with a blue screen "Erasing". After several hours I force rebooted and now it is showing a similar screen with "Error!" and a percentage which is increasing to a random number from 0% to 12% on each boot. On first boot it shows the boot screen ("Galaxy S7"), then "Installing system update" shortly and then "Erasing". After force-reboot it shows boot screen, "Erasing" then "Installing system update", both for a very short time (sometimes misses "Installing...")
As suggested I used SamFirm to download the newest BTU-ROM (SM-G930F_1_20191218140415_dgobhw6g3v_fac; G930FXXS7ESL5/G930FOXA7ESL5/G930FXXS7ESL5/G930FXXS7ESL5). I just ticked F. Reset Time and Reboot. Re-Partitioning did not change anything. Using Odin v3.13.1 does not make a difference. The other ROMs, like SM-G930F_1_20191226131628_8ds2p6kf0v (G930FXXS7ESL9/G930FDBT7ESL9/G930FXXS7ESLA/G930FXXS7ESL9) which I downloaded with Frija (should do the same: download enc4-files from Samsung and decrypt) make the phone going to the initial setup fine, but with the reboot-problem. Tried also with Odin 3B patched.
At this point I was going to write, that I could not access the recovery mode with the BTU-ROM but just now I started it unintentionally when looking for the sequence of screens showed on boot. So I used my chance, made a full wipe and screenshot. After this the phone booted until the glowing "Samsung"-logo appeared. Then rebooted and went to initial setup (after "Androi"Installing applications") in German. The freeze-reboot-issue appears as with all the other ROMs.
The phone is certainly an original SM-930F as it was bought directly from a big, trustworthy dealer and then just used by my aunt. The only one touching it when problems appeared was me. There is SM-G930F printed on the backside and showed in download mode.
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089

philipp-h said:
Hi cooltt and thanks for your help!
Gallery with screenshots (as I cannot find way to upload attachments - although I posted attachments on XDA before...): https://forum.xda-developers.com/album.php?albumid=16089
Click to expand...
Click to collapse
Hi Phill
The only options checked in Odin should be F-Reset and Auto reboot. Don't check any others.
The blue screen erasing and updating is normal after a flash with Odin, the phone will restart a couple of times, just leave it do it's thing for a bout 10 minutes or so. If it's any longer than that as you have mentioned then it's stuck as you've said.
So we're going to start from the begining again but do something slightly different.
1. Place the phone into download mode
2. Run Odin but uncheck "Auto Reboot" so the only option checked is F-Reset Time.
3. Use whatever firmware you want, BTU or DBT the latest version. Make sure files are in the correct boxes.
4. Connect phone and flash with Odin, wait until Odin says "succeed 1" and "dissconnected" . It may even say "pass" in green, not important but "succeed 1" is important.
5. Your phone will show the bar and do not disconnect. So....disconnect from laptop / PC. The screen should remain "do not disconnect".
6. Hold volume down+home+power (in that sequence).
7. As soon as the screen goes black move your finger to volume up, while still holding down home + power. You are trying to get the phone into Recovery mode as you said earlier.
8. The option to choose in the recovery menu is "wipe cache partition" NOT "wipe/factory reset". I can see from your pictures that this option has failed because the FRP lock is still on!!
9. When you've chosen "wipe cache partition" then choose "reboot system now"
The phone should go through it's normal set up routine, erasing, update, installing apps etc, just leave it do this and hopefully the phone will boot then ask for the Google email and password which was used on the phone.
There are very few reasons for the phone to get stuck on boot....
1. Incorrect firmware,
2. Water damage
3. The phone has been Rooted with FRP lock on. It is very rare to be a hardware issue.
You should always turn FRP lock off and enable OEM unlock in settings before flashing to a phone. I know it's a little late for that but something to remember.
To check for water damage.
1. Remove SIM card and holder
2. Shine a light in the hole, you will see a WHITE sticker which turns PINK if water has ever got inside the phone.

Thanks a lot again for your great efforts!
I tried as you wrote but did not manage to start recovery immediately after flashing (tried >10 times). But after some while the BTU-ROM started and now keeps doing so even after new flash without wiping cache afterwards. Wiping data worked for me in past when I sometimes had enough time to enter Wi-Fi-password. It was saved even after reboot and away when I did data wipe in recovery. With the newest ROMs I never got beyond typing Wi-Fi credentials.
I cannot see a water damage. A root was never tried before (and OEM-lock and FRP were always on because stock, which is very bad now ). Would be absolutely no problem if this !#@*#% stock ROMs would work... TWRP installation was directly blocked when I tried my luck as last resort. I did not try other images.
Thanks nevertheless for your time and patience!

SOLVED: N986B/DS KSA and Odin is failing to flash. Would greatly appreciate assistance. Thanks!

Condensed for brevity:
Unlocked bootloader and Debug USB enabled. Went to flash an AP and it failed. Tried to use Frija to get the most recent update, found N986BXXS3EULH REV01, tried to flash the AP/BL/CP/CSC to refresh the phone and it's failing.
Everything matches my phone when I typed *#1234# (EULB/EULH) except the download has REV01 added to the end.
Phone is stuck in download mode no matter how I reboot it. Phone isn't bricked but won't do anything else.
Edit: Updated to using Odin 3.14.4 instead of 3.13.1
Edit 2: Figured out the phone is freezing after any fail (brightness doesn't change with volume keys). I get the failed PIT as well as "Can't open specified file (Line:2006)"
Edit 3: Re-opened Frija and it gave me an entirely different FW this time that superseded what I had on the phone originally and the DL'd file (*3EULH became *3EVA9).
Tried to use new CSC and it keeps failing at prism.img. It's progress but not really at the same time.
Edit 4: It lets me install the BL and CP for either/or EULH or EVA9 but neither CSC or AP work ever. I'm thinking I just have a bad firmware or something.
Final update for the night: The files are good. Compared hashes across multiple downloads. Phone isn't seen in Samsung Smart Switch and there doesn't seem to be a recovery menu. TWRP or otherwise.
If anyone has any ideas please let me know. I'm pulling my hair out because it's brand new. All I did was try to start by updating the stock firmware with Odin (after bootloader unlocking and USB debug enabling) and this happened.
-------------------------------------------------------------------------------------
Day 2: Moved back to Odin 13.1 and extracted PIT from EULH CSC, installed it, then did the BL/CP, installed fine. Still froze with CSC/AP. Then attempted to try it all at once. PIT, CP, BL, CSC, and AP. It actually starts installing now. But it specifically always freezes at the super.img portion. So while I'm unsure what's going on now since I'm still trying to install the correct official ROM, I'm starting to think the ROM is somehow incompatible with my phone.

HERE'S THE ANSWER! Many thanks to those who attempting to help. We were doing and advising everything correctly.
The problem is the PC itself. Which was why the issues seemed so varied. I attempted every USB in my computer, none would flash (they drop out randomly with my phone), and the first sign I didn't realize was a sign was the phone wouldn't work on my USB-C ports, only 3.0/3.1.
I run a Threadripper 3960x on an Aorus TRX40board. I had to go to a 2015 touchscreen laptop to do this. If you're having issues then literally try a new PC if possible. If you see that it isn't connecting to Odin on USB-C, then you may well have the same issues I was having.
Note: this may be a driver issue, as I used every one of my 20-ish ports and they all still failed, as well as about 5 different cable options to go between USB/USB to C and USB-C to USB-C.