Related
Hi guys!
I bought the Galaxy Note 4 (SM-N910T), and it did not come with Portuguese language ('m from Brazil).
I've tried to translate app's (morelocale2) already replaced the ROM for the newest, but it worked!
Is there any way to put the language?
Is there any custom ROM or not, that works for my model?
Thank you!
Additional language added for Note 4 SM-N9100G without root
Hi,
I face the same problem with a Note 4 SM-N9100G trying to install a additional local language without to root the phone and to affect the warranty. The solution found on Internet is given below:
1. On Windows PC download and install the latest Android SDK Manager (Google for it).
2. Unlock the "Developer Option" on your Note 4 device.
3. Install MoreLocale 2 from Google Play on your Note 4 device.
4. On your PC go on the <Platform - Tools> subfolder from SDK Manager folder and launch a command prompt window here (press simultaneously shift and right click then select from drop menu).
5. Connect the Note 4 to PC though the USB cable on USB debugging mode (accept the debugging action from your PC on the popping window from your phone).
6. To ensure that the devices are properly communicating type <adb devices> on the Command Prompt window from your PC and you shall see your device listed.
7. Launch the adb shell from same Command Prompt window with the command <adb shell> then enter
Note: the top of the command prompt window shall indicate "adb shell" mode upon command input.
8. Input the following command line exactly as is given in the Command Prompt window then press enter (take care on CAPS LOCK):
pm grant jp.co.c_lis.ccl.morelocale android.permission.CHANGE_CONFIGURATION
9. If you don't receive any error on the command prompt window then you manage to unlock the MoreLocale 2 application on your phone.
10. Go to your Note 4 launch MoreLocale 2 and select the language you want to load, set it as default then you are done.
Hope that this will help.
Hello to everyone, Im posting here because I cannot make a question to the post related to what I need (http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269), sa basically, I need to unlock the GSM 1900 band to use it in Chile (Entel company).
What do I need? Im still having some problems about understanding the adb terminal. Can someone help me with this please?
These are the steps to unlock the bands **My doubts are in red-bold and enumerate**
"Download this zip Google it as it's banned from xda for the ability of imei change
2. Extract it and install QPST from that zip
3. Open the caller app and type in *#*#8778#*#* (it should go off the screen after you type in the last symbol "*"
3.5 Those on custom roms (tested on cyanogen 11 with s4 mini) can use the efs professional toolkit to change the mode to enable the diag port.(Thanks @blackburn !)
4. Connect your phone to your PC ( 1)HERE, in which mode do I have to connect my phone to the computer?)
5. Open ADB console ( 2) From the folder of the adb program, right? pressing SHIFT + RIGHT CLICK?)
6. Type in these commands: ( 3) Can I type these commands from my phone? from the Terminal Emulator for example? Like in the step 34 of this guide???)
Code:
adb shell
su
setprop persist.usb.eng 1
Click to expand...
Click to collapse
7. Turn off USB Debugging, Disconnect your phone from the PC
8. Wait about 10 seconds (don't have to be exact, just let it all disconnect in the PC) and turn USB Debugging back on
10. Connect it back to the PC. It should try to install drivers. Wait until it fails to install all of them.
11. Open device manager - you will see your device model a few times. Go to details tab. Scroll down a single time on that tab. You will see MI_0x there.
12. Go through those devices until you find MI_04 under the second drop down position. ( 4)For what does this MI_04 stands for?)
13. Select "update driver" for this device and install the htc driver from the zip.
14. Press start button and navigate to QPST -> QPST Configuration
15. Go back to device manager -> modems -> HTC
16. Find "COM*" in my case it was "COM3". It might be different for you.
17. In QPST Configuration click on "Add new port" and in "Port" type in your "COM*". In my case It's "COM3" in there. In Port label it could be anyting u want. In my case I used a Z1 so I typed IN "Z1".
18. It should look like this now.
19. Navigate to QPST/bin and open RV_NV_Manager.exe
20. press on settings -> Comport and choose your COM port.
21. Press on file -> read from phone
22. Wait patiently until it is finished. Now pay attention!
23. Go to line 1877, click it and copy the decimal number on the right side of a programme. right click - copy
24. Go to the place where you extracted the zip from the first step and start mzTool
25. On the left side you will see "Input radix" - press decimal there. ( 5) For example, if the hole number is "153546.256", the decimal should be "256", right?
26. On the right side you will see "RF BC CONFIG" paste your previously copied number from the RV_NV_Manager.exe there.
27. You will see now what bands are you able to use on the bottom of the app in "Bit information"
28. Switch tab to "Band Preference (NV Value)"
29. In there select all GSM bands and WCDMA bands. This place is really a field of testing. In my case (C6903 LTE) I selected all of GSM and WCDMA. I wouldn't suggest you to do anyting else in here unless you know what your'e doing. Let me know if you got something interesting in there.
30. After you're done choosing what bands do you want - copy decimal number from the bottom right ( 6) Here I really need and example or a major explanation, in macro detail :c)
31. Remove all commas from that number ( "," ) so it would be just a bunch of numbers without anything else. ( 7) A bunch of number like this 524356??
32. Open RV_NV_Manager.exe from the point you left it (step 23) and paste your new number without commas "," there.
33. Press on write NV and then press on file ->write changed NV to the phone.
34. Open up the terminal emulator on your phone and write there this: ( 8) This is what I was refering to! Why it can be done directly from the phone? Can I do the step 6 from the Terminal Emulator of the phone too??)
Code:
su
setprop persist.usb.eng 0
Click to expand...
Click to collapse
35. Reboot the device and hope you'll have the reception. If you do, hooray!
36. Type in *#*#SERVICE#*#* (*#*#7378423#*#*) to see your new bands that your phone can use! "
Please help me! I have a basic, baaasic knowledge about this, and there are no videos for the Sprint m8 version :c
If Im posting in a wrong category, my apologies, but I cant comment in the real guide-post to get assitance :c
Thanks in advance.
- Conchetumare celular culiao :crying: -
.
Anyone? Just that simple? come on :c!!!!!!!!!!!!!
..
So many thanks ah...
Finally
I can confirm it worked on my Oneplus 7 Pro both Volte and Vowifi calling it also can work on oneplus 6, and 6T since I don't have a device so I can't test it.
some people are unable to activated so this method require additional step for them.
Install QPST: https://mega.nz/file/zQt3ESDA#dd69iA2r9xZaYwWvYrCvVHl-OmjucIWI4ETFBTO5bM8 (This tool only work on Oneplus 6,6t, 7 series. Oneplus has blocked this tool on oneplus 5 series)
Next steps:
find PDC tool from installed QPST and open
select device from drop-down menu, if it is empty, you will have to reinstall/choose another driver
now right-click on overseas commerical ds and select Deactivated - Sub0
now right-click on Commerical-TMO and select SetSelectedConfig - Sub0
and now button Activate
Restart your phone than apply following step:
Oneplus Usb driver (Dont install it if you already installed this before)
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI
After unzipping pixel3.zip you need to go to: Pixel3\mcfg_sw\generic\Pixel\NA\Freedom\VoLTE and copy mcfg_sw.mbn file to folder where you will have your EfsTools saved. It will ask you to overwrite one that is in that folder. Press yes.
Now follow these steps:
This method doesn't required root.
0. Make sure that you just enabled the VoWiFi and VoLTE in your carrier first !!!
1. Download and install the oneplus LogKit and Engineering mode apk:
3. Type *#800# --> oneplus Logkit --> Function Switch --> enable VoLTE and VoWifi switch
4. Open Settings --> WiFi & Intenet --> SIM & netwok --> enable VoLTE and VoWifi switch
5. Connect your phone to PC
6. Type *#801# in Phone app and enable Full-port switch (if your computer unable to recognize COM PORT try installing qualcomm driver: https://mega.nz/file/jV9ByarL#lbryKSC6uk9D-GTErtJ0SHyVOfWKA2TIl-psXmhj4YU)
7. Download and unzip the EfsTools with config files includes. (Make sure copy mcfg_sw.mbn file from pixel3.zip freedom folder replace the file if already exit.)
8. Open CMD as Administrator on the PC, navigate to the folder where you extract the files (eg. cd c:\EfsTools-0.10-modded-1.2-win32)
9. Now execute the following commands:
EfsTools.exe efsInfo
If your Freedom sim in Slot 1 use this command:
1. EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
2. EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
If your Freedom sim in Slot 2 use this command:
1. EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
2. EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
Thats it. Commands with "1" on at the end are for the second SIM card.
You must register here in order to wifi calling work: https://vowifi.authenticateme.ca/
Credit goes to @popos1 and @astracd. Original Post: https://forums.oneplus.com/threads/freedom-mobile-wifi-calling-working.1284987/
You need These file:
Pixel 3 mbn file:
https://forum.xda-developers.com/showpost.php?p=78563337&postcount=4 (Recommend for oneplus 6 series)
Pixel 4 mbn file:
https://forum.xda-developers.com/pixel-4/help/mbn-files-pixel-4-request-t4050247 (Recommend for Oneplus 7 series)
Thanks for @asasanc
Oneplus logkit:
https://mega.nz/file/rZlADYzD#Pg8vLZI4tZ16VXe-v-JfPLCiCab9fTTWwFcPBI04oho
Efstool:
https://mega.nz/file/fQcnQAZT#i0dRA6PvsuK4_PmLHPVXSwhOZroSsR6P1CuUDHwHW8g
Enigneering Mode apk:
https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/
Join Telegram group:
https://t.me/joinchat/QOPwqkqivRqnI4YIW2bojA
Edit:
Alot of people have confirm this method working on Oneplus 6,6t, 7,7 pro, 7t, and 8. For some people VoLTE works right away but for some it take few day to provision as per freedom it could take somewhere 72-120 HR to provision.
Edit 2:
Pixel 2 mbn for oneplus 5. This is recommended for Oneplus 5 only.
https://mega.nz/file/HUsHVYqS#n7pDP-mEMIY5MXffqViAVoqPgF_Au3hzzm6s5dgBZu0
Update: 3/25/2021
This new method requires Root on Android 11.Please note Engineering won't work on Android 11. you need to follow the following steps to open the ports.
you need Adb tool Platform-tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
1. Extract the Folder
2. Open the Platform Tool folder then hold the Shift key and right-click on empty space to open the Command Prompt in the same folder.
3. Then Type "ADB shell"
4. Then type "su" (This will ask root access on your phone)
5. Then type this command to open the port.
"setprop sys.usb.config diag,serial_cdev,rmnet,adb"
Then you have will access to EFStool and PDC tool to Flash mbn file using the above method
can any other users confirm this is working? I wonder if this will allow the oneplus to connect to band 13 then as well? Because freedom was keeping band 13 for phones compatible with VOLTE on their network.
It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)
astracd said:
It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)
Click to expand...
Click to collapse
does this trick only work on stock roms, or would it work on a custom rom as well?
What do you mean by Step 0?
Edit: Did some Googling and found that you have to enable it on a webpage. Use this link to do so: https://vowifi.authenticateme.ca
I can't seem to get past the command: EfsTools.exe efsInfo
Keep getting the follow: Critical Error. The Operation has timed out.
And yes I am in an elevated command prompt.
Checking device manager shows me that when I have Serial and Full-port Switch ON, I have three devices (CDev Serial, OnePlus, OnePlus) that there are no drivers installed for. Not sure where to get these as searching automatically for an updated driver returns nothing...
omvir said:
can any other users confirm this is working? I wonder if this will allow the oneplus to connect to band 13 then as well? Because freedom was keeping band 13 for phones compatible with VOLTE on their network.
Click to expand...
Click to collapse
Yes it does connect to band 13.
CrazedBoredom said:
What do you mean by Step 0?
Edit: Did some Googling and found that you have to enable it on a webpage. Use this link to do so: https://vowifi.authenticateme.ca
I can't seem to get past the command: EfsTools.exe efsInfo
Keep getting the follow: Critical Error. The Operation has timed out.
And yes I am in an elevated command prompt.
Checking device manager shows me that when I have Serial and Full-port Switch ON, I have three devices (CDev Serial, OnePlus, OnePlus) that there are no drivers installed for. Not sure where to get these as searching automatically for an updated driver returns nothing...
Click to expand...
Click to collapse
here you can download this oneplus driver . but can get this driver as well when you connect your phone to computer.
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI
nabbasi said:
here you can download this oneplus driver . but can get this driver as well when you connect your phone to computer.
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI
Click to expand...
Click to collapse
I've installed the one from my phone and still no dice. Still no drivers for the three devices. =\
This is awesome news. Thanks for sharing brother!
CrazedBoredom said:
I've installed the one from my phone and still no dice. Still no drivers for the three devices. =\
Click to expand...
Click to collapse
.
Did you run CMD as administrator if not try with that.
nabbasi said:
.
Did you run CMD as administrator if not try with that.
Click to expand...
Click to collapse
Yep, no dice.
astracd said:
It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)
Click to expand...
Click to collapse
I have op6t and am trying to do this but i am stuck on step 6 (6. Type *#801# in Phone app and enable Serial and Full-port switch).
everytime i try to do that , nothing happens. I am rooted on stock oxygen 10.3.5 if that matters.
darkknight200 said:
I have op6t and am trying to do this but i am stuck on step 6 (6. Type *#801# in Phone app and enable Serial and Full-port switch).
everytime i try to do that , nothing happens. I am rooted on stock oxygen 10.3.5 if that matters.
Click to expand...
Click to collapse
I have google dialer. So each time I run codes need to disable it and enable OP dialer as default dialer. So that could be one of reasons that doesn't work for you.
Second reason that it can be
You also need to get dialer that works as latest version doesn't work. I will try to find a post where they had dialer that works. I believe it was in one of OP5 topics for enabling the volte/vowifi.
Third reason
You would need to install engineering mode
I will try to attach the app
astracd said:
I have google dialer. So each time I run codes need to disable it and enable OP dialer as default dialer. So that could be one of reasons that doesn't work for you.
Second reason that it can be
You also need to get dialer that works as latest version doesn't work. I will try to find a post where they had dialer that works. I believe it was in one of OP5 topics for enabling the volte/vowifi.
Third reason
You would need to install engineering mode
I will try to attach the app
Click to expand...
Click to collapse
ya i managed to install the engineering mode apk from https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/ and can dial in the op dialer fine now.
when i try to enable serial it crashes but full port switch is able to turn on though.
darkknight200 said:
ya i managed to install the engineering mode apk from https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/ and can dial in the op dialer fine now.
when i try to enable serial it crashes but full port switch is able to turn on though.
Click to expand...
Click to collapse
Full port is enough. You don't need serial. :good:
astracd said:
Full port is enough. You don't need serial. :good:
Click to expand...
Click to collapse
ok now i am trying the commands in full admin but i keep getting the error message in the screenshot attatched
edit also when I have the serial port enabled, i chekd device manager and it gave me this in the 2nd screenshot. In normal mode without serial port enable, my phone shows up as normal function phone storage device.
darkknight200 said:
ok now i am trying the commands in full admin but i keep getting the error message in the screenshot attatched
edit also when I have the serial port enabled, i chekd device manager and it gave me this in the 2nd screenshot. In normal mode without serial port enable, my phone shows up as normal function phone storage device.
Click to expand...
Click to collapse
Did you open CMD as administrator?
And when you connect phone to laptop did laptop made connection sound ?
astracd said:
Did you open CMD as administrator?
And when you connect phone to laptop did laptop made connection sound ?
Click to expand...
Click to collapse
Yes to both
Other things I can think of right now change charging to drive for your usb connection.
Sometimes windows acting weird when the addresses are long. C:\xxxxxxxxx
I had saved mine in C:\efstools
I renamed folder didn't use full name
I don't think this will help, but worth to try. I will think more about it.
astracd said:
Other things I can think of right now change charging to drive for your usb connection.
Sometimes windows acting weird when the addresses are long. C:\xxxxxxxxx
I had saved mine in C:\efstools
I renamed folder didn't use full name
I don't think this will help, but worth to try. I will think more about it.
Click to expand...
Click to collapse
stil no luck with renaming them and using different state from charging to file transfer mode
NOTE - THIS GUIDE IS ONLY FOR THE REALME GT NEO 2T (RMX3357)
For the X7 Max or GT Neo/GT Neo Flash Edition, please refer to the excellent guide by @mahotlov found here.
(The X7 Max subforum seemed the best place for this guide, but please let me know if there's a better place!)
------------------------------------------------------------------------------------------------------------------Preamble: I recently purchased a Realme GT Neo 2T under the assumption it could take Realme X7 Max ROMs. The specs and design were an exact match, and since Realme has a history of releasing existing phones with new model numbers and sparklier plastic, I felt pretty good about compatibility. I quickly learned I was mistaken - both stock and custom ROMs for the X7 Max cause the display on the Neo 2T to stop working. Flashing back the stock bootloader fixed the display, but the phone would only boot into recovery, which had no touch support. Flashing the stock recovery brought back touch support, but nothing I tried could get the ROM to boot. Clearly there are changes under the hood.
Unfortunately, that left precious few options for turning the Neo 2T into a usable phone. The hardware is amazing for the price, and ColorOS is pretty decent, but the amount of non-removable bloatware and lack of Android Auto and Hey Google to activate Google Assistant was a dealbreaker for me. In the end, I decided to take matters into my own hands.
------------------------------------------------------------------------------------------------------------------
This guide will show you how to:
- Unlock your bootloader.
- Root your phone. (Magisk)
- Bypass SafetyNet. (Universal SafetyNet Fix Magisk module)
- Install Android Auto and Google apps as system apps. (BusyBox-NDK and Terminal Systemizer Magisk modules)
- Remove Realme bloatware. (ADB)
- Flash device with SP Tools and stock ROM to recover from a softbrick or restore to factory state. (SP Tools)
(Some sections are still being written and will be available soon.)
------------------------------------------------------------------------------------------------------------------
THE GUIDE ASSUMES YOU ARE USING WINDOWS 10. SOME STEPS MAY BE DIFFERENT FOR OTHER OPERATING SYSTEMS
PLEASE READ THROUGH ALL INSTRUCTIONS FIRST BEFORE PROCEEDING. ALL REQUIRED FILES CAN BE FOUND ATTACHED TO THIS POST.
UNLOCKING YOUR BOOTLOADER WILL VOID YOUR WARRANTY. THIS PROCESS WILL WIPE ALL DATA FROM YOUR PHONE. I AM NOT RESPONSIBLE FOR LOST DATA. I AM ALSO NOT RESPONSIBLE IF YOU DAMAGE OR KILL YOUR DEVICE, YOUR PROPERTY, YOUR LOVED ONES OR YOURSELF BY FOLLOWING THESE INSTRUCTIONS. YOU HAVE BEEN WARNED!
------------------------------------------------------------------------------------------------------------------
STEP 1: Unlock your bootloader.
Spoiler: Click here for instructions.
First, we need to enable developer mode. On the Neo 2T:
- Open Settings.
- Choose "About Phone".
- Choose "Version - Baseband & Kernel"
- Tap "Build Number" until developer mode is enabled.
Next, we need to turn on USB Debugging and allow OEM Unlock. On the Neo 2T:
- Go back to Settings.
- Choose "Additional Settings".
- Choose "Developer Options".
- Turn on "OEM Unlock" and "USB Debugging".
We need to get the Deep Testing app to unlock the bootloader. On your PC:
- Download "DeepTesting_GT_NEO_2T.apk" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apk to the Neo 2T. On your PC:
- Copy the "DeepTesting_GT_NEO_2T.apk" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to request unlocking of the bootloader. On the Neo 2T:
- Open the "File Manager" app.
- Choose the "APK" option.
- Find "DeepTesting_GT_NEO_2T.apk" and open it.
- Follow the instruction to install the app. You may need to allow installing from the "File Manager" app.
- Once install is finished, launch the app.
- Click "Start Applying".
- Tick the checkbox to agree to the disclaimer. Due to a bug, the disclaimer text itself may or may not appear.
- When you see "Application Submitted", click "Back."
- Go grab a coffee. It can sometimes take up to an hour for the bootloader unlock request to be approved.
- You can close the app and use your phone as normal in the meantime. Periodically open the app and click "Query Verification Status" to check your request. Once you see "Application Approved" we are done with this step.
- Unplug the Neo 2T from your PC.
- Click "Start Deep Testing".
- The Neo 2T will reboot into "Fastboot" mode. You should see a black screen with small white text.
- Plug the Neo 2T into your PC.
Now we need to install the ADB drivers. On your PC:
- Download "ADB_DRIVERS.zip" attached to this post.
- Unzip the files somewhere. Remember the location.
- Right-click on your start menu button and choose "Device Manager".
- Find the device called "Android".
- Right-click the device and choose "Update Driver".
- Choose "Browse My Computer for Drivers".
- Choose "Let Me Pick From a List of Available Drivers On My Computer".
- Click "Have Disk".
- Click "Browse".
- Navigate to the folder where you extracted the files.
- Choose "android_winusb.inf".
- Choose "Android Bootloader Interface".
- Click "Finish" to close the driver wizard once it has finished.
We need to use Fastboot to unlock the bootloader. On your PC:
- Download "ADB_FASTBOOT.zip" attached to this post.
- Unzip the files somewhere. Remember the location.
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: fastboot.exe devices
- You should see your device represented by a long string of numbers and letters followed by "fastboot".
- If you don't see this, or it doesn't say "fastboot", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: fastboot.exe flashing unlock
Your phone will now ask you to confirm unlocking of the bootloader. On the Neo 2T:
- REMINDER: THIS WILL WIPE ALL YOUR DATA!
- Read the text on the screen and follow the instructions to confirm the bootloader unlock.
Next we reboot the phone. On your PC:
- Enter this command: fastboot.exe reboot
- Your phone will now warn you during boot that the bootloader is unlocked.
- Unplug the Neo 2T from your PC.
Now we need to enter Fastboot again. On the Neo 2T:
- Allow the phone to fully boot to the initial setup wizard.
- Turn off the phone by holding down the power button until the power actions slider appears.
- Slide down to turn off the phone.
- While holding down Vol-, press and hold the power button.
- Release the power button when you feel the phone vibrate.
- Release the Vol- button when you have entered Fastboot mode. You should see a black screen with small white text.
- Plug the Neo 2T into your PC.
We will use Fastboot to get into recovery mode. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: fastboot.exe devices
- You should see your device represented by a long string of numbers and letters followed by "fastboot".
- If you don't see this, or it doesn't say "fastboot", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: fastboot.exe reboot recovery
- Wait for phone to reboot into recovery
Finally, we will wipe the data partition to ensure a clean state for future steps. On the Neo 2T:
- Select your language.
- Select "Wipe data".
- Select "Format data".
- Enter the code displayed on the screen.
- Select "Format".
- Data will be wiped. Select "OK" when finished. Phone will reboot.
- Once the phone has booted, proceed through the first time setup until you reach the home screen.
- Setup WiFi or verify/configure a data connection which will be needed for the next steps.
- If still plugged into your PC, or upon the next connection, the phone will show a popup to allow USB debugging. Check "always allow from this computer" and select OK.
- We can now move on to rooting!
STEP 2: Root your phone.
Spoiler: Click here for instructions.
First we need to reboot the phone into fastboot. On the Neo 2T:
- Unplug the Neo 2T from your PC.
- Turn off the phone by holding down the power button until the power actions slider appears.
- Slide down to turn off the phone.
- While holding down Vol-, press and hold the power button.
- Release the power button when you feel the phone vibrate.
- Release the Vol- button when you have entered Fastboot mode. You should see a black screen with small white text.
- Plug the Neo 2T into your PC.
We need to use Fastboot to root the phone. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: fastboot.exe devices
- You should see your device represented by a long string of numbers and letters followed by "fastboot".
- If you don't see this, or it doesn't say "fastboot", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: fastboot.exe flash boot magisk.img
- Enter this command: fastboot.exe flash vbmeta --disable-verity --disable-verification vbmeta.img
- Enter this command: fastboot.exe reboot
- Wait for phone to reboot.
Complete Magisk setup. On the Neo 2T:
- Open Magisk from your app drawer.
- Accept the request to install the full version of Magisk.
- Allow Magisk to install apps in the resulting popup.
- Open Magisk from your app drawer.
- Accept the request to reboot to complete installation.
- Once the phone has rebooted, the process is complete and we can move on to bypassing SafetyNet!
STEP 3: Bypass SafetyNet.
Spoiler: Click here for instructions.
First we grab the SafetyNet module for Magisk. On your PC:
- Download "safetynet-fix-v2.2.1.zip" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apk to the Neo 2T. On your PC:
- Copy the "safetynet-fix-v2.2.1.zip" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to install the module. On the Neo 2T:
- Open the "Magisk" app.
- Open Settings.
- Turn on "Zygist (Beta)" and "Enforce DenyList".
- Exit settings.
- Go to the "Modules" tab.
- Select "Install From Storage".
- Find "safetynet-fix-v2.2.1.zip" and open it.
- Wait until installation of the module is complete.
- Click the "Reboot" button that appears to reboot the phone.
- Once the phone has rebooted, the process is complete and we can move on to installing Android Auto and Google apps as system apps!
STEP 4: Install Android Auto and and Google apps as system apps.
Spoiler: Click here for instructions.
First we grab the BusyBox-NDK and Terminal Systemizer modules for Magisk. On your PC:
- Download "busybox-v1.34.1.zip" attached to this post.
- Download "terminal_systemizer_v17.4.1.zip" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apks to the Neo 2T. On your PC:
- Copy the "busybox-v1.34.1.zip" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
- Copy the "terminal_systemizer_v17.4.1.zip" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to install the BusyBox-NDK module. On the Neo 2T:
- Open the "Magisk" app.
- Go to the "Modules" tab.
- Select "Install From Storage".
- Find "busybox-v1.34.1.zip" and open it.
- Wait until installation of the module is complete.
- Click the back button.
We're ready to install the Terminal Systemizer module. On the Neo 2T:
- Go to the "Modules" tab.
- Select "Install From Storage".
- Find "terminal_systemizer_v17.4.1.zip" and open it.
- Wait until installation of the module is complete.
- Click the "Reboot" button to reboot the phone.
Time to get the Google Play Store app. On your PC:
- Download "Google_Play_Store_29.9.16-21.apk" attached to this post.
- Plug the Neo 2T into your PC.
Now, we need to allow file transfers. On the Neo 2T:
- Select "Transfer Files" on the "Use USB to" popup.
Time to send the .apk to the Neo 2T. On your PC:
- Copy the "Google_Play_Store_29.9.16-21.apk" file you downloaded to the "Download" folder on the internal storage of the Neo 2T.
We're ready to install the Google Play Store. On the Neo 2T:
- Open the "Files" app.
- Choose the "APK" option.
- Find "Google_Play_Store_29.9.16-21.apk" and open it.
- Follow the instruction to install the app. You may need to allow installing from the "File Manager" app.
- Once install is finished, launch the app.
We need to install our apps before we can systemize them. On the Neo 2T:
- Open the Google Play Store and sign in.
- Update any apps that have updates available.
- Use the Google Play Store to install Android Auto, Google Assistant, and the Google app.
We need to use ADB to systemize Android Auto and Google Assistant. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: adb.exe devices
- You should see your device represented by a long string of numbers and letters followed by "device".
- If you don't see this, or it doesn't say "device", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: adb shell
- Have your phone unlocked and at the ready, then enter this command: su
Allow root for ADB Shell. On the Neo 2T:
- Select "Forever" on the superuser request popup for Shell. Click "Grant".
Now we can systemize Android Auto and Google. On your PC:
- Enter this command: systemize
- Type 1 and hit enter to choose "Systemize Installed Apps (Listed)".
- You should see a numbered list of apps after a few seconds of loading. Find the numbers for "Android Auto" and "Google" and type them with a space in between. For example, if you see "1 - Android Auto" and "2 - Google", type 1 2 followed by enter.
- Type 2 and hit enter to choose "/system/priv-app" for the first app.
- Type 2 and hit enter to choose "/system/priv-app" for the second app.
Reboot the phone. On the Neo 2T:
- Hold down the power button until the power actions slider appears.
- Slide up to reboot the phone.
- Once rebooted, Android Auto will soon disappear from your app launcher now that is a system app. This is by design.
- Use the Google Play Store to install "Android Auto for Phone Screens".
- Open the "Android Auto for Phone Screens" app. Complete all setup steps.
- Open the "Android Assistant" app. Complete all setup steps.
- Open the "Google" app. Go to More > Settings > Google Assistant > Hey Google & Voice Match.
- Turn on "Hey Google". Complete all setup steps.
- In the Google Assistant settings in the Google app, you should now be able to turn on "Hey Google" voice activation.
- Hold down the power button until the power actions slider appears.
- Slide up to reboot the phone.
- Upon reboot, Android Auto should now work both on the phone and with Android Auto compatible vehicles head units.
- Hey Google should now work as long as the screen is on.
- Time for debloating!
STEP 5: Remove Realme bloatware.
Spoiler: Click here for instructions.
First we need to install an alternative input method, since we will be removing the stock keyboard. On the Neo 2T:
- Use the Google Play Store to install an input method of your choice, such as GBoard.
Now we can run the debloat script. On your PC:
- Plug the Neo 2T into your PC if it is not already.
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Double-click the RMX3357_A14_DEBLOAT_NO_ROOT.bat file to run the non-root debloat script.
- Press Enter to run the script.
- Close the window or press Enter to exit once finished.
We need to use ADB to remove a few system apps. On your PC:
- Open the folder where you extracted the "ADB_FASTBOOT.zip" (Done previously during Step 1: Unlock your bootloader.)
- Open a command prompt pointing to the extracted files. (The fastest way to do this is to open the folder, then replace the file path with "cmd" end hit enter.)
- Enter this command to check that your phone is detected: adb.exe devices
- You should see your device represented by a long string of numbers and letters followed by "device".
- If you don't see this, or it doesn't say "device", double-check your USB cable or port, and make sure you installed the drivers as instructed previously.
- Enter this command: adb shell
- Enter this command: su
- Enter this command: pm uninstall --user 0 com.android.email
- Enter this command: pm uninstall --user 0 com.coloros.safecenter
- Enter this command: pm uninstall --user 0 com.heytap.book
- Enter this command: pm uninstall --user 0 com.heytap.market
- Enter this command: pm uninstall --user 0 com.heytap.themestore
- Enter this command: pm uninstall --user 0 com.nearme.gamecenter
Reboot the phone. On the Neo 2T:
- Hold down the power button until the power actions slider appears.
- Slide up to reboot the phone.
- You're done! Enjoy your debloated phone!
UH OH: Unbricking and Factory Restore.
Spoiler: Click here for instructions.
Click here for the ROM, use SP tools to flash. Guide coming soon, for now use the guide here.
------------------------------------------------------------------------------------------------------------------Realme GT Neo 2T Tips:
- If you find yourself needing to force your phone to power off for any reason, on the Neo 2T you must hold Vol+, Vol- and Power at the same time for around 10 seconds.
- The stock messaging app is com.android.mms, otherwise known as Mms.apk. It seemingly cannot be removed without breaking SMS/MMS.
- Removing Breeno will replace it with Google Feed when swiping left on the stock launcher fi the Google app is installed.
- There's a good chance the APN settings the phone chose are incorrect or nonexistent. Double-check them to make sure you have working data and MMS for your SIMs.
- Android Auto forces the phone to 60Hz and locks the settings, even once disconnected. Seems to be a common issue across a bunch of phones. Reboot to fix.
- If an app isn't showing notifications or is otherwise misbehaving:
>>> Make sure the app has been opened at least once since the phone was last powered on or rebooted.
>>> Check that notifications are enabled in Settings > Notifications & Status Bar > Manage Notifications > [Your App].
>>> If that doesn't help, try allowing background activity in Settings > Battery > App Battery Management > [Your App].
>>> Lastly, you can disable battery optimization for an app in Settings > Battery > More Battery Settings > Optimize Battery Use > [Your App].
------------------------------------------------------------------------------------------------------------------
Spoiler: SOURCES
Guide by @mahotlov I shamelessly stole bits from: https://forum.xda-developers.com/t/x7-max-and-gt-neo-flash-ubrick-instructions.4337339/
Magisk: https://github.com/topjohnwu/Magisk
SafetyNet-Fix: https://github.com/kdrag0n/safetynet-fix
BusyBox NDK: https://github.com/Magisk-Modules-Repo/busybox-ndk
Terminal Systemizer: https://github.com/Magisk-Modules-Repo/terminal_systemizer
Reserved #1.
Hi, thanks for topic!
Have any room stock global? Need with language Portuguese of Brazil, i'm using the app MoreLocale to change, but this is not automatic
J_Eudes said:
Hi, thanks for topic!
Have any room stock global? Need with language Portuguese of Brazil, i'm using the app MoreLocale to change, but this is not automatic
Click to expand...
Click to collapse
Unfortunately there is no global ROM for the GT Neo 2T, I specifically asked Realme and they said they have no plans to release one.
Hi @MatinatorX, can you help to extract framework-res.apk and settings.apk? I would like to explore the possibility of decompiling those apk and adding languages. thank you!
dewidoj461 said:
Hi @MatinatorX, can you help to extract framework-res.apk and settings.apk? I would like to explore the possibility of decompiling those apk and adding languages. thank you!
Click to expand...
Click to collapse
Sure, here you go.
Hey, Is there a notification solution? to come from everyone?
AngelXTR91 said:
Hey, Is there a notification solution? to come from everyone?
Click to expand...
Click to collapse
Haven't had any issues with notifications myself. I'd check these:
- Make sure the app has been opened at least once since the phone was last powered on or rebooted.
- Check that notifications are enabled in Settings > Notifications & Status Bar > Manage Notifications > [Your App].
- If that doesn't help, try allowing background activity in Settings > Battery > App Battery Management > [Your App].
- Lastly, you can disable battery optimization for an app in Settings > Battery > More Battery Settings > Optimize Battery Use > [Your App].
Who faced such a (another) problem, let's say I have a working chat in a telegram, and today I read it through a smart watch while I was busy, but noticed that if there are more than 5+ unread notifications in the chat, then it stops even making a sound that something new has come, is there a way to treat this? and a similar story with viber as well. (translate.google)
AngelXTR91 said:
Who faced such a (another) problem, let's say I have a working chat in a telegram, and today I read it through a smart watch while I was busy, but noticed that if there are more than 5+ unread notifications in the chat, then it stops even making a sound that something new has come, is there a way to treat this? and a similar story with viber as well. (translate.google)
Click to expand...
Click to collapse
Unfortunately I'm not sure why that might be happening. I don't have a smartwatch and I don't use Telegram or Viber. I can tell you that Slack and Wyze both keep giving me notifications well after 5 of them. Maybe someone else might know.
My Neo 2T just arrived and upon further inspection, seemed to be preinstalled with Indian firmware by the seller which has Google Play Services and the languages I needed. Posted a screenshot of build number in case it helps anyone.
If anyone knows how to backup my ROM file, I'm willing to try and share it for everyone.
Edit: Out of ideas. MTK Droid Tool reports "Unknown ROM structure, backup NOT possible!"
dewidoj461 said:
My Neo 2T just arrived and upon further inspection, seemed to be preinstalled with Indian firmware by the seller which has Google Play Services and the languages I needed. Posted a screenshot of build number in case it helps anyone.
If anyone knows how to backup my ROM file, I'm willing to try and share it for everyone.
Edit: Out of ideas. MTK Droid Tool reports "Unknown ROM structure, backup NOT possible!"
Click to expand...
Click to collapse
As much as I'd love to find some sort of global ROM for this phone, that looks identical to my build number etc. when I first got the phone and probably the China ROM. Latest now is A14. When I asked, Realme was pretty adamant that this phone will never see a global ROM. They had also installed Google Play and a long list of languages for me before shipping, but these just bolt on to the stock China ROM.
I'm not sure how to tell 100% if it's actually the China ROM or not, but I'd give "Hey Google" a try, or Android Auto if you have an AA compatible vehicle. Would also be curious to know if your phone came with a bunch of bloatware apps and Breeno.
As for backing up, SP Tools is what worked for me. I recommend taking a proper backup ASAP just in case something goes wrong later. That said, I'm not sure how to anonymize the files it spits out (empty data partition, remove your IMEI etc) so it's safe to share.
I can confirm that "Hey Google" works, no chinese apps and breeno too. FYI, the bootloader was already unlocked when I got the phone. I noticed the Region defaulted to India so it's probably a custom firmware tailored to this phone. The box and manuals were chinese though.
As for the SP Flash Tool, how do I load the DA? This error appears after selecting the scatter file and clicking readback.
dewidoj461 said:
I can confirm that "Hey Google" works, no chinese apps and breeno too. FYI, the bootloader was already unlocked when I got the phone. I noticed the Region defaulted to India so it's probably a custom firmware tailored to this phone. The box and manuals were chinese though.
Click to expand...
Click to collapse
Oh wow. A proper global ROM for this phone would be amazing. I'll see if I can figure out how to turn a backup into something flashable. In the meantime I think I'm going to email Realme again and see if their tune has changed.
Would it be possible to share where you bought the phone? I got mine from "realme Direct Store" on AliExpress.
I bought it from a reseller in shopee malaysia. I've asked the seller for the source to no avail, they just said it was the supplier who installed the rom.
I sent Realme an email directly, hopefully I get a more favorable answer this time. Will update if I hear anything. My AndroidFileHost account finally got upload perms so if I manage to get the ROM out of them it'll be easy to share.
Managed to take a proper backup after reading the guide by mahotlov linked in your thread. Just let me know which files you'd need anytime and I'd be willing to share.
Edit: Wifi and bluetooth no longer works after flashing your magisk.img & vbmeta.img. Restored my backup and it works again, interesting
I have a DM from someone else who also has an India A13 ROM shipped with their Neo 2T, so this is definitely a thing, but Realme responded to me yesterday and is still claiming it doesn't exist. They are having similar issues with the China ROM I uploaded breaking things. I seriously hope there aren't multiple hardware versions under the RMX3357 model number messing everything up.
As for your backup, I think it should be possible to just pick some of the files from your backup and use them to replace the matching .img file in the China ROM upload. This is assuming the partition structure and other things are the same and only the contents of the partitions are different (which it should be, but you never know). Only thing I'm not 100% sure on is which partitions would be safe to share and which ones might have personal info like IMEI or bits of your data partition.
dewidoj461 said:
Just let me know which files you'd need anytime and I'd be willing to share.
Click to expand...
Click to collapse
Please check here scatter to backup phone on sp flash tool and give me link download ROM_0-55 except ROM_14,15,18,19,24(ram, nvdata, nvcfg, protect1, protect2) in folder SP Flash tool.
Andy_men2 said:
Please check here scatter to backup phone on sp flash tool and give me link download all ROM_0-55
Click to expand...
Click to collapse
I would advise against this @dewidoj461. One of those ROMs has your IMEI info in it, and if you had been using the phone before your backup there is likely personal info somewhere too, especially if SIMs were installed. Maybe the intent here is not malicious but that user account is brand new and you would absolutely be giving sensitive information by supplying your full backup.
EDIT: I'm also suspicious about that RAR. The scatter file is only 54kb while that RAR is 2.1MB.
A lot of things changed with OnePlus brand, now they are exactly same as Oppo (OxygenOS 13 and ColorOS 13 are exactly same)
I believe OnePlus 9 Pro was the last real OnePlus smartphone.
R.I.P. OnePlus and OxygenOS !!
By the way this isn't the point of this thread, so let's start the process:
Unfortunately you need root access to enable VoLTE, also you need a windows PC for this.
Warning: do it at your own risk, I'm not responsible if somethings goes wrong for you !!
In my opinion, OnePlus created a whitelist for carriers and if your carrier is not on the list, you can't use VoLTE, even though it fully supports it !! WTF OnePlus ?!!
Before with OnePlus 9 Pro we could enable VoLTE by LogKit and EngineerMode
Now with OnePlus 10 Pro you are out of luck because LogKit doesn't work at all and you can't easily access to EngineerMode !!
Fortunately, still we can enable it
Note: If your phone model is NE2215 i recommend you to convert it to NE2213 with OPLocalUpdate app as NE2213 supports more 4G bands
0- Extract stock boot.img from payload.bin
Download one of below Full ROMs:
[NE2213] OxygenOS 13.1.0.522(EX01)
[NE2213] OxygenOS 13.1.0.521(EX01)
[NE2213] OxygenOS 13.1.0.520(EX01)
[NE2213] OxygenOS 13 C.30
[NE2213] OxygenOS 13 C.26
[NE2213] OxygenOS 13 C.22
[NE2213] OxygenOS 13 C.21
[NE2213] OxygenOS 13 C.20
[NE2213] OxygenOS 13 C.19
[NE2213] OxygenOS 13 C.17 (Android 13 Beta 2)
[NE2213] OxygenOS 12 A.15
[NE2213] OxygenOS 12 A.12 (Android 12 Rollback)
You can find payload.bin in Full ROM zip file
Use payload_dumper to extract boot.img
Code:
python3 payload_dumper.py --images boot payload.bin
Another option to doing this is FastbootEnhance which is a windows GUI app
1- Prepare your PC
Unzip Platform-Tools (You should add the directory path to "Environment Variables > System variables > Path")
Spoiler: Verify "Platform-Tools" installation
Check if you installed platform tools correctly:
Search for cmd, right click on it and select "Run as administrator"
Type "adb --version" and hit the enter button
If the output shows adb version that means you installed platform tools correctly
Install Qualcomm USB Drivers
Install QPST
2- Prepare your phone
Enable "Developer options" (click on "Settings > About device > Version > Build number" several times)
Go to "Settings > System settings > Developer options" and enable "OEM unlocking" + "USB debugging"
Spoiler: Unlock bootloader
Connect your phone to PC in MTP mode (File Transfer)
Open cmd (Run as administrator) and type "adb reboot bootloader"
Allow USB Debugging for your PC in the phone
Now type "fastboot flashing unlock"
On your phone you should see a message about unlocking the bootloader
With volume up/down you can move between options
Select Unlock boot loader option with power button (It will wipe your data)
Done, the phone bootloader is unlock now.
Spoiler: Root access
Since you unlocked the bootloader you should enable developer options again
Install latest version of Magisk (Download apk from here)
Patch stock boot.img:
Transfer stock boot.img to your phone
Open Magisk and select install
Choose "Select and Patch a File" then click on "LET'S GO"
You can find the patched boot in "Download" directory
Transfer it to your PC
Temporary root access:
Open cmd (Run as administrator) and type "adb reboot bootloader"
Allow USB Debugging for your PC in the phone
Type "fastboot boot patched_boot.img" (change patched_boot.img to whatever your filename is)
Permanent root access:
After booting, Open Magisk and click on install again
Now select "Direct Install (Recommended)" then click on "LET'S GO"
Done, you have a permanent root access now
Note: There are some guides that suggest you a way to update with OTA when you have root access
But i don't recommend it, because it's risky and you may get into bootloop
** IGNORE OTA UPDATE while you have root access **
3- LogKit alternative
With LogKit you could bring back "VoLTE calls" and "Wi-Fi calling" to sim settings
As i mentioned before LogKit no longer works on OnePlus 10 Pro
To achieve this:
Install "VoLTEEnabler" magisk module and reboot
Now you should see the options in "Settings > Mobile network > SIM 1"
4- EngineerMode alternative
With EngineerMode we could enable "Full-port switch" to working with PDC
By root access you can achieve this easily:
1- Connect your phone to PC in MTP mode
2- Open cmd and type:
Code:
adb shell
3- Switch to root user (For first time you need to grant root access to adb on your phone) :
Code:
su
4- Enable Full-port switch:
Code:
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
5- Last step
Open PDC app (It's included in QPST)
Open device dropdown and select your phone
Spoiler: Skip this if you can find "Commercial-DT-VOLTE"
Find "Oversea-Commercial_DS" or "Common-Commercial" and make sure both Sub0 and Sub1 are Inactive (for me both were Inactive by default)
Find "Commercial-DT-VOLTE" and Active it for both Sub0 and Sub1 (right click on it > SetSelectedConfig > click on Sub0 ... do the same for Sub1 ... now both are Pending, click on Activate)
BOOM! you can see "VoLTE" icon on your status bar
{
"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"
}
Note: You should repeat steps 4 and 5 after each reboot
Anyway, it's better than nothing
If someone found a permanent way please share it with the community
[Edit] Just one more step:
Remove the default profile ("Oversea-Commercial_DS" or "Common-Commercial") to keep VoLTE active after device reboot
(Thanks to @ash083)
>> Final word
This is my first and last OnePlus phone!
OnePlus completely destroyed OxygenOS (Say hi to MiUi [ColorOS] by OnePlus [OPPO] !!!)
Almost 99% people buy OnePlus to enjoy stock android experience with a bunch of customization options.
For me OnePlus is dead.
I will buy google pixel 7 pro next year and don't let any of my family member or my friends buy from this FAKE BRAND (OnePlus) !!!
If this topic was useful for you press the thanks button
Hi
Followed everything but never got the voLTE icon on the statusbar
Gunsmoke_79 said:
Hi
Followed everything but never got the voLTE icon on the statusbar
Click to expand...
Click to collapse
Dude, first make sure your carrier supports VoLTE ...
Install "5G Only" app:
5G Only - Android 11 Compatibl - Apps on Google Play
Change your network mode to 5G only (NR only)
play.google.com
You need to check "Voice Service" and "Voice Network Type" values.
Here is mine
As you can see:
Code:
Voice Service: In Service
Voice Network Type: LTE
Guys, I have bad news, since "1 September" SecrecyAutoUnlocker stopped working as other users reported here
I just do a reboot today and damn !! No VoLTE again !!
SecrecyAutoUnlocker no longger works for me too
Nice job OPPO (OnePlus) !!!
No need to use SecrecyAutoUnlocker if you're rooted.
QPST port can be opened with adb command
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
not sure about PDC but I use efsTools and efs explorer to enable volte.
Also, engineermode is still accessible with this magisk module I made. It doesn't require that decrypt tool. Flash this module, reboot and type *#649010# to open ports. And btw Engineermode's main activity is *#36446337#
6addri said:
No need to use SecrecyAutoUnlocker if you're rooted.
QPST port can be opened with adb command
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
not sure about PDC but I use efsTools and efs explorer to enable volte.
Also, engineermode is still accessible with this magisk module I made. It doesn't require that decrypt tool. Flash this module, reboot and type *#649010# to open ports. And btw Engineermode's main activity is *#36446337#
Click to expand...
Click to collapse
Thanks!
With root access we don't need EngineerMode at all
6addri said:
No need to use SecrecyAutoUnlocker if you're rooted.
QPST port can be opened with adb command
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
not sure about PDC but I use efsTools and efs explorer to enable volte.
Also, engineermode is still accessible with this magisk module I made. It doesn't require that decrypt tool. Flash this module, reboot and type *#649010# to open ports. And btw Engineermode's main activity is *#36446337#
Click to expand...
Click to collapse
Hey 6addri yes please share your method!
Thanks
Gunsmoke_79 said:
Hey 6addri yes please share your method!
Thanks
Click to expand...
Click to collapse
OP edited
Check it again
I managed to enable VoLTE on OOS13 OB 2
Thanks to @6addri
Is this working for 9 pro?
vigorito said:
Is this working for 9 pro?
Click to expand...
Click to collapse
Probably yes
On 9pro with a familiar dial code there is no logkit and engeer. mode too,they remove it ,so what are the steps then for 9pro (LE2123)
vigorito said:
On 9pro with a familiar dial code there is no logkit and engeer. mode too,they remove it ,so what are the steps then for 9pro (LE2123)
Click to expand...
Click to collapse
You need unlocked bootloader + root access (check 9 Pro forum)
Other steps should be same as 10 Pro
Already start to working on that,so after i finish unlock b./root access, i should skip rom flashing and start from step prepare your pc i mean its allready prerared skipping flashing rom step 0,i just dont get this step for "Environment Variables > System variables > Path") do i have to unzip platform tools to the path you wrote or i have to do something else
vigorito said:
Already start to working on that,so after i finish unlock b./root access, i should skip rom flashing and start from step prepare your pc i mean its allready prerared skipping flashing rom step 0,i just dont get this step for "Environment Variables > System variables > Path") do i have to unzip platform tools to the path you wrote or i have to do something else
Click to expand...
Click to collapse
You need "adb" + "fastboot" and both are required for rooting
So i think you already have these (if you didn't use a wrapped tool for rooting)
To confirm this type:
"adb --version"
"fastboot --version"
In cmd, you should see adb and fastboot version.
i figure out variable settings path,i have working adb,and i can boot into bootloader with "adb reboot bootloader" command (locked) but im having problem after i type "fastboot devices" in cmd not showing device id,but command "adb devices" showing device id hm
vigorito said:
i figure out variable settings path,i have working adb,and i can boot into bootloader with "adb reboot bootloader" command (locked) but im having problem after i type "fastboot devices" in cmd not showing device id,but command "adb devices" showing device id hm
Click to expand...
Click to collapse
You should open cmd with admin access (Run as administrator)
i always do that
i use command adb reboot bootloader,phone get into fastboot mode and when i send command fastboot oem unlock its just says waithing for any device,usb debb. is ON and oem unlcok is ON,qualcom drivers are installed its all good
I tried using the magisk module, and in the SIM1 settings I have VoWifi enabled (with preference), but it does not work at all. The icon does not show in the status bar, and when I turn off VoLTE, calls do not work. Is this module known to not work on A13?
EDIT: In the 5G Only app, under IMS status I see that Voiceover WiFi is unavailable (LTE is available). How do I enable it? Contact my carrier?
Arnav74 said:
I tried using the magisk module, and in the SIM1 settings I have VoWifi enabled (with preference), but it does not work at all. The icon does not show in the status bar, and when I turn off VoLTE, calls do not work. Is this module known to not work on A13?
EDIT: In the 5G Only app, under IMS status I see that Voiceover WiFi is unavailable (LTE is available). How do I enable it? Contact my carrier?
Click to expand...
Click to collapse
This topic isn't about VoWiFi
Also my carrier doesn't support VoWiFi, so i can't test it, sorry!