Related
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T and regular OP7TPRO here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus 7T Pro 5G McLaren bought from T-Mobile.
They can also be used to rollback your phone to a previous release of OOS if for some reason you want to go back to an older firmware
It will only work with 5G T-Mobile variant HD1925
You can download the following versions:
ANDROID 10:
10.0.13 HD61CB
10.0.16 HD61CB
10.0.19 HD61CB
10.0.27 HD61CB
10.0.34 HD61CB
10.0.35 HD61CB
10.0.36 HD61CB
10.0.39 HD61CB
10.0.40 HD61CB
10.0.41 HD61CB
10.0.42 HD61CB
Mirror for first and last MSMs: https://onepluscommunityserver.com/
ANDROID 11:
11.0.1.5 HD61CB
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
Specific to 10.0.27 and up
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Click on Target button and select T-MO if it hasn't been automatically.
Power your device off.
Maintain volume up and volume down keys to get into Qualcomm EDL mode.
Plug your device to your computer using stock OnePlus cable.
Click on Enum to be sure your device is detected and press Start.
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Will this fix OTAs I couldn't receive after unlocking bootloader?
Yes. Mind it will however wipe all of your internal storage and relock bootloader automatically (but you shouldn't have to reapply for an unlock token if your bootloader was unlocked previously).
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected when I click on "Enum" button
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61, all credits to @Shadow12347 for finding it out.
Credits:
@omariscal1019 for getting 10.0.27 version from OnePlus
@a63548 for getting 10.0.19 version from OnePlus
An anonymous user for unblocking situation with OnePlus CS (they kept sending package meant for 7T T-Mobile)
@jhofseth for decryption of 10.0.19 tool
@xian1243 and @omariscal1019 for testing 10.0.13 version, @twinnfamous for testing 10.0.13 and 10.0.16 versions, @ntzrmtthihu777 for testing 10.0.13 , 10.0.16 and 10.0.19 versions, @DanDroidOS for testing 10.0.19 version, and @me2151 for testing 11.0.1.5 version.
@Titokhan for being a friend and providing inspiration in writing
@headsh0t95 for being a friend and suggesting me to request an access to upload files on AndroidFileHost now one year ago for my previous threads
@AndroidFileHost for the hosting
OnePlus for the device and OS
Related: [HD1925] [OP7TPROTMO] reserve.img dumps OTA fixer from @ntzrmtthihu777 for folks that want to get OTAs if they unlock their phone after using MSM tool
Woooooo!!! Let's hope it's the real deal. Downloading now so I can root in a bit
It's real and was tested extensively. We also used them to complete our reserve.img collection.
Nice work! I refuse to go any further than bootloader unlocking until I had a tested MSM recovery. Can't tell you how many times those saved my butt with previous 1+ phones.
I apologise in advance, but I do not see a link for the msm tool to flash zips in this post ? Can someone please link a copy of the correct msm tool so we can download it, please and thank you if there is a adb command that I'd have to run instead of msm tool please help me by listing a small guide of how to do it thanks
Excuse my lack of knowledge on the subject. Is this what we've been waiting for? I'm guessing no or very little experimenting was being done because nobody wanted to destroy their phone. But if I understanding correctly this will work like the one for the 6T only difference is we can't flash a global firmware (for the moment) if you royally f**k up this will save you. With this tool it should make experimenting with the device a lot less of an issue?
Justingaribay7 said:
I apologise in advance, but I do not see a link for the msm tool to flash zips in this post ? Can someone please link a copy of the correct msm tool so we can download it, please and thank you if there is a adb command that I'd have to run instead of msm tool please help me by listing a small guide of how to do it thanks
Click to expand...
Click to collapse
There's a button that has them all listed. There's three versions.
Joe199799 said:
Excuse my lack of knowledge on the subject. Is this what we've been waiting for? I'm guessing no or very little experimenting was being done because nobody wanted to destroy their phone. But if I understanding correctly this will work like the one for the 6T only difference is we can't flash a global firmware (for the moment) if you royally f**k up this will save you. With this tool it should make experimenting with the device a lot less of an issue?
Click to expand...
Click to collapse
More or less, but there simply is no global firmware for us to
convert to for this device (they could create one, I suppose).
This tool will fix just about any sort of brick we may encounter
during normal experimentation.
ntzrmtthihu777 said:
There's a button that has them all listed. There's three versions.
More or less, but there simply is no global firmware for us to
convert to for this device (they could create one, I suppose).
This tool will fix just about any sort of brick we may encounter
during normal experimentation.
Click to expand...
Click to collapse
I guessing there's a strong possibility of a global conversion hindering 5G?
I'm just glad there's a tool available to people that want to modify their phones and don't end up with a 900$ paperweight in the event something goes wrong.
Damn, I can't believe I didn't even think about unzipping the whole file lol figured it was just the phone firmware on those links , because there was only software versions listed haha thanks for your help guys! figured it out, download whatever version you want to flash, unzip file accordingly, all the proper files you'll need will be in the extracted folder install directions above, thanks again!!!
You sir are a lifesaver! I was having too many issues with my phone after some of the tweaks, and was stuck on the .16 software version. Now I'm updated to .19 and ready to break the phone again!
One plus 7T 5G Mclaren pro T-Mobile
OMG, I just used this tool and it worked. I can't believe it. Thank you so much. I thought my device was toasted.
Any chance of updating the post to include the latest update 10.0.25?
adit07 said:
Any chance of updating the post to include the latest update 10.0.25?
Click to expand...
Click to collapse
Might happen, might not.
If it doesn't happen this however won't be an issue as you can rollback anyway by using.
Mind that I don't make these tools so don't have any control on how they could be updated
What if you connect your phone and it does not even show up as the bulk driver in device manager. I have literally bricked it to the point that only edl mode shows up. Can anyone please show me the light?
djohnson1618 said:
What if you connect your phone and it does not even show up as the bulk driver in device manager. I have literally bricked it to the point that only edl mode shows up. Can anyone please show me the light?
Click to expand...
Click to collapse
While booting up the phone hold I believe volume up and plug it in while doing that it should just remain on a black screen after that open msmtool and see if it's connected if it is then do what you would normally do for msmtool. It took me a couple of tries to get it to recognize with this phone compared to my 6T
Lost
Does anyone know what it should say once I press Enum
djohnson1618 said:
Does anyone know what it should say once I press Enum
Click to expand...
Click to collapse
Read the OP carefully.
So My One Plus One 7t Pro Mclaren edition (TMO) is bricked beyond belief. It only reboots into Fastboot mode. From CMD when ADB devices command is typed in it says no devices found. When I look in device manager when connected it says Android Bootloader Interface it does not show any of the drivers to update. I tried using MSM. My phone does not make a connection. Can anyone offer any assistance to help me get this phone back and working? Or am I just stuck with an expensive paperweight.
djohnson1618 said:
So My One Plus One 7t Pro Mclaren edition (TMO) is bricked beyond belief. It only reboots into Fastboot mode. From CMD when ADB devices command is typed in it says no devices found. When I look in device manager when connected it says Android Bootloader Interface it does not show any of the drivers to update. I tried using MSM. My phone does not make a connection. Can anyone offer any assistance to help me get this phone back and working? Or am I just stuck with an expensive paperweight.
Click to expand...
Click to collapse
As said in the OP, you need to turn your device off and enter in Qualcomm EDL mode.
Maintain power button until your device screen goes off, wait 20 seconds, maintain volume up and down keys, plug your device to your computer using OnePlus original cable and use MSM tool.
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T and Nord N10 5G here is the EDL package (also known as MSM tool or unbrick tool) that can revive a bricked OnePlus Nord N200.
You should be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
DE17AA tools (global firmware):
ANDROID 11:
OOS 11.0.3
Mirror: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@drfsupercenter for testing 11.0.3 version on his device
OnePlus for the device and OS
I can confirm this works for the "unlocked" version that I bought at Best Buy. Thanks for posting!
Here is a question
Can I convert T-Mobile version to global this way?
mingkee said:
Here is a question
Can I convert T-Mobile version to global this way?
Click to expand...
Click to collapse
No, you can't convert T-Mobile variant to unlocked one with this tool.
Some_Random_Username said:
No, you can't convert T-Mobile variant to unlocked one with this tool.
Click to expand...
Click to collapse
The scenario is like 8T.
I remember somebody alter the project code to cross flash.
I have to find out
Wait... We finally got MSMTools for the Unlocked variant? When'd/How'd this happen?
THANK YOU!!!! My paperweight is a phone again!
edale1 said:
Wait... We finally got MSMTools for the Unlocked variant? When'd/How'd this happen?
Click to expand...
Click to collapse
I bricked my phone messing with it after the recent update they pushed out to official phones which broke 5g. Maybe more people than I did, I was pretty happy until then.
edale1 said:
Wait... We finally got MSMTools for the Unlocked variant? When'd/How'd this happen?
Click to expand...
Click to collapse
I don't know how he got it, but it does work.
mingkee said:
Here is a question
Can I convert T-Mobile version to global this way?
Click to expand...
Click to collapse
I'd imagine it would be the same as when I tried to flash the T-Mobile MSMTool to my unlocked phone. It just said wrong model and wouldn't continue.
It seems like oneplus finally released the msmtool for global/unlocked version.
Follow this guide to flash global/international unlocked firmware to metro/tmo version with locked bootloader (convert metro/tmo version to an unlocked international/global version):
Flash international ROM to Tmobile/Metro w/ locked bootloader
MAJOR UPDATE: Managed to flash Global stock rom to the MetroPCS variant Pros: Stock Oneplus and everything works Cons: OEM unlock is still greyed out Before you go any further: THERE IS NO ROOT FOR THIS DEVICE WITH A LOCKED BOOTLOADER (YET)...
forum.xda-developers.com
Basically, you need to change a few lines inside "settings.xml" about the project id so that it would not complain about non-matching project id/wrong model when cross flashing global rom to metro/tmo hardware.
After crossflashing global rom to metro/tmo verion of hardware, it can then take international ota so it will behave exactly like the unlocked version.
The only difference is about unlocking bootloader, and you will still need to go through the oneplus/T-Mobile portal to request the bootloader unlock bin to unlock the bootloader, while the true unlocked version doesn't need.
Some_Random_Username said:
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T and Nord N10 5G here is the EDL package (also known as MSM tool or unbrick tool) that can revive a bricked OnePlus Nord N200.
You should be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
DE17AA tools (global firmware):
ANDROID 11:
OOS 11.0.3
Mirror: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
@drfsupercenter for testing 11.0.3 version on his device
Votton for providing a server as an alternative mirror
OnePlus for the device and OS
Click to expand...
Click to collapse
great thanks lol
googlephoneFKLenAsh said:
It seems like oneplus finally released the msmtool for global/unlocked version.
Follow this guide to flash global/international unlocked firmware to metro/tmo version with locked bootloader (convert metro/tmo version to an unlocked international/global version):
Flash international ROM to Tmobile/Metro w/ locked bootloader
MAJOR UPDATE: Managed to flash Global stock rom to the MetroPCS variant Pros: Stock Oneplus and everything works Cons: OEM unlock is still greyed out Before you go any further: THERE IS NO ROOT FOR THIS DEVICE WITH A LOCKED BOOTLOADER (YET)...
forum.xda-developers.com
Basically, you need to change a few lines inside "settings.xml" about the project id so that it would not complain about non-matching project id/wrong model when cross flashing global rom to metro/tmo hardware.
After crossflashing global rom to metro/tmo verion of hardware, it can then take international ota so it will behave exactly like the unlocked version.
The only difference is about unlocking bootloader, and you will still need to go through the oneplus/T-Mobile portal to request the bootloader unlock bin to unlock the bootloader, while the true unlocked version doesn't need.
Click to expand...
Click to collapse
I changed everything related to project ID and everything in that post, but mine still says
{
"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"
}
justauserthatusesaphone said:
I changed everything related to project ID and everything in that post, but mine still says
View attachment 5652955
Click to expand...
Click to collapse
The project code should be for N200 not other models
mingkee said:
The project code should be for N200 not other models
Click to expand...
Click to collapse
That's what I put.
I even control+f'd it for anything that says "2083c" or "ID" and "project", yet it still somehow got that error.
justauserthatusesaphone said:
I changed everything related to project ID and everything in that post, but mine still says
View attachment 5652955
Click to expand...
Click to collapse
Open up settings.xml from the Global decrypted folder and change the following 5 values to match the settings.xml from Metro and hit save
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
googlephoneFKLenAsh said:
Open up settings.xml from the Global decrypted folder and change the following 5 values to match the settings.xml from Metro and hit save
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
Click to expand...
Click to collapse
ok i'll do that in a bit and i'll probably release it here.
googlephoneFKLenAsh said:
Open up settings.xml from the Global decrypted folder and change the following 5 values to match the settings.xml from Metro and hit save
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
Click to expand...
Click to collapse
well
okay i give up
justauserthatusesaphone said:
View attachment 5653443
well
okay i give up
Click to expand...
Click to collapse
You didn't follow the instructions correctly.
Re-read the instructions, especially the editing project id step.
The error message mentioned "image 2083c", which means there are lines from 2083c ops not replaced with values from 20818 ops yet.
You need to replace all those lines:
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
in the settings.xml from unlocked 2083c ops with the values in the settings.xml from metro/tmo 20818 ops. (better to use copy&paste to avoid typos).
Also you need to copy the modified unlocked/global ops to the msmtool folder of the metro/tmo version and replace the original metro/tmo ops.
I believe 2083c is the unlocked version and 20818 is the metro/tmo version.
googlephoneFKLenAsh said:
You didn't follow the instructions correctly.
Re-read the instructions, especially the editing project id step.
The error message mentioned "image 2083c", which means there are lines from 2083c ops not replaced with values from 20818 ops yet.
You need to replace all those lines:
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
in the settings.xml from unlocked 2083c ops with the values in the settings.xml from metro/tmo 20818 ops. (better to use copy&paste to avoid typos).
Also you need to copy the modified unlocked/global ops to the msmtool folder of the metro/tmo version and replace the original metro/tmo ops.
I believe 2083c is the unlocked version and 20818 is the metro/tmo version.
Click to expand...
Click to collapse
I can't tell what's wrong.
XML:
<BasicInfo Project="20818" TargetName="SM4350" Version="dre8t_10_O.05_210713" MemoryName="ufs" GrowLastPartToFillDisk="true" LogEnable="false" LogPositionIndex="-1" DelayStartTime="0" UseGPT="true" CheckImage="false" CheckHwVersion="false" NeedUsbDownload="true" BackupPart="false" BackupPartId="" ChipType="1" FactoryID="20818US" MinToolVersion="5.0.3" SupportHwID="false" SupportRfID="false" SupportPrjID="false" CheckRfVersion="false" CheckProjectVersion="false" SkipImgSHA256Check="true" ParamVersion="1" SkipParamProcess="false" ModelVerifyVersion="0" ModelVerifyPrjName="" SkipCheckHWVerByCustFlag="false" DefaultCleanFRP="true" FrpPartitionLabel="frp" CarrierID="0" AutoDetectDDR="false" DPPackingVer="0" ProjectSoftwareIDSupport="false" ATOBuild="false" SkipMultiImageIdentify="true" RandomPadding="anxKohPaJKUq2kVPIbXgD7RXNa96iUeGFZa1GzbYH6OIorf7RCneJCCgkJlSlN" ModelVerifyRandom="RG8sc2EUOj51TeCw" ModelVerifyHashToken="F9417334897C488DEA1DA5AC787906F743E85C17B47EB9669FFE96F11529D33C" Applicant="Unknown" Hostname="rd-build-77" BuildTime="1631716601" ApplicantIP="not sure if this is sensitive" />
Everything you listed is changed, the unlocked ops is also put into the tmobile msm
for example, here's the tmobile one
XML:
<BasicInfo Project="20818" TargetName="SM4350" Version="dre8t_10_O.05_210713" MemoryName="ufs" GrowLastPartToFillDisk="true" LogEnable="false" LogPositionIndex="-1" DelayStartTime="0" UseGPT="true" CheckImage="false" CheckHwVersion="false" NeedUsbDownload="true" BackupPart="false" BackupPartId="" ChipType="1" FactoryID="20818US" MinToolVersion="5.0.3" SupportHwID="false" SupportRfID="false" SupportPrjID="false" CheckRfVersion="false" CheckProjectVersion="false" SkipImgSHA256Check="true" ParamVersion="1" SkipParamProcess="false" ModelVerifyVersion="0" ModelVerifyPrjName="" SkipCheckHWVerByCustFlag="false" DefaultCleanFRP="true" FrpPartitionLabel="frp" CarrierID="1" CarrierNoneEnable="true" AutoDetectDDR="false" DPPackingVer="0" ProjectSoftwareIDSupport="false" ATOBuild="false" SkipMultiImageIdentify="true" RandomPadding="CQLTBL0oxs4BM2pdtK1y8Q1rvzgUtd033KWDfU1dM3mh3bKuwJs4jrtcqa6iB7lERIP4kOf5RRmS16MxPDz74tjvRq" ModelVerifyRandom="RG8sc2EUOj51TeCw" ModelVerifyHashToken="F9417334897C488DEA1DA5AC787906F743E85C17B47EB9669FFE96F11529D33C" Applicant="Unknown" Hostname="rd-build-74" BuildTime="1626183302" ApplicantIP="eeeeeeee" />
You are a godsend. Thank you so much, this is exactly what I needed!!
CHANGELOG:
Guide v1.0 - Warn that Lineage cannot be flashed on A12 firmware.
Guide v1.1 - Update guide for flashing Lineage after complete conversion and updates so phone is fully converted first.
There are THREE firmware versions for the N200.
DE2118 - Carrier infected phones for T-Mobile and MetroPCS in US.
DE2117 - Retail US OEM firmware that is 100% compatible with US carriers and fully supports 5G, 4G, 3G (gone), 2G, VoLTE, and VoWIFI.
This guide is intended to remove the carrier virusware that the carrier uses to wipe/spy on the user as well as branding bloat like the bootup/shutdown graphic/sound.
DE2117AA - International version of the phone. This has a different modem/firmware, supports 2 sim cards, and is NOT compatible with US N200 hardware.
WARNINGS:
1. Do NOT flash Intl. DE2117AA firmware or use msmtool for DE2117AA on any US phone or you will no longer make/receive voice or text calls until you flash back to US firmware with Fastboot Enhance!
2. You must NOT stop the guide after you flash DE2117 onto the first slot as the phone will NOT be fully converted until it takes the OTA update to Android 12 and one more to C_17.
If you go to the about screen before the Android 12 OTA update, you will still see DE2118.
3. A You should take ALL OTA updates to Android 12 C_17 and then follow the root guide for Dummies if you want to test drive the latest and very stable current OEM firmware.
B Flash back to DE2117 Android 11 final with my downgrade guide to go back to the final Android 11 DE2117 US before you install current N200 Lineage.
Lineage requires you to be on Android 11 or it will soft brick when you flash Lineage boot.img.
4. Finally, I have had enough people use my N200 guides that they are proven to work very well, but I take no responsibility if you abort the flashing process or skip parts of the guide and manage to boot loop/brick your phone!
However, I will work with you to get you going again. This phone cannot be fully bricked with the Qualcomm chipset and EDL recovery mode. You will create a full backup of your phone in the guide, so you can restore it 100% even if you walk away and your cat manages to fully wipe the entire firmware area of the phone with Fastboot Enhance.
PREREQUISITES: (see other guides)
1. You must have your boot loader unlocked.
2. Request and receive your unlock token from OP website to unlock boot loader.
(This takes exactly one week from requesting on Oneplus Website until OnePlus delivers the unlock token.)
If your phone is still sim subsidy locked and you cannot move the "OEM unlocking in dev options to on as it's greyed out, follow steps (20-24) to bypass this and turn on OEM unlocking so you can get unlocking code without being sim unlocked.
3. Install latest Android Platform Tools installed on PC. Currently v33.0.3
Old versions platform tools will cause fastboot commands to FAIL!!
4. Fastboot Enhance tool
Download and unzip folder into working directory.
This tool is Windows only and requires .net framework 4.5 (can be ran in VM with enough free ram for experienced linux users) This tool also needs a good amount of ram as someone with a old Windows 7 machine with very limited ram had the program hang when unpacking the firmware. They then switched to a newer machine resolved the issue.
5. Backup your phone data as this guide will wipe your phone in the process.
I recommend you put a MicroSD card in your N200 and select MicroSD card as backup location in Swift/APP Manager as all data on MicroSD will survive a phone wipe/reset.
A. The most simple backup tool is Swift Backup with a rooted phone to save all your app, data, phonebook, texts, and wifi passwords for easy restore after you are converted, upgraded and re-rooted.
B. For power users I highly recommend using App Manager to back up your apps.
The App Manager instructions are worth reading like a book as this tool is very complex and powerful.
This tool will backup APK source files/splits, internal/ext data/obb and media/cache, app permissions, battery savings,data usage, Magis khide status, SSAID, rules set up in App Manager. It will also import backups fromOAndBackup, Titanium and Swift (3.0-3.2) and keep multiple version backups of same app.
It's also an Interceptor, Manifest viewer, Scanner (API key from virus total), Enhanced Package installer with version upgrade/downgrade information and library add/remove info on install, Usage, Log viewer with colors/filters, App explore and much more.
-----------------------------------------------------------------------------------------
Begin GUIDE
-----------------------------------------------------------------------------------------
1. Place your phones unlock key into Platform Tools directory.
(You can download it again by logging into OnePlus site and going to this page.)
2. Download Tmobile/MetroPCS OnePlus MSMtool for V11.0.1.7 and unzip to working folder of your choice.
3A. Download FINAL Android V11 Update Image .
If installing Lineage,You MUST flash Lineage boot.ini from Android 11 or you WILL go into a soft boot loop from Android 12!
3B. If you are going to re-flash your phone that is already flashed to DE2117 and on A12 due to a bad update (in a soft boot loop) or installed other A12 rom and need to flash back, Download Full US OEM A12 C_16 Update Image and keep as .zip file and place in working folder instead.
(See Downgrade Guide if you are already running US OEM A12 and want to go back to A11 to install Lineage.)
4. Go to working folder you unzipped msmtool and open folder "dre8t_10_O.07_211014_repack"
5. A. Execute program as Administrator "MsmDownloadTool V4.0.exe" if your running Windows 10 or 11.
B. Execute program as administrator "MsmDownloadTool V4.0_Win7.exe" if your running Windows 7.
6. At login prompt, change user type to:
"User Type: Others" & Hit Next button.
7. At main page of MsmDownload Tool hit "F8"
A new window will pop-up that is called Firehose Readback:
(Ignore my crazy Windows theme colors - Yours will look different)
{
"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"
}
8. Locate Password box at bottom of pop-up and enter lowercase password: oneplus
9. Make sure the box is still active window and hit <cntrl-a> and every box in the list will then become checked.
10. hit OK to close box.
11. Click new "Read Back" button.
13. Place phone in special EDL recovery mode:
A. Since ADB is working, it is easier to simply open your Android Platform tools folder in Explorer and type cmd in location box to open dos prompt and type:
C:\platform-tools>adb reboot edl
B. You can turn phone off and then hold both volume buttons down and power on to force phone into EDL mode if phone is not working properly.
NOTE: When phone is in EDL mode the screen on the phone will be BLANK.
This is NORMAL.
14. As soon as the command is entered switch back to MSMtool window and watch it make a FULL backup of your phone including all firmware (slot a/b) and phone identifying information areas. When this is complete your phone will reboot.
15. Go to root of system drive (Default C:\) in explorer and sort files by date (Double Click on the Date Modified) and move all the new files just created ending in .bin, .img, .elf, and .mbn to a folder and name it to identify this exact phone if you have more than one N200 and store in a safe place like a USB flash drive. You can zip the folder first to save space.
See: Firehose backup files.txt attached for full list.
Do NOT share this backup with anyone online as they can clone your phones IMEI/SN with this PRIVATE backup data!
16. Re-run msmtool again. It will remember user type option: others. Click Next.
17. This time at main screen simply press start. and place phone in EDL mode as in step 13.
18. Watch the tool flash V11.0.1.7 firmware and most importantly the older fastbootd that is proven to perform the conversion firmware flash.
(Phone will reboot wiped/locked and in out of box condition.)
19. Do phone setup offline without entering wifi and as soon as you are out of setup turn off data to prevent phone from starting to download firmware update from OTA.
20. Goto Settings -> About Device -> Version -> build number and click until developer again.
21. Goto Settings -> System Settings -> Developer Options and turn on USB debugging and then exit settings.
22. Go back to dos box and send command to remove software that prevents OEM Unlock from being turned on:
C:\platform-tools>adb shell pm uninstall --user 0 com.qualcomm.qti.uim
23. On Phone: Go to Settings -> System Settings -> Developer Options
Turn ON "OEM Unlocking"
24. Go back to dos box and type:
C:\platform-tools>adb reboot fastboot
25. Send your unlock code to phone again.
(Assuming the file is called unlock_code.bin)
C:\platform-tools>fastboot flash cust-unlock unlock_code.bin
26. Unlock Bootloader:
C:\platform-tools>fastboot oem unlock
27. Follow on screen directions and phone will unlock bootloader, erase data and enter new phone setup again.
Do steps 19-21 again (developer/adb debugging on) and step 24 (Reboot to fastboot)
Now visually verify your phone is in Fastboot mode and unlocked.
28. Go to working folder in explorer and open folder "Fastboot_EnhanceV1.3.0" and execute "FastbootEnhance.exe"
29. On Fastboot Visualization tab, Double click on your device that will be shown.
30. Now you have two tabs, "Basic Properties" and Partitions.
31. Click on Partitions tab and scroll to bottom of the partitions list and verify that there are none that end in "_cow"
(They are creeated when you do OTA upgrades. They are left over and need to be deleted if present otherwise there may not be enough room to write new image.)
32. Highlight EVERY file ending in "_cow" and click the erase button.
They are always at the bottom of the list.
Repeat until there are NO files ending in "_cow"
33. Click the button bottom left corner called "Reboot to Fastbootd"
34. Your phone willl now reboot into special fastbootd mode.
35. Click English on phone to see this. Do NOT click any other options on phone.
36. Tick the box on right Show Logs to watch it's progress. A log box will pop up. Drag it over to the side to watch.
37. Tick the box Ignore Unknown Partitions
(fastbootd will NOT flash over newer modem firmware with older, if flashing older firmware and required for flash to still work)
38A. Click Flash Payload Bin box and select file "DE2117-A11-Final-OnePlusN200Oxygen_10.O.11_OTA_011_all_2203021426_downgrade_66cde69fe1e342db.zip" from working directory.
38B. For Android 12 USS OEM Reflash-Restore, Select file "(US_RETAIL_A12_C_16_FULL_ROM)DE2117_11.C.15_0150_202205192325.zip"
39. Click Flash Payload bin button.
It will unpack all the partitions from the .zip file first.
It will then delete old partitions and re-create partition with new required size and flash each .bin file of firmware one at a time automatically.
40. WAIT.....Watch the log output window and DO NOTHING until complete.
A. Fastboot Enhance will unpack all the partitions from the .zip file first.
B. It will then delete old partitions and re-create partition with new required size and flash each .bin file of firmware one at a time automatically.
41. When process is finished click "Reboot to recovery" button.
42. on phone, tap English.
43. on phone, tap "wipe data" and follow prompts to wipe and restart.
You will now boot up on US OEM DE2117 Android 11 Final.
WARNING: Do NOT stop the guide at this point, as your phone is not fully converted yet!
If you go to about info you will still see DE2118 and the boot area and other slot is still on carrier firmware! (Even if you are going to install Lineage, you must continue OTA upgrades to Android 12 C_17 and then downgrade to Android 11 afterwards)
44. Perform system setup with wifi and go to settings -> about device and perform system update and you will update to A12 (C_16) and proceed to second partial OTA update to latest OTA (C_17) before following the root guide for dummies
WELL DONE MY GOOD SIR!
Thanks for the thorough write-up for this dummy! So once this procedure is completed I can assume that everything that works for the DE2117 (like LineageOS) will be OK for a DE2118?
My fastboot enhance keeps stopping once i select the payload.bin to flash
I have all the correct files but it seems like windows keeps stopping the program from continuing further...
So say you run through this guide, everything goes correctly and you end up with a DE2117. Is it for all intents and purposes a DE2117 or would you still run the DE2118 MSM Tool should you run into a problem and need to reset?
Maatt_OG said:
My fastboot enhance keeps stopping once i select the payload.bin to flash
I have all the correct files but it seems like windows keeps stopping the program from continuing further...
Click to expand...
Click to collapse
Are you seeing anything in the log window?
What is the error message Windows is giving you, and how is it stopping the program?
It sounds like you have Windows issues.
Are you running this in a VM or under very low memory conditions?
You may want to refresh your Windows installation.
Link575 said:
So say you run through this guide, everything goes correctly and you end up with a DE2117. Is it for all intents and purposes a DE2117 or would you still run the DE2118 MSM Tool should you run into a problem and need to reset?
Click to expand...
Click to collapse
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone is for all practical reason a US OEM. Your IMEI is still in the T-mobile/MetroPCS range so the OP will not give you credits for registering a new OEM phone at Red Cable Club and will say that IMEI is invalid.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
scanman0 said:
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone s for alll practical reason a US OEM. Your IMEI is still in the Tmobile range so OP site login will not give you register credit for registering new phone at store.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
Click to expand...
Click to collapse
it says extracting files in the log but i have eeven waited and ignored the windows pop up error saying , Program has stopped working, we will let you know if theres a solution, but it doesnt proceed any further.
AND... DO NOT USE MSM TOOL AFTER CONVERTING. modem and core-nhlos and a few other partitions are a bit different along with the hardware versions and all and youll bootloop.
scanman0 said:
Are you seeing anything in the log window?
What is the error message Windows is giving you, and how is it stopping the program?
It sounds like you have Windows issues.
Are you running this in a VM or under very low memory conditions?
You may want to refresh your Windows installation.
Click to expand...
Click to collapse
as for memory, i am running pretty low tbh....
scanman0 said:
That is a very good question.
Once you have flashed DE2117 to one slot and then taken an OTA upgrade, then both slots are converted and your phone s for alll practical reason a US OEM. Your IMEI is still in the Tmobile range so OP site login will not give you register credit for registering new phone at store.
I tell people to take OTA updates so they are not half cross flashed as we have had one person try to use msmtool and bricked phone when in this half converted state.
msmtool re-locks the boot loader so it's not the first thing I would do. It's best to use fastboot enhance and re-flash from fastbootd again and wipe if you fail with a GSI or installing another rom.
Click to expand...
Click to collapse
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
scanman0 said:
13. Place phone in special EDL recovery mode:
Click to expand...
Click to collapse
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.
We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.
Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
katooom said:
Even funnier was that I never did find the backup files after the Download was complete.
Click to expand...
Click to collapse
And the only reasonable explanation for this is that among my many confused attempts to make things work this was the time that I did not actually do the backup, just pressed the start button. I would hate to think that I made such a ridiculous blunder but what else could it be. Oh my .....
Maatt_OG said:
as for memory, i am running pretty low tbh....
Click to expand...
Click to collapse
You need to have enough memory free for the program to unpack the .zip file in ram. If Windows is crashing the process with "program is not responding" then your pc (or is it a vm?) does not have enough memory.
Link575 said:
I see thanks for that. So one more follow up, I'm not even sure if you would know this but I installed Lineage 19 on my DE2118 and after that About phone states its a 2117. I'm assuming this is just because that's what this ROM was made for and it's not actually converting to a DE2117. I did MSM after Lineage and had no problems going back to stock DE2118.
Click to expand...
Click to collapse
Lineage has one build that is compatible with both versions and reports that either is DE2117.
katooom said:
This dummy had never seen EDL mode before and because my MSMDownload tool for Win7 seemed to require running as administrator the tool did not automatically connect so all I saw was a black screen in Step 14.
We shall not talk about how long nor how many different reboot combinations were required for me to understand that I needed to run the tool as administrator and that the black screen was normal. Really funny.
Even funnier was that I never did find the backup files after the Download was complete. Not on C:, not on D:, none found with the Explorer search function. Somehow I made them vanish even after your careful description.
Click to expand...
Click to collapse
I have updated the guide to reflect that you need to run as administrator on Windows 7 and to run the windows 7 .exe file.
I have only tested under Windows 10 and Windows 11 and the program demanded administrator mode to run.
The msmtool always dumps to the root of the working system boot drive that is usually C:
I made a screen shot of the F8 windows as you must select the boxes and place the password to place the tool in the backup mode.
I never said in the guide to look at the phone when in EDL mode as the screen is black.
I have updated the guide to inform people that are not familiar with EDL mode to expect that it is blank.
This is the reason I had people go to EDL mode with the pc with adb is the fact that it is a blank screen mode and people can be confused if the phone is in EDL or off.
I cannot tell by your condescending comments if you actually did the F8 procedure correctly to place msmtool in backup mode.
There is no indicator before it starts (other than the window closing without an error) and the tool will indicate as shown in the screenshot that it is "Reading back <Partition name>" as it reads the partitions from the phone.
If you simply press start as you implied you "tried" the tool will flash the phone to default factory state and NOT do a backup.
You do realize I wrote this guide to try to help people and cannot test every possible configuration as I don't have Windows 7 anymore.
People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
scanman0 said:
Lineage has one build that is compatible with both versions and reports that either is DE2117.
Click to expand...
Click to collapse
Got it, thanks.
scanman0 said:
People with your poor attitude is the reason there are fewer hand holding guides present on XDA.
Click to expand...
Click to collapse
Whoa, I have to apologize for making you think that I was in any way critical or dissatisfied! I was merely making fun of myself for messing up the process in spite of how well you explained it. I actually hoped that you would be amused by my errors and the silly reasons that I made them. It is deeply upsetting to me to have offended someone who puts so much effort into helping. I can only apologize again for expressing myself so poorly.
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
rcartaz09 said:
@scanman0 Dumb question probably, but after completing this, would it be possible to downgrade to Android 11 OEM?
Click to expand...
Click to collapse
Nothing dumb about this question!
I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware
And put warning to only install Lineage with Android 11 firmware.
I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
After completing this, would it be possible
scanman0 said:
Nothing dumb about this question!
I have updated the guide to INCLUDE converting to last Android 11 US OEM Firmware
And put warning to only install Lineage with Android 11 firmware.
I also posted a separate downgrade guide so people will not miss this fact if they already upgraded to Android 12 and want to install Lineage:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
Click to expand...
Click to collapse
You are awesome! Thank you!
Hello Fellows,
I've got a Redmi 9 Pro for Linux purposes, but the phone came with FRP triggered and of course, I couldn't get access to the sellers
account. I spare you the details, because I am sure, every one knows a story like that.
I checked xda and the web about guides for quite some time, and actually found a lot of them, but none of them worked. At the end I could combine
some of these guides to actually make it happened. I've created a little screen recording to show all the steps that worked for my device.
Yes you can actually install and open almost every apk even with a triggered FRP. Almost means, you can even enable the developer options, but
they don't show anything for that user.
Initial situation:
Xiaomi Redmi 9 Pro EEA (joyeuse)
Bootloader Locked
triggered FRP Lock
find my device - OFF
No MI-Account
Software Variant 1:
Firmware: MIUI V12.0.2.0.QJZEUXM Stable Official Update for Redmi Note 9 Pro EEA (joyeuse)
Android 10 - Miui 12
Android Security Patch Date: 2021-01-21
Software Variant 2:
Firmware: MIUI V12.5.8.0.RJZEUXM Stable Official Update for Redmi Note 9 Pro EEA (joyeuse)
Android 11 - Miui 12.5
Android Security Patch Date: 2022-03-01
FRP Bypass start conditions:
Wifi is connected
The basic idea and steps:
Get into System Settings via the Help & Feedback from Gmail to disable and stop certain apps.
Only for this is the wifi needed, if you type delete, the right help topic will show up
2x Android Setup
Carrier Dafault App
Google Play Services (must be disabled at the very last)
enable the Accessibility Suite to re-enable Google Play Services at the right moment
Continue the actually process to setup the phone, the procedure will stuck at "Just a sec..." "Checking for updates..."
now try to re-enable the Google Play Services, once this is done, the FRP Bypass will take place the next step
One important note, after enabling Google Play Services, its Storage and Cache must be deleted!
This is one of the main reasons why it didn't worked for me the first 100 times i tried.
It does go through though, but right at the moment the setup is finished, the FRP Lock gets triggered and
we are back at the beginning.
Enabling the Google Play Services can be annoying, because the screen is flashing/changing so fast, that the touch
will not be accepted right away. But there is plenty of time to try until it hits.
Finish the setup process until you see the home screen
Execute the factory reset over the settings menu and the FRP is gone for good
Optional, you can enable oem unlock before you factory reset the phone
With oem unlock enabled, the phone can't get FRP Lock on.
Spoiler: FRP Bypass and Reset Android 10 - Miui 12
Spoiler: FRP Bypass and Reset Android 11 - Miui 12.5
Regarding Bootloader Unlock, which es mandatory to install Linux (Ubuntu Touch) on this phone.
I couldn't found any free way to either unlock the bootloader without Mi-Account, or reboot the phone into EDL.
They are some Apps I tried so far:
Xiaomi Sideload Tool and ROM2box from Romprovider.com
But they need MIUI Recovery 5.0, and I only have MIUI Recovery 3.0
And don't want to upgrade, because Ubuntu Touch need Android 10
Does anybody have more information about that exploit these Sideload Apps are using?
I don't get how you can read data from and adb sideload connection, where you just can upload zip files
for updates
EDL from the famous Bjoern Kerler "bkerler" (MTK-Client)
For this tool the phone must be in EDL Mode, which I can't get into it
Does anybody know a way how to do that without Test Point? I tried so many ways, but none worked.
I even compiled fastboot and adb from AOSP, but the "old" ways like reboot-edl don't work.
My last hope is a USB-C V2 Cable/Dongle from Team Hydra.
Updates will follow...
[Update 1: 2023-04-25]
The FRP Bypass Procedure also works on Android 11 MIUI 12.5
[Update 2: 2023-04-25]
I've built the EDL Cable/Dongle, but it didn't work. I've bought the official
Hydra EDL Cable V2, exact same result, it also didn't work. Hydra refuses to give me a straight answer to this issue, even as a customer. The shop I've bought it
from, asked Hydra as well, with the feedback, this could be a SPD issue.
But still, they refuse to tell me, which SPD I need to get it working. At this
time I was on SPD 2021-01-21, and they published the EDL Cable Pinouts in Dec. 2022 [Latest Security]. So this was a very false promise from Hydra or rather mobilerdx, not sure who's to blame here, perhaps myself.
[Update 3: 2023-04-25]
I've wrote an ADB and Fastboot Sniffer for Windows. Which worked
pretty well, and I was able to get the ADB commands from the Xiaomi Sideload Tool. So the Exploit is basically, that you can perform ADB PULL and ADB PUSH while your in SIDELOAD Mode, that's it. And that it uses a built-in command to gather the partition structure while you are in the
normal ADB Mode.
With that knowledge now, I've also wrote a Bash pendant from the Xiaomi Sideload Tool -> Xiaomi SideLoad Terminal Tool (xsltt). Which inherits all its functions plus a bit more user comfort.
With this tool, I was able to delete my xloader, and the device now boots
straight into EDL Mode. Which is great, you can call this a Software Testpoint.
But, there is always a but, it seems that there is still no proper firehose file out there, that bypasses this annoying EDL authentication. And no, I will not even try to bypass that myself, this is way over my head.
So I would very much appriciate it, if someone can point me to a working firehose file that bypasses the EDL authentication for the Redmi Note 9 Pro (joyeuse).
I am facing the same problem, can not find the right firehose tool.
And all the apps that claim they have proper firehose file are all paid service.
since you have hydra tool, did they work for the edl? since they said they have the right firehose file.
ccaye said:
I am facing the same problem, can not find the right firehose tool.
And all the apps that claim they have proper firehose file are all paid service.
since you have hydra tool, did they work for the edl? since they said they have the right firehose file.
Click to expand...
Click to collapse
Haha, no they don't. They even recommended me the hydra dongle in their own telegram support channel. Now i have this dongle since a day, they say it is not supported in EDL Mode, only Sideload mode. And now i have to find someone who can fix the phone remotely with a auth service account. Isn't it great?
I'
newbit said:
Hello Fellows,
I've got a Redmi 9 Pro for Linux purposes, but the phone came with FRP triggered and of course, I couldn't get access to the sellers
account. I spare you the details, because I am sure, every one knows a story like that.
I checked xda and the web about guides for quite some time, and actually found a lot of them, but none of them worked. At the end I could combine
some of these guides to actually make it happened. I've created a little screen recording to show all the steps that worked for my device.
Yes you can actually install and open almost every apk even with a triggered FRP. Almost means, you can even enable the developer options, but
they don't show anything for that user.
Initial situation:
Xiaomi Redmi 9 Pro EEA (joyeuse)
Bootloader Locked
triggered FRP Lock
find my device - OFF
No MI-Account
Software Variant 1:
Firmware: MIUI V12.0.2.0.QJZEUXM Stable Official Update for Redmi Note 9 Pro EEA (joyeuse)
Android 10 - Miui 12
Android Security Patch Date: 2021-01-21
Software Variant 2:
Firmware: MIUI V12.5.8.0.RJZEUXM Stable Official Update for Redmi Note 9 Pro EEA (joyeuse)
Android 11 - Miui 12.5
Android Security Patch Date: 2022-03-01
FRP Bypass start conditions:
Wifi is connected
The basic idea and steps:
Get into System Settings via the Help & Feedback from Gmail to disable and stop certain apps.
Only for this is the wifi needed, if you type delete, the right help topic will show up
2x Android Setup
Carrier Dafault App
Google Play Services (must be disabled at the very last)
enable the Accessibility Suite to re-enable Google Play Services at the right moment
Continue the actually process to setup the phone, the procedure will stuck at "Just a sec..." "Checking for updates..."
now try to re-enable the Google Play Services, once this is done, the FRP Bypass will take place the next step
One important note, after enabling Google Play Services, its Storage and Cache must be deleted!
This is one of the main reasons why it didn't worked for me the first 100 times i tried.
It does go through though, but right at the moment the setup is finished, the FRP Lock gets triggered and
we are back at the beginning.
Enabling the Google Play Services can be annoying, because the screen is flashing/changing so fast, that the touch
will not be accepted right away. But there is plenty of time to try until it hits.
Finish the setup process until you see the home screen
Execute the factory reset over the settings menu and the FRP is gone for good
Optional, you can enable oem unlock before you factory reset the phone
With oem unlock enabled, the phone can't get FRP Lock on.
Spoiler: FRP Bypass and Reset Android 10 - Miui 12
Spoiler: FRP Bypass and Reset Android 11 - Miui 12.5
Regarding Bootloader Unlock, which es mandatory to install Linux (Ubuntu Touch) on this phone.
I couldn't found any free way to either unlock the bootloader without Mi-Account, or reboot the phone into EDL.
They are some Apps I tried so far:
Xiaomi Sideload Tool and ROM2box from Romprovider.com
But they need MIUI Recovery 5.0, and I only have MIUI Recovery 3.0
And don't want to upgrade, because Ubuntu Touch need Android 10
Does anybody have more information about that exploit these Sideload Apps are using?
I don't get how you can read data from and adb sideload connection, where you just can upload zip files
for updates
EDL from the famous Bjoern Kerler "bkerler" (MTK-Client)
For this tool the phone must be in EDL Mode, which I can't get into it
Does anybody know a way how to do that without Test Point? I tried so many ways, but none worked.
I even compiled fastboot and adb from AOSP, but the "old" ways like reboot-edl don't work.
My last hope is a USB-C V2 Cable/Dongle from Team Hydra.
Updates will follow...
[Update 1: 2023-04-25]
The FRP Bypass Procedure also works on Android 11 MIUI 12.5
[Update 2: 2023-04-25]
I've built the EDL Cable/Dongle, but it didn't work. I've bought the official
Hydra EDL Cable V2, exact same result, it also didn't work. Hydra refuses to give me a straight answer to this issue, even as a customer. The shop I've bought it
from, asked Hydra as well, with the feedback, this could be a SPD issue.
But still, they refuse to tell me, which SPD I need to get it working. At this
time I was on SPD 2021-01-21, and they published the EDL Cable Pinouts in Dec. 2022 [Latest Security]. So this was a very false promise from Hydra or rather mobilerdx, not sure who's to blame here, perhaps myself.
[Update 3: 2023-04-25]
I've wrote an ADB and Fastboot Sniffer for Windows. Which worked
pretty well, and I was able to get the ADB commands from the Xiaomi Sideload Tool. So the Exploit is basically, that you can perform ADB PULL and ADB PUSH while your in SIDELOAD Mode, that's it. And that it uses a built-in command to gather the partition structure while you are in the
normal ADB Mode.
With that knowledge now, I've also wrote a Bash pendant from the Xiaomi Sideload Tool -> Xiaomi SideLoad Terminal Tool (xsltt). Which inherits all its functions plus a bit more user comfort.
With this tool, I was able to delete my xloader, and the device now boots
straight into EDL Mode. Which is great, you can call this a Software Testpoint.
But, there is always a but, it seems that there is still no proper firehose file out there, that bypasses this annoying EDL authentication. And no, I will not even try to bypass that myself, this is way over my head.
So I would very much appriciate it, if someone can point me to a working firehose file that bypasses the EDL authentication for the Redmi Note 9 Pro (joyeuse).
Click to expand...
Click to collapse
I'm ready to fund for research cause. I will invest in the tool that I know which allows EDL authentication so that we can verify if it works with your device.
Please let me know so that together we can succed in fixing your phone.
mvikrant97 said:
I'
I'm ready to fund for research cause. I will invest in the tool that I know which allows EDL authentication so that we can verify if it works with your device.
Please let me know so that together we can succed in fixing your phone.
Click to expand...
Click to collapse
Thank you for your generous offer, I am not sure If I understand you right, plus I don't have the need
for charity. To be honest, I don't even have a clue, what to believe now. They all promise you honey
flowing in rivers, but can't really deliver.
They are tools called EMT and UAT Pro. Never heard about them before. But they claim they have
auth support for this model in EDL mode. UAT even offers a pure software solution for an affordable price.
If you are willing to fund your self, please try it out, and report back.
newbit said:
Thank you for your generous offer, I am not sure If I understand you right, plus I don't have the need
for charity. To be honest, I don't even have a clue, what to believe now. They all promise you honey
flowing in rivers, but can't really deliver.
They are tools called EMT and UAT Pro. Never heard about them before. But they claim they have
auth support for this model in EDL mode. UAT even offers a pure software solution for an affordable price.
If you are willing to fund your self, please try it out, and report back.
Click to expand...
Click to collapse
I won't be investing in those tools. Both EMT and UAT allow auth flashing however I know a tool called Xiaomi Pro tool which supports auth flashing and it works and the investment is pretty low so I can invest in that tool to help you out with auth flashing.
I cannot discuss any further as XDA does not allow that.
mvikrant97 said:
I won't be investing in those tools. Both EMT and UAT allow auth flashing however I know a tool called Xiaomi Pro tool which supports auth flashing and it works and the investment is pretty low so I can invest in that tool to help you out with auth flashing.
I cannot discuss any further as XDA does not allow that.
Click to expand...
Click to collapse
Yeah that's weird, I've read this a lot, never had any issues with XDA about that.
Anyways, I can't find any manufacture website to the Xiaomi Pro Tool, so I cannot compare.
I think 15 bucks for are 3 Months time period is much cheaper compared to the 110 I've paid
for this Hydra Dongle, which brings me zero yet. So please, write me a PM with a link to a shop.
Just a little Update.
Thank your @mvikrant97, Xiaomi Fire Tool did the trick. They don't unlock bootloader,
but flash firmware with EDL auth. And now my phone is back to life. Support was very good, in fact,
they were the only ones who responded at all. Very patience and polite as well. Plus, very affordable.
Once my phone is fully charged, battery was totally drained since it was in EDL Mode for weeks, I will see
what Hydra has to offer. Btw: They've banned me from their Support Channel, without any explanation.
I guess I asked the wrong questions, pitty.
newbit said:
Just a little Update.
Thank your @mvikrant97, Xiaomi Fire Tool did the trick. They don't unlock bootloader,
but flash firmware with EDL auth. And now my phone is back to life. Support was very good, in fact,
they were the only ones who responded at all. Very patience and polite as well. Plus, very affordable.
Once my phone is fully charged, battery was totally drained since it was in EDL Mode for weeks, I will see
what Hydra has to offer. Btw: They've banned me from their Support Channel, without any explanation.
I guess I asked the wrong questions, pitty.
Click to expand...
Click to collapse
I'm very happy to learn that your phone is fixed.
While the rest we can discuss in PM!
Tale as old as time. Have a phone given, factory reset with a Google account that wasn't properly removed.
So FRP lock is in play.
Seems like all the old tricks & tips I knew years ago don't seem to work on this device. Seems like the A14 on Android 13 is lock tight.
What I can do is use ODIN to flash back to stock rom, but that didn't really help.
And what I can also do is go through User License agreements, and somehow fumble my way through Learn More links that I can eventually lead to Google Search
But this method doesn't have Java Script enabled, so I can't login to Google account and add my own account that way.
I'm looking towards roms for the previous model since they're so similar but this feels like a dead end before I even think of a download since incompatible roms can't be flashed.
All I really need is Bootable Android 11 or 12 regardless of how functional or broken it is so I can try exploits for those versions. Just enough to activate OEM unlocking and USB debugging is the end goal
Any tips y'all have?
According to this list
LineageOS 20 Supported Phones: All Models For 2023 [UPDATED]
Here's a quick breakdown of ALL the Android phones that can run LineageOS 20...
www.knowyourmobile.com
the popular Lineage OS isn't available for the Galaxy A14
Rottytops said:
Tale as old as time. Have a phone given, factory reset with a Google account that wasn't properly removed.
So FRP lock is in play.
Seems like all the old tricks & tips I knew years ago don't seem to work on this device. Seems like the A14 on Android 13 is lock tight.
What I can do is use ODIN to flash back to stock rom, but that didn't really help.
And what I can also do is go through User License agreements, and somehow fumble my way through Learn More links that I can eventually lead to Google Search
But this method doesn't have Java Script enabled, so I can't login to Google account and add my own account that way.
I'm looking towards roms for the previous model since they're so similar but this feels like a dead end before I even think of a download since incompatible roms can't be flashed.
All I really need is Bootable Android 11 or 12 regardless of how functional or broken it is so I can try exploits for those versions. Just enough to activate OEM unlocking and USB debugging is the end goal
Any tips y'all have?
Click to expand...
Click to collapse
You can't do anything because the bootloader lock is on.
I bypassed frp with sp flash tool but a14 has exynos processor so sp flash tool will not work.
There is no offical previous android, So downgrade will not work too.
Was able to bypass FRP unlock using one of those paid tools, but it may have been unnecessary to pay. (SamFW to be specific)
I'll explain for future googlers dealing with the same issue.
So I had the ATT model of the device. Specifically model SM-A146U. It comes with an Exynos or Mediatek SoC.
Mine was specifically the MT variant.
I used Odin3 to revert to the stock build. Build dated November 29/Dec 1 2022; despite the official release date of the device being Jan 2023.
The emergency code *#0*# does not work, but *#*#88#*#* does.
Obviously you needed Samsung USB, ADB, drivers installed. Additional troubleshooting has me download Microsoft Visual C++ 2015 ; and MT65XX Preload Drivers.
The SamFW tool claims it's free to remove the FRP lock on security patches pre-dating December 2022.
The SamFW tool only suggests you needed Samsung driver's and Visual C++. So I tried several times using the SamFW tool to push it's exploit, and it kept failing.
So in a moment of weakness, I bought the $15 credit pack because it promised "All models", ran the tool again, and still it failed. It required a credit card number for a service called coffee break or something, which is exactly the shady **** I have a cash app card for. I was not going to use my real bank account.
Because it runs a ADB exploit, I reboot into Recovery. Then in recovery menu, I select to Reboot into Bootloader, which puts the device into fastboot.
This is where I discover that I had no ADB drivers.
So I install ADB, and open Terminal/shell, whatever you call it. (Hold Shift and right click in ADB folder to shortcut ADB terminal)
I type:
Fastboot Devices
Didn't get a serial. I reboot Fastboot again, this time with Device Manager open on Windows, and notice for 5 seconds, a device called MT65xx preloader was lacking driver, and unloaded to reload ADB drivers. This is where I find out I'm using a MediaTek SoC
So I finally googled and install MT65xx Preload. Reboot to Fastboot 1 more time. I type
Fastboot Devices
I get a serial.
So not I reboot to system, then on phone in emergency dial type *#*#88#*#* then do another device check. Looks good.
Because I already paid $15 for the premium unlock, that's the first option I pick it finally unlocks. But because all this time I was missing critical mediatek drivers, the free option still could have worked. So I can't confirm if being free would have sufficed, or if I needed that paid service.
But what's done was done, and I was able to get into the phone.
So to recap I used:
SM-A146U ATT stock Rom (5.5GB), earliest build Nov-Dec 2022 (Google it)
Odin v3 Flash Tool (Hold Vol+ Vol- & Power to access)
Samsung USB Drivers (Latest and official)
Google ADB Drivers (Mini installer)
Microsoft Visual C++ 2015
MT65xx preloader Drivers (Google it)
And SamFW 4.6 FRP Tool
Emergency Dial code : *#*#88#*#*
To bypass FRP Lock on Galaxy A14 ATT version, Model SM-A146U ; MediaTek variant.
and to reiterate, Recovery and Fast Boot are not necessary in any part of the process.
I use Recovery to boot into Fastboot, and I only use FastBoot + ADB to personally confirm that my computer recognizes the device connected in several boot modes