How To Guide Converting Japanese Pixel 6 to Global version - Google Pixel 6

I live in a country with no Pixel availability and end up purchasing one in Japan.
Limitations(mostly forced shutter and screenshot sound) on Japan phones can be pretty annoying, so I researched a bit on how to remove those.
Search leads me to this reply by @ziand for same trick but on Pixel 5. Turns out Pixel 6 is different but similar. So I'll summarize what I've done here.
At the same time @ziand may also work on a magisk module or something when possible, doing the same thing but in a much safer way. Once his work is done please switch to his method.
Disclaimer
I'm not familiar with law in every country but doing this could have risk. Research before acting.
The instructions requires basic Linux/Android knowledge. You could brick your phone if not knowing what you're doing. You can always wait for ziand's work for more safety.
I confirm this works on my phone. But I'm not responsible for anything happens on yours. Use at your own risk.
Click to expand...
Click to collapse
Spoiler: steps
1. Root your phone
2.
adb shell
su
dd if=/dev/block/by-name/devinfo of=/sdcard/devinfo.img
Click to expand...
Click to collapse
3. Quit adb shell, then
adb pull /sdcard/devinfo.img
Click to expand...
Click to collapse
Keep this file as backup
4. Use a hex editor, open the "devinfo.img" pulled in step 3, find "GR1YH", it should be in 0x000000F7, edit it to "GB7N6", save as "devinfo_modified.img"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5.
adb push ./devinfo_modified.img /sdcard/
adb shell
su
dd if=/sdcard/devinfo_modified.img of=/dev/block/by-name/devinfo
Click to expand...
Click to collapse
6. Reboot and enjoy
This should be permanent, you can also revert root if you want.

Thank you HarryShan. It's confirmed work for me. Much appreciated for your share.

Do I need to unlock bootloader to root sir?

norman00037 said:
Do I need to unlock bootloader to root sir?
Click to expand...
Click to collapse
Yes. Please refer to the rooting guide I've linked to

Thank you HarryShan! It's worked for me)

Hi,
Someone tried this on pixel 5a?
I dealing with the same anoying japanese problem.

Curious if this would adversely affect NFC function as the Japanese model is NFC-F.

you did it with non rooted phone, right? and how did you do it without TWRP?

HarryShan said:
At the same time @ziand may also work on a magisk module or something when possible, doing the same thing but in a much safer way. Once his work is done please switch to his method.
Click to expand...
Click to collapse
Here is below a script to convert the device to another version.
About versions of Google Pixel 6, Product ID oriole :
Model IDs:
G9S9B - Verizon and AT&T US carriers
GB7N6 - US Unlocked, US Google Fi, US TMO, Canada, Taiwan, Australia, Europe countries and carriers
GR1YH - Japan and carriers
Script for changing Model ID
for devices: Google Pixel 5, 6/pro, 6a, 7/pro​Prerequisites
TWRP or Magisk 20.4+
Downloads
Magisk module: MID_Changer_v2.10-MAGISK-TWRP.zip
Change log
-v2.10 : Pixel 7 added
- v2.09 : Pixel 7pro added
- v2.08 : Pixel 6a added
Example running image:
To apple changing, flash global Factory Image with erasing data. You can use Android Flash Tool with locked bootloader option.

ziand said:
Here is below a script to convert the device to another version.
About versions of Google Pixel 6, Product ID oriole :
Model IDs:
G9S9B - Verizon and AT&T US carriers
GB7N6 - US Unlocked, US Google Fi, US TMO, Canada, Taiwan, Australia, Europe countries and carriers
GR1YH - Japan and carriers
Script for changing Model ID on Pixel 6​Prerequisites
Your phone has to be rooted
Downloads
Magisk module: MID_Changer_v2.04-MAGISK.zip
Installation instruction
Download and install Magisk module above.
Running instruction
Variant 1 with commands from PC:
Code:
adb shell
su
MID_Changer.sh
Example image:
View attachment 5471525
Shorter Variant 1 with commands for PC:
Code:
adb shell
su -c MID_Changer.sh
Variant 2 with commands without PC.
Also you can use for example Android Terminal Emulator with commands:
Code:
su
MID_Changer.sh
To apple changing, flash global Factory Image with erasing data.
Recommendations
If someone wouldn't like to use root in the future, he can lock bootloader by the command at bootloader mode:
Code:
fastboot flashing lock
or use parameter "Lock bootloader" at flashing Factory Image via Android Flash Tool.
Click to expand...
Click to collapse
thank you very much. I tried and succeeded. my pixel 6 can mute the shutter sound. but after inserting the Japan sim, the sound comes back. so sad. I don't know is there any other solution?

h281994 said:
thank you very much. I tried and succeeded. my pixel 6 can mute the shutter sound. but after inserting the Japan sim, the sound comes back. so sad. I don't know is there any other solution?
Click to expand...
Click to collapse
Did you flash Factory Image with erasing data, factory reset ?
The converting is success if you have:
- new Model ID in bootloader - Barcode -SKU;
- new Model ID in Settings - About phone - Regulatory Labels;
- appeared option to switch off the sound in settings of stock Camera app.
Do you have all of them ? Show some pictures.

ziand said:
Did you flash Factory Image with erasing data, factory reset ?
The converting is success if you have:
- new Model ID in bootloader - Barcode -SKU;
- new Model ID in Settings - About phone - Regulatory Labels;
- appeared option to switch off the sound in settings of stock Camera app.
Do you have all of them ? Show some pictures.
Click to expand...
Click to collapse

@h281994, are you in Japan ?
I think to necessary to check how is with it on original non-Japanese phone with any sim there ?

ziand said:
@h281994, are you in Japan ?
I think to necessary to check how is with it on original non-Japanese phone with any sim there ?
Click to expand...
Click to collapse
Yes i am working in japan, i tried inserting softbank sim, sadly the camera sound is back again and the setting to turn off shutter sound is gone.I tried removing the sim and restarting the device ...the setting to turn off camera sound appeared again. very happy

Do you have possibility to insert another sim not softbank and maybe not Japanese carrier at all ? it is interesting how with this sound on other pixels 6 not Japanese versions there in Japan.

h281994 said:
Yes i am working in japan, i tried inserting softbank sim, sadly the camera sound is back again and the setting to turn off shutter sound is gone.I tried removing the sim and restarting the device ...the setting to turn off camera sound appeared again. very happy
Click to expand...
Click to collapse
This is known issue as even global Pixel do have forced shutter and screenshot sound when a Japanese carrier SIM is inserted, no matter where you use it. In this case MID changing method can't help you.
The module from the other thread may work though as it's directly modifying system UI APK:
GitHub - AndroPlus-org/magisk-module-pixel6: Google Pixel 6シリーズ以降向けのMagiskモジュールです。
Google Pixel 6シリーズ以降向けのMagiskモジュールです。. Contribute to AndroPlus-org/magisk-module-pixel6 development by creating an account on GitHub.
github.com
Downside would be you'll always need Magisk installed. You can have a try.

ziand said:
Here is below a script to convert the device to another version.
About versions of Google Pixel 6, Product ID oriole :
Model IDs:
G9S9B - Verizon and AT&T US carriers
GB7N6 - US Unlocked, US Google Fi, US TMO, Canada, Taiwan, Australia, Europe countries and carriers
GR1YH - Japan and carriers
Script for changing Model ID on Pixel 6​Prerequisites
Your phone has to be rooted
Downloads
Magisk module: MID_Changer_v2.05-MAGISK.zip
Installation instruction
Download and install Magisk module above.
Running instruction
Variant 1 with commands from PC:
Code:
adb shell
su
MID_Changer.sh
Example image:
View attachment 5471525
Shorter Variant 1 with commands for PC:
Code:
adb shell
su -c MID_Changer.sh
Variant 2 with commands without PC.
Also you can use for example Android Terminal Emulator with commands:
Code:
su
MID_Changer.sh
To apple changing, flash global Factory Image with erasing data.
Recommendations
If someone wouldn't like to use root in the future, he can lock bootloader by the command at bootloader mode:
Code:
fastboot flashing lock
or use parameter "Lock bootloader" at flashing Factory Image via Android Flash Tool.
Click to expand...
Click to collapse
I can't use this module for my Pixel 6 pro Japan. How can I use .
Thank you!

khoanx said:
I can't use this module for my Pixel 6 pro Japan. How can I use .
Thank you!
Click to expand...
Click to collapse
Of course, because Pixel 6 and Pixel 6 pro are different devices.
Pixel 6 is Product ID "oriole" and Pixel 6 pro Product ID "raven". For now the module v2.05 and less is for Pixel 6 only.
Send me to PM some info from your device to upgrade this for Pixel 6 pro too. No problem, I will add everything into the script for converting.

I use HarryShan's guide. And change GF5KQ to GLU0G for my Pixel 6 Pro. It worked. My phone don't have sound when capture sceen and take photo.
Thank you.

HarryShan said:
This is known issue as even global Pixel do have forced shutter and screenshot sound when a Japanese carrier SIM is inserted, no matter where you use it. In this case MID changing method can't help you.
The module from the other thread may work though as it's directly modifying system UI APK:
GitHub - AndroPlus-org/magisk-module-pixel6: Google Pixel 6シリーズ以降向けのMagiskモジュールです。
Google Pixel 6シリーズ以降向けのMagiskモジュールです。. Contribute to AndroPlus-org/magisk-module-pixel6 development by creating an account on GitHub.
github.com
Downside would be you'll always need Magisk installed. You can have a try.
Click to expand...
Click to collapse
You can also use a gcam mod camera for silent shutter . There used to be a workaround for the silent camera by simswapping in Japan but it was removed or patched in android 12. A Japanese sim will always enable sounds

Related

[FAQ] Frequently Asked Questions For Moto E (2015) [UPDATED-3/7/2015]

Frequently Asked Questions
Motorola Moto E
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello Guys this is a FAQ for Moto E(2015) . Please read this here before posting it in the developmental section or creating a thread anywhere.
I am sure it will help.
Thank You
A big thanks goes to @matmutant for providing FAQ templates and his own FAQ from I have copied some things.Here is the original guide
[SIZE=+1]Q1: How to access Fastboot?[/SIZE]Hold PowerButton and VolDown during boot.​
[SIZE=+1]Q2: How to unlock Bootloader?[/SIZE]Boot to Fastboot and
follow my guide
Motorola guide on Motorola's website
[SIZE=+1]Q2: How to relock Bootloader?[/SIZE]Boot to Fastboot and give the command "fastboot oem lock"​
[SIZE=+1]Q3: How do i get adb and fastboot drivers ?[/SIZE]For windows, follow this guide or this one
although, it seems Motorola Device Manager works ok for win7x86-32 (but not for win7x64-64?) i cannot answer this i'm under linux
other USB drivers if first method failed, source
For Linux, get fastboot files here also, adb and fastboot can be installed using repos for ubuntu-based distros packages needed are : android-tools-adb and android-tools-fastboot (android-tools-fsutils may be useful too)
eg:
Code:
sudo apt-get install android-tools-fastboot
[SIZE=+1]Q4: How to flash Stock Firmware?[/SIZE]Please Follow My Guidehere.​
[SIZE=+1]Q5: How to Root my device ?[/SIZE]First you'll need to unlock your bootloader,
then follow this guide
​
[SIZE=+1]Q6: Where can i find a Custom recovery ?[/SIZE]Yet to be uploaded​
[SIZE=+1]Q7: How to access bootloader?[/SIZE]- Via ADB :
Code:
adb reboot bootloader
- The hard(ware) way :
With the phone powered off, press the VOL DOWN KEY for 2-3 seconds then POWER key then release.
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
[SIZE=+1]Q8: How to access recovery?[/SIZE]
using terminal, if the device is already rooted
Code:
su
reboot recovery
via adb
Code:
adb reboot recovery
via bootloader
boot to bootloader (see Q11) and select recovery (use Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select)
[SIZE=+1]Q9: How to force reboot my frozen device?[/SIZE]
Press and hold the Power button for 10 - 20 seconds, the device will restart and go through the boot-up sequence [source]
(VOL DOWN hold + a quick tap on POWER should force reboot when in bootloader) [source]
[SIZE=+1]Q10: How to charge my device and extend battery life?[/SIZE]Follow Motorola tips:
How do I properly charge my device?
How can I extend my battery life?
[SIZE=+1]Q11: Does rooting/unlocking your phone invalidate its warranty? (In EU)[/SIZE]In short: No. Just the fact that you modified or changed the software of your device, is not a sufficient reason to void your statutory warranty. As long as you have bought the device as a consumer in the European Union.
For Indian customers, The warranty is void if you unlock/root your device. Motorola also reserves the right to maintain the records of unlocked bootloader devices. So you may not even get the warranty by relocking the device
[source]​
[SIZE=+1]Q12: What to do if my battery is fully discharged and not re-charging?[/SIZE][source]​
[SIZE=+1]Q13: Lost IMEI ? : How to backup / restore PDS partition and why?[/SIZE]On Motorola devices the 'pds' partition contains information specific to your machine: IMEI, MAC address, serial number, etc. This partition can be lost by accidental format or over time due to filesystem corruption. If you have made a backup, there is a good chance you can bring your handset back to life.
==> PDS backup will help to restore lost IMEI. It is a situation when the phone reports that the IMEI is unknown. ; This works like a vaccine, apply before having issue with IMEI, after it will be too late !
Instructions:
**Root Required**
Using ADB you can make a copy of the partition and move it to a safe place (Google Drive?):
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/pds of=/sdcard/pds.img​
To restore in the event of corruption or loss:
adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds​(assuming you've pushed pds.img to internal SDcard storage first)
If for some reason this doesn't work, maybe your IMEI isn't destroyed but only not "readable" by system (file system issue? misread cluster reading frame ? no idea), in that case you may read the following story : http://forum.xda-developers.com/showthread.php?p=52648789
​
[SIZE=+1]Q14: How to disable/enable auto On/Off screen with Flip Shell?[/SIZE]
for stock rom : (disabling, since it's enabled by default)
install Xposed framework (and reboot)
install and enable MotoMagnetOff (and reboot)
Follow this FAQ​
[SIZE=+1]Q15: How to remove the 'unlocked warning' message?[/SIZE]Follow my guide here and default Motorola logo will be back .​
[SIZE=+1]Q16: How to reboot into 'safe mode'?[/SIZE]
Press power button, on the pop up, either keep pressing 'shut down' [stock] or 'reboot' [AOSP based]
more infos about this feature​
[SIZE=+1]Q17: What are the Moto E tech specs[/SIZE]
XT1527, XT1511 - for USA
XT1505 - Global model
[SIZE=+1]Q18: How to get OTA updates even after Rooting and Flashing a custom Recovery[/SIZE]
Use the full unroot option from the Super Su
Flash the stock recovery Use Code : mfastboot flash recovery recovery.img
Now you'll be able to get OTA updates as before
[SIZE=+1]Q19: How to Unlock Advanced Camera Settings?[/SIZE]
Refer to this thread​
some usefull lines of commands for any user wanting to know what's going on:
requirements :
On Windows : install Moto E drivers and
On Linux : set your rules following that guide (3. Set up your system to detect your device.) : add to /etc/udev/rules.d/51-android.rules the following code
Code:
#motoe normal mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e82″, MODE="0666"
#motoe debug mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e76″, MODE="0666"
#motoe fastboot mode
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}==”2e80″, MODE="0666"
For specific access by one group of users, add GROUP="[groupname]"
______________________________
______________________________
______________________________​
Let's start ! :
in terminal, just type the lines,
in ADB, add "adb" before the commands
if you want not to display the output in terminal, specify the path :
Code:
command > /where_you_want_your_output_to_be_stored/name_you_want_for_the_log
to know if KSM is really turned on : KSM means Kernel Samepage Merging, may not exist on Moto E stock or custom roms
Code:
cat /sys/kernel/mm/ksm/run
to know what modules are running :
Code:
lsmod
install an app from terminal :
Code:
pm install /sdcard/app1.apk
from adb :
Code:
adb install /home/user/app1.apk
(if your .apk is located there )
your kernel crashed?
Code:
cat /proc/last_kmsg
ex : from adb, and stored in /home/user/last_kmsg1
Code:
adb cat /proc/last_kmsg > /home/user/last_kmsg1
an app crashed, you want to know why?
Code:
logcat
ex : from adb and stored in /home/user/myfirstlogever
Code:
adb logcat > /home/user/myfirstlogever
don't have an USB cable ?or adb "other the air" :
connect to your home wifi network (both device and pc)
in settings/dev options/ enable adb on TCP/IP
Code:
adb connect xxx.xxx.xxx.xxx:5555
(the IP is the one displayed in the option you choose previously
and then, since it is connected, catch the log :
Code:
adb logcat > /home/user/myfirstlogever
All commands and syntax used for ADB can be found here
Reserved
This is a WIP for now. Thread will be updated soon
My only question about this phone is if it has the autofocus feature or not (as was happened with 1st gen of it)
Lucas Eugene said:
This is a WIP for now. Thread will be updated soon
Click to expand...
Click to collapse
Lucas, have you tested the root method on the 2015 Moto E yet?
qbking77 said:
Lucas, have you tested the root method on the 2015 Moto E yet?
Click to expand...
Click to collapse
Updated thread now. You can visit the root thread
Lucas Eugene said:
This is a WIP for now. Thread will be updated soon
Click to expand...
Click to collapse
Bro,U tested moto e 2015 before it's arrival in the market.that's good
---------- Post added at 01:31 PM ---------- Previous post was at 01:25 PM ----------
Antonio Li said:
My only question about this phone is if it has the autofocus feature or not (as was happened with 1st gen of it)
Click to expand...
Click to collapse
Me too have the same doubt that it has auto focus cam or not.because I had moto e gen1 which has an average cam with manual exposure
Antonio Li said:
My only question about this phone is if it has the autofocus feature or not (as was happened with 1st gen of it)
Click to expand...
Click to collapse
suryaz124 said:
Bro,U tested moto e 2015 before it's arrival in the market.that's good
---------- Post added at 01:31 PM ---------- Previous post was at 01:25 PM ----------
Me too have the same doubt that it has auto focus cam or not.because I had moto e gen1 which has an average cam with manual exposure
Click to expand...
Click to collapse
Yes I suppose it has
confirmed
changing default install location
I am having trouble changing the default install location. I've used the command "adb shell pm set-install-location 2" and I received an error "error: java.lang.SecurityException: Package android does not belong to 2000." Anybody else getting this error? How do I go about fixing this issue? I am running stock 5.02 and getting this error before and after I unlocked the bootloader. Thank you.
Can't unlock bootloader
I have Cricket and my phone is not eligible to unlock the boot loader. Is there a workaround for this yet?
can i buy this phone .. is good ?? please help me ..
Sent from my 7236 2G using Tapatalk
Are the guides here the same for the 3G variant vs the LTE one? I'm thinking they are.
I scored a free Moto E 3G version for free when the wife ordered her Moto X from Motorola.com. Figured I'd just play with it. Thanks
apristel said:
Are the guides here the same for the 3G variant vs the LTE one? I'm thinking they are.
I scored a free Moto E 3G version for free when the wife ordered her Moto X from Motorola.com. Figured I'd just play with it. Thanks
Click to expand...
Click to collapse
The guides for unlocking bootloader etc. should be the same. Just don't flash LTE images on the 3G model, as they have completely different processors.
The CPU in the 3G model is actually rather similar to the first gen E, but beefed up with more cores. It may be possible to port Moto E 1st gen stuff to the 3G version fairly easily. I was thinking of getting a 3G model to tinker with, but unfortunately they are not available in Canada and I can't justify the cost of importing one myself.
It's a shame that Motorola hasn't released stock firmware images for this model. There is a leak for the European LTE model (that might work on North American ones with an unlocked bootloader). There are no stock images for the 3G out there yet.
squid2 said:
The guides for unlocking bootloader etc. should be the same. Just don't flash LTE images on the 3G model, as they have completely different processors.
The CPU in the 3G model is actually rather similar to the first gen E, but beefed up with more cores. It may be possible to port Moto E 1st gen stuff to the 3G version fairly easily. I was thinking of getting a 3G model to tinker with, but unfortunately they are not available in Canada and I can't justify the cost of importing one myself.
It's a shame that Motorola hasn't released stock firmware images for this model. There is a leak for the European LTE model (that might work on North American ones with an unlocked bootloader). There are no stock images for the 3G out there yet.
Click to expand...
Click to collapse
OK thanks! Funny you are in Canada. I ended up selling it to my friend in Canada. Its on its way there now.
WiFi tether
Has anyone managed to get WiFi tether working on their moto e 2015
Please update the thread
The recovery and root method for 3g version are working. @Lucas Eugene.
By the way this device is lagging like hell sometimes. Is it the memory leak problem.
How to solve it.
Ravx said:
Please update the thread
The recovery and root method for 3g version are working. @Lucas Eugene.
By the way this device is lagging like hell sometimes. Is it the memory leak problem.
How to solve it.
Click to expand...
Click to collapse
I'll update it asap with a lot of other things.
Don't if it works for you but you can try clearing cache/art cache and then compare
mdewii23 said:
I have Cricket and my phone is not eligible to unlock the boot loader. Is there a workaround for this yet?
Click to expand...
Click to collapse
No, much like the VZW variant I have. No root for us.

Enable 4G+/4.5G Carrier Aggregation on Mi9 - For Rooted Device

Hello
China Packages have limited active Bands and Aggregation is not active on Global Bands! This guide will help you to remove that limit and active global bands easily!
Because of new security patch, your device must be rooted to be able to activate Diag Port!
I have edited the needed file and all you need is below files, So download them and do the rest:
Files Required
1. IMEI Converter
https://www.mediafire.com/file/4qkiwnglhnejtmb/IMEI_Converter.exe/file
2. QPST Flash Tools
https://androiddatahost.com/w68st
3. Notepad++
And the Important File
https://www.mediafire.com/file/k5yccs1ih2islv8/EditedQCN.xqcn/file
Guide:
First thing First:
I'm Not Responsible for any Damage caused to your phone
Use QPST Flash tools and make a backup, So if any thing happened wrong you can restore it easily!
For start, the Diag Port must be on:
There are two ways to enable diagnostic mode after root which are as follows:
1. ADB
Enable "USB Debugging"on your phone.
Connect it to your PC/Laptop.
Open "Minimal ADB & Fastboot" Command Prompt with administrative rights.
Type adb devices and press enter.
Type adb shell and press enter.
Type su and press enter.
Type setprop sys.usb.config diag,adb and press enter.
2. Terminal Emulator App
Install any "Terminal Emulator" app from play store e.g. Termux
Enable "USB Debugging"on your phone.
Connect it to your PC/Laptop.
Open "Termux" .
Type su and press enter.
Type setprop sys.usb.config diag,adb and press enter.
If got success you must see the Diag Port in Device Manager like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So let's start,Connect phone to PC:
1- Open QPST and make a backup
Save the file for any further problem
Now use the IMEI Converter and convert your IMEI to HEX!
NOW:
Open Editedqcn file with Notepad++
1. Find the line zz zz zz zz zz zz zz zz zz
Replace them with the HEX number of your FIRST IMEI
2.Find the line xx xx xx xx xx xx xx xx xx
Replace them with the HEX number of your Second IMEI
3.Find your WIFI Mac address- Go to setting/My device/All specs/status
Find the lines(4 lines) zx zx zx zx zx zx
replace them with your WIFI MAC (the mac is already in HEX so, no need to change just find the exact)
4.Now save the file
Open QPST and thsi time choose restore tab, browse for qcn file that edited and restore it in your phone! Wait for 10 second and then unplug the phone!
Restart
And Boom
Now 4G+
After doing the whole procedure our device have permanent support to carrier aggregation? Flashing from global to China beta for example we have to flag this again?
Sent from my MI 9 using Tapatalk
AlexanderKgr said:
After doing the whole procedure our device have permanent support to carrier aggregation? Flashing from global to China beta for example we have to flag this again?
Click to expand...
Click to collapse
I don't think so...! Fastboot flash won't change files to original state!
i already have 4g+ on my phone without doing any of that...am i missin something?
No for sure
AlexanderKgr said:
After doing the whole procedure our device have permanent support to carrier aggregation? Flashing from global to China beta for example we have to flag this again?
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
No, NV files doesn't related to ROM!
bilal91 said:
i already have 4g+ on my phone without doing any of that...am i missin something?
Click to expand...
Click to collapse
This guide is for Chinese packages that don't aggregate bands in other countries !
One question:
This procedure unlock BAND 28 in chinese phones too?
Because I buy a chinese one (in a Xiami store in Shangai) and use it in Brazil. When I was in São Paulo I already saw 4G+. but I don´t know if it was using BAND 28.
Thanks
thanks for your work, I did everything as instructed and BOOM... no 4G+
SpeedoFST said:
thanks for your work, I did everything as instructed and BOOM... no 4G+
Click to expand...
Click to collapse
I believe that this is carrier dependent also, so if your carrier doesn't support aggregation, then no use about all this process!
Let's use my example, i have global version of this phone and all of this is natively supported and when i am within reach of my carrier station then i have 4G+ sign, but when is other way around then there is no 4G+ icon, no carrier aggregation!
If I put my sim card in my old Samsung s8 I have full range 4G+, on Mi9 full range 4G only. So I'm sure it's the Mi9's fault.
I am using xiaomi.eu and I get 4g+ on mine. I suppose I don't have to do this, right.
Can this support b20 on chinese device model?
SpeedoFST said:
If I put my sim card in my old Samsung s8 I have full range 4G+, on Mi9 full range 4G only. So I'm sure it's the Mi9's fault.
Click to expand...
Click to collapse
Excellent!
Then You know 100% that there is a "fault" on Mi 9 side but again, if You have Global-EEA Version and not Chinese then this is strange because all this bands should be already unlocked-enabled in Global-EEA version of this device.
Now it's cross my mind, what type of ROM is on Your device?!
Is it Global ROM or EEA ROM?!
I believe that I heave red on some forum that if You are in EEA region then it's better to flash this ROM on device because there is also some modem drivers discrepancy between Global and EEA version of the ROM (if You compare sizes of corresponding files in those two ROM's, You will see that they are different also).
Now, maybe I'm wrong but I also have this EEA ROM on my device and just as i have said, at me this carrier aggregation is working as it should.
SpeedoFST said:
thanks for your work, I did everything as instructed and BOOM... no 4G+
Click to expand...
Click to collapse
dude, at the first line of the thread i said that it is for china packages used in a country with aggregation support!
You are right, your carrier doesn't support aggregation!
head_djmusic said:
dude, at the first line of the thread i said that it is for china packages used in a country with aggregation support!
You are right, your carrier doesn't support aggregation!
Click to expand...
Click to collapse
U mean for Chinese version of mi9 right?
Enviado desde mi MI 9 mediante Tapatalk
Yes, The Chinese packages have limited bands!
head_djmusic said:
Yes, The Chinese packages have limited bands!
Click to expand...
Click to collapse
i cant see my phone in qpst , i cant continue, soime help please
head_djmusic said:
Yes, The Chinese packages have limited bands!
Click to expand...
Click to collapse
I was in the part of the back up but my device doesn't appear in the list, I'm using w10 pro, version 1903
Enviado desde mi MI 9 mediante Tapatalk
SpeedoFST said:
If I put my sim card in my old Samsung s8 I have full range 4G+, on Mi9 full range 4G only. So I'm sure it's the Mi9's fault.
Click to expand...
Click to collapse
Put your SIM card in the S8+, turn on mobile data and wait till you connect to 4G+, then open the dialer and dial *#0011#, press STACK1 if the SIM is in slot 1, and STACK2 if in slot 2.
You'll get to a ServiceMode screen, take a screenshot of that and post it here. The phone may be using bands that the Mi9 doesn't support.
partially works
I have a Mi 9 Chinese, 6/128. I did all the procedures correctly, and it shows that I have 4G + on the screen, but when I try to use some application / browser, there is no connection. Any suggestions what might be wrong?

How To Guide 5II/1&5III VoLTE patch. [Guide to release the root]

In the Xperia user group in
cafe.naver.com/x1smart
I'm HTCMAGE.
Last year, Xperia 1II.
How to activate VoLTE.
After the guide version,
VOLTE Success, Activation without Firmware Replacement (Sony Mobile withdrawal area)
Hello Xperia users! In the meantime, I finally solved the VOLTE problem! I approached Qualcomm's diagnostic port-active-efsExplorer and solved the problem by inserting a VOLTE profile from my carrier :) Sorry, this is Korea and I am Korean...
forum.xda-developers.com
5II and...
Xperia's 1III/5III products.
Activating VoLTE and...
"Root".
I'll share how to turn it off.
I am not good at English.
I use the translator.
Please understand.
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader
Later, to unlock.
Maejiseukeu manager app.
Patch. magiskFiles img
While connected to your computer with a usb
You can use the instructions below at least adb.
adb reboot bootloader && fastboot flash boot "magisk.img" && fastboot reboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then, you can install it.
It's going to rebooted.
This is the restart screen. It's connected to USB.
Always allow debugging when enabled.
Connect to Wi-Fi and do not log in.
Please move on quickly.
Turn off the internet quickly (Mobile data X)
Save the magisk manager app on your computer.
Then go to Xperia and install it.
github.com/topjohnwu/Magisk/releases/tag/v23.0
Please make sure the Internet is turned off.
I'll carry it out. Magisk Manager in the upper right corner.
Cogwheel - Setting page - Middle.
Activate "Hide".
When it's done, we'll start the VoLTE patch.
At least ADB.
Adb shell.
Enter and enter.
su
If you type it in,
In the same window as the picture below,
If you allow it,
The shape of the dollar...
It changes to #.
setprop persist.usb.eng 1
Enter and enter.
It's from My Computer Properties Device Manager.
There are several floating yellow exclamation marks.
Drive manually.
Please hold it.
Among the yellow exclamation points,
We don't know which part is connected.
Please select a few targets and update them manually.
Update Driver - Browse to My Computer
Directly select the list available on your computer.
Port-QUALCOM 9081 choice.
Starting with the ELS Explorer selection LAHA (based on 1 III).
This is something that can go in. If you connect...
Please copy and paste the EBS file.
(Use the mouse to pull it in and put it in twice.)
I'll make a folder that doesn't exist.
Put it in twice.
Policyman folder delete the existing one.
You can put it in and the NV at the top...
Likewise, place it at the top.
Close the window when done.
adb shell su -c setprop persist.dbg.volte_avail_ovr 1
adb shell su -c setprop persist.dbg.vt_avail_ovr 1
And then "adb reboot".
If you type Enter, we'll reboot you.
On the basic Soonjung phone app,
Check IMS status in *#*#4636#*
If it's available, it's good.
Wi-Fi or data on.
Log in various ways. Google, Sony accounts,
Update the Play Store and...
Various basic apps (Netflix)
Update everything.
And information on the bottom of the Play Store,
It should say play protection certification.
If you run the magisk manager app,
If you check out the following,
I reboot on my own.
Reboot and run the manager app again.
Please press "Remove the Magisk".
Completely removed.
Then I'll start deleting and reboot on my own.
Delete completed.
Finished.
It's easy to use.
Netflix is also on PlayStore.
It'll be updated normally.
root
If you maintain the route,
I change my font or record on the phone.
When you do the whole gesture, remove the bottom white stick.
That's one of the advantages.
You can choose Xperia.
The users can choose.
https://forum.xda-developers.com/t/...-mobile-withdrawal-area.4144701/post-83277123
In the old guide version,
My English skills that I'm not good at...
This person translated it.
Please keep in mind.
The EBS file (VoLTE file) is...
It's in Sony firmware.
In the country you're using,
All the mobile carrier files are in here.
You can use that.
It's in the policy man folder.
You must modify the XML file!
In the area that was withdrawn,
I don't have a mobile carrier band code.
Make sure to change it to a notepad.
If you change the XML file,
VoLTE, of course.
5G works normally, too.
My poor English skills...
Someone wise.
Please deliver it.
We wish.
Be happy always.
How can I get the efs file?
/system/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic
It's in the firmware or on the device
So you can either unlock BL & root to have VoLTE, VoWiFi, etc; or keep everything untouched to have Widewine DRM (Netflix HD etc), full camera filter support, etc?
There is just no middle ground, is there :-/
GOOD JOP
How about WiFi calling?
Hazzay88 said:
How about WiFi calling?
Click to expand...
Click to collapse
disabled by Sony
malikin said:
disabled by Sony
Click to expand...
Click to collapse
That's annoying that WiFi calling is disabled.
I hope Sony fix volte issues globally for the upcoming Xperia 1 IV. All other manufacturers such as Xiaomi don't have this issue even if it's a grey import. I don't see why Sony can't fix the problem
Hazzay88 said:
That's annoying that WiFi calling is disabled.
I hope Sony fix volte issues globally for the upcoming Xperia 1 IV. All other manufacturers such as Xiaomi don't have this issue even if it's a grey import. I don't see why Sony can't fix the problem
Click to expand...
Click to collapse
I think nothing will change.
Bofahad said:
I think nothing will change.
Click to expand...
Click to collapse
I will basically stop buying a Sony phone as simple as that.
Hazzay88 said:
I will basically stop buying a Sony phone as simple as that.
Click to expand...
Click to collapse
U can do like what i did (5G)
Bofahad said:
U can do like what i did (5G)
Click to expand...
Click to collapse
Battery consumption is higher with 5G.
What benefits do you get with 5G besides speed?
Hazzay88 said:
Battery consumption is higher with 5G.
What benefits do you get with 5G besides speed?
Click to expand...
Click to collapse
I am happy with 4G as it is more than enough for my general usage.
What I want Sony to basically fix is volte and WiFi calling as that is a deal breaker considering 3G network will be phased out.
If Sony don't fix volte issue then certain countries will not be able to buy the upcoming Xperia phones as it will no longer be able to make calls.
Hazzay88 said:
I am happy with 4G as it is more than enough for my general usage.
What I want Sony to basically fix is volte and WiFi calling as that is a deal breaker considering 3G network will be phased out.
If Sony don't fix volte issue then certain countries will not be able to buy the upcoming Xperia phones as it will no longer be able to make calls.
Click to expand...
Click to collapse
You can enable VoLTE by flashing SEA firmware without unlocking bootloader.
Bofahad said:
You can enable VoLTE by flashing SEA firmware without unlocking bootloader.
Click to expand...
Click to collapse
Yes I have volte working by flashing SEA firmware. Working in Australia on Vodafone only for the Xperia 1 II.
However I haven't heard anyone getting it to work on the current generation Xperia 1 III so that puts further Doubt on the upcoming Xperia 1 IV which would be enough to keep me away and look elsewhere instead. It's not possible to make calls it volte doesn't work and 3G network is shut down
Hazzay88 said:
Yes I have volte working by flashing SEA firmware. Working in Australia on Vodafone only for the Xperia 1 II.
However I haven't heard anyone getting it to work on the current generation Xperia 1 III so that puts further Doubt on the upcoming Xperia 1 IV which would be enough to keep me away and look elsewhere instead. It's not possible to make calls it volte doesn't work and 3G network is shut down
Click to expand...
Click to collapse
It's working with me.
Bofahad said:
It's working with me.
Click to expand...
Click to collapse
That's good to hear.
Which country and carrier are you with?
Also did you get it to work after flashing it with SEA firmware to get it to work

How To Guide Getting VoLTE and VoWiFi on unlisted carriers by flashing mbn file

I live in Canada and I have a BC72 (Asian version). I am struggling to get VoLTE and VoWiFi working. I know that mbn file is the key to getting IMS support and sony seems to block some carrier mbn files (only mbn in sales areas are available). So recently I have been working on flashing mbn files to my phone.
UPDATE:
Everything works fine now. Here's the guide:
FIRST THING FIRST: Data is priceless. Always backup before you modify your phone software.
Disclaimer: Not every carrier in the world support VoLTE or VoWiFi. Please ask your carrier first to get more info if you don't know if they provide support to VoLTE or VoWiFi.
Things you need:
1. PC with windows or bootcamp (virtual machines won't work)
2. An Xperia 1 III with magisk installed (see guide here)
3. A reliable USB-C cable
Software you need:
1. EfsTools (from github)
2. Platform tools (from Google)
3. Qualcomm USB diagnostic port driver
4. QPST (from qpsttool.com)
3. mbn files (extract from your phone)
1. Open command line in the platform tools folder, type
Code:
./adb.exe shell
and press enter, you should see a linux shell on your command line starting with $. Then Type
Code:
su
and a super user window should pop up on your phone screen, after you allowing the permission, the $ should change into #, then type
Code:
setprop persist.usb.eng 1
. If your phone asks "Allow access?", press deny; if it doesn't, go to notification centre, find USB options, and select "No data transfer".
2. Go to your device manage on windows, there should be three "Xperia 1 III"s listed. Choose one, right click, and select "Update driver". In the pop up window, select "Browse my computer" and then "Select one from the available drivers". Find Qualcomm USB diagnostic 9091 and select next. Do the same thing for the rest two. For more details, please check this post and there's a Youtube video demonstration.
3. Open QPST Configurator, check the list and find which COM port corresponds to "LAHAINA". Go to the device manager and disable the rest, ONLY KEEP THE PORT FOR LAHAINA. Quit any QPST tools after this.
4. Open command line in the EfsTools folder, type
Code:
./EfsTools.exe efsInfo
and press enter. No error should occur if you configured correctly, and the COM port in step 3 should be shown.
5. Type
Code:
./EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
and press enter. There is no expected output so that if there's no error message, you are good.
6. Select the mbn file from the mbn folder. Find the mbn file for your carrier. If you're using a secondary operator, please use the mbn file for the main operator (e.g. Koodo -> use Telus mbn). Copy the mcfg_sw.mbn to the root of the EfsTools folder, then type
Code:
./EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
and press enter.
7. After the command line done it's magic, reboot your phone. Type
Code:
*#*#4636#*#*
in the phone original dialler. Select Phone Information, press the dots at the upper-right corner and select IMS Status, you can check if the IMS status is registered.
Now, you can enjoy VoLTE, VoWiFi, and even 5G (depends on your carrier's support). If you don't see VoLTE or VoWiFi toggle in your phone settings, try install VoEnabler in magisk or run these in adb shell:
Code:
setprop persist.vendor.dbg.ims_volte_enable 1
setprop persist.vendor.dbg.volte_avail_ovr 1
setprop persist.vendor.dbg.vt_avail_ovr 1
setprop persist.vendor.dbg.wfc_avail_ovr 1
Sorry for the late posting. I've been finding mbn files for other carriers but it seems there's no specific carrier's mbn files available on Snapdragon 888 (or I haven't found one). I'll update if there's any progress.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IMS Status when Wifi is disconnected and connected.
Additional link: Buy me a coffee : )
Interested in the progress of this...if I can get WiFi Calling i would prefer that over LTE calling for when I go to my Sister's Ranch where there's no signal what so ever...
I'm very interested in this, I've been looking for a way to get TMO Wi-Fi calling working on this phone for a while now.
My phone just died today. I’m not sure if the mbn file caused that. I won’t post the guide until I figure it out :-(
Forbesii said:
My phone just died today. I’m not sure if the mbn file caused that. I won’t post the guide until I figure it out :-(
Click to expand...
Click to collapse
Damn fam, hope it works out...i just cross flashed to the US rom from SEA cause I'm on Metro PCS but my modem got ****ed.....so no calling and network is constantly disconnecting
I have the SEA version in the US on T-Mobile. I flashed Ponce's Pixel Experienc GSI and Sony's binaries (no idea if this was necessary) and I have VoLTE and VoWiFi.
thatguy222 said:
I have the SEA version in the US on T-Mobile. I flashed Ponce's Pixel Experienc GSI and Sony's binaries (no idea if this was necessary) and I have VoLTE and VoWiFi.
Click to expand...
Click to collapse
Hmmm I will flash the binaries and see what happens if nothing changes I'll have to get back to Sea
thatguy222 said:
I have the SEA version in the US on T-Mobile. I flashed Ponce's Pixel Experienc GSI and Sony's binaries (no idea if this was necessary) and I have VoLTE and VoWiFi.
Click to expand...
Click to collapse
how did you flash the Binaries?
Delete
Ainz_Ooal_Gown said:
how did you flash the Binaries?
Click to expand...
Click to collapse
fastboot flash oem filename.img
Ainz_Ooal_Gown said:
Hmmm I will flash the binaries and see what happens if nothing changes I'll have to get back to Sea
Click to expand...
Click to collapse
Where might one get these binaries from?
@Forbesii Thanks for starting this thread. I am struggling with the same for my Xperia 5 III. Really Really looking forward to your Complete step-by-step guide and see how I can do this for my xperia as well. Thanks in advance.
Ndlelex said:
Where might one get these binaries from?
Click to expand...
Click to collapse
Sony's website
The guide is done guys. I'm still looking for methods to get mbn files not in the sony firmware.
Thanks for the update on the guide. I believe step 5 is missing a part. The mcfg_autoselect_by_uim file is not in the EFSTools download on Github.
misquia said:
Thanks for the update on the guide. I believe step 5 is missing a part. The mcfg_autoselect_by_uim file is not in the EFSTools download on Github.
Click to expand...
Click to collapse
Yes. I am stuck on the same step. It is returning the below error:
Critical error. Could not find file 'E:\Sony Xperia 5 III\EfsTools-0.14\mcfg_autoselect_by_uim'.
@Forbesii Could you please help/guide on this?
Ignored this step and it still works. The VoLTE and VoWifi both are working now (for Reliance Jio network in India). AMAZING article!
Definitely save it for future.
@Forbesii - On a side note: I am trying to add Airtel mbn (India carrier) file to my Xperia 5 III but it simply doesn't work. Neither VoLTE nor VoWifi. Are there any secondary steps/different command to copy this for SIM 2?
misquia said:
Thanks for the update on the guide. I believe step 5 is missing a part. The mcfg_autoselect_by_uim file is not in the EFSTools download on Github.
Click to expand...
Click to collapse
Thanks for your report, I‘ll update.
anmolkakkar said:
Ignored this step and it still works. The VoLTE and VoWifi both are working now (for Reliance Jio network in India). AMAZING article!
Definitely save it for future.
@Forbesii - On a side note: I am trying to add Airtel mbn (India carrier) file to my Xperia 5 III but it simply doesn't work. Neither VoLTE nor VoWifi. Are there any secondary steps/different command to copy this for SIM 2?
Click to expand...
Click to collapse
I haven’t tested on SIM 2. The second sim at least on Xperia 1 III is not correctly recognized by EFSTools. I might check other methods for the second SIM slot.
Thanks. Will wait to hear back from you.

How To Guide TCL 20 5G Unlock and Root

Warning:
This isn't my method and I haven't tested it myself, Im just posting it in case it helps someone.
Procedure was taken from this article, so beware of auto-translation to english.
Even if it uses the MTKroot application and this phone is Qualcomm, it looks legit as it installs the Qualcomm drivers during the process.
All credits go to the original author (thanks a lot!), just pasting this here in case the site goes offline in the future.
I don't take any responsability and I won't be supporting any bricked phones.
Test it under your own risk!
How to Root on TCL 20 5G Phone​
In the tutorial below you can find an automatic process to root the TCL 20 5G smartphones, through which you will get access to the root in a few minutes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Problems finding the boot.img file?, check
this.
What is it to do root?
Superuser or root is the usual name assigned to user accounts that have all rights in all forms of access, both monousual and multi-user.
Rooting a device is a method that makes it easier for the user of a computer with Android to gain privileged access to the system in a similar way to administrative permissions in Linux or Unix systems, allowing to cross any system barriers as well as software that could be established by the manufacturer or network operator.
Benefits of rooting for your TCL 20 5G
Remove all types of Bloatware simply and delete potentially useless system applications.
Being able to get extra storage space.
Customize system in-depth adjustments, such as releasing TCL 20 5G, repairing the IMEI of our TCL 20 5G and MAC steering, overclock among many possibilities.
Use programs designed only for those cell phones that have superuser permits.
Adapting or creating new partitions in memory (Watch out, doing this can be extremely dangerous to device integrity).
Create bakups or backups of the partition system or export the rom.
Precautions and warnings that we must always keep in mind
The mobile device shall cease the coverage of the guarantee granted by the manufacturer.
Risk that harmful applications can get permission from Superuser.
Threat of damage or deterioration of data during the procedure, therefore I recommend you in any case to back up before starting the root.
The Firmware of your TCL 20 5G may be harmed, it is recommended to be sure to be able to obtain a valid copy of the firmware if necessary.
Support for OTA upgrades will end up cancelled.
Conditions of the procedure
PC with Windows XP system or subsequent, architectures 32/64bits.
USB to Micro USB data cable.
Download to your computer the latest version of MTKroot v2.5.5 tool for your TCL 20 5G.
Download the original firmware for your terminal from where you will have to extract the boot component if possible from the manufacturer's online technical service.
If you fail to find an original TCL 20 5G firmware as an alternative you can also dispose of the boot component directly from your phone easily by taking the steps of this tutorial.
Settings to be made on the TCL 20 5G phone
The first thing we will have to do, obviously, will be to configure the necessary adjustments for the process, which basically consist of activating USB debugging and unlocking OEM.
These configurations are included in the development menu, which you must have unlocked in advance by pressing 7 times continuously on top of;
Configuration-"Downer information - version of the software or compilation number.
How to root the mobile phone TCL 20 5G easily​
First of all you must unzip the contents of the package previously downloaded to the Windows computer desktop and then run MTKroot v2.5.5.
Run MTKroot v2.5.5 for TCL 20 5G
Click Drivers - Qualcomm and complete the installation of the respective drivers.
Install Qualcomm drivers for TCL 20 5G
Take these exact same steps to implement the installation of ADB drivers.
Note: The MTKroot v2.5.5 tool incorporates all the updated drivers that are required by TCL 20 5G.
Then connect your team TCL 20 5G to the computer using a USB data cable and click on USB restart.
Click on the top left in No boot. - Load, add the boot.img file and then click Process patch.
Automatically the Magisk Manager application will be started on your TCL 20 5G, make the indications that will be on your screen to patch the boot.
Then you have to click on ADB Test and when you can read the message - Recognized Device you must press the Go to Fastboot button.
TCL 20 5G Restart USB . Test ADB . Fastboot
Wait for the meantime the TCL 20 5G restart with bootloader mode, then click the Test Fastboot button.
Again wait until the message comes out - Device found to be able to proceed to the next step.
​Release the bootloader from TCL 20 5G cell phones​In the next step you must unlock the bootloader to your TCL 20 5G, which you will do in a completely automated way.
Although remember that you must omit that operation if you had done it before.
Click on Test Bootloader to ensure your status is assured.
Check to bootloader TCL 20 5G
If you want to open the bootloader to TCL 20 5G simply click Unlock Bootloader -. Accept and then complete the suggestions that will be on the 20 5G TCL screen.
Remember to press the button upload the volume to unlock.
Unlock bootloader on TCL 20 5G
Note: When you release the bootloader, your smartphone will be resected to the default state.
Consider it appropriate to create a backup or simply copy all the files, contacts, photos and other data within an external memory.
After releasing the bootloader the next step will be to complete the process and finally leave your phone with the corresponding root privileges.
Head to the top of the left of the software and choose the rooting option, then click the Root button at the bottom.
Select Root TCL 20 5G
In less than 5 seconds the device will be rooted, so the word "OK" projected in the terminal and in the MTKroot v2.5.5.
Later click the Exit button to return your TCL 20 5G cell phone will restart the Android system.
Once the TCL 20 5G restarts completely, click Apps - Install Magisk and make sure you if the Magisk Manager app is effectively on your phone desk.
In order for the Magisk Manager application to be able to function properly, you must first connect TCL 20 5G to the Internet, either by wi-fi or mobile data.
To finish the tutorial you just click on Check Root - then accept and nothing else.
Test Root TCL 20 5G
Note: In case the Magisk Manager App fails to install at the first, click the Uninstall button, wait two seconds and again do once you click on the Magisk Instant button.
Summary Steps
Summary of the Rootear TCL 20 5G steps
Start MTKroot v2.5.5 utility and connect your TCL 20 5G to your PC.
Restart your TCL 20 5G in fastboot mode by clicking on the Go to Fastboot button - Test Fastboot.
If necessary, unlock the bootloader by clicking Liberate Bootloader.
Finally select the root wing option and press the Root button.
I thought MTKRoot only worked on mediatek chipsets. These phones have Qualcomm cpus and gpus.
We dont have file boot.img to do it
Comment edited since information in it was not useful to the thread
The situation looks like this: someone is messaging me about tcl-t810s, which is the model of my phone, and they need rom tcl-t810s, but they are giving me tcl-t767h rom instead. Could you please clarify what you meant by that? Perhaps, you could provide more information about what you are trying to achieve and why you are suggesting the rom for a different phone model. This could help us determine if the tcl-t767h rom is compatible with my tcl-t810s model and if it could solve the problem you are looking for.
DoctorBooty said:
^
Click to expand...
Click to collapse
Profesornauk said:
The situation looks like this: someone is messaging me about tcl-t810s, which is the model of my phone, and they need rom tcl-t810s, but they are giving me tcl-t767h rom instead. Could you please clarify what you meant by that? Perhaps, you could provide more information about what you are trying to achieve and why you are suggesting the rom for a different phone model. This could help us determine if the tcl-t767h rom is compatible with my tcl-t810s model and if it could solve the problem you are looking for.
Click to expand...
Click to collapse
I see, I wasn't aware that they were different models. I apologize. I'll delete my previous comment
DoctorBooty said:
I see, I wasn't aware that they were different models. I apologize. I'll delete my previous comment
Click to expand...
Click to collapse
Do you have contact with Gabby or did he tell you how to access the boot.img on TCL? That would be some clue
Profesornauk said:
Do you have contact with Gabby or did he tell you how to access the boot.img on TCL? That would be some clue
Click to expand...
Click to collapse
The files were in a paid site. Gaby happened to have a subscription in that site and she shared it after I requested it. I can't remember the site's name but it only had those files regarding TCL models
link to the latest version of MTKroot v2.5.5 tool is no longer valid, need an updated link if possible
update: found this link, seems to be legit MTKroot v2.7b (2022): https://drive.google.com/u/0/uc?id=1wnXGGca-uznK1bgG4WLSREnZ_nQXuEsY&export=download
Androiderz said:
link to the latest version of MTKroot v2.5.5 tool is no longer valid, need an updated link if possible
update: found this link, seems to be legit MTKroot v2.7b (2022): https://drive.google.com/u/0/uc?id=1wnXGGca-uznK1bgG4WLSREnZ_nQXuEsY&export=download
Click to expand...
Click to collapse
broken links

Categories

Resources