Related
Hi people,
I've been to /data/media/obb but there's no data in it - after a failed program install - i thought - go there first - delete the data - then try again - i open it an no data - any thoughts - or should i use a different file manager to access it ?
Hello,
I have AL10C00B182 ROM - ota upgrade after start use the phone.
Now I have two question:
Can I upgrade from AL10C00B182 to B353 without any other upgrades (dload method)?
Thank!
since u got the OTA to B182, im guessing ure on full stock with locked bootload and no root so in that case, installation of B353 via dload method is no problem. enjoy!
Thank you.
Now I'm on 353 (AL10) with unlocked bootloader.
I'll instal TWPR (EMUI 4.1) with decryption support and them what..?
1. install superSU
2. Have to I do wipe system or with decryption support is not nesesery?
Clean ROM with root is all I need Maybe KangVIP
hello,
May I ask how did you update your AL10C00B182 to B353?
I just had the phone for 2 days and tried checking for updates, but no updates so far.
Thank you.
bodzio3333 said:
Thank you.
Now I'm on 353 (AL10) with unlocked bootloader.
I'll instal TWPR (EMUI 4.1) with decryption support and them what..?
1. install superSU
2. Have to I do wipe system or with decryption support is not nesesery?
Clean ROM with root is all I need Maybe KangVIP
Click to expand...
Click to collapse
wellit depends what u want. if u want to stay on B353 stock and u only want root, flashing supersu is enough. otherwise go ahead and flash kangvip slim via twrp, it comes prerooted so you should be fine
Sent from my Huawei Mate 8 NXT-AL10
shackks said:
hello,
May I ask how did you update your AL10C00B182 to B353?
I just had the phone for 2 days and tried checking for updates, but no updates so far.
Thank you.
Click to expand...
Click to collapse
I had the phone for 3 days
Update is very easy:
- download the ROM - zip file,
- extract update.app from it,
- copy the UPDATE.APP to the internal memory in a folder called - dload (you may have to create it),
- power off phone,
- press [volume+]+ [volume-]+[power] together to force the update,
- done
Please check somethink:
In dialer * # * # 2846579 # * # * Enter and then 3 - Network Information and then on 4 - Vendor Country Info
Here you will find a following entries:
I have Vendor: all
Country: cn
differet that this:
cust eu = C432 - Europe
cust specseas = C636 - Asia
cust meanaf = C185 - Africa / Middle East
cust ru = C10 Russian
I bught phone from Spemall with unlocked bootloader.
jbmc83 said:
wellit depends what u want. if u want to stay on B353 stock and u only want root, flashing supersu is enough. otherwise go ahead and flash kangvip slim via twrp, it comes prerooted so you should be fine
Sent from my Huawei Mate 8 NXT-AL10
Click to expand...
Click to collapse
I suppose stay on B353 stock. I flashed supersu, reboot and its done ? Any wipe? I read that I have to do format system... Maybe too much info.
Ok. I have B353 stock with root and I want too upgrade my phone, so now I have to change twpr too stock and dload, yes ?
bodzio3333 said:
I had the phone for 3 days
Update is very easy:
- download the ROM - zip file,
- extract update.app from it,
- copy the UPDATE.APP to the internal memory in a folder called - dload (you may have to create it),
- power off phone,
- press [volume+]+ [volume-]+[power] together to force the update,
- done
Please check somethink:
In dialer * # * # 2846579 # * # * Enter and then 3 - Network Information and then on 4 - Vendor Country Info
Here you will find a following entries:
I have Vendor: all
Country: cn
differet that this:
cust eu = C432 - Europe
cust specseas = C636 - Asia
cust meanaf = C185 - Africa / Middle East
cust ru = C10 Russian
I bught phone from Spemall with unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the reply bodzio3333,
I shall do it this way later on. But, why do we have to check the region code? I'm having the same country info as yours.
Good morning Everyone
I have an Mate 8 L09C605 (Latin America) and i am trying to change its region to C432 (Europe) but it is impossible to find the oeminfo and custom.bin
Could someone share those files from the C432 please?
With all those rom players i guess there is a lot of backups out there... should not be so difficult to find
Thanks a lot.
Me too. Please help us. Thank you
Cust international (normal) = C900 OTA LOSS but you should be able to install rom from any region
--------------------------------------------------------------------------------------------------------------
Update running
--------------------------------------------------------------------------------------------------------------
Update OK. Now i am L09C900B320
---------------------------------------------------------------------------------------------------------------
The only thing I can not remember is how I am switched to L09C900B100 ... too much manipulation with SRK Tool among others with the change of region.
But it seems to me that it is doing as follows:
1- Full backup with TWRP -Before to change region-
2- Reboot
3- Region change (SRK Tool)
4- Restore TWRP Backup
5- Reboot (it seems to me that at this moment I found myself in L09C900B100, my starting Rom was L09C605B100 (Latin America). So if your starting Rom is a B180 for example, you should end up with L09C900B180.
THEN...
1- Create dload on SDCard with UPPDATE.APP (in my case from L09C432B320)
2- Restore Huawei recovery (SRK Tool)
3- Launch update * # * # 2846579 # * # *
4- Install TWRP EMUI 4.1 (SRK tool)
7- Root with TWRP
8- Reboot
--------------------------------------------------------------------------------------------------------------
VERSION INFORMATION:
In dialer * # * # 2846579 # * # * Enter and then 3 - Network Information and then on 4 -
Vendor Country Info
Here you will find a following entries:
Cust eu = C432 - Europe
Cust specseas = C636 - Asia
Cust meanaf = C185 - Africa / Middle East
Cust ru = C10 Russian
Cust international (normal) = C900 OTA LOSS but you should be able to install rom from any region
Cust la = C605 Latin America
platajeret said:
Cust international (normal) = C900 OTA LOSS but you should be able to install rom from any region
--------------------------------------------------------------------------------------------------------------
Update running
--------------------------------------------------------------------------------------------------------------
Update OK. Now i am L09C900B320
---------------------------------------------------------------------------------------------------------------
The only thing I can not remember is how I am switched to L09C900B100 ... too much manipulation with SRK Tool among others with the change of region.
Click to expand...
Click to collapse
First of all, thank you for spending your precious time writing out the instructions for us.
I followed exactly as your instruction; however, at the end, when I checked About Phone in Settings, my phone is L29C432B320 instead of L09C432B320. This is why I need the OEMINFO and CUSTOM.BIN file for L09C432B320. Thank you
Before to change the region (that gave you the L29), have you done the TWRP backup? While you where still in L09?
Oops! I don't think I did. Do you think that could be the case? BTW, how do you like C432 stock firmware? Is it any better than C636? Thank you
Yes i think that is thé reason. C432 or C636 are not firmware but région. Thé firmware i had was B100 ans now i am with B320. So far m'y phone is faster even without doing any Factory reset. But for stability ans battery life, i can't say yet.
I Guess you could be back to L09 by changing with Srk Tool the buildprop things, but better check with specialists on the fórum.
Thank you, platajeret.
I went back to L09C636B191
backup System with TWRP (for some reasons, TWRP wouldn't lemme backup Data)
reboot
changed Region
reboot
restored Backup in TWRP
dload L09C432B192
I still get L29C432B192 after all was done. So frustrated.
Hi All
Today I am releasing Moto X Play (India) Official Nougat 7.1.1 OTA ZIP Files :laugh:. These were released by Motorola for Indian Version of Moto X Play during Soak Test and is currently on-going. There are few bugs to be fixed; however stable enough for release and daily usage. Any new updates from Motorola will be updated here as and when released.
After installation of 5th OTA, your phone should be updated to below version :
System Version : 26.31.1
Build Number : NPD26.48-24-1
Android Security Patch Level : 1 September 2017 :laugh:
Below is the sequence in which updates have to be applied. An update can be installed ONLY if existing version matches given after file name below. Note you can directly install a version and skip previous builds if your existing build matches one given below. Example : If your current build is 7.1.1/NPD26.48-8/8, can skip to install 01 and 02; directly install 03-05.
01. Blur_Version.26.1.42.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 6.0.1/MPDS24.107-70-1-5/5" OR "ro.build = 7.1.1/NPD26.42/34"
02. Blur_Version.26.21.8.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.42/34" OR "ro.build = 7.1.1/NPD26.48-8/8"
03. Blur_Version.26.21.16.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.48-8/8" OR "ro.build = 7.1.1/NPD26.48-16/16"
04. Blur_Version.26.21.24.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.48-16/16" OR "ro.build = 7.1.1/NPD26.48-24/24"
05. Blur_Version.26.31.1.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.48-24/24" OR "ro.build = 7.1.1/NPD26.48-24-1/1"
Download Links :
Dailyuploads.net -
01. Blur_Version.26.1.42.lux_retasia_ds.retasiaall.en.03.zip [760 MB]
02. Blur_Version.26.21.8.lux_retasia_ds.retasiaall.en.03.zip [78.9 MB]
03. Blur_Version.26.21.16.lux_retasia_ds.retasiaall.en.03.zip [46.6 MB]
04. Blur_Version.26.21.24.lux_retasia_ds.retasiaall.en.03.zip [41.6 MB]
05. Blur_Version.26.31.1.lux_retasia_ds.retasiaall.en.03.zip [15.6 MB]
Mega.nz -
01. Blur_Version.26.1.42.lux_retasia_ds.retasiaall.en.03.zip [760 MB]
02. Blur_Version.26.21.8.lux_retasia_ds.retasiaall.en.03.zip [78.9 MB]
03. Blur_Version.26.21.16.lux_retasia_ds.retasiaall.en.03.zip [46.6 MB]
04. Blur_Version.26.21.24.lux_retasia_ds.retasiaall.en.03.zip [41.6 MB]
05. Blur_Version.26.31.1.lux_retasia_ds.retasiaall.en.03.zip [15.6 MB]
Zip Files Checksum
==================================================
Filename : 01. Blur_Version.26.1.42.lux_retasia_ds.retasiaall.en.03.zip
MD5 : 8d1677c757087ad49af9211ff454945e
SHA1 : a751aadad8662c5a5a6f5a630aeb37426b95be15
CRC32 : 2610d0c7
SHA-256 : 1572a567ef5054a735b794b7e65bffd36a7cfa78fdf5eda24c56f058970d0b37
SHA-512 : 4e76ce5e7519a220d2fb15cec0d9414cebbb0d44b15412026c5bb08fa7d614da06720c8c5b55d534f9c5a5c26bb815c745325acc74b75fda697e1179d72cc6b8
SHA-384 : bc7534a90e72a4e2c1afc00c14106dfa6054ab0a8d824fbcd5e8b095331059703da78316eb421e64e9cc8f46c7d51c0e
File Size : 797,595,918
Extension : zip
==================================================
==================================================
Filename : 02. Blur_Version.26.21.8.lux_retasia_ds.retasiaall.en.03.zip
MD5 : 4dbfe38e3aace6d148de1557e6ea512e
SHA1 : 1174d4698e9ff4c2408d3dfb09ce48faef55fbc2
CRC32 : 4c56a95b
SHA-256 : c7f4f0fe8a12c9d05c6b5349347037f3072f19895fc78cfeeaa46e11ab6e32b1
SHA-512 : f555918c8c8e784bf30281258d5a89a355d6dd81571373a8d5cdbce4dcdf6f9d2439988d139044213dd78091be20f0a6bb024fdad53ac3448d079fcecf9c10c6
SHA-384 : f993c846fd012ee647a0bb708f1a7e524dd922eee821b54d3dce06be67275aca6f891b300d98d09a2e3f1bd102cb1375
File Size : 82,813,245
Extension : zip
==================================================
==================================================
Filename : 03. Blur_Version.26.21.16.lux_retasia_ds.retasiaall.en.03.zip
MD5 : 664ecff177e4c14da476ed405c23f289
SHA1 : 0f490c52f176387cb3abd712aa2a02f511621097
CRC32 : 02702ede
SHA-256 : 28d33ed8da0a0da513257d4d32d805546b9157657dbaad9324c59c00715ab4b7
SHA-512 : 7b4fd6881a9bc1ca872ab1e66f46d9001c5d0668708d5855371379df8a62f1125251d79b79f7393916767b0edbdead0569200d39596df6e3d56f9b7d86af3669
SHA-384 : f2343aa4a36d54344819c08c6697386c147b5831968974bf14588d50fb6cc3e4b56963ff4414e913d3caf6815ff67d31
File Size : 48,914,241
Extension : zip
==================================================
==================================================
Filename : 04. Blur_Version.26.21.24.lux_retasia_ds.retasiaall.en.03.zip
MD5 : b0225339c14141e5ffb67c83c710f4c9
SHA1 : b62ec2fcd4113cd974a9984e3179d6892296d0f3
CRC32 : 9cc9c5b0
SHA-256 : 10fadca67babd93b621929c0bd16d13e3f01a2c3cd30fc2b7e4fe110b1f867e9
SHA-512 : baa95d79b36060dc24e358f6abbeffb8cc411636e08cc9a1a2fd9e8e24b2d931eae6ef97f9150e7cbd11d7dbfc31ce29ada7bdeab1621ccc9e33e62853e7d72e
SHA-384 : c2a4998e05270eecaa7d873d8683d88b8dd78a7a48308eba690bd473aaa67b85250cfe2e2f1beafe1c755ee56239b6a4
File Size : 43,724,857
Extension : zip
==================================================
==================================================
Filename : 05. Blur_Version.26.31.1.lux_retasia_ds.retasiaall.en.03.zip
MD5 : 699ac49664ea5629f437b0477107ac2b
SHA1 : 7c317dbd42f6aa332412bee7784998b4e7d50816
CRC32 : 0a208184
SHA-256 : bc40f8796fda899154105d509fa7ea8e8db32816dce5245892d02186400a1abd
SHA-512 : 07f167d514335396f6c4ea6c540b7d67b2ece55284e57a8f70ec4303393746e64feab46fb185118effab3406c35e7128cec9442f16366e942f6618224de58dee
SHA-384 : 98011bee82a697b256de5f6d1b4c5b267f6429deb5ca8e7684befa612033c074e2007dc78345021da7eded18cb3d66bc
File Size : 16,408,621
Extension : zip
==================================================
FAQs :
01. Why am i releasing these after 2 months of Soak Test ?
Well, first few releases were very buggy, unstable and unusable. I decided to wait until Motorola (Lenovo) fixes them. Now that major issues have been fixed, i am releasing the files so that everyone can start using Android 7.1.1 and before the handset reaches is EOL. Motorola (Lenovo) are very slow to fix the issues and i dont expect the Soak to be completed soon. So why to suffer for their inefficiency ? Now it can be used as daily driver.
02. What are the known issues pending to be fixed ?
Few prominent users reported issues to be fixed are - Random shutdown (minor users facing it), high battery consumption (everyone), network issues (few users facing it, VoLTE issue has been fixed), scaling of graphics on lock screen (minor users facing it), vibration on receipt of notifications during call (everyone, actually Motorola (Lenovo) terms it feature instead of bug though Google has fixed in AOSP).
03. Will i get Official Download and Updates ?
This is an Official Update from an Unofficial Source. Why will you receive the same update twice No modifications have been done to these files. You will get any future OTAs Motorola (Lenovo) releases.
Steps To Update To Android 7.1.1
Save the downloaded files to Root of SD Card and follow instructions :
Method 01
Just Save the downloaded file to Root of SD Card [External Memory Card and not Internal Memory] and go to Settings --> About Phone --> System Updates. Update will be auto recognized and user will be prompted to apply update. In case update is not recognized and do not get any update prompt, then try Method 02.
Method 02 :
With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on.
Press the Volume Down button to highlight "Recovery mode"
Press the Power button to restart into Recovery mode.
You'll see an image of an Android robot with a red exclamation mark.
While holding down the Power button, press the Volume Up button.
Phone will auto reboot to Recovery Mode.
Using Volume Down Button highlight Apply update from SD Card and press Power Button.
From the contents of SD Card Listed, using Volume Up / Down button select downloaded .zip files in order (01, 02) and press Power Button to apply update.
Updatation Process will start. It will take about 30 Mins to complete updatation.
Caution : You have to apply updates one after another in serial order else update will not be applied. At Worst, you may end up with bricked handset.
Regards
XDASNR
whether i hv to download all d files?
rohitpaul9000 said:
whether i hv to download all d files?
Click to expand...
Click to collapse
Yes.. Motorola (Lenovo) has released 5 updates so far, each fixing bugs and increasing the system version.
XDASNR said:
Yes.. Motorola (Lenovo) has released 5 updates so far, each fixing bugs and increasing the system version.
Click to expand...
Click to collapse
if i put all the files in sd card will it update in sequence automatically or i have to put one file at a time????
---------- Post added at 06:02 PM ---------- Previous post was at 05:38 PM ----------
any bugs? and what about battery backup????
can i root it?
read the op and you will receive answers...
Has anyone tested?
I thought to give it a try.
First I backuped my phone, and flashed stock Indian rom and latest OTA update I had. (Mind that my device is a european XT1562 on which I have flashed Indian firmware in order to enable dual sim functionality).
Then I tried to flash the first .zip file via stock recovery, and all I got was error (status 7). It said that "package expects build fingerprint of ... MPDS24.107-70-1-5 or NPD26.42 and mine was MPDS24.107-52-11.
After searching the forum, I found a twrp backup of that exact version I needed(MPDS24.107-70-1-5)
So I just booted twrp recovery without flashing it on the phone, and restored the backup I downloaded.
Afterwards I rebooted to stock recovery and tried to flash the first zip, which again failed and I got the same message.
My system version was indeed MPDS24.107-70-1-5 at the time.
So I gave up and restored my perfectly working 6.0.1 setup.
Thanks for sharing the OTAs, but I had no luck installing them.
I guess I have to wait.
does not recognize ota
What version of the system do I need to have installed to be able to install the otas?
download from this thread " https://forum.xda-developers.com/mo...official-7-1-1-nougat-factory-update-t3626387 " and does not recognize them
2017-09-11--02-10-03_npd26.48-24-1_retasia_ds
mark_kou said:
After searching the forum, I found a twrp backup of that exact version I needed(MPDS24.107-70-1-5)
So I just booted twrp recovery without flashing it on the phone, and restored the backup I downloaded.
Afterwards I rebooted to stock recovery and tried to flash the first zip, which again failed and I got the same message.
Click to expand...
Click to collapse
Not a surprise! You need recovery and modem to be of latest version too.
But I really don't recommend to mess with OTA because you risk to get bricked. It's easy and unforgettable )
Ok folks, I'm pretty familiar with this stuff, here is ready to flash restore TWRP-backup 7.1.1 NPD26.48-24-1 for RETASIA DS model (modem and recovery also supplied). If you got different model, leave your native 6.0.1 modem on place.
I have 1 doubt , Afaik Moto never released soak ota to non soak member ,so what happen if we apply this ota and By chance Moto release 1 more ota to soak members . We will stuck on this version will be fully dependent on someone to leak that also . And aside you I don't see anyone doing this .
After installing all 5 of the updates , will the moto dev apps like Moto Survey , Perf Monitor , PM Test etc will be there or not..?
s5610 said:
Not a surprise! You need recovery and modem to be of latest version too.
But I really don't recommend to mess with OTA because you risk to get bricked. It's easy and unforgettable )
Ok folks, I'm pretty familiar with this stuff, here is ready to flash restore TWRP-backup 7.1.1 NPD26.48-24-1 for RETASIA DS model (modem and recovery also supplied). If you got different model, leave your native 6.0.1 modem on place.
Click to expand...
Click to collapse
After restore your backup, i still have to aply all the OTA updates?!:good:
martt said:
After restore your backup, i still have to aply all the OTA updates?!:good:
Click to expand...
Click to collapse
Of course not. I did all dirty job to rework OTA into ready to use 7.1.1 fresh build (final even, maybe )
Unlock needed, TWRP backup/restore experience, etc. You have to be at medium android-fu level. Please, read a bit about OTA risks
---------- Post added at 03:23 AM ---------- Previous post was at 03:21 AM ----------
debanildas said:
After installing all 5 of the updates , will the moto dev apps like Moto Survey , Perf Monitor , PM Test etc will be there or not..?
Click to expand...
Click to collapse
You mix up leaked development beta build, and public release candidate, that was just dumped and shared.
del post. its old
avi_loveindia said:
We will stuck on this version
Click to expand...
Click to collapse
Until you have locked bootloader, or RSD service ROM 7.1.1 will leak. It should happen, I'm sure.
avi_loveindia said:
I have 1 doubt , Afaik Moto never released soak ota to non soak member ,so what happen if we apply this ota and By chance Moto release 1 more ota to soak members . We will stuck on this version will be fully dependent on someone to leak that also . And aside you I don't see anyone doing this .
Click to expand...
Click to collapse
debanildas said:
After installing all 5 of the updates , will the moto dev apps like Moto Survey , Perf Monitor , PM Test etc will be there or not..?
Click to expand...
Click to collapse
The updates remain same for all and are ready to install on Moto Servers. However they limit the people who can access these updates by EMEI number which they collect during Soak Test. Once the test is over, the EMEI limit is removed and same updates are delivered to everyone. Once the Soak Test is over, i believe, everyone will get to install all these one after another OR one build with all these updates packed in one file. However the final build number or version will be same for everyone. So nothing to be afraid of.
Having said these, you will just have to wait until Soak is over for any updates to come from Moto; Until then, i will release them here for benefit
Zip Files Not Visible
I went into the recovery mode and selected the update from SD card option But the zip files i copied into the root directory are not visible to select there. What should i do?
mark_kou said:
I thought to give it a try.
First I backuped my phone, and flashed stock Indian rom and latest OTA update I had. (Mind that my device is a european XT1562 on which I have flashed Indian firmware in order to enable dual sim functionality).
Then I tried to flash the first .zip file via stock recovery, and all I got was error (status 7). It said that "package expects build fingerprint of ... MPDS24.107-70-1-5 or NPD26.42 and mine was MPDS24.107-52-11.
After searching the forum, I found a twrp backup of that exact version I needed(MPDS24.107-70-1-5)
So I just booted twrp recovery without flashing it on the phone, and restored the backup I downloaded.
Afterwards I rebooted to stock recovery and tried to flash the first zip, which again failed and I got the same message.
My system version was indeed MPDS24.107-70-1-5 at the time.
So I gave up and restored my perfectly working 6.0.1 setup.
Thanks for sharing the OTAs, but I had no luck installing them.
I guess I have to wait.
Click to expand...
Click to collapse
I have updated main post with below, however posting it for you as it is apt. Note if you dont have below builds, you can get one of Stock ROM from other threads in the forum and continue with installation.
Below is the sequence in which updates have to be applied. An update can be installed ONLY if existing version matches given after file name below. Note you can directly install a version and skip previous builds if your existing build matches one given below. Example : If your current build is 7.1.1/NPD26.48-8/8, can skip to install 01 and 02; directly install 03-05.
01. Blur_Version.26.1.42.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 6.0.1/MPDS24.107-70-1-5/5" OR "ro.build = 7.1.1/NPD26.42/34"
02. Blur_Version.26.21.8.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.42/34" OR "ro.build = 7.1.1/NPD26.48-8/8"
03. Blur_Version.26.21.16.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.48-8/8" OR "ro.build = 7.1.1/NPD26.48-16/16"
04. Blur_Version.26.21.24.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.48-16/16" OR "ro.build = 7.1.1/NPD26.48-24/24"
05. Blur_Version.26.31.1.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.48-24/24" OR "ro.build = 7.1.1/NPD26.48-24-1/1"
s5610 said:
Until you have locked bootloader, or RSD service ROM 7.1.1 will leak. It should happen, I'm sure.
Click to expand...
Click to collapse
There are other threads in this forum where in full Stock ROM is released after integrating OTAs. One of the developers will do this and until then, just wait. Same has happened when i had released OTAs for previous version.
murugunm said:
I went into the recovery mode and selected the update from SD card option But the zip files i copied into the root directory are not visible to select there. What should i do?
Click to expand...
Click to collapse
If you have copied files to Internal Memory, then you will have to choose Internal Memory instead of SD Card Option. I recommend you to move all files from Internal Memory to SD Card and apply update. In case you dont have SD Card, place one at a time in Internal Memory and apply updates.
Hi Guys
Finally i was able to activate volte on my carrier (STC-KSA) by the help of @somin.n module
You need to have unlocked bootloader and Magisk Canary installed
1. Flash the attached module via Magisk and reboot
2. Check and activate Volte in settings
3. Dial *#*#4636#*#* > check IMS service status > you should find IMS service registered and VOLTE is available
4. You are good to GO !
Edit: it look like you need a Magisk module "SELinux Permissive" to get it working with you.
Note:
I had a problem that the volte getting disabled after a reboot, in order to fix this:
1. After applying the module restart your phone
2. go to settings>network>Mobile network> wifi calling> choose "call over mobile network"
3. Turn off your phone and take out your sim card.
4. Turn it on again with sim card uninstalled.
5. Turn off your phone, install your sim card , turn it on again.
Note: i have installed vodafone UK mbn file for my phone, you may need to change mbn file for your carrier (attached Mi9T mbn files)
in order to change mbn file:
1. Download the attached Mi9T mbn
2. Extract the file and choose the desired mbn file
3. open "Volte Pixel 4.zip" and go to
Code:
/system/vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/generic/myown/
and paste your choosen MBN file.
4. Go to the mentioned flashing steps and you are good to go!
Did both ways - with my own mbn and stock zip's - no changes at all (
It only makes a Volte toggle to appear in settings - but it doesnt change anything for me
Eiad Ajam said:
Hi Guys
Finally i was able to activate volte on my carrier (STC-KSA) by the help of @somin.n module
You need to have unlocked bootloader and Magisk Canary installed
1. Flash the attached module via Magisk and reboot
2. Check and activate Volte in settings
3. Dial *#*#4636#*#* > check IMS service status > you should find IMS service registered and VOLTE is available
4. You are good to GO !
Note:
I had a problem that the volte getting disabled after a reboot, in order to fix this:
1. After applying the module restart your phone
2. go to settings>network>Mobile network> wifi calling> choose "call over mobile network"
3. Turn off your phone and take out your sim card.
4. Turn it on again with sim card uninstalled.
5. Turn off your phone, install your sim card , turn it on again.
Note: i have installed vodafone UK mbn file for my phone, you may need to change mbn file for your carrier (attached Mi9T mbn files)
in order to change mbn file:
1. Download the attached Mi9T mbn
2. Extract the file and choose the desired mbn file
3. open "Volte Pixel 4.zip" and go to
Code:
/system/vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/generic/myown/
and paste your choosen MBN file.
4. Go to the mentioned flashing steps and you are good to go!
Click to expand...
Click to collapse
I`m running Kirisakura kernel - may that be a case?
FlatOutRU said:
Did both ways - with my own mbn and stock zip's - no changes at all (
It only makes a Volte toggle to appear in settings - but it doesnt change anything for me
I`m running Kirisakura kernel - may that be a case?
Click to expand...
Click to collapse
Actually i am not sure about the mentioned kernel
I have network signal Guru installed from this thread:
https://forum.xda-developers.com/showpost.php?p=83499679&postcount=75
I am not if it has anything to do with this as well
Maaaaan u save my life,I just installed .zip in magisk and is working
does not work for me, installed my mbn and only thing I see is VoLTE switch.
pornogeroc said:
Maaaaan u save my life,I just installed .zip in magisk and is working
Click to expand...
Click to collapse
What Carrier you have?with cosmote-Greece don't working....
tasoskio said:
What Carrier you have?with cosmote-Greece don't working....
Click to expand...
Click to collapse
Vodafone I have.if u have account in myphone.gr I have upload photo in pixel 4 xl section. I haven't changed nothing in zip.i have use vodafone uk
Any chance do it without root?
masi0 said:
Any chance do it without root?
Click to expand...
Click to collapse
It's based on replacing files on your system partition, so you def need an bootloader unlock.
You could flash rom with this change and choose not to root this rom, but on stock it is not possible afaik.
Just to say many thanks Eiad Ajam and somin.n. It work for me running R11 rooted with Canary build.
I've tried many many of Mi9T mbn files with my current profile (SEA, Hong Kong CSL/1010) but still not working. Finally, I followed the below list on focusing Volte_OEM_lab (Volte_OEM_lab work before on my Oneplus 5T). Replaced with Russia - MegaPhone Region not Moscow then bingo :good:. Hope this can help some guys which still not yet VoLte.
Greece - Cosmote - H3G_Denmark_Commercial
Czech Republic - O2 - Telefonica_UK_Commercial
Belgium - Orange - Telefonica_UK_Commercial
France - Orange - Telefonica_UK_Commercial
France - Orange - Orange_Commercial_France
France - RED SFR - Telefonica_UK_Commercial
Turkey - TurkTelekom - India_Volte_Vodafone
Norway - Telenor - India_Volte_Vodafone
Belgium - Proximus - India_Volte_Vodafone
Netherlands - KPN - Norway Telia Commercial
Brazil - Claro - Telefonica_UK_Commercial
Switzerland - Wingo (Swisscom) - Netherlands_VoLTE_Vodafone
Kenya - Faiba - ROW_Commercial
Australia - Optus - Telefonica_UK_Commercial
Sri Lanka - Dialog - India_Volte_Vodafone
Canada - Telus - Telefonica_UK_Commercial
Canada - Bell - Telefonica_UK_Commercial
Romania - Vodafone RO - India_Volte_Vodafone
Romania - Orange RO - India_Volte_Vodafone
Mexico - ALTAN - Telefonica_UK_Commercial
Israel - Partner - Telefonica_UK_Commercial
Israel - 012 mobile - Telefonica_UK_Commercial
ksa Saudi Arabia - Zain ksa - Germany
ksa Saudi Arabia - Zain ksa - Telefonica_UK_Commercial
ksa Saudi Arabia - Zain ksa - India_Volte_Vodafone
Slovakia - Orange - DT_Slovakia_Commercial
Australia - Telstra - Telefonica_UK_Commercial
Brazil - TIM - Volte_OEM_lab
Poland - Orange - DT_Poland_Commercial
Russia - All Carriers - Telia_Finland
Russia - MegaPhone Region not Moscow - Volte_OEM_lab
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-activate-volte-vowifi-t4116051
where i can find Telia_Finland .mbn file?
I am using CSL as well... but I cannot find Volte_OEM_lab in mbns-mi9t.zip, not sure which one
yiufey said:
Just to say many thanks Eiad Ajam and somin.n. It work for me running R11 rooted with Canary build.
I've tried many many of Mi9T mbn files with my current profile (SEA, Hong Kong CSL/1010) but still not working. Finally, I followed the below list on focusing Volte_OEM_lab (Volte_OEM_lab work before on my Oneplus 5T). Replaced with Russia - MegaPhone Region not Moscow then bingo :good:. Hope this can help some guys which still not yet VoLte.
Greece - Cosmote - H3G_Denmark_Commercial
Czech Republic - O2 - Telefonica_UK_Commercial
Belgium - Orange - Telefonica_UK_Commercial
France - Orange - Telefonica_UK_Commercial
France - Orange - Orange_Commercial_France
France - RED SFR - Telefonica_UK_Commercial
Turkey - TurkTelekom - India_Volte_Vodafone
Norway - Telenor - India_Volte_Vodafone
Belgium - Proximus - India_Volte_Vodafone
Netherlands - KPN - Norway Telia Commercial
Brazil - Claro - Telefonica_UK_Commercial
Switzerland - Wingo (Swisscom) - Netherlands_VoLTE_Vodafone
Kenya - Faiba - ROW_Commercial
Australia - Optus - Telefonica_UK_Commercial
Sri Lanka - Dialog - India_Volte_Vodafone
Canada - Telus - Telefonica_UK_Commercial
Canada - Bell - Telefonica_UK_Commercial
Romania - Vodafone RO - India_Volte_Vodafone
Romania - Orange RO - India_Volte_Vodafone
Mexico - ALTAN - Telefonica_UK_Commercial
Israel - Partner - Telefonica_UK_Commercial
Israel - 012 mobile - Telefonica_UK_Commercial
ksa Saudi Arabia - Zain ksa - Germany
ksa Saudi Arabia - Zain ksa - Telefonica_UK_Commercial
ksa Saudi Arabia - Zain ksa - India_Volte_Vodafone
Slovakia - Orange - DT_Slovakia_Commercial
Australia - Telstra - Telefonica_UK_Commercial
Brazil - TIM - Volte_OEM_lab
Poland - Orange - DT_Poland_Commercial
Russia - All Carriers - Telia_Finland
Russia - MegaPhone Region not Moscow - Volte_OEM_lab
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-activate-volte-vowifi-t4116051
Click to expand...
Click to collapse
chankeung1217 said:
I am using CSL as well... but I cannot find Volte_OEM_lab in mbns-mi9t.zip, not sure which one
Click to expand...
Click to collapse
The mbn file should inside below path of mi9t.zip :
mbns-mi9t.zip\russia\megafon\commerci\ru\mcfg_sw.mbn
Extract it and replaced with the :
VOLTE_Pixel_4.zip\system\vendor\rfs\msm\mpss\readonly\vendor\mbn\mcfg_sw\generic\myown\mcfg_sw.mbn
PS: No selinux_permissive is required.
Good luck.
yiufey said:
The mbn file should inside below path of mi9t.zip :
mbns-mi9t.zip\russia\megafon\commerci\ru\mcfg_sw.mbn
Extract it and replaced with the :
VOLTE_Pixel_4.zip\system\vendor\rfs\msm\mpss\readonly\vendor\mbn\mcfg_sw\generic\myown\mcfg_sw.mbn
PS: No selinux_permissive is required.
Good luck.
Click to expand...
Click to collapse
Just tried... no luck for me
I've flashed this one, it work for me all the day.
yiufey said:
I've flashed this one, it work for me all the day.
Click to expand...
Click to collapse
Wow, this worked for me! Russia - megafon
chankeung1217 said:
Just tried... no luck for me
Click to expand...
Click to collapse
When I updated to R11 with Oct security update, the VoLte broken again and it unable activated since remove/add few times.
Luckily, It worked again when I added SELinux Permissive back.
Please try it again with my flow.
yiufey said:
When I updated to R11 with Oct security update, the VoLte broken again and it unable activated since remove/add few times.
Luckily, It worked again when I added SELinux Permissive back.
Please try it again with my flow.
Click to expand...
Click to collapse
This is true!
Thank you so much
I've added this to the post
Eiad Ajam said:
Hi Guys
Finally i was able to activate volte on my carrier (STC-KSA) by the help of @somin.n module
You need to have unlocked bootloader and Magisk Canary installed
1. Flash the attached module via Magisk and reboot
2. Check and activate Volte in settings
3. Dial *#*#4636#*#* > check IMS service status > you should find IMS service registered and VOLTE is available
4. You are good to GO !
Edit: it look like you need a Magisk module "SELinux Permissive" to get it working with you.
Note:
I had a problem that the volte getting disabled after a reboot, in order to fix this:
1. After applying the module restart your phone
2. go to settings>network>Mobile network> wifi calling> choose "call over mobile network"
3. Turn off your phone and take out your sim card.
4. Turn it on again with sim card uninstalled.
5. Turn off your phone, install your sim card , turn it on again.
Note: i have installed vodafone UK mbn file for my phone, you may need to change mbn file for your carrier (attached Mi9T mbn files)
in order to change mbn file:
1. Download the attached Mi9T mbn
2. Extract the file and choose the desired mbn file
3. open "Volte Pixel 4.zip" and go to
Code:
/system/vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/generic/myown/
and paste your choosen MBN file.
4. Go to the mentioned flashing steps and you are good to go!
Click to expand...
Click to collapse
will this work on Pixel 5? and which MBN should I use? thanks in advance
Great news will give it a shot.
Out of subject, I'm wandering if stcpay still not working with root ?
Thanks