Develop Bugs

unbrick oneplus 5t, stuck in waiting for device in msmDownloadTool

Hi Guys,
Yesterday during an official update of my oneplus 5t (using the update manager from the phone itself), the phone got bricked and i dont know why....
So after some research i found it is hard bricked ( basically i cant do nothing, power on i cant, power +volume UP/DOWN too, and even when i plug the charge cable i have neither vibrations nor LED on)
So i follow this tutorial to unbrick the phone:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
I could get the phone recognize by the PC by pressing UP to see the phone as QUSB-BULK and then QUALCOMM QD LOADER after driver's update.
But when i run MSMDownloadTool ( V4.0.27 dumpling 43_0.36_180613) as administrator and click on start, the process get stuck in "waiting for device"
the status of connection before click on start was "connected" and after click and some process it turn to N/A
the status of communication is "memory size....."
status of last communication is "waiting for device"
I have tried several time and always the same result..... stuck in the waiting device
does someone have an idea on how to solve this? because i really need to unbrick the phone....
thank you in advance
EDIT:
I tried another version of MsmDownloadTool (dumpling_43_O.06_171206) and this time, the downloading of cache image failed....
I dont know what to do

You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?

DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.

rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.

DaRk-L0rD said:
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
Click to expand...
Click to collapse
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.

rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
rokusho32 said:
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
Click to expand...
Click to collapse
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know

DaRk-L0rD said:
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
Click to expand...
Click to collapse
I have installed the ADB drivers
which version of MSMDownloadTool should i use?

DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.

rcbjr2 said:
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
Click to expand...
Click to collapse
I have same situation.. did you resolve this problem?

piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
I contacted OnePlus and I sent them the phone and they reinstalled the operating system. I was never able to fix it myself. I even had an online session with OnePlus and they couldn't get the MSM software to recognize the phone (even though it was truly connected to my laptop). I also had an issue with my OnePlus 8T that got messed up doing something with Magisk, and OnePlus reinstalled the operating system as well. I still can't boot from the A partition though; just the B partition.

piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
At first, I chose WWAN-DHCP - which caused problem with connection

piechu11 said:
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
View attachment 5511425
At first, I chose WWAN-DHCP - which caused problem with connection
Click to expand...
Click to collapse
Thank you this solved my problem exactly.
i was restoring my metro by tmobile oneplus nord n10 BE2025 model with build tag BE88CF

G710EM bricked after trying to re-lock the bootloader. How to solve?

Hi!
I recently unlocked my bootloader and installed LineageOS on my LG G7, successfully.
I wanted to go back to stock, and I followed this guide:
https://forum.xda-developers.com/lg-g7-thinq/how-to/guide-how-to-flash-stock-firmware-lock-t3820888
After flashing with LGUP, the phone booted to stock firmware with no problems, so I executed:
adb reboot bootloader
fastboot oem lock
At this point, the phone rebooted and it was bricked, since now it shows:
"Your device has failed a routine safety check and will not boot."
I found this thread of a guy with the same problem:
https://forum.xda-developers.com/lg-g7-thinq/help/how-recover-phone-red-warning-boot-t3931975
Someone at the end of the thread claims to have solved it:
I successfully recovered from this by getting the v35 engeneering bootloader flashed dump someones frp partition with oem unlock toggled flash it to my phone with fastboot reboot to bootloader, do fastboot flashing unlock, use lgup to refurbish and you're unlocked and good to go again
Click to expand...
Click to collapse
One of the problems is indeed that I cannot unlock the bootloader again because I can't boot and check oem unlock in developer options (fastboot gives an explicit error).
The point is: could anyone describe this procedure a little better and tell me how to get this dump with oem unlock toggled and how to flash it with fastboot?
Other guys already asked on that thread, but he didn't answer...
Thank you in advance!

i have a problem after crossflash my g710pm and i have no 3g or 4g internet enabled, i change the apn and i reset all and flashed a different firmware and no lucky.

Try geting it to boot to download mode and flash kdz with lgup. It might be hard to try to time the reboot with volume and USB cable, I manage after maby 15 attempts

maydayind said:
Try geting it to boot to download mode and flash kdz with lgup. It might be hard to try to time the reboot with volume and USB cable, I manage after maby 15 attempts
Click to expand...
Click to collapse
I'm already able to boot both into download mode and fastboot mode, I tried flashing various kdz with LGUP... I think I'm going to take the phone to customer service.

@Emmeggi95 I can help! Send me a P.M.

I did the same thing a few weeks ago. I had a guy on here fix it for me with his octoplus, and then i ended up buying an octoplus medusa pro for myself for any future mistakes i make hahaha
The only way to fix this is with the octoplus jtag and unlocking the bootloader again through 9008 mode.

^^^sirbow2 is right. On my phone, I had only locked bootloader fastboot available, (It would boot to download mode for about half a second, then revert to the useless fastboot) and would not boot to system. I had to disassemble it (use heat gun and warm up back cover then carefully pull it off). Then remove the wireless charging coil. Then disconnect battery connector from the mainboard Then with tweezers touch the two test points and plug usb cable in while holding the tweezers to the test points, this caused the 9008 mode driver to install into the ports section of device manager. At that point, I was able to install the ULM11G ROM and go through the steps in loonycbg2's tutorial to bootloader unlock again. I installed the KDZ with octoplus pro, battery still disconnected, in emergency dl mode.
Hopefully, you wont have to go through all that, that's the most work anyone would have to do to unbrick one of these.

sirbow2 said:
I did the same thing a few weeks ago. I had a guy on here fix it for me with his octoplus, and then i ended up buying an octoplus medusa pro for myself for any future mistakes i make hahaha
The only way to fix this is with the octoplus jtag and unlocking the bootloader again through 9008 mode.
Click to expand...
Click to collapse
way2aware said:
^^^sirbow2 is right. On my phone, I had only locked bootloader fastboot available, (It would boot to download mode for about half a second, then revert to the useless fastboot) and would not boot to system. I had to disassemble it (use heat gun and warm up back cover then carefully pull it off). Then remove the wireless charging coil. Then disconnect battery connector from the mainboard Then with tweezers touch the two test points and plug usb cable in while holding the tweezers to the test points, this caused the 9008 mode driver to install into the ports section of device manager. At that point, I was able to install the ULM11G ROM and go through the steps in loonycbg2's tutorial to bootloader unlock again. I installed the KDZ with octoplus pro, battery still disconnected, in emergency dl mode.
Hopefully, you wont have to go through all that, that's the most work anyone would have to do to unbrick one of these.
Click to expand...
Click to collapse
Would love if yall would attempt to find the firehose used for the lg g7 thinq..
This would fully kill out the need for those boxes

loonycgb2 said:
Would love if yall would attempt to find the firehose used for the lg g7 thinq..
This would fully kill out the need for those boxes
Click to expand...
Click to collapse
Isn't that an internal LG thing? It's nearly impossible to obtain besides a leak, right?
way2aware said:
^^^sirbow2 is right. On my phone, I had only locked bootloader fastboot available, (It would boot to download mode for about half a second, then revert to the useless fastboot) and would not boot to system. I had to disassemble it (use heat gun and warm up back cover then carefully pull it off). Then remove the wireless charging coil. Then disconnect battery connector from the mainboard Then with tweezers touch the two test points and plug usb cable in while holding the tweezers to the test points, this caused the 9008 mode driver to install into the ports section of device manager. At that point, I was able to install the ULM11G ROM and go through the steps in loonycbg2's tutorial to bootloader unlock again. I installed the KDZ with octoplus pro, battery still disconnected, in emergency dl mode.
Hopefully, you wont have to go through all that, that's the most work anyone would have to do to unbrick one of these.
Click to expand...
Click to collapse
You dont have to disassemble the phone to get into 9008 mode. Hold power and vol down while quickly mashing vol up until you hear the device connect or see it in device manager. The screen stays black so, if you see the logo, you missed it.

sirbow2 said:
Isn't that an internal LG thing? It's nearly impossible to obtain besides a leak, right?
Click to expand...
Click to collapse
Firehose is a qualcomm file thats usually signed by the brand(oem).
Yes most of the time it either leaks or someone privately buys it from a dev of the oem for a good amount of money.

sirbow2 said:
Isn't that an internal LG thing? It's nearly impossible to obtain besides a leak, right?
You dont have to disassemble the phone to get into 9008 mode. Hold power and vol down while quickly mashing vol up until you hear the device connect or see it in device manager. The screen stays black so, if you see the logo, you missed it.
Click to expand...
Click to collapse
My phone was not capable of it, or I was incapable of it. Believe me I tried about 50 times, one after another.

way2aware said:
My phone was not capable of it, or I was incapable of it. Believe me I tried about 50 times, one after another.
Click to expand...
Click to collapse
ooohf, sorry. Yeah it is a pain. The time frame has to be a very small fraction of a second right after it shuts off and just starts to boot. Im probably hitting 4 or 5 presses a second could definitely be model dependent as well.

hellp
loonycgb2 said:
Would love if yall would attempt to find the firehose used for the lg g7 thinq..
This would fully kill out the need for those boxes
Click to expand...
Click to collapse
me puedes decir cual caja compraste

LG G7 ThinQ T mobile hard brick

Hi guys!
I tried to put the android 10 korean beta on my LG G7 ThinQ g710TM T-Mobile, and now it doesn't turn on, the laptop recognizes it as QUALCOMM 9008 MODE I just need to know if its trash already or there's a way that can unbrick the phone (really stupid I know)
Thank you in advance!

If the phone wasn't a T-Mobile:
May be able to flash v35.eng img onto the phone's abl_a partition (make sure this is backed up), then use fastboot commands to copy over the laf_a/_b files of the stock img. Then use download mode to revert back to Android 8/oreo.
May need to use, fastboot boot laf.img, to get onto download mode, as suggested here.

It was a t mobile damn never go for a t mobile again REALLY
paxar331 said:
If the phone wasn't a T-Mobile:
May be able to flash v35.eng img onto the phone's abl_a partition (make sure this is backed up), then use fastboot commands to copy over the laf_a/_b files of the stock img. Then use download mode to revert back to Android 8/oreo.
May need to use, fastboot boot laf.img, to get onto download mode, as suggested here.
Click to expand...
Click to collapse
It was a t mobile damn never go for a t mobile again REALLY

Pocketjam347 said:
It was a t mobile damn never go for a t mobile again REALLY
Click to expand...
Click to collapse
You can try my method to fix it?
https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
I

I don't understand one part
Awesomeslayerg said:
You can try my method to fix it?
https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841
I
Click to expand...
Click to collapse
I tried this method 2 days ago but for some reason when I try STEP 7: It says "Extracting kdz to ..." so I tried to wait a WHILE but after 4 hours of wait nothing happened so I was unable to do the next steps
Does it matter if the Phyton says that it was the end of its life?
Thank you so much for your post tho I believe you helped other people

Don't throw it away, I think there's a fix with QFIL.

I'm having a similar problem, but in my case I managed to accidentally erase laf_b from QFIL and this has corrupted my GPT. Now the QFIL partitioner can't see my partitions. Can you help? I may need a flat pack or something? I'm stuck in 9008 mode. The bootloader was unlocked but I couldn't get into fastboot to install TWRP and Lineage OS, so I ended up trying to erase laf_a and laf_b like it says to do in the V40 Qfil guide. Big mistake. Qfil and windows both recognize it as a 9008 device on Com3, but can't access the partitions.

I got the phone from a friend and i'm in the same position. The method from Awesomeslayerg just gives me sahara error

THE KHAMELEON said:
I got the phone from a friend and i'm in the same position. The method from Awesomeslayerg just gives me sahara error
Click to expand...
Click to collapse
See the FAQ in that guide.
Restart edl when connected to qfil or try different USB port or different PC.

lefttobleed said:
See the FAQ in that guide.
Restart edl when connected to qfil or try different USB port or different PC.
Click to expand...
Click to collapse
I don't have another PC to try it on. I been trying other ports and nothing. As I use my tweezers to put the phone in EDL I press download and still the error.
I don't know if this phone is T-Mobile or not. The IMEI shows T-Mobile but inside the phone shows numbers for Verizon

THE KHAMELEON said:
I don't have another PC to try it on. I been trying other ports and nothing. As I use my tweezers to put the phone in EDL I press download and still the error.
I don't know if this phone is T-Mobile or not. The IMEI shows T-Mobile but inside the phone shows numbers for Verizon
Click to expand...
Click to collapse
Not sure what's wrong with your phone...
Once I got out of this error by quickly pressing download when phone enters edl. Need to be fast.
Try that.

lefttobleed said:
Not sure what's wrong with your phone...
Once I got out of this error by quickly pressing download when phone enters edl. Need to be fast.
Try that.
Click to expand...
Click to collapse
To be honest I think it could be me just having the files in the wrong place or something else I'm doing wrong. All I get is Sahara error

Pocketjam347 said:
Hi guys!
I tried to put the android 10 korean beta on my LG G7 ThinQ g710TM T-Mobile, and now it doesn't turn on, the laptop recognizes it as QUALCOMM 9008 MODE I just need to know if its trash already or there's a way that can unbrick the phone (really stupid I know)
Thank you in advance!
Click to expand...
Click to collapse
Same problem with my phone.
I also try these things.
If you solved that problem then please share with me.

Question Bricked Mi PAD 5 PRO CN

Hello, i tried helping my grandmother by installing the global rom on her Xiaomi Mi Pad 5 Pro WIFI, however as it didn't work i tried forcing the rom onto it by flashing it manually using fastboot, after this i am not able to power it on, or reach fastboot. It's just a black screen it doesn't matter how long you hold the power key it's just completely black.. Is there something i can do???? Or is it completely destroyed?

Global ROM is not available for PRO version. Probably you flashed a wrong one. Try flashing back the CN one matches your model.

mkcs said:
Global ROM is not available for PRO version. Probably you flashed a wrong one. Try flashing back the CN one matches your model.
Click to expand...
Click to collapse
Ahh thats the thing, it won't even power on now, i cannot even access fastboot

desyncccccccc said:
Ahh thats the thing, it won't even power on now, i cannot even access fastboot
Click to expand...
Click to collapse
long press "Volume Down" + "Power" for a few seconds at the same time and then release only"Power" once the fastboot logo appears, finally release "Volume Down" to enter the fastboot mode

Its for xiaomi mi5
Maybe helps
Is there anything I can do? Brick help
My Xiaomi mi5 does not turn on. No lights, fastboot is not accessible, resetting it does not do anything. Basically for any combination of buttons that I press, nothing happens and the screen stays black - it is completely dead. However, when I...
forum.xda-developers.com

Keyvannn said:
Its for xiaomi mi5
Maybe helps
Is there anything I can do? Brick help
My Xiaomi mi5 does not turn on. No lights, fastboot is not accessible, resetting it does not do anything. Basically for any combination of buttons that I press, nothing happens and the screen stays black - it is completely dead. However, when I...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah so the only problem with this is that mine won't even show up even though i have said drivers installed.. I'm starting to think it's hard bricked

Hello, yes same as me. The tablet are in the 9008 edl state when you put it on your computer. there are many flashing tools out there, the problem are the flash authentification from xiaomis side. i prepared a empty pc with windows 10 and loaded the last fastboot image. then i got a telegram contact from a russian guy who was able to use the xiaomi auth procedure, cost me 30 dollar and 3 days to find out this crap

Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com

desyncccccccc said:
Hello, i tried helping my grandmother by installing the global rom on her Xiaomi Mi Pad 5 Pro WIFI, however as it didn't work i tried forcing the rom onto it by flashing it manually using fastboot, after this i am not able to power it on, or reach fastboot. It's just a black screen it doesn't matter how long you hold the power key it's just completely black.. Is there something i can do???? Or is it completely destroyed?
Click to expand...
Click to collapse
When it's plugged into the PC, is it recognised with "fastboot devices" or "adb devices"?
If it is you should be able to wipe with "fastboot -w" and start again.
Google detailed instructions.

mikefnz said:
When it's plugged into the PC, is it recognised with "fastboot devices" or "adb devices"?
If it is you should be able to wipe with "fastboot -w" and start again.
Google detailed instructions.
Click to expand...
Click to collapse
Unfortunately no, i do not get any response from fastboot whatsoever, there's no device detection in either fastboot or device manager. I even tried on my laptop which is brand new still no sign of life

fritzeman said:
Hello, yes same as me. The tablet are in the 9008 edl state when you put it on your computer. there are many flashing tools out there, the problem are the flash authentification from xiaomis side. i prepared a empty pc with windows 10 and loaded the last fastboot image. then i got a telegram contact from a russian guy who was able to use the xiaomi auth procedure, cost me 30 dollar and 3 days to find out this crap
Click to expand...
Click to collapse
Where would i be able to get in contact with someone like that??

desyncccccccc said:
Unfortunately no, i do not get any response from fastboot whatsoever, there's no device detection in either fastboot or device manager. I even tried on my laptop which is brand new still no sign of life
Click to expand...
Click to collapse
Try different cable & different pc usb slot?

Try flashing using * Xiaomi professional pro tools . Buy credit and all done,

mikefnz said:
Try different cable & different pc usb slot?
Click to expand...
Click to collapse
Unfortunately any cable/pc i try i get the same result, i'm debating wether i should just get a new one for her with global rom instead

desyncccccccc said:
Unfortunately any cable/pc i try i get the same result, i'm debating wether i should just get a new one for her with global rom instead
Click to expand...
Click to collapse
Don't give up yet!
Charge the tablet with another cable that you know works.
Make sure that you have the most up to date version of Platform Tools.
Make sure that when you're in the Command Prompt that you are in the Platform Tools folder.
Check connections with another device....

mikefnz said:
Don't give up yet!
Charge the tablet with another cable that you know works.
Make sure that you have the most up to date version of Platform Tools.
Make sure that when you're in the Command Prompt that you are in the Platform Tools folder.
Check connections with another device....
Click to expand...
Click to collapse
Hello again, i tried with all possible cables and or devices, somehow it still does not show up, i am rather confused and thinking that i might've broke it fully

desyncccccccc said:
Hello again, i tried with all possible cables and or devices, somehow it still does not show up, i am rather confused and thinking that i might've broke it fully
Click to expand...
Click to collapse
Buy an EDL Cable For Qualcomm 9008 Mode for deep flashing

desyncccccccc said:
Hello again, i tried with all possible cables and or devices, somehow it still does not show up, i am rather confused and thinking that i might've broke it fully
Click to expand...
Click to collapse
Have you got the most up to date version of Platform-tools installed and are you checking the connection from a CMD prompt in that Platform-tools folder?

mkcs said:
Buy an EDL Cable For Qualcomm 9008 Mode for deep flashing
Click to expand...
Click to collapse
Could you please link me one of those? I'm over in the EU so maybe they'll be fairly easy to find?

mikefnz said:
Have you got the most up to date version of Platform-tools installed and are you checking the connection from a CMD prompt in that Platform-tools folder?
Click to expand...
Click to collapse
Yeah, i've been doing all of that. I just now found out that there's an EDL cable specifically made for flashing in that mode

Question LineageOS Bootloop within 1 second

Hi Guys,
Oneplus 9 Pro
I installed LineageOS 19.1 and Gapps and all worked fine. The phone booted up and entered setup. I skipped setting it up as I wanted to relock the bootloader so I could use Google Pay.
After rebooting into fastboot, I typed in "fastboot oem lock" and now I'm in an infinite loop. Phone starts up for 1/2 a second I see the startup flash for a split second and then it reboots.
I cant enter fastboot mode or recovery and holding down vol up or down does nothing along with holding power button. The phone literally stays on for 0.5 secs...
Please help

..

hidara said:
Hi Guys,
Oneplus 9 Pro
I installed LineageOS 19.1 and Gapps and all worked fine. The phone booted up and entered setup. I skipped setting it up as I wanted to relock the bootloader so I could use Google Pay.
After rebooting into fastboot, I typed in "fastboot oem lock" and now I'm in an infinite loop. Phone starts up for 1/2 a second I see the startup flash for a split second and then it reboots.
I cant enter fastboot mode or recovery and holding down vol up or down does nothing along with holding power button. The phone literally stays on for 0.5 secs...
Please help
Click to expand...
Click to collapse
You cant relock bootloader on a custom rom unless stated so.the only option you have is to try and get it into edl mode and msm back to stock

gillim74 said:
You cant relock bootloader on a custom rom unless stated so.the only option you have is to try and get it into edl mode and msm back to stock
Click to expand...
Click to collapse
Thank you. Just managed to get into fastboot by holding both vol up and down at the same time. Reflashing now. I hear of people relocking the bootloader after installing LineageOS. Is there any way to do this. All I really want is google pay
Cheers for the help

hidara said:
Thank you. Just managed to get into fastboot by holding both vol up and down at the same time. Reflashing now. I hear of people relocking the bootloader after installing LineageOS. Is there any way to do this. All I really want is google pay
Cheers for the help
Click to expand...
Click to collapse
If you want Google Pay, locking bootloader won't help you.
Set your fingerprint to an A11 print with props config, install Universal SafetyNet fix, and clear data on play services. Easy.

Umgak said:
If you want Google Pay, locking bootloader won't help you.
Set your fingerprint to an A11 print with props config, install Universal SafetyNet fix, and clear data on play services. Easy.
Click to expand...
Click to collapse
Appreciated though my phone is now a paperweight . No fastboot etc. Just a blank screen. Qualcomm driver detected when I plug it in but MSM tool fails ;(

From my understanding you should never re-lock your bootloader unless you're on stock, with no modifications flashed, unless you want to deal with a bricked phone. MSM is your only hope. When you open the MSM tool you need to put your phone in EDL Mode you have connect it to the MSM tool quickly, is that the issue? If you have the Qualcomm driver detected then, maybe you're missing a vital step?

hidara said:
Appreciated though my phone is now a paperweight . No fastboot etc. Just a blank screen. Qualcomm driver detected when I plug it in but MSM tool fails ;(
Click to expand...
Click to collapse
This isn't very descriptive. MSM Tool is fussy, you have to use the right combo of settings and you have to be quick about it.
Open the MSM Tool, check use lite firehose, click Start so it's already looking for the phone, press and hold both volume buttons and while doing so connect the cable.
If it gives you device not match image error, try to uncheck Sha256 check too and if that doesn't work, download the Indian variant MSM and try that.
lemonadep_22_I.07_210412.zip | by craznazn for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
If that works, you then need to flash the appropriate downgrade package to get back on the right software for your model. Unlock the bootloader and use the local update tool and flash the downgrade package from your model from here - https://forum.xda-developers.com/t/oneplus-9-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254587/
If your phone can go into EDL, it should be able to be recovered, it just is the matter of finding the right combination.

EtherealRemnant said:
This isn't very descriptive. MSM Tool is fussy, you have to use the right combo of settings and you have to be quick about it.
Open the MSM Tool, check use lite firehose, click Start so it's already looking for the phone, press and hold both volume buttons and while doing so connect the cable.
If it gives you device not match image error, try to uncheck Sha256 check in too and if that doesn't work, download the Indian variant MSM and try that. PL
lemonadep_22_I.07_210412.zip | by craznazn for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
If that works, you then need to flash the appropriate downgrade package to get back on the right software for your model. Unlock the bootloader and use the local update tool and flash the downgrade package from your model from here - https://forum.xda-developers.com/t/oneplus-9-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254587/
If your phone can go into EDL, it should be able to be recovered, it just is the matter of finding the right combination.
Click to expand...
Click to collapse
Thanks for the advice. Not sure if it's having the Chinese version is the issue but heres what I tried.
Tried the EU and global version of MSM.
With stock settings I get
"Sahara communication failed"
With lite firehouse checked I get "incorrect image ......" With and without SHA.. checked. Tried to download the Indian rom but got an anti-virus message (had these with Linux based PC/Android images before so we going to revisit)
This is where I was at when I posted the paperweight message above and had spent the day on it, not a great idea when you're in the middle of Uni exams
Will revisit the Indian rom though. Thanks for the advice again

hidara said:
Thanks for the advice. Not sure if it's having the Chinese version is the issue but heres what I tried.
Tried the EU and global version of MSM.
With stock settings I get
"Sahara communication failed"
With lite firehouse checked I get "incorrect image ......" With and without SHA.. checked. Tried to download the Indian rom but got an anti-virus message (had these with Linux based PC/Android images before so we going to revisit)
This is where I was at when I posted the paperweight message above and had spent the day on it, not a great idea when you're in the middle of Uni exams
Will revisit the Indian rom though. Thanks for the advice again
Click to expand...
Click to collapse
The Indian MSM Tool doesn't seem to actually run those checks to make sure the device firmware matches for some reason. I have used it on my regular 9 to recover it when none of the other MSM Tools would work.
Disable your antivirus before running MSM Tool as it can trigger false positives. None of these files are infected though. They all trigger multiple false positives but the EXE is the same across all of them.
VirusTotal
VirusTotal
www.virustotal.com

EtherealRemnant said:
The Indian MSM Tool doesn't seem to actually run those checks to make sure the device firmware matches for some reason. I have used it on my regular 9 to recover it when none of the other MSM Tools would work.
Disable your antivirus before running MSM Tool as it can trigger false positives. None of these files are infected though. They all trigger multiple false positives but the EXE is the same across all of them.
VirusTotal
VirusTotal
www.virustotal.com
Click to expand...
Click to collapse
Wooohoooo I'm back. Thank you

hidara said:
Wooohoooo I'm back. Thank you
Click to expand...
Click to collapse
Glad that you got it all sorted out!