Related
MTK ADB gets you a privileged shell at the push of a button, allowing you to run commands directly on your MediaTek device. Some might wonder if rooting hasn't already solved this. Firstly, root access is persisted by modifying system files. When the real binary gets substituted by that of the root app's, if the device is rebooted, the init daemon running as root runs the binary giving the app root. What's wrong with this? If you have “purist” tendencies, you probably would want your phone as stock as possible, or at least with your permission. Sadly, not only binaries are dumped. Extra temp files, logs and helper binaries too, that manually removing them is like dancing on floor of pins and a prick means a brick. Not only that, consider yourself blocked from updates. If you're unfortunate enough, an update could result in bricking your phone as the files supposed to be present had been changed. This is more common than you think. MTK ADB makes no changes to your files whatsoever. Also, there's the matter of security/privacy. Root apps tend to always do something in the background. Either sneaking in a new app, or phoning home with your private data, or both. MTK ADB doesn't steal your data. The Internet permission is for Telnet, etc. On some devices, MTK ADB can get root access (depending on manufacturer) while all devices can get shell access. You just have to check which yours belongs.
IMPORTANT
•Refresh before (and after) clicking Start to check ADB status.
•Supports all ADB functionality. Just run "adb <command>" eg "adb pull" (without quotes).
•The minimalist terminal is for those who haven't any. Feel free to use your regular terminal (I use Terminal IDE) and keyboard (Hacker's Keyboard is really good). Just run "adb shell" on it.
•You can connect to your device using another phone, PC, or anything with a terminal and in the same network by running "adb connect IP_address".
•If you get a " device offline" error, disable and enable USB debugging. Next time connect to the network before running the app.
http://www.youtube.com/watch?v=_bt8BVaDCf0
http://slaycode.WordPress.com
Bump
Proof:
http://forum.xda-developers.com/gen...iled-error-t3191150/post62611445#post62611445
More Proof:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546/page10
Proof:
http://forum.xda-developers.com/gen...iled-error-t3191150/post62611445#post62611445
More Proof:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546/page10
When I open the app it opens but it doesn't work when I enter the commands and moreover the app when I try to start the adb it says unsupported device
Am using infinix hot 4 pro running NOUGAT xos 2.2
LordFME said:
MTK ADB gets you a privileged shell at the push of a button, allowing you to run commands directly on your MediaTek device. Some might wonder if rooting hasn't already solved this. Firstly, root access is persisted by modifying system files. When the real binary gets substituted by that of the root app's, if the device is rebooted, the init daemon running as root runs the binary giving the app root. What's wrong with this? If you have “purist” tendencies, you probably would want your phone as stock as possible, or at least with your permission. Sadly, not only binaries are dumped. Extra temp files, logs and helper binaries too, that manually removing them is like dancing on floor of pins and a prick means a brick. Not only that, consider yourself blocked from updates. If you're unfortunate enough, an update could result in bricking your phone as the files supposed to be present had been changed. This is more common than you think. MTK ADB makes no changes to your files whatsoever. Also, there's the matter of security/privacy. Root apps tend to always do something in the background. Either sneaking in a new app, or phoning home with your private data, or both. MTK ADB doesn't steal your data. The Internet permission is for Telnet, etc. On some devices, MTK ADB can get root access (depending on manufacturer) while all devices can get shell access. You just have to check which yours belongs.
IMPORTANT
•Refresh before (and after) clicking Start to check ADB status.
•Supports all ADB functionality. Just run "adb <command>" eg "adb pull" (without quotes).
•The minimalist terminal is for those who haven't any. Feel free to use your regular terminal (I use Terminal IDE) and keyboard (Hacker's Keyboard is really good). Just run "adb shell" on it.
•You can connect to your device using another phone, PC, or anything with a terminal and in the same network by running "adb connect IP_address".
•If you get a " device offline" error, disable and enable USB debugging. Next time connect to the network before running the app.
http://slaycode.WordPress.com
Click to expand...
Click to collapse
Are you familiar with an APK that utilizes mtk_bypass to directly flash firmware to device.
I'm looking for an APK that basically does what sp flash tool does because I don't have a computer.
Hi, I want to extract qcn file of my pixel 3 and followed other steps. After stressful searches, I was almost done with the following links
1) https://forum.xda-developers.com/pixel-2-xl/how-to/guide-qxdm-port-activation-pixel-2-xl-t3884967
2) https://forum.xda-developers.com/pixel-3/help/qxdm-pixel-3-limited-success-help-t3887152
steps I followed
1) bootloader unlock
2) factory image (android 9) from official google
3) Twrp recovery
4) Magisk from link 1
5) Module (Pixel 2 diag port.zip) from link 1
6) Mi5 Qualcomm drivers from link 2
and with that, I got diag port somehow opened but it only gets on MTP connection via USB but no proper detection in QPST. I tried to backup qcn file with partial detection of COM port but it says "checking connection" and then "backup failed no phone attached".
Is there any way for this? I'm really stuck with my mobile network problem. :crying:
P.S: just to make it clear, my question is not for VoLTE or PDC.
Update:-
I managed to get detected properly via Modem port but not in QFIL.
1) Magisk and Module from link 1
2) "QUD.WIN.1.1 Installer-10037.3 Setup" Qualcomm Drivers
3) Put phone in MTP connection
4) Following commands in adb
Code:
adb shell
su
setenforce 0
setprop sys.usb.configfs 1 && setprop sys.usb.config diag,serial_cdev,rmnet_gsi,adb
5) open "QPST Configuration"
6) Add port
7) Add Modem port
With these steps, i get manage to get detected in QPST Download and able to make a backup of "*.xqcn". But after editing and restoring, there is no such change. Am i missing something?
any usfull info here? https://gist.github.com/julian-alarcon/53f9a782008b5d5f879bf6fa878f87f3
Hello sir i lost my physical sim card on pixel 3a only shows esim option please help
luqman.mirza said:
Hi, I want to extract qcn file of my pixel 3 and followed other steps. After stressful searches, I was almost done with the following links
1) https://forum.xda-developers.com/pixel-2-xl/how-to/guide-qxdm-port-activation-pixel-2-xl-t3884967
2) https://forum.xda-developers.com/pixel-3/help/qxdm-pixel-3-limited-success-help-t3887152
steps I followed
1) bootloader unlock
2) factory image (android 9) from official google
3) Twrp recovery
4) Magisk from link 1
5) Module (Pixel 2 diag port.zip) from link 1
6) Mi5 Qualcomm drivers from link 2
and with that, I got diag port somehow opened but it only gets on MTP connection via USB but no proper detection in QPST. I tried to backup qcn file with partial detection of COM port but it says "checking connection" and then "backup failed no phone attached".
Is there any way for this? I'm really stuck with my mobile network problem. :crying:
P.S: just to make it clear, my question is not for VoLTE or PDC.
Update:-
I managed to get detected properly via Modem port but not in QFIL.
1) Magisk and Module from link 1
2) "QUD.WIN.1.1 Installer-10037.3 Setup" Qualcomm Drivers
3) Put phone in MTP connection
4) Following commands in adb
Code:
adb shell
su
setenforce 0
setprop sys.usb.configfs 1 && setprop sys.usb.config diag,serial_cdev,rmnet_gsi,adb
5) open "QPST Configuration"
6) Add port
7) Add Modem port
With these steps, i get manage to get detected in QPST Download and able to make a backup of "*.xqcn". But after editing and restoring, there is no such change. Am i missing something?
Click to expand...
Click to collapse
Can you share the XQCN file with me??
I was able to use QPST and PDC on my OnePlus Nord (AC2003) when it was running Android 10 / Oxygen 10.5
After this weekends update to Android 11 / Oxygen 11 my phone is no longer recognised. I've tried all sorts of USB drivers I could find using some Google Fu, but none of them recognises it anymore.
Does anyone have USB drivers for the OnePlus Nord (AC2003) that works with Android 11?
Thank you
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Jaansburger said:
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Click to expand...
Click to collapse
Thank you for this. Managed to get mine working with VoLTE and VoWIFI.
I have added all the drivers needed and some instructions here : https://gitlab.com/sorinfatu/opnord-volte-vowifi
If anyone wants to contribute to the profiles list feel free.
Thank you again Jaansburger
Jaansburger said:
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Click to expand...
Click to collapse
No need to root?
Thanks
ippo18 said:
No need to root?
Thanks
Click to expand...
Click to collapse
Nope, no need
Jaansburger said:
Nope, no need
Click to expand...
Click to collapse
Thanks, I got blocked at the PDC step: no options available in the devices list.
Do I need a special version of PDC?
Tks
Thanks, it worked in the end, good job!
sorfat said:
Thank you for this. Managed to get mine working with VoLTE and VoWIFI.
I have added all the drivers needed and some instructions here : https://gitlab.com/sorinfatu/opnord-volte-vowifi
If anyone wants to contribute to the profiles list feel free.
Thank you again Jaansburger
Click to expand...
Click to collapse
I have no gitlab account, you may add, on the profiles Markdown file:
WindTre Italy ---> Italy-Volte-Vodafone profile works properely!
ippo18 said:
I have no gitlab account, you may add, on the profiles Markdown file:
WindTre Italy ---> Italy-Volte-Vodafone profile works properely!
Click to expand...
Click to collapse
Done
Hi,
A friend of mine want's to recover some pictures from an old phone of his, but he forgot the pattern to unlock the device...
* The phone is a CAT S41 stock android.
* The phone is in perfect conditions
* The USB debug option of the phone is disabled.
- Because of that, I've been unable to execute any adb commands on the device.
- When the phone is in Recovery Mode, the device is detected by adb, but unauthorized:
[email protected]:~$ adb devices
List of devices attached
S411931008366 unauthorized
[email protected]:~$ adb shell
adb: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Click to expand...
Click to collapse
I've tried to set the $ADB_VENDOR_KEYS manually, with no success.
In this situation, I have some questions to ask:
1. Is there a known way of bypassing the pattern lock?
2. Is there a known way of dumping data to any other device, in order to retrieve the pictures
3. Can the debug options be activated somehow?
As a last resource, I'd be willing to open the phone and spend some bucks on whatever hardware is needed to dump the whole disk, if that is relatively feasible to do.
4. Could you give me any feedback/information on hardware methods of dumping the disk of the phone? 0 experience there.
I would greatly appreciate any input you could give me.
If more details of the system or the situation are needed, please ask.
Thank you kindly for your attention,
abocador
Can't offer a solution.
But, even if there is a way to dump the files - what requires phone's Android is got rooted and USB-Debugging is activated , IMO it makes no sense to waste more time in this because since Android 4 data are AES-128 encrypted ( FBE and/or FDE method ) and the encryption probably can't get cracked.
2. + 4. won't work because of encryption, but 1. + 3. is possible on that old android 7 mediatek device.
assuming device runs on FDE full-disk encryption, is encrypted with default_password, one can hack boot.img and authorize usb-debugging. because device decrypts itself on boot that's all you need to get access.
but first install VCOM preloader drivers and make a readback of device with WwrMTK v2.51 + SP Flash Tool (old method) or mtkclient (new method).
I will tell you how to patch and resign boot.img once you made the important backup step. most important partitions are userdata+metadata.
Btw there is maybe another (even more easier) method. Just port TWRP recovery for that device. Because of weak security implementation phone will boot into custom recovery on locked bootloader (I did on Cubot King Kong)
Hi,
Thank you a lot for your reply.
I've been trying to do the backup, but I wasn't able to even use the mtkclient
I think I will just forget about this.
you know device must powered off completely, and preloader only says 'Hello' to computer for ~ 1 second? Did you install VCOM preloader drivers during that second (device manager -> pick device -> Update Driver -> Browse my computer for driver software -> Let me pick from the list of device drivers on my computer -> Show all devices -> Have Disk) ?
Hello again!
Yes, I'm aware the device must be powered off.
I'm quite sure I have all the drivers I need. I'm working from a Debian system.
Some weeks ago, I posted the log I get when I try to connect mtkclient to the phone:
Error on sending data: DA hash mismatch · Issue #575 · bkerler/mtkclient
Hi! I'm trying to use this tool on a CAT S41 phone, but I'm unable to get any proper connection between the device and my computer. After initializing the GUI with_python mtk_gui_, I get the follow...
github.com
One more time, thanks for your help,
I think I'm going to park this project for a while.
Cheers,
abocador
okay, for linux no need for drivers looks good, have you tried some random cmd line usage just for fun?
Code:
python3 mtk printgpt
python3 mtk rl out
python3 mtk crash
python3 mtk --preloader printgpt
python3 mtk --preloader rl out
First of all, Thanks to @johndaniel, @htcmage, @gorEisberg @Forbesii @morphvale @arjun_m4 for sharing all the information and files required for this 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 and 5G. Tested on a Xperia 5 III (XQ-BQ72).
Prerequisites:
* Xperia 1 III or Xperia 5 III (This guide works on Android 12 and 13)
* Windows Computer
* Firmware for your device
* USB Cable
Downloading Firmware
Download XperiFirm from https://xperifirm.com/download/xperifirm-v4-6-0/ and Install
Open the XperiFirm and Download the firmware for your device ( check your model number and download the firmware)
Preparing the Device for Rooting
* Back up all the data from your device.
Make sure the device is supported for Bootloader unlock by opening the dialer and enter the code *#*#7378423#*#* and then press Service Info -> Configuration.
If the Bootloader unlock status is Yes, then you’re lucky and continue the rest of the guide.
Visit https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/ and Select your device and enter IMEI and get the code.
Enable Developer Options and then Enable OEM Unlocking and USB debugging on your device.
Download Platform tools for Windows using this link
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Open CMD and go to the Platform-tools directory and enter the below command:
adb reboot bootloader
Once it’s in bootloader mode or fastboot mode you will see blue light then type this command on CMD:
fastboot oem unlock 0xYOURKEY
Wait for the reply on cmd and then type
fastboot reboot
Now your device is Unlocked.
After reboot, configure your phone without entering Google Account's, we don't need this now, just connect your phone with a Wifi Network
Rooting
Download and Install Magisk in your phone from here
In your computer, open the firmware folder you have downloaded and look for boot.sin file it looks something like boot_X-FLASH-ALL-4BA8.sin with around 96MB size (might look different for other versions and regions)
Download UnSin Exe from https://forum.xda-developers.com/t/tool-unsin-sin-v3-v4-v5-unpacker-v1-13.3128106/ and then drag and drop the boot.sin this will give you boot.img
Rename the boot_X-FLASH-ALL-4BA8.img into boot.img (easier to flash) and then using Magisk Manager to patch it.
Just don’t delete the original boot.img we need that for the re-locking bootloader.
Now copy the magisk_patched.img into the Platform-tools folder and rename it into boot_magisk.img
Open CMD and go to the Platform-tools directory and enter the below command:
adb reboot bootloader
Once in fastboot mode type this command
fastboot flash boot boot_magisk.img
Wait for it and then type
fastboot reboot
After restarting your phone, open magisk and verify it's rooted.
How to extract your MBN files from your device's firmware
After rooting your phone, you can use a file explorer (in my case I use Solid Explorer, you can download it from here if you want).
Select the folder root inside the app and then look for your .mbn files searching in this path:
Code:
root/vendor/firmware_mnt/modem_pr/mcfg/configs/mcfg_sw/generic/(area)/(operator)/Commercial/mcfg_sw.mbn
Copy your mbn file to a normal folder in your phone, like "downloads" and then copy that file again to your computer.
Enabling 5G and Volte
Open CMD and go to the Platform-tools directory and enter the below command:
adb shell
su
setprop persist.usb.eng 1
Allow the access in Magisk after entering the su command.
If the phone, asks for Allow access press Deny.
Download QPST from https://qpsttool.com/ and install, also, you can find the Qualcomm Drivers inside the zip, install them.
After that, it should show up 3 Xperia on the device manager and install one by one manually using Qualcomm driver just youtube this part. Use Qualcomm USB diagnostic 9091 or 9081.
REMEMBER: To configure modem files in Efs explorer or flash the MBN file it is required to enter the following commands in adb:
adb devices (to start the usb debugging, allow your computer if is neccesary)
adb shell
su
setprop persist.usb.eng 1
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.
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.
I attached some mbn files on this post, check if some of them are compatible with your carrier.
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. Telcel -> use ATT mbn). Copy the mcfg_sw.mbn to the root of the EfsTools folder, open a terminal inside this folder (shift + right click = open a new Powershell Window) then type.
Code:
./EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
and press enter.
The program will overwrite your modem information updating it to the mbn file you flashed.
Open EFS Explorer and select LAHAINA if the name is there otherwise try one by one until you see a bunch of folders.
Once all the folders are showing up go to Policyman folder and copy carrier_policy.xml attached in this post and paste it there.
Restart the device.
You should now have the Speed of 5G or 4G+ and Volte enabled.
Don’t stop here.
Time to go back to Stock (Unroot)
Open CMD and go to the Platform-tools directory and enter the below command:
adb reboot bootloader
Remember the original boot.img we have before patching copy that file into platform tools and replace it with the patched boot_magisk.img
Then type this command:
fastboot flash boot boot.img
Once that’s done then type this command:
fastboot oem lock
Wait for the response and then type this command:
fastboot reboot
Once that’s done your device should format and bootloader locked and back to stock ROM with 5G and Volte enabled.
Enabling VOLTE Options after re-lock bootloader and unroot.
Go to Playstore and install Shizuku app.
With the app opened, open up a terminal and write
Code:
Code:
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
to start it
Check the app. It should say Shizuku is running.
Download and install this apk
In your app drawer find Pixel IMS app, open it and click on allow all the time for "Allow Pixel IMS to access Shizuku"
Hit the enable VoLTE button at the lower left.
Go to settings, mobile data settings and you will find the enable Volte Option or 4G Call.
Also, it kept working after uninstalling Pixel IMS and Shizuku apps.
You can restart the device and the Volte/5G will remain active.
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).
How to Update your phone keeping your flashed mbn and carrier policy files.
Thanks to @bentree for the great idea, I just updated my phone with the firmware released today using newflasher and removing the modem files from the folder.
DON'T UPDATE USING OTA, download your most recent firmware with XperiFirm.
Download Newflasher (I'll attach the file on this post)
Extract the Newflasher files from the .rar file and copy them to the firmware's folder.
Remove the modem files from the folder, personally I removed these ones:
modem_X-FLASH-ALL-XXXX.sin
modemst1_X-FLASH-ALL-XXXX.sin
modemst2_X-FLASH-ALL-XXXX.sin
Open the NewFlasher.exe file and follow the steps in the command prompt.
Flash keeping your data.
After rebooting, your phone will boot as normal, but your will notice the Volte and VoWifi options are missed.
Repeat this step (Enabling VOLTE Options after re-lock bootloader and unroot).
Enjoy!
Amazing detailed guide. Thanks for sharing.
Quick question, can all of this be done on Android 13 now? And does it support 45/5G VoLTE/VoWifi on both SIMs?
I haven't upgraded for almost a year now coz everything was working fine on A12 with 4G VoLTE and VoWifi.
anmolkakkar said:
Amazing detailed guide. Thanks for sharing.
Quick question, can all of this be done on Android 13 now? And does it support 45/5G VoLTE/VoWifi on both SIMs?
I haven't upgraded for almost a year now coz everything was working fine on A12 with 4G VoLTE and VoWifi.
Click to expand...
Click to collapse
Of course I forgot to tell you that I achieve this on Android 13, last security patch. Firmware version 61.2.A.0.388.
My carrier doesn't support VoWifi, but remember the last step only provides to enable Volte option and no VoWifi, so you probably won't get VoWifi anyways.
My carrier (Jio (India)) supports both but just wanted to know if this on A13 now. Good to know.
Will risk upgrading tonight and see if I get successful. I will update here based on how it goes.
Yeme said:
You can't restart the device and the Volte/5G will remain active.
Click to expand...
Click to collapse
You can or can't restart the device? Will the settings stay after restarts?
anmolkakkar said:
You can or can't restart the device? Will the settings stay after restarts?
Click to expand...
Click to collapse
Yes, the settings stay after restarting, sorry the post was corrected.
Does unlocking bootloader loses drm keys ? If yes the how to backup drm keys and after relocking bootloader will drm keys restored ? And also will jio and Airtel 4g volte, 5g both work after this method? I have Sony xperia 5 iii xqbq 62 us variant. Looking forward to follow your method. Is this is same procedure for xq bq62 and xqbq72.
anmolkakkar said:
My carrier (Jio (India)) supports both but just wanted to know if this on A13 now. Good to know.
Will risk upgrading tonight and see if I get successful. I will update here based on how it goes.
Click to expand...
Click to collapse
Were you able to upgrade, Anmol? How did it go? (fingers crossed)
Updated to A13. Did all the process (i have my own process similar to this in a notepad). Airtel mbn files just DON'T work. Vowifi shows up but no calls can be placed coz the phone doesn't even show VoLTE on top if Wifi is off (even though IMS service status shows available). Some issue with the bands maybe. Mobile data works fine on 4G/5G for Airtel.
Jio works fine though all through.
Historically, Airtel didnt work for me in A12 too.
anmolkakkar said:
Updated to A13. Did all the process (i have my own process similar to this in a notepad). Airtel mbn files just DON'T work. Vowifi shows up but no calls can be placed coz the phone doesn't even show VoLTE on top if Wifi is off (even though IMS service status shows available). Some issue with the bands maybe. Mobile data works fine on 4G/5G for Airtel.
Jio works fine though all through.
Historically, Airtel didnt work for me in A12 too.
Click to expand...
Click to collapse
Thanks for the update, Anmol!
xperiafirm kam nhi krra
{
"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 this might be an extremely stupid question, but once I restart my phone into bootloader via adb, the device is no longer in the list. adb devices will not display anything, reconnect doesn't care and fastboot obviously doesn't do anything either. Unplugging will shut down the phone normally and allow me to restart without changes.
I'm suspecting a driver problem, did anyone here have that same issue and knows how to quickly fix it?
Google USB Drivers are installed via Android studio (v13) and Xperia 5 III drivers are installed manually (by installing sa0200adb.inf).
Retenor said:
So this might be an extremely stupid question, but once I restart my phone into bootloader via adb, the device is no longer in the list. adb devices will not display anything, reconnect doesn't care and fastboot obviously doesn't do anything either. Unplugging will shut down the phone normally and allow me to restart without changes.
I'm suspecting a driver problem, did anyone here have that same issue and knows how to quickly fix it?
Google USB Drivers are installed via Android studio (v13) and Xperia 5 III drivers are installed manually (by installing sa0200adb.inf).
Click to expand...
Click to collapse
Check this video bro
I had the same issue, tell me if you could fix it.
Can you post a tutorial video?
For me and beginner
Yeme said:
Check this video bro
I had the same issue, tell me if you could fix it.
Click to expand...
Click to collapse
Wow, thanks for the quick reply, and yes, this worked flawlessly, thanks!
Is there also a list somewhere about which Magisk installation settings one has to check or leave unchecked for patching the boot.img?
Mmm I don't remember checking settings while patching the file. Leave everything as it is.
Retenor said:
Wow, thanks for the quick reply, and yes, this worked flawlessly, thanks!
Is there also a list somewhere about which Magisk installation settings one has to check or leave unchecked for patching the boot.img?
Click to expand...
Click to collapse
Yeme said:
Mmm I don't remember checking settings while patching the file. Leave everything as it is.
Click to expand...
Click to collapse
Turns out that is not even needed and just me reading too many guides and confusing things.
Anyways, I am rooted now, which was the plan from the start! VoLTE and VoWIFI was enabled for my provider from the getgo so I am done with low-level tinkering for now. Thanks for the assistance!
shoaib130088 said:
Can you post a tutorial video?
For me and beginner
Click to expand...
Click to collapse
Since I am now at the point where I did everything I can't record it anymore, but the guide is actually very straight-forward and specific about things. I suggest just following step-by-step and asking here if something is not clear.
If you run into the driver issue, you will have to do the same thing as done in the video above TWICE: once for when you unlock the bootloader and the second time when flashing the patched img.
Keep in mind the commands above only work (at least in powershell) without further ado when platform tools etc. is installed with PATH variable set (At least seems to be the issue for me, correct me if I'm wrong here). If you don't know what PATH is or don't want to set it, you can navigate to your platform-tools folder and then hold shift and right click to any blank area to bring up "open powershell here" in the context menu. This way you get an input shell right where you need it.
Then, don't enter "adb reboot bootloader" or similar, type in
Code:
.\adb.exe reboot
or whatever you want to input. This will call the exe from your current directory.
Same goes for flashing, typing
Code:
.\fastboot.exe flash boot .\boot_magisk.img
is equivalent to the one in the guide, provided you moved the boot_magisk.img file to the platform-tools folder.
I also encourage you to input
Code:
.\adb.exe devices
after each command step to make sure your device is still properly recognized. If it is not, you may need to go for the steps in the video.
So quick question. I know that the Samsung S21 5g uses same chipset. I need the mbn files from the samsung firmware but everytime I try to open the modem.bin file from the samsung firmware I get an unable to open as archive error. Every other Bin file I can open but not the modem file. Does anyone have a copy of the S21 5G modem files? Cheers, Bentree.
Any one help me to anydesk
Thanks @Yeme for support for successful xperia 1 iii volte wifi calling enable in India jio sim