Database Info

A bit of an emergency...

Hey there, guys and gals,
I'm having a bit of an issue here, and it's somewhat serious.
The issue is as follows. I have Android 5.0.1 on my Nexus 5. When I connect my computer to my laptop... nothing.
Nothing at all. It doesn't show up in device manager, not even as unknown. Fastboot doesn't detect it, nor does ADB. I can't do anything, and it's scaring me. I don't know how I could have broken it, but I need to know how to fix it.
I'm happy to do whatever to get it working, so please help...
Update: Tried to factory reset, to see if it would fix the issue. It's stuck "Erasing...", and won't go further. I'm afraid my phone may be hard-bricked... Is it possible to reflash these using JTAG, and if so is there anyone that can assist with that process?

CypherX1389 said:
Hey there, guys and gals,
I'm having a bit of an issue here, and it's somewhat serious.
The issue is as follows. I have Android 5.0.1 on my Nexus 5. When I connect my computer to my laptop... nothing.
Nothing at all. It doesn't show up in device manager, not even as unknown. Fastboot doesn't detect it, nor does ADB. I can't do anything, and it's scaring me. I don't know how I could have broken it, but I need to know how to fix it.
I'm happy to do whatever to get it working, so please help...
Update: Tried to factory reset, to see if it would fix the issue. It's stuck "Erasing...", and won't go further. I'm afraid my phone may be hard-bricked... Is it possible to reflash these using JTAG, and if so is there anyone that can assist with that process?
Click to expand...
Click to collapse
Is it stock or what? are you rooted?

Also , keep in mind that the factory reset can take up to 30 minutes.
IMO it sounds like a busted cable/usb port on either side / incorrect drivers.
Edit : JTAG is not possible on our devices , access is locked from the chipset itself.

Are u on Windows 8.1 if so I had a problem with Windows thinking that my phone was a acer and I had to go the driver settings and manually tell it that it was a ADB USB connection then it would connect fine also could be USB cable I found the nexus 5 to be very picky about cables

Sometimes I get that but it solves by going into dev and checking and unchecking usb debugg, but sounds more like a busted usb plug

Have you considered that you may be using incorrect drivers on your PC? This issue can be caused by having improperly installed drivers.

dkconor said:
Have you considered that you may be using incorrect drivers on your PC? This issue can be caused by having improperly installed drivers.
Click to expand...
Click to collapse
Alxhn said:
Sometimes I get that but it solves by going into dev and checking and unchecking usb debugg, but sounds more like a busted usb plug
Click to expand...
Click to collapse
xstokerx said:
Are u on Windows 8.1 if so I had a problem with Windows thinking that my phone was a acer and I had to go the driver settings and manually tell it that it was a ADB USB connection then it would connect fine also could be USB cable I found the nexus 5 to be very picky about cables
Click to expand...
Click to collapse
Niflheimer said:
Also , keep in mind that the factory reset can take up to 30 minutes.
IMO it sounds like a busted cable/usb port on either side / incorrect drivers.
Edit : JTAG is not possible on our devices , access is locked from the chipset itself.
Click to expand...
Click to collapse
AndreIrawan97 said:
Is it stock or what? are you rooted?
Click to expand...
Click to collapse
Right. I'll address you all at once for ease.
Firstly, the USB connector functions fine. My USB-OTG cable still allows me to access files on a flash drive.
Secondly, drivers can't be an issue in this case. It won't even enumerate the device in device manager. As if the phone simply isn't plugged in.
Thirdly, Win8 isn't the issue, as I"ve had this phone connected to this computer many, /many/ times.
So it must be a problem within Android 5.0.1
But here's the problem. In order to install anything else, I'd have to install a recovery. In order to that, I need root. In order to root, I need USB. I'm lost, guys...

I just had an idea does towel root work on 5.0 if so u could try that?

xstokerx said:
I just had an idea does towel root work on 5.0 if so u could try that?
Click to expand...
Click to collapse
Hmm... That might work. I'll take a look. But if it succeeds, then something gets broken later in the process, this thing is a paperweight, right?
Edit: According to http://forums.androidcentral.com/an...29-rooting-nexus-5-towelroot.html#post4125236 Towelroot will never be possible on Lollipop. I didn't go much further than that though...

Ya I just read that to bummer
Edit: as of now there is no way to root without pc sounds like u may have some sort of hardware failure I'm guessing only way to fix is to send it in and that's 150 bucks min

xstokerx said:
Ya I just read that to bummer
Edit: as of now there is no way to root without pc sounds like u may have some sort of hardware failure I'm guessing only way to fix is to send it in and that's 150 bucks min
Click to expand...
Click to collapse
Well... This happened when I updated via OTA (after reinstalling the stock recovery) to 5.0.1 after 5.0. I did this all over USB. Immediately thereafter, it quit. I got it to boot, btw. The erasing problem fixed itself, and it's now running, but the USB is still stuffed. This is sounding more like software than hardware. Almost as if whatever chip talks via USB lost it's own firmware somehow.

Cable or driver 95% sure. Did you try connecting it to a windows 7 /linux pc ? And ... u can never be sure but try connecting to a usb2.0 port. I had those issues when I accidentally plugged my cable in my frontal panel ( usb3.0)

A few months ago I had the same problem, my phone got not recognized by adb or fastboot. I played around a whole day with drivers and stuff like that. At the end I found a post on the internet describing that not all USB cables are able to do adb connections and I should try the original USB cable that came with my Nexus 5. So I looked for that particular cable and hey presto it worked right away.

And 2$ usb cables do break over time. They might still charge , but one cold solder joint and no connection

CypherX1389 said:
Secondly, drivers can't be an issue in this case. It won't even enumerate the device in device manager. As if the phone simply isn't plugged in.
Click to expand...
Click to collapse
So you are correct. I didn't see that in your post, my bad.

Have you tried with another cable maybe?

Make sure you have either MTP or PTP checked in Settings/Storage/USB computer connection.

Niflheimer said:
Cable or driver 95% sure. Did you try connecting it to a windows 7 /linux pc ? And ... u can never be sure but try connecting to a usb2.0 port. I had those issues when I accidentally plugged my cable in my frontal panel ( usb3.0)
Click to expand...
Click to collapse
Georg2808 said:
A few months ago I had the same problem, my phone got not recognized by adb or fastboot. I played around a whole day with drivers and stuff like that. At the end I found a post on the internet describing that not all USB cables are able to do adb connections and I should try the original USB cable that came with my Nexus 5. So I looked for that particular cable and hey presto it worked right away.
Click to expand...
Click to collapse
Telyx said:
Make sure you have either MTP or PTP checked in Settings/Storage/USB computer connection.
Click to expand...
Click to collapse
Alxhn said:
Have you tried with another cable maybe?
Click to expand...
Click to collapse
Niflheimer said:
And 2$ usb cables do break over time. They might still charge , but one cold solder joint and no connection
Click to expand...
Click to collapse
I've tried multiple cables. I KNOW that this cable is fine for ADB, because it works fine for my other devices. All of them. I may be marked a newbie on the forums, but I'm really not one. When I first signed up for this account I was, but that was in what... '07?
I've tried:
Drivers (Obviously won't work.)
Cables
Rebooting
Factory Reset
Different Computers
Linux
Windows
Switching USB connection modes
Toggling Dev Mode/Debugging on/off
Nothing works. It HAS to be a software issue on the phone. I don't think anyone read it, but it's almost as if the IC that handles USB connections has lost it's firmware. I don't think that can happen, honestly, so it must be whatever's in the ROM that TALKS to that IC that's causing the issue. Problem is, I don't know how to fix the ROM without USB connection and Fastboot.

CypherX1389 said:
Nothing works. It HAS to be a software issue on the phone. I don't think anyone read it, but it's almost as if the IC that handles USB connections has lost it's firmware. I don't think that can happen, honestly, so it must be whatever's in the ROM that TALKS to that IC that's causing the issue. Problem is, I don't know how to fix the ROM without USB connection and Fastboot.
Click to expand...
Click to collapse
Its unlikely that the ROM will be the cause if the USB port suddenly stops working.
Do you have a custom recovery?
If not, then not much you can do except send it in for repair/replacement.

[Q] Cannot detect Nexus 5 except fastboot

So I've tried absolutely everything, new drivers, flash batch all newest firmware.. different computers, restarting computer..
whatever I do I cannot manage to get any computer to detect my Nexus 5 via adb or mounted storage.. the only thing that is detected is fastboot..?
any ideas??

Maybe it's a driver problem on your system. Did you try another computer?

What does device manager show? An unknown device connected? An acer device connected?
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5

Ben36 said:
What does device manager show? An unknown device connected? An acer device connected?
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
nothing, nothing detected at all. but the USB port on the phone works fine because fastboot is working fine..

any idea's anybody? I've tired several computer with different windows versions.
This phone is absolutely undetectable by USB/ADB. It charges perfectly fine and fastboot works flawlessly...

You have an issue with the Nexus 5's driver and your adb driver, but not your fastboot driver.
Try uninstalling/reinstalling the drivers and use the 15-second adb/driver installer, if that doesn't work then try the universal naked driver.

Elluel said:
You have an issue with the Nexus 5's driver and your adb driver, but not your fastboot driver.
Try uninstalling/reinstalling the drivers and use the 15-second adb/driver installer, if that doesn't work then try the universal naked driver.
Click to expand...
Click to collapse
tried both, this phone isn't detected by any computer at all when it's switched on, zero. It doesn't show up as android, or acer or anything, there is no driver able to be installed because the phone isn't even detected by the computer unless I put it in fastboot mode.

omg, first the first time it just got magically detected in TWRP as ADB composite device. This is completely un-explainable, it's been days this was achievable..
restarted phone, impossible to detect again....

THE_KINGDOM said:
tried both, this phone isn't detected by any computer at all when it's switched on, zero. It doesn't show up as android, or acer or anything, there is no driver able to be installed because the phone isn't even detected by the computer unless I put it in fastboot mode.
Click to expand...
Click to collapse
You can still install/uninstall a driver if the device is not plugged in/detected as unknown device.
Have you tried manually reinstalling the driver?

Elluel said:
You can still install/uninstall a driver if the device is not plugged in/detected as unknown device.
Have you tried manually reinstalling the driver?
Click to expand...
Click to collapse
it's not detected at all thats what I'm trying to explain, it's not an unknown device, it's never detected at all

THE_KINGDOM said:
it's not detected at all thats what I'm trying to explain, it's not an unknown device, it's never detected at all
Click to expand...
Click to collapse
If you are certain it is an issue with the device and not your drivers, try booting up a Linux distro (Ubuntu will do) in a VM or directly off a USB stick, as it requires no driver installation in Linux to access the internal storage via USB.

Elluel said:
If you are certain it is an issue with the device and not your drivers, try booting up a Linux distro (Ubuntu will do) in a VM or directly off a USB stick, as it requires no driver installation in Linux to access the internal storage via USB.
Click to expand...
Click to collapse
it's strange because for the first time a few moments ago i was able to see the device in adb mode via TWRP, as soon as I restarted the phone it's impossible again, I've tried 20+ times since then.
only thing i can get repeatedly with no issues at all is the bootloader interface/fastboot

tried with linux, ubuntu. no connection.. But I already knew it wasn't drivers.. device isn't detected at all.. it's not like it's allocating the wrong drivers.. it's not even registering a usb device was connected to the PC unless in bootloader/fastboot.

Sounds like an issue with your usb cable or the phone side adapter. Have you tried ADB through a wireless connection?

[RANT ON]
I have already addressed your issue in this thread http://forum.xda-developers.com/google-nexus-5/help/diagnosing-usb-driver-adb-issues-windows-t2514396/post59570828#post59570828 and yet without so much as even a single reply or simple thank you for taking my time and telling you in detail how it is, you found it necessary to create a new thread? Are you hoping for a magic bullet?
What's even worse in my world. You offered not a single thank you to anyone here in this tread that completely wasted their valuable time trying to help you after you already have your answers.
I realize I am relatively new member here at XDA. But I've been lurking here for over 5 years. Forgive me but this guy is why I have been reluctant to join and help until recently. He is the reason I will not waste much more of my time attempting to help others. [RANT OFF]
I will try to calm now.
Thanks for listening and I don't care if you are offended.
THE_KINGDOM said:
my situation is quite different from yours. There is no ability to "adb reboot" my device because the device is completely undetectable by USB.
I've now only managed to see the device twice in adb mode and that was completely random while in TWRP recovery, and I didn't need to turn on ADB sideload to make it visible either.. other than these two times I've tried well over 100-150 times, this phone is absolutely undetectable by USB/Computer unless in the bootloader.
Click to expand...
Click to collapse
joegestes said:
If you are able to detect the device in bootloader "fastboot devices" but still can't ABD devices in android with USB debug enabled or in recovery and/or you experience intermittent ABD detection. After looking through OP and post #322 you are absolutely certain that it is not a driver issue, you are likely looking at a hardware failure of the charging port.
https://www.youtube.com/watch?v=qqCEXEmcj4Y
If it were me, I'd replace the port and re-attempt ADB devices.
Click to expand...
Click to collapse
joegestes said:
Also be sure to try a new high quality USB data cable. (not a cheep charging cable)
Click to expand...
Click to collapse

joegestes said:
[RANT ON]
I have already addressed your issue in this thread http://forum.xda-developers.com/goo...es-windows-t2514396/post59570828#post59570828 and yet without so much as even a single reply or simple thank you for taking my time and telling you in detail how it is, you found it necessary to create a new thread? Are you hoping for a magic bullet?
What's even worse in my world. You offered not a single thank you to anyone here in this tread that completely wasted their valuable time trying to help you after you already have your answers.
I realize I am relatively new member here at XDA. But I've been lurking here for over 5 years. Forgive me but this guy is why I have been reluctant to join and help until recently. He is the reason I will not waste much more of my time attempting to help others. [RANT OFF]
I will try to calm now.
Thanks for listening and I don't care if you are offended.
Click to expand...
Click to collapse
Wow man you need to cut the estrogen pills out. This is borderline extremely weird...
You gave me one potential plausible scenario and this thread was created days before my activity on that other thread. And my first comment u quoted was a reply to somebody else lolol...
Also, I have no charging issues whatsoever with this phone... therefore charging port may not be an issue at all. But at this point I don't deny that chances are it's an extremely rare hardware issue, rare.. Hence why I'm trying to explore potential software issues/fixes before hand.
And actually I'm very generous with the "thank you" I dish out to users on XDA, unfortunately I most people seem to think its a driver issue because thats the common issue.. But im trying to relay to people that my phone is not detected at all, zero recognition of a USB attached device. EXCEPT when in fastboot.. Which makes no sense... If it was a broken port then why does fastboot work????

THE_KINGDOM said:
If it was a broken port then why does fastboot work????
Click to expand...
Click to collapse
Because it could be a single broken connector in the port, it could be a bad internal connector, it could be a motherboard issue, etc.

THE_KINGDOM said:
Wow man you need to cut the estrogen pills out. This is borderline extremely weird...
Click to expand...
Click to collapse
Resorting to childish insults when you are called out is weird for a Man and IMO cowardly.
It is also why you should consider taking you own sage advice.
THE_KINGDOM said:
You gave me one potential plausible scenario
Click to expand...
Click to collapse
Actually, I gave you virtually all plausible scenarios.
THE_KINGDOM said:
this thread was created days before my activity on that other thread.
Click to expand...
Click to collapse
Correct. You did not create a new thread afterwards. You first created a new thread and then posted the same issue in a separate thread.
My mistake.
But still you are here, after you already have your answers, never bothering to thank anyone.
THE_KINGDOM said:
I don't deny that chances are it's an extremely rare hardware issue
Click to expand...
Click to collapse
Good, but IMO, it's not that rare on N5.
THE_KINGDOM said:
And actually I'm very generous with the "thank you" I dish out.
Click to expand...
Click to collapse
I,ll give you the same answer I give most people I encounter who are likely in denial.
Your Right! :good:

I haven't seen this mentioned, just making sure you have turned on usb debugging in the developer options otherwise adb won't work.
Sent from my Nexus 5 using Tapatalk

LG G6 stuck in firmware update, windows can't detect com port

I need help... Is my phone dead or what..? I tried to update software via lg up and uppercut (which i did like 10 times on this phone already) and this time something gone wrong on 10% the lg up turned off by itself after some timeout and my wonderful cable unplugged because if I don't hold it, then it falls off. I tried to relaunch uppercut which had an error, I rebooted my laptop and uppercut worked again, but my phone couldn't be detected (as it used to be a couple of minutes earlier) as a com port or anything. I rebooted the phone, it came back to firmware update. Still no reaction, trying to install legacy driver in device manager, ports (com & lpt) as communication gives out code 34. Installing newer lg usb drivers also don't work... Any idea what to do..?

Did you fixed already your phone? This is my problem also.

charledave said:
Did you fixed already your phone? This is my problem also.
Click to expand...
Click to collapse
You probably flashed the wrong update for your device and now your device is bricked, potentially hard bricked, if it is hard bricked, you won't be able to fix it. You can try sending it to a shop to repair it but they would probably just replace your motherboard. Or, you can try changing the motherboard yourself.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
You probably flashed the wrong update for your device and now your device is bricked, potentially hard bricked, if it is hard bricked, you won't be able to fix it. You can try sending it to a shop to repair it but they would probably just replace your motherboard. Or, you can try changing the motherboard yourself.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
thanks bro.

T-Mobile OnePlus -- Hard (HARD) Brick

Sorry for lack of details, but I'm not sure it will help anyway. Feeling pretty bad right now.
T-Mobile Oneplus 7 Pro. 256GB version.
I wanted to go to stock OxygenOS after buying the branded version two weeks ago.
I successfully got T-Mobile to unlock my SIM, and got OnePlus to send me unlock code for my bootloader after a week.
Successfully unlocked via fastboot. Tried several times to flash TWRP and no success using fastboot.
Tried MSM-Downloader from guacamole_21_O.07_190512_repack and successfully held volume both buttons to connect to the PC. MSM-Downloader said it was successfully connected.
I cannot find the exact error message I got from MSM-Downloader, but it said it didn't match plus another error message. At that point, my heart sank.
USB Device Not Recognized keeps popping up on windows again and again, while the connect sound plays. Doesn't matter if I hold down the volume buttons or not.
Can't get into qualcomm EDL mode. My guess is I hosed my boot and now it restarts endlessly when connected to anything at all.
Is this the end of my journey? I did tons of research on the best phone and the best deals available to save money, but looks like I played myself here with lack of caution.

I would suggest following this guide to attempt reflashing of the international firmware (use the androidfilehost download).
If that also fails, you could always just reflash the TMO firmware with this guide.

bmg1001 said:
I would suggest following this guide to attempt reflashing of the international firmware (use the androidfilehost download).
If that also fails, you could always just reflash the TMO firmware with this guide.
Click to expand...
Click to collapse
I cannot get into EDL. Regardless of what buttons I press (I am holding both volume buttons down in excess of 5 seconds) when connecting USB to the phone, Windows makes the "connect" sound endlessly and the driver isn't recognized.
If I can get into EDL, I will definitely try the above.

Do you have the proper drivers installed to use EDL mode?
Also, if you go into the Device Manager, do you see the phone in there? Should pop up as something like "Qualcomm HS-USB 9008" or some variant of that.

bmg1001 said:
Do you have the proper URL installed to use EDL mode?
Also, if you go into the Device Manager, do you see the phone in there? Should pop up as something like "Qualcomm HS-USB 9008" or some variant of that.
Click to expand...
Click to collapse
Ok. I may be making progress thanks to your help but do have some hurdles I can see.
I do see the device when I hook it up to another computer. It shows up as Unknown USB Device (Device Descriptor Request Failed).
When I go to device manager to manually update the driver, and browse to the location I extracted the CAB file into, I see lots of devices to choose from, but the Qualcomm driver cab file list does not show "Qualcomm HS-USB QDLoader 9008" as an option. I see many Qualcomm USB Composite Devices in the list but none I have chosen seem to work (install fails).

Hmm. I know it may be an obvious question, but just to be sure, you're using the cable that came with the device correct?

bmg1001 said:
Hmm. I know it may be an obvious question, but just to be sure, you're using the cable that came with the device correct?
Click to expand...
Click to collapse
Yes, that is correct. Same cable i used to get into fastboot, etc... The original PC I caused the problems with recognized the device differently (showed up as a Qualcomm device) when I got into EDL with it before.
Edit: First event when plugging it into this second PC under device properties:
Device USB\VID_0000&PID_0002\5&3c8d678&0&2 was not migrated due to partial or ambiguous match.
Last Device Instance Id: USB\VID_0000&PID_0000\5&1AE39384&0&2
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path:
Migration Rank: 0xF000FFFFFFFFF000
Present: false
Status: 0xC0000719

I just did some googling and found this article. Perhaps you can try the drivers in this guide? They are .exe files so they should be easy to install, but I'm not sure if the other drivers I provided have any OnePlus specific stuff in it, but it's worth a shot.

bmg1001 said:
I just did some googling and found this article. Perhaps you can try the drivers in this guide? They are .exe files so they should be easy to install, but I'm not sure if the other drivers I provided have any OnePlus specific stuff in it, but it's worth a shot.
Click to expand...
Click to collapse
I've already tried the .zip version with no success. I am loath to install an .exe file (don't want to make the problem worse by infecting my PC) but may as well. I will restart and report back. Thank you again for your attention.
If this doesn't bear fruit, I may be SOL, correct?

unluckyoneplus7pro said:
I've already tried the .zip version with no success. I am loath to install an .exe file (don't want to make the problem worse by infecting my PC) but may as well. I will restart and report back. Thank you again for your attention.
If this doesn't bear fruit, I may be SOL, correct?
Click to expand...
Click to collapse
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.

bmg1001 said:
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.
Click to expand...
Click to collapse
I'll try there next. Can't seem to get any of my windows machines to recognize the thing.

bmg1001 said:
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.
Click to expand...
Click to collapse
OK! I found on reddit that if you hold your vol up + down + power for 30 seconds, it will boot back into fastboot, which it did! Holy **** I'm so happy. Haven't even seen if the PC recognizes it but will check now. If it does, I just need to not screw up the conversion to international.
Thank you for your "unbrickable" comment. That gave me hope to not give up.

unluckyoneplus7pro said:
OK! I found on reddit that if you hold your vol up + down + power for 30 seconds, it will boot back into fastboot, which it did! Holy **** I'm so happy. Haven't even seen if the PC recognizes it but will check now. If it does, I just need to not screw up the conversion to international.
Thank you for your "unbrickable" comment. That gave me hope to not give up.
Click to expand...
Click to collapse
I just wanted to share a tip. After you load the msmtool and before you connect your phone with the cable, click the start button, the message will read "waiting for device". Then, as soon as you plug in the cable while holding the p-up and p-down, the msmtool will automatically start. No more rushing to hit the start button before EDL mode times out.

razorshiv said:
I just wanted to share a tip. After you load the msmtool and before you connect your phone with the cable, click the start button, the message will read "waiting for device". Then, as soon as you plug in the cable while holding the p-up and p-down, the msmtool will automatically start. No more rushing to hit the start button before EDL mode times out.
Click to expand...
Click to collapse
That's pretty cool. Makes the whole process much less stressful.
Got it up and running with international version. Now to see if I can get LOS installed. My sincere thanks to all and apologies for crapping up the board with my panic. I thought I had really screwed up, but it appears it was just stuck in EDL mode and needed a hard (HARD) reset.

Hey man, thanks for the donation. Glad you were able to get your phone up and running!

Holy Sh*t man. I know 5 bucks ain't much but I wanted to thank you so much. I thought I was fukd

motorola one vision hardbrick

hey, my motorola one vision got this message displaying " your device has failed verification and may not work properly" that i rescued it and replaced firmware with motorola assistant software then after a while it dead again and now hardbricked it is not not even recognized by my pc before it showed at least exynos driver in ports now it displays not recognized, I tried giving it to service center but they returned it and told they can't fix it connsider going come other center...., so is there anything i could do to get it recognized by my pc..?

Hardbricked means a hardware component became faulty thus phone is dead. In your case phone is basically working even though erroneous: that means your phone may be softbricked.
BTW: The mentioned message is normal if phone's bootloader is unlocked.

jwoegerbauer said:
Hardbricked means a hardware component became faulty thus phone is dead. In your case phone is basically working even though erroneous: that means your phone may be softbricked.
BTW: The mentioned message is normal if phone's bootloader is unlocked.
Click to expand...
Click to collapse
if it is soft bricked at least it should show the processor connected.., bt in my case it just connects and not turning fastboot or cant even do blank flash

jwoegerbauer said:
Hardbricked means a hardware component became faulty thus phone is dead. In your case phone is basically working even though erroneous: that means your phone may be softbricked.
BTW: The mentioned message is normal if phone's bootloader is unlocked.
Click to expand...
Click to collapse
And i tried that ADB-FASTBOOT-INSTALLER, still it shows not recoganized

Re-flashing phone's Stock ROM never is done
Ammar595 said:
And i tried that ADB-FASTBOOT-INSTALLER, still it shows not recoganized by Fastboot.
Click to expand...
Click to collapse
To successfully run Fastboot you additionally have to install on Windows computer the "Android USB Driver" that is suitable to your phone.
See also here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
support.motorola.com

jwoegerbauer said:
Re-flashing phone's Stock ROM never is done
To successfully run Fastboot you additionally have to install on Windows computer the "Android USB Driver" that is suitable to your phone.
See also here:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
support.motorola.com
Click to expand...
Click to collapse
yes tried this too still not recoganized..

Both ADB and Fastboot at Android-side get initialized by phone's bootloader. If ADB works but Fastboot not then phone's Android is corrupted. This is obviously due to the fact that you have tampered Android.

jwoegerbauer said:
Both ADB and Fastboot at Android-side get initialized by phone's bootloader. If ADB works but Fastboot not then phone's Android is corrupted. This is obviously due to the fact that you have tampered Android.
Click to expand...
Click to collapse
so what should i do now..?

jwoegerbauer said:
Both ADB and Fastboot at Android-side get initialized by phone's bootloader. If ADB works but Fastboot not then phone's Android is corrupted. This is obviously due to the fact that you have tampered Android.
Click to expand...
Click to collapse
this is what its showing and phone is completly dead like a brick..

Delete this USB device from within Windows' Device Manager. Re-install the "Android USB Driver".

jwoegerbauer said:
Delete this USB device from within Windows' Device Manager.
Click to expand...
Click to collapse
yes i did that too, stilll not working....

Ammar595 said:
so what should i do now..?
Click to expand...
Click to collapse
Does this work?
Code:
adb devices

jwoegerbauer said:
Does this work?
Code:
adb devices
Click to expand...
Click to collapse
no..... the only thing working is that it shows not recoganized

We could have saved ourselves all this back and forth if this had been known from the start.

jwoegerbauer said:
We could have saved ourselves all this back and forth if this had been known from the start.
Click to expand...
Click to collapse
so there's nothing i could do now...?

Ammar595 said:
so there's nothing i could do now...?
Click to expand...
Click to collapse
my sdcard reader also show that i think thats normal

ineedroot69 said:
my sdcard reader also show that i think thats normal
Click to expand...
Click to collapse
what is normal....? my phone is entirely dead, it isn't responding al it does is shows not recognized
when i connects it to my pc, ya maybe that's normal, bt am asking for solution not a compliment