Develop Bugs

Usb brick fix unrooted. S-on

TOTAL NOOB HERE.
I have already posted but everyones situation is different to mine and I really need someone to talk me through what it is I need to do I've been trying to fix this issue for the last 20hrs with no sleep!
Here is the situation:
I have an HTC Desire HD 2.3.3. It is S-ON. The issue (after doing hours of reading) appears to look like a classic USB brick. As in no matter what sdcard I place in the phone it still reads as "unavailable" with no mounting options. Same thing happens when I connect to the PC I have HTC SYNC/Charge only/USB Tethering but no Mass storage option. This is driving me F****** mad now!
I have already tried 3 different SDcards all three are class 2 and both work fine in my Galaxy S2 and have also reformatted all 3 in the PC using Fat32 and even through command line prompt. I've also tried 2 different USB cables on various usb ports. I have tried cleaning contacts and even beefing up the cover with folded paper. Bluetooth works fine and when I connect it to the PC i have all the options you would expect to see apart from mass storage. The issue is the card will not mount and everything just reads 'unavailable' inc mount - which is just greyed out.
I have managed to get ADB/Fastboot to work (at least I think) I can perform function: 'Fastboot oem enableqxdm 0' when I am in boot menu (vol down + power) and I get a msg which says OKAY. However at this moment in time I need the help of GOD! I have SDK installed with all packages installed and placed in C:/android. I also have USB debugging enabled. Should I be executing these commands from boot menu (Fastboot usb) or the phones desktop. when I try 'adb devices' while phone is in desktop it reads fine and tells me that there is a device listed. but when I try ...enableqxdm from desktop I just get 'waiting for device'. I have used PDAnet to correctly install ADB drivers. I am running Windows 7 64bit. I have factory reset soft/hard. The only thing I havent tried is to see if it appears in recovery mode and the various brick fixes which tbh just confuse the living hell out of me. Please can someone talk me through what it is I need to do I have no idea where to go from here. Like I said I am totally new to this but looking to build up a competency for next time. I have read a guide (Im sorry cant remember who it was by) but they mention to perform 'getvar cid' then follow link to website which creates mtd file...which no longer exists I have searched far and wide and I am ready to throw this piece of crap on ebay for spares/repairs. It was originally on Orange but unlocked and I have been using a tmobile sim which works fine.
PLEASE HELP ME :-(

Edit: Cards not being picked up in recovery mode
Sorry about horizantal fail.
Sent from my GT-I9100 using xda app-developers app

Phone sent to independent repair centre will post with what issue was.

[Q] Bricked Verizon Gnex. Need assistance

My Verizon Galaxy Nexus is bricked. I was having issues with it receiving mobile network signal, so by using TWRP, i factory reset and in the process decided to swipe the internal space. (my first big mistake). I lost all my images, custom roms, gapps, files.
I was unable to boot the phone and decided to use the trusty ODIN back to stock. ...I've done this previously without any issues. I downloaded all the factory 4.0.4 images and attempted many times. I can't remember all the fancy lingo but I believe it continued to get stuck at "NAND write." I was also having troubles with my phone reading "fastboot error" while at the green android screen. It reads "fastboot command read error- 2147483647"
When I tried using wugfresh's gnex tool kit I was able to flash Boot, Bootloader, Radio, Recovery ... but not system. Gave me the ADB error. I'm currently unable to install the adb drivers ... or they're not being recognized because I can't boot my device and select development options.
The "1-click 4.0.4 back to stock toolkit" shows red circles for both fastboot and adb. I'm completely lost .... and frustrated at this point.
I used the "galaxy nexus toolkit" and when it executes it writes everything but also says FAILED at the end of every line. At this point I feel my two biggest issues are ADB driver so my phone's not recognized .... also something to do with the partition on the internal sd. I don't think these programs know where to write the data on my phone...........
This go around, I'm unsure what happened but I'm left with the phone, Yellow Triangle! and computer monitor icon. I was able to odin a file called "u1_02_20110310_emmc_EXT4.pit" (unsure how or where I came up with this file...) which PASSED and the phone reboots back to the green android icon screen.
I've tried many ODIN versions, three different usb cables and three computers, with all ports. I'm still getting hung up with PDA and PHONE files when trying to odin back to stock. The device shows up on ODIN and the files are reading ... it just gets hung up like the pc can't communicate with the phone.
I'm sorry for not having the language to express in detail what I'm enduring. I will be receiving a replacement device in the mail tomorrow and hoping I can connect it to the PC and hopefully have the driver's install properly.
Any and all help would be appreciated.

I am able to boot into ODIN mode and also the screen with green android with chest open. It reads in red letters "no revocery or boot img"
The device is still in locked status.
...sure hope this passes the brief Verizon inspection.

My tool failed you? I have other ideas. Pm me
Sent from my Galaxy Nexus using xda app-developers app

vabeachfc3s said:
My tool failed you? I have other ideas. Pm me
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm sorry, I tried but your profile only shows skype chat. I'm really unsure how to PM through these forums.
I was able to keep bootloader unlocked and attempted everything once more. I have no ADB access due to the phone not being able to power on and select development tools option.
Fastboot fails on everything primarily due to "partition" issues. .......... I locked the bootloader and boxed it up "as is"

[Q] Wiped everything with TWRP 2.8.4.0, now softbricked?

So just as the title says, but here's a little back story (might help).
I'm trying to help out a friend with his Bell Mobility i747M. He wanted to try out Lollipop, so I looked into it and said I could do it. Last I even touched his phone was quite a while ago when he wanted me to flash CM11, back when KK was still pretty new. So it's been over a year. I flashed CWM back then, got the ROM installed, and everything has been good ever since. Fast forward to now, and he wants to try Lollipop. I figured the first thing I should do is update the bootloader/radio, which went perfectly fine (after some researching, I chose 4.3/MK5 for his i747M). I tested them by booting back to the ROM and checking About Phone - everything was good. So I booted back to the old version of CWM, and thought it would be a good idea to get a more modern recovery. CWM or TWRP didn't matter, just as long as it was more up to date (I thought it might help with Lollipop compatibility). So I decided on TWRP, and I got the latest version (2.8.4.0 as of now) and flashed it. Successfully flashed, then rebooted recovery. TWRP is there and working. Great. Next step... I had the Lollipop ROM and Gapps already downloaded and ready to go, so in TWRP, I proceeded to wipe everything (system, data, cache, internal sd).
Uh oh... Half way through wiping, the phone reboots itself! Now there's no ROM, so naturally it has nothing to boot to. Try going back to TWRP, and I see the splash screen again. OK, false alarm... Well, not really... Because now it just reboots itself after the splash screen, every time. Can't get into TWRP no matter what! I can access download mode, but Odin doesn't recognize the phone. Yes, I have the drivers. In fact, the device isn't detected by Windows at all.
So here we are. Download mode boots, but Odin doesn't work because there's no communication through USB at all. There's no ROM on the phone because it was wiped. And TWRP won't boot beyond the splash screen.... Now what?? I tried the 80MB MK5 debricking .img on a 64GB microSD. It does nothing - besides, USB isn't reading anyway, so it's not like I can proceed with Odin.
I'm at a stalemate here... Any suggestions?
My friend's gonna kill me if I killed his phone I'm pretty experienced with several devices, but not much with Samsung. I've never seen anything like this happen before...

When connecting to the computer, have you tried different USB 2.0 ports and USB cables? Have you tried different computers? Different operating systems?
Is the phone recognized using adb or fastboot commands?

audit13 said:
When connecting to the computer, have you tried different USB 2.0 ports and USB cables? Have you tried different computers? Different operating systems?
Is the phone recognized using adb or fastboot commands?
Click to expand...
Click to collapse
Yeah, I figured that would be the case. Just about done downloading Ubuntu which I'll boot from USB. I'll post back with results once that's ready. I should have it booted within 10 minutes. Once I get there and verify the phone connects, what would be my next step? Should I try flashing stock 4.3 first?

I would confirm the bootloader that is on the phone before flashing anything from sammobile.com.
You may be able to use fastboot commands to get the information by typing fastboot getvar all.

OK, in Linux now. ADB/fastboot won't connect. Tried different USB ports and cables, ones that I know work. No luck...
The only thing I can boot to in the phone is Download mode, so that's where I'm trying from.
For the record, ADB picks up my Nexus 5, so I know it's all set up right.
I'm gonna retry the debrick img, using dd to write it this time.

Bloodflame said:
OK, in Linux now. ADB/fastboot won't connect. Tried different USB ports and cables, ones that I know work. No luck...
The only thing I can boot to in the phone is Download mode, so that's where I'm trying from.
For the record, ADB picks up my Nexus 5, so I know it's all set up right.
I'm gonna retry the debrick img, using dd to write it this time.
Click to expand...
Click to collapse
No luck. wrote to the SD successfully, and it just boots to download mode. Nothing else.
ADB and fastboot still do nothing

Maybe the phone's USB port is flaky?
Have you tried Kies to see if it recognizes the phone?

audit13 said:
Maybe the phone's USB port is flaky?
Have you tried Kies to see if it recognizes the phone?
Click to expand...
Click to collapse
I don't have Kies, but I'm doubting that would work anyway. There's absolutely no communication between the computer and phone. Nothing happens when I plug it in. No sound, no indication anything was even plugged in. Running lsusb in a terminal doesn't show the phone either.
Edit: Downloading Heimdall (Linux-compatible Odin)...

Bloodflame said:
I don't have Kies, but I'm doubting that would work anyway. There's absolutely no communication between the computer and phone. Nothing happens when I plug it in. No sound, no indication anything was even plugged in. Running lsusb in a terminal doesn't show the phone either.
Click to expand...
Click to collapse
Okay, forget kies. Sounds like a USB port issue. Does the phone start charging when connected to a power source?

audit13 said:
Okay, forget kies. Sounds like a USB port issue. Does the phone start charging when connected to a power source?
Click to expand...
Click to collapse
Plugging into the wall makes the phone vibrate every couple of seconds, but nothing shows up on screen, and there's no indicator light.
The vibrations lead me to believe it's detecting something, but no indicator light worries me (unless that's just because there's no kernel)
The red light does come on if I plug it in without the battery.
Heimdall fails to detect the device as well (no surprise there)

If the phone was bricked, it would usually be recognized as a some sort of device under Windows' device manager which leads me to conclude that it is a USB port issue.

audit13 said:
If the phone was bricked, it would usually be recognized as a some sort of device under Windows' device manager which leads me to conclude that it is a USB port issue.
Click to expand...
Click to collapse
I agree that it is weird, because it's not coming up as a device at all, in either Windows or Linux, yet it does receive power.

I'm guessing here but it appears to me that the only left to try is a debrick image. Is it possible the battery is drained and needs to be charged?

audit13 said:
I'm guessing here but it appears to me that the only left to try is a debrick image. Is it possible the battery is drained and needs to be charged?
Click to expand...
Click to collapse
The debrick image is what I've been trying. It's on a 64GB microSD. And I made a new one from Linux a few minutes ago (booted back to Windows now).
The battery was about 80% before all this started, and the phone powers on without being plugged in, so I doubt it's the battery.

Maybe you need a different SD card? Based on posts I have seen, it seems that certain brand/size combinations work while others don't.

audit13 said:
Maybe you need a different SD card? Based on posts I have seen, it seems that certain brand/size combinations work while others don't.
Click to expand...
Click to collapse
I only have one card over 16gb...
Either way, I still have the USB problem. I'll need USB to flash with Odin. The debrick card only seems useful when Download mode isn't working, but that part works fine on the phone, even without the debrick card. My problem is with recovery. If I could run that from the SD, I think I would be fine - just flash a ROM. But I'm not finding anything for that (not surprised).
I thought it could potentially be a corrupt driver, so I tried using USBDeview to uninstall all disconnected devices. I tested it with a portable hard drive, which indeed had to reinstall after. So the program works as intended. However, the phone still isn't detected when I plug it in. No sound, no notification saying it's installing or install failed - absolutely nothing. Power goes to the phone through USB, with multiple cables and USB ports. Just no data connection.
I'm starting to think there's just nothing I can do...

The phone may need a USB port replacement. I know of no way to push recovery to the phone from as SD card without USB capabilities.

audit13 said:
The phone may need a USB port replacement. I know of no way to push recovery to the phone from as SD card without USB capabilities.
Click to expand...
Click to collapse
Yeah, that's what I'm thinking. Found this, and it's cheap enough... But that shipping!

You'd be better off getting it from China with free shipping. The problem is the amount of time required to get the part.
Maybe contact a cell repair shop to see how much it would cost to have them replace it. Soldering is not my strongest skill

audit13 said:
You'd be better off getting it from China with free shipping. The problem is the amount of time required to get the part.
Maybe contact a cell repair shop to see how much it would cost to have them replace it. Soldering is not my strongest skill
Click to expand...
Click to collapse
Yeah, doesn't look easy. I already tore down to here, and visibily, it looks OK. I'm not so sure about soldering either :silly:
I appreciate your assistance.

Win10 PC won't find phone at all

Hello guys,
I really hope,you can help me. I wanted to update my phone from 14.1 to 15.1.
First problem was, my Nexus 5x wasn't recognized by my pc at all (not even as an unknown device in device manager).
Solution: Under developer options, disable and enable USB-debugging.
After that my phone was recognized, even "fastboot devices" gave a result.
I rebooted into recovery (latest TWRP), wiped everything and rebooted into fastboot to start flashing radio, bootloader, vendor etc.
Problem
Now again, my PC won't recognize the Nexus 5x at all (again also not even as an unknown device) and also TWRP won't let me mount the USB partition.
I am not able to disable and enable USB-debugging again, because I do not have a OS installed anymore. Also ADB-sideloading won't work.
What can I do?
Reasons I can rule out:
1. broken cable - tried 3 different ones, also in the meantime phone had been recognized by PC
2. broken drivers - not possible, phone had been recongized as fastboot device
Please help! How can I let Windows recognize the device?

I had a similar problem with the 5x. Every other Android device I had was recognized except the 5x. This solved the problem, https://forum.xda-developers.com/showthread.php?t=3236946
Sent from my [device_name] using XDA-Developers Legacy app

Thanks a lot for your answer! The problem with this is, that in device manager, I see no device at all. So there is no way, I can right-click on a device to uninstall it or to update its drivers. Or which part of the thread are you referring to?

I think you got the right part of the thread. It's the part that's quoted and I think links back to a post by threewolfs. But if nothing shows up in device manager that's a problem. If you boot into recovery does adb recognize your device?
And if it does what does device manager show?
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
I think you got the right part of the thread. It's the part that's quoted and I think links back to a post by threewolfs. But if nothing shows up in device manager that's a problem. If you boot into recovery does adb recognize your device?
And if it does what does device manager show?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
There is nothing in device manager at all, not in recovery, not in fastboot. ADB does not find it too. As I said, at one point I got the computer to see it (after disabling and enabling USB debugging), then I rebooted into recovery, wiped everything, rebooted from there into fastboot - nothing.

I'm not sure what to tell you. Just wiping the device in twrp? Should not have caused a problem. You don't have another Android device you could try? The only other things I'd do is if you're using a pc use the USB ports in the back of it, not the front. And try different cables, although it seems you already did that.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
I'm not sure what to tell you. Just wiping the device in twrp? Should not have caused a problem. You don't have another Android device you could try? The only other things I'd do is if you're using a pc use the USB ports in the back of it, not the front. And try different cables, although it seems you already did that.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
You're already helping by listening and answering, because I feel like this is a really weird issue and I have no idea at all.
I am not at home right now, but as soon as I am, I will first try another PC. My computer only has one USB port, but maybe I'll try a hub, too. Will keep this thread updated.

Sounds good. Good luck.
Sent from my [device_name] using XDA-Developers Legacy app

So, I've tried another USB-Port and another computer, where another phone in Fastboot is being recognized. Must be an issue of the Nexus, but I have no idea what it could be.

I saw your post earlier and have been thinking about it. I don't have any good suggestions but Google 15 second adb xda. You'll find a tool there that installs drivers and adb and fastboot. I don't think it will make a difference, but who knows. If I think of anything else I'll post it.
Also with the device connected open a command window, or power shell, and type
adb kill-server
adb start-server
Then if you're in the bootloader, fastboot devices. And keep your fingers crossed.
Sent from my [device_name] using XDA-Developers Legacy app

I am in a somewhat similar situation. Was running PureNexus ROM, when suddenly got BLOD. In my desperation, I wiped data clean as soon as it booted into TWRP after a million tries. but it's back to BLOD, as soon as I tried quitting recovery. Now device won't go beyond Google logo, and the bootloader (fastboot) mode is not being detected in PC so I am not able to flash the fixed boot.img file.
I tried all driver installation methods, but the culprit is incorrect device ID being shown to my PC - USB\VID_0000&PID_0002\5&ECB7860&0&9 (unknown usb device - device descriptor request failed). Any idea how I can salvage my device ?

bikerabhinav said:
I am in a somewhat similar situation. Was running PureNexus ROM, when suddenly got BLOD. In my desperation, I wiped data clean as soon as it booted into TWRP after a million tries. but it's back to BLOD, as soon as I tried quitting recovery. Now device won't go beyond Google logo, and the bootloader (fastboot) mode is not being detected in PC so I am not able to flash the fixed boot.img file.
I tried all driver installation methods, but the culprit is incorrect device ID being shown to my PC - USB\VID_0000&PID_0002\5&ECB7860&0&9 (unknown usb device - device descriptor request failed). Any idea how I can salvage my device ?
Click to expand...
Click to collapse
I think your issue is different. It sounds like the BLOD. Some people have had success heating their device. Some just enough that it sounds like thermal expansion is enough to make a connection long enough to flash the boot image. Others to the point where they actually get solder to flow. There are some threads here that discuss this.
See this, http://dev-with-alex.blogspot.com/2016/12/oven-fresh-phone.html
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
I saw your post earlier and have been thinking about it. I don't have any good suggestions but Google 15 second adb xda. You'll find a tool there that installs drivers and adb and fastboot. I don't think it will make a difference, but who knows. If I think of anything else I'll post it.
Also with the device connected open a command window, or power shell, and type
adb kill-server
adb start-server
Then if you're in the bootloader, fastboot devices. And keep your fingers crossed.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I used the 15 seconds ADb right from the start. I don´t think, it is a driver issue, because before the wipe, the device had been recognized by the PC, so drivers seemed to be installed correctly. Will try the two commands later on, thanks!

jd1639 said:
I think your issue is different. It sounds like the BLOD. Some people have had success heating their device. Some just enough that it sounds like thermal expansion is enough to make a connection long enough to flash the boot image. Others to the point where they actually get solder to flow. There are some threads here that discuss this.
See this, http://dev-with-alex.blogspot.com/2016/12/oven-fresh-phone.html
Click to expand...
Click to collapse
It was a BLOD issue, like I mentioned. My situation was peculiar, because I had wiped the /data partition when the device was already bootlooping (managed to boot into TWRP after cooling the phone and wiped /data in my infinite wisdom). After that, I was still stuck in BLOD, except one change - PC was no longer recognizing the device in fastboot (see the hardware ID I mentioned above).
How it fixed it:
Removed the case, and heated up my phone with a hair dryer for 5min
Booted it up, it was stuck on Google logo for a fairly long time before bootlooping, as compared to earlier. My guess - it was trying to load system files, which wasn't happening when the phone wasn't heated up.
Now I booted into bootloader and PC was able to recognize the device in fastboot mode.
Finally I was able to flash the moded boot.img files to disable bigger cores and my 5X is back to being my daily driver.

Congrats on fixing your device, but has nothing to do with my issue. My phone is booting just fine and always was. When in Fastboot or in Recovery it is simply not recognized by the computer, although all I did was wiping it.

hsquare said:
Congrats on fixing your device, but has nothing to do with my issue. My phone is booting just fine and always was. When in Fastboot or in Recovery it is simply not recognized by the computer, although all I did was wiping it.
Click to expand...
Click to collapse
Can you tell us what is the hardware device ID for your 5X in bootloader/recovery? It should be under USB controllers section (last) under device management

No, I can´t, because as already stated like three times in this thread probably, it is not recognized at all. It behaves as if nothing was connected to the PC.

hsquare said:
Congrats on fixing your device, but has nothing to do with my issue. My phone is booting just fine and always was. When in Fastboot or in Recovery it is simply not recognized by the computer, although all I did was wiping it.
Click to expand...
Click to collapse
Do you remember what you wiped? I assume it was in twrp?
Sent from my [device_name] using XDA-Developers Legacy app

Yes, I did a full wipe including also data in TWRP.

adb kill-server
adb start-server
did not help unfortunately. Also tried repairing data partition with Ext4. Another phone with the same cable and computer is being recognized just fine. It's really weird. I never had wiping doing any harm.

emmc error? Suddenly black screen

Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!

slev!n said:
Hello guys,
Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.

knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/

knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
slev!n said:
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
Click to expand...
Click to collapse
slev!n said:
Hello guys,
I've got an issue and don't know if it belongs to the build or not. I'm on the last build with my 3T and today after charging my phone I couldn't turn on WiFi or start any app. It just didn't open. So I restated my phone but it never booted. Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
Sounds to me like an hardware error involving (but not necessarily limited to) emmc access. That would explain, why the parts still in ram (like homescreen) were still working but apps won't start anymore, as well as the blank screen on device startup (even the logo needs emmc access to read the logo partition).
Try unbricking (I'm afraid your pc won't find the device, if my guess is correct), if that fails: rma or repair center.

slev!n said:
Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)

150208 said:
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
Click to expand...
Click to collapse
Thanks, I'll create a post there. Just one more post here:
I used this phone just carefully at home as a media device. So this brick came totally out of nowhere. When I connect my bricked 3T now to my computer it makes the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more pop up again.

slev!n said:
I'll create a post there.
Click to expand...
Click to collapse
When you've created that post ask the moderators to move this complete conversation from this thread to the newly created on in the help forum, please. This helps to keep this thread readable and searcheble.
For your trouble: if you can't boot rom, recovery nor fastboot mode, it doesn't make sense to debug the usb connection: what should the pc connect to if none of the three is bootable? There is just nothing up to connect to. That's why I recommended unbrick tool - if that fails rma or go to a repair center.

Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!

Post SS of the device manager after connecting the phone to the PC

150208 said:
Post SS of the device manager after connecting the phone to the PC
Click to expand...
Click to collapse
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
@slev!n: please ask the moderators to move the existing conversation to thos from the los16 thread here. If all postings have moved, ask the moderators to move this thread from op3/help to op3t/help.

@nvertigo67 I wanted to do so and was searching how to contact moderators but couldn't find it in my XDA app. Maybe someone can give me a hint? I'm kind of new on xda... Thanks!
@150208 And as I wrote: it's not possible to get any kind of message on windows anymore. Just the sound appears when I connect and disconnect.
@nvertigo67 I was also following your advice to use the unbrick tool. I followed the steps on oneplus forum:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
When it comes to the integrity check windows doesn't accept "TESTSIGNING ON". And so windows doesn't recognise my phone in the device manager for the next steps.
And I guess RMA or repair centres are super expensive. I don't know if it's worth it? I thought about buying a device with a broken screen on eBay and try to change the motherboard...

Log in with a web browser locate each posting of the comversation. For each posting in question use the little triangle icon at the botom on the left side, report each posting, set non-urgent and pit the link of this thread together with something like "Please move this posting to the linked thread, thanx in advance".
For disabling driver signature enforcement try method 2. from this post: http://maxedtech.com/about-testmode/
Most of tbe time xda postings are more reliable and more current then the Oneplus forums: https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722, https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722

slev!n said:
[MENTION=4405529]i thought about buying a device with a broken screen on eBay and try to change the motherboard...
Click to expand...
Click to collapse
If you already have a thought why do you keep asked here though? If you want another possible solution, at least put an effort to provide the information needed when asked by the one who tried to help you
I'm not into a guessing games, so i'm out
nvertigo67 said:
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
Click to expand...
Click to collapse
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
If it's hw problem, i'll try not to jump on MB conclussion yet, since there are still another possible reason
When talking about MSM, you need to make sure it's available first on the device manager
Otherwise, it's a waste of data for downloading the tool in these human malware days
Oh yes, the msm guide is quite lag behind. You don't need to boot into test mode anymore with the current driver for qualcomm
I flashed a lot qualcomm devices with w10 without the need to boot into test mode

150208 said:
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
Click to expand...
Click to collapse
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
For the costs of rma: maybe it's expensive - maybe oneplus will be obliging... Since you don't relay on the device as your daily driver, you can ask for an estimate of costs - so you can decide if it's worth the costs.

nvertigo67 said:
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
Click to expand...
Click to collapse
Wait, I fail to see your explanation in line with mine. I want to start debug it on the windows side, but you seems to see it on the phone side.
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.

150208 said:
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
Click to expand...
Click to collapse
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc. In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side. Once this is fixed (at least fastboot mode is up again) you can utilize the "normal" usb connection again.
What do you want to do with the usb connection, if neither fastboot mode nor recovery is up amd running? What is your suggested next step, if the device is recognized? What should the pc recognize if neither fastboot nor adb os an option? Which command or procedure will fix the emmc?

nvertigo67 said:
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc.
Click to expand...
Click to collapse
Yes, there are other tools but i'm not gonna bother since it's paid
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect. There are 4 status when a device plugged into the pc.
1. detected and driver is loaded
2. detected and driver isn't loaded
3. detected but not recognized
4. no sign at all
1 and 2 is sw problem, 3 and 4 is hw problem
In order for MSM to do it's job, you need to have either problem no 1 or 2 with qualcomm qloader 9008 driver already or later detected in devmanager
So it's important to know the driver status
OP states there was sounds coming then nothing, which mean it's either 2 or 3, more like 3 but again i repeating myself i don't like guessing games
I don't understand the part why you're explaining/asking about fastboot recovery or etc, his phone is on dead state, nothing-literally-no sign of life unless he plug it to the pc and then it making sounds for the first time,
Why do you even bother thinking about it?
nvertigo67 said:
Which command or procedure will fix the emmc?
Click to expand...
Click to collapse
No procedure will fixed his phone since there are no enough information
I think your other question should be already answered. If else, i don't know what to say anymore.

150208 said:
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect.
Click to expand...
Click to collapse
If so, please explain how you can format a partition or fix the partition table if neither fastboot mode nor recovery (or a rooted system for that matter) is bootable.
@slev!n: please give a screenshot of the device manager to @150208. I'm too curious to learn how to fix a broken emmc without recovery nor fastboot mode.

Thank you so far!
I dont want to bother someone. Just thinking about further options thats why I wrote my thought about replacing the motherboard down.
I 'm in test mode now and I did this:
"Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for a few seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB (under COMs and Ports)]."
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?

slev!n said:
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
Click to expand...
Click to collapse
The pic is from msm tool, not the device manager. No unknown device in device manager?