Develop Bugs

Updating baseband/modem WITHOUT flashing ROM - i.e. people running on CM12 - how to?

Hey guys,
Had a quick question that I hope somebody here can answer.
Want to update the baseband to the newest version contained in the .90 update but I'm running CM12. Obviously I don't want to go through the hassle of reflashing CM12, so want to flash the baseband through recovery/adb/fastboot if possible.
I understand that the baseband is in the ifwi.zip file within the update, and that within this zip are a few files in regards to each ZF2 model. The two files of importance are the ifwi*.bin and dnx*.bin files. From some searching it seems that these can be flashed through fastboot.
My questions are:
Which one is modem/baseband and which one is bootloader?
Can one be flashed without the other?
Cheers guys

So I did the following with the files from ifwi.zip
fastboot flash dnx dnx*ze551ml.bin
fastboot flash ifwi ifwi*ze551ml..bin
fastboot reboot-bootloader
Click to expand...
Click to collapse
The operation completed successfully, bootloader still unlocked and ROM still intact.
Doesn't look like baseband was updated though. Might be located elsewhere?

I thought CRPalmer included the binary updates in the latest CM. I have a baseband version of 1535_5.0.37.1_0831
What is the latest?

kylemd said:
.... Obviously I don't want to go through the hassle of reflashing CM12, so want to flash the baseband through recovery/adb/fastboot if possible.
Click to expand...
Click to collapse
What hassle? It takes about 5 minutes tops to download and dirty flash the latest CM build. You don't even need to connect to a PC - DL the file from the thread, reboot into TWRP, wipe cache/dalvik (from the advanced wipe menu, not sure wiping is really necessary but I always do), flash the CM build, reboot. Easy.

kylemd said:
So I did the following with the files from ifwi.zip
The operation completed successfully, bootloader still unlocked and ROM still intact.
Doesn't look like baseband was updated though. Might be located elsewhere?
Click to expand...
Click to collapse
file you are looking is in /vendor/firmware/telephony/*.fls
kylemd said:
So I did the following with the files from ifwi.zip
The operation completed successfully, bootloader still unlocked and ROM still intact.
Doesn't look like baseband was updated though. Might be located elsewhere?
Click to expand...
Click to collapse

alose said:
I thought CRPalmer included the binary updates in the latest CM. I have a baseband version of 1535_5.0.37.1_0831
What is the latest?
Click to expand...
Click to collapse
You are correct. I did ask in the thread whether this was the case and nobody answered, so I went to figure it out for myself.
Bootloader is updated by the ifwi files but not baseband. Baseband is part of the blob files comes with the ROM.
I am so used to devices having a separate baseband (Nexus, SGS etc) that it carried over to this phone - hence the thread.
kanagawaben said:
What hassle? It takes about 5 minutes tops to download and dirty flash the latest CM build. You don't even need to connect to a PC - DL the file from the thread, reboot into TWRP, wipe cache/dalvik (from the advanced wipe menu, not sure wiping is really necessary but I always do), flash the CM build, reboot. Easy.
Click to expand...
Click to collapse
I am aware of that, I do it every day I was thinking I might have needed to flash the stock ROM to update the baseband - of which I haven't seen a way to flash from TWRP recovery yet. Now aware this isn't the case as the baseband files are part of the blob files that are integrated into the ROM.
harpreet.s said:
file you are looking is in /vendor/firmware/telephony/*.fls
Click to expand...
Click to collapse
If I ever go to muck around with them this will be helpful thanks!

kylemd said:
So I did the following with the files from ifwi.zip
The operation completed successfully, bootloader still unlocked and ROM still intact.
Doesn't look like baseband was updated though. Might be located elsewhere?
Click to expand...
Click to collapse
Hmm.. I get this error while trying to flash this.
target reported max download size of 536870912 bytes
sending 'ifwi' (4096 KB)...
OKAY [ 0.312s]
writing 'ifwi'...
FAILED (remote: Permission denied
)
finished. total time: 0.499s

Bootloader unlocked?
Running it in bootloader mode?
Also make sure that you're running it for the right model.

yumms said:
Hmm.. I get this error while trying to flash this.
target reported max download size of 536870912 bytes
sending 'ifwi' (4096 KB)...
OKAY [ 0.312s]
writing 'ifwi'...
FAILED (remote: Permission denied
)
finished. total time: 0.499s
Click to expand...
Click to collapse
Try running as administrator. I'm not sure though.
Sent from my ASUS_Z00A using Tapatalk

I am running as an admin. So it looks like I Cait use fastboot at all, all commands show the same permission denied error.

yumms said:
I am running as an admin. So it looks like I Cait use fastboot at all, all commands show the same permission denied error.
Click to expand...
Click to collapse
and your phone's bootloader is unlocked? i think this is one of the most important thing if you wanna chenge baseband

Bootloader unlocked. I've installed TWRP previously so I'm not sure why this problem popped up all of a sudden.
Question, if I install the stock recovery and reinstall the stock rom with via adb sideload, will that update the modem?

Yumms, you've probably found out the hard way by now, but I believe it will
Sent from my ASUS_Z00A using Tapatalk

Calling not working in all custom roms [solved]

I have tried several custom roms (Oreo 8.1) like jaguar and AEX and calling is not working. It seems like the phone cannot connect to 3G.
4G is working.
In the stock rom everything is working.
My baseband version is 1.7.X as the roms requires.
I have used sim slot 1 and 2 without any luck.
I make a clean flash when i change rom.
Any suggestions on how to get calling working?

Flash stock zui 2.5 with qifl. It will work as I was having the same problem.

andreas951207 said:
I have tried several custom roms (Oreo 8.1) like jaguar and AEX and calling is not working. It seems like the phone cannot connect to 3G.
4G is working.
In the stock rom everything is working.
My baseband version is 1.7.X as the roms requires.
I have used sim slot 1 and 2 without any luck.
I make a clean flash when i change rom.
Any suggestions on how to get calling working?
Click to expand...
Click to collapse
Your baseband must be corrupted, flash 1.70 baseband.

cannot delete this comment?

ChetanLokhande said:
Your baseband must be corrupted, flash 1.70 baseband.
Click to expand...
Click to collapse
that did not work

AmaanRaza said:
Flash stock zui 2.5 with qifl. It will work as I was having the same problem.
Click to expand...
Click to collapse
Downgrade to 2.5 and then directly flash the custom ROM? Or should i update to latest zui oreo first?

andreas951207 said:
Downgrade to 2.5 and then directly flash the custom ROM? Or should i update to latest zui oreo first?
Click to expand...
Click to collapse
I think,
1. QFIL 1.9
2. Test if call working
3. Flash 3.5
4. OTA to latest
5. Unlock bootloader + TWRP
6. Flash Custom ROM
7. Test call now.

andreas951207 said:
Downgrade to 2.5 and then directly flash the custom ROM? Or should i update to latest zui oreo first?
Click to expand...
Click to collapse
Flash 2.5 through qifl then test if calls are working. If they are, then go back to custom roms. If they are not, update to 3.5.

andreas951207 said:
that did not work
Click to expand...
Click to collapse
Check if your efs partition is is fine. If it is corrupted then you have flash the xqcn file by editing it for your IMEI, there is one thread on that go through it.

Thank you for the help everyone. I found the solution after a long time.
Type this in fastboot:
fastboot -i 0x2b4c erase modemst1
fastboot -i 0x2b4c erase modemst2
fastboot -i 0x2b4c reboot

andreas951207 said:
Thank you for the help everyone. I found the solution after a long time.
Type this in fastboot:
fastboot -i 0x2b4c erase modemst1
fastboot -i 0x2b4c erase modemst2
fastboot -i 0x2b4c reboot
Click to expand...
Click to collapse
Did it worked I'm using a santoni,
For me the issue is that I cannot call a person perfectly (like my voice cuts everytime, and the other person can't hear all the words I spoke)
Will it be useful for that

Stuck at january patch

Im stuck at january security patch and my phone cant even find feb update , reflashed stock using miflash but the problem still there

I don't know if it's relevant to A2 Lite but A2 updates were rolled back since they were bricking devices.
Sent from my Mi A2 Lite using Tapatalk

catsh said:
Im stuck at january security patch and my phone cant even find feb update , reflashed stock using miflash but the problem still there
Click to expand...
Click to collapse
try taking your simcards out, unlock bootloader and flash the rom mi downloads(website), use flash all, but fastboot erase boot_b also, just add it to the bat file, then there should be absolute no problems in searching for update.

boe323 said:
try taking your simcards out, unlock bootloader and flash the rom mi downloads(website), use flash all, but fastboot erase boot_b also, just add it to the bat file, then there should be absolute no problems in searching for update.
Click to expand...
Click to collapse
I already did all that but the problem still there neither feb nor march update is found

[GUIDE] How to install Internal Android 10 build for Nokia 7.1

If you want to repost this internal OTA to other websites (other than XDA itself), please ask me for permission, thanks.
Click to expand...
Click to collapse
WARNING!
This is early internal test build, so LATER OTA UPDATES CAN'T BE GUARANTEED!
If you don't have unlocked bootloader, you'll unable to roll back to stable build!
Please be careful when testing!
Click to expand...
Click to collapse
Now I think it's time to bring you back to canary labs faster than beta labs.
Internal build version: CTL-4040-0-00WW-B01
It will be updated from: CTL-354K-0-00WW-B01, which is not pushed to public
As I've warned before - having an unlocked bootloader is strongly recommended.
So recent builds removed handy 874 dialing codes, we have to install them under recovery or Nokia Extensions.
UPDATE: Thanks everyone. To fix microphone bug, please disable the microphone permission of the "Google" app.
You'll lose "OK Google" ability, but you can make telephone call properly.
Click to expand...
Click to collapse
Let me tell you how to verify:
1. Dial *#*#227#*#* to check current Version. If older than CTL-354J-0-00WW-B01 (check if the letter is greater than J), update to 354J before proceed.
FYI, 354J is August 2019 Security Update.
Alternately, you can use command "fastboot oem getversions" under fastboot mode / Download mode to check current firmware version.
If newer than 354J (probably 354N when this post released), you'll need to downgrade your phone back to at most 354H - which can't be done easily without unlocked bootloader.
2. Install CTL-354K-0-00WW-B01-354J-0-00WW-B01-update.zip with Nokia Extensions OTA Update module or adb sideload under recovery.
3. Reboot your phone.
4. Install CTL-4040-0-00WW-B01-354K-0-00WW-B01-update.zip with Nokia Extensions OTA Update module or adb sideload under recovery.
5. Reboot your phone.
That's it.
If minor fixes released, I will upload them as well, then use the same method to install it.
To root the phone, you may want to use Magisk 20 released October 12th, 2019 or newer.
Download link:
Full OTA link (CTL-408B-0-00WW-B03-update.zip): https://android.googleapis.com/pack.../29ad191f90eedc643ed008dc06c81ed3c5b5565a.zip
Following link now discontinued.
https://www.androidfilehost.com/?w=files&flid=299362

Dude I Did Not Find TA-1097 NOKIA 7.1?

[email protected]! said:
Dude I Did Not Find TA-1097 NOKIA 7.1?
Click to expand...
Click to collapse
Packages are identical, regardless of TA-1085, 1095, 1096, 1097, 1100.

Anybody try this? It's everything ok? No issues?
Sent from my TA-1021 using Tapatalk

Support for Project Mainline?
Will this update (or perhaps a future update) for the Nokia 7.1 to Android 10 support Project Mainline?
I ask because I’ve read in some places that only devices that ship with Android 10 can support Project Mainline, and in other places that devices upgraded to Android 10 can support Project Mainline.

Hello, There is an issue with going from 4080 to 408A. Noticed it's also uploaded twice, but not sure what the issue is. I get a sideload package zip error.

hikari_calyx said:
Packages are identical, regardless of TA-1085, 1095, 1096, 1097, 1100.
Click to expand...
Click to collapse
How to get its TWRP image?

UPDATE:
1. To users who have installed 4090: Please rollback the phone to 408B B01, and wait for the full OTA link to 408B B03.
2. To users who have installed 408B B01: Please rollback the phone to 408A then install 408A to 408B B03 package instead.
3. To users who have 354P currently, you can update to 408B B03 directly.
You can confirm the current build by dialing *#*#7837#*#*, expected output should look like this:
Version: 00WW_3_54P-B01
Click to expand...
Click to collapse
How to rollback?
1. Enter fastboot mode / download mode
2. Check your current slot by using "fastboot getvar current-slot"
3. If current slot is A, then execute:
Code:
fastboot --set-active=b oem HALT
4. If current slot is B, then execute:
Code:
fastboot --set-active=a oem HALT
5. Disconnect the phone and boot to recovery mode.
6. To users rollback from 408B B01, you can apply update package to 408B B03 here. To users rollback from 4090 B01, you may perform factory reset.

Zip package ota Android 10?! Anyone? [emoji1]
Sent from my Nokia 7.1 using Tapatalk

Full OTA link:
https://android.googleapis.com/pack.../29ad191f90eedc643ed008dc06c81ed3c5b5565a.zip
CTL-408B-0-00WW-B03-update.zip

Thx Calyx, work on every 7.1? ta-1095?!
Sent from my Nokia 7.1 using Tapatalk

dex87xda said:
Thx Calyx, work on every 7.1? ta-1095?!
Sent from my Nokia 7.1 using Tapatalk
Click to expand...
Click to collapse
It works on any version of Nokia 7.1, regardless of TA-1085, 1095, 1096, 1097, 1100.

is there diffence between this OTA and updated with CTL-408B-0-00WW-B03-354P-0-00WW-B01-update.zip????
There is different file size??

No difference
Sent from my TA-1021 using Tapatalk

hikari_calyx said:
It works on any version of Nokia 7.1, regardless of TA-1085, 1095, 1096, 1097, 1100.
Click to expand...
Click to collapse
Hi. Can the stable OTA be sideloaded over any Android Pie version or do we specifically need to be on 3.54P?

I would greatly appreciate any direction attempting to move from 4080 to 408A. When I try to sideload with adb in recovery I'm getting a package zip error and it will not update. I do have an unlocked bootloader and I've tried resetting the phone with twrp but not having any luck.

i have version ctl-256a-0-00ww-b07 . i need a file to update to android 9 then 10 using ADB sideload method .. thx HIKari

Question Chinese version flashed OP 11 EU OTA rom but failed to update

Convert ColorOS to OxygenOS (OFP & OTA | Bootloader reLock & PIN working)
Update: 18th March 2023 **** Give Up **** I got so fedup and decided to goto HK and get my OnePlus 11, a real CPH2449 GLO. Paid and waiting to collect. I will not be update and maintaining this post from now on. Why give up? Minor issue like...
forum.xda-developers.com
Hi guys, i have flashed the CPH2449 EU rom 07 version following this guide. Today I tried to update to the 08 version, but it got in bootloop. After like 10 times reboot it booted into system (I was going to cry if it didn't) and said that the update failed. Did anyone encounter the same problem? thanks.

Did you flash oplusstanvbk.img?

yes, I have the same issue

yakming said:
Did you flash oplusstanvbk.img?
Click to expand...
Click to collapse
I did.
I meant that I flashed oplusstanvbk.img when I switched from ColorOs to HydrogenOs.
I didn't flash when I updated from 07 to 08 since what i did was an OTA update.

Are you using Ota method to flash Oxygen OS GDPR 13.0.0 A.08? Because it works for me.

yakming said:
Are you using Ota method to flash Oxygen OS GDPR 13.0.0 A.08? Because it works for me.
Click to expand...
Click to collapse
How did you do that?
Is your phone the Chinese version or global version?

I'm using Chinese version phone.
Already unlocked bootloader and fingerprint lock is working. Non-root btw.
I also have done "fastboot flash --slot=all my_preload images/my_preload.img" from CPH2449GDPR_11_A.06_2023010723370128.zip before update. Not sure it will contribute my success.
So i just follow Step 3 to Step 5 for update to A08. Before Step 4 i have done "fastboot --set-active=a". I'm not sure this extra step will help or not.
for oplusstanvbk.img, i'm using colorOS A08 Version.
In the end I have success without data lost and fingerprint lock still working. I also didn't lock the bootloader after update done.
Hope it helps.
I didn't flash when I updated from 07 to 08 since what i did was an OTA update.
Click to expand...
Click to collapse
You need to flash oplusstanvbk.img again after update. If not bootloop will happen.

yakming said:
I'm using Chinese version phone.
Already unlocked bootloader and fingerprint lock is working. Non-root btw.
I also have done "fastboot flash --slot=all my_preload images/my_preload.img" from CPH2449GDPR_11_A.06_2023010723370128.zip before update. Not sure it will contribute my success.
So i just follow Step 3 to Step 5 for update to A08. Before Step 4 i have done "fastboot --set-active=a". I'm not sure this extra step will help or not.
for oplusstanvbk.img, i'm using colorOS A08 Version.
In the end I have success without data lost and fingerprint lock still working. I also didn't lock the bootloader after update done.
Hope it helps.
You need to flash oplusstanvbk.img again after update. If not bootloop will happen.
Click to expand...
Click to collapse
Ok, I thought you directly updated from the settings. Your method did work. I flashed the firmware twice and oplusstanvbk.img.

jinglei207 said:
I did.
I meant that I flashed oplusstanvbk.img when I switched from ColorOs to HydrogenOs.
I didn't flash when I updated from 07 to 08 since what i did was an OTA update.
Click to expand...
Click to collapse
oplusstanvbk.img , should this img be oxygenos or coloros ?

sefai77 said:
oplusstanvbk.img , should this img be oxygenos or coloros ?
Click to expand...
Click to collapse
On china op11 what you have convertet to oos you have to flash the oplusstanvbk.img , from coloros back , when you flash this not back you have an bootloop (this you have to flash back after each oos update )

sefai77 said:
oplusstanvbk.img , should this img be oxygenos or coloros ?
Click to expand...
Click to collapse
I'd your is Chinese phone then cos's. I do not recommend to flash oos because it randomly shuts off!