Related
I am having trouble finding a root method for this phone
, Or even just some news about development. Anyone point the way?
i have the same question. Anyone have any information?
It's kinda like a bum deal right now. I got two ZTE devices no root. Upset I can't disable all these google apps
Sent from my Z971 using Tapatalk
Same. Waiting for ZTE 971 root.
What is needed to get the process started to Root the ZTE Blade Spark z971
CharmedWhovian said:
What is needed to get the process started to Root the ZTE Blade Spark z971
Click to expand...
Click to collapse
Nobody knows yet
Sent from my ZTE Z971 using XDA Labs
Anybody has ROM or smth else for this phone?
Frp for blade spark?
I have had now about 4 or 5 newer ZTE phones. What I have come across is that none were able to be rooted. I posted a few requests, no one here took on the task. I don't know if it is that they can't be rooted or its just to hard for someone to do. Either way I have gotten away from buying ZTE phones for this reason.
Did anyone try to unlock the bootloader?
Code:
adb reboot bootloader
fastboot oem unlock
AT&T shows that there have been multiple OTA updates for this phone, and the last one early Jan 2018 was over 500mb. It should not be hard to port TWRP if we have an unlocked bootloader.
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1217955?make=ZTE&model=ZTEZ971
sparkie420 said:
I am having trouble finding a root method for this phone
, Or even just some news about development. Anyone point the way?
Click to expand...
Click to collapse
Nope, fastboot is removed on ZTE Nougat devices
It looks like they figured out ways around this for the Axon7, using EDL mode, but I tried a few things (including axon7tool, and the flashable zip to enable fastboot) without any luck.
I'll keep digging but it doesn't look too promising.
ZTE has our kernel sources at http://opensource.ztedevice.com [ZTE Z971 Nougat(7.1.1) Kernel(3.18.31)]
Won't do us much good without an unlocked bootloader though..
Anyone know if you can use MiFlash to flash in EDL mode without an unlocked bootloader?
aslezak said:
Did anyone try to unlock the bootloader?
Code:
adb reboot bootloader
fastboot oem unlock
AT&T shows that there have been multiple OTA updates for this phone, and the last one early Jan 2018 was over 500mb. It should not be hard to port TWRP if we have an unlocked bootloader.
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1217955?make=ZTE&model=ZTEZ971
Click to expand...
Click to collapse
TWRP for ZTE 791
Here is a Z971 TWRP I compiled for our device.
Any brave soul want to flash it using QPST or using one of the other methods in this post? Unbrick All Qualcomm
You'll need to rename it to recovery.img first. If you have to choose a firehose, choose prog_emmc_firehose_8917_ddr.mbn
Supposedly you can flash even with a locked bootloader :good:
aslezak said:
Here is a Z971 TWRP I compiled for our device.
Any brave soul want to flash it using QPST or using one of the other methods in this post? Unbrick All Qualcomm
You'll need to rename it to recovery.img first. If you have to choose a firehose, choose prog_emmc_firehose_8917_ddr.mbn
Supposedly you can flash even with a locked bootloader :good:
Click to expand...
Click to collapse
I'll do it man just message me details on how to
I was going to try & backup all the partitions using QPST, but it seems you need to get the phone into 9006 mode. We can only get into 9008 mode [Qualcomm HS-USB QDLoader 9008] with "adb reboot edl" (emergency download mode). Holding down Vol+/Vol-/Power from EDL will get you into yet another mode, ZTE Handset Diagnostic (DFU) mode, but I couldn't figure out how to do anything from here with QPST.
The only way to get the phone into 9006 mode is to brick the bootloader, which I'm not willing to do at the moment. Supposedly you can use the "axon7tool -d" and it will try to write to your bootloader & boot, but it just crashed when I tried to do it.
The other way to get into 9006 mode is to flash an mbn and another file, but I believe those are device specific, and we don't have those..
Anyway, does anyone have a phone that wasn't updated to the latest Z971V1.0.0B20 firmware? It would be nice if we could get that from the /update folder so if we brick, we have something we might be able to flash to recover.
JonnyGrench said:
I'll do it man just message me details on how to
Click to expand...
Click to collapse
I figured out if you put the AT&T SIM card in, then Settings / AT&T Software Update, you will see the Z971V2.0 update & it will download.
I wasn't able to see the update until I put the AT&T SIM card in.
Unfortunately, I was unable to grab the OTA update.
If someone hasn't already updated to the latest software version, if you could "adb logcat -d -f /sdcard/Download/ota.txt" once the download starts, we can probably get the url of the OTA update, then work from there on building a flashable firmware... :good:
aslezak said:
I was going to try & backup all the partitions using QPST, but it seems you need to get the phone into 9006 mode. We can only get into 9008 mode [Qualcomm HS-USB QDLoader 9008] with "adb reboot edl" (emergency download mode). Holding down Vol+/Vol-/Power from EDL will get you into yet another mode, ZTE Handset Diagnostic (DFU) mode, but I couldn't figure out how to do anything from here with QPST.
The only way to get the phone into 9006 mode is to brick the bootloader, which I'm not willing to do at the moment. Supposedly you can use the "axon7tool -d" and it will try to write to your bootloader & boot, but it just crashed when I tried to do it.
The other way to get into 9006 mode is to flash an mbn and another file, but I believe those are device specific, and we don't have those..
Anyway, does anyone have a phone that wasn't updated to the latest Z971V1.0.0B20 firmware? It would be nice if we could get that from the /update folder so if we brick, we have something we might be able to flash to recover.
Click to expand...
Click to collapse
Greetings, i have ZTE blade spark too, as i see, this thread looks like it died very quick. well, i am not a developer but i'll try contacting some developers to check if we can do something. Maybe since they know a lot about it, they can help us to unlock bootloader, etc. I JUST HOPE that this thread doesnt die like the Huawei Ascend XT forums did and the phone couldnt have any custom ROM. The best thing is we have source code (the XT didnt had a good source code or no source code at all) and we can start from that. But we need a good dev to help us, try to contact as many devs as possible too.
Not to discourage you, but the fastboot is "disabled" on all ZTE U.S. devices. You would need to flash using QPST which requires having the correct vendor signed firehose programmer (which isn't available). You could try modifying the ota zip update, if you received one on your phone. You would need to download this OTA update manually before rebooting the phone (to have it installed), otherwise the link will be rolled off the logcat logs.
Good luck.
ensol52 said:
Greetings, i have ZTE blade spark too, as i see, this thread looks like it died very quick. well, i am not a developer but i'll try contacting some developers to check if we can do something. Maybe since they know a lot about it, they can help us to unlock bootloader, etc. I JUST HOPE that this thread doesnt die like the Huawei Ascend XT forums did and the phone couldnt have any custom ROM. The best thing is we have source code (the XT didnt had a good source code or no source code at all) and we can start from that. But we need a good dev to help us, try to contact as many devs as possible too.
Click to expand...
Click to collapse
So I just got this phone and wanted to root and all that like I did my S4. Came here for some help because I am most definitely not educated enough for this. I did have a question though. I see a lot about a locked bootloader but under the developer settings I see "OEM Unlocking Allow the bootloader to be unlocked." The default is off, and I have left it so. Is this anything or am I missing something?
aslezak said:
I figured out if you put the AT&T SIM card in, then Settings / AT&T Software Update, you will see the Z971V2.0 update & it will download.
I wasn't able to see the update until I put the AT&T SIM card in.
Unfortunately, I was unable to grab the OTA update.
If someone hasn't already updated to the latest software version, if you could "adb logcat -d -f /sdcard/Download/ota.txt" once the download starts, we can probably get the url of the OTA update, then work from there on building a flashable firmware... :good:
Click to expand...
Click to collapse
Just got the phone, going to do this. Edit: Total skid here btw. Is it safe to post that file here?
Foggofed said:
Just got the phone, going to do this. Edit: Total skid here btw. Is it safe to post that file here?
Click to expand...
Click to collapse
Hello ? Lol, yeah! Upload it to a good site like Android dev, I'm a lil behind the loop but I'm sure sharing your findings are what's going to lead us into a possibility of getting some Dev love...
Sent from my Z971 using Tapatalk
I was trying to help a friend out by installing the international OS on his new OP6T (A6010) because I know a friend who did it a year or two ago and it worked perfectly. We thought it would work out but I couldn't get the firmware to install using the normal system update--it said that the firmware was lower than the currently installed firmware and therefore couldn't be installed.
So, I tried downgrading using the msm tool (I didn't realize the Chinese version was different...) and now it is stuck in a boot loop saying "build version and HW version is not match!"
What options do I have here? I didn't install TWRP (I was going to but tried the MSM tool because people were recommending it on many other sites...but were only talking about Tmobile and Global variants so I didn't realize Chinese was an entirely separate one).
Is there any way to fix this?
You can get it into fastboot right? I'd push the latest official fastboot ROM into it via ADB.
snatale1 said:
You can get it into fastboot right? I'd push the latest official fastboot ROM into it via ADB.
Click to expand...
Click to collapse
No, when I hold any combination of buttons, it gives me the error message. I can't do anything with it at the moment.
I got it to flash "fastboot mode" for a moment, but then the error message went up again and black screen.
That's weird, fastboot should be coming up before it tries to load the OS, you're going to be left with reflashing (in your case) HydrogenOS via download mode and MSM.
snatale1 said:
That's weird, fastboot should be coming up before it tries to load the OS, you're going to be left with reflashing (in your case) HydrogenOS via download mode and MSM.
Click to expand...
Click to collapse
Thank you for the information here with this. Are all msm things specific to certain firmwares or is it possible to throw a firmware into an msm thing? I'm not sure about this one yet.
I have a A6010 I have used this to go back to Android 9 with out issue.
https://androidfilehost.com/?fid=1395089523397966003
mchlbenner said:
I have a A6010 I have used this to go back to Android 9 with out issue.
https://androidfilehost.com/?fid=1395089523397966003
Click to expand...
Click to collapse
Thank you for your help here.
Unfortunately I keep getting the same message again and again in all of the msm tools I've tried: images do not match with the phone.
I'm not sure how I've done it but I've messed it up badly and now not sure how to fix it.
nightcow said:
Thank you for your help here.
Unfortunately I keep getting the same message again and again in all of the msm tools I've tried: images do not match with the phone.
I'm not sure how I've done it but I've messed it up badly and now not sure how to fix it.
Click to expand...
Click to collapse
You're going into download mode correctly right? Holding BOTH Vol buttons while then plugging into the USB cable thats already in your comp?
snatale1 said:
You're going into download mode correctly right? Holding BOTH Vol buttons while then plugging into the USB cable thats already in your comp?
Click to expand...
Click to collapse
Yeah, I was able to get it recognized by the computer and the msm software. It was just not accepting it.
I actually finally got it to work, though, but using the patched version of the msm tool that Tmobile users were using to install the international firmware, because it ignores the check for hardware/firmware matching and just forces the firmware on there.
It took two different msm tools/firmwares but finally it worked out. It was an incredibly relieving sight to see it boot up and not immediately go into the same bootloop again.
Glad to see you got it going.
Good day, please I got into the same issue of hardbrick on my oneplus 6t chinese variant. Please would you be kind enough to give a break down on how you got it to work. And were you able to finally install Oxygen OS?
I'm not seeming to find coherent instructions to get back to stock 11.0.2.2IN11AA
I have the 8 Pro, rooted, newest magisk and I installed a magisk module that is now causing System UI crash at startup. I have tried a couple things: 1) tried the "adb wait-for-device shell magisk --remove-modules" --> nothing happens when starting back up except System UI error. 2) I've flashed back to stock boot.img (hoping to get to safe mode to disable magisk)...all I get is System UI error again.
So...what I want to do is start all over and end up with 11.0.2.2IN11AA rooted. Once I'm back to "factory" I'm pretty sure I can get back to magisk and root.
Can anyone help me with some decent instructions please?
Thanks
I can. So last week I managed go back from a rooted situation to stock rom with LOCKED bootloader. This means that you're phone will be as you bought it and you're gonna lose everything of course.
This video on YT helped me.
***REMEMBER TO CHOOSE YOUR FIRMWARE BECAUSE I THINK THIS VIDEO IS FOR ASIA, IF IT IS THE SAME FOR YOU THEN YOU SHOULD FOLLOW THIS VIDEO***
I provide you a link with a thread on xda where I found the version for my oneplus 8 pro (EU)
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS | XDA Developers Forums (xda-developers.com)
Thanks I'll check it out and report back
glhelinski said:
Thanks I'll check it out and report back
Click to expand...
Click to collapse
Let me know
glhelinski said:
I'm not seeming to find coherent instructions to get back to stock 11.0.2.2IN11AA
I have the 8 Pro, rooted, newest magisk and I installed a magisk module that is now causing System UI crash at startup. I have tried a couple things: 1) tried the "adb wait-for-device shell magisk --remove-modules" --> nothing happens when starting back up except System UI error. 2) I've flashed back to stock boot.img (hoping to get to safe mode to disable magisk)...all I get is System UI error again.
So...what I want to do is start all over and end up with 11.0.2.2IN11AA rooted. Once I'm back to "factory" I'm pretty sure I can get back to magisk and root.
Can anyone help me with some decent instructions please?
Thanks
Click to expand...
Click to collapse
Visit the MSM thread, that's it
Sneakdovi said:
Let me know
Click to expand...
Click to collapse
Good site and instructions. They sure don't make it clear that msmtool is packaged inside the image download file
glhelinski said:
Good site and instructions. They sure don't make it clear that msmtool is packaged inside the image download file
Click to expand...
Click to collapse
I only donwloaded the EU verision (because i'm in Italy), went to qualcom recovery, and started the process
Sneakdovi said:
I only donwloaded the EU verision (because i'm in Italy), went to qualcom recovery, and started the process
Click to expand...
Click to collapse
Please help me, i'm bricked my new device. I want that ****** monocrome filter and make to many bull**** ! :-( I need my phone.
The MSM-Tool is give me always "Sahara" errors. Make the same misstake then you! I locked the bootloader!
Please.
chr_rocke808 said:
Please help me, i'm bricked my new device. I want that ****** monocrome filter and make to many bull**** ! :-( I need my phone.
The MSM-Tool is give me always "Sahara" errors. Make the same misstake then you! I locked the bootloader!
Please.
Click to expand...
Click to collapse
First off, you may want to edit your language in here, no need to swear. Secondly you should check out the thread regarding the MSM tool.
[OP8PRO][OOS 11AA/BA/DA] 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
Post #2 above has a video and also links to the same place that freshlybaked420 referenced... Should be enough to get you back on track
FreshlyBaked 420 said:
First off, you may want to edit your language in here, no need to swear. Secondly you should check out the thread regarding the MSM tool.
[OP8PRO][OOS 11AA/BA/DA] 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
Click to expand...
Click to collapse
Yes, it's all true. Sorry for that i have now working for many days on this. Not sleeping enought. One more question that could bring me a step foward...
I was on IN11.0.2.2 before i locked the bootloader and bricked the device.
Now i downladed the Decrypted OxygenOS 11.0.0 IN21BA Version. I have now the error: Param Preload Device not match image. Question: Must i habe the Decrypted OxygenOS 11.0..2.2 IN21BA Version that it goes to work?
I can't the use the link for the right version, it is password protected.!
Thanks
The password is listed in the OP
glhelinski said:
The password is listed in the OP
Click to expand...
Click to collapse
Thank you, but I didn't find it.
One point I have forgotten to tell. Before the hard brick happened, I used Magistik and Patch a new boot.img then I flashed this with fastboot command. My failure was to make this 2. times. with different patches. The horrible thing is now that I must delete these files on my Laptop to get more space. When this the Problem of the MSMTOOL error is I had not really a chance to unbrick my device. Have anyone Downgrade with MSMTOOL the Stock Rom?
Thx for your help. I download now from OP the latest ROM. I will try it. I feel really scared. Maybe my device is not unbricked anymore.
The other Tool that I have (last chance) is the original Qualcomm flashing Tool QPST.
described here:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
-- > But I found nothing here, that this tool was used. There is no special Rom here to found.
chr_rocke808 said:
Thank, but i didn't find it.
One point i forgotten to tell. Before the hard brick happend, i used Magistik and Patch a new boot.img then i flashed this with fastboot comand. My failure was to make this 2. times. with diffred pachtes. The horrible thing is now that i must delete this files on my Laptop to get more space. When this the Problem of the MSMTOOL error is i had not realy a chance to unbrick my device. Habe anyone Donwgrade with MSMTOOL the Stock Rom?
Thx for your help. I download now from OP the latest ROM. I will try. i feel realy scared. Mabye my device is not unbricked anymore.
The other Tool that i have (last chance) is the orginal Qulacomm flashing Tool QPST.
described here:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
-- > But i found nothing here, that this tool was used. There is noch spezial Rom here to found.
Click to expand...
Click to collapse
None of that matters.
1st identify your device!
What region is it?
If you have BA then don't flash AA you'll mess things up.
2nd visit the MSM thread!
Download the tool 'for your device!'
3rd boot to EDL (I responded to you in the romaur thread how to do this)
4th as soon as it's connected to your pc in edl, flash the device
5th MSM will relock your bootloader.
6th don't do something if you're not sure, just ask.
Oh and lol chill on the swearing also on posting everywhere, just make 1 thread and stick with it, people will help
Hey, my Phone is working like a charm. Thx for the great work !!!. I'm so happy !!!
It is better to come here to real developers, I had to get bad download links and bad Software! This was the only problem. For many years I have the first Samsung Galaxy and I'm knowing that I can get all the problems for not booting devices back. But I was scared that many Devices like Huwai bring their bootloaders with cryptographic methods in a safe trunk.
Best wishes to you, and the people that I'm working for the android project!
regardless,
chr_rocke808
chr_rocke808 said:
Hey, my Phone is working like a charm. Thx for the great work !!!. I'm so happy !!!
It is better to come here to real developers, I had to get bad download links and bad Software! This was the only problem. For many years I have the first Samsung Galaxy and I'm knowing that I can get all the problems for not booting devices back. But I was scared that many Devices like Huwai bring their bootloaders with cryptographic methods in a safe trunk.
Best wishes to you, and the people that I'm working for the android project!
regardless,
chr_rocke808
Click to expand...
Click to collapse
Lol no worries pal, but trust me, always make a thread unless one exists, it'll work out.
Glad you're sorted.
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.
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.