Database Info

[Q] Cant enter apx mode, cant usb debug, cant mount sdcard, cant update sdcard.

I had an old flash and wanted to update. I was going to update to Nightlies. Couldn't go into usb debugging. Chose zip from sdcard and it says can't mount /sdcard/. Tried to apply /sdcard/update.zip and cant mount and aborts. I decided after rt wants me to enter APX mode (which is volume up and power) nothing. My finger is cramped now from holding for so long. "What do I do wid these keeds," says Cartman. If I could just get APX mode to work, I was going to flash updated Asus Firmware and start over.........help?

hutchrt said:
I had an old flash and wanted to update. I was going to update to Nightlies. Couldn't go into usb debugging. Chose zip from sdcard and it says can't mount /sdcard/. Tried to apply /sdcard/update.zip and cant mount and aborts. I decided after rt wants me to enter APX mode (which is volume up and power) nothing. My finger is cramped now from holding for so long. "What do I do wid these keeds," says Cartman. If I could just get APX mode to work, I was going to flash updated Asus Firmware and start over.........help?
Click to expand...
Click to collapse
From my understanding of APX mode:
Step 1:
Install the naked drivers (IDK where to find them, however they are in this forum)
Step 2:
Connect your USB cable
Step 3:
Press power and volume up.
Step 4:
Wait for USB connection tone from windows
Step 5:
Profit

did that
ghost0001 said:
From my understanding of APX mode:
Step 1:
Install the naked drivers (IDK where to find them, however they are in this forum)
Step 2:
Connect your USB cable
Step 3:
Press power and volume up.
Step 4:
Wait for USB connection tone from windows
Step 5:
Profit
Click to expand...
Click to collapse
When I do that while it is on......it just powers off. When I do that when it is off, it does make the sound on my computer, but computer is still off. Press up and power.......still stays off.

hutchrt said:
When I do that while it is on......it just powers off. When I do that when it is off, it does make the sound on my computer, but computer is still off. Press up and power.......still stays off.
Click to expand...
Click to collapse
Weird, that should have worked. your unit should already be off. then use the button combo to power up into APX mode. the screen stays off in APX mode. the only way you know it is in APX mode is when the windows PC detects it plugged in as a USB device. am i reading correctly? you are saying that pushing the button combo will not power up the unit in APX mode?

ghost0001 said:
Weird, that should have worked. your unit should already be off. then use the button combo to power up into APX mode. the screen stays off in APX mode. the only way you know it is in APX mode is when the windows PC detects it plugged in as a USB device. am i reading correctly? you are saying that pushing the button combo will not power up the unit in APX mode?
Click to expand...
Click to collapse
Yup! I hear the sound on the computer suggesting it went into the APX mode, but screen is still off. If I remember correctly, isnt there suppose to be a screen for APX mode? Even if there isnt, I tried to follow through with the program to change it and it is if it never went into the mode.

hutchrt said:
Yup! I hear the sound on the computer suggesting it went into the APX mode, but screen is still off. If I remember correctly, isnt there suppose to be a screen for APX mode? Even if there isnt, I tried to follow through with the program to change it and it is if it never went into the mode.
Click to expand...
Click to collapse
I did APX mode before on my droid 2, and the screen never came on. It just stayed black. Got the connection sound and then did a push to my device. I had a bad upgrade while I was in Iraq/Kuwait over WiFi for the phone. It killed the CDMA portion of the phone. I didn't know because I only used the WiFi at the time. Anyways, to make a long story short. There are some commands you can use to see if you can communicate with your device via APX mode. I think there is a shell program out there that will run in Command Prompt. You can issue commands to make sure your device is recognized via APX.

clueless
ghost0001 said:
I did APX mode before on my droid 2, and the screen never came on. It just stayed black. Got the connection sound and then did a push to my device. I had a bad upgrade while I was in Iraq/Kuwait over WiFi for the phone. It killed the CDMA portion of the phone. I didn't know because I only used the WiFi at the time. Anyways, to make a long story short. There are some commands you can use to see if you can communicate with your device via APX mode. I think there is a shell program out there that will run in Command Prompt. You can issue commands to make sure your device is recognized via APX.
Click to expand...
Click to collapse
I am clueless how to do that! It does sound like something that would work though I've never entered commands on my computer to do something like that.

hutchrt said:
I am clueless how to do that! It does sound like something that would work though I've never entered commands on my computer to do something like that.
Click to expand...
Click to collapse
Also, if I am not mistaken, if you look under device manager, you should see your device under USB.

[Help] Bricked my Nexus what's next? :(

Hi, this situation is kind of strange and I hope it's just the battery and not the whole goddamn phone.
What I'm dealing with at the moment is:
The phone doesn't boot
When plugged onto charger or USB cable it boots but stuck at Google logo after a blink and stays there. Also, Home, Back and other buttons are lighten.
When "forcefully" put into fastboot mode, e.g. after plugging it onto USB and instantly pressing Vol Up + Power it stuck there as well, volume rocker no more response neither does the power button. Also, I notice there are no commands at the end like "USB int" etc we see normally.
Fastboot or ADB returns no device found
Please help. I personally believe it could be due to battery, what do you guys think?
Thank you.

As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.

ej8989 said:
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
Click to expand...
Click to collapse
Thanks. My OS is Windows 8.1 Update 1. The last thing was to install UPDATE-SuperSU to root so that I can install ROM Manager to update Recovery but the installation was aborted so I attempt to flash it via Fastboot with success. Then, wanted to install SlimKat but it couldn't let me mount USB storage so that I can put the .zip file. I, then stupidly click on install via ADB but didn't know how to go back so I pulled the battery and powered up; used ADP push command to transfer said the file, but again for some reason I had to pull the battery and since then I am in above position.
Sent from my XT1032 using Tapatalk

Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app

Setting.Out said:
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.

BaghiXDA said:
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
Click to expand...
Click to collapse
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...

Setting.Out said:
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Click to expand...
Click to collapse
The problem is, even the Toolkit doesn't recognize the device no matter what. Even the keys for ODIN don't work, aren't they Home+VOL+ and Power?
EDIT1:
Kept plugged in for little longer as suggested but it heats up (it's too hot here) so I plugged out. Going to be running it off of Linux and lets see how it goes. :fingers-crossed:
EDIT2:
Tried Adam's UnBrickable method on Linux and even that couldn't find device. But that was to be expected since Adam clearly mentioned in his post that this tool isn't for those who see anything on their screen.

Whelp! Currently I can only see I:\ drive in device manager and that's all under portable devices and that's all. I see the same even in BIOS boot options, it's listed as "Google".

Guess need to close this thread now.

[Q] Bricked : Flashing sbl1

I was trying to flash BlissPop. It didn't flash. So, I decided to flash fastboot image of CM11s 44.
I issued this command :
Code:
fastboot flash modem NON-HLOS.bin
fastboot reboot-bootloader
fastboot flash sbl1 sbl1.mbn
fastboot reboot-bootloader
The flash sbl1 command gave an error.
I rebooted bootloader. The phone turned off, but it never turned on.
I don't know how could it brick my phone, because I've done it a few times without any error.
My battery was on 65% when I was doing all this. So, I don't suspect battery has died.
But, I'm charging the phone anyway. There is no lead, but the power bank shows that battery is taking charge.
When I connect the phone to PC, it shows no signs of any device connected. Device manager doesn't show any thing/any refresh.
I've tried to push the power button for about a minute for 5 times, as 1+1 site says.
I've tried vol up + power and vol down + power buttons. It doesn't boot it.
I've no access to fastboot, recovery, OS, anything.
Please, suggest me solutions.

Did you flash the firmware updates before you flashed bliss? There is a toolkit out there, linked in bliss thread, on how to unbrick. I'll see if I can't find it.
Sent from my A0001 using Tapatalk
---------- Post added at 11:49 PM ---------- Previous post was at 11:45 PM ----------
http://forum.xda-developers.com/showthread.php?p=58230647
First look at this perhaps. If not there is a toolkit out there to flash back to stock. Should be able to communicate w the phone if it can turn on at all.
Sent from my A0001 using Tapatalk

http://forum.xda-developers.com/showthread.php?p=58230647
First look at this perhaps. If not there is a toolkit out there to flash back to stock. Should be able to communicate w the phone if it can turn on at all.
Click to expand...
Click to collapse
Thanks. I looked at it.
But, as you said I can't do anything till the phone turns on even once.
BTW, I highly suspect battery drain, because I was in TWRP for long to take backup, flashing MultiROM, etc. TWRP is known to not allow charging, as reported by some people.
Can you tell me whether flashing sbl1 could have bricked it or not? It didn't fail to flash in past and it never caused problem.
I had flashed CM12 firmware update before flashing BlissPop. Could reflashing CM11s fastboot image over it cause problem. I think it should not, because fastboot image replace all things. What's your opinion?

Had the same problem. Try first leave it charging for 12 hours after that plug it in. Then get into fastboot this is not easy. Just hold vol up and power together for atv least 5 Sec.
Sent from my A0001 using XDA Free mobile app

I guess its possible. But I would do what falastine said. Charge it for some time. With a soft brick it may not show anything on the screen but could actually be on. So be patient trying to get the toolkit to find the phone. I've heard in another thread someone's phone did in fact connect but nothing was on the screen
Sent from my A0001 using Tapatalk

any progress on this? i think the exact same thing happened to me. was trying to flash back to CM11s using fastboot, but it died. now i dont get anything at all. no response to the chrager, or the computer or anything.
ive tried holding the power button, holding the vol keys with the pwr button, but no avail.
let me know if you figured it out!

Falastine said:
Had the same problem. Try first leave it charging for 12 hours after that plug it in. Then get into fastboot this is not easy. Just hold vol up and power together for atv least 5 Sec.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I left the phone in charge for 24 hours using original charger and wire.
Tried long presses for multiple times - nothing happens.
Tried vol up/ vol down combinations with power button for long nothing happens.
I am now waiting for 12 hours and then will plug it again, as some thread said.
In between I'm trying to download a tool from here : http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I hope it detects my phone.

hassan3216 said:
any progress on this? i think the exact same thing happened to me. was trying to flash back to CM11s using fastboot, but it died. now i dont get anything at all. no response to the chrager, or the computer or anything.
ive tried holding the power button, holding the vol keys with the pwr button, but no avail.
let me know if you figured it out!
Click to expand...
Click to collapse
There is no progress.
It appears that we are in same situation.
I highly suspect dead battery, instead of dead phone. Anyway, I'll post updates.
Please, share if anything works for you.

I had the same problem and had to restore the phone with this tool:
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
I had many problems with the drivers and i had tot install the qualcom drivers http://sciencespaces.com/search/Qualcomm+HS-USB+Android+DIAG+9018/
The topic said that there is an issue with the modem and you have tot flash it manually but i don't have problems so far.

michaeldepotter said:
I had the same problem and had to restore the phone with this tool:
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
I had many problems with the drivers and i had tot install the qualcom drivers http://sciencespaces.com/search/Qualcomm+HS-USB+Android+DIAG+9018/
The topic said that there is an issue with the modem and you have tot flash it manually but i don't have problems so far.
Click to expand...
Click to collapse
@michaeldepotter
Thanks for writing here.
I'm following the thread mentioned by you.
But, the problem is that I don't know how to get the phone in Qualacom mode.
I don't whether my phone is on or off. So, I've tried to connect it with PC and pressing key mentioned in the thread. It didn't work.
If you could share your experience with me, it will be kind of you.
I've windows 8.1 64 bit.

I'm at work now but in a couple of hours i can give you more info how i did it
Sent from my A0001 using XDA Free mobile app

michaeldepotter said:
I'm at work now but in a couple of hours i can give you more info how i did it
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
@michaeldepotter,
Sure, no problem.
I'll be eagerly waiting.

mahastat said:
@michaeldepotter
Thanks for writing here.
I'm following the thread mentioned by you.
But, the problem is that I don't know how to get the phone in Qualacom mode.
I don't whether my phone is on or off. So, I've tried to connect it with PC and pressing key mentioned in the thread. It didn't work.
If you could share your experience with me, it will be kind of you.
I've windows 8.1 64 bit.
Click to expand...
Click to collapse
open your device manager in your pc and use volume up and power button while connected to pc to get into qualcom mode.most probably it would be detected as android fastboot interface just click on it and update the driver to qualcom usb serial interface then use http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851 this tool to recover

wilbur2brooks said:
open your device manager in your pc and use volume up and power button while connected to pc to get into qualcom mode.most probably it would be detected as android fastboot interface just click on it and update the driver to qualcom usb serial interface then use http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851 this tool to recover
Click to expand...
Click to collapse
@wilbur2brooks
Thanks for writing.
I could understand that once my phone is detected as even unknown device, I can install drivers and try to recover through the tool you mentioned.
But, the problem is that my phone is not recognized as anything. The Device Manager shows no reaction when I connect the phone to computer.
I have disabled driver signature on my Windows 8.1 64 bit. I've Qualacom drivers installed. Rebooted computer in disabled signature mode.
I've connected my device through official cable and I've tried the key combination mentioned.
My other devices show up when connected to PC, but 1+1 doesn't.
Any other thing which I could try.
I had left my phone in charging for 24 hours, but it doesn't wake it up.
Any suggestion is appreciated.

mahastat said:
@michaeldepotter
Thanks for writing here.
I'm following the thread mentioned by you.
But, the problem is that I don't know how to get the phone in Qualacom mode.
I don't whether my phone is on or off. So, I've tried to connect it with PC and pressing key mentioned in the thread. It didn't work.
If you could share your experience with me, it will be kind of you.
I have windows 8.1 64 bit.
Click to expand...
Click to collapse
So this is how i did it.
1. install the drivers from OPO (located in the .zip file from this tool https://forums.oneplus.net/threads/t...ks-etc.237827/ )
2. Open your device manager (Start - right click on computer - properties - devices manager)
3. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
4. Download the qualcomdriver ( https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0 ). Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.
5. Now the OPO tool should recognize your device. I turn off all my network connections so the usb device can't find other drivers. (in case windows overwrite the driver).
---------- Post added at 07:29 PM ---------- Previous post was at 07:07 PM ----------
Have you tried another PC?
Sent from my A0001 using XDA Free mobile app

michaeldepotter said:
So this is how i did it.
1. install the drivers from OPO (located in the .zip file from this tool https://forums.oneplus.net/threads/t...ks-etc.237827/ )
2. Open your device manager (Start - right click on computer - properties - devices manager)
3. Press on power + vol up for like 10 sec until you see a device showing up (called QHSUSB_BULK)
4. Download the qualcomdriver ( https://www.dropbox.com/s/vgujdut93m341qm/Qualcomm 2012.rar?dl=0 ). Right click on this devices and click on "Update Driver Software" -> "Browse my computer for driver software" -> locate the Qualcomm 2012\fre\Windows7 8 or vista folder depending on your setup. Update the driver.
5. Now the OPO tool should recognize your device. I turn off all my network connections so the usb device can't find other drivers. (in case windows overwrite the driver).
---------- Post added at 07:29 PM ---------- Previous post was at 07:07 PM ----------
Have you tried another PC?Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
The hard part is that I could not get the phone detected by PC as anything.
I followed the same key combination which you mentioned. It doesn't help.
Can you tell me if battery is totally depleted, will it be possible for phone to be detected?
I've tried to charge my phone with various chargers and power banks. The battery stays cold, the charger stays cold, power bank blinks and get depleted, but phone is not vibrating even on long press.
I've tried on virtual PC, a XP machine. And on other real XP PC.
Thanks for your help.
If you have some more suggestions based on information given by me, kindly post it again.

mahastat said:
@wilbur2brooks
Thanks for writing.
I could understand that once my phone is detected as even unknown device, I can install drivers and try to recover through the tool you mentioned.
But, the problem is that my phone is not recognized as anything. The Device Manager shows no reaction when I connect the phone to computer.
I have disabled driver signature on my Windows 8.1 64 bit. I've Qualacom drivers installed. Rebooted computer in disabled signature mode.
I've connected my device through official cable and I've tried the key combination mentioned.
My other devices show up when connected to PC, but 1+1 doesn't.
Any other thing which I could try.
I had left my phone in charging for 24 hours, but it doesn't wake it up.
Any suggestion is appreciated.
Click to expand...
Click to collapse
Even if your battery is depleted it should get detected in your machine when u press volume up and power while its connected to your pc.hold it for a minute this combination should show something also keep your pc volume up to hear any port connect discconect sounds.If this doesnt happen then your hardware is dead no other option but try to give it to opo for service.

So, nothing ever comes on the screen? Does the phone vibrate if you hold the power button for 20 seconds? If so, this might be of help, if it sounds like it's bricked: http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732

wilbur2brooks said:
Even if your battery is depleted it should get detected in your machine when u press volume up and power while its connected to your pc.hold it for a minute this combination should show something also keep your pc volume up to hear any port connect discconect sounds.If this doesnt happen then your hardware is dead no other option but try to give it to opo for service.
Click to expand...
Click to collapse
I've PC volume UP, device manager in front and phone connect. Key combination brings nothing.
So, I think I'll take it to OPO Service Center now.
Thanks for helping me.
netbuzz said:
So, nothing ever comes on the screen? Does the phone vibrate if you hold the power button for 20 seconds? If so, this might be of help, if it sounds like it's bricked: http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Nothing comes on screen, no vibrations. It's bricked.
Going to OPO Service Center.
Thanks for looking after my problem.
I appreciate all who took part in this thread to help me. Thanks.
Moderators may close this thread now.

Power button won't work after using recovery tool

Have an HTC One M8 Windows [T-mobile] which was running Windows 10 from Insider program. Downloaded the latest device recovery tool and was attempting to reset to Windows 8.1. Got stuck somewhere in the process, now I can't get the boot screen to come up. Phone is fully charged and visible to pc when plugged in by USB. Even the recovery tool detects the phone, and I can view phone contents. But pushing/holding the power button does not cause the phone to vibrate and no combination of power and volume buttons has any effect.
Never heard of this issue before and can't find anything about this anywhere. Any suggestions? Perhaps I need to copy something via USB / Windows file manager to device?

mdn8rdr said:
Have an HTC One M8 Windows [T-mobile] which was running Windows 10 from Insider program. Downloaded the latest device recovery tool and was attempting to reset to Windows 8.1. Got stuck somewhere in the process, now I can't get the boot screen to come up. Phone is fully charged and visible to pc when plugged in by USB. Even the recovery tool detects the phone, and I can view phone contents. But pushing/holding the power button does not cause the phone to vibrate and no combination of power and volume buttons has any effect.
Never heard of this issue before and can't find anything about this anywhere. Any suggestions? Perhaps I need to copy something via USB / Windows file manager to device?
Click to expand...
Click to collapse
NEVER MIND! After playing around a while longer and holding the button down for nearly a minute (maybe longer), it FINALLY vibrated and reset. UGH. Oh well, problem resolved.

bricked: a confession,

1) stuck in bootloader
2) changed to B slot thru terminal . following a thread I guess
3) got into recovery (.IMG) but couldn't flash zip
4) seen "edl" and thought, what's that? So I clicked it
5) screen now blank
6) buttons have no response
7) I've owned the phone for 2 days (new)
Am I out a lot of $ or is there a hope for me

does your computer detect the phone at all when you plug it in? I know it isn't responsive, but try powering it on when you plug it in via USB and see if your PC detects anything.

Seems like you stuck at edl mode. Try holding vol down (or up) + power buttons for at least 30 seconds. Than you can try flashing stock rom from fastboot mode.

alexkalicharan said:
does your computer detect the phone at all when you plug it in? I know it isn't responsive, but try powering it on when you plug it in via USB and see if your PC detects anything.
Click to expand...
Click to collapse
Everytine I plug it in (windows8: test mode) the PC makes a sound but can't seem t find the device in the device manager.
Msmdownload tool finds nothing

Hold volume up + power button together for 10 to 30 seconds. Then release. Wait a few seconds. Now press and hold power button until it vibrates to see if it boots

alexkalicharan said:
does your computer detect the phone at all when you plug it in? I know it isn't responsive, but try powering it on when you plug it in via USB and see if your PC detects anything.
Click to expand...
Click to collapse
elmarian756 said:
Hold volume up + power button together for 10 to 30 seconds. Then release. Wait a few seconds. Now press and hold power button until it vibrates to see if it boots
Click to expand...
Click to collapse
Used a newer PC, w/win 10
Held volume up+down + power , plugged in USB to PC
Held those 3 buttons until of made a second sound
(almost 30 secs)
I can now see battery charging, woohoo
I seriously can't wait to installed mclroG
And rid myself from G00g1e
Still reading hard brick guide
I apologize to everyone reading this but sometimes you have to interact w/ someone to get the solve

elmarian756 said:
Hold volume up + power button together for 10 to 30 seconds. Then release. Wait a few seconds. Now press and hold power button until it vibrates to see if it boots
Click to expand...
Click to collapse
OnePlus 7pro bought directly from OnePlus
( i think its GM1915)
windows 10 pc
device manager lists phone as Kedacom USB Device ---> Android Bootloader Interface
i downloaded "10.0.3-GLOBAL-OnePlus7ProOxygen_21.O.23_OTA_023_all_1912032357_76b445-FASTBOOT"
ran the "flash-all" batch file
when it's done, phone reboots into "Qualcomm: CrashDump"
I can press the up+down volume buttons w/ the power button and get back to Fastboot mode
I can also get into the Chinese mode.. with that, i click ENGLISH then WIPE EVERYTHING
still no luck.... truly is an interesting BRICK

Well, you can try flashing using "TOOL ALL IN ONE".

Did you try the MSMtool?
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691/amp/

I also bricked mine a couple days ago , restored it by using MNSTOOL , you can find threads or youtube videos how to use it , it will finish it in around 5 minutes and also it will lock the bootloader.

Zed Kay said:
Did you try the MSMtool?
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691/amp/
Click to expand...
Click to collapse
so many times i've tried the msmdownload tool
my device is not recognized... so i figure it's the driver
i followed the instructions.. it says with phone off ,hold the vol up+down for 5 secs then plug in to usb on pc
the drivers should auto download into the pc
it did.. i see in Device Manager under PORTS the qualcomm driver appear when phone is plugged in
but phone is in Qualcomm CrashDump mode
when i reboot to FASTBOOT MODE (by holding volume up+down and power button) the Device Manager
recognizes the phone as Kedacom USB Device/Android Bootloader Interface
(not Qualcomm)
and of course MSMDownload tool does not recognize phone... i'll keep trying

csmooth2001 said:
so many times i've tried the msmdownload tool
my device is not recognized... so i figure it's the driver
i followed the instructions.. it says with phone off ,hold the vol up+down for 5 secs then plug in to usb on pc
the drivers should auto download into the pc
it did.. i see in Device Manager under PORTS the qualcomm driver appear when phone is plugged in
but phone is in Qualcomm CrashDump mode
when i reboot to FASTBOOT MODE (by holding volume up+down and power button) the Device Manager
recognizes the phone as Kedacom USB Device/Android Bootloader Interface
(not Qualcomm)
and of course MSMDownload tool does not recognize phone... i'll keep trying
Click to expand...
Click to collapse
I will tell you the full guide.
1. Extract msm(whatever).zip
2. Turn off your phone
3. Open msm.exe (green icon) as admin
5. Hold vol+ and vol- for 30 (no less)
5. Connect usb while holding both volume buttons and release after connecting the usb
6. As soon as you connect the usb hit start.

msmtool does not recognize
Zed Kay said:
Did you try the MSMtool?
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691/amp/
Click to expand...
Click to collapse
i figure it's the driver.. windows keeps installing a specific driver for the phone.
but i think it's the wrong driver
(doesnt say QUALCOMM in the device manager)
so now i have to force install the driver
by right clicking on the phone in the device manager and working thru the menu to get to 'HAVE DISK'
so i have to be in windows as an admin
https://www.technipages.com/windows-administrator-account-login-screen
then after downloading the Qualcomm driver in a .cab file as admin i can right click and choose install .cab file
***AAAAAND nope can't right click to have "install" appear in the menu
FUDGE FUDGE FUDGE
all because windows says the driver is already installed... and has a kaed???? driver instead of the Qualcomm
can my life with this phone be any more difficult??

csmooth2001 said:
i figure it's the driver.. windows keeps installing a specific driver for the phone.
but i think it's the wrong driver
(doesnt say QUALCOMM in the device manager)
so now i have to force install the driver
by right clicking on the phone in the device manager and working thru the menu to get to 'HAVE DISK'
so i have to be in windows as an admin
https://www.technipages.com/windows-administrator-account-login-screen
then after downloading the Qualcomm driver in a .cab file as admin i can right click and choose install .cab file
***AAAAAND nope can't right click to have "install" appear in the menu
FUDGE FUDGE FUDGE
Click to expand...
Click to collapse
You can just use the drivers which are provided in the msm archive.

tried manually install a .cab with a terminal command as admin
but i get error "An error occurred trying to open - c:\usb.cab Error: 0x80070003
maybe i have to rename it KB(+number).cab in order for it to work (instead of usb.cab)
NOPE THAT DIDNT WORK

Zed Kay said:
Did you try the MSMtool?
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691/amp/
Click to expand...
Click to collapse
Zed Kay said:
You can just use the drivers which are provided in the msm archive.
Click to expand...
Click to collapse
I'll try that
NOPE!!!
pop window states
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."

csmooth2001 said:
I'll try that
NOPE!!!
pop window states
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Click to expand...
Click to collapse
What do you see in device manager while the phone is connected?
---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------
csmooth2001 said:
I'll try that
NOPE!!!
pop window states
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Click to expand...
Click to collapse
L2 drivers>qcser64>view signature>view certificate>install certificate>next>next>finish then reboot

my phone is GM1915
which is tmobile (even though i bought it directly from OnePlus)
so i will search for downloads for that
**on a mission**

Msmtool is what you need to use. You will recover it for sure

csmooth2001 said:
my phone is GM1915
which is tmobile (even though i bought it directly from OnePlus)
so i will search for downloads for that
**on a mission**
Click to expand...
Click to collapse
currently trying --> https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947