Related
Hello, I have a Nexus S 4G, flashed on Metro PCs, data is working and MMS works fine as well, but would like 3G instead of 1X. Im running GB, and a rom. I have my msl code, and am trying to update my prl to 3022. I have all the drivers installed also. Ive tried the HERO rom, and many others but I cant dial ##775#. I have also changed the epst.apk file, but cannot update prl, Thanks for the help & I am running CM
These are the steps I took to add the PRL to my Samsung Galaxy S2 Epic 4g (metropcs)...credit goes to an XDA Developer member that did this...I just copied and paste. It was a while ago and did not get his name. I take no credit. But this worked for me.
Updating the PRL on Samsung
Once you know your MSL, you need to download and install the program QPST 2.7 Build 323, it might be possible to use another version of the program but this guide was made using version 2.7 b323. QPST is not a paid program but is intended for developers, providers and maintenance technicians, according x-drivers.com the software is “freeware”.
1. google, download and install QPST 2.7 Build 323.
2. download the Kies setup program above and install it, included are the drivers you will need.
3. Make sure your Epic is not USB debugging mode, to disable, go to settings>applications>development>uncheck USB debugging
4. On your Epic, with the touchscreen dialer, dial ##8778#
5. Change the setting from AP to CP, then hit Home.
6. Connect your phone to your computer with the usb cable.
7. Your computer will automatically install the modem drivers for your Epic wait until you see the “device is ready for use”
8. Open QPST Configurations. Start>All Programs> QPST> QPST Configuration.
9. Click on the “Ports” tab and “Add a new port”
10. Select the “COMXX – USB\QC Diagnostic” and click ok, in my case the port number was 10, your port number will be different, if you see more than one, disconnect all your external devices such as external HDDs, phones, Bluetooth dongles, ect. If you don’t see a port. Disconnect your phone, restart your computer, connect your phone and try again, you might want to remember your Epic’s port number for future use. If you still don't see a port uncheck the box for "Show Serial and USB/QC Diagnostic ports only" and add all of the USB/Unknown ports. One of them should show an active phone.
11. Click “Start Clients” on the top of the program and open Service programming.
12. On the new Phone Selection windows you should see one active phone select it and click ok.
13. Click “Read from the phone” and enter your 6-digit MSL code
14. Click on the “Roam” tab and click the “Browse…” button, here you will need to browse for the PRL file select it and open it.
15. Click “Write to Phone”
16. Your Epic Touch will reboot and you can close all the programs now. On your phone go to settings>about phone>status> and make sure the PRL version matches the PRL number you downloaded, if yes, Congratulations you all done!!
17. Don’t forget to change back the USB settings to AP on the ##8778# menu
The problem,
montecristo1 said:
These are the steps I took to add the PRL to my Samsung Galaxy S2 Epic 4g (metropcs)...credit goes to an XDA Developer member that did this...I just copied and paste. It was a while ago and did not get his name. I take no credit. But this worked for me.
Updating the PRL on Samsung
Once you know your MSL, you need to download and install the program QPST 2.7 Build 323, it might be possible to use another version of the program but this guide was made using version 2.7 b323. QPST is not a paid program but is intended for developers, providers and maintenance technicians, according x-drivers.com the software is “freeware”.
1. google, download and install QPST 2.7 Build 323.
2. download the Kies setup program above and install it, included are the drivers you will need.
3. Make sure your Epic is not USB debugging mode, to disable, go to settings>applications>development>uncheck USB debugging
4. On your Epic, with the touchscreen dialer, dial ##8778#
5. Change the setting from AP to CP, then hit Home.
6. Connect your phone to your computer with the usb cable.
7. Your computer will automatically install the modem drivers for your Epic wait until you see the “device is ready for use”
8. Open QPST Configurations. Start>All Programs> QPST> QPST Configuration.
9. Click on the “Ports” tab and “Add a new port”
10. Select the “COMXX – USB\QC Diagnostic” and click ok, in my case the port number was 10, your port number will be different, if you see more than one, disconnect all your external devices such as external HDDs, phones, Bluetooth dongles, ect. If you don’t see a port. Disconnect your phone, restart your computer, connect your phone and try again, you might want to remember your Epic’s port number for future use. If you still don't see a port uncheck the box for "Show Serial and USB/QC Diagnostic ports only" and add all of the USB/Unknown ports. One of them should show an active phone.
11. Click “Start Clients” on the top of the program and open Service programming.
12. On the new Phone Selection windows you should see one active phone select it and click ok.
13. Click “Read from the phone” and enter your 6-digit MSL code
14. Click on the “Roam” tab and click the “Browse…” button, here you will need to browse for the PRL file select it and open it.
15. Click “Write to Phone”
16. Your Epic Touch will reboot and you can close all the programs now. On your phone go to settings>about phone>status> and make sure the PRL version matches the PRL number you downloaded, if yes, Congratulations you all done!!
17. Don’t forget to change back the USB settings to AP on the ##8778# menu
Click to expand...
Click to collapse
See, I was doing some research and found that you couldn't use the ##8778# (diag mode) in Cyanogen Mod.
This is my build here,
{
"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"
}
& this is how my drivers, and what QPST says.
so I have no idea why it wont let me use ##8778#, or why I QPST wont even recognize the phone. I will be using 3022.prl though for Metro Pcs 3G
hi
To get into diag mode for cyanogenmod or any aosp roms it is going to be *#*#8778#*#*
savalasurge said:
To get into diag mode for cyanogenmod or any aosp roms it is going to be *#*#8778#*#*
Click to expand...
Click to collapse
I've tried but I cant get into DIag mode with a custom ROM from cyanogen
:laugh:Hello guys,
This is my first tutorial on the XDA-developers forum, in order to improve myself and be more efficient, do not hesitate to comment, or ask questions, I will be more then happy to answer since I have spent so much time on this, using two different I9505, mine and my boss's. So without further ado, let's get started
Here is a full guide on how to downgrade your I9505 from 4.4.2 to 4.3. KNOX WILL TRIGGER, there are other tutorials that show how to downgrade 4.4.2 to 4.3 without triggering the knox, I will explain some of them, but they are not 100% successful.
Do it on your own risk, neither me nor XDA-developers will be responsible if you brick or damage your phone.Nevertheless, if you follow those exact steps, you won't have any problem (you may actually have some, but we can solve them together).
Requirements:
Samsung galaxy S4 I9505
Rooted phone
CWM or any custom Recovery
CyanogenMod 10.2.1 [click here] (jellybean 4.3.1) or any other custom with its proper kernel
Google apps jellybean [here]
(May need) Modem FNC4 or any above FNB8 [here]
(May need) Pit File to resolve some problems [here]
[KNOX 0x1 (triggered) WORKS 100%]
[Step 1: Optional, only if you can root your phone]
Before we start, I advice you backup your phone, save your EFS folder which contains your IMEI and other "sensitive information" related to your phone:
To do that, first you need to root your phone, then use a file explorer such as "ES FILE EXPLORER".
{
"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"
}
Go to your explorer and turn on "root explorer".
Once you have done that, go to your root folder.
Copy the folder called EFS to your SD Card.
(Optional)Make another copy on your HDD or file-hosting provider.
[Step 2: Installing the rom]
Copy your CyanogenMod or any other 4.3 custom fw + Google apps into your sdcard
Shutdown your phone
Press and hold down volume up, home button and power button to start in recovery mode (for about 5secondes)
Wipe data/cache (if you have philztouch, chose that you will install a new rom) and press YES
Advanced -> Wipe dalvik cache YES
Install zip from sdcard -> chose cyanogenmod zip file -> YES
Install zip from sdcard -> chose gapps zip file -> YES
Reboot your computer.
[Step 3: Resolving some problems]
If the phone application crashes whenever you try to make a phone-call, then you should flash your modem.
1.Shutdown you phone.
2.Press and hold down volume down, home button and power button to start in download mode until you see the confirmation, then press up to continue
3.Plug your micro usb cable into your phone, go to odin
4.Select modem (or CP for odin 3.09) and select the modem file
5.Uncheck Autoreboot
6.Click Start
7.Once done, unplug your cable, take off the battery, put it back, redo steps 2 to 4
8.Check this time Autoreboot and Start the process
If you flash your phone and you don't have the sound, then I advice you go back to 4.4.2, and follow this guide from the beginning
[KNOX 0x0 (not triggered) WIFI OFF]
I do see the point to go back to 4.3 (a lot of applications don't work properly on Kitkat + better performances for the S4 on Jellybean), however, I don't know if someone can use his phone without the wifi. Anyway, if you want you can try this method, for simply go back to 4.3, use saferoot and install mobile odin to go to 4.4.2 rooted, without triggering the knox (be aware that there is a simple method which roots the 4.4.2 but this doesn't work on newer 4.4.2).
I remind you that KNOX triggers only if you use a custom rom or modified kernel, in that case Knox turns to 0x1, and this cannot be undone.
Instead of writing my method, I find out two threads on xda.
First one, you cannot make phonecalls unless you flash the modem, and then you won't have the wifi anymore.[here]
Second, not tested yet, but it is promising, you can find out [here]
That's it guys, hope this will help you find your happiness.
I get 'No SIM' after 4.4.2 update. Any solution dear?
Sim adapter?
tariq2kn said:
I get 'No SIM' after 4.4.2 update. Any solution dear?
Click to expand...
Click to collapse
Ohhh noo sim, did you have a nano sim with an adapter or something ? I get this with my nanosim with the adapter
cefkiller said:
Ohhh noo sim, did you have a nano sim with an adapter or something ? I get this with my nanosim with the adapter
Click to expand...
Click to collapse
No adapter used.
My phone seems to be region locked, btu. I had an unlocking pin code to use another sim. But, when I am using the phone in India, It doesn't asks the pin but I get No SIM, I can see the signals on the statusbar & in about/status. It is not able to resolve the network. The /system/csc/customer.xml file states the mmc 404 as network blocked. The changing of network bands is also not possible. It is set by default at lte/wcdma/gsm.
I tried downgrading to 4.3 but got the phone in emergency mode, probably due to the locked bootloader. The Service Mode by *#0011# doesn't moves after the initial page.
How do I get through this mess? Kindly help in solving the issue.
tariq2kn said:
No adapter used.
My phone seems to be region locked, btu. I had an unlocking pin code to use another sim. But, when I am using the phone in India, It doesn't asks the pin but I get No SIM, I can see the signals on the statusbar & in about/status. It is not able to resolve the network. The /system/csc/customer.xml file states the mmc 404 as network blocked. The changing of network bands is also not possible. It is set by default at lte/wcdma/gsm.
I tried downgrading to 4.3 but got the phone in emergency mode, probably due to the locked bootloader. The Service Mode by *#0011# doesn't moves after the initial page.
How do I get through this mess? Kindly help in solving the issue.
Click to expand...
Click to collapse
Mmm I am afraid your phone is region locked, in this case it is very difficult to resolve the issue, for example if you are in Turkey your phone must be registered through a service, or purchased locally, I don't know maybe in India it is the same, meanwhile, try using your original sim Card, if it works, try using another sim card, i have a sim card that works on my Oneplus One but doesn't on the S4, it is crazy but what can we do. Finally, (before selling or throwing out your phone) try to visit this thread it might be helpful to follow those steps, visit all the links there, each one propose a solution. Hope you will find your happiness.
Regards.
Moncef
First of all this is not my work I only tested theirs.
Credit to @themustached for finding that a patched .ops was the solution.
This guy doesn't even have the damn phone yet and did this for us so show some love. You can donate to him through paypal here - http://paypal.me/dustinwann
Also @Eliminater74 @jkyoho and others for their hard work and dedication to this conversion.
Disclaimer: I do not take responsibility for any damage done to your device by using this procedure. Everyone has problems sometimes so be civil and ask clear questions explaining where you failed if you expect help.
These instructions will convert your TMOBILE Oneplus 7 PRO to the International version of the phone.
This lets you unlock the bootloader, root, twrp etc.. Sim unlock is still being worked on.
Take a breath, drop the hype and read every single step before you even plug your phone into the PC.
These steps assume you understand you lose all data on the device, are sim unlocked, have the Download mode drivers installed, adb and fastboot and your device powered OFF.
1) Download both of these archives and extract them to a folder you can locate. - https://mega.nz/#!289BVITR https://mega.nz/#!St1DiShb Mirror - https://www.androidfilehost.com/?w=files&flid=294946
2) Open the MSM tool and uncheck the box next to SHA 256.
3) Hold both volume buttons for 5 seconds then plug in the USB cable. OR In ADB type "adb reboot edl".
4) Watch the MSM tool and the second it says *Connected* next to one of the COM ports, press START.
5) DO NOT unplug the device until after it says Success in green.
6) Once the phone boots into the system, go through all the setup options.
7) Enable Developer Options and enable OEM Unlocking.
8) Enter bootloader mode on your device and type "fastboot oem unlock".
You now have an unlocked international OP7.
If you want to root and install twrp dont take the OTA yet.
-Follow these two threads below then take the OTA, do that after you root and twrp. You can preserve root by going into Magisk Manager after the OTA installs, then press the top Install button on the right and use the after OTA option.
This will put you on the latest version with twrp, root and working sound/wifi.
1) Root - https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205 by @acervenky
2) Twrp - https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322 by @mauronofrio
3) OTA zips - https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585 by @Titokhan
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
*Future proofing Update*
Hot off the press. Here is a tool that will allow you to patch an ops file without having to download a new modified one every update.
You can use this with a stock MSM or the modified one linked above. Must be run on an unmodified ops..
Global
EU
China
1) Extract the Patcher into the same directory as your MSM tool and OPS firmware.
2) Launch the Patcher as admin. Now select the ops you want to patch and check all the boxes under Patch Options and click Start.
{
"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"
}
3) Once it finishes you will be able to flash the ops file from the stock MSM or the modded one above.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
*TMobile Update*
The MSM tool/firmware for TMobile OP7Pro is now released.
You can find it on my other thread - HERE
Credit for this one also goes to @themustached.
Guacamole decryption key - 836tI3vZa3ixi9487IpxNEw-I5RGT3QjJXmm0dGYLcI
Additional decryption key - ezLIQmIL9j7OQV1qcvJtof8M0pCHYY_nC9W4pDaw3is
~FAQ~
~Not fast enough to start flash
If you press Start on the MSMTool it will "wait for device".
Doing this will make the flash start right when the phone enters EDL.
~MSM is getting stuck on Param Preload or something similar.
This can be caused by having old Oneplus L2 drivers from a different model installed.
-Follow the steps up until MSM gets stuck. Open Device Manager, right click on the Qualcomm device under the COM section.
Click Uninstall but do not check the box to delete the driver, then click Scan for Hardware changes. Now go to the folder you extracted the L2 driver to, right click the inf file and click Install.
You should be able to use the MSM tool right away but may need to exit and re-open. Also restart back into EDL if needed.
You guys are the best, I'm going to try it once I get home. Do I need to unlock the bootloader if I don't want to after the conversion?
Sent from my GM1915 using Tapatalk
Can u lock bootlaoder and stay like international version plus get update update the air without pushing it?
I converted mine manually or I'd do this, but that was quick boys! Awesome job. Going to be lots of happy people now that this is out.
Niceeeeeeee
So this is the patched tool to convert to intl
Yup I'll give it a shot once I get home!
Sent from my GM1915 using Tapatalk
Can't wait to try this when I get home. Thank you all for the work.
So I did accidentally unplugged the device after doing the 5 seconds thing and plugged it into a computer. I unplugged it by accident and now it won't turn on.
Strike99Fear said:
So I did accidentally unplugged the device after doing the 5 seconds thing and plugged it into a computer. I unplugged it by accident and now it won't turn on.
Click to expand...
Click to collapse
Just press the power button for 20 seconds or so
Primal instinct said:
Just press the power button for 20 seconds or so
Click to expand...
Click to collapse
Tried it and it won't work.
i connect the op and show Qualcomm QD loader on device manager but then it will disconnect and show usb mass storage device
Strike99Fear said:
So I did accidentally unplugged the device after doing the 5 seconds thing and plugged it into a computer. I unplugged it by accident and now it won't turn on.
Click to expand...
Click to collapse
Try hold power and both volume buttons
Bootloader unlock is optional, correct?
Adb reboot edl also works but fully converted here
Primal instinct said:
Try hold power and both volume buttons
Click to expand...
Click to collapse
That worked thanks brother!
Does deleting modem St files remove the Sim lock on the OP7 as well?
I'm gonna try it wish me luck
OEM unlocking is greyed out for me at Step 7, not sure if I did something wrong.
Spoiler: Phone Data:
{
"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"
}
Hi Guys,
I'm super new to the whole topic and am only doing this because I have a spare smartphone and wanted to learn something.
The bootloader is unlocked.
The USB drivers are installed on the PC.
USB Debugging is turned on.
Smartphone states "Orange State [...]" while booting.
Then I tried to extract the boot.img via the "MTK Droid Root & Tools v2.5.3" to flash this later with Magisk. But here I got the following error message:
Spoiler: MTK Error
The same messages have been there before I did anything on the smartphone for the first time.
From DE to ENG:
--->>> Connect to device <<<---
--- ERROR: --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!--- unknown ROM structure, backup NOT possible!ATTENTION! a file (/system/recovery-from-boot.p) which restores the stock recovery in case of normal phone startup was found!
So I flashed a stock rom here from
Spoiler: link
Umidigi A7 Pro Stock Firmware ROM (Flash File)
Download Official Umidigi A7 Pro Firmware (original flash file) without any password for Free. We also provide the Stock Rom for other Umidigi devices.
xdafirmware.com
to the phone via the SP Flash Tool (because I did something that enabled the first Boot Loop), the phone restarts in factory state succesfully, I set it up once and then installed Magisk, and using Magisk patched the boot.img of the from I downloaded.
However, when I now want to flash it via the flash tool, this error message appears:
Spoiler: Flash Tool Error
And suddenly I am in boot loop. As soon as I flash the original boot.img, the phone starts as usual.
I have also tried the whole thing via TWRP, and as soon as I install Magisk.zip via the TWRP the boot loop angers me again. Also MTK still shows the same error.
Spoiler: I have followed the following instructions:
Main Guide: https://www.getdroidtips.com/root-umidigi-a7-pro/
Helping Video:
Spoiler: Magisk log
I'm happy about anything that helps me out getting this phone rooted
Sorry my friend that noone has yet to have replied to your inquiry here. Ill do my best to give you some of the knowledge I have when it comes to setting you in the right direction without failure next time. Today and for the last month or so I have been working hard with the Umidigi a7 pro 64gb. To be clear are you making sure to flash the magisk zip file of the boot.img file that you saved from the stock firmware. You shouldn't have to fiddle around with to many of the settings just when you do flash the patched file you have to make sure to uncheck everything other then boot.img patched file. I am very new to this as well and honestly it's a tricky process to get it ever done right on your first attempt. You seem to have and know enough knowledge on this topic. MTK is a finnacky processor. I myself have yet to get this device fully rooted yet. The issue I myself have is my PC is not properly updating the MTK and other drivers to make the magic happen which I think I am just going to have to get my other dell going again to try on a fresh PC that I just set up again for this exact thing. To my most recent knowledge though when it comes to the Umidigi a7 pro you have to follow each and every step closely and to a exact precise t or the whole operation will fail every time you try. Are you using your micro SD card to it's full potential and making sure that you saved the patched file properly. You also have to watch for corrupt files when it comes to this kind of thing. But you know enough to just trust the pages you are downloading your files from and make sure everything is signed and legit. Another thing is what seemed to help me is removing SP flash tool completely from my PC. Then re downloading it and starting from scratch by flashing your stock scatter file and I find when flashing hold the power button when it starts for just a few seconds only some people think to keep holding the power button through the entire flash process but to my knowledge what has worked from a noobs perspective is hold power for just a few seconds until the full load of the red bar comes and then when it goes away you can let go of power button and it will continue on with the rest of the manual installment process. There are a lot of high technical highs and lowes when it comes to what you can do here and from the info I've gotten MTK devices weren't really meant to be able to withstand even being remotely compatible devices for root. Honestly let me know how things are going lately for you as I know this post is a bit old. I myself have came close to periodically throwing this phone as far out of the window as it can reach, I'm not a quitter by any means and still today and even right now m working on that to try to help others in any way i possibly can and today I will get this device into full root accesss.
Hello, I'm new to this- all of it, I've only just recently got into rooting and such things, but I'm progressing and that's what matters, no?
Anyway, I've successfully managed to root this phone via Magisk, that no one probably cares for anymore through trial and error and I'll do my very best to explain my method, and give updates as this is very on-going, there are certain issues and things I need to work out, but I appreciate any help, pointers, and such as before mentioned, I am new.
{
"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"
}
ALCATEL A30 FIERCE - Specs, and Specifications.
This phone was released in August, 2017.
Display - 5.5inches, 1280 x 720
Camera - 13 MP (Single Camera)
Hardware - MediaTek, 2GB RAM
Storage - 32GB, microSDXC
Battery - 3000mAh
OS - Android 7.0 Nougat
My own notes about this device.
Lots of MetroPCS Bloatware, can be a bit janky, but it's manageable.
It does not have a traditionally accessed Bootloader, no "adb reboot bootloader", this command just restarts the device to system.
Fastboot is odd, I managed to access Fastboot by some way I don't entirely understand, I'll go about what I did to get there later on in this post and try to recreate it later on as this post updates.
This device has colour states (if that's commonology), meaning, once the Bootloader is "unlocked", you will get an "Orange State" message before starting your phone that gets in the way of some things, I have yet to fix this, but I imagine we will if this gains traction, there will be a quicker fix!
No TWRP yet, as of posting, flashing a ported twrp.img through MTK_TWRP, or the TWRP_Port has not worked, and after flashing, neither will flashing the stock recovery but I've a quickfire way of getting around to fix this, if I can.
MTKCLIENT - https://github.com/bkerler/mtkclient
My Process, in the system, press the build number seven times to enable developer options - enable OEM Unlocking.
Then enable USB Debugging, and make sure you've installed adb and fastboot, as well as the correct drivers.
Through that link, follow the instructions specific to your operating system (I use POP OS and WINDOWS 11, YOU DON'T HAVE TO USE THE SAME AS ME), you may use the mtkclient_gui for an easier experience.
To unlock the bootloader, which will trigger "Orange State", open your terminal in the directory of the mtkclient and run python "mtk e metadata,userdata,md_udc", then, with your powered off device, and it will say something along the lines of "Preloader - Waiting for Device", with your USB Cable, and your wits about you, hold the volume down button (if this doesn't work for you, hold both volume buttons in" and plug your device into your PC with that command running. If the command completes, then run "python mtk da seccfg unlock", and this will unlock your bootloader.
WARNING: Unlocking the bootloader wipes the data of your device!
After this, dump your boot vbmeta with the commands in the mtkclient instructions, if this does not work for you with python or python3, I will provide the required files below.
Then, power your device back up, and install the patched magisk-app and push it to your sd card through adb, or traditional file transfer.
If you have your boot.img, push it to your sd card and patch it with magisk, then retrieve it from your phone - this is where my tutorial and mtk's tutorial take a bit of a turn!
I had a problem with the "reconnecting to preloader" phase, as it would not go through, or an error labeled [Unpack Requires A Buffer Of 12 Bytes] would crop up which prevented me from flashing the required files through "python mtk w boot,vbmeta boot.patched,vbmeta.img.empty". Let's go through some cautionary steps, what I did to achieve perma-root.
Create a funny-named file in the mtkclient directory labeled "DUMPY", do "python/python3 mtk_gui" and connect your powered off phone through the previously mentioned volume holding until it connects you in BROM mode. Under "read partitions", select all partitions, then "read partitions" and make sure the output is that "DUMPY" folder. This process will take awhile!
Once it finishes, rename your patched magisk-boot from [magisk.img name] to "boot.patched.bin" and under "write partitions", select the boot partition and write the boot.patched.bin to the boot partition! Once finished, start your device and install a root checker! It should be working!
If there are any errors, I will do my best to try and help you but keep in mind, I am very new to this, I hope it works for you too!