Related
Hey everyone, I'm currently on B29, non-rooted and locked bootloader.
I would like to root and make my up to stock 7.1.1. The issue I'm having, is that there is an absolute ton of conflicting info and ways to do things that I'm just not sure at all how to proceed.
What I've tried so far was starting with this guide: https://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234. But the tool from step three wouldn't download and the hosting site threw a ton of popups and redirects at me (yes, I have uBlock).
Then continuing through that same thread I found this tool https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254 that is apparently safer, but I have no idea how to use it.
Then I started hearing about this EDL mode stuff https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514 which I attempted to do when I tried the Axon7Toolkit yesterday, but my phone just wouldn't go into EDL mode (or I just had no idea how to tell if it was or not) and the MiFlash thing didn't do anything.
So my real questions are:
1: Which version of TWRP and SuperSU do I need?
2: How do I unlock the bootloader?
3: What steps should I take so that I eventually end up rooted on stock 7.1.1 (currently still on B29)?
Thanks!
umm shouldn't this go on questions and answers?
Just one thing: You mostly can't tell if your phone is in EDL mode. Some axons will turn the notif light red, some will not do s**t, like mine. Just do whatever the guide says. On A2017G you use "adb reboot edl" and the phone just goes into EDL mode. After that you have to use axon7tool but I'm not sure if it works for nougat...
If the phone is not on EDL mode then the worst thing that can happen is that you get an error. Axon7tool doesn't do anything unless the phone is on EDL, so you pretty much can't mess up
Choose an username... said:
umm shouldn't this go on questions and answers?
Just one thing: You mostly can't tell if your phone is in EDL mode. Some axons will turn the notif light red, some will not do s**t, like mine. Just do whatever the guide says. On A2017G you use "adb reboot edl" and the phone just goes into EDL mode. After that you have to use axon7tool but I'm not sure if it works for nougat...
If the phone is not on EDL mode then the worst thing that can happen is that you get an error. Axon7tool doesn't do anything unless the phone is on EDL, so you pretty much can't mess up
Click to expand...
Click to collapse
Sorry, I thought it would go here because it was a question about the guides. I'm not sure if a mod would move this but I don't think I should repost the same question in another section?
But yeah, about the EDL, I have the U and I ran "adb reboot edl" but MiFlash didn't see anything and it wasn't showing up when I did "adb devices" so I wasn't sure what was going on. Do you have any guides or anything you'd recommend?
CookedBooks said:
Sorry, I thought it would go here because it was a question about the guides. I'm not sure if a mod would move this but I don't think I should repost the same question in another section?
But yeah, about the EDL, I have the U and I ran "adb reboot edl" but MiFlash didn't see anything and it wasn't showing up when I did "adb devices" so I wasn't sure what was going on. Do you have any guides or anything you'd recommend?
Click to expand...
Click to collapse
No access with adb or fastboot in edl mode. It' strictly for use with low level tools like miflash. Your environment will make the difference. I couldn't get miflash on my main pc (win8/x64) to see the device. Likely an issue of drivers even through the proper driver is installed, and phone is showing up properly in device mgr. I used a spare pc with a relatively fresh win10/x64 install. Miflash saw the phone right away.
Also, for edl mode, my u model will just flash the led once then go blank.
To achieve your goal, easiest to probably just unlock the bootloader with the B29, then mess around with updating to latest.
gpz1100 said:
To achieve your goal, easiest to probably just unlock the bootloader with the B29, then mess around with updating to latest.
Click to expand...
Click to collapse
Okay thanks, I'll give it a go again. Would you be able to clarify which version of TWRP I should use? I'm thinking 3.0.2-0 but I've seen other guides mention different versions and other people say the wrong version is going to be a massive headache.
For the initial unlocking, you'll have to use the signed twrp. I don't recall the exact version, but whatever is included in the unlock thread. Once unlocked, then you can flash the latest 3.1.something.
gpz1100 said:
For the initial unlocking, you'll have to use the signed twrp. I don't recall the exact version, but whatever is included in the unlock thread. Once unlocked, then you can flash the latest 3.1.something.
Click to expand...
Click to collapse
Okay thanks. As for the rest, am I correct in my understanding that I need to:
First: Use Axon7tool to flash TWRP https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Second: Unlock bootloader
Third: flash the official 7.1.1
Hmm you could use a7tool to flash TWRP, then install the twrp app and upgrade to 3.1 or whatever, and then get to nougat after some backups. I'm not sure but I think tenfar's twrp FUBAR'd some partitions when you tried to backup
Okay thanks. I think I'll give it a rest for today, I've been scouring threads since yesterday trying to get a clear picture of what to do. I think I'll spend the week researching further and give it a go next weekend.
I just miss having AdAway and CF Lumen installed on my phone. And I really want to give Substratum a try.
Thanks for all the tips and info!
Hang in there. You are on the right track. The edl thing can take a few attempts to get recognized.
Did you try the toolkit? Same as using miflash but he has direct downloads to all the necessary drivers and tools along with instructions.
lafester said:
Did you try the toolkit? Same as using miflash but he has direct downloads to all the necessary drivers and tools along with instructions.
Click to expand...
Click to collapse
There are people who are reporting that the drivers that I provide in the toolkit do not work and therefore MiFlash fails to flash packages. I am going to use new drivers in the next version(the drivers that come with the stock ROM) and then the OP should test it.
If you have to use axon7tool then you might find this useful
https://forum.xda-developers.com/showpost.php?p=71206394
But I think that the US version has a different way to root and stuff, so i wouldn't be able to help...
bkores said:
There are people who are reporting that the drivers that I provide in the toolkit do not work and therefore MiFlash fails to flash packages. I am going to use new drivers in the next version(the drivers that come with the stock ROM) and then the OP should test it.
Click to expand...
Click to collapse
Okay I think this may be my issue, this is where I get roadblocked. Thanks for the response, I'll try the new version as soon as it's available.
CookedBooks said:
Okay I think this may be my issue, this is where I get roadblocked. Thanks for the response, I'll try the new version as soon as it's available.
Click to expand...
Click to collapse
Can you try these drivers: http://drivers.softpedia.com/get/MOBILES/Others/ZTE-Handset-USB-Driver-52066111.shtml
Then test the option again and see if MiFlash will detect your device? Thank you.
Just make sure after you install them you go to C:\Windows and delete adb.exe and AdbWinApi.dll otherwise there will be two conflicting adb versions which will cause the toolkit to indefinitely hang when checking adb connectivity.
bkores said:
Can you try these drivers: http://drivers.softpedia.com/get/MOBILES/Others/ZTE-Handset-USB-Driver-52066111.shtml
Then test the option again and see if MiFlash will detect your device? Thank you.
Just make sure after you install them you go to C:\Windows and delete adb.exe and AdbWinApi.dll otherwise there will be two conflicting adb versions which will cause the toolkit to indefinitely hang when checking adb connectivity.
Click to expand...
Click to collapse
Okay, I just walked into work though. When I get home and settled this evening I'll give it a whirl and let you know what happens.
@CookedBooks I have great news for you: Thanks to one of my testers I have fixed the MiFlash issue. The problem was not with the drivers, but with MiFlash itself. So the solution was an EARLIER VERSION of MiFlash!! The next version of the toolkit will utilize the earlier version so I should no longer have to deal with this issue! Huzzahh!
bkores said:
@CookedBooks I have great news for you: Thanks to one of my testers I have fixed the MiFlash issue. The problem was not with the drivers, but with MiFlash itself. So the solution was an EARLIER VERSION of MiFlash!! The next version of the toolkit will utilize the earlier version so I should no longer have to deal with this issue! Huzzahh!
Click to expand...
Click to collapse
Did they just release a new version? The one I'm using has been ok.
If you could post which one is bad that would be great.
lafester said:
Did they just release a new version? The one I'm using has been ok.
If you could post which one is bad that would be great.
Click to expand...
Click to collapse
The one that is bad is the one in the toolkit right now. Its the EARLIER version of MiFlash that works correctly.
bkores said:
The one that is bad is the one in the toolkit right now. Its the EARLIER version of MiFlash that works correctly.
Click to expand...
Click to collapse
I used the toolkit to flash b15 full with miflash and it worked fine, however I already had miflash installed.
I want to install TWRP as my recovery I've tried at least four different versions that are listed here and a few others from other links:
https://forum.xda-developers.com/t/...p-for-oneplus-8-8-pro-unified-stable.4101313/
I'm not having driver issues anymore so I'm working with adb and fastboot fine. All commands are going through fine and I've tried flashing to recovery_a and recovery_b. Factory resetting doesn't resolve the issue. Every walkthrough I find I get to says flash then boot to TWRP but every time I flash it qualcomm dumps and every time I boot to it it qualcomm dumps.
Is there something corrupted in my recovery I need to wipe somehow? If so how do I wipe it because the only command I found online that would run was fastboot -w and that didn't fix the issue either.
Honestly really annoying at this. This is my 4th OnePlus phone and I've never had so many issues flashing it.
Edit:
I have also tried to do whatever steps are needed to go back to base stock and OS and it doesn't seem to work either. Any help would be appreciated.
Edit 2:
I did it. For anyone who finds this thread in the future the MSM tool did finally work. This is the video I used in the end
(I muted it.) and the first few starts it failed. I went into the properties of the MSM exe and under compatibility checked ran as admin. I also did install the qualcomm driver at some point way before this so not sure if that helped. The MSM tool still didn't work until I started it, turned my phone off, held both volume buttons (not the power) while plugging the phone in. All the stuff online I saw had people starting the program at this point but mine had started already and was in a "waiting for device" state when it worked.
What a lifesaver. Won't be messing around with this again until TWRP is available.
Because you are unable to flash phone's Stock ROM take phone to authorized service center and let them fix it.
Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Edit: not
Lossyx said:
Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Click to expand...
Click to collapse
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.
TheFloppyDisk said:
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.
Click to expand...
Click to collapse
Meant to say it's **not** compatible with Android 11 yet.
Lossyx said:
Meant to say it's **not** compatible with Android 11 yet.
Click to expand...
Click to collapse
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.
TheFloppyDisk said:
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.
Click to expand...
Click to collapse
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch
Lossyx said:
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch
Click to expand...
Click to collapse
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.
TheFloppyDisk said:
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.
Click to expand...
Click to collapse
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though
Lossyx said:
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though
Click to expand...
Click to collapse
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.
TheFloppyDisk said:
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.
Click to expand...
Click to collapse
It is very sensitive to which USB port you use. For some people only USB2.0 works, for me USB3 works fine as long as it's chipset USB3. The second ASMedia controller doesn't work.
Also, use original cable, and switch off the phone completely, get MSM to the point it's waiting for device so start the download before connecting phone, then while holding the volume keys connect the USB cable and it should instantly start flashing.
My OP6T had Ubuntu Touch (equivalent to Android 9) installed on it. When it broke, I tried to flash TWRP (version 3.3.1) to clear and reinstall Ubuntu Touch. For some reason it wouldn't boot, so I foolishly decided to flash TWRP onto every single partition. This only succeeded in breaking recovery mode. Following some advice I used the 6T MsmDownloadTool v4.0.58 (OOS v9.0.11), which fixed recovery mode, but not Android - it just showed the booting animation in a infinite loop (bootloop).
I've attached an image I found online showing the screen: bootloop
The issue is that I cannot flash in fastboot mode as the bootloader was relocked by MsmDownloadTool, *and* I cannot get into Android to enable OEM mode/USB debugging. I seem to have encountered a paradox where fastboot mode requires the permissions to be enabled in Android, but I can't boot to Android to enable those permissions, nor can I flash anything else to fix Android.
Is this possible to solve?
AOnePlus6TDestroyer said:
My OP6T had Ubuntu Touch (equivalent to Android 9) installed on it. When it broke, I tried to flash TWRP (version 3.3.1) to clear and reinstall Ubuntu Touch. For some reason it wouldn't boot, so I foolishly decided to flash TWRP onto every single partition. This only succeeded in breaking recovery mode. Following some advice I used the 6T MsmDownloadTool v4.0.58 (OOS v9.0.11), which fixed recovery mode, but not Android - it just showed the booting animation in a infinite loop (bootloop).
I've attached an image I found online showing the screen: bootloop
The issue is that I cannot flash in fastboot mode as the bootloader was relocked by MsmDownloadTool, *and* I cannot get into Android to enable OEM mode/USB debugging. I seem to have encountered a paradox where fastboot mode requires the permissions to be enabled in Android, but I can't boot to Android to enable those permissions, nor can I flash anything else to fix Android.
Is this possible to solve?
Click to expand...
Click to collapse
You can try booting with the twrp.img. "fastboot boot name.img" using that ADB command. If that does not work the only other option is to completely retore your phone using msmdownload tool. This method will also depend on whether you have the international version or the T-Mobile version as there are different approaches depending on the type of phone. Read and study carefully how to proceed. If the msm tool does not work I'm pretty damn sure there are no other options.
rogerrulez said:
You can try booting with the twrp.img. "fastboot boot name.img" using that ADB command. If that does not work the only other option is to completely retore your phone using msmdownload tool. This method will also depend on whether you have the international version or the T-Mobile version as there are different approaches depending on the type of phone. Read and study carefully how to proceed. If the msm tool does not work I'm pretty damn sure there are no other options.
Click to expand...
Click to collapse
He can't boot into anything with bootloader locked. This is why msm tool sucks and people should stop recommending it for any little problem.
Only option now is to use msm tool again and hopefully get something working
Even with the bootloader locked you still should be able to boot the recocery image.
I have the 6T and 7T Pro. When I messed up my 6T my only hope was the msmdownloadtool. But make sure it's the right one.
When I had to use the msm download tool it did lock the bootloader. But I was able to unloack it again from the ADB command prompt at the bootloader screen by typing fastboot oem unlock. But this can only be done if it is set in developer options.
I spent alot of time trying to figure it out but later found outthat I was using the wrong msm tool.
Good luck. I hope you get it and running again because the 6T is still a very good phone.
Brettroth said:
He can't boot into anything with bootloader locked. This is why msm tool sucks and people should stop recommending it for any little problem.
Click to expand...
Click to collapse
Are there more suitable tools for fixing a broken recovery mode? It did successfully do that.
rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
How?
rogerrulez said:
When I had to use the msm download tool it did lock the bootloader. But I was able to unloack it again from the ADB command prompt at the bootloader screen by typing fastboot oem unlock. But this can only be done if it is set in developer options.
I spent alot of time trying to figure it out but later found outthat I was using the wrong msm tool.
Good luck. I hope you get it and running again because the 6T is still a very good phone.
Click to expand...
Click to collapse
Thank you! And yes, I tried that command but it is probably unset in the developer options (which I cannot reach, as Android isn't working anymore). I guess I'm using the incorrect version - how do you identify the correct one? I think I've used both the T-Mobile one and the other. I don't think the phone is T-Mobile, but I'm not sure how to identify whether it is or not.
It is very easy to convert a t-mobile variant to the international version. If you bought the phone used you would not know. One tell tale sign could be if you sim card holder supports either one or 2 sims. But that's not a sure way either because you can buy a replacement sim card holder. The fastet was would be to look up the IMEI # and see what variant of the 6 you have.
As for the msm tool you would needd a modified version of that tool. You first use it to downgrade to Android 9. Then you have to upgrade that verion of android 9 to a slightly higher version before you are able to fully upgrade feely to 10 than 11 if you wanted.
If you have the international version pretty much and version of the msm tool would work but a modified version would be best.
However, the first step is to find out which variant you have.
When you used the msmdownload tool which version did you use, and did it finish the job ?
If you have the t-mobile vesion there is a thread on here that gives you step by step instructions to convert from t-mobile to international along with the links to download the software. And even the modified version will know what variant you have simply by not working.
If you are able to get into the bootloader than you have a great chance of fixing your phone. Your phone is bootlooping so that tells me you can access the bootloader screen.
When I bricked mine I thought it was gone forever, I spent several days working on it but I was able to restore it. But I would never use the ubuntu rom on any phone that I care for.
When you are at this level it is very important you proceed with caution and don't just start flashing anything you can find. It will nake matters much worse.
rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
Wasn't sure about that. If that's the case, can you also flash from twrp then?
Brettroth said:
Wasn't sure about that. If that's the case, can you also flash from twrp then?
Click to expand...
Click to collapse
No. Not without an unlocked bootloader. But booting into twrp would give you the ability to flash a ROM tho.
rogerrulez said:
No. Not without an unlocked bootloader. But booting into twrp would give you the ability to flash a ROM tho.
Click to expand...
Click to collapse
That's what I meant. Flash a ROM from twrp. Ok so if that works this guy can fix everything from there. Gonna be a hassle tho. Instead of rebooting to recovery I think you would have to shut off phone and fastboot boot back into twrp to change slots right?
Somehow I feel like that won't work but I'm not locking my bootloader to test it
rogerrulez said:
The fastet was would be to look up the IMEI # and see what variant of the 6 you have.
Click to expand...
Click to collapse
I'm afraid I can't' find it... It is dual-sim though.
rogerrulez said:
When you used the msmdownload tool which version did you use, and did it finish the job ?
Click to expand...
Click to collapse
I used a few - both T-Mobile and not. They all succeeded with (seemingly) no error, but didn't fix the bootloop.
rogerrulez said:
If you have the t-mobile vesion there is a thread on here that gives you step by step instructions to convert from t-mobile to international along with the links to download the software. And even the modified version will know what variant you have simply by not working.
Click to expand...
Click to collapse
I see, but won't that need me to be in Android to be able to run the software?
rogerrulez said:
If you are able to get into the bootloader than you have a great chance of fixing your phone. Your phone is bootlooping so that tells me you can access the bootloader screen.
Click to expand...
Click to collapse
Yup, fastboot and recovery mode work fine. The bootloader is locked though, else installing TWRP, etc. would be easy.
rogerrulez said:
When you are at this level it is very important you proceed with caution and don't just start flashing anything you can find. It will nake matters much worse.
Click to expand...
Click to collapse
Yeah...
rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
It doesn't do it automatically. Is there another way to boot it?
Brettroth said:
Somehow I feel like that won't work but I'm not locking my bootloader to test it
Click to expand...
Click to collapse
As far as I can tell there's no way to flash TWRP without unlocking the bootloader. And there doesn't seem to be any way to do that without getting into Android. And I can't get into Android...
Someone else suggested using this tool (https://github.com/bkerler/edl) as a last-ditch attempt. I'm going to give it a try and hope for the best!
Thank you both for your suggestions.
Hello all,
I am trying to help my son fix some of his Oneplus 6t phones. Please bear with me as I am not the most tech savvy. He uses the phones for a business and I like to try to help out.
He has 5 Oneplus 6t devices, 3 are stuck in fastboot and 2 went into qualcomm crash dump errors. These issues happened when he tried to install a custom rom, Arrow OS.
I wanted to help him factory restore the phones so that we could try again. I downloaded the following:
1) Oneplus 6t USB drivers - https://oneplususbdrivers.com/oneplus-6t-usb-driver-download/
2) Qualcomm USB drivers - https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3) A decrypted Oxygeon OS MSM download tool - https://www.thecustomdroid.com/oneplus-6-6t-unbrick-guide/
We ran the MSM tool as administrator and plugged in the phone with a black screen, while holding the up and down volume button. Only sometimes it was recognized / connected. When we clicked start in the MSM tool, I ran into a few potential issues.
1) Image files do not match device
2) Waiting for device (just keeps counting)
Also, often the device was not recognized, and we could not get it to work.
In the device manager, it does not show the correct device. It gives some error / device not recognized issue. I am not sure if this is related. I tried re-installing the drivers, as well as trying on a second computer. The cable we are using is able to detect non-corrupt Oneplus 6t devices fine, so I do not believe that is the issue. Also an important note, some of the devices may be T-mobile branded but I am not sure which, if any.
Does anyone know what are the next steps or things I can try? I would really like to get these devices working for him so he can continue with his business. Sadly I cannot afford to replace or rebuy the devices. I fear I am making a simple mistake somewhere but am not sure where.
Thanks for your help in advance.
It's highly likely you may need the Verizon version of the factory image you can reset with MSM Tool
Do NOT Use the patched version of the MSM Tool unless you are sure you are flashing a correct compatible image with your phone
Following what I have written here to install the correct drivers may help you
[Fix] [Guide] Device not showing in Fastboot or MSM Tool (Windows)
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who...
forum.xda-developers.com
HelpOneplus6t said:
Hello all,
I am trying to help my son fix some of his Oneplus 6t phones. Please bear with me as I am not the most tech savvy. He uses the phones for a business and I like to try to help out.
He has 5 Oneplus 6t devices, 3 are stuck in fastboot and 2 went into qualcomm crash dump errors. These issues happened when he tried to install a custom rom, Arrow OS.
I wanted to help him factory restore the phones so that we could try again. I downloaded the following:
1) Oneplus 6t USB drivers - https://oneplususbdrivers.com/oneplus-6t-usb-driver-download/
2) Qualcomm USB drivers - https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3) A decrypted Oxygeon OS MSM download tool - https://www.thecustomdroid.com/oneplus-6-6t-unbrick-guide/
We ran the MSM tool as administrator and plugged in the phone with a black screen, while holding the up and down volume button. Only sometimes it was recognized / connected. When we clicked start in the MSM tool, I ran into a few potential issues.
1) Image files do not match device
2) Waiting for device (just keeps counting)
Also, often the device was not recognized, and we could not get it to work.
In the device manager, it does not show the correct device. It gives some error / device not recognized issue. I am not sure if this is related. I tried re-installing the drivers, as well as trying on a second computer. The cable we are using is able to detect non-corrupt Oneplus 6t devices fine, so I do not believe that is the issue. Also an important note, some of the devices may be T-mobile branded but I am not sure which, if any.
Does anyone know what are the next steps or things I can try? I would really like to get these devices working for him so he can continue with his business. Sadly I cannot afford to replace or rebuy the devices. I fear I am making a simple mistake somewhere but am not sure where.
Thanks for your help in advance.
Click to expand...
Click to collapse
Did you figure it out?
FireRattus said:
It's highly likely you may need the Verizon version of the factory image you can reset with MSM Tool
Do NOT Use the patched version of the MSM Tool unless you are sure you are flashing a correct compatible image with your phone
Following what I have written here to install the correct drivers may help you
[Fix] [Guide] Device not showing in Fastboot or MSM Tool (Windows)
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi, thank you for your response.
I'm not sure the issue you had is the same as mine. My Oneplus 6T does not show up in the device manager at all.
I tried doing the unsigned device drivers thing, but when I select the folder that contains the onplus_android_winusb folder, it says it cannot find the drivers.
Sadly I think I have to give up on this one I am not very tech savvy and really don't know what else I can do.
I was able to fix one of the phones. I tried using fajita_41_J.50_210121 as my MSM recovery and it worked.
The fact that it worked implies to me my issue doesn't lie with the drivers, but rather which MSM file I am using, is this a good assumption?
If so, how can I figure out which files to use? I tried that same file on the 4 other phones, but would always get Sahara communication error.
HelpOneplus6t said:
I was able to fix one of the phones. I tried using fajita_41_J.50_210121 as my MSM recovery and it worked.
The fact that it worked implies to me my issue doesn't lie with the drivers, but rather which MSM file I am using, is this a good assumption?
If so, how can I figure out which files to use? I tried that same file on the 4 other phones, but would always get Sahara communication error.
Click to expand...
Click to collapse
This is what I was trying to say, you probably have the Verizon version, you need to make absolutely sure the MSM recovery files you are using are for that phone model
I bought my phone as global but they sent me a unlocked Verizon model, I found out because I couldn't flash it with MSM tool until I used the Verizon versions files
FireRattus said:
This is what I was trying to say, you probably have the Verizon version, you need to make absolutely sure the MSM recovery files you are using are for that phone model
I bought my phone as global but they sent me a unlocked Verizon model, I found out because I couldn't flash it with MSM tool until I used the Verizon versions files
Click to expand...
Click to collapse
Hi,
I believe you are right, that makes sense.
I see that the 1 phone that was fixable is very slightly different than the other 4- it doesn't have an IMEI code on the back, so likely it was a different version or something.
Where do I find the right recovery files? I searched for Verizon Oneplus 6t MSM Download Tool but I don't see anything different.
Sorry for my incompetence, I appreciate your help
I was able to fix a few more phones using the Tmobile 9.0.13 MSM Tool here:
[TOOL] T-Mobile OnePlus 6T MSMDownloadTool [Firmware 9.0.13] [8/9]
Okay folks, took forever to find, but we finally have it, the T-Mobile OnePlus 6T MSMDownloadTool, your brick savior, bootloader relocker, among other things, I will include a basic faq at the end. Requirements: 1. Windows PC 2. OnePlus 6T -...
forum.xda-developers.com
2 of the phones didn't work, they have Sahara communication errors still. I am not sure how to locate the right MSM tools for these- any ideas?
Furthermore, I flashed 9.0.13 from the MSM tool, but I would like to update to specifically 10.3.11, how can I do that?
HelpOneplus6t said:
Furthermore, I flashed 9.0.13 from the MSM tool, but I would like to update to specifically 10.3.11, how can I do that?
Click to expand...
Click to collapse
That is the same version I flash with MSM Tool I think
You should follow the instructions here for the Verizon version https://forum.xda-developers.com/t/guide-sim-unlock-t-mobile-version-all-type-of-imei-supported.3915269/
You can unlock the verizon variant by using a custom patched MSM Tool
After you have followed those instructions to have it unlocked on the international version rom
Then you are able to just flash the Normal OOS Flashable Update Zips via TWRP or the built in updater
Download them here https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3865396/
This allows you to update to the latest OOS 10 or 11
I really don't know about your other phones, Are they definitely OnePlus 6Ts ? I am only aware of the global and verizon variants, so if it's not either of those, I am not sure it's a OnePlus 6T
I managed to fix them by flashing the T-mobile version. This worked, but then I needed to unlock them since they were T-mobile locked. I converted them to the international version earlier successfully.
I am on 9.0.11 stock now! All I need to do really is update to 10.3.11
I will try following the links you have provided.
They are definitely 6ts
Thanks for your continued help.
FireRattus said:
That is the same version I flash with MSM Tool I think
You should follow the instructions here for the Verizon version https://forum.xda-developers.com/t/guide-sim-unlock-t-mobile-version-all-type-of-imei-supported.3915269/
You can unlock the verizon variant by using a custom patched MSM Tool
After you have followed those instructions to have it unlocked on the international version rom
Then you are able to just flash the Normal OOS Flashable Update Zips via TWRP or the built in updater
Download them here https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3865396/
This allows you to update to the latest OOS 10 or 11
I really don't know about your other phones, Are they definitely OnePlus 6Ts ? I am only aware of the global and verizon variants, so if it's not either of those, I am not sure it's a OnePlus 6T
Click to expand...
Click to collapse
Hi,
I tried downloading the 10.3.11 OS from the provided link and doing a local upgrade, but it said that it failed.
I tried doing an upgrade first to 9.0.17 (I read somewhere this would help), which was successful. I then tried going to 10.3.11 but it failed. I went to 10.0 which worked. Do you know how I can get to 10.3.11? Is there a certain order of "mandatory" updates I need to do first? I'm not too keen on local upgrading every single increment since there are a lot.
HelpOneplus6t said:
Hi,
I tried downloading the 10.3.11 OS from the provided link and doing a local upgrade, but it said that it failed.
I tried doing an upgrade first to 9.0.17 (I read somewhere this would help), which was successful. I then tried going to 10.3.11 but it failed. I went to 10.0 which worked. Do you know how I can get to 10.3.11? Is there a certain order of "mandatory" updates I need to do first? I'm not too keen on local upgrading every single increment since there are a lot.
Click to expand...
Click to collapse
Yes you are right but you do not need to download Every single update
I have found that these are the files I need to upgrade, I keep them saved for easy access
Code:
1-OnePlus6TOxygen_34_OTA_024_all_1909112343_d5b1905(9.0.17).zip
2-OnePlus6TOxygen_34_OTA_047_all_2007171912_ac6dc9b(10.3.5).zip
3-OnePlus6TOxygen_34.J.48_OTA_048_all_2010042240_dbd576b615(10.3.6).zip
4-OnePlus6TOxygen_34.J.55_OTA_055_all_2107132253_b2cbbb97b4eee(10.3.12).zip
If you wanted 10.3.11 instead of 10.3.12, I don't see why that wouldn't work
These are all the full upgrade zips, but if you have a locked bootloader and use the official update method through the settings, I have been able to use the smaller OnePlus6TOxygen_34.J.55_OTA_048-055_patch_2107132253_b96081(10.3.6-10.3.12).zip Upgrade Zip to go from 10.3.6 to 10.3.12
HelpOneplus6t said:
Hi,
I tried downloading the 10.3.11 OS from the provided link and doing a local upgrade, but it said that it failed.
I tried doing an upgrade first to 9.0.17 (I read somewhere this would help), which was successful. I then tried going to 10.3.11 but it failed. I went to 10.0 which worked. Do you know how I can get to 10.3.11? Is there a certain order of "mandatory" updates I need to do first? I'm not too keen on local upgrading every single increment since there are a lot.
Click to expand...
Click to collapse
I have actually found from testing that I did not need to flash the 10.3.5 or 10.3.6 Zips and could go from 9.0.17 to 10.3.12 if I used the full flashable update zips
so I am not sure why it failed for you
You are so awesome, thank you that worked flawlessly (the 4 separate upgrades). Throughout this thread I was able to:
Go from a soft bricked device, use the Tmobile MSM download tool to restore it, use a normal MSM download tool to convert it to the international variant, then upgrade it to 10.3.11.
My last question is regarding root, we are looking to root the device with magisk/twrp. I haven't done it in a few years so am a bit rusty on the process. It is a Oneplus 6t on 10.3.11, do you know where I can find the relevant files?
I see the latest fajita (oneplus 6t) files here: https://dl.twrp.me/fajita/
I'm a bit hesitant to use them because:
1) I'm not sure if I should use the latest ones, or an older version. I think I tried using the latest ones for something before and it messed something up.
2) I see people post online that I may need Enchilada files instead, even though that is for the Oneplus 6t, or that I need a mauronofrio twrp file instead, so I would prefer to wait for a decisive answer.
Thanks again for your help, you saved the day and my son is so elated
HelpOneplus6t said:
You are so awesome, thank you that worked flawlessly (the 4 separate upgrades). Throughout this thread I was able to:
Go from a soft bricked device, use the Tmobile MSM download tool to restore it, use a normal MSM download tool to convert it to the international variant, then upgrade it to 10.3.11.
My last question is regarding root, we are looking to root the device with magisk/twrp. I haven't done it in a few years so am a bit rusty on the process. It is a Oneplus 6t on 10.3.11, do you know where I can find the relevant files?
I see the latest fajita (oneplus 6t) files here: https://dl.twrp.me/fajita/
I'm a bit hesitant to use them because:
1) I'm not sure if I should use the latest ones, or an older version. I think I tried using the latest ones for something before and it messed something up.
2) I see people post online that I may need Enchilada files instead, even though that is for the Oneplus 6t, or that I need a mauronofrio twrp file instead, so I would prefer to wait for a decisive answer.
Thanks again for your help, you saved the day and my son is so elated
Click to expand...
Click to collapse
I am glad I could help and I do understand the hesitation, it is smart to be careful and not flash the wrong recovery file, the only time I have truly bricked a phone was by flashing the wrong recovery
I use the fajita twrp from the official source that you linked but the version you want to use does depend on your android version
You can get a crash dump error by using the latest TWRP on older OOS
I have been using Jaguar ROM for the OnePlus6T
My own installation process is as follows and WILL WIPE ALL DATA ON THE PHONE
Assuming you are coming from Latest Official OOS 10 (10.3.12)
Enable Developer mode and OEM Unlocking (In the Hidden Developer Settings)
(Optionally enable USB Debugging to adb reboot to bootloader)
(You may have to Disable Driver Signature Enforcement on Windows 10/11 to install correct drivers)
Reboot your phone to Fastboot by holding volume up and down during power up or with "adb reboot bootloader" in terminal, allowing the connection on your phone.
In Terminal
fastboot flashing unlock
FastBoot to TWRP 3.5.2
fastboot boot twrp.img
Install TWRP 3.5.2 .zip and Reboot to TWRP
WIPE Data Factory Reset and type YES to confirm and Reboot to TWRP
Flash the ROM and then flash TWRP 3.5.2
Reboot to TWRP Again
Flash ROM again then TWRP again
Reboot once then flash magisk etc via twrp
The process is more simple to just install magisk on stock OOS and I hope soon Jaguar will update to android 12, then the latest twrp should work with it
You will of course also need to have the android platform tools installed
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Worst case scenario I have found with OP6T, like not able to boot into recovery or anything
I can just do a factory flash with MSM tool using the patched version and then follow the above steps again
Everything is working, thanks so much for your help- I will pay it forward.
Hi everybody. I downloaded IN 2025_11_C.16 https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315 via fastboot uploaded to my Oneplus 8 pro. After the reboot, my phone turned off and didn't turn on. I tried all kinds of inclusion methods. The phone is not responding.
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
You all are flashing wrong xbl img. Wrong ram versions
what do u mean xbl img? I remember I have read about the ram versions but I think it wasn't the 8 pro...
duxler said:
Hi everybody. I downloaded IN 2025_11_C.16 https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315 via fastboot uploaded to my Oneplus 8 pro. After the reboot, my phone turned off and didn't turn on. I tried all kinds of inclusion methods. The phone is not responding.
Click to expand...
Click to collapse
jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
Im am sorry for you guys but you hard bricked your phones for real.
The only thing you can do now is to replace the motherboard.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
jimger said:
Similar to that, I upgraded to C35, went fine, but then tried to fastboot boot latest twrp. Got corrupted. Tried to flash/boot stock boot. NOthing. Same with patched boot. The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all... Phone is dead. Can't be recognized as usb from windows, or any sign of charging even with warp charger
Click to expand...
Click to collapse
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11
AkayamiShurui said:
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11
Click to expand...
Click to collapse
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.
xtcislove said:
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.
Click to expand...
Click to collapse
Unfortunately that's the case...
jimger said:
Unfortunately that's the case...
Click to expand...
Click to collapse
Im sorry for you. Thats an expensive lesson to learn from. If you are lucky you get a free replacement depending on the rules of your country etc. Im from germany and i guess i would get a free replacement here. Anyway if not and you search for a good phone, i recently bought the onepplus nord ce 2 for around 200€ on amazon. Its a decent phone and my dad is happy with it.
xtcislove said:
Im sorry for you. Thats an expensive lesson to learn from. If you are lucky you get a free replacement depending on the rules of your country etc. Im from germany and i guess i would get a free replacement here. Anyway if not and you search for a good phone, i recently bought the onepplus nord ce 2 for around 200€ on amazon. Its a decent phone and my dad is happy with it.
Click to expand...
Click to collapse
Hopefully will get it here too(UK). Will see. Stupid thing is that it is almost new. Less than 6 months from new. But what's worse, is that now left without phone and signal reception for some days... The bad thing of not having any spare phone...
jimger said:
Hopefully will get it here too(UK). Will see. Stupid thing is that it is almost new. Less than 6 months from new. But what's worse, is that now left without phone and signal reception for some days... The bad thing of not having any spare phone...
Click to expand...
Click to collapse
Thats a bummer for sure. Im glad i keep my "old" P30 Pro and im using AutoSync to mirror my 8 Pro to the P30 Pro which is at home so if anything happens i still have all my data.
xtcislove said:
Thats a bummer for sure. Im glad i keep my "old" P30 Pro and im using AutoSync to mirror my 8 Pro to the P30 Pro which is at home so if anything happens i still have all my data.
Click to expand...
Click to collapse
Yeah tbh I have every photo etc backed up. Also run my daily swiftkey backup before updating. But the big big bummer now is that I have no way to restore banking apps to tablet atm... Anyway let's hope at least they replace it...
As I understand it, the phone can be thrown away
how will Qualcomm ® Package Manager help if the computer does not see the device.
AkayamiShurui said:
You can't kill the phone that way, try making and Qualcomm Id and use the Qualcomm packager manager to get the tools needed for windows 7,8,10,11
Click to expand...
Click to collapse
duxler said:
As I understand it, the phone can be thrown away
Click to expand...
Click to collapse
Tbh at least I hope they replace it... For now found an Mi A1 from a friend...
I know this topic has been brought up before. But there is not always a half and full explanation.I have Oneplus 8 pro too. I can't enter recovery mode. Boots into fastboot. I've printed a wide variety of msm tools files from edl. It writes smoothly, but when opening the boot screen, it says "your device is corrupted it cannot be trusted and may not work properly" and does not open. What could be the reason? Android 10 11 msm roms, Coloros Hydrogenos all but all tried. There is no recovery. I can't open the oem lock, I can't do anything.
xtcislove said:
"The followed instructions to flash everything. Flashed ok. But after fastboot reboot, doesn't turn on at all..."
He flashed everything which usually means you flash all images extracted from payload.bin and this means you flash xbl.img and xbl_config.img too. But are supposed to be flashed on 8 only (ddr4 ram) only and will kill 8pro/8t/9r (ddr5).
I wish i am wrong but if he flashed ALL via fastboot this is what happend.
Click to expand...
Click to collapse
Not true oh I know this because I did that as well flashing the wrong ram but I was curious when time and plugged one of my Samsung phones into it and they were able to go into file transfer mode winning the phone is running the problem is getting it picked up with the right driver setup according to know I have read on Qualcomm forms it seems like it's a set of drivers not just an individual one if the device is at the point where it doesn't get to the EDL mode. You can get the signed version of the qualcomm drivers off their website using the qualcomm package manager
AkayamiShurui said:
Not true oh I know this because I did that as well flashing the wrong ram but I was curious when time and plugged one of my Samsung phones into it and they were able to go into file transfer mode winning the phone is running the problem is getting it picked up with the right driver setup according to know I have read on Qualcomm forms it seems like it's a set of drivers not just an individual one if the device is at the point where it doesn't get to the EDL mode. You can get the signed version of the qualcomm drivers off their website using the qualcomm package manager
Click to expand...
Click to collapse
Im sorry my friend i dont understand your post.
xtcislove said:
Im sorry my friend i dont understand your post.
Click to expand...
Click to collapse
If your got discord I can show you
duxler said:
As I understand it, the phone can be thrown away
Click to expand...
Click to collapse
Hold up. I'm looking for a dead OP8 Pro. I have started a conversation with you; check notification.