Develop Bugs

[Q] [Cry] Galaxy Nexus bricked. (Dead fastboot, dead 3e recovery, only safemode

Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium

Reserved for updates

Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/

iowabowtech said:
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Click to expand...
Click to collapse
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250

bk201doesntexist said:
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
Click to expand...
Click to collapse
Yup, tried it but its still the same. Fastboot still dosent work and relashing packaged factory images in odin dosent fix the fastboot
Sent from my GT-I9100 using xda premium

Saw a Jtag service nearby and thinking of sending it in. Its roughly after conversion from RM(Malaysian Ringgit) around USD$90. Possible recovery from the issue?
Sent from my GT-I9100 using xda premium

does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.

override182 said:
Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.

chadouming said:
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
Click to expand...
Click to collapse
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
killersloth said:
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
Click to expand...
Click to collapse
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium

override182 said:
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it. Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options. But that would be strange that adb work on safe mode. There is probably a way to that with adb but you will have to google it. Tell your friend to follow instruction next time. And ffs, do not use odin ! (Little idea too, try to get in fastboot not connected on PC and wait a few minutes then see if you can move with the volume button, then try to connect it on pc)

chadouming said:
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it.
Click to expand...
Click to collapse
Yes i have already did that few times. Few times of ICS factory image and few with JB. All are repacked version provided by chainfire. Its the full package not the software only with stripped bootloader n recovery. Its still the same
Sent from my GT-I9100 using xda premium

http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work

killersloth said:
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
Click to expand...
Click to collapse
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium

override182 said:
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?

killersloth said:
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
Click to expand...
Click to collapse
Yes i had, still boots to safe mode and the fastboot is still dead. Yes ive tried adb reboot bootloader but its dead in fastboot, again.
Sent from my GT-I9100 using xda premium

only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.

Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639

killersloth said:
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Click to expand...
Click to collapse
Tried yesterday, nothing happened
Sparx639 said:
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
Click to expand...
Click to collapse
First tried pda only with auto reboot, no gooding. The i tried with booloader, no good. Then bootloader only, still no good. Then i tested all including pit file, still no good.
Update, sent in for Jtagging few min ago. The phone is not with me now and ill get it back in 3days working or not. I shall report in back after 3 days. Thanks to all by giving suggestion and ideas. See u guys again in 3 days
Sent from my GT-I9100 using xda premium

chadouming said:
Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options.
Click to expand...
Click to collapse
adb does not work in download mode/bootloader. adb only works when adbd (adb service) is started, and that happens in android boot process. it means android debug bridge.
sent from my i9250

Sorry for the long delay to anyone waiting for the answer/status.
Jtag cant fix it. Returned the device to a friend. Prolly a mobo replacement is the solution but its damn pricy here in Malaysia. It costs 80% of the price to get a new Gnex.
Hell yeah and thx to everyone supporting this.
Sent from my GT-I9100 using xda premium

Flashed wrong boot.img and recovery.img!

Hi, i need help. My phone is on lollipop. I tried flashing a bumped recovery.img and i stupidly didn't realise that bumping was patched. But the phone still booted fine, I just couldn't boot into recovery. Today, I tried booting a modified boot.img and now it won't boot AT ALL! Every time I try and press the power button, it will come up with a message that says something like "security error - cause 2 boot certification verify" then the screen will just go black and the LED will flash red and blue constantly unless I pull the battery out. I am so worried!!!! If you want to know, I flashed the recovery and boot images with flashify. I am very very worried. Is there any way I can fix my phone? Thanks.

GSYNCER said:
Hi, i need help. My phone is on lollipop. I tried flashing a bumped recovery.img and i stupidly didn't realise that bumping was patched. But the phone still booted fine, I just couldn't boot into recovery. Today, I tried booting a modified boot.img and now it won't boot AT ALL! Every time I try and press the power button, it will come up with a message that says something like "security error - cause 2 boot certification verify" then the screen will just go black and the LED will flash red and blue constantly unless I pull the battery out. I am so worried!!!! If you want to know, I flashed the recovery and boot images with flashify. I am very very worried. Is there any way I can fix my phone? Thanks.
Click to expand...
Click to collapse
@GSYNCER, can you get to the download mode? If yes, you might as well flash your firmware using the flash tool. I hope I didn't misunderstand you.

ravi.vydianathan said:
@GSYNCER, can you get to the download mode? If yes, you might as well flash your firmware using the flash tool. I hope I didn't misunderstand you.
Click to expand...
Click to collapse
I am not at home right now, so I can't check. But what I did do was connect a USB cable directly connected to the mains plug (no pc) and tried the download method and it didn't work. Should I try with a proper PC to see if it works? As I said, I cannot enter recovery mode or boot into the system. But I CAN do a hard factory reset, but unfortunately that did nothing I am getting very worried and I do not know if download mode works or not. I will try the download mode method when I get home.

@GSYNCER, do let me know if the Download Mode worked for you or not. I am not sure if plugging in to the mains will have the same effect as connecting to a PC. Hope to hear from you.

ravi.vydianathan said:
@GSYNCER, do let me know if the Download Mode worked for you or not. I am not sure if plugging in to the mains will have the same effect as connecting to a PC. Hope to hear from you.
Click to expand...
Click to collapse
I managed to do it!! I managed to get into download mode when connected to a PC. Just make sure that the cable is USB 2.0 and it will boot into download mode and follow the steps in this video: https: //youtu. be/1WgXuxDbmbc (remove the spaces in the URL)
If you follow the steps in that video, your phone will be working again. I am even sending this message from my LG G3 itself! Good luck restoring. Thank you.

GSYNCER said:
I managed to do it!! I managed to get into download mode when connected to a PC. Just make sure that the cable is USB 2.0 and it will boot into download mode and follow the steps in this video: https: //youtu. be/1WgXuxDbmbc (remove the spaces in the URL)
If you follow the steps in that video, your phone will be working again. I am even sending this message from my LG G3 itself! Good luck restoring. Thank you.
Click to expand...
Click to collapse
@GSYNCER, Happy to hear that it worked for you ?

hello i also have the same problem
I have the same problem as him but mine is not going to download mode and neither is the phone displaying anything.

linzvidzi said:
I have the same problem as him but mine is not going to download mode and neither is the phone displaying anything.
Click to expand...
Click to collapse
Follow this guide
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359

Bricked my phone

Hello guys, I'm a newbie on pretty much anything dev related when it comes to phones. And I guess this time I screwed things up. My phone was rooted and it was working perfectly, but when I tried to enter SuperUser app it said I needed to root manually again, probably because it updated to android 5.0. So I tried to one click root and it didn't work. So as dumb as I am I started messing around with things and I ended up with my phone completely broke. I can't even get into recovery mode or anything. My phone is just stuck on logo screen and then it dies. I tried like a thousand times to enter recovery by pressing power and volume up, but that's just doesn't work anymore. And fastboot can't reconize my phone anymore, so I can't even try to boot a recovery or something. I guess I fuc*** everything now. But I don't know. Is there still hope guys?

zedopovo said:
Hello guys, I'm a newbie on pretty much anything dev related when it comes to phones. And I guess this time I screwed things up. My phone was rooted and it was working perfectly, but when I tried to enter SuperUser app it said I needed to root manually again, probably because it updated to android 5.0. So I tried to one click root and it didn't work. So as dumb as I am I started messing around with things and I ended up with my phone completely broke. I can't even get into recovery mode or anything. My phone is just stuck on logo screen and then it dies. I tried like a thousand times to enter recovery by pressing power and volume up, but that's just doesn't work anymore. And fastboot can't reconize my phone anymore, so I can't even try to boot a recovery or something. I guess I fuc*** everything now. But I don't know. Is there still hope guys?
Click to expand...
Click to collapse
if you can go to fast boot means your pc must recognize it. install asus usb driver and intel android usb driver. then flash firmware with AFT or with commands

sukhwant717 said:
if you can go to fast boot means your pc must recognize it. install asus usb driver and intel android usb driver. then flash firmware with AFT or with commands
Click to expand...
Click to collapse
He said fastboot doesn't recognize his phone anymore
Sent from my ASUS_Z00A using Tapatalk

zedopovo said:
Hello guys, I'm a newbie on pretty much anything dev related when it comes to phones. And I guess this time I screwed things up. My phone was rooted and it was working perfectly, but when I tried to enter SuperUser app it said I needed to root manually again, probably because it updated to android 5.0. So I tried to one click root and it didn't work. So as dumb as I am I started messing around with things and I ended up with my phone completely broke. I can't even get into recovery mode or anything. My phone is just stuck on logo screen and then it dies. I tried like a thousand times to enter recovery by pressing power and volume up, but that's just doesn't work anymore. And fastboot can't reconize my phone anymore, so I can't even try to boot a recovery or something. I guess I fuc*** everything now. But I don't know. Is there still hope guys?
Click to expand...
Click to collapse
There is still hope, this tutorial worked for me so I'll give this link to you:
https://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
just follow the instructions and you're good to go, if you need help, I'll try to reply as soon as possible and there are many more experiencedd members here to help you, Hopefully this will work, Goodluck! :good:

Stuck in recovery

Hi,
My phone got a message about a virus which I assumed was a devious add, it wouldn't go away so I rebooted. It has gone into Mi-Recovery 3.0 and I cant get out. I've tried to connect to PC suite but it won't connect to my laptop
without debugging, which I can't do. I've wiped data but no good. Any ideas?

Flash full rom img via EDL mode and MiFlash software. Check out the official forums how to do it all.
For me the command fastboot oem edl works to get into edl mode.

pr0x2 said:
Flash full rom img via EDL mode and MiFlash software. Check out the official forums how to do it all.
For me the command fastboot oem edl works to get into edl mode.
Click to expand...
Click to collapse
Thank you for answering. I have downloaded a full rom and the MiFlash software. I have made an EDL cable but nothing happens. From what I read it says turn the phone off and connect the modified cable and it will enter EDL mode however it just stays on the Mi-Recovery 3.0 page. I've tried the command line you suggest but that can't find the phone. I've also tried the test point method and still can't get into edl mode. What am I doing wrong?
Sorry, I'm new to this so don't really know what I'm doing. Would you be able to give me some easy to follow advise or some links please.

Multi57 said:
Thank you for answering. I have downloaded a full rom and the MiFlash software. I have made an EDL cable but nothing happens. From what I read it says turn the phone off and connect the modified cable and it will enter EDL mode however it just stays on the Mi-Recovery 3.0 page. I've tried the command line you suggest but that can't find the phone. I've also tried the test point method and still can't get into edl mode. What am I doing wrong?
Sorry, I'm new to this so don't really know what I'm doing. Would you be able to give me some easy to follow advise or some links please.
Click to expand...
Click to collapse
You need your normal USB C cable. When you are in fastboot you need to type "fastboot oem edl" your screen will go to black and you are now in EDL mode. Now flash full img via miflash software.

pr0x2 said:
You need your normal USB C cable. When you are in fastboot you need to type "fastboot oem edl" your screen will go to black and you are now in EDL mode. Now flash full img via miflash software.
Click to expand...
Click to collapse
I cant get to fastboot as I'm stuck in Recovery. My only choices are Reboot to System and Back to Main Menu. When I'm in Main Menu my choices are Reboot, Wipe Data or Connect with MIAssistant.

Multi57 said:
I cant get to fastboot as I'm stuck in Recovery. My only choices are Reboot to System and Back to Main Menu. When I'm in Main Menu my choices are Reboot, Wipe Data or Connect with MIAssistant.
Click to expand...
Click to collapse
When you turn off the phone and press vol down + power what does that do?

It shows the Mi start screen then boots strait into recovery Main Menu. I can't turn the phone off without it rebooting.

Does anyone know how I can get around this? I've run out of things to try.

Did you try reflashing the recovery maybe that fixes it?
Sent from my MI 5s using Tapatalk

Can you explain how I do that? I can't connect to my computer so not sure what you mean. I'm new at this so unsure of the options.

Multi57 said:
Can you explain how I do that? I can't connect to my computer so not sure what you mean. I'm new at this so unsure of the options.
Click to expand...
Click to collapse
Oh hmm never mind. Ignore what I said above. I thought you had TWRP recovery but you've got the stock one.
Sent from my MI 5s using Tapatalk

templeka said:
Oh hmm never mind. Ignore what I said above. I thought you had TWRP recovery but you've got the stock one.
Sent from my MI 5s using Tapatalk
Click to expand...
Click to collapse
Is there no way of getting out of stock recovery?

Maybe your volume rocker buttons are faulty .
Happened with one of my friend his device was only booting into recovery mode on reboot because vol+ button was permanently stuck ?
Try to lift up the button if it is stuck or
press button repeatedly for sometime .

Ashish 289, you are right, it was a faulty volume rocker. Once disconnected it booted. Thanks.

Multi57 said:
Hi,
My phone got a message about a virus which I assumed was a devious add, it wouldn't go away so I rebooted. It has gone into Mi-Recovery 3.0 and I cant get out. I've tried to connect to PC suite but it won't connect to my laptop
without debugging, which I can't do. I've wiped data but no good. Any ideas?
Click to expand...
Click to collapse
now its my turn brother got my mi5 bricked in the same way .
it stays in mi recovery 3.0 always . if you tell me what you did after these steps not working ? could you do anything ?
need a solution man, please help .
thanks in advance.

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