Related
"NOST" - short for "No Service Tool" (or "Nokia Service Tool" but that sounds too official and boring ) is a small hobby project I've been working on in the last couple of days.
It aims to make the service tool for Nokia 8 (and HMD Phones in general) more useable, user-friendly, and straigtforward to use, and after having to test it myself, and also
making a small beta test in the Telegram group for Nokia 8, I feel like posting it here so others can try it out too if they want.
First, to be clear: NOST is not completely my work. It is based on OST LA 6.0.4, which was made by HMD/Foxconn. Unlike the previous OST Patches, NOST does not replace
the executable with a hacked one, but instead wraps it and patches the methods that need patching at runtime. The result is that the changes are completely opensource
and readable by others, while the underlying OST files are not modified at all. I tried to base it on a different (i.e. newer) version of OST, but those are pretty much unpatchable,
at least not with a serious amount of reverse engineering, which brings not only time issues but legal ones as well.
NOST changes a couple of things, compared to the unmodified OST LA:
It removes the need for authentification against HMD/FIH servers (really, shoutout to the one who made the original hack, even though I could not use their code)
Moved the logs folder to the same folder as the application, as opposed to somewhere on the system to make debugging easier
The options for flashing firmware images appear reliable now. (At least for me they only appeared sometimes if not never on the original OST).
Removed one of the options that if it appeared crashed the flashing process ("Check System AP Status")
One user of the Telegram group had issues where OST would crash because it detects an invalid locale setting in Windows. NOST just catches that issue and defaults to english
Removed the "Edit Phone Information" button. It never worked and it's only purpose was to make the "Next" button appear, which works like it should now as well.
NOST refuses to flash your phone if your bootloader isn't unlocked critically. The old OST would just try to flash but never make any progress which confuses inexperienced users.
Perhaps the most important change: NOST allows to flash modified firmware images without the need to extract and modify them by hand.
With the original OST, people who wanted to reflash their phone had to download a firmware bundle, extract and edit it to be able to use it with OST LA 6.0.4, since the newer versions
had unpatchable issues that prevent using them. Repacking the images in a format OST expects wasn't possible either since that enabled some sort of signature algorithm on the modified
images and caused the flashing to fail. NOST solves this problem by allowing the use of a different packaging format. Those binaries still need to be extracted but it is done transparently in
the background without the user having to download any other tools. The formats that can be used in images are .zip and .qlz
.zip Firmwares:
.zip firmware files are simply archives of the (edited) files that would normally be extracted from an .nb0 file. This means, if you extract a .nb0 with the extractor found on XDA, the contents
of the *_unpacked folder it creates should be the contents of your .zip.
.qlz Firmwares:
.qlz files are based on QuickLZ compression, which gives them a small size but also a low decompression time.
The tool to generate them is called exdupe. Generating these images is pretty straigtforward. Assuming you are on windows, download the exdupe
tool from the link above (or take it from the NOST Tools/ folder) and copy it into the folder that contains the unpacked .nb0.
Code:
- exdupe.exe
- <nb0 name>_unpacked/
- <nb0 name>.mlf
- ....
Open a commandline in that folder, and run the following command:
Code:
exdupe.exe <name of the folder to compress> <name of the firmware file>.qlz
You should already see how fast it compresses the firmware folder now. As a reference: Compressing the latest Nokia 8 firmware (about 4GB) takes maybe 30 seconds and yields a 2GB file.
Repacked Firmware Bundles:
I created .qlz images of the May and November firmwares, as well as one of the various Pie Maintainance Releases.
You can find them here: https://tmsp.io/fs/xda/nb1/firmware
I already successfully reverted from December Security Patch to November using NOST, and then updated back using OTA Sideloading without problems.
As always when working with flashing tools, proceed with caution!
How to unlock to critical:
KonikoO said:
For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
Click to expand...
Click to collapse
Download:
The actual tool: https://github.com/StollD/NOST/releases
Drivers: https://github.com/StollD/nokia-driver-installer/tree/master/out
Source Code: https://github.com/StollD/NOST
License:
OST LA 6.0.4 is copyrighted by the respective authors. It is not modified permanently.
The custom NOST code is licensed under the GNU General Public License.
Icon by Freepik © Flaticon
I tried this is working,nice tool.
Thanks dev.
Thank you THMSP! very cool?
Sent from my TA-1004 using XDA Labs
Can flash the May and November update but cannot flash latest Pie with this tool. I flashed Pie but returned back to November update?
Lee Castro said:
Can flash the May and November update but cannot flash latest Pie with this tool. I flashed Pie but returned back to November update?
Click to expand...
Click to collapse
Yes, you can revert back from Pie to Oreo using this. What is the issue with Pie for you?
THMSP said:
Yes, you can revert back from Pie to Oreo using this. What is the issue with Pie for you?
Click to expand...
Click to collapse
What I mean is if I flash the Pie file you provided I just returned back to Android 8.1 Novemeber update no changes at all. Maybe there something wrong with the Pie file you uploaded. But the rests are all working fine with the tool.
Lee Castro said:
What I mean is if I flash the Pie file you provided I just returned back to Android 8.1 Novemeber update no changes at all. Maybe there something wrong with the Pie file you uploaded. But the rests are all working fine with the tool.
Click to expand...
Click to collapse
Thanks for the hint, I will take a look. Probably just derped when pulling partitions and renaming the images (might have worked in my November folder by accident).
EDIT: I repulled the images from Pie (I indeed somehow worked in my November folder when making the image), repackaged them and updated the version in the drive folder. You should now be able to flash Pie. Sorry for the mistake.
THMSP said:
Thanks for the hint, I will take a look. Probably just derped when pulling partitions and renaming the images (might have worked in my November folder by accident).
EDIT: I repulled the images from Pie (I indeed somehow worked in my November folder when making the image), repackaged them and updated the version in the drive folder. You should now be able to flash Pie. Sorry for the mistake.
Click to expand...
Click to collapse
Thanks again,This is really a big help.
Wow, this is something we've been all seeking for a long time now ! For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
hey there! wonderful tool to have. Thank u so much
Not working in my laptop say a software need a to update
Blackhacker07 said:
Not working in my laptop say a software need a to update
Click to expand...
Click to collapse
If you have dependency issues I would suggest to install OST LA 6.0.4 first, so you get its dependencies, until I can make a proper installer for NOST.
THMSP said:
If you have dependency issues I would suggest to install OST LA 6.0.4 first, so you get its dependencies, until I can make a proper installer for NOST.
Click to expand...
Click to collapse
Could you perhaps figure out how to get rid of the unlocked bootloader message?
ironman38102 said:
Could you perhaps figure out how to get rid of the unlocked bootloader message?
Click to expand...
Click to collapse
Are you talking about the error message that appears when you press the Next button to start flashing?
If yes, your bootloader needs to be unlocked to critical, then the message won't appear.
If you are unsure if your bootloader is unlocked to critical, do "fastboot oem device-info", it will tell you.
If you mean the message that your phone displays when booting with an unlocked bootloader then sorry, I doubt that's possible (I think it is embedded into the bootloader).
THMSP said:
Are you talking about the error message that appears when you press the Next button to start flashing?
If yes, your bootloader needs to be unlocked to critical, then the message won't appear.
If you are unsure if your bootloader is unlocked to critical, do "fastboot oem device-info", it will tell you.
If you mean the message that your phone displays when booting with an unlocked bootloader then sorry, I doubt that's possible (I think it is embedded into the bootloader).
Click to expand...
Click to collapse
Actually its in splash.img that can be dumped. Its the hex editing possibly that might be a problem for someone not familiar with it
How to flash it's says this...
Blackhacker07 said:
How to flash it's says this...
Click to expand...
Click to collapse
What do you mean?
KonikoO said:
Wow, this is something we've been all seeking for a long time now ! For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
Click to expand...
Click to collapse
Thank you so much for this advice. I wouldn't have ever figured out how to unlock critical on my own and that was the thing that was preventing me from flashing. I tried searching the other OST LA flashing threads as well but this info seemed to have been missing, or then i completely missed it. Thank you so much anyways. If anybody else is trying to figure out why their OST LA or NOST is giving them the se_err_adb_cmd_get_fail_result error, this should help. I just used the unlock.key in place of the *unlock.bin* in your command and it worked.
Can you please upload Oreo December update stock and patched boot image. TIA
Yesterday I noticed that my Pie Image was still not quite useable, since it contained a corrupted system partition.
This seems to have happened because of my Magisk Setup and me only replacing the boot partition image and not uninstalling Magisk completely.
I rebuilt the image, to be fully stock, and also included the latest B07 update that @hikari_calyx uploaded yesterday. You can get it from the drive link in the OP.
Just to add my experience here, I flashed MARS_SOM magisk rom module which entered a seemingly unrecoverable endless bootloop. This was likely as it conflicted with another magisk module or xposed that I have installed, so not the fault of the rom!
However given we've no twrp yet, the best way (after a LOT of research!) to fix this wasn't easy or obvious. I thought I could just flash stock kernel, uninstall magisk, flash magisk again and uninstall the module. Which unfortunately you can't as they remain in the system files and without root, you can't touch them, though with root, it loads and you get the bootloop - so a vicious endless cycle!
The solution I managed to work out, rather than a full clean wipe was to extract the stock boot from downloaded firmware (using Xperifirm), convert it to an img file using UnSIN, use to unpack, place a certain folder in there (found via the link below), repack and then fastboot flash. This makes magisk operate in core root mode only allowing you to uninstall the module. Once the module is uninstalled, you can simply disable core only mode from the magisk settings.
This saved me from a full wipe!
See here for more details about that unpacking the img, copying a folder etc see here:
https://forum.xda-developers.com/pi...modules-disabler-booting-magisk-t3976621/amp/
This worked for me and so hope it helps someone out too!
cd993 said:
Just to add my experience here, I flashed MARS_SOM magisk rom module which entered a seemingly unrecoverable endless bootloop. This was likely as it conflicted with another magisk module or xposed that I have installed, so not the fault of the rom!
However given we've no twrp yet, the best way (after a LOT of research!) to fix this wasn't easy or obvious. I thought I could just flash stock kernel, uninstall magisk, flash magisk again and uninstall the module. Which unfortunately you can't as they remain in the system files and without root, you can't touch them, though with root, it loads and you get the bootloop - so a vicious endless cycle!
The solution I managed to work out, rather than a full clean wipe was to extract the stock boot from downloaded firmware (using Xperifirm), convert it to an img file using UnSIN, use to unpack, place a certain folder in there (found via the link below), repack and then fastboot flash. This makes magisk operate in core root mode only allowing you to uninstall the module. Once the module is uninstalled, you can simply disable core only mode from the magisk settings.
This saved me from a full wipe!
See here for more details about that unpacking the img, copying a folder etc see here:
https://forum.xda-developers.com/pi...modules-disabler-booting-magisk-t3976621/amp/
This worked for me and so hope it helps someone out too!
Click to expand...
Click to collapse
With Unsin (on windows at least) you can just drag your file over the cmd without having to mess with command lines
AJHutchinson said:
With Unsin (on windows at least) you can just drag your file over the cmd without having to mess with command lines
Click to expand...
Click to collapse
Yeah that's a handy little feature, makes converting it super simple!
cd993 said:
Just to add my experience here, I flashed MARS_SOM magisk rom module which entered a seemingly unrecoverable endless bootloop. This was likely as it conflicted with another magisk module or xposed that I have installed, so not the fault of the rom!
However given we've no twrp yet, the best way (after a LOT of research!) to fix this wasn't easy or obvious. I thought I could just flash stock kernel, uninstall magisk, flash magisk again and uninstall the module. Which unfortunately you can't as they remain in the system files and without root, you can't touch them, though with root, it loads and you get the bootloop - so a vicious endless cycle!
The solution I managed to work out, rather than a full clean wipe was to extract the stock boot from downloaded firmware (using Xperifirm), convert it to an img file using UnSIN, use to unpack, place a certain folder in there (found via the link below), repack and then fastboot flash. This makes magisk operate in core root mode only allowing you to uninstall the module. Once the module is uninstalled, you can simply disable core only mode from the magisk settings.
This saved me from a full wipe!
See here for more details about that unpacking the img, copying a folder etc see here:
https://forum.xda-developers.com/pi...modules-disabler-booting-magisk-t3976621/amp/
This worked for me and so hope it helps someone out too!
Click to expand...
Click to collapse
Hi there; I was in the same situation, flashing a corrupted magisk boot image from standard firmware for XQ-AT51, provided by same author for simple rooting Xperia 1 II; my phone was without xposed, it was in clean factory state. the magisk boot image was taken from another thread "[ROOT] Magisk patched Boot Images & Instructions" designated for rooting of Xperia 1 II;
unfortunately is the same author who build your ROM, he delivered also corrupted magisk image.
It was not enter in bootloop if you flash only one image on phone, not both; his instructions are wrong. the correct flashing instruction is below, at end of my comment.
I solved in smilar way like you: using flashtool to obtain XQ-AT51 ftf file: XQ-AT51_58.0.A.3.39_1321-7706_R13A.ftf;
Attention: the name of file depends of region firmware you want to flash and type of phone (single or dual sim); the given names are with title of example.
Then from download folder of flashtool form your disk C:\Users\username\.flashTool\firmwares\Downloads (username is your username on pc); check for file: boot_X-FLASH-ALL-2389.sin ( applicable for XQ-AT51) and convert the file to .img using unsin; check on xda for unsin, extract unsin archive in exe file and then drag & drop over unsin.exe the file boot_X-FLASH-ALL-2389.sin; will be generated boot_X-FLASH-ALL-2389.img file.
This name file can be other, is just an example, if you have another phone with firmware for other region, pay attention to this!
This can be flashed then back to phone using adb comands; fastboot flash boot boot_X-FLASH-ALL-2389.img;
The same image can be transfered to phone and used later to generate correct magisk image and root the phone.
Best to you all!
daphix said:
Hi there; I was in the same situation, flashing a corrupted magisk boot image from standard firmware for XQ-AT51, provided by same author for simple rooting Xperia 1 II; my phone was without xposed, it was in clean factory state. the magisk boot image was taken from another thread "[ROOT] Magisk patched Boot Images & Instructions" designated for rooting of Xperia 1 II;
unfortunately is the same author who build your ROM, he delivered also corrupted magisk image.
It was not enter in bootloop if you flash only one image on phone, not both; his instructions are wrong. the correct flashing instruction is below, at end of my comment.
I solved in smilar way like you: using flashtool to obtain XQ-AT51 ftf file: XQ-AT51_58.0.A.3.39_1321-7706_R13A.ftf;
Attention: the name of file depends of region firmware you want to flash and type of phone (single or dual sim); the given names are with title of example.
Then from download folder of flashtool form your disk C:\Users\username\.flashTool\firmwares\Downloads (username is your username on pc); check for file: boot_X-FLASH-ALL-2389.sin ( applicable for XQ-AT51) and convert the file to .img using unsin; check on xda for unsin, extract unsin archive in exe file and then drag & drop over unsin.exe the file boot_X-FLASH-ALL-2389.sin; will be generated boot_X-FLASH-ALL-2389.img file.
This name file can be other, is just an example, if you have another phone with firmware for other region, pay attention to this!
This can be flashed then back to phone using adb comands; fastboot flash boot boot_X-FLASH-ALL-2389.img;
The same image can be transfered to phone and used later to generate correct magisk image and root the phone.
Best to you all!
Click to expand...
Click to collapse
Thanks for that, glad you managed to fix your situation too!
cd993 said:
Thanks for that, glad you managed to fix your situation too!
Click to expand...
Click to collapse
What to posted you is very very usefull; it helps you to fix after flashing wrong magisk module.
:good:
IF YOUR BOOTLOADER IS NOT ALREADY UNLOCKED, THIS GUIDE IS NOT FOR YOU.
READ EVERYTHING AT LEAST ONCE BEFORE PROCEEDING!
THIS GUIDE WORKED GREAT FOR AT LEAST 3 PERSONS, THIS DOESN'T MEAN IT WILL WORK ON YOUR PHONE.
This guide exist in case the ULM Q never released
This guide should do the following :
relocalize to your country (I'm only providing the files for canada, usa and eu)
Root and TWRP (useful if any custom roms get released)
debloating
volte/vowifi/vilte/viwifi
Very Good battery (see screenshots down below)
mute shutter camera
4k 60fps video recording (?some people said it wasn't available on the korean Q?)
wifi tethering
and more
WHAT'S NOT WORKING FOR ME :
lg smartworld : meaning no lg app update.. which can lead to the next problem
Drag down for search : working only if you do not update the google app
What you need:
1 to 2hrs of free time
Working QFIL with minimal knowledge
Working Fastboot on your pc (See spoilers)
I did NOT manage to make fastboot work on my amd ryzen pc (3600)
here's what I tried :
- multiple fastboot drivers
(fastboot was kinda working.. now it just never load any driver)
- plugged in a usb 3.0 hub
- FWUL : https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
(the latest version as of 2020-11-25 couldn't even boot on this pc...)
- ubuntu
(crashed the phone to a gray screen)
- all my usb ports : 2, 3 and 3.1 What I didn't try but could work for you:
- plugged in a usb 2.0 hub
- linux mint?
Soo... what did I do? I went back to my good ol' intel pc running windows 10 worked like a charm.
Click to expand...
Click to collapse
Also, this guide assume you had working volte/vowifi on your phone at some point...
Because, you will need the carrier folder from the /oem/op/ folder.. should look like this : open_us, vrz_us, open_ca..
Or you will need to retrieve it from your working firmware...
I'll be providing :
- Android 10 - G7 - OPEN_CA (Canadian operator folder) (What I'm using on my phone right now)
- Android 9 - V35 - OPEN_US (ULM/GFi) (Confirmed working by @cmrntnnr)
- Android 10 - G7 - OPEN_EU (untested) (thanks @vlad48)
!!!!!! Before crossflashing to the korean kdz !!!!!!
------------------------------------------------------------------------
Crossflashing can break stuff sometime.. it is advised to do a full backup of your phone using https://github.com/bkerler/edl
if you're feeling lucky and do not want to do a full backup... you should still use qfil to atleast backup the following VITAL partitions : Fsg, modem, modemst1&2, ftm
STORE THOSE FILES PRECIOUSLY
------------------------------------------------------------------------
File you need to download :
To your phone SDCARD :
OPEN_CA or OPEN_US or OPEN_EU (untested) (Decompress this file, delete the zip)
OPEN_CA is too big, I had to delete apks that weren't from my carrier. (Bell)
(open_ca/apps/ -> kept only bell apks)
debloated-priv-app-RENAME-ME.zip (Decompress this file, delete the zip)
debloated-app-RENAME-ME.zip (Decompress this file, delete the zip)
twrp-installer-v3.3.1-v35_a.zip
Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
Magisk
(OPEN_EU only) : voenabler-v1.8.zip
To your pc:
vbmeta.img
30b_boot_magisk.img
30b_abl.bin (shouldn't be needed, but provided as backup)
Korean Q 30b (I went with LGU_KR since the other one weren't available back then)
The V35 engineering abl you got from here : https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
This file was renamed to engabl.bin in this guide
You need to use SOLID EXPLORER, not esfile or any other since I can not guaranteed it will apply the correct permission to the files and folder.
LGUP > Flash V350N30b_00_LGU_KR_OP_1015.KDZ using partition DL, select everything except FTM
Let the phone boot for the first time and reach setup screen
LGUP > refurbish phone using the kdz (this should fix potential nt error when booting the phone, it did for me)
Let the phone boot for the first time and setup the phone quickly so you can install app. (no lock or fingerprint)
Patching vbmeta to edit the operator/carrier information & patching boot for magisk/root
QFIL > partition manager > abl_a > read, store that file and name it : needed_abl.bin
How to retrieve the file: WIN+R , %AppData%/Qualcomm/QFIL , enter, pick right folder, save and rename bin file
QFIL > partition manager > abl_a > load > engabl.bin (for fastboot)
QFIL > partition manager > abl_b > load > engabl.bin (for fastboot) (Optional)
This is useful in case you need fastboot in the future, simply boot twrp then change slot from a to b and reboot.
To switch back from fastboot : fastboot --set-active=a
reboot the phone using vol- + power
command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot oem edl
QFIL > partition manager > abl_a > load > needed_abl.bin
QFIL > partition manager > boot_a > load > boot_magisk.img
reboot by holding vol- + power
[*]
Click to expand...
Click to collapse
Reboot to system, Install magisk manager and solid explorer
Start magisk manager and let it reboot your phone
magisk > modules > install from storage > twrp-installer-v3.3.1-v35_a.zip
SOLID EXPLORER > copy the carrier folder to the oem/op/ partition ('OPEN_CA' in my case)
SOLID EXPLORER > edit oem/op/cust_path_mapping.cfg and replace LGU_KR with OPEN_US ('OPEN_CA' in my case)
If you're still getting nt error at boot, you'll have to fix it in order to make the phone load open_us..
try adding a second line like this :
FFFFFF,84=/oem/OP/OPEN_US
If this doesnt do it, you'll have to share your nt error in the comment.
Click to expand...
Click to collapse
SOLID EXPLORER > Rename the folder /oem/op/LGU_KR to LGU_KRori (this will make your phone lag/glitch/freeze real quick.. proceed with the next step ASAP)
Quickly go in magisk and use the reboot menu to get to twrp. (reboot to recovery)
Format data
Reboot to TWRP/recovery
Flash Magisk-v21.1.zip, if it doesn't flash, reboot using the reboot menu to TWRP/recovery again until it works. (no red text)
Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
Reboot to system
if the vowifi toggle is not working for you
For OPEN_CA/OPEN_US :
SOLID EXPLORER > move debloated-priv-app-RENAME-ME to /oem/op/priv-app/
SOLID EXPLORER > Rename the new folder to OPEN_US or OPEN_CA
Reboot
Click to expand...
Click to collapse
FOR OPEN_EU : (these steps are from the v40 community telegram, Quote from Lucky)
magisk > modules > install from storage > voenabler-v1.8.zip
If you transplant the KR OP with OPEN_EU, and are based in EU, this module should add the props that enables the VoLTE and VoWifi options.
Only if this fails, do you need to tinker with the xml files.
Click to expand...
Click to collapse
Optional.
Adding back missing lg apps (I provide QMemo and LG Weather)
you can either install manually the apk from debloated-app-RENAME-ME
or
move the folder to oem/op/app/ and rename it OPEN_CA or OPEN_US
Click to expand...
Click to collapse
Enable LGMessage over Google message and add back LGFMRadio (you'll need to uninstall any sms app you might have installed.. like google message or fb messenger(if used for sms))
Solid Explorer
edit this file /oem/op/open_us/config/custom_apk_list.cfg
change the sign on the following lines (from - to + and + to -)
-com.lge.fmradio:/system/product/priv-app/LGFmRadio
-com.android.mms:/system/product/priv-app/LGMessage
-/system/app/SmartMessagingEngine
+com.google.android.apps.messaging:/system/app/Messages
Example
-/system/app/SmartMessagingEngine
to
+/system/app/SmartMessagingEngine
Reboot
Click to expand...
Click to collapse
Do not forget to enable developer option and adb AND
Plug you phone in computer, open adb shell and type su
on the phone, grant root.
It is useful to have a root shell in case the phone is stuck while booting (not boot looping)
you can also just reboot to twrp and undo your modification from there.
Click to expand...
Click to collapse
Thanks to everyone patient enough to answer my questions and who did provide most of the solution for this guide:
vlad48, Lucky, azitlies, xsavi, kaneorotar and many more..
Thanks for the guide
alonzo_ama26 said:
Thanks for the guide
Click to expand...
Click to collapse
No prob!
Added OPEN_EU files, but they are untested.. no clue if everything will work... Some people in the v40 community got it to work
Good luck everyone
I've completed all the steps (except for lg weather) and I didn't notice anything different in call features until I saw the description of the international roaming setting referenced "outside of US PR etc." instead of "outside of foreign territory or whatever" which indicates a success.
Then I Applied the vomaster.zip from somewhere else (prob the same thing as the OP's not sure) and flipped on wificalling on the settings and got the setup prompt for wificalling from my carrier and later a "wifi setup's been completed" notification, so I guess things are finally good again. Unfortunately RCS doesn't seem to want to cooperate either way =\
Not sure why I did it because korean q on its own was usable, but I did it it anyway and it is nice, performance feels better too but this could be because I went from LG firmware to open_us. Both the incoming and outgoing calls and texts feel much snappier as well and doesn't take 5 seconds to go anywhere. Also it doesn't ask me whether I want to listen to the call recording or not at the end of every phonecalls so that's nice. thank you
-edit
one question, is there any way I can use the korean AOD's? I liked the one that shows calendar and time.
issc said:
I've completed all the steps (except for lg weather) and I didn't notice anything different in call features until I saw the description of the international roaming setting referenced "outside of US PR etc." instead of "outside of foreign territory or whatever" which indicates a success.
Then I Applied the vomaster.zip from somewhere else (prob the same thing as the OP's not sure) and flipped on wificalling on the settings and got the setup prompt for wificalling from my carrier and later a "wifi setup's been completed" notification, so I guess things are finally good again. Unfortunately RCS doesn't seem to want to cooperate either way =\
Not sure why I did it because korean q on its own was usable, but I did it it anyway and it is nice, performance feels better too but this could be because I went from LG firmware to open_us. Both the incoming and outgoing calls and texts feel much snappier as well and doesn't take 5 seconds to go anywhere. Also it doesn't ask me whether I want to listen to the call recording or not at the end of every phonecalls so that's nice. thank you
-edit
one question, is there any way I can use the korean AOD's? I liked the one that shows calendar and time.
Click to expand...
Click to collapse
odd! you really shouldn't have to flash that vomaster.zip at all if you're located in the US.. honestly.. I don't even know if rcs is available in canada and I'm really not sure how to test this feature.. You might have to toggle wifi calling again if you got the wifi calling activation success notification.. it was the case on my friend phone..
Just to confirm...
volte/vowifi working?
ulm or awm?
carrier?
Looks like the calendar is available with the open_ca files... not sure for the open_us.. sorry..
[ATTACH
cloud1250000 said:
The V35 engineering abl you got from here : https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
This file was renamed to engabl.bin in this guide
Click to expand...
Click to collapse
That file is a zip file with two different files in it, do you mean to rename this zip file to engabl.bin?
After step 5 I started to get some weird outputs.
fastboot.exe oem edl
FAILED (Status read failed (Too many links))
fastboot: error: Command failed
Click to expand...
Click to collapse
Seems like that output is normal because I have the rom rooted and twrped right now but I did have to change the active slot to B at this point because otherwise QFIL wasn't able to read the partitions afterwards. Oddly enough that was the only change I had to make, every other command worked as is referencing abl_a even though I changed the active slot to B (and when I flipped the steps to target slot B instead I just got bootlooped).
Everything's looking good so far. I had not been able to setup twrp on this phone so that's welcome. Hotspot wasn't working on Oreo either so that's another good improvement at least for me. Hopefully, this update ends up being a little bit more stable than Pie.
rpgdev said:
That file is a zip file with two different files in it, do you mean to rename this zip file to engabl.bin?
Click to expand...
Click to collapse
omg no, pick one of the 2 files and rename it to engabl.bin
Blad2301 said:
[ATTACH
Click to expand...
Click to collapse
??????
rpgdev said:
After step 5 I started to get some weird outputs.
Seems like that output is normal because I have the rom rooted and twrped right now but I did have to change the active slot to B at this point because otherwise QFIL wasn't able to read the partitions afterwards. Oddly enough that was the only change I had to make, every other command worked as is referencing abl_a even though I changed the active slot to B (and when I flipped the steps to target slot B instead I just got bootlooped).
Everything's looking good so far. I had not been able to setup twrp on this phone so that's welcome. Hotspot wasn't working on Oreo either so that's another good improvement at least for me. Hopefully, this update ends up being a little bit more stable than Pie.
Click to expand...
Click to collapse
sometime, with both fastboot and qfil/edl.. you need multiple try to get them working
cloud1250000 said:
omg no, pick one of the 2 files and rename it to engabl.bin
Click to expand...
Click to collapse
that's somewhat ambiguous, I ended up putting the abl_a in the a slot and the abl_b in the b slot. Not sure if they're interchangeable or if that's the reason why I experienced the issue I experienced. Shouldn't be but who knows.
I'm noticing that locking the screen takes a while using double tap. At least a second or more before the phone responds and actually locks the screen, is anyone else experiencing this?
rpgdev said:
I'm noticing that locking the screen takes a while using double tap. At least a second or more before the phone responds and actually locks the screen, is anyone else experiencing this?
Click to expand...
Click to collapse
that's odd mine is almost instantly..
cloud1250000 said:
that's odd mine is almost instantly..
Click to expand...
Click to collapse
Apparently it was due to my launcher, they're having some issues with that gesture on Android 10.
The Korean Q is solid, I'm surprised that it's performing better than Pie on this phone. Thanks for doing this guide. Anyways, I still get the camera shutter sound any idea as to why? Also, is there a way to disable the vibration for the fingerprint reader when the read is successful? I managed to do it for Oreo but haven't found a way to do it for Q
rpgdev said:
Apparently it was due to my launcher, they're having some issues with that gesture on Android 10.
The Korean Q is solid, I'm surprised that it's performing better than Pie on this phone. Thanks for doing this guide. Anyways, I still get the camera shutter sound any idea as to why? Also, is there a way to disable the vibration for the fingerprint reader when the read is successful? I managed to do it for Oreo but haven't found a way to do it for Q
Click to expand...
Click to collapse
shutter is muted when I'm on vibration mode
cloud1250000 said:
shutter is muted when I'm on vibration mode
Click to expand...
Click to collapse
Ah, I thought it disabled it on all modes. I didn't get it on vibration. Would be nice to disable it on every mode.
Right the thing with the korean firmware usually is.. it's not disabled even in silent mode lol
cloud1250000 said:
Right the thing with the korean firmware usually is.. it's not disabled even in silent mode lol
Click to expand...
Click to collapse
I see, do you happen to know where is the camera shutter sound now? It used to be \system\media\audio\ui\ but it seems that dir was removed on A10.
cloud1250000 said:
odd! you really shouldn't have to flash that vomaster.zip at all if you're located in the US.. honestly.. I don't even know if rcs is available in canada and I'm really not sure how to test this feature.. You might have to toggle wifi calling again if you got the wifi calling activation success notification.. it was the case on my friend phone..
Just to confirm...
volte/vowifi working?
ulm or awm?
carrier?
Looks like the calendar is available with the open_ca files... not sure for the open_us.. sorry..
Click to expand...
Click to collapse
I don't know how to check for volte working, but vowifi is def working at my work with ****ty at&t signals.
awm -> ulm -> korean q.
I get advanced chat features enabled but nothing works =/ maybe its fixable with googling but im reasonably happy with my phone atm, minus lgpay not being accessible for v35 and v30s outside of korea =\
Has anyone passed safetynet using this rom? Some pointers would be appreciated.
MAJOR UPDATE: Managed to flash Global stock rom to the MetroPCS variant
Pros: Stock Oneplus and everything works
Cons: OEM unlock is still greyed out
Before you go any further:
THERE IS NO ROOT FOR THIS DEVICE WITH A LOCKED BOOTLOADER (YET). THIS THREAD IS FOR THE DEVELOPMENT AND TESTING OF METHODS TO ACHIEVE THIS.
Just got this device from MetroPCS this week and love this device. However I found out very quick that you have to be with MetroPCS for 180 days before you can get unlocked. To unlock the bootloader you have to be sim unlocked from the carrier.
This thread will be for development of a working root process for others to offer perspective. Feel free to try to replicate at your own risk. If anyone is interested in these files/tools let me know and I will publish more links.
;Download international and metro ROM and MSM tool from these thread (thanks to @Some_Random_Username)International
MetroPCS
This download will include the latest MSM Download Tool
The work around that I found does not need MSM to be patched
;TOOLS
download and extract oppo decrypt master
unpack and repack .OPS files for use with MSM Download Tool 4 .exe
----------------------------------------------------------------------------------------------------------------------------------------------
Method----------------------------------------------------------------------------------------------------------------------------------------------
TD;RL:
Extract the .ops file, open settings.xml replace the project ID, repack
Set up:
1. Download international zip and metro zip from above, extract into 2 seperate folders and delete billie8t_14_O.01_201218.ops in the metro folder
2. have adb installed
3. Install python3 and prereqs for oppo decrypt master
Extract .ops, edit and flash:
1. unzip the zip file with the .ops file from both folders and move it to the folder with oppo decrypt
2. run "python3 opscrypto.py decrypt billie8_14_O.01_210128.ops" (decrypt both .ops files from each firmware, the first one being the metro and get the /extract/settings.xml file and open it. we will need info from it)
3. Now extract the international firmware with opoo decrypt and open the extract folder
4. open "settings.xml" from both firmwares in your favorite editor
6. Change the following in the international settings.xml: Project=20886 to Project=20885 and ModelVerifyRandom= (THESE NEED TO BE EXACTLY WHAT ARE IN THE METRO SETTINGS.XML file)
6. Save the file
7. run "python3 opscrypto.py encrypt extract". This will create a file called out.ops
8. Once finished place out.ops into the metro firmware folder and rename to "billie8t_14_O.01_201218.ops"
9. With your phone turned on, plug your phone into the computer
10. Open MSMdownloadtoolv4.0.exe and press start
11. Run "adb reboot edl"
12. Your computer should recognize and start the download.
13. Wait a while and it will reboot.
Here is my working files for anyone who wants to tinker
Includes MSMdownloadtools, modded OPS file and (edited settings.xml and patched recovery.img inside OPS)
Updated downloads include:
Decrypted Metro OPS (IMGs, BIN, etc)
Metro to Global (OPS)
Metro to Global w/ magisk patched recovery (ZIP)
Google Drive - Updated 7/11/2021
Hi!,
Did you try this method:
Root N10 using Magisk
Warning: I'm not responsible for any damage or bricked phones! Mirror for all OxygenOS images General Info: You need adb and fastboot installed and should know how to use it TWRP is not needed You must do this process only once...
forum.xda-developers.com
?
I have reviewed that method, however it seems to only work with the EU and Global version of the phone. With the US version being on TMobile or MetroPCS (which is owned by TMobile) the "OEM" unlock is greyed out.
To be able to unlock the bootloader I have found that you have to do the following:
1. On MetroPCS you have to have the phone for 180 days.
2. Once that 180 days is up you have to apply to get the device unlocked from their network.
3. After the device gets unlocked from the network you can then use "OEM unlock" in the settings.
4. Then you have to apply to OnePlus with IMEI, serial and unlock code (fastboot get_unlock_code)
5. Wait a week
6. They send you the unlock.
To me this is ridiculously convoluted.
I don't want to have to wait 6 months to start modding
Some other OnePlus devices (6t Tmobile specifically), you use a patched/modified MSM tool to flash the firmware, and it bypasses the device checking if its meant for the device or not. From there, you can unlock the bootloader and you're all set.
Try that, link to the 6t instructions below, I'd wonder if it works on the n10. If I had a carrier locked one, I'd try it, but I got my n10 5g from an amazon return pallet lol
T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)
In the previous thread, we discussed a method to convert T-Mobile 6T's to the international variant, sort of, but it required an unlocked bootloader, which itself requires a SIM unlock which T-Mobile gives people a hard time about. However, it...
forum.xda-developers.com
Thank you. Will give it a shot. Are the MSM download tool specific to the device? If not I will give this a shot tomorrow. Any idea how it is patched?
I believe MSM tool is device specified. So I assume you use the Metro MSM and load a modified .OPS from US Retail unlock model? or anything I'm missing? I don't think MSM is included in official oneplus firmware zip.
MSM comes included with the ops firmware. But according to another thread on here
"Crossflashing regional builds is no longer possible by EDL, flash is tied to device project ID. For reference EU devices project ID is 20889 while international devices project ID is 20886."
With that being said. I was able to flash modified Metro firmware (patched ramdisk in boot.img) as noted earlier. So perhaps I can try extracting firmware for the global version and metro, replace any project ID in global with metro project ID and attempt to flash the firmware.
Alternatively we can try to patch the Metro MSM tool like the one used for the 6T above.
ieatgravity said:
MSM comes included with the ops firmware. But according to another thread on here
"Crossflashing regional builds is no longer possible by EDL, flash is tied to device project ID. For reference EU devices project ID is 20889 while international devices project ID is 20886."
With that being said. I was able to flash modified Metro firmware (patched ramdisk in boot.img) as noted earlier. So perhaps I can try extracting firmware for the global version and metro, replace any project ID in global with metro project ID and attempt to flash the firmware.
Alternatively we can try to patch the Metro MSM tool like the one used for the 6T above.
Click to expand...
Click to collapse
If I had one to test, I'd try it myself. I don't think it's device specific, but it might give you an error, much like Galaxy Devices do on device, if you flash firmware that doesn't match and it knows it doesn't match
You used to be able to flash Chinese firmware to Galaxy Tab A 10.1 tablets to get around FRP because there's no google apps on older Galaxy Tablets for the Chinese region. You'd flash the chinese firmware with patched odin, go through setup, go back to odin, flash US firmware, and it'd get around frp... that no longer works because they added a check into the bootloader itself.
KaptinBoxxi said:
If I had one to test, I'd try it myself. I don't think it's device specific, but it might give you an error, much like Galaxy Devices do on device, if you flash firmware that doesn't match and it knows it doesn't match
You used to be able to flash Chinese firmware to Galaxy Tab A 10.1 tablets to get around FRP because there's no google apps on older Galaxy Tablets for the Chinese region. You'd flash the chinese firmware with patched odin, go through setup, go back to odin, flash US firmware, and it'd get around frp... that no longer works because they added a check into the bootloader itself.
Click to expand...
Click to collapse
I saw the 6T had a patched MSMdownloadtool but according to another post on here for the ubrick guide for this specific variant cannot be patched because it has some anti-debugging code built in.
With that said. I noticed the files you get for the MSM tool has two .DLL files (which could be device specific) that the MSM download tool uses. Also since it is possible to flash modified .OPS it might be possible to still flash the Global version. I saw one guide on the 6t that after you flash the global rom from MSM you get the same error I received with the modified .OPS (patched bootloader) I flashed. Error was "your device cannot be trusted and will not boot". But they took it a step further and ran "fastboot OEM unlock critical" and the bootloader unlocked and booted.
If this device wasn't my daily I would have attempted this by now.
I was able to flash the Global stock Oneplus rom using MSM download tools to the MetroPCS Nord N10 5G.
BUT
OEM unlock is still greyed out. Any ideas?
also updated first post with how to replicate what I did to flash. This should work on any variant as long as you replace the project number to your own
ieatgravity said:
I was able to flash the Global stock Oneplus rom using MSM download tools to the MetroPCS Nord N10 5G.
BUT
OEM unlock is still greyed out. Any ideas?
also updated first post with how to replicate what I did to flash. This should work on any variant as long as you replace the project number to your own
Click to expand...
Click to collapse
It is network checked for OEM Unlock even on the global variants. You need to connect via SIM Data or Wifi for it to check if OEM Unlock can be done, which might mean its doing it via IMEI or some other bootloader specific check
Even connected to the internet the toggle is still greyed out. Device still shows BE2025 despite flashing the international firmware. But it does show the International build number. It also has the international system update engine which was able to do OTA update to latest, it also has the icon at the top where you can pick the file.
Other things I have tried:
- replaced vbmeta and vbmeta_system with empty vbmetas [Device got stuck in an EDL loop]
- replaced recovery.img with twrp.img [Device got stuck in an EDL loop]
- replaced boot.img with magisk_patched.img [Device corrupt, cannot be trusted and will not boot - bootloader loop]
- replaced recovery.img with magisk_patched.img [Device boots like normal. Tried booting magisk (volume down + power until splash screen, then release) Device corrupt, cannot be trusted - reboot back into system just fine.
- Used a HEX editor on boot.img to disable dm-verity [Hex code not found - no changes made]
I don't even know where to begin to see if it is network locked with the international rom. Voice over wifi and 5g works just fine though.
ieatgravity said:
MAJOR UPDATE: Managed to flash Global stock rom to the MetroPCS variant
Pros: Stock Oneplus and everything works
Cons: OEM unlock is still greyed out
Before you go any further:
THERE IS NO ROOT FOR THIS DEVICE WITH A LOCKED BOOTLOADER (YET). THIS THREAD IS FOR THE DEVELOPMENT AND TESTING OF METHODS TO ACHIEVE THIS.
Just got this device from MetroPCS this week and love this device. However I found out very quick that you have to be with MetroPCS for 180 days before you can get unlocked. To unlock the bootloader you have to be sim unlocked from the carrier.
This thread will be for development of a working root process for others to offer perspective. Feel free to try to replicate at your own risk. If anyone is interested in these files/tools let me know and I will publish more links.
;Download international and metro ROM and MSM tool from these thread (thanks to @Some_Random_Username)International
MetroPCS
This download will include the latest MSM Download Tool
The work around that I found does not need MSM to be patched
;TOOLS
download and extract oppo decrypt master
unpack and repack .OPS files for use with MSM Download Tool 4 .exe
----------------------------------------------------------------------------------------------------------------------------------------------
Method----------------------------------------------------------------------------------------------------------------------------------------------
TD;RL:
Extract the .ops file, open settings.xml replace the project ID, repack
Set up:
1. Download international zip and metro zip from above, extract into 2 seperate folders and delete billie8t_14_O.01_201218.ops in the metro folder
2. have adb installed
3. Install python3 and prereqs for oppo decrypt master
Extract .ops, edit and flash:
1. unzip the zip file with the .ops file from both folders and move it to the folder with oppo decrypt
2. run "python3 opscrypto.py decrypt billie8_14_O.01_210128.ops" (decrypt both .ops files from each firmware, the first one being the metro and get the /extract/settings.xml file and open it. we will need info from it)
3. Now extract the international firmware with opoo decrypt and open the extract folder
4. open "settings.xml" from both firmwares in your favorite editor
6. Change the following in the international settings.xml: Project=20886 to Project=20885 and ModelVerifyRandom= (THESE NEED TO BE EXACTLY WHAT ARE IN THE METRO SETTINGS.XML file)
6. Save the file
7. run "python3 opscrypto.py encrypt extract". This will create a file called out.ops
8. Once finished place out.ops into the metro firmware folder and rename to "billie8t_14_O.01_201218.ops"
9. With your phone turned on, plug your phone into the computer
10. Open MSMdownloadtoolv4.0.exe and press start
11. Run "adb reboot edl"
12. Your computer should recognize and start the download.
13. Wait a while and it will reboot.
Click to expand...
Click to collapse
I did what someone else suggested i contacted fcc 2 days ago to file a complaint already sim unlocked on metro oem toggle not grey anymore
scottlam1 said:
I did what someone else suggested i contacted fcc 2 days ago to file a complaint already sim unlocked on metro oem toggle not grey anymore
Click to expand...
Click to collapse
How did you go about this? Were you passed your 180 days?
Here is an interesting(or weird) thread
OnePlus Nord | N10 | N100 [TMO/MPCS] Network Unlock & Enable OEM Unlocking (April 19th, 2021)
1.) ADB access must be enabled -Tap build number 7 times until Developer Options are enabled 2.) Enable USB Debugging -For PC-less enable Wireless Debugging Optional if PC-less 3.) Go to Play Store or F-Droid and download Shizuku 4.) Tap...
forum.xda-developers.com
arda99 said:
Here is an interesting(or weird) thread
OnePlus Nord | N10 | N100 [TMO/MPCS] Network Unlock & Enable OEM Unlocking (April 19th, 2021)
1.) ADB access must be enabled -Tap build number 7 times until Developer Options are enabled 2.) Enable USB Debugging -For PC-less enable Wireless Debugging Optional if PC-less 3.) Go to Play Store or F-Droid and download Shizuku 4.) Tap...
forum.xda-developers.com
Click to expand...
Click to collapse
I...
have mixed feelings about this.
Cannot tell if this is troll or someone actually trying to help
ieatgravity said:
How did you go about this? Were you passed your 180 days?
Click to expand...
Click to collapse
150 days just google fcc complaint the form is simple and explains everything i got an email and call from metro a very nice woman
I used your files oem unlocked bootloader still needs unlock token
I'm aware, I still haven't been able to get unlock bootloader ungreyed out either.
At this point I'm not quite sure what to try next but I will keep researching.
If I can find a way to remove dm-verity (secure boot) I'm 100% positive that I can get it rooted without network unlock and unlocked bootloader.
Though an unlocked bootloader would be nice.
ieatgravity said:
I'm aware, I still haven't been able to get unlock bootloader ungreyed out either.
At this point I'm not quite sure what to try next but I will keep researching.
If I can find a way to remove dm-verity (secure boot) I'm 100% positive that I can get it rooted without network unlock and unlocked bootloader.
Though an unlocked bootloader would be nice.
Click to expand...
Click to collapse
No mine is carrier unlocked and the oem in development is active now but i was hoping i woulnt need the token because for some reason onplus says invalid imei when i try to request a token
For anyone searching..
I was facing the "no caller id issue" on VOLTE/VOWifi calls
The solution for me was always this guide.
However, this wasn't a stable solution for A12, as the made changes to the modem config were gone after a reboot and defaulted back to ROW Commericial. My own network wasn’t available in the PDC list as well (NL KPN)..
Then I recently started playing with the firmware flashable img from xiaomifirmwareupdater.com (fw_alioth_miui_ALIOTHGlobal_V13.0.3.0.SKHMIXM.zip in my case).
I had extracted the modem.img , opened it with powerISO and I found that the PDC tool wasn't showing my specific network because my network wasn't listed in one of the txt files in the folder \image\modem_pr\mcfg\configs\mcfg_sw.
However, the right modem config file (mcfg_sw.mbn) was available, deeply nested in the generic folder.
(\image\modem_pr\mcfg\configs\mcfg_sw\generic\EU\KPN\Commercial\NL).
So there are a lot more (hundreds) configs available than the PDC tool shows!
Not knowing which txt file I needed to change to add my network, I boldly replaced the default ROW commercial mcfg_sw.mbn file (\image\modem_pr\mcfg\configs\mcfg_sw\generic\common\ROW\Commercial) with the one I found nested.
- Saved the image file.
- Replaced it in the firmware zip.
- Flashed the edited zip file.
- Boot into system
Success!
I now have a working VOLTE/VoWifi after each reboot!
Checking with the PDC tool afterwards. It showed that my own network was automatically chosen.
No root acces needed!
Good luck!
Hi there landgenoot,
Came across your topic. Facing the same issues overhere with KPN on a Mi10tpro.
Can you tell me how you extracted the modem.img from the firmware. I did my research but not way I could find the modem.img file in the firmware (extracted with winrar)
TY
hi there, problem solved. your solution was great and working for me too!
Thank you very much!
I guess it can easily be an universal for Xiaomi Devices
I also tried this method on a Poco F3 device, but it didn't work. I am from EU\Slovenia and my mobile operator is Mobitel. I found the settings in the file structure
\image\modem_pr\mcfg\configs\mcfg_sw\generic\EU\Mobitel\Commercial\SI\mcfg_sw.mbn
and copied them to the
\image\modem_pr\mcfg\configs\mcfg_sw\generic\common\ROW\Commercial\mcfg_sw.mbn
in the modem.img file, but I still get an unknown caller ID when using VoLTE.
I also added the path of my carrier settings to the text files (mbn_global.txt, oem_sw.txt, oem_sw_j11.txt and oem_sw_l3a_global.txt) that were missing at
\image\modem_pr\mcfg\configs\mcfg_sw
hoping that would solve my problem, but the caller id didn't work in that case either.
In order to check if the settings for my operator are correct, I also tried the process with the QPST and PDC tools. This time the caller id works, but the process is really complicated, especially with root access in the ArrowOS I'm using and I don't want to do it every time I upgrade.
Miami_T said:
I also tried this method on a Poco F3 device, but it didn't work. I am from EU\Slovenia and my mobile operator is Mobitel. I found the settings in the file structure
\image\modem_pr\mcfg\configs\mcfg_sw\generic\EU\Mobitel\Commercial\SI\mcfg_sw.mbn
and copied them to the
\image\modem_pr\mcfg\configs\mcfg_sw\generic\common\ROW\Commercial\mcfg_sw.mbn
in the modem.img file, but I still get an unknown caller ID when using VoLTE.
I also added the path of my carrier settings to the text files (mbn_global.txt, oem_sw.txt, oem_sw_j11.txt and oem_sw_l3a_global.txt) that were missing at
\image\modem_pr\mcfg\configs\mcfg_sw
hoping that would solve my problem, but the caller id didn't work in that case either.
In order to check if the settings for my operator are correct, I also tried the process with the QPST and PDC tools. This time the caller id works, but the process is really complicated, especially with root access in the ArrowOS I'm using and I don't want to do it every time I upgrade.
Click to expand...
Click to collapse
Sorry it didn't work for you. I assume that you properly replacement the edited modem IMG in the firmware zip and flashed the edited firmware?
Perhaps you can also try again using the same config you chose with the PDC tools
I did try I think three times even with different national mobile providers (A1, Telemach), but it didn't worked. For now it is working because I set it up with PDC tool. I guess I will try again on next update of ArrowOS
Do i need to unlock the bootloader to flash the firmware and how do i flash the firmware?
These instructions are for custom roms only. If you have any of the available custom roms installed for Alioth, you already have an unlocked bootloader. The firmware can be applied in recovery.
EldigoR said:
However, the right modem config file (mcfg_sw.mbn) was available, deeply nested in the generic folder.
(\image\modem_pr\mcfg\configs\mcfg_sw\generic\EU\KPN\Commercial\NL).
Click to expand...
Click to collapse
I've been searching high and low for a solution, and this one is so relatively easy.
There is an other way to do this, if you've already a working connection with PDC.
- extract the correct .mbn file from the firmware with your suggestion.
- start the PDC tool
- chose load and then chose the .mbn file
- activate it on the sub0 and sub1
- reboot your phone and check if it still works.
Thanks a lot!!! Because I used the wrong modem config, it reseted itself on reboot. Had to use PDC every time I rebooted my phone. Now with the right profile, it stays active.