Database Develop

Device won't be detected on QFIL/QPST, No ESN/No Phone

So, to modify the modem of dipper in order to get VoWi-Fi on my phone, I probably need to have the aceess to 9008 DIAG port. When I enable the diag port from ADB shell, it only enables 901D which won't work with QFIL or QPST. Are there anybody succeded with this?
EDL enables 9008, but QPST or QFIL still won't let me to backup or modify since it's on the download mode.
@tsongming I believe you are experienced with this procedure, so I guess I want to tag you.
Edit : Anyone has an idea to fix this? NO PHONE / NO ESL on QPST

The War Profiteer said:
So, to modify the modem of dipper in order to get VoWi-Fi on my phone, I probably need to have the aceess to 9008 DIAG port. When I enable the diag port from ADB shell, it only enables 901D which won't work with QFIL or QPST. Are there anybody succeded with this?
EDL enables 9008, but QPST or QFIL still won't let me to backup or modify since it's on the download mode.
@tsongming I believe you are experienced with this procedure, so I guess I want to tag you.
Click to expand...
Click to collapse
I have seen this issue a few years ago and off the top of my head I don't remember. But there is a solution, and I am pretty sure that I made notes about it, give me a few minutes and I will look for it, and will be back soon.
---------- Post added at 12:31 AM ---------- Previous post was at 12:12 AM ----------
The War Profiteer said:
So, to modify the modem of dipper in order to get VoWi-Fi on my phone, I probably need to have the aceess to 9008 DIAG port. When I enable the diag port from ADB shell, it only enables 901D which won't work with QFIL or QPST. Are there anybody succeded with this?
EDL enables 9008, but QPST or QFIL still won't let me to backup or modify since it's on the download mode.
@tsongming I believe you are experienced with this procedure, so I guess I want to tag you.
Click to expand...
Click to collapse
Okay, at first I thought that you are bricked and that you could not get into EDL. But after re-reading your post. I see that you are not, You are wanting to open bands using QPST. While, I have read that this possible, as far as I know you need a proprietary a proprietary tool that is very expensive.
This link describes the steps and has a broken link to an old version of the tool and a link to a current version which is very pricy
https://forum.xda-developers.com/le-pro3/help/unlocking-bands-t3565979
I have more info on this, and when I find it, I will come back and add more. I remember an article on a Miui website that had instructions step by step, so I am looking for that too. I have never personally never attempted opening bands. However, I have read stories of success and failure when attempting to do it, so it may be risky. Nonetheless, I think you are well aware of that, and I am interested to see if it can be done.
Edit: If you are hard bricked and can not enter EDL, you will need to buy the EDL cable from Amazon they are cheap, like $5 or if the phone is seen from ADB you can get to EDL ( 9008) with this command : adb reboot edl

tsongming said:
I have seen this issue a few years ago and off the top of my head I don't remember. But there is a solution, and I am pretty sure that I made notes about it, give me a few minutes and I will look for it, and will be back soon.
---------- Post added at 12:31 AM ---------- Previous post was at 12:12 AM ----------
Okay, at first I thought that you are bricked and that you could not get into EDL. But after re-reading your post. I see that you are not, You are wanting to open bands using QPST. While, I have read that this possible, as far as I know you need a proprietary a proprietary tool that is very expensive.
This link describes the steps and has a broken link to an old version of the tool and a link to a current version which is very pricy
https://forum.xda-developers.com/le-pro3/help/unlocking-bands-t3565979
I have more info on this, and when I find it, I will come back and add more. I remember an article on a Miui website that had instructions step by step, so I am looking for that too. I have never personally never attempted opening bands. However, I have read stories of success and failure when attempting to do it, so it may be risky. Nonetheless, I think you are well aware of that, and I am interested to see if it can be done.
Click to expand...
Click to collapse
Thanks for your help. I'm not trying to unlock bands, I need to merge a few files into the phone using the QPST in order to get it working, so I need to get into 9008 without having to use download mode. ?

The War Profiteer said:
Thanks for your help. I'm not trying to unlock bands, I need to merge a few files into the phone using the QPST in order to get it working, so I need to get into 9008 without having to use download mode. ?
Click to expand...
Click to collapse
I edited the last post; EDL is port 9008 : you can get there with : adb reboot edl or worst case scenario : https://www.amazon.com/Flash-Cable-...coding=UTF8&psc=1&refRID=7ZR98PJHRW9BJE5SQXV3 Cheaper ones exist on Amazon
@The War Profiteer
You can also enter EDL with this TWRP : https://drive.google.com/open?id=1eOnz-NzHkLc_UNCeD_ecE6C3sCXhwU-U
Just choose the reboot to EDL option

tsongming said:
I edited the last post; EDL is port 9008 : you can get there with : adb reboot edl or worst case scenario : https://www.amazon.com/Flash-Cable-...coding=UTF8&psc=1&refRID=7ZR98PJHRW9BJE5SQXV3 Cheaper ones exist on Amazon
You can also enter EDL with this TWRP : https://drive.google.com/open?id=1eOnz-NzHkLc_UNCeD_ecE6C3sCXhwU-U
Click to expand...
Click to collapse
I see. Some people were able to backup or modify the firmware on 901D mode apparently, but I'm unable to do that. It says No Phone/No ESN on QPST program, and QFIL will say that no phone found on that port. Do you have any idea how can I achieve this? I've been trying many drivers to be able to do it, all of them has failed.

The War Profiteer said:
I see. Some people were able to backup or modify the firmware on 901D mode apparently, but I'm unable to do that. It says No Phone/No ESN on QPST program, and QFIL will say that no phone found on that port. Do you have any idea how can I achieve this? I've been trying many drivers to be able to do it, all of them has failed.
Click to expand...
Click to collapse
You can use software tools such as this : https://forum.hovatek.com/thread-22384.html
This guy claims to have had some luck : https://forum.xda-developers.com/showpost.php?p=76921725&postcount=23 with his Note 5 Pro. I am not sure if it will work on newer phones with, newer SDK's especially with the massive amount of security changes in the past 6 months.

tsongming said:
You can use software tools such as this : https://forum.hovatek.com/thread-22384.html
This guy claims to have had some luck : https://forum.xda-developers.com/showpost.php?p=76921725&postcount=23 with his Note 5 Pro. I am not sure if it will work on newer phones with, newer SDK's especially with the massive amount of security changes in the past 6 months.
Click to expand...
Click to collapse
Thanks a lot. I'm starting to think that I'm having this issue because of I'm on a custom rom. Does MIUI EU roms require wiping the data when migrating from other Custom roms? If so, I'll probably stop messing with it since I have 90 gb of data on my phone ?

The War Profiteer said:
Thanks a lot. I'm starting to think that I'm having this issue because of I'm on a custom rom. Does MIUI EU roms require wiping the data when migrating from other Custom roms? If so, I'll probably stop messing with it since I have 90 gb of data on my phone
Click to expand...
Click to collapse
The last time that I installed EU beta rom, I definitely had to format storage and of course the same for the Stable build.
However, there is usually no issues when switching from one custom Miui to another, sometimes all I do is wipe cache, install the new Rom, ( FYI : temporary remove root prior to switching to avoid bootloops) and usually there are no issues at all. After installing the new Rom, I check for Google updates, clean out any remaining files with SD Maid, then Root the phone. To be clear, in this example, I am talking about using Miui Pro to Mi-Globe or to Ros Miui etc.
Again, I usually will always have to wipe storage when using the beta EU builds, which is why I usually stick with Mi-Globe when using Miui. On the other hand, for a long while I was using a version of TWRP that could not decrypt data. So it possible that I would have the issue with the TWRP that I linked above.
Currently my data is unencrypted and although I really like the recent Havoc Rom that I have been using for several days, I am wanting to checkout the very latest Stable Miui build ( and manually debloat it)
I will see if I can keep my data without wiping and come back her and let you know if I have an issue. ( I keep all of my most commonly used files on a Flash drive, so it doesn't take very long to restore its no where near the amount of data that you have. Plus, one thing that is great about Mi Cloud is how it restores practically everything.
@The War Profiteer
Okay, I just installed the latest stable, its updating now and I was able to confirm that all of my data is still here. ( Nice!) Which also confirms that the last time when I had an issue and had to format user data it was mostly likely because of the version of TWRP that I was using at the time.
So it seems if you want to install Miui Stable or Miui EU, your data should remain in tact as long as you are using a TWRP that can decrypt data or you do not have your data encrypted.

tsongming said:
The last time that I installed EU beta rom, I definitely had to format storage and of course the same for the Stable build.
However, there is usually no issues when switching from one custom Miui to another, sometimes all I do is wipe cache, install the new Rom, ( FYI : temporary remove root prior to switching to avoid bootloops) and usually there are no issues at all. After installing the new Rom, I check for Google updates, clean out any remaining files with SD Maid, then Root the phone. To be clear, in this example, I am talking about using Miui Pro to Mi-Globe or to Ros Miui etc.
Again, I usually will always have to wipe storage when using the beta EU builds, which is why I usually stick with Mi-Globe when using Miui. On the other hand, for a long while I was using a version of TWRP that could not decrypt data. So it possible that I would have the issue with the TWRP that I linked above.
Currently my data is unencrypted and although I really like the recent Havoc Rom that I have been using for several days, I am wanting to checkout the very latest Stable Miui build ( and manually debloat it)
I will see if I can keep my data without wiping and come back her and let you know if I have an issue. ( I keep all of my most commonly used files on a Flash drive, so it doesn't take very long to restore its no where near the amount of data that you have. Plus, one thing that is great about Mi Cloud is how it restores practically everything.
@The War Profiteer
Okay, I just installed the latest stable, its updating now and I was able to confirm that all of my data is still here. ( Nice!) Which also confirms that the last time when I had an issue and had to format user data it was mostly likely because of the version of TWRP that I was using at the time.
So it seems if you want to install Miui Stable or Miui EU, your data should remain in tact as long as you are using a TWRP that can decrypt data or you do not have your data encrypted.
Click to expand...
Click to collapse
I'm using Pixel Experience. I'm sure switching between MIUI based roms are not an issue, but I'm afraid of AOSP to MIUI. ?

The War Profiteer said:
I'm using Pixel Experience. I'm sure switching between MIUI based roms are not an issue, but I'm afraid of AOSP to MIUI. ?
Click to expand...
Click to collapse
I was on Havoc, and went to Miui stable, I wrote that in my post above.
All of my data is still here. Photos, Music, Texts etc.
@The War Profiteer
The confusion maybe came from my original statement then I came back and edited the post.
So there my original was due to TWRP.
Apparently no issue going from AOSP to MIUI... Using the version of TWRP that works with encryption.

tsongming said:
I was on Havoc, and went to Miui stable, I wrote that in my post above.
All of my data is still here. Photos, Music, Texts etc.
@The War Profiteer
The confusion maybe came from my original statement then I came back and edited the post.
So there my original was due to TWRP.
Apparently no issue going from AOSP to MIUI... Using the version of TWRP that works with encryption.
Click to expand...
Click to collapse
That's awesome. Since I am creating backups of all of my apps, it feels safe to migrate temporarily. Still I will have NANDroid backups before I do. Thanks for the info.

The War Profiteer said:
That's awesome. Since I am creating backups of all of my apps, it feels safe to migrate temporarily. Still I will have NANDroid backups before I do. Thanks for the info.
Click to expand...
Click to collapse
Anytime brother, you have definitely helped me before as well

A heads up: It works on stock miui while not working on pixel experience. Please write on this thread if anyone gets it working on any other custom roms.
Edit: Apparently custom roms don't have the required tools to use the software, only stock roms will let you to modify your efs.

tsongming said:
Anytime brother, you have definitely helped me before as well
Click to expand...
Click to collapse
Hi, if you still are on MIUI, can I have a screenshot of your /sys/devices/virtual/android_usb/android0 ? I think the required USB drivers for the communication between QPST and Phone should be in this folder, which are non-existent on a custom rom. I am expecting a folder named "f_diag".

The War Profiteer said:
Hi, if you still are on MIUI, can I have a screenshot of your /sys/devices/virtual/android_usb/android0 ? I think the required USB drivers for the communication between QPST and Phone should be in this folder, which are non-existent on a custom rom. I am expecting a folder named "f_diag".
Click to expand...
Click to collapse
Sure, I am using Miui Pro at the moment. Here is the screen shot.
Unfortunately, no f_diag here. But I will look for it.
@The War Profiteer
This page has some information that may be helpful, there is also a video.
http://www.99mediasector.com/how-to-enable-qualcomm-diagnostic-mode-diag-port/
It's possible that the f_diag is hidden until its enabled.
According to the linked page : The DIAG PORT Code For Xiaomi Qualcomm : #*#717717#*#* or alternately *#*#13491#*#*
I hope this helps.

tsongming said:
Sure, I am using Miui Pro at the moment. Here is the screen shot.
Unfortunately, no f_diag here. But I will look for it.
@The War Profiteer
This page has some information that may be helpful, there is also a video.
http://www.99mediasector.com/how-to-enable-qualcomm-diagnostic-mode-diag-port/
It's possible that the f_diag is hidden until its enabled.
According to the linked page : The DIAG PORT Code For Xiaomi Qualcomm : #*#717717#*#* or alternately *#*#13491#*#*
I hope this helps.
Click to expand...
Click to collapse
Thank you for the information.
The issue here is while diag port can be enabled on any custom rom using the setprop command, and will be detected by host, I believe the interface that allows the communication of the host and device does not exist on custom roms. I thought that the f_diag folder's content would be the interface and that's why I asked for a screenshot.
I am guessing that custom roms won't support modified modem/efs to get custom files for WFC and ViLTE. So to fix this, I've tried to replace priv-app content of the Pixel Experience with the ones from MIUI, and didn't succeed.
For now, I'm trying to find out which files in OS are responsible for WFC (ViLTE is not that important) and the interface of MIUI or any other stock roms that allows you to communicate with diag port.
UPDATE: It appears that diag port has something to do with the kernel, I'm still looking into it. It's possible that the communication between the host and the device may need an interface that is supported by kernel, still unsure about it. Needs more investigation. Unfortunately most of the people asking for "How to open it", but nobody asks "How does it work and communicate"", which makes it difficult to find the information I need.

The War Profiteer said:
Thank you for the information.
The issue here is while diag port can be enabled on any custom rom using the setprop command, and will be detected by host, I believe the interface that allows the communication of the host and device does not exist on custom roms. I thought that the f_diag folder's content would be the interface and that's why I asked for a screenshot.
I am guessing that custom roms won't support modified modem/efs to get custom files for WFC and ViLTE. So to fix this, I've tried to replace priv-app content of the Pixel Experience with the ones from MIUI, and didn't succeed.
For now, I'm trying to find out which files in OS are responsible for WFC (ViLTE is not that important) and the interface of MIUI or any other stock roms that allows you to communicate with diag port.
UPDATE: It appears that diag port has something to do with the kernel, I'm still looking into it. It's possible that the communication between the host and the device may need an interface that is supported by kernel, still unsure about it. Needs more investigation. Unfortunately most of the people asking for "How to open it", but nobody asks "How does it work and communicate"", which makes it difficult to find the information I need.
Click to expand...
Click to collapse
I have a couple of friends who have developed Miui Roms for years, and they definitely know Miui inside and out. I haven't spoken to them for a while, but I will message both of them and ask if they can come here and help.

tsongming said:
I have a couple of friends who have developed Miui Roms for years, and they definitely know Miui inside and out. I haven't spoken to them for a while, but I will message both of them and ask if they can come here and help.
Click to expand...
Click to collapse
Thanks a lot!
So I'll summarize the issue:
- The goal: My priority is to be able to use VoWiFi with the modified EFS, which works flawlessly MIUI but not on other ROMs. I'm suspecting that the ROM files aren't able to read EFS to provide VoWiFi or they don't exist at all, which means VoWiFi isn't supported by the ROM. Wanna fix this.
- Diag port seems to be communicating on MIUI while doesn't on custom roms. The reason to work with this port is to be able to edit EFS while custom rom is installed, since I'm creating an EFS backup on Miui and reflasshing it on the desired ROM.

The War Profiteer said:
Thanks a lot!
So I'll summarize the issue:
- The goal: My priority is to be able to use VoWiFi with the modified EFS, which works flawlessly MIUI but not on other ROMs. I'm suspecting that the ROM files aren't able to read EFS to provide VoWiFi or they don't exist at all, which means VoWiFi isn't supported by the ROM. Wanna fix this.
- Diag port seems to be communicating on MIUI while doesn't on custom roms. The reason to work with this port is to be able to edit EFS while custom rom is installed, since I'm creating an EFS backup on Miui and reflasshing it on the desired ROM.
Click to expand...
Click to collapse
Just to clarify things a bit (my own experience):
-on my phone I have full working VoWIFI (at least on my second SIM) on Vodafone Germany.
-I'm using PE as a ROM
-it worked with both Sphinx and Canting Kernels
-VoLTE and VoWIFI are both Carrier dependant
-in order to get VoWIFI working, I just activated the option in the settings. It just worked ootb.
And I must say sorry, because I am not able to test other ROMs/kernels. I need a stable phone as a daily driver. I'm using my phone for work stuff too, because I don't want to have to carry two phones around.

phonexpert_alex said:
Just to clarify things a bit (my own experience):
-on my phone I have full working VoWIFI (at least on my second SIM) on Vodafone Germany.
-I'm using PE as a ROM
-it worked with both Sphinx and Canting Kernels
-VoLTE and VoWIFI are both Carrier dependant
-in order to get VoWIFI working, I just activated the option in the settings. It just worked ootb.
And I must say sorry, because I am not able to test other ROMs/kernels. I need a stable phone as a daily driver. I'm using my phone for work stuff too, because I don't want to have to carry two phones around.
Click to expand...
Click to collapse
Thank you for additional info, surely will help a lot to my search. I'm using PE CAF too (sadly, CAF will be cancelled).
First of all, I thought PE wasn't compatible with WFC, but your statement has confirmed that it's working, so the problem is on my side.
The problems I'm guessing that could be about ROMs and/or kernels are:
1- They may be unable to recognize/read/process a modified EFS and they may be reading only modem. I've merged the proprietary files for enabling VoWiFi, which were officially extracted from a SDM845 device that is officially supported by carrier, to the EFS using QPST. It was supposed to work on MIUI, and it did when I tested it. I created a backup of EFS and did a clean install of PE CAF, restored EFS from the backup and it didn't work. I also tested the backup with a clean MIUI setup and it did work, so I don't think there is an issue about the backup or restoration process since I used the same TWRP version.
2- Diagnostics port will be enabled with "# setprop sys.usb.config diag,adb" command, but since the kernel or the ROM doesn't have the interface to establish the communication between the host and the device, I was unable to check or edit the EFS partition if everything is OK.
I'm here to look for suggestions at the moment. Modifying modem image may be dangerous since it can be signed by the manufacturers in order to prevent any modification, which can lead to an unrecoverable bricks, and I don't know what to modify and how to do it.
Thanks, again. Pardon me if I did any grammar mistakes which will lead to misunderstandings or will make the post completely unintelligible.

[Q] A Proper Guide for Rom Flashing Our Mi8? Avoiding EDL and Bricking Device

Greetings Folks
For starters I just got Mi8 and am planning to go for Havoc or Pixel Experience there is a Pixel Port too I'll have to try which is best close to stock but with gestures features and full fledged Gcam support
Back to Questions
I have seen many threads where newer folks are victim of their devices getting bricked and paying for fix?
Why isnt there a proper guide thread to avoid these obstacles and spread awareness out ?
I know there are certain partitions you need to backup too e.g efs in case of lost IMEI there was a thread Its hell I have been through it with a Samsung Device,There was a guy who messed up his phone sensor files?
But most of all EDL and Devices getting brick so lets address the elephant in the room
Now My Phone is on
MIUI 10.3 Global 10.3.2.0(PEAMIXM)
Android Version : 9 PKQ1.180729.001
Android Security Patch : 2019-04-01
Rom threads say 9.3
take havoc for example
Help Appreciated thanks

@techyrock
Here is a guide : https://forum.xda-developers.com/mi-8/how-to/how-to-install-roms-resolve-issues-t3911611
Part 1 ( The OP is general info ) Below the first couple of comments have detailed steps for AOSP.
Be extremely careful, unfortunately this community doesn't have a lot of highly active professionals.
So definitely double check any advice that you are given, or that you find. With that being said there are definitely several members that are mature, knowledgeable, friendly and overall fantastic.
If you need help, feel free to ask me anytime, I haven't had a lot of time to use XDA recently. But if I am around, I am always willing to help. At the moment I am going to sleep, but go ahead and read my thread, and I have made some lengthy post that may be helpful as well. You can find those posts by reading my post history. Enjoy.
As long as your account is bound to your device, unbricking is pretty easy with these phones. If you want to avoid a brick, avoid brand new builds, test software etc. Some of the recent issues actually stemmed from the 7.11 china developer rom which had a major issue.
if you want to use Miui with zero ads, and every single feature, then Mi-Globe is pretty great, and solid on a week to week basis.
As far as AOSP, I feel that in my experience that Syberia is practically always highly stable, but it's a little plain compared to some other roms. I also liked Pixel 3, Bootleggers ( Newer version) and Havoc. ( I used Havoc in the beginning of July and loved it, that build is fantastic)
I haven't tried a lot of AOSP roms on this phone yet. So that is all I have

Addition to that, the main issue is people are using Miflash to flash a ROM from bootloader. DO NOT USE IT.
Just use the flash_all.bat in the fastboot rom zip, it's easy. Miflash chooses to lock bootloader by default, and if you don't change it, you'll need to use EDL to fix your device. People usually forget about it, and will whine here to be able to unbrick. Don't be one of them
Don't relock the damn bootloader. It's unnecessary, and dangerous on a Chinese machine.

The War Profiteer said:
Addition to that, the main issue is people are using Miflash to flash a ROM from bootloader. DO NOT USE IT.
Just use the flash_all.bat in the fastboot rom zip, it's easy. Miflash chooses to lock bootloader by default, and if you don't change it, you'll need to use EDL to fix your device. People usually forget about it, and will whine here to be able to unbrick. Don't be one of them
Don't relock the damn bootloader. It's unnecessary, and dangerous on a Chinese machine.
Click to expand...
Click to collapse
We ok that to unlock bootloader on mi8 we have to use mi "flash" unlock tool. Right?
Cheers

Erpe7 said:
We ok that to unlock bootloader on mi8 we have to use mi "flash" unlock tool. Right?
Cheers
Click to expand...
Click to collapse
Yes, that is the only way to unlock. he was talking about using Mi Flash to flash roms, which may seem to be user friendly which it is but is also extremely dangerous because the the option to lock the bootloader is checked by default. If using it make sure that its unchecked and you should not have any issues.
Personally, I prefer ADB if flashing via fastboot or TWRP with a OTG flash drive.
Also there is a tool that is excellent that I have also used many times, its called Tool all in One ( TAIO) After your bootloader is unlocked, you can use TAIO for many functions, including keep your PC's ADB platform tools, up to date, and providing system wide access. You can use it to remove encryption, flash recovery, root, roms or to restore to stock. It definitely worth installing if if you only use it to keep your drivers, and platform tools up to date.

First of all thanks guys for replies wasn't expecting this response
My device is Global Mi8 bootloader is locked for now I still have some hours left I'll be able to unlock it by 26th
miflash_unlock prompted to bind my account from developer option for unlocking,I did so it will be bound to my account and ill be unlocking it for first time I believe i bought it used but previous owner seemed to have know info about ROMs though
I have been using Pixel 2XL twice followed by Nokia 8 so I am much more inclined towards AOSP stock experience the two feature I would love to have from MIUI are the
1)MIUI gestures
2)MIUI Dual Apps (I am aware of Play store alternatives but clash of clans doesnt work as good on them as on dual apps )
I know gestures are on Havoc
guess you guys have been playing around with your mi8 kindly guide me to right directrion what ROMs you guys prefer and why ?
how would you prefer to flash a ROM do I need to back up any partitions ? if so which app should use for it ,Ill surely back up everything via TWRP for sure
also the encryption thingy should I sign out my google account before bootloader unlock and other stuff?
and since I am on
MIUI 10.3 Global 10.3.2.0(PEAMIXM)
Android Version : 9 PKQ1.180729.001
Android Security Patch : 2019-04-01
is it safe to flash havoc ?

tsongming said:
Yes, that is the only way to unlock. he was talking about using Mi Flash to flash roms, which may seem to be user friendly which it is but is also extremely dangerous because the the option to lock the bootloader is checked by default. If using it make sure that its unchecked and you should not have any issues.
Personally, I prefer ADB if flashing via fastboot or TWRP with a OTG flash drive.
Also there is a tool that is excellent that I have also used many times, its called Tool all in One ( TAIO) After your bootloader is unlocked, you can use TAIO for many functions, including keep your PC's ADB platform tools, up to date, and providing system wide access. You can use it to remove encryption, flash recovery, root, roms or to restore to stock. It definitely worth installing if if you only use it to keep your drivers, and platform tools up to date.
Click to expand...
Click to collapse
Thank you for this precious advices ;(
I'll note that!
Sent from my Redmi Note 5 Pro using XDA Labs

Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk

ktrokar said:
Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk
Click to expand...
Click to collapse
There's a primary bootloader that we consumer know of and there's Qualcomm's Emergency Download Mode bootloader (EDL) , since Mi8 has ARB(Anti Rollback) downgrading the phone gets it bricked to EDL mode requiring EDL authentication to my understanding thats why edl is a thing(since its just emergency bootloader for oems to work with) I have not experienced it personally so I don't know whether it bricks that way or not but ARB and EDL authentication are a thing with Mi8 from what I have read in different threads
Sent from my MI 8 using Tapatalk

ktrokar said:
Thank you folks.
Could someone explain what EDL is meaning?
Gesendet von meinem BTV-DL09 mit Tapatalk
Click to expand...
Click to collapse
EDL is Qualcomm recovery mode, it's the mode that you must be in to restore a hard bricked phone.
As long as you are careful you should never need to worry about EDL. Basically, you place the phone into a mode that the computer is able to recognise port 9008, once that is down you can use 1 of 4 techniques to restore your phone. Unbricking Xiaomi's is actually very easy to do, as long as the device is bound to your account.
The big issue is that unscrupulous Chinese vendors, used their own account to unlock bootloaders of Mi8's and other Xiaomi devices, then installed the Global Miui ROM and then sold the phone as new to unsuspecting western customers and at a lower price than western outlets such as Amazon. These vendors marketed the phones as Ïnternational versions" when they were actually Chinese devices and not the Global version that the customer thought they bought.
When these customer's used programs such as MiFlash to upgrade their phone's their bootloaders were locked and the are unable to log into their Mi Account to restore the phone. Remember the vendors unlocked the phone, so these Mi8's were bound to the vendor and not the final customer. This is the Primary reason why Xiaomi makes us wait to unlock the bootloader. Finally, ARB is potential issue, but it hasn't been implemented yet on Global devices.
So do your research before flashing anything and you should be safe.

Is it possible to encrpyt a ROM and dont lose anything.?

The question probably sounds stupid but after almost a year of just forgetting about using root or unlocking bootlader i forgot many things.
I remember i used to have a mi 9 with encryption on and everytime i open twrp you will need to decrypt the data.
Now with the MI 9T Pro i had to format data in order to boot into Evolution X ROM that of course left me with a decrypted phone and i dont really like it in case my phone gets stole or something.
Do you guys know if i can use the option inside teh ROM to encrypt and what else i wuld need to do?
Thanks in advance to whoever takes the time to respond

PriPhaze said:
The question probably sounds stupid but after almost a year of just forgetting about using root or unlocking bootlader i forgot many things.
I remember i used to have a mi 9 with encryption on and everytime i open twrp you will need to decrypt the data.
Now with the MI 9T Pro i had to format data in order to boot into Evolution X ROM that of course left me with a decrypted phone and i dont really like it in case my phone gets stole or something.
Do you guys know if i can use the option inside teh ROM to encrypt and what else i wuld need to do?
Thanks in advance to whoever takes the time to respond
Click to expand...
Click to collapse
If all you did was format data, then encryption is still enabled. As soon as you setup lock-screen security, i.e. PIN, password, pattern, etc., for the first time your phone will automatically be encrypted.

Robbo.5000 said:
If all you did was format data, then encryption is still enabled. As soon as you setup lock-screen security, i.e. PIN, password, pattern, etc., for the first time your phone will automatically be encrypted.
Click to expand...
Click to collapse
No I couldn't boot until I flashed the DM verity.
So the encryption is now gone, but do you know if I can encrypt and then flash DM verity again with the force encryption on?.

PriPhaze said:
No I couldn't boot until I flashed the DM verity.
So the encryption is now gone, but do you know if I can encrypt and then glad DM verity again with the force encryption on?.
Click to expand...
Click to collapse
Ordinarily you shouldn't need to flash dm-verity. And as far as I'm aware, there is still no need to.
Normally it's just a case of formatting data to temporarily remove encryption, if flashing over MIUI.
As to your specific question, I couldn't say, as I've never needed to flash a dm-verity, disable force encrypt, or vbmeta file/script.
Personally, I would flash the latest fastboot MIUI ROM for the phone, then reinstall EvoX.
Before installing the ROM, in TWRP do the factory reset and then format data (There is no need to wipe anything else). Then reboot into TWRP to ensure the newly formatted data partition is properly mounted and flash as normal.
This has worked for me every time.

Yeah, some roms aren't booting without dfe.
to remove decrypt you can just wipe vendor and flash it again. you'll get encrypted. (however, some users confirm it puts them back into recovery, and they needed to reflash vendor+dfe for them.) Currently investigating if this is a RIN or RCN problem or for every device.
alternatively. If you are scared about having your device stolen. May I suggest you stay decrypted. Use ofox. and under ofox settings add a recovery password?
In the event you get stolen, they won't be able to access your recovery.
also, I'm looking for someone to test if wiping the data partition and not flashing dfe (after a rom has booted for the first time) and rebooting causes encyrption. (as you desired.) If you're willing to test. Try the above 3 methods?

Sandeeep Kiran said:
Yeah, some roms aren't booting without dfe.
to remove decrypt you can just wipe vendor and flash it again. you'll get encrypted. (however, some users confirm it puts them back into recovery, and they needed to reflash vendor+dfe for them.) Currently investigating if this is a RIN or RCN problem or for every device.
alternatively. If you are scared about having your device stolen. May I suggest you stay decrypted. Use ofox. and under ofox settings add a recovery password?
In the event you get stolen, they won't be able to access your recovery.
also, I'm looking for someone to test if wiping the data partition and not flashing dfe (after a rom has booted for the first time) and rebooting causes encyrption. (as you desired.) If you're willing to test. Try the above 3 methods?
Click to expand...
Click to collapse
BS. There is zero 'need' to flash dfe scripts. People are not formatting data when they need to, then when they cannot boot into a newly flashed ROM, they search and find solutions telling them to format data and flash dfe scripts. The thing is, people do not realise that it is the formatting data that fixes the problem, and they believe it is the dfe patch that is the fix. In all these cases formatting data alone would have been enough to fix the problem.
Also Orange Fox is only preferential if you stay with MIUI, as it's extra features are all about working with MIUI. If you are going with an AOSP ROM, stick with mauronofrio's latest TWRP, it is by far the best recovery for this phone.
As far as your 'test' is concerned, twice I have had bootloops after flashing a ROM, that have been fixed by formatting data alone.
The first time was when I first flashed an AOSP based ROM over MIUI before knowing that formatting data was required in this scenario. The second time was flashing AOSiP over LOS, when I still thought that going from one AOSP ROM to another never needed to format data when flashing.

Robbo.5000 said:
BS. There is zero 'need' to flash dfe scripts. People are not formatting data when they need to, then when they cannot boot into a newly flashed ROM, they search and find solutions telling them to format data and flash dfe scripts. The thing is, people do not realise that it is the formatting data that fixes the problem, and they believe it is the dfe patch that is the fix. In all these cases formatting data alone would have been enough to fix the problem.
Also Orange Fox is only preferential if you stay with MIUI, as it's extra features are all about working with MIUI. If you are going with an AOSP ROM, stick with mauronofrio's latest TWRP, it is by far the best recovery for this phone.
As far as your 'test' is concerned, twice I have had bootloops after flashing a ROM, that have been fixed by formatting data alone.
The first time was when I first flashed an AOSP based ROM over MIUI before knowing that formatting data was required in this scenario. The second time was flashing AOSiP over LOS, when I still thought that going from one AOSP ROM to another never needed to format data when flashing.
Click to expand...
Click to collapse
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.

Sandeeep Kiran said:
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.
Click to expand...
Click to collapse
Numerous cases? Who's we? What roms on what devices need dfe then? Only seen 2 roms ask for dfe, everything else it's as easy as 'going to and from miui, format data and reboot recovery' works every single time.

Sandeeep Kiran said:
We've had numerous cases for specific devices not booting without dfe despite formatting for some roms. I believe they are aosp roms that face this. Some when using oss, I vaguely remember. or when moving from LOS fod to mi9 fod or which flashing a different kernel.
(Do note. There are over 50+ roms for our device. 6 variants of the phone. 7 vendors (and separate modified vendors). 2 kinds of fod implementations. and about 95% of the cases arent asked on xda. 25% of the roms aren't posted either. None of the experimental builds are provided on xda.
There are tons of combos users use.)
I have not seen you on telegram. Only on xda. Who are you btw?
twrp is great. Ofox has a better ui and more features. Also, mauronofrio doesn't own a k20p btw. Just FYI. But he has the experience to still update twrp.
updated twrp is still not official, and gives error 7 for some raphaelin users who haven't updated updater-script.
recoveries are subjective. I mean, we have like 6 different recoveries now so.
Click to expand...
Click to collapse
Try this next time you see somebody saying they have tried may things and always get bootloops when trying to flash an AOSP ROM and you want to advise them to flash dfe.
Instead tell them to flash the latest MIUI fastboot ROM for their device, then install TWRP, in TWRP do a factory reset followed by format data, then reboot into TWRP and flash the ROM.
I bet they will come back and tell you it worked.
Again there should be zero need to flash dfe scripts.
If there are any AOSP ROMs out there that genuinely won't boot without flashing dfe (and here I'm talking about all users of such ROM), then the dev had done something stupid and everyone should seriously avoid the ROM.
At least half of the 50+ ROMs are no longer actively maintained.
The vast majority of Orange Fox extra features are specific to MIUI and so are redundant for AOSP ROMs. Mauronifrio's latest TWRP is the most stable for this phone, so if you're going with AOSP ROMs then the extra stability makes most sense.
I've been aware that mauronifrio does not own this phone ever since his initial build. I was also aware back then that he is also an official TWRP maintainer for other devices and so would mostly likely become the maintainer of the official version for this phone, which has now happened. If you go to the official TWRP site and download for this phone, it is by mauronifrio. You can also download the official version from the OP of his TWRP thread.
I would suggest that in most cases, people getting error 7 issues are not on the latest mauronofrio TWRP build.
Are you aware that all these different recoveries are just TWRP with a fancy dress. This is the great thing about TWRP. It was designed to be extensible, to allow others to build on it, in terms of functionality and design. So really there is only TWRP, just many different flavours.

Need help in flashing cutom roms

I got my device yesterday and today i have been trying to flash legion os 2.11 but i always keep getting error 7 even tried by installing global rom through mi flash tool but still got error 7 from twrp and oxfox both.
Can someone just guide me clearly on flashing roms on this k20 pro.
Currently i using global miui 11 11.0.4.0 rom but want to try other custom roms as well..

Ezio553 said:
I got my device yesterday and today i have been trying to flash legion os 2.11 but i always keep getting error 7 even tried by installing global rom through mi flash tool but still got error 7 from twrp and oxfox both.
Can someone just guide me clearly on flashing roms on this k20 pro.
Currently i using global miui 11 11.0.4.0 rom but want to try other custom roms as well..
Click to expand...
Click to collapse
Try the latest TWRP from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
If you still get the same problem, report back in this thread.

Robbo.5000 said:
Try the latest TWRP from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
If you still get the same problem, report back in this thread.
Click to expand...
Click to collapse
yeah finally the twrp 3.4 unofficial worked fine from global miui 11 rom i wiped everything and flashed indian vendor-firmware file and then flashed rom with fcrypt zip file nd worked fine...
Thanks for suggesting this file i was using youtube videos as guide and everyone was using oxfox or older twrp..

Ezio553 said:
yeah finally the twrp 3.4 unofficial worked fine from global miui 11 rom i wiped everything and flashed indian vendor-firmware file and then flashed rom with fcrypt zip file nd worked fine...
Thanks for suggesting this file i was using youtube videos as guide and everyone was using oxfox or older twrp..
Click to expand...
Click to collapse
I've got a bit more time to reply now.
OFox is really designed to be used with MIUI. The majority of it's extra features are specific to running MIUI. I would only recommend it if you decide to stick with MIUI in the long run.
The TWRP I pointed to is from the dev who maintains the official TWRP for our device. The unofficial version you've installed is identical to the official version, but with the TWRP app removed. If you intend to stick with custom ROMs, I recommend you stick with TWRP from mauronofrio.
If you prefer to have your phone encrypted, then there was no need to flash fcrypt/DFE. There are a small number of users that continue to insist that we need to disable encryption, but it is not needed.
Having the phone unencrypted does make life a little easier when flashing, but if you prefer the security and want to know about living with an encrypted phone, reply back and I'll give you more details.

Robbo.5000 said:
I've got a bit more time to reply now.
OFox is really designed to be used with MIUI. The majority of it's extra features are specific to running MIUI. I would only recommend it if you decide to stick with MIUI in the long run.
The TWRP I pointed to is from the dev who maintains the official TWRP for our device. The unofficial version you've installed is identical to the official version, but with the TWRP app removed. If you intend to stick with custom ROMs, I recommend you stick with TWRP from mauronofrio.
If you prefer to have your phone encrypted, then there was no need to flash fcrypt/DFE. There are a small number of users that continue to insist that we need to disable encryption, but it is not needed.
Having the phone unencrypted does make life a little easier when flashing, but if you prefer the security and want to know about living with an encrypted phone, reply back and I'll give you more details.
Click to expand...
Click to collapse
I tried Legion Os which is Aosp based and it installed fine but then i tried Masik X 16 which again said this isn't for your device so had to make changes in updater script then it flashed fine.
Also i would like to know about decryption of storage and would it cause any issues in flashing roms again nd again..

Ezio553 said:
I tried Legion Os which is Aosp based and it installed fine but then i tried Masik X 16 which again said this isn't for your device so had to make changes in updater script then it flashed fine.
Also i would like to know about decryption of storage and would it cause any issues in flashing roms again nd again..
Click to expand...
Click to collapse
If you want to be permanently decrypted, then you will not have any problems flashing ROMs. However, whenever you need to update the vendor and firmware, you will also need to flash the DFE script again.
If you want to be encrypted, then the best thing to do, every time you flash, is to temporarily remove encryption by removing all lockscreen security just before flashing, then once you've finished, restore encryption by adding back lockscreen security. However, if you restore MIUI, then choose to go to another custom ROM, you will need to format the data partition when flashing over MIUI, even if you've removed lockscreen security first.

Robbo.5000 said:
If you want to be permanently decrypted, then you will not have any problems flashing ROMs. However, whenever you need to update the vendor and firmware, you will also need to flash the DFE script again.
If you want to be encrypted, then the best thing to do, every time you flash, is to temporarily remove encryption by removing all lockscreen security just before flashing, then once you've finished, restore encryption by adding back lockscreen security. However, if you restore MIUI, then choose to go to another custom ROM, you will need to format the data partition when flashing over MIUI, even if you've removed lockscreen security first.
Click to expand...
Click to collapse
Ok that means going from miui to aosp & vice versa - format data needed.
So this should similarly apply to all Miui based roms like xiaomi.eu or masik x or it is just for stock miui.

Ezio553 said:
Ok that means going from miui to aosp & vice versa - format data needed.
So this should similarly apply to all Miui based roms like xiaomi.eu or masik x or it is just for stock miui.
Click to expand...
Click to collapse
As far as I know, you only need to format data when flashing over official MIUI. I don't know the details, but it is my understanding that encryption on MIUI does not follow standard practice, which is why it it's necessary to format data when flashing over MIUI. I don't believe this issue exists with MIUI based custom ROMs, or when reverting back to MIUI.
Though, there may be occasions, when flashing from one AOSP ROM to another, and the phone is encrypted, when you may get a bootloop. In this case booting to TWRP and formatting data, will fix the problem. This is why I earlier recommended temporarily removing lockscreen security, if you choose to have an encrypted phone, even though this is a rare occurrence.

Robbo.5000 said:
As far as I know, you only need to format data when flashing over official MIUI. I don't know the details, but it is my understanding that encryption on MIUI does not follow standard practice, which is why it it's necessary to format data when flashing over MIUI. I don't believe this issue exists with MIUI based custom ROMs, or when reverting back to MIUI.
Though, there may be occasions, when flashing from one AOSP ROM to another, and the phone is encrypted, when you may get a bootloop. In this case booting to TWRP and formatting data, will fix the problem. This is why I earlier recommended temporarily removing lockscreen security, if you choose to have an encrypted phone, even though this is a rare occurrence.
Click to expand...
Click to collapse
Thanks for the info.
I tried custom miui rom and well flashing dfe worked fine so i think its just for official miui.

Question I have ne2217. Help root and Global. Please!!!!

These threads have to many things going on, and now I am thoroughly confused. I just want to go to global from stock T-Mobile. I have downloaded so many things and I don't know what to use or not use. I have network unlocked and my bootloader is unlocked. I can enter fastboot and fastbootd.

Loustsoul said:
These threads have to many things going on, and now I am thoroughly confused. I just want to go to global from stock T-Mobile. I have downloaded so many things and I don't know what to use or not use. I have network unlocked and my bootloader is unlocked. I can enter fastboot and fastbootd.
Click to expand...
Click to collapse
There is no way to do it as of now. No one bothered making a conversion from T-Mobile to global with the 10 as there is no reliable MSM tool in case something were to go wrong in the conversion process. The most you can do on the T-Mobile version is unlock and root right now. I personally would love to be on global instead of T-Mobile firmware, but I doubt it will happen with the 10 Pro (although there is work being done on getting a useable MSM tool currently, so who knows).

jeffsga88 said:
There is no way to do it as of now. No one bothered making a conversion from T-Mobile to global with the 10 as there is no reliable MSM tool in case something were to go wrong in the conversion process. The most you can do on the T-Mobile version is unlock and root right now. I personally would love to be on global instead of T-Mobile firmware, but I doubt it will happen with the 10 Pro (although there is work being done on getting a useable MSM tool currently, so who knows).
Click to expand...
Click to collapse
All that'd take would be extracting your boot.img and flashing? Any issues with magisk?

Grin59 said:
All that'd take would be extracting your boot.img and flashing? Any issues with magisk?
Click to expand...
Click to collapse
For root? Just use the global patched boot.img and boot into OS, go to Magisk and perform a direct install. No issues at all with root on T-Mobile firmware. I've been rooted ever since they allowed us to unlock the bootloader and get our tokens.

Removed

EtherealRemnant said:
Really all you should need to do to convert to global is unlock the bootloader, take the NA downgrade package, and flash it with Fastboot Enhance. Make sure you go to the partitions screen and search for cow and delete every one of them so there is room for the image and if you get any other errors, don't continue. Once the flash is successful (the bar will seem to stop, just let it sit for a bit and it will continue), choose English on the phone screen and go through the menus to find where to wipe the phone and then reboot.
There is a risk of a brick if something goes wrong so without the MSM Tool, this is at your own risk, but Fastboot Enhance doesn't tend to brick phones like fastboot scripts do as long as you stop if it gives you an error.
Here is the NA downgrade package.
https://oxygenos.oneplus.net/2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001.zip
Click to expand...
Click to collapse
Yeah, technically should work. Unfortunately the risk is too high without having the MSM in case something goes wrong. Especially if it's your daily phone, like it is mine. But if anyone wants to give it a go, let us know how it goes, just know it could brick your phone and there's no current way to restore it without sending it to OnePlus or paying a scam artist to restore it.

Removed

Can I get my boot.img off of my phone or do I need to download it? Also the 10 pro is not listed in the software on the oneplus website. Where can I get the official stuff I need? Im happy with just root for now, I just want to use Magisk and do the updates......

EtherealRemnant said:
Fastboot Enhance really shouldn't brick. It's flashing the official downgrade package so unless OnePlus changed the hardware between the two significantly (which seems unlikely both because they haven't before other than minor changes like removing dual SIM and adding mmWave to the 9 Pro as well as the added cost of doing so), it should work fine. I made a tutorial for the OnePlus 9 using Fastboot Enhance to convert regions and nobody has reported a brick yet and this is after seeing 30+ bricks from people using fastboot scripts that prompted me to make the guide. Bricks with FBE happen if people ignore warnings about cow partitions or missing partitions and flash anyway. Like it doesn't even reboot the device after the flash is done so if the flash gets cut off in the middle, you just would need to flash the zip again before rebooting. Since all the flashing takes place in fastbootd from the start, it's possible to recover unlike regular flashing where it starts in fastboot and finishes in fastbootd so you're hosed if something goes wrong and you can't get back to fastboot.
I get it though, I wouldn't want to risk my device either. And I made sure to point out the brick risk, even if it's small, because I would never want to take that choice away from someone.
Click to expand...
Click to collapse
Im willing to try but I am too unsure of what to use as far as the correct boot and rom.... You seem to have way more knowledge than I and I would greatly appreciate your help.

Removed

EtherealRemnant said:
Fastboot Enhance really shouldn't brick. It's flashing the official downgrade package so unless OnePlus changed the hardware between the two significantly (which seems unlikely both because they haven't before other than minor changes like removing dual SIM and adding mmWave to the 9 Pro as well as the added cost of doing so), it should work fine. I made a tutorial for the OnePlus 9 using Fastboot Enhance to convert regions and nobody has reported a brick yet and this is after seeing 30+ bricks from people using fastboot scripts that prompted me to make the guide. Bricks with FBE happen if people ignore warnings about cow partitions or missing partitions and flash anyway. Like it doesn't even reboot the device after the flash is done so if the flash gets cut off in the middle, you just would need to flash the zip again before rebooting. Since all the flashing takes place in fastbootd from the start, it's possible to recover unlike regular flashing where it starts in fastboot and finishes in fastbootd so you're hosed if something goes wrong and you can't get back to fastboot.
I get it though, I wouldn't want to risk my device either. And I made sure to point out the brick risk, even if it's small, because I would never want to take that choice away from someone.
Click to expand...
Click to collapse
The only downside I could see then it's that we don't even have the full T-Mobile firmware to flash back to in case it starts to flash global but then failed. I'm tempted to take the plunge and try (would be nice to be on Android 13 now instead of waiting months for T-Mobile to get the update) but just don't want to end up bricking with no way to recover. Also, in the past I know people were using the MSM to convert to global or EU, does using the global downgrade script alone work for converting? I might take a look at your guide for the 9 series and try with the 10 pro. I guess I can always send it in if it does brick, still have my 9 pro I can use in case something goes wrong.

Removed

EtherealRemnant said:
It is a legitimate concern that you can't get back to T-Mobile firmware if something goes wrong and that is definitely something to think about.
I can tell you that the downgrade package is as close as you can get to the MSM Tool in terms of a restore without an MSM. I have used the downgrade packages to convert between regions on my 9 and never had any issues except for when I used the India MSM Tool for the 9 Pro on my 9 and kept losing touchscreen in OOS12. That was only fixed with an MSM Tool modded to get me back on regular global 9 firmware.
Click to expand...
Click to collapse
Well I'm taking the plunge so I'll update after if it's successful or not. Was able to delete all the COW partitions and start the flash no issue, so just have to wait for it to finish.

Removed

I will say this is my 2nd 10 pro because I did this exact method being described and it flashed rebooted all that but when trying to open any app I was greeted with a message that said.. "this app has been disabled due to security".

tman23 said:
I will say this is my 2nd 10 pro because I did this exact method being described and it flashed rebooted all that but when trying to open any app I was greeted with a message that said.. "this app has been disabled due to security".
Click to expand...
Click to collapse
Yeah, don't think it's going to work. Can't fully get out of the setup screen (or if you do it just stays at black screen only able to pull down quick settings and not enter options or anything). Wiped after flashing and won't work. I guess I could try using Fastboot Enhance to flash some of the global update zips and see if that does anything.

From what I've seen and read, switching regions on this phone is quite easy. You just need to use the full downgrade zip of that region and flash it basically. No messing around with FBE. NE2210/3/5/7 all share the same hardware, the full downgrade zips are actually interchangeable from what I've read/seen. There's only been one full zip for NE2217 released, IIRC, so the process to go back would involve a lot of upgrading incrementally. EDIT: I was wrong. There is no true full T-Mobile NE2217 ZiP available.. really sad.
But to go to/from NE2213 to/from NE2215, just take the downgrade zip, with a fully unlocked bootloader, and local update it.
Someone can correct if I'm wrong, but this seems to be the method most people have been using with success. That being said, as said above, root is very easily achievable by just BOOTing a patched global boot.img if you just want to root and maintain your original software.

Prant said:
From what I've seen and read, switching regions on this phone is quite easy. You just need to use the full downgrade zip of that region and flash it basically. No messing around with FBE. NE2210/3/5/7 all share the same hardware, the full downgrade zips are actually interchangeable from what I've read/seen. There's only been one full zip for NE2217 released, IIRC, so the process to go back would involve a lot of upgrading incrementally. But to go to/from NE2213 to/from NE2215, just take the downgrade zip, with a fully unlocked bootloader, and local update it.
Someone can correct if I'm wrong, but this seems to be the method most people have been using with success.
Click to expand...
Click to collapse
I haven't really heard of anyone converting the 10 due to lack of MSM. Also, haven't seen any full zips for the 2217 (T-Mobile version), so if you have a link to it that would be very useful. Also on 2217, you can't flash from in system as it's disabled in firmware (unless the separate apk works).

Stalk the forums enough, I think I've read every post here since I got the device back in March. There's a handful of people here successfully converted regions without any extra work. I believe there are actually 2 now for 2217. Here and here.
EDIT: As mentioned later in the thread even these are not full images for NE2217.

Prant said:
Stalk the forums enough, I think I've read every post here since I got the device back in March. There's a handful of people here successfully converted regions without any extra work. I believe there are actually 2 now for 2217. Here and here.
Click to expand...
Click to collapse
Thank you, not sure how I missed those. If my attempt to restore the device doesn't work I'll try restoring it by flashing T-Mobile firmware again.