Related
hello friends today i will share a method that i found on youtube how to switch from chinese to global firmware on Meizu Pro 7
all the credits are for Uncle MokuS
i just wanted to help people that is searching for it like me
so just follow the totorial - https://www.youtube.com/watch?v=aDp...5wdjofattwgksn3zi1jpw03c010c.1508299039136556
the totorial is in russian so if you have any doubt just read the coments in video discription
that method is different that the one that i use in my old mx5 by terminal emulator... i really would prefer the terminal emulator method because just change the phone and you can install any G firmware by flyme recovery and keep with ota updates and without the phone rooted (i dont want root because i use some apps that doesnt allow me use if i have root) but i didnt find a diferent mode yet i hope some one could show a diferent method like i did to mx5
everything works because its original firmware the only thing is that to next updates you´ll have to do by flashfire
anyway i hope you all enjoy G firmware
Hi, thanks for the good news.
Does anyone know whether this method also works with the Meizu Pro 7 PLUS?
The people in comments say that its not working
You can find an english Guide for the installation of the Global ROM on the chinese Meizu Pro 7 here:
https://www.china-phone.net/meizu-pro-7-global-rom-guide.html
Lost imei
I have lost my imei numbers and they become null.
Also i have lost root access after intalling the update.zip from flymeos.com. Because i cant login into meizu account after installing the update.zip,
it says ''invalid parameter ''.
Phone has locked bootlader. Cant flash anything..
Any suggestions ?
Dennis1311 said:
Hi, thanks for the good news.
Does anyone know whether this method also works with the Meizu Pro 7 PLUS?
Click to expand...
Click to collapse
I've got this one working for Pro 7 Plus, model M793Q:
1. Download Flyme 6.7.10.31 beta rom from official chinese Flyme site and put it to your phone's main folder
2. Enter Recovery mode (Volume Up + Power), select "Update firmware" and "Wipe data", then wait until the update is done
3. Download Flyme 6.1.2.0G rom from official site and also put it to your phone just like the chinese rom
4. Enter Recovery mode again and do the same things - select "Update firmware" and "Wipe data", then wait until the update is done
Thanks for your Method..It is working great on Meizu Pro 7 PLUS Model: M793H to :good:
T3Rm0 said:
I've got this one working for Pro 7 Plus, model M793Q:
1. Download Flyme 6.7.10.31 beta rom from official chinese Flyme site and put it to your phone's main folder
2. Enter Recovery mode (Volume Up + Power), select "Update firmware" and "Wipe data", then wait until the update is done
3. Download Flyme 6.1.2.0G rom from official site and also put it to your phone just like the chinese rom
4. Enter Recovery mode again and do the same things - select "Update firmware" and "Wipe data", then wait until the update is done
Click to expand...
Click to collapse
Just one thing you still have ota updates right?
im trying in my pro 7 (standard) and when i try to install the G firmware in recovery i got the message firmware corrupt do the people with pro 7 plus is lucky
its not working in the standard version i give up xD
1. I have still my ota updates on Meizu pro 7 plus with the global version that i recently update from A chinese firmware to beta chinese then to Global version.
2. You need to have the Chinese Beta version first on your phone to update to Global version.
3. You can download the chinese flyme firmware beta version from Meizufans. Search Meizufans on the Google.
4. Allways backup your Imei number so you can restore it. That is only if the Imei NR gets NULL.Best place to have your backup is PC.
5. Download the global version from the flymeos.com
6. It should work on the standard version because it has the beta version too.
Good Luck :good:
DiogoSepultura said:
Just one thing you still have ota updates right?
im trying in my pro 7 (standard) and when i try to install the G firmware in recovery i got the message firmware corrupt do the people with pro 7 plus is lucky
its not working in the standard version i give up xD
Click to expand...
Click to collapse
TedGok said:
1. I have still my ota updates on Meizu pro 7 plus with the global version that i recently update from A chinese firmware to beta chinese then to Global version.
2. You need to have the Chinese Beta version first on your phone to update to Global version.
3. You can download the chinese flyme firmware beta version from Meizufans. Search Meizufans on the Google.
4. Allways backup your Imei number so you can restore it. That is only if the Imei NR gets NULL.Best place to have your backup is PC.
5. Download the global version from the flymeos.com
6. It should work on the standard version because it has the beta version too.
Good Luck :good:
Click to expand...
Click to collapse
lets see...
so i download the firmwares from flyme websites (they are the same that we have in meizu fans) so i installed flyme 6.7.10.31 beta
after that i went to recovery and put the G firmware inside the phone main folder, the only G firmware version that pro7 standard has is 6.1.3.0
and in recovery i try to update and always say that the firmware is corrupt
DiogoSepultura said:
lets see...
so i download the firmwares from flyme websites (they are the same that we have in meizu fans) so i installed flyme 6.7.10.31 beta
after that i went to recovery and put the G firmware inside the phone main folder, the only G firmware version that pro7 standard has is 6.1.3.0
and in recovery i try to update and always say that the firmware is corrupt
Click to expand...
Click to collapse
Try to do this:
1. Get Root permissions in settings and download Root Explorer
2. Put Global rom into your main folder
3. Start Root Explorer, grant root permissions to him and go to /dev/block/platform/bootdevice/by-name
4. Open devinfo as text file and change it from 0x79101001 to 0x79151001, then save it
5. Open the standard Flyme explorer, click on your global rom and agree with wipe
I can't guarantee that it will work but if it won't nothing bad will happen - the phone will just reboot
T3Rm0 said:
Try to do this:
1. Get Root permissions in settings and download Root Explorer
2. Put Global rom into your main folder
3. Start Root Explorer, grant root permissions to him and go to /dev/block/platform/bootdevice/by-name
4. Open devinfo as text file and change it from 0x79101001 to 0x79151001, then save it
5. Open the standard Flyme explorer, click on your global rom and agree with wipe
I can't guarantee that it will work but if it won't nothing bad will happen - the phone will just reboot
Click to expand...
Click to collapse
Hello! But i have there not 0x79101001 in "devinfo" i have 0x79201001
How can i change?
best regards
peter
pmartin said:
Hello! But i have there not 0x79101001 in "devinfo" i have 0x79201001
How can i change?
best regards
peter
Click to expand...
Click to collapse
In that case change it to 0x79251001, "5" means european device
Do you have Pro 7 HE or something? I thought there are only 2 IDs:
PRO 7 Plus 0x79351001
PRO 7 0x79151001
T3Rm0 said:
In that case change it to 0x79251001, "5" means european device
Do you have Pro 7 HE or something? I thought there are only 2 IDs:
PRO 7 Plus 0x79351001
PRO 7 0x79151001
Click to expand...
Click to collapse
pmartin did you tried this already? let us know what happend
DiogoSepultura said:
pmartin did you tried this already? let us know what happend
Click to expand...
Click to collapse
I've already tried it on my Plus device and nothing happened
The problem is that the developer has made a protection against changing ID - there are several scripts named loop, so if you change ID in devinfo and reboot they will roll back the changes.
Also I've searched for previous scripts that were working on old meizu devices, there are several ways of doing that:
1. Rewrite devinfo by using unix commands - as I understood the program finds a sector where the ID is based and replaces it. The problem is that you need to know an exact binary address for the ID but I don't know how to disassemble .img files :<
2. Get devinfo straight from the same EU device and replace it - it's easier but I don't have an EU file (If someone has it please contact me)
3. Use flash tool to write the ID directly in chipset - the most dangerous way but I can't find binary files for Helio X30, and also you need to know an adress of ID
So the easiest and the most safe way is method 2, because even if something will go wrong you can just reinstall rom from recovery mode, but if someone here knows unix\assembler he can try to locate the ID, I have extracted devinfo file (it's still has chinese ID but I believe we can find a way out)
Hello!
At first i had to install the "beta"-Rom. Because i had installed the SuperSu and i am at the "bootloop".
I am back, i try the version.
regards
peter
T3Rm0 said:
In that case change it to 0x79251001, "5" means european device
Do you have Pro 7 HE or something? I thought there are only 2 IDs:
PRO 7 Plus 0x79351001
PRO 7 0x79151001
Click to expand...
Click to collapse
pmartin said:
Hello!
At first i had to install the "beta"-Rom. Because i had installed the SuperSu and i am at the "bootloop".
I am back, i try the version.
regards
peter
Click to expand...
Click to collapse
it work´d for you?
Hi
I just tried the devinfo method with no success, as stated before, it rolls back to it original stage, I even change the permissions of devinfo file with read and exwcute only, but the permissions Also rolls back
I purchased a meizu pro 7, spanish model(global model) And I will probably Return it since I purchased Also one meizu pro 7 plus, but if you want, I can accept it a few days in order to get the files needed from the European model.
Thanks!
kralde said:
Hi
I just tried the devinfo method with no success, as stated before, it rolls back to it original stage, I even change the permissions of devinfo file with read and exwcute only, but the permissions Also rolls back
I purchased a meizu pro 7, spanish model(global model) And I will probably Return it since I purchased Also one meizu pro 7 plus, but if you want, I can accept it a few days in order to get the files needed from the European model.
Thanks!
Click to expand...
Click to collapse
if you can just share the information mate, i praying for someone who understant about this crack this thing so we can all use global firmware in our phones
T3Rm0 said:
Try to do this:
1. Get Root permissions in settings and download Root Explorer
2. Put Global rom into your main folder
3. Start Root Explorer, grant root permissions to him and go to /dev/block/platform/bootdevice/by-name
4. Open devinfo as text file and change it from 0x79101001 to 0x79151001, then save it
5. Open the standard Flyme explorer, click on your global rom and agree with wipe
I can't guarantee that it will work but if it won't nothing bad will happen - the phone will just reboot
Click to expand...
Click to collapse
DiogoSepultura said:
it work´d for you?
Click to expand...
Click to collapse
Hey guys! Now i have the beta-version from "a" but no "g" version!
I have change the devinfo but nothing happend.
Has anyone an idea how i can install the "g" version?
Best regards.
peter
NB :
- Repacked the HWOTA8 files so you don't have to download stuff you don't need
- Added oeminfo files link
If this tutorial does not work for you, use the ****** tutorial, just Google it.
ONLY WORKS ON VKY MODELS!
I created this thread for people like me who found it difficult to follow the other tutorials, guaranteed to work from oreo to oreo.
This is a simple tutorial for beginners on how to rebrand vky-L09 to vky-l29c432
A. Files needed
1. Download the original vky-l29c432b360 firmware from the firmware finder website
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2325/g1699/v120287/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...87/f1/full/public/update_data_full_public.zip (Rename to update_data_public.zip)
http://update.hicloud.com:8180/TDS/...l/VKY-L29_hw_eu/update_full_VKY-L29_hw_eu.zip (Rename to update_all_hw.zip)
2. Download the HWOTA8 repack package https://drive.google.com/open?id=12zXvow8pz8osj-XYMMfY5jRNyKQDFZNg
3. Download minimal adb and fastboot https://www.androidfilehost.com/?fid=746010030569952951
4. Download twrp from https://www.androidfilehost.com/?fid=818070582850499350 (rename it to twrp.img)
5. Download the vky-l29c432 oeminfo files from https://forum.xda-developers.com/p1...32-oeminfo-t3590134/post71874883#post71874883
B. Tutorial
1. Get your bootloader unlock code using DC Unlocker or the Huawei official site.
2. Install minimal adb and fastboot, open it. Switch of your phone, press volume down and plug in USB to enter fastboot mode, while in fastboot type 'fastboot oem unlock your-unlock-password'
Something should pop up on your phone, press yes. The device will automatically restart and format. After that the bootloader is unlocked.
3. Enter fastboot mode again, move twrp.img to c:/ directory. After that type fastboot flash recovery_ramdisk c :/twrp.img. Everything should go through. After that you have flashed twrp custom recovery.
4. Enter twrp custom recovery by pressing volume up and power till you reach twrp recovery. While in twrp go to back up and back up oeminfo (2 times) on SD card.
5. Copy the 3 downloaded firmware files from the firmware finder website (update.zip, update_data_public. Zip and update_all_hw.zip) to HWOTA8 folder in MicoSD card.
6. Go to the downloaded HWOTA8 package and extract only (hwota8_update.zip and MHA_Recovery_NoCheck.img to the HWOTA8 folder on SD card.
7. Replace the oeminfo files from twrp > backup from SD card with oeminfo.emmc.win and oeminfo.emmc.win.wid5 from the vky-l29c432.
7. Go to twrp recovery again and go to restore to restore the new oeminfo files, after that go to wipe > advanced and wipe system only. After go to install and install hwota8_update.zip from. The HWOTA8 folder in SD card.
8. The phone should restart and install vky-l29c432 firmware
9. If it doesn't, unlock the bootloader again (if locked) and then flash twrp recovery again, then restore the oeminfo again then install hwota8_updatezip.zip from the HWOTA8 folder again, it will boot now and install vky-l29c432b360.
10. You're now done. Enjoy your rebranded vky-l29c432.
HWOTA8zip is empty folders from what i can see, would love to finish this dual sim rebrand but im having zero luck and your guide seems the most simplified but im stuck
fromilla said:
HWOTA8zip is empty folders from what i can see, would love to finish this dual sim rebrand but im having zero luck and your guide seems the most simplified but im stuck
Click to expand...
Click to collapse
I've updated the link
fromilla said:
HWOTA8zip is empty folders from what i can see, would love to finish this dual sim rebrand but im having zero luck and your guide seems the most simplified but im stuck
Click to expand...
Click to collapse
Thanks for the comment
Hi
New user and new to tinkering with Android but tech savvy (i think).
However i am stuck on part 6, the two files listed "hwota8_updatezip" & "mha_recovery_NoCheck.img" do not appear within the HWOTA8 package? Unless i am going completely mad?
Inside the HWOTA8 package i have update.zip, update_all_hw.zip and update_data_public.zip (which are of course the same as the other 3 files you had us download).
Also i have a "vky_recovery_NoCheck.img" but not the mha one?
Sorry for newbie questions
Euromir said:
Hi
New user and new to tinkering with Android but tech savvy (i think).
However i am stuck on part 6, the two files listed "hwota8_updatezip" & "mha_recovery_NoCheck.img" do not appear within the HWOTA8 package? Unless i am going completely mad?
Inside the HWOTA8 package i have update.zip, update_all_hw.zip and update_data_public.zip (which are of course the same as the other 3 files you had us download).
Also i have a "vky_recovery_NoCheck.img" but not the mha one?
Sorry for newbie questions
Click to expand...
Click to collapse
Sorry for the late reply but everything has been updated
Euromir said:
Hi
New user and new to tinkering with Android but tech savvy (i think).
However i am stuck on part 6, the two files listed "hwota8_updatezip" & "mha_recovery_NoCheck.img" do not appear within the HWOTA8 package? Unless i am going completely mad?
Inside the HWOTA8 package i have update.zip, update_all_hw.zip and update_data_public.zip (which are of course the same as the other 3 files you had us download).
Also i have a "vky_recovery_NoCheck.img" but not the mha one?
Sorry for newbie questions
Click to expand...
Click to collapse
All you need is provided in the links
msn44360 said:
All you need is provided in the links
Click to expand...
Click to collapse
So, it doesn't seem to work if you move the "HWOTA8 FILES REPACK" folder straight to your sd card. You actually have to rename/make a new folder named "HWOTA8". Found out the hard way.
So, the install fails at 6%. Any ideas?
I do have a VKY-AL00, chinese p10 plus, but it said for any. Restoring the oeminfo seems to work fine. Install also works, but fails at 6% every time.
I never said move the folder, read the tutorial properly
riverwalker92 said:
So, it doesn't seem to work if you move the "HWOTA8 FILES REPACK" folder straight to your sd card. You actually have to rename/make a new folder named "HWOTA8". Found out the hard way.
So, the install fails at 6%. Any ideas?
I do have a VKY-AL00, chinese p10 plus, but it said for any. Restoring the oeminfo seems to work fine. Install also works, but fails at 6% every time.
Click to expand...
Click to collapse
Did you wipe the system?
Help
Hi, I have a p10 plus with the Chinese version of ROM and would like to switch to the global version. Can I use the same procedure as this tutorial? Would you have some video explaining to facilitate the exchange?
Thank you
msn44360 said:
Thanks for the comment
Click to expand...
Click to collapse
Hi friend.
I'm trying to rebrand and I followed all the instructions but, when the eRecovery screen shows up, nothing happens.
My second oeminfo backup file is .md5, not .sh2 like the one you shared to replace.
I'm on P10 Plus C636.
Thanks!
moscka said:
Hi friend.
I'm trying to rebrand and I followed all the instructions but, when the eRecovery screen shows up, nothing happens.
My second oeminfo backup file is .md5, not .sh2 like the one you shared to replace.
I'm on P10 Plus C636.
Thanks!
Click to expand...
Click to collapse
WhatsApp me https://chat.whatsapp.com/FNV5SqHuFxLHxtUv8Yfma4
msn44360 said:
WhatsApp me 0749402051
Click to expand...
Click to collapse
Can you help me? Please
Hi Friend, I have a p10 plus with the Chinese version of ROM and would like to switch to the global version. Can I use the same procedure as this tutorial? Would you have some video explaining to facilitate the exchange?
fjgandrade said:
Can you help me? Please
Hi Friend, I have a p10 plus with the Chinese version of ROM and would like to switch to the global version. Can I use the same procedure as this tutorial? Would you have some video explaining to facilitate the exchange?
Click to expand...
Click to collapse
I do not have a video as I do not have an extra device, but I can guarantee you that everything works 100%
msn44360 said:
Did you wipe the system?
Click to expand...
Click to collapse
yes, I tried once wiping it only before the first install and once wiping it before each install attempt. TWRP also remains on my phone after the first install, only the bootloader is locked again. As soon as i unlock it, the phone boots to twrp. Do I need to wipe some other stuff too? I did try flashing a bunch of other stuff before I found your posts.
riverwalker92 said:
yes, I tried once wiping it only before the first install and once wiping it before each install attempt. TWRP also remains on my phone after the first install, only the bootloader is locked again. As soon as i unlock it, the phone boots to twrp. Do I need to wipe some other stuff too? I did try flashing a bunch of other stuff before I found your posts.
Click to expand...
Click to collapse
If you need to contact me ASAP join the WhatsApp group, I rarely check my emails
Hi,
I try since weeks to bring my Chinese P10 plus VKY-AL00C00B217 to the L29 Version and found now your
explanation, unfortunately the link to the " HWOTA8 repack package" is empty.
I want to make sure that I work with the correct tools, so i want to load all you recommend.
Thanks for your help!
BR
Flodder
Flodder72 said:
Hi,
I try since weeks to bring my Chinese P10 plus VKY-AL00C00B217 to the L29 Version and found now your
explanation, unfortunately the link to the " HWOTA8 repack package" is empty.
I want to make sure that I work with the correct tools, so i want to load all you recommend.
Thanks for your help!
BR
Flodder
Click to expand...
Click to collapse
I have updated everything
msn44360 said:
I have updated everything
Click to expand...
Click to collapse
HI, thanks for your great help.
When I try to install the "hwota8_update.zip" it gives me following info:
"Zip file is corrupt!
Error installing zip file '/external_sd/HWOTA8/hwota8_update.zip"
Is it correct that I copy the "MHA_RECOVERY8_NoCheck.img" file twice and rename it to "VTR_RECOVERY_NoCheck.img" and one to"VTR_RECOVERY2_NoCheck.img"?
I tried it several times?!
Any idea?
Thanks a lot
Flodder72
I am curious if it is possible to allow for Verizon to be provisioned on the XZ2 Premium. I know that it is possible on the XZ2 (regular model) on older firmware by flashing the OEM.sin partition from the XZ2 Compact as it is certified by Verizon. I believe that this was done on older firmware however, due to the files being placed differently on Android 10. The XZ2 family all have the same source code and same file structure it seems. So maybe this would be possible.
Things I have tried:
Following this thread I followed the instructions provided on older firmware getting T-mobile volte support for the XZ1 devices.
-I tried flashing the OEM.sin partition from the certified XZ2 compact without any success.
-I temp rooted my device and tried placing the files manually as well in the modem folder. However on previous builds such as in the thread linked above, the .mbn files looked to be labeled differently. I do not have the files in front of me at the moment, but I will insert them here when I can later tonight possibly.
-The mbn files look to be structured in a file format such as general/row/verizon....mbn
-I de-compiled the modem.img in the modem of the XZ2 compact and it did seem to be the same file extension listed in the OEM/modem section (General/row/***). I found Verizon listed in the XZ2 compact's modem but did not see it in any of the modems of the XZ2 Premium. I'm not sure if this is going to be a major issue on getting it provisioned or not.
-I did also attempt to flash the modem as well as OEM from the XZ2 Compact on the XZ2 Premium with newflasher, but in the software it only showed "Unknown" for the modem information in the dialer code.
I will admit that I am not knowledgeable when it comes to Sony devices as this is the first one I have owned. I am unlocking my bootloader tonight, so I will have access to any file system in the phone for reference. I think that this could essentially help other carriers with provisioning as well if someone can assist in figuring out how to get it working. Thank you for anyone who tries to help.
jal3223 said:
-I did also attempt to flash the modem as well as OEM from the XZ2 Compact on the XZ2 Premium with newflasher, but in the software it only showed "Unknown" for the modem information in the dialer code.
Click to expand...
Click to collapse
Do you mean 'Current Modem Config' in Sony Service Menu? Do you know which Modem Config should be active to enable VoLTE for your network?
I am unlocking my bootloader tonight
Click to expand...
Click to collapse
It is possible to backup and restore the TA partition or are you not afraid of losing the DRM keys?
Android 10 VoLTE config files (Pixel 2):
Code:
/data/user_de/0/com.android.phone/files/
Since the right MBN was already loaded I only needed to enable some booleans like:
Code:
<boolean name="carrier_volte_available_bool" value="true" />
@SGH-i200
I do have my TA partition backed up, but there currently is no way to restore it on the XZ2. There was an advisory on the temp root thread by the maintainer/create there that created the restore function for the previous devices. The thread is located here.
https://forum.xda-developers.com/xp...-xz2c-xz2p-xz3-temp-root-exploit-via-t4099131
I am planning on unlocking it anyways though as the camera seems to be functional on Android 10 with the bootloader unlocked.
Concerning the modem files, I actually tried flashing the XZ2 Compacts modem image itself as they have basically the same file structure. I flashed with newflasher without any errors (as I planned on unlocking the bootloader anyways if it went bad). It booted fine, but maybe the mismatched file system didn't allow for it to work properly. Also yes, it stated unknown in the Current modem config area in the Sony Service menu.
Regarding the Modem config needed, I can post the exact information tonight when I get home. Or I may need to go to the XZ2 Compact section and ask a Verizon user what is being shown in that menu.
From what I can tell, the file structure when selecting modem mdn files are way different than Oreo and Nougat. Instead of just having an Mdn like "tmobile_us_ims" in the modem folder in the OEM folder, there is a generic looking file with a mdn extention. When you open the mdn, there is a file system written in like "generic/row/verizon/....". At the end of the string of folders there is a single "modem.mdn" file in the last folder. Again, I can post the specifics tonight on the exact location and file structure of everything.
Is there anything that I can pull from the phone to be helpful in this process?
Also, I possibly should have posted this thread in the XZ2 forum. There is no talk of Verizon being able to be provisioned on the XZ2 using the compact files, but I have spoken with a couple of people that did it on an earlier android using the method posted in the Tmobile Lte/Volte thread substituting the xz2 Compact oem.sin. This may help them as well.
jal3223 said:
Regarding the Modem config needed, I can post the exact information tonight when I get home. Or I may need to go to the XZ2 Compact section and ask a Verizon user what is being shown in that menu.
From what I can tell, the file structure when selecting modem mdn files are way different than Oreo and Nougat.
Click to expand...
Click to collapse
If you find a Verizon Xperia user on Android 10 with working VoLTE, please ask for the 'Current Modem Config' and the firmware version installed on the device and download this via XperiFirm.
The oem.sin partition can be crossflashed the other partitions (which include the MBN files) can not easily exchanged between all devices. Not even between a single und dual SIM version of the same model!
Maybe something can be learned from this Magisk module which adds missing MBN files to a Android 10 device: "Magisk Module that adds VoLTE support [and MBN modem files!]" https://github.com/protonchang/Pixel3-VoLTE-for-TW
MBN file location in Android 10 for Pixel 2:
Code:
/vendor/mbn/mcfg/configs/mcfg_sw/generic/EU/Vodafone/VoLTE/Germany/mcfg_sw.mbn
SGH-i200 said:
If you find a Verizon Xperia user on Android 10 with working VoLTE, please ask for the 'Current Modem Config' and the firmware version installed on the device and download this via XperiFirm.
Click to expand...
Click to collapse
I do know the firmware that is working for Verizon if that is what you're asking. It is the latest firmware for the XZ2 compact downloading through XperiFirm down-loader. It's the "customized US - 52.1.A.0.672/R7C" for the H8314 model.
I have requested for the thread to be moved to the XZ2 thread, as all xz2 devices are intermingled there. I will ask on the XZ2C thread as well though.
SGH-i200 said:
MBN file location in Android 10 for Pixel 2:
Code:
/vendor/mbn/mcfg/configs/mcfg_sw/generic/EU/Vodafone/VoLTE/Germany/mcfg_sw.mbn
Click to expand...
Click to collapse
Something interesting that I have found is that the mbn files are indeed stored in the modem. After opening the modem.img, the path to Verizon's mbn is:
mcfg_sw/generic/row/verizon/vl/us/mcfg_sw.mbn
While having the original modem with the US firmware for the Dual Sim XZ2 Premium, the file is missing in the image. However, I did just flash the modem from the XZ2 Compact, and I found the mapping in a text file located in: /data/vendor/modem_config/mcfg_sw.txt. Inside the modem_config folder along with the mcfg_sw.txt are two other files: mapping.txt and mbn_sw.dig. I am unsure of the purpose of these two files.
So I feel that I am a step farther than I was. I just need to figure out how the system tells the phone to use that mapping. On the dual sim phones there are no modem_config folder in the OEM partition. Does anyone know how the system decides what mbn to use?
*Edit* I actually found the mbn. It is located in /data/vendor/modem_config/mcfg_sw/generic/row/verizon/vl/us/mcfg_sw.mbn. I guess the mapping is there to decide what to use. In my mind I just want to copy the mcfg_sw.mbm to every single extension to make sure it takes, but I'm sure that wouldn't work.
Okay, I have an update.
I am quite certain that I have found the solution to getting the signal/volte to work. It requires me to edit and place files into the /data/vendor/modem_config/ location. However, for some reason any changes that I make get removed and reverted on each boot. I have disabled vbmeta (to the best of my knowledge) as well as decrypt data and removed DM-Verity. I also have magisk installed as well.
If anyone has any advice on how to modify these files without having them revert, would you please post your advice?
*Solved*
Okay, I managed to get the XZ2 Premium working 100% with Verizon now. I will place a guide when I have a little more time. It requires the bootloader to be unlocked as well as root. I have Volte, MMS, IMS provisioning, as well as LTE. The process is very easy despite it taking me days and hours figuring it out. Thank you for those who answered all of my questions and replying to PMs.
jal3223 said:
*Solved*
Okay, I managed to get the XZ2 Premium working 100% with Verizon now. I will place a guide when I have a little more time. It requires the bootloader to be unlocked as well as root. I have Volte, MMS, IMS provisioning, as well as LTE. The process is very easy despite it taking me days and hours figuring it out. Thank you for those who answered all of my questions and replying to PMs.
Click to expand...
Click to collapse
Did you ever publish this guide?
Additionally, does that account for Android 10?
Just curious as I'd also like to get VoLTE running. I have XZ2 (not Prem.), and will go w/ the XZ2C route, but I want others to hopefully reference this!
iCopyPhones said:
Did you ever publish this guide?
Additionally, does that account for Android 10?
Just curious as I'd also like to get VoLTE running. I have XZ2 (not Prem.), and will go w/ the XZ2C route, but I want others to hopefully reference this!
Click to expand...
Click to collapse
Sorry, I have not posted it yet. There didn't seem to be a lot of interest at the time and I got sidetracked on trying to compile a kernel for the device. I was going to make a flashable zip to do the hard work, but I haven't gotten around to it yet either. So I will post how I did it when I have a day off of work. I'm at work now, so I don't have the exact file locations in front of me. It's definitely working on Android 10 though.
jal3223 said:
Sorry, I have not posted it yet. There didn't seem to be a lot of interest at the time and I got sidetracked on trying to compile a kernel for the device. I was going to make a flashable zip to do the hard work, but I haven't gotten around to it yet either. So I will post how I did it when I have a day off of work. I'm at work now, so I don't have the exact file locations in front of me. It's definitely working on Android 10 though.
Click to expand...
Click to collapse
That's cool, no worries.
I have a feeling it would be the same process for the XZ2 to XZ2C for Verizon VoLTE, but honestly just looking for what was done as reference to better learn the steps myself.
Thanks much for the reply. Looking forward to the mini-guide then
jal3223 said:
Sorry, I have not posted it yet. There didn't seem to be a lot of interest at the time and I got sidetracked on trying to compile a kernel for the device. I was going to make a flashable zip to do the hard work, but I haven't gotten around to it yet either. So I will post how I did it when I have a day off of work. I'm at work now, so I don't have the exact file locations in front of me. It's definitely working on Android 10 though.
Click to expand...
Click to collapse
Any luck so far? The full-size XZ2 would be a great phone to get working on Verizon Wireless.
Hello,
Can anybody confirm, does XZ2 H8266 on Customized US firmware have volte in options menu visible?
If not what firmware versions have it visible in the settings?
Is it possible to mix and match XZ2 firmware with XZ3 to get Volte on Tmobile?
Thanks
jal3223 said:
Sorry, I have not posted it yet. There didn't seem to be a lot of interest at the time and I got sidetracked on trying to compile a kernel for the device. I was going to make a flashable zip to do the hard work, but I haven't gotten around to it yet either. So I will post how I did it when I have a day off of work. I'm at work now, so I don't have the exact file locations in front of me. It's definitely working on Android 10 though.
Click to expand...
Click to collapse
Have you found the procedure yet, Jal?
Bill720 said:
Have you found the procedure yet, Jal?
Click to expand...
Click to collapse
XZ2 here. Also very interested, @jal3223 . I've been trying to figure it out to no avail. I flashed XZ2 Compact oem.bin and modem.bin to XZ2 successfully. Alas, no difference in Verizon compatibility.
nykreimox said:
XZ2 here. Also very interested, @jal3223 . I've been trying to figure it out to no avail. I flashed XZ2 Compact oem.bin and modem.bin to XZ2 successfully. Alas, no difference in Verizon compatibility.
Click to expand...
Click to collapse
I'm beginning to think she forgot about us. Good thing I didn't buy one of these phones.
Bill720 said:
I'm beginning to think she forgot about us. Good thing I didn't buy one of these phones.
Click to expand...
Click to collapse
Ya jeez... I just want to get it working on any carrier in general!
jal3223 said:
Sorry, I have not posted it yet. There didn't seem to be a lot of interest at the time and I got sidetracked on trying to compile a kernel for the device. I was going to make a flashable zip to do the hard work, but I haven't gotten around to it yet either. So I will post how I did it when I have a day off of work. I'm at work now, so I don't have the exact file locations in front of me. It's definitely working on Android 10 though.
Click to expand...
Click to collapse
Please reply please please please reply I really like this phone and I just bought it and I need that file
bobo31 said:
Please reply please please please reply I really like this phone and I just bought it and I need that file
Click to expand...
Click to collapse
I'm sorry, I have long since moved on from this phone. I could never find a way to simplify the method, and I do not have the time to guide or troubleshoot at this time.
The only advice I can give is to find the modem iso image from the US XZ2C (I don't remember the location of this file). You then mount the image and find the folder that holds the Mbn files. You will have to compare both the XZ2P Mbn files to know the file structure that they must go in. You need the text file that has the mapping as well as the group of folders associated with Verizon. Then, the phone will recognize Verizon and no further work is needed.
Root is required as well. I could only place the files using a root explorer after flashing the normal firmware for the XZ2P. Or this could be done is TWRP.
Again, I do not work on this phone anymore and cannot offer further guidance.
I will request that this thread be closed.
Bill720 said:
I'm beginning to think she forgot about us. Good thing I didn't buy one of these phones.
Click to expand...
Click to collapse
I'm a guy by the way. Lol
I have spend 5 full working days to get root on my OnePlus Nord CE 5G, and have heard several times asking arround, it is the hardest OnePlus phone to root. So I decided to write a short manual to help anybody else.
I used this method:
https://magiskapp.com/root-oneplus-nord-ce-5g-using-magisk/
Where I changed tactics is how to get the boot.img The problem is with this phone is that you are not able to find the same version that your phone comes with, giving a version mismatch with the modem drivers, so making wifi not work, and multiple small problems with your 4G 5G connections and phonecalls.
https://www.quora.com/How-do-I-get-boot-img-from-an-Android-phone
I used TWRP to start a terminal to run those commands locally on the phone, rebooted the device and run Magisk , and then downloaded the patched Boot.img and flashed it via fastboot.
Sounds easy right? it is if you know
Let me know if you have any questions.
Thanks for this post. It was helpful during rooting my oneplus nord ce with oos12 and i would like to give you a tip for boot.img. As you mentioned there was a model name change for me during oos11 to oos12 and the device code changed from eb2103 to eb2101(which helped me to find my device is indian variant). Anyway, , couldn't found an official or unofficial twrp recovery for oos12 so i didn't prooced with the twrp on web to prevent bricking device since i got no warranty. I head to oneplus website to download full rom but thanks to my luck the websites was down so i found that i can download full rom using oxygen updater(can be found in play store). After i finish downloading full rom, i extracted boot image using payload dumper and patched it with magisk app. Voila! now i have root on my nord ce oos12. This huge effort is needed just to enable volte on oos12 because after i upgrade to oos12, my volte switch was gone and that made phone calls unstable.
Anyway thanks again for enlighting the path @pimzwager
Hi guys, I've read almost all a of the post avalaible about converting the Chinese NE2210 to NE2215 or NE2213, but I've seen a lot of bricked devices around there.
So I want to ask to all the people that make successful the conversion, if there so risky at it appears, it worth the price?
I'm very pleased with Color OS, but the WhatsApp notification problem it's driving me crazy, something it works sometimes not.
Thanks in advance for your response guys.
dannytgt said:
Hi guys, I've read almost all a of the post avalaible about converting the Chinese NE2210 to NE2215 or NE2213, but I've seen a lot of bricked devices around there.
So I want to ask to all the people that make successful the conversion, if there so risky at it appears, it worth the price?
I'm very pleased with Color OS, but the WhatsApp notification problem it's driving me crazy, something it works sometimes not.
Thanks in advance for your response guys.
Click to expand...
Click to collapse
So I converted from NE2215 to NE2213, easy enough I'll tell you exactly how I did it. First and foremost you want to factory reset your device and if you where rooted make sure you're not anymore. Then you'll want to get one of the Rollback ZIPs from here:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
You'll want to follow the instructions on how to flash the rollback with your desired rom.
That's it, your phone will boot up on A.12 of whichever version you rollback too and you can update OTA normally from there. If you need anymore help just ask!
unsafe8989 said:
So I converted from NE2215 to NE2213, easy enough I'll tell you exactly how I did it. First and foremost you want to factory reset your device and if you where rooted make sure you're not anymore. Then you'll want to get one of the Rollback ZIPs from here:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
You'll want to follow the instructions on how to flash the rollback with your desired rom.
That's it, your phone will boot up on A.12 of whichever version you rollback too and you can update OTA normally from there. If you need anymore help just ask!
Click to expand...
Click to collapse
Thanks for your answer, but i'm ny case it will be from NE2210 to NE2213 or any similar oxygen os model, coming from the chinese Color OS, i don't know if that's posible, i've tried with the enhanced fast boot tool múltiple times but was unsuccessful.
dannytgt said:
Thanks for your answer, but i'm ny case it will be from NE2210 to NE2213 or any similar oxygen os model, coming from the chinese Color OS, i don't know if that's posible, i've tried with the enhanced fast boot tool múltiple times but was unsuccessful.
Click to expand...
Click to collapse
I have a NE2210 which the seller converted to NE2215 using the same method. I then converted it from NE2215 to NE2213 using this method as well.
abdulhamid1978 said:
I have a NE2210 which the seller converted to NE2215 using the same method. I then converted it from NE2215 to NE2213 using this method as well.
Click to expand...
Click to collapse
I've tried this method right now; but definitely doesn't worked, i guess it will work when you roll back from any Oxygen model version; but not from Color OS.
dannytgt said:
I've tried this method right now; but definitely doesn't worked, i guess it will work when you roll back from any Oxygen model version; but not from Color OS.
Click to expand...
Click to collapse
Did you use this method? If so, what exactly happened? There are 2 methods below. Also which version of Color Os are you on?
OBT to MP rollback guide - via Local OTA update (NA ONLY)
Note: This downgrade method only works for NA version, IN and EU users please refer to the rollback guide above.
Note: This rollback method will erase all the contents of the phone, please be sure to backup first. Some applications may be lost after upgrading, you can restore the lost applications by installing the packages below.
Download the latest ROM rollback zip package from the specified server.
Copy the Rollback package to the phone storage.
Install this apk . You'll need it to rollback. Then, open the app -> tap the top right gear icon -> find the downgrade package and tap it -> wait to finish the installation -> tap reboot
After the rollback is complete, click Restart.
Rollback successful.
Please note that if you are not able to click "Local install", you can try the following step to fix it:
Disconnect all Wi-Fi and Mobile data
Go to Settings -> Apps -> App management -> Click the top right button -> Show system -> search "Software update" in the search bar and tap "Software update" -> Storage usage -> Clear data
Keep all networks disconnected and repeat the upgrade or rollback guide
Want to go back to OxygenOS 12? Download the Rollback package from the links below:
OnePlus 10 Pro NA Version
OnePlus 10 Pro IN Version
OnePlus 10 Pro EU Version
Or did you use this metod:
OBT to MP rollback guide - via Local OTA update (IN&EU ONLY)
Note: This downgrade method only works for the IN&EU version, NA users please refer to the rollback guide below.
Note: This rollback method will erase all the contents of the phone, please be sure to backup first. Some applications may be lost after upgrading, you can restore the lost applications by updating to the latest MP version via Local OTA update.
Download the latest ROM rollback zip package from the specified server.
Copy the ROM rollback package to the phone storage.
Go to Settings -> About device -> Version -> Click Build number 7 times and enter the password, now you are in the developer mode.
Go back to Settings -> About device -> Up to date -> Click the top right button -> Local install -> Click on the corresponding rollback package -> Extract -> Upgrade -> System upgrade completed to 100%.
After the rollback is complete, click Restart.
Rollback successful.
Want to go back to OxygenOS 12? Download the Rollback package from the links below:
OnePlus 10 Pro NA Version
OnePlus 10 Pro IN Version
OnePlus 10 Pro EU Version
Thanks for yoour interest and help, I've tried the second method you quoted trought the system updater, but i try on "local install" I get a "Verification failed" message.
After your answer I've tried the listed apk method , but doesn't happen, i've got : "move installation package into roor directory", tried your recommendations, but doesn't work either.
I'm actually on Color OS 13.0.0 NE2210_11_C.18, i dont know if that has some influence.
dannytgt said:
Thanks for yoour interest and help, I've tried the second method you quoted trought the system updater, but i try on "local install" I get a "Verification failed" message.
After your answer I've tried the listed apk method , but doesn't happen, i've got : "move installation package into roor directory", tried your recommendations, but doesn't work either.
I'm actually on Color OS 13.0.0 NE2210_11_C.18, i dont know if that has some influence.
Click to expand...
Click to collapse
See if there is a rollback package to go from Color OS 13 to 12, and then try again. I have no idea if neither method worked.
After your answer I've tried the listed apk method , but doesn't happen, i've got : "move installation package into roor directory", tried your recommendations, but doesn't work either.
Did you save the rollback package on the root of the internal storage?
That's exactly what i´m doing right now, i can´t find a rollback package but i guess and old Color 12.1 version will work as well.
Yes, i've moved the file into the root folder and delete the .jar extension on the name.
This was the rollback package file I downloaded:
OnePlus 10 Pro EU Version
2354_sign_NE2213_11_A_OTA_0120_all_9f570f_01000100.zip
I did not have to rename it at all, just saved the above file in the root. Mine did not have a .jar extension.
Used this apk to install from root
I then installed this the same way:
Here are the latest packages of OxygenOS 12 to help you restore the lost applications after rollback to Android 12:
OnePlus 10 Pro EU Version (A.15)
NE2213_11_A_OTA_0150_all_90846a_01000100.zip
Hope you find a solution
I've tried with the Color OS 12.1 package, al least get recognized by the "local upgrade app" but it gives me this error:
"The version of your selected package is lower than that of the current systema. To avoid booting failure, downgrading is not allowed".
So Im stuck at Color OS 13 i guess, i dont know if there is an especific Color Os 13 rollback package, i've search it , but cand find anyone, onle the same you quoted me.
I would asume the only avalible method is to flash trought enhanced fastboot, however since I've tried multiple times and can't delete de .cow files at partition, better to get familar with Color OS.
abdulhamid1978 said:
I have a NE2210 which the seller converted to NE2215 using the same method. I then converted it from NE2215 to NE2213 using this method as well.
Click to expand...
Click to collapse
just discovered i have the same phone.. 2210 12gb256 converted to 2215 out of the box (bootloader was locked)..
may i ask what are the advantages, if any, of shifting to 2213 over the 2215?
i just found that rooting a 2210 converted to 2215 causes the ram extension feature to break. (phone is on android 13 c26 jan update)
is yous rooted on 2213? does anything break or are there any major bugs? does the ram extension work (does it show 12gb+xgb in about device)?
I have not rooted the phone. One benefit for 2213 is OTA updates are received faster.