Develop Bugs

Find 7 (x9076) soft bricked, misread by device manager,

Hey Everyone,
I have a Find 7 (X9076). A while back I updated to the "stable version " of ColorOSi and ever since my usb doesn't charge the phone and vol down key doesn't work. Additionally it is being misread by the computer device manager as a "Samsung Android Device" when it is in boot loader mode.
I suspected it was a software/kernel issue because when I checked the registry I found the original oppo drivers, so I attempted to flash a new kernel to the device and ended up soft bricking it (no image). Now even though it is soft bricked I am still able to get into boot loader mode (no image). Please Help?
I have used Find 7 recovery installer and FASTBOOT (CMD) as well as trying to use ADB and a Find 7 unbricking tool in Windows 7 test mode the last two didn't work/didn't recognize my phone at all. I refuse to abandon my device so what do I do?

Given you have adb access, you could extract the contents of the current (2.x?) color os image, and fastboot flash the partitions manually.
I recently did this and 'recovered' my device.

adb didnt recognize my device -but how do I do that just in case I'm able to get it working?

Midnight247 said:
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Click to expand...
Click to collapse
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.

ADB, FastBoot and the USB
I don't know if I was clear in my explanation as to how and when my device (FIND7 X9076) is recognized ONLY by the following: my Computer (Windows 7), the Device Manager, Fast-Boot and on the FIND7 Recovery Installer. I have been able to enter fast-boot mode on any version of the ColorOS I flashed, 1.2 - 2.5.1, (stable version) and work within the confines of that mode. However when the USB is connected in anything other mode (recovery-main OS) it ceases functionality (sending information to comp for recognition, charging, etc.). Also the charger doesn't work and nor does the notification light. Now I may be wrong, but for these reasons I believe the problem is likely software related. I am open to any opinions and advice.
-Thank You Everyone

tropical cactus said:
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
Click to expand...
Click to collapse
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??

Midnight247 said:
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Click to expand...
Click to collapse
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.

tropical cactus said:
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
Click to expand...
Click to collapse
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.

Midnight247 said:
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Click to expand...
Click to collapse
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.

tropical cactus said:
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
Click to expand...
Click to collapse
hmm okay, i see I will keep you posted

**IMPORTANT UPDATE**
***MAKE OPPO FIND 7 OPERABLE****
following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
By using the afformentioned commands in fastboot (of course) I was able to restore my phone to almost full functionality. It operates noramally and I fixed the notication light, But I say almost because I cannot charge my phone or have it recognized by my computer through any charger or usb connection when it is on normally or in recovery mode so if any one is familiar with this problem please respond or simply voice ideas.

If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.

RobboW said:
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
Click to expand...
Click to collapse
I do, have full functionality : ) everything but the USB is performing properly, but to be honest I dont know what AOSP is.....also this will repair functionality to the USB?

Flashing using MI Flash got stuck

Hello,
I'm using Redmi Note 5 pro. Recently my device went on boot loop. Whenever I tried to restart, it was showing MI Logo for long time, nothing happens. I'm not able to enter into recovery mode as well (Vol Up + Power). But I can go to Fastboot mode (Vol down + power key).
Mine is not bootloader unlocked and I dont think I have enabled OEM Unlocking from the settings.
I tried downloading the ROM from below URL (Rom for Fastboot flash) -> whyred_global_images_V11.0.3.0.PEIMIXM_20191108.0000.00_9.0_global
http://c.mi.com/in/miuidownload/detail?guide=2
http://update.miui.com/updates/v1/fullromdownload.php?d=whyred_global&b=F&r=global&n=
When I check, whether the fastboot devices is showing mine or not, I can see my device listed
In another forum, I can across this, before flashing using MiFlash, they asked to download the Edl.cmd file from the below link and run it. I did that as well.
https://forum.xda-developers.com/an.../guide-how-to-reboot-to-edl-fastboot-t3394292
After that, when I select the downloaded ROM, and try to flash it with MiFlash (v2019.12.6.0), it keep showing the below line. but its not getting errored out. progress bar keeps going till the end but it stays with the below status. Attached the screenshot as well.
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || echo Missmatching image and device
Any help with will be much helpful! Thanks in advance!

I think flashing via fastboot on unlocked bootloader is not possible

Hi, you mean locked bootloader is not possible?
If yes, is there a way to fix the phone?
Thanks in advance!

karthik623521 said:
Hi, you mean locked bootloader is not possible?
If yes, is there a way to fix the phone?
Thanks in advance!
Click to expand...
Click to collapse
The way i see is Edl flash mode (wait for a proper answer)

I accidentally locked my chinese whyred while flashing global rom using miflash.
The only thing that worked for me was EDL flash chinese rom using QFIL following the tutorial here: https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
I had to use chinese rom for 360 hours until I could unlock the bootloader again.
You need to flash the rom version that matches your device origin (global, china, india, russia, etc..)

tsarig said:
I accidentally locked my chinese whyred while flashing global rom using miflash.
The only thing that worked for me was EDL flash chinese rom using QFIL following the tutorial here: https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
I had to use chinese rom for 360 hours until I could unlock the bootloader again.
You need to flash the rom version that matches your device origin (global, china, india, russia, etc..)
Click to expand...
Click to collapse
Hello, Thanks for letting me know about this method. I tried this but I'm not able to find my devices showing in Device Manager as "qualcomm hs-usb qdloader 9008" (I'm trying with fastboot mode as am not able to go to Recovery mode)
I tried installing the Qualcomm QDLoader 9008 driver using the method shown in the below link
https://www.99mediasector.com/install-qualcomm-hs-usb-qdloader-9008-install/
1. tried direct installation of exe - didn't work)
2. there was manual method which asked me to reboot in edl mode using the command fastboot oem edl - but this shows error saying FAILED (remote: 'Device is already locked!')
//attached screenshot for reference
Thanks!

karthik623521 said:
Hello, Thanks for letting me know about this method. I tried this but I'm not able to find my devices showing in Device Manager as "qualcomm hs-usb qdloader 9008" (I'm trying with fastboot mode as am not able to go to Recovery mode)
I tried installing the Qualcomm QDLoader 9008 driver using the method shown in the below link
https://www.99mediasector.com/install-qualcomm-hs-usb-qdloader-9008-install/
1. tried direct installation of exe - didn't work)
2. there was manual method which asked me to reboot in edl mode using the command fastboot oem edl - but this shows error saying FAILED (remote: 'Device is already locked!')
//attached screenshot for reference
Thanks!
Click to expand...
Click to collapse
You're in fastboot. not EDL mode.
EDL Testpoint - https://youtu.be/dYVR5BgNwG0
Connect the usb cable to both phone and pc, disconnect the battery flex cable, short the two EDL testpoint, and connect the battery flex cable. it will take some practice.
Also, there is a limited time in EDL mode to start flashing, if you too late you will have to repeat again.
Use this tutorial https://youtu.be/ikGsxf_s-zw

It seems shorting pins and edl flashing is the only way for reviving ur phone pal
Good luck

LG G8 G820UM stuck unlocking bootloader plz help?

Hi and thanks for reading--
I followed this guide for my new LG820UMBK Verizon Unlocked:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
I flashed the engineer abl_a and abl_b and my first hangup was to enter Fastboot mode I hold Vol+ instead of Vol- as the guide says. But it tooks several reboots and flashing back to the backup abl to figure that out. My device in Fastboot mode isnt recognized by my PC with the fastboot devices command. It is recognized by Device Manager however as Other devices: Android.
Upon boot it gets stuck at VZW splash screen. I can enter EDL mode but when I try to restore my backup abl_a+b it says Data Overflow do you wish to continue. If I select yes it wont flash the backup abl with the size of 32,768 kb. It leaves the abl files at 1,024 kb which was the size of the engineer file.
I can boot to Fastboot but my fastboot devices commands can't see the device. In Device Manager like I said in Fastboot mode it just shows up as Other Devices: Android. On the Verizon spash screen it appears in Device Manager as LGE AndroidNet USB Serial Port (COM3) and in EDL mode it shows up under Ports as: Qualcomm HS-USB QDLoader 9008 (COM11).
I ran the LG Mobile Support Tool and it installed all the proper drivers it says. Maybe I dont have the adb/fastboot drivers? I tried to find them in the SDK but its way more complicated than it used to be. I havent rooted since the LG G2 lol.
Any ideas or help would be so awesome. Its basically bricked cause I cant flash the ABL backups. LGUP program doesn't recognize the device, I did download the correct G820UM20i_00_VZW_US_OP_1124.kdz file so maybe i'll just attempt to restore the stock rom. Can I do that with QFIL??
I cant believe I'm the only person this happened to....
Thanks for any thoughts!!

durrant111 said:
Hi and thanks for reading--
I followed this guide for my new LG820UMBK Verizon Unlocked:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
I flashed the engineer abl_a and abl_b and my first hangup was to enter Fastboot mode I hold Vol+ instead of Vol- as the guide says. But it tooks several reboots and flashing back to the backup abl to figure that out. My device in Fastboot mode isnt recognized by my PC with the fastboot devices command. It is recognized by Device Manager however as Other devices: Android.
Upon boot it gets stuck at VZW splash screen. I can enter EDL mode but when I try to restore my backup abl_a+b it says Data Overflow do you wish to continue. If I select yes it wont flash the backup abl with the size of 32,768 kb. It leaves the abl files at 1,024 kb which was the size of the engineer file.
I can boot to Fastboot but my fastboot devices commands can't see the device. In Device Manager like I said in Fastboot mode it just shows up as Other Devices: Android. On the Verizon spash screen it appears in Device Manager as LGE AndroidNet USB Serial Port (COM3) and in EDL mode it shows up under Ports as: Qualcomm HS-USB QDLoader 9008 (COM11).
I ran the LG Mobile Support Tool and it installed all the proper drivers it says. Maybe I dont have the adb/fastboot drivers? I tried to find them in the SDK but its way more complicated than it used to be. I havent rooted since the LG G2 lol.
Any ideas or help would be so awesome. Its basically bricked cause I cant flash the ABL backups. LGUP program doesn't recognize the device, I did download the correct G820UM20i_00_VZW_US_OP_1124.kdz file so maybe i'll just attempt to restore the stock rom. Can I do that with QFIL??
I cant believe I'm the only person this happened to....
Thanks for any thoughts!!
Click to expand...
Click to collapse
So I forgot to eject my micro SD card, I know so dumb. I am now able to fastboot. I tried to flash the original abl_a and b with fastboot and it is telling me Error Flashng Partition: Volume Full. Same issue I was having in QFIL basically. How do I restore the abl files ughhhhh.

you can fomat data : - and power before click power

durrant111 said:
So I forgot to eject my micro SD card, I know so dumb. I am now able to fastboot. I tried to flash the original abl_a and b with fastboot and it is telling me Error Flashng Partition: Volume Full. Same issue I was having in QFIL basically. How do I restore the abl files ughhhhh.
Click to expand...
Click to collapse
Boot to EDL mode by holding the vol - and power button while your G8 is plugged in your computer, after you hear a disconnection sound immediately press the vol + until you hear a connection sound from your computer.
Now, open QFIL then look for the abl a and b then flash your backed up abl_a nd abl_b accordingly and reboot. And you're good to go again.

I can help you. Do you fix problem ???

I am having some issues with rooting my g8 at&t I managed to successfully unlock the bootloader but now I am stuck in a bootloop after trying to flash magisk. I can start in edl mode or download mode and that is all. My phone flashes the lg splash screen for a split second over and over it doesn't matter if I flash my backup adl files or boot files it just keeps doing the same thing. What am I missingm

Anybody?

Ratty696 said:
Anybody?
Click to expand...
Click to collapse
.

Ratty696 said:
I am having some issues with rooting my g8 at&t I managed to successfully unlock the bootloader but now I am stuck in a bootloop after trying to flash magisk. I can start in edl mode or download mode and that is all. My phone flashes the lg splash screen for a split second over and over it doesn't matter if I flash my backup adl files or boot files it just keeps doing the same thing. What am I missingm
Click to expand...
Click to collapse
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?

armodons said:
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?
Click to expand...
Click to collapse
Used method in beginning of this thread. Tried flashing backup
armodons said:
Gonna need more details. What steps did you take to try to flash magisk that resulted in the bootloop?
Click to expand...
Click to collapse
I used the method in that thread to unlock and try to root. When I flashed majisk is when my problem started. I have tried flashing the backup files I made but that doesn't help either

Ratty696 said:
Used method in beginning of this thread. Tried flashing backup
I used the method in that thread to unlock and try to root. When I flashed majisk is when my problem started. I have tried flashing the backup files I made but that doesn't help either
Click to expand...
Click to collapse
So you are saying you bootloop after you use QFIL to flash Magisk-patched boot_a and boot_b? Do "backup files" mean the original boot_a and boot_b that you flash back using QFIL?
If so, you should double check you are flashing the correct partitions in QFIL because neither of these steps seem like they can result in bootloop. LGUP and start over.

armodons said:
So you are saying you bootloop after you use QFIL to flash Magisk-patched boot_a and boot_b? Do "backup files" mean the original boot_a and boot_b that you flash back using QFIL?
If so, you should double check you are flashing the correct partitions in QFIL because neither of these steps seem like they can result in bootloop. LGUP and start over.
Click to expand...
Click to collapse
Yes when I used QFIL to flash magus isvwgen it started abd flashung original boot_a and boot_b dont fix it. I can't get kdz file for at&t to lg up.

Ratty696 said:
Yes when I used QFIL to flash magus isvwgen it started abd flashung original boot_a and boot_b dont fix it. I can't get kdz file for at&t to lg up.
Click to expand...
Click to collapse
Is there any place to get the KDZ file for the AT&T g8? I got someone claiming to have it but want me to prepay $30 for it

Nobody able to help me?

Ratty696 said:
Nobody able to help me?
Click to expand...
Click to collapse
I'm new to the G8 (not LG), so just now browsing these posts.
First and foremost, this thread shouldn't be in this forum. This forum is for roms, kernels, recoveries and other development.
This thread is a question about a guide (which is in guides forum). This 'question' is not development of a rom, kernel or recovery, it's a question.
I'd suggest, if you want people to respond that can help, ask the question in it's individual guide thread, that's where the people that know the most about it will be. If you get no response in that thread, then maybe think about posting the question in the questions forum.
but here? in dev forum? absolutely the wrong place for a question about a guide.
cheers

Thread moved to Q&A section.
Thanks!
woodman
Senior Moderator

@durrant111
So to the original OP; 2 things; If your device isn't recognized when in fastboot mode, that's because you don't have the right driver installed in WinBlows.
You have to download the LG USB drivers, install them, then in device manager select the "! Android" and install the driver (usually says ADB) and then 'fastboot devices' will see the phone.
Second; if you ever get a message telling you that 'Data Overflow' then you are absolutely making a big mistake. When you did the backup of your abl(s) (and other partitions), you should have renamed then one by one, that way you don't make the mistake of naming the laf_a partition as the abl_a partition (or any name other than what ti should be). If you flash the wrong partition you run the risk of overwriting the nearby partition, which would make the device essentially unusable except only to qfil.
Lastly, yer lucky the device is VZW, as they make their kdz available and you can use use lg up to get back to stock. If it was Sprint or At&t you'd be scrambling to find a qfil or bkerler backup someone luckily made that you come across (a much more unlikely scenario).
Good luck, you've probably already moved on from this, but just in case, thought I'd mention the above.
cheers

Ratty696 said:
Is there any place to get the KDZ file for the AT&T g8? I got someone claiming to have it but want me to prepay $30 for it
Click to expand...
Click to collapse
Unfortunately at&t doesn't make their kdz available. You can be 99.9% positive the only thing this person that wants to charge you 30$ is going to give you is the partitions backed up by qfil or bkerler edl stuff.
With both at&t and sprint, because no kdz, you can only restore (if you didn't back up the files yourself originally), with someone elses backup, and then you have to use qfil or bkerler edl utilities to restore. If you look around in the G8 forums (or the tele group), there's a decent chance someone has already make their backup available.
cheers and good luck.

Ratty696 said:
Nobody able to help me?
Click to expand...
Click to collapse
Could you solve your problem?
I also have an at&t lg g8 and I want to unlock the bootloader

Yarib said:
Could you solve your problem?
I also have an at&t lg g8 and I want to unlock the bootloader
Click to expand...
Click to collapse
Lol no still haven't solved my problem. I need the abl_a and abl_b files for a lg g8 at&t. My phone only goes in fastboot or qfil and Fastboot says its a lmg850um because I tried using the files from my lg g8x and it didn't work. I have also now bricked my lg g8x it only boots into qfil. Any help would be great. My g8x is canada version

Question Help unbricking 9Pro after attempt to convert T-Mobile to Global

I recently purchased a 9 Pro T-Mobile edition. It was supposed to be a global edition, but this information was willfully obscured by the eBay seller. Whatever, I figured I could follow this guide to convert it to global firmware. I've rooted plenty of OnePlus phones before and am very comfortable with the process, as well as using MSM to fix things when they go wrong. However, things went even worse than normal. I went through the usual process of unlocking the bootloader, and began flashing the images from the download. However, as usual, they don't tell you to unlock flashing for critical partitions, so only half the partitions got flashed and the whole thing failed. Now I cannot access fastboot or recovery, or do quite literally anything with it.
I figured I'd use MSM and fix it just like I did when things like this happened to my OnePlus 8. So I downloaded the T-Mobile MSM from this thread and ran it. When I try to run it normally, it gets as far as "Start download Firehouse binary" and will attempt for 18 seconds, at which point it shows the error "Sahara Communication Failed. Please try again after power off phone (FH:258)". So I tried ticking the box to use Lite Firehose. It gets farther, but errors during Param preload, with the message "Device not match image."
I assumed that this error was due to the fact that some of the images that were successfully flashed are from the global image, while this MSM tool is for TMO specifically, so I tried to the global MSM tool from the same thread instead. It also fails Sahara communication with the exact same error. If I use Lite Firehose, it gives the error "Unsupported Target TMO."
At this point, I'm at a complete loss. I've tried to power off the phone via holding the power button + volume up button, but it never gives any response no matter how long I hold it. I'm not sure that the phone is able to turn on at all. My next guess would be to disconnect the battery and reconnect it, but I'm very hesitant to pull apart the phone without seeing if anyone has any better suggestions first. If I could access fastboot, I could have a download of a clean TMO firmware and could easily re-flash everything, but I can't get a single response out of the phone besides MSM errors. Any help would be much appreciated.

I just realized that that article is for the Oneplus 9 and NOT the Pro. That definitely explains why it broke in the first place, but doesn't help me get it back. The MSM Tools I'm using ARE for the Pro.

When you open Windows Device Manager and expand out the "Ports" section, what COM port is your phone using? Does that match up with the port the MSM tool is trying to use?

CZ Eddie said:
When you open Windows Device Manager and expand out the "Ports" section, what COM port is your phone using? Does that match up with the port the MSM tool is trying to use?
Click to expand...
Click to collapse
They're both using COM3

blindcat97 said:
They're both using COM3
Click to expand...
Click to collapse
Qualcomm.......9008?

TheGhost1951 said:
Qualcomm.......9008?
Click to expand...
Click to collapse
The full title of the device is Qualcomm HS-USB QDLoader 9008 (COM3)

blindcat97 said:
The full title of the device is Qualcomm HS-USB QDLoader 9008 (COM3)
Click to expand...
Click to collapse
That is the correct id and driver....however, is it the latest driver. That makes a difference as well.

TheGhost1951 said:
That is the correct id and driver....however, is it the latest driver. That makes a difference as well.
Click to expand...
Click to collapse
Windows lists the drivers version as 2.1.2.2 and date as 3/25/2016. I can't find anything newer by googling, and Windows automatic search for updated drivers reports it as the latest version.

Is there something in this link that will help?
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com

CZ Eddie said:
Is there something in this link that will help?
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com
Click to expand...
Click to collapse
No, I tried what I could in that article earlier already. At this point, I'm fairly certain that the only thing I could do would be to somehow force MSM to flash even though it thinks it has the wrong device, which I don't think is possible.

blindcat97 said:
No, I tried what I could in that article earlier already. At this point, I'm fairly certain that the only thing I could do would be to somehow force MSM to flash even though it thinks it has the wrong device, which I don't think is possible.
Click to expand...
Click to collapse
I'm a little confused about how you got your phone to its current state.
Your first paragraph has some minutia in it.
" I went through the usual process of unlocking the bootloader, and began flashing the images from the download. However, as usual, they don't tell you to unlock flashing for critical partitions, so only half the partitions got flashed and the whole thing failed."
What images did you download and how did you apply them to your phone?

I was following this guide to convert OP9 (not *pro*, which is where I messed up and I feel very stupid for not realizing that) from T-Mobile to Global firmware. It provided download links to a zip file full of img files, and a flash-all.bat which used fastboot commands to flash the individual files. Half of the files didn't flash because "Flashing critical partitions is not allowed", but some of them did flash successfully. There's no log file to tell me which ones did and did not work. Here's the chunk of the flash-all script that actually contains the fastboot commands:
Spoiler: flash-all excerpt
fastboot flash dtbo dtbo.img
fastboot flash splash splash.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
fastboot reboot fastboot
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash splash splash.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash abl abl.img
fastboot flash bluetooth bluetooth.img
fastboot flash cpucp cpucp.img
fastboot flash devcfg devcfg.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot reboot fastboot
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
It got through the first reboot okay (despite booting to fastbootd and me having to manually redirect it back to fastboot), but when it reached the second reboot command, it just died and wouldn't turn on any more, and the third block of commands were never executed. So I'm guessing that something it flashed in that second block is what completely broke its ability to boot. I would flash the images from a clean copy of OP9Pro TMO firmware, but I can't get to fastboot at all.

blindcat97 said:
Windows lists the drivers version as 2.1.2.2 and date as 3/25/2016. I can't find anything newer by googling, and Windows automatic search for updated drivers reports it as the latest version.
Click to expand...
Click to collapse
You will need a modded MSM tool....when you use the stock TMO MSM tool what error do you get?

im not really that experienced with this stuff but this kind of happened to me today so i decided to make an account and try to help you. Basically what I did was I deleted everything on it, like I could only use fastboot mode. Then i used an msm tool from here. make sure you get the tmobile one because i tried global and it didn't work. after i used the msm tool it started working again. once again, i am not experienced in this stuff, so my advice may screw you over, but at this point you don't really have anything to lose.

TheGhost1951 said:
You will need a modded MSM tool....when you use the stock TMO MSM tool what error do you get?
Click to expand...
Click to collapse
From my original post: When I try to run it normally, it gets as far as "Start download Firehouse binary" and will attempt for 18 seconds, at which point it shows the error "Sahara Communication Failed. Please try again after power off phone (FH:258)". So I tried ticking the box to use Lite Firehose. It gets farther, but errors during Param preload, with the message "Device not match image."

I've never run into the firehouse issue before.
But it's very common and is talked about in dozens of threads here.
But it looks like you've actually flashed some system files from a different phone.
I hope that doesn't mean MSM is rejecting you because it thinks you're a different phone.
Maybe try flashing a 9pro boot.img that would match the software you're supposed to be at right now?
Not sure if that'll mess you up more or not though.

Double-check that you've downloaded the correct MSM file
Research the SMT mode.
It's disabled for a reason - because it'll wipe your IMEI & other important things.
I don't know how to use it yet, but supposedly it'll fix unfixable things. When used properly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I have no way of flashing. I can't get to fastboot, I can't get the phone to respond to quite literally anything other than MSM. Any combination of buttons does nothing. I'm not a professional with this stuff; if there's a way to flash to EDL without MSM, I don't know it. It looks like MSM rejecting because it thinks it's a different phone is exactly what's happening, and the only thing I can think to do would be essentially to mod it so that it thinks it's allowed to flash OP9 as well as 9Pro, or otherwise bypass the device check.
I'm certain I've got the right MSM tool. Doing some research into the SMT Download mode, it looks like it breaks core features, like the IMEI, and widevine. Is it possible to backup those partitions from EDL mode?
Basically, if my only way of recovering the device is to destroy critical sectors entirely, I might just send the device to OnePlus for repairs. My warranty was already voided by unlocking the bootloader.

blindcat97 said:
I can't get to fastboot
Click to expand...
Click to collapse
Why not? What happens when you power off the phone.
Wait 15 seconds.
And then press + hold the volume(-) and power button at the same time?
Remember to hold them until *after* the splash screen comes up.

CZ Eddie said:
Why not? What happens when you power off the phone.
Wait 15 seconds.
And then press + hold the volume(-) and power button at the same time?
Remember to hold them until *after* the splash screen comes up.
Click to expand...
Click to collapse
The phone is already off and cannot be turned on in any way, to any mode. Nothing happens when I hold that combination, nor any other. The phone is completely unresponsive.

Question Did I hard brick my phone? (SOLVED)

First off, I converted my Tmo version to EU using the MSM conversion tool... I then proceeded to fastboot flash the A13 OTA manually. (I was hoping to keep the bootloader unlocked by manually flashing) At the point that I needed to reboot in to fastbootD to flash critical partitions, I couldnt get it to do so. I may have hit recovery mode while in the bootloader and my phone just went blank. Now I can only access EDL mode but I cant get any of the MSM tools to work.
I get an "IMEI is incorrect" error with the TMo-EU MSM, Global MSM says "invalid target TMo" so it recognizes it as tmobile.
below are the fastboot commands I entered. Is there anything that would completely brick my phone and erase recovery and bootloader??
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img

In MSM tool, there's a check box which says 'Use Lite Firehose'. can you tick that once and try again ?

mbj731 said:
First off, I converted my Tmo version to EU using the MSM conversion tool... I then proceeded to fastboot flash the A13 OTA manually. (I was hoping to keep the bootloader unlocked by manually flashing) At the point that I needed to reboot in to fastbootD to flash critical partitions, I couldnt get it to do so. I may have hit recovery mode while in the bootloader and my phone just went blank. Now I can only access EDL mode but I cant get any of the MSM tools to work.
I get an "IMEI is incorrect" error with the TMo-EU MSM, Global MSM says "invalid target TMo" so it recognizes it as tmobile.
below are the fastboot commands I entered. Is there anything that would completely brick my phone and erase recovery and bootloader??
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
Click to expand...
Click to collapse
Also, you need T-Mobile msm

oddlyspaced said:
In MSM tool, there's a check box which says 'Use Lite Firehose'. can you tick that once and try again ?
Click to expand...
Click to collapse
I've tried that. Still no luck. Getting either "IMEI is incorrect" or "device doesnt match image" errors. Kind of odd getting different errors each time.
jamescable said:
Also, you need T-Mobile msm
Click to expand...
Click to collapse
I've tried them all just hoping one will work. Tmo-EU, Tmo, EU, Global etc etc

Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.

Shooter7889 said:
Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.
Click to expand...
Click to collapse
I use USB C to USB C 3.2 with no issues

Shooter7889 said:
Sorry for your situation...for future concerns, once u unlock bootloader, theres nothing other than msm that will relock it. As far as restoring your phone, I've seen where some ppl who can't find luck with their correct msm tool, they've had to use EU, or in most cases IND msm. Again, u will have to check box for lite firehose for it to work.
Also another thing to note...u really need to use regular style USB cable. Not newer ones that are C to C. If u haven't tried the cable problem I'd go back and try older style cable with correct msm tool b4 trying IND msm.
Click to expand...
Click to collapse
thanks for the reply. Actually, I upgraded through MSM Tmo-EU and then took system updates up til the latest A12 OTA... after installing A13 .16 that I got through Oxygen updater, I was no longer able to unlock the bootloader! I cant remember ever relocking it but either way, I couldnt unlock on Android 13 stable.
I'm beginning to wonder if maybe it's this Windows 7 pc thats giving me problems. but I've successfully used it before to MSM... just did my OnePlus 7t to get it back to working state while I try to figure out this 9pro situation. I've tried several cables and all of the MSMs at this point. I'm getting "device doesnt match image" a lot now. With my luck, I got home to try my laptop and the harddrive has crapped out on it! ha
I wonder if theres a way to modify the MSM tool to just flash to any Oneplus 9pro without identifying the variant. I know that would be dangerous, but at this point I just need SOMETHING to work! Or the next option is sending it back to OnePlus under warranty (I didnt request an unlock token etc so should still be good)

BTW, I've been doing this whole rooting/roming thing for a long time and I've also manually flashed through fastboot 100 times on different devices. I have NEVER ended up not being able to boot in to bootloader etc. I still dont understand how I lost bootloader and recovery etc flashing what I did,. Any ideas?

mbj731 said:
BTW, I've been doing this whole rooting/roming thing for a long time and I've also manually flashed through fastboot 100 times on different devices. I have NEVER ended up not being able to boot in to bootloader etc. I still dont understand how I lost bootloader and recovery etc flashing what I did,. Any ideas?
Click to expand...
Click to collapse
I'm not sure either. So after u converted using conversion tool, u booted into OS and then u needed to unlock BL once more, correct? It's strange u lost bootloader/recovery completely.

Shooter7889 said:
I'm not sure either. So after u converted using conversion tool, u booted into OS and then u needed to unlock BL once more, correct? It's strange u lost bootloader/recovery completely.
Click to expand...
Click to collapse
Yes, I had been running on A13 for a few days. Got the itch to root but as I said, I couldnt unlock bootloader (kept saying to flash token) so I decided to start the whole process over, unlock the bootloader and try to manually flash A13 instead of doing a local upgrade. (hadnt hit OTA for me yet)
During the process, theres a point where you have to boot in to fastbootD to flash critical partitions that wont flash in regular fastboot.... using the commands "fastboot reboot fastboot" wouldnt get me to fastbootD as I read it's supposed to. I think during all that and scrolling through the bootloader menu, I hit "recovery mode" which was apparently wiped because I just went straight to a black screen and thats where it's been ever since. I did all the button combos etc thinking it would just go back to bootloader but to no avail.
I wish there was a way to do manual commands in EDL or something. Maybe bootloader is there just that it's not responding to the hardware keys?

Oh. When u tried to unlock BL did u try "fastboot oem unlock? Yeh usually, eben if I mess up with msm or flashing imgs, it will kind of get stuck in edl, and I have to hold all three hardware buttons for some time b4 it will finally respond

Have you tried any of the older "all in one tools/fastboot enhance" posted on here in the past for older OP devices to see if they can do anything
Also, when I've had trouble in there past trying to find the right msm tool to work, each time I try one, if it shows connected on pc, then I try to run it, even if it fails, it kind of bricks edl, so I'd have to hold all three buttons to reset edl then try again(and it takes a little longer to respond than normal). If ur out of options other than returning it, id try the IND msm, check "lite firehose" and uncheck "sha256 check" and see if u have any luck

First I'd try holding all 3 buttons an UNGODLY long period of time and see if it finally boots to bootloader. Sometimes it takes for ever to shut down and restart. Then plug into pc use a USB 2 port if you have one. If pc sees the phone. If it does try adb devices in cmd terminal. If it list device try adb reboot bootloader and see if it boots.

kjslabber said:
First I'd try holding all 3 buttons an UNGODLY long period of time and see if it finally boots to bootloader. Sometimes it takes for ever to shut down and restart. Then plug into pc use a USB 2 port if you have one. If pc sees the phone. If it does try adb devices in cmd terminal. If it list device try adb reboot bootloader and see if it boots.
Click to expand...
Click to collapse
I taped all the buttons down and I'll watch it for a while and see if it boots up. I have tried holding them for a very good while with no luck already though

Shooter7889 said:
Have you tried any of the older "all in one tools/fastboot enhance" posted on here in the past for older OP devices to see if they can do anything
Also, when I've had trouble in there past trying to find the right msm tool to work, each time I try one, if it shows connected on pc, then I try to run it, even if it fails, it kind of bricks edl, so I'd have to hold all three buttons to reset edl then try again(and it takes a little longer to respond than normal). If ur out of options other than returning it, id try the IND msm, check "lite firehose" and uncheck "sha256 check" and see if u have any luck
Click to expand...
Click to collapse
I've tried the IND MSM gives me an "unsuspected target TMO" error or something like that. So at least some tools are seeing it as TMo... Tmo tools say the device doesnt match! I'll have to find another computer or 2 to try.. I was supposed to ship off my oneplus 7t tomorrow for trade in on this 9 pro but now I'm using the 7t again as it's my only working device. this has been a headache. lol
thanks for the feedback. I'm trying everything I can think of and researching too

Whew! I finally got it using EU MSM and the perfect combonation of cord/usb port, I guess. I had 3 cords, 10 usb ports and 5-6 MSMtools and after 2 days and probably 8+ hours of trying, I got my phone to boot again. lol

mbj731 said:
Whew! I finally got it using EU MSM and the perfect combonation of cord/usb port, I guess. I had 3 cords, 10 usb ports and 5-6 MSMtools and after 2 days and probably 8+ hours of trying, I got my phone to boot again. lol
Click to expand...
Click to collapse
Every one of us that's been at this long enough has gone thru this or a similar experience. It's a lot more headache but you also learn a lot more for the next time or to help others. Congrats on getting it up

mbj731 said:
thanks for the reply. Actually, I upgraded through MSM Tmo-EU and then took system updates up til the latest A12 OTA... after installing A13 .16 that I got through Oxygen updater, I was no longer able to unlock the bootloader! I cant remember ever relocking it but either way, I couldnt unlock on Android 13 stable.
I'm beginning to wonder if maybe it's this Windows 7 pc thats giving me problems. but I've successfully used it before to MSM... just did my OnePlus 7t to get it back to working state while I try to figure out this 9pro situation. I've tried several cables and all of the MSMs at this point. I'm getting "device doesnt match image" a lot now. With my luck, I got home to try my laptop and the harddrive has crapped out on it! ha
I wonder if theres a way to modify the MSM tool to just flash to any Oneplus 9pro without identifying the variant. I know that would be dangerous, but at this point I just need SOMETHING to work! Or the next option is sending it back to OnePlus under warranty (I didnt request an unlock token etc so should still be good)
Click to expand...
Click to collapse
You can use python3 to decrypt the .ops file, edit the first line parameters in the settings.ini, then python3 to encrypt the folder that was decrypted. Slow process but gives extra options.....