I have Lineage OS 14.1 on my phone and need to use Duo Mobile for 2 factor authentication. In spite of the fact that I have "unrooted" the system is still detecting that I a have tampered with my device. I will assume it's because the bootloader is unlocked.
I really, really don't want to wipe the phone and reconfigure all my apps (yes, it's easier than it used to be). Getting into fastboot and doing the fast relock commands is pretty clear to me, but how to get my device back to exactly where it is, but just with the bootloader locked?
Not possible.
Sent from my ZTE A2017U using Tapatalk
kendoori said:
I have Lineage OS 14.1 on my phone and need to use Duo Mobile for 2 factor authentication. In spite of the fact that I have "unrooted" the system is still detecting that I a have tampered with my device. I will assume it's because the bootloader is unlocked.
I really, really don't want to wipe the phone and reconfigure all my apps (yes, it's easier than it used to be). Getting into fastboot and doing the fast relock commands is pretty clear to me, but how to get my device back to exactly where it is, but just with the bootloader locked?
Click to expand...
Click to collapse
You can't relock unless you are fully stock (actually you can, but you'll have a brick for life)
Choose an username... said:
You can't relock unless you are fully stock (actually you can, but you'll have a brick for life)
Click to expand...
Click to collapse
I have the a2017 model. Can I flash G or U stock firmware keeping the Chinese firmware modem and relock the bootloader. Do you know whether this is possible or would work without bricking.
FuzzyDunlop9 said:
I have the a2017 model. Can I flash G or U stock firmware keeping the Chinese firmware modem and relock the bootloader. Do you know whether this is possible or would work without bricking.
Click to expand...
Click to collapse
To relock the bootloader you will need fastboot. None of the newer stock firmwares have fastboot asides from Chinese B19. You will need to EDL Flash B19 and use the Axon 7 Tool to relock the bootloader. After that, you can flash any Axon 7 firmware you'd like. Any A7 firmware works on any A7 model.
Make sure to replace the NONHLOS.bin in the files of the EDL package with the NONHLOS.bin from the Chinese firmware. This file is the modem, and so if you live in China, you will need to replace the US/EU modem file inside the package with the Chinese one.
It won't brick your phone, but it's not possible to relock the bootloader without wiping. I'd suggest a backup app such as Titanium Backup or something else (not too sure about non-root backup apps).
runninghamster said:
To relock the bootloader you will need fastboot. None of the newer stock firmwares have fastboot asides from Chinese B19. You will need to EDL Flash B19 and use the Axon 7 Tool to relock the bootloader. After that, you can flash any Axon 7 firmware you'd like. Any A7 firmware works on any A7 model.
Make sure to replace the NONHLOS.bin in the files of the EDL package with the NONHLOS.bin from the Chinese firmware. This file is the modem, and so if you live in China, you will need to replace the US/EU modem file inside the package with the Chinese one.
It won't brick your phone, but it's not possible to relock the bootloader without wiping. I'd suggest a backup app such as Titanium Backup or something else (not too sure about non-root backup apps).
Click to expand...
Click to collapse
Thanks for replying. So I flashed the A2017_B15_FULL_EDL Android: 6.0.1 onto my a2017 axon 7. I replaced the NONHLOS.bin (modem) in the edl file with the Chinese modem which I took from A2017_B15_FULL_EDL Android: 6.0.1. I'm able to get network signal and works as expected.
I can't seem to lock the bootloader. Fastboot works on this firmware but the fastboot oem lock command does nothing, I keep getting failed.
Are you suggesting I flash stock firmware, one that has fastboot commands working, designed for a2017, lock the bootloader and then using a tool like djkuz Axon 7 EDL Tool flash a2017g firmware.
The reason why I need a2017g firmware is I'm tryna sell my axon at CEX and they won't accept it cos it has Chinese software. If it has European firmware with locked bootloader it'll pass their software check.
FuzzyDunlop9 said:
Thanks for replying. So I flashed the A2017_B15_FULL_EDL Android: 6.0.1 onto my a2017 axon 7. I replaced the NONHLOS.bin (modem) in the edl file with the Chinese modem which I took from A2017_B15_FULL_EDL Android: 6.0.1. I'm able to get network signal and works as expected.
I can't seem to lock the bootloader. Fastboot works on this firmware but the fastboot oem lock command does nothing, I keep getting failed.
Are you suggesting I flash stock firmware, one that has fastboot commands working, designed for a2017, lock the bootloader and then using a tool like djkuz Axon 7 EDL Tool flash a2017g firmware.
The reason why I need a2017g firmware is I'm tryna sell my axon at CEX and they won't accept it cos it has Chinese software. If it has European firmware with locked bootloader it'll pass their software check.
Click to expand...
Click to collapse
Yeah, that's basically it.
runninghamster said:
Yeah, that's basically it.
Click to expand...
Click to collapse
Ooh so it's possible to edl flash even with a locked bootloader?
FuzzyDunlop9 said:
Ooh so it's possible to edl flash even with a locked bootloader?
Click to expand...
Click to collapse
Yep.
Related
I bought a chinese Huawei Mate 8 NXT-DL00. It is now unlocked, thanks to DC-unlocker:good:
It communicates with adb, and reboots in bootloader. For some reason adb will not flash TWRP 3.0.2.0. (or any other TWRP). Is there a known TWRP for DL00 chinese, or is it the same as AL-10?
is FRP unlocked?
No, FRP is not unlocked now, but I have unlocked in on DC before. After reboot it shows locked message in bootloader.
I see now that you mention it that it's possible to have the FRP stay unlocked. Is that necessary to flash twrp and SU?
Think City said:
No, FRP is not unlocked now, but I have unlocked in on DC before. After reboot it shows locked message in bootloader.
I see now that you mention it that it's possible to have the FRP stay unlocked. Is that necessary to flash twrp and SU?
Click to expand...
Click to collapse
In "Developer options", I do not have the "Enable OEM unlock" option. Does that mean my chinese phone does not have FRP?
Think City said:
I bought a chinese Huawei Mate 8 NXT-DL00. It is now unlocked, thanks to DC-unlocker:good:
It communicates with adb, and reboots in bootloader. For some reason adb will not flash TWRP 3.0.2.0. (or any other TWRP). Is there a known TWRP for DL00 chinese, or is it the same as AL-10?
Click to expand...
Click to collapse
The Chinese model does not have this option to Enable OEM unlock, and need not, in the Chinese versions google has less activity, which protects and blocks the device are the options of Huawei. In your case, only if you have installed the system in another model, international for example, then yes there would be this option, but it would not work. I did this idiocy, and I was blocked FRP, only the DC unlocker could release the lock. Anyway, it is not original firmware of another model, which is the version of your system? If you are in DL00C17B320 or above this, you need to downgrade to EMUI 4.0. In versions above it as the 320 for example, the system does not accept commands via fastboot. Only commands that do NOT change anything. And yes, everything works in AL10, DL00 serves in, you can install without fear ARE the same model, the difference is just the operator.
AL10 = chinese version, unlocked
TL00, DL00, CL00 = chinese versions, locked to chinese carriers
MarceloAF said:
The Chinese model does not have this option to Enable OEM unlock, and need not, in the Chinese versions google has less activity, which protects and blocks the device are the options of Huawei. In your case, only if you have installed the system in another model, international for example, then yes there would be this option, but it would not work. I did this idiocy, and I was blocked FRP, only the DC unlocker could release the lock. Anyway, it is not original firmware of another model, which is the version of your system? If you are in DL00C17B320 or above this, you need to downgrade to EMUI 4.0. In versions above it as the 320 for example, the system does not accept commands via fastboot. Only commands that do NOT change anything. And yes, everything works in AL10, DL00 serves in, you can install without fear ARE the same model, the difference is just the operator.
AL10 = chinese version, unlocked
TL00, DL00, CL00 = chinese versions, locked to chinese carriers
Click to expand...
Click to collapse
My system is DL00C17B197. I still can't flash twrp. ADB says: "error: cannot load "twrp.img"". Must I unlock the chinese carriers, or something?
Think City said:
My system is DL00C17B197. I still can't flash twrp. ADB says: "error: cannot load "twrp.img"". Must I unlock the chinese carriers, or something?
Click to expand...
Click to collapse
Forgive me for the delay, I only saw it now. I do not think so, does your mistake look like something else, the bootloader, it's unlocked?
Long story short. I had an Axon 7 A2017 B11 which I updated to B13. I was able to unlock the bootloader, root the phone then flash a custom rom Z.A.D.Mix7_v0.3. I was having fun with the phone but I did something very stupid when I realised I could not use Android pay due to unlocked boot loader. Without doing enough research, I went to fastboot and did a fastboot oem lock. The command was successful but I could no longer boot into the system or recovery or fastboot. I tried MiFlash with B07 which was posted in this forum, but it did not work, came back an error of bad format. Then I used axon7tool to flash TWRP 3.0.2 and the boot.img which I extracted from B13. I am now able to boot into TWRP and fastboot. But I still do not have a working system. I tried fastboot oem unlock, it does not let me do it. I flash ZAD Mix7 again but once I flash that it does not boot anymore. I am now really stuck. What should I do to go back to stock then start everything again. Thanks a lot for the help.
I understand your device doesn't boot into system anymore, but can adb on your pc detect it at all? If so, you can try following all steps after "B)" in my tutorial. I think your aboot img and fbop partition are messed up. If you can use adb to replace the files in aboot and fbop with files that allow the fastboot oem unlock command to be executed, it should be unlockable again. After that, custom ROMs should boot.
Stock bootloader
Controllerboy said:
If you can use adb to replace the files in aboot and fbop with files that allow the fastboot oem unlock command to be executed, it should be unlockable again. After that, custom ROMs should boot.
Click to expand...
Click to collapse
I'm having a similar issue. Although my phone boots to stock rom I seem to have messed up my bootloader. I had TWRP and unlocked bootloader. I, similarly, locked the bootloader and things seemed to be fine. After attempting to install Nougat received from OTA I realized my bootloader is corrupted. When I hold the power and volume up the phone seems to just turn off (or go to EDL mode? I'm not sure) I can always just hold power and it'll boot up normally. Is there a way to get the stock bootloader to work and keep it locked?
I also bricked my A7 after relocking my bootloader. I used tenfar's tool to make TWRP my boot.img, then flashed ZTE's stock B20 image. Here's the thread where I found the file links.
From there I updated all the way up to the OTA Nougat, but I suppose you can decide where you want to go after it's unbricked. Hope this helps.
Why are so many people relocking bl? Regardless, always take an ota before locking to ensure you are completely shock.
Stock bootloader
lafester said:
Why are so many people relocking bl? Regardless, always take an ota before locking to ensure you are completely shock.
Click to expand...
Click to collapse
Don't you have to be running a locked bootloader in order to be able to install OTAs?
aabnamak said:
Don't you have to be running a locked bootloader in order to be able to install OTAs?
Click to expand...
Click to collapse
Of course not.
aabnamak said:
Don't you have to be running a locked bootloader in order to be able to install OTAs?
Click to expand...
Click to collapse
No, you do not. I thought that was the case at first as well, but I was mistaken. You do, however, need the stock recovery and an untouched system partition.
My problem is that I don't seem to have a recovery at all. I realized once the ZTE logo pops up I can hold down both volume keys and get to the bootloader. The bootloader is locked but does not display a bootloader version or basedband version. I tried the tenfar tool (axon7root.exe) and now my phone doesn't boot into the system either. I really need help...
Just an update to everyone that helped.
I finally managed to fix it.
I used axon7tool to flash a signed TWRP, so that i can boot into TWRP. The signed TWRP is the only way to make it work. Then I downloaded the A2017 B11 from this thread
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
There are two zip files. The boot stack and the rom. Because it is a stock rom, I can boot into the system. The next thing I did was to enable the developer option and turn back on the option to allow OEM unlock.
I went back to TWRP. boot into the fastboot screen. Then I simply typed in 'fastboot oem unlock'.
I went back to TWRP, which says can't read encrypted device. I formated everything. mount the USB then flash the custom rom again.
Hola, phone fixed. Made me sweat for the whole day.
deleted...forgot I had a micro sd card. Flashed stock update from the card and it worked. Phew!
Hi all,
I am trying to re-lock my bootloader, but my fastboot commands aren't working. It says "remote error command not found."
I am running stock b19 (7.1.1) unrooted. The only thing modified is the bootloader, which is unlocked.
How do I fix this error. I installed the ADB drivers. I do not know what is causing this error. Any help will be appreciated.
TheWoerbler said:
Hi all,
I am trying to re-lock my bootloader, but my fastboot commands aren't working. It says "remote error command not found."
I am running stock b19 (7.1.1) unrooted. The only thing modified is the bootloader, which is unlocked.
How do I fix this error. I installed the ADB drivers. I do not know what is causing this error. Any help will be appreciated.
Click to expand...
Click to collapse
I think fastboot commands were disabled in b19. There's no harm in keeping it unlocked unless you're wanting to use Android Pay (in which case Magisk can hide the unlocked bootloader), or you're needing to return the phone for warranty reasons.
bluestudy said:
I think fastboot commands were disabled in b19. There's no harm in keeping it unlocked unless you're wanting to use Android Pay (in which case Magisk can hide the unlocked bootloader), or you're needing to return the phone for warranty reasons.
Click to expand...
Click to collapse
So I installed the factory image from ZTE's website, which uninstalled twrp and SuperSU (which I knew it would), but I am still unable to use fastboot commands. What might be causing this problem?
As far as I know you need to rollback and flash DrakenFX's fastboot command zip in order to be able to use fastboot again.
iNaruX said:
As far as I know you need to rollback and flash DrakenFX's fastboot command zip in order to be able to use fastboot again.
Click to expand...
Click to collapse
So I changed some settings in Windows Device Manager, now fastboot is working...kinda. I type "fastboot oem lock" and it hangs up for 5 seconds and gives me the error "FAILED (command write failed (Unknown error))...
I solve one problem, and another pops up... Thoughts?
EDIT: In regards to DrakenFX's fastboot command zip, where would I get that? Is it the full systemstock?
I read this guide for the Axon7 A2017G, but the zips used are for the A2017U.
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
The first couple of steps restore the bootloader and get fastboot commands up and running via EDL mode.
iNaruX said:
I read this guide for the Axon7 A2017G, but the zips used are for the A2017U.
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
The first couple of steps restore the bootloader and get fastboot commands up and running via EDL mode.
Click to expand...
Click to collapse
I am currently running B29 (6.0.1). Will this still work, even though I am on a different version of Android? Or should I update to B19?
Oh...if you are on MM this should work for you.
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Just flashable zip in Recovery, no need for EDL.
I'm not an A2017U though...
iNaruX said:
Oh...if you are on MM this should work for you.
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Just flashable zip in Recovery, no need for EDL.
I'm not an A2017U though...
Click to expand...
Click to collapse
Just for clarification: I am trying to LOCK my bootloader, not UNLOCK. Sorry if I've been unclear. I need to RE-LOCK my bootloader...everything else is stock (recovery, no SuperSU, etc.)
P.S. Thank you for your help, I really appreciate you taking the time.\
EDIT: AHHHHHHHHHHHHH I GOT IT!!!!! Thank you so so much!!! I really appreciate your help, you have no idea!! I followed the last guide you sent me and replaced "unlock" with "lock." You're the best, man...or woman!
TheWoerbler said:
Just for clarification: I am trying to LOCK my bootloader, not UNLOCK. Sorry if I've been unclear. I need to RE-LOCK my bootloader...everything else is stock (recovery, no SuperSU, etc.)
P.S. Thank you for your help, I really appreciate you taking the time.\
EDIT: AHHHHHHHHHHHHH I GOT IT!!!!! Thank you so so much!!! I really appreciate your help, you have no idea!! I followed the last guide you sent me and replaced "unlock" with "lock." You're the best, man...or woman!
Click to expand...
Click to collapse
Haha cheers, I think you got it, I sent that guide just to enable fastboot commands, glad it worked :good:
I need to re-lock the bootloader on my A2017U. I put in a warranty repair claim with ZTE for a dead SIM2 slot. They said if I could relock it to stock, they would not charge the $79.99 out-of-warranty fee.
My only concern with the guides above is that I'm on the RR Nougat ROM. Will any of the links above work for me?
Hi Guys,
The Axon 7 Model A2017U I just purchased has the bootloader locked and it is running LineageOS 14.1 - 2018032-Nightly-axon7. I need to relock the bootloader and get back to the stock MiFavor rom so that I can send the phone to ZTE for repair. Can you please explain to a newb in some detail how to achieve that.
Thank you.
TheBoozer said:
Hi Guys,
The Axon 7 Model A2017U I just purchased has the bootloader locked and it is running LineageOS 14.1 - 2018032-Nightly-axon7. I need to relock the bootloader and get back to the stock MiFavor rom so that I can send the phone to ZTE for repair. Can you please explain to a newb in some detail how to achieve that.
Thank you.
Click to expand...
Click to collapse
This guide should do the trick: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
soren25 said:
This guide should do the trick: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
Click to expand...
Click to collapse
Thank you very much for your help, I am now back to stock B15. The only thing left for me is to relock the bootloader.
I had hardbricked my devices while installing an OTA update and the device was Hardbricked .
I blank flashed the device and it booted and bootloader.
Now the problem starts here.
I flashed the OEM_Lock.bat as I wanted to relock the bootloader. I'm not sure what went wrong but the flash didn't complete and stuck in middle.
The problem remains here is it shows
Fastboot Reason: Failed to initialize partition table
I am unable to flash anything now. Recovery.img fails, bootloader.img fails, twrp flashing fails.
Nothing flashes as Bootloader is locked.
I went to Motorola Service Centre. They also couldn't do anything and simply said that their software doesnt read the phone.
Is there anyone whoe can really help me out with anything left to do?
Any method to force flash recovery, even twrp?
Phone is detected as Fastboot athene_16mp S in computer. It doesnt detect as "Qualcomm HS-USB QDLoader 9008".
What firmware are you attempting to flash?
Your device looks like it's still on the blank flash provided bootloader, which means you have to flash at least the GPT and bootloader. The lack of a serial number and the generic identifier implies you have not been able to flash an actual GPT and bootloader. Also, OEM_locked is normal until you get an actual bootloader flashed over the blank flash bootloader, which usually means trying to flash a GPT and bootloader at least as new as the latest version you had on your device (regardless of downgrades).
I'd suggest downloading the latest Nougat stock ROM we have from here. Do not use any of the scripts at this time.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Edit - also, this post probably is better suited to the Q and A section...
echo92 said:
What firmware are you attempting to flash?
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Click to expand...
Click to collapse
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
mysteryno46 said:
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
Click to expand...
Click to collapse
Eh, you live and learn. Besides, you've now got your device running now!
Honestly, it's up to you. Having a locked or unlocked bootloader will not affect your ability to receive OTA updates - you should still receive updates so long as your firmware matches your software channel (and since your device was XT1643, the NPJS25.93-14-18 April 2018 security update should be the correct firmware). At this moment in time, you'll have to use the NPJS25.93-14-18 firmware to re-lock your bootloader - we don't have the stock Oreo firmware at this time. Thus, if you update to stock Oreo, you will not be able to re-lock your bootloader until you can get a leak of the Oreo firmware.
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Back to Locked Bootloader, complete stock.
echo92 said:
Eh, you live and learn. Besides, you've now got your device running now!
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Click to expand...
Click to collapse
I am back to Locked Bootloader as feel the same as you said that anyone buying might get scared by looking the warning sign. Thanks for helping out. :highfive:
Oreo Update via OTA has already started rolling out as per the news I've been reading. I just wanted to see the oreo 8.1 before I sell the phone.
Anyways I got a new device now, Realme C1, 3|32GB as my smartphone usage has declined a lot recently and might remain similar. This device will suffice my requirements.
Thanks for the help and support. :victory:
Hello, I recently purchased the T-mobile version of the 6T (bad idea) that had a locked bootloader, and tried to flash it to the international version so I can root the device. I followed this post in hopes of achieving it. The device will no longer boot. The screen quickly flashes with a Oneplus logo with "fastboot mode" underneath then I am met with this error: "Build version and HW is not match!". Is it completely bricked? Can I flash back to a T-Mobile OS?
If it is truly bricked I am curious if someone could explain why it may have happened. As in, has T-Mobile changed some the checks involved with flashing to the international version? Or was it because the device was running the latest Oxygen OS, is it impossible to downgrade this way? I am genuinely curious and want to take this as a bitter learning experience.
Thanks for your input.
It depends, did you select oem unlock and usb debugging and then unlock the bootloader prior to trying to flash another rom to the device? If you successfully unlocked the bootloader, prior to messing around with flashing, then no, I doubt you hard bricked. If you did NOT unlock the bootloader, then yes, you may have hard bricked.
If you did unlock the BL, I would suggest flashing the fastboot rom for the build your currently on. Or, you could use the msm tool. Both of the above can be found in the forums for the 6t.
Pain-N-Panic said:
It depends, did you select oem unlock and usb debugging and then unlock the bootloader prior to trying to flash another rom to the device? If you successfully unlocked the bootloader, prior to messing around with flashing, then no, I doubt you hard bricked. If you did NOT unlock the bootloader, then yes, you may have hard bricked.
If you did unlock the BL, I would suggest flashing the fastboot rom for the build your currently on. Or, you could use the msm tool. Both of the above can be found in the forums for the 6t.
Click to expand...
Click to collapse
Thanks for the reply. Oem unlock and usb debugging were enabled but the bootloader was not unlocked. I was trying to avoid the 7-day wait time for the unlock bin from oneplus/tmobile.
I was able to flash back to tmobile OOS 9.0 found in this post using the v2 version. I was still able to update OTA to the latest 10.3.7.
Edit: Some_Random_Username has comented to include tmobile OOS 10.3.7
Did you get it all figured out? If not here's a semi detailed version of what I had to do with my tmobile 6t, because I had issues as well. Mainly my phone not showing up in msm tool. Only wanted to work after it had Android 9. Also I had little sleep the night I did this so I'm trying to recall the best I can.
Assuming your phone shows in msm tool at this point
Used msm tool to flashed older A9 ops https://androidfilehost.com/?fid=11410963190603895067
Boot in and enable adb and oem bootloader unlock
Boot to bootloader and unlock it
Flashed first A10 OOS https://androidfilehost.com/?fid=4349826312261819701
Flashed 10.3.7 to both slots with twrp https://androidfilehost.com/?fid=10763459528675591630
Flash rom
Flash Magisk
Profit
Some of this could be redundant, but my late night research and trial and error paid off.
GoldfishSnack said:
Thanks for the reply. Oem unlock and usb debugging were enabled but the bootloader was not unlocked. I was trying to avoid the 7-day wait time for the unlock bin from oneplus/tmobile.
I was able to flash back to tmobile OOS 9.0 found in this post using the v2 version. I was still able to update OTA to the latest 10.3.7.
Edit: Some_Random_Username has comented to include tmobile OOS 10.3.7
Click to expand...
Click to collapse
Well I'm glad you were able to get it up and running. I highly suggest unlocking that bootloader as soon as you can....having an unlocked BL is key to getting out of a lot of bricked situations.