Database Info

[OBSOLETE][GUIDE] Updating Modem, Bluetooth and DSP! Without triggering ARP!

[OBSOLETE] @yshalsager As of 8.8.16 flashable TWRP non ARB Firmware now available see thread.
[GUIDE] Updating Modem, Bluetooth and DSP! ~~~ Without triggering ARP on WHYRED!
For anyone on customs rom and need to updated the above partitions?
The commands to flash them in fastboot are: -
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
pause
I just created a bat file (windows) with the above content.
All I need do in future is download a firmware from here, extract the three files and place the bat file in the same folder, and run it.
^^^ Note I have adb/fastboot setup with a global path in windows.
Haven't tested in operation yet but in theory should work. I'm on 8.7.5 Beta firmware at present and see no need to update until the custom rom in use requires update files.
Above 3 files have been reported safe to flash here (Thanks @aank) , without effecting the bootloader, so not to trigger ARP.
First two files are self explained.
DSP (Digital Signal Processor)
[INFO] ANDROID DEVICE PARTITIONS and FILESYSTEMS
Attached is a sample bat file, just remove the .txt from the end of the file name.
I posted this before in the Everything About Anti Roll-back [Whyred] by @AL_IRAQI , but would probably get lost there.
Edit: - Edited the batch file to include a "pause", in case you double click instead of running in CMD/POWERSHELL window.

Cool, hope it works if i ever need it. Thanks

thx tested it, it works, i am still on anti 3 after updating these 3

does this improve signal reception? when I'm using any custom rom, my signal is really bad, but in MIUI it isn't, it's really great and it's full.

rizdar said:
does this improve signal reception? when I'm using any custom rom, my signal is really bad, but in MIUI it isn't, it's really great and it's full.
Click to expand...
Click to collapse
It may depend on the custom rom your on?
What was your last MIUI firmware?
Updating/downgrading the modem to the working version may help/improve things.

@corkiejp Do you recommend flashing the firmware files from 9.5.19 or the ones from 8.7.26 when moving to a custom rom?

corkiejp said:
It may depend on the custom rom your on?
What was your last MIUI firmware?
Updating/downgrading the modem to the working version may help/improve things.
Click to expand...
Click to collapse
I'm on Arrow OS right now.
But after I do the steps above, it seems like nothings changed.
The signal is still the same.
It's happening on all custom ROMs, is it because my providers?
Edit: I was on 8.7.26 (Masik U 2.2)

@eyebiz
I would stick with whatever firmware your device has at present. It is probably more recent than firmware recommend by custom roms.
There is really no reason to update firmware, if your device is working well with what you have!
If the rom recommends a specific firmware, then you may need to upgrade, but don't downgrade firmware to match.
If I'm flashing firmware, I usually use the version from beta roms, as that is often the more recent firmware.
I only update roms, once a month when security patches included. And patch the firmware at the same time.

@rizdar Your network provider maybe the problem, check your APN settings with the recommend settings of your provider.
The three files mentioned in this thread, may not be alter from one firmware to the next. It is usually the bootloader (which we need to avoid for ARP) that regularly changes.
You could compare files and hashes from different firmware to see if there is changes.

Hi @corkiejp
I've created TWRP flashable .zip with latest stable modem, dsp and bluetooth here :
https://drive.google.com/file/d/1eYys31FFgdxz4GyMFgMiuvoTWwwgER1Y/view?usp=drivesdk
The ARB should be fine as well,
I've tried myself, flashed it on top of 9.6.3 fw less ROM.

@otonieru Saw your post in the firmwareless rom thread. Are you same person that was creating these zips on xiaomi.eu?
Had a look at the script again, looks safe.
It would help if you labeled the zip with the date/version of firmware. i.e. Global 8.8.16.
Also I thought you where going to remove unneeded files. Don't know what update binary script does?
Edit: - Waiting on a RR rom update before flashing new partial firmware.

corkiejp said:
@otonieru Saw your post in the firmwareless rom thread. Are you same person that was creating these zips on xiaomi.eu?
Had a look at the script again, looks safe.
It would help if you labeled the zip with the date/version of firmware. i.e. Global 8.8.16.
Also I thought you where going to remove unneeded files. Don't know what update binary script does?
Edit: - Waiting on a RR rom update before flashing new partial firmware.
Click to expand...
Click to collapse
Oh, no, am not on xiaomi.eu. Just happen to look around the fw less thread, and it seems there's a need for a TWRP flashable zip for radio only update,
I use firmware file from git, and merged it with TWRP flashable zip. Only, i edit the updater script to make it only flash modem, bluetooth and DSP.
I didnt delete too much files from firmware update folder, only one i think is really safe to delete.
Alright, i will modify the file name.
It contain 8.8.16 Global files.

otonieru said:
I use firmware file from git, and merged it with TWRP flashable zip. Only, i edit the updater script to make it only flash modem, bluetooth and DSP.
Click to expand...
Click to collapse
Have you a link to git, it would be easier to just download the three files for me, than extracting them from Firmware zips.

Apparently those firmware files are safe. I flashed them with a .zip file I put together. For anyone that wants to try you can download it from here.

Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.

corkiejp said:
Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.
Click to expand...
Click to collapse
lol. you spoiled the surprise, it was a test. I'll release it soon

corkiejp said:
Looks like @yshalsager is also going to provide update zips with just the three files as well.
@otonieru @Ookami999 He must of edited his automatic script to create the zips.
Click to expand...
Click to collapse
I edited the original one and signed the .zip, it seems to be working. Although the cell power consumption is still quite high so far.

deleted

I have this problem
Jio-volte network goes away after reboot in all pie custom roms. Network signals are on after changing preferred nertwork type.
and data on jio-volte is not working.
I was told i should upgrade firmware,but same problem.
will upgrading these 3 files from here help me?

ahsnali said:
I have this problem
Jio-volte network goes away after reboot in all pie custom roms. Network signals are on after changing preferred nertwork type.
and data on jio-volte is not working.
I was told i should upgrade firmware,but same problem.
will upgrading these 3 files from here help me?
Click to expand...
Click to collapse
It may or may not help your situation. If your worried about your anti version, there is non arb firmware zips available with just them files.
VoLTE is broken on most PIE roms (I believe based on discussions in TE) , check your rom thread and see if anyone else has it working. Or if there is Patch to enable it.

[Stock based only] How to enable VoLTE & VoWiFi for India on any region phone.

Why:
You imported the phone to India from another country and now VoLTE doesn't work for you. Maybe you unwittingly messed with your phones "/odm" partition.
This guide will help you get back the VoLTE functionality for INDIAN MOBILE CARRIERS*. Participate in the poll you want similar guide for other countries.
*might work for Bangladesh, Nepal etc.
Before:
Make sure your carrier supports VoLTE or VoWiFi.
Stock or stock based ROMs.
You should have at least TWRP or root.
Where:
Download the UNFLASHABLE files from here.
How:
-=:TWRP METHOD:=-
Extract the downloaded file, "volte_twrp.zip", to the root of your internal or external storage.
Internal Storage: /storage/emulated/0/TWRP (may not be the same for you)
External Storage: /storage/0000-0000/TWRP (may not be the same for you)
Reboot to recovery.
Select "Backup" from TWRP menu.
Hit "Select Storage".
Select the storage you extracted the downloaded file to.
You should see "2019-05-22-05-24-06_treble....". Select it.
You should see a single entry for "/odm" under "Select Partitions to Restore". Select it if it isn't already.
Uncheck "Enable Digest Verification..."
Swipe to restore. Restart to "System".
-=:root METHOD:=-
I haven't tried this. Let me know!
With your favorite file explorer obtain root access for "/odm".
Replace contents of "/odm" with files extracted from the downloaded file, "volte_root.zip".
Restart.

Good tutorial, but wouldn't be easier just to flash with odin the modem and csc for the specific carrier? It works even on Pie with older oreo modem/csc. You don't need root or twrp.
Tested myselsf, first Pie update was for Russia. Flashed it, but I lost wifi call and volte. So i downloaded oreo stock for my country(Romania - Orange) and flashed the modem and csc. Got back wifi call and volte.

kimitza said:
Good tutorial, but wouldn't be easier just to flash with odin the modem and csc for the specific carrier? It works even on Pie with older oreo modem/csc. You don't need root or twrp.
Tested myselsf, first Pie update was for Russia. Flashed it, but I lost wifi call and volte. So i downloaded oreo stock for my country(Romania - Orange) and flashed the modem and csc. Got back wifi call and volte.
Click to expand...
Click to collapse
This method only works if both the firmwares are for the same model. For examples I cannot flash Indian(SM-A750FN) firmware on a device I obtained from Malaysia(SM-A750GN) because they are different models (FN<->GN). For more information read my other guide.

Hi my phone model SM-A750FN, purchased in Europe and using in India and volte not working , only jiovoice call app working . With this app I can't access bank apps due auto verification failure ... I checked the CSC available list and I didn't found Indian CSC .... Please help me what to do

ch.snehith said:
Hi my phone model SM-A750FN, purchased in Europe and using in India and volte not working , only jiovoice call app working . With this app I can't access bank apps due auto verification failure ... I checked the CSC available list and I didn't found Indian CSC .... Please help me what to do
Click to expand...
Click to collapse
some changes and instructions need to work this fix
After changing that your file worked for me

ch.snehith said:
some changes and instructions need to work this fix
After changing that your file worked for me
Click to expand...
Click to collapse
i have the model SM-A750F/DS bought from dubai.. same issues ..cant access banking apps through jio call app..plz help bro

OK ..finally i have got volte working..its not a big deal at all..self experimnet is everything.
follow the steps
1. goto updato.com search for the firmware SM-A750F and refine the search for India (INS) and the android version 9
2.get the latest firmware and download it.
3.need odin version Odin3_v3.13.1 or above to flash it.
4.enable oem unlock and usb debuggin in developer option.
5.extract the firmware with 7zip, run odin as administartor and
select AP>AP, BL>BL , CP>CP, and important CSC>shud select CSC and not HOME CSC.
put your mobile on download mode flash the firmware.reboot will take a while be patient.
and VoLte wil be there..

Magisk module need help testing for China and Korea users.

The firmware does not contain carrier files for China and Korea carriers.
I made a magisk module that installs these carrier files systemlessly.
I don't live in China or Korea so I have no way to test this.
If you're living in China or Korea, please help me test the module to see if it works.
Thanks.

Hi swangjang, thank you for sharing your module! I used QPST to replace the modified xml files to enable 5G, and now I installed your module. The 5G runs well, but I can't tell if it is enabled by your module.
For VoLTE, the switcher appeared in the option, but it dosen't work. When I made a phone call, the network drop to 3G. (My carrier is China unicom)

q.snake said:
Hi swangjang, thank you for sharing your module! I used QPST to replace the modified xml files to enable 5G, and now I installed your module. The 5G runs well, but I can't tell if it is enabled by your module.
For VoLTE, the switcher appeared in the option, but it dosen't work. When I made a phone call, the network drop to 3G. (My carrier is China unicom)
Click to expand...
Click to collapse
Thank you for testing.
I think due to dm-verity, the module files don't actually get placed in the system. I'll need to wait until we get TWRP to disable verity.
Can you try and change sim cards to force the phone to reload the mbn file?

swangjang said:
Thank you for testing.
I think due to dm-verity, the module files don't actually get placed in the system. I'll need to wait until we get TWRP to disable verity.
Can you try and change sim cards to force the phone to reload the mbn file?
Click to expand...
Click to collapse
I'll test it later.

q.snake said:
I'll test it later.
Click to expand...
Click to collapse
Tbh, I don't think it will work.
I plan to install a custom rom (custom roms don't have dm-verity) in the weekend and see if the module works on there. As long as dm-verity is enabled, I don't think any /system modifcation by magisk will work.

swangjang said:
The firmware does not contain carrier files for China and Korea carriers.
I made a magisk module that installs these carrier files systemlessly.
I don't live in China or Korea so I have no way to test this.
If you're living in China or Korea, please help me test the module to see if it works.
Thanks.
Click to expand...
Click to collapse
Hi, I live in south korea and I have UK version of Pixel 5(GTT9Q).
I'll try this module tonight and see if it works.
May I ask you where did you get mbn files for korean carrier? In my experience, KT and LGU need some efs modification especially for google pixel series, so directly injecting mbn from other device won't work well.

cdexswzaq said:
Hi, I live in south korea and I have UK version of Pixel 5(GTT9Q).
I'll try this module tonight and see if it works.
May I ask you where did you get mbn files for korean carrier? In my experience, KT and LGU need some efs modification especially for google pixel series, so directly injecting mbn from other device won't work well.
Click to expand...
Click to collapse
That attached module is very outdated. Please download from here:
GitHub - swangjang/Pixel-Redbull-Carrier-Patch: This is a Magisk module (in testing) for Pixel 4a (5G) and Pixel 5 that enables 5G for Unlisted Countries, VoLTE switches in the settings and add support for more countries/carriers.
This is a Magisk module (in testing) for Pixel 4a (5G) and Pixel 5 that enables 5G for Unlisted Countries, VoLTE switches in the settings and add support for more countries/carriers. - GitHub - swa...
github.com
I got the mbn files from Xiaomi Redmi K30. The K30 uses the same chipset as Pixel 5.

Just tested module in south korea, but it doesn't works.
It seems that magisk module is doing it's job. I run root explorer and confirmed that mbm_sw.txt and other additonal korea and china mbn successfully loaded.
But when I run efs explorer, Banner shows "SW_DEFAULT" instead of "LGU".
Maybe Pixel 5 can't load LGU mbn because of some other reason.

cdexswzaq said:
Just tested module in south korea, but it doesn't works.
It seems that magisk module is doing it's job. I run root explorer and confirmed that mbm_sw.txt and other additonal korea and china mbn successfully loaded.
But when I run efs explorer, Banner shows "SW_DEFAULT" instead of "LGU".
Maybe Pixel 5 can't load LGU mbn because of some other reason.
Click to expand...
Click to collapse
Thank you for testing. Did you install the A or B? could you try the other one as well to see if it works? Please make sure to uninstall first.
Also maybe take out sim card and insert again?

swangjang said:
Thank you for testing. Did you install the A or B? could you try the other one as well to see if it works? Please make sure to uninstall first.
Also maybe take out sim card and insert again?
Click to expand...
Click to collapse
I used A. and took out & changed sim card several times.
I'll check B tonight.

cdexswzaq said:
I used A. and took out & changed sim card several times.
I'll check B tonight.
Click to expand...
Click to collapse
I read on a Korean forum that you may need to visit your carrier customer centre to register your device
???ۺ????丮 [??????, ???÷???, ????? ?ؿ??? Ŀ?´?Ƽ] : ???̹? ī??
cafe.naver.com
Under section 3. part (4), "VoLTE calls can be made only by registering OMD (Open Model Device) as a VoLTE capable model name with each mobile operator".
Also, after installing the module, maybe reboot the device once?

swangjang said:
Thank you for testing.
I think due to dm-verity, the module files don't actually get placed in the system. I'll need to wait until we get TWRP to disable verity.
Can you try and change sim cards to force the phone to reload the mbn file?
Click to expand...
Click to collapse
Hi, I changed the SIM card of another carrier but the 5G is still enabled, even after I installed magisk completely and restore the original files with QPST, the 5G is still there...
I doubt that the new firewares (Feb and Mar updates) canceled the carrier limitation for 5G.

cdexswzaq said:
I used A. and took out & changed sim card several times.
I'll check B tonight.
Click to expand...
Click to collapse
Hi, I made more variations of the module using different mbn files for Korean carriers. Could you please them one at a time. It would be greatly appreciated.

I tried this with korean LGU, SKT simcard, but efs explorer shows SW_DEFAULT or Wildcard banner randomly.
I did sim tray out and in several times, and did WI-FI, Mobile Bluetooth reset on android settings-system menu.
And I also tried Taiwanese Chunghwa Telecom sim card which i got during taiwan travel, (Chunghwa Telecom is one of supported carrier for pixel 5) And It reports CHT banner correctly.
I don't know why, but it seems that pixel 5 refuses to load korean mbns for some reason.

cdexswzaq said:
I tried this with korean LGU, SKT simcard, but efs explorer shows SW_DEFAULT or Wildcard banner randomly.
I did sim tray out and in several times, and did WI-FI, Mobile Bluetooth reset on android settings-system menu.
And I also tried Taiwanese Chunghwa Telecom sim card which i got during taiwan travel, (Chunghwa Telecom is one of supported carrier for pixel 5) And It reports CHT banner correctly.
I don't know why, but it seems that pixel 5 refuses to load korean mbns for some reason.
Click to expand...
Click to collapse
Thank you.
So "pr-red", "nokia" and "mi9t" all not working for korean sim?

swangjang said:
Thank you.
So "pr-red", "nokia" and "mi9t" all not working for korean sim?
Click to expand...
Click to collapse
Yes, I tried all of 6 mbns, but no luck. All recognized as SW_DEFAULT or Wildcard banner.
I'm trying to figure out why only pixel rejects those mbns. Maybe there's some hidden policy to reject unsupported country's sim?

cdexswzaq said:
Yes, I tried all of 6 mbns, but no luck. All recognized as SW_DEFAULT or Wildcard banner.
I'm trying to figure out why only pixel rejects those mbns. Maybe there's some hidden policy to reject unsupported country's sim?
Click to expand...
Click to collapse
I don't think there would be something that will reject it. Other people reported they got VoLTE working for their 'unofficial' carrier.

General ROG Phone 5 Ultimate | New Firmware WW-18.0840.2109.188 | WW RAW & ROOT Images

Model - ROG Phone 5 Ultimate (Possibly ROG Phone 5 as well see here )
2021/11/05
Version Name - WW-18.0840.2109.188
Release Date - 2021/11/05
OTA Download Link - Download
RAW Download Link - PENDING
Stock Boot Image - Download
Magisk Patched Boot Image - Download
Changelog
ROG Phone 5 (ZS673KS) software Image：WW-18.0840.2109.188 for WW/JP/EU/RU only*
This firmware is only for ROG Phone 5 WW/JP/EU version use and not applicable to ROG Phone 5S/5S Pro series models.
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
For WW SKU Improved Item:
1. Optimize the charging experience function
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please back up your important data before system upgrading.
Click to expand...
Click to collapse
Spoiler
2021/08/24
Version Name - WW-18.0840.2107.151
Release Date - 2021/08/24
OTA Download Link - Download
RAW Download Link - Download
Stock Boot Image - Download
Magisk Patched Boot Image - Download
Changelog
ROG Phone 5 (ZS673KS) software Image：WW-18.0840.2107.151 for WW/JP/EU only*
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
For WW SKU Improved Item:
1.Updated Android security patch to 2021-07
2.Fixed issue with sending MMS messages on Optus Australia
3.Fixed an issue where some videos played through apps would get stuck and without response.
4.Fixed issue where AirTriggers would become insensitive after opening Taobao APP
For JP SKU Improved Item:
1.Updated Android security patch to 2021-07
2.Fixed an issue where some videos played through apps would get stuck and without response.
3.Fixed issue where AirTriggers would become insensitive after opening Taobao APP
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please back up your important data before system upgrading.
Click to expand...
Click to collapse
*********************************************************************************************************************
2021/07/22
Version Name - WW18.0840.2106.86
Release Date - 2021/07/22
OTA Download Link - Download
RAW Download Link - Waiting
Stock Boot Image - Download
Magisk Patched Boot Image - Download
Changelog
ROG Phone 5 (ZS673KS) software Image：WW-18.0840.2106.86 for WW/JP/EU only*
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
Note: Please be patience it's normal when downloading status bar stop a while with large update package.
Improved Item:
1. Updated Android security patch to 2021-06
2. Fixed an issue where the game would crash when using multiple windows to open the settings and change the system navigation
3. Fixed the problem of broken sound when using screen recording
4. Fixed the problem of low notification sound when using Bluetooth headsets in standby mode
5. Fixed an issue where blocking notifications in the game could not block Facebook messenger notifications
6. Fixed the problem of reduced call volume
7. Fixed the problem of using a microphone to record the voice of a team in the game, and the problem of not being able to record your own voice
8. Fixed the problem that the 5G network cannot be detected when connected to the GT-AX11000 router
9. Fixed a serious delay in the screen when entering the game with Geforce Now
10. Optimize touch experience
11. Fix sound effect for speaker playback.
Steps of Update:
1. Check software version of your device**
2. Download device software and Update SOP (From “Manual” Item)
3. Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4. Software update cannot transfer the software SKU and downgrade the software version.
5. Wrong SKU may cause update failure, please update the same SKU version only.
**How to know the device model?
Path: Settings->About-> Model number
Example: ASUS PadFone2
**How to know the device software version?
Path: Settings->About-> software information->Build number
Example: CHT_PadFone2-user-10.4.17.15-UpdateLauncher
**System upgrade may cause part of data missing, please back up your important data before system upgrading.
Click to expand...
Click to collapse

I would assume it is all the same, since the firmware you posted is
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
and the firmware from https://forum.xda-developers.com/t/new-firmwair-version-ww18-0840-2106-86.4309457/ is also
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip

twistedumbrella said:
I would assume it is all the same, since the firmware you posted is
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
and the firmware from https://forum.xda-developers.com/t/new-firmwair-version-ww18-0840-2106-86.4309457/ is also
https://dlcdnets.asus.com/pub/ASUS/...S_I005_1-ASUS-18.0840.2106.86-1.1.92-user.zip
Click to expand...
Click to collapse
It is the same, I'm looking for the RAW File.

JazonX said:
It is the same, I'm looking for the RAW File.
Click to expand...
Click to collapse
Wouldn't it also be the same then?

twistedumbrella said:
Wouldn't it also be the same then?
Click to expand...
Click to collapse
Not really, Once you install an OTA, The Active boot partition switches to the opposite one to boot the new firmware.
If you have Root + TWRP, I find this messy because then you have to manually patch the boot images, and it is usually after a few bootloops and softbricks. There is an option in Magisk, Install to inactive slot. That doesn't work always, at least during my ROG II and ROG III days.
Good thing about the RAW files, They do a clean install without wiping, and you can set it up easily afterwards with the usual magisk and patch steps without losing userdata. For a firmware upgrade I always prefer Raw files.
I actually found a RAW file from a usual source I used to get these, But surprisingly this version is not available in the ASUS site. Its about 3 digits below the current one.
WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw | Download

Well... I can at least take some of your worries... OTAs won't be a thing after you unlocked your bootloader. You need to manually install them via magisk again. So there is no chance these automatic updates will break your phone.
Furthermore you don't have to worry about root + TWRP as well because there is no twrp for this phone and I doubt there will be one in the next time.
But applying updates and keeping root access without loosing your user data should be no problem. Magisk has special options for this and many people here update that way without bootloops and soft bricks.

JazonX said:
Not really, Once you install an OTA, The Active boot partition switches to the opposite one to boot the new firmware.
If you have Root + TWRP, I find this messy because then you have to manually patch the boot images, and it is usually after a few bootloops and softbricks. There is an option in Magisk, Install to inactive slot. That doesn't work always, at least during my ROG II and ROG III days.
Good thing about the RAW files, They do a clean install without wiping, and you can set it up easily afterwards with the usual magisk and patch steps without losing userdata. For a firmware upgrade I always prefer Raw files.
I actually found a RAW file from a usual source I used to get these, But surprisingly this version is not available in the ASUS site. Its about 3 digits below the current one.
WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw | Download
Click to expand...
Click to collapse
I think you completely misunderstood my comment. I was saying that if the firmware for both models is the same, it is likely the raw files for both are the same (but still separate from the firmware).
In addition to what was already pointed out above, you have things backwards. The RAW firmware is intended to be a low-level rebuild. The regular firmware is not an incremental (which I assume is what you were thinking) and comes will a full firmware image every time.
Edit: The version from this thread now includes a separate flash_raw and flash_raw_and_wipe command.

twistedumbrella said:
I think you completely misunderstood my comment, but I am sure someone new will appreciate the explanation (with a few corrections).
In addition to what was already pointed out above, you have things backwards. The RAW firmware is intended to wipe your data, while the regular firmware upgrades are not. The regular firmware is not an incremental (which I assume is what you were thinking) and comes will a full firmware image every time.
Click to expand...
Click to collapse
RAW never wipes data. I've done it for almost 2 years in my ROG II.
That's how I usually update my firmware.
Unless something is changed in ROG 5 ... If yes, Then I'm wrong.
I'm yet to test all these anyway, Since unit is still on the way.

JazonX said:
RAW never wipes data. I've done it for almost 2 years in my ROG II.
That's how I usually update my firmware.
Unless something is changed in ROG 5 ... If yes, Then I'm wrong.
I'm yet to test all these anyway, Since unit is still on the way.
Click to expand...
Click to collapse
Then apparently it has changed. I didn't have a ROG II, but I have the ROG 5 in hand. I couldn't tell you what has changed, though.
You can, however, opt out of the erase. Not sure if you have to convert the raw to images first, though. I think that would be the method you used in previous phones. It was a flash_all script (or command, if you were on Windows).
Edit: The version from this thread now includes a separate flash_raw and flash_raw_and_wipe command.

twistedumbrella said:
Then apparently it has changed. I didn't have a ROG II, but I actually have my ROG 5. Couldn't tell you what else has changed.
You can, however, opt out of the erase. Not sure if you have to convert the raw to images first, though. I think that would be the method you used in previous phones. It was a flash_all script (or command, if you were on Windows).
Click to expand...
Click to collapse
Ohh .. In that case I was super wrong, and apologies over my misinformation.
Yeah, Actually ROG II Raw files had a Flash-all file which installs the full firmware, and reboots.
I even had a source (A Persian website) to get these when the OTA releases.
I was on windows, and usually after a RAW installation, the cache (Art or Dalvik, Whatever it is we have now) gets cleared and Phone becomes a little bit snappier than it was before.
Guess we gotta stick to ASUS OTA files from the support site then.
Thanks a lot ! : )

These updates come with a flash_raw script that looks more or less harmless. There is no visible wipe command included, but the phone did appear wiped after installing.
The flash_all, on the other hand, has a rather obvious section to opt in or out of an erase that opting out on Linux and Windows. I think the wipe isn't as much a wipe as it overwrites the partition.
I typically install my firmware with fastboot using a slightly modified version of the flash_all script and an unpacked payload. Somehow I broke the installer, which gives me a chance to test the raw again.
Edit: The version from this thread now includes a separate flash_raw and flash_raw_and_wipe command.

JazonX said:
The cache (Art or Dalvik, Whatever it is we have now) gets cleared and Phone becomes a little bit snappier than it was before
Click to expand...
Click to collapse
I thought that rumor died long ago. Usually unless things go wrong clearing the cache should not make your phone faster.
It's like closing all apps/recents after each usage in order to boost the performance.

Anubarak16 said:
I thought that rumor died long ago. Usually unless things go wrong clearing the cache should not make your phone faster.
It's like closing all apps/recents after each usage in order to boost the performance.
Click to expand...
Click to collapse
I think Art broke that. If I remember the explanation, the idea was to create something like the old odex layout that was less sloppy. The code that used to be cached is now broken out into a physical file alongside the application. It's also how apps like *that one everyone remembers for IAP* are able to modify code without breaking signatures.

Successfully rooted using the same commands from here and the root images in the OP.

JazonX said:
Successfully rooted using the same commands from here and the root images in the OP.
Click to expand...
Click to collapse
Any word on the raw firmware? What about the existing boot images?

twistedumbrella said:
Any word on the raw firmware? What about the existing boot images?
Click to expand...
Click to collapse
The RAW firmware I shared earlier - I didn't test it since it's a downgrade.
If the current firmware gets a RAW release, I will definitely test it.
Currently I patched only Boot Slot_A and booted to system using A. (using the same patched image I updated in OP)
Since there is no TWRP, I dont want to manually patch A and B both.
Magisk is stable, Didnt pass SafetyNet - So might need a module for that.

JazonX said:
The RAW firmware I shared earlier - I didn't test it since it's a downgrade.
If the current firmware gets a RAW release, I will definitely test it.
Currently I patched only Boot Slot_A and booted to system using A. (using the same patched image I updated in OP)
Since there is no TWRP, I dont want to manually patch A and B both.
Magisk is stable, Didnt pass SafetyNet - So might need a module for that.
Click to expand...
Click to collapse
You do need a module. It's posted in one of the root threads. I guess we won't know if you need different boot images until someone tests, but at least you seem to be comfortable patching your own.

twistedumbrella said:
You do need a module. It's posted in one of the root threads. I guess we won't know if you need different boot images until someone tests, but at least you seem to be comfortable patching your own.
Click to expand...
Click to collapse
Patching own images are always reliable...
SafetyNet Passed with this fix !

JazonX said:
Patching own images are always reliable...
SafetyNet Passed with this fix !
Click to expand...
Click to collapse
Glad you found it. Good luck.
I flashed the raw firmware. It was a downgrade and my device was already set up and in use, but it included the scripts and commands to install without a wipe (finally). Moving the latest firmware to the sdcard allowed me to update almost immediately after finishing the flash.
I would assume it works on the Ultimate, since everything else has been identical and the date on that package is the same as the software image.

New update !

Replacing a modem mbn file

I know it's possible but I'm not sure how to do it.
The Verizon modem file is loaded with coding to disable 5G, I know for a fact it has at least 2 methods to disable 5g, I found a way around those but still can't get it to connect to 5g but it sees the 5g is available. Which is the step in the right direction as stock mbn file with no mods results in the phone never seeing 5g as being available period.
So what I'm suggesting might work is swapping the Verizon modem mbn file with one from a phone that works on Verizon's 5G,like a s20 or similar or perhaps the Verizon's UW model also(heard the chipset needs to be the same on the device's)
Can anyone assist? Or point me in the right direction???

I think I have the same issue now. Verizon, I assume, somehow disabled the 5G functionality after some sort of update and I can't get it back. I use T - Mobile.

this may help https://forum.xda-developers.com/t/guide-fix-enable-5g-and-dss.4206461/ (look in other OnePlus phones like 10 or 8t )

After a bit of trial and error, I got 5G to work again on my device (IN2019). I had to replace the carrier_policy.xml files with another one from XDA in order to enable the network again.

@intheb0x Have you found a solution to this? I am interested in the same thing, I have a Korean S20 that does not have the info for North American/US NR5G bands. Other than software/firmware differences the Korean S20 is identical to the US versions, even the pit files are the same when examined with PIT Magic.
I've unpacked various modem images from XAA and TMB roms and then compared to Korean (KOO) roms and found the 549_10_0.mbn and 549_11_0.mbn to be missing a lot of data on the Korean roms. Looking at these files with a hex editor I can see that the US roms definitely have information regarding additional bands.
I have tried copying over the files and repacking the modem.img but the phone fails to load the files I copy. I believe this is because they are signed with a different signature than the Korean files.
I'm wondering if there is a way to disable signature verification on the modem files, maybe something like this?:
[Magisk MODULE] Patch SecureFolder - Disable Signature Verification - Flag Secure - Biometrics after reboot
SAMSUNG GENERAL PATCHER V2.2 SUPPORT: TELEGRAM CHANNEL - TELEGRAM GROUP - SUPPORT ME ABOUT THIS: Magisk module to automatically patch the services.jar of Samsung devices, based on Dynamic Installer The compatibility is relative but Android...
forum.xda-developers.com
I know I can edit the policy.xml with tools like QPST, EFS Explorer, QFIL but I have yet to find anywhere that I can load the additional info for these bands.
Any help would be much appreciated