Develop Bugs

[Q] Official software upgrade - probably bricked my galaxy grand :'(

Hi all
I got a notification of the latest software upgrade available for my device. I downloaded it and installed it. The installation process was shown to have reached 100% and then the phone screen went black and then did not turn back up. When I connect the phone to charger, I do not see any battery charging icon
I had my phone connected to the power outlet while I was upgrading? Is my phone bricked? Any way I can resolve this issue? My phone is out of warranty.
I have never ever rooted the phone. Not sure why would this happen with an official software upgrade.
Any help will be immensely appreciated

Are u able to enter recovery mode!

nick2408 said:
Hi all
I got a notification of the latest software upgrade available for my device. I downloaded it and installed it. The installation process was shown to have reached 100% and then the phone screen went black and then did not turn back up. When I connect the phone to charger, I do not see any battery charging icon
I had my phone connected to the power outlet while I was upgrading? Is my phone bricked? Any way I can resolve this issue? My phone is out of warranty.
I have never ever rooted the phone. Not sure why would this happen with an official software upgrade.
Any help will be immensely appreciated
Click to expand...
Click to collapse
Bro, hava read here....hopefully this will fix for u, FULL UNBRICKING TUT
http://forum.xda-developers.com/showthread.php?t=2725706

bodmar said:
Bro, hava read here....hopefully this will fix for u, FULL UNBRICKING TUT
http://forum.xda-developers.com/showthread.php?t=2725706
Click to expand...
Click to collapse
I was unable to go to recovery or download mode..
I took my phone to samsung service center and they told my motherboard has problems and it needs to be replaced.. huh

nick2408 said:
I was unable to go to recovery or download mode..
I took my phone to samsung service center and they told my motherboard has problems and it needs to be replaced.. huh
Click to expand...
Click to collapse
So its under warranty? Right? Or do u have to pay for the mess samsung created

doctor_droid said:
So its under warranty? Right? Or do u have to pay for the mess samsung created
Click to expand...
Click to collapse
I had to pay for it. It was out of warranty

nick2408 said:
I had to pay for it. It was out of warranty
Click to expand...
Click to collapse
Thats a really bad consumer behavior from an intl oem...

doctor_droid said:
Thats a really bad consumer behavior from an intl oem...
Click to expand...
Click to collapse
Why do you think so. I am quite sure my phone was hard bricked

nick2408 said:
Why do you think so. I am quite sure my phone was hard bricked
Click to expand...
Click to collapse
I meant behavior towards consumer... not ur fault mate...i knw how pathetic it can be to give away hard earned money when its nt our fault

Ridiculous move from Samsung IMO.

nick2408 said:
Hi all
I got a notification of the latest software upgrade available for my device. I downloaded it and installed it. The installation process was shown to have reached 100% and then the phone screen went black and then did not turn back up. When I connect the phone to charger, I do not see any battery charging icon
I had my phone connected to the power outlet while I was upgrading? Is my phone bricked? Any way I can resolve this issue? My phone is out of warranty.
I have never ever rooted the phone. Not sure why would this happen with an official software upgrade.
Any help will be immensely appreciated
Click to expand...
Click to collapse
Dear friend, Did you repair your phone my case is similar to yours.

agsao said:
Dear friend, Did you repair your phone my case is similar to yours.
Click to expand...
Click to collapse
Dear friend, just download your latest firmware at sammobile and flash it thru odin. Its the easiest and safest way to upgrade in my experience.

kaiserlourdes said:
Dear friend, just download your latest firmware at sammobile and flash it thru odin. Its the easiest and safest way to upgrade in my experience.
Click to expand...
Click to collapse
I could not open my phone and PC recognized it as unknown device.

agsao said:
I could not open my phone and PC recognized it as unknown device.
Click to expand...
Click to collapse
Search the forum on how to root and u can find there the Samsung USB drivers link. Download that

kaiserlourdes said:
Search the forum on how to root and u can find there the Samsung USB drivers link. Download that
Click to expand...
Click to collapse
Previously the PC was able to detect the phone (that mean the driver is installed successfully) but after this problem I can't turn on my phone ,and the screen is always blank.

agsao said:
Previously the PC was able to detect the phone (that mean the driver is installed successfully) but after this problem I can't turn on my phone ,and the screen is always blank.
Click to expand...
Click to collapse
can u explain how did you end up with blank screen when plug into PC?
did u go to download mode?
because mine was perfectly fine when plug into the PC.

kaiserlourdes said:
can u explain how did you end up with blank screen when plug into PC?
did u go to download mode?
because mine was perfectly fine when plug into the PC.
Click to expand...
Click to collapse
Dear friend,
My phone was stuck on logo screen.
I tried to full flash it using Odin I chooses all files except PDA files.
The phone accepted the flashing successfully
Phone restated and showing the android robot for updating
During this screen became black.
The result:
No response from phone it cann' be charged nor be turned on
I can't open the phone in any mode even download mode
When I plug my phone to the PC it's recognized as unknown device not as previous.
Thanks

agsao said:
Dear friend,
My phone was stuck on logo screen.
I tried to full flash it using Odin I chooses all files except PDA files.
The phone accepted the flashing successfully
Phone restated and showing the android robot for updating
During this screen became black.
The result:
No response from phone it cann' be charged nor be turned on
I can't open the phone in any mode even download mode
When I plug my phone to the PC it's recognized as unknown device not as previous.
Thanks
Click to expand...
Click to collapse
After successful flash the phone will reboot automatically and will stay on bootloop, while rebooting press and hols home+vol.up+power button. Then factory reset, wipe dalvik, wipe cache. Then reboot system..
Why not PDA? When i flashed stock rom i choose PDA and choose the file.
Auto reboot and f.reset time are the only checked boxes

kaiserlourdes said:
After successful flash the phone will reboot automatically and will stay on bootloop, while rebooting press and hols home+vol.up+power button. Then factory reset, wipe dalvik, wipe cache. Then reboot system..
Why not PDA? When i flashed stock rom i choose PDA and choose the file.
Auto reboot and f.reset time are the only checked boxes
Click to expand...
Click to collapse
Now I cannot flash it any more because the phone can't start in any mode neither download download mode nor recovery mode. ( may be hard bricked)

agsao said:
Now I cannot flash it any more because the phone can't start in any mode neither download download mode nor recovery mode. ( may be hard bricked)
Click to expand...
Click to collapse
one cannot hard bricked thru OTA update of official samsung. because i once update thru OTA and it updated successfully.
maybe it hard bricked when you flashed thru odin, maybe a wrong step.
i cant help you anymore brother, you can search this forum on how to unbricked device, u can try it. goodluck!

In some deep ****

I rooted my friends htc desire 816g dual sim and got him cwm.
i flashed it with a programm on the pc (can't quite remember the name) after that it said ''boot in recovery mode?''
i pressed yes and it went into a bootloop,i was like ok fixable just go into fastboot and flash new rom right?
no it cannot go into bootloop or recovery and when it is connected to pc during this whole bootloop it shows me the cell phone with some drivers i installed with a yellow exclamation mark under it,also it doesn't stay connected for more than 3-5 seconds

thongdaddy said:
I rooted my friends htc desire 816g dual sim and got him cwm.
i flashed it with a programm on the pc (can't quite remember the name) after that it said ''boot in recovery mode?''
i pressed yes and it went into a bootloop,i was like ok fixable just go into fastboot and flash new rom right?
no it cannot go into bootloop or recovery and when it is connected to pc during this whole bootloop it shows me the cell phone with some drivers i installed with a yellow exclamation mark under it,also it doesn't stay connected for more than 3-5 seconds
Click to expand...
Click to collapse
Yeah the g is the Mediatek processor and needs to be flashed with flashtools and the phone off I believe. Not many custom roms for it either. So you think you flashed the wrong rom and did you use flashtools ? There's also a quad core version and octa core version that can't use each other's custom roms I believe. One is MT682 and the other is MT692 for octa core I believe.

thoctor said:
Yeah the g is the Mediatek processor and needs to be flashed with flashtools and the phone off I believe. Not many custom roms for it either. So you think you flashed the wrong rom and did you use flashtools ? There's also a quad core version and octa core version that can't use each other's custom roms I believe. One is MT682 and the other is MT692 for octa core I believe.
Click to expand...
Click to collapse
I didn't flash a rom I flashed cwm and It wasn't off indeed but I need help not to find the cause because I cannot get into any menus or get my pc to recognise it due to the minimum time it stays connected

thongdaddy said:
I didn't flash a rom I flashed cwm and It wasn't off indeed but I need help not to find the cause because I cannot get into any menus or get my pc to recognise it due to the minimum time it stays connected
Click to expand...
Click to collapse
Oh , yeah. My bad. I was tired last night and helping a few different people here and in other sites so the recovery flash slipped by me. Your going to have to get the phone powered down (either by you or by it draining down.)and use flashtools again I believe. Assuming that's what you used initially. XDA member Nukaru has helped people with Mediatek chipsets more than I have ( I have the a5_chl snapdragon) and I would recommend getting her help. I've never used flashtools with the Mediatek devices just ADB/fastboot with Qualcomm.

thoctor said:
Oh , yeah. My bad. I was tired last night and helping a few different people here and in other sites so the recovery flash slipped by me. Your going to have to get the phone powered down (either by you or by it draining down.)and use flashtools again I believe. Assuming that's what you used initially. XDA member Nukaru has helped people with Mediatek chipsets more than I have ( I have the a5_chl snapdragon) and I would recommend getting her help. I've never used flashtools with the Mediatek devices just ADB/fastboot with Qualcomm.
Click to expand...
Click to collapse
My computer cannot recognise it though because once I connect in it disconnects within seconds if I could do that I would have tried and the only reason I have hopes is because it turns on but not in android or any bootloader also my phone is discoverable by my pc only when it is in the state of turning on as soon as there is light on the screen it disconnects

thongdaddy said:
My computer cannot recognise it though because once I connect in it disconnects within seconds if I could do that I would have tried and the only reason I have hopes is because it turns on but not in android or any bootloader also my phone is discoverable by my pc only when it is in the state of turning on as soon as there is light on the screen it disconnects
Click to expand...
Click to collapse
I get all that . The phone won't enter recovery or bootloader or OS and keeps rebooting. I believe it's going to have to completely power down either by you or the phone itself then use flashtools. I provided a link to a flashtools forum for the HTC Mediatek devices. Yours is included. Also contact Nukaru as she has direct experience with the Mediatek chipset. The phone is going to have to run down basically so you don't get any reboots but like I said the Mediatek isn't my area of expertise. Follow my advice and you'll get it figured out. Good luck.
http://forum.xda-developers.com/android/general/htc-mtk-cpu-flash-files-flashtool-t3114271

thoctor said:
I get all that . The phone won't enter recovery or bootloader or OS and keeps rebooting. I believe it's going to have to completely power down either by you or the phone itself then use flashtools. I provided a link to a flashtools forum for the HTC Mediatek devices. Yours is included. Also contact Nukaru as she has direct experience with the Mediatek chipset. The phone is going to have to run down basically so you don't get any reboots but like I said the Mediatek isn't my area of expertise. Follow my advice and you'll get it figured out. Good luck.
http://forum.xda-developers.com/android/general/htc-mtk-cpu-flash-files-flashtool-t3114271
Click to expand...
Click to collapse
Sorry for replying again but just to make it clear I make the phone battery die so it doesn't reboot and I use the flash tools to flash a stock rom?

thongdaddy said:
Sorry for replying again but just to make it clear I make the phone battery die so it doesn't reboot and I use the flash tools to flash a stock rom?
Click to expand...
Click to collapse
Don't be sorry I'm happy to help. That's my understanding but bear in mind my knowledge with the Mediatek is really limited. I know you need flashtools and I'm pretty sure the device needs to be powered off. After that I'm kind of out of my area of expertise. Been told by Nukaru that the Mediatek is actually easier to flash/work with so that's good. Send her a PM and when she's not busy I'm sure she will try to help you here.

thoctor said:
Don't be sorry I'm happy to help. That's my understanding but bear in mind my knowledge with the Mediatek is really limited. I know you need flashtools and I'm pretty sure the device needs to be powered off. After that I'm kind of out of my area of expertise. Been told by Nukaru that the Mediatek is actually easier to flash/work with so that's good. Send her a PM and when she's not busy I'm sure she will try to help you here.
Click to expand...
Click to collapse
OK thank you for all your help

thongdaddy said:
Sorry for replying again but just to make it clear I make the phone battery die so it doesn't reboot and I use the flash tools to flash a stock rom?
Click to expand...
Click to collapse
Just popped in, I think I can help you.
SP Flashtool can detect the device even if it is on bootloop. On SP Flashtool just tick all items except preloader then click on download and connect the phone to the PC. If it still does not get recognized try holding the power button while you are connecting it to the PC to try and force it into the switched off state

The best way to flash RUU on a mediatek device is ALWAYS to remove the battery. Not removing the battery can brick your device!
To help I'll need more information about your device.
1. What RUU did you flash? European or Indian?
2. When and where was this phone bought, which region?

nukaru said:
The best way to flash RUU on a mediatek device is ALWAYS to remove the battery. Not removing the battery can brick your device!
To help I'll need more information about your device.
1. What RUU did you flash? European or Indian?
2. When and where was this phone bought, which region?
Click to expand...
Click to collapse
I flashed a clockwork mod it was European if that is ruu but I didn't flash a rom
the phone was bought about 1 year ago in Greece

Gibz97 said:
Just popped in, I think I can help you.
SP Flashtool can detect the device even if it is on bootloop. On SP Flashtool just tick all items except preloader then click on download and connect the phone to the PC. If it still does not get recognized try holding the power button while you are connecting it to the PC to try and force it into the switched off state
Click to expand...
Click to collapse
OK I will try that thanks

This (D816h) is the rom you'll need. Instructions are in the file description. If you're having trouble signing in, please contact me and I'll upload the file once I'm done with work.
And this is how to remove the battery.

nukaru said:
This (D816h) is the rom you'll need. Instructions are in the file description. If you're having trouble signing in, please contact me and I'll upload the file once I'm done with work.
And this is how to remove the battery.
Click to expand...
Click to collapse
it is stuck now because as soon as it connects it stays connected and it disconnects after a few seconds i also got an error about the usb port but i uninstalled the i guess false drivers i had installed by myself any other ideas?

Have you tried a different driver for your USB Port? Or connecting the device to another USB Port?
Flashtools won't disconnect, if the battery is removed, that's why it's always the safest bet to remove the battery.

nukaru said:
Have you tried a different driver for your USB Port? Or connecting the device to another USB Port?
Flashtools won't disconnect, if the battery is removed, that's why it's always the safest bet to remove the battery.
Click to expand...
Click to collapse
It still doesn't flash it it stays there at 0b/s maybe different settings?the options not quite like you told me it is a different version I guess

thongdaddy said:
It still doesn't flash it it stays there at 0b/s maybe different settings?the options not quite like you told me it is a different version I guess
Click to expand...
Click to collapse
What is your device model?
It is usually shown at the back bottom of the phone. It is usually something like 0PGZ100, 0PJ120... etc

thongdaddy said:
It still doesn't flash it it stays there at 0b/s maybe different settings?the options not quite like you told me it is a different version I guess
Click to expand...
Click to collapse
What error message do you get? Is there an error message?
Some versions of flashtool are problematic with Desire 816, which version did you install?

nukaru said:
What error message do you get? Is there an error message?
Some versions of flashtool are problematic with Desire 816, which version did you install?
Click to expand...
Click to collapse
It is 5. Something should I search some else version?

Unbrick bricked by writing boot.img to wrong mmcblk

Hello community members,
TL;DR no adb, no fastboot, no flashmode, no QDloader (or similar) ... how to unbrick it?
I was trying to force Android to allow lower lcd backlight brightness levels by patching framework-res.apk and I had the edited zip file ready to flash. Then I realized that my Android 7 Ressurection remix ROM (thread) flashed Cyanogenmod recovery, which I don't like. So I decided to reflash TWRP 3.0.2 (link) ( edit: using "fastboot flash boot twrp.img", which was almost fatal mistake) and it has gone almost well. The phone started to boot into recovery mode everytime (and took a long time doing so). So I googled a bit and found this thread which lead me to this thread. I was looking forward to seeing my display brightness at lower than default values, so I probably skipped some security checks and texts with red color, so I flashed the zip with the boot.img replaced. After flashing I chose reboot and nothing happened since.
The problem is I flashed something that was not for my device (extracted boot.img to wrong mmcblk). The command that bricked my phone is (from META-INF/com/google/android/updater-script):
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p6");
After that it doesn't boot, doesn't light up LED (even when charging), doesn't get detected by PC in any state.
So I have no adb, no fastboot and no flashmode and not even a QDloader or similar mode.
Is there a way to unbrick it?
EDIT: How to unbrick it using JTAG interface? If I find somebody that has the required equipment, what data do I need to give them?

Hey there! Did you manage to solve the issue, because I just got into the same situation after the zip didn't save the corrected partitions but the initial ones... So i ended up without any signs of life in my phone

valkata752 said:
Hey there! Did you manage to solve the issue, because I just got into the same situation after the zip didn't save the corrected partitions but the initial ones... So i ended up without any signs of life in my phone
Click to expand...
Click to collapse
Nope, I found no solution ... even some kind of Qualcomm flashing mode via COM (serial port over USB) does not show up nowhere. I gave up and bought a used S5 mini, which is full of features I appreciate.
I'm gonna keep this Xperia M for some time if some solution comes up.

hi , can you boot into recovery ? ..if yes, i can maybe help

olibub said:
hi , can you boot into recovery ? ..if yes, i can maybe help
Click to expand...
Click to collapse
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.

mik13ST said:
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.
Click to expand...
Click to collapse
:/ this will be a problem... try look here http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
and find this article "Unbrick any android device with Once Click Unbrick tool"

mik13ST said:
No, as I said, the phone does not react on anything. I would be able to put it back together if this was possible.
Click to expand...
Click to collapse
can you still access fastboot mode? anyway you need to know first what is exactly partition that you overwrite with boot.img :/
. That was really critical -_-

olibub said:
:/ this will be a problem... try look here http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
and find this article "Unbrick any android device with Once Click Unbrick tool"
Click to expand...
Click to collapse
Nice looking tutorial, but I cannot find any download link for that One Click Unbrick Tool in that article. I doubt it would work, they are not explaining what it does.
Nicklas Van Dam said:
can you still access fastboot mode? anyway you need to know first what is exactly partition that you overwrite with boot.img :/
. That was really critical -_-
Click to expand...
Click to collapse
No, as I said. The partition that got overwritten was /dev/block/mmcblk0p6. It was overwritten by boot.img from LG OPTIMUS 3D that I link to in the main post.

here you can download unbrick tool https://forum.xda-developers.com/showthread.php?t=1153310

olibub said:
here you can download unbrick tool https://forum.xda-developers.com/showthread.php?t=1153310
Click to expand...
Click to collapse
I don't think this has any chance that it will work.
"This Software:
Will work on all Samsung devices which use Odin3"

Do you know how to use Flashtool?
If so, did you already attempt flashing a ftf via Flashmode (Hold VolDown)?

PhoenixTwoFive said:
Do you know how to use Flashtool?
If so, did you already attempt flashing a ftf via Flashmode (Hold VolDown)?
Click to expand...
Click to collapse
I know what Flashtool is. I know what ftf is. I used it once I think.
But the phone does not boot into flashmode as I mention in the main post.

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

Question Soft Bricked T-Mobile OnePlus 9 Pro

So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?

I did that to an HTC U11 once - Never got it recovered, had to toss it...
Never dared relock a bootloader since...

I had the same thing happen to me.
The only thing that worked for me is to boot recovery and wipe system. Good luck

Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
i have the same problem let me know if you figure out a way around this !

For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.

I had this issue as well, but you better not have messed with the sensitive partitions without a backup, otherwise there's no way to repair it.

razercortex said:
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
Click to expand...
Click to collapse
i cannot figure out how to run the msm tool properly it always throws an error message

KidSudo6969 said:
i cannot figure out how to run the msm tool properly it always throws an error message
Click to expand...
Click to collapse
what is the error message? Maybe you dont have the correct one.

Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
Here is the msm tool

This was fixed via MSM. But I had another issue come up where MSM doesn't work.

Jhoopes517 said:
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Click to expand...
Click to collapse
What do you mean doesnt work? What did it do?

its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.

Aleena1217 said:
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Click to expand...
Click to collapse
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).

ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that

Aleena1217 said:
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Click to expand...
Click to collapse
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.

ekin_strops said:
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
Click to expand...
Click to collapse
thank you so much. msm is downloading now. while I have you, do you have a link for the 9 pro conversion files? id really like to get that xpan update finally...

ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.

Aleena1217 said:
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Click to expand...
Click to collapse
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?

ekin_strops said:
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
Click to expand...
Click to collapse
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.

Aleena1217 said:
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Click to expand...
Click to collapse
Are you getting the mismatch on the global/eu MSM or are you trying to flash back to stock T-Mobile? You're getting a mismatch because you're most likely using the wrong version of a firmware (msm).