Database Info

[Q] Bricked phone. Odin and Oneclick does not recognize my device. Help?

I am not sure if i am on the right section. Just kindly move this thread to the right section if im wrong. Thanks.
So, i have flashed Cyanogenmod Rom on my GT 15800 phone using Odin Multidownloader v 2.252.
The flash was successful, then i tweaked on some settings on the recovery and got my phone bricked.
I can still access download mode through voldown+homekey+powerbutton.
Before, i can also access the recovery mode.
I have tried odin to reflash again CWM on my phone, but is stucked on factory.rfs for an hour so i tried to abort it. Closed Odin and unplugged the USB cable.
Now, i cant access the recovery mode. Whenever i open my phone and access recovery mode, i get this.
And Odin doesnt recognize my phone anymore.
Kies aren't running also.
{
"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"
}
But i can still access Download mode.
While trying OneClick Unbrick from here http://forum.xda-developers.com/showthread.php?t=1153310
I always get this error message.
Yes, my phone is connected to the computer and is in download mode. So i tried clicking on the resolution center.
So i tried the first solution and this is what i get.
Im running on Windows 7 Home Premium 64-bit.
When I tried the second one, everything worked fine.
And for the third one, it worked fine too.
Now, im running out of solutions on how to unbrick my phone. I have tried everything I can.
Can anyone help me?

Dannahsaur said:
I am not sure if i am on the right section. Just kindly move this thread to the right section if im wrong. Thanks.
So, i have flashed Cyanogenmod Rom on my GT 15800 phone using Odin Multidownloader v 2.252.
The flash was successful, then i tweaked on some settings on the recovery and got my phone bricked.
I can still access download mode through voldown+homekey+powerbutton.
Before, i can also access the recovery mode.
I have tried odin to reflash again CWM on my phone, but is stucked on factory.rfs for an hour so i tried to abort it. Closed Odin and unplugged the USB cable.
Now, i cant access the recovery mode. Whenever i open my phone and access recovery mode, i get this.
And Odin doesnt recognize my phone anymore.
Kies aren't running also.
But i can still access Download mode.
While trying OneClick Unbrick from here http://forum.xda-developers.com/showthread.php?t=1153310
I always get this error message.
Yes, my phone is connected to the computer and is in download mode. So i tried clicking on the resolution center.
So i tried the first solution and this is what i get.
Im running on Windows 7 Home Premium 64-bit.
When I tried the second one, everything worked fine.
And for the third one, it worked fine too.
Now, im running out of solutions on how to unbrick my phone. I have tried everything I can.
Can anyone help me?
Click to expand...
Click to collapse
I have faced the same problem with my home PC. But it detected with my office PC. Maybe windows stopped detecting it due to errors in drivers. Try on another pc or format your windows installation.

sekhargreen said:
I have faced the same problem with my home PC. But it detected with my office PC. Maybe windows stopped detecting it due to errors in drivers. Try on another pc or format your windows installation.
Click to expand...
Click to collapse
After trying it with another PC, you were able to unbrick your phone?

Try re-installing your drivers,that may help you out

it looks like you need a 32bit Windows version to use OneClick Unbrick
give it a try on another pc

I have the Problem
hello i have the same problem.
im using Odin 3 but it doesnt reconized it, i got all the drivers, the oneClick Unbrick was avaible to brick back the device, but now i cant flash it anymore, because Odin doesnt reconized it.
ive tried everything please help me.
Im running everything on Windows 7 32bits

Try this.
Take out the battery.now,while the battery is out,plug your phone into pc,and while holding vol down+home+power and phone plugged in,someone that can help you needs to put the battery while you are holding all this.it worked that way for me,i had the odin doesnt recognize problem.i tried two pc's,it didnt work.
Sent from my GT-I5800 using xda premium

First of all remember if you have usb debugging is ON.Secondly try on other pc Desktop,Laptop,Macbook and different versions.Thirstly use odin 3.Finally if it's stuck it's software problem try searching the right Stock roms for your phone.Hope this helps..Be careful with modding your phone you can no longer use android.

Try flashing zerofill tar first through force recovery mode. Refer to my old post from profile for step by step procedure.
Sent from my LG-E610 using xda app-developers app

[Q] Downgrade to 4.2.2 Xperia L stock bootloader unlocked

Hi guys.
I need your help very urgently.
Update my phone to android 4.4.4 and I only realized until that moment that CM11 has no radio support on many devices.
I wanted to install the stock firmware but unfortunately 15.3.A.1.14 open my bootloader after I failed to make the connect via FlashBoot.
That is, if I try to connect to fastboot I have no problems doing that and that's that mean flashing kernels, but if I connect the phone to flash mode the LED does not light,
Although flashtools if recognized as a device connected in this way, if I try to flash the firmware via everything starts normally but before end I throw an error.
Anyone have an idea that I can do, and be able to tell me why this is happening?
I appreciate your help, and I hope you can understand my English is lousy.

Stronger1101 said:
Hi guys.
I need your help very urgently.
Update my phone to android 4.4.4 and I only realized until that moment that CM11 has no radio support on many devices.
I wanted to install the stock firmware but unfortunately 15.3.A.1.14 open my bootloader after I failed to make the connect via FlashBoot.
That is, if I try to connect to fastboot I have no problems doing that and that's that mean flashing kernels, but if I connect the phone to flash mode the LED does not light,
Although flashtools if recognized as a device connected in this way, if I try to flash the firmware via everything starts normally but before end I throw an error.
Anyone have an idea that I can do, and be able to tell me why this is happening?
I appreciate your help, and I hope you can understand my English is lousy.
Click to expand...
Click to collapse
Post the screenshot of the error!

{
"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"
}
[/url][/IMG]
david pro said:
Post the screenshot of the error!
Click to expand...
Click to collapse
Thank repsonder, this is the error.
However I must clarify what I have all drivers installed and up before upgrading the phone was detected in flash mode.

Stronger1101 said:
[/url][/IMG]
Thank repsonder, this is the error.
However I must clarify what I have all drivers installed and up before upgrading the phone was detected in flash mode.
Click to expand...
Click to collapse
Try again!!! One day, It happened with me too!!!
Try Changing the Cable or USB port!
:highfive:

david pro said:
Try again!!! One day, It happened with me too!!!
:highfive:
Click to expand...
Click to collapse
Try changing ftf. If still not resolved, try changing flashtool.
Best of luck
Hit thanks if it helps.

still connect flash mode
abhi007.john said:
Try changing ftf. If still not resolved, try changing flashtool.
Best of luck
Hit thanks if it helps.
Click to expand...
Click to collapse
Unfortunately the failure seems to be on the phone and tried it on another pc and the problem persists.
When I connect it with the volume down button, the LED lights green and then red for less than half a second, the pc makes the sound of announcing that something was connected but the phone does not turn on but the led.
The problem is that I have several tested tft and the result is the same, even though flashtool flash mode recognizes something is not right and I assume that's why flash it throws error.
I had the idea to flash in fastboot mode tft but I'm afraid to leave me a hardbrick,:crying:

Stronger1101 said:
Unfortunately the failure seems to be on the phone and tried it on another pc and the problem persists.
When I connect it with the volume down button, the LED lights green and then red for less than half a second, the pc makes the sound of announcing that something was connected but the phone does not turn on but the led.
The problem is that I have several tested tft and the result is the same, even though flashtool flash mode recognizes something is not right and I assume that's why flash it throws error.
I had the idea to flash in fastboot mode tft but I'm afraid to leave me a hardbrick,:crying:
Click to expand...
Click to collapse
I don't think that the red led keeps glowing when you connect on flash mode. It just flashes green and red once.
Also did you an updated flashtool on the other pc?
if not then try once with another cable। and flashtool.

abhi007.john said:
I don't think that the red led keeps glowing when you connect on flash mode. It just flashes green and red once.
Also did you an updated flashtool on the other pc?
if not then try once with another cable। and flashtool.
Click to expand...
Click to collapse
so it is, and try in another pc and another cable but I can not make connect, I have desperate

Stronger1101 said:
so it is, and try in another pc and another cable but I can not make connect, I have desperate
Click to expand...
Click to collapse
One more thing, the companion I recognized only when the computer is turned on but if I turn it off and connect in flash mode does not detect it.

Stronger1101 said:
One more thing, the companion I recognized only when the computer is turned on but if I turn it off and connect in flash mode does not detect it.
Click to expand...
Click to collapse
If I try to flash the firmware via fastboot damage my phone?

Stronger1101 said:
If I try to flash the firmware via fastboot damage my phone?
Click to expand...
Click to collapse
First of all, your english is terrible mate.
As far as I know you can't use fastboot to flash a firmware. I believe it's only for flashing kernels.
Also, make sure you have the required drivers installed. You can download latest drivers from here
http://forum.xda-developers.com/showthread.php?t=2635830
Along with that make sure you use an updated flashtool.
Head over to the general threadand you will find it
Hope it helps
Hit thanks if it does.

hei man, same **** hapens to me, try to use a old version of flashtool, 0.9.11.0 works for me

Hard bricked my OnePlus One by just rebooting it, help! [5$ REWARD]

I will be straightforward:
I bought an used OPO, I booted it up, configured the phone, took a photo and then decided to reboot it (turn off and then turn on), then my device simply hard bricked.
1. I already tried turning it on, the device does nothing (no vibration).
2. I already tried using Power + Vol Up and Power + Vol Down, nothing happens (no vibration).
3. Windows recognizes the device as "QHSUSB_BULK", I already tried installing the drivers and using ColorOS flashing tool from here http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , the device IS RECOGNIZED by the tool, but when I start flashing, it starts a loop when trying to flash the "8974_msimage.mbn" file (the progress bar goes until the end and then the process repeat in the same file).
Yes, the device has the bootloader unlocked, because the previous owner flashed a custom ROM, custom kernel and SuperSU.
No, the device isn't recognized by adb.
No, the device isn't recognized by fastboot.
I already tried searching on Google for this issue, everyone who had this issue never replied saying that they fixed the issue...
I never had any kind of soft/hard brick on my Moto G 2014 (and I flashed custom ROMs constantly on it)... so... can someone help me? Thanks!
I'm also willing to give 5$ on PayPal to someone who can fix this issue.

Also, if I try to use the ColorOS flashing tool, the device disconnects in the middle of the process, causing the infinite flash loop.

First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English

sino1641 said:
First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English
Click to expand...
Click to collapse
Nah, your english is fine, I could understand what you are saying.
{
"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"
}
After I clicked "Start"
Then the "device plugged in" sound plays and the process repeats...
It keeps doing this:
(If you can't view the images, click here:
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-39-42.png
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-40-18.png
http://lori.mrpowergamerbr.com/sharex/2016-07-22_10-41-05.gif
)

Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.

sino1641 said:
Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.
Click to expand...
Click to collapse
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers

MrPowerGamerBR said:
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers
Click to expand...
Click to collapse
Open Device Manager.
Press Power &Vol Up for about 10 seconds.
See if it will change between 9008 and 9006.

I have same thing did it work
I am just wondering if u managed to fix it.

I had the exact same issue. To stop the device from disconnecting, I needed to remove all existing drivers, let the phone charge, plug it into the PC. Hold volume up + power until the PC recognises it. Then I used the color OS flashing tool.
I had to run it as administrator, and it worked fine on Windows 10, without anything extra. However remember you'll lose all your stuff. Lucky for me I had a backup of my entire phone on my PC when I switched file system to F2FS.
This issue in itself has really baffled me. It happened to me when flashing sultans rom, and the phone completely bricked. However I'm using the rom now after fully recovering the device... I guess it's just down to bad luck?

mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Nope, never fixed it, I don't even have the device anymore (now rocking a Moto G Turbo)

mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Don't use "msm8974-download-manager" use qfil to recover the phone. Worked for me.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/

Download 2012 qhs diagnostic driver and use xp machine.It will work just fine.

install a fresh windows either x32/x64 winxp/win 7 extract color OS and install the correct drivers

Accidentally wiped phone system OS using TWRP; how can I fix this?

I have basic to medium experience relating to rooting, fastboot, Odin, flashing, etc.
I accidentally wiped my phone's OS. My phone is a Samsung S5 Neo SM-903W with no root and no unlocked bootloader but with TWRP installed. My OS was Android 6.0.1
I tried downloading the stock firmware of Android 6 and flashing it using an SD card; TWRP said it was an invalid zip file and did not find an md5 ( even though it was the only file in the zip)
When I am in TWRP, my laptop recognizes me as "Samsung Mobile MTP Device" but when I am in download mode, my phone is not recognized at all. I think that I need to flash drivers on my phone, but I have no idea how to do so, and if so, how can I flash an "invalid zip file" onto my phone?
Please help me, or at least give me some advice.
Thanks (I'm an idiot for experimenting with advanced wipe )

MCMarsBoyee said:
I have basic to medium experience relating to rooting, fastboot, Odin, flashing, etc.
I accidentally wiped my phone's OS. My phone is a Samsung S5 Neo SM-903W with no root and no unlocked bootloader but with TWRP installed. My OS was Android 6.0.1
I tried downloading the stock firmware of Android 6 and flashing it using an SD card; TWRP said it was an invalid zip file and did not find an md5 ( even though it was the only file in the zip)
When I am in TWRP, my laptop recognizes me as "Samsung Mobile MTP Device" but when I am in download mode, my phone is not recognized at all. I think that I need to flash drivers on my phone, but I have no idea how to do so, and if so, how can I flash an "invalid zip file" onto my phone?
Please help me, or at least give me some advice.
Thanks (I'm an idiot for experimenting with advanced wipe [emoji14] )
Click to expand...
Click to collapse
The stock firmware cannot be flashed with TWRP. It is built to be flashed with Odin.
If there is a stock firmware that has been converted into a custom recovery flashable zip, you can flash that in TWRP, it has to be converted from the Odin flashable firmware though, it can't be the actual downloaded firmware, it isn't compatible with recovery. This is only if such a file is available or if you learn to convert the firmware yourself.
The easiest thing would be to get your device recognized with Odin while in download mode so you can flash the firmware, this should restore your device. Try installing the USB drivers for Samsung phones from here:
http://www.samsungusbdrivers.net/2016/12/samsung-galaxy-s5-neo-usb-driver-for.html?m=1
Flashing the stock firmware via Odin will also remove TWRP and replace it with stock recovery, you'll have to flash TWRP again.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

The thing is, I installed TWRP via Odin, so I know there was (or is) nothing wrong with the drivers on my laptop, but after the system wipe, my phone could only be recognized by Odin if it was charging through it or if I was at TWRP. (the 0:COM indicator was pink, not green) I will try the method you mentioned, but if I have any difficulties I will come back here.
Thanks.

MCMarsBoyee said:
The thing is, I installed TWRP via Odin, so I know there was (or is) nothing wrong with the drivers on my laptop, but after the system wipe, my phone could only be recognized by Odin if it was charging through it or if I was at TWRP. (the 0:COM indicator was pink, not green) I will try the method you mentioned, but if I have any difficulties I will come back here.
Thanks.
Click to expand...
Click to collapse
When you are in download mode, connect to PC then open device manager and see if it at least detects the device, even if it isn't recognizing it correctly. Does it show anything in device manager? What does it show?
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

I have a problem.
Since Samsung Drivers were already installed, I re-installed it by running the installer and prompting it to install it again. The problem is, when I try updating my "Samsung Mobile MTP Device"'s drivers, they say that the drivers installed are already at the latest version. I tried this several times, with a different type of drivers like ADB, and it still said that they were the latest (which is Samsung Mobile MTP Device).
Here is a screenshot to make sense of it
{
"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"
}
(If the screenshot doesn't show just tell me and I will try again)
Please help! I am in no situation of getting a new phone anytime soon!

MCMarsBoyee said:
I have a problem.
Since Samsung Drivers were already installed, I re-installed it by running the installer and prompting it to install it again. The problem is, when I try updating my "Samsung Mobile MTP Device"'s drivers, they say that the drivers installed are already at the latest version. I tried this several times, with a different type of drivers like ADB, and it still said that they were the latest (which is Samsung Mobile MTP Device).
Here is a screenshot to make sense of it
(If the screenshot doesn't show just tell me and I will try again)
Please help! I am in no situation of getting a new phone anytime soon!
Click to expand...
Click to collapse
Try installing Kies, it automatically installs Samsung drivers correctly.
But make sure kies is completely closed and not running in the background when using Odin, it interferes.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

MCMarsBoyee said:
I have a problem.
Since Samsung Drivers were already installed, I re-installed it by running the installer and prompting it to install it again. The problem is, when I try updating my "Samsung Mobile MTP Device"'s drivers, they say that the drivers installed are already at the latest version. I tried this several times, with a different type of drivers like ADB, and it still said that they were the latest (which is Samsung Mobile MTP Device).
Here is a screenshot to make sense of it
(If the screenshot doesn't show just tell me and I will try again)
Please help! I am in no situation of getting a new phone anytime soon!
Click to expand...
Click to collapse
Thank you! It works perfectly! Marking as solved.

MCMarsBoyee said:
Thank you! It works perfectly! Marking as solved.
Click to expand...
Click to collapse
Which parts of what I posted solved it for you? It will help others understand if they read this thread.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

I think I killed my brand new phone

I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.

Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David

DvdStrbl said:
Hi!
I really don't know if this helps because you might have already tried it, but I had a similar problem where the normal fastboot mode didnt work and I had no Recovery. Someone suggested, that I should hold Volume Up, Volume down and the Power button all at the same time and from there I was able to revive the phone with the All-In-One Tool...
I quickly looked up the Qualcomm Mode and MSM-Tool you mentioned but I'm still not sure if that is what I just described, so Im posting this just to make sure you tried it because it was a really easy fix when I thought I bricked my phone
Sorry if you already did it, anyway Good Luck!
David
Click to expand...
Click to collapse
Well see the issue is I'm trying to get All in One to recognize my phone but it won't seem to boot into EDL mode. I installed the Qualcomm USB drivers but it's still not showing my phone. When I use the key combo suggested to boot into EDL mode my phone does refresh in device manager giving me the qualcomm device so I assume this is download mode just not displaying the text anymore. If i try the key combo with my phone unplugged it takes awhile but eventually goes into fastboot.

In this case I can't help you, i googled EDL, it is what I meant and it was all I got :-/
Wish you good luck

If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

Bradl79 said:
If your bootloader is unlocked try to flash the fastboot rom from fastboot.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
When I try flashing anything at fastboot it just hangs waiting

viralhysteria said:
I've been running the crDroid OOS 10 OB3 ROM since I got my phone two weeks ago and everything was fine and I updated to OB4 today. Well, after I tried changing system ui themeing my phone stopped displaying any system ui at all so I tried to restore my nandroid backup. My nandroid backup took 4 hours then when it got to bluetooth my battery was dying so I had to stop it.
I rebooted into TWRP and tried to clean flash the rom but it gave me errors about mounting the data partition so I tried changing slots.
Well after I changed slots I am stuck in fastboot mode and can't get back to TWRP and adb wont recognize my phone. There's no bootloader or baseband version displayed on fastboot and the product name/variant is msmnile/SDM UFS, my phone is still unlocked if it matters. Someone in the ROM telegram suggested I try the MSM tool but my phone doesn't seem to want to boot into Qualcomm mode and I'm worried that might be a big issue.
Click to expand...
Click to collapse
what the problem u are facing while flashing from msm tools?

If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.

whoamanwtf said:
If you haven't fixed your phone yet just use MSMtool it will fix it, this phones essentially unbrickable.
Click to expand...
Click to collapse
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date

Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.

viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
During Installing drivers again choose the option (something of) search from internet. And let the file be downloaded and install. Trust me this method works. I too had same problem

whoamanwtf said:
Well you need to hit start once it's connected. https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691 follow the instructions there with the phone being unplugged and powered off open msm hold volumes while not hitting power at all and wait then plug into the computer.
Click to expand...
Click to collapse
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?

viralhysteria said:
I installed the qualcomm drivers and it showed up in MSM tool and gave me success after 6 seconds but nothing else happened so I unplugged my phone now it says device descriptor failed when I try to go into qualcomm mode
If i uninstall the drivers and try again same thing and trying to use the qualcomm driver files tells me my driver is already up to date
Click to expand...
Click to collapse
viralhysteria said:
Okay I got the descriptor issue to stop and MSM is detecting the phone again but its still not booting to anything when I run the tool like the guide said it should. I do upgrade mode right?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good. It's Android 9 but that doesn't matter, you can update from there once your phones working again.

whoamanwtf said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I meant to send that one, follow those instructions and you'll be good.
Click to expand...
Click to collapse
It says to wait about 5 minutes after starting but I get stuck at this
{
"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"
}

Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work

whoamanwtf said:
Where did you get the files you're using? Maybe download one from my link, they're the only ones I've personally used and can say for sure they work
Click to expand...
Click to collapse
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?

viralhysteria said:
Your file does the same thing
The connection status switches to N/A but if i stop it and enum it still detects the phone
I used the drivers provided in your link and it still doesnt seem to work
that status bar at the bottom says Running: Upgrade though but thats just an indicator of the job task, no?
Click to expand...
Click to collapse
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.

whoamanwtf said:
Send a larger screen grab of the MSMtool running, I don't recognize what you sent.
Click to expand...
Click to collapse

So it sounds dumb but try rebooting your computer and switching USB ports then trying again.

whoamanwtf said:
So it sounds dumb but try rebooting your computer and switching USB ports then trying again.
Click to expand...
Click to collapse
Same thing it just assigned a new COM port