Related
Maybe someone know or test it already.
4g,3g,2g modem: Intel 7262 + Intel 2230 in all version of ZF2
So, if hardware same, it's possible to change firmware TW on WW or US and it will change supported LTE band? Who have already zf2, maybe you can test it?
I would love to be able to get the correct LTE band. I like the phone i'm just not that happy that its not the right band when the sites I used said it would work. It is my own fault but it still sux.
The Samsung galaxy alpha also uses this modem. As seen here:
https://www.ifixit.com/Teardown/Samsung+Galaxy+Alpha+Teardown/29604
The actual sku is different. This leads me to believe the chips are not the same between regions.
Anyone can test it?
If you want to switch on blocked LTE band
BUT: everything is done at your own risk.
Instruction for variant when you have TW(CN) version and wanna convert to WW bands or US bands.
You need root and /system folder with R/W permission, it's possible to do through Root Explorer
Variant 1:
1) Copy file /system/vendor/firmware/telephony/ze550ml_TW_726x.tlv for backup
2) Copy/system/vendor/firmware/telephony/ze550ml_WW_726x.tlv -> /system/vendor/firmware/telephony/ze550ml_TW_726x.tlv (change, press yes if you will be asked ).
3) reload your telephone and check 4G
If in a system asus have checksum file names, than this variant willn't help, and perhaps you will lose any connection, than just copy back file from step 1 and reload telephone.
Now varina 2:
1) Copy file /system/etc/catalog/V1_DSDA_ZE550ML_TW/telephony_config/V1_DSDA_ZE550ML_TW_726x.xml for backup
2) Copy /system/etc/catalog/V1_DSDA_ZE550ML_WW/telephony_config/V1_DSDA_ZE550ML_WW_726x.xml -> /system/etc/catalog/V1_DSDA_ZE550ML_TW/telephony_config/V1_DSDA_ZE550ML_TW_726x.xml (change, press yes if you will be asked ).
3) reload your telephone and check 4G
One more: You can not copy files, you can open /system/etc/catalog/V1_DSDA_ZE550ML_TW/telephony_config/V1_DSDA_ZE550ML_TW_726x.xml in any text editor and change ze550ml_TW_726x.tlv on ze550ml_WW_726x.tlv
original url: 4pda.ru/forum/index.php?showtopic=657946&st=40#entry39697801
@Fenrisar
applause for your super quick copy-paste of my Russian instruction, but i've posted it already here: http://forum.xda-developers.com/zenfone2/general/how-to-change-4g-bands-ze551ml-t3091869
Just got the phone bootloader unlocked (thanks to Wh1t3Rose for the guide) and now need to add the LTE bands from L24. Settings > About says the model is BND-AL10, however, HCU client says it's BND-L22 so a little confused. Can't find any fw in firmware finder for L22 so assuming AL10 is the right model.
Can I now safely use HuRUpdater to flash BND-L24C567CUSTC567D1B344 (8.0.0.344) FullOTA-MF on this device? Or I am missing some steps like rooting / installing TWRP etc.?
Another question - what TWRP to use with HuRUpdater? Would the first one from here work for 7x?
Thanks for any comments!
rexian said:
Just got the phone bootloader unlocked (thanks to Wh1t3Rose for the guide) and now need to add the LTE bands from L24. Settings > About says the model is BND-AL10, however, HCU client says it's BND-L22 so a little confused. Can't find any fw in firmware finder for L22 so assuming AL10 is the right model.
Can I now safely use HuRUpdater to flash BND-L24C567CUSTC567D1B344 (8.0.0.344) FullOTA-MF on this device? Or I am missing some steps like rooting / installing TWRP etc.?
Another question - what TWRP to use with HuRUpdater? Would the first one from here work for 7x?
Thanks for any comments!
Click to expand...
Click to collapse
If you need to change model bands , it takes more than that.
If you do like that , the model number doesn't change and modem bands also stay the same. You will need to do what is referred to as "re-brand" which changes the oeminfo file , then flash the l24 full ota.
Changing the oeminfo. Makes bootloader lock again. But the same key is supposed to still work.
It can be easy to make brick during re-brand
. You should Study the bnd-hwota-eng script to understand the process.
mrmazak said:
If you need to change model bands , it takes more than that.
If you do like that , the model number doesn't change and modem bands also stay the same. You will need to do what is referred to as "re-brand" which changes the oeminfo file , then flash the l24 full ota.
Changing the oeminfo. Makes bootloader lock again. But the same key is supposed to still work.
It can be easy to make brick during re-brand
. You should Study the bnd-hwota-eng script to understand the process.
Click to expand...
Click to collapse
Thanks mrmazak. Is this a viable option of getting L24 bands on AL10?
Found the L24 oeminfo here. Is there a way I can backup the oeminfo from my AL10 just in case I brick it
Maybe installing TWRP and taking a full backup is a better idea but can't find a TWRP img for AL10 Naugat :|
rexian said:
Found the L24 oeminfo here. Is there a way I can backup the oeminfo from my AL10 just in case I brick it
Maybe installing TWRP and taking a full backup is a better idea but can't find a TWRP img for AL10 Naugat :|
Click to expand...
Click to collapse
I will look at it tonight when I get home.
I had found good hwota tool with the re-brand script in it. I had to translate from russain and add L24 oeminfo but ithas been used successfully.
I will look at that linked oeminfo and compare to the one I put in the hwota tool.
A search on the 7x main page for "bnd hwota- eng" or similar should show the tool like.
If you don't find Ivan upload again.
mrmazak said:
I will look at it tonight when I get home.
I had found good hwota tool with the re-brand script in it. I had to translate from russain and add L24 oeminfo but ithas been used successfully.
I will look at that linked oeminfo and compare to the one I put in the hwota tool.
A search on the 7x main page for "bnd hwota- eng" or similar should show the tool like.
If you don't find Ivan upload again.
Click to expand...
Click to collapse
Thanks again, mrmazak. I saw your post in the other thread while searching but wasn't sure if there is more up to date information or an alternate tool.
Is it possible to just add certain bands to a model without removing existing bands? The only bands of interest are LTE 12 and 17 that are missing in this. The person doesn't really care about Oreo or Nougat - as long as it works with AT&T
Thanks mrmazak for updating HWTOA. I'll try rebranding AL10 to L24 tomorrow. Don't see a way to just add new bands so rebranding L24 seems to be the only way for now.
BTW, I took a backup of Boot, OEMInfo, System and modem_fw partitions. For some reason backup of Data partition failed after multiple attempts (unable to find partition for path /system and createTarProcess() ended with error 255). Is Data partition important in this case? The phone has no real data or app installed anyway as it's not in use.
Another question - planning to use HWOTA7 since I have Nougat right now but downloaded BND-L24C567CUSTC567D1B344 (8.0.0.344) full OTA - is this ok? I can't find a Nougat version for L24C567.
I flashed from L21C10 to TL10,before that I saved 8 modem files with L21 to him and the emui tweaker from the phone,then I restored it,and I had 4G+,try so.
rexian said:
Thanks mrmazak for updating HWTOA. I'll try rebranding AL10 to L24 tomorrow. Don't see a way to just add new bands so rebranding L24 seems to be the only way for now.
BTW, I took a backup of Boot, OEMInfo, System and modem_fw partitions. For some reason backup of Data partition failed after multiple attempts (unable to find partition for path /system and createTarProcess() ended with error 255). Is Data partition important in this case? The phone has no real data or app installed anyway as it's not in use.
Another question - planning to use HWOTA7 since I have Nougat right now but downloaded BND-L24C567CUSTC567D1B344 (8.0.0.344) full OTA - is this ok? I can't find a Nougat version for L24C567.
Click to expand...
Click to collapse
There is a nougat full it's. It is labeled for Oreo roll-back. But should work for you . It is found as 'bond' intead of 'bnd'. ( Wait, the rebrand script is looking for three files. I will try and adjust the script to not fault out with just two.)
And link is actually in the hwota thread as a downgrade package.
I do reupload most current hwota file yesterday. I found a bug when I did a downgrade. So I proof read through the files again and re-uploaded.
Also added link to bnd-hwota-eng to the guide thread.
Klirensxp said:
I flashed from L21C10 to TL10,before that I saved 8 modem files with L21 to him and the emui tweaker from the phone,then I restored it,and I had 4G+,try so.
Click to expand...
Click to collapse
Did you do this to rebrand the phone to support other LTE bands? Or just to get OTA updates keeping the same radios? Sounds like latter.
I am trying to get the US radio bands on my AL10 by rebranding it to L24.
mrmazak said:
There is a nougat full it's. It is labeled for Oreo roll-back. But should work for you . It is found as 'bond' intead of 'bnd'. ( Wait, the rebrand script is looking for three files. I will try and adjust the script to not fault out with just two.)
And link is actually in the hwota thread as a downgrade package.
I do reupload most current hwota file yesterday. I found a bug when I did a downgrade. So I proof read through the files again and re-uploaded.
Also added link to bnd-hwota-eng to the guide thread.
Click to expand...
Click to collapse
Ok, will wait for the updated script. I downloaded rest of the files.
In the oeminfo folder I see AL10C00 img but not AL10C675. Trying to root the phone to be able to copy custom.bin/oeminfo so that I can go back to stock later. For some reason SuperSU doesn't work... will try Magisk now
rexian said:
Ok, will wait for the updated script. I downloaded rest of the files.
In the oeminfo folder I see AL10C00 img but not AL10C675. Trying to root the phone to be able to copy custom.bin/oeminfo so that I can go back to stock later. For some reason SuperSU doesn't work... will try Magisk now
Click to expand...
Click to collapse
I have been looking at some ways to edit the script to make it automatically adjust if there is only 2 update files. And it will be easier to just manually edit the one script before you run it.
Add a "#" to the front of line 332 of hwota.sh.
"HWOTA_BND\HWOTA7_BND-eng\hwota.sh"
Need to just comment out the line with "$TARGET_UPDATE_DATA"
Code:
echo
echo "Copying recovery files, please be patient and wait...."
$ADB push $RECOVERY $RECOVERY_TMP
$ADB push $RECOVERY2 $RECOVERY2_TMP
$ADB shell "dd if=$RECOVERY_TMP of=/dev/block/bootdevice/by-name/recovery bs=1048576"
$ADB shell "dd if=$RECOVERY2_TMP of=/dev/block/bootdevice/by-name/recovery2 bs=1048576"
$ADB shell "echo --update_package=$TARGET_UPDATE > /cache/recovery/command"
#$ADB shell "echo --update_package=$TARGET_UPDATE_DATA >> /cache/recovery/command"
$ADB shell "echo --update_package=$TARGET_UPDATE_HW >> /cache/recovery/command"
$ADB reboot recovery
$ADB kill-server
mrmazak said:
I have been looking at some ways to edit the script to make it automatically adjust if there is only 2 update files. And it will be easier to just manually edit the one script before you run it.
Add a "#" to the front of line 332 of hwota.sh.
"HWOTA_BND\HWOTA7_BND-eng\hwota.sh"
Need to just comment out the line with "$TARGET_UPDATE_DATA"
Code:
echo
echo "Copying recovery files, please be patient and wait...."
$ADB push $RECOVERY $RECOVERY_TMP
$ADB push $RECOVERY2 $RECOVERY2_TMP
$ADB shell "dd if=$RECOVERY_TMP of=/dev/block/bootdevice/by-name/recovery bs=1048576"
$ADB shell "dd if=$RECOVERY2_TMP of=/dev/block/bootdevice/by-name/recovery2 bs=1048576"
$ADB shell "echo --update_package=$TARGET_UPDATE > /cache/recovery/command"
#$ADB shell "echo --update_package=$TARGET_UPDATE_DATA >> /cache/recovery/command"
$ADB shell "echo --update_package=$TARGET_UPDATE_HW >> /cache/recovery/command"
$ADB reboot recovery
$ADB kill-server
Click to expand...
Click to collapse
Cool, done commenting #332. Also was able to root and make a copy of custom.bin / oeminfo.
Now, going to run the script :fingers-crossed:
Alright, an update - it went through lot of steps as expected (including installing oeminfo and unlocking the bootloader) but ended up with "software update failed" error on the phone. On command prompt here is the last few lines of the log -
Use the volume buttons to select YES and press the power button
...
(bootloader) The device will reboot and do factory reset...
OKAY [ 11.001s]
finished. total time: 11.001s
Wait for the device to boot into TWRP.
Press Enter to continue...
Wait for the files to load. Neither of which you do not need to press !!!.
Copying is in progress ....
[100%] /data/update/HWOTA/update.zip
Copying is in progress ....
adb: error: cannot stat 'D:/UX/HCU-Client/HWOTA7_BND-eng//update/update_data_public.zip': No such file or directory
Copying is in progress ....
adb: error: cannot stat 'D:/UX/HCU-Client/HWOTA7_BND-eng//update/update_all_hw.zip': No such file or directory
Copying recovery files, please be patient and wait....
[100%] /tmp/BND_RECOVERY_NoCheck.img
[100%] /tmp/BND_RECOVERY2_NoCheck.img
35+1 records in
35+1 records out
37109760 bytes (35.4MB) copied, 0.414091 seconds, 85.5MB/s
35+1 records in
35+1 records out
37109760 bytes (35.4MB) copied, 0.508804 seconds, 69.6MB/s
The system update should start automatically.
Press Enter to continue...
Click to expand...
Click to collapse
Error for update_data_public.zip was expected and on close inspection I noticed there was an extra '.' in the name of update_all_hw.zip. It was update_all_hw..zip.
So, fixed it and put the phone in fastboot mode and re-ran update.bat. It installed recovery and asked me to put into TWRP. I tried but it never went to TWRP started installing the previously copied ZIP files. It took a while but after it restarted, it went to straight to Android (YAY!). Went to Settings > About and say the model as BND-L24 and build number System 5.1.0.98(07DV).
So far it seemed everything was fine - then I inserted the FreedomPop SIM (uses AT&T towers), added the fp.com.attz APN and restarted it - AND the same issue, can't see the carriers and 0 bars
The oeminfo was definitely installed as I see a lot more options in "preferred network mode" but selecting Global or LTE or anything else does nothing...
Since I am not able to boot into TWRP, I wonder if that's causing an issue. Every attempt to boot into TWRP goes into a screen showing "installing update" with 5% status. It eventually (after 10 minutes or so) boots into Nougat.
Gave up and started from scratch (after installing TWRP img mount manually) and it completed successfully (with expected error for the missing update_data_public.zip). Build number changed to BND-L24C567B150 so both zips were installed yet the problem remains the same - no cellular connectivity and settings > More > Mobile Network > Carrier remains disabled...
rexian said:
Did you do this to rebrand the phone to support other LTE bands? Or just to get OTA updates keeping the same radios? Sounds like latter.
I am trying to get the US radio bands on my AL10 by rebranding it to L24.
Click to expand...
Click to collapse
It’s just that the L21 is always 4G,and on the TL10 it goes to 3G,I switched from L21 to TL10 because of gestures, now I have 4G+ as well as on L21.
rexian said:
Gave up and started from scratch (after installing TWRP img mount manually) and it completed successfully (with expected error for the missing update_data_public.zip). Build number changed to BND-L24C567B150 so both zips were installed yet the problem remains the same - no cellular connectivity and settings > More > Mobile Network > Carrier remains disabled...
Click to expand...
Click to collapse
Good catch with the renamed file. You did right thing to start over, because that first build number was not correct.
As far as I know this should have changed the radio files (modem).
I will keep looking for other confirmed way to change the selected bands.
mrmazak said:
Good catch with the renamed file. You did right thing to start over, because that first build number was not correct.
As far as I know this should have changed the radio files (modem).
I will keep looking for other confirmed way to change the selected bands.
Click to expand...
Click to collapse
Thanks mrmazak. What could be the reason behind disabled option? Earlier with AL10, I could go inside and see AT&T listed but selecting that would not help as corresponding radios were not enabled in AL10.
Now, even if L24 radios are not properly installed / enabled, I should be able to go inside and see AT&T listed - makes me wonder if all the radios are now disabled.
Is there another way to check what radios are available in a phone by running some app?
rexian said:
Thanks mrmazak. What could be the reason behind disabled option? Earlier with AL10, I could go inside and see AT&T listed but selecting that would not help as corresponding radios were not enabled in AL10.
Now, even if L24 radios are not properly installed / enabled, I should be able to go inside and see AT&T listed - makes me wonder if all the radios are now disabled.
Is there another way to check what radios are available in a phone by running some app?
Click to expand...
Click to collapse
Not sure about other ways to check the bands. There are playstore apps that will show what band you are connected to, but have not seen one that shows which ones you can connect to.
side note::: Funkyhuawei (paid service) says of there rebrand guide, that you must flash the new firmware at least 2 times. So maybe take the flash one more time.
some general questions about your problem.
On about phone screen, what is shown for 'baseband' ?
does the imei # number show?
are you installing sim into slot #1 ? (#2 does not support 4g)
did you verify freedom pop sim is activated? (tested in other device)
edit:
found few posts in some "rebranding" threads, that say what you want to do might not be possible.
They say on the software side it will have drivers for the correct bands. But he hardware may not suppport it.
here:
https://forum.xda-developers.com/showpost.php?p=76462513&postcount=175
mrmazak said:
Not sure about other ways to check the bands. There are playstore apps that will show what band you are connected to, but have not seen one that shows which ones you can connect to.
side note::: Funkyhuawei (paid service) says of there rebrand guide, that you must flash the new firmware at least 2 times. So maybe take the flash one more time.
Click to expand...
Click to collapse
I tried once more tonight but the same result - no service and carrier disabled.
mrmazak said:
some general questions about your problem.
On about phone screen, what is shown for 'baseband' ?
does the imei # number show?
are you installing sim into slot #1 ? (#2 does not support 4g)
did you verify freedom pop sim is activated? (tested in other device)
Click to expand...
Click to collapse
There are 2 long numbers for the baseband - both start with 21C60B. Yes, both IMEIs show and are the same as before.
Yes, I always used the dedicated SIM slot as I have a micro-SD inserted for backup.
mrmazak said:
edit:
found few posts in some "rebranding" threads, that say what you want to do might not be possible.
They say on the software side it will have drivers for the correct bands. But he hardware may not suppport it.
here:
https://forum.xda-developers.com/showpost.php?p=76462513&postcount=175
Click to expand...
Click to collapse
I am inclining towards this as well - possibly missing hardware
Now, how do I get back to AL10C675 (don't see a Nougat option in FW Finder) and original radio? HWOTA doesn't have C675 as option, it has C00. I do have the original custom.bin and oeminfo but how do I create a zip to install with TWRP?
Hello,
since Android 9, there are no modifications (rename, delete, ect) in oem/OP/... allowed.
ex (https://forum.xda-developers.com/lg...-enable-volte-vowifi-uk-mobile-t3835167/page3)
After reboot, the modifications has been recovered by itself.
Can everybody help?
Have a nice day
flash this boot
boot_20b-magisk-op_disabled-1.img
https://drive.google.com/open?id=12htRoR94XKocVQZ4VWubLPsIgjLf3a8B
or
using hex-redactor open your boot.img and change boot.product.lge.op_verity=1 to boot.product.lge.op_verity=0, save and flash it
Great - it works like a charme. I did it by myself with a simple hex-editor (HxD) :good::good::good:
edit
boot_20d_magisk_op_disabled.img
https://forum.xda-developers.com/showpost.php?p=80276083&postcount=12
thanks!!!
help
Can someone help me here pls? https://forum.xda-developers.com/showpost.php?p=80961859&postcount=24
you need to flash respective boot with op dissabled for your especific stock rom
you need open bootloader and caution... you can brick your phone...
Stvn77 said:
you need to flash respective boot with op dissabled for your especific stock rom
you need open bootloader and caution... you can brick your phone...
Click to expand...
Click to collapse
I have LG H930DS, which actually didn't suppose to have unlockable bootloader, but i have unlocked it, and magisk root with this tutorial from ChazzMatt: https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193 , and because of that having access to /OP/OPEN_AME_DS (oh yes, btw, my phone is H930DS, but have AME software version, which stands for United Arab Emirates, latest oreo, and i don't live in UAE, i'm living in Europe, so folders /OP/OPEN_AME_DS and someone who have europe V30 with folder /OP/OPEN_EU actually have little differences, some files related to ims are missing in my one, and some are different from EU folder). My carrier don't have VoLTE and VoWifi, but it have video calling, so i want somehow to activate ims status to be registered to have video calling. If someone have that OPEN_EU(or any other which you have OPEN_) folder, and have ims registered (check your ims status by dialing *#*#4636#*#* and three dots up right corner), and maybe have video calling in dialer, i would be really thankful if someone send me that OPEN_ folder(like zip) to compare with my OP folder, and maybe send me even build.prop
vo_config.xml
Hi all, i have the following situation:
- I've unlocked an LG V40 EBW with LG unlock;
- Extracted boot_a, boot_b image from latest kdz ( 20f) in a Linux VM
- Installed Magisk Manager, patched boot_a with Magisk Manager
- Booted in ADB from magisk_patched.img
- Installed magisk_patched.img in Magisk Manager on slot 1
I have obtained permanent root on the stock rom.
I'm trying to edit vo_config.xml from /oem/OP/OPEN_EN_DS/config for VoWiFi/VoLTE.
It seems this is mounted on /dev/block/dm-0.
Even if i can write to the file, change permissions etc. , the changes are reset after a reboot.
I have already HEX edited magisk_patched.img "judypn androidboot.product.lge.op_verity=0" and flashed it in ADB and didn't solve my problem.
How could this be done? I'm on Android 9, stock rom ( 20f)
Help 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.