I bricked my phone by flashing a patched boot image from 11.0.2 to a phone with 11.0.0 and I can't get to fastboot mode - etc. I think MSM is my only way back?
I got it to fastboot mode, but there's no boot image for 11.0.0 available, right? Please help
Is it T-Mobile version or unlocked?
There's MSM tool for T-Mobile version and you can download full ROM for unlocked
If yours is unlocked and you can access recovery, use sideload
Code:
adb sideload
Press spacebar once and drag and drop the ROM onto command window and press enter
This can fix boot as well as making version update
bouyakasha said:
I bricked my phone by flashing a patched boot image from 11.0.2 to a phone with 11.0.0 and I can't get to fastboot mode - etc. I think MSM is my only way back?
Click to expand...
Click to collapse
there is no msm tool for the full paid version from OP store .. only for T-Mobile .. but if you phone is still under waranty please get a hold of tech support and tell them you request a remote session and that your phone is seen by your computer . they will have you fill up some forms via email and send you the link to download the tools .. if you do please share them here .. when i had my issue they didnt have the tools available and chose not to send my phone back so i am like you with a briked phone
T-Mobile Variant MSM Tools:
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
Do not use this on any other variant.
I have no idea how to send it, but I have a boot.img from my factory unlocked N200 (Model DE2117) on firmware Oxygen OS 11.0.0.0.DE17AA. I also have a magisk patched copy of that boot.img. Let me know how to send it and you can give it a shot.
I have found fastboot flashing method for 8T to flash unlocked ROM on T-Mobile version (unlocked bootloader required).
Since T-Mobile version MSM is available, I can use it if anything goes wrong
Stay tuned
amboyscout said:
I have no idea how to send it, but I have a boot.img from my factory unlocked N200 (Model DE2117) on firmware Oxygen OS 11.0.0.0.DE17AA. I also have a magisk patched copy of that boot.img. Let me know how to send it and you can give it a shot.
Click to expand...
Click to collapse
wow .. please upload it to google drive or mega (dot) nz and post the link here .... honestly this gets me very excited ...
mingkee said:
I have found fastboot flashing method for 8T to flash unlocked ROM on T-Mobile version (unlocked bootloader required).
Since T-Mobile version MSM is available, I can use it if anything goes wrong
Stay tuned
Click to expand...
Click to collapse
my bootloader is locked .. thats why MSMDownload tool is a must
edale1 said:
T-Mobile Variant MSM Tools:
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
Do not use this on any other variant.
Click to expand...
Click to collapse
I tried that on my full paid one from oneplus.com and it dont work ... so yes its a waste to download it for nothing
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
There's a maual method.
If you're familiar with fastboot flash with Moto phone, yes, similar commands.
Download full ROM and unpack with payload dumper, and flash every .img one by one
Dimitrimem said:
I tried that on my full paid one from oneplus.com and it dont work ... so yes its a waste to download it for nothing
Click to expand...
Click to collapse
If you use the "+ Quote" button, rather than the reply button, it'll create a multiquote, letting you quote and reply to multiple posts all at once (it'll add a "insert quotes" button to the reply box). This eliminates double-posts, which most forums frown upon.
@Dimitrimem here ya go https://drive.google.com/drive/folders/1DzR0uEdyFeBeID4sVaT96z0Y88sMaomL?usp=sharing
Dimitrimem said:
there is no msm tool for the full paid version from OP store .. only for T-Mobile .. but if you phone is still under waranty please get a hold of tech support and tell them you request a remote session and that your phone is seen by your computer . they will have you fill up some forms via email and send you the link to download the tools .. if you do please share them here .. when i had my issue they didnt have the tools available and chose not to send my phone back so i am like you with a briked phone
Click to expand...
Click to collapse
Tried this today. Now waiting on OnePlus to respond.
bouyakasha said:
Tried this today. Now waiting on OnePlus to respond.
Click to expand...
Click to collapse
Don't wait to long for their reply .. if they don't answer call them on the phone.. it takes less than a minute to have them speak with you ... I dragged it for too long with them waiting 7 days to send me a shipping label than another 5 for another try at it .. another 4 to get the link for download ..after all that they said they don't have it... but this was a while back ... I'd be on that phone fast.. tell them you need your phone as it's the only one ... honestly if you can get the msm tool it would be amazing
mingkee said:
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
There's a manual method.
If you're familiar with fastboot flash with Moto phone, yes, similar commands.
Download full ROM and unpack with payload dumper, and flash every .img one by one
Click to expand...
Click to collapse
I am familiar with this from Moto, and some previous manual flashes with my OEM OP5. However, after extracting the partition .imgs from the OOS OTA via this tool when I try to `fastboot flash logo logo.img` (among others), I get hit with `FAILED remote: flashing is not allowed for critical partitions`, even after having unlocked with `fastboot flashing unlock_critical`. How were you able to get everything to work?
I also tried flashing the OTA zip via the TWRP, but it seems like the current dev version of TWRP in that thread is completely borked for N200 as far as ROM flashing goes ://
darkghost568 said:
I am familiar with this from Moto, and some previous manual flashes with my OEM OP5. However, after extracting the partition .imgs from the OOS OTA via this tool when I try to `fastboot flash logo logo.img` (among others), I get hit with `FAILED remote: flashing is not allowed for critical partitions`, even after having unlocked with `fastboot flashing unlock_critical`. How were you able to get everything to work?
I also tried flashing the OTA zip via the TWRP, but it seems like the current dev version of TWRP in that thread is completely borked for N200 as far as ROM flashing goes ://
Click to expand...
Click to collapse
You have to flash in fastbootd (... reboot fastboot) as instructed in 8T forum
mingkee said:
You have to flash in fastbootd (... reboot fastboot) as instructed in 8T forum
Click to expand...
Click to collapse
Ok so now I'm stuck here as well (saw your comment in the other thread):
mingkee said:
I attempted to flash unlocked ROM on bootloader unlocked T-Mobile version phone
It stuck on products.img. The error stated "not enough space for the partition"
What happened?
Click to expand...
Click to collapse
Any luck getting past this?
darkghost568 said:
Ok so now I'm stuck here as well (saw your comment in the other thread):
Any luck getting past this?
Click to expand...
Click to collapse
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Towards the bottom of that post it talks about getting past that error.
Related
I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
SpectreCular said:
I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
Click to expand...
Click to collapse
I also have the Samsung A21 from T Mobile (SM-A21UZKATMB). The phone is unlocked by T Mobile but there is no OEM bootloader unlock button under the Developer mode. Changing the date (forward and backward in time), then run the software update did not solve the OEM bootloader unlock button problem. I suspect the carrier (T Mobile) has disabled this function. You will need to unlock the bootloader to install the stock firmware.
To those who have enabled the OEM bootloader in the A21. Is your phone locked to a carrier in the USA like Verizon or T Mobile?
I also have the SM215DL, using straight talk utilizing verizon service, I also cannot unlock the bootloader. Everything you guys did, I did. Nothing worked.
samsung has done this to all A series phones intended for the U.S. from what i understand
Where there's a will, there's a way... someone has messed with my phone too do doesn't that mean that they're altering the data/data partition to r/w. Did you guys try fastboot flashing unlock vs. fastboot oem unlock. I'm going to contact Samsung about this and let u all know what's up.
And also why would there be a usb debugging port if this phone can't be modded? Idon't know the answer but maybe someone more expediency could come in and help us out. I also wonder if the flash_image command or just dd it would bypass it?
... there is NO way, to root the A21(s), see here: https://forum.xda-developers.com/t/root-possibility.4130739/page-12#post-84944589
MaBo2020 said:
... there is NO way, to root the A21(s), see here: https://forum.xda-developers.com/t/root-possibility.4130739/page-12#post-84944589
Click to expand...
Click to collapse
I confirm that I have rooted my A21S sucessfully using this modified magisk (U3 Rom). No need to patch the whole AP.tar file, just patch boot.img file only. I upload my patched boot.img for those who need it. Just flash it via odin in AP slot. Thank you very much @grccorps.
https://forum.xda-developers.com/attachments/boot-tar.5299081/
thatha said:
I confirm that I have rooted my A21S sucessfully using this modified magisk (U3 Rom). No need to patch the whole AP.tar file, just patch boot.img file only. I upload my patched boot.img for those who need it. Just flash it via odin in AP slot. Thank you very much @grccorps.
https://forum.xda-developers.com/attachments/boot-tar.5299081/
Click to expand...
Click to collapse
... exactly Step-by-Step, how u do it with downloadlinks of all Software, what u used !
Many Peoples writes, that they have rooted the A21s, but no one shows, how ! With the newest Firmware u cant rooted the Phone, because there is no working TWRP, SuperSU or MAGISK - Version out for this Phone !
MaBo2020 said:
... exactly Step-by-Step, how u do it with downloadlinks of all Software, what u used !
Many Peoples writes, that they have rooted the A21s, but no one shows, how ! With the newest Firmware u cant rooted the Phone, because there is no working TWRP, SuperSU or MAGISK - Version out for this Phone !
Click to expand...
Click to collapse
Extract boot.img from AP.tar, then use modified-magisk to patched it
... this Methode is not working, i try it many Times, no RootAcess ! Again: if u have newer Firmware on this Phone (End 2020 - until now) u cant root this Phone ! Maybe on ure Phone an older Firmware ...
And this is my U5 patched boot.img
MaBo2020 said:
... this Methode is not working, i try it many Times, no RootAcess ! Again: if u have newer Firmware on this Phone (End 2020 - until now) u cant root this Phone ! Maybe on ure Phone an older Firmware ...
Click to expand...
Click to collapse
I have just made a post here, you can try it
[SHARING] HOW TO ROOT A21S STOCK ROM WITH MAGISK
Hello friends I just want to share how to root A21S stock rom in case anybody needs it: 1. Unlock bootloader 2. (On PC) Extract boot.img.lz4 from AP...tar file, then copy it to phone 3. (On phone) Install ZArchiver to extract boot.img from...
forum.xda-developers.com
... and u shure, it its for the A21s or for A21 ?
The only hope of getting root on this phone is if you find a Dev who's interested enough to build a bootstrap recovery. I've not looked at the firmware & have no idea if there's an exploit that would work for that purpose.
Bootstrap recovery was the only way of getting root/custom recovery back in the days of Motorola D2 & Droid X, the original Droid X. Motorola was THE phone for development... Liberty ROM, Gummy ROM, Simply Stunning, etc.
I would not hold out hopes for that to happen here.
Peace - MS
Seriousfreedom said:
samsung has done this to all A series phones intended for the U.S. from what i understand
Click to expand...
Click to collapse
No, Samsung has done this to ALL North American models ever since the Galaxy S8. The bootloaders are not user-unlockable, like they are on international models. However, some models can be rooted via a software exploit if they're running very old firmware, or some models can even be bootloader unlocked via special files, if their firmware version is old enough
SpectreCular said:
I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
Click to expand...
Click to collapse
Mine is rooted. But you have to buy a token.
o.class.jav said:
Mine is rooted. But you have to buy a token.
Click to expand...
Click to collapse
what token??
[email protected] said:
what token??
Click to expand...
Click to collapse
The one generated by the SamPwns steady.bin flash.
{Mod edit: Quoted post removed}
and where does one get 'TWRP' for the Samsung Galaxy A21S?? Thanks for the post its very detailed with very clear instructions, and i agree with you this is the tried and tested and perfect way of rooting your phone, only problem is that this is an unperect world a world where 'TWRP' for the SM-A217F does not exist
I just received a refurbished SM-S215DL (A21,) not as my provider's solution to the VoLTE soon to be required for 4G devices thing and right now it's a pretty severe downgrade for me since it lacks a lot of basic functionality I'm used to from my 2017 phone running LineageOS. Obviously it's pretty unlikely or probably outright impossible to ever see a real LineageOS ROM for this thing (and even if someone ever does it probably would be insanely unstable or incomplete,) but if I could at least root it (even if I have to manually patch or something) it would really help me out a lot. Has just nothing really been found short of sending some unknown person online some very very key device details and money (which I don't have or I'd be buying something else anyway)? (Also kind of suspicious that whatever method they're using isn't something available to the public anyway...)
So to use this, you will need to be bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled this is a must!!(its always good to make a nandroid before making any changes on your phone). What this will do is more or less provision your Lg G8x to your Desired Carrier, it will also let you change your apns, so you have volte working and also the data indicator will change to match the carrier. WIfi calling is working on tmobile, will need someone to test other carriers.
There seems to be confusion , this is only for the Stock rom. this will do nothing for GSI roms.
Instructions:
1.Extract to Content of zip to Sdcard
2.Make a copy/backup of your own files: Go to twrp and backup your product partition and your op configs in case you need to restore them
3.Copy and paste the files from my zip to:
/product/op/config
and this single file cust.prop to /product/op
make sure permissions are 644.
4.Reboot your device it should now be provisioned to your Desired Carrier.
Click to expand...
Click to collapse
Download
Sprint Untested
SPR-VOLTE-FIX
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
T-Mobile
Tmo-VOLTE-VOWIFI-FIx-G8x
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
VZW Untested
VZW-VOLTE-FIX
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Credits:
vl48 this guy is awesome, and also very patient an expert in lg devices.
Can you write a guide for ATT LG G8X (LMG850UM) on
How to bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled? It's confusing which method is valid and which files to use.
e20140 said:
Can you write a guide for ATT LG G8X (LMG850UM) on
How to bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled? It's confusing which method is valid and which files to use.
Click to expand...
Click to collapse
There is one already made, you just need the correct twrp from telegram
siulmagic said:
There is one already made, you just need the correct twrp from telegram
Click to expand...
Click to collapse
Why not post on xda? Is everyone switching to telegram? I've read everything on xda and don't see a specific method to unlock bootloader+twrp+DM but a few failed attempts on ATT version of the G8X. I only see working solution for India, Europe, and Sprint Models. You are the only one that has successfully unlock it. I am sure more people will need help as 3G is going away and we need Volte working on this phone.
well the basic gist of it is:
This will WIpe Your Phone, make sure to backup first.
Cant post the recovery zip, but pm il send it to you. i will move this to a proper thread later today. and better formatted
1.install qpst/qualcom driver or use windows update ones
2. download firehose uncompress it somewere on your pc
3.download g8x twrp and magisk 20.4 zip also the dm verity zip
also make sure to grab the eng abl for the g8x(eng bootloader that will allow us to unlock).
4. enable oem unlock in developer settings
5. boot phone into edl mode
6.start qpst set storage type to ufs, slect built type, make sure it is flat build
7.Look for select programer then click browse, here you will chose the firehose file
8. click select port on qfil then double click 9008 com port were the phone is detected in edl mode
9.now in qfil select tools then partition manager
10. when the list of partitions show up look for abl_a,abl_b,modem a/b, and modemst1 and 2, you will right click each of them and click manage partition data then read data, this will back them up to your computer(be very careful you can wipe your whole phone if you click in the wrong place)
11.after you back up everything select load img and flash abl_a to Abl_a and abl_b. after this unplug phone and boot into bootloader mode.
To boot into bootloader mode turn off your phone and hold volm down and plug in your usb cable, this should boot it into bootloader mode .
12. if you see text that says you active boot slot, you now have successfully flashed the eng bootloader witch will allow you to unlock the bootloader.
13. now while the phone is pluged into your computer you will open a adb window and type fastboot oem unlock , the phone will ask you to agree to unlock the bootloader, select yes.
14.after this reboot your phone into edl mode, reflash your backup abl_a to abl_a and abl_b, this will restore stock bootloader you wont have fastboot anymore but no worries, also you can flash your stock rooted boot.img to boot_a and boot_b.
15. After you reboot into android, install magisk manager, flash the g8x twrp zip and without reboot, also flash magisk 20.04 zip, if you do not do it this way you will break your boot.img and have issues, like freezing system.
16 now reboot to recovery wipe data then reboot and flash the dm verity disabler to disable encryption. after this create a nandroid backup, then just reboot back to system and enjoy.
17. profit
Nice
I need to return my G8X since it has the latest 20g firmware. If anyone wants me to try or test something, please let me know before it's going back.
e20140 said:
Nice
I need to return my G8X since it has the latest 20g firmware. If anyone wants me to try or test something, please let me know before it's going back.
Click to expand...
Click to collapse
why 0o with gpst and firehose you can root bl unlock any att g8x, unless there something im not aware of?
I post the short error log here. The firehose we got can't read the partitions correctly. Maybe the mappings are different, IDK? If you want to read the full log, let me know.
e20140 said:
I post the short error log here. The firehose we got can't read the partitions correctly. Maybe the mappings are different, IDK? If you want to read the full log, let me know.
Click to expand...
Click to collapse
thats a driver error, you need to let windows install the driver from windows update or like i did use qpst on windows 7. i never got that erro fixed, so i just used windows 7 on a old laptop i have, and it works mint.
I don't have Window 7 to try but tried on other Win 10 PCs and Laptops, just no luck. I can use QPST to flash flat built on my G6 fine, really don't think it's driver issue.
e20140 said:
I don't have Window 7 to try but tried on other Win 10 PCs and Laptops, just no luck. I can use QPST to flash flat built on my G6 fine, really don't think it's driver issue.
Click to expand...
Click to collapse
well thats the error i got, with my g8 and g8x on windows 10.
wangsu10 suggested the error could be installation selection option for the QCOMM driver. Need to be install as 2nd option " ETHERNET-DHCP". I already returned mine
Maybe you can try it on your Win10 and report back. If it works, we need to have it added to the OP for all others to see.
Thank you for sharing this. I have a sprint model that ended up with T-mobile provisioning after I boot loader unlocked it. The only issue I think I have at least the obvious is google messages will never verify and setup rcs. I suspect this will be permanent eventually as they begin to roll out their other layer of security for verifying that which would basically black list bootloader unlocked or rooted devices...will your files/instructions aid in any issues with RCS currently before before Google makes the final rollout?
nate0 said:
Thank you for sharing this. I have a sprint model that ended up with T-mobile provisioning after I boot loader unlocked it. The only issue I think I have at least the obvious is google messages will never verify and setup rcs. I suspect this will be permanent eventually as they begin to roll out their other layer of security for verifying that which would basically black list bootloader unlocked or rooted devices...will your files/instructions aid in any issues with RCS currently before before Google makes the final rollout?
Click to expand...
Click to collapse
Thats an easy fix search for carrier services on play store , update it and see if chat features get enabled, I got rcs working just fine on att g8x bl unlocked and rooted ofc.
siulmagic said:
Thats an easy fix search for carrier services on play store , update it and see if chat features get enabled, I got rcs working just fine on att g8x bl unlocked and rooted ofc.
Click to expand...
Click to collapse
Yeah I did this, and by default it was already installed. Still no luck. I tried clearing data while on airplane mode everything. Nothing works yet.
@siulmagic where is the twrp image for the g8x? Did they pull it down?
nate0 said:
@siulmagic where is the twrp image for the g8x? Did they pull it down?
Click to expand...
Click to collapse
the one here never worked properlly, if you want a working one join telegram and i can send it to you,.
nate0 said:
Yeah I did this, and by default it was already installed. Still no luck. I tried clearing data while on airplane mode everything. Nothing works yet.
Click to expand...
Click to collapse
there is another app that needs updated i forgot witch one it was.
siulmagic said:
the one here never worked properlly, if you want a working one join telegram and i can send it to you,.
Click to expand...
Click to collapse
Newbie to Telegram, how does one find the group please?
mangojain said:
Newbie to Telegram, how does one find the group please?
Click to expand...
Click to collapse
LG Mobiles India 🇮🇳
Political Discussion, Obscene material/words, Selling, Fraudulent link posting will lead to Ban SHARING COPYRIGHT CONTENT & PIRACY NOT ALLOWED, it leads to REPORT & BLOCK Photography Group: @lgg8xphotography OT Group: @LG_G8X_OffTopic
t.me
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system partition
Now my phone is stuck in fastboot and won't boot from an image, take a recovery image, etc. etc. it's kinda completely messed up and it's my fault for trying to tinker with commandline tools.
The problem is there is no MSM recovery for my phone, and even if there was virtualbox can't detect my phone's USB(I've already tried with just the nord MSM, I run linux and I was using a win10 VM)
Is there any hope? Do I have to go to a repair shop?
First post has a section specifically about the drivers you'll need to have your phone recognized in fastboot mode:
The Quest for a Bootloader Unlock (partial guide, T-Mobile variant, may work for MetroPCS/Metro variant)
OK, this process has been hell, but I'm gonna try and consolidate everything I've worked out so far in one place. This all applies only to the T-Mobile variant (ie. it comes preloaded with all the T-Mobile bloatware) of the N200 on the T-Mobile...
forum.xda-developers.com
That said, I'm pretty sure you're stuck until the MSM tool comes out (the MSM tool is different for each phone, DO NOT use one for a different OnePlus phone) to fix it yourself.
edale1 said:
First post has a section specifically about the drivers you'll need to have your phone recognized in fastboot mode:
The Quest for a Bootloader Unlock (partial guide, T-Mobile variant, may work for MetroPCS/Metro variant)
OK, this process has been hell, but I'm gonna try and consolidate everything I've worked out so far in one place. This all applies only to the T-Mobile variant (ie. it comes preloaded with all the T-Mobile bloatware) of the N200 on the T-Mobile...
forum.xda-developers.com
That said, I'm pretty sure you're stuck until the MSM tool comes out (the MSM tool is different for each phone, DO NOT use one for a different OnePlus phone) to fix it yourself.
Click to expand...
Click to collapse
Yeah I run linux, I don't need the drivers
It b what it b
Gip-Gip said:
Yeah I run linux, I don't need the drivers
It b what it b
Click to expand...
Click to collapse
Ah. Sadly, I have next to no experience with Linux outside of the tinkering I've done on my Raspberry Pis, so can't help you there.
Gip-Gip said:
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system partition
Now my phone is stuck in fastboot and won't boot from an image, take a recovery image, etc. etc. it's kinda completely messed up and it's my fault for trying to tinker with commandline tools.
The problem is there is no MSM recovery for my phone, and even if there was virtualbox can't detect my phone's USB(I've already tried with just the nord MSM, I run linux and I was using a win10 VM)
Is there any hope? Do I have to go to a repair shop?
Click to expand...
Click to collapse
My experience with USB passthrough on different hypervisors is that they all suck. I have to use Windows at work, so I use it for most of the tools including MSM tools.
That being said, I've never seen a real difference in adb / fastboot on Linux or Windows.
Have you tried calling OnePlus by chance?
SMcC2 said:
My experience with USB passthrough on different hypervisors is that they all suck. I have to use Windows at work, so I use it for most of the tools including MSM tools.
That being said, I've never seen a real difference in adb / fastboot on Linux or Windows.
Have you tried calling OnePlus by chance?
Click to expand...
Click to collapse
No, but there is a 100% chance that they'll just tell me to use their repair program. Which I'll be surprised if it's under $100 for me to mail it in, have some dude spend 5 minutes flashing it, and then mail it back
Gip-Gip said:
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system partition
Now my phone is stuck in fastboot and won't boot from an image, take a recovery image, etc. etc. it's kinda completely messed up and it's my fault for trying to tinker with commandline tools.
The problem is there is no MSM recovery for my phone, and even if there was virtualbox can't detect my phone's USB(I've already tried with just the nord MSM, I run linux and I was using a win10 VM)
Is there any hope? Do I have to go to a repair shop?
Click to expand...
Click to collapse
what exactly is messed up on your phone. i have metro ver rooted and can backup any partition img you need to flash from my stock rooted n200. do you need stock boot or recovery? if not then what do you need?
an is fastboot able to detect your phone?
PopCaps1996 said:
what exactly is messed up on your phone. i have metro ver rooted and can backup any partition img you need to flash from my stock rooted n200. do you need stock boot or recovery? if not then what do you need?
an is fastboot able to detect your phone?
Click to expand...
Click to collapse
i am not replying for the OP but i did the same thing .. fastboot sees the phone yet the bootloader is locked ... so OEM cant be unlocked using fastboot .. if i got this right .. only after oneplus releases the rom on their site this can be fixed .. Please correct me if i am wrong ...
Dimitrimem said:
i am not replying for the OP but i did the same thing .. fastboot sees the phone yet the bootloader is locked ... so OEM cant be unlocked using fastboot .. if i got this right .. only after oneplus releases the rom on their site this can be fixed .. Please correct me if i am wrong ...
Click to expand...
Click to collapse
do you have a unlock code from oneplus for you n200?
PopCaps1996 said:
do you have a unlock code from oneplus for you n200?
Click to expand...
Click to collapse
my phone was paid in full from oneplus store in US .. so i dont think i need a code
Dimitrimem said:
i am not replying for the OP but i did the same thing .. fastboot sees the phone yet the bootloader is locked ... so OEM cant be unlocked using fastboot .. if i got this right .. only after oneplus releases the rom on their site this can be fixed .. Please correct me if i am wrong ...
Click to expand...
Click to collapse
my bootloader is unlocked I just can't enter fastbootd, which is a problem
Hey there, so I managed to get a hold of the MSM tools this morning. Since I have to go out soon, I'll upload them later. Once I upload them, you should be able to unbrick your phone.
lzgmc said:
Hey there, so I managed to get a hold of the MSM tools this morning. Since I have to go out soon, I'll upload them later. Once I upload them, you should be able to unbrick your phone.
Click to expand...
Click to collapse
Excellent! This will be of so much help to many folks out here who have bricked their phones. Look forward to your sharing the tool.
Is the MSMDownload tool, that you got, for the Tmobile version or the unlocked version/retail or both?
jilebi said:
Excellent! This will be of so much help to many folks out here who have bricked their phones. Look forward to your sharing the tool.
Is the MSMDownload tool, that you got, for the Tmobile version or the unlocked version/retail or both?
Click to expand...
Click to collapse
It's for the T-Mobile version. Someone with a retail N200 will have to request a "remote session" with OP support in order to get the MSM tools for the retail version.
lzgmc said:
It's for the T-Mobile version. Someone with a retail N200 will have to request a "remote session" with OP support in order to get the MSM tools for the retail version.
Click to expand...
Click to collapse
@lzgmc, thanks.
How does this "remote session" with OP work? Does one report that the phone is bricked, and then they send you the tool which you execute? Or do they run the tool in real time using a remote desktop tool, but then one has to somehow capture their MSMDownlod tool using some other tool? Do they not try to delete the downloaded tool?
If you could share your detailed experience of this "remote session", and how to capture the MSMDownload tool, it would be of tremendous help. I don't own a retail/unlocked N200, but your experience can perhaps help those who have one, in getting the MSMDownload tool for the retail version. It would benefit the Tmobile users too, in finding a way to potentially convert Tmobile version to retail version. Thanks!
Can you upload the tool please mine is bricked after crash dump
nache2001 said:
Can you upload the tool please mine is bricked after crash dump
Click to expand...
Click to collapse
this might help..... https://forum.xda-developers.com/t/...ot-magisk-patched-boot-imgs-included.4323439/
PopCaps1996 said:
this might help..... https://forum.xda-developers.com/t/...ot-magisk-patched-boot-imgs-included.4323439/
Click to expand...
Click to collapse
Bootloader is locked i can't flash a patched rom, thanks anyway.
nache2001 said:
Bootloader is locked i can't flash a patched rom, thanks anyway.
Click to expand...
Click to collapse
That is a pity. The MSMDownload Tool seems to be the only way to fix this.
The good news is that the MSMDownload Tool is now available with Oneplus support, as of today e.g. until last week, folks out here posted that Oneplus support did not have the tool released to them. Perhaps you can contact Oneplus support and request a "remote session" to unbrick it similar to what @lzgmc did, and get your phone un-bricked sooner? If you do so, try to grab a copy of the MSMDownload Tool that they use in the session and share it with others out here. I am sure @lzgmc will post it soon, but no harm in having multiple copies available.
lzgmc said:
It's for the T-Mobile version.
Click to expand...
Click to collapse
@lzgmc Do you happen to recall which version of Oxygen OS the MSMDownlod tool is for? 11.0.1.4 or 11.0.1.5?
There's no way to root this a phone with the following, is there?
OP N10 5G / TMO / BE2025.BE88CB / 11.0.2.BE88CB
- Bootloader unlocked.
- Not rooted.
Seems to me there's no MSM tool for the BE88CB (TMO) variant, no TWRP, and no flashed boot images available.
Do I have this right? Rooting is impossible?
How much of a loss do you want to risk? (I think a refurb is ~$250 now for an international).
I'd try the TWRP for the international one, and you can flash Magisk directly from that (rename .apk to .zip); I've never needed the boot images.
If that doesn't work, I think you can MSM the ENTIRE international recovery image over it... even if you lose some of the T-mo bands (m-wave?) it is still pretty quick (mine is a international phone, on Tmo, 5G works great for me).
If the bootloader is unlocked, you should be in good shape.
YMMV, no refunds, at your own risk, etc. I have gotten braver in my old age, though.
I've been through this thread: https://forum.xda-developers.com/t/...bile-metro-w-locked-bootloader.4297501/page-5
But both links to MSM the TMO to GLO are dead, so the MSM is currently not available.
The TWRP for the international... I'll happily try that, do you know where it is? I've tried booting to 3.5.2_10-1 and it boots but the touchscreen doesn't work via `fastboot boot` (not `fastboot flash boot` ) which can be found here: https://forum.xda-developers.com/t/twrp-3-5-2_10-billie-twrp-for-oneplus-nord-n10-5g-beta.4256333/
bouyakasha said:
There's no way to root this a phone with the following, is there?
OP N10 5G / TMO / BE2025.BE88CB / 11.0.2.BE88CB
- Bootloader unlocked.
- Not rooted.
Seems to me there's no MSM tool for the BE88CB (TMO) variant, no TWRP, and no flashed boot images available.
Do I have this right? Rooting is impossible?
Click to expand...
Click to collapse
nah man you can actually unlock the bootloader without tmo carrier unlock and root...see my guide to do that, its as straight forward as any other oneplus, but basically you have to request the bootloader unlock code from oneplus, then assuming your carrier unlocked or use the guide to break the carrier lock functionality. If your already at that point grab the boot image for your version, store on device, root that image with magisk manager then flash it in bootloader
https://github.com/nylar357/nord_oem
nylar357 said:
nah man you can actually unlock the bootloader without tmo carrier unlock and root...see my guide to do that, its as straight forward as any other oneplus, but basically you have to request the bootloader unlock code from oneplus, then assuming your carrier unlocked or use the guide to break the carrier lock functionality. If your already at that point grab the boot image for your version, store on device, root that image with magisk manager then flash it in bootloader
https://github.com/nylar357/nord_oem
Click to expand...
Click to collapse
As you can see in my message, bootloader is unlocked.
@nylar357 How can I "grab" boot image for 11.0.2 when not rooted?
bouyakasha said:
As you can see in my message, bootloader is unlocked.
@nylar357 How can I "grab" boot image for 11.0.2 when not rooted?
Click to expand...
Click to collapse
Root N10 using Magisk
Warning: I'm not responsible for any damage or bricked phones! Mirror for all OxygenOS images General Info: You need adb and fastboot installed and should know how to use it TWRP is not needed You must do this process only once...
forum.xda-developers.com
I'm sure you can find your img files here...
??? there is a MSM tool for TMo.
[OPN105G][OOS TMO BE88CB] Unbrick tool to restore your device to OxygenOS
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...
forum.xda-developers.com
Use readback mode to get the stock root image.
Where can i get stock image for BE2025?
Need a stock image for metro pc n10 5g android 11 build 11.BE88CF so i can root. My device is now oem unlock by waiting 90 days. Cant find image on google.
forum.xda-developers.com
See last post for detailed instruction.
JazzieBoi said:
Root N10 using Magisk
Warning: I'm not responsible for any damage or bricked phones! Mirror for all OxygenOS images General Info: You need adb and fastboot installed and should know how to use it TWRP is not needed You must do this process only once...
forum.xda-developers.com
I'm sure you can find your img files here...
Click to expand...
Click to collapse
Nope. Not there for 11.0.2.BE88CB
arda99 said:
??? there is a MSM tool for TMo.
[OPN105G][OOS TMO BE88CB] Unbrick tool to restore your device to OxygenOS
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...
forum.xda-developers.com
Use readback mode to get the stock root image.
Where can i get stock image for BE2025?
Need a stock image for metro pc n10 5g android 11 build 11.BE88CF so i can root. My device is now oem unlock by waiting 90 days. Cant find image on google.
forum.xda-developers.com
See last post for detailed instruction.
Click to expand...
Click to collapse
Trying this now, thank you.
arda99 said:
??? there is a MSM tool for TMo.
[OPN105G][OOS TMO BE88CB] Unbrick tool to restore your device to OxygenOS
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...
forum.xda-developers.com
Use readback mode to get the stock root image.
Where can i get stock image for BE2025?
Need a stock image for metro pc n10 5g android 11 build 11.BE88CF so i can root. My device is now oem unlock by waiting 90 days. Cant find image on google.
forum.xda-developers.com
See last post for detailed instruction.
Click to expand...
Click to collapse
Thank you so much, this worked!!!
bouyakasha said:
Thank you so much, this worked!!!
Click to expand...
Click to collapse
So there's been an MSM download tool for the B88 this whole time while everybody was saying "there's no MSM for TMobile". ?!?!
bouyakasha said:
As you can see in my message, bootloader is unlocked.
@nylar357 How can I "grab" boot image for 11.0.2 when not rooted?
Click to expand...
Click to collapse
Use twrp
"If ever attacked by a polar bear, just remember x = r*cos(theta), y=r*sin(theta) and you can convert it into a harmless rectangular bear."
Great signature @SomeRandomGuy
Oops
you can install the global rom on both lito(metro) or billie. With or without locking the bootloader. that same process will unbrick the device as well, ive done it several times. if for some reason msm and the global rom disappeared, I do have it.
bouyakasha said:
Nope. Not there for 11.0.2.BE88CB
Click to expand...
Click to collapse
Here's one not rooted. Came from a restore package on telegram, you might check it out...it's 11.02 or 10.5.12 for restore .no msm needed...worked for me with fastboot.
##copy/pasted from telegram, I did NOT make these, just helping people save time.....oh if your on Linux run dos2unix on the bat file, you'll also have to change reboot-bootloader to reboot bootloader and set-active-slot becomes set_active a/b
**********************
I've put together two bundles to restore the OnePlus Nord N10 5G to Factory OS without the need for MSM Download Tool. One for OOS10 and one for OOS11.
Simply boot into the bootloader (Fastboot mode) and run the script! ("OnePlusNordN10_Restore.bat") (Roughly 5 minute duration to restore, give or take)
Note that all custom ROMs currently available require you to be on OOS10 in order to boot successfully. We hope to change this soon, but this is how it is for now until OnePlus properly re-syncs their Android 11 Kernel.
These are for the International variants only! If you require the European firmware, you will have to extract it's OTA payload and replace the appropriate files.
OnePlus OxygenOS 10.5.12
OnePlusNordN105G_Restore_OOS10.5.12_BE86AA
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
MD5: A5BF4C91124B75513159A8F55AEE944E
SHA-1: 57C5C87DF8CDB169076C57717A7F0F3045D361F3
OnePlus OxygenOS 11.0.2
OnePlusNordN105G_Restore_OOS11.0.2
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
MD5: 0CBA0395C8838F29B6728AF20B9CCA54
SHA-1: 160ACE7C2739027609785C5615FDB60601E824DF
Delete.
Check your OnePlus updater.
mingkee said:
Check your OnePlus updater.
Click to expand...
Click to collapse
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Scragge said:
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
S build based on Color OS and even the font changed.
I think I can deal with mine, but the most important of all, there's no player error on rooted N200 with S
Scragge said:
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
THANK YOU for posting this!! My mom purchased an N200 for the exact same reason and after the A-12 update she's having the same issues with her device. All her voice, sms, and mms transmissions go through Cricket wireless (which also uses AT&T network) She contacted OnePlus customer service and they said they'd get back to her within 48 hours. It's now been 48 hours but with it being a weekend, she's hoping to hear back from them by Monday. She went to the Cricket store yesterday and they cleaned and tried a new SIM card to see if that might fix the issue but it didn't.
While it doesn't sound like there's any fix available yet, it's helpful knowing that this issue is affecting someone else using the AT&T carrier network. Hopefully between OnePlus and the AT&T wireless carriers they'll figure out a solution sooner rather than later.
Best of luck with your devices.
The12thJuror said:
THANK YOU for posting this!! My mom purchased an N200 for the exact same reason and after the A-12 update she's having the same issues with her device. All her voice, sms, and mms transmissions go through Cricket wireless (which also uses AT&T network) She contacted OnePlus customer service and they said they'd get back to her within 48 hours. It's now been 48 hours but with it being a weekend, she's hoping to hear back from them by Monday. She went to the Cricket store yesterday and they cleaned and tried a new SIM card to see if that might fix the issue but it didn't.
While it doesn't sound like there's any fix available yet, it's helpful knowing that this issue is affecting someone else using the AT&T carrier network. Hopefully between OnePlus and the AT&T wireless carriers they'll figure out a solution sooner rather than later.
Best of luck with your devices.
Click to expand...
Click to collapse
Yeah, I called OP three times got the same promise from OPs customer service and they never got back with me. I've never dealt with a less enthusiastic company when dealing with a serious product defect. The tech support people at first acted like the didn't believe me when I described the problem. Then once I had (I think) convinced them the problem was real, their response was like "oh well, too bad, so sad". OP offered no solutions or even ideas of what to try to do to fix the problem.
Do they test anything before pushing out an update?
I had a two day window left for returning the devices for a refund so now they're gone, and I'm gone as an OP customer, I can't just do without a phone while they fumble around trying to figure out the details for some (maybe) upcoming patch.
Good devices, terrible customer service. Never settle, nope, never again.
Scragge said:
According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
Try this
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
For those of you who want to downgrade from 12 to 11, use fastboot enhanced/payload dumper, boot fastbootd, delete all of the "my_" partitions, flash android 11 ROM zip (payload.bin button). Reboot bootloader, use the command fastboot -w to initiate a factory reset, reboot recovery and wipe data (this fixes mismatching metadata/userdata partitions) reboot device and voila you're on Android 11 again. Confirmed on my converted TMobile variant.
Also T-Mobile variant got official A12 OTA with the same C.15 build number.
And AT&T doesn't play nice with OnePlus, their new sim cards will not let you use a OnePlus device at all because they are unsupported.
Travisholt92 said:
For those of you who want to downgrade from 12 to 11, use fastboot enhanced/payload dumper, boot fastbootd, delete all of the "my_" partitions, flash android 11 ROM zip (payload.bin button). Reboot bootloader, use the command fastboot -w to initiate a factory reset, reboot recovery and wipe data (this fixes mismatching metadata/userdata partitions) reboot device and voila you're on Android 11 again. Confirmed on my converted TMobile variant.
Also T-Mobile variant got official A12 OTA with the same C.15 build number.
And AT&T doesn't play nice with OnePlus, their new sim cards will not let you use a OnePlus device at all because they are unsupported.
Click to expand...
Click to collapse
Do you know where to download the A12(or at least the latest A11 update so I can update to A12 via OTA) stock firmware/update or could you upload it for the T-MO(metro) variant or show how to update OTA even when I unroot both slots the OTA still fails
Tyreethetruth said:
Do you know where to download the A12 stock firmware/update or could you upload it for the T-MO(metro) variant or show how to update OTA even when I unroot both slots the OTA still fails
Click to expand...
Click to collapse
I'll get the link scraped today. To fix OTA you have to reflash the stock build to restore avb (android verified boot / vbmeta verification). Without this being restored you can't flash OTA's using the normal methods. But once I get a link to the T-Mobile/metro update, you can use fastboot enhanced to manually upgrade like I did. I'll make a tutorial for the manual upgrade/downgrade process. I first have to downgrade from OxygenOS 12 to 11, then use the MSMtool to restore stock T-Mobile software. Easy stuff
Travisholt92 said:
I'll get the link scraped today. To fix OTA you have to reflash the stock build to restore avb (android verified boot / vbmeta verification). Without this being restored you can't flash OTA's using the normal methods. But once I get a link to the T-Mobile/metro update, you can use fastboot enhanced to manually upgrade like I did. I'll make a tutorial for the manual upgrade/downgrade process. I first have to downgrade from OxygenOS 12 to 11, then use the MSMtool to restore stock T-Mobile software. Easy stuff
Click to expand...
Click to collapse
Thank you! I been stuck on the same update like 4-5 updates ago
On this build (metro/TMobile version converted. I can't keep android auto connected. I went into developer options and selected the default to transfer files/ android auto and all the other options but it just connects for a few and then disconnected and says device unsupported.
Rooted device and using a alpine iLX-w650
Tyreethetruth said:
Thank you! I been stuck on the same update like 4-5 updates ago
Click to expand...
Click to collapse
The link to the download is literally a https link in the logcat when downloading the OTA. In case you're wondering how to manually download the zip onto a computer, that is how to get the link. If anyone else beats me to sharing the link it would save me from having to downgrade to get the link for the T-Mobile variant myself
"adb logcat > logcat.txt"
Travisholt92 said:
The link to the download is literally a https link in the logcat when downloading the OTA. In case you're wondering how to manually download the zip onto a computer, that is how to get the link. If anyone else beats me to sharing the link it would save me from having to downgrade to get the link for the T-Mobile variant myself
"adb logcat > logcat.txt"
Click to expand...
Click to collapse
So I get on computer and go on bootloader and type "adb logcat"?
Negative, while booted and after you start to download the android 12 OTA you can run the adb command to get the link while the OS is running.
https://android.googleapis.com/packages/ota-api/package/7cd89efc84e6db817ed16b59b0af3120521ab323.zip
(Shout out to @lzgmc )
I dirty flashed this (DE2118 T-Mobile/Metro) build over the leaked unlocked variant (DE2117) OxygenOS 12 build most are running and did not have to factory reset after flashing with Fastboot Enhanced.
My TMobile variant is now running the T-Mobile firmware. No downgrade required for that.
Downgrade process is download the android 11 build from OnePlus, boot fastbootd, use fastboot enhanced to delete all of the "my_" partitions, flash "payload bin" (full android 11 ota zip from OnePlus), make sure to tick ignore unknown partitions. After that is done shut the phone down and boot to fastboot/bootloader using the key combo, and flash the same payload again with ignore unknown partitions ticked. This will update the partitions that were inaccessible in fastbootd (such as modem). After this you will have to use a terminal with adb/fastboot to run "fastboot -w" this will wipe metadata(encryption key for userdata) and userdata. Reboot to recovery and perform factory reset there as well. After that you should be good to reboot to OxygenOS 11. To return to stock T-Mobile after that just use msmtool
Travisholt92 said:
Negative, while booted and after you start to download the android 12 OTA you can run the adb command to get the link while the OS is running.
https://android.googleapis.com/packages/ota-api/package/7cd89efc84e6db817ed16b59b0af3120521ab323.zip
(Shout out to @lzgmc )
I dirty flashed this (DE2118 T-Mobile/Metro) build over the leaked unlocked variant (DE2117) OxygenOS 12 build most are running and did not have to factory reset after flashing with Fastboot Enhanced.
My TMobile variant is now running the T-Mobile firmware. No downgrade required for that.
Downgrade process is download the android 11 build from OnePlus, boot fastbootd, use fastboot enhanced to delete all of the "my_" partitions, flash "payload bin" (full android 11 ota zip from OnePlus), make sure to tick ignore unknown partitions. After that is done shut the phone down and boot to fastboot/bootloader using the key combo, and flash the same payload again with ignore unknown partitions ticked. This will update the partitions that were inaccessible in fastbootd (such as modem). After this you will have to use a terminal with adb/fastboot to run "fastboot -w" this will wipe metadata(encryption key for userdata) and userdata. Reboot to recovery and perform factory reset there as well. After that you should be good to reboot to OxygenOS 11. To return to stock T-Mobile after that just use msmtool
Click to expand...
Click to collapse
Alright cool thanks for the download so just go to twrp/orangefox and install it or do I get on pc and flash it via adb? Does it have to only be fastboot enhanced?
Tyreethetruth said:
Alright cool thanks for the download so just go to twrp/orangefox and install it or do I get on pc and flash it via adb? Does it have to only be fastboot enhanced?
Click to expand...
Click to collapse
PC and flash via fastbootd then again in fastboot after fastbootd. Fastboot enhanced is the easiest way to do it, otherwise you will need to fix custom recovery to support android 12 or use command line tools to unpack the oneplus ota file to manually flash each partition.
Travisholt92 said:
PC and flash via fastbootd then again in fastboot after fastbootd. Fastboot enhanced is the easiest way to do it, otherwise you will need to fix custom recovery to support android 12 or use command line tools to unpack the oneplus ota file to manually flash each partition.
Click to expand...
Click to collapse
Gotcha, how do I go to fastbootd and fastboot? Its confusing me which one is which
Tyreethetruth said:
Gotcha, how do I go to fastbootd and fastboot? Its confusing me which one is which
Click to expand...
Click to collapse
fastboot = bootloader
Fastbootd has access to more critical partitions and can be accessed by the command "fastboot reboot fastboot" at the bootloader or by hitting the "reboot to fastbootd" button in fastboot enhanced. Make sure to flash it in fastbootd BEFORE flashing it again in fastboot
Travisholt92 said:
fastboot = bootloader
Fastbootd has access to more critical partitions and can be accessed by the command "fastboot reboot fastboot" at the bootloader or by hitting the "reboot to fastbootd" button in fastboot enhanced. Make sure to flash it in fastbootd BEFORE flashing it again in fastboot
Click to expand...
Click to collapse
Gotcha, one last thing how do I flash using fastboot enhance? Idk what to pick to flash the A12 OTA
EDIT: Nvm I extracted the update and found the payload
Magisk patched boot.img for this release: https://drive.google.com/file/d/1A2x8YbnnO6SJq-R-1rdZZ18CU673Z2-Y/view?usp=sharing